1 This document summarizes new features and bugfixes in each stable release
2 of Tor. If you want to see more detailed descriptions of the changes in
3 each development snapshot, see the ChangeLog file.
5 Changes in version 0.2.9.9 - 2017-01-23
6 Tor 0.2.9.9 fixes a denial-of-service bug where an attacker could
7 cause relays and clients to crash, even if they were not built with
8 the --enable-expensive-hardening option. This bug affects all 0.2.9.x
9 versions, and also affects 0.3.0.1-alpha: all relays running an affected
10 version should upgrade.
12 This release also resolves a client-side onion service reachability
13 bug, and resolves a pair of small portability issues.
15 o Major bugfixes (security):
16 - Downgrade the "-ftrapv" option from "always on" to "only on when
17 --enable-expensive-hardening is provided." This hardening option,
18 like others, can turn survivable bugs into crashes -- and having
19 it on by default made a (relatively harmless) integer overflow bug
20 into a denial-of-service bug. Fixes bug 21278 (TROVE-2017-001);
21 bugfix on 0.2.9.1-alpha.
23 o Major bugfixes (client, onion service):
24 - Fix a client-side onion service reachability bug, where multiple
25 socks requests to an onion service (or a single slow request)
26 could cause us to mistakenly mark some of the service's
27 introduction points as failed, and we cache that failure so
28 eventually we run out and can't reach the service. Also resolves a
29 mysterious "Remote server sent bogus reason code 65021" log
30 warning. The bug was introduced in ticket 17218, where we tried to
31 remember the circuit end reason as a uint16_t, which mangled
32 negative values. Partially fixes bug 21056 and fixes bug 20307;
33 bugfix on 0.2.8.1-alpha.
35 o Minor features (geoip):
36 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
39 o Minor bugfixes (portability):
40 - Avoid crashing when Tor is built using headers that contain
41 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
42 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
44 - Fix Libevent detection on platforms without Libevent 1 headers
45 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
48 Changes in version 0.2.8.12 - 2016-12-19
49 Tor 0.2.8.12 backports a fix for a medium-severity issue (bug 21018
50 below) where Tor clients could crash when attempting to visit a
51 hostile hidden service. Clients are recommended to upgrade as packages
52 become available for their systems.
54 It also includes an updated list of fallback directories, backported
57 Now that the Tor 0.2.9 series is stable, only major bugfixes will be
58 backported to 0.2.8 in the future.
60 o Major bugfixes (parsing, security, backported from 0.2.9.8):
61 - Fix a bug in parsing that could cause clients to read a single
62 byte past the end of an allocated region. This bug could be used
63 to cause hardened clients (built with --enable-expensive-hardening)
64 to crash if they tried to visit a hostile hidden service. Non-
65 hardened clients are only affected depending on the details of
66 their platform's memory allocator. Fixes bug 21018; bugfix on
67 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
68 2016-12-002 and as CVE-2016-1254.
70 o Minor features (fallback directory list, backported from 0.2.9.8):
71 - Replace the 81 remaining fallbacks of the 100 originally
72 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
73 fallbacks (123 new, 54 existing, 27 removed) generated in December
74 2016. Resolves ticket 20170.
76 o Minor features (geoip, backported from 0.2.9.7-rc):
77 - Update geoip and geoip6 to the December 7 2016 Maxmind GeoLite2
81 Changes in version 0.2.9.8 - 2016-12-19
82 Tor 0.2.9.8 is the first stable release of the Tor 0.2.9 series.
84 The Tor 0.2.9 series makes mandatory a number of security features
85 that were formerly optional. It includes support for a new shared-
86 randomness protocol that will form the basis for next generation
87 hidden services, includes a single-hop hidden service mode for
88 optimizing .onion services that don't actually want to be hidden,
89 tries harder not to overload the directory authorities with excessive
90 downloads, and supports a better protocol versioning scheme for
91 improved compatibility with other implementations of the Tor protocol.
93 And of course, there are numerous other bugfixes and improvements.
95 This release also includes a fix for a medium-severity issue (bug
96 21018 below) where Tor clients could crash when attempting to visit a
97 hostile hidden service. Clients are recommended to upgrade as packages
98 become available for their systems.
100 Below are listed the changes since Tor 0.2.8.11. For a list of
101 changes since 0.2.9.7-rc, see the ChangeLog file.
103 o New system requirements:
104 - When building with OpenSSL, Tor now requires version 1.0.1 or
105 later. OpenSSL 1.0.0 and earlier are no longer supported by the
106 OpenSSL team, and should not be used. Closes ticket 20303.
107 - Tor now requires Libevent version 2.0.10-stable or later. Older
108 versions of Libevent have less efficient backends for several
109 platforms, and lack the DNS code that we use for our server-side
110 DNS support. This implements ticket 19554.
111 - Tor now requires zlib version 1.2 or later, for security,
112 efficiency, and (eventually) gzip support. (Back when we started,
113 zlib 1.1 and zlib 1.0 were still found in the wild. 1.2 was
114 released in 2003. We recommend the latest version.)
116 o Deprecated features:
117 - A number of DNS-cache-related sub-options for client ports are now
118 deprecated for security reasons, and may be removed in a future
119 version of Tor. (We believe that client-side DNS caching is a bad
120 idea for anonymity, and you should not turn it on.) The options
121 are: CacheDNS, CacheIPv4DNS, CacheIPv6DNS, UseDNSCache,
122 UseIPv4Cache, and UseIPv6Cache.
123 - A number of options are deprecated for security reasons, and may
124 be removed in a future version of Tor. The options are:
125 AllowDotExit, AllowInvalidNodes, AllowSingleHopCircuits,
126 AllowSingleHopExits, ClientDNSRejectInternalAddresses,
127 CloseHSClientCircuitsImmediatelyOnTimeout,
128 CloseHSServiceRendCircuitsImmediatelyOnTimeout,
129 ExcludeSingleHopRelays, FastFirstHopPK, TLSECGroup,
130 UseNTorHandshake, and WarnUnsafeSocks.
131 - The *ListenAddress options are now deprecated as unnecessary: the
132 corresponding *Port options should be used instead. These options
133 may someday be removed. The affected options are:
134 ControlListenAddress, DNSListenAddress, DirListenAddress,
135 NATDListenAddress, ORListenAddress, SocksListenAddress,
136 and TransListenAddress.
138 o Major bugfixes (parsing, security, new since 0.2.9.7-rc):
139 - Fix a bug in parsing that could cause clients to read a single
140 byte past the end of an allocated region. This bug could be used
141 to cause hardened clients (built with --enable-expensive-hardening)
142 to crash if they tried to visit a hostile hidden service. Non-
143 hardened clients are only affected depending on the details of
144 their platform's memory allocator. Fixes bug 21018; bugfix on
145 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
146 2016-12-002 and as CVE-2016-1254.
148 o Major features (build, hardening):
149 - Tor now builds with -ftrapv by default on compilers that support
150 it. This option detects signed integer overflow (which C forbids),
151 and turns it into a hard-failure. We do not apply this option to
152 code that needs to run in constant time to avoid side-channels;
153 instead, we use -fwrapv in that code. Closes ticket 17983.
154 - When --enable-expensive-hardening is selected, stop applying the
155 clang/gcc sanitizers to code that needs to run in constant time.
156 Although we are aware of no introduced side-channels, we are not
157 able to prove that there are none. Related to ticket 17983.
159 o Major features (circuit building, security):
160 - Authorities, relays, and clients now require ntor keys in all
161 descriptors, for all hops (except for rare hidden service protocol
162 cases), for all circuits, and for all other roles. Part of
164 - Authorities, relays, and clients only use ntor, except for
165 rare cases in the hidden service protocol. Part of ticket 19163.
167 o Major features (compilation):
168 - Our big list of extra GCC warnings is now enabled by default when
169 building with GCC (or with anything like Clang that claims to be
170 GCC-compatible). To make all warnings into fatal compilation
171 errors, pass --enable-fatal-warnings to configure. Closes
173 - Use the Autoconf macro AC_USE_SYSTEM_EXTENSIONS to automatically
174 turn on C and POSIX extensions. (Previously, we attempted to do
175 this on an ad hoc basis.) Closes ticket 19139.
177 o Major features (directory authorities, hidden services):
178 - Directory authorities can now perform the shared randomness
179 protocol specified by proposal 250. Using this protocol, directory
180 authorities generate a global fresh random value every day. In the
181 future, this value will be used by hidden services to select
182 HSDirs. This release implements the directory authority feature;
183 the hidden service side will be implemented in the future as part
184 of proposal 224. Resolves ticket 16943; implements proposal 250.
186 o Major features (downloading, random exponential backoff):
187 - When we fail to download an object from a directory service, wait
188 for an (exponentially increasing) randomized amount of time before
189 retrying, rather than a fixed interval as we did before. This
190 prevents a group of Tor instances from becoming too synchronized,
191 or a single Tor instance from becoming too predictable, in its
192 download schedule. Closes ticket 15942.
194 o Major features (resource management):
195 - Tor can now notice it is about to run out of sockets, and
196 preemptively close connections of lower priority. (This feature is
197 off by default for now, since the current prioritizing method is
198 yet not mature enough. You can enable it by setting
199 "DisableOOSCheck 0", but watch out: it might close some sockets
200 you would rather have it keep.) Closes ticket 18640.
202 o Major features (single-hop "hidden" services):
203 - Add experimental HiddenServiceSingleHopMode and
204 HiddenServiceNonAnonymousMode options. When both are set to 1,
205 every hidden service on that Tor instance becomes a non-anonymous
206 Single Onion Service. Single Onions make one-hop (direct)
207 connections to their introduction and rendezvous points. One-hop
208 circuits make Single Onion servers easily locatable, but clients
209 remain location-anonymous. This is compatible with the existing
210 hidden service implementation, and works on the current Tor
211 network without any changes to older relays or clients. Implements
212 proposal 260, completes ticket 17178. Patch by teor and asn.
214 o Major features (subprotocol versions):
215 - Tor directory authorities now vote on a set of recommended
216 "subprotocol versions", and on a set of required subprotocol
217 versions. Clients and relays that lack support for a _required_
218 subprotocol version will not start; those that lack support for a
219 _recommended_ subprotocol version will warn the user to upgrade.
220 This change allows compatible implementations of the Tor protocol(s)
221 to exist without pretending to be 100% bug-compatible with
222 particular releases of Tor itself. Closes ticket 19958; implements
223 part of proposal 264.
225 o Major bugfixes (circuit building):
226 - Hidden service client-to-intro-point and service-to-rendezvous-
227 point circuits use the TAP key supplied by the protocol, to avoid
228 epistemic attacks. Fixes bug 19163; bugfix on 0.2.4.18-rc.
230 o Major bugfixes (download scheduling):
231 - Avoid resetting download status for consensuses hourly, since we
232 already have another, smarter retry mechanism. Fixes bug 8625;
233 bugfix on 0.2.0.9-alpha.
234 - If a consensus expires while we are waiting for certificates to
235 download, stop waiting for certificates.
236 - If we stop waiting for certificates less than a minute after we
237 started downloading them, do not consider the certificate download
238 failure a separate failure. Fixes bug 20533; bugfix
240 - When using exponential backoff in test networks, use a lower
241 exponent, so the delays do not vary as much. This helps test
242 networks bootstrap consistently. Fixes bug 20597; bugfix on 20499.
244 o Major bugfixes (exit policies):
245 - Avoid disclosing exit outbound bind addresses, configured port
246 bind addresses, and local interface addresses in relay descriptors
247 by default under ExitPolicyRejectPrivate. Instead, only reject
248 these (otherwise unlisted) addresses if
249 ExitPolicyRejectLocalInterfaces is set. Fixes bug 18456; bugfix on
250 0.2.7.2-alpha. Patch by teor.
252 o Major bugfixes (hidden services):
253 - Allow Tor clients with appropriate controllers to work with
254 FetchHidServDescriptors set to 0. Previously, this option also
255 disabled descriptor cache lookup, thus breaking hidden services
256 entirely. Fixes bug 18704; bugfix on 0.2.0.20-rc. Patch by "twim".
257 - Clients now require hidden services to include the TAP keys for
258 their intro points in the hidden service descriptor. This prevents
259 an inadvertent upgrade to ntor, which a malicious hidden service
260 could use to distinguish clients by consensus version. Fixes bug
261 20012; bugfix on 0.2.4.8-alpha. Patch by teor.
263 o Major bugfixes (relay, resolver, logging):
264 - For relays that don't know their own address, avoid attempting a
265 local hostname resolve for each descriptor we download. This
266 will cut down on the number of "Success: chose address 'x.x.x.x'"
267 log lines, and also avoid confusing clock jumps if the resolver
268 is slow. Fixes bugs 20423 and 20610; bugfix on 0.2.8.1-alpha.
270 o Minor features (port flags):
271 - Add new flags to the *Port options to give finer control over which
272 requests are allowed. The flags are NoDNSRequest, NoOnionTraffic,
273 and the synthetic flag OnionTrafficOnly, which is equivalent to
274 NoDNSRequest, NoIPv4Traffic, and NoIPv6Traffic. Closes enhancement
275 18693; patch by "teor".
277 o Minor features (build, hardening):
278 - Detect and work around a libclang_rt problem that would prevent
279 clang from finding __mulodi4() on some 32-bit platforms, and thus
280 keep -ftrapv from linking on those systems. Closes ticket 19079.
281 - When building on a system without runtime support for the runtime
282 hardening options, try to log a useful warning at configuration
283 time, rather than an incomprehensible warning at link time. If
284 expensive hardening was requested, this warning becomes an error.
287 o Minor features (client, directory):
288 - Since authorities now omit all routers that lack the Running and
289 Valid flags, we assume that any relay listed in the consensus must
290 have those flags. Closes ticket 20001; implements part of
293 o Minor features (code safety):
294 - In our integer-parsing functions, ensure that the maximum value we
295 allow is no smaller than the minimum value. Closes ticket 19063;
298 o Minor features (compilation, portability):
299 - Compile correctly on MacOS 10.12 (aka "Sierra"). Closes
302 o Minor features (config):
303 - Warn users when descriptor and port addresses are inconsistent.
304 Mitigates bug 13953; patch by teor.
306 o Minor features (controller):
307 - Allow controllers to configure basic client authorization on
308 hidden services when they create them with the ADD_ONION controller
309 command. Implements ticket 15588. Patch by "special".
310 - Fire a STATUS_SERVER controller event whenever the hibernation
311 status changes between "awake"/"soft"/"hard". Closes ticket 18685.
312 - Implement new GETINFO queries for all downloads that use
313 download_status_t to schedule retries. This allows controllers to
314 examine the schedule for pending downloads. Closes ticket 19323.
316 o Minor features (development tools, etags):
317 - Teach the "make tags" Makefile target how to correctly find
318 "MOCK_IMPL" function definitions. Patch from nherring; closes
321 o Minor features (directory authority):
322 - After voting, if the authorities decide that a relay is not
323 "Valid", they no longer include it in the consensus at all. Closes
324 ticket 20002; implements part of proposal 272.
325 - Directory authorities now only give the Guard flag to a relay if
326 they are also giving it the Stable flag. This change allows us to
327 simplify path selection for clients. It should have minimal effect
328 in practice, since >99% of Guards already have the Stable flag.
329 Implements ticket 18624.
330 - Directory authorities now write their v3-status-votes file out to
331 disk earlier in the consensus process, so we have a record of the
332 votes even if we abort the consensus process. Resolves
335 o Minor features (fallback directory list, new since 0.2.9.7-rc):
336 - Replace the 81 remaining fallbacks of the 100 originally
337 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
338 fallbacks (123 new, 54 existing, 27 removed) generated in December
339 2016. Resolves ticket 20170.
341 o Minor features (hidden service):
342 - Stop being so strict about the payload length of "rendezvous1"
343 cells. We used to be locked in to the "TAP" handshake length, and
344 now we can handle better handshakes like "ntor". Resolves
347 o Minor features (infrastructure, time):
348 - Tor now includes an improved timer backend, so that we can
349 efficiently support tens or hundreds of thousands of concurrent
350 timers, as will be needed for some of our planned anti-traffic-
351 analysis work. This code is based on William Ahern's "timeout.c"
352 project, which implements a "tickless hierarchical timing wheel".
354 - Tor now uses the operating system's monotonic timers (where
355 available) for internal fine-grained timing. Previously we would
356 look at the system clock, and then attempt to compensate for the
357 clock running backwards. Closes ticket 18908.
359 o Minor features (logging):
360 - Add a set of macros to check nonfatal assertions, for internal
361 use. Migrating more of our checks to these should help us avoid
362 needless crash bugs. Closes ticket 18613.
363 - Provide a more useful warning message when configured with an
364 invalid Nickname. Closes ticket 18300; patch from "icanhasaccount".
365 - When dumping unparseable router descriptors, optionally store them
366 in separate files, named by digest, up to a configurable size
367 limit. You can change the size limit by setting the
368 MaxUnparseableDescSizeToLog option, and disable this feature by
369 setting that option to 0. Closes ticket 18322.
371 o Minor features (performance):
372 - Change the "optimistic data" extension from "off by default" to
373 "on by default". The default was ordinarily overridden by a
374 consensus option, but when clients were bootstrapping for the
375 first time, they would not have a consensus to get the option
376 from. Changing this default saves a round-trip during startup.
379 o Minor features (relay, usability):
380 - When the directory authorities refuse a bad relay's descriptor,
381 encourage the relay operator to contact us. Many relay operators
382 won't notice this line in their logs, but it's a win if even a few
383 learn why we don't like what their relay was doing. Resolves
386 o Minor features (security, TLS):
387 - Servers no longer support clients that lack AES ciphersuites.
388 (3DES is no longer considered an acceptable cipher.) We believe
389 that no such Tor clients currently exist, since Tor has required
390 OpenSSL 0.9.7 or later since 2009. Closes ticket 19998.
392 o Minor features (testing):
393 - Disable memory protections on OpenBSD when performing our unit
394 tests for memwipe(). The test deliberately invokes undefined
395 behavior, and the OpenBSD protections interfere with this. Patch
396 from "rubiate". Closes ticket 20066.
397 - Move the test-network.sh script to chutney, and modify tor's test-
398 network.sh to call the (newer) chutney version when available.
399 Resolves ticket 19116. Patch by teor.
400 - Use the lcov convention for marking lines as unreachable, so that
401 we don't count them when we're generating test coverage data.
402 Update our coverage tools to understand this convention. Closes
404 - Our link-handshake unit tests now check that when invalid
405 handshakes fail, they fail with the error messages we expected.
406 - Our unit testing code that captures log messages no longer
407 prevents them from being written out if the user asked for them
408 (by passing --debug or --info or --notice or --warn to the "test"
409 binary). This change prevents us from missing unexpected log
410 messages simply because we were looking for others. Related to
412 - The unit tests now log all warning messages with the "BUG" flag.
413 Previously, they only logged errors by default. This change will
414 help us make our testing code more correct, and make sure that we
415 only hit this code when we mean to. In the meantime, however,
416 there will be more warnings in the unit test logs than before.
417 This is preparatory work for ticket 19999.
418 - The unit tests now treat any failure of a "tor_assert_nonfatal()"
419 assertion as a test failure.
420 - We've done significant work to make the unit tests run faster.
422 o Minor features (testing, ipv6):
423 - Add the hs-ipv6 chutney target to make test-network-all's IPv6
424 tests. Remove bridges+hs, as it's somewhat redundant. This
425 requires a recent chutney version that supports IPv6 clients,
426 relays, and authorities. Closes ticket 20069; patch by teor.
427 - Add the single-onion and single-onion-ipv6 chutney targets to
428 "make test-network-all". This requires a recent chutney version
429 with the single onion network flavors (git c72a652 or later).
430 Closes ticket 20072; patch by teor.
432 o Minor features (Tor2web):
433 - Make Tor2web clients respect ReachableAddresses. This feature was
434 inadvertently enabled in 0.2.8.6, then removed by bugfix 19973 on
435 0.2.8.7. Implements feature 20034. Patch by teor.
437 o Minor features (unix domain sockets):
438 - When configuring a unix domain socket for a SocksPort,
439 ControlPort, or Hidden service, you can now wrap the address in
440 quotes, using C-style escapes inside the quotes. This allows unix
441 domain socket paths to contain spaces. Resolves ticket 18753.
443 o Minor features (user interface):
444 - Tor now supports the ability to declare options deprecated, so
445 that we can recommend that people stop using them. Previously, this
446 was done in an ad-hoc way. There is a new --list-deprecated-options
447 command-line option to list all of the deprecated options. Closes
450 o Minor features (virtual addresses):
451 - Increase the maximum number of bits for the IPv6 virtual network
452 prefix from 16 to 104. In this way, the condition for address
453 allocation is less restrictive. Closes ticket 20151; feature
456 o Minor bug fixes (circuits):
457 - Use the CircuitBuildTimeout option whenever
458 LearnCircuitBuildTimeout is disabled. Previously, we would respect
459 the option when a user disabled it, but not when it was disabled
460 because some other option was set. Fixes bug 20073; bugfix on
461 0.2.4.12-alpha. Patch by teor.
463 o Minor bugfixes (build):
464 - The current Git revision when building from a local repository is
465 now detected correctly when using git worktrees. Fixes bug 20492;
466 bugfix on 0.2.3.9-alpha.
468 o Minor bugfixes (relay address discovery):
469 - Stop reordering IP addresses returned by the OS. This makes it
470 more likely that Tor will guess the same relay IP address every
471 time. Fixes issue 20163; bugfix on 0.2.7.1-alpha, ticket 17027.
472 Reported by René Mayrhofer, patch by "cypherpunks".
474 o Minor bugfixes (memory allocation):
475 - Change how we allocate memory for large chunks on buffers, to
476 avoid a (currently impossible) integer overflow, and to waste less
477 space when allocating unusually large chunks. Fixes bug 20081;
478 bugfix on 0.2.0.16-alpha. Issue identified by Guido Vranken.
480 o Minor bugfixes (bootstrap):
481 - Remember the directory server we fetched the consensus or previous
482 certificates from, and use it to fetch future authority
483 certificates. This change improves bootstrapping performance.
484 Fixes bug 18963; bugfix on 0.2.8.1-alpha.
486 o Minor bugfixes (circuits):
487 - Make sure extend_info_from_router() is only called on servers.
488 Fixes bug 19639; bugfix on 0.2.8.1-alpha.
490 o Minor bugfixes (client, fascistfirewall):
491 - Avoid spurious warnings when ReachableAddresses or FascistFirewall
492 is set. Fixes bug 20306; bugfix on 0.2.8.2-alpha.
494 o Minor bugfixes (client, unix domain sockets):
495 - Disable IsolateClientAddr when using AF_UNIX backed SocksPorts as
496 the client address is meaningless. Fixes bug 20261; bugfix
499 o Minor bugfixes (code style):
500 - Fix an integer signedness conversion issue in the case conversion
501 tables. Fixes bug 19168; bugfix on 0.2.1.11-alpha.
503 o Minor bugfixes (compilation):
504 - Build correctly on versions of libevent2 without support for
505 evutil_secure_rng_add_bytes(). Fixes bug 19904; bugfix
507 - When building with Clang, use a full set of GCC warnings.
508 (Previously, we included only a subset, because of the way we
509 detected them.) Fixes bug 19216; bugfix on 0.2.0.1-alpha.
510 - Detect Libevent2 functions correctly on systems that provide
511 libevent2, but where libevent1 is linked with -levent. Fixes bug
512 19904; bugfix on 0.2.2.24-alpha. Patch from Rubiate.
513 - Run correctly when built on Windows build environments that
514 require _vcsprintf(). Fixes bug 20560; bugfix on 0.2.2.11-alpha.
516 o Minor bugfixes (configuration):
517 - When parsing quoted configuration values from the torrc file,
518 handle Windows line endings correctly. Fixes bug 19167; bugfix on
519 0.2.0.16-alpha. Patch from "Pingl".
521 o Minor bugfixes (directory authority):
522 - Authorities now sort the "package" lines in their votes, for ease
523 of debugging. (They are already sorted in consensus documents.)
524 Fixes bug 18840; bugfix on 0.2.6.3-alpha.
525 - Die with a more useful error when the operator forgets to place
526 the authority_signing_key file into the keys directory. This
527 avoids an uninformative assert & traceback about having an invalid
528 key. Fixes bug 20065; bugfix on 0.2.0.1-alpha.
529 - When allowing private addresses, mark Exits that only exit to
530 private locations as such. Fixes bug 20064; bugfix
532 - When parsing a detached signature, make sure we use the length of
533 the digest algorithm instead of a hardcoded DIGEST256_LEN in
534 order to avoid comparing bytes out-of-bounds with a smaller digest
535 length such as SHA1. Fixes bug 19066; bugfix on 0.2.2.6-alpha.
537 o Minor bugfixes (getpass):
538 - Defensively fix a non-triggerable heap corruption at do_getpass()
539 to protect ourselves from mistakes in the future. Fixes bug
540 19223; bugfix on 0.2.7.3-rc. Bug found by Guido Vranken, patch
543 o Minor bugfixes (guard selection):
544 - Don't mark guards as unreachable if connection_connect() fails.
545 That function fails for local reasons, so it shouldn't reveal
546 anything about the status of the guard. Fixes bug 14334; bugfix
548 - Use a single entry guard even if the NumEntryGuards consensus
549 parameter is not provided. Fixes bug 17688; bugfix
552 o Minor bugfixes (hidden services):
553 - Increase the minimum number of internal circuits we preemptively
554 build from 2 to 3, so a circuit is available when a client
555 connects to another onion service. Fixes bug 13239; bugfix
557 - Allow hidden services to run on IPv6 addresses even when the
558 IPv6Exit option is not set. Fixes bug 18357; bugfix
560 - Stop logging intro point details to the client log on certain
561 error conditions. Fixed as part of bug 20012; bugfix on
562 0.2.4.8-alpha. Patch by teor.
563 - When deleting an ephemeral hidden service, close its intro points
564 even if they are not completely open. Fixes bug 18604; bugfix
566 - When configuring hidden services, check every hidden service
567 directory's permissions. Previously, we only checked the last
568 hidden service. Fixes bug 20529; bugfix on 0.2.6.2-alpha.
570 o Minor bugfixes (IPv6, testing):
571 - Check for IPv6 correctly on Linux when running test networks.
572 Fixes bug 19905; bugfix on 0.2.7.3-rc; patch by teor.
574 o Minor bugfixes (Linux seccomp2 sandbox):
575 - Add permission to run the sched_yield() and sigaltstack() system
576 calls, in order to support versions of Tor compiled with asan or
577 ubsan code that use these calls. Now "sandbox 1" and
578 "--enable-expensive-hardening" should be compatible on more
579 systems. Fixes bug 20063; bugfix on 0.2.5.1-alpha.
581 o Minor bugfixes (logging):
582 - Downgrade a harmless log message about the
583 pending_entry_connections list from "warn" to "info". Mitigates
585 - Log a more accurate message when we fail to dump a microdescriptor.
586 Fixes bug 17758; bugfix on 0.2.2.8-alpha. Patch from Daniel Pinto.
587 - When logging a directory ownership mismatch, log the owning
588 username correctly. Fixes bug 19578; bugfix on 0.2.2.29-beta.
589 - When we are unable to remove the bw_accounting file, do not warn
590 if the reason we couldn't remove it was that it didn't exist.
591 Fixes bug 19964; bugfix on 0.2.5.4-alpha. Patch from pastly.
593 o Minor bugfixes (memory leak):
594 - Fix a series of slow memory leaks related to parsing torrc files
595 and options. Fixes bug 19466; bugfix on 0.2.1.6-alpha.
596 - Avoid a small memory leak when informing worker threads about
597 rotated onion keys. Fixes bug 20401; bugfix on 0.2.6.3-alpha.
598 - Fix a small memory leak when receiving AF_UNIX connections on a
599 SocksPort. Fixes bug 20716; bugfix on 0.2.6.3-alpha.
600 - When moving a signed descriptor object from a source to an
601 existing destination, free the allocated memory inside that
602 destination object. Fixes bug 20715; bugfix on 0.2.8.3-alpha.
603 - Fix a memory leak and use-after-free error when removing entries
604 from the sandbox's getaddrinfo() cache. Fixes bug 20710; bugfix on
605 0.2.5.5-alpha. Patch from "cypherpunks".
606 - Fix a small, uncommon memory leak that could occur when reading a
607 truncated ed25519 key file. Fixes bug 18956; bugfix
610 o Minor bugfixes (option parsing):
611 - Count unix sockets when counting client listeners (SOCKS, Trans,
612 NATD, and DNS). This has no user-visible behavior changes: these
613 options are set once, and never read. Required for correct
614 behavior in ticket 17178. Fixes bug 19677; bugfix on
615 0.2.6.3-alpha. Patch by teor.
617 o Minor bugfixes (options):
618 - Check the consistency of UseEntryGuards and EntryNodes more
619 reliably. Fixes bug 20074; bugfix on 0.2.4.12-alpha. Patch
621 - Stop changing the configured value of UseEntryGuards on
622 authorities and Tor2web clients. Fixes bug 20074; bugfix on
623 commits 51fc6799 in 0.1.1.16-rc and acda1735 in 0.2.4.3-alpha.
626 o Minor bugfixes (relay):
627 - Ensure relays don't make multiple connections during bootstrap.
628 Fixes bug 20591; bugfix on 0.2.8.1-alpha.
629 - Do not try to parallelize workers more than 16x without the user
630 explicitly configuring us to do so, even if we do detect more than
631 16 CPU cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
633 o Minor bugfixes (testing):
634 - The test-stem and test-network makefile targets now depend only on
635 the tor binary that they are testing. Previously, they depended on
636 "make all". Fixes bug 18240; bugfix on 0.2.8.2-alpha. Based on a
637 patch from "cypherpunks".
638 - Allow clients to retry HSDirs much faster in test networks. Fixes
639 bug 19702; bugfix on 0.2.7.1-alpha. Patch by teor.
640 - Avoid a unit test failure on systems with over 16 detectable CPU
641 cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
642 - Let backtrace tests work correctly under AddressSanitizer:
643 disable ASAN's detection of segmentation faults while running
644 test_bt.sh, so that we can make sure that our own backtrace
645 generation code works. Fixes bug 18934; bugfix
646 on 0.2.5.2-alpha. Patch from "cypherpunks".
647 - Fix the test-network-all target on out-of-tree builds by using the
648 correct path to the test driver script. Fixes bug 19421; bugfix
650 - Stop spurious failures in the local interface address discovery
651 unit tests. Fixes bug 20634; bugfix on 0.2.8.1-alpha; patch by
653 - Use ECDHE ciphers instead of ECDH in tortls tests. LibreSSL has
654 removed the ECDH ciphers which caused the tests to fail on
655 platforms which use it. Fixes bug 20460; bugfix on 0.2.8.1-alpha.
656 - The tor_tls_server_info_callback unit test no longer crashes when
657 debug-level logging is turned on. Fixes bug 20041; bugfix
660 o Minor bugfixes (time):
661 - Improve overflow checks in tv_udiff and tv_mdiff. Fixes bug 19483;
662 bugfix on all released tor versions.
663 - When computing the difference between two times in milliseconds,
664 we now round to the nearest millisecond correctly. Previously, we
665 could sometimes round in the wrong direction. Fixes bug 19428;
666 bugfix on 0.2.2.2-alpha.
668 o Minor bugfixes (Tor2web):
669 - Prevent Tor2web clients from running hidden services: these services
670 are not anonymous due to the one-hop client paths. Fixes bug
671 19678. Patch by teor.
673 o Minor bugfixes (user interface):
674 - Display a more accurate number of suppressed messages in the log
675 rate-limiter. Previously, there was a potential integer overflow
676 in the counter. Now, if the number of messages hits a maximum, the
677 rate-limiter doesn't count any further. Fixes bug 19435; bugfix
679 - Fix a typo in the passphrase prompt for the ed25519 identity key.
680 Fixes bug 19503; bugfix on 0.2.7.2-alpha.
682 o Code simplification and refactoring:
683 - Remove redundant declarations of the MIN macro. Closes
685 - Rename tor_dup_addr() to tor_addr_to_str_dup() to avoid confusion.
686 Closes ticket 18462; patch from "icanhasaccount".
687 - Split the 600-line directory_handle_command_get function into
688 separate functions for different URL types. Closes ticket 16698.
691 - Add module-level internal documentation for 36 C files that
692 previously didn't have a high-level overview. Closes ticket 20385.
693 - Correct the IPv6 syntax in our documentation for the
694 VirtualAddrNetworkIPv6 torrc option. Closes ticket 19743.
695 - Correct the minimum bandwidth value in torrc.sample, and queue a
696 corresponding change for torrc.minimal. Closes ticket 20085.
697 - Fix spelling of "--enable-tor2web-mode" in the manpage. Closes
698 ticket 19153. Patch from "U+039b".
699 - Module-level documentation for several more modules. Closes
700 tickets 19287 and 19290.
701 - Document the --passphrase-fd option in the tor manpage. Fixes bug
702 19504; bugfix on 0.2.7.3-rc.
703 - Document the default PathsNeededToBuildCircuits value that's used
704 by clients when the directory authorities don't set
705 min_paths_for_circs_pct. Fixes bug 20117; bugfix on 0.2.4.10-alpha.
706 Patch by teor, reported by Jesse V.
707 - Fix manual for the User option: it takes a username, not a UID.
708 Fixes bug 19122; bugfix on 0.0.2pre16 (the first version to have
710 - Fix the description of the --passphrase-fd option in the
711 tor-gencert manpage. The option is used to pass the number of a
712 file descriptor to read the passphrase from, not to read the file
713 descriptor from. Fixes bug 19505; bugfix on 0.2.0.20-alpha.
716 - We no longer include the (dead, deprecated) bufferevent code in
717 Tor. Closes ticket 19450. Based on a patch from "U+039b".
720 - Remove support for "GET /tor/bytes.txt" DirPort request, and
721 "GETINFO dir-usage" controller request, which were only available
722 via a compile-time option in Tor anyway. Feature was added in
723 0.2.2.1-alpha. Resolves ticket 19035.
724 - There is no longer a compile-time option to disable support for
725 TransPort. (If you don't want TransPort, just don't use it.) Patch
726 from "U+039b". Closes ticket 19449.
729 - Run more workqueue tests as part of "make check". These had
730 previously been implemented, but you needed to know special
731 command-line options to enable them.
732 - We now have unit tests for our code to reject zlib "compression
733 bombs". (Fortunately, the code works fine.)
736 Changes in version 0.2.8.11 - 2016-12-08
737 Tor 0.2.8.11 backports fixes for additional portability issues that
738 could prevent Tor from building correctly on OSX Sierra, or with
739 OpenSSL 1.1. Affected users should upgrade; others can safely stay
742 o Minor bugfixes (portability):
743 - Avoid compilation errors when building on OSX Sierra. Sierra began
744 to support the getentropy() and clock_gettime() APIs, but created
745 a few problems in doing so. Tor 0.2.9 has a more thorough set of
746 workarounds; in 0.2.8, we are just using the /dev/urandom and mach
747 monotonic time interfaces. Fixes bug 20865. Bugfix
750 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
751 - Fix compilation with OpenSSL 1.1 and less commonly-used CPU
752 architectures. Closes ticket 20588.
755 Changes in version 0.2.8.10 - 2016-12-02
756 Tor 0.2.8.10 backports a fix for a bug that would sometimes make clients
757 unusable after they left standby mode. It also backports fixes for
758 a few portability issues and a small but problematic memory leak.
760 o Major bugfixes (client reliability, backport from 0.2.9.5-alpha):
761 - When Tor leaves standby because of a new application request, open
762 circuits as needed to serve that request. Previously, we would
763 potentially wait a very long time. Fixes part of bug 19969; bugfix
766 o Major bugfixes (client performance, backport from 0.2.9.5-alpha):
767 - Clients now respond to new application stream requests immediately
768 when they arrive, rather than waiting up to one second before
769 starting to handle them. Fixes part of bug 19969; bugfix
772 o Minor bugfixes (portability, backport from 0.2.9.6-rc):
773 - Work around a bug in the OSX 10.12 SDK that would prevent us from
774 successfully targeting earlier versions of OSX. Resolves
777 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
778 - Fix implicit conversion warnings under OpenSSL 1.1. Fixes bug
779 20551; bugfix on 0.2.1.1-alpha.
781 o Minor bugfixes (relay, backport from 0.2.9.5-alpha):
782 - Work around a memory leak in OpenSSL 1.1 when encoding public
783 keys. Fixes bug 20553; bugfix on 0.0.2pre8.
785 o Minor features (geoip):
786 - Update geoip and geoip6 to the November 3 2016 Maxmind GeoLite2
790 Changes in version 0.2.8.9 - 2016-10-17
791 Tor 0.2.8.9 backports a fix for a security hole in previous versions
792 of Tor that would allow a remote attacker to crash a Tor client,
793 hidden service, relay, or authority. All Tor users should upgrade to
794 this version, or to 0.2.9.4-alpha. Patches will be released for older
797 o Major features (security fixes, also in 0.2.9.4-alpha):
798 - Prevent a class of security bugs caused by treating the contents
799 of a buffer chunk as if they were a NUL-terminated string. At
800 least one such bug seems to be present in all currently used
801 versions of Tor, and would allow an attacker to remotely crash
802 most Tor instances, especially those compiled with extra compiler
803 hardening. With this defense in place, such bugs can't crash Tor,
804 though we should still fix them as they occur. Closes ticket
805 20384 (TROVE-2016-10-001).
807 o Minor features (geoip):
808 - Update geoip and geoip6 to the October 4 2016 Maxmind GeoLite2
812 Changes in version 0.2.8.8 - 2016-09-23
813 Tor 0.2.8.8 fixes two crash bugs present in previous versions of the
814 0.2.8.x series. Relays running 0.2.8.x should upgrade, as should users
815 who select public relays as their bridges.
817 o Major bugfixes (crash):
818 - Fix a complicated crash bug that could affect Tor clients
819 configured to use bridges when replacing a networkstatus consensus
820 in which one of their bridges was mentioned. OpenBSD users saw
821 more crashes here, but all platforms were potentially affected.
822 Fixes bug 20103; bugfix on 0.2.8.2-alpha.
824 o Major bugfixes (relay, OOM handler):
825 - Fix a timing-dependent assertion failure that could occur when we
826 tried to flush from a circuit after having freed its cells because
827 of an out-of-memory condition. Fixes bug 20203; bugfix on
828 0.2.8.1-alpha. Thanks to "cypherpunks" for help diagnosing
831 o Minor feature (fallback directories):
832 - Remove broken fallbacks from the hard-coded fallback directory
833 list. Closes ticket 20190; patch by teor.
835 o Minor features (geoip):
836 - Update geoip and geoip6 to the September 6 2016 Maxmind GeoLite2
840 Changes in version 0.2.8.7 - 2016-08-24
841 Tor 0.2.8.7 fixes an important bug related to the ReachableAddresses
842 option in 0.2.8.6, and replaces a retiring bridge authority. Everyone
843 who sets the ReachableAddresses option, and all bridges, are strongly
844 encouraged to upgrade.
846 o Directory authority changes:
847 - The "Tonga" bridge authority has been retired; the new bridge
848 authority is "Bifroest". Closes tickets 19728 and 19690.
850 o Major bugfixes (client, security):
851 - Only use the ReachableAddresses option to restrict the first hop
852 in a path. In earlier versions of 0.2.8.x, it would apply to
853 every hop in the path, with a possible degradation in anonymity
854 for anyone using an uncommon ReachableAddress setting. Fixes bug
855 19973; bugfix on 0.2.8.2-alpha.
857 o Minor features (geoip):
858 - Update geoip and geoip6 to the August 2 2016 Maxmind GeoLite2
861 o Minor bugfixes (compilation):
862 - Remove an inappropriate "inline" in tortls.c that was causing
863 warnings on older versions of GCC. Fixes bug 19903; bugfix
866 o Minor bugfixes (fallback directories):
867 - Avoid logging a NULL string pointer when loading fallback
868 directory information. Fixes bug 19947; bugfix on 0.2.4.7-alpha
869 and 0.2.8.1-alpha. Report and patch by "rubiate".
872 Changes in version 0.2.8.6 - 2016-08-02
874 Tor 0.2.8.6 is the first stable version of the Tor 0.2.8 series.
876 The Tor 0.2.8 series improves client bootstrapping performance,
877 completes the authority-side implementation of improved identity
878 keys for relays, and includes numerous bugfixes and performance
879 improvements throughout the program. This release continues to
880 improve the coverage of Tor's test suite. For a full list of
881 changes since Tor 0.2.7, see the ReleaseNotes file.
883 Below is a list of the changes since Tor 0.2.7.
885 o New system requirements:
886 - Tor no longer attempts to support platforms where the "time_t"
887 type is unsigned. (To the best of our knowledge, only OpenVMS does
888 this, and Tor has never actually built on OpenVMS.) Closes
890 - Tor no longer supports versions of OpenSSL with a broken
891 implementation of counter mode. (This bug was present in OpenSSL
892 1.0.0, and was fixed in OpenSSL 1.0.0a.) Tor still detects, but no
893 longer runs with, these versions.
894 - Tor now uses Autoconf version 2.63 or later, and Automake 1.11 or
895 later (released in 2008 and 2009 respectively). If you are
896 building Tor from the git repository instead of from the source
897 distribution, and your tools are older than this, you will need to
898 upgrade. Closes ticket 17732.
900 o Directory authority changes:
901 - Update the V3 identity key for the dannenberg directory authority:
902 it was changed on 18 November 2015. Closes task 17906. Patch
904 - Urras is no longer a directory authority. Closes ticket 19271.
906 o Major features (directory system):
907 - Include a trial list of default fallback directories, based on an
908 opt-in survey of suitable relays. Doing this should make clients
909 bootstrap more quickly and reliably, and reduce the load on the
910 directory authorities. Closes ticket 15775. Patch by teor.
911 Candidates identified using an OnionOO script by weasel, teor,
912 gsathya, and karsten.
913 - Previously only relays that explicitly opened a directory port
914 (DirPort) accepted directory requests from clients. Now all
915 relays, with and without a DirPort, accept and serve tunneled
916 directory requests that they receive through their ORPort. You can
917 disable this behavior using the new DirCache option. Closes
919 - When bootstrapping multiple consensus downloads at a time, use the
920 first one that starts downloading, and close the rest. This
921 reduces failures when authorities or fallback directories are slow
922 or down. Together with the code for feature 15775, this feature
923 should reduces failures due to fallback churn. Implements ticket
924 4483. Patch by teor. Implements IPv4 portions of proposal 210 by
927 o Major features (security, Linux):
928 - When Tor starts as root on Linux and is told to switch user ID, it
929 can now retain the capability to bind to low ports. By default,
930 Tor will do this only when it's switching user ID and some low
931 ports have been configured. You can change this behavior with the
932 new option KeepBindCapabilities. Closes ticket 8195.
934 o Major bugfixes (client, bootstrapping):
935 - Check if bootstrap consensus downloads are still needed when the
936 linked connection attaches. This prevents tor making unnecessary
937 begindir-style connections, which are the only directory
938 connections tor clients make since the fix for 18483 was merged.
939 - Fix some edge cases where consensus download connections may not
940 have been closed, even though they were not needed. Related to fix
942 - Make relays retry consensus downloads the correct number of times,
943 rather than the more aggressive client retry count. Fixes part of
946 o Major bugfixes (dns proxy mode, crash):
947 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
948 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
950 o Major bugfixes (ed25519, voting):
951 - Actually enable support for authorities to match routers by their
952 Ed25519 identities. Previously, the code had been written, but
953 some debugging code that had accidentally been left in the
954 codebase made it stay turned off. Fixes bug 17702; bugfix
956 - When collating votes by Ed25519 identities, authorities now
957 include a "NoEdConsensus" flag if the ed25519 value (or lack
958 thereof) for a server does not reflect the majority consensus.
959 Related to bug 17668; bugfix on 0.2.7.2-alpha.
960 - When generating a vote with keypinning disabled, never include two
961 entries for the same ed25519 identity. This bug was causing
962 authorities to generate votes that they could not parse when a
963 router violated key pinning by changing its RSA identity but
964 keeping its Ed25519 identity. Fixes bug 17668; fixes part of bug
965 18318. Bugfix on 0.2.7.2-alpha.
967 o Major bugfixes (key management):
968 - If OpenSSL fails to generate an RSA key, do not retain a dangling
969 pointer to the previous (uninitialized) key value. The impact here
970 should be limited to a difficult-to-trigger crash, if OpenSSL is
971 running an engine that makes key generation failures possible, or
972 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
973 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
976 o Major bugfixes (security, client, DNS proxy):
977 - Stop a crash that could occur when a client running with DNSPort
978 received a query with multiple address types, and the first
979 address type was not supported. Found and fixed by Scott Dial.
980 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
982 o Major bugfixes (security, compilation):
983 - Correctly detect compiler flags on systems where _FORTIFY_SOURCE
984 is predefined. Previously, our use of -D_FORTIFY_SOURCE would
985 cause a compiler warning, thereby making other checks fail, and
986 needlessly disabling compiler-hardening support. Fixes one case of
987 bug 18841; bugfix on 0.2.3.17-beta. Patch from "trudokal".
988 - Repair hardened builds under the clang compiler. Previously, our
989 use of _FORTIFY_SOURCE would conflict with clang's address
990 sanitizer. Fixes bug 14821; bugfix on 0.2.5.4-alpha.
992 o Major bugfixes (security, pointers):
993 - Avoid a difficult-to-trigger heap corruption attack when extending
994 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
995 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
996 Reported by Guido Vranken.
998 o Major bugfixes (testing):
999 - Fix a bug that would block 'make test-network-all' on systems where
1000 IPv6 packets were lost. Fixes bug 19008; bugfix on 0.2.7.3-rc.
1002 o Major bugfixes (user interface):
1003 - Correctly give a warning in the cases where a relay is specified
1004 by nickname, and one such relay is found, but it is not officially
1005 Named. Fixes bug 19203; bugfix on 0.2.3.1-alpha.
1007 o Minor features (accounting):
1008 - Added two modes to the AccountingRule option: One for limiting
1009 only the number of bytes sent ("AccountingRule out"), and one for
1010 limiting only the number of bytes received ("AccountingRule in").
1011 Closes ticket 15989; patch from "unixninja92".
1013 o Minor features (bug-resistance):
1014 - Make Tor survive errors involving connections without a
1015 corresponding event object. Previously we'd fail with an
1016 assertion; now we produce a log message. Related to bug 16248.
1017 - Use tor_snprintf() and tor_vsnprintf() even in external and low-
1018 level code, to harden against accidental failures to NUL-
1019 terminate. Part of ticket 17852. Patch from jsturgix. Found
1022 o Minor features (build):
1023 - Detect systems with FreeBSD-derived kernels (such as GNU/kFreeBSD)
1024 as having possible IPFW support. Closes ticket 18448. Patch from
1026 - Since our build process now uses "make distcheck", we no longer
1027 force "make dist" to depend on "make check". Closes ticket 17893;
1028 patch from "cypherpunks".
1029 - Tor now builds once again with the recent OpenSSL 1.1 development
1030 branch (tested against 1.1.0-pre5 and 1.1.0-pre6-dev). We have been
1031 tracking OpenSSL 1.1 development as it has progressed, and fixing
1032 numerous compatibility issues as they arose. See tickets
1033 17549, 17921, 17984, 19499, and 18286.
1034 - When building manual pages, set the timezone to "UTC", so that the
1035 output is reproducible. Fixes bug 19558; bugfix on 0.2.2.9-alpha.
1036 Patch from intrigeri.
1038 o Minor features (clients):
1039 - Make clients, onion services, and bridge relays always use an
1040 encrypted begindir connection for directory requests. Resolves
1041 ticket 18483. Patch by teor.
1043 o Minor features (controller):
1044 - Add 'GETINFO exit-policy/reject-private/[default,relay]', so
1045 controllers can examine the the reject rules added by
1046 ExitPolicyRejectPrivate. This makes it easier for stem to display
1048 - Adds the FallbackDir entries to 'GETINFO config/defaults'. Closes
1049 tickets 16774 and 17817. Patch by George Tankersley.
1050 - New 'GETINFO hs/service/desc/id/' command to retrieve a hidden
1051 service descriptor from a service's local hidden service
1052 descriptor cache. Closes ticket 14846.
1054 o Minor features (crypto):
1055 - Add SHA3 and SHAKE support to crypto.c. Closes ticket 17783.
1056 - Add SHA512 support to crypto.c. Closes ticket 17663; patch from
1058 - Improve performance when hashing non-multiple of 8 sized buffers,
1059 based on Andrew Moon's public domain SipHash-2-4 implementation.
1060 Fixes bug 17544; bugfix on 0.2.5.3-alpha.
1061 - Validate the hard-coded Diffie-Hellman parameters and ensure that
1062 p is a safe prime, and g is a suitable generator. Closes
1064 - When allocating a digest state object, allocate no more space than
1065 we actually need. Previously, we would allocate as much space as
1066 the state for the largest algorithm would need. This change saves
1067 up to 672 bytes per circuit. Closes ticket 17796.
1069 o Minor features (directory downloads):
1070 - Add UseDefaultFallbackDirs, which enables any hard-coded fallback
1071 directory mirrors. The default is 1; set it to 0 to disable
1072 fallbacks. Implements ticket 17576. Patch by teor.
1073 - Wait for busy authorities and fallback directories to become non-
1074 busy when bootstrapping. (A similar change was made in 6c443e987d
1075 for directory caches chosen from the consensus.) Closes ticket
1076 17864; patch by teor.
1078 o Minor features (geoip):
1079 - Update geoip and geoip6 to the July 6 2016 Maxmind GeoLite2
1082 o Minor features (hidden service directory):
1083 - Streamline relay-side hsdir handling: when relays consider whether
1084 to accept an uploaded hidden service descriptor, they no longer
1085 check whether they are one of the relays in the network that is
1086 "supposed" to handle that descriptor. Implements ticket 18332.
1088 o Minor features (IPv6):
1089 - Add ClientPreferIPv6DirPort, which is set to 0 by default. If set
1090 to 1, tor prefers IPv6 directory addresses.
1091 - Add ClientUseIPv4, which is set to 1 by default. If set to 0, tor
1092 avoids using IPv4 for client OR and directory connections.
1093 - Add address policy assume_action support for IPv6 addresses.
1094 - Add an argument 'ipv6=address:orport' to the DirAuthority and
1095 FallbackDir torrc options, to specify an IPv6 address for an
1096 authority or fallback directory. Add hard-coded ipv6 addresses for
1097 directory authorities that have them. Closes ticket 17327; patch
1098 from Nick Mathewson and teor.
1099 - Allow users to configure directory authorities and fallback
1100 directory servers with IPv6 addresses and ORPorts. Resolves
1102 - Limit IPv6 mask bits to 128.
1103 - Make tor_ersatz_socketpair work on IPv6-only systems. Fixes bug
1104 17638; bugfix on 0.0.2pre8. Patch by teor.
1105 - Try harder to obey the IP version restrictions "ClientUseIPv4 0",
1106 "ClientUseIPv6 0", "ClientPreferIPv6ORPort", and
1107 "ClientPreferIPv6DirPort". Closes ticket 17840; patch by teor.
1108 - Warn when comparing against an AF_UNSPEC address in a policy, it's
1109 almost always a bug. Closes ticket 17863; patch by teor.
1110 - routerset_parse now accepts IPv6 literal addresses. Fixes bug
1111 17060; bugfix on 0.2.1.3-alpha. Patch by teor.
1113 o Minor features (Linux seccomp2 sandbox):
1114 - Reject attempts to change our Address with "Sandbox 1" enabled.
1115 Changing Address with Sandbox turned on would never actually work,
1116 but previously it would fail in strange and confusing ways. Found
1119 o Minor features (logging):
1120 - When logging to syslog, allow a tag to be added to the syslog
1121 identity (the string prepended to every log message). The tag can
1122 be configured with SyslogIdentityTag and defaults to none. Setting
1123 it to "foo" will cause logs to be tagged as "Tor-foo". Closes
1126 o Minor features (portability):
1127 - Use timingsafe_memcmp() where available. Closes ticket 17944;
1128 patch from <logan@hackers.mu>.
1130 o Minor features (relay, address discovery):
1131 - Add a family argument to get_interface_addresses_raw() and
1132 subfunctions to make network interface address interogation more
1133 efficient. Now Tor can specifically ask for IPv4, IPv6 or both
1134 types of interfaces from the operating system. Resolves
1136 - When get_interface_address6_list(.,AF_UNSPEC,.) is called and
1137 fails to enumerate interface addresses using the platform-specific
1138 API, have it rely on the UDP socket fallback technique to try and
1139 find out what IP addresses (both IPv4 and IPv6) our machine has.
1140 Resolves ticket 17951.
1142 o Minor features (replay cache):
1143 - The replay cache now uses SHA256 instead of SHA1. Implements
1144 feature 8961. Patch by teor, issue reported by rransom.
1146 o Minor features (robustness):
1147 - Exit immediately with an error message if the code attempts to use
1148 Libevent without having initialized it. This should resolve some
1149 frequently-made mistakes in our unit tests. Closes ticket 18241.
1151 o Minor features (security, clock):
1152 - Warn when the system clock appears to move back in time (when the
1153 state file was last written in the future). Tor doesn't know that
1154 consensuses have expired if the clock is in the past. Patch by
1155 teor. Implements ticket 17188.
1157 o Minor features (security, exit policies):
1158 - ExitPolicyRejectPrivate now rejects more private addresses by
1159 default. Specifically, it now rejects the relay's outbound bind
1160 addresses (if configured), and the relay's configured port
1161 addresses (such as ORPort and DirPort). Fixes bug 17027; bugfix on
1162 0.2.0.11-alpha. Patch by teor.
1164 o Minor features (security, memory erasure):
1165 - Make memwipe() do nothing when passed a NULL pointer or buffer of
1166 zero size. Check size argument to memwipe() for underflow. Fixes
1167 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
1169 - Set the unused entries in a smartlist to NULL. This helped catch
1170 a (harmless) bug, and shouldn't affect performance too much.
1171 Implements ticket 17026.
1172 - Use SecureMemoryWipe() function to securely clean memory on
1173 Windows. Previously we'd use OpenSSL's OPENSSL_cleanse() function.
1174 Implements feature 17986.
1175 - Use explicit_bzero or memset_s when present. Previously, we'd use
1176 OpenSSL's OPENSSL_cleanse() function. Closes ticket 7419; patches
1177 from <logan@hackers.mu> and <selven@hackers.mu>.
1179 o Minor features (security, RNG):
1180 - Adjust Tor's use of OpenSSL's RNG APIs so that they absolutely,
1181 positively are not allowed to fail. Previously we depended on
1182 internal details of OpenSSL's behavior. Closes ticket 17686.
1183 - Never use the system entropy output directly for anything besides
1184 seeding the PRNG. When we want to generate important keys, instead
1185 of using system entropy directly, we now hash it with the PRNG
1186 stream. This may help resist certain attacks based on broken OS
1187 entropy implementations. Closes part of ticket 17694.
1188 - Use modern system calls (like getentropy() or getrandom()) to
1189 generate strong entropy on platforms that have them. Closes
1192 o Minor features (security, win32):
1193 - Set SO_EXCLUSIVEADDRUSE on Win32 to avoid a local port-stealing
1194 attack. Fixes bug 18123; bugfix on all tor versions. Patch
1197 o Minor features (unix domain sockets):
1198 - Add a new per-socket option, RelaxDirModeCheck, to allow creating
1199 Unix domain sockets without checking the permissions on the parent
1200 directory. (Tor checks permissions by default because some
1201 operating systems only check permissions on the parent directory.
1202 However, some operating systems do look at permissions on the
1203 socket, and tor's default check is unneeded.) Closes ticket 18458.
1206 o Minor features (unix file permissions):
1207 - Defer creation of Unix sockets until after setuid. This avoids
1208 needing CAP_CHOWN and CAP_FOWNER when using systemd's
1209 CapabilityBoundingSet, or chown and fowner when using SELinux.
1210 Implements part of ticket 17562. Patch from Jamie Nguyen.
1211 - If any directory created by Tor is marked as group readable, the
1212 filesystem group is allowed to be either the default GID or the
1213 root user. Allowing root to read the DataDirectory prevents the
1214 need for CAP_READ_SEARCH when using systemd's
1215 CapabilityBoundingSet, or dac_read_search when using SELinux.
1216 Implements part of ticket 17562. Patch from Jamie Nguyen.
1217 - Introduce a new DataDirectoryGroupReadable option. If it is set to
1218 1, the DataDirectory will be made readable by the default GID.
1219 Implements part of ticket 17562. Patch from Jamie Nguyen.
1221 o Minor bugfixes (accounting):
1222 - The max bandwidth when using 'AccountRule sum' is now correctly
1223 logged. Fixes bug 18024; bugfix on 0.2.6.1-alpha. Patch
1226 o Minor bugfixes (assert, portability):
1227 - Fix an assertion failure in memarea.c on systems where "long" is
1228 shorter than the size of a pointer. Fixes bug 18716; bugfix
1231 o Minor bugfixes (bootstrap):
1232 - Consistently use the consensus download schedule for authority
1233 certificates. Fixes bug 18816; bugfix on 0.2.4.13-alpha.
1235 o Minor bugfixes (build):
1236 - Avoid spurious failures from configure files related to calling
1237 exit(0) in TOR_SEARCH_LIBRARY. Fixes bug 18626; bugfix on
1238 0.2.0.1-alpha. Patch from "cypherpunks".
1239 - Do not link the unit tests against both the testing and non-
1240 testing versions of the static libraries. Fixes bug 18490; bugfix
1242 - Resolve warnings when building on systems that are concerned with
1243 signed char. Fixes bug 18728; bugfix on 0.2.7.2-alpha
1245 - Silence spurious clang-scan warnings in the ed25519_donna code by
1246 explicitly initializing some objects. Fixes bug 18384; bugfix on
1247 0.2.7.2-alpha. Patch by teor.
1248 - When libscrypt.h is found, but no libscrypt library can be linked,
1249 treat libscrypt as absent. Fixes bug 19161; bugfix
1251 - Cause the unit tests to compile correctly on mingw64 versions that
1252 lack sscanf. Fixes bug 19213; bugfix on 0.2.7.1-alpha.
1253 - Don't try to use the pthread_condattr_setclock() function unless
1254 it actually exists. Fixes compilation on NetBSD-6.x. Fixes bug
1255 17819; bugfix on 0.2.6.3-alpha.
1256 - Fix backtrace compilation on FreeBSD. Fixes bug 17827; bugfix
1258 - Fix search for libevent libraries on OpenBSD (and other systems
1259 that install libevent 1 and libevent 2 in parallel). Fixes bug
1260 16651; bugfix on 0.1.0.7-rc. Patch from "rubiate".
1261 - Isolate environment variables meant for tests from the rest of the
1262 build system. Fixes bug 17818; bugfix on 0.2.7.3-rc.
1263 - Mark all object files that include micro-revision.i as depending
1264 on it, so as to make parallel builds more reliable. Fixes bug
1265 17826; bugfix on 0.2.5.1-alpha.
1266 - Remove config.log only from make distclean, not from make clean.
1267 Fixes bug 17924; bugfix on 0.2.4.1-alpha.
1268 - Replace usage of 'INLINE' with 'inline'. Fixes bug 17804; bugfix
1270 - Remove an #endif from configure.ac so that we correctly detect the
1271 presence of in6_addr.s6_addr32. Fixes bug 17923; bugfix
1274 o Minor bugfixes (client, bootstrap):
1275 - Count receipt of new microdescriptors as progress towards
1276 bootstrapping. Previously, with EntryNodes set, Tor might not
1277 successfully repopulate the guard set on bootstrapping. Fixes bug
1278 16825; bugfix on 0.2.3.1-alpha.
1280 o Minor bugfixes (code correctness):
1281 - Fix a bad memory handling bug that would occur if we had queued a
1282 cell on a channel's incoming queue. Fortunately, we can't actually
1283 queue a cell like that as our code is constructed today, but it's
1284 best to avoid this kind of error, even if there isn't any code
1285 that triggers it today. Fixes bug 18570; bugfix on 0.2.4.4-alpha.
1286 - Assert that allocated memory held by the reputation code is freed
1287 according to its internal counters. Fixes bug 17753; bugfix
1289 - Assert when the TLS contexts fail to initialize. Fixes bug 17683;
1291 - Update to the latest version of Trunnel, which tries harder to
1292 avoid generating code that can invoke memcpy(p,NULL,0). Bug found
1293 by clang address sanitizer. Fixes bug 18373; bugfix
1295 - When closing an entry connection, generate a warning if we should
1296 have sent an end cell for it but we haven't. Fixes bug 17876;
1297 bugfix on 0.2.3.2-alpha.
1299 o Minor bugfixes (configuration):
1300 - Fix a tiny memory leak when parsing a port configuration ending in
1301 ":auto". Fixes bug 18374; bugfix on 0.2.3.3-alpha.
1303 o Minor bugfixes (containers):
1304 - If we somehow attempt to construct a heap with more than
1305 1073741822 elements, avoid an integer overflow when maintaining
1306 the heap property. Fixes bug 18296; bugfix on 0.1.2.1-alpha.
1308 o Minor bugfixes (controller, microdescriptors):
1309 - Make GETINFO dir/status-vote/current/consensus conform to the
1310 control specification by returning "551 Could not open cached
1311 consensus..." when not caching consensuses. Fixes bug 18920;
1312 bugfix on 0.2.2.6-alpha.
1314 o Minor bugfixes (crypto):
1315 - Check the return value of HMAC() and assert on failure. Fixes bug
1316 17658; bugfix on 0.2.3.6-alpha. Patch by teor.
1318 o Minor bugfixes (directories):
1319 - When fetching extrainfo documents, compare their SHA256 digests
1320 and Ed25519 signing key certificates with the routerinfo that led
1321 us to fetch them, rather than with the most recent routerinfo.
1322 Otherwise we generate many spurious warnings about mismatches.
1323 Fixes bug 17150; bugfix on 0.2.7.2-alpha.
1324 - When generating a URL for a directory server on an IPv6 address,
1325 wrap the IPv6 address in square brackets. Fixes bug 18051; bugfix
1326 on 0.2.3.9-alpha. Patch from Malek.
1328 o Minor bugfixes (downloading):
1329 - Predict more correctly whether we'll be downloading over HTTP when
1330 we determine the maximum length of a URL. This should avoid a
1331 "BUG" warning about the Squid HTTP proxy and its URL limits. Fixes
1334 o Minor bugfixes (exit policies, security):
1335 - Refresh an exit relay's exit policy when interface addresses
1336 change. Previously, tor only refreshed the exit policy when the
1337 configured external address changed. Fixes bug 18208; bugfix on
1338 0.2.7.3-rc. Patch by teor.
1340 o Minor bugfixes (fallback directories):
1341 - Mark fallbacks as "too busy" when they return a 503 response,
1342 rather than just marking authorities. Fixes bug 17572; bugfix on
1343 0.2.4.7-alpha. Patch by teor.
1344 - When requesting extrainfo descriptors from a trusted directory
1345 server, check whether it is an authority or a fallback directory
1346 which supports extrainfo descriptors. Fixes bug 18489; bugfix on
1347 0.2.4.7-alpha. Reported by atagar, patch by teor.
1349 o Minor bugfixes (hidden service, client):
1350 - Handle the case where the user makes several fast consecutive
1351 requests to the same .onion address. Previously, the first six
1352 requests would each trigger a descriptor fetch, each picking a
1353 directory (there are 6 overall) and the seventh one would fail
1354 because no directories were left, thereby triggering a close on
1355 all current directory connections asking for the hidden service.
1356 The solution here is to not close the connections if we have
1357 pending directory fetches. Fixes bug 15937; bugfix
1360 o Minor bugfixes (hidden service, control port):
1361 - Add the onion address to the HS_DESC event for the UPLOADED action
1362 both on success or failure. It was previously hardcoded with
1363 UNKNOWN. Fixes bug 16023; bugfix on 0.2.7.2-alpha.
1365 o Minor bugfixes (hidden service, directory):
1366 - Bridges now refuse "rendezvous2" (hidden service descriptor)
1367 publish attempts. Suggested by ticket 18332.
1369 o Minor bugfixes (IPv6):
1370 - Update the limits in max_dl_per_request for IPv6 address length.
1371 Fixes bug 17573; bugfix on 0.2.1.5-alpha.
1373 o Minor bugfixes (Linux seccomp2 sandbox):
1374 - Allow more syscalls when running with "Sandbox 1" enabled:
1375 sysinfo, getsockopt(SO_SNDBUF), and setsockopt(SO_SNDBUFFORCE). On
1376 some systems, these are required for Tor to start. Fixes bug
1377 18397; bugfix on 0.2.5.1-alpha. Patch from Daniel Pinto.
1378 - Allow IPPROTO_UDP datagram sockets when running with "Sandbox 1",
1379 so that get_interface_address6_via_udp_socket_hack() can work.
1380 Fixes bug 19660; bugfix on 0.2.5.1-alpha.
1381 - Allow the setrlimit syscall, and the prlimit and prlimit64
1382 syscalls, which some libc implementations use under the hood.
1383 Fixes bug 15221; bugfix on 0.2.5.1-alpha.
1384 - Avoid a 10-second delay when starting as a client with "Sandbox 1"
1385 enabled and no DNS resolvers configured. This should help TAILS
1386 start up faster. Fixes bug 18548; bugfix on 0.2.5.1-alpha.
1387 - Fix a crash when using offline master ed25519 keys with the Linux
1388 seccomp2 sandbox enabled. Fixes bug 17675; bugfix on 0.2.7.3-rc.
1389 - Allow statistics to be written to disk when "Sandbox 1" is
1390 enabled. Fixes bugs 19556 and 19957; bugfix on 0.2.5.1-alpha and
1391 0.2.6.1-alpha respectively.
1393 o Minor bugfixes (logging):
1394 - In log messages that include a function name, use __FUNCTION__
1395 instead of __PRETTY_FUNCTION__. In GCC, these are synonymous, but
1396 with clang __PRETTY_FUNCTION__ has extra information we don't
1397 need. Fixes bug 16563; bugfix on 0.0.2pre8. Fix by Tom van
1399 - Remove needless quotes from a log message about unparseable
1400 addresses. Fixes bug 17843; bugfix on 0.2.3.3-alpha.
1401 - Scrub service name in "unrecognized service ID" log messages.
1402 Fixes bug 18600; bugfix on 0.2.4.11-alpha.
1403 - When logging information about an unparsable networkstatus vote or
1404 consensus, do not say "vote" when we mean consensus. Fixes bug
1405 18368; bugfix on 0.2.0.8-alpha.
1406 - When we can't generate a signing key because OfflineMasterKey is
1407 set, do not imply that we should have been able to load it. Fixes
1408 bug 18133; bugfix on 0.2.7.2-alpha.
1409 - When logging a malformed hostname received through socks4, scrub
1410 it if SafeLogging says we should. Fixes bug 17419; bugfix
1413 o Minor bugfixes (memory safety):
1414 - Avoid freeing an uninitialized pointer when opening a socket fails
1415 in get_interface_addresses_ioctl(). Fixes bug 18454; bugfix on
1416 0.2.3.11-alpha. Reported by toralf and "cypherpunks", patch
1418 - Fix a memory leak in "tor --list-fingerprint". Fixes part of bug
1419 18672; bugfix on 0.2.5.1-alpha.
1420 - Fix a memory leak in tor-gencert. Fixes part of bug 18672; bugfix
1423 o Minor bugfixes (pluggable transports):
1424 - Avoid reporting a spurious error when we decide that we don't need
1425 to terminate a pluggable transport because it has already exited.
1426 Fixes bug 18686; bugfix on 0.2.5.5-alpha.
1428 o Minor bugfixes (pointer arithmetic):
1429 - Fix a bug in memarea_alloc() that could have resulted in remote
1430 heap write access, if Tor had ever passed an unchecked size to
1431 memarea_alloc(). Fortunately, all the sizes we pass to
1432 memarea_alloc() are pre-checked to be less than 128 kilobytes.
1433 Fixes bug 19150; bugfix on 0.2.1.1-alpha. Bug found by
1436 o Minor bugfixes (private directory):
1437 - Prevent a race condition when creating private directories. Fixes
1438 part of bug 17852; bugfix on 0.0.2pre13. Part of ticket 17852.
1439 Patch from jsturgix. Found with Flawfinder.
1441 o Minor bugfixes (relays):
1442 - Check that both the ORPort and DirPort (if present) are reachable
1443 before publishing a relay descriptor. Otherwise, relays publish a
1444 descriptor with DirPort 0 when the DirPort reachability test takes
1445 longer than the ORPort reachability test. Fixes bug 18050; bugfix
1446 on 0.1.0.1-rc. Reported by "starlight", patch by teor.
1447 - Resolve some edge cases where we might launch an ORPort
1448 reachability check even when DisableNetwork is set. Noticed while
1449 fixing bug 18616; bugfix on 0.2.3.9-alpha.
1451 o Minor bugfixes (relays, hidden services):
1452 - Refuse connection requests to private OR addresses unless
1453 ExtendAllowPrivateAddresses is set. Previously, tor would connect,
1454 then refuse to send any cells to a private address. Fixes bugs
1455 17674 and 8976; bugfix on 0.2.3.21-rc. Patch by teor.
1457 o Minor bugfixes (security, hidden services):
1458 - Prevent hidden services connecting to client-supplied rendezvous
1459 addresses that are reserved as internal or multicast. Fixes bug
1460 8976; bugfix on 0.2.3.21-rc. Patch by dgoulet and teor.
1462 o Minor bugfixes (statistics):
1463 - Consistently check for overflow in round_*_to_next_multiple_of
1464 functions, and add unit tests with additional and maximal values.
1465 Fixes part of bug 13192; bugfix on 0.2.2.1-alpha.
1466 - Handle edge cases in the laplace functions: avoid division by
1467 zero, avoid taking the log of zero, and silence clang type
1468 conversion warnings using round and trunc. Add unit tests for edge
1469 cases with maximal values. Fixes part of bug 13192; bugfix
1471 - We now include consensus downloads via IPv6 in our directory-
1472 request statistics. Fixes bug 18460; bugfix on 0.2.3.14-alpha.
1474 o Minor bugfixes (test networks, IPv6):
1475 - Allow internal IPv6 addresses in descriptors in test networks.
1476 Fixes bug 17153; bugfix on 0.2.3.16-alpha. Patch by teor, reported
1479 o Minor bugfixes (testing):
1480 - Check the full results of SHA256 and SHA512 digests in the unit
1481 tests. Bugfix on 0.2.2.4-alpha. Patch by teor.
1482 - Fix a memory leak in the ntor test. Fixes bug 17778; bugfix
1484 - Fix a small memory leak that would occur when the
1485 TestingEnableCellStatsEvent option was turned on. Fixes bug 18673;
1486 bugfix on 0.2.5.2-alpha.
1487 - Make unit tests pass on IPv6-only systems, and systems without
1488 localhost addresses (like some FreeBSD jails). Fixes bug 17632;
1489 bugfix on 0.2.7.3-rc. Patch by teor.
1490 - The test for log_heartbeat was incorrectly failing in timezones
1491 with non-integer offsets. Instead of comparing the end of the time
1492 string against a constant, compare it to the output of
1493 format_local_iso_time when given the correct input. Fixes bug
1494 18039; bugfix on 0.2.5.4-alpha.
1495 - We no longer disable assertions in the unit tests when coverage is
1496 enabled. Instead, we require you to say --disable-asserts-in-tests
1497 to the configure script if you need assertions disabled in the
1498 unit tests (for example, if you want to perform branch coverage).
1499 Fixes bug 18242; bugfix on 0.2.7.1-alpha.
1501 o Minor bugfixes (time handling):
1502 - When correcting a corrupt 'struct tm' value, fill in the tm_wday
1503 field. Otherwise, our unit tests crash on Windows. Fixes bug
1504 18977; bugfix on 0.2.2.25-alpha.
1505 - Avoid overflow in tor_timegm when parsing dates in and after 2038
1506 on platforms with 32-bit time_t. Fixes bug 18479; bugfix on
1507 0.0.2pre14. Patch by teor.
1509 o Minor bugfixes (tor-gencert):
1510 - Correctly handle the case where an authority operator enters a
1511 passphrase but sends an EOF before sending a newline. Fixes bug
1512 17443; bugfix on 0.2.0.20-rc. Found by junglefowl.
1514 o Code simplification and refactoring:
1515 - Clean up a little duplicated code in
1516 crypto_expand_key_material_TAP(). Closes ticket 17587; patch
1518 - Decouple the list of streams waiting to be attached to circuits
1519 from the overall connection list. This change makes it possible to
1520 attach streams quickly while simplifying Tor's callgraph and
1521 avoiding O(N) scans of the entire connection list. Closes
1523 - Extract the more complicated parts of circuit_mark_for_close()
1524 into a new function that we run periodically before circuits are
1525 freed. This change removes more than half of the functions
1526 currently in the "blob". Closes ticket 17218.
1527 - Move logging of redundant policy entries in
1528 policies_parse_exit_policy_internal into its own function. Closes
1529 ticket 17608; patch from "juce".
1530 - Quote all the string interpolations in configure.ac -- even those
1531 which we are pretty sure can't contain spaces. Closes ticket
1532 17744. Patch from zerosion.
1533 - Remove code for configuring OpenSSL dynamic locks; OpenSSL doesn't
1534 use them. Closes ticket 17926.
1535 - Remove specialized code for non-inplace AES_CTR. 99% of our AES is
1536 inplace, so there's no need to have a separate implementation for
1537 the non-inplace code. Closes ticket 18258. Patch from Malek.
1538 - Simplify return types for some crypto functions that can't
1539 actually fail. Patch from Hassan Alsibyani. Closes ticket 18259.
1540 - When a direct directory request fails immediately on launch,
1541 instead of relaunching that request from inside the code that
1542 launches it, instead mark the connection for teardown. This change
1543 simplifies Tor's callback and prevents the directory-request
1544 launching code from invoking itself recursively. Closes
1548 - Add a description of the correct use of the '--keygen' command-
1549 line option. Closes ticket 17583; based on text by 's7r'.
1550 - Change build messages to refer to "Fedora" instead of "Fedora
1551 Core", and "dnf" instead of "yum". Closes tickets 18459 and 18426.
1552 Patches from "icanhasaccount" and "cypherpunks".
1553 - Document the contents of the 'datadir/keys' subdirectory in the
1554 manual page. Closes ticket 17621.
1555 - Document the minimum HeartbeatPeriod value. Closes ticket 15638.
1556 - Explain actual minima for BandwidthRate. Closes ticket 16382.
1557 - Fix a minor formatting typo in the manpage. Closes ticket 17791.
1558 - Mention torspec URL in the manpage and point the reader to it
1559 whenever we mention a document that belongs in torspce. Fixes
1561 - Stop recommending use of nicknames to identify relays in our
1562 MapAddress documentation. Closes ticket 18312.
1565 - Remove client-side support for connecting to Tor relays running
1566 versions of Tor before 0.2.3.6-alpha. These relays didn't support
1567 the v3 TLS handshake protocol, and are no longer allowed on the
1568 Tor network. Implements the client side of ticket 11150. Based on
1569 patches by Tom van der Woerdt.
1570 - We no longer maintain an internal freelist in memarea.c.
1571 Allocators should be good enough to make this code unnecessary,
1572 and it's doubtful that it ever had any performance benefit.
1575 - Add unit tests to check for common RNG failure modes, such as
1576 returning all zeroes, identical values, or incrementing values
1577 (OpenSSL's rand_predictable feature). Patch by teor.
1578 - Always test both ed25519 backends, so that we can be sure that our
1579 batch-open replacement code works. Part of ticket 16794.
1580 - Cover dns_resolve_impl() in dns.c with unit tests. Implements a
1581 portion of ticket 16831.
1582 - Fix several warnings from clang's address sanitizer produced in
1584 - Log more information when the backtrace tests fail. Closes ticket
1585 17892. Patch from "cypherpunks."
1586 - More unit tests for compat_libevent.c, procmon.c, tortls.c,
1587 util_format.c, directory.c, and options_validate.c. Closes tickets
1588 17075, 17082, 17084, 17003, and 17076 respectively. Patches from
1590 - Treat backtrace test failures as expected on FreeBSD until we
1591 solve bug 17808. Closes ticket 18204.
1592 - Unit tests for directory_handle_command_get. Closes ticket 17004.
1593 Patch from Reinaldo de Souza Jr.
1596 Changes in version 0.2.7.6 - 2015-12-10
1597 Tor version 0.2.7.6 fixes a major bug in entry guard selection, as
1598 well as a minor bug in hidden service reliability.
1600 o Major bugfixes (guard selection):
1601 - Actually look at the Guard flag when selecting a new directory
1602 guard. When we implemented the directory guard design, we
1603 accidentally started treating all relays as if they have the Guard
1604 flag during guard selection, leading to weaker anonymity and worse
1605 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
1608 o Minor features (geoip):
1609 - Update geoip and geoip6 to the December 1 2015 Maxmind GeoLite2
1612 o Minor bugfixes (compilation):
1613 - When checking for net/pfvar.h, include netinet/in.h if possible.
1614 This fixes transparent proxy detection on OpenBSD. Fixes bug
1615 17551; bugfix on 0.1.2.1-alpha. Patch from "rubiate".
1616 - Fix a compilation warning with Clang 3.6: Do not check the
1617 presence of an address which can never be NULL. Fixes bug 17781.
1619 o Minor bugfixes (correctness):
1620 - When displaying an IPv6 exit policy, include the mask bits
1621 correctly even when the number is greater than 31. Fixes bug
1622 16056; bugfix on 0.2.4.7-alpha. Patch from "gturner".
1623 - The wrong list was used when looking up expired intro points in a
1624 rend service object, causing what we think could be reachability
1625 issues for hidden services, and triggering a BUG log. Fixes bug
1626 16702; bugfix on 0.2.7.2-alpha.
1627 - Fix undefined behavior in the tor_cert_checksig function. Fixes
1628 bug 17722; bugfix on 0.2.7.2-alpha.
1631 Changes in version 0.2.7.5 - 2015-11-20
1632 The Tor 0.2.7 release series is dedicated to the memory of Tor user
1633 and privacy advocate Caspar Bowden (1961-2015). Caspar worked
1634 tirelessly to advocate human rights regardless of national borders,
1635 and oppose the encroachments of mass surveillance. He opposed national
1636 exceptionalism, he brought clarity to legal and policy debates, he
1637 understood and predicted the impact of mass surveillance on the world,
1638 and he laid the groundwork for resisting it. While serving on the Tor
1639 Project's board of directors, he brought us his uncompromising focus
1640 on technical excellence in the service of humankind. Caspar was an
1641 inimitable force for good and a wonderful friend. He was kind,
1642 humorous, generous, gallant, and believed we should protect one
1643 another without exception. We honor him here for his ideals, his
1644 efforts, and his accomplishments. Please honor his memory with works
1645 that would make him proud.
1647 Tor 0.2.7.5 is the first stable release in the Tor 0.2.7 series.
1649 The 0.2.7 series adds a more secure identity key type for relays,
1650 improves cryptography performance, resolves several longstanding
1651 hidden-service performance issues, improves controller support for
1652 hidden services, and includes small bugfixes and performance
1653 improvements throughout the program. This release series also includes
1654 more tests than before, and significant simplifications to which parts
1655 of Tor invoke which others. For a full list of changes, see below.
1657 o New system requirements:
1658 - Tor no longer includes workarounds to support Libevent versions
1659 before 1.3e. Libevent 2.0 or later is recommended. Closes
1661 - Tor no longer supports copies of OpenSSL that are missing support
1662 for Elliptic Curve Cryptography. (We began using ECC when
1663 available in 0.2.4.8-alpha, for more safe and efficient key
1664 negotiation.) In particular, support for at least one of P256 or
1665 P224 is now required, with manual configuration needed if only
1666 P224 is available. Resolves ticket 16140.
1667 - Tor no longer supports versions of OpenSSL before 1.0. (If you are
1668 on an operating system that has not upgraded to OpenSSL 1.0 or
1669 later, and you compile Tor from source, you will need to install a
1670 more recent OpenSSL to link Tor against.) These versions of
1671 OpenSSL are still supported by the OpenSSL, but the numerous
1672 cryptographic improvements in later OpenSSL releases makes them a
1673 clear choice. Resolves ticket 16034.
1675 o Major features (controller):
1676 - Add the ADD_ONION and DEL_ONION commands that allow the creation
1677 and management of hidden services via the controller. Closes
1679 - New "GETINFO onions/current" and "GETINFO onions/detached"
1680 commands to get information about hidden services created via the
1681 controller. Part of ticket 6411.
1682 - New HSFETCH command to launch a request for a hidden service
1683 descriptor. Closes ticket 14847.
1684 - New HSPOST command to upload a hidden service descriptor. Closes
1685 ticket 3523. Patch by "DonnchaC".
1687 o Major features (Ed25519 identity keys, Proposal 220):
1688 - Add support for offline encrypted Ed25519 master keys. To use this
1689 feature on your tor relay, run "tor --keygen" to make a new master
1690 key (or to make a new signing key if you already have a master
1691 key). Closes ticket 13642.
1692 - All relays now maintain a stronger identity key, using the Ed25519
1693 elliptic curve signature format. This master key is designed so
1694 that it can be kept offline. Relays also generate an online
1695 signing key, and a set of other Ed25519 keys and certificates.
1696 These are all automatically regenerated and rotated as needed.
1697 Implements part of ticket 12498.
1698 - Directory authorities now vote on Ed25519 identity keys along with
1699 RSA1024 keys. Implements part of ticket 12498.
1700 - Directory authorities track which Ed25519 identity keys have been
1701 used with which RSA1024 identity keys, and do not allow them to
1702 vary freely. Implements part of ticket 12498.
1703 - Microdescriptors now include Ed25519 identity keys. Implements
1704 part of ticket 12498.
1705 - Add a --newpass option to allow changing or removing the
1706 passphrase of an encrypted key with tor --keygen. Implements part
1708 - Add a new OfflineMasterKey option to tell Tor never to try loading
1709 or generating a secret Ed25519 identity key. You can use this in
1710 combination with tor --keygen to manage offline and/or encrypted
1711 Ed25519 keys. Implements ticket 16944.
1712 - On receiving a HUP signal, check to see whether the Ed25519
1713 signing key has changed, and reload it if so. Closes ticket 16790.
1714 - Significant usability improvements for Ed25519 key management. Log
1715 messages are better, and the code can recover from far more
1716 failure conditions. Thanks to "s7r" for reporting and diagnosing
1719 o Major features (ECC performance):
1720 - Improve the runtime speed of Ed25519 signature verification by
1721 using Ed25519-donna's batch verification support. Implements
1723 - Improve the speed of Ed25519 operations and Curve25519 keypair
1724 generation when built targeting 32 bit x86 platforms with SSE2
1725 available. Implements ticket 16535.
1726 - Improve the runtime speed of Ed25519 operations by using the
1727 public-domain Ed25519-donna by Andrew M. ("floodyberry").
1728 Implements ticket 16467.
1729 - Improve the runtime speed of the ntor handshake by using an
1730 optimized curve25519 basepoint scalarmult implementation from the
1731 public-domain Ed25519-donna by Andrew M. ("floodyberry"), based on
1732 ideas by Adam Langley. Implements ticket 9663.
1734 o Major features (Hidden services):
1735 - Hidden services, if using the EntryNodes option, are required to
1736 use more than one EntryNode, in order to avoid a guard discovery
1737 attack. (This would only affect people who had configured hidden
1738 services and manually specified the EntryNodes option with a
1739 single entry-node. The impact was that it would be easy to
1740 remotely identify the guard node used by such a hidden service.
1741 See ticket for more information.) Fixes ticket 14917.
1742 - Add the torrc option HiddenServiceNumIntroductionPoints, to
1743 specify a fixed number of introduction points. Its maximum value
1744 is 10 and default is 3. Using this option can increase a hidden
1745 service's reliability under load, at the cost of making it more
1746 visible that the hidden service is facing extra load. Closes
1748 - Remove the adaptive algorithm for choosing the number of
1749 introduction points, which used to change the number of
1750 introduction points (poorly) depending on the number of
1751 connections the HS sees. Closes ticket 4862.
1753 o Major features (onion key cross-certification):
1754 - Relay descriptors now include signatures of their own identity
1755 keys, made using the TAP and ntor onion keys. These signatures
1756 allow relays to prove ownership of their own onion keys. Because
1757 of this change, microdescriptors will no longer need to include
1758 RSA identity keys. Implements proposal 228; closes ticket 12499.
1760 o Major bugfixes (client-side privacy, also in 0.2.6.9):
1761 - Properly separate out each SOCKSPort when applying stream
1762 isolation. The error occurred because each port's session group
1763 was being overwritten by a default value when the listener
1764 connection was initialized. Fixes bug 16247; bugfix on
1765 0.2.6.3-alpha. Patch by "jojelino".
1767 o Major bugfixes (hidden service clients, stability, also in 0.2.6.10):
1768 - Stop refusing to store updated hidden service descriptors on a
1769 client. This reverts commit 9407040c59218 (which indeed fixed bug
1770 14219, but introduced a major hidden service reachability
1771 regression detailed in bug 16381). This is a temporary fix since
1772 we can live with the minor issue in bug 14219 (it just results in
1773 some load on the network) but the regression of 16381 is too much
1774 of a setback. First-round fix for bug 16381; bugfix
1777 o Major bugfixes (hidden services):
1778 - Revert commit that made directory authorities assign the HSDir
1779 flag to relay without a DirPort; this was bad because such relays
1780 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
1782 - When cannibalizing a circuit for an introduction point, always
1783 extend to the chosen exit node (creating a 4 hop circuit).
1784 Previously Tor would use the current circuit exit node, which
1785 changed the original choice of introduction point, and could cause
1786 the hidden service to skip excluded introduction points or
1787 reconnect to a skipped introduction point. Fixes bug 16260; bugfix
1790 o Major bugfixes (memory leaks):
1791 - Fix a memory leak in ed25519 batch signature checking. Fixes bug
1792 17398; bugfix on 0.2.6.1-alpha.
1794 o Major bugfixes (open file limit):
1795 - The open file limit wasn't checked before calling
1796 tor_accept_socket_nonblocking(), which would make Tor exceed the
1797 limit. Now, before opening a new socket, Tor validates the open
1798 file limit just before, and if the max has been reached, return an
1799 error. Fixes bug 16288; bugfix on 0.1.1.1-alpha.
1801 o Major bugfixes (security, correctness):
1802 - Fix an error that could cause us to read 4 bytes before the
1803 beginning of an openssl string. This bug could be used to cause
1804 Tor to crash on systems with unusual malloc implementations, or
1805 systems with unusual hardening installed. Fixes bug 17404; bugfix
1808 o Major bugfixes (stability, also in 0.2.6.10):
1809 - Stop crashing with an assertion failure when parsing certain kinds
1810 of malformed or truncated microdescriptors. Fixes bug 16400;
1811 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
1812 by "cypherpunks_backup".
1813 - Stop random client-side assertion failures that could occur when
1814 connecting to a busy hidden service, or connecting to a hidden
1815 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
1818 o Minor features (client, SOCKS):
1819 - Add GroupWritable and WorldWritable options to unix-socket based
1820 SocksPort and ControlPort options. These options apply to a single
1821 socket, and override {Control,Socks}SocketsGroupWritable. Closes
1823 - Relax the validation done to hostnames in SOCKS5 requests, and
1824 allow a single trailing '.' to cope with clients that pass FQDNs
1825 using that syntax to explicitly indicate that the domain name is
1826 fully-qualified. Fixes bug 16674; bugfix on 0.2.6.2-alpha.
1827 - Relax the validation of hostnames in SOCKS5 requests, allowing the
1828 character '_' to appear, in order to cope with domains observed in
1829 the wild that are serving non-RFC compliant records. Resolves
1832 o Minor features (client-side privacy):
1833 - New KeepAliveIsolateSOCKSAuth option to indefinitely extend circuit
1834 lifespan when IsolateSOCKSAuth and streams with SOCKS
1835 authentication are attached to the circuit. This allows
1836 applications like TorBrowser to manage circuit lifetime on their
1837 own. Implements feature 15482.
1838 - When logging malformed hostnames from SOCKS5 requests, respect
1839 SafeLogging configuration. Fixes bug 16891; bugfix on 0.1.1.16-rc.
1841 o Minor features (clock-jump tolerance):
1842 - Recover better when our clock jumps back many hours, like might
1843 happen for Tails or Whonix users who start with a very wrong
1844 hardware clock, use Tor to discover a more accurate time, and then
1845 fix their clock. Resolves part of ticket 8766.
1847 o Minor features (command-line interface):
1848 - Make --hash-password imply --hush to prevent unnecessary noise.
1849 Closes ticket 15542. Patch from "cypherpunks".
1850 - Print a warning whenever we find a relative file path being used
1851 as torrc option. Resolves issue 14018.
1853 o Minor features (compilation):
1854 - Give a warning as early as possible when trying to build with an
1855 unsupported OpenSSL version. Closes ticket 16901.
1856 - Use C99 variadic macros when the compiler is not GCC. This avoids
1857 failing compilations on MSVC, and fixes a log-file-based race
1858 condition in our old workarounds. Original patch from Gisle Vanem.
1860 o Minor features (control protocol):
1861 - Support network-liveness GETINFO key and NETWORK_LIVENESS event in
1862 the control protocol. Resolves ticket 15358.
1864 o Minor features (controller):
1865 - Add DirAuthority lines for default directory authorities to the
1866 output of the "GETINFO config/defaults" command if not already
1867 present. Implements ticket 14840.
1868 - Controllers can now use "GETINFO hs/client/desc/id/..." to
1869 retrieve items from the client's hidden service descriptor cache.
1870 Closes ticket 14845.
1871 - Implement a new controller command "GETINFO status/fresh-relay-
1872 descs" to fetch a descriptor/extrainfo pair that was generated on
1873 demand just for the controller's use. Implements ticket 14784.
1875 o Minor features (directory authorities):
1876 - Directory authorities no longer vote against the "Fast", "Stable",
1877 and "HSDir" flags just because they were going to vote against
1878 "Running": if the consensus turns out to be that the router was
1879 running, then the authority's vote should count. Patch from Peter
1880 Retzlaff; closes issue 8712.
1882 o Minor features (directory authorities, security, also in 0.2.6.9):
1883 - The HSDir flag given by authorities now requires the Stable flag.
1884 For the current network, this results in going from 2887 to 2806
1885 HSDirs. Also, it makes it harder for an attacker to launch a sybil
1886 attack by raising the effort for a relay to become Stable to
1887 require at the very least 7 days, while maintaining the 96 hours
1888 uptime requirement for HSDir. Implements ticket 8243.
1890 o Minor features (DoS-resistance):
1891 - Make it harder for attackers to overload hidden services with
1892 introductions, by blocking multiple introduction requests on the
1893 same circuit. Resolves ticket 15515.
1895 o Minor features (geoip):
1896 - Update geoip and geoip6 to the October 9 2015 Maxmind GeoLite2
1899 o Minor features (hidden services):
1900 - Add the new options "HiddenServiceMaxStreams" and
1901 "HiddenServiceMaxStreamsCloseCircuit" to allow hidden services to
1902 limit the maximum number of simultaneous streams per circuit, and
1903 optionally tear down the circuit when the limit is exceeded. Part
1905 - Client now uses an introduction point failure cache to know when
1906 to fetch or keep a descriptor in their cache. Previously, failures
1907 were recorded implicitly, but not explicitly remembered. Closes
1909 - Relays need to have the Fast flag to get the HSDir flag. As this
1910 is being written, we'll go from 2745 HSDirs down to 2342, a ~14%
1911 drop. This change should make some attacks against the hidden
1912 service directory system harder. Fixes ticket 15963.
1913 - Turn on hidden service statistics collection by setting the torrc
1914 option HiddenServiceStatistics to "1" by default. (This keeps
1915 track only of the fraction of traffic used by hidden services, and
1916 the total number of hidden services in existence.) Closes
1918 - To avoid leaking HS popularity, don't cycle the introduction point
1919 when we've handled a fixed number of INTRODUCE2 cells but instead
1920 cycle it when a random number of introductions is reached, thus
1921 making it more difficult for an attacker to find out the amount of
1922 clients that have used the introduction point for a specific HS.
1923 Closes ticket 15745.
1925 o Minor features (logging):
1926 - Include the Tor version in all LD_BUG log messages, since people
1927 tend to cut and paste those into the bugtracker. Implements
1930 o Minor features (pluggable transports):
1931 - When launching managed pluggable transports on Linux systems,
1932 attempt to have the kernel deliver a SIGTERM on tor exit if the
1933 pluggable transport process is still running. Resolves
1935 - When launching managed pluggable transports, setup a valid open
1936 stdin in the child process that can be used to detect if tor has
1937 terminated. The "TOR_PT_EXIT_ON_STDIN_CLOSE" environment variable
1938 can be used by implementations to detect this new behavior.
1939 Resolves ticket 15435.
1941 o Minor bugfixes (torrc exit policies):
1942 - In each instance above, usage advice is provided to avoid the
1943 message. Resolves ticket 16069. Patch by "teor". Fixes part of bug
1944 16069; bugfix on 0.2.4.7-alpha.
1945 - In torrc, "accept6 *" and "reject6 *" ExitPolicy lines now only
1946 produce IPv6 wildcard addresses. Previously they would produce
1947 both IPv4 and IPv6 wildcard addresses. Patch by "teor". Fixes part
1948 of bug 16069; bugfix on 0.2.4.7-alpha.
1949 - When parsing torrc ExitPolicies, we now issue an info-level
1950 message when expanding an "accept/reject *" line to include both
1951 IPv4 and IPv6 wildcard addresses. Related to ticket 16069.
1952 - When parsing torrc ExitPolicies, we now warn for a number of cases
1953 where the user's intent is likely to differ from Tor's actual
1954 behavior. These include: using an IPv4 address with an accept6 or
1955 reject6 line; using "private" on an accept6 or reject6 line; and
1956 including any ExitPolicy lines after accept *:* or reject *:*.
1957 Related to ticket 16069.
1959 o Minor bugfixes (command-line interface):
1960 - When "--quiet" is provided along with "--validate-config", do not
1961 write anything to stdout on success. Fixes bug 14994; bugfix
1963 - When complaining about bad arguments to "--dump-config", use
1965 - Print usage information for --dump-config when it is used without
1966 an argument. Also, fix the error message to use different wording
1967 and add newline at the end. Fixes bug 15541; bugfix
1970 o Minor bugfixes (compilation):
1971 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
1972 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
1973 - Repair compilation with the most recent (unreleased, alpha)
1974 vesions of OpenSSL 1.1. Fixes part of ticket 17237.
1976 o Minor bugfixes (compilation, also in 0.2.6.9):
1977 - Build with --enable-systemd correctly when libsystemd is
1978 installed, but systemd is not. Fixes bug 16164; bugfix on
1979 0.2.6.3-alpha. Patch from Peter Palfrader.
1981 o Minor bugfixes (configuration, unit tests):
1982 - Only add the default fallback directories when the DirAuthorities,
1983 AlternateDirAuthority, and FallbackDir directory config options
1984 are set to their defaults. The default fallback directory list is
1985 currently empty, this fix will only change tor's behavior when it
1986 has default fallback directories. Includes unit tests for
1987 consider_adding_dir_servers(). Fixes bug 15642; bugfix on
1988 90f6071d8dc0 in 0.2.4.7-alpha. Patch by "teor".
1990 o Minor bugfixes (controller):
1991 - Add the descriptor ID in each HS_DESC control event. It was
1992 missing, but specified in control-spec.txt. Fixes bug 15881;
1993 bugfix on 0.2.5.2-alpha.
1995 o Minor bugfixes (correctness):
1996 - For correctness, avoid modifying a constant string in
1997 handle_control_postdescriptor. Fixes bug 15546; bugfix
1999 - Remove side-effects from tor_assert() calls. This was harmless,
2000 because we never disable assertions, but it is bad style and
2001 unnecessary. Fixes bug 15211; bugfix on 0.2.5.5, 0.2.2.36,
2003 - When calling channel_free_list(), avoid calling smartlist_remove()
2004 while inside a FOREACH loop. This partially reverts commit
2005 17356fe7fd96af where the correct SMARTLIST_DEL_CURRENT was
2006 incorrectly removed. Fixes bug 16924; bugfix on 0.2.4.4-alpha.
2008 o Minor bugfixes (crypto error-handling, also in 0.2.6.10):
2009 - Check for failures from crypto_early_init, and refuse to continue.
2010 A previous typo meant that we could keep going with an
2011 uninitialized crypto library, and would have OpenSSL initialize
2012 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
2013 when implementing ticket 4900. Patch by "teor".
2015 o Minor bugfixes (hidden service):
2016 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
2017 a client authorized hidden service. Fixes bug 15823; bugfix
2019 - Remove an extraneous newline character from the end of hidden
2020 service descriptors. Fixes bug 15296; bugfix on 0.2.0.10-alpha.
2022 o Minor bugfixes (Linux seccomp2 sandbox):
2023 - Use the sandbox in tor_open_cloexec whether or not O_CLOEXEC is
2024 defined. Patch by "teor". Fixes bug 16515; bugfix on 0.2.3.1-alpha.
2025 - Allow bridge authorities to run correctly under the seccomp2
2026 sandbox. Fixes bug 16964; bugfix on 0.2.5.1-alpha.
2027 - Add the "hidserv-stats" filename to our sandbox filter for the
2028 HiddenServiceStatistics option to work properly. Fixes bug 17354;
2029 bugfix on 0.2.6.2-alpha. Patch from David Goulet.
2031 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.10):
2032 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
2033 these when eventfd2() support is missing. Fixes bug 16363; bugfix
2034 on 0.2.6.3-alpha. Patch from "teor".
2036 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.9):
2037 - Allow systemd connections to work with the Linux seccomp2 sandbox
2038 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
2040 - Fix sandboxing to work when running as a relay, by allowing the
2041 renaming of secret_id_key, and allowing the eventfd2 and futex
2042 syscalls. Fixes bug 16244; bugfix on 0.2.6.1-alpha. Patch by
2045 o Minor bugfixes (logging):
2046 - When building Tor under Clang, do not include an extra set of
2047 parentheses in log messages that include function names. Fixes bug
2048 15269; bugfix on every released version of Tor when compiled with
2049 recent enough Clang.
2051 o Minor bugfixes (network):
2052 - When attempting to use fallback technique for network interface
2053 lookup, disregard loopback and multicast addresses since they are
2054 unsuitable for public communications.
2056 o Minor bugfixes (open file limit):
2057 - Fix set_max_file_descriptors() to set by default the max open file
2058 limit to the current limit when setrlimit() fails. Fixes bug
2059 16274; bugfix on tor- 0.2.0.10-alpha. Patch by dgoulet.
2061 o Minor bugfixes (portability):
2062 - Check correctly for Windows socket errors in the workqueue
2063 backend. Fixes bug 16741; bugfix on 0.2.6.3-alpha.
2064 - Try harder to normalize the exit status of the Tor process to the
2065 standard-provided range. Fixes bug 16975; bugfix on every version
2067 - Use libexecinfo on FreeBSD to enable backtrace support. Fixes part
2068 of bug 17151; bugfix on 0.2.5.2-alpha. Patch from Marcin Cieślak.
2070 o Minor bugfixes (relay):
2071 - Ensure that worker threads actually exit when a fatal error or
2072 shutdown is indicated. This fix doesn't currently affect the
2073 behavior of Tor, because Tor workers never indicates fatal error
2074 or shutdown except in the unit tests. Fixes bug 16868; bugfix
2076 - Fix a rarely-encountered memory leak when failing to initialize
2077 the thread pool. Fixes bug 16631; bugfix on 0.2.6.3-alpha. Patch
2079 - Unblock threads before releasing the work queue mutex to ensure
2080 predictable scheduling behavior. Fixes bug 16644; bugfix
2083 o Minor bugfixes (security, exit policies):
2084 - ExitPolicyRejectPrivate now also rejects the relay's published
2085 IPv6 address (if any), and any publicly routable IPv4 or IPv6
2086 addresses on any local interfaces. ticket 17027. Patch by "teor".
2087 Fixes bug 17027; bugfix on 0.2.0.11-alpha.
2089 o Minor bugfixes (statistics):
2090 - Disregard the ConnDirectionStatistics torrc options when Tor is
2091 not a relay since in that mode of operation no sensible data is
2092 being collected and because Tor might run into measurement hiccups
2093 when running as a client for some time, then becoming a relay.
2094 Fixes bug 15604; bugfix on 0.2.2.35.
2096 o Minor bugfixes (systemd):
2097 - Tor's systemd unit file no longer contains extraneous spaces.
2098 These spaces would sometimes confuse tools like deb-systemd-
2099 helper. Fixes bug 16162; bugfix on 0.2.5.5-alpha.
2101 o Minor bugfixes (test networks):
2102 - When self-testing reachability, use ExtendAllowPrivateAddresses to
2103 determine if local/private addresses imply reachability. The
2104 previous fix used TestingTorNetwork, which implies
2105 ExtendAllowPrivateAddresses, but this excluded rare configurations
2106 where ExtendAllowPrivateAddresses is set but TestingTorNetwork is
2107 not. Fixes bug 15771; bugfix on 0.2.6.1-alpha. Patch by "teor",
2108 issue discovered by CJ Ess.
2110 o Minor bugfixes (tests, also in 0.2.6.9):
2111 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
2112 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
2114 o Code simplification and refactoring:
2115 - Change the function that's called when we need to retry all
2116 downloads so that it only reschedules the downloads to happen
2117 immediately, rather than launching them all at once itself. This
2118 further simplifies Tor's callgraph.
2119 - Define WINVER and _WIN32_WINNT centrally, in orconfig.h, in order
2120 to ensure they remain consistent and visible everywhere.
2121 - Move some format-parsing functions out of crypto.c and
2122 crypto_curve25519.c into crypto_format.c and/or util_format.c.
2123 - Move the client-only parts of init_keys() into a separate
2124 function. Closes ticket 16763.
2125 - Move the hacky fallback code out of get_interface_address6() into
2126 separate function and get it covered with unit-tests. Resolves
2128 - Refactor hidden service client-side cache lookup to intelligently
2129 report its various failure cases, and disentangle failure cases
2130 involving a lack of introduction points. Closes ticket 14391.
2131 - Remove some vestigial workarounds for the MSVC6 compiler. We
2132 haven't supported that in ages.
2133 - Remove the unused "nulterminate" argument from buf_pullup().
2134 - Simplify the microdesc_free() implementation so that it no longer
2135 appears (to code analysis tools) to potentially invoke a huge
2136 suite of other microdesc functions.
2137 - Simply the control graph further by deferring the inner body of
2138 directory_all_unreachable() into a callback. Closes ticket 16762.
2139 - The link authentication code has been refactored for better
2140 testability and reliability. It now uses code generated with the
2141 "trunnel" binary encoding generator, to reduce the risk of bugs
2142 due to programmer error. Done as part of ticket 12498.
2143 - Treat the loss of an owning controller as equivalent to a SIGTERM
2144 signal. This removes a tiny amount of duplicated code, and
2145 simplifies our callgraph. Closes ticket 16788.
2146 - Use our own Base64 encoder instead of OpenSSL's, to allow more
2147 control over the output. Part of ticket 15652.
2148 - When generating an event to send to the controller, we no longer
2149 put the event over the network immediately. Instead, we queue
2150 these events, and use a Libevent callback to deliver them. This
2151 change simplifies Tor's callgraph by reducing the number of
2152 functions from which all other Tor functions are reachable. Closes
2154 - Wrap Windows-only C files inside '#ifdef _WIN32' so that tools
2155 that try to scan or compile every file on Unix won't decide that
2159 - Fix capitalization of SOCKS in sample torrc. Closes ticket 15609.
2160 - Improve the descriptions of statistics-related torrc options in
2161 the manpage to describe rationale and possible uses cases. Fixes
2163 - Improve the layout and formatting of ./configure --help messages.
2164 Closes ticket 15024. Patch from "cypherpunks".
2165 - Include a specific and (hopefully) accurate documentation of the
2166 torrc file's meta-format in doc/torrc_format.txt. This is mainly
2167 of interest to people writing programs to parse or generate torrc
2168 files. This document is not a commitment to long-term
2169 compatibility; some aspects of the current format are a bit
2170 ridiculous. Closes ticket 2325.
2171 - Include the TUNING document in our source tarball. It is referred
2172 to in the ChangeLog and an error message. Fixes bug 16929; bugfix
2174 - Note that HiddenServicePorts can take a unix domain socket. Closes
2176 - Recommend a 40 GB example AccountingMax in torrc.sample rather
2177 than a 4 GB max. Closes ticket 16742.
2178 - Standardize on the term "server descriptor" in the manual page.
2179 Previously, we had used "router descriptor", "server descriptor",
2180 and "relay descriptor" interchangeably. Part of ticket 14987.
2181 - Advise users on how to configure separate IPv4 and IPv6 exit
2182 policies in the manpage and sample torrcs. Related to ticket 16069.
2183 - Fix an error in the manual page and comments for
2184 TestingDirAuthVoteHSDir[IsStrict], which suggested that a HSDir
2185 required "ORPort connectivity". While this is true, it is in no
2186 way unique to the HSDir flag. Of all the flags, only HSDirs need a
2187 DirPort configured in order for the authorities to assign that
2188 particular flag. Patch by "teor". Fixed as part of 14882; bugfix
2190 - Fix the usage message of tor-resolve(1) so that it no longer lists
2191 the removed -F option. Fixes bug 16913; bugfix on 0.2.2.28-beta.
2194 - Remove `USE_OPENSSL_BASE64` and the corresponding fallback code
2195 and always use the internal Base64 decoder. The internal decoder
2196 has been part of tor since 0.2.0.10-alpha, and no one should
2197 be using the OpenSSL one. Part of ticket 15652.
2198 - Remove the 'tor_strclear()' function; use memwipe() instead.
2199 Closes ticket 14922.
2200 - Remove the code that would try to aggressively flush controller
2201 connections while writing to them. This code was introduced in
2202 0.1.2.7-alpha, in order to keep output buffers from exceeding
2203 their limits. But there is no longer a maximum output buffer size,
2204 and flushing data in this way caused some undesirable recursions
2205 in our call graph. Closes ticket 16480.
2206 - The internal pure-C tor-fw-helper tool is now removed from the Tor
2207 distribution, in favor of the pure-Go clone available from
2208 https://gitweb.torproject.org/tor-fw-helper.git/ . The libraries
2209 used by the C tor-fw-helper are not, in our opinion, very
2210 confidence- inspiring in their secure-programming techniques.
2211 Closes ticket 13338.
2214 - Remove the (seldom-used) DynamicDHGroups feature. For anti-
2215 fingerprinting we now recommend pluggable transports; for forward-
2216 secrecy in TLS, we now use the P-256 group. Closes ticket 13736.
2217 - Remove the HidServDirectoryV2 option. Now all relays offer to
2218 store hidden service descriptors. Related to 16543.
2219 - Remove the VoteOnHidServDirectoriesV2 option, since all
2220 authorities have long set it to 1. Closes ticket 16543.
2221 - Remove the undocumented "--digests" command-line option. It
2222 complicated our build process, caused subtle build issues on
2223 multiple platforms, and is now redundant since we started
2224 including git version identifiers. Closes ticket 14742.
2225 - Tor no longer contains checks for ancient directory cache versions
2226 that didn't know about microdescriptors.
2227 - Tor no longer contains workarounds for stat files generated by
2228 super-old versions of Tor that didn't choose guards sensibly.
2231 - The test-network.sh script now supports performance testing.
2232 Requires corresponding chutney performance testing changes. Patch
2233 by "teor". Closes ticket 14175.
2234 - Add a new set of callgraph analysis scripts that use clang to
2235 produce a list of which Tor functions are reachable from which
2236 other Tor functions. We're planning to use these to help simplify
2237 our code structure by identifying illogical dependencies.
2238 - Add new 'test-full' and 'test-full-online' targets to run all
2239 tests, including integration tests with stem and chutney.
2240 - Autodetect CHUTNEY_PATH if the chutney and Tor sources are side-
2241 by-side in the same parent directory. Closes ticket 16903. Patch
2243 - Document use of coverity, clang static analyzer, and clang dynamic
2244 undefined behavior and address sanitizers in doc/HACKING. Include
2245 detailed usage instructions in the blacklist. Patch by "teor".
2246 Closes ticket 15817.
2247 - Make "bridges+hs" the default test network. This tests almost all
2248 tor functionality during make test-network, while allowing tests
2249 to succeed on non-IPv6 systems. Requires chutney commit 396da92 in
2250 test-network-bridges-hs. Closes tickets 16945 (tor) and 16946
2251 (chutney). Patches by "teor".
2252 - Make the test-workqueue test work on Windows by initializing the
2253 network before we begin.
2254 - New make target (make test-network-all) to run multiple applicable
2255 chutney test cases. Patch from Teor; closes 16953.
2256 - Now that OpenSSL has its own scrypt implementation, add an unit
2257 test that checks for interoperability between libscrypt_scrypt()
2258 and OpenSSL's EVP_PBE_scrypt() so that we could not use libscrypt
2259 and rely on EVP_PBE_scrypt() whenever possible. Resolves
2261 - The link authentication protocol code now has extensive tests.
2262 - The relay descriptor signature testing code now has
2264 - The test_workqueue program now runs faster, and is enabled by
2265 default as a part of "make check".
2266 - Unit test dns_resolve(), dns_clip_ttl() and dns_get_expiry_ttl()
2267 functions in dns.c. Implements a portion of ticket 16831.
2268 - Use environment variables rather than autoconf substitutions to
2269 send variables from the build system to the test scripts. This
2270 change should be easier to maintain, and cause 'make distcheck' to
2271 work better than before. Fixes bug 17148.
2272 - When building Tor with testing coverage enabled, run Chutney tests
2273 (if any) using the 'tor-cov' coverage binary.
2274 - When running test-network or test-stem, check for the absence of
2275 stem/chutney before doing any build operations.
2276 - Add a test to verify that the compiler does not eliminate our
2277 memwipe() implementation. Closes ticket 15377.
2278 - Add make rule `check-changes` to verify the format of changes
2279 files. Closes ticket 15180.
2280 - Add unit tests for control_event_is_interesting(). Add a compile-
2281 time check that the number of events doesn't exceed the capacity
2282 of control_event_t.event_mask. Closes ticket 15431, checks for
2283 bugs similar to 13085. Patch by "teor".
2284 - Command-line argument tests moved to Stem. Resolves ticket 14806.
2285 - Integrate the ntor, backtrace, and zero-length keys tests into the
2286 automake test suite. Closes ticket 15344.
2287 - Remove assertions during builds to determine Tor's test coverage.
2288 We don't want to trigger these even in assertions, so including
2289 them artificially makes our branch coverage look worse than it is.
2290 This patch provides the new test-stem-full and coverage-html-full
2291 configure options. Implements ticket 15400.
2292 - New TestingDirAuthVote{Exit,Guard,HSDir}IsStrict flags to
2293 explicitly manage consensus flags in testing networks. Patch by
2294 "robgjansen", modified by "teor". Implements part of ticket 14882.
2295 - Check for matching value in server response in ntor_ref.py. Fixes
2296 bug 15591; bugfix on 0.2.4.8-alpha. Reported and fixed
2298 - Set the severity correctly when testing
2299 get_interface_addresses_ifaddrs() and
2300 get_interface_addresses_win32(), so that the tests fail gracefully
2301 instead of triggering an assertion. Fixes bug 15759; bugfix on
2302 0.2.6.3-alpha. Reported by Nicolas Derive.
2304 Changes in version 0.2.6.10 - 2015-07-12
2305 Tor version 0.2.6.10 fixes some significant stability and hidden
2306 service client bugs, bulletproofs the cryptography init process, and
2307 fixes a bug when using the sandbox code with some older versions of
2308 Linux. Everyone running an older version, especially an older version
2309 of 0.2.6, should upgrade.
2311 o Major bugfixes (hidden service clients, stability):
2312 - Stop refusing to store updated hidden service descriptors on a
2313 client. This reverts commit 9407040c59218 (which indeed fixed bug
2314 14219, but introduced a major hidden service reachability
2315 regression detailed in bug 16381). This is a temporary fix since
2316 we can live with the minor issue in bug 14219 (it just results in
2317 some load on the network) but the regression of 16381 is too much
2318 of a setback. First-round fix for bug 16381; bugfix
2321 o Major bugfixes (stability):
2322 - Stop crashing with an assertion failure when parsing certain kinds
2323 of malformed or truncated microdescriptors. Fixes bug 16400;
2324 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
2325 by "cypherpunks_backup".
2326 - Stop random client-side assertion failures that could occur when
2327 connecting to a busy hidden service, or connecting to a hidden
2328 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
2331 o Minor features (geoip):
2332 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
2333 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
2335 o Minor bugfixes (crypto error-handling):
2336 - Check for failures from crypto_early_init, and refuse to continue.
2337 A previous typo meant that we could keep going with an
2338 uninitialized crypto library, and would have OpenSSL initialize
2339 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
2340 when implementing ticket 4900. Patch by "teor".
2342 o Minor bugfixes (Linux seccomp2 sandbox):
2343 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
2344 these when eventfd2() support is missing. Fixes bug 16363; bugfix
2345 on 0.2.6.3-alpha. Patch from "teor".
2348 Changes in version 0.2.6.9 - 2015-06-11
2349 Tor 0.2.6.9 fixes a regression in the circuit isolation code, increases the
2350 requirements for receiving an HSDir flag, and addresses some other small
2351 bugs in the systemd and sandbox code. Clients using circuit isolation
2352 should upgrade; all directory authorities should upgrade.
2354 o Major bugfixes (client-side privacy):
2355 - Properly separate out each SOCKSPort when applying stream
2356 isolation. The error occurred because each port's session group was
2357 being overwritten by a default value when the listener connection
2358 was initialized. Fixes bug 16247; bugfix on 0.2.6.3-alpha. Patch
2361 o Minor feature (directory authorities, security):
2362 - The HSDir flag given by authorities now requires the Stable flag.
2363 For the current network, this results in going from 2887 to 2806
2364 HSDirs. Also, it makes it harder for an attacker to launch a sybil
2365 attack by raising the effort for a relay to become Stable which
2366 takes at the very least 7 days to do so and by keeping the 96
2367 hours uptime requirement for HSDir. Implements ticket 8243.
2369 o Minor bugfixes (compilation):
2370 - Build with --enable-systemd correctly when libsystemd is
2371 installed, but systemd is not. Fixes bug 16164; bugfix on
2372 0.2.6.3-alpha. Patch from Peter Palfrader.
2374 o Minor bugfixes (Linux seccomp2 sandbox):
2375 - Fix sandboxing to work when running as a relaymby renaming of
2376 secret_id_key, and allowing the eventfd2 and futex syscalls. Fixes
2377 bug 16244; bugfix on 0.2.6.1-alpha. Patch by Peter Palfrader.
2378 - Allow systemd connections to work with the Linux seccomp2 sandbox
2379 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
2382 o Minor bugfixes (tests):
2383 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
2384 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
2387 Changes in version 0.2.6.8 - 2015-05-21
2388 Tor 0.2.6.8 fixes a bit of dodgy code in parsing INTRODUCE2 cells, and
2389 fixes an authority-side bug in assigning the HSDir flag. All directory
2390 authorities should upgrade.
2392 o Major bugfixes (hidden services, backport from 0.2.7.1-alpha):
2393 - Revert commit that made directory authorities assign the HSDir
2394 flag to relay without a DirPort; this was bad because such relays
2395 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
2398 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
2399 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
2400 a client authorized hidden service. Fixes bug 15823; bugfix
2403 o Minor features (geoip):
2404 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
2405 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
2409 Changes in version 0.2.6.7 - 2015-04-06
2410 Tor 0.2.6.7 fixes two security issues that could be used by an
2411 attacker to crash hidden services, or crash clients visiting hidden
2412 services. Hidden services should upgrade as soon as possible; clients
2413 should upgrade whenever packages become available.
2415 This release also contains two simple improvements to make hidden
2416 services a bit less vulnerable to denial-of-service attacks.
2418 o Major bugfixes (security, hidden service):
2419 - Fix an issue that would allow a malicious client to trigger an
2420 assertion failure and halt a hidden service. Fixes bug 15600;
2421 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
2422 - Fix a bug that could cause a client to crash with an assertion
2423 failure when parsing a malformed hidden service descriptor. Fixes
2424 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
2426 o Minor features (DoS-resistance, hidden service):
2427 - Introduction points no longer allow multiple INTRODUCE1 cells to
2428 arrive on the same circuit. This should make it more expensive for
2429 attackers to overwhelm hidden services with introductions.
2430 Resolves ticket 15515.
2431 - Decrease the amount of reattempts that a hidden service performs
2432 when its rendezvous circuits fail. This reduces the computational
2433 cost for running a hidden service under heavy load. Resolves
2437 Changes in version 0.2.5.12 - 2015-04-06
2438 Tor 0.2.5.12 backports two fixes from 0.2.6.7 for security issues that
2439 could be used by an attacker to crash hidden services, or crash clients
2440 visiting hidden services. Hidden services should upgrade as soon as
2441 possible; clients should upgrade whenever packages become available.
2443 This release also backports a simple improvement to make hidden
2444 services a bit less vulnerable to denial-of-service attacks.
2446 o Major bugfixes (security, hidden service):
2447 - Fix an issue that would allow a malicious client to trigger an
2448 assertion failure and halt a hidden service. Fixes bug 15600;
2449 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
2450 - Fix a bug that could cause a client to crash with an assertion
2451 failure when parsing a malformed hidden service descriptor. Fixes
2452 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
2454 o Minor features (DoS-resistance, hidden service):
2455 - Introduction points no longer allow multiple INTRODUCE1 cells to
2456 arrive on the same circuit. This should make it more expensive for
2457 attackers to overwhelm hidden services with introductions.
2458 Resolves ticket 15515.
2461 Changes in version 0.2.4.27 - 2015-04-06
2462 Tor 0.2.4.27 backports two fixes from 0.2.6.7 for security issues that
2463 could be used by an attacker to crash hidden services, or crash clients
2464 visiting hidden services. Hidden services should upgrade as soon as
2465 possible; clients should upgrade whenever packages become available.
2467 This release also backports a simple improvement to make hidden
2468 services a bit less vulnerable to denial-of-service attacks.
2470 o Major bugfixes (security, hidden service):
2471 - Fix an issue that would allow a malicious client to trigger an
2472 assertion failure and halt a hidden service. Fixes bug 15600;
2473 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
2474 - Fix a bug that could cause a client to crash with an assertion
2475 failure when parsing a malformed hidden service descriptor. Fixes
2476 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
2478 o Minor features (DoS-resistance, hidden service):
2479 - Introduction points no longer allow multiple INTRODUCE1 cells to
2480 arrive on the same circuit. This should make it more expensive for
2481 attackers to overwhelm hidden services with introductions.
2482 Resolves ticket 15515.
2485 Changes in version 0.2.6.6 - 2015-03-24
2486 Tor 0.2.6.6 is the first stable release in the 0.2.6 series.
2488 It adds numerous safety, security, correctness, and performance
2489 improvements. Client programs can be configured to use more kinds of
2490 sockets, AutomapHosts works better, the multithreading backend is
2491 improved, cell transmission is refactored, test coverage is much
2492 higher, more denial-of-service attacks are handled, guard selection is
2493 improved to handle long-term guards better, pluggable transports
2494 should work a bit better, and some annoying hidden service performance
2495 bugs should be addressed.
2497 o New compiler and system requirements:
2498 - Tor 0.2.6.x requires that your compiler support more of the C99
2499 language standard than before. The 'configure' script now detects
2500 whether your compiler supports C99 mid-block declarations and
2501 designated initializers. If it does not, Tor will not compile.
2503 We may revisit this requirement if it turns out that a significant
2504 number of people need to build Tor with compilers that don't
2505 bother implementing a 15-year-old standard. Closes ticket 13233.
2506 - Tor no longer supports systems without threading support. When we
2507 began working on Tor, there were several systems that didn't have
2508 threads, or where the thread support wasn't able to run the
2509 threads of a single process on multiple CPUs. That no longer
2510 holds: every system where Tor needs to run well now has threading
2511 support. Resolves ticket 12439.
2513 o Deprecated versions and removed support:
2514 - Tor relays older than 0.2.4.18-rc are no longer allowed to
2515 advertise themselves on the network. Closes ticket 13555.
2516 - Tor clients no longer support connecting to hidden services
2517 running on Tor 0.2.2.x and earlier; the Support022HiddenServices
2518 option has been removed. (There shouldn't be any hidden services
2519 running these versions on the network.) Closes ticket 7803.
2521 o Directory authority changes:
2522 - The directory authority Faravahar has a new IP address. This
2523 closes ticket 14487.
2524 - Remove turtles as a directory authority.
2525 - Add longclaw as a new (v3) directory authority. This implements
2526 ticket 13296. This keeps the directory authority count at 9.
2528 o Major features (bridges):
2529 - Expose the outgoing upstream HTTP/SOCKS proxy to pluggable
2530 transports if they are configured via the "TOR_PT_PROXY"
2531 environment variable. Implements proposal 232. Resolves
2534 o Major features (changed defaults):
2535 - Prevent relay operators from unintentionally running exits: When a
2536 relay is configured as an exit node, we now warn the user unless
2537 the "ExitRelay" option is set to 1. We warn even more loudly if
2538 the relay is configured with the default exit policy, since this
2539 can indicate accidental misconfiguration. Setting "ExitRelay 0"
2540 stops Tor from running as an exit relay. Closes ticket 10067.
2542 o Major features (client performance, hidden services):
2543 - Allow clients to use optimistic data when connecting to a hidden
2544 service, which should remove a round-trip from hidden service
2545 initialization. See proposal 181 for details. Implements
2548 o Major features (directory system):
2549 - Upon receiving an unparseable directory object, if its digest
2550 matches what we expected, then don't try to download it again.
2551 Previously, when we got a descriptor we didn't like, we would keep
2552 trying to download it over and over. Closes ticket 11243.
2553 - When downloading server- or microdescriptors from a directory
2554 server, we no longer launch multiple simultaneous requests to the
2555 same server. This reduces load on the directory servers,
2556 especially when directory guards are in use. Closes ticket 9969.
2557 - When downloading server- or microdescriptors over a tunneled
2558 connection, do not limit the length of our requests to what the
2559 Squid proxy is willing to handle. Part of ticket 9969.
2560 - Authorities can now vote on the correct digests and latest
2561 versions for different software packages. This allows packages
2562 that include Tor to use the Tor authority system as a way to get
2563 notified of updates and their correct digests. Implements proposal
2564 227. Closes ticket 10395.
2566 o Major features (guards):
2567 - Introduce the Guardfraction feature to improves load balancing on
2568 guard nodes. Specifically, it aims to reduce the traffic gap that
2569 guard nodes experience when they first get the Guard flag. This is
2570 a required step if we want to increase the guard lifetime to 9
2571 months or greater. Closes ticket 9321.
2573 o Major features (hidden services):
2574 - Make HS port scanning more difficult by immediately closing the
2575 circuit when a user attempts to connect to a nonexistent port.
2576 Closes ticket 13667.
2577 - Add a HiddenServiceStatistics option that allows Tor relays to
2578 gather and publish statistics about the overall size and volume of
2579 hidden service usage. Specifically, when this option is turned on,
2580 an HSDir will publish an approximate number of hidden services
2581 that have published descriptors to it the past 24 hours. Also, if
2582 a relay has acted as a hidden service rendezvous point, it will
2583 publish the approximate amount of rendezvous cells it has relayed
2584 the past 24 hours. The statistics themselves are obfuscated so
2585 that the exact values cannot be derived. For more details see
2586 proposal 238, "Better hidden service stats from Tor relays". This
2587 feature is currently disabled by default. Implements feature 13192.
2589 o Major features (performance):
2590 - Make the CPU worker implementation more efficient by avoiding the
2591 kernel and lengthening pipelines. The original implementation used
2592 sockets to transfer data from the main thread to the workers, and
2593 didn't allow any thread to be assigned more than a single piece of
2594 work at once. The new implementation avoids communications
2595 overhead by making requests in shared memory, avoiding kernel IO
2596 where possible, and keeping more requests in flight at once.
2597 Implements ticket 9682.
2599 o Major features (relay):
2600 - Raise the minimum acceptable configured bandwidth rate for bridges
2601 to 50 KiB/sec and for relays to 75 KiB/sec. (The old values were
2602 20 KiB/sec.) Closes ticket 13822.
2603 - Complete revision of the code that relays use to decide which cell
2604 to send next. Formerly, we selected the best circuit to write on
2605 each channel, but we didn't select among channels in any
2606 sophisticated way. Now, we choose the best circuits globally from
2607 among those whose channels are ready to deliver traffic.
2609 This patch implements a new inter-cmux comparison API, a global
2610 high/low watermark mechanism and a global scheduler loop for
2611 transmission prioritization across all channels as well as among
2612 circuits on one channel. This schedule is currently tuned to
2613 (tolerantly) avoid making changes in network performance, but it
2614 should form the basis for major circuit performance increases in
2615 the future. Code by Andrea; tuning by Rob Jansen; implements
2618 o Major features (sample torrc):
2619 - Add a new, infrequently-changed "torrc.minimal". This file is
2620 similar to torrc.sample, but it will change as infrequently as
2621 possible, for the benefit of users whose systems prompt them for
2622 intervention whenever a default configuration file is changed.
2623 Making this change allows us to update torrc.sample to be a more
2624 generally useful "sample torrc".
2626 o Major features (security, unix domain sockets):
2627 - Allow SocksPort to be an AF_UNIX Unix Domain Socket. Now high risk
2628 applications can reach Tor without having to create AF_INET or
2629 AF_INET6 sockets, meaning they can completely disable their
2630 ability to make non-Tor network connections. To create a socket of
2631 this type, use "SocksPort unix:/path/to/socket". Implements
2633 - Support mapping hidden service virtual ports to AF_UNIX sockets.
2634 The syntax is "HiddenServicePort 80 unix:/path/to/socket".
2635 Implements ticket 11485.
2637 o Major bugfixes (client, automap):
2638 - Repair automapping with IPv6 addresses. This automapping should
2639 have worked previously, but one piece of debugging code that we
2640 inserted to detect a regression actually caused the regression to
2641 manifest itself again. Fixes bug 13811 and bug 12831; bugfix on
2642 0.2.4.7-alpha. Diagnosed and fixed by Francisco Blas
2645 o Major bugfixes (crash, OSX, security):
2646 - Fix a remote denial-of-service opportunity caused by a bug in
2647 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
2650 o Major bugfixes (directory authorities):
2651 - Do not assign the HSDir flag to relays if they are not Valid, or
2652 currently hibernating. Fixes 12573; bugfix on 0.2.0.10-alpha.
2654 o Major bugfixes (directory bandwidth performance):
2655 - Don't flush the zlib buffer aggressively when compressing
2656 directory information for clients. This should save about 7% of
2657 the bandwidth currently used for compressed descriptors and
2658 microdescriptors. Fixes bug 11787; bugfix on 0.1.1.23.
2660 o Major bugfixes (exit node stability):
2661 - Fix an assertion failure that could occur under high DNS load.
2662 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
2663 diagnosed and fixed by "cypherpunks".
2665 o Major bugfixes (FreeBSD IPFW transparent proxy):
2666 - Fix address detection with FreeBSD transparent proxies, when
2667 "TransProxyType ipfw" is in use. Fixes bug 15064; bugfix
2670 o Major bugfixes (hidden services):
2671 - When closing an introduction circuit that was opened in parallel
2672 with others, don't mark the introduction point as unreachable.
2673 Previously, the first successful connection to an introduction
2674 point would make the other introduction points get marked as
2675 having timed out. Fixes bug 13698; bugfix on 0.0.6rc2.
2677 o Major bugfixes (Linux seccomp2 sandbox):
2678 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
2679 crash during attempts to call wait4. Fixes bug 15088; bugfix on
2680 0.2.5.1-alpha. Patch from "sanic".
2682 o Major bugfixes (mixed relay-client operation):
2683 - When running as a relay and client at the same time (not
2684 recommended), if we decide not to use a new guard because we want
2685 to retry older guards, only close the locally-originating circuits
2686 passing through that guard. Previously we would close all the
2687 circuits through that guard. Fixes bug 9819; bugfix on
2688 0.2.1.1-alpha. Reported by "skruffy".
2690 o Major bugfixes (pluggable transports):
2691 - Initialize the extended OR Port authentication cookie before
2692 launching pluggable transports. This prevents a race condition
2693 that occured when server-side pluggable transports would cache the
2694 authentication cookie before it has been (re)generated. Fixes bug
2695 15240; bugfix on 0.2.5.1-alpha.
2697 o Major bugfixes (relay, stability, possible security):
2698 - Fix a bug that could lead to a relay crashing with an assertion
2699 failure if a buffer of exactly the wrong layout is passed to
2700 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
2701 0.2.0.10-alpha. Patch from "cypherpunks".
2702 - Do not assert if the 'data' pointer on a buffer is advanced to the
2703 very end of the buffer; log a BUG message instead. Only assert if
2704 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
2706 o Minor features (build):
2707 - New --disable-system-torrc compile-time option to prevent Tor from
2708 looking for the system-wide torrc or torrc-defaults files.
2709 Resolves ticket 13037.
2711 o Minor features (client):
2712 - Clients are now willing to send optimistic data (before they
2713 receive a 'connected' cell) to relays of any version. (Relays
2714 without support for optimistic data are no longer supported on the
2715 Tor network.) Resolves ticket 13153.
2717 o Minor features (client):
2718 - Validate hostnames in SOCKS5 requests more strictly. If SafeSocks
2719 is enabled, reject requests with IP addresses as hostnames.
2720 Resolves ticket 13315.
2722 o Minor features (controller):
2723 - Add a "SIGNAL HEARTBEAT" controller command that tells Tor to
2724 write an unscheduled heartbeat message to the log. Implements
2726 - Include SOCKS_USERNAME and SOCKS_PASSWORD values in controller
2727 events so controllers can observe circuit isolation inputs. Closes
2729 - ControlPort now supports the unix:/path/to/socket syntax as an
2730 alternative to the ControlSocket option, for consistency with
2731 SocksPort and HiddenServicePort. Closes ticket 14451.
2732 - New "GETINFO bw-event-cache" to get information about recent
2733 bandwidth events. Closes ticket 14128. Useful for controllers to
2734 get recent bandwidth history after the fix for ticket 13988.
2735 - Messages about problems in the bootstrap process now include
2736 information about the server we were trying to connect to when we
2737 noticed the problem. Closes ticket 15006.
2739 o Minor features (Denial of service resistance):
2740 - Count the total number of bytes used storing hidden service
2741 descriptors against the value of MaxMemInQueues. If we're low on
2742 memory, and more than 20% of our memory is used holding hidden
2743 service descriptors, free them until no more than 10% of our
2744 memory holds hidden service descriptors. Free the least recently
2745 fetched descriptors first. Resolves ticket 13806.
2746 - When we have recently been under memory pressure (over 3/4 of
2747 MaxMemInQueues is allocated), then allocate smaller zlib objects
2748 for small requests. Closes ticket 11791.
2750 o Minor features (directory authorities):
2751 - Don't list relays with a bandwidth estimate of 0 in the consensus.
2752 Implements a feature proposed during discussion of bug 13000.
2753 - In tor-gencert, report an error if the user provides the same
2754 argument more than once.
2755 - If a directory authority can't find a best consensus method in the
2756 votes that it holds, it now falls back to its favorite consensus
2757 method. Previously, it fell back to method 1. Neither of these is
2758 likely to get enough signatures, but "fall back to favorite"
2759 doesn't require us to maintain support an obsolete consensus
2760 method. Implements part of proposal 215.
2762 o Minor features (geoip):
2763 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
2764 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
2767 o Minor features (guard nodes):
2768 - Reduce the time delay before saving guard status to disk from 10
2769 minutes to 30 seconds (or from one hour to 10 minutes if
2770 AvoidDiskWrites is set). Closes ticket 12485.
2772 o Minor features (heartbeat):
2773 - On relays, report how many connections we negotiated using each
2774 version of the Tor link protocols. This information will let us
2775 know if removing support for very old versions of the Tor
2776 protocols is harming the network. Closes ticket 15212.
2778 o Minor features (hidden service):
2779 - Make Sybil attacks against hidden services harder by changing the
2780 minimum time required to get the HSDir flag from 25 hours up to 96
2781 hours. Addresses ticket 14149.
2782 - New option "HiddenServiceAllowUnknownPorts" to allow hidden
2783 services to disable the anti-scanning feature introduced in
2784 0.2.6.2-alpha. With this option not set, a connection to an
2785 unlisted port closes the circuit. With this option set, only a
2786 RELAY_DONE cell is sent. Closes ticket 14084.
2787 - When re-enabling the network, don't try to build introduction
2788 circuits until we have successfully built a circuit. This makes
2789 hidden services come up faster when the network is re-enabled.
2790 Patch from "akwizgran". Closes ticket 13447.
2791 - When we fail to retrieve a hidden service descriptor, send the
2792 controller an "HS_DESC FAILED" controller event. Implements
2794 - New HiddenServiceDirGroupReadable option to cause hidden service
2795 directories and hostname files to be created group-readable. Patch
2796 from "anon", David Stainton, and "meejah". Closes ticket 11291.
2798 o Minor features (interface):
2799 - Implement "-f -" command-line option to read torrc configuration
2800 from standard input, if you don't want to store the torrc file in
2801 the file system. Implements feature 13865.
2803 o Minor features (logging):
2804 - Add a count of unique clients to the bridge heartbeat message.
2805 Resolves ticket 6852.
2806 - Suppress "router info incompatible with extra info" message when
2807 reading extrainfo documents from cache. (This message got loud
2808 around when we closed bug 9812 in 0.2.6.2-alpha.) Closes
2810 - Elevate hidden service authorized-client message from DEBUG to
2811 INFO. Closes ticket 14015.
2812 - On Unix-like systems, you can now use named pipes as the target of
2813 the Log option, and other options that try to append to files.
2814 Closes ticket 12061. Patch from "carlo von lynX".
2815 - When opening a log file at startup, send it every log message that
2816 we generated between startup and opening it. Previously, log
2817 messages that were generated before opening the log file were only
2818 logged to stdout. Closes ticket 6938.
2819 - Add a TruncateLogFile option to overwrite logs instead of
2820 appending to them. Closes ticket 5583.
2821 - Quiet some log messages in the heartbeat and at startup. Closes
2824 o Minor features (portability, Solaris):
2825 - Threads are no longer disabled by default on Solaris; we believe
2826 that the versions of Solaris with broken threading support are all
2827 obsolete by now. Resolves ticket 9495.
2829 o Minor features (relay):
2830 - Re-check our address after we detect a changed IP address from
2831 getsockname(). This ensures that the controller command "GETINFO
2832 address" will report the correct value. Resolves ticket 11582.
2834 - A new AccountingRule option lets Relays set whether they'd like
2835 AccountingMax to be applied separately to inbound and outbound
2836 traffic, or applied to the sum of inbound and outbound traffic.
2837 Resolves ticket 961. Patch by "chobe".
2838 - When identity keypair is generated for first time, log a
2839 congratulatory message that links to the new relay lifecycle
2840 document. Implements feature 10427.
2842 o Minor features (security, memory wiping):
2843 - Ensure we securely wipe keys from memory after
2844 crypto_digest_get_digest and init_curve25519_keypair_from_file
2845 have finished using them. Resolves ticket 13477.
2847 o Minor features (security, out-of-memory handling):
2848 - When handling an out-of-memory condition, allocate less memory for
2849 temporary data structures. Fixes issue 10115.
2850 - When handling an out-of-memory condition, consider more types of
2851 buffers, including those on directory connections, and zlib
2852 buffers. Resolves ticket 11792.
2854 o Minor features (stability):
2855 - Add assertions in our hash-table iteration code to check for
2856 corrupted values that could cause infinite loops. Closes
2859 o Minor features (systemd):
2860 - Various improvements and modernizations in systemd hardening
2861 support. Closes ticket 13805. Patch from Craig Andrews.
2862 - Where supported, when running with systemd, report successful
2863 startup to systemd. Part of ticket 11016. Patch by Michael Scherer.
2864 - When running with systemd, support systemd watchdog messages. Part
2865 of ticket 11016. Patch by Michael Scherer.
2867 o Minor features (testing networks):
2868 - Add the TestingDirAuthVoteExit option, which lists nodes to assign
2869 the "Exit" flag regardless of their uptime, bandwidth, or exit
2870 policy. TestingTorNetwork must be set for this option to have any
2871 effect. Previously, authorities would take up to 35 minutes to
2872 give nodes the Exit flag in a test network. Partially implements
2874 - Drop the minimum RendPostPeriod on a testing network to 5 seconds,
2875 and the default on a testing network to 2 minutes. Drop the
2876 MIN_REND_INITIAL_POST_DELAY on a testing network to 5 seconds, but
2877 keep the default on a testing network at 30 seconds. This reduces
2878 HS bootstrap time to around 25 seconds. Also, change the default
2879 time in test-network.sh to match. Closes ticket 13401. Patch
2881 - Create TestingDirAuthVoteHSDir to correspond to
2882 TestingDirAuthVoteExit/Guard. Ensures that authorities vote the
2883 HSDir flag for the listed relays regardless of uptime or ORPort
2884 connectivity. Respects the value of VoteOnHidServDirectoriesV2.
2885 Partial implementation for ticket 14067. Patch by "teor".
2887 o Minor features (tor2web mode):
2888 - Introduce the config option Tor2webRendezvousPoints, which allows
2889 clients in Tor2webMode to select a specific Rendezvous Point to be
2890 used in HS circuits. This might allow better performance for
2891 Tor2Web nodes. Implements ticket 12844.
2893 o Minor features (transparent proxy):
2894 - Update the transparent proxy option checks to allow for both ipfw
2895 and pf on OS X. Closes ticket 14002.
2896 - Use the correct option when using IPv6 with transparent proxy
2897 support on Linux. Resolves 13808. Patch by Francisco Blas
2900 o Minor features (validation):
2901 - Check all date/time values passed to tor_timegm and
2902 parse_rfc1123_time for validity, taking leap years into account.
2903 Improves HTTP header validation. Implemented with bug 13476.
2904 - In correct_tm(), limit the range of values returned by system
2905 localtime(_r) and gmtime(_r) to be between the years 1 and 8099.
2906 This means we don't have to deal with negative or too large dates,
2907 even if a clock is wrong. Otherwise we might fail to read a file
2908 written by us which includes such a date. Fixes bug 13476.
2909 - Stop allowing invalid address patterns like "*/24" that contain
2910 both a wildcard address and a bit prefix length. This affects all
2911 our address-range parsing code. Fixes bug 7484; bugfix
2914 o Minor bugfixes (bridge clients):
2915 - When configured to use a bridge without an identity digest (not
2916 recommended), avoid launching an extra channel to it when
2917 bootstrapping. Fixes bug 7733; bugfix on 0.2.4.4-alpha.
2919 o Minor bugfixes (bridges):
2920 - When DisableNetwork is set, do not launch pluggable transport
2921 plugins, and if any are running, terminate them. Fixes bug 13213;
2922 bugfix on 0.2.3.6-alpha.
2924 o Minor bugfixes (C correctness):
2925 - Fix several instances of possible integer overflow/underflow/NaN.
2926 Fixes bug 13104; bugfix on 0.2.3.1-alpha and later. Patches
2928 - In circuit_build_times_calculate_timeout() in circuitstats.c,
2929 avoid dividing by zero in the pareto calculations. This traps
2930 under clang's "undefined-trap" sanitizer. Fixes bug 13290; bugfix
2932 - Fix an integer overflow in format_time_interval(). Fixes bug
2933 13393; bugfix on 0.2.0.10-alpha.
2934 - Set the correct day of year value when the system's localtime(_r)
2935 or gmtime(_r) functions fail to set struct tm. Not externally
2936 visible. Fixes bug 13476; bugfix on 0.0.2pre14.
2937 - Avoid unlikely signed integer overflow in tor_timegm on systems
2938 with 32-bit time_t. Fixes bug 13476; bugfix on 0.0.2pre14.
2940 o Minor bugfixes (certificate handling):
2941 - If an authority operator accidentally makes a signing certificate
2942 with a future publication time, do not discard its real signing
2943 certificates. Fixes bug 11457; bugfix on 0.2.0.3-alpha.
2944 - Remove any old authority certificates that have been superseded
2945 for at least two days. Previously, we would keep superseded
2946 certificates until they expired, if they were published close in
2947 time to the certificate that superseded them. Fixes bug 11454;
2948 bugfix on 0.2.1.8-alpha.
2950 o Minor bugfixes (client):
2951 - Fix smartlist_choose_node_by_bandwidth() so that relays with the
2952 BadExit flag are not considered worthy candidates. Fixes bug
2953 13066; bugfix on 0.1.2.3-alpha.
2954 - Use the consensus schedule for downloading consensuses, and not
2955 the generic schedule. Fixes bug 11679; bugfix on 0.2.2.6-alpha.
2956 - Handle unsupported or malformed SOCKS5 requests properly by
2957 responding with the appropriate error message before closing the
2958 connection. Fixes bugs 12971 and 13314; bugfix on 0.0.2pre13.
2960 o Minor bugfixes (client, automapping):
2961 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
2962 no value follows the option. Fixes bug 14142; bugfix on
2963 0.2.4.7-alpha. Patch by "teor".
2964 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
2965 14195; bugfix on 0.1.0.1-rc.
2966 - Prevent changes to other options from removing the wildcard value
2967 "." from "AutomapHostsSuffixes". Fixes bug 12509; bugfix
2969 - Allow MapAddress and AutomapHostsOnResolve to work together when
2970 an address is mapped into another address type (like .onion) that
2971 must be automapped at resolve time. Fixes bug 7555; bugfix
2974 o Minor bugfixes (client, bridges):
2975 - When we are using bridges and we had a network connectivity
2976 problem, only retry connecting to our currently configured
2977 bridges, not all bridges we know about and remember using. Fixes
2978 bug 14216; bugfix on 0.2.2.17-alpha.
2980 o Minor bugfixes (client, DNS):
2981 - Report the correct cached DNS expiration times on SOCKS port or in
2982 DNS replies. Previously, we would report everything as "never
2983 expires." Fixes bug 14193; bugfix on 0.2.3.17-beta.
2984 - Avoid a small memory leak when we find a cached answer for a
2985 reverse DNS lookup in a client-side DNS cache. (Remember, client-
2986 side DNS caching is off by default, and is not recommended.) Fixes
2987 bug 14259; bugfix on 0.2.0.1-alpha.
2989 o Minor bugfixes (client, IPv6):
2990 - Reject socks requests to literal IPv6 addresses when IPv6Traffic
2991 flag is not set; and not because the NoIPv4Traffic flag was set.
2992 Previously we'd looked at the NoIPv4Traffic flag for both types of
2993 literal addresses. Fixes bug 14280; bugfix on 0.2.4.7-alpha.
2995 o Minor bugfixes (client, microdescriptors):
2996 - Use a full 256 bits of the SHA256 digest of a microdescriptor when
2997 computing which microdescriptors to download. This keeps us from
2998 erroneous download behavior if two microdescriptor digests ever
2999 have the same first 160 bits. Fixes part of bug 13399; bugfix
3001 - Reset a router's status if its microdescriptor digest changes,
3002 even if the first 160 bits remain the same. Fixes part of bug
3003 13399; bugfix on 0.2.3.1-alpha.
3005 o Minor bugfixes (client, torrc):
3006 - Stop modifying the value of our DirReqStatistics torrc option just
3007 because we're not a bridge or relay. This bug was causing Tor
3008 Browser users to write "DirReqStatistics 0" in their torrc files
3009 as if they had chosen to change the config. Fixes bug 4244; bugfix
3011 - When GeoIPExcludeUnknown is enabled, do not incorrectly decide
3012 that our options have changed every time we SIGHUP. Fixes bug
3013 9801; bugfix on 0.2.4.10-alpha. Patch from "qwerty1".
3015 o Minor bugfixes (compilation):
3016 - Fix a compilation warning on s390. Fixes bug 14988; bugfix
3018 - Silence clang warnings under --enable-expensive-hardening,
3019 including implicit truncation of 64 bit values to 32 bit, const
3020 char assignment to self, tautological compare, and additional
3021 parentheses around equality tests. Fixes bug 13577; bugfix
3023 - Fix a clang warning about checking whether an address in the
3024 middle of a structure is NULL. Fixes bug 14001; bugfix
3026 - The address of an array in the middle of a structure will always
3027 be non-NULL. clang recognises this and complains. Disable the
3028 tautologous and redundant check to silence this warning. Fixes bug
3029 14001; bugfix on 0.2.1.2-alpha.
3030 - Compile correctly with (unreleased) OpenSSL 1.1.0 headers.
3031 Addresses ticket 14188.
3032 - Build without warnings with the stock OpenSSL srtp.h header, which
3033 has a duplicate declaration of SSL_get_selected_srtp_profile().
3034 Fixes bug 14220; this is OpenSSL's bug, not ours.
3035 - Do not compile any code related to Tor2Web mode when Tor2Web mode
3036 is not enabled at compile time. Previously, this code was included
3037 in a disabled state. See discussion on ticket 12844.
3038 - Allow our configure script to build correctly with autoconf 2.62
3039 again. Fixes bug 12693; bugfix on 0.2.5.2-alpha.
3040 - Improve the error message from ./configure to make it clear that
3041 when asciidoc has not been found, the user will have to either add
3042 --disable-asciidoc argument or install asciidoc. Resolves
3045 o Minor bugfixes (controller):
3046 - Report "down" in response to the "GETINFO entry-guards" command
3047 when relays are down with an unreachable_since value. Previously,
3048 we would report "up". Fixes bug 14184; bugfix on 0.1.2.2-alpha.
3049 - Avoid crashing on a malformed EXTENDCIRCUIT command. Fixes bug
3050 14116; bugfix on 0.2.2.9-alpha.
3052 o Minor bugfixes (controller):
3053 - Return an error when the second or later arguments of the
3054 "setevents" controller command are invalid events. Previously we
3055 would return success while silently skipping invalid events. Fixes
3056 bug 13205; bugfix on 0.2.3.2-alpha. Reported by "fpxnns".
3058 o Minor bugfixes (directory authority):
3059 - Allow directory authorities to fetch more data from one another if
3060 they find themselves missing lots of votes. Previously, they had
3061 been bumping against the 10 MB queued data limit. Fixes bug 14261;
3062 bugfix on 0.1.2.5-alpha.
3063 - Do not attempt to download extrainfo documents which we will be
3064 unable to validate with a matching server descriptor. Fixes bug
3065 13762; bugfix on 0.2.0.1-alpha.
3066 - Fix a bug that was truncating AUTHDIR_NEWDESC events sent to the
3067 control port. Fixes bug 14953; bugfix on 0.2.0.1-alpha.
3068 - Enlarge the buffer to read bwauth generated files to avoid an
3069 issue when parsing the file in dirserv_read_measured_bandwidths().
3070 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
3071 - When running as a v3 directory authority, advertise that you serve
3072 extra-info documents so that clients who want them can find them
3073 from you too. Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
3075 o Minor bugfixes (directory system):
3076 - Always believe that v3 directory authorities serve extra-info
3077 documents, whether they advertise "caches-extra-info" or not.
3078 Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
3079 - Check the BRIDGE_DIRINFO flag bitwise rather than using equality.
3080 Previously, directories offering BRIDGE_DIRINFO and some other
3081 flag (i.e. microdescriptors or extrainfo) would be ignored when
3082 looking for bridges. Partially fixes bug 13163; bugfix
3085 o Minor bugfixes (file handling):
3086 - Stop failing when key files are zero-length. Instead, generate new
3087 keys, and overwrite the empty key files. Fixes bug 13111; bugfix
3088 on all versions of Tor. Patch by "teor".
3089 - Stop generating a fresh .old RSA onion key file when the .old file
3090 is missing. Fixes part of 13111; bugfix on 0.0.6rc1.
3091 - Avoid overwriting .old key files with empty key files.
3092 - Skip loading zero-length extrainfo store, router store, stats,
3093 state, and key files.
3094 - Avoid crashing when trying to reload a torrc specified as a
3095 relative path with RunAsDaemon turned on. Fixes bug 13397; bugfix
3098 o Minor bugfixes (hidden services):
3099 - Close the introduction circuit when we have no more usable intro
3100 points, instead of waiting for it to time out. This also ensures
3101 that no follow-up HS descriptor fetch is triggered when the
3102 circuit eventually times out. Fixes bug 14224; bugfix on 0.0.6.
3103 - When fetching a hidden service descriptor for a down service that
3104 was recently up, do not keep refetching until we try the same
3105 replica twice in a row. Fixes bug 14219; bugfix on 0.2.0.10-alpha.
3106 - Correctly send a controller event when we find that a rendezvous
3107 circuit has finished. Fixes bug 13936; bugfix on 0.1.1.5-alpha.
3108 - Pre-check directory permissions for new hidden-services to avoid
3109 at least one case of "Bug: Acting on config options left us in a
3110 broken state. Dying." Fixes bug 13942; bugfix on 0.0.6pre1.
3111 - When fetching hidden service descriptors, we now check not only
3112 for whether we got the hidden service we had in mind, but also
3113 whether we got the particular descriptors we wanted. This prevents
3114 a class of inefficient but annoying DoS attacks by hidden service
3115 directories. Fixes bug 13214; bugfix on 0.2.1.6-alpha. Reported
3118 o Minor bugfixes (Linux seccomp2 sandbox):
3119 - Make transparent proxy support work along with the seccomp2
3120 sandbox. Fixes part of bug 13808; bugfix on 0.2.5.1-alpha. Patch
3121 by Francisco Blas Izquierdo Riera.
3122 - Fix a memory leak in tor-resolve when running with the sandbox
3123 enabled. Fixes bug 14050; bugfix on 0.2.5.9-rc.
3124 - Allow glibc fatal errors to be sent to stderr before Tor exits.
3125 Previously, glibc would try to write them to /dev/tty, and the
3126 sandbox would trap the call and make Tor exit prematurely. Fixes
3127 bug 14759; bugfix on 0.2.5.1-alpha.
3129 o Minor bugfixes (logging):
3130 - Avoid crashing when there are more log domains than entries in
3131 domain_list. Bugfix on 0.2.3.1-alpha.
3132 - Downgrade warnings about RSA signature failures to info log level.
3133 Emit a warning when an extra info document is found incompatible
3134 with a corresponding router descriptor. Fixes bug 9812; bugfix
3136 - Make connection_ap_handshake_attach_circuit() log the circuit ID
3137 correctly. Fixes bug 13701; bugfix on 0.0.6.
3139 o Minor bugfixes (networking):
3140 - Check for orconns and use connection_or_close_for_error() rather
3141 than connection_mark_for_close() directly in the getsockopt()
3142 failure case of connection_handle_write_impl(). Fixes bug 11302;
3143 bugfix on 0.2.4.4-alpha.
3145 o Minor bugfixes (parsing):
3146 - Stop accepting milliseconds (or other junk) at the end of
3147 descriptor publication times. Fixes bug 9286; bugfix on 0.0.2pre25.
3148 - Support two-number and three-number version numbers correctly, in
3149 case we change the Tor versioning system in the future. Fixes bug
3150 13661; bugfix on 0.0.8pre1.
3152 o Minor bugfixes (portability):
3153 - Fix the ioctl()-based network interface lookup code so that it
3154 will work on systems that have variable-length struct ifreq, for
3156 - Use the correct datatype in the SipHash-2-4 function to prevent
3157 compilers from assuming any sort of alignment. Fixes bug 15436;
3158 bugfix on 0.2.5.3-alpha.
3160 o Minor bugfixes (preventative security, C safety):
3161 - When reading a hexadecimal, base-32, or base-64 encoded value from
3162 a string, always overwrite the whole output buffer. This prevents
3163 some bugs where we would look at (but fortunately, not reveal)
3164 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
3166 - Clear all memory targetted by tor_addr_{to,from}_sockaddr(), not
3167 just the part that's used. This makes it harder for data leak bugs
3168 to occur in the event of other programming failures. Resolves
3171 o Minor bugfixes (relay):
3172 - When generating our family list, remove spaces from around the
3173 entries. Fixes bug 12728; bugfix on 0.2.1.7-alpha.
3174 - If our previous bandwidth estimate was 0 bytes, allow publishing a
3175 new relay descriptor immediately. Fixes bug 13000; bugfix
3178 o Minor bugfixes (shutdown):
3179 - When shutting down, always call event_del() on lingering read or
3180 write events before freeing them. Otherwise, we risk double-frees
3181 or read-after-frees in event_base_free(). Fixes bug 12985; bugfix
3184 o Minor bugfixes (small memory leaks):
3185 - Avoid leaking memory when using IPv6 virtual address mappings.
3186 Fixes bug 14123; bugfix on 0.2.4.7-alpha. Patch by Tom van
3189 o Minor bugfixes (statistics):
3190 - Increase period over which bandwidth observations are aggregated
3191 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
3193 o Minor bugfixes (systemd support):
3194 - Run correctly under systemd with the RunAsDaemon option set. Fixes
3195 part of bug 14141; bugfix on 0.2.5.7-rc. Patch from Tomasz Torcz.
3196 - Inform the systemd supervisor about more changes in the Tor
3197 process status. Implements part of ticket 14141. Patch from
3200 o Minor bugfixes (testing networks):
3201 - Fix TestingDirAuthVoteGuard to properly give out Guard flags in a
3202 testing network. Fixes bug 13064; bugfix on 0.2.5.2-alpha.
3203 - Stop using the default authorities in networks which provide both
3204 AlternateDirAuthority and AlternateBridgeAuthority. Partially
3205 fixes bug 13163; bugfix on 0.2.0.13-alpha.
3207 o Minor bugfixes (testing networks, fast startup):
3208 - Allow Tor to build circuits using a consensus with no exits. If
3209 the consensus has no exits (typical of a bootstrapping test
3210 network), allow Tor to build circuits once enough descriptors have
3211 been downloaded. This assists in bootstrapping a testing Tor
3212 network. Fixes bug 13718; bugfix on 0.2.4.10-alpha. Patch
3214 - When V3AuthVotingInterval is low, give a lower If-Modified-Since
3215 header to directory servers. This allows us to obtain consensuses
3216 promptly when the consensus interval is very short. This assists
3217 in bootstrapping a testing Tor network. Fixes parts of bugs 13718
3218 and 13963; bugfix on 0.2.0.3-alpha. Patch by "teor".
3219 - Stop assuming that private addresses are local when checking
3220 reachability in a TestingTorNetwork. Instead, when testing, assume
3221 all OR connections are remote. (This is necessary due to many test
3222 scenarios running all relays on localhost.) This assists in
3223 bootstrapping a testing Tor network. Fixes bug 13924; bugfix on
3224 0.1.0.1-rc. Patch by "teor".
3225 - Avoid building exit circuits from a consensus with no exits. Now
3226 thanks to our fix for 13718, we accept a no-exit network as not
3227 wholly lost, but we need to remember not to try to build exit
3228 circuits on it. Closes ticket 13814; patch by "teor".
3229 - Stop requiring exits to have non-zero bandwithcapacity in a
3230 TestingTorNetwork. Instead, when TestingMinExitFlagThreshold is 0,
3231 ignore exit bandwidthcapacity. This assists in bootstrapping a
3232 testing Tor network. Fixes parts of bugs 13718 and 13839; bugfix
3233 on 0.2.0.3-alpha. Patch by "teor".
3234 - Add "internal" to some bootstrap statuses when no exits are
3235 available. If the consensus does not contain Exits, Tor will only
3236 build internal circuits. In this case, relevant statuses will
3237 contain the word "internal" as indicated in the Tor control-
3238 spec.txt. When bootstrap completes, Tor will be ready to build
3239 internal circuits. If a future consensus contains Exits, exit
3240 circuits may become available. Fixes part of bug 13718; bugfix on
3241 0.2.4.10-alpha. Patch by "teor".
3242 - Decrease minimum consensus interval to 10 seconds when
3243 TestingTorNetwork is set, or 5 seconds for the first consensus.
3244 Fix assumptions throughout the code that assume larger intervals.
3245 Fixes bugs 13718 and 13823; bugfix on 0.2.0.3-alpha. Patch
3247 - Avoid excluding guards from path building in minimal test
3248 networks, when we're in a test network and excluding guards would
3249 exclude all relays. This typically occurs in incredibly small tor
3250 networks, and those using "TestingAuthVoteGuard *". Fixes part of
3251 bug 13718; bugfix on 0.1.1.11-alpha. Patch by "teor".
3253 o Minor bugfixes (testing):
3254 - Avoid a side-effect in a tor_assert() in the unit tests. Fixes bug
3255 15188; bugfix on 0.1.2.3-alpha. Patch from Tom van der Woerdt.
3256 - Stop spawn test failures due to a race condition between the
3257 SIGCHLD handler updating the process status, and the test reading
3258 it. Fixes bug 13291; bugfix on 0.2.3.3-alpha.
3259 - Avoid passing an extra backslash when creating a temporary
3260 directory for running the unit tests on Windows. Fixes bug 12392;
3261 bugfix on 0.2.2.25-alpha. Patch from Gisle Vanem.
3263 o Minor bugfixes (TLS):
3264 - Check more thoroughly throughout the TLS code for possible
3265 unlogged TLS errors. Possible diagnostic or fix for bug 13319.
3267 o Minor bugfixes (transparent proxy):
3268 - Use getsockname, not getsockopt, to retrieve the address for a
3269 TPROXY-redirected connection. Fixes bug 13796; bugfix
3272 o Minor bugfixes (windows):
3273 - Remove code to special-case handling of NTE_BAD_KEYSET when
3274 acquiring windows CryptoAPI context. This error can't actually
3275 occur for the parameters we're providing. Fixes bug 10816; bugfix
3278 o Minor bugfixes (zlib):
3279 - Avoid truncating a zlib stream when trying to finalize it with an
3280 empty output buffer. Fixes bug 11824; bugfix on 0.1.1.23.
3282 o Code simplification and refactoring:
3283 - Change the entry_is_live() function to take named bitfield
3284 elements instead of an unnamed list of booleans. Closes
3286 - Refactor and unit-test entry_is_time_to_retry() in entrynodes.c.
3287 Resolves ticket 12205.
3288 - Use calloc and reallocarray functions instead of multiply-
3289 then-malloc. This makes it less likely for us to fall victim to an
3290 integer overflow attack when allocating. Resolves ticket 12855.
3291 - Use the standard macro name SIZE_MAX, instead of our
3293 - Document usage of the NO_DIRINFO and ALL_DIRINFO flags clearly in
3294 functions which take them as arguments. Replace 0 with NO_DIRINFO
3295 in a function call for clarity. Seeks to prevent future issues
3297 - Avoid 4 null pointer errors under clang static analysis by using
3298 tor_assert() to prove that the pointers aren't null. Fixes
3300 - Rework the API of policies_parse_exit_policy() to use a bitmask to
3301 represent parsing options, instead of a confusing mess of
3302 booleans. Resolves ticket 8197.
3303 - Introduce a helper function to parse ExitPolicy in
3304 or_options_t structure.
3305 - Move fields related to isolating and configuring client ports into
3306 a shared structure. Previously, they were duplicated across
3307 port_cfg_t, listener_connection_t, and edge_connection_t. Failure
3308 to copy them correctly had been the cause of at least one bug in
3309 the past. Closes ticket 8546.
3310 - Refactor the get_interface_addresses_raw() doom-function into
3311 multiple smaller and simpler subfunctions. Cover the resulting
3312 subfunctions with unit-tests. Fixes a significant portion of
3314 - Remove workaround in dirserv_thinks_router_is_hs_dir() that was
3315 only for version <= 0.2.2.24 which is now deprecated. Closes
3317 - Remove a test for a long-defunct broken version-one
3319 - Refactor main loop to extract the 'loop' part. This makes it
3320 easier to run Tor under Shadow. Closes ticket 15176.
3321 - Stop using can_complete_circuits as a global variable; access it
3322 with a function instead.
3323 - Avoid using operators directly as macro arguments: this lets us
3324 apply coccinelle transformations to our codebase more directly.
3325 Closes ticket 13172.
3326 - Combine the functions used to parse ClientTransportPlugin and
3327 ServerTransportPlugin into a single function. Closes ticket 6456.
3328 - Add inline functions and convenience macros for inspecting channel
3329 state. Refactor the code to use convenience macros instead of
3330 checking channel state directly. Fixes issue 7356.
3331 - Document all members of was_router_added_t and rename
3332 ROUTER_WAS_NOT_NEW to ROUTER_IS_ALREADY_KNOWN to make it less
3333 confusable with ROUTER_WAS_TOO_OLD. Fixes issue 13644.
3334 - In connection_exit_begin_conn(), use END_CIRC_REASON_TORPROTOCOL
3335 constant instead of hardcoded value. Fixes issue 13840.
3336 - Refactor our generic strmap and digestmap types into a single
3337 implementation, so that we can add a new digest256map
3341 - Add a doc/TUNING document with tips for handling large numbers of
3342 TCP connections when running busy Tor relay. Update the warning
3343 message to point to this file when running out of sockets
3344 operating system is allowing to use simultaneously. Resolves
3346 - Adding section on OpenBSD to our TUNING document. Thanks to mmcc
3347 for writing the OpenBSD-specific tips. Resolves ticket 13702.
3348 - Make the tor-resolve documentation match its help string and its
3349 options. Resolves part of ticket 14325.
3350 - Log a more useful error message from tor-resolve when failing to
3351 look up a hidden service address. Resolves part of ticket 14325.
3352 - Document the bridge-authority-only 'networkstatus-bridges' file.
3353 Closes ticket 13713; patch from "tom".
3354 - Fix typo in PredictedPortsRelevanceTime option description in
3355 manpage. Resolves issue 13707.
3356 - Stop suggesting that users specify relays by nickname: it isn't a
3357 good idea. Also, properly cross-reference how to specify relays in
3358 all parts of manual documenting options that take a list of
3359 relays. Closes ticket 13381.
3360 - Clarify the HiddenServiceDir option description in manpage to make
3361 it clear that relative paths are taken with respect to the current
3362 working directory. Also clarify that this behavior is not
3363 guaranteed to remain indefinitely. Fixes issue 13913.
3365 o Distribution (systemd):
3366 - systemd unit file: only allow tor to write to /var/lib/tor and
3367 /var/log/tor. The rest of the filesystem is accessible for reading
3368 only. Patch by intrigeri; resolves ticket 12751.
3369 - systemd unit file: ensure that the process and all its children
3370 can never gain new privileges. Patch by intrigeri; resolves
3372 - systemd unit file: set up /var/run/tor as writable for the Tor
3373 service. Patch by intrigeri; resolves ticket 13196.
3375 o Downgraded warnings:
3376 - Don't warn when we've attempted to contact a relay using the wrong
3377 ntor onion key. Closes ticket 9635.
3380 - Remove some lingering dead code that once supported mempools.
3381 Mempools were disabled by default in 0.2.5, and removed entirely
3382 in 0.2.6.3-alpha. Closes more of ticket 14848; patch
3385 o Removed features (directory authorities):
3386 - Remove code that prevented authorities from listing Tor relays
3387 affected by CVE-2011-2769 as guards. These relays are already
3388 rejected altogether due to the minimum version requirement of
3389 0.2.3.16-alpha. Closes ticket 13152.
3390 - The "AuthDirRejectUnlisted" option no longer has any effect, as
3391 the fingerprints file (approved-routers) has been deprecated.
3392 - Directory authorities do not support being Naming dirauths anymore.
3393 The "NamingAuthoritativeDir" config option is now obsolete.
3394 - Directory authorities do not support giving out the BadDirectory
3396 - Directory authorities no longer advertise or support consensus
3397 methods 1 through 12 inclusive. These consensus methods were
3398 obsolete and/or insecure: maintaining the ability to support them
3399 served no good purpose. Implements part of proposal 215; closes
3403 - To avoid confusion with the "ExitRelay" option, "ExitNode" is no
3404 longer silently accepted as an alias for "ExitNodes".
3405 - The --enable-mempool and --enable-buf-freelists options, which
3406 were originally created to work around bad malloc implementations,
3407 no longer exist. They were off-by-default in 0.2.5. Closes
3409 - We no longer remind the user about configuration options that have
3410 been obsolete since 0.2.3.x or earlier. Patch by Adrien Bak.
3411 - Remove our old, non-weighted bandwidth-based node selection code.
3412 Previously, we used it as a fallback when we couldn't perform
3413 weighted bandwidth-based node selection. But that would only
3414 happen in the cases where we had no consensus, or when we had a
3415 consensus generated by buggy or ancient directory authorities. In
3416 either case, it's better to use the more modern, better maintained
3417 algorithm, with reasonable defaults for the weights. Closes
3419 - Remove the --disable-curve25519 configure option. Relays and
3420 clients now are required to support curve25519 and the
3422 - The old "StrictEntryNodes" and "StrictExitNodes" options, which
3423 used to be deprecated synonyms for "StrictNodes", are now marked
3424 obsolete. Resolves ticket 12226.
3425 - Clients don't understand the BadDirectory flag in the consensus
3426 anymore, and ignore it.
3428 o Removed platform support:
3429 - We no longer include special code to build on Windows CE; as far
3430 as we know, nobody has used Tor on Windows CE in a very long time.
3431 Closes ticket 11446.
3433 o Testing (test-network.sh):
3434 - Stop using "echo -n", as some shells' built-in echo doesn't
3435 support "-n". Instead, use "/bin/echo -n". Partially fixes
3437 - Stop an apparent test-network hang when used with make -j2. Fixes
3439 - Add a --delay option to test-network.sh, which configures the
3440 delay before the chutney network tests for data transmission.
3441 Partially implements ticket 13161.
3444 - Test that tor does not fail when key files are zero-length. Check
3445 that tor generates new keys, and overwrites the empty key files.
3446 - Test that tor generates new keys when keys are missing
3447 (existing behavior).
3448 - Test that tor does not overwrite key files that already contain
3449 data (existing behavior). Tests bug 13111. Patch by "teor".
3450 - New "make test-stem" target to run stem integration tests.
3451 Requires that the "STEM_SOURCE_DIR" environment variable be set.
3452 Closes ticket 14107.
3453 - Make the test_cmdline_args.py script work correctly on Windows.
3454 Patch from Gisle Vanem.
3455 - Move the slower unit tests into a new "./src/test/test-slow"
3456 binary that can be run independently of the other tests. Closes
3458 - New tests for many parts of channel, relay, and circuitmux
3459 functionality. Code by Andrea; part of 9262.
3460 - New tests for parse_transport_line(). Part of ticket 6456.
3461 - In the unit tests, use chgrp() to change the group of the unit
3462 test temporary directory to the current user, so that the sticky
3463 bit doesn't interfere with tests that check directory groups.
3465 - Add unit tests for resolve_my_addr(). Part of ticket 12376; patch
3467 - Refactor the function that chooses guard nodes so that it can more
3468 easily be tested; write some tests for it.
3469 - Fix and re-enable the fgets_eagain unit test. Fixes bug 12503;
3470 bugfix on 0.2.3.1-alpha. Patch from "cypherpunks."
3471 - Create unit tests for format_time_interval(). With bug 13393.
3472 - Add unit tests for tor_timegm signed overflow, tor_timegm and
3473 parse_rfc1123_time validity checks, correct_tm year clamping. Unit
3474 tests (visible) fixes in bug 13476.
3475 - Add a "coverage-html" make target to generate HTML-visualized
3476 coverage results when building with --enable-coverage. (Requires
3477 lcov.) Patch from Kevin Murray.
3478 - Enable the backtrace handler (where supported) when running the
3480 - Revise all unit tests that used the legacy test_* macros to
3481 instead use the recommended tt_* macros. This patch was generated
3482 with coccinelle, to avoid manual errors. Closes ticket 13119.
3484 Changes in version 0.2.5.11 - 2015-03-17
3485 Tor 0.2.5.11 is the second stable release in the 0.2.5 series.
3487 It backports several bugfixes from the 0.2.6 branch, including a
3488 couple of medium-level security fixes for relays and exit nodes.
3489 It also updates the list of directory authorities.
3491 o Directory authority changes:
3492 - Remove turtles as a directory authority.
3493 - Add longclaw as a new (v3) directory authority. This implements
3494 ticket 13296. This keeps the directory authority count at 9.
3495 - The directory authority Faravahar has a new IP address. This
3496 closes ticket 14487.
3498 o Major bugfixes (crash, OSX, security):
3499 - Fix a remote denial-of-service opportunity caused by a bug in
3500 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
3503 o Major bugfixes (relay, stability, possible security):
3504 - Fix a bug that could lead to a relay crashing with an assertion
3505 failure if a buffer of exactly the wrong layout was passed to
3506 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
3507 0.2.0.10-alpha. Patch from 'cypherpunks'.
3508 - Do not assert if the 'data' pointer on a buffer is advanced to the
3509 very end of the buffer; log a BUG message instead. Only assert if
3510 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
3512 o Major bugfixes (exit node stability):
3513 - Fix an assertion failure that could occur under high DNS load.
3514 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
3515 diagnosed and fixed by "cypherpunks".
3517 o Major bugfixes (Linux seccomp2 sandbox):
3518 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
3519 crash during attempts to call wait4. Fixes bug 15088; bugfix on
3520 0.2.5.1-alpha. Patch from "sanic".
3522 o Minor features (controller):
3523 - New "GETINFO bw-event-cache" to get information about recent
3524 bandwidth events. Closes ticket 14128. Useful for controllers to
3525 get recent bandwidth history after the fix for ticket 13988.
3527 o Minor features (geoip):
3528 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
3529 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
3532 o Minor bugfixes (client, automapping):
3533 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
3534 no value follows the option. Fixes bug 14142; bugfix on
3535 0.2.4.7-alpha. Patch by "teor".
3536 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
3537 14195; bugfix on 0.1.0.1-rc.
3539 o Minor bugfixes (compilation):
3540 - Build without warnings with the stock OpenSSL srtp.h header, which
3541 has a duplicate declaration of SSL_get_selected_srtp_profile().
3542 Fixes bug 14220; this is OpenSSL's bug, not ours.
3544 o Minor bugfixes (directory authority):
3545 - Allow directory authorities to fetch more data from one another if
3546 they find themselves missing lots of votes. Previously, they had
3547 been bumping against the 10 MB queued data limit. Fixes bug 14261;
3548 bugfix on 0.1.2.5-alpha.
3549 - Enlarge the buffer to read bwauth generated files to avoid an
3550 issue when parsing the file in dirserv_read_measured_bandwidths().
3551 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
3553 o Minor bugfixes (statistics):
3554 - Increase period over which bandwidth observations are aggregated
3555 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
3557 o Minor bugfixes (preventative security, C safety):
3558 - When reading a hexadecimal, base-32, or base-64 encoded value from
3559 a string, always overwrite the whole output buffer. This prevents
3560 some bugs where we would look at (but fortunately, not reveal)
3561 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
3565 Changes in version 0.2.4.26 - 2015-03-17
3566 Tor 0.2.4.26 includes an updated list of directory authorities. It
3567 also backports a couple of stability and security bugfixes from 0.2.5
3570 o Directory authority changes:
3571 - Remove turtles as a directory authority.
3572 - Add longclaw as a new (v3) directory authority. This implements
3573 ticket 13296. This keeps the directory authority count at 9.
3574 - The directory authority Faravahar has a new IP address. This
3575 closes ticket 14487.
3577 o Major bugfixes (exit node stability, also in 0.2.6.3-alpha):
3578 - Fix an assertion failure that could occur under high DNS load.
3579 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
3580 diagnosed and fixed by "cypherpunks".
3582 o Major bugfixes (relay, stability, possible security, also in 0.2.6.4-rc):
3583 - Fix a bug that could lead to a relay crashing with an assertion
3584 failure if a buffer of exactly the wrong layout was passed to
3585 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
3586 0.2.0.10-alpha. Patch from 'cypherpunks'.
3587 - Do not assert if the 'data' pointer on a buffer is advanced to the
3588 very end of the buffer; log a BUG message instead. Only assert if
3589 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
3591 o Minor features (geoip):
3592 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
3593 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
3596 Changes in version 0.2.5.10 - 2014-10-24
3597 Tor 0.2.5.10 is the first stable release in the 0.2.5 series.
3599 It adds several new security features, including improved
3600 denial-of-service resistance for relays, new compiler hardening
3601 options, and a system-call sandbox for hardened installations on Linux
3602 (requires seccomp2). The controller protocol has several new features,
3603 resolving IPv6 addresses should work better than before, and relays
3604 should be a little more CPU-efficient. We've added support for more
3605 OpenBSD and FreeBSD transparent proxy types. We've improved the build
3606 system and testing infrastructure to allow unit testing of more parts
3607 of the Tor codebase. Finally, we've addressed several nagging pluggable
3608 transport usability issues, and included numerous other small bugfixes
3609 and features mentioned below.
3611 This release marks end-of-life for Tor 0.2.3.x; those Tor versions
3612 have accumulated many known flaws; everyone should upgrade.
3614 o Major features (security):
3615 - The ntor handshake is now on-by-default, no matter what the
3616 directory authorities recommend. Implements ticket 8561.
3617 - Make the "tor-gencert" tool used by directory authority operators
3618 create 2048-bit signing keys by default (rather than 1024-bit, since
3619 1024-bit is uncomfortably small these days). Addresses ticket 10324.
3620 - Warn about attempts to run hidden services and relays in the same
3621 process: that's probably not a good idea. Closes ticket 12908.
3622 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
3623 today support TLS 1.0 or later, so we can safely turn off support
3624 for this old (and insecure) protocol. Fixes bug 13426.
3626 o Major features (relay security, DoS-resistance):
3627 - When deciding whether we have run out of memory and we need to
3628 close circuits, also consider memory allocated in buffers for
3629 streams attached to each circuit.
3631 This change, which extends an anti-DoS feature introduced in
3632 0.2.4.13-alpha and improved in 0.2.4.14-alpha, lets Tor exit relays
3633 better resist more memory-based DoS attacks than before. Since the
3634 MaxMemInCellQueues option now applies to all queues, it is renamed
3635 to MaxMemInQueues. This feature fixes bug 10169.
3636 - Avoid hash-flooding denial-of-service attacks by using the secure
3637 SipHash-2-4 hash function for our hashtables. Without this
3638 feature, an attacker could degrade performance of a targeted
3639 client or server by flooding their data structures with a large
3640 number of entries to be stored at the same hash table position,
3641 thereby slowing down the Tor instance. With this feature, hash
3642 table positions are derived from a randomized cryptographic key,
3643 and an attacker cannot predict which entries will collide. Closes
3645 - If you don't specify MaxMemInQueues yourself, Tor now tries to
3646 pick a good value based on your total system memory. Previously,
3647 the default was always 8 GB. You can still override the default by
3648 setting MaxMemInQueues yourself. Resolves ticket 11396.
3650 o Major features (bridges and pluggable transports):
3651 - Add support for passing arguments to managed pluggable transport
3652 proxies. Implements ticket 3594.
3653 - Bridges now track GeoIP information and the number of their users
3654 even when pluggable transports are in use, and report usage
3655 statistics in their extra-info descriptors. Resolves tickets 4773
3657 - Don't launch pluggable transport proxies if we don't have any
3658 bridges configured that would use them. Now we can list many
3659 pluggable transports, and Tor will dynamically start one when it
3660 hears a bridge address that needs it. Resolves ticket 5018.
3661 - The bridge directory authority now assigns status flags (Stable,
3662 Guard, etc) to bridges based on thresholds calculated over all
3663 Running bridges. Now bridgedb can finally make use of its features
3664 to e.g. include at least one Stable bridge in its answers. Fixes
3667 o Major features (controller):
3668 - Extend ORCONN controller event to include an "ID" parameter,
3669 and add four new controller event types CONN_BW, CIRC_BW,
3670 CELL_STATS, and TB_EMPTY that show connection and circuit usage.
3671 The new events are emitted in private Tor networks only, with the
3672 goal of being able to better track performance and load during
3673 full-network simulations. Implements proposal 218 and ticket 7359.
3675 o Major features (relay performance):
3676 - Speed up server-side lookups of rendezvous and introduction point
3677 circuits by using hashtables instead of linear searches. These
3678 functions previously accounted between 3 and 7% of CPU usage on
3679 some busy relays. Resolves ticket 9841.
3680 - Avoid wasting CPU when extending a circuit over a channel that is
3681 nearly out of circuit IDs. Previously, we would do a linear scan
3682 over possible circuit IDs before finding one or deciding that we
3683 had exhausted our possibilities. Now, we try at most 64 random
3684 circuit IDs before deciding that we probably won't succeed. Fixes
3685 a possible root cause of ticket 11553.
3687 o Major features (seccomp2 sandbox, Linux only):
3688 - Use the seccomp2 syscall filtering facility on Linux to limit
3689 which system calls Tor can invoke. This is an experimental,
3690 Linux-only feature to provide defense-in-depth against unknown
3691 attacks. To try turning it on, set "Sandbox 1" in your torrc
3692 file. Please be ready to report bugs. We hope to add support
3693 for better sandboxing in the future, including more fine-grained
3694 filters, better division of responsibility, and support for more
3695 platforms. This work has been done by Cristian-Matei Toader for
3696 Google Summer of Code. Resolves tickets 11351 and 11465.
3698 o Major features (testing networks):
3699 - Make testing Tor networks bootstrap better: lower directory fetch
3700 retry schedules and maximum interval without directory requests,
3701 and raise maximum download tries. Implements ticket 6752.
3702 - Add make target 'test-network' to run tests on a Chutney network.
3703 Implements ticket 8530.
3705 o Major features (other):
3706 - On some platforms (currently: recent OSX versions, glibc-based
3707 platforms that support the ELF format, and a few other
3708 Unix-like operating systems), Tor can now dump stack traces
3709 when a crash occurs or an assertion fails. By default, traces
3710 are dumped to stderr (if possible) and to any logs that are
3711 reporting errors. Implements ticket 9299.
3713 o Deprecated versions:
3714 - Tor 0.2.3.x has reached end-of-life; it has received no patches or
3715 attention for some while.
3717 o Major bugfixes (security, directory authorities):
3718 - Directory authorities now include a digest of each relay's
3719 identity key as a part of its microdescriptor.
3721 This is a workaround for bug 11743 (reported by "cypherpunks"),
3722 where Tor clients do not support receiving multiple
3723 microdescriptors with the same SHA256 digest in the same
3724 consensus. When clients receive a consensus like this, they only
3725 use one of the relays. Without this fix, a hostile relay could
3726 selectively disable some client use of target relays by
3727 constructing a router descriptor with a different identity and the
3728 same microdescriptor parameters and getting the authorities to
3729 list it in a microdescriptor consensus. This fix prevents an
3730 attacker from causing a microdescriptor collision, because the
3731 router's identity is not forgeable.
3733 o Major bugfixes (openssl bug workaround):
3734 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
3735 1.0.1j, built with the 'no-ssl3' configuration option. Fixes
3736 bug 13471. This is a workaround for an OpenSSL bug.
3738 o Major bugfixes (client):
3739 - Perform circuit cleanup operations even when circuit
3740 construction operations are disabled (because the network is
3741 disabled, or because there isn't enough directory information).
3742 Previously, when we were not building predictive circuits, we
3743 were not closing expired circuits either. Fixes bug 8387; bugfix on
3744 0.1.1.11-alpha. This bug became visible in 0.2.4.10-alpha when we
3745 became more strict about when we have "enough directory information
3748 o Major bugfixes (client, pluggable transports):
3749 - When managing pluggable transports, use OS notification facilities
3750 to learn if they have crashed, and don't attempt to kill any
3751 process that has already exited. Fixes bug 8746; bugfix
3754 o Major bugfixes (relay denial of service):
3755 - Instead of writing destroy cells directly to outgoing connection
3756 buffers, queue them and intersperse them with other outgoing cells.
3757 This can prevent a set of resource starvation conditions where too
3758 many pending destroy cells prevent data cells from actually getting
3759 delivered. Reported by "oftc_must_be_destroyed". Fixes bug 7912;
3760 bugfix on 0.2.0.1-alpha.
3762 o Major bugfixes (relay):
3763 - Avoid queuing or sending destroy cells for circuit ID zero when we
3764 fail to send a CREATE cell. Fixes bug 12848; bugfix on 0.0.8pre1.
3765 Found and fixed by "cypherpunks".
3766 - Fix ORPort reachability detection on relays running behind a
3767 proxy, by correctly updating the "local" mark on the controlling
3768 channel when changing the address of an or_connection_t after the
3769 handshake. Fixes bug 12160; bugfix on 0.2.4.4-alpha.
3770 - Use a direct dirport connection when uploading non-anonymous
3771 descriptors to the directory authorities. Previously, relays would
3772 incorrectly use tunnel connections under a fairly wide variety of
3773 circumstances. Fixes bug 11469; bugfix on 0.2.4.3-alpha.
3774 - When a circuit accidentally has the same circuit ID for its
3775 forward and reverse direction, correctly detect the direction of
3776 cells using that circuit. Previously, this bug made roughly one
3777 circuit in a million non-functional. Fixes bug 12195; this is a
3778 bugfix on every version of Tor.
3780 o Minor features (security):
3781 - New --enable-expensive-hardening option to enable security
3782 hardening options that consume nontrivial amounts of CPU and
3783 memory. Right now, this includes AddressSanitizer and UbSan, which
3784 are supported in newer versions of GCC and Clang. Closes ticket
3786 - Authorities now assign the Guard flag to the fastest 25% of the
3787 network (it used to be the fastest 50%). Also raise the consensus
3788 weight that guarantees the Guard flag from 250 to 2000. For the
3789 current network, this results in about 1100 guards, down from 2500.
3790 This step paves the way for moving the number of entry guards
3791 down to 1 (proposal 236) while still providing reasonable expected
3792 performance for most users. Implements ticket 12690.
3794 o Minor features (security, memory management):
3795 - Memory allocation tricks (mempools and buffer freelists) are now
3796 disabled by default. You can turn them back on with
3797 --enable-mempools and --enable-buf-freelists respectively. We're
3798 disabling these features because malloc performance is good enough
3799 on most platforms, and a similar feature in OpenSSL exacerbated
3800 exploitation of the Heartbleed attack. Resolves ticket 11476.
3802 o Minor features (bridge client):
3803 - Report a more useful failure message when we can't connect to a
3804 bridge because we don't have the right pluggable transport
3805 configured. Resolves ticket 9665. Patch from Fábio J. Bertinatto.
3807 o Minor features (bridge):
3808 - Add an ExtORPortCookieAuthFileGroupReadable option to make the
3809 cookie file for the ExtORPort g+r by default.
3811 o Minor features (bridges, pluggable transports):
3812 - Bridges now write the SHA1 digest of their identity key
3813 fingerprint (that is, a hash of a hash of their public key) to
3814 notice-level logs, and to a new hashed-fingerprint file. This
3815 information will help bridge operators look up their bridge in
3816 Globe and similar tools. Resolves ticket 10884.
3817 - Improve the message that Tor displays when running as a bridge
3818 using pluggable transports without an Extended ORPort listener.
3819 Also, log the message in the log file too. Resolves ticket 11043.
3820 - Add threshold cutoffs to the networkstatus document created by
3821 the Bridge Authority. Fixes bug 1117.
3822 - On Windows, spawn background processes using the CREATE_NO_WINDOW
3823 flag. Now Tor Browser Bundle 3.5 with pluggable transports enabled
3824 doesn't pop up a blank console window. (In Tor Browser Bundle 2.x,
3825 Vidalia set this option for us.) Implements ticket 10297.
3827 o Minor features (build):
3828 - The configure script has a --disable-seccomp option to turn off
3829 support for libseccomp on systems that have it, in case it (or
3830 Tor's use of it) is broken. Resolves ticket 11628.
3831 - Assume that a user using ./configure --host wants to cross-compile,
3832 and give an error if we cannot find a properly named
3833 tool-chain. Add a --disable-tool-name-check option to proceed
3834 nevertheless. Addresses ticket 9869. Patch by Benedikt Gollatz.
3835 - If we run ./configure and the compiler recognizes -fstack-protector
3836 but the linker rejects it, warn the user about a potentially missing
3837 libssp package. Addresses ticket 9948. Patch from Benedikt Gollatz.
3838 - Add support for `--library-versions` flag. Implements ticket 6384.
3839 - Return the "unexpected sendme" warnings to a warn severity, but make
3840 them rate limited, to help diagnose ticket 8093.
3841 - Detect a missing asciidoc, and warn the user about it, during
3842 configure rather than at build time. Fixes issue 6506. Patch from
3845 o Minor features (client):
3846 - Add a new option, PredictedPortsRelevanceTime, to control how long
3847 after having received a request to connect to a given port Tor
3848 will try to keep circuits ready in anticipation of future requests
3849 for that port. Patch from "unixninja92"; implements ticket 9176.
3851 o Minor features (config options and command line):
3852 - Add an --allow-missing-torrc commandline option that tells Tor to
3853 run even if the configuration file specified by -f is not available.
3854 Implements ticket 10060.
3855 - Add support for the TPROXY transparent proxying facility on Linux.
3856 See documentation for the new TransProxyType option for more
3857 details. Implementation by "thomo". Closes ticket 10582.
3859 o Minor features (config options):
3860 - Config (torrc) lines now handle fingerprints which are missing
3861 their initial '$'. Resolves ticket 4341; improvement over 0.0.9pre5.
3862 - Support a --dump-config option to print some or all of the
3863 configured options. Mainly useful for debugging the command-line
3864 option parsing code. Helps resolve ticket 4647.
3865 - Raise awareness of safer logging: notify user of potentially
3866 unsafe config options, like logging more verbosely than severity
3867 "notice" or setting SafeLogging to 0. Resolves ticket 5584.
3868 - Add a new configuration option TestingV3AuthVotingStartOffset
3869 that bootstraps a network faster by changing the timing for
3870 consensus votes. Addresses ticket 8532.
3871 - Add a new torrc option "ServerTransportOptions" that allows
3872 bridge operators to pass configuration parameters to their
3873 pluggable transports. Resolves ticket 8929.
3874 - The config (torrc) file now accepts bandwidth and space limits in
3875 bits as well as bytes. (Anywhere that you can say "2 Kilobytes",
3876 you can now say "16 kilobits", and so on.) Resolves ticket 9214.
3879 o Minor features (controller):
3880 - Make the entire exit policy available from the control port via
3881 GETINFO exit-policy/*. Implements enhancement 7952. Patch from
3883 - Because of the fix for ticket 11396, the real limit for memory
3884 usage may no longer match the configured MaxMemInQueues value. The
3885 real limit is now exposed via GETINFO limits/max-mem-in-queues.
3886 - Add a new "HS_DESC" controller event that reports activities
3887 related to hidden service descriptors. Resolves ticket 8510.
3888 - New "DROPGUARDS" controller command to forget all current entry
3889 guards. Not recommended for ordinary use, since replacing guards
3890 too frequently makes several attacks easier. Resolves ticket 9934;
3892 - Implement the TRANSPORT_LAUNCHED control port event that
3893 notifies controllers about new launched pluggable
3894 transports. Resolves ticket 5609.
3896 o Minor features (diagnostic):
3897 - When logging a warning because of bug 7164, additionally check the
3898 hash table for consistency (as proposed on ticket 11737). This may
3899 help diagnose bug 7164.
3900 - When we log a heartbeat, log how many one-hop circuits we have
3901 that are at least 30 minutes old, and log status information about
3902 a few of them. This is an attempt to track down bug 8387.
3903 - When encountering an unexpected CR while writing text to a file on
3904 Windows, log the name of the file. Should help diagnosing
3906 - Give more specific warnings when a client notices that an onion
3907 handshake has failed. Fixes ticket 9635.
3908 - Add significant new logging code to attempt to diagnose bug 12184,
3909 where relays seem to run out of available circuit IDs.
3910 - Improve the diagnostic log message for bug 8387 even further to
3911 try to improve our odds of figuring out why one-hop directory
3912 circuits sometimes do not get closed.
3913 - Add more log messages to diagnose bug 7164, which causes
3914 intermittent "microdesc_free() called but md was still referenced"
3915 warnings. We now include more information, to figure out why we
3916 might be cleaning a microdescriptor for being too old if it's
3917 still referenced by a live node_t object.
3918 - Log current accounting state (bytes sent and received + remaining
3919 time for the current accounting period) in the relay's heartbeat
3920 message. Implements ticket 5526; patch from Peter Retzlaff.
3922 o Minor features (geoip):
3923 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
3926 o Minor features (interface):
3927 - Generate a warning if any ports are listed in the SocksPolicy,
3928 DirPolicy, AuthDirReject, AuthDirInvalid, AuthDirBadDir, or
3929 AuthDirBadExit options. (These options only support address
3930 ranges.) Fixes part of ticket 11108.
3932 o Minor features (kernel API usage):
3933 - Use the SOCK_NONBLOCK socket type, if supported, to open nonblocking
3934 sockets in a single system call. Implements ticket 5129.
3936 o Minor features (log messages):
3937 - When ServerTransportPlugin is set on a bridge, Tor can write more
3938 useful statistics about bridge use in its extrainfo descriptors,
3939 but only if the Extended ORPort ("ExtORPort") is set too. Add a
3940 log message to inform the user in this case. Resolves ticket 9651.
3941 - When receiving a new controller connection, log the origin address.
3942 Resolves ticket 9698; patch from "sigpipe".
3943 - When logging OpenSSL engine status at startup, log the status of
3944 more engines. Fixes ticket 10043; patch from Joshua Datko.
3946 o Minor features (log verbosity):
3947 - Demote the message that we give when a flushing connection times
3948 out for too long from NOTICE to INFO. It was usually meaningless.
3949 Resolves ticket 5286.
3950 - Don't log so many notice-level bootstrapping messages at startup
3951 about downloading descriptors. Previously, we'd log a notice
3952 whenever we learned about more routers. Now, we only log a notice
3953 at every 5% of progress. Fixes bug 9963.
3954 - Warn less verbosely when receiving a malformed
3955 ESTABLISH_RENDEZVOUS cell. Fixes ticket 11279.
3957 o Minor features (performance):
3958 - If we're using the pure-C 32-bit curve25519_donna implementation
3959 of curve25519, build it with the -fomit-frame-pointer option to
3960 make it go faster on register-starved hosts. This improves our
3961 handshake performance by about 6% on i386 hosts without nacl.
3964 o Minor features (relay):
3965 - If a circuit timed out for at least 3 minutes, check if we have a
3966 new external IP address, and publish a new descriptor with the new
3967 IP address if it changed. Resolves ticket 2454.
3969 o Minor features (testing):
3970 - If Python is installed, "make check" now runs extra tests beyond
3971 the unit test scripts.
3972 - When bootstrapping a test network, sometimes very few relays get
3973 the Guard flag. Now a new option "TestingDirAuthVoteGuard" can
3974 specify a set of relays which should be voted Guard regardless of
3975 their uptime or bandwidth. Addresses ticket 9206.
3977 o Minor features (transparent proxy, *BSD):
3978 - Support FreeBSD's ipfw firewall interface for TransPort ports on
3979 FreeBSD. To enable it, set "TransProxyType ipfw". Resolves ticket
3980 10267; patch from "yurivict".
3981 - Support OpenBSD's divert-to rules with the pf firewall for
3982 transparent proxy ports. To enable it, set "TransProxyType
3983 pf-divert". This allows Tor to run a TransPort transparent proxy
3984 port on OpenBSD 4.4 or later without root privileges. See the
3985 pf.conf(5) manual page for information on configuring pf to use
3986 divert-to rules. Closes ticket 10896; patch from Dana Koch.
3988 o Minor bugfixes (bridge client):
3989 - Stop accepting bridge lines containing hostnames. Doing so would
3990 cause clients to perform DNS requests on the hostnames, which was
3991 not sensible behavior. Fixes bug 10801; bugfix on 0.2.0.1-alpha.
3993 o Minor bugfixes (bridges):
3994 - Avoid potential crashes or bad behavior when launching a
3995 server-side managed proxy with ORPort or ExtORPort temporarily
3996 disabled. Fixes bug 9650; bugfix on 0.2.3.16-alpha.
3997 - Fix a bug where the first connection works to a bridge that uses a
3998 pluggable transport with client-side parameters, but we don't send
3999 the client-side parameters on subsequent connections. (We don't
4000 use any pluggable transports with client-side parameters yet,
4001 but ScrambleSuit will soon become the first one.) Fixes bug 9162;
4002 bugfix on 0.2.0.3-alpha. Based on a patch from "rl1987".
4004 o Minor bugfixes (build, auxiliary programs):
4005 - Stop preprocessing the "torify" script with autoconf, since
4006 it no longer refers to LOCALSTATEDIR. Fixes bug 5505; patch
4008 - The tor-fw-helper program now follows the standard convention and
4009 exits with status code "0" on success. Fixes bug 9030; bugfix on
4010 0.2.3.1-alpha. Patch by Arlo Breault.
4011 - Corrected ./configure advice for what openssl dev package you should
4012 install on Debian. Fixes bug 9207; bugfix on 0.2.0.1-alpha.
4014 o Minor bugfixes (client):
4015 - Avoid "Tried to open a socket with DisableNetwork set" warnings
4016 when starting a client with bridges configured and DisableNetwork
4017 set. (Tor launcher starts Tor with DisableNetwork set the first
4018 time it runs.) Fixes bug 10405; bugfix on 0.2.3.9-alpha.
4019 - Improve the log message when we can't connect to a hidden service
4020 because all of the hidden service directory nodes hosting its
4021 descriptor are excluded. Improves on our fix for bug 10722, which
4022 was a bugfix on 0.2.0.10-alpha.
4023 - Raise a control port warning when we fail to connect to all of
4024 our bridges. Previously, we didn't inform the controller, and
4025 the bootstrap process would stall. Fixes bug 11069; bugfix on
4027 - Exit immediately when a process-owning controller exits.
4028 Previously, tor relays would wait for a little while after their
4029 controller exited, as if they had gotten an INT signal -- but this
4030 was problematic, since there was no feedback for the user. To do a
4031 clean shutdown, controllers should send an INT signal and give Tor
4032 a chance to clean up. Fixes bug 10449; bugfix on 0.2.2.28-beta.
4033 - Stop attempting to connect to bridges before our pluggable
4034 transports are configured (harmless but resulted in some erroneous
4035 log messages). Fixes bug 11156; bugfix on 0.2.3.2-alpha.
4036 - Fix connections to IPv6 addresses over SOCKS5. Previously, we were
4037 generating incorrect SOCKS5 responses, and confusing client
4038 applications. Fixes bug 10987; bugfix on 0.2.4.7-alpha.
4040 o Minor bugfixes (client, DNSPort):
4041 - When using DNSPort, try to respond to AAAA requests with AAAA
4042 answers. Previously, we hadn't looked at the request type when
4043 deciding which answer type to prefer. Fixes bug 10468; bugfix on
4045 - When receiving a DNS query for an unsupported record type, reply
4046 with no answer rather than with a NOTIMPL error. This behavior
4047 isn't correct either, but it will break fewer client programs, we
4048 hope. Fixes bug 10268; bugfix on 0.2.0.1-alpha. Original patch
4051 o Minor bugfixes (client, logging during bootstrap):
4052 - Only report the first fatal bootstrap error on a given OR
4053 connection. This stops us from telling the controller bogus error
4054 messages like "DONE". Fixes bug 10431; bugfix on 0.2.1.1-alpha.
4055 - Avoid generating spurious warnings when starting with
4056 DisableNetwork enabled. Fixes bug 11200 and bug 10405; bugfix on
4059 o Minor bugfixes (closing OR connections):
4060 - If write_to_buf() in connection_write_to_buf_impl_() ever fails,
4061 check if it's an or_connection_t and correctly call
4062 connection_or_close_for_error() rather than
4063 connection_mark_for_close() directly. Fixes bug 11304; bugfix on
4065 - When closing all connections on setting DisableNetwork to 1, use
4066 connection_or_close_normally() rather than closing OR connections
4067 out from under the channel layer. Fixes bug 11306; bugfix on
4070 o Minor bugfixes (code correctness):
4071 - Previously we used two temporary files when writing descriptors to
4072 disk; now we only use one. Fixes bug 1376.
4073 - Remove an erroneous (but impossible and thus harmless) pointer
4074 comparison that would have allowed compilers to skip a bounds
4075 check in channeltls.c. Fixes bugs 10313 and 9980; bugfix on
4076 0.2.0.10-alpha. Noticed by Jared L Wong and David Fifield.
4077 - Fix an always-true assertion in pluggable transports code so it
4078 actually checks what it was trying to check. Fixes bug 10046;
4079 bugfix on 0.2.3.9-alpha. Found by "dcb".
4081 o Minor bugfixes (command line):
4082 - Use a single command-line parser for parsing torrc options on the
4083 command line and for finding special command-line options to avoid
4084 inconsistent behavior for torrc option arguments that have the same
4085 names as command-line options. Fixes bugs 4647 and 9578; bugfix on
4087 - No longer allow 'tor --hash-password' with no arguments. Fixes bug
4088 9573; bugfix on 0.0.9pre5.
4090 o Minor bugfixes (compilation):
4091 - Compile correctly with builds and forks of OpenSSL (such as
4092 LibreSSL) that disable compression. Fixes bug 12602; bugfix on
4093 0.2.1.1-alpha. Patch from "dhill".
4094 - Restore the ability to compile Tor with V2_HANDSHAKE_SERVER
4095 turned off (that is, without support for v2 link handshakes). Fixes
4096 bug 4677; bugfix on 0.2.3.2-alpha. Patch from "piet".
4097 - In routerlist_assert_ok(), don't take the address of a
4098 routerinfo's cache_info member unless that routerinfo is non-NULL.
4099 Fixes bug 13096; bugfix on 0.1.1.9-alpha. Patch by "teor".
4100 - Fix a large number of false positive warnings from the clang
4101 analyzer static analysis tool. This should make real warnings
4102 easier for clang analyzer to find. Patch from "teor". Closes
4104 - Resolve GCC complaints on OpenBSD about discarding constness in
4105 TO_{ORIGIN,OR}_CIRCUIT functions. Fixes part of bug 11633; bugfix
4106 on 0.1.1.23. Patch from Dana Koch.
4107 - Resolve clang complaints on OpenBSD with -Wshorten-64-to-32 due to
4108 treatment of long and time_t as comparable types. Fixes part of
4109 bug 11633. Patch from Dana Koch.
4110 - When deciding whether to build the 64-bit curve25519
4111 implementation, detect platforms where we can compile 128-bit
4112 arithmetic but cannot link it. Fixes bug 11729; bugfix on
4113 0.2.4.8-alpha. Patch from "conradev".
4114 - Fix compilation when DNS_CACHE_DEBUG is enabled. Fixes bug 11761;
4115 bugfix on 0.2.3.13-alpha. Found by "cypherpunks".
4116 - Fix compilation with dmalloc. Fixes bug 11605; bugfix
4118 - Build and run correctly on systems like OpenBSD-current that have
4119 patched OpenSSL to remove get_cipher_by_char and/or its
4120 implementations. Fixes issue 13325.
4122 o Minor bugfixes (controller and command-line):
4123 - If changing a config option via "setconf" fails in a recoverable
4124 way, we used to nonetheless write our new control ports to the
4125 file described by the "ControlPortWriteToFile" option. Now we only
4126 write out that file if we successfully switch to the new config
4127 option. Fixes bug 5605; bugfix on 0.2.2.26-beta. Patch from "Ryman".
4129 o Minor bugfixes (directory server):
4130 - No longer accept malformed http headers when parsing urls from
4131 headers. Now we reply with Bad Request ("400"). Fixes bug 2767;
4132 bugfix on 0.0.6pre1.
4133 - When sending a compressed set of descriptors or microdescriptors,
4134 make sure to finalize the zlib stream. Previously, we would write
4135 all the compressed data, but if the last descriptor we wanted to
4136 send was missing or too old, we would not mark the stream as
4137 finished. This caused problems for decompression tools. Fixes bug
4138 11648; bugfix on 0.1.1.23.
4140 o Minor bugfixes (hidden service):
4141 - Only retry attempts to connect to a chosen rendezvous point 8
4142 times, not 30. Fixes bug 4241; bugfix on 0.1.0.1-rc.
4144 o Minor bugfixes (interface):
4145 - Reject relative control socket paths and emit a warning. Previously,
4146 single-component control socket paths would be rejected, but Tor
4147 would not log why it could not validate the config. Fixes bug 9258;
4148 bugfix on 0.2.3.16-alpha.
4150 o Minor bugfixes (log messages):
4151 - Fix a bug where clients using bridges would report themselves
4152 as 50% bootstrapped even without a live consensus document.
4153 Fixes bug 9922; bugfix on 0.2.1.1-alpha.
4154 - Suppress a warning where, if there's only one directory authority
4155 in the network, we would complain that votes and signatures cannot
4156 be uploaded to other directory authorities. Fixes bug 10842;
4157 bugfix on 0.2.2.26-beta.
4158 - Report bootstrapping progress correctly when we're downloading
4159 microdescriptors. We had updated our "do we have enough microdescs
4160 to begin building circuits?" logic most recently in 0.2.4.10-alpha
4161 (see bug 5956), but we left the bootstrap status event logic at
4162 "how far through getting 1/4 of them are we?" Fixes bug 9958;
4163 bugfix on 0.2.2.36, which is where they diverged (see bug 5343).
4165 o Minor bugfixes (logging):
4166 - Downgrade "Unexpected onionskin length after decryption" warning
4167 to a protocol-warn, since there's nothing relay operators can do
4168 about a client that sends them a malformed create cell. Resolves
4169 bug 12996; bugfix on 0.0.6rc1.
4170 - Log more specific warnings when we get an ESTABLISH_RENDEZVOUS
4171 cell on a cannibalized or non-OR circuit. Resolves ticket 12997.
4172 - When logging information about an EXTEND2 or EXTENDED2 cell, log
4173 their names correctly. Fixes part of bug 12700; bugfix
4175 - When logging information about a relay cell whose command we don't
4176 recognize, log its command as an integer. Fixes part of bug 12700;
4177 bugfix on 0.2.1.10-alpha.
4178 - Escape all strings from the directory connection before logging
4179 them. Fixes bug 13071; bugfix on 0.1.1.15. Patch from "teor".
4180 - Squelch a spurious LD_BUG message "No origin circuit for
4181 successful SOCKS stream" in certain hidden service failure cases;
4183 - Downgrade the severity of the 'unexpected sendme cell from client'
4184 from 'warn' to 'protocol warning'. Closes ticket 8093.
4186 o Minor bugfixes (misc code correctness):
4187 - In munge_extrainfo_into_routerinfo(), check the return value of
4188 memchr(). This would have been a serious issue if we ever passed
4189 it a non-extrainfo. Fixes bug 8791; bugfix on 0.2.0.6-alpha. Patch
4191 - On the chance that somebody manages to build Tor on a
4192 platform where time_t is unsigned, correct the way that
4193 microdesc_add_to_cache() handles negative time arguments.
4194 Fixes bug 8042; bugfix on 0.2.3.1-alpha.
4195 - Fix various instances of undefined behavior in channeltls.c,
4196 tor_memmem(), and eventdns.c that would cause us to construct
4197 pointers to memory outside an allocated object. (These invalid
4198 pointers were not accessed, but C does not even allow them to
4199 exist.) Fixes bug 10363; bugfixes on 0.1.1.1-alpha, 0.1.2.1-alpha,
4200 0.2.0.10-alpha, and 0.2.3.6-alpha. Reported by "bobnomnom".
4201 - Use the AddressSanitizer and Ubsan sanitizers (in clang-3.4) to
4202 fix some miscellaneous errors in our tests and codebase. Fixes bug
4203 11232. Bugfixes on versions back as far as 0.2.1.11-alpha.
4204 - Always check return values for unlink, munmap, UnmapViewOfFile;
4205 check strftime return values more often. In some cases all we can
4206 do is report a warning, but this may help prevent deeper bugs from
4207 going unnoticed. Closes ticket 8787; bugfixes on many, many tor
4209 - Fix numerous warnings from the clang "scan-build" static analyzer.
4210 Some of these are programming style issues; some of them are false
4211 positives that indicated awkward code; some are undefined behavior
4212 cases related to constructing (but not using) invalid pointers;
4213 some are assumptions about API behavior; some are (harmlessly)
4214 logging sizeof(ptr) bytes from a token when sizeof(*ptr) would be
4215 correct; and one or two are genuine bugs that weren't reachable
4216 from the rest of the program. Fixes bug 8793; bugfixes on many,
4219 o Minor bugfixes (node selection):
4220 - If ExcludeNodes is set, consider non-excluded hidden service
4221 directory servers before excluded ones. Do not consider excluded
4222 hidden service directory servers at all if StrictNodes is
4223 set. (Previously, we would sometimes decide to connect to those
4224 servers, and then realize before we initiated a connection that
4225 we had excluded them.) Fixes bug 10722; bugfix on 0.2.0.10-alpha.
4227 - If we set the ExitNodes option but it doesn't include any nodes
4228 that have the Exit flag, we would choose not to bootstrap. Now we
4229 bootstrap so long as ExitNodes includes nodes which can exit to
4230 some port. Fixes bug 10543; bugfix on 0.2.4.10-alpha.
4232 o Minor bugfixes (performance):
4233 - Avoid a bug where every successful connection made us recompute
4234 the flag telling us whether we have sufficient information to
4235 build circuits. Previously, we would forget our cached value
4236 whenever we successfully opened a channel (or marked a router as
4237 running or not running for any other reason), regardless of
4238 whether we had previously believed the router to be running. This
4239 forced us to run an expensive update operation far too often.
4240 Fixes bug 12170; bugfix on 0.1.2.1-alpha.
4241 - Avoid using tor_memeq() for checking relay cell integrity. This
4242 removes a possible performance bottleneck. Fixes part of bug
4243 12169; bugfix on 0.2.1.31.
4245 o Minor bugfixes (platform-specific):
4246 - When dumping a malformed directory object to disk, save it in
4247 binary mode on Windows, not text mode. Fixes bug 11342; bugfix on
4249 - Don't report failures from make_socket_reuseable() on incoming
4250 sockets on OSX: this can happen when incoming connections close
4251 early. Fixes bug 10081.
4253 o Minor bugfixes (pluggable transports):
4254 - Avoid another 60-second delay when starting Tor in a pluggable-
4255 transport-using configuration when we already have cached
4256 descriptors for our bridges. Fixes bug 11965; bugfix
4259 o Minor bugfixes (protocol correctness):
4260 - When receiving a VERSIONS cell with an odd number of bytes, close
4261 the connection immediately since the cell is malformed. Fixes bug
4262 10365; bugfix on 0.2.0.10-alpha. Spotted by "bobnomnom"; fix by
4265 o Minor bugfixes (relay, other):
4266 - We now drop CREATE cells for already-existent circuit IDs and for
4267 zero-valued circuit IDs, regardless of other factors that might
4268 otherwise have called for DESTROY cells. Fixes bug 12191; bugfix
4270 - When rejecting DATA cells for stream_id zero, still count them
4271 against the circuit's deliver window so that we don't fail to send
4272 a SENDME. Fixes bug 11246; bugfix on 0.2.4.10-alpha.
4274 o Minor bugfixes (relay, threading):
4275 - Check return code on spawn_func() in cpuworker code, so that we
4276 don't think we've spawned a nonworking cpuworker and write junk to
4277 it forever. Fix related to bug 4345; bugfix on all released Tor
4278 versions. Found by "skruffy".
4279 - Use a pthread_attr to make sure that spawn_func() cannot return an
4280 error while at the same time launching a thread. Fix related to
4281 bug 4345; bugfix on all released Tor versions. Reported
4284 o Minor bugfixes (relays and bridges):
4285 - Avoid crashing on a malformed resolv.conf file when running a
4286 relay using Libevent 1. Fixes bug 8788; bugfix on 0.1.1.23.
4287 - Non-exit relays no longer launch mock DNS requests to check for
4288 DNS hijacking. This has been unnecessary since 0.2.1.7-alpha, when
4289 non-exit relays stopped servicing DNS requests. Fixes bug 965;
4290 bugfix on 0.2.1.7-alpha. Patch from Matt Pagan.
4291 - Bridges now report complete directory request statistics. Related
4292 to bug 5824; bugfix on 0.2.2.1-alpha.
4293 - Bridges now never collect statistics that were designed for
4294 relays. Fixes bug 5824; bugfix on 0.2.3.8-alpha.
4296 o Minor bugfixes (testing):
4297 - Fix all valgrind warnings produced by the unit tests. There were
4298 over a thousand memory leak warnings previously, mostly produced
4299 by forgetting to free things in the unit test code. Fixes bug
4300 11618, bugfixes on many versions of Tor.
4302 o Minor bugfixes (tor-fw-helper):
4303 - Give a correct log message when tor-fw-helper fails to launch.
4304 (Previously, we would say something like "tor-fw-helper sent us a
4305 string we could not parse".) Fixes bug 9781; bugfix
4308 o Minor bugfixes (trivial memory leaks):
4309 - Fix a small memory leak when signing a directory object. Fixes bug
4310 11275; bugfix on 0.2.4.13-alpha.
4311 - Resolve some memory leaks found by coverity in the unit tests, on
4312 exit in tor-gencert, and on a failure to compute digests for our
4313 own keys when generating a v3 networkstatus vote. These leaks
4314 should never have affected anyone in practice.
4316 o Code simplification and refactoring:
4317 - Remove some old fallback code designed to keep Tor clients working
4318 in a network with only two working relays. Elsewhere in the code we
4319 have long since stopped supporting such networks, so there wasn't
4320 much point in keeping it around. Addresses ticket 9926.
4321 - Reject 0-length EXTEND2 cells more explicitly. Fixes bug 10536;
4322 bugfix on 0.2.4.8-alpha. Reported by "cypherpunks".
4323 - Extract the common duplicated code for creating a subdirectory
4324 of the data directory and writing to a file in it. Fixes ticket
4325 4282; patch from Peter Retzlaff.
4326 - Since OpenSSL 0.9.7, the i2d_*() functions support allocating output
4327 buffer. Avoid calling twice: i2d_RSAPublicKey(), i2d_DHparams(),
4328 i2d_X509(), and i2d_PublicKey(). Resolves ticket 5170.
4329 - Add a set of accessor functions for the circuit timeout data
4330 structure. Fixes ticket 6153; patch from "piet".
4331 - Clean up exit paths from connection_listener_new(). Closes ticket
4332 8789. Patch from Arlo Breault.
4333 - Since we rely on OpenSSL 0.9.8 now, we can use EVP_PKEY_cmp()
4334 and drop our own custom pkey_eq() implementation. Fixes bug 9043.
4335 - Use a doubly-linked list to implement the global circuit list.
4336 Resolves ticket 9108. Patch from Marek Majkowski.
4337 - Remove contrib/id_to_fp.c since it wasn't used anywhere.
4338 - Remove constants and tests for PKCS1 padding; it's insecure and
4339 shouldn't be used for anything new. Fixes bug 8792; patch
4341 - Remove instances of strcpy() from the unit tests. They weren't
4342 hurting anything, since they were only in the unit tests, but it's
4343 embarassing to have strcpy() in the code at all, and some analysis
4344 tools don't like it. Fixes bug 8790; bugfix on 0.2.3.6-alpha and
4345 0.2.3.8-alpha. Patch from Arlo Breault.
4346 - Remove is_internal_IP() function. Resolves ticket 4645.
4347 - Remove unused function circuit_dump_by_chan from circuitlist.c.
4348 Closes issue 9107; patch from "marek".
4349 - Change our use of the ENUM_BF macro to avoid declarations that
4351 - Get rid of router->address, since in all cases it was just the
4352 string representation of router->addr. Resolves ticket 5528.
4355 - Adjust the URLs in the README to refer to the new locations of
4356 several documents on the website. Fixes bug 12830. Patch from
4358 - Document 'reject6' and 'accept6' ExitPolicy entries. Resolves
4360 - Update manpage to describe some of the files you can expect to
4361 find in Tor's DataDirectory. Addresses ticket 9839.
4362 - Clean up several option names in the manpage to match their real
4363 names, add the missing documentation for a couple of testing and
4364 directory authority options, remove the documentation for a
4365 V2-directory fetching option that no longer exists. Resolves
4367 - Correct the documenation so that it lists the correct directory
4368 for the stats files. (They are in a subdirectory called "stats",
4370 - In the manpage, move more authority-only options into the
4371 directory authority section so that operators of regular directory
4372 caches don't get confused.
4373 - Fix the layout of the SOCKSPort flags in the manpage. Fixes bug
4374 11061; bugfix on 0.2.4.7-alpha.
4375 - Resolve warnings from Doxygen.
4376 - Document in the manpage that "KBytes" may also be written as
4377 "kilobytes" or "KB", that "Kbits" may also be written as
4378 "kilobits", and so forth. Closes ticket 9222.
4379 - Document that the ClientOnly config option overrides ORPort.
4380 Our old explanation made ClientOnly sound as though it did
4381 nothing at all. Resolves bug 9059.
4382 - Explain that SocksPolicy, DirPolicy, and similar options don't
4383 take port arguments. Fixes the other part of ticket 11108.
4384 - Fix a comment about the rend_server_descriptor_t.protocols field
4385 to more accurately describe its range. Also, make that field
4386 unsigned, to more accurately reflect its usage. Fixes bug 9099;
4387 bugfix on 0.2.1.5-alpha.
4388 - Fix the manpage's description of HiddenServiceAuthorizeClient:
4389 the maximum client name length is 16, not 19. Fixes bug 11118;
4390 bugfix on 0.2.1.6-alpha.
4393 - The contrib directory has been sorted and tidied. Before, it was
4394 an unsorted dumping ground for useful and not-so-useful things.
4395 Now, it is divided based on functionality, and the items which
4396 seemed to be nonfunctional or useless have been removed. Resolves
4397 ticket 8966; based on patches from "rl1987".
4399 o Removed code and features:
4400 - Clients now reject any directory authority certificates lacking
4401 a dir-key-crosscert element. These have been included since
4402 0.2.1.9-alpha, so there's no real reason for them to be optional
4403 any longer. Completes proposal 157. Resolves ticket 10162.
4404 - Remove all code that existed to support the v2 directory system,
4405 since there are no longer any v2 directory authorities. Resolves
4407 - Remove the HSAuthoritativeDir and AlternateHSAuthority torrc
4408 options, which were used for designating authorities as "Hidden
4409 service authorities". There has been no use of hidden service
4410 authorities since 0.2.2.1-alpha, when we stopped uploading or
4411 downloading v0 hidden service descriptors. Fixes bug 10881; also
4412 part of a fix for bug 10841.
4413 - Remove /tor/dbg-stability.txt URL that was meant to help debug WFU
4414 and MTBF calculations, but that nobody was using. Fixes bug 11742.
4415 - The TunnelDirConns and PreferTunnelledDirConns options no longer
4416 exist; tunneled directory connections have been available since
4417 0.1.2.5-alpha, and turning them off is not a good idea. This is a
4418 brute-force fix for 10849, where "TunnelDirConns 0" would break
4420 - Remove all code for the long unused v1 directory protocol.
4421 Resolves ticket 11070.
4422 - Remove all remaining code related to version-0 hidden service
4423 descriptors: they have not been in use since 0.2.2.1-alpha. Fixes
4424 the rest of bug 10841.
4425 - Remove migration code from when we renamed the "cached-routers"
4426 file to "cached-descriptors" back in 0.2.0.8-alpha. This
4427 incidentally resolves ticket 6502 by cleaning up the related code
4428 a bit. Patch from Akshay Hebbar.
4430 o Test infrastructure:
4431 - Tor now builds each source file in two modes: a mode that avoids
4432 exposing identifiers needlessly, and another mode that exposes
4433 more identifiers for testing. This lets the compiler do better at
4434 optimizing the production code, while enabling us to take more
4435 radical measures to let the unit tests test things.
4436 - The production builds no longer include functions used only in
4437 the unit tests; all functions exposed from a module only for
4438 unit-testing are now static in production builds.
4439 - Add an --enable-coverage configuration option to make the unit
4440 tests (and a new src/or/tor-cov target) to build with gcov test
4442 - Update to the latest version of tinytest.
4443 - Improve the tinytest implementation of string operation tests so
4444 that comparisons with NULL strings no longer crash the tests; they
4445 now just fail, normally. Fixes bug 9004; bugfix on 0.2.2.4-alpha.
4446 - New macros in test.h to simplify writing mock-functions for unit
4447 tests. Part of ticket 11507. Patch from Dana Koch.
4448 - We now have rudimentary function mocking support that our unit
4449 tests can use to test functions in isolation. Function mocking
4450 lets the tests temporarily replace a function's dependencies with
4451 stub functions, so that the tests can check the function without
4452 invoking the other functions it calls.
4455 - Complete tests for the status.c module. Resolves ticket 11507.
4456 Patch from Dana Koch.
4457 - Add more unit tests for the <circid,channel>->circuit map, and
4458 the destroy-cell-tracking code to fix bug 7912.
4459 - Unit tests for failing cases of the TAP onion handshake.
4460 - More unit tests for address-manipulation functions.
4462 o Distribution (systemd):
4463 - Include a tor.service file in contrib/dist for use with systemd.
4464 Some distributions will be able to use this file unmodified;
4465 others will need to tweak it, or write their own. Patch from Jamie
4466 Nguyen; resolves ticket 8368.
4467 - Verify configuration file via ExecStartPre in the systemd unit
4468 file. Patch from intrigeri; resolves ticket 12730.
4469 - Explicitly disable RunAsDaemon in the systemd unit file. Our
4470 current systemd unit uses "Type = simple", so systemd does not
4471 expect tor to fork. If the user has "RunAsDaemon 1" in their
4472 torrc, then things won't work as expected. This is e.g. the case
4473 on Debian (and derivatives), since there we pass "--defaults-torrc
4474 /usr/share/tor/tor-service-defaults-torrc" (that contains
4475 "RunAsDaemon 1") by default. Patch by intrigeri; resolves
4479 Changes in version 0.2.4.25 - 2014-10-20
4480 Tor 0.2.4.25 disables SSL3 in response to the recent "POODLE" attack
4481 (even though POODLE does not affect Tor). It also works around a crash
4482 bug caused by some operating systems' response to the "POODLE" attack
4483 (which does affect Tor).
4485 o Major security fixes (also in 0.2.5.9-rc):
4486 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
4487 today support TLS 1.0 or later, so we can safely turn off support
4488 for this old (and insecure) protocol. Fixes bug 13426.
4490 o Major bugfixes (openssl bug workaround, also in 0.2.5.9-rc):
4491 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
4492 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
4493 13471. This is a workaround for an OpenSSL bug.
4496 Changes in version 0.2.4.24 - 2014-09-22
4497 Tor 0.2.4.24 fixes a bug that affects consistency and speed when
4498 connecting to hidden services, and it updates the location of one of
4499 the directory authorities.
4502 - Clients now send the correct address for their chosen rendezvous
4503 point when trying to access a hidden service. They used to send
4504 the wrong address, which would still work some of the time because
4505 they also sent the identity digest of the rendezvous point, and if
4506 the hidden service happened to try connecting to the rendezvous
4507 point from a relay that already had a connection open to it,
4508 the relay would reuse that connection. Now connections to hidden
4509 services should be more robust and faster. Also, this bug meant
4510 that clients were leaking to the hidden service whether they were
4511 on a little-endian (common) or big-endian (rare) system, which for
4512 some users might have reduced their anonymity. Fixes bug 13151;
4513 bugfix on 0.2.1.5-alpha.
4515 o Directory authority changes:
4516 - Change IP address for gabelmoo (v3 directory authority).
4518 o Minor features (geoip):
4519 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
4523 Changes in version 0.2.4.23 - 2014-07-28
4524 Tor 0.2.4.23 brings us a big step closer to slowing down the risk from
4525 guard rotation, and also backports several important fixes from the
4526 Tor 0.2.5 alpha release series.
4529 - Clients now look at the "usecreatefast" consensus parameter to
4530 decide whether to use CREATE_FAST or CREATE cells for the first hop
4531 of their circuit. This approach can improve security on connections
4532 where Tor's circuit handshake is stronger than the available TLS
4533 connection security levels, but the tradeoff is more computational
4534 load on guard relays. Implements proposal 221. Resolves ticket 9386.
4535 - Make the number of entry guards configurable via a new
4536 NumEntryGuards consensus parameter, and the number of directory
4537 guards configurable via a new NumDirectoryGuards consensus
4538 parameter. Implements ticket 12688.
4541 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
4542 implementation that caused incorrect results on 32-bit
4543 implementations when certain malformed inputs were used along with
4544 a small class of private ntor keys. This bug does not currently
4545 appear to allow an attacker to learn private keys or impersonate a
4546 Tor server, but it could provide a means to distinguish 32-bit Tor
4547 implementations from 64-bit Tor implementations. Fixes bug 12694;
4548 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
4552 - Warn and drop the circuit if we receive an inbound 'relay early'
4553 cell. Those used to be normal to receive on hidden service circuits
4554 due to bug 1038, but the buggy Tor versions are long gone from
4555 the network so we can afford to resume watching for them. Resolves
4556 the rest of bug 1038; bugfix on 0.2.1.19.
4557 - Correct a confusing error message when trying to extend a circuit
4558 via the control protocol but we don't know a descriptor or
4559 microdescriptor for one of the specified relays. Fixes bug 12718;
4560 bugfix on 0.2.3.1-alpha.
4561 - Avoid an illegal read from stack when initializing the TLS
4562 module using a version of OpenSSL without all of the ciphers
4563 used by the v2 link handshake. Fixes bug 12227; bugfix on
4564 0.2.4.8-alpha. Found by "starlight".
4567 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
4571 Changes in version 0.2.4.22 - 2014-05-16
4572 Tor 0.2.4.22 backports numerous high-priority fixes from the Tor 0.2.5
4573 alpha release series. These include blocking all authority signing
4574 keys that may have been affected by the OpenSSL "heartbleed" bug,
4575 choosing a far more secure set of TLS ciphersuites by default, closing
4576 a couple of memory leaks that could be used to run a target relay out
4577 of RAM, and several others.
4579 o Major features (security, backport from 0.2.5.4-alpha):
4580 - Block authority signing keys that were used on authorities
4581 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
4582 don't have any evidence that these keys _were_ compromised; we're
4583 doing this to be prudent.) Resolves ticket 11464.
4585 o Major bugfixes (security, OOM):
4586 - Fix a memory leak that could occur if a microdescriptor parse
4587 fails during the tokenizing step. This bug could enable a memory
4588 exhaustion attack by directory servers. Fixes bug 11649; bugfix
4591 o Major bugfixes (TLS cipher selection, backport from 0.2.5.4-alpha):
4592 - The relay ciphersuite list is now generated automatically based on
4593 uniform criteria, and includes all OpenSSL ciphersuites with
4594 acceptable strength and forward secrecy. Previously, we had left
4595 some perfectly fine ciphersuites unsupported due to omission or
4596 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
4597 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
4598 - Relays now trust themselves to have a better view than clients of
4599 which TLS ciphersuites are better than others. (Thanks to bug
4600 11513, the relay list is now well-considered, whereas the client
4601 list has been chosen mainly for anti-fingerprinting purposes.)
4602 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
4603 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
4604 AES128. Resolves ticket 11528.
4605 - Clients now try to advertise the same list of ciphersuites as
4606 Firefox 28. This change enables selection of (fast) GCM
4607 ciphersuites, disables some strange old ciphers, and stops
4608 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
4609 Resolves ticket 11438.
4611 o Minor bugfixes (configuration, security):
4612 - When running a hidden service, do not allow TunneledDirConns 0:
4613 trying to set that option together with a hidden service would
4614 otherwise prevent the hidden service from running, and also make
4615 it publish its descriptors directly over HTTP. Fixes bug 10849;
4616 bugfix on 0.2.1.1-alpha.
4618 o Minor bugfixes (controller, backport from 0.2.5.4-alpha):
4619 - Avoid sending a garbage value to the controller when a circuit is
4620 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
4622 o Minor bugfixes (exit relay, backport from 0.2.5.4-alpha):
4623 - Stop leaking memory when we successfully resolve a PTR record.
4624 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
4626 o Minor bugfixes (bridge client, backport from 0.2.5.4-alpha):
4627 - Avoid 60-second delays in the bootstrapping process when Tor is
4628 launching for a second time while using bridges. Fixes bug 9229;
4629 bugfix on 0.2.0.3-alpha.
4631 o Minor bugfixes (relays and bridges, backport from 0.2.5.4-alpha):
4632 - Give the correct URL in the warning message when trying to run a
4633 relay on an ancient version of Windows. Fixes bug 9393.
4635 o Minor bugfixes (compilation):
4636 - Fix a compilation error when compiling with --disable-curve25519.
4637 Fixes bug 9700; bugfix on 0.2.4.17-rc.
4640 - Downgrade the warning severity for the the "md was still
4641 referenced 1 node(s)" warning. Tor 0.2.5.4-alpha has better code
4642 for trying to diagnose this bug, and the current warning in
4643 earlier versions of tor achieves nothing useful. Addresses warning
4646 o Minor features (log verbosity, backport from 0.2.5.4-alpha):
4647 - When we run out of usable circuit IDs on a channel, log only one
4648 warning for the whole channel, and describe how many circuits
4649 there were on the channel. Fixes part of ticket 11553.
4651 o Minor features (security, backport from 0.2.5.4-alpha):
4652 - Decrease the lower limit of MaxMemInCellQueues to 256 MBytes (but
4653 leave the default at 8GBytes), to better support Raspberry Pi
4654 users. Fixes bug 9686; bugfix on 0.2.4.14-alpha.
4656 o Documentation (backport from 0.2.5.4-alpha):
4657 - Correctly document that we search for a system torrc file before
4658 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
4662 Changes in version 0.2.4.21 - 2014-02-28
4663 Tor 0.2.4.21 further improves security against potential adversaries who
4664 find breaking 1024-bit crypto doable, and backports several stability
4665 and robustness patches from the 0.2.5 branch.
4667 o Major features (client security):
4668 - When we choose a path for a 3-hop circuit, make sure it contains
4669 at least one relay that supports the NTor circuit extension
4670 handshake. Otherwise, there is a chance that we're building
4671 a circuit that's worth attacking by an adversary who finds
4672 breaking 1024-bit crypto doable, and that chance changes the game
4673 theory. Implements ticket 9777.
4676 - Do not treat streams that fail with reason
4677 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
4678 since it could also indicate an ENETUNREACH connection error. Fixes
4679 part of bug 10777; bugfix on 0.2.4.8-alpha.
4681 o Code simplification and refactoring:
4682 - Remove data structures which were introduced to implement the
4683 CellStatistics option: they are now redundant with the new timestamp
4684 field in the regular packed_cell_t data structure, which we did
4685 in 0.2.4.18-rc in order to resolve bug 9093. Resolves ticket 10870.
4688 - Always clear OpenSSL bignums before freeing them -- even bignums
4689 that don't contain secrets. Resolves ticket 10793. Patch by
4691 - Build without warnings under clang 3.4. (We have some macros that
4692 define static functions only some of which will get used later in
4693 the module. Starting with clang 3.4, these give a warning unless the
4694 unused attribute is set on them.) Resolves ticket 10904.
4695 - Update geoip and geoip6 files to the February 7 2014 Maxmind
4696 GeoLite2 Country database.
4699 - Set the listen() backlog limit to the largest actually supported
4700 on the system, not to the value in a header file. Fixes bug 9716;
4701 bugfix on every released Tor.
4702 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
4703 exit node as a NOROUTE error, not an INTERNAL error, since they
4704 can apparently happen when trying to connect to the wrong sort
4705 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
4706 - Fix build warnings about missing "a2x" comment when building the
4707 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
4708 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
4709 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
4710 not entirely remove it from the connection lists. Fixes bug 9602;
4711 bugfix on 0.2.4.4-alpha.
4712 - Fix a segmentation fault in our benchmark code when running with
4713 Fedora's OpenSSL package, or any other OpenSSL that provides
4714 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
4715 - Turn "circuit handshake stats since last time" log messages into a
4716 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
4718 o Documentation fixes:
4719 - Document that all but one DirPort entry must have the NoAdvertise
4720 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
4723 Changes in version 0.2.4.20 - 2013-12-22
4724 Tor 0.2.4.20 fixes potentially poor random number generation for users
4725 who 1) use OpenSSL 1.0.0 or later, 2) set "HardwareAccel 1" in their
4726 torrc file, 3) have "Sandy Bridge" or "Ivy Bridge" Intel processors,
4727 and 4) have no state file in their DataDirectory (as would happen on
4728 first start). Users who generated relay or hidden service identity
4729 keys in such a situation should discard them and generate new ones.
4731 This release also fixes a logic error that caused Tor clients to build
4732 many more preemptive circuits than they actually need.
4735 - Do not allow OpenSSL engines to replace the PRNG, even when
4736 HardwareAccel is set. The only default builtin PRNG engine uses
4737 the Intel RDRAND instruction to replace the entire PRNG, and
4738 ignores all attempts to seed it with more entropy. That's
4739 cryptographically stupid: the right response to a new alleged
4740 entropy source is never to discard all previously used entropy
4741 sources. Fixes bug 10402; works around behavior introduced in
4742 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
4744 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
4745 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
4746 - Avoid launching spurious extra circuits when a stream is pending.
4747 This fixes a bug where any circuit that _wasn't_ unusable for new
4748 streams would be treated as if it were, causing extra circuits to
4749 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
4752 - Avoid a crash bug when starting with a corrupted microdescriptor
4753 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
4754 - If we fail to dump a previously cached microdescriptor to disk, avoid
4755 freeing duplicate data later on. Fixes bug 10423; bugfix on
4756 0.2.4.13-alpha. Spotted by "bobnomnom".
4759 Changes in version 0.2.4.19 - 2013-12-11
4760 The Tor 0.2.4 release series is dedicated to the memory of Aaron Swartz
4761 (1986-2013). Aaron worked on diverse projects including helping to guide
4762 Creative Commons, playing a key role in stopping SOPA/PIPA, bringing
4763 transparency to the U.S government's PACER documents, and contributing
4764 design and development for Tor and Tor2Web. Aaron was one of the latest
4765 martyrs in our collective fight for civil liberties and human rights,
4766 and his death is all the more painful because he was one of us.
4768 Tor 0.2.4.19, the first stable release in the 0.2.4 branch, features
4769 a new circuit handshake and link encryption that use ECC to provide
4770 better security and efficiency; makes relays better manage circuit
4771 creation requests; uses "directory guards" to reduce client enumeration
4772 risks; makes bridges collect and report statistics about the pluggable
4773 transports they support; cleans up and improves our geoip database;
4774 gets much closer to IPv6 support for clients, bridges, and relays; makes
4775 directory authorities use measured bandwidths rather than advertised
4776 ones when computing flags and thresholds; disables client-side DNS
4777 caching to reduce tracking risks; and fixes a big bug in bridge
4778 reachability testing. This release introduces two new design
4779 abstractions in the code: a new "channel" abstraction between circuits
4780 and or_connections to allow for implementing alternate relay-to-relay
4781 transports, and a new "circuitmux" abstraction storing the queue of
4782 circuits for a channel. The release also includes many stability,
4783 security, and privacy fixes.
4785 o Major features (new circuit handshake):
4786 - Tor now supports a new circuit extension handshake designed by Ian
4787 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
4788 circuit extension handshake, later called "TAP", was a bit slow
4789 (especially on the relay side), had a fragile security proof, and
4790 used weaker keys than we'd now prefer. The new circuit handshake
4791 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
4792 function, making it significantly more secure than the older
4793 handshake, and significantly faster. Tor can use one of two built-in
4794 pure-C curve25519-donna implementations by Adam Langley, or it
4795 can link against the "nacl" library for a tuned version if present.
4797 The built-in version is very fast for 64-bit systems when building
4798 with GCC. The built-in 32-bit version is still faster than the
4799 old TAP protocol, but using libnacl is better on most such hosts.
4801 Implements proposal 216; closes ticket 7202.
4803 o Major features (better link encryption):
4804 - Relays can now enable the ECDHE TLS ciphersuites when available
4805 and appropriate. These ciphersuites let us negotiate forward-secure
4806 TLS secret keys more safely and more efficiently than with our
4807 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
4808 public relays prefer the (faster) P224 group, and bridges prefer
4809 the (more common) P256 group; you can override this with the
4812 This feature requires clients running 0.2.3.17-beta or later,
4813 and requires both sides to be running OpenSSL 1.0.0 or later
4814 with ECC support. OpenSSL 1.0.1, with the compile-time option
4815 "enable-ec_nistp_64_gcc_128", is highly recommended.
4817 Implements the relay side of proposal 198; closes ticket 7200.
4819 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
4820 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
4821 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
4822 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
4823 them to solve bug 6033.)
4825 o Major features (relay performance):
4826 - Instead of limiting the number of queued onionskins (aka circuit
4827 create requests) to a fixed, hard-to-configure number, we limit
4828 the size of the queue based on how many we expect to be able to
4829 process in a given amount of time. We estimate the time it will
4830 take to process an onionskin based on average processing time
4831 of previous onionskins. Closes ticket 7291. You'll never have to
4832 configure MaxOnionsPending again.
4833 - Relays process the new "NTor" circuit-level handshake requests
4834 with higher priority than the old "TAP" circuit-level handshake
4835 requests. We still process some TAP requests to not totally starve
4836 0.2.3 clients when NTor becomes popular. A new consensus parameter
4837 "NumNTorsPerTAP" lets us tune the balance later if we need to.
4838 Implements ticket 9574.
4840 o Major features (client bootstrapping resilience):
4841 - Add a new "FallbackDir" torrc option to use when we can't use
4842 a directory mirror from the consensus (either because we lack a
4843 consensus, or because they're all down). Currently, all authorities
4844 are fallbacks by default, and there are no other default fallbacks,
4845 but that will change. This option will allow us to give clients a
4846 longer list of servers to try to get a consensus from when first
4847 connecting to the Tor network, and thereby reduce load on the
4848 directory authorities. Implements proposal 206, "Preconfigured
4849 directory sources for bootstrapping". We also removed the old
4850 "FallbackNetworkstatus" option, since we never got it working well
4851 enough to use it. Closes bug 572.
4852 - If we have no circuits open, use a relaxed timeout (the
4853 95th-percentile cutoff) until a circuit succeeds. This heuristic
4854 should allow Tor to succeed at building circuits even when the
4855 network connection drastically changes. Should help with bug 3443.
4857 o Major features (use of guards):
4858 - Support directory guards (proposal 207): when possible, clients now
4859 use their entry guards for non-anonymous directory requests. This
4860 can help prevent client enumeration. Note that this behavior only
4861 works when we have a usable consensus directory, and when options
4862 about what to download are more or less standard. In the future we
4863 should re-bootstrap from our guards, rather than re-bootstrapping
4864 from the preconfigured list of directory sources that ships with
4865 Tor. Resolves ticket 6526.
4866 - Raise the default time that a client keeps an entry guard from
4867 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
4868 2012 paper. (We would make it even longer, but we need better client
4869 load balancing first.) Also, make the guard lifetime controllable
4870 via a new GuardLifetime torrc option and a GuardLifetime consensus
4871 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
4873 o Major features (bridges with pluggable transports):
4874 - Bridges now report the pluggable transports they support to the
4875 bridge authority, so it can pass the supported transports on to
4876 bridgedb and/or eventually do reachability testing. Implements
4878 - Automatically forward the TCP ports of pluggable transport
4879 proxies using tor-fw-helper if PortForwarding is enabled. Implements
4882 o Major features (geoip database):
4883 - Maxmind began labelling Tor relays as being in country "A1",
4884 which breaks by-country node selection inside Tor. Now we use a
4885 script to replace "A1" ("Anonymous Proxy") entries in our geoip
4886 file with real country codes. This script fixes about 90% of "A1"
4887 entries automatically and uses manual country code assignments to
4888 fix the remaining 10%. See src/config/README.geoip for details.
4890 - Add GeoIP database for IPv6 addresses. The new config option
4892 - Update to the October 2 2013 Maxmind GeoLite Country database.
4894 o Major features (IPv6):
4895 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
4896 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
4897 to happen. Implements ticket 5535.
4898 - All kind of relays, not just bridges, can now advertise an IPv6
4899 OR port. Implements ticket 6362.
4900 - Relays can now exit to IPv6 addresses: make sure that you have IPv6
4901 connectivity, then set the IPv6Exit flag to 1. Also make sure your
4902 exit policy reads as you would like: the address * applies to all
4903 address families, whereas *4 is IPv4 address only, and *6 is IPv6
4904 addresses only. On the client side, you'll need to wait for enough
4905 exits to support IPv6, apply the "IPv6Traffic" flag to a SocksPort,
4906 and use Socks5. Closes ticket 5547, implements proposal 117 as
4907 revised in proposal 208.
4908 - Bridge authorities now accept IPv6 bridge addresses and include
4909 them in network status documents. Implements ticket 5534.
4910 - Directory authorities vote on IPv6 OR ports. Implements ticket 6363.
4912 o Major features (directory authorities):
4913 - Directory authorities now prefer using measured bandwidths to
4914 advertised ones when computing flags and thresholds. Resolves
4916 - Directory authorities that vote measured bandwidths about more
4917 than a threshold number of relays now treat relays with
4918 unmeasured bandwidths as having bandwidth 0 when computing their
4919 flags. Resolves ticket 8435.
4920 - Directory authorities now support a new consensus method (17)
4921 where they cap the published bandwidth of relays for which
4922 insufficient bandwidth measurements exist. Fixes part of bug 2286.
4923 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
4924 serve any v2 directory information. Now we can test disabling the
4925 old deprecated v2 directory format, and see whether doing so has
4926 any effect on network load. Begins to fix bug 6783.
4928 o Major features (build and portability):
4929 - Switch to a nonrecursive Makefile structure. Now instead of each
4930 Makefile.am invoking other Makefile.am's, there is a master
4931 Makefile.am that includes the others. This change makes our build
4932 process slightly more maintainable, and improves parallelism for
4933 building with make -j. Original patch by Stewart Smith; various
4934 fixes by Jim Meyering.
4935 - Where available, we now use automake's "silent" make rules by
4936 default, so that warnings are easier to spot. You can get the old
4937 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
4938 - Resume building correctly with MSVC and Makefile.nmake. This patch
4939 resolves numerous bugs and fixes reported by ultramage, including
4940 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
4942 o Security features:
4943 - Switch to a completely time-invariant approach for picking nodes
4944 weighted by bandwidth. Our old approach would run through the
4945 part of the loop after it had made its choice slightly slower
4946 than it ran through the part of the loop before it had made its
4947 choice. Addresses ticket 6538.
4948 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
4949 by tor2web clients allows hidden services to identify tor2web
4950 clients through their repeated selection of the same rendezvous
4951 and introduction point circuit endpoints (their guards). Resolves
4954 o Major bugfixes (relay denial of service):
4955 - When we have too much memory queued in circuits (according to a new
4956 MaxMemInCellQueues option), close the circuits that have the oldest
4957 queued cells, on the theory that those are most responsible for
4958 us running low on memory. This prevents us from running out of
4959 memory as a relay if circuits fill up faster than they can be
4960 drained. Fixes bugs 9063 and 9093; bugfix on the 54th commit of
4961 Tor. This bug is a further fix beyond bug 6252, whose fix was
4962 merged into 0.2.3.21-rc.
4963 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
4964 ID: these could be used to create unexpected streams and circuits
4965 which would count as "present" to some parts of Tor but "absent"
4966 to others, leading to zombie circuits and streams or to a bandwidth
4967 denial-of-service. Fixes bug 7889; bugfix on every released version
4968 of Tor. Reported by "oftc_must_be_destroyed".
4969 - Avoid a bug where our response to TLS renegotiation under certain
4970 network conditions could lead to a busy-loop, with 100% CPU
4971 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
4973 o Major bugfixes (asserts, crashes, leaks):
4974 - Prevent the get_freelists() function from running off the end of
4975 the list of freelists if it somehow gets an unrecognized
4976 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
4978 - Avoid a memory leak where we would leak a consensus body when we
4979 find that a consensus which we couldn't previously verify due to
4980 missing certificates is now verifiable. Fixes bug 8719; bugfix
4982 - If we are unable to save a microdescriptor to the journal, do not
4983 drop it from memory and then reattempt downloading it. Fixes bug
4984 9645; bugfix on 0.2.2.6-alpha.
4985 - Fix an assertion failure that would occur when disabling the
4986 ORPort setting on a running Tor process while accounting was
4987 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
4988 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
4989 when an exit connection with optimistic data succeeds immediately
4990 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
4992 - Fix a memory leak that would occur whenever a configuration
4993 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
4995 o Major bugfixes (relay rate limiting):
4996 - When a TLS write is partially successful but incomplete, remember
4997 that the flushed part has been flushed, and notice that bytes were
4998 actually written. Reported and fixed pseudonymously. Fixes bug 7708;
4999 bugfix on Tor 0.1.0.5-rc.
5000 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
5001 to 1GB/1GB. The previous defaults were intended to be "basically
5002 infinite", but it turns out they're now limiting our 100mbit+
5003 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
5004 last time we raised it).
5005 - No longer stop reading or writing on cpuworker connections when
5006 our rate limiting buckets go empty. Now we should handle circuit
5007 handshake requests more promptly. Resolves bug 9731.
5009 o Major bugfixes (client-side privacy):
5010 - When we mark a circuit as unusable for new circuits, have it
5011 continue to be unusable for new circuits even if MaxCircuitDirtiness
5012 is increased too much at the wrong time, or the system clock jumps
5013 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
5014 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
5015 which have resolved to internal addresses") is set, apply that
5016 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
5017 - When an exit relay rejects a stream with reason "exit policy", but
5018 we only know an exit policy summary (e.g. from the microdesc
5019 consensus) for it, do not mark the relay as useless for all exiting.
5020 Instead, mark just the circuit as unsuitable for that particular
5021 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
5023 o Major bugfixes (stream isolation):
5024 - Allow applications to get proper stream isolation with
5025 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
5026 username/password authentication also offer "no authentication". Tor
5027 had previously preferred "no authentication", so the applications
5028 never actually sent Tor their auth details. Now Tor selects
5029 username/password authentication if it's offered. You can disable
5030 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
5031 bug 8117; bugfix on 0.2.3.3-alpha.
5032 - Follow the socks5 protocol when offering username/password
5033 authentication. The fix for bug 8117 exposed this bug, and it
5034 turns out real-world applications like Pidgin do care. Bugfix on
5035 0.2.3.2-alpha; fixes bug 8879.
5037 o Major bugfixes (client circuit building):
5038 - Alter circuit build timeout measurement to start at the point
5039 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
5040 initialization). This should make our timeout measurements more
5041 uniform. Previously, we were sometimes including ORconn setup time
5042 in our circuit build time measurements. Should resolve bug 3443.
5043 - If the circuit build timeout logic is disabled (via the consensus,
5044 or because we are an authority), then don't build testing circuits.
5045 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
5047 o Major bugfixes (client-side DNS):
5048 - Turn off the client-side DNS cache by default. Updating and using
5049 the DNS cache is now configurable on a per-client-port
5050 level. SOCKSPort, DNSPort, etc lines may now contain
5051 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
5052 cache these types of DNS answers when we receive them from an
5053 exit node in response to an application request on this port, and
5054 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
5055 cached DNS answers of these types, we shouldn't use them. It's
5056 potentially risky to use cached DNS answers at the client, since
5057 doing so can indicate to one exit what answers we've gotten
5058 for DNS lookups in the past. With IPv6, this becomes especially
5059 problematic. Using cached DNS answers for requests on the same
5060 circuit would present less linkability risk, since all traffic
5061 on a circuit is already linkable, but it would also provide
5062 little performance benefit: the exit node caches DNS replies
5063 too. Implements a simplified version of Proposal 205. Implements
5066 o Major bugfixes (hidden service privacy):
5067 - Limit hidden service descriptors to at most ten introduction
5068 points, to slow one kind of guard enumeration. Fixes bug 9002;
5069 bugfix on 0.1.1.11-alpha.
5071 o Major bugfixes (directory fetching):
5072 - If the time to download the next old-style networkstatus is in
5073 the future, do not decline to consider whether to download the
5074 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
5076 - We used to always request authority certificates by identity digest,
5077 meaning we'd get the newest one even when we wanted one with a
5078 different signing key. Then we would complain about being given
5079 a certificate we already had, and never get the one we really
5080 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
5081 resource to request the one we want. Fixes bug 5595; bugfix on
5084 o Major bugfixes (bridge reachability):
5085 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
5086 previously they did not, which prevented them from receiving
5087 successful connections from relays for self-test or bandwidth
5088 testing. Also, when a relay is extending a circuit to a bridge,
5089 it needs to send a NETINFO cell, even when the bridge hasn't sent
5090 an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
5092 o Major bugfixes (control interface):
5093 - When receiving a new configuration file via the control port's
5094 LOADCONF command, do not treat the defaults file as absent.
5095 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
5097 o Major bugfixes (directory authorities):
5098 - Stop marking every relay as having been down for one hour every
5099 time we restart a directory authority. These artificial downtimes
5100 were messing with our Stable and Guard flag calculations. Fixes
5101 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
5102 - When computing directory thresholds, ignore any rejected-as-sybil
5103 nodes during the computation so that they can't influence Fast,
5104 Guard, etc. (We should have done this for proposal 109.) Fixes
5106 - When marking a node as a likely sybil, reset its uptime metrics
5107 to zero, so that it cannot time towards getting marked as Guard,
5108 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
5110 - Fix a bug in the voting algorithm that could yield incorrect results
5111 when a non-naming authority declared too many flags. Fixes bug 9200;
5112 bugfix on 0.2.0.3-alpha.
5114 o Internal abstraction features:
5115 - Introduce new channel_t abstraction between circuits and
5116 or_connection_t to allow for implementing alternate OR-to-OR
5117 transports. A channel_t is an abstract object which can either be a
5118 cell-bearing channel, which is responsible for authenticating and
5119 handshaking with the remote OR and transmitting cells to and from
5120 it, or a listening channel, which spawns new cell-bearing channels
5121 at the request of remote ORs. Implements part of ticket 6465.
5122 - Make a channel_tls_t subclass of channel_t, adapting it to the
5123 existing or_connection_t code. The V2/V3 protocol handshaking
5124 code which formerly resided in command.c has been moved below the
5125 channel_t abstraction layer and may be found in channeltls.c now.
5126 Implements the rest of ticket 6465.
5127 - Introduce new circuitmux_t storing the queue of circuits for
5128 a channel; this encapsulates and abstracts the queue logic and
5129 circuit selection policy, and allows the latter to be overridden
5130 easily by switching out a policy object. The existing EWMA behavior
5131 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
5133 o New build requirements:
5134 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
5135 strongly recommended.
5136 - Tor maintainers now require Automake version 1.9 or later to build
5137 Tor from the Git repository. (Automake is not required when building
5138 from a source distribution.)
5140 o Minor features (protocol):
5141 - No longer include the "opt" prefix when generating routerinfos
5142 or v2 directories: it has been needless since Tor 0.1.2. Closes
5144 - Reject EXTEND cells sent to nonexistent streams. According to the
5145 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
5146 we were only checking for stream IDs that were currently in use.
5147 Found while hunting for more instances of bug 6271. Bugfix on
5148 0.0.2pre8, which introduced incremental circuit construction.
5149 - Tor relays and clients now support a better CREATE/EXTEND cell
5150 format, allowing the sender to specify multiple address, identity,
5151 and handshake types. Implements Robert Ransom's proposal 200;
5153 - Reject as invalid most directory objects containing a NUL.
5154 Belt-and-suspender fix for bug 8037.
5156 o Minor features (security):
5157 - Clear keys and key-derived material left on the stack in
5158 rendservice.c and rendclient.c. Check return value of
5159 crypto_pk_write_private_key_to_string() in rend_service_load_keys().
5160 These fixes should make us more forward-secure against cold-boot
5161 attacks and the like. Fixes bug 2385.
5162 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
5163 Irix's random() only return 15 bits; Solaris's random() returns more
5164 bits but its RAND_MAX says it only returns 15, and so on. Motivated
5165 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
5167 o Minor features (control protocol):
5168 - Add a "GETINFO signal/names" control port command. Implements
5170 - Provide default values for all options via "GETINFO config/defaults".
5171 Implements ticket 4971.
5172 - Allow an optional $ before the node identity digest in the
5173 controller command GETINFO ns/id/<identity>, for consistency with
5174 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
5175 - Add CACHED keyword to ADDRMAP events in the control protocol
5176 to indicate whether a DNS result will be cached or not. Resolves
5178 - Generate bootstrapping status update events correctly when fetching
5179 microdescriptors. Fixes bug 9927.
5181 o Minor features (path selection):
5182 - When deciding whether we have enough descriptors to build circuits,
5183 instead of looking at raw relay counts, look at which fraction
5184 of (bandwidth-weighted) paths we're able to build. This approach
5185 keeps clients from building circuits if their paths are likely to
5186 stand out statistically. The default fraction of paths needed is
5187 taken from the consensus directory; you can override it with the
5188 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
5189 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
5190 and we have GeoIP information, also exclude all nodes with unknown
5191 countries "??" and "A1". This behavior is controlled by the
5192 new GeoIPExcludeUnknown option: you can make such nodes always
5193 excluded with "GeoIPExcludeUnknown 1", and disable the feature
5194 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
5195 gets you the default behavior. Implements feature 7706.
5197 o Minor features (hidden services):
5198 - Improve circuit build timeout handling for hidden services.
5199 In particular: adjust build timeouts more accurately depending
5200 upon the number of hop-RTTs that a particular circuit type
5201 undergoes. Additionally, launch intro circuits in parallel
5202 if they timeout, and take the first one to reply as valid.
5203 - The Tor client now ignores sub-domain components of a .onion
5204 address. This change makes HTTP "virtual" hosting
5205 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
5206 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
5207 hosted on the same hidden service. Implements proposal 204.
5208 - Enable Tor to read configuration, state, and key information from
5209 a FIFO. Previously Tor would only read from files with a positive
5210 stat.st_size. Code from meejah; fixes bug 6044.
5212 o Minor features (clients):
5213 - Teach bridge-using clients to avoid 0.2.2.x bridges when making
5214 microdescriptor-related dir requests, and only fall back to normal
5215 descriptors if none of their bridges can handle microdescriptors
5216 (as opposed to the fix in ticket 4013, which caused them to fall
5217 back to normal descriptors if *any* of their bridges preferred
5218 them). Resolves ticket 4994.
5219 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
5220 TCP ports to forward. In the past it only accepted two ports:
5221 the ORPort and the DirPort.
5223 o Minor features (protecting client timestamps):
5224 - Clients no longer send timestamps in their NETINFO cells. These were
5225 not used for anything, and they provided one small way for clients
5226 to be distinguished from each other as they moved from network to
5227 network or behind NAT. Implements part of proposal 222.
5228 - Clients now round timestamps in INTRODUCE cells down to the nearest
5229 10 minutes. If a new Support022HiddenServices option is set to 0, or
5230 if it's set to "auto" and the feature is disabled in the consensus,
5231 the timestamp is sent as 0 instead. Implements part of proposal 222.
5232 - Stop sending timestamps in AUTHENTICATE cells. This is not such
5233 a big deal from a security point of view, but it achieves no actual
5234 good purpose, and isn't needed. Implements part of proposal 222.
5235 - Reduce down accuracy of timestamps in hidden service descriptors.
5236 Implements part of proposal 222.
5238 o Minor features (bridges):
5239 - Make bridge relays check once a minute for whether their IP
5240 address has changed, rather than only every 15 minutes. Resolves
5242 - Bridge statistics now count bridge clients connecting over IPv6:
5243 bridge statistics files now list "bridge-ip-versions" and
5244 extra-info documents list "geoip6-db-digest". The control protocol
5245 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
5246 implementation by "shkoo", addressing ticket 5055.
5247 - Add a new torrc option "ServerTransportListenAddr" to let bridge
5248 operators select the address where their pluggable transports will
5249 listen for connections. Resolves ticket 7013.
5250 - Randomize the lifetime of our SSL link certificate, so censors can't
5251 use the static value for filtering Tor flows. Resolves ticket 8443;
5252 related to ticket 4014 which was included in 0.2.2.33.
5254 o Minor features (relays):
5255 - Option OutboundBindAddress can be specified multiple times and
5256 accepts IPv6 addresses. Resolves ticket 6876.
5258 o Minor features (IPv6, client side):
5259 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
5260 prefer to hand out virtual IPv6 addresses, since there are more of
5261 them and we can't run out. To override this behavior and make IPv4
5262 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
5263 or DNSPort you're using for resolving. Implements ticket 7571.
5264 - AutomapHostsOnResolve responses are now randomized, to avoid
5265 annoying situations where Tor is restarted and applications
5266 connect to the wrong addresses.
5267 - Never try more than 1000 times to pick a new virtual address when
5268 AutomapHostsOnResolve is set. That's good enough so long as we
5269 aren't close to handing out our entire virtual address space;
5270 if you're getting there, it's best to switch to IPv6 virtual
5273 o Minor features (IPv6, relay/authority side):
5274 - New config option "AuthDirHasIPv6Connectivity 1" that directory
5275 authorities should set if they have IPv6 connectivity and want to
5276 do reachability tests for IPv6 relays. Implements feature 5974.
5277 - A relay with an IPv6 OR port now sends that address in NETINFO
5278 cells (in addition to its other address). Implements ticket 6364.
5280 o Minor features (directory authorities):
5281 - Directory authorities no long accept descriptors for any version of
5282 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
5283 These versions are insecure, unsupported, or both. Implements
5285 - When directory authorities are computing thresholds for flags,
5286 never let the threshold for the Fast flag fall below 4096
5287 bytes. Also, do not consider nodes with extremely low bandwidths
5288 when deciding thresholds for various directory flags. This change
5289 should raise our threshold for Fast relays, possibly in turn
5290 improving overall network performance; see ticket 1854. Resolves
5292 - Directory authorities now include inside each vote a statement of
5293 the performance thresholds they used when assigning flags.
5294 Implements ticket 8151.
5295 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
5296 in directory authority votes to describe whether they have enough
5297 measured bandwidths to ignore advertised (relay descriptor)
5298 bandwidth claims. Resolves ticket 8711.
5300 o Minor features (path bias detection):
5301 - Path Use Bias: Perform separate accounting for successful circuit
5302 use. Keep separate statistics on stream attempt rates versus stream
5303 success rates for each guard. Provide configurable thresholds to
5304 determine when to emit log messages or disable use of guards that
5305 fail too many stream attempts. Resolves ticket 7802.
5306 - Create three levels of Path Bias log messages, as opposed to just
5307 two. These are configurable via consensus as well as via the torrc
5308 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
5309 The default values are 0.70, 0.50, and 0.30 respectively.
5310 - Separate the log message levels from the decision to drop guards,
5311 which also is available via torrc option PathBiasDropGuards.
5312 PathBiasDropGuards still defaults to 0 (off).
5313 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
5314 in combination with PathBiasExtremeRate.
5315 - Increase the default values for PathBiasScaleThreshold and
5316 PathBiasCircThreshold from (200, 20) to (300, 150).
5317 - Add in circuit usage accounting to path bias. If we try to use a
5318 built circuit but fail for any reason, it counts as path bias.
5319 Certain classes of circuits where the adversary gets to pick your
5320 destination node are exempt from this accounting. Usage accounting
5321 can be specifically disabled via consensus parameter or torrc.
5322 - Convert all internal path bias state to double-precision floating
5323 point, to avoid roundoff error and other issues.
5324 - Only record path bias information for circuits that have completed
5325 *two* hops. Assuming end-to-end tagging is the attack vector, this
5326 makes us more resilient to ambient circuit failure without any
5327 detection capability loss.
5329 o Minor features (build):
5330 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
5331 dhill. Resolves ticket 6982.
5332 - Compile on win64 using mingw64. Fixes bug 7260; patches from
5334 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
5335 separate error codes; or at least, don't break for that reason.
5336 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
5338 o Build improvements (autotools):
5339 - Warn if building on a platform with an unsigned time_t: there
5340 are too many places where Tor currently assumes that time_t can
5341 hold negative values. We'd like to fix them all, but probably
5343 - Do not report status verbosely from autogen.sh unless the -v flag
5344 is specified. Fixes issue 4664. Patch from Onizuka.
5345 - Detect and reject attempts to build Tor with threading support
5346 when OpenSSL has been compiled without threading support.
5348 - Try to detect if we are ever building on a platform where
5349 memset(...,0,...) does not set the value of a double to 0.0. Such
5350 platforms are permitted by the C standard, though in practice
5351 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
5352 currently support them, but it's better to detect them and fail
5353 than to perform erroneously.
5354 - We no longer warn so much when generating manpages from their
5356 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
5357 the signs of types during autoconf. This is better than our old
5358 approach, which didn't work when cross-compiling.
5360 o Minor features (log messages, warnings):
5361 - Detect when we're running with a version of OpenSSL other than the
5362 one we compiled with. This conflict has occasionally given people
5363 hard-to-track-down errors.
5364 - Warn users who run hidden services on a Tor client with
5365 UseEntryGuards disabled that their hidden services will be
5366 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
5367 attack which motivated Tor to support entry guards in the first
5368 place). Resolves ticket 6889.
5369 - Warn when we are binding low ports when hibernation is enabled;
5370 previously we had warned when we were _advertising_ low ports with
5371 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
5372 - Issue a warning when running with the bufferevents backend enabled.
5373 It's still not stable, and people should know that they're likely
5374 to hit unexpected problems. Closes ticket 9147.
5376 o Minor features (log messages, notices):
5377 - Refactor resolve_my_address() so it returns the method by which we
5378 decided our public IP address (explicitly configured, resolved from
5379 explicit hostname, guessed from interfaces, learned by gethostname).
5380 Now we can provide more helpful log messages when a relay guesses
5381 its IP address incorrectly (e.g. due to unexpected lines in
5382 /etc/hosts). Resolves ticket 2267.
5383 - Track how many "TAP" and "NTor" circuit handshake requests we get,
5384 and how many we complete, and log it every hour to help relay
5385 operators follow trends in network load. Addresses ticket 9658.
5387 o Minor features (log messages, diagnostics):
5388 - If we fail to free a microdescriptor because of bug 7164, log
5389 the filename and line number from which we tried to free it.
5390 - We compute the overhead from passing onionskins back and forth to
5391 cpuworkers, and report it when dumping statistics in response to
5392 SIGUSR1. Supports ticket 7291.
5393 - Add another diagnostic to the heartbeat message: track and log
5394 overhead that TLS is adding to the data we write. If this is
5395 high, we are sending too little data to SSL_write at a time.
5396 Diagnostic for bug 7707.
5397 - Log packaged cell fullness as part of the heartbeat message.
5398 Diagnosis to try to determine the extent of bug 7743.
5399 - Add more detail to a log message about relaxed timeouts, to help
5401 - When learning a fingerprint for a bridge, log its corresponding
5402 transport type. Implements ticket 7896.
5403 - Warn more aggressively when flushing microdescriptors to a
5404 microdescriptor cache fails, in an attempt to mitigate bug 8031,
5405 or at least make it more diagnosable.
5406 - Improve the log message when "Bug/attack: unexpected sendme cell
5407 from client" occurs, to help us track bug 8093.
5408 - Improve debugging output to help track down bug 8185 ("Bug:
5409 outgoing relay cell has n_chan==NULL. Dropping.")
5411 o Minor features (log messages, quieter bootstrapping):
5412 - Log fewer lines at level "notice" about our OpenSSL and Libevent
5413 versions and capabilities when everything is going right. Resolves
5414 part of ticket 6736.
5415 - Omit the first heartbeat log message, because it never has anything
5416 useful to say, and it clutters up the bootstrapping messages.
5417 Resolves ticket 6758.
5418 - Don't log about reloading the microdescriptor cache at startup. Our
5419 bootstrap warnings are supposed to tell the user when there's a
5420 problem, and our bootstrap notices say when there isn't. Resolves
5421 ticket 6759; bugfix on 0.2.2.6-alpha.
5422 - Don't log "I learned some more directory information" when we're
5423 reading cached directory information. Reserve it for when new
5424 directory information arrives in response to a fetch. Resolves
5426 - Don't complain about bootstrapping problems while hibernating.
5427 These complaints reflect a general code problem, but not one
5428 with any problematic effects (no connections are actually
5429 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
5431 o Minor features (testing):
5432 - In our testsuite, create temporary directories with a bit more
5433 entropy in their name to make name collisions less likely. Fixes
5435 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
5436 (P-256) Diffie-Hellman handshakes to src/or/bench.
5437 - Add benchmark functions to test onion handshake performance.
5440 - The DirServer option is now DirAuthority, for consistency with
5441 current naming patterns. You can still use the old DirServer form.
5443 o Minor bugfixes (protocol):
5444 - Fix the handling of a TRUNCATE cell when it arrives while the
5445 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
5446 - When a Tor client gets a "truncated" relay cell, the first byte of
5447 its payload specifies why the circuit was truncated. We were
5448 ignoring this 'reason' byte when tearing down the circuit, resulting
5449 in the controller not being told why the circuit closed. Now we
5450 pass the reason from the truncated cell to the controller. Bugfix
5451 on 0.1.2.3-alpha; fixes bug 7039.
5452 - Fix a misframing issue when reading the version numbers in a
5453 VERSIONS cell. Previously we would recognize [00 01 00 02] as
5454 'version 1, version 2, and version 0x100', when it should have
5455 only included versions 1 and 2. Fixes bug 8059; bugfix on
5456 0.2.0.10-alpha. Reported pseudonymously.
5457 - Make the format and order of STREAM events for DNS lookups
5458 consistent among the various ways to launch DNS lookups. Fixes
5459 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy".
5461 o Minor bugfixes (syscalls and disk interaction):
5462 - Always check the return values of functions fcntl() and
5463 setsockopt(). We don't believe these are ever actually failing in
5464 practice, but better safe than sorry. Also, checking these return
5465 values should please analysis tools like Coverity. Patch from
5466 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
5467 - Avoid double-closing the listener socket in our socketpair()
5468 replacement (used on Windows) in the case where the addresses on
5469 our opened sockets don't match what we expected. Fixes bug 9400;
5470 bugfix on 0.0.2pre7. Found by Coverity.
5471 - Correctly store microdescriptors and extrainfo descriptors that
5472 include an internal NUL byte. Fixes bug 8037; bugfix on
5473 0.2.0.1-alpha. Bug reported by "cypherpunks".
5474 - If for some reason we fail to write a microdescriptor while
5475 rebuilding the cache, do not let the annotations from that
5476 microdescriptor linger in the cache file, and do not let the
5477 microdescriptor stay recorded as present in its old location.
5478 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
5479 - Use direct writes rather than stdio when building microdescriptor
5480 caches, in an attempt to mitigate bug 8031, or at least make it
5483 o Minor fixes (config options):
5484 - Warn and fail if a server is configured not to advertise any
5485 ORPorts at all. (We need *something* to put in our descriptor,
5486 or we just won't work.)
5487 - Behave correctly when the user disables LearnCircuitBuildTimeout
5488 but doesn't tell us what they would like the timeout to be. Fixes
5489 bug 6304; bugfix on 0.2.2.14-alpha.
5490 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
5491 to start with a triple-underscore so the controller won't touch it.
5492 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
5493 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
5494 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
5495 - When autodetecting the number of CPUs, use the number of available
5496 CPUs in preference to the number of configured CPUs. Inform the
5497 user if this reduces the number of available CPUs. Fixes bug 8002;
5498 bugfix on 0.2.3.1-alpha.
5499 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
5500 - Make it an error when you set EntryNodes but disable UseGuardNodes,
5501 since it will (surprisingly to some users) ignore EntryNodes. Fixes
5502 bug 8180; bugfix on 0.2.3.11-alpha.
5503 - Avoid overflows when the user sets MaxCircuitDirtiness to a
5504 ridiculously high value, by imposing a (ridiculously high) 30-day
5505 maximum on MaxCircuitDirtiness.
5507 o Minor bugfixes (control protocol):
5508 - Stop sending a stray "(null)" in some cases for the server status
5509 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
5511 - The ADDRMAP command can no longer generate an ill-formed error
5512 code on a failed MAPADDRESS. It now says "internal" rather than
5513 an English sentence fragment with spaces in the middle. Bugfix on
5516 o Minor bugfixes (clients / edges):
5517 - When we receive a RELAY_END cell with the reason DONE, or with no
5518 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
5519 status as "connection refused". Previously we reported these cases
5520 as success but then immediately closed the connection. Fixes bug
5521 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
5522 - If the guard we choose first doesn't answer, we would try the
5523 second guard, but once we connected to the second guard we would
5524 abandon it and retry the first one, slowing down bootstrapping.
5525 The fix is to treat all our initially chosen guards as acceptable
5526 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
5527 - When choosing which stream on a formerly stalled circuit to wake
5528 first, make better use of the platform's weak RNG. Previously,
5529 we had been using the % ("modulo") operator to try to generate a
5530 1/N chance of picking each stream, but this behaves badly with
5531 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
5534 o Minor bugfixes (path bias detection):
5535 - If the state file's path bias counts are invalid (presumably from a
5536 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
5537 additional checks and log messages to the scaling of Path Bias
5538 counts, in case there still are remaining issues with scaling.
5539 Should help resolve bug 8235.
5540 - Prevent rounding error in path bias counts when scaling
5541 them down, and use the correct scale factor default. Also demote
5542 some path bias related log messages down a level and make others
5543 less scary sounding. Fixes bug 6647. Bugfix on 0.2.3.17-beta.
5544 - Remove a source of rounding error during path bias count scaling;
5545 don't count cannibalized circuits as used for path bias until we
5546 actually try to use them; and fix a circuit_package_relay_cell()
5547 warning message about n_chan==NULL. Fixes bug 7802.
5548 - Paste the description for PathBias parameters from the man
5549 page into or.h, so the code documents them too. Fixes bug 7982;
5550 bugfix on 0.2.3.17-beta.
5552 o Minor bugfixes (relays):
5553 - Stop trying to resolve our hostname so often (e.g. every time we
5554 think about doing a directory fetch). Now we reuse the cached
5555 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
5556 and 2410 (bugfix on 0.1.2.2-alpha).
5557 - When examining the list of network interfaces to find our address,
5558 do not consider non-running or disabled network interfaces. Fixes
5559 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
5561 o Minor bugfixes (blocking resistance):
5562 - Only disable TLS session ticket support when running as a TLS
5563 server. Now clients will blend better with regular Firefox
5564 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
5566 o Minor bugfixes (IPv6):
5567 - Use square brackets around IPv6 addresses in numerous places
5568 that needed them, including log messages, HTTPS CONNECT proxy
5569 requests, TransportProxy statefile entries, and pluggable transport
5570 extra-info lines. Fixes bug 7011; patch by David Fifield.
5572 o Minor bugfixes (directory authorities):
5573 - Reject consensus votes with more than 64 known-flags. We aren't even
5574 close to that limit yet, and our code doesn't handle it correctly.
5575 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
5576 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
5577 bugfix on 0.2.0.3-alpha.
5579 o Minor bugfixes (memory leaks):
5580 - Avoid leaking memory if we fail to compute a consensus signature
5581 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
5582 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
5583 on 0.2.1.1-alpha; fixes bug 7816.
5584 - Fix a memory leak during safe-cookie controller authentication.
5585 Bugfix on 0.2.3.13-alpha; fixes bug 7816.
5586 - Free some more still-in-use memory at exit, to make hunting for
5587 memory leaks easier. Resolves bug 7029.
5589 o Minor bugfixes (code correctness):
5590 - Increase the width of the field used to remember a connection's
5591 link protocol version to two bytes. Harmless for now, since the
5592 only currently recognized versions are one byte long. Reported
5593 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
5594 - Fix a crash when debugging unit tests on Windows: deallocate a
5595 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
5596 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
5597 - When detecting the largest possible file descriptor (in order to
5598 close all file descriptors when launching a new program), actually
5599 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
5600 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
5602 - Avoid a crash if we fail to generate an extrainfo descriptor.
5603 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
5605 - Avoid an off-by-one error when checking buffer boundaries when
5606 formatting the exit status of a pluggable transport helper.
5607 This is probably not an exploitable bug, but better safe than
5608 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
5610 - Get rid of a couple of harmless clang warnings, where we compared
5611 enums to ints. These warnings are newly introduced in clang 3.2.
5613 o Minor bugfixes (code cleanliness):
5614 - Avoid use of reserved identifiers in our C code. The C standard
5615 doesn't like us declaring anything that starts with an
5616 underscore, so let's knock it off before we get in trouble. Fix
5617 for bug 1031; bugfix on the first Tor commit.
5618 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
5619 with large values. This situation was untriggered, but nevertheless
5620 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
5621 - Fix an impossible buffer overrun in the AES unit tests. Fixes
5622 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
5623 - Fix handling of rendezvous client authorization types over 8.
5624 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
5625 - Remove a couple of extraneous semicolons that were upsetting the
5626 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
5627 bugfix on 0.2.2.1-alpha.
5628 - When complaining about a client port on a public address, log
5629 which address we're complaining about. Fixes bug 4020; bugfix on
5630 0.2.3.3-alpha. Patch by Tom Fitzhenry.
5632 o Minor bugfixes (log messages, warnings):
5633 - If we encounter a write failure on a SOCKS connection before we
5634 finish our SOCKS handshake, don't warn that we closed the
5635 connection before we could send a SOCKS reply. Fixes bug 8427;
5636 bugfix on 0.1.0.1-rc.
5637 - Fix a directory authority warn caused when we have a large amount
5638 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
5639 - Downgrade "Failed to hand off onionskin" messages to "debug"
5640 severity, since they're typically redundant with the "Your computer
5641 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
5642 - Avoid spurious warnings when configuring multiple client ports of
5643 which only some are nonlocal. Previously, we had claimed that some
5644 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
5647 o Minor bugfixes (log messages, other):
5648 - Fix log messages and comments to avoid saying "GMT" when we mean
5649 "UTC". Fixes bug 6113.
5650 - When rejecting a configuration because we were unable to parse a
5651 quoted string, log an actual error message. Fixes bug 7950; bugfix
5653 - Correctly recognize that [::1] is a loopback address. Fixes
5654 bug 8377; bugfix on 0.2.1.3-alpha.
5655 - Don't log inappropriate heartbeat messages when hibernating: a
5656 hibernating node is _expected_ to drop out of the consensus,
5657 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
5658 bugfix on 0.2.3.1-alpha.
5659 - Eliminate several instances where we use "Nickname=ID" to refer to
5660 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
5661 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
5664 o Minor bugfixes (build):
5665 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
5666 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
5667 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
5669 o Documentation fixes:
5670 - Make the torify manpage no longer refer to tsocks; torify hasn't
5671 supported tsocks since 0.2.3.14-alpha.
5672 - Make the tor manpage no longer reference tsocks.
5673 - Fix the GeoIPExcludeUnknown documentation to refer to
5674 ExcludeExitNodes rather than the currently nonexistent
5675 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
5676 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
5678 - Say "KBytes" rather than "KB" in the man page (for various values
5679 of K), to further reduce confusion about whether Tor counts in
5680 units of memory or fractions of units of memory. Resolves ticket 7054.
5681 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
5682 names match. Fixes bug 7768.
5683 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
5684 message is logged at notice, not at info.
5685 - Clarify the usage and risks of setting the ContactInfo torrc line
5686 for your relay or bridge. Resolves ticket 9854.
5687 - Add anchors to the manpage so we can link to the html version of
5688 the documentation for specific options. Resolves ticket 9866.
5689 - Replace remaining references to DirServer in man page and
5690 log entries. Resolves ticket 10124.
5693 - Stop exporting estimates of v2 and v3 directory traffic shares
5694 in extrainfo documents. They were unneeded and sometimes inaccurate.
5695 Also stop exporting any v2 directory request statistics. Resolves
5697 - Drop support for detecting and warning about versions of Libevent
5698 before 1.3e. Nothing reasonable ships with them any longer; warning
5699 the user about them shouldn't be needed. Resolves ticket 6826.
5700 - Now that all versions before 0.2.2.x are disallowed, we no longer
5701 need to work around their missing features. Remove a bunch of
5705 - The tor-tsocks.conf is no longer distributed or installed. We
5706 recommend that tsocks users use torsocks instead. Resolves
5708 - Remove some of the older contents of doc/ as obsolete; move others
5709 to torspec.git. Fixes bug 8965.
5711 o Code simplification:
5712 - Avoid using character buffers when constructing most directory
5713 objects: this approach was unwieldy and error-prone. Instead,
5714 build smartlists of strings, and concatenate them when done.
5715 - Rename "isin" functions to "contains", for grammar. Resolves
5717 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
5718 with the natural logarithm function from the system libm. Resolves
5720 - Start using OpenBSD's implementation of queue.h, so that we don't
5721 need to hand-roll our own pointer and list structures whenever we
5722 need them. (We can't rely on a sys/queue.h, since some operating
5723 systems don't have them, and the ones that do have them don't all
5724 present the same extensions.)
5725 - Start using OpenBSD's implementation of queue.h (originally by
5727 - Enhance our internal sscanf replacement so that we can eliminate
5728 the last remaining uses of the system sscanf. (Though those uses
5729 of sscanf were safe, sscanf itself is generally error prone, so
5730 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
5732 - Replace all calls to snprintf() outside of src/ext with
5733 tor_snprintf(). Also remove the #define to replace snprintf with
5734 _snprintf on Windows; they have different semantics, and all of
5735 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
5738 - Add a wrapper function for the common "log a message with a
5740 - Split the onion.c file into separate modules for the onion queue
5741 and the different handshakes it supports.
5742 - Move the client-side address-map/virtual-address/DNS-cache code
5743 out of connection_edge.c into a new addressmap.c module.
5744 - Move the entry node code from circuitbuild.c to its own file.
5745 - Move the circuit build timeout tracking code from circuitbuild.c
5747 - Source files taken from other packages now reside in src/ext;
5748 previously they were scattered around the rest of Tor.
5749 - Move the generic "config" code into a new file, and have "config.c"
5750 hold only torrc- and state-related code. Resolves ticket 6823.
5751 - Move the core of our "choose a weighted element at random" logic
5752 into its own function, and give it unit tests. Now the logic is
5753 testable, and a little less fragile too.
5754 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
5755 - Move last_reachable and testing_since from routerinfo_t to node_t.
5756 Implements ticket 5529.
5757 - Add replaycache_t structure, functions and unit tests, then refactor
5758 rend_service_introduce() to be more clear to read, improve, debug,
5759 and test. Resolves bug 6177.
5762 - Remove some now-needless code that tried to aggressively flush
5763 OR connections as data was added to them. Since 0.2.0.1-alpha, our
5764 cell queue logic has saved us from the failure mode that this code
5765 was supposed to prevent. Removing this code will limit the number
5766 of baroque control flow paths through Tor's network logic. Reported
5767 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
5768 - Remove unused code for parsing v1 directories and "running routers"
5769 documents. Fixes bug 6887.
5770 - Remove the marshalling/unmarshalling code for sending requests to
5771 cpuworkers over a socket, and instead just send structs. The
5772 recipient will always be the same Tor binary as the sender, so
5773 any encoding is overkill.
5774 - Remove the testing_since field of node_t, which hasn't been used
5775 for anything since 0.2.0.9-alpha.
5776 - Finally remove support for malloc_good_size and malloc_usable_size.
5777 We had hoped that these functions would let us eke a little more
5778 memory out of our malloc implementation. Unfortunately, the only
5779 implementations that provided these functions are also ones that
5780 are already efficient about not overallocation: they never got us
5781 more than 7 or so bytes per allocation. Removing them saves us a
5782 little code complexity and a nontrivial amount of build complexity.
5785 Changes in version 0.2.3.25 - 2012-11-19
5786 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
5787 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
5788 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
5789 programmer, and friend. Unstinting in his dedication to the cause of
5790 freedom, he inspired and helped many of us as we began our work on
5791 anonymity, and inspires us still. Please honor his memory by writing
5792 software to protect people's freedoms, and by helping others to do so.
5794 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
5795 significantly reduced directory overhead (via microdescriptors),
5796 enormous crypto performance improvements for fast relays on new
5797 enough hardware, a new v3 TLS handshake protocol that can better
5798 resist fingerprinting, support for protocol obfuscation plugins (aka
5799 pluggable transports), better scalability for hidden services, IPv6
5800 support for bridges, performance improvements like allowing clients
5801 to skip the first round-trip on the circuit ("optimistic data") and
5802 refilling token buckets more often, a new "stream isolation" design
5803 to isolate different applications on different circuits, and many
5804 stability, security, and privacy fixes.
5806 Major features (v3 directory protocol):
5807 - Clients now use microdescriptors instead of regular descriptors
5808 to build circuits. Microdescriptors are authority-generated
5809 summaries of regular descriptors' contents, designed to change very
5810 rarely (see proposal 158 for details). This feature is designed
5811 to save bandwidth, especially for clients on slow internet
5812 connections. Use "UseMicrodescriptors 0" to disable it.
5813 - Caches now download, cache, and serve microdescriptors, as well
5814 as multiple "flavors" of the consensus, including a flavor that
5815 describes microdescriptors.
5817 o Major features (build hardening):
5818 - Enable gcc and ld hardening by default. Resolves ticket 5210.
5820 o Major features (relay scaling):
5821 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
5822 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
5823 vectorized AES implementations as appropriate. These can be much,
5824 much faster than other AES implementations.
5825 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
5826 implementation. It makes AES_CTR about 7% faster than our old one
5827 (which was about 10% faster than the one OpenSSL used to provide).
5828 Resolves ticket 4526.
5829 - Use OpenSSL's EVP interface for AES encryption, so that all AES
5830 operations can use hardware acceleration (if present). Resolves
5832 - Unconditionally use OpenSSL's AES implementation instead of our
5833 old built-in one. OpenSSL's AES has been better for a while, and
5834 relatively few servers should still be on any version of OpenSSL
5835 that doesn't have good optimized assembly AES.
5837 o Major features (blocking resistance):
5838 - Update TLS cipher list to match Firefox 8 and later. Resolves
5840 - Remove support for clients falsely claiming to support standard
5841 ciphersuites that they can actually provide. As of modern OpenSSL
5842 versions, it's not necessary to fake any standard ciphersuite,
5843 and doing so prevents us from using better ciphersuites in the
5844 future, since servers can't know whether an advertised ciphersuite
5845 is really supported or not. Some hosts -- notably, ones with very
5846 old versions of OpenSSL or where OpenSSL has been built with ECC
5847 disabled -- will stand out because of this change; TBB users should
5848 not be affected. Implements the client side of proposal 198.
5849 - Implement a new handshake protocol (v3) for authenticating Tors to
5850 each other over TLS. It should be more resistant to fingerprinting
5851 than previous protocols, and should require less TLS hacking for
5852 future Tor implementations. Implements proposal 176.
5853 - Allow variable-length padding cells, to disguise the length of
5854 Tor's TLS records. Implements part of proposal 184.
5855 - While we're trying to bootstrap, record how many TLS connections
5856 fail in each state, and report which states saw the most failures
5857 in response to any bootstrap failures. This feature may speed up
5858 diagnosis of censorship events. Implements ticket 3116.
5860 o Major features (pluggable transports):
5861 - Clients and bridges can now be configured to use a separate
5862 "transport" proxy. This approach makes the censorship arms race
5863 easier by allowing bridges to use protocol obfuscation plugins.
5864 Implements proposal 180 (tickets 2841 and 3472).
5866 o Major features (DoS resistance):
5867 - Now that Tor 0.2.0.x is completely deprecated, enable the final
5868 part of "Proposal 110: Avoiding infinite length circuits" by
5869 refusing all circuit-extend requests that do not use a relay_early
5870 cell. This change helps Tor resist a class of denial-of-service
5871 attacks by limiting the maximum circuit length.
5872 - Tear down the circuit if we get an unexpected SENDME cell. Clients
5873 could use this trick to make their circuits receive cells faster
5874 than our flow control would have allowed, or to gum up the network,
5875 or possibly to do targeted memory denial-of-service attacks on
5876 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
5877 from July 2002, before the release of Tor 0.0.0.
5879 o Major features (hidden services):
5880 - Adjust the number of introduction points that a hidden service
5881 will try to maintain based on how long its introduction points
5882 remain in use and how many introductions they handle. Fixes
5884 - Add a "tor2web mode" for clients that want to connect to hidden
5885 services non-anonymously (and possibly more quickly). As a safety
5886 measure to try to keep users from turning this on without knowing
5887 what they are doing, tor2web mode must be explicitly enabled at
5888 compile time, and a copy of Tor compiled to run in tor2web mode
5889 cannot be used as a normal Tor client. Implements feature 2553.
5891 o Major features (IPv6):
5892 - Clients can now connect to private bridges over IPv6. Bridges
5893 still need at least one IPv4 address in order to connect to
5894 other relays. Note that we don't yet handle the case where the
5895 user has two bridge lines for the same bridge (one IPv4, one
5896 IPv6). Implements parts of proposal 186.
5898 o Major features (directory authorities):
5899 - Use a more secure consensus parameter voting algorithm. Now at
5900 least three directory authorities or a majority of them must
5901 vote on a given parameter before it will be included in the
5902 consensus. Implements proposal 178.
5903 - Remove the artificially low cutoff of 20KB to guarantee the Fast
5904 flag. In the past few years the average relay speed has picked
5905 up, and while the "top 7/8 of the network get the Fast flag" and
5906 "all relays with 20KB or more of capacity get the Fast flag" rules
5907 used to have the same result, now the top 7/8 of the network has
5908 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
5910 o Major features (performance):
5911 - Exit nodes now accept and queue data on not-yet-connected streams.
5912 Previously, the client wasn't allowed to send data until the
5913 stream was connected, which slowed down all connections. This
5914 change will enable clients to perform a "fast-start" on streams
5915 and send data without having to wait for a confirmation that the
5916 stream has opened. Patch from Ian Goldberg; implements the server
5917 side of Proposal 174.
5918 - When using an exit relay running 0.2.3.x, clients can now
5919 "optimistically" send data before the exit relay reports that
5920 the stream has opened. This saves a round trip when starting
5921 connections where the client speaks first (such as web browsing).
5922 This behavior is controlled by a consensus parameter (currently
5923 disabled). To turn it on or off manually, use the "OptimisticData"
5924 torrc option. Implements proposal 181; code by Ian Goldberg.
5925 - Add a new TokenBucketRefillInterval option to refill token buckets
5926 more frequently than once per second. This should improve network
5927 performance, alleviate queueing problems, and make traffic less
5928 bursty. Implements proposal 183; closes ticket 3630. Design by
5929 Florian Tschorsch and Björn Scheuermann; implementation by
5931 - Raise the threshold of server descriptors needed (75%) and exit
5932 server descriptors needed (50%) before we will declare ourselves
5933 bootstrapped. This will make clients start building circuits a
5934 little later, but makes the initially constructed circuits less
5935 skewed and less in conflict with further directory fetches. Fixes
5938 o Major features (relays):
5939 - Relays now try regenerating and uploading their descriptor more
5940 frequently if they are not listed in the consensus, or if the
5941 version of their descriptor listed in the consensus is too
5942 old. This fix should prevent situations where a server declines
5943 to re-publish itself because it has done so too recently, even
5944 though the authorities decided not to list its recent-enough
5945 descriptor. Fix for bug 3327.
5947 o Major features (stream isolation):
5948 - You can now configure Tor so that streams from different
5949 applications are isolated on different circuits, to prevent an
5950 attacker who sees your streams as they leave an exit node from
5951 linking your sessions to one another. To do this, choose some way
5952 to distinguish the applications: have them connect to different
5953 SocksPorts, or have one of them use SOCKS4 while the other uses
5954 SOCKS5, or have them pass different authentication strings to the
5955 SOCKS proxy. Then, use the new SocksPort syntax to configure the
5956 degree of isolation you need. This implements Proposal 171.
5957 - There's a new syntax for specifying multiple client ports (such as
5958 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
5959 multiple *Port entries with full addr:port syntax on each.
5960 The old *ListenAddress format is still supported, but you can't
5961 mix it with the new *Port syntax.
5963 o Major features (bufferevents):
5964 - Tor can now optionally build with the "bufferevents" buffered IO
5965 backend provided by Libevent 2. To use this feature, make sure you
5966 have the latest possible version of Libevent, and pass the
5967 --enable-bufferevents flag to configure when building Tor from
5968 source. This feature will make our networking code more flexible,
5969 let us stack layers on each other, and let us use more efficient
5970 zero-copy transports where available.
5971 - Add experimental support for running on Windows with IOCP and no
5972 kernel-space socket buffers. This feature is controlled by a new
5973 "UserspaceIOCPBuffers" config option (off by default), which has
5974 no effect unless Tor has been built with bufferevents enabled,
5975 you're running on Windows, and you've set "DisableIOCP 0". In the
5976 long run, this may help solve or mitigate bug 98.
5978 o Major features (path selection):
5979 - The EntryNodes option can now include country codes like {de} or IP
5980 addresses or network masks. Previously we had disallowed these
5981 options because we didn't have an efficient way to keep the list up
5982 to date. Addresses ticket 1982, but see bug 2798 for an unresolved
5985 o Major features (port forwarding):
5986 - Add support for automatic port mapping on the many home routers
5987 that support NAT-PMP or UPnP. To build the support code, you'll
5988 need to have the libnatpnp library and/or the libminiupnpc library,
5989 and you'll need to enable the feature specifically by passing
5990 "--enable-upnp" and/or "--enable-natpnp" to ./configure. To turn
5991 it on, use the new PortForwarding option.
5993 o Major features (logging):
5994 - Add a new 'Heartbeat' log message type to periodically log a message
5995 describing Tor's status at level Notice. This feature is meant for
5996 operators who log at notice, and want to make sure that their Tor
5997 server is still working. Implementation by George Kadianakis.
5998 - Make logging resolution configurable with a new LogTimeGranularity
5999 option, and change the default from 1 millisecond to 1 second.
6000 Implements enhancement 1668.
6002 o Major features (other):
6003 - New "DisableNetwork" config option to prevent Tor from launching any
6004 connections or accepting any connections except on a control port.
6005 Bundles and controllers can set this option before letting Tor talk
6006 to the rest of the network, for example to prevent any connections
6007 to a non-bridge address. Packages like Orbot can also use this
6008 option to instruct Tor to save power when the network is off.
6009 - Try to use system facilities for enumerating local interface
6010 addresses, before falling back to our old approach (which was
6011 binding a UDP socket, and calling getsockname() on it). That
6012 approach was scaring OS X users whose draconian firewall
6013 software warned about binding to UDP sockets regardless of
6014 whether packets were sent. Now we try to use getifaddrs(),
6015 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
6016 system supports. Resolves ticket 1827.
6017 - Add experimental support for a "defaults" torrc file to be parsed
6018 before the regular torrc. Torrc options override the defaults file's
6019 options in the same way that the command line overrides the torrc.
6020 The SAVECONF controller command saves only those options which
6021 differ between the current configuration and the defaults file. HUP
6022 reloads both files. Implements task 4552.
6024 o New directory authorities:
6025 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
6026 authority. Closes ticket 5749.
6028 o Security/privacy fixes:
6029 - Avoid read-from-freed-memory and double-free bugs that could occur
6030 when a DNS request fails while launching it. Fixes bug 6480;
6031 bugfix on 0.2.0.1-alpha.
6032 - Reject any attempt to extend to an internal address. Without
6033 this fix, a router could be used to probe addresses on an internal
6034 network to see whether they were accepting connections. Fixes bug
6035 6710; bugfix on 0.0.8pre1.
6036 - Close any connection that sends unrecognized junk before the TLS
6037 handshake. Solves an issue noted in bug 4369.
6038 - The advertised platform of a relay now includes only its operating
6039 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not
6040 its service pack level (for Windows) or its CPU architecture
6041 (for Unix). Also drop the "git-XYZ" tag in the version. Packagers
6042 can insert an extra string in the platform line by setting the
6043 preprocessor variable TOR_BUILD_TAG. Resolves bug 2988.
6044 - Disable TLS session tickets. OpenSSL's implementation was giving
6045 our TLS session keys the lifetime of our TLS context objects, when
6046 perfect forward secrecy would want us to discard anything that
6047 could decrypt a link connection as soon as the link connection
6048 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
6049 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
6050 - Tor tries to wipe potentially sensitive data after using it, so
6051 that if some subsequent security failure exposes Tor's memory,
6052 the damage will be limited. But we had a bug where the compiler
6053 was eliminating these wipe operations when it decided that the
6054 memory was no longer visible to a (correctly running) program,
6055 hence defeating our attempt at defense in depth. We fix that
6056 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
6057 is unlikely to optimize away. Future versions of Tor may use
6058 a less ridiculously heavy approach for this. Fixes bug 7352.
6059 Reported in an article by Andrey Karpov.
6061 o Major bugfixes (crashes and asserts):
6062 - Avoid a pair of double-free and use-after-mark bugs that can
6063 occur with certain timings in canceled and re-received DNS
6064 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
6065 - Fix a denial of service attack by which any directory authority
6066 could crash all the others, or by which a single v2 directory
6067 authority could crash everybody downloading v2 directory
6068 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
6069 - Fix an assert that directory authorities could trigger on sighup
6070 during some configuration state transitions. We now don't treat
6071 it as a fatal error when the new descriptor we just generated in
6072 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
6073 - Avoid segfault when starting up having run with an extremely old
6074 version of Tor and parsing its state file. Fixes bug 6801; bugfix
6077 o Major bugfixes (clients):
6078 - If we are unable to find any exit that supports our predicted ports,
6079 stop calling them predicted, so that we don't loop and build
6080 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
6081 which introduced predicted ports.
6082 - Check at each new consensus whether our entry guards were picked
6083 long enough ago that we should rotate them. Previously, we only
6084 did this check at startup, which could lead to us holding a guard
6085 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
6086 - When fetching a bridge descriptor from a bridge authority,
6087 always do so anonymously, whether we have been able to open
6088 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
6089 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
6090 but we'll need to wait for bug 6010 before it's actually usable.
6092 o Major bugfixes (directory voting):
6093 - Check more thoroughly to prevent a rogue authority from
6094 double-voting on any consensus directory parameter. Previously,
6095 authorities would crash in this case if the total number of
6096 votes for any parameter exceeded the number of active voters,
6097 but would let it pass otherwise. Partially fixes bug 5786; bugfix
6099 - When computing weight parameters, behave more robustly in the
6100 presence of a bad bwweightscale value. Previously, the authorities
6101 would crash if they agreed on a sufficiently broken weight_scale
6102 value; now, they use a reasonable default and carry on. Fixes the
6103 rest of bug 5786; bugfix on 0.2.2.17-alpha.
6104 - If authorities are unable to get a v2 consensus document from other
6105 directory authorities, they no longer fall back to fetching
6106 them from regular directory caches. Fixes bug 5635; bugfix on
6107 0.2.2.26-beta, where routers stopped downloading v2 consensus
6110 o Major bugfixes (relays):
6111 - Fix a bug handling SENDME cells on nonexistent streams that could
6112 result in bizarre window values. Report and patch contributed
6113 pseudonymously. Fixes part of bug 6271. This bug was introduced
6114 before the first Tor release, in svn commit r152.
6115 - Don't update the AccountingSoftLimitHitAt state file entry whenever
6116 tor gets started. This prevents a wrong average bandwidth
6117 estimate, which would cause relays to always start a new accounting
6118 interval at the earliest possible moment. Fixes bug 2003; bugfix
6119 on 0.2.2.7-alpha. Reported by Bryon Eldridge, who also helped
6120 immensely in tracking this bug down.
6121 - Fix a possible crash bug when checking for deactivated circuits
6122 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
6123 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
6124 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
6125 connections. This change should allow busy exit relays to stop
6126 running out of available sockets as quickly. Fixes bug 4950;
6127 bugfix on 0.2.2.26-beta.
6129 o Major bugfixes (blocking resistance):
6130 - Bridges no longer include their address in NETINFO cells on outgoing
6131 OR connections, to allow them to blend in better with clients.
6132 Removes another avenue for enumerating bridges. Reported by
6133 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
6134 cells were introduced.
6135 - Warn the user when HTTPProxy, but no other proxy type, is
6136 configured. This can cause surprising behavior: it doesn't send
6137 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
6138 directory traffic only. Resolves ticket 4663.
6140 o Major bugfixes (hidden services):
6141 - Improve hidden service robustness: when an attempt to connect to
6142 a hidden service ends, be willing to refetch its hidden service
6143 descriptors from each of the HSDir relays responsible for them
6144 immediately. Previously, we would not consider refetching the
6145 service's descriptors from each HSDir for 15 minutes after the last
6146 fetch, which was inconvenient if the hidden service was not running
6147 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
6148 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
6149 They used to check that the timestamp was within 30 minutes
6150 of their system clock, so they could cap the size of their
6151 replay-detection cache, but that approach unnecessarily refused
6152 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
6153 the v3 intro-point protocol (the first one which sent a timestamp
6154 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
6155 - When one of a hidden service's introduction points appears to be
6156 unreachable, stop trying it. Previously, we would keep trying
6157 to build circuits to the introduction point until we lost the
6158 descriptor, usually because the user gave up and restarted Tor.
6159 Fixes part of bug 3825.
6161 o Changes to default torrc file:
6162 - Stop listing "socksport 9050" in torrc.sample. We open a socks
6163 port on 9050 by default anyway, so this should not change anything
6165 - Stop mentioning the deprecated *ListenAddress options in
6166 torrc.sample. Fixes bug 5438.
6167 - Document unit of bandwidth-related options in sample torrc.
6169 - Fix broken URLs in the sample torrc file, and tell readers about
6170 the OutboundBindAddress, ExitPolicyRejectPrivate, and
6171 PublishServerDescriptor options. Addresses bug 4652.
6173 o Minor features (directory authorities):
6174 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
6175 change when the authority is deciding whether to accept a newly
6176 uploaded descriptor. Implements ticket 6423.
6177 - Directory authorities are now a little more lenient at accepting
6178 older router descriptors, or newer router descriptors that don't
6179 make big changes. This should help ameliorate past and future
6180 issues where routers think they have uploaded valid descriptors,
6181 but the authorities don't think so. Fix for ticket 2479.
6182 - Authority operators can now vote for all relays in a given
6183 set of countries to be BadDir/BadExit/Invalid/Rejected.
6184 - Provide two consensus parameters (FastFlagMinThreshold and
6185 FastFlagMaxThreshold) to control the range of allowable bandwidths
6186 for the Fast directory flag. These allow authorities to run
6187 experiments on appropriate requirements for being a "Fast" node.
6188 The AuthDirFastGuarantee config value still applies. Implements
6191 o Minor features (bridges / bridge authorities):
6192 - Make bridge SSL certificates a bit more stealthy by using random
6193 serial numbers, in the same fashion as OpenSSL when generating
6194 self-signed certificates. Implements ticket 4584.
6195 - Tag a bridge's descriptor as "never to be sent unencrypted".
6196 This shouldn't matter, since bridges don't open non-anonymous
6197 connections to the bridge authority and don't allow unencrypted
6198 directory connections from clients, but we might as well make
6199 sure. Closes bug 5139.
6200 - The Bridge Authority now writes statistics on how many bridge
6201 descriptors it gave out in total, and how many unique descriptors
6202 it gave out. It also lists how often the most and least commonly
6203 fetched descriptors were given out, as well as the median and
6204 25th/75th percentile. Implements tickets 4200 and 4294.
6206 o Minor features (IPv6):
6207 - Make the code that clients use to detect an address change be
6208 IPv6-aware, so that it won't fill clients' logs with error
6209 messages when trying to get the IPv4 address of an IPv6
6210 connection. Implements ticket 5537.
6211 - Relays now understand an IPv6 address when they get one from a
6212 directory server. Resolves ticket 4875.
6214 o Minor features (hidden services):
6215 - Expire old or over-used hidden service introduction points.
6216 Required by fix for bug 3460.
6217 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
6218 public key replay-detection cache from 60 minutes to 5 minutes. This
6219 replay-detection cache is now used only to detect multiple
6220 INTRODUCE2 cells specifying the same rendezvous point, so we can
6221 avoid launching multiple simultaneous attempts to connect to it.
6222 - When a hidden service's introduction point times out, consider
6223 trying it again during the next attempt to connect to the
6224 HS. Previously, we would not try it again unless a newly fetched
6225 descriptor contained it. Required by fixes for bugs 1297 and 3825.
6227 o Minor features (relays):
6228 - Relays now include a reason for regenerating their descriptors
6229 in an HTTP header when uploading to the authorities. This will
6230 make it easier to debug descriptor-upload issues in the future.
6231 - Turn on directory request statistics by default and include them in
6232 extra-info descriptors. Don't break if we have no GeoIP database.
6233 - Replace files in stats/ rather than appending to them. Now that we
6234 include statistics in extra-info descriptors, it makes no sense to
6235 keep old statistics forever. Implements ticket 2930.
6236 - Relays that set "ConnDirectionStatistics 1" write statistics on the
6237 bidirectional use of connections to disk every 24 hours.
6238 - Add a GeoIP file digest to the extra-info descriptor. Implements
6241 o Minor features (new config options):
6242 - New config option "DynamicDHGroups" (disabled by default) provides
6243 each bridge with a unique prime DH modulus to be used during
6244 SSL handshakes. This option attempts to help against censors
6245 who might use the Apache DH modulus as a static identifier for
6246 bridges. Addresses ticket 4548.
6247 - New config option "DisableDebuggerAttachment" (on by default)
6248 to prevent basic debugging attachment attempts by other processes.
6249 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
6250 - Ordinarily, Tor does not count traffic from private addresses (like
6251 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
6252 There is now a new option, CountPrivateBandwidth, to disable this
6253 behavior. Patch from Daniel Cagara.
6255 o Minor features (different behavior for old config options):
6256 - Allow MapAddress directives to specify matches against super-domains,
6257 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
6258 Implements issue 933.
6259 - Don't disable the DirPort when we cannot exceed our AccountingMax
6260 limit during this interval because the effective bandwidthrate is
6261 low enough. This is useful in a situation where AccountMax is only
6262 used as an additional safeguard or to provide statistics.
6263 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
6264 implements ticket 3439.
6265 - When configuring a large set of nodes in EntryNodes, and there are
6266 enough of them listed as Guard so that we don't need to consider
6267 the non-guard entries, prefer the ones listed with the Guard flag.
6268 - If you set the NumCPUs option to 0, Tor will now try to detect how
6269 many CPUs you have. This is the new default behavior.
6270 - The NodeFamily option -- which let you declare that you want to
6271 consider nodes to be part of a family whether they list themselves
6272 that way or not -- now allows IP address ranges and country codes.
6274 o Minor features (new command-line config behavior):
6275 - Slightly change behavior of "list" options (that is, config
6276 options that can appear more than once) when they appear both in
6277 torrc and on the command line. Previously, the command-line options
6278 would be appended to the ones from torrc. Now, the command-line
6279 options override the torrc options entirely. This new behavior
6280 allows the user to override list options (like exit policies and
6281 ports to listen on) from the command line, rather than simply
6282 appending to the list.
6283 - You can get the old (appending) command-line behavior for "list"
6284 options by prefixing the option name with a "+".
6285 - You can remove all the values for a "list" option from the command
6286 line without adding any new ones by prefixing the option name
6289 o Minor features (controller, new events):
6290 - Extend the control protocol to report flags that control a circuit's
6291 path selection in CIRC events and in replies to 'GETINFO
6292 circuit-status'. Implements part of ticket 2411.
6293 - Extend the control protocol to report the hidden service address
6294 and current state of a hidden-service-related circuit in CIRC
6295 events and in replies to 'GETINFO circuit-status'. Implements part
6297 - Include the creation time of a circuit in CIRC and CIRC2
6298 control-port events and the list produced by the 'GETINFO
6299 circuit-status' control-port command.
6300 - Add a new CONF_CHANGED event so that controllers can be notified
6301 of any configuration changes made by other controllers, or by the
6302 user. Implements ticket 1692.
6303 - Add a new SIGNAL event to the controller interface so that
6304 controllers can be notified when Tor handles a signal. Resolves
6305 issue 1955. Patch by John Brooks.
6307 o Minor features (controller, new getinfo options):
6308 - Expose our view of whether we have gone dormant to the controller,
6309 via a new "GETINFO dormant" value. Torbutton and other controllers
6310 can use this to avoid doing periodic requests through Tor while
6311 it's dormant (bug 4718). Resolves ticket 5954.
6312 - Add a new GETINFO option to get total bytes read and written. Patch
6313 from pipe, revised by atagar. Resolves ticket 2345.
6314 - Implement new GETINFO controller fields to provide information about
6315 the Tor process's pid, euid, username, and resource limits.
6317 o Minor features (controller, other):
6318 - Allow controllers to request an event notification whenever a
6319 circuit is cannibalized or its purpose is changed. Implements
6320 part of ticket 3457.
6321 - Use absolute path names when reporting the torrc filename in the
6322 control protocol, so a controller can more easily find the torrc
6323 file. Resolves bug 1101.
6324 - When reporting the path to the cookie file to the controller,
6325 give an absolute path. Resolves ticket 4881.
6327 o Minor features (log messages):
6328 - Add more information to a log statement that might help track down
6329 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
6330 non-IP address" messages (or any Bug messages, for that matter!),
6331 please let us know about it.
6332 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
6333 EntryNodes will have no effect. Resolves issue 2571.
6334 - Try to make the introductory warning message that Tor prints on
6335 startup more useful for actually finding help and information.
6336 Resolves ticket 2474.
6337 - When the system call to create a listener socket fails, log the
6338 error message explaining why. This may help diagnose bug 4027.
6340 o Minor features (other):
6341 - When we fail to initialize Libevent, retry with IOCP disabled so we
6342 don't need to turn on multi-threading support in Libevent, which in
6343 turn requires a working socketpair(). This is a workaround for bug
6344 4457, which affects Libevent versions from 2.0.1-alpha through
6346 - When starting as root and then changing our UID via the User
6347 control option, and we have a ControlSocket configured, make sure
6348 that the ControlSocket is owned by the same account that Tor will
6349 run under. Implements ticket 3421; fix by Jérémy Bobbio.
6350 - Accept attempts to include a password authenticator in the
6351 handshake, as supported by SOCKS5. This handles SOCKS clients that
6352 don't know how to omit a password when authenticating. Resolves
6354 - Check for and recover from inconsistency in the microdescriptor
6355 cache. This will make it harder for us to accidentally free a
6356 microdescriptor without removing it from the appropriate data
6357 structures. Fixes issue 3135; issue noted by "wanoskarnet".
6358 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
6360 o Minor bugfixes (code security):
6361 - Prevent a null-pointer dereference when receiving a data cell
6362 for a nonexistent stream when the circuit in question has an
6363 empty deliver window. We don't believe this is triggerable,
6364 since we don't currently allow deliver windows to become empty,
6365 but the logic is tricky enough that it's better to make the code
6366 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
6367 - Fix a (harmless) integer overflow in cell statistics reported by
6368 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
6369 - Fix our implementation of crypto_random_hostname() so it can't
6370 overflow on ridiculously large inputs. (No Tor version has ever
6371 provided this kind of bad inputs, but let's be correct in depth.)
6372 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
6373 - Add a (probably redundant) memory clear between iterations of
6374 the router status voting loop, to prevent future coding errors
6375 where data might leak between iterations of the loop. Resolves
6378 o Minor bugfixes (wrapper functions):
6379 - Abort if tor_vasprintf() fails in connection_printf_to_buf() (a
6380 utility function used in the control-port code). This shouldn't
6381 ever happen unless Tor is completely out of memory, but if it did
6382 happen and Tor somehow recovered from it, Tor could have sent a log
6383 message to a control port in the middle of a reply to a controller
6384 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
6385 - Fix some (not actually triggerable) buffer size checks in usage of
6386 tor_inet_ntop(). Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
6388 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
6389 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
6390 - Enforce correct return behavior of tor_vsscanf() when the '%%'
6391 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
6392 - Make our replacement implementation of strtok_r() compatible with
6393 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
6394 bugfix on 0.2.2.1-alpha.
6395 - Find more places in the code that should have been testing for
6396 invalid sockets using the SOCKET_OK macro. Required for a fix
6397 for bug 4533. Bugfix on 0.2.2.28-beta.
6399 o Minor bugfixes (code correctness):
6400 - Check return value of fputs() when writing authority certificate
6401 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
6402 - When building Tor on Windows with -DUNICODE (not default), ensure
6403 that error messages, filenames, and DNS server names are always
6404 NUL-terminated when we convert them to a single-byte encoding.
6405 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
6406 - Fix a memory leak when trying to launch a DNS request when the
6407 nameservers are unconfigurable. Fixes bug 5916; bugfix on Tor
6409 - Correct file sizes when reading binary files on Cygwin, to avoid
6410 a bug where Tor would fail to read its state file. Fixes bug 6844;
6411 bugfix on 0.1.2.7-alpha.
6412 - Make sure to set *socket_error in all error cases in
6413 connection_connect(), so it can't produce a warning about
6414 errno being zero from errno_to_orconn_end_reason(). Bugfix on
6415 0.2.1.1-alpha; resolves ticket 6028.
6416 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
6417 bug 4532; found by "troll_un".
6419 o Minor bugfixes (clients):
6420 - Allow one-hop directory-fetching circuits the full "circuit build
6421 timeout" period, rather than just half of it, before failing them
6422 and marking the relay down. This fix should help reduce cases where
6423 clients declare relays (or worse, bridges) unreachable because
6424 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
6425 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
6427 - Ensure we don't cannibalize circuits that are longer than three hops
6428 already, so we don't end up making circuits with 5 or more
6429 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
6430 0.1.0.1-rc which introduced cannibalization.
6432 o Minor bugfixes (relays):
6433 - Don't publish a new relay descriptor when we reload our onion key,
6434 unless the onion key has actually changed. Fixes bug 3263 and
6435 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
6436 - When relays refuse a "create" cell because their queue of pending
6437 create cells is too big (typically because their cpu can't keep up
6438 with the arrival rate), send back reason "resource limit" rather
6439 than reason "internal", so network measurement scripts can get a
6440 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
6441 - Exit nodes don't need to fetch certificates for authorities that
6442 they don't recognize; only directory authorities, bridges,
6443 and caches need to do that. Fixes part of bug 2297; bugfix on
6446 o Minor bugfixes (directory authority / mirrors):
6447 - Avoid O(n^2) performance characteristics when parsing a large
6448 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
6449 - Authorities no longer include any router in their microdescriptor
6450 consensuses for which they couldn't generate or agree on a
6451 microdescriptor. Fixes the second piece of bug 6404; fix on
6453 - When checking for requested signatures on the latest consensus
6454 before serving it to a client, make sure to check the right
6455 consensus flavor. Bugfix on 0.2.2.6-alpha.
6456 - Fix an edge case where TestingTorNetwork is set but the authorities
6457 and relays all have an uptime of zero, so the private Tor network
6458 could briefly lack support for hidden services. Fixes bug 3886;
6459 bugfix on 0.2.2.18-alpha.
6460 - Directory caches no longer refuse to clean out descriptors because
6461 of missing v2 networkstatus documents, unless they're configured
6462 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
6463 0.2.2.26-beta. Patch by Daniel Bryg.
6464 - Don't serve or accept v2 hidden service descriptors over a relay's
6465 DirPort. It's never correct to do so, and disabling it might
6466 make it more annoying to exploit any bugs that turn up in the
6467 descriptor-parsing code. Fixes bug 7149.
6469 o Minor bugfixes (hidden services, client-side):
6470 - Assert that hidden-service-related operations are not performed
6471 using single-hop circuits. Previously, Tor would assert that
6472 client-side streams are not attached to single-hop circuits,
6473 but not that other sensitive operations on the client and service
6474 side are not performed using single-hop circuits. Fixes bug 3332;
6476 - Avoid undefined behavior when parsing the list of supported
6477 rendezvous/introduction protocols in a hidden service descriptor.
6478 Previously, Tor would have confused (as-yet-unused) protocol version
6479 numbers greater than 32 with lower ones on many platforms. Fixes
6480 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
6481 - Don't close hidden service client circuits which have almost
6482 finished connecting to their destination when they reach
6483 the normal circuit-build timeout. Previously, we would close
6484 introduction circuits which are waiting for an acknowledgement
6485 from the introduction point, and rendezvous circuits which have
6486 been specified in an INTRODUCE1 cell sent to a hidden service,
6487 after the normal CBT. Now, we mark them as 'timed out', and launch
6488 another rendezvous attempt in parallel. This behavior change can
6489 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
6490 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
6492 o Minor bugfixes (hidden services, service-side):
6493 - Don't close hidden-service-side rendezvous circuits when they
6494 reach the normal circuit-build timeout. This behavior change can
6495 be disabled using the new
6496 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
6497 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
6498 - Don't launch more than 10 service-side introduction-point circuits
6499 for a hidden service in five minutes. Previously, we would consider
6500 launching more introduction-point circuits if at least one second
6501 had passed without any introduction-point circuits failing. Fixes
6502 bug 4607; bugfix on 0.0.7pre1.
6504 o Minor bugfixes (config option behavior):
6505 - If the user tries to set MyFamily on a bridge, refuse to
6506 do so, and warn about the security implications. Fixes bug 4657;
6507 bugfix on 0.2.0.3-alpha.
6508 - The "--quiet" and "--hush" options now apply not only to Tor's
6509 behavior before logs are configured, but also to Tor's behavior in
6510 the absense of configured logs. Fixes bug 3550; bugfix on
6512 - Change the AllowDotExit rules so they should actually work.
6513 We now enforce AllowDotExit only immediately after receiving an
6514 address via SOCKS or DNSPort: other sources are free to provide
6515 .exit addresses after the resolution occurs. Fixes bug 3940;
6516 bugfix on 0.2.2.1-alpha.
6517 - Make "LearnCircuitBuildTimeout 0" work more reliably. Specifically,
6518 don't depend on the consensus parameters or compute adaptive
6519 timeouts when it is disabled. Fixes bug 5049; bugfix on
6521 - After we pick a directory mirror, we would refuse to use it if
6522 it's in our ExcludeExitNodes list, resulting in mysterious failures
6523 to bootstrap for people who just wanted to avoid exiting from
6524 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
6525 - When told to add a bridge with the same digest as a preexisting
6526 bridge but a different addr:port, change the addr:port as
6527 requested. Previously we would not notice the change. Fixes half
6528 of bug 5603; fix on 0.2.2.26-beta.
6530 o Minor bugfixes (controller):
6531 - Allow manual 'authenticate' commands to the controller interface
6532 from netcat (nc) as well as telnet. We were rejecting them because
6533 they didn't come with the expected whitespace at the end of the
6534 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
6535 - Report a real bootstrap problem to the controller on router
6536 identity mismatch. Previously we just said "foo", which probably
6537 made a lot of sense at the time. Fixes bug 4169; bugfix on
6539 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
6540 option is set to 0 (which Vidalia version 0.2.16 now does when
6541 a SAVECONF attempt fails), perform other actions that SIGHUP
6542 usually causes (like reopening the logs). Fixes bug 5095; bugfix
6544 - Correctly handle checking the permissions on the parent
6545 directory of a control socket in the root directory. Bug found
6546 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
6548 - End AUTHCHALLENGE error messages (in the control protocol) with
6549 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36.
6551 o Minor bugfixes (network reading/writing):
6552 - Disable writing on marked-for-close connections when they are
6553 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
6554 bug 5263; bugfix on 0.0.2pre13, where we first added a special
6555 case for flushing marked connections.
6556 - Make sure that there are no unhandled pending TLS errors before
6557 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
6558 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
6559 Bugfix on 0.1.0.5-rc; fixes bug 4528.
6560 - Detect SSL handshake even when the initial attempt to write the
6561 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
6562 - If the client fails to set a reasonable set of ciphersuites
6563 during its v2 handshake renegotiation, allow the renegotiation to
6564 continue nevertheless (i.e. send all the required certificates).
6565 Fixes bug 4591; bugfix on 0.2.0.20-rc.
6567 o Minor bugfixes (other):
6568 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
6569 resource exhaustion, so that clients can adjust their load to
6570 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
6571 started using END_STREAM_REASON_RESOURCELIMIT.
6572 - Don't check for whether the address we're using for outbound
6573 connections has changed until after the outbound connection has
6574 completed. On Windows, getsockname() doesn't succeed until the
6575 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
6576 - Don't hold a Windows file handle open for every file mapping;
6577 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
6579 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
6580 bugfix on 0.2.1.10-alpha.
6581 - If we fail to write a microdescriptor to the disk cache, do not
6582 continue replacing the old microdescriptor file. Fixes bug 2954;
6583 bugfix on 0.2.2.6-alpha.
6585 o Minor bugfixes (log messages, path selection):
6586 - Downgrade "set buildtimeout to low value" messages to "info"
6587 severity; they were never an actual problem, there was never
6588 anything reasonable to do about them, and they tended to spam logs
6589 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
6590 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
6591 more information to it, so that we can track it down in case it
6592 returns again. Mitigates bug 5235.
6593 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
6594 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
6595 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
6596 - Issue a log message if a guard completes less than 40% of your
6597 circuits. Threshold is configurable by torrc option
6598 PathBiasNoticeRate and consensus parameter pb_noticepct. There is
6599 additional, off-by-default code to disable guards which fail too
6600 many circuits. Addresses ticket 5458.
6602 o Minor bugfixes (log messages, client):
6603 - Downgrade "Got a certificate, but we already have it" log messages
6604 from warning to info, except when we're a dirauth. Fixes bug 5238;
6605 bugfix on 0.2.1.7-alpha.
6606 - Fix the log message describing how we work around discovering
6607 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
6608 4837; bugfix on 0.2.2.9-alpha.
6609 - When logging about a disallowed .exit name, do not also call it
6610 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
6611 - Fix a log message suggesting that people contact a non-existent
6612 email address. Fixes bug 3448.
6613 - Rephrase the log message emitted if the TestSocks check is
6614 successful. Patch from Fabian Keil; fixes bug 4094.
6615 - Log (at debug level) whenever a circuit's purpose is changed.
6616 - Log SSL state transitions at log level DEBUG, log domain
6617 HANDSHAKE. This can be useful for debugging censorship events.
6618 Implements ticket 3264.
6619 - We now log which torrc file we're using on startup. Implements
6621 - Rate-limit log messages when asked to connect anonymously to
6622 a private address. When these hit, they tended to hit fast and
6623 often. Also, don't bother trying to connect to addresses that we
6624 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
6625 reply makes us think we have been lied to, even when the address the
6626 client tried to connect to was "localhost." Resolves ticket 2822.
6628 o Minor bugfixes (log messages, non-client):
6629 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
6630 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
6631 - Don't log that we have "decided to publish new relay descriptor"
6632 unless we are actually publishing a descriptor. Fixes bug 3942;
6633 bugfix on 0.2.2.28-beta.
6634 - Log which authority we're missing votes from when we go to fetch
6635 them from the other auths.
6636 - Replace "Sending publish request" log messages with "Launching
6637 upload", so that they no longer confusingly imply that we're
6638 sending something to a directory we might not even be connected
6639 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
6640 - Warn when Tor is configured to use accounting in a way that can
6641 link a hidden service to some other hidden service or public
6642 address. Resolves ticket 6490.
6643 - Fix a minor formatting issue in one of tor-gencert's error messages.
6647 - Update to the latest version of the tinytest unit testing framework.
6648 This includes a couple of bugfixes that can be relevant for
6649 running forked unit tests on Windows, and removes all reserved
6651 - Avoid a false positive in the util/threads unit test by increasing
6652 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
6653 - Make it possible to set the TestingTorNetwork configuration
6654 option using AlternateDirAuthority and AlternateBridgeAuthority
6655 as an alternative to setting DirServer. Addresses ticket 6377.
6656 - Add a unit test for the environment_variable_names_equal() function.
6657 - A wide variety of new unit tests by Esteban Manchado Velázquez.
6658 - Numerous new unit tests for functions in util.c and address.c by
6660 - The long-disabled benchmark tests are now split into their own
6661 ./src/test/bench binary.
6662 - The benchmark tests can now use more accurate timers than
6663 gettimeofday() when such timers are available.
6664 - Use tt_assert(), not tor_assert(), for checking for test failures.
6665 This makes the unit tests more able to go on in the event that
6668 o Build improvements:
6669 - Use the dead_strip option when building Tor on OS X. This reduces
6670 binary size by almost 19% when linking openssl and libevent
6671 statically, which we do for Tor Browser Bundle.
6672 - Provide a better error message about possible OSX Asciidoc failure
6673 reasons. Fixes bug 6436.
6674 - Detect attempts to build Tor on (as yet hypothetical) versions
6675 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
6676 fix for bug 4533. Bugfix on 0.2.2.28-beta.
6677 - On Windows, we now define the _WIN32_WINNT macros only if they
6678 are not already defined. This lets the person building Tor decide,
6679 if they want, to require a later version of Windows.
6680 - Our autogen.sh script now uses autoreconf to launch autoconf,
6681 automake, and so on. This is more robust against some of the failure
6682 modes associated with running the autotools pieces on their own.
6683 - Running "make version" now displays the version of Tor that
6684 we're about to build. Idea from katmagic; resolves issue 4400.
6685 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
6686 on 0.2.2.4-alpha; fixes bug 3427.
6687 - New --enable-static-tor configure option for building Tor as
6688 statically as possible. Idea, general hackery and thoughts from
6689 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
6691 - Limited, experimental support for building with nmake and MSVC.
6693 o Build requirements:
6694 - Building Tor with bufferevent support now requires Libevent
6695 2.0.13-stable or later. Previous versions of Libevent had bugs in
6696 SSL-related bufferevents and related issues that would make Tor
6697 work badly with bufferevents. Requiring 2.0.13-stable also allows
6698 Tor with bufferevents to take advantage of Libevent APIs
6699 introduced after 2.0.8-rc.
6700 - Our build system requires automake 1.6 or later to create the
6701 Makefile.in files. Previously, you could have used 1.4.
6702 This only affects developers and people building Tor from git;
6703 people who build Tor from the source distribution without changing
6704 the Makefile.am files should be fine.
6705 - Detect when we try to build on a platform that doesn't define
6706 AF_UNSPEC to 0. We don't work there, so refuse to compile.
6708 o Build fixes (compile/link):
6709 - Format more doubles with %f, not %lf. Patch from grarpamp to make
6710 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
6712 - When building with --enable-static-tor on OpenBSD, do not
6713 erroneously attempt to link -lrt. Fixes bug 5103.
6714 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
6715 that IPv6 stuff will compile on MSVC, and compilation issues
6716 will be easier to track down. Fixes bug 5861.
6717 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
6718 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
6719 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
6720 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
6722 o Build fixes (other):
6723 - Use the _WIN32 macro throughout our code to detect Windows.
6724 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
6726 - Properly handle the case where the build-tree is not the same
6727 as the source tree when generating src/common/common_sha1.i,
6728 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
6729 bugfix on 0.2.0.1-alpha.
6730 - During configure, search for library containing cos function as
6731 libm lives in libcore on some platforms (BeOS/Haiku). Linking
6732 against libm was hard-coded before. Fixes the first part of bug
6733 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
6735 - Prevent a false positive from the check-spaces script, by disabling
6736 the "whitespace between function name and (" check for functions
6739 o Packaging (RPM) changes:
6740 - Update our default RPM spec files to work with mock and rpmbuild
6741 on RHEL/Fedora. They have an updated set of dependencies and
6742 conflicts, a fix for an ancient typo when creating the "_tor"
6743 user, and better instructions. Thanks to Ondrej Mikle for the
6744 patch series. Fixes bug 6043.
6745 - On OpenSUSE, create the /var/run/tor directory on startup if it
6746 is not already created. Patch from Andreas Stieger. Fixes bug 2573.
6748 o Code refactoring (safety):
6749 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
6750 10 lines. Also, don't nest them. Doing so in the past has
6751 led to hard-to-debug code. The new style is to use the
6752 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
6753 - Use macros to indicate OpenSSL versions, so we don't need to worry
6754 about accidental hexadecimal bit shifts.
6755 - Use tor_sscanf() in place of scanf() in more places through the
6756 code. This makes us a little more locale-independent, and
6757 should help shut up code-analysis tools that can't tell
6758 a safe sscanf string from a dangerous one.
6759 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
6760 - Use the smartlist_add_asprintf() alias more consistently.
6762 o Code refactoring (consolidate):
6763 - A major revision to our internal node-selecting and listing logic.
6764 Tor already had at least two major ways to look at the question of
6765 "which Tor servers do we know about": a list of router descriptors,
6766 and a list of entries in the current consensus. With
6767 microdescriptors, we're adding a third. Having so many systems
6768 without an abstraction layer over them was hurting the codebase.
6769 Now, we have a new "node_t" abstraction that presents a consistent
6770 interface to a client's view of a Tor node, and holds (nearly) all
6771 of the mutable state formerly in routerinfo_t and routerstatus_t.
6772 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
6773 Libevent's notion of cached time when possible.
6774 - Remove duplicate code for invoking getrlimit() from control.c.
6775 - Use OpenSSL's built-in SSL_state_string_long() instead of our
6776 own homebrewed ssl_state_to_string() replacement. Patch from
6777 Emile Snyder. Fixes bug 4653.
6778 - Change the symmetric cipher interface so that creating and
6779 initializing a stream cipher are no longer separate functions.
6781 o Code refactoring (separate):
6782 - Make a new "entry connection" struct as an internal subtype of "edge
6783 connection", to simplify the code and make exit connections smaller.
6784 - Split connection_about_to_close() into separate functions for each
6786 - Rewrite the listener-selection logic so that parsing which ports
6787 we want to listen on is now separate from binding to the ports
6790 o Code refactoring (name changes):
6791 - Rename a handful of old identifiers, mostly related to crypto
6792 structures and crypto functions. By convention, our "create an
6793 object" functions are called "type_new()", our "free an object"
6794 functions are called "type_free()", and our types indicate that
6795 they are types only with a final "_t". But a handful of older
6796 types and functions broke these rules, with function names like
6797 "type_create" or "subsystem_op_type", or with type names like
6799 - Rename Tor functions that turn strings into addresses, so that
6800 "parse" indicates that no hostname resolution occurs, and
6801 "lookup" indicates that hostname resolution may occur. This
6802 should help prevent mistakes in the future. Fixes bug 3512.
6803 - Use the name "CERTS" consistently to refer to the new cell type;
6804 we were calling it CERT in some places and CERTS in others.
6805 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
6806 invalid value, rather than just -1.
6807 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
6808 can pick them up when the tests aren't disabled. Bugfix on
6809 0.2.2.4-alpha which introduced tinytest.
6811 o Code refactoring (other):
6812 - Defensively refactor rend_mid_rendezvous() so that protocol
6813 violations and length checks happen in the beginning. Fixes
6815 - Remove the pure attribute from all functions that used it
6816 previously. In many cases we assigned it incorrectly, because the
6817 functions might assert or call impure functions, and we don't have
6818 evidence that keeping the pure attribute is worthwhile. Implements
6819 changes suggested in ticket 4421.
6820 - Move the replay-detection cache for the RSA-encrypted parts of
6821 INTRODUCE2 cells to the introduction point data structures.
6822 Previously, we would use one replay-detection cache per hidden
6823 service. Required by fix for bug 3460.
6824 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
6825 no longer link against Libevent: they never used it, but
6826 our library structure used to force them to link it.
6828 o Removed features and files:
6829 - Remove all internal support for unpadded RSA. We never used it, and
6830 it would be a bad idea to start.
6831 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
6833 - Remove some redundant #include directives throughout the code.
6834 Patch from Andrea Gelmini.
6835 - Remove some old code to remember statistics about which descriptors
6836 we've served as a directory mirror. The feature wasn't used and
6837 is outdated now that microdescriptors are around.
6838 - Remove some old code to work around even older versions of Tor that
6839 used forked processes to handle DNS requests. Such versions of Tor
6840 are no longer in use as relays.
6841 - The "torify" script no longer supports the "tsocks" socksifier
6842 tool, since tsocks doesn't support DNS and UDP right for Tor.
6843 Everyone should be using torsocks instead. Fixes bugs 3530 and
6844 5180. Based on a patch by "ugh".
6845 - Remove the torrc.bridge file: we don't use it for anything, and
6846 it had become badly desynchronized from torrc.sample. Resolves
6850 - Begin a doc/state-contents.txt file to explain the contents of
6851 the Tor state file. Fixes bug 2987.
6852 - Clarify the documentation for the Alternate*Authority options.
6854 - Document the --defaults-torrc option, and the new semantics for
6855 overriding, extending, and clearing lists of options. Closes
6857 - Add missing man page documentation for consensus and microdesc
6858 files. Resolves ticket 6732.
6859 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
6861 o Documentation fixes:
6862 - Improve the manual's documentation for the NT Service command-line
6863 options. Addresses ticket 3964.
6864 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
6865 - Document the changes to the ORPort and DirPort options, and the
6866 fact that {OR/Dir}ListenAddress is now unnecessary (and
6867 therefore deprecated). Resolves ticket 5597.
6868 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
6869 - Clarify that hidden services are TCP only. Fixes bug 6024.
6872 Changes in version 0.2.2.39 - 2012-09-11
6873 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
6877 - Fix an assertion failure in tor_timegm() that could be triggered
6878 by a badly formatted directory object. Bug found by fuzzing with
6879 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
6880 - Do not crash when comparing an address with port value 0 to an
6881 address policy. This bug could have been used to cause a remote
6882 assertion failure by or against directory authorities, or to
6883 allow some applications to crash clients. Fixes bug 6690; bugfix
6887 Changes in version 0.2.2.38 - 2012-08-12
6888 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
6889 attack that could in theory leak path information.
6892 - Avoid an uninitialized memory read when reading a vote or consensus
6893 document that has an unrecognized flavor name. This read could
6894 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
6895 - Try to leak less information about what relays a client is
6896 choosing to a side-channel attacker. Previously, a Tor client would
6897 stop iterating through the list of available relays as soon as it
6898 had chosen one, thus finishing a little earlier when it picked
6899 a router earlier in the list. If an attacker can recover this
6900 timing information (nontrivial but not proven to be impossible),
6901 they could learn some coarse-grained information about which relays
6902 a client was picking (middle nodes in particular are likelier to
6903 be affected than exits). The timing attack might be mitigated by
6904 other factors (see bug 6537 for some discussion), but it's best
6905 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
6908 Changes in version 0.2.2.37 - 2012-06-06
6909 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
6910 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
6914 - Work around a bug in OpenSSL that broke renegotiation with TLS
6915 1.1 and TLS 1.2. Without this workaround, all attempts to speak
6916 the v2 Tor connection protocol when both sides were using OpenSSL
6917 1.0.1 would fail. Resolves ticket 6033.
6918 - When waiting for a client to renegotiate, don't allow it to add
6919 any bytes to the input buffer. This fixes a potential DoS issue.
6920 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
6921 - Fix an edge case where if we fetch or publish a hidden service
6922 descriptor, we might build a 4-hop circuit and then use that circuit
6923 for exiting afterwards -- even if the new last hop doesn't obey our
6924 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
6927 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
6928 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
6931 - Tell GCC and Clang to check for any errors in format strings passed
6932 to the tor_v*(print|scan)f functions.
6935 Changes in version 0.2.2.36 - 2012-05-24
6936 Tor 0.2.2.36 updates the addresses for two of the eight directory
6937 authorities, fixes some potential anonymity and security issues,
6938 and fixes several crash bugs.
6940 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
6941 known flaws, and nobody should be using them. You should upgrade. If
6942 you're using a Linux or BSD and its packages are obsolete, stop using
6943 those packages and upgrade anyway.
6945 o Directory authority changes:
6946 - Change IP address for maatuska (v3 directory authority).
6947 - Change IP address for ides (v3 directory authority), and rename
6951 - When building or running with any version of OpenSSL earlier
6952 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
6953 versions have a bug (CVE-2011-4576) in which their block cipher
6954 padding includes uninitialized data, potentially leaking sensitive
6955 information to any peer with whom they make a SSLv3 connection. Tor
6956 does not use SSL v3 by default, but a hostile client or server
6957 could force an SSLv3 connection in order to gain information that
6958 they shouldn't have been able to get. The best solution here is to
6959 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
6960 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
6961 to make sure that the bug can't happen.
6962 - Never use a bridge or a controller-supplied node as an exit, even
6963 if its exit policy allows it. Found by wanoskarnet. Fixes bug
6964 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
6965 and 0.2.0.3-alpha (for bridge-purpose descriptors).
6966 - Only build circuits if we have a sufficient threshold of the total
6967 descriptors that are marked in the consensus with the "Exit"
6968 flag. This mitigates an attack proposed by wanoskarnet, in which
6969 all of a client's bridges collude to restrict the exit nodes that
6970 the client knows about. Fixes bug 5343.
6971 - Provide controllers with a safer way to implement the cookie
6972 authentication mechanism. With the old method, if another locally
6973 running program could convince a controller that it was the Tor
6974 process, then that program could trick the controller into telling
6975 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
6976 authentication method uses a challenge-response approach to prevent
6977 this attack. Fixes bug 5185; implements proposal 193.
6980 - Avoid logging uninitialized data when unable to decode a hidden
6981 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
6982 - Avoid a client-side assertion failure when receiving an INTRODUCE2
6983 cell on a general purpose circuit. Fixes bug 5644; bugfix on
6985 - Fix builds when the path to sed, openssl, or sha1sum contains
6986 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
6988 - Correct our replacements for the timeradd() and timersub() functions
6989 on platforms that lack them (for example, Windows). The timersub()
6990 function is used when expiring circuits, while timeradd() is
6991 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
6992 bugfix on 0.2.2.24-alpha.
6993 - Fix the SOCKET_OK test that we use to tell when socket
6994 creation fails so that it works on Win64. Fixes part of bug 4533;
6995 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
6998 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
6999 Fixes bug 5346; bugfix on 0.0.8pre3.
7000 - Make our number-parsing functions always treat too-large values
7001 as an error, even when those values exceed the width of the
7002 underlying type. Previously, if the caller provided these
7003 functions with minima or maxima set to the extreme values of the
7004 underlying integer type, these functions would return those
7005 values on overflow rather than treating overflow as an error.
7006 Fixes part of bug 5786; bugfix on 0.0.9.
7007 - Older Linux kernels erroneously respond to strange nmap behavior
7008 by having accept() return successfully with a zero-length
7009 socket. When this happens, just close the connection. Previously,
7010 we would try harder to learn the remote address: but there was
7011 no such remote address to learn, and our method for trying to
7012 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
7013 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
7014 - Correct parsing of certain date types in parse_http_time().
7015 Without this patch, If-Modified-Since would behave
7016 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
7017 Esteban Manchado Velázques.
7018 - Change the BridgePassword feature (part of the "bridge community"
7019 design, which is not yet implemented) to use a time-independent
7020 comparison. The old behavior might have allowed an adversary
7021 to use timing to guess the BridgePassword value. Fixes bug 5543;
7022 bugfix on 0.2.0.14-alpha.
7023 - Detect and reject certain misformed escape sequences in
7024 configuration values. Previously, these values would cause us
7025 to crash if received in a torrc file or over an authenticated
7026 control port. Bug found by Esteban Manchado Velázquez, and
7027 independently by Robert Connolly from Matta Consulting who further
7028 noted that it allows a post-authentication heap overflow. Patch
7029 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
7030 bugfix on 0.2.0.16-alpha.
7031 - Fix a compile warning when using the --enable-openbsd-malloc
7032 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
7033 - During configure, detect when we're building with clang version
7034 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
7035 CFLAGS. clang doesn't support them yet.
7036 - When sending an HTTP/1.1 proxy request, include a Host header.
7037 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
7038 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
7039 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
7040 - If we hit the error case where routerlist_insert() replaces an
7041 existing (old) server descriptor, make sure to remove that
7042 server descriptor from the old_routers list. Fix related to bug
7043 1776. Bugfix on 0.2.2.18-alpha.
7045 o Minor bugfixes (documentation and log messages):
7046 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
7047 Fixes bug 4856; bugfix on Tor 0.0.6.
7048 - Update "ClientOnly" man page entry to explain that there isn't
7049 really any point to messing with it. Resolves ticket 5005.
7050 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
7051 directory authority option (introduced in Tor 0.2.2.34).
7052 - Downgrade the "We're missing a certificate" message from notice
7053 to info: people kept mistaking it for a real problem, whereas it
7054 is seldom the problem even when we are failing to bootstrap. Fixes
7055 bug 5067; bugfix on 0.2.0.10-alpha.
7056 - Correctly spell "connect" in a log message on failure to create a
7057 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
7058 - Clarify the behavior of MaxCircuitDirtiness with hidden service
7059 circuits. Fixes issue 5259.
7062 - Directory authorities now reject versions of Tor older than
7063 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
7064 inclusive. These versions accounted for only a small fraction of
7065 the Tor network, and have numerous known security issues. Resolves
7067 - Update to the May 1 2012 Maxmind GeoLite Country database.
7070 - When sending or relaying a RELAY_EARLY cell, we used to convert
7071 it to a RELAY cell if the connection was using the v1 link
7072 protocol. This was a workaround for older versions of Tor, which
7073 didn't handle RELAY_EARLY cells properly. Now that all supported
7074 versions can handle RELAY_EARLY cells, and now that we're enforcing
7075 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
7076 remove this workaround. Addresses bug 4786.
7079 Changes in version 0.2.2.35 - 2011-12-16
7080 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
7081 buffers code. Absolutely everybody should upgrade.
7083 The bug relied on an incorrect calculation when making data continuous
7084 in one of our IO buffers, if the first chunk of the buffer was
7085 misaligned by just the wrong amount. The miscalculation would allow an
7086 attacker to overflow a piece of heap-allocated memory. To mount this
7087 attack, the attacker would need to either open a SOCKS connection to
7088 Tor's SocksPort (usually restricted to localhost), or target a Tor
7089 instance configured to make its connections through a SOCKS proxy
7090 (which Tor does not do by default).
7092 Good security practice requires that all heap-overflow bugs should be
7093 presumed to be exploitable until proven otherwise, so we are treating
7094 this as a potential code execution attack. Please upgrade immediately!
7095 This bug does not affect bufferevents-based builds of Tor. Special
7096 thanks to "Vektor" for reporting this issue to us!
7098 Tor 0.2.2.35 also fixes several bugs in previous versions, including
7099 crash bugs for unusual configurations, and a long-term bug that
7100 would prevent Tor from starting on Windows machines with draconian
7103 With this release, we remind everyone that 0.2.0.x has reached its
7104 formal end-of-life. Those Tor versions have many known flaws, and
7105 nobody should be using them. You should upgrade -- ideally to the
7106 0.2.2.x series. If you're using a Linux or BSD and its packages are
7107 obsolete, stop using those packages and upgrade anyway.
7109 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
7110 longer receive support after some time in early 2012.
7113 - Fix a heap overflow bug that could occur when trying to pull
7114 data into the first chunk of a buffer, when that chunk had
7115 already had some data drained from it. Fixes CVE-2011-2778;
7116 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
7117 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
7118 that it doesn't attempt to allocate a socketpair. This could cause
7119 some problems on Windows systems with overzealous firewalls. Fix for
7120 bug 4457; workaround for Libevent versions 2.0.1-alpha through
7122 - If we mark an OR connection for close based on a cell we process,
7123 don't process any further cells on it. We already avoid further
7124 reads on marked-for-close connections, but now we also discard the
7125 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
7126 which was the first version where we might mark a connection for
7127 close based on processing a cell on it.
7128 - Correctly sanity-check that we don't underflow on a memory
7129 allocation (and then assert) for hidden service introduction
7130 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
7131 bugfix on 0.2.1.5-alpha.
7132 - Fix a memory leak when we check whether a hidden service
7133 descriptor has any usable introduction points left. Fixes bug
7134 4424. Bugfix on 0.2.2.25-alpha.
7135 - Don't crash when we're running as a relay and don't have a GeoIP
7136 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
7137 we've had in the 0.2.3.x branch already.
7138 - When running as a client, do not print a misleading (and plain
7139 wrong) log message that we're collecting "directory request"
7140 statistics: clients don't collect statistics. Also don't create a
7141 useless (because empty) stats file in the stats/ directory. Fixes
7142 bug 4353; bugfix on 0.2.2.34.
7145 - Detect failure to initialize Libevent. This fix provides better
7146 detection for future instances of bug 4457.
7147 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
7148 function. This was eating up hideously large amounts of time on some
7149 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
7150 - Resolve an integer overflow bug in smartlist_ensure_capacity().
7151 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
7153 - Don't warn about unused log_mutex in log.c when building with
7154 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
7155 0.1.0.6-rc which introduced --disable-threads.
7156 - When configuring, starting, or stopping an NT service, stop
7157 immediately after the service configuration attempt has succeeded
7158 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
7159 - When sending a NETINFO cell, include the original address
7160 received for the other side, not its canonical address. Found
7161 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
7162 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
7163 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
7164 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
7165 occurred when a client tried to fetch a descriptor for a bridge
7166 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
7167 - Backport fixes for a pair of compilation warnings on Windows.
7168 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
7169 - If we had ever tried to call tor_addr_to_str on an address of
7170 unknown type, we would have done a strdup on an uninitialized
7171 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
7172 Reported by "troll_un".
7173 - Correctly detect and handle transient lookup failures from
7174 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
7175 Reported by "troll_un".
7176 - Fix null-pointer access that could occur if TLS allocation failed.
7177 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
7178 - Use tor_socket_t type for listener argument to accept(). Fixes bug
7179 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
7182 - Add two new config options for directory authorities:
7183 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
7184 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
7185 that is always sufficient to satisfy the bandwidth requirement for
7186 the Guard flag. Now it will be easier for researchers to simulate
7187 Tor networks with different values. Resolves ticket 4484.
7188 - When Tor ignores a hidden service specified in its configuration,
7189 include the hidden service's directory in the warning message.
7190 Previously, we would only tell the user that some hidden service
7191 was ignored. Bugfix on 0.0.6; fixes bug 4426.
7192 - Update to the December 6 2011 Maxmind GeoLite Country database.
7194 o Packaging changes:
7195 - Make it easier to automate expert package builds on Windows,
7196 by removing an absolute path from makensis.exe command.
7199 Changes in version 0.2.1.32 - 2011-12-16
7200 Tor 0.2.1.32 backports important security and privacy fixes for
7201 oldstable. This release is intended only for package maintainers and
7202 others who cannot use the 0.2.2 stable series. All others should be
7203 using Tor 0.2.2.x or newer.
7205 The Tor 0.2.1.x series will reach formal end-of-life some time in
7206 early 2012; we will stop releasing patches for it then.
7208 o Major bugfixes (also included in 0.2.2.x):
7209 - Correctly sanity-check that we don't underflow on a memory
7210 allocation (and then assert) for hidden service introduction
7211 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
7212 bugfix on 0.2.1.5-alpha.
7213 - Fix a heap overflow bug that could occur when trying to pull
7214 data into the first chunk of a buffer, when that chunk had
7215 already had some data drained from it. Fixes CVE-2011-2778;
7216 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
7219 - Update to the December 6 2011 Maxmind GeoLite Country database.
7222 Changes in version 0.2.2.34 - 2011-10-26
7223 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
7224 can deanonymize Tor users. Everybody should upgrade.
7226 The attack relies on four components: 1) Clients reuse their TLS cert
7227 when talking to different relays, so relays can recognize a user by
7228 the identity key in her cert. 2) An attacker who knows the client's
7229 identity key can probe each guard relay to see if that identity key
7230 is connected to that guard relay right now. 3) A variety of active
7231 attacks in the literature (starting from "Low-Cost Traffic Analysis
7232 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
7233 discover the guard relays that a Tor user visiting the website is using.
7234 4) Clients typically pick three guards at random, so the set of guards
7235 for a given user could well be a unique fingerprint for her. This
7236 release fixes components #1 and #2, which is enough to block the attack;
7237 the other two remain as open research problems. Special thanks to
7238 "frosty_un" for reporting the issue to us!
7240 Clients should upgrade so they are no longer recognizable by the TLS
7241 certs they present. Relays should upgrade so they no longer allow a
7242 remote attacker to probe them to test whether unpatched clients are
7243 currently connected to them.
7245 This release also fixes several vulnerabilities that allow an attacker
7246 to enumerate bridge relays. Some bridge enumeration attacks still
7247 remain; see for example proposal 188.
7249 o Privacy/anonymity fixes (clients):
7250 - Clients and bridges no longer send TLS certificate chains on
7251 outgoing OR connections. Previously, each client or bridge would
7252 use the same cert chain for all outgoing OR connections until
7253 its IP address changes, which allowed any relay that the client
7254 or bridge contacted to determine which entry guards it is using.
7255 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
7256 - If a relay receives a CREATE_FAST cell on a TLS connection, it
7257 no longer considers that connection as suitable for satisfying a
7258 circuit EXTEND request. Now relays can protect clients from the
7259 CVE-2011-2768 issue even if the clients haven't upgraded yet.
7260 - Directory authorities no longer assign the Guard flag to relays
7261 that haven't upgraded to the above "refuse EXTEND requests
7262 to client connections" fix. Now directory authorities can
7263 protect clients from the CVE-2011-2768 issue even if neither
7264 the clients nor the relays have upgraded yet. There's a new
7265 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
7266 to let us transition smoothly, else tomorrow there would be no
7269 o Privacy/anonymity fixes (bridge enumeration):
7270 - Bridge relays now do their directory fetches inside Tor TLS
7271 connections, like all the other clients do, rather than connecting
7272 directly to the DirPort like public relays do. Removes another
7273 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
7274 - Bridges relays now build circuits for themselves in a more similar
7275 way to how clients build them. Removes another avenue for
7276 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
7277 when bridges were introduced.
7278 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
7279 that they initiated. Relays could distinguish incoming bridge
7280 connections from client connections, creating another avenue for
7281 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
7282 Found by "frosty_un".
7285 - Fix a crash bug when changing node restrictions while a DNS lookup
7286 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
7288 - Don't launch a useless circuit after failing to use one of a
7289 hidden service's introduction points. Previously, we would
7290 launch a new introduction circuit, but not set the hidden service
7291 which that circuit was intended to connect to, so it would never
7292 actually be used. A different piece of code would then create a
7293 new introduction circuit correctly. Bug reported by katmagic and
7294 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
7297 - Change an integer overflow check in the OpenBSD_Malloc code so
7298 that GCC is less likely to eliminate it as impossible. Patch
7299 from Mansour Moufid. Fixes bug 4059.
7300 - When a hidden service turns an extra service-side introduction
7301 circuit into a general-purpose circuit, free the rend_data and
7302 intro_key fields first, so we won't leak memory if the circuit
7303 is cannibalized for use as another service-side introduction
7304 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
7305 - Bridges now skip DNS self-tests, to act a little more stealthily.
7306 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
7307 bridges. Patch by "warms0x".
7308 - Fix internal bug-checking logic that was supposed to catch
7309 failures in digest generation so that it will fail more robustly
7310 if we ask for a nonexistent algorithm. Found by Coverity Scan.
7311 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
7312 - Report any failure in init_keys() calls launched because our
7313 IP address has changed. Spotted by Coverity Scan. Bugfix on
7314 0.1.1.4-alpha; fixes CID 484.
7316 o Minor bugfixes (log messages and documentation):
7317 - Remove a confusing dollar sign from the example fingerprint in the
7318 man page, and also make the example fingerprint a valid one. Fixes
7319 bug 4309; bugfix on 0.2.1.3-alpha.
7320 - The next version of Windows will be called Windows 8, and it has
7321 a major version of 6, minor version of 2. Correctly identify that
7322 version instead of calling it "Very recent version". Resolves
7323 ticket 4153; reported by funkstar.
7324 - Downgrade log messages about circuit timeout calibration from
7325 "notice" to "info": they don't require or suggest any human
7326 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
7327 bugfix on 0.2.2.14-alpha.
7330 - Turn on directory request statistics by default and include them in
7331 extra-info descriptors. Don't break if we have no GeoIP database.
7332 Backported from 0.2.3.1-alpha; implements ticket 3951.
7333 - Update to the October 4 2011 Maxmind GeoLite Country database.
7336 Changes in version 0.2.1.31 - 2011-10-26
7337 Tor 0.2.1.31 backports important security and privacy fixes for
7338 oldstable. This release is intended only for package maintainers and
7339 others who cannot use the 0.2.2 stable series. All others should be
7340 using Tor 0.2.2.x or newer.
7342 o Security fixes (also included in 0.2.2.x):
7343 - Replace all potentially sensitive memory comparison operations
7344 with versions whose runtime does not depend on the data being
7345 compared. This will help resist a class of attacks where an
7346 adversary can use variations in timing information to learn
7347 sensitive data. Fix for one case of bug 3122. (Safe memcmp
7348 implementation by Robert Ransom based partially on code by DJB.)
7349 - Fix an assert in parsing router descriptors containing IPv6
7350 addresses. This one took down the directory authorities when
7351 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
7353 o Privacy/anonymity fixes (also included in 0.2.2.x):
7354 - Clients and bridges no longer send TLS certificate chains on
7355 outgoing OR connections. Previously, each client or bridge would
7356 use the same cert chain for all outgoing OR connections until
7357 its IP address changes, which allowed any relay that the client
7358 or bridge contacted to determine which entry guards it is using.
7359 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
7360 - If a relay receives a CREATE_FAST cell on a TLS connection, it
7361 no longer considers that connection as suitable for satisfying a
7362 circuit EXTEND request. Now relays can protect clients from the
7363 CVE-2011-2768 issue even if the clients haven't upgraded yet.
7364 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
7365 that they initiated. Relays could distinguish incoming bridge
7366 connections from client connections, creating another avenue for
7367 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
7368 Found by "frosty_un".
7369 - When receiving a hidden service descriptor, check that it is for
7370 the hidden service we wanted. Previously, Tor would store any
7371 hidden service descriptors that a directory gave it, whether it
7372 wanted them or not. This wouldn't have let an attacker impersonate
7373 a hidden service, but it did let directories pre-seed a client
7374 with descriptors that it didn't want. Bugfix on 0.0.6.
7375 - Avoid linkability based on cached hidden service descriptors: forget
7376 all hidden service descriptors cached as a client when processing a
7377 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
7378 - Make the bridge directory authority refuse to answer directory
7379 requests for "all" descriptors. It used to include bridge
7380 descriptors in its answer, which was a major information leak.
7381 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
7382 - Don't attach new streams to old rendezvous circuits after SIGNAL
7383 NEWNYM. Previously, we would keep using an existing rendezvous
7384 circuit if it remained open (i.e. if it were kept open by a
7385 long-lived stream, or if a new stream were attached to it before
7386 Tor could notice that it was old and no longer in use). Bugfix on
7387 0.1.1.15-rc; fixes bug 3375.
7389 o Minor bugfixes (also included in 0.2.2.x):
7390 - When we restart our relay, we might get a successful connection
7391 from the outside before we've started our reachability tests,
7392 triggering a warning: "ORPort found reachable, but I have no
7393 routerinfo yet. Failing to inform controller of success." This
7394 bug was harmless unless Tor is running under a controller
7395 like Vidalia, in which case the controller would never get a
7396 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
7398 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
7399 enabled. Fixes bug 1526.
7400 - Remove undocumented option "-F" from tor-resolve: it hasn't done
7401 anything since 0.2.1.16-rc.
7402 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
7403 None of the cases where we did this before were wrong, but by making
7404 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
7405 - Fix a rare crash bug that could occur when a client was configured
7406 with a large number of bridges. Fixes bug 2629; bugfix on
7407 0.2.1.2-alpha. Bugfix by trac user "shitlei".
7408 - Correct the warning displayed when a rendezvous descriptor exceeds
7409 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
7411 - Fix an uncommon assertion failure when running with DNSPort under
7412 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
7413 - When warning about missing zlib development packages during compile,
7414 give the correct package names. Bugfix on 0.2.0.1-alpha.
7415 - Require that introduction point keys and onion keys have public
7416 exponent 65537. Bugfix on 0.2.0.10-alpha.
7417 - Do not crash when our configuration file becomes unreadable, for
7418 example due to a permissions change, between when we start up
7419 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
7421 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
7423 - Always NUL-terminate the sun_path field of a sockaddr_un before
7424 passing it to the kernel. (Not a security issue: kernels are
7425 smart enough to reject bad sockaddr_uns.) Found by Coverity;
7426 CID #428. Bugfix on Tor 0.2.0.3-alpha.
7427 - Don't stack-allocate the list of supplementary GIDs when we're
7428 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
7429 could take up to 256K, which is way too much stack. Found by
7430 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
7432 o Minor bugfixes (only in 0.2.1.x):
7433 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
7434 rely on them. Bugfix on 0.2.1.30.
7435 - Use git revisions instead of svn revisions when generating our
7436 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
7438 o Minor features (also included in 0.2.2.x):
7439 - Adjust the expiration time on our SSL session certificates to
7440 better match SSL certs seen in the wild. Resolves ticket 4014.
7441 - Allow nameservers with IPv6 address. Resolves bug 2574.
7442 - Update to the October 4 2011 Maxmind GeoLite Country database.
7445 Changes in version 0.2.2.33 - 2011-09-13
7446 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
7447 TLS handshake that makes relays and bridges that run this new version
7448 reachable from Iran again.
7451 - Avoid an assertion failure when reloading a configuration with
7452 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
7453 3923; bugfix on 0.2.2.25-alpha.
7455 o Minor features (security):
7456 - Check for replays of the public-key encrypted portion of an
7457 INTRODUCE1 cell, in addition to the current check for replays of
7458 the g^x value. This prevents a possible class of active attacks
7459 by an attacker who controls both an introduction point and a
7460 rendezvous point, and who uses the malleability of AES-CTR to
7461 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
7462 that these attacks are infeasible (requiring the attacker to send
7463 on the order of zettabytes of altered cells in a short interval),
7464 but we'd rather block them off in case there are any classes of
7465 this attack that we missed. Reported by Willem Pinckaers.
7468 - Adjust the expiration time on our SSL session certificates to
7469 better match SSL certs seen in the wild. Resolves ticket 4014.
7470 - Change the default required uptime for a relay to be accepted as
7471 a HSDir (hidden service directory) from 24 hours to 25 hours.
7472 Improves on 0.2.0.10-alpha; resolves ticket 2649.
7473 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
7474 authorities to abstain from voting on assignment of the HSDir
7475 consensus flag. Related to bug 2649.
7476 - Update to the September 6 2011 Maxmind GeoLite Country database.
7478 o Minor bugfixes (documentation and log messages):
7479 - Correct the man page to explain that HashedControlPassword and
7480 CookieAuthentication can both be set, in which case either method
7481 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
7482 when we decided to allow these config options to both be set. Issue
7484 - Demote the 'replay detected' log message emitted when a hidden
7485 service receives the same Diffie-Hellman public key in two different
7486 INTRODUCE2 cells to info level. A normal Tor client can cause that
7487 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
7488 fixes part of bug 2442.
7489 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
7490 level. There is nothing that a hidden service's operator can do
7491 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
7493 - Clarify a log message specifying the characters permitted in
7494 HiddenServiceAuthorizeClient client names. Previously, the log
7495 message said that "[A-Za-z0-9+-_]" were permitted; that could have
7496 given the impression that every ASCII character between "+" and "_"
7497 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
7500 - Provide a substitute implementation of lround() for MSVC, which
7501 apparently lacks it. Patch from Gisle Vanem.
7502 - Clean up some code issues that prevented Tor from building on older
7503 BSDs. Fixes bug 3894; reported by "grarpamp".
7504 - Search for a platform-specific version of "ar" when cross-compiling.
7505 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
7508 Changes in version 0.2.2.32 - 2011-08-27
7509 The Tor 0.2.2 release series is dedicated to the memory of Andreas
7510 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
7511 a founder of the PETS community, a leader in our field, a mentor,
7512 and a friend. He left us with these words: "I had the possibility
7513 to contribute to this world that is not as it should be. I hope I
7514 could help in some areas to make the world a better place, and that
7515 I could also encourage other people to be engaged in improving the
7516 world. Please, stay engaged. This world needs you, your love, your
7517 initiative -- now I cannot be part of that anymore."
7519 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
7520 ready. More than two years in the making, this release features improved
7521 client performance and hidden service reliability, better compatibility
7522 for Android, correct behavior for bridges that listen on more than
7523 one address, more extensible and flexible directory object handling,
7524 better reporting of network statistics, improved code security, and
7525 many many other features and bugfixes.
7527 o Major features (client performance):
7528 - When choosing which cells to relay first, relays now favor circuits
7529 that have been quiet recently, to provide lower latency for
7530 low-volume circuits. By default, relays enable or disable this
7531 feature based on a setting in the consensus. They can override
7532 this default by using the new "CircuitPriorityHalflife" config
7533 option. Design and code by Ian Goldberg, Can Tang, and Chris
7535 - Directory authorities now compute consensus weightings that instruct
7536 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
7537 and no flag. Clients use these weightings to distribute network load
7538 more evenly across these different relay types. The weightings are
7539 in the consensus so we can change them globally in the future. Extra
7540 thanks to "outofwords" for finding some nasty security bugs in
7541 the first implementation of this feature.
7543 o Major features (client performance, circuit build timeout):
7544 - Tor now tracks how long it takes to build client-side circuits
7545 over time, and adapts its timeout to local network performance.
7546 Since a circuit that takes a long time to build will also provide
7547 bad performance, we get significant latency improvements by
7548 discarding the slowest 20% of circuits. Specifically, Tor creates
7549 circuits more aggressively than usual until it has enough data
7550 points for a good timeout estimate. Implements proposal 151.
7551 - Circuit build timeout constants can be controlled by consensus
7552 parameters. We set good defaults for these parameters based on
7553 experimentation on broadband and simulated high-latency links.
7554 - Circuit build time learning can be disabled via consensus parameter
7555 or by the client via a LearnCircuitBuildTimeout config option. We
7556 also automatically disable circuit build time calculation if either
7557 AuthoritativeDirectory is set, or if we fail to write our state
7558 file. Implements ticket 1296.
7560 o Major features (relays use their capacity better):
7561 - Set SO_REUSEADDR socket option on all sockets, not just
7562 listeners. This should help busy exit nodes avoid running out of
7563 useable ports just because all the ports have been used in the
7564 near past. Resolves issue 2850.
7565 - Relays now save observed peak bandwidth throughput rates to their
7566 state file (along with total usage, which was already saved),
7567 so that they can determine their correct estimated bandwidth on
7568 restart. Resolves bug 1863, where Tor relays would reset their
7569 estimated bandwidth to 0 after restarting.
7570 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
7571 should give us approximately 40-50% more Guard-flagged nodes,
7572 improving the anonymity the Tor network can provide and also
7573 decreasing the dropoff in throughput that relays experience when
7574 they first get the Guard flag.
7575 - Directory authorities now take changes in router IP address and
7576 ORPort into account when determining router stability. Previously,
7577 if a router changed its IP or ORPort, the authorities would not
7578 treat it as having any downtime for the purposes of stability
7579 calculation, whereas clients would experience downtime since the
7580 change would take a while to propagate to them. Resolves issue 1035.
7581 - New AccelName and AccelDir options add support for dynamic OpenSSL
7582 hardware crypto acceleration engines.
7584 o Major features (relays control their load better):
7585 - Exit relays now try harder to block exit attempts from unknown
7586 relays, to make it harder for people to use them as one-hop proxies
7587 a la tortunnel. Controlled by the refuseunknownexits consensus
7588 parameter (currently enabled), or you can override it on your
7589 relay with the RefuseUnknownExits torrc option. Resolves bug 1751;
7590 based on a variant of proposal 163.
7591 - Add separate per-conn write limiting to go with the per-conn read
7592 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
7593 but never per-conn write limits.
7594 - New consensus params "bwconnrate" and "bwconnburst" to let us
7595 rate-limit client connections as they enter the network. It's
7596 controlled in the consensus so we can turn it on and off for
7597 experiments. It's starting out off. Based on proposal 163.
7599 o Major features (controllers):
7600 - Export GeoIP information on bridge usage to controllers even if we
7601 have not yet been running for 24 hours. Now Vidalia bridge operators
7602 can get more accurate and immediate feedback about their
7603 contributions to the network.
7604 - Add an __OwningControllerProcess configuration option and a
7605 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
7606 that when it exits, Tor will shut down. Implements feature 3049.
7608 o Major features (directory authorities):
7609 - Directory authorities now create, vote on, and serve multiple
7610 parallel formats of directory data as part of their voting process.
7611 Partially implements Proposal 162: "Publish the consensus in
7613 - Directory authorities now agree on and publish small summaries
7614 of router information that clients can use in place of regular
7615 server descriptors. This transition will allow Tor 0.2.3 clients
7616 to use far less bandwidth for downloading information about the
7617 network. Begins the implementation of Proposal 158: "Clients
7618 download consensus + microdescriptors".
7619 - The directory voting system is now extensible to use multiple hash
7620 algorithms for signatures and resource selection. Newer formats
7621 are signed with SHA256, with a possibility for moving to a better
7622 hash algorithm in the future.
7623 - Directory authorities can now vote on arbitary integer values as
7624 part of the consensus process. This is designed to help set
7625 network-wide parameters. Implements proposal 167.
7627 o Major features and bugfixes (node selection):
7628 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
7629 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and Strict*Nodes
7630 options. Previously, we had been ambiguous in describing what
7631 counted as an "exit" node, and what operations exactly "StrictNodes
7632 0" would permit. This created confusion when people saw nodes built
7633 through unexpected circuits, and made it hard to tell real bugs from
7634 surprises. Now the intended behavior is:
7635 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
7636 a node that delivers user traffic outside the Tor network.
7637 . "Entry", in the context of EntryNodes, means a node used as the
7638 first hop of a multihop circuit. It doesn't include direct
7639 connections to directory servers.
7640 . "ExcludeNodes" applies to all nodes.
7641 . "StrictNodes" changes the behavior of ExcludeNodes only. When
7642 StrictNodes is set, Tor should avoid all nodes listed in
7643 ExcludeNodes, even when it will make user requests fail. When
7644 StrictNodes is *not* set, then Tor should follow ExcludeNodes
7645 whenever it can, except when it must use an excluded node to
7646 perform self-tests, connect to a hidden service, provide a
7647 hidden service, fulfill a .exit request, upload directory
7648 information, or fetch directory information.
7649 Collectively, the changes to implement the behavior fix bug 1090.
7650 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
7651 change during a config reload, mark and discard all our origin
7652 circuits. This fix should address edge cases where we change the
7653 config options and but then choose a circuit that we created before
7655 - Make EntryNodes config option much more aggressive even when
7656 StrictNodes is not set. Before it would prepend your requested
7657 entrynodes to your list of guard nodes, but feel free to use others
7658 after that. Now it chooses only from your EntryNodes if any of
7659 those are available, and only falls back to others if a) they're
7660 all down and b) StrictNodes is not set.
7661 - Now we refresh your entry guards from EntryNodes at each consensus
7662 fetch -- rather than just at startup and then they slowly rot as
7663 the network changes.
7664 - Add support for the country code "{??}" in torrc options like
7665 ExcludeNodes, to indicate all routers of unknown country. Closes
7667 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
7668 a node is listed in both, it's treated as excluded.
7669 - ExcludeNodes now applies to directory nodes -- as a preference if
7670 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
7671 Don't exclude all the directory authorities and set StrictNodes to 1
7672 unless you really want your Tor to break.
7673 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
7674 - ExcludeExitNodes now overrides .exit requests.
7675 - We don't use bridges listed in ExcludeNodes.
7676 - When StrictNodes is 1:
7677 . We now apply ExcludeNodes to hidden service introduction points
7678 and to rendezvous points selected by hidden service users. This
7679 can make your hidden service less reliable: use it with caution!
7680 . If we have used ExcludeNodes on ourself, do not try relay
7681 reachability self-tests.
7682 . If we have excluded all the directory authorities, we will not
7683 even try to upload our descriptor if we're a relay.
7684 . Do not honor .exit requests to an excluded node.
7685 - When the set of permitted nodes changes, we now remove any mappings
7686 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
7688 - We never cannibalize a circuit that had excluded nodes on it, even
7689 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
7690 - Improve log messages related to excluded nodes.
7692 o Major features (misc):
7693 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
7694 to help Tor build correctly for Android phones.
7695 - The options SocksPort, ControlPort, and so on now all accept a
7696 value "auto" that opens a socket on an OS-selected port. A
7697 new ControlPortWriteToFile option tells Tor to write its
7698 actual control port or ports to a chosen file. If the option
7699 ControlPortFileGroupReadable is set, the file is created as
7700 group-readable. Now users can run two Tor clients on the same
7701 system without needing to manually mess with parameters. Resolves
7702 part of ticket 3076.
7703 - Tor now supports tunneling all of its outgoing connections over
7704 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
7705 configuration options. Code by Christopher Davis.
7707 o Code security improvements:
7708 - Replace all potentially sensitive memory comparison operations
7709 with versions whose runtime does not depend on the data being
7710 compared. This will help resist a class of attacks where an
7711 adversary can use variations in timing information to learn
7712 sensitive data. Fix for one case of bug 3122. (Safe memcmp
7713 implementation by Robert Ransom based partially on code by DJB.)
7714 - Enable Address Space Layout Randomization (ASLR) and Data Execution
7715 Prevention (DEP) by default on Windows to make it harder for
7716 attackers to exploit vulnerabilities. Patch from John Brooks.
7717 - New "--enable-gcc-hardening" ./configure flag (off by default)
7718 to turn on gcc compile time hardening options. It ensures
7719 that signed ints have defined behavior (-fwrapv), enables
7720 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
7721 with canaries (-fstack-protector-all), turns on ASLR protection if
7722 supported by the kernel (-fPIE, -pie), and adds additional security
7723 related warnings. Verified to work on Mac OS X and Debian Lenny.
7724 - New "--enable-linker-hardening" ./configure flag (off by default)
7725 to turn on ELF specific hardening features (relro, now). This does
7726 not work with Mac OS X or any other non-ELF binary format.
7727 - Always search the Windows system directory for system DLLs, and
7728 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
7729 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
7730 current and future memory pages via mlockall(). On supported
7731 platforms (modern Linux and probably BSD but not Windows or OS X),
7732 this should effectively disable any and all attempts to page out
7733 memory. This option requires that you start your Tor as root --
7734 if you use DisableAllSwap, please consider using the User option
7735 to properly reduce the privileges of your Tor.
7737 o Major bugfixes (crashes):
7738 - Fix crash bug on platforms where gmtime and localtime can return
7739 NULL. Windows 7 users were running into this one. Fixes part of bug
7740 2077. Bugfix on all versions of Tor. Found by boboper.
7741 - Introduce minimum/maximum values that clients will believe
7742 from the consensus. Now we'll have a better chance to avoid crashes
7743 or worse when a consensus param has a weird value.
7744 - Fix a rare crash bug that could occur when a client was configured
7745 with a large number of bridges. Fixes bug 2629; bugfix on
7746 0.2.1.2-alpha. Bugfix by trac user "shitlei".
7747 - Do not crash when our configuration file becomes unreadable, for
7748 example due to a permissions change, between when we start up
7749 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
7751 - If we're in the pathological case where there's no exit bandwidth
7752 but there is non-exit bandwidth, or no guard bandwidth but there
7753 is non-guard bandwidth, don't crash during path selection. Bugfix
7755 - Fix a crash bug when trying to initialize the evdns module in
7756 Libevent 2. Bugfix on 0.2.1.16-rc.
7758 o Major bugfixes (stability):
7759 - Fix an assert in parsing router descriptors containing IPv6
7760 addresses. This one took down the directory authorities when
7761 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
7762 - Fix an uncommon assertion failure when running with DNSPort under
7763 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
7764 - Treat an unset $HOME like an empty $HOME rather than triggering an
7765 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
7766 - More gracefully handle corrupt state files, removing asserts
7767 in favor of saving a backup and resetting state.
7768 - Instead of giving an assertion failure on an internal mismatch
7769 on estimated freelist size, just log a BUG warning and try later.
7770 Mitigates but does not fix bug 1125.
7771 - Fix an assert that got triggered when using the TestingTorNetwork
7772 configuration option and then issuing a GETINFO config-text control
7773 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
7774 - If the cached cert file is unparseable, warn but don't exit.
7776 o Privacy fixes (relays/bridges):
7777 - Don't list Windows capabilities in relay descriptors. We never made
7778 use of them, and maybe it's a bad idea to publish them. Bugfix
7780 - If the Nickname configuration option isn't given, Tor would pick a
7781 nickname based on the local hostname as the nickname for a relay.
7782 Because nicknames are not very important in today's Tor and the
7783 "Unnamed" nickname has been implemented, this is now problematic
7784 behavior: It leaks information about the hostname without being
7785 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
7786 introduced the Unnamed nickname. Reported by tagnaq.
7787 - Maintain separate TLS contexts and certificates for incoming and
7788 outgoing connections in bridge relays. Previously we would use the
7789 same TLS contexts and certs for incoming and outgoing connections.
7790 Bugfix on 0.2.0.3-alpha; addresses bug 988.
7791 - Maintain separate identity keys for incoming and outgoing TLS
7792 contexts in bridge relays. Previously we would use the same
7793 identity keys for incoming and outgoing TLS contexts. Bugfix on
7794 0.2.0.3-alpha; addresses the other half of bug 988.
7795 - Make the bridge directory authority refuse to answer directory
7796 requests for "all descriptors". It used to include bridge
7797 descriptors in its answer, which was a major information leak.
7798 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
7800 o Privacy fixes (clients):
7801 - When receiving a hidden service descriptor, check that it is for
7802 the hidden service we wanted. Previously, Tor would store any
7803 hidden service descriptors that a directory gave it, whether it
7804 wanted them or not. This wouldn't have let an attacker impersonate
7805 a hidden service, but it did let directories pre-seed a client
7806 with descriptors that it didn't want. Bugfix on 0.0.6.
7807 - Start the process of disabling ".exit" address notation, since it
7808 can be used for a variety of esoteric application-level attacks
7809 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
7811 - Reject attempts at the client side to open connections to private
7812 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
7813 a randomly chosen exit node. Attempts to do so are always
7814 ill-defined, generally prevented by exit policies, and usually
7815 in error. This will also help to detect loops in transparent
7816 proxy configurations. You can disable this feature by setting
7817 "ClientRejectInternalAddresses 0" in your torrc.
7818 - Log a notice when we get a new control connection. Now it's easier
7819 for security-conscious users to recognize when a local application
7820 is knocking on their controller door. Suggested by bug 1196.
7822 o Privacy fixes (newnym):
7823 - Avoid linkability based on cached hidden service descriptors: forget
7824 all hidden service descriptors cached as a client when processing a
7825 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
7826 - On SIGHUP, do not clear out all TrackHostExits mappings, client
7827 DNS cache entries, and virtual address mappings: that's what
7828 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
7829 - Don't attach new streams to old rendezvous circuits after SIGNAL
7830 NEWNYM. Previously, we would keep using an existing rendezvous
7831 circuit if it remained open (i.e. if it were kept open by a
7832 long-lived stream, or if a new stream were attached to it before
7833 Tor could notice that it was old and no longer in use). Bugfix on
7834 0.1.1.15-rc; fixes bug 3375.
7836 o Major bugfixes (relay bandwidth accounting):
7837 - Fix a bug that could break accounting on 64-bit systems with large
7838 time_t values, making them hibernate for impossibly long intervals.
7839 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
7840 - Fix a bug in bandwidth accounting that could make us use twice
7841 the intended bandwidth when our interval start changes due to
7842 daylight saving time. Now we tolerate skew in stored vs computed
7843 interval starts: if the start of the period changes by no more than
7844 50% of the period's duration, we remember bytes that we transferred
7845 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
7847 o Major bugfixes (bridges):
7848 - Bridges now use "reject *:*" as their default exit policy. Bugfix
7849 on 0.2.0.3-alpha. Fixes bug 1113.
7850 - If you configure your bridge with a known identity fingerprint,
7851 and the bridge authority is unreachable (as it is in at least
7852 one country now), fall back to directly requesting the descriptor
7853 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
7855 - Fix a bug where bridge users who configure the non-canonical
7856 address of a bridge automatically switch to its canonical
7857 address. If a bridge listens at more than one address, it
7858 should be able to advertise those addresses independently and
7859 any non-blocked addresses should continue to work. Bugfix on Tor
7860 0.2.0.3-alpha. Fixes bug 2510.
7861 - If you configure Tor to use bridge A, and then quit and
7862 configure Tor to use bridge B instead (or if you change Tor
7863 to use bridge B via the controller), it would happily continue
7864 to use bridge A if it's still reachable. While this behavior is
7865 a feature if your goal is connectivity, in some scenarios it's a
7866 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
7867 - When the controller configures a new bridge, don't wait 10 to 60
7868 seconds before trying to fetch its descriptor. Bugfix on
7869 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
7871 o Major bugfixes (directory authorities):
7872 - Many relays have been falling out of the consensus lately because
7873 not enough authorities know about their descriptor for them to get
7874 a majority of votes. When we deprecated the v2 directory protocol,
7875 we got rid of the only way that v3 authorities can hear from each
7876 other about other descriptors. Now authorities examine every v3
7877 vote for new descriptors, and fetch them from that authority. Bugfix
7879 - Authorities could be tricked into giving out the Exit flag to relays
7880 that didn't allow exiting to any ports. This bug could screw
7881 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
7882 1238. Bug discovered by Martin Kowalczyk.
7883 - If all authorities restart at once right before a consensus vote,
7884 nobody will vote about "Running", and clients will get a consensus
7885 with no usable relays. Instead, authorities refuse to build a
7886 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
7888 o Major bugfixes (stream-level fairness):
7889 - When receiving a circuit-level SENDME for a blocked circuit, try
7890 to package cells fairly from all the streams that had previously
7891 been blocked on that circuit. Previously, we had started with the
7892 oldest stream, and allowed each stream to potentially exhaust
7893 the circuit's package window. This gave older streams on any
7894 given circuit priority over newer ones. Fixes bug 1937. Detected
7895 originally by Camilo Viecco. This bug was introduced before the
7896 first Tor release, in svn commit r152: it is the new winner of
7897 the longest-lived bug prize.
7898 - Fix a stream fairness bug that would cause newer streams on a given
7899 circuit to get preference when reading bytes from the origin or
7900 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
7901 introduced before the first Tor release, in svn revision r152.
7902 - When the exit relay got a circuit-level sendme cell, it started
7903 reading on the exit streams, even if had 500 cells queued in the
7904 circuit queue already, so the circuit queue just grew and grew in
7905 some cases. We fix this by not re-enabling reading on receipt of a
7906 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
7907 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
7909 - Newly created streams were allowed to read cells onto circuits,
7910 even if the circuit's cell queue was blocked and waiting to drain.
7911 This created potential unfairness, as older streams would be
7912 blocked, but newer streams would gladly fill the queue completely.
7913 We add code to detect this situation and prevent any stream from
7914 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
7917 o Major bugfixes (hidden services):
7918 - Apply circuit timeouts to opened hidden-service-related circuits
7919 based on the correct start time. Previously, we would apply the
7920 circuit build timeout based on time since the circuit's creation;
7921 it was supposed to be applied based on time since the circuit
7922 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
7923 - Improve hidden service robustness: When we find that we have
7924 extended a hidden service's introduction circuit to a relay not
7925 listed as an introduction point in the HS descriptor we currently
7926 have, retry with an introduction point from the current
7927 descriptor. Previously we would just give up. Fixes bugs 1024 and
7928 1930; bugfix on 0.2.0.10-alpha.
7929 - Directory authorities now use data collected from their own
7930 uptime observations when choosing whether to assign the HSDir flag
7931 to relays, instead of trusting the uptime value the relay reports in
7932 its descriptor. This change helps prevent an attack where a small
7933 set of nodes with frequently-changing identity keys can blackhole
7934 a hidden service. (Only authorities need upgrade; others will be
7935 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
7936 - Stop assigning the HSDir flag to relays that disable their
7937 DirPort (and thus will refuse to answer directory requests). This
7938 fix should dramatically improve the reachability of hidden services:
7939 hidden services and hidden service clients pick six HSDir relays
7940 to store and retrieve the hidden service descriptor, and currently
7941 about half of the HSDir relays will refuse to work. Bugfix on
7942 0.2.0.10-alpha; fixes part of bug 1693.
7944 o Major bugfixes (misc):
7945 - Clients now stop trying to use an exit node associated with a given
7946 destination by TrackHostExits if they fail to reach that exit node.
7947 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
7948 - Fix a regression that caused Tor to rebind its ports if it receives
7949 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
7950 - Remove an extra pair of quotation marks around the error
7951 message in control-port STATUS_GENERAL BUG events. Bugfix on
7952 0.1.2.6-alpha; fixes bug 3732.
7954 o Minor features (relays):
7955 - Ensure that no empty [dirreq-](read|write)-history lines are added
7956 to an extrainfo document. Implements ticket 2497.
7957 - When bandwidth accounting is enabled, be more generous with how
7958 much bandwidth we'll use up before entering "soft hibernation".
7959 Previously, we'd refuse new connections and circuits once we'd
7960 used up 95% of our allotment. Now, we use up 95% of our allotment,
7961 AND make sure that we have no more than 500MB (or 3 hours of
7962 expected traffic, whichever is lower) remaining before we enter
7964 - Relays now log the reason for publishing a new relay descriptor,
7965 so we have a better chance of hunting down instances of bug 1810.
7966 Resolves ticket 3252.
7967 - Log a little more clearly about the times at which we're no longer
7968 accepting new connections (e.g. due to hibernating). Resolves
7970 - When AllowSingleHopExits is set, print a warning to explain to the
7971 relay operator why most clients are avoiding her relay.
7972 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
7973 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
7974 clients are already deprecated because of security bugs.
7976 o Minor features (network statistics):
7977 - Directory mirrors that set "DirReqStatistics 1" write statistics
7978 about directory requests to disk every 24 hours. As compared to the
7979 "--enable-geoip-stats" ./configure flag in 0.2.1.x, there are a few
7980 improvements: 1) stats are written to disk exactly every 24 hours;
7981 2) estimated shares of v2 and v3 requests are determined as mean
7982 values, not at the end of a measurement period; 3) unresolved
7983 requests are listed with country code '??'; 4) directories also
7984 measure download times.
7985 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
7986 number of exit streams and transferred bytes per port to disk every
7988 - Relays that set "CellStatistics 1" write statistics on how long
7989 cells spend in their circuit queues to disk every 24 hours.
7990 - Entry nodes that set "EntryStatistics 1" write statistics on the
7991 rough number and origins of connecting clients to disk every 24
7993 - Relays that write any of the above statistics to disk and set
7994 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
7995 their extra-info documents. Implements proposal 166.
7997 o Minor features (GeoIP and statistics):
7998 - Provide a log message stating which geoip file we're parsing
7999 instead of just stating that we're parsing the geoip file.
8000 Implements ticket 2432.
8001 - Make sure every relay writes a state file at least every 12 hours.
8002 Previously, a relay could go for weeks without writing its state
8003 file, and on a crash could lose its bandwidth history, capacity
8004 estimates, client country statistics, and so on. Addresses bug 3012.
8005 - Relays report the number of bytes spent on answering directory
8006 requests in extra-info descriptors similar to {read,write}-history.
8007 Implements enhancement 1790.
8008 - Report only the top 10 ports in exit-port stats in order not to
8009 exceed the maximum extra-info descriptor length of 50 KB. Implements
8011 - If writing the state file to disk fails, wait up to an hour before
8012 retrying again, rather than trying again each second. Fixes bug
8013 2346; bugfix on Tor 0.1.1.3-alpha.
8014 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
8015 when we switch from being a public relay to a bridge. Otherwise
8016 there will still be clients that see the relay in their consensus,
8017 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes
8019 - Update to the August 2 2011 Maxmind GeoLite Country database.
8021 o Minor features (clients):
8022 - When expiring circuits, use microsecond timers rather than
8023 one-second timers. This can avoid an unpleasant situation where a
8024 circuit is launched near the end of one second and expired right
8025 near the beginning of the next, and prevent fluctuations in circuit
8027 - If we've configured EntryNodes and our network goes away and/or all
8028 our entrynodes get marked down, optimistically retry them all when
8029 a new socks application request appears. Fixes bug 1882.
8030 - Always perform router selections using weighted relay bandwidth,
8031 even if we don't need a high capacity circuit at the time. Non-fast
8032 circuits now only differ from fast ones in that they can use relays
8033 not marked with the Fast flag. This "feature" could turn out to
8034 be a horrible bug; we should investigate more before it goes into
8036 - When we run out of directory information such that we can't build
8037 circuits, but then get enough that we can build circuits, log when
8038 we actually construct a circuit, so the user has a better chance of
8039 knowing what's going on. Fixes bug 1362.
8040 - Log SSL state transitions at debug level during handshake, and
8041 include SSL states in error messages. This may help debug future
8042 SSL handshake issues.
8044 o Minor features (directory authorities):
8045 - When a router changes IP address or port, authorities now launch
8046 a new reachability test for it. Implements ticket 1899.
8047 - Directory authorities now reject relays running any versions of
8048 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
8049 known bugs that keep RELAY_EARLY cells from working on rendezvous
8050 circuits. Followup to fix for bug 2081.
8051 - Directory authorities now reject relays running any version of Tor
8052 older than 0.2.0.26-rc. That version is the earliest that fetches
8053 current directory information correctly. Fixes bug 2156.
8054 - Directory authorities now do an immediate reachability check as soon
8055 as they hear about a new relay. This change should slightly reduce
8056 the time between setting up a relay and getting listed as running
8057 in the consensus. It should also improve the time between setting
8058 up a bridge and seeing use by bridge users.
8059 - Directory authorities no longer launch a TLS connection to every
8060 relay as they startup. Now that we have 2k+ descriptors cached,
8061 the resulting network hiccup is becoming a burden. Besides,
8062 authorities already avoid voting about Running for the first half
8063 hour of their uptime.
8064 - Directory authorities now log the source of a rejected POSTed v3
8065 networkstatus vote, so we can track failures better.
8066 - Backport code from 0.2.3.x that allows directory authorities to
8067 clean their microdescriptor caches. Needed to resolve bug 2230.
8069 o Minor features (hidden services):
8070 - Use computed circuit-build timeouts to decide when to launch
8071 parallel introduction circuits for hidden services. (Previously,
8072 we would retry after 15 seconds.)
8073 - Don't allow v0 hidden service authorities to act as clients.
8074 Required by fix for bug 3000.
8075 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
8076 by fix for bug 3000.
8077 - Make hidden services work better in private Tor networks by not
8078 requiring any uptime to join the hidden service descriptor
8079 DHT. Implements ticket 2088.
8080 - Log (at info level) when purging pieces of hidden-service-client
8081 state because of SIGNAL NEWNYM.
8083 o Minor features (controller interface):
8084 - New "GETINFO net/listeners/(type)" controller command to return
8085 a list of addresses and ports that are bound for listeners for a
8086 given connection type. This is useful when the user has configured
8087 "SocksPort auto" and the controller needs to know which port got
8088 chosen. Resolves another part of ticket 3076.
8089 - Have the controller interface give a more useful message than
8090 "Internal Error" in response to failed GETINFO requests.
8091 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
8092 event, to give information on the current rate of circuit timeouts
8093 over our stored history.
8094 - The 'EXTENDCIRCUIT' control port command can now be used with
8095 a circ id of 0 and no path. This feature will cause Tor to build
8096 a new 'fast' general purpose circuit using its own path selection
8098 - Added a BUILDTIMEOUT_SET controller event to describe changes
8099 to the circuit build timeout.
8100 - New controller command "getinfo config-text". It returns the
8101 contents that Tor would write if you send it a SAVECONF command,
8102 so the controller can write the file to disk itself.
8104 o Minor features (controller protocol):
8105 - Add a new ControlSocketsGroupWritable configuration option: when
8106 it is turned on, ControlSockets are group-writeable by the default
8107 group of the current user. Patch by Jérémy Bobbio; implements
8109 - Tor now refuses to create a ControlSocket in a directory that is
8110 world-readable (or group-readable if ControlSocketsGroupWritable
8111 is 0). This is necessary because some operating systems do not
8112 enforce permissions on an AF_UNIX sockets. Permissions on the
8113 directory holding the socket, however, seems to work everywhere.
8114 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
8115 not. This would lead to a cookie that is still not group readable.
8116 Closes bug 1843. Suggested by katmagic.
8117 - Future-proof the controller protocol a bit by ignoring keyword
8118 arguments we do not recognize.
8120 o Minor features (more useful logging):
8121 - Revise most log messages that refer to nodes by nickname to
8122 instead use the "$key=nickname at address" format. This should be
8123 more useful, especially since nicknames are less and less likely
8124 to be unique. Resolves ticket 3045.
8125 - When an HTTPS proxy reports "403 Forbidden", we now explain
8126 what it means rather than calling it an unexpected status code.
8127 Closes bug 2503. Patch from Michael Yakubovich.
8128 - Rate-limit a warning about failures to download v2 networkstatus
8129 documents. Resolves part of bug 1352.
8130 - Rate-limit the "your application is giving Tor only an IP address"
8131 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
8132 - Rate-limit "Failed to hand off onionskin" warnings.
8133 - When logging a rate-limited warning, we now mention how many messages
8134 got suppressed since the last warning.
8135 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
8136 2 no signature, 4 required" messages about consensus signatures
8137 easier to read, and make sure they get logged at the same severity
8138 as the messages explaining which keys are which. Fixes bug 1290.
8139 - Don't warn when we have a consensus that we can't verify because
8140 of missing certificates, unless those certificates are ones
8141 that we have been trying and failing to download. Fixes bug 1145.
8143 o Minor features (log domains):
8144 - Add documentation for configuring logging at different severities in
8145 different log domains. We've had this feature since 0.2.1.1-alpha,
8146 but for some reason it never made it into the manpage. Fixes
8148 - Make it simpler to specify "All log domains except for A and B".
8149 Previously you needed to say "[*,~A,~B]". Now you can just say
8151 - Add a "LogMessageDomains 1" option to include the domains of log
8152 messages along with the messages. Without this, there's no way
8153 to use log domains without reading the source or doing a lot
8155 - Add a new "Handshake" log domain for activities that happen
8156 during the TLS handshake.
8158 o Minor features (build process):
8159 - Make compilation with clang possible when using
8160 "--enable-gcc-warnings" by removing two warning options that clang
8161 hasn't implemented yet and by fixing a few warnings. Resolves
8163 - Detect platforms that brokenly use a signed size_t, and refuse to
8164 build there. Found and analyzed by doorss and rransom.
8165 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
8167 - Add support for statically linking zlib by specifying
8168 "--enable-static-zlib", to go with our support for statically
8169 linking openssl and libevent. Resolves bug 1358.
8170 - Instead of adding the svn revision to the Tor version string, report
8171 the git commit (when we're building from a git checkout).
8172 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
8174 - New --digests command-line switch to output the digests of the
8175 source files Tor was built with.
8176 - Generate our manpage and HTML documentation using Asciidoc. This
8177 change should make it easier to maintain the documentation, and
8178 produce nicer HTML. The build process fails if asciidoc cannot
8179 be found and building with asciidoc isn't disabled (via the
8180 "--disable-asciidoc" argument to ./configure. Skipping the manpage
8181 speeds up the build considerably.
8183 o Minor features (options / torrc):
8184 - Warn when the same option is provided more than once in a torrc
8185 file, on the command line, or in a single SETCONF statement, and
8186 the option is one that only accepts a single line. Closes bug 1384.
8187 - Warn when the user configures two HiddenServiceDir lines that point
8188 to the same directory. Bugfix on 0.0.6 (the version introducing
8189 HiddenServiceDir); fixes bug 3289.
8190 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
8191 do individual connection-level rate limiting of clients. The torrc
8192 config options with the same names trump the consensus params, if
8193 both are present. Replaces the old "bwconnrate" and "bwconnburst"
8194 consensus params which were broken from 0.2.2.7-alpha through
8195 0.2.2.14-alpha. Closes bug 1947.
8196 - New config option "WarnUnsafeSocks 0" disables the warning that
8197 occurs whenever Tor receives a socks handshake using a version of
8198 the socks protocol that can only provide an IP address (rather
8199 than a hostname). Setups that do DNS locally over Tor are fine,
8200 and we shouldn't spam the logs in that case.
8201 - New config option "CircuitStreamTimeout" to override our internal
8202 timeout schedule for how many seconds until we detach a stream from
8203 a circuit and try a new circuit. If your network is particularly
8204 slow, you might want to set this to a number like 60.
8205 - New options for SafeLogging to allow scrubbing only log messages
8206 generated while acting as a relay. Specify "SafeLogging relay" if
8207 you want to ensure that only messages known to originate from
8208 client use of the Tor process will be logged unsafely.
8209 - Time and memory units in the configuration file can now be set to
8210 fractional units. For example, "2.5 GB" is now a valid value for
8212 - Support line continuations in the torrc config file. If a line
8213 ends with a single backslash character, the newline is ignored, and
8214 the configuration value is treated as continuing on the next line.
8217 o Minor features (unit tests):
8218 - Revise our unit tests to use the "tinytest" framework, so we
8219 can run tests in their own processes, have smarter setup/teardown
8220 code, and so on. The unit test code has moved to its own
8221 subdirectory, and has been split into multiple modules.
8222 - Add a unit test for cross-platform directory-listing code.
8223 - Add some forgotten return value checks during unit tests. Found
8225 - Use GetTempDir to find the proper temporary directory location on
8226 Windows when generating temporary files for the unit tests. Patch
8229 o Minor features (misc):
8230 - The "torify" script now uses torsocks where available.
8231 - Make Libevent log messages get delivered to controllers later,
8232 and not from inside the Libevent log handler. This prevents unsafe
8233 reentrant Libevent calls while still letting the log messages
8235 - Certain Tor clients (such as those behind check.torproject.org) may
8236 want to fetch the consensus in an extra early manner. To enable this
8237 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
8238 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
8239 as only certain clients who must have this information sooner should
8241 - Expand homedirs passed to tor-checkkey. This should silence a
8242 coverity complaint about passing a user-supplied string into
8243 open() without checking it.
8244 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
8245 used on bridges, and it makes bridge scanning somewhat easier.
8246 - Create the /var/run/tor directory on startup on OpenSUSE if it is
8247 not already created. Patch from Andreas Stieger. Fixes bug 2573.
8249 o Minor bugfixes (relays):
8250 - When a relay decides that its DNS is too broken for it to serve
8251 as an exit server, it advertised itself as a non-exit, but
8252 continued to act as an exit. This could create accidental
8253 partitioning opportunities for users. Instead, if a relay is
8254 going to advertise reject *:* as its exit policy, it should
8255 really act with exit policy "reject *:*". Fixes bug 2366.
8256 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
8257 - Publish a router descriptor even if generating an extra-info
8258 descriptor fails. Previously we would not publish a router
8259 descriptor without an extra-info descriptor; this can cause fast
8260 exit relays collecting exit-port statistics to drop from the
8261 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
8262 - When we're trying to guess whether we know our IP address as
8263 a relay, we would log various ways that we failed to guess
8264 our address, but never log that we ended up guessing it
8265 successfully. Now add a log line to help confused and anxious
8266 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
8267 - For bandwidth accounting, calculate our expected bandwidth rate
8268 based on the time during which we were active and not in
8269 soft-hibernation during the last interval. Previously, we were
8270 also considering the time spent in soft-hibernation. If this
8271 was a long time, we would wind up underestimating our bandwidth
8272 by a lot, and skewing our wakeup time towards the start of the
8273 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
8274 - Demote a confusing TLS warning that relay operators might get when
8275 someone tries to talk to their ORPort. It is not the operator's
8276 fault, nor can they do anything about it. Fixes bug 1364; bugfix
8278 - Change "Application request when we're believed to be offline."
8279 notice to "Application request when we haven't used client
8280 functionality lately.", to clarify that it's not an error. Bugfix
8281 on 0.0.9.3; fixes bug 1222.
8283 o Minor bugfixes (bridges):
8284 - When a client starts or stops using bridges, never use a circuit
8285 that was built before the configuration change. This behavior could
8286 put at risk a user who uses bridges to ensure that her traffic
8287 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
8289 - Do not reset the bridge descriptor download status every time we
8290 re-parse our configuration or get a configuration change. Fixes
8291 bug 3019; bugfix on 0.2.0.3-alpha.
8292 - Users couldn't configure a regular relay to be their bridge. It
8293 didn't work because when Tor fetched the bridge descriptor, it found
8294 that it already had it, and didn't realize that the purpose of the
8295 descriptor had changed. Now we replace routers with a purpose other
8296 than bridge with bridge descriptors when fetching them. Bugfix on
8297 0.1.1.9-alpha. Fixes bug 1776.
8298 - In the special case where you configure a public exit relay as your
8299 bridge, Tor would be willing to use that exit relay as the last
8300 hop in your circuit as well. Now we fail that circuit instead.
8301 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
8303 o Minor bugfixes (clients):
8304 - We now ask the other side of a stream (the client or the exit)
8305 for more data on that stream when the amount of queued data on
8306 that stream dips low enough. Previously, we wouldn't ask the
8307 other side for more data until either it sent us more data (which
8308 it wasn't supposed to do if it had exhausted its window!) or we
8309 had completely flushed all our queued data. This flow control fix
8310 should improve throughput. Fixes bug 2756; bugfix on the earliest
8311 released versions of Tor (svn commit r152).
8312 - When a client finds that an origin circuit has run out of 16-bit
8313 stream IDs, we now mark it as unusable for new streams. Previously,
8314 we would try to close the entire circuit. Bugfix on 0.0.6.
8315 - Make it explicit that we don't cannibalize one-hop circuits. This
8316 happens in the wild, but doesn't turn out to be a problem because
8317 we fortunately don't use those circuits. Many thanks to outofwords
8318 for the initial analysis and to swissknife who confirmed that
8319 two-hop circuits are actually created.
8320 - Resolve an edge case in path weighting that could make us misweight
8321 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
8322 - Make the DNSPort option work with libevent 2.x. Don't alter the
8323 behavior for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
8325 o Minor bugfixes (directory authorities):
8326 - Make directory authorities more accurate at recording when
8327 relays that have failed several reachability tests became
8328 unreachable, so we can provide more accuracy at assigning Stable,
8329 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
8330 - Directory authorities are now more robust to hops back in time
8331 when calculating router stability. Previously, if a run of uptime
8332 or downtime appeared to be negative, the calculation could give
8333 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
8335 - Directory authorities will now attempt to download consensuses
8336 if their own efforts to make a live consensus have failed. This
8337 change means authorities that restart will fetch a valid
8338 consensus, and it means authorities that didn't agree with the
8339 current consensus will still fetch and serve it if it has enough
8340 signatures. Bugfix on 0.2.0.9-alpha; fixes bug 1300.
8341 - Never vote for a server as "Running" if we have a descriptor for
8342 it claiming to be hibernating, and that descriptor was published
8343 more recently than our last contact with the server. Bugfix on
8344 0.2.0.3-alpha; fixes bug 911.
8345 - Directory authorities no longer change their opinion of, or vote on,
8346 whether a router is Running, unless they have themselves been
8347 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
8350 o Minor bugfixes (hidden services):
8351 - Log malformed requests for rendezvous descriptors as protocol
8352 warnings, not warnings. Also, use a more informative log message
8353 in case someone sees it at log level warning without prior
8354 info-level messages. Fixes bug 2748; bugfix on 0.2.0.10-alpha.
8355 - Accept hidden service descriptors if we think we might be a hidden
8356 service directory, regardless of what our consensus says. This
8357 helps robustness, since clients and hidden services can sometimes
8358 have a more up-to-date view of the network consensus than we do,
8359 and if they think that the directory authorities list us a HSDir,
8360 we might actually be one. Related to bug 2732; bugfix on
8362 - Correct the warning displayed when a rendezvous descriptor exceeds
8363 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
8365 - Clients and hidden services now use HSDir-flagged relays for hidden
8366 service descriptor downloads and uploads even if the relays have no
8367 DirPort set and the client has disabled TunnelDirConns. This will
8368 eventually allow us to give the HSDir flag to relays with no
8369 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
8370 - Only limit the lengths of single HS descriptors, even when multiple
8371 HS descriptors are published to an HSDir relay in a single POST
8372 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
8374 o Minor bugfixes (controllers):
8375 - Allow GETINFO fingerprint to return a fingerprint even when
8376 we have not yet built a router descriptor. Fixes bug 3577;
8377 bugfix on 0.2.0.1-alpha.
8378 - Send a SUCCEEDED stream event to the controller when a reverse
8379 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
8380 discovered by katmagic.
8381 - Remove a trailing asterisk from "exit-policy/default" in the
8382 output of the control port command "GETINFO info/names". Bugfix
8384 - Make the SIGNAL DUMP controller command work on FreeBSD. Fixes bug
8385 2917. Bugfix on 0.1.1.1-alpha.
8386 - When we restart our relay, we might get a successful connection
8387 from the outside before we've started our reachability tests,
8388 triggering a warning: "ORPort found reachable, but I have no
8389 routerinfo yet. Failing to inform controller of success." This
8390 bug was harmless unless Tor is running under a controller
8391 like Vidalia, in which case the controller would never get a
8392 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
8394 - When a controller changes TrackHostExits, remove mappings for
8395 hosts that should no longer have their exits tracked. Bugfix on
8397 - When a controller changes VirtualAddrNetwork, remove any mappings
8398 for hosts that were automapped to the old network. Bugfix on
8400 - When a controller changes one of the AutomapHosts* options, remove
8401 any mappings for hosts that should no longer be automapped. Bugfix
8403 - Fix an off-by-one error in calculating some controller command
8404 argument lengths. Fortunately, this mistake is harmless since
8405 the controller code does redundant NUL termination too. Found by
8406 boboper. Bugfix on 0.1.1.1-alpha.
8407 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
8408 would return "551 Internal error" rather than "552 Unrecognized key
8409 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
8410 - Don't spam the controller with events when we have no file
8411 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
8412 for log messages was already solved from bug 748.)
8413 - Emit a GUARD DROPPED controller event for a case we missed.
8414 - Ensure DNS requests launched by "RESOLVE" commands from the
8415 controller respect the __LeaveStreamsUnattached setconf options. The
8416 same goes for requests launched via DNSPort or transparent
8417 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
8419 o Minor bugfixes (config options):
8420 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
8421 Change the limit to 512 characters by removing base64 newlines.
8422 Fixes bug 2752. Fix by Michael Yakubovich.
8423 - Complain if PublishServerDescriptor is given multiple arguments that
8424 include 0 or 1. This configuration will be rejected in the future.
8425 Bugfix on 0.2.0.1-alpha; closes bug 1107.
8426 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
8427 Bugfix on 0.2.0.13-alpha; closes bug 928.
8429 o Minor bugfixes (log subsystem fixes):
8430 - When unable to format an address as a string, report its value
8431 as "???" rather than reusing the last formatted address. Bugfix
8433 - Be more consistent in our treatment of file system paths. "~" should
8434 get expanded to the user's home directory in the Log config option.
8435 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
8436 feature for the -f and --DataDirectory options.
8438 o Minor bugfixes (memory management):
8439 - Don't stack-allocate the list of supplementary GIDs when we're
8440 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
8441 could take up to 256K, which is way too much stack. Found by
8442 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
8443 - Save a couple bytes in memory allocation every time we escape
8444 certain characters in a string. Patch from Florian Zumbiehl.
8446 o Minor bugfixes (protocol correctness):
8447 - When checking for 1024-bit keys, check for 1024 bits, not 128
8448 bytes. This allows Tor to correctly discard keys of length 1017
8449 through 1023. Bugfix on 0.0.9pre5.
8450 - Require that introduction point keys and onion handshake keys
8451 have a public exponent of 65537. Starts to fix bug 3207; bugfix
8453 - Handle SOCKS messages longer than 128 bytes long correctly, rather
8454 than waiting forever for them to finish. Fixes bug 2330; bugfix
8455 on 0.2.0.16-alpha. Found by doorss.
8456 - Never relay a cell for a circuit we have already destroyed.
8457 Between marking a circuit as closeable and finally closing it,
8458 it may have been possible for a few queued cells to get relayed,
8459 even though they would have been immediately dropped by the next
8460 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
8461 - Never queue a cell for a circuit that's already been marked
8463 - Fix a spec conformance issue: the network-status-version token
8464 must be the first token in a v3 consensus or vote. Discovered by
8465 "parakeep". Bugfix on 0.2.0.3-alpha.
8466 - A networkstatus vote must contain exactly one signature. Spec
8467 conformance issue. Bugfix on 0.2.0.3-alpha.
8468 - When asked about a DNS record type we don't support via a
8469 client DNSPort, reply with NOTIMPL rather than an empty
8470 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
8471 - Make more fields in the controller protocol case-insensitive, since
8472 control-spec.txt said they were.
8474 o Minor bugfixes (log messages):
8475 - Fix a log message that said "bits" while displaying a value in
8476 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
8478 - Downgrade "no current certificates known for authority" message from
8479 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
8480 - Correctly describe errors that occur when generating a TLS object.
8481 Previously we would attribute them to a failure while generating a
8482 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
8484 - Fix an instance where a Tor directory mirror might accidentally
8485 log the IP address of a misbehaving Tor client. Bugfix on
8487 - Stop logging at severity 'warn' when some other Tor client tries
8488 to establish a circuit with us using weak DH keys. It's a protocol
8489 violation, but that doesn't mean ordinary users need to hear about
8490 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
8491 - If your relay can't keep up with the number of incoming create
8492 cells, it would log one warning per failure into your logs. Limit
8493 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
8495 o Minor bugfixes (build fixes):
8496 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
8497 - When warning about missing zlib development packages during compile,
8498 give the correct package names. Bugfix on 0.2.0.1-alpha.
8499 - Fix warnings that newer versions of autoconf produce during
8500 ./autogen.sh. These warnings appear to be harmless in our case,
8501 but they were extremely verbose. Fixes bug 2020.
8502 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
8505 o Minor bugfixes (portability):
8506 - Write several files in text mode, on OSes that distinguish text
8507 mode from binary mode (namely, Windows). These files are:
8508 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
8509 that collect those statistics; 'client_keys' and 'hostname' for
8510 hidden services that use authentication; and (in the tor-gencert
8511 utility) newly generated identity and signing keys. Previously,
8512 we wouldn't specify text mode or binary mode, leading to an
8513 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
8514 the DirRecordUsageByCountry option which would have triggered
8515 the assertion failure was added), although this assertion failure
8516 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
8517 - Selectively disable deprecation warnings on OS X because Lion
8518 started deprecating the shipped copy of openssl. Fixes bug 3643.
8519 - Use a wide type to hold sockets when built for 64-bit Windows.
8521 - Fix an issue that prevented static linking of libevent on
8522 some platforms (notably Linux). Fixes bug 2698; bugfix on 0.2.1.23,
8523 where we introduced the "--with-static-libevent" configure option.
8524 - Fix a bug with our locking implementation on Windows that couldn't
8525 correctly detect when a file was already locked. Fixes bug 2504,
8526 bugfix on 0.2.1.6-alpha.
8527 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
8529 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
8530 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
8533 o Minor bugfixes (code correctness):
8534 - Always NUL-terminate the sun_path field of a sockaddr_un before
8535 passing it to the kernel. (Not a security issue: kernels are
8536 smart enough to reject bad sockaddr_uns.) Found by Coverity;
8537 CID #428. Bugfix on Tor 0.2.0.3-alpha.
8538 - Make connection_printf_to_buf()'s behavior sane. Its callers
8539 expect it to emit a CRLF iff the format string ends with CRLF;
8540 it actually emitted a CRLF iff (a) the format string ended with
8541 CRLF or (b) the resulting string was over 1023 characters long or
8542 (c) the format string did not end with CRLF *and* the resulting
8543 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
8544 fixes part of bug 3407.
8545 - Make send_control_event_impl()'s behavior sane. Its callers
8546 expect it to always emit a CRLF at the end of the string; it
8547 might have emitted extra control characters as well. Bugfix on
8548 0.1.1.9-alpha; fixes another part of bug 3407.
8549 - Make crypto_rand_int() check the value of its input correctly.
8550 Previously, it accepted values up to UINT_MAX, but could return a
8551 negative number if given a value above INT_MAX+1. Found by George
8552 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
8553 - Fix a potential null-pointer dereference while computing a
8554 consensus. Bugfix on 0.2.0.3-alpha, found with the help of
8556 - If we fail to compute the identity digest of a v3 legacy keypair,
8557 warn, and don't use a buffer-full of junk instead. Bugfix on
8558 0.2.1.1-alpha; fixes bug 3106.
8559 - Resolve an untriggerable issue in smartlist_string_num_isin(),
8560 where if the function had ever in the future been used to check
8561 for the presence of a too-large number, it would have given an
8562 incorrect result. (Fortunately, we only used it for 16-bit
8563 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
8564 - Be more careful about reporting the correct error from a failed
8565 connect() system call. Under some circumstances, it was possible to
8566 look at an incorrect value for errno when sending the end reason.
8567 Bugfix on 0.1.0.1-rc.
8568 - Correctly handle an "impossible" overflow cases in connection byte
8569 counting, where we write or read more than 4GB on an edge connection
8570 in a single second. Bugfix on 0.1.2.8-beta.
8571 - Avoid a double mark-for-free warning when failing to attach a
8572 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
8574 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
8575 found by "cypherpunks". This bug was introduced before the first
8576 Tor release, in svn commit r110.
8577 - Fix a bug in bandwidth history state parsing that could have been
8578 triggered if a future version of Tor ever changed the timing
8579 granularity at which bandwidth history is measured. Bugfix on
8581 - Add assertions to check for overflow in arguments to
8582 base32_encode() and base32_decode(); fix a signed-unsigned
8583 comparison there too. These bugs are not actually reachable in Tor,
8584 but it's good to prevent future errors too. Found by doorss.
8585 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
8587 - Set target port in get_interface_address6() correctly. Bugfix
8588 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
8589 - Fix an impossible-to-actually-trigger buffer overflow in relay
8590 descriptor generation. Bugfix on 0.1.0.15.
8591 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
8593 o Minor bugfixes (code improvements):
8594 - After we free an internal connection structure, overwrite it
8595 with a different memory value than we use for overwriting a freed
8596 internal circuit structure. Should help with debugging. Suggested
8598 - If OpenSSL fails to make a duplicate of a private or public key, log
8599 an error message and try to exit cleanly. May help with debugging
8600 if bug 1209 ever remanifests.
8601 - Some options used different conventions for uppercasing of acronyms
8602 when comparing manpage and source. Fix those in favor of the
8603 manpage, as it makes sense to capitalize acronyms.
8604 - Take a first step towards making or.h smaller by splitting out
8605 function definitions for all source files in src/or/. Leave
8606 structures and defines in or.h for now.
8607 - Remove a few dead assignments during router parsing. Found by
8609 - Don't use 1-bit wide signed bit fields. Found by coverity.
8610 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
8611 None of the cases where we did this before were wrong, but by making
8612 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
8613 - The memarea code now uses a sentinel value at the end of each area
8614 to make sure nothing writes beyond the end of an area. This might
8615 help debug some conceivable causes of bug 930.
8616 - Always treat failure to allocate an RSA key as an unrecoverable
8618 - Add some more defensive programming for architectures that can't
8619 handle unaligned integer accesses. We don't know of any actual bugs
8620 right now, but that's the best time to fix them. Fixes bug 1943.
8622 o Minor bugfixes (misc):
8623 - Fix a rare bug in rend_fn unit tests: we would fail a test when
8624 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
8625 on 0.2.0.10-alpha; fixes bug 1808.
8626 - Where available, use Libevent 2.0's periodic timers so that our
8627 once-per-second cleanup code gets called even more closely to
8628 once per second than it would otherwise. Fixes bug 943.
8629 - Ignore OutboundBindAddress when connecting to localhost.
8630 Connections to localhost need to come _from_ localhost, or else
8631 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
8633 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
8635 - If any of the v3 certs we download are unparseable, we should
8636 actually notice the failure so we don't retry indefinitely. Bugfix
8637 on 0.2.0.x; reported by "rotator".
8638 - When Tor fails to parse a descriptor of any kind, dump it to disk.
8639 Might help diagnosing bug 1051.
8640 - Make our 'torify' script more portable; if we have only one of
8641 'torsocks' or 'tsocks' installed, don't complain to the user;
8642 and explain our warning about tsocks better.
8643 - Fix some urls in the exit notice file and make it XHTML1.1 strict
8644 compliant. Based on a patch from Christian Kujau.
8646 o Documentation changes:
8647 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
8648 - Resolve all doxygen warnings except those for missing documentation.
8650 - Add doxygen documentation for more functions, fields, and types.
8651 - Convert the HACKING file to asciidoc, and add a few new sections
8652 to it, explaining how we use Git, how we make changelogs, and
8653 what should go in a patch.
8654 - Document the default socks host and port (127.0.0.1:9050) for
8656 - Removed some unnecessary files from the source distribution. The
8657 AUTHORS file has now been merged into the people page on the
8658 website. The roadmaps and design doc can now be found in the
8659 projects directory in svn.
8661 o Deprecated and removed features (config):
8662 - Remove the torrc.complete file. It hasn't been kept up to date
8663 and users will have better luck checking out the manpage.
8664 - Remove the HSAuthorityRecordStats option that version 0 hidden
8665 service authorities could use to track statistics of overall v0
8666 hidden service usage.
8667 - Remove the obsolete "NoPublish" option; it has been flagged
8668 as obsolete and has produced a warning since 0.1.1.18-rc.
8669 - Caches no longer download and serve v2 networkstatus documents
8670 unless FetchV2Networkstatus flag is set: these documents haven't
8671 haven't been used by clients or relays since 0.2.0.x. Resolves
8674 o Deprecated and removed features (controller):
8675 - The controller no longer accepts the old obsolete "addr-mappings/"
8676 or "unregistered-servers-" GETINFO values.
8677 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
8678 always on; using them is necessary for correct forward-compatible
8681 o Deprecated and removed features (misc):
8682 - Hidden services no longer publish version 0 descriptors, and clients
8683 do not request or use version 0 descriptors. However, the old hidden
8684 service authorities still accept and serve version 0 descriptors
8685 when contacted by older hidden services/clients.
8686 - Remove undocumented option "-F" from tor-resolve: it hasn't done
8687 anything since 0.2.1.16-rc.
8688 - Remove everything related to building the expert bundle for OS X.
8689 It has confused many users, doesn't work right on OS X 10.6,
8690 and is hard to get rid of once installed. Resolves bug 1274.
8691 - Remove support for .noconnect style addresses. Nobody was using
8692 them, and they provided another avenue for detecting Tor users
8693 via application-level web tricks.
8694 - When we fixed bug 1038 we had to put in a restriction not to send
8695 RELAY_EARLY cells on rend circuits. This was necessary as long
8696 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
8697 active. Now remove this obsolete check. Resolves bug 2081.
8698 - Remove workaround code to handle directory responses from servers
8699 that had bug 539 (they would send HTTP status 503 responses _and_
8700 send a body too). Since only server versions before
8701 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
8702 keep the workaround in place.
8703 - Remove the old 'fuzzy time' logic. It was supposed to be used for
8704 handling calculations where we have a known amount of clock skew and
8705 an allowed amount of unknown skew. But we only used it in three
8706 places, and we never adjusted the known/unknown skew values. This is
8707 still something we might want to do someday, but if we do, we'll
8708 want to do it differently.
8709 - Remove the "--enable-iphone" option to ./configure. According to
8710 reports from Marco Bonetti, Tor builds fine without any special
8711 tweaking on recent iPhone SDK versions.
8714 Changes in version 0.2.1.30 - 2011-02-23
8715 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
8716 change is a slight tweak to Tor's TLS handshake that makes relays
8717 and bridges that run this new version reachable from Iran again.
8718 We don't expect this tweak will win the arms race long-term, but it
8719 buys us time until we roll out a better solution.
8722 - Stop sending a CLOCK_SKEW controller status event whenever
8723 we fetch directory information from a relay that has a wrong clock.
8724 Instead, only inform the controller when it's a trusted authority
8725 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
8726 the rest of bug 1074.
8727 - Fix a bounds-checking error that could allow an attacker to
8728 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
8730 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
8731 Tor would ignore their RelayBandwidthBurst setting,
8732 potentially using more bandwidth than expected. Bugfix on
8733 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
8734 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
8735 hidserv" in her torrc. The 'hidserv' argument never controlled
8736 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
8739 - Adjust our TLS Diffie-Hellman parameters to match those used by
8741 - Update to the February 1 2011 Maxmind GeoLite Country database.
8744 - Check for and reject overly long directory certificates and
8745 directory tokens before they have a chance to hit any assertions.
8746 Bugfix on 0.2.1.28. Found by "doorss".
8747 - Bring the logic that gathers routerinfos and assesses the
8748 acceptability of circuits into line. This prevents a Tor OP from
8749 getting locked in a cycle of choosing its local OR as an exit for a
8750 path (due to a .exit request) and then rejecting the circuit because
8751 its OR is not listed yet. It also prevents Tor clients from using an
8752 OR running in the same instance as an exit (due to a .exit request)
8753 if the OR does not meet the same requirements expected of an OR
8754 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
8756 o Packaging changes:
8757 - Stop shipping the Tor specs files and development proposal documents
8758 in the tarball. They are now in a separate git repository at
8759 git://git.torproject.org/torspec.git
8760 - Do not include Git version tags as though they are SVN tags when
8761 generating a tarball from inside a repository that has switched
8762 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
8765 Changes in version 0.2.1.29 - 2011-01-15
8766 Tor 0.2.1.29 continues our recent code security audit work. The main
8767 fix resolves a remote heap overflow vulnerability that can allow remote
8768 code execution. Other fixes address a variety of assert and crash bugs,
8769 most of which we think are hard to exploit remotely.
8771 o Major bugfixes (security):
8772 - Fix a heap overflow bug where an adversary could cause heap
8773 corruption. This bug probably allows remote code execution
8774 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
8776 - Prevent a denial-of-service attack by disallowing any
8777 zlib-compressed data whose compression factor is implausibly
8778 high. Fixes part of bug 2324; reported by "doorss".
8779 - Zero out a few more keys in memory before freeing them. Fixes
8780 bug 2384 and part of bug 2385. These key instances found by
8781 "cypherpunks", based on Andrew Case's report about being able
8782 to find sensitive data in Tor's memory space if you have enough
8783 permissions. Bugfix on 0.0.2pre9.
8785 o Major bugfixes (crashes):
8786 - Prevent calls to Libevent from inside Libevent log handlers.
8787 This had potential to cause a nasty set of crashes, especially
8788 if running Libevent with debug logging enabled, and running
8789 Tor with a controller watching for low-severity log messages.
8790 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
8791 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
8792 underflow errors there too. Fixes the other part of bug 2324.
8793 - Fix a bug where we would assert if we ever had a
8794 cached-descriptors.new file (or another file read directly into
8795 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
8796 on 0.2.1.25. Found by doorss.
8797 - Fix some potential asserts and parsing issues with grossly
8798 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
8801 o Minor bugfixes (other):
8802 - Fix a bug with handling misformed replies to reverse DNS lookup
8803 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
8804 bug reported by doorss.
8805 - Fix compilation on mingw when a pthreads compatibility library
8806 has been installed. (We don't want to use it, so we shouldn't
8807 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
8808 - Fix a bug where we would declare that we had run out of virtual
8809 addresses when the address space was only half-exhausted. Bugfix
8811 - Correctly handle the case where AutomapHostsOnResolve is set but
8812 no virtual addresses are available. Fixes bug 2328; bugfix on
8813 0.1.2.1-alpha. Bug found by doorss.
8814 - Correctly handle wrapping around when we run out of virtual
8815 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
8818 - Update to the January 1 2011 Maxmind GeoLite Country database.
8819 - Introduce output size checks on all of our decryption functions.
8822 - Tor does not build packages correctly with Automake 1.6 and earlier;
8823 added a check to Makefile.am to make sure that we're building with
8824 Automake 1.7 or later.
8825 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
8826 because we built it with a too-old version of automake. Thus that
8827 release broke ./configure --enable-openbsd-malloc, which is popular
8828 among really fast exit relays on Linux.
8831 Changes in version 0.2.1.28 - 2010-12-17
8832 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
8833 exploitable bugs. We also took this opportunity to change the IP address
8834 for one of our directory authorities, and to update the geoip database
8838 - Fix a remotely exploitable bug that could be used to crash instances
8839 of Tor remotely by overflowing on the heap. Remote-code execution
8840 hasn't been confirmed, but can't be ruled out. Everyone should
8841 upgrade. Bugfix on the 0.1.1 series and later.
8843 o Directory authority changes:
8844 - Change IP address and ports for gabelmoo (v3 directory authority).
8847 - Update to the December 1 2010 Maxmind GeoLite Country database.
8850 Changes in version 0.2.1.27 - 2010-11-23
8851 Yet another OpenSSL security patch broke its compatibility with Tor:
8852 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
8853 also took this opportunity to fix several crash bugs, integrate a new
8854 directory authority, and update the bundled GeoIP database.
8857 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
8858 No longer set the tlsext_host_name extension on server SSL objects;
8859 but continue to set it on client SSL objects. Our goal in setting
8860 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
8861 bugfix on 0.2.1.1-alpha.
8862 - Do not log messages to the controller while shrinking buffer
8863 freelists. Doing so would sometimes make the controller connection
8864 try to allocate a buffer chunk, which would mess up the internals
8865 of the freelist and cause an assertion failure. Fixes bug 1125;
8866 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
8867 - Learn our external IP address when we're a relay or bridge, even if
8868 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
8869 where we introduced bridge relays that don't need to publish to
8870 be useful. Fixes bug 2050.
8871 - Do even more to reject (and not just ignore) annotations on
8872 router descriptors received anywhere but from the cache. Previously
8873 we would ignore such annotations at first, but cache them to disk
8874 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
8875 - When you're using bridges and your network goes away and your
8876 bridges get marked as down, recover when you attempt a new socks
8877 connection (if the network is back), rather than waiting up to an
8878 hour to try fetching new descriptors for your bridges. Bugfix on
8879 0.2.0.3-alpha; fixes bug 1981.
8882 - Move to the November 2010 Maxmind GeoLite country db (rather
8883 than the June 2009 ip-to-country GeoIP db) for our statistics that
8884 count how many users relays are seeing from each country. Now we'll
8885 have more accurate data, especially for many African countries.
8887 o New directory authorities:
8888 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
8892 - Fix an assertion failure that could occur in directory caches or
8893 bridge users when using a very short voting interval on a testing
8894 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
8896 - Enforce multiplicity rules when parsing annotations. Bugfix on
8897 0.2.0.8-alpha. Found by piebeer.
8898 - Allow handshaking OR connections to take a full KeepalivePeriod
8899 seconds to handshake. Previously, we would close them after
8900 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
8901 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
8903 - When building with --enable-gcc-warnings on OpenBSD, disable
8904 warnings in system headers. This makes --enable-gcc-warnings
8905 pass on OpenBSD 4.8.
8908 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
8909 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
8910 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
8911 Servers can start sending this code when enough clients recognize
8912 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
8913 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
8914 Patch from mingw-san.
8917 - Remove the old debian/ directory from the main Tor distribution.
8918 The official Tor-for-debian git repository lives at the URL
8919 https://git.torproject.org/debian/tor.git
8920 - Stop shipping the old doc/website/ directory in the tarball. We
8921 changed the website format in late 2010, and what we shipped in
8922 0.2.1.26 really wasn't that useful anyway.
8925 Changes in version 0.2.1.26 - 2010-05-02
8926 Tor 0.2.1.26 addresses the recent connection and memory overload
8927 problems we've been seeing on relays, especially relays with their
8928 DirPort open. If your relay has been crashing, or you turned it off
8929 because it used too many resources, give this release a try.
8931 This release also fixes yet another instance of broken OpenSSL libraries
8932 that was causing some relays to drop out of the consensus.
8935 - Teach relays to defend themselves from connection overload. Relays
8936 now close idle circuits early if it looks like they were intended
8937 for directory fetches. Relays are also more aggressive about closing
8938 TLS connections that have no circuits on them. Such circuits are
8939 unlikely to be re-used, and tens of thousands of them were piling
8940 up at the fast relays, causing the relays to run out of sockets
8941 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
8942 their directory fetches over TLS).
8943 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
8944 that claim to be earlier than 0.9.8m, but which have in reality
8945 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
8946 behavior. Possible fix for some cases of bug 1346.
8947 - Directory mirrors were fetching relay descriptors only from v2
8948 directory authorities, rather than v3 authorities like they should.
8949 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
8950 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
8953 - Finally get rid of the deprecated and now harmful notion of "clique
8954 mode", where directory authorities maintain TLS connections to
8958 - In the util/threads test, no longer free the test_mutex before all
8959 worker threads have finished. Bugfix on 0.2.1.6-alpha.
8960 - The master thread could starve the worker threads quite badly on
8961 certain systems, causing them to run only partially in the allowed
8962 window. This resulted in test failures. Now the master thread sleeps
8963 occasionally for a few microseconds while the two worker-threads
8964 compete for the mutex. Bugfix on 0.2.0.1-alpha.
8967 Changes in version 0.2.1.25 - 2010-03-16
8968 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
8969 prevent relays from guessing their IP address correctly. It also fixes
8970 several minor potential security bugs.
8973 - Fix a regression from our patch for bug 1244 that caused relays
8974 to guess their IP address incorrectly if they didn't set Address
8975 in their torrc and/or their address fails to resolve. Bugfix on
8976 0.2.1.23; fixes bug 1269.
8977 - When freeing a session key, zero it out completely. We only zeroed
8978 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
8979 patched by ekir. Fixes bug 1254.
8982 - Fix a dereference-then-NULL-check sequence when publishing
8983 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
8985 - Fix another dereference-then-NULL-check sequence. Bugfix on
8986 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
8987 - Make sure we treat potentially not NUL-terminated strings correctly.
8988 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
8991 Changes in version 0.2.1.24 - 2010-02-21
8992 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
8996 - Work correctly out-of-the-box with even more vendor-patched versions
8997 of OpenSSL. In particular, make it so Debian and OS X don't need
8998 customized patches to run/build.
9001 Changes in version 0.2.1.23 - 2010-02-13
9002 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
9003 again on the latest OS X, and updates the location of a directory
9006 o Major bugfixes (performance):
9007 - We were selecting our guards uniformly at random, and then weighting
9008 which of our guards we'd use uniformly at random. This imbalance
9009 meant that Tor clients were severely limited on throughput (and
9010 probably latency too) by the first hop in their circuit. Now we
9011 select guards weighted by currently advertised bandwidth. We also
9012 automatically discard guards picked using the old algorithm. Fixes
9013 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
9016 - Make Tor work again on the latest OS X: when deciding whether to
9017 use strange flags to turn TLS renegotiation on, detect the OpenSSL
9018 version at run-time, not compile time. We need to do this because
9019 Apple doesn't update its dev-tools headers when it updates its
9020 libraries in a security patch.
9021 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
9022 that could happen on 32-bit platforms with 64-bit time_t. Also fix
9023 a memory leak when requesting a hidden service descriptor we've
9024 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
9028 - Refactor resolve_my_address() to not use gethostbyname() anymore.
9029 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
9032 - Avoid a mad rush at the beginning of each month when each client
9033 rotates half of its guards. Instead we spread the rotation out
9034 throughout the month, but we still avoid leaving a precise timestamp
9035 in the state file about when we first picked the guard. Improves
9036 over the behavior introduced in 0.1.2.17.
9039 Changes in version 0.2.1.22 - 2010-01-19
9040 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
9041 authorities -- it would tell you its whole history of bridge descriptors
9042 if you make the right directory request. This stable update also
9043 rotates two of the seven v3 directory authority keys and locations.
9045 o Directory authority changes:
9046 - Rotate keys (both v3 identity and relay identity) for moria1
9050 - Stop bridge directory authorities from answering dbg-stability.txt
9051 directory queries, which would let people fetch a list of all
9052 bridge identities they track. Bugfix on 0.2.1.6-alpha.
9055 Changes in version 0.2.1.21 - 2009-12-21
9056 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
9057 library. If you use Tor on Linux / Unix and you're getting SSL
9058 renegotiation errors, upgrading should help. We also recommend an
9059 upgrade if you're an exit relay.
9062 - Work around a security feature in OpenSSL 0.9.8l that prevents our
9063 handshake from working unless we explicitly tell OpenSSL that we
9064 are using SSL renegotiation safely. We are, of course, but OpenSSL
9065 0.9.8l won't work unless we say we are.
9066 - Avoid crashing if the client is trying to upload many bytes and the
9067 circuit gets torn down at the same time, or if the flip side
9068 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
9071 - Do not refuse to learn about authority certs and v2 networkstatus
9072 documents that are older than the latest consensus. This bug might
9073 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
9074 Spotted and fixed by xmux.
9075 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
9076 trigger platform-specific option misparsing case found by Coverity
9078 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
9079 trigger assert. Fixes bug 1173.
9082 Changes in version 0.2.1.20 - 2009-10-15
9083 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
9084 services at once, prepares for more performance improvements, and
9085 fixes a bunch of smaller bugs.
9087 The Windows and OS X bundles also include a more recent Vidalia,
9088 and switch from Privoxy to Polipo.
9090 The OS X installers are now drag and drop. It's best to un-install
9091 Tor/Vidalia and then install this new bundle, rather than upgrade. If
9092 you want to upgrade, you'll need to update the paths for Tor and Polipo
9093 in the Vidalia Settings window.
9096 - Send circuit or stream sendme cells when our window has decreased
9097 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
9098 by Karsten when testing the "reduce circuit window" performance
9099 patch. Bugfix on the 54th commit on Tor -- from July 2002,
9100 before the release of Tor 0.0.0. This is the new winner of the
9102 - Fix a remotely triggerable memory leak when a consensus document
9103 contains more than one signature from the same voter. Bugfix on
9105 - Avoid segfault in rare cases when finishing an introduction circuit
9106 as a client and finding out that we don't have an introduction key
9107 for it. Fixes bug 1073. Reported by Aaron Swartz.
9110 - Tor now reads the "circwindow" parameter out of the consensus,
9111 and uses that value for its circuit package window rather than the
9112 default of 1000 cells. Begins the implementation of proposal 168.
9114 o New directory authorities:
9115 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
9117 - Move moria1 and tonga to alternate IP addresses.
9120 - Fix a signed/unsigned compile warning in 0.2.1.19.
9121 - Fix possible segmentation fault on directory authorities. Bugfix on
9123 - Fix an extremely rare infinite recursion bug that could occur if
9124 we tried to log a message after shutting down the log subsystem.
9125 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
9126 - Fix an obscure bug where hidden services on 64-bit big-endian
9127 systems might mis-read the timestamp in v3 introduce cells, and
9128 refuse to connect back to the client. Discovered by "rotor".
9129 Bugfix on 0.2.1.6-alpha.
9130 - We were triggering a CLOCK_SKEW controller status event whenever
9131 we connect via the v2 connection protocol to any relay that has
9132 a wrong clock. Instead, we should only inform the controller when
9133 it's a trusted authority that claims our clock is wrong. Bugfix
9134 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
9135 - We were telling the controller about CHECKING_REACHABILITY and
9136 REACHABILITY_FAILED status events whenever we launch a testing
9137 circuit or notice that one has failed. Instead, only tell the
9138 controller when we want to inform the user of overall success or
9139 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
9141 - Don't warn when we're using a circuit that ends with a node
9142 excluded in ExcludeExitNodes, but the circuit is not used to access
9143 the outside world. This should help fix bug 1090. Bugfix on
9145 - Work around a small memory leak in some versions of OpenSSL that
9146 stopped the memory used by the hostname TLS extension from being
9150 - Add a "getinfo status/accepted-server-descriptor" controller
9151 command, which is the recommended way for controllers to learn
9152 whether our server descriptor has been successfully received by at
9153 least on directory authority. Un-recommend good-server-descriptor
9154 getinfo and status events until we have a better design for them.
9157 Changes in version 0.2.1.19 - 2009-07-28
9158 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
9162 - Make accessing hidden services on 0.2.1.x work right again.
9163 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
9164 part of patch provided by "optimist".
9167 - When a relay/bridge is writing out its identity key fingerprint to
9168 the "fingerprint" file and to its logs, write it without spaces. Now
9169 it will look like the fingerprints in our bridges documentation,
9170 and confuse fewer users.
9173 - Relays no longer publish a new server descriptor if they change
9174 their MaxAdvertisedBandwidth config option but it doesn't end up
9175 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
9176 fixes bug 1026. Patch from Sebastian.
9177 - Avoid leaking memory every time we get a create cell but we have
9178 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
9179 fixes bug 1034. Reported by BarkerJr.
9182 Changes in version 0.2.1.18 - 2009-07-24
9183 Tor 0.2.1.18 lays the foundations for performance improvements,
9184 adds status events to help users diagnose bootstrap problems, adds
9185 optional authentication/authorization for hidden services, fixes a
9186 variety of potential anonymity problems, and includes a huge pile of
9187 other features and bug fixes.
9189 o Major features (clients):
9190 - Start sending "bootstrap phase" status events to the controller,
9191 so it can keep the user informed of progress fetching directory
9192 information and establishing circuits. Also inform the controller
9193 if we think we're stuck at a particular bootstrap phase. Implements
9195 - Clients replace entry guards that were chosen more than a few months
9196 ago. This change should significantly improve client performance,
9197 especially once more people upgrade, since relays that have been
9198 a guard for a long time are currently overloaded.
9199 - Network status consensus documents and votes now contain bandwidth
9200 information for each relay. Clients use the bandwidth values
9201 in the consensus, rather than the bandwidth values in each
9202 relay descriptor. This approach opens the door to more accurate
9203 bandwidth estimates once the directory authorities start doing
9204 active measurements. Implements part of proposal 141.
9206 o Major features (relays):
9207 - Disable and refactor some debugging checks that forced a linear scan
9208 over the whole server-side DNS cache. These accounted for over 50%
9209 of CPU time on a relatively busy exit node's gprof profile. Also,
9210 disable some debugging checks that appeared in exit node profile
9211 data. Found by Jacob.
9212 - New DirPortFrontPage option that takes an html file and publishes
9213 it as "/" on the DirPort. Now relay operators can provide a
9214 disclaimer without needing to set up a separate webserver. There's
9215 a sample disclaimer in contrib/tor-exit-notice.html.
9217 o Major features (hidden services):
9218 - Make it possible to build hidden services that only certain clients
9219 are allowed to connect to. This is enforced at several points,
9220 so that unauthorized clients are unable to send INTRODUCE cells
9221 to the service, or even (depending on the type of authentication)
9222 to learn introduction points. This feature raises the bar for
9223 certain kinds of active attacks against hidden services. Design
9224 and code by Karsten Loesing. Implements proposal 121.
9225 - Relays now store and serve v2 hidden service descriptors by default,
9226 i.e., the new default value for HidServDirectoryV2 is 1. This is
9227 the last step in proposal 114, which aims to make hidden service
9228 lookups more reliable.
9230 o Major features (path selection):
9231 - ExitNodes and Exclude*Nodes config options now allow you to restrict
9232 by country code ("{US}") or IP address or address pattern
9233 ("255.128.0.0/16"). Patch from Robert Hogan. It still needs some
9234 refinement to decide what config options should take priority if
9235 you ask to both use a particular node and exclude it.
9237 o Major features (misc):
9238 - When building a consensus, do not include routers that are down.
9239 This cuts down 30% to 40% on consensus size. Implements proposal
9241 - New TestingTorNetwork config option to allow adjustment of
9242 previously constant values that could slow bootstrapping. Implements
9243 proposal 135. Patch from Karsten.
9244 - Convert many internal address representations to optionally hold
9245 IPv6 addresses. Generate and accept IPv6 addresses in many protocol
9246 elements. Make resolver code handle nameservers located at IPv6
9248 - More work on making our TLS handshake blend in: modify the list
9249 of ciphers advertised by OpenSSL in client mode to even more
9250 closely resemble a common web browser. We cheat a little so that
9251 we can advertise ciphers that the locally installed OpenSSL doesn't
9253 - Use the TLS1 hostname extension to more closely resemble browser
9256 o Security fixes (anonymity/entropy):
9257 - Never use a connection with a mismatched address to extend a
9258 circuit, unless that connection is canonical. A canonical
9259 connection is one whose address is authenticated by the router's
9260 identity key, either in a NETINFO cell or in a router descriptor.
9261 - Implement most of proposal 110: The first K cells to be sent
9262 along a circuit are marked as special "early" cells; only K "early"
9263 cells will be allowed. Once this code is universal, we can block
9264 certain kinds of denial-of-service attack by requiring that EXTEND
9265 commands must be sent using an "early" cell.
9266 - Resume using OpenSSL's RAND_poll() for better (and more portable)
9267 cross-platform entropy collection again. We used to use it, then
9268 stopped using it because of a bug that could crash systems that
9269 called RAND_poll when they had a lot of fds open. It looks like the
9270 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
9271 at startup, and to call RAND_poll() when we reseed later only if
9272 we have a non-buggy OpenSSL version.
9273 - When the client is choosing entry guards, now it selects at most
9274 one guard from a given relay family. Otherwise we could end up with
9275 all of our entry points into the network run by the same operator.
9276 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
9277 - Do not use or believe expired v3 authority certificates. Patch
9278 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
9279 - Drop begin cells to a hidden service if they come from the middle
9280 of a circuit. Patch from lark.
9281 - When we erroneously receive two EXTEND cells for the same circuit
9282 ID on the same connection, drop the second. Patch from lark.
9283 - Authorities now vote for the Stable flag for any router whose
9284 weighted MTBF is at least 5 days, regardless of the mean MTBF.
9285 - Clients now never report any stream end reason except 'MISC'.
9286 Implements proposal 148.
9288 o Major bugfixes (crashes):
9289 - Parse dates and IPv4 addresses in a locale- and libc-independent
9290 manner, to avoid platform-dependent behavior on malformed input.
9291 - Fix a crash that occurs on exit nodes when a nameserver request
9292 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
9293 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
9295 - Do not assume that a stack-allocated character array will be
9296 64-bit aligned on platforms that demand that uint64_t access is
9297 aligned. Possible fix for bug 604.
9298 - Resolve a very rare crash bug that could occur when the user forced
9299 a nameserver reconfiguration during the middle of a nameserver
9300 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
9301 - Avoid a "0 divided by 0" calculation when calculating router uptime
9302 at directory authorities. Bugfix on 0.2.0.8-alpha.
9303 - Fix an assertion bug in parsing policy-related options; possible fix
9305 - Rate-limit too-many-sockets messages: when they happen, they happen
9306 a lot and end up filling up the disk. Resolves bug 748.
9307 - Fix a race condition that could cause crashes or memory corruption
9308 when running as a server with a controller listening for log
9310 - Avoid crashing when we have a policy specified in a DirPolicy or
9311 SocksPolicy or ReachableAddresses option with ports set on it,
9312 and we re-load the policy. May fix bug 996.
9313 - Fix an assertion failure on 64-bit platforms when we allocated
9314 memory right up to the end of a memarea, then realigned the memory
9315 one step beyond the end. Fixes a possible cause of bug 930.
9316 - Protect the count of open sockets with a mutex, so we can't
9317 corrupt it when two threads are closing or opening sockets at once.
9318 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
9320 o Major bugfixes (clients):
9321 - Discard router descriptors as we load them if they are more than
9322 five days old. Otherwise if Tor is off for a long time and then
9323 starts with cached descriptors, it will try to use the onion keys
9324 in those obsolete descriptors when building circuits. Fixes bug 887.
9325 - When we choose to abandon a new entry guard because we think our
9326 older ones might be better, close any circuits pending on that
9327 new entry guard connection. This fix should make us recover much
9328 faster when our network is down and then comes back. Bugfix on
9329 0.1.2.8-beta; found by lodger.
9330 - When Tor clients restart after 1-5 days, they discard all their
9331 cached descriptors as too old, but they still use the cached
9332 consensus document. This approach is good for robustness, but
9333 bad for performance: since they don't know any bandwidths, they
9334 end up choosing at random rather than weighting their choice by
9335 speed. Fixed by the above feature of putting bandwidths in the
9338 o Major bugfixes (relays):
9339 - Relays were falling out of the networkstatus consensus for
9340 part of a day if they changed their local config but the
9341 authorities discarded their new descriptor as "not sufficiently
9342 different". Now directory authorities accept a descriptor as changed
9343 if BandwidthRate or BandwidthBurst changed. Partial fix for bug 962;
9345 - Ensure that two circuits can never exist on the same connection
9346 with the same circuit ID, even if one is marked for close. This
9347 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
9348 - Directory authorities were neglecting to mark relays down in their
9349 internal histories if the relays fall off the routerlist without
9350 ever being found unreachable. So there were relays in the histories
9351 that haven't been seen for eight months, and are listed as being
9352 up for eight months. This wreaked havoc on the "median wfu" and
9353 "median mtbf" calculations, in turn making Guard and Stable flags
9354 wrong, hurting network performance. Fixes bugs 696 and 969. Bugfix
9357 o Major bugfixes (hidden services):
9358 - When establishing a hidden service, introduction points that
9359 originate from cannibalized circuits were completely ignored
9360 and not included in rendezvous service descriptors. This might
9361 have been another reason for delay in making a hidden service
9362 available. Bugfix from long ago (0.0.9.x?)
9364 o Major bugfixes (memory and resource management):
9365 - Fixed some memory leaks -- some quite frequent, some almost
9366 impossible to trigger -- based on results from Coverity.
9367 - Speed up parsing and cut down on memory fragmentation by using
9368 stack-style allocations for parsing directory objects. Previously,
9369 this accounted for over 40% of allocations from within Tor's code
9370 on a typical directory cache.
9371 - Use a Bloom filter rather than a digest-based set to track which
9372 descriptors we need to keep around when we're cleaning out old
9373 router descriptors. This speeds up the computation significantly,
9374 and may reduce fragmentation.
9376 o New/changed config options:
9377 - Now NodeFamily and MyFamily config options allow spaces in
9378 identity fingerprints, so it's easier to paste them in.
9379 Suggested by Lucky Green.
9380 - Allow ports 465 and 587 in the default exit policy again. We had
9381 rejected them in 0.1.0.15, because back in 2005 they were commonly
9382 misconfigured and ended up as spam targets. We hear they are better
9383 locked down these days.
9384 - Make TrackHostExit mappings expire a while after their last use, not
9385 after their creation. Patch from Robert Hogan.
9386 - Add an ExcludeExitNodes option so users can list a set of nodes
9387 that should be be excluded from the exit node position, but
9388 allowed elsewhere. Implements proposal 151.
9389 - New --hush command-line option similar to --quiet. While --quiet
9390 disables all logging to the console on startup, --hush limits the
9391 output to messages of warning and error severity.
9392 - New configure/torrc options (--enable-geoip-stats,
9393 DirRecordUsageByCountry) to record how many IPs we've served
9394 directory info to in each country code, how many status documents
9395 total we've sent to each country code, and what share of the total
9396 directory requests we should expect to see.
9397 - Make outbound DNS packets respect the OutboundBindAddress setting.
9398 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
9399 - Allow separate log levels to be configured for different logging
9400 domains. For example, this allows one to log all notices, warnings,
9401 or errors, plus all memory management messages of level debug or
9402 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
9403 - Update to the "June 3 2009" ip-to-country file.
9405 o Minor features (relays):
9406 - Raise the minimum rate limiting to be a relay from 20000 bytes
9407 to 20480 bytes (aka 20KB/s), to match our documentation. Also
9408 update directory authorities so they always assign the Fast flag
9409 to relays with 20KB/s of capacity. Now people running relays won't
9410 suddenly find themselves not seeing any use, if the network gets
9412 - If we're a relay and we change our IP address, be more verbose
9413 about the reason that made us change. Should help track down
9414 further bugs for relays on dynamic IP addresses.
9415 - Exit servers can now answer resolve requests for ip6.arpa addresses.
9416 - Implement most of Proposal 152: allow specialized servers to permit
9417 single-hop circuits, and clients to use those servers to build
9418 single-hop circuits when using a specialized controller. Patch
9419 from Josh Albrecht. Resolves feature request 768.
9420 - When relays do their initial bandwidth measurement, don't limit
9421 to just our entry guards for the test circuits. Otherwise we tend
9422 to have multiple test circuits going through a single entry guard,
9423 which makes our bandwidth test less accurate. Fixes part of bug 654;
9424 patch contributed by Josh Albrecht.
9426 o Minor features (directory authorities):
9427 - Try not to open more than one descriptor-downloading connection
9428 to an authority at once. This should reduce load on directory
9429 authorities. Fixes bug 366.
9430 - Add cross-certification to newly generated certificates, so that
9431 a signing key is enough information to look up a certificate. Start
9432 serving certificates by <identity digest, signing key digest>
9433 pairs. Implements proposal 157.
9434 - When a directory authority downloads a descriptor that it then
9435 immediately rejects, do not retry downloading it right away. Should
9436 save some bandwidth on authorities. Fix for bug 888. Patch by
9438 - Directory authorities now serve a /tor/dbg-stability.txt URL to
9439 help debug WFU and MTBF calculations.
9440 - In directory authorities' approved-routers files, allow
9441 fingerprints with or without space.
9443 o Minor features (directory mirrors):
9444 - When a download gets us zero good descriptors, do not notify
9445 Tor that new directory information has arrived.
9446 - Servers support a new URL scheme for consensus downloads that
9447 allows the client to specify which authorities are trusted.
9448 The server then only sends the consensus if the client will trust
9449 it. Otherwise a 404 error is sent back. Clients use this
9450 new scheme when the server supports it (meaning it's running
9451 0.2.1.1-alpha or later). Implements proposal 134.
9453 o Minor features (bridges):
9454 - If the bridge config line doesn't specify a port, assume 443.
9455 This makes bridge lines a bit smaller and easier for users to
9457 - If we're using bridges and our network goes away, be more willing
9458 to forgive our bridges and try again when we get an application
9461 o Minor features (hidden services):
9462 - When the client launches an introduction circuit, retry with a
9463 new circuit after 30 seconds rather than 60 seconds.
9464 - Launch a second client-side introduction circuit in parallel
9465 after a delay of 15 seconds (based on work by Christian Wilms).
9466 - Hidden services start out building five intro circuits rather
9467 than three, and when the first three finish they publish a service
9468 descriptor using those. Now we publish our service descriptor much
9469 faster after restart.
9470 - Drop the requirement to have an open dir port for storing and
9471 serving v2 hidden service descriptors.
9473 o Minor features (build and packaging):
9474 - On Linux, use the prctl call to re-enable core dumps when the User
9476 - Try to make sure that the version of Libevent we're running with
9477 is binary-compatible with the one we built with. May address bug
9479 - Add a new --enable-local-appdata configuration switch to change
9480 the default location of the datadir on win32 from APPDATA to
9481 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
9482 entirely. Patch from coderman.
9483 - Build correctly against versions of OpenSSL 0.9.8 or later that
9484 are built without support for deprecated functions.
9485 - On platforms with a maximum syslog string length, truncate syslog
9486 messages to that length ourselves, rather than relying on the
9487 system to do it for us.
9488 - Automatically detect MacOSX versions earlier than 10.4.0, and
9489 disable kqueue from inside Tor when running with these versions.
9490 We previously did this from the startup script, but that was no
9491 help to people who didn't use the startup script. Resolves bug 863.
9492 - Build correctly when configured to build outside the main source
9493 path. Patch from Michael Gold.
9494 - Disable GCC's strict alias optimization by default, to avoid the
9495 likelihood of its introducing subtle bugs whenever our code violates
9496 the letter of C99's alias rules.
9497 - Change the contrib/tor.logrotate script so it makes the new
9498 logs as "_tor:_tor" rather than the default, which is generally
9499 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
9500 - Change our header file guard macros to be less likely to conflict
9501 with system headers. Adam Langley noticed that we were conflicting
9502 with log.h on Android.
9503 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
9504 and stop using a warning that had become unfixably verbose under
9506 - Use a lockfile to make sure that two Tor processes are not
9507 simultaneously running with the same datadir.
9508 - Allow OpenSSL to use dynamic locks if it wants.
9509 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
9511 o Minor features (controllers):
9512 - When generating circuit events with verbose nicknames for
9513 controllers, try harder to look up nicknames for routers on a
9514 circuit. (Previously, we would look in the router descriptors we had
9515 for nicknames, but not in the consensus.) Partial fix for bug 941.
9516 - New controller event NEWCONSENSUS that lists the networkstatus
9517 lines for every recommended relay. Now controllers like Torflow
9518 can keep up-to-date on which relays they should be using.
9519 - New controller event "clients_seen" to report a geoip-based summary
9520 of which countries we've seen clients from recently. Now controllers
9521 like Vidalia can show bridge operators that they're actually making
9523 - Add a 'getinfo status/clients-seen' controller command, in case
9524 controllers want to hear clients_seen events but connect late.
9525 - New CONSENSUS_ARRIVED event to note when a new consensus has
9526 been fetched and validated.
9527 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
9528 controllers to prevent SIGHUP from reloading the configuration.
9530 - Return circuit purposes in response to GETINFO circuit-status.
9532 - Serve the latest v3 networkstatus consensus via the control
9533 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
9534 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
9535 controller can query our current bootstrap state in case it attaches
9536 partway through and wants to catch up.
9537 - Provide circuit purposes along with circuit events to the controller.
9539 o Minor features (tools):
9540 - Do not have tor-resolve automatically refuse all .onion addresses;
9541 if AutomapHostsOnResolve is set in your torrc, this will work fine.
9542 - Add a -p option to tor-resolve for specifying the SOCKS port: some
9543 people find host:port too confusing.
9544 - Print the SOCKS5 error message string as well as the error code
9545 when a tor-resolve request fails. Patch from Jacob.
9547 o Minor bugfixes (memory and resource management):
9548 - Clients no longer cache certificates for authorities they do not
9549 recognize. Bugfix on 0.2.0.9-alpha.
9550 - Do not use C's stdio library for writing to log files. This will
9551 improve logging performance by a minute amount, and will stop
9552 leaking fds when our disk is full. Fixes bug 861.
9553 - Stop erroneous use of O_APPEND in cases where we did not in fact
9554 want to re-seek to the end of a file before every last write().
9555 - Fix a small alignment and memory-wasting bug on buffer chunks.
9557 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
9558 to avoid unused RAM in buffer chunks and memory pools.
9559 - Reduce the default smartlist size from 32 to 16; it turns out that
9560 most smartlists hold around 8-12 elements tops.
9561 - Make dumpstats() log the fullness and size of openssl-internal
9563 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
9564 patch to their OpenSSL, turn it on to save memory on servers. This
9565 patch will (with any luck) get included in a mainline distribution
9567 - Fix a memory leak when v3 directory authorities load their keys
9568 and cert from disk. Bugfix on 0.2.0.1-alpha.
9569 - Stop using malloc_usable_size() to use more area than we had
9570 actually allocated: it was safe, but made valgrind really unhappy.
9571 - Make the assert_circuit_ok() function work correctly on circuits that
9572 have already been marked for close.
9573 - Fix uninitialized size field for memory area allocation: may improve
9574 memory performance during directory parsing.
9576 o Minor bugfixes (clients):
9577 - Stop reloading the router list from disk for no reason when we
9578 run out of reachable directory mirrors. Once upon a time reloading
9579 it would set the 'is_running' flag back to 1 for them. It hasn't
9580 done that for a long time.
9581 - When we had picked an exit node for a connection, but marked it as
9582 "optional", and it turned out we had no onion key for the exit,
9583 stop wanting that exit and try again. This situation may not
9584 be possible now, but will probably become feasible with proposal
9585 158. Spotted by rovv. Fixes another case of bug 752.
9586 - Fix a bug in address parsing that was preventing bridges or hidden
9587 service targets from being at IPv6 addresses.
9588 - Do not remove routers as too old if we do not have any consensus
9589 document. Bugfix on 0.2.0.7-alpha.
9590 - When an exit relay resolves a stream address to a local IP address,
9591 do not just keep retrying that same exit relay over and
9592 over. Instead, just close the stream. Addresses bug 872. Bugfix
9593 on 0.2.0.32. Patch from rovv.
9594 - Made Tor a little less aggressive about deleting expired
9595 certificates. Partial fix for bug 854.
9596 - Treat duplicate certificate fetches as failures, so that we do
9597 not try to re-fetch an expired certificate over and over and over.
9598 - Do not say we're fetching a certificate when we'll in fact skip it
9599 because of a pending download.
9600 - If we have correct permissions on $datadir, we complain to stdout
9601 and fail to start. But dangerous permissions on
9602 $datadir/cached-status/ would cause us to open a log and complain
9603 there. Now complain to stdout and fail to start in both cases. Fixes
9604 bug 820, reported by seeess.
9606 o Minor bugfixes (bridges):
9607 - When we made bridge authorities stop serving bridge descriptors over
9608 unencrypted links, we also broke DirPort reachability testing for
9609 bridges. So bridges with a non-zero DirPort were printing spurious
9610 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
9611 - Don't allow a bridge to publish its router descriptor to a
9612 non-bridge directory authority. Fixes part of bug 932.
9613 - When we change to or from being a bridge, reset our counts of
9614 client usage by country. Fixes bug 932.
9616 o Minor bugfixes (relays):
9617 - Log correct error messages for DNS-related network errors on
9619 - Actually return -1 in the error case for read_bandwidth_usage().
9620 Harmless bug, since we currently don't care about the return value
9621 anywhere. Bugfix on 0.2.0.9-alpha.
9622 - Provide a more useful log message if bug 977 (related to buffer
9623 freelists) ever reappears, and do not crash right away.
9624 - We were already rejecting relay begin cells with destination port
9625 of 0. Now also reject extend cells with destination port or address
9626 of 0. Suggested by lark.
9627 - When we can't transmit a DNS request due to a network error, retry
9628 it after a while, and eventually transmit a failing response to
9629 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
9630 - Solve a bug that kept hardware crypto acceleration from getting
9631 enabled when accounting was turned on. Fixes bug 907. Bugfix on
9633 - When a canonical connection appears later in our internal list
9634 than a noncanonical one for a given OR ID, always use the
9635 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
9637 - Avoid some nasty corner cases in the logic for marking connections
9638 as too old or obsolete or noncanonical for circuits. Partial
9640 - Fix another interesting corner-case of bug 891 spotted by rovv:
9641 Previously, if two hosts had different amounts of clock drift, and
9642 one of them created a new connection with just the wrong timing,
9643 the other might decide to deprecate the new connection erroneously.
9644 Bugfix on 0.1.1.13-alpha.
9645 - If one win32 nameserver fails to get added, continue adding the
9646 rest, and don't automatically fail.
9647 - Fix a bug where an unreachable relay would establish enough
9648 reachability testing circuits to do a bandwidth test -- if
9649 we already have a connection to the middle hop of the testing
9650 circuit, then it could establish the last hop by using the existing
9651 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
9652 circuits no longer use entry guards in 0.2.1.3-alpha.
9654 o Minor bugfixes (directory authorities):
9655 - Limit uploaded directory documents to be 16M rather than 500K.
9656 The directory authorities were refusing v3 consensus votes from
9657 other authorities, since the votes are now 504K. Fixes bug 959;
9658 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
9659 - Directory authorities should never send a 503 "busy" response to
9660 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
9662 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
9663 headers. Bugfix on 0.2.0.10-alpha.
9665 o Minor bugfixes (hidden services):
9666 - When we can't find an intro key for a v2 hidden service descriptor,
9667 fall back to the v0 hidden service descriptor and log a bug message.
9668 Workaround for bug 1024.
9669 - In very rare situations new hidden service descriptors were
9670 published earlier than 30 seconds after the last change to the
9671 service. (We currently think that a hidden service descriptor
9672 that's been stable for 30 seconds is worth publishing.)
9673 - If a hidden service sends us an END cell, do not consider
9674 retrying the connection; just close it. Patch from rovv.
9675 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
9676 service directories if they have no advertised dir port. Bugfix
9679 o Minor bugfixes (tools):
9680 - In the torify(1) manpage, mention that tsocks will leak your
9683 o Minor bugfixes (controllers):
9684 - If the controller claimed responsibility for a stream, but that
9685 stream never finished making its connection, it would live
9686 forever in circuit_wait state. Now we close it after SocksTimeout
9687 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
9688 - Make DNS resolved controller events into "CLOSED", not
9689 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
9691 - The control port would close the connection before flushing long
9692 replies, such as the network consensus, if a QUIT command was issued
9693 before the reply had completed. Now, the control port flushes all
9694 pending replies before closing the connection. Also fix a spurious
9695 warning when a QUIT command is issued after a malformed or rejected
9696 AUTHENTICATE command, but before the connection was closed. Patch
9697 by Marcus Griep. Fixes bugs 1015 and 1016.
9698 - Fix a bug that made stream bandwidth get misreported to the
9701 o Deprecated and removed features:
9702 - The old "tor --version --version" command, which would print out
9703 the subversion "Id" of most of the source files, is now removed. It
9704 turned out to be less useful than we'd expected, and harder to
9706 - RedirectExits has been removed. It was deprecated since
9708 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
9709 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
9710 - Cell pools are now always enabled; --disable-cell-pools is ignored.
9711 - Directory mirrors no longer fetch the v1 directory or
9712 running-routers files. They are obsolete, and nobody asks for them
9713 anymore. This is the first step to making v1 authorities obsolete.
9714 - Take out the TestVia config option, since it was a workaround for
9715 a bug that was fixed in Tor 0.1.1.21.
9716 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
9717 HiddenServiceExcludeNodes as obsolete: they never worked properly,
9718 and nobody seems to be using them. Fixes bug 754. Bugfix on
9719 0.1.0.1-rc. Patch from Christian Wilms.
9720 - Remove all backward-compatibility code for relays running
9721 versions of Tor so old that they no longer work at all on the
9724 o Code simplifications and refactoring:
9725 - Tool-assisted documentation cleanup. Nearly every function or
9726 static variable in Tor should have its own documentation now.
9727 - Rename the confusing or_is_obsolete field to the more appropriate
9728 is_bad_for_new_circs, and move it to or_connection_t where it
9730 - Move edge-only flags from connection_t to edge_connection_t: not
9731 only is this better coding, but on machines of plausible alignment,
9732 it should save 4-8 bytes per connection_t. "Every little bit helps."
9733 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
9734 for consistency; keep old option working for backward compatibility.
9735 - Simplify the code for finding connections to use for a circuit.
9736 - Revise the connection_new functions so that a more typesafe variant
9737 exists. This will work better with Coverity, and let us find any
9738 actual mistakes we're making here.
9739 - Refactor unit testing logic so that dmalloc can be used sensibly
9740 with unit tests to check for memory leaks.
9741 - Move all hidden-service related fields from connection and circuit
9742 structure to substructures: this way they won't eat so much memory.
9743 - Squeeze 2-5% out of client performance (according to oprofile) by
9744 improving the implementation of some policy-manipulation functions.
9745 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
9746 be more efficient. Formerly it was quadratic in the number of
9747 servers; now it should be linear. Fixes bug 509.
9748 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
9749 and n_conn_id_digest fields into a separate structure that's
9750 only needed when the circuit has not yet attached to an n_conn.
9751 - Optimize out calls to time(NULL) that occur for every IO operation,
9752 or for every cell. On systems like Windows where time() is a
9753 slow syscall, this fix will be slightly helpful.
9756 Changes in version 0.2.0.35 - 2009-06-24
9758 - Avoid crashing in the presence of certain malformed descriptors.
9759 Found by lark, and by automated fuzzing.
9760 - Fix an edge case where a malicious exit relay could convince a
9761 controller that the client's DNS question resolves to an internal IP
9762 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
9765 - Finally fix the bug where dynamic-IP relays disappear when their
9766 IP address changes: directory mirrors were mistakenly telling
9767 them their old address if they asked via begin_dir, so they
9768 never got an accurate answer about their new address, so they
9769 just vanished after a day. For belt-and-suspenders, relays that
9770 don't set Address in their config now avoid using begin_dir for
9771 all direct connections. Should fix bugs 827, 883, and 900.
9772 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
9773 that would occur on some exit nodes when DNS failures and timeouts
9774 occurred in certain patterns. Fix for bug 957.
9777 - When starting with a cache over a few days old, do not leak
9778 memory for the obsolete router descriptors in it. Bugfix on
9779 0.2.0.33; fixes bug 672.
9780 - Hidden service clients didn't use a cached service descriptor that
9781 was older than 15 minutes, but wouldn't fetch a new one either,
9782 because there was already one in the cache. Now, fetch a v2
9783 descriptor unless the same descriptor was added to the cache within
9784 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
9787 Changes in version 0.2.0.34 - 2009-02-08
9788 Tor 0.2.0.34 features several more security-related fixes. You should
9789 upgrade, especially if you run an exit relay (remote crash) or a
9790 directory authority (remote infinite loop), or you're on an older
9791 (pre-XP) or not-recently-patched Windows (remote exploit).
9793 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
9794 have many known flaws, and nobody should be using them. You should
9795 upgrade. If you're using a Linux or BSD and its packages are obsolete,
9796 stop using those packages and upgrade anyway.
9799 - Fix an infinite-loop bug on handling corrupt votes under certain
9800 circumstances. Bugfix on 0.2.0.8-alpha.
9801 - Fix a temporary DoS vulnerability that could be performed by
9802 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
9803 - Avoid a potential crash on exit nodes when processing malformed
9804 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
9805 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
9806 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
9809 - Fix compilation on systems where time_t is a 64-bit integer.
9810 Patch from Matthias Drochner.
9811 - Don't consider expiring already-closed client connections. Fixes
9812 bug 893. Bugfix on 0.0.2pre20.
9815 Changes in version 0.2.0.33 - 2009-01-21
9816 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
9817 useful to users. It also finally fixes a bug where a relay or client
9818 that's been off for many days would take a long time to bootstrap.
9820 This update also fixes an important security-related bug reported by
9821 Ilja van Sprundel. You should upgrade. (We'll send out more details
9822 about the bug once people have had some time to upgrade.)
9825 - Fix a heap-corruption bug that may be remotely triggerable on
9826 some platforms. Reported by Ilja van Sprundel.
9829 - When a stream at an exit relay is in state "resolving" or
9830 "connecting" and it receives an "end" relay cell, the exit relay
9831 would silently ignore the end cell and not close the stream. If
9832 the client never closes the circuit, then the exit relay never
9833 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
9835 - When sending CREATED cells back for a given circuit, use a 64-bit
9836 connection ID to find the right connection, rather than an addr:port
9837 combination. Now that we can have multiple OR connections between
9838 the same ORs, it is no longer possible to use addr:port to uniquely
9839 identify a connection.
9840 - Bridge relays that had DirPort set to 0 would stop fetching
9841 descriptors shortly after startup, and then briefly resume
9842 after a new bandwidth test and/or after publishing a new bridge
9843 descriptor. Bridge users that try to bootstrap from them would
9844 get a recent networkstatus but would get descriptors from up to
9845 18 hours earlier, meaning most of the descriptors were obsolete
9846 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
9847 - Prevent bridge relays from serving their 'extrainfo' document
9848 to anybody who asks, now that extrainfo docs include potentially
9849 sensitive aggregated client geoip summaries. Bugfix on
9851 - If the cached networkstatus consensus is more than five days old,
9852 discard it rather than trying to use it. In theory it could be
9853 useful because it lists alternate directory mirrors, but in practice
9854 it just means we spend many minutes trying directory mirrors that
9855 are long gone from the network. Also discard router descriptors as
9856 we load them if they are more than five days old, since the onion
9857 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
9860 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
9861 could make gcc generate non-functional binary search code. Bugfix
9863 - Build correctly on platforms without socklen_t.
9864 - Compile without warnings on solaris.
9865 - Avoid potential crash on internal error during signature collection.
9866 Fixes bug 864. Patch from rovv.
9867 - Correct handling of possible malformed authority signing key
9868 certificates with internal signature types. Fixes bug 880.
9869 Bugfix on 0.2.0.3-alpha.
9870 - Fix a hard-to-trigger resource leak when logging credential status.
9872 - When we can't initialize DNS because the network is down, do not
9873 automatically stop Tor from starting. Instead, we retry failed
9874 dns_init() every 10 minutes, and change the exit policy to reject
9875 *:* until one succeeds. Fixes bug 691.
9876 - Use 64 bits instead of 32 bits for connection identifiers used with
9877 the controller protocol, to greatly reduce risk of identifier reuse.
9878 - When we're choosing an exit node for a circuit, and we have
9879 no pending streams, choose a good general exit rather than one that
9880 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
9881 - Fix another case of assuming, when a specific exit is requested,
9882 that we know more than the user about what hosts it allows.
9883 Fixes one case of bug 752. Patch from rovv.
9884 - Clip the MaxCircuitDirtiness config option to a minimum of 10
9885 seconds. Warn the user if lower values are given in the
9886 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
9887 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
9888 user if lower values are given in the configuration. Bugfix on
9889 0.1.1.17-rc. Patch by Sebastian.
9890 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
9891 the cache because we already had a v0 descriptor with the same ID.
9892 Bugfix on 0.2.0.18-alpha.
9893 - Fix a race condition when freeing keys shared between main thread
9894 and CPU workers that could result in a memory leak. Bugfix on
9895 0.1.0.1-rc. Fixes bug 889.
9896 - Send a valid END cell back when a client tries to connect to a
9897 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
9898 840. Patch from rovv.
9899 - Check which hops rendezvous stream cells are associated with to
9900 prevent possible guess-the-streamid injection attacks from
9901 intermediate hops. Fixes another case of bug 446. Based on patch
9903 - If a broken client asks a non-exit router to connect somewhere,
9904 do not even do the DNS lookup before rejecting the connection.
9905 Fixes another case of bug 619. Patch from rovv.
9906 - When a relay gets a create cell it can't decrypt (e.g. because it's
9907 using the wrong onion key), we were dropping it and letting the
9908 client time out. Now actually answer with a destroy cell. Fixes
9909 bug 904. Bugfix on 0.0.2pre8.
9911 o Minor bugfixes (hidden services):
9912 - Do not throw away existing introduction points on SIGHUP. Bugfix on
9913 0.0.6pre1. Patch by Karsten. Fixes bug 874.
9916 - Report the case where all signatures in a detached set are rejected
9917 differently than the case where there is an error handling the
9919 - When we realize that another process has modified our cached
9920 descriptors, print out a more useful error message rather than
9921 triggering an assertion. Fixes bug 885. Patch from Karsten.
9922 - Implement the 0x20 hack to better resist DNS poisoning: set the
9923 case on outgoing DNS requests randomly, and reject responses that do
9924 not match the case correctly. This logic can be disabled with the
9925 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
9926 of servers that do not reliably preserve case in replies. See
9927 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
9929 - Check DNS replies for more matching fields to better resist DNS
9931 - Never use OpenSSL compression: it wastes RAM and CPU trying to
9932 compress cells, which are basically all encrypted, compressed, or
9936 Changes in version 0.2.0.32 - 2008-11-20
9937 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
9938 packages (and maybe other packages) noticed by Theo de Raadt, fixes
9939 a smaller security flaw that might allow an attacker to access local
9940 services, further improves hidden service performance, and fixes a
9941 variety of other issues.
9944 - The "User" and "Group" config options did not clear the
9945 supplementary group entries for the Tor process. The "User" option
9946 is now more robust, and we now set the groups to the specified
9947 user's primary group. The "Group" option is now ignored. For more
9948 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
9949 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
9950 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
9951 - The "ClientDNSRejectInternalAddresses" config option wasn't being
9952 consistently obeyed: if an exit relay refuses a stream because its
9953 exit policy doesn't allow it, we would remember what IP address
9954 the relay said the destination address resolves to, even if it's
9955 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
9958 - Fix a DOS opportunity during the voting signature collection process
9959 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
9961 o Major bugfixes (hidden services):
9962 - When fetching v0 and v2 rendezvous service descriptors in parallel,
9963 we were failing the whole hidden service request when the v0
9964 descriptor fetch fails, even if the v2 fetch is still pending and
9965 might succeed. Similarly, if the last v2 fetch fails, we were
9966 failing the whole hidden service request even if a v0 fetch is
9967 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
9968 - When extending a circuit to a hidden service directory to upload a
9969 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
9970 requests failed, because the router descriptor has not been
9971 downloaded yet. In these cases, do not attempt to upload the
9972 rendezvous descriptor, but wait until the router descriptor is
9973 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
9974 descriptor from a hidden service directory for which the router
9975 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
9979 - Fix several infrequent memory leaks spotted by Coverity.
9980 - When testing for libevent functions, set the LDFLAGS variable
9981 correctly. Found by Riastradh.
9982 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
9983 bootstrapping with tunneled directory connections. Bugfix on
9984 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
9985 - When asked to connect to A.B.exit:80, if we don't know the IP for A
9986 and we know that server B rejects most-but-not all connections to
9987 port 80, we would previously reject the connection. Now, we assume
9988 the user knows what they were asking for. Fixes bug 752. Bugfix
9989 on 0.0.9rc5. Diagnosed by BarkerJr.
9990 - If we overrun our per-second write limits a little, count this as
9991 having used up our write allocation for the second, and choke
9992 outgoing directory writes. Previously, we had only counted this when
9993 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
9994 Bugfix on 0.2.0.x (??).
9995 - Remove the old v2 directory authority 'lefkada' from the default
9996 list. It has been gone for many months.
9997 - Stop doing unaligned memory access that generated bus errors on
9998 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
9999 - Make USR2 log-level switch take effect immediately. Bugfix on
10002 o Minor bugfixes (controller):
10003 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
10004 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
10007 Changes in version 0.2.0.31 - 2008-09-03
10008 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
10009 a big bug we're seeing where in rare cases traffic from one Tor stream
10010 gets mixed into another stream, and fixes a variety of smaller issues.
10013 - Make sure that two circuits can never exist on the same connection
10014 with the same circuit ID, even if one is marked for close. This
10015 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
10016 - Relays now reject risky extend cells: if the extend cell includes
10017 a digest of all zeroes, or asks to extend back to the relay that
10018 sent the extend cell, tear down the circuit. Ideas suggested
10020 - If not enough of our entry guards are available so we add a new
10021 one, we might use the new one even if it overlapped with the
10022 current circuit's exit relay (or its family). Anonymity bugfix
10023 pointed out by rovv.
10026 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
10027 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
10028 - Correctly detect the presence of the linux/netfilter_ipv4.h header
10029 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
10030 - Pick size of default geoip filename string correctly on windows.
10031 Fixes bug 806. Bugfix on 0.2.0.30.
10032 - Make the autoconf script accept the obsolete --with-ssl-dir
10033 option as an alias for the actually-working --with-openssl-dir
10034 option. Fix the help documentation to recommend --with-openssl-dir.
10035 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
10036 - When using the TransPort option on OpenBSD, and using the User
10037 option to change UID and drop privileges, make sure to open
10038 /dev/pf before dropping privileges. Fixes bug 782. Patch from
10039 Christopher Davis. Bugfix on 0.1.2.1-alpha.
10040 - Try to attach connections immediately upon receiving a RENDEZVOUS2
10041 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
10042 on the client side when connecting to a hidden service. Bugfix
10043 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
10044 - When closing an application-side connection because its circuit is
10045 getting torn down, generate the stream event correctly. Bugfix on
10046 0.1.2.x. Anonymous patch.
10049 Changes in version 0.2.0.30 - 2008-07-15
10050 This new stable release switches to a more efficient directory
10051 distribution design, adds features to make connections to the Tor
10052 network harder to block, allows Tor to act as a DNS proxy, adds separate
10053 rate limiting for relayed traffic to make it easier for clients to
10054 become relays, fixes a variety of potential anonymity problems, and
10055 includes the usual huge pile of other features and bug fixes.
10057 o New v3 directory design:
10058 - Tor now uses a new way to learn about and distribute information
10059 about the network: the directory authorities vote on a common
10060 network status document rather than each publishing their own
10061 opinion. Now clients and caches download only one networkstatus
10062 document to bootstrap, rather than downloading one for each
10063 authority. Clients only download router descriptors listed in
10064 the consensus. Implements proposal 101; see doc/spec/dir-spec.txt
10066 - Set up moria1, tor26, and dizum as v3 directory authorities
10067 in addition to being v2 authorities. Also add three new ones:
10068 ides (run by Mike Perry), gabelmoo (run by Karsten Loesing), and
10069 dannenberg (run by CCC).
10070 - Switch to multi-level keys for directory authorities: now their
10071 long-term identity key can be kept offline, and they periodically
10072 generate a new signing key. Clients fetch the "key certificates"
10073 to keep up to date on the right keys. Add a standalone tool
10074 "tor-gencert" to generate key certificates. Implements proposal 103.
10075 - Add a new V3AuthUseLegacyKey config option to make it easier for
10076 v3 authorities to change their identity keys if another bug like
10077 Debian's OpenSSL RNG flaw appears.
10078 - Authorities and caches fetch the v2 networkstatus documents
10079 less often, now that v3 is recommended.
10081 o Make Tor connections stand out less on the wire:
10082 - Use an improved TLS handshake designed by Steven Murdoch in proposal
10083 124, as revised in proposal 130. The new handshake is meant to
10084 be harder for censors to fingerprint, and it adds the ability
10085 to detect certain kinds of man-in-the-middle traffic analysis
10086 attacks. The new handshake format includes version negotiation for
10087 OR connections as described in proposal 105, which will allow us
10088 to improve Tor's link protocol more safely in the future.
10089 - Enable encrypted directory connections by default for non-relays,
10090 so censor tools that block Tor directory connections based on their
10091 plaintext patterns will no longer work. This means Tor works in
10092 certain censored countries by default again.
10093 - Stop including recognizeable strings in the commonname part of
10094 Tor's x509 certificates.
10096 o Implement bridge relays:
10097 - Bridge relays (or "bridges" for short) are Tor relays that aren't
10098 listed in the main Tor directory. Since there is no complete public
10099 list of them, even an ISP that is filtering connections to all the
10100 known Tor relays probably won't be able to block all the bridges.
10101 See doc/design-paper/blocking.pdf and proposal 125 for details.
10102 - New config option BridgeRelay that specifies you want to be a
10103 bridge relay rather than a normal relay. When BridgeRelay is set
10104 to 1, then a) you cache dir info even if your DirPort ins't on,
10105 and b) the default for PublishServerDescriptor is now "bridge"
10106 rather than "v2,v3".
10107 - New config option "UseBridges 1" for clients that want to use bridge
10108 relays instead of ordinary entry guards. Clients then specify
10109 bridge relays by adding "Bridge" lines to their config file. Users
10110 can learn about a bridge relay either manually through word of
10111 mouth, or by one of our rate-limited mechanisms for giving out
10112 bridge addresses without letting an attacker easily enumerate them
10113 all. See https://www.torproject.org/bridges for details.
10114 - Bridge relays behave like clients with respect to time intervals
10115 for downloading new v3 consensus documents -- otherwise they
10116 stand out. Bridge users now wait until the end of the interval,
10117 so their bridge relay will be sure to have a new consensus document.
10119 o Implement bridge directory authorities:
10120 - Bridge authorities are like normal directory authorities, except
10121 they don't serve a list of known bridges. Therefore users that know
10122 a bridge's fingerprint can fetch a relay descriptor for that bridge,
10123 including fetching updates e.g. if the bridge changes IP address,
10124 yet an attacker can't just fetch a list of all the bridges.
10125 - Set up Tonga as the default bridge directory authority.
10126 - Bridge authorities refuse to serve bridge descriptors or other
10127 bridge information over unencrypted connections (that is, when
10128 responding to direct DirPort requests rather than begin_dir cells.)
10129 - Bridge directory authorities do reachability testing on the
10130 bridges they know. They provide router status summaries to the
10131 controller via "getinfo ns/purpose/bridge", and also dump summaries
10132 to a file periodically, so we can keep internal stats about which
10133 bridges are functioning.
10134 - If bridge users set the UpdateBridgesFromAuthority config option,
10135 but the digest they ask for is a 404 on the bridge authority,
10136 they fall back to contacting the bridge directly.
10137 - Bridges always use begin_dir to publish their server descriptor to
10138 the bridge authority using an anonymous encrypted tunnel.
10139 - Early work on a "bridge community" design: if bridge authorities set
10140 the BridgePassword config option, they will serve a snapshot of
10141 known bridge routerstatuses from their DirPort to anybody who
10142 knows that password. Unset by default.
10143 - Tor now includes an IP-to-country GeoIP file, so bridge relays can
10144 report sanitized aggregated summaries in their extra-info documents
10145 privately to the bridge authority, listing which countries are
10146 able to reach them. We hope this mechanism will let us learn when
10147 certain countries start trying to block bridges.
10148 - Bridge authorities write bridge descriptors to disk, so they can
10149 reload them after a reboot. They can also export the descriptors
10150 to other programs, so we can distribute them to blocked users via
10151 the BridgeDB interface, e.g. via https://bridges.torproject.org/
10152 and bridges@torproject.org.
10154 o Tor can be a DNS proxy:
10155 - The new client-side DNS proxy feature replaces the need for
10156 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
10157 for DNS requests on port 9999, use the Tor network to resolve them
10158 anonymously, and send the reply back like a regular DNS server.
10159 The code still only implements a subset of DNS.
10160 - Add a new AutomapHostsOnResolve option: when it is enabled, any
10161 resolve request for hosts matching a given pattern causes Tor to
10162 generate an internal virtual address mapping for that host. This
10163 allows DNSPort to work sensibly with hidden service users. By
10164 default, .exit and .onion addresses are remapped; the list of
10165 patterns can be reconfigured with AutomapHostsSuffixes.
10166 - Add an "-F" option to tor-resolve to force a resolve for a .onion
10167 address. Thanks to the AutomapHostsOnResolve option, this is no
10168 longer a completely silly thing to do.
10170 o Major features (relay usability):
10171 - New config options RelayBandwidthRate and RelayBandwidthBurst:
10172 a separate set of token buckets for relayed traffic. Right now
10173 relayed traffic is defined as answers to directory requests, and
10174 OR connections that don't have any local circuits on them. See
10175 proposal 111 for details.
10176 - Create listener connections before we setuid to the configured
10177 User and Group. Now non-Windows users can choose port values
10178 under 1024, start Tor as root, and have Tor bind those ports
10179 before it changes to another UID. (Windows users could already
10181 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
10182 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
10183 on "vserver" accounts. Patch from coderman.
10185 o Major features (directory authorities):
10186 - Directory authorities track weighted fractional uptime and weighted
10187 mean-time-between failures for relays. WFU is suitable for deciding
10188 whether a node is "usually up", while MTBF is suitable for deciding
10189 whether a node is "likely to stay up." We need both, because
10190 "usually up" is a good requirement for guards, while "likely to
10191 stay up" is a good requirement for long-lived connections.
10192 - Directory authorities use a new formula for selecting which relays
10193 to advertise as Guards: they must be in the top 7/8 in terms of
10194 how long we have known about them, and above the median of those
10195 nodes in terms of weighted fractional uptime.
10196 - Directory authorities use a new formula for selecting which relays
10197 to advertise as Stable: when we have 4 or more days of data, use
10198 median measured MTBF rather than median declared uptime. Implements
10200 - Directory authorities accept and serve "extra info" documents for
10201 routers. Routers now publish their bandwidth-history lines in the
10202 extra-info docs rather than the main descriptor. This step saves
10203 60% (!) on compressed router descriptor downloads. Servers upload
10204 extra-info docs to any authority that accepts them; directory
10205 authorities now allow multiple router descriptors and/or extra
10206 info documents to be uploaded in a single go. Authorities, and
10207 caches that have been configured to download extra-info documents,
10208 download them as needed. Implements proposal 104.
10209 - Authorities now list relays who have the same nickname as
10210 a different named relay, but list them with a new flag:
10211 "Unnamed". Now we can make use of relays that happen to pick the
10212 same nickname as a server that registered two years ago and then
10213 disappeared. Implements proposal 122.
10214 - Store routers in a file called cached-descriptors instead of in
10215 cached-routers. Initialize cached-descriptors from cached-routers
10216 if the old format is around. The new format allows us to store
10217 annotations along with descriptors, to record the time we received
10218 each descriptor, its source, and its purpose: currently one of
10219 general, controller, or bridge.
10221 o Major features (other):
10222 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
10223 Tor can warn and/or refuse connections to ports commonly used with
10224 vulnerable-plaintext protocols. Currently we warn on ports 23,
10225 109, 110, and 143, but we don't reject any. Based on proposal 129
10226 by Kevin Bauer and Damon McCoy.
10227 - Integrate Karsten Loesing's Google Summer of Code project to publish
10228 hidden service descriptors on a set of redundant relays that are a
10229 function of the hidden service address. Now we don't have to rely
10230 on three central hidden service authorities for publishing and
10231 fetching every hidden service descriptor. Implements proposal 114.
10232 - Allow tunnelled directory connections to ask for an encrypted
10233 "begin_dir" connection or an anonymized "uses a full Tor circuit"
10234 connection independently. Now we can make anonymized begin_dir
10235 connections for (e.g.) more secure hidden service posting and
10238 o Major bugfixes (crashes and assert failures):
10239 - Stop imposing an arbitrary maximum on the number of file descriptors
10240 used for busy servers. Bug reported by Olaf Selke; patch from
10242 - Avoid possible failures when generating a directory with routers
10243 with over-long versions strings, or too many flags set.
10244 - Fix a rare assert error when we're closing one of our threads:
10245 use a mutex to protect the list of logs, so we never write to the
10246 list as it's being freed. Fixes the very rare bug 575, which is
10247 kind of the revenge of bug 222.
10248 - Avoid segfault in the case where a badly behaved v2 versioning
10249 directory sends a signed networkstatus with missing client-versions.
10250 - When we hit an EOF on a log (probably because we're shutting down),
10251 don't try to remove the log from the list: just mark it as
10252 unusable. (Bulletproofs against bug 222.)
10254 o Major bugfixes (code security fixes):
10255 - Detect size overflow in zlib code. Reported by Justin Ferguson and
10257 - Rewrite directory tokenization code to never run off the end of
10258 a string. Fixes bug 455. Patch from croup.
10259 - Be more paranoid about overwriting sensitive memory on free(),
10260 as a defensive programming tactic to ensure forward secrecy.
10262 o Major bugfixes (anonymity fixes):
10263 - Reject requests for reverse-dns lookup of names that are in
10264 a private address space. Patch from lodger.
10265 - Never report that we've used more bandwidth than we're willing to
10266 relay: it leaks how much non-relay traffic we're using. Resolves
10268 - As a client, do not believe any server that tells us that an
10269 address maps to an internal address space.
10270 - Warn about unsafe ControlPort configurations.
10271 - Directory authorities now call routers Fast if their bandwidth is
10272 at least 100KB/s, and consider their bandwidth adequate to be a
10273 Guard if it is at least 250KB/s, no matter the medians. This fix
10274 complements proposal 107.
10275 - Directory authorities now never mark more than 2 servers per IP as
10276 Valid and Running (or 5 on addresses shared by authorities).
10277 Implements proposal 109, by Kevin Bauer and Damon McCoy.
10278 - If we're a relay, avoid picking ourselves as an introduction point,
10279 a rendezvous point, or as the final hop for internal circuits. Bug
10280 reported by taranis and lodger.
10281 - Exit relays that are used as a client can now reach themselves
10282 using the .exit notation, rather than just launching an infinite
10283 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
10284 - Fix a bug where, when we were choosing the 'end stream reason' to
10285 put in our relay end cell that we send to the exit relay, Tor
10286 clients on Windows were sometimes sending the wrong 'reason'. The
10287 anonymity problem is that exit relays may be able to guess whether
10288 the client is running Windows, thus helping partition the anonymity
10289 set. Down the road we should stop sending reasons to exit relays,
10290 or otherwise prevent future versions of this bug.
10291 - Only update guard status (usable / not usable) once we have
10292 enough directory information. This was causing us to discard all our
10293 guards on startup if we hadn't been running for a few weeks. Fixes
10295 - When our directory information has been expired for a while, stop
10296 being willing to build circuits using it. Fixes bug 401.
10298 o Major bugfixes (peace of mind for relay operators)
10299 - Non-exit relays no longer answer "resolve" relay cells, so they
10300 can't be induced to do arbitrary DNS requests. (Tor clients already
10301 avoid using non-exit relays for resolve cells, but now servers
10302 enforce this too.) Fixes bug 619. Patch from lodger.
10303 - When we setconf ClientOnly to 1, close any current OR and Dir
10304 listeners. Reported by mwenge.
10306 o Major bugfixes (other):
10307 - If we only ever used Tor for hidden service lookups or posts, we
10308 would stop building circuits and start refusing connections after
10309 24 hours, since we falsely believed that Tor was dormant. Reported
10311 - Add a new __HashedControlSessionPassword option for controllers
10312 to use for one-off session password hashes that shouldn't get
10313 saved to disk by SAVECONF --- Vidalia users were accumulating a
10314 pile of HashedControlPassword lines in their torrc files, one for
10315 each time they had restarted Tor and then clicked Save. Make Tor
10316 automatically convert "HashedControlPassword" to this new option but
10317 only when it's given on the command line. Partial fix for bug 586.
10318 - Patch from "Andrew S. Lists" to catch when we contact a directory
10319 mirror at IP address X and he says we look like we're coming from
10320 IP address X. Otherwise this would screw up our address detection.
10321 - Reject uploaded descriptors and extrainfo documents if they're
10322 huge. Otherwise we'll cache them all over the network and it'll
10323 clog everything up. Suggested by Aljosha Judmayer.
10324 - When a hidden service was trying to establish an introduction point,
10325 and Tor *did* manage to reuse one of the preemptively built
10326 circuits, it didn't correctly remember which one it used,
10327 so it asked for another one soon after, until there were no
10328 more preemptive circuits, at which point it launched one from
10329 scratch. Bugfix on 0.0.9.x.
10331 o Rate limiting and load balancing improvements:
10332 - When we add data to a write buffer in response to the data on that
10333 write buffer getting low because of a flush, do not consider the
10334 newly added data as a candidate for immediate flushing, but rather
10335 make it wait until the next round of writing. Otherwise, we flush
10336 and refill recursively, and a single greedy TLS connection can
10337 eat all of our bandwidth.
10338 - When counting the number of bytes written on a TLS connection,
10339 look at the BIO actually used for writing to the network, not
10340 at the BIO used (sometimes) to buffer data for the network.
10341 Looking at different BIOs could result in write counts on the
10342 order of ULONG_MAX. Fixes bug 614.
10343 - If we change our MaxAdvertisedBandwidth and then reload torrc,
10344 Tor won't realize it should publish a new relay descriptor. Fixes
10345 bug 688, reported by mfr.
10346 - Avoid using too little bandwidth when our clock skips a few seconds.
10347 - Choose which bridge to use proportional to its advertised bandwidth,
10348 rather than uniformly at random. This should speed up Tor for
10349 bridge users. Also do this for people who set StrictEntryNodes.
10351 o Bootstrapping faster and building circuits more intelligently:
10352 - Fix bug 660 that was preventing us from knowing that we should
10353 preemptively build circuits to handle expected directory requests.
10354 - When we're checking if we have enough dir info for each relay
10355 to begin establishing circuits, make sure that we actually have
10356 the descriptor listed in the consensus, not just any descriptor.
10357 - Correctly notify one-hop connections when a circuit build has
10358 failed. Possible fix for bug 669. Found by lodger.
10359 - Clients now hold circuitless TLS connections open for 1.5 times
10360 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
10361 rebuild a new circuit over them within that timeframe. Previously,
10362 they held them open only for KeepalivePeriod (5 minutes).
10364 o Performance improvements (memory):
10365 - Add OpenBSD malloc code from "phk" as an optional malloc
10366 replacement on Linux: some glibc libraries do very poorly with
10367 Tor's memory allocation patterns. Pass --enable-openbsd-malloc to
10368 ./configure to get the replacement malloc code.
10369 - Switch our old ring buffer implementation for one more like that
10370 used by free Unix kernels. The wasted space in a buffer with 1mb
10371 of data will now be more like 8k than 1mb. The new implementation
10372 also avoids realloc();realloc(); patterns that can contribute to
10373 memory fragmentation.
10374 - Change the way that Tor buffers data that it is waiting to write.
10375 Instead of queueing data cells in an enormous ring buffer for each
10376 client->OR or OR->OR connection, we now queue cells on a separate
10377 queue for each circuit. This lets us use less slack memory, and
10378 will eventually let us be smarter about prioritizing different kinds
10380 - Reference-count and share copies of address policy entries; only 5%
10381 of them were actually distinct.
10382 - Tune parameters for cell pool allocation to minimize amount of
10384 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
10385 for every single inactive connection_t. Free items from the
10386 4k/16k-buffer free lists when they haven't been used for a while.
10387 - Make memory debugging information describe more about history
10388 of cell allocation, so we can help reduce our memory use.
10389 - Be even more aggressive about releasing RAM from small
10390 empty buffers. Thanks to our free-list code, this shouldn't be too
10391 performance-intensive.
10392 - Log malloc statistics from mallinfo() on platforms where it exists.
10393 - Use memory pools to allocate cells with better speed and memory
10394 efficiency, especially on platforms where malloc() is inefficient.
10395 - Add a --with-tcmalloc option to the configure script to link
10396 against tcmalloc (if present). Does not yet search for non-system
10399 o Performance improvements (socket management):
10400 - Count the number of open sockets separately from the number of
10401 active connection_t objects. This will let us avoid underusing
10402 our allocated connection limit.
10403 - We no longer use socket pairs to link an edge connection to an
10404 anonymous directory connection or a DirPort test connection.
10405 Instead, we track the link internally and transfer the data
10406 in-process. This saves two sockets per "linked" connection (at the
10407 client and at the server), and avoids the nasty Windows socketpair()
10409 - We were leaking a file descriptor if Tor started with a zero-length
10410 cached-descriptors file. Patch by "freddy77".
10412 o Performance improvements (CPU use):
10413 - Never walk through the list of logs if we know that no log target
10414 is interested in a given message.
10415 - Call routerlist_remove_old_routers() much less often. This should
10416 speed startup, especially on directory caches.
10417 - Base64 decoding was actually showing up on our profile when parsing
10418 the initial descriptor file; switch to an in-process all-at-once
10419 implementation that's about 3.5x times faster than calling out to
10421 - Use a slightly simpler string hashing algorithm (copying Python's
10422 instead of Java's) and optimize our digest hashing algorithm to take
10423 advantage of 64-bit platforms and to remove some possibly-costly
10425 - When implementing AES counter mode, update only the portions of the
10426 counter buffer that need to change, and don't keep separate
10427 network-order and host-order counters on big-endian hosts (where
10428 they are the same).
10429 - Add an in-place version of aes_crypt() so that we can avoid doing a
10430 needless memcpy() call on each cell payload.
10431 - Use Critical Sections rather than Mutexes for synchronizing threads
10432 on win32; Mutexes are heavier-weight, and designed for synchronizing
10435 o Performance improvements (bandwidth use):
10436 - Don't try to launch new descriptor downloads quite so often when we
10437 already have enough directory information to build circuits.
10438 - Version 1 directories are no longer generated in full. Instead,
10439 authorities generate and serve "stub" v1 directories that list
10440 no servers. This will stop Tor versions 0.1.0.x and earlier from
10441 working, but (for security reasons) nobody should be running those
10443 - Avoid going directly to the directory authorities even if you're a
10444 relay, if you haven't found yourself reachable yet or if you've
10445 decided not to advertise your dirport yet. Addresses bug 556.
10446 - If we've gone 12 hours since our last bandwidth check, and we
10447 estimate we have less than 50KB bandwidth capacity but we could
10448 handle more, do another bandwidth test.
10449 - Support "If-Modified-Since" when answering HTTP requests for
10450 directories, running-routers documents, and v2 and v3 networkstatus
10451 documents. (There's no need to support it for router descriptors,
10452 since those are downloaded by descriptor digest.)
10453 - Stop fetching directory info so aggressively if your DirPort is
10454 on but your ORPort is off; stop fetching v2 dir info entirely.
10455 You can override these choices with the new FetchDirInfoEarly
10458 o Changed config option behavior (features):
10459 - Configuration files now accept C-style strings as values. This
10460 helps encode characters not allowed in the current configuration
10461 file format, such as newline or #. Addresses bug 557.
10462 - Add hidden services and DNSPorts to the list of things that make
10463 Tor accept that it has running ports. Change starting Tor with no
10464 ports from a fatal error to a warning; we might change it back if
10465 this turns out to confuse anybody. Fixes bug 579.
10466 - Make PublishServerDescriptor default to 1, so the default doesn't
10467 have to change as we invent new directory protocol versions.
10468 - Allow people to say PreferTunnelledDirConns rather than
10469 PreferTunneledDirConns, for those alternate-spellers out there.
10470 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
10471 accommodate the growing number of servers that use the default
10472 and are reaching it.
10473 - Make it possible to enable HashedControlPassword and
10474 CookieAuthentication at the same time.
10475 - When a TrackHostExits-chosen exit fails too many times in a row,
10476 stop using it. Fixes bug 437.
10478 o Changed config option behavior (bugfixes):
10479 - Do not read the configuration file when we've only been told to
10480 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
10481 based on patch from Sebastian Hahn.
10482 - Actually validate the options passed to AuthDirReject,
10483 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
10484 - Make "ClientOnly 1" config option disable directory ports too.
10485 - Don't stop fetching descriptors when FetchUselessDescriptors is
10486 set, even if we stop asking for circuits. Bug reported by tup
10488 - Servers used to decline to publish their DirPort if their
10489 BandwidthRate or MaxAdvertisedBandwidth were below a threshold. Now
10490 they look only at BandwidthRate and RelayBandwidthRate.
10491 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
10492 minus 1 byte: the actual maximum declared bandwidth.
10493 - Make "TrackHostExits ." actually work. Bugfix on 0.1.0.x.
10494 - Make the NodeFamilies config option work. (Reported by
10495 lodger -- it has never actually worked, even though we added it
10497 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
10498 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
10500 o New config options:
10501 - New configuration options AuthDirMaxServersPerAddr and
10502 AuthDirMaxServersperAuthAddr to override default maximum number
10503 of servers allowed on a single IP address. This is important for
10504 running a test network on a single host.
10505 - Three new config options (AlternateDirAuthority,
10506 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
10507 user selectively replace the default directory authorities by type,
10508 rather than the all-or-nothing replacement that DirServer offers.
10509 - New config options AuthDirBadDir and AuthDirListBadDirs for
10510 authorities to mark certain relays as "bad directories" in the
10511 networkstatus documents. Also supports the "!baddir" directive in
10512 the approved-routers file.
10513 - New config option V2AuthoritativeDirectory that all v2 directory
10514 authorities must set. This lets v3 authorities choose not to serve
10515 v2 directory information.
10517 o Minor features (other):
10518 - When we're not serving v2 directory information, there is no reason
10519 to actually keep any around. Remove the obsolete files and directory
10520 on startup if they are very old and we aren't going to serve them.
10521 - When we negotiate a v2 link-layer connection (not yet implemented),
10522 accept RELAY_EARLY cells and turn them into RELAY cells if we've
10523 negotiated a v1 connection for their next step. Initial steps for
10525 - When we have no consensus, check FallbackNetworkstatusFile (defaults
10526 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
10527 we can start out knowing some directory caches. We don't ship with
10528 a fallback consensus by default though, because it was making
10529 bootstrapping take too long while we tried many down relays.
10530 - Authorities send back an X-Descriptor-Not-New header in response to
10531 an accepted-but-discarded descriptor upload. Partially implements
10533 - If we find a cached-routers file that's been sitting around for more
10534 than 28 days unmodified, then most likely it's a leftover from
10535 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
10537 - When we (as a cache) download a descriptor because it was listed
10538 in a consensus, remember when the consensus was supposed to expire,
10539 and don't expire the descriptor until then.
10540 - Optionally (if built with -DEXPORTMALLINFO) export the output
10541 of mallinfo via http, as tor/mallinfo.txt. Only accessible
10543 - Tag every guard node in our state file with the version that
10544 we believe added it, or with our own version if we add it. This way,
10545 if a user temporarily runs an old version of Tor and then switches
10546 back to a new one, she doesn't automatically lose her guards.
10547 - When somebody requests a list of statuses or servers, and we have
10548 none of those, return a 404 rather than an empty 200.
10549 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
10551 - Add an HSAuthorityRecordStats option that hidden service authorities
10552 can use to track statistics of overall hidden service usage without
10553 logging information that would be as useful to an attacker.
10554 - Allow multiple HiddenServicePort directives with the same virtual
10555 port; when they occur, the user is sent round-robin to one
10556 of the target ports chosen at random. Partially fixes bug 393 by
10557 adding limited ad-hoc round-robining.
10558 - Revamp file-writing logic so we don't need to have the entire
10559 contents of a file in memory at once before we write to disk. Tor,
10562 o Minor bugfixes (other):
10563 - Alter the code that tries to recover from unhandled write
10564 errors, to not try to flush onto a socket that's given us
10566 - Directory mirrors no longer include a guess at the client's IP
10567 address if the connection appears to be coming from the same /24
10568 network; it was producing too many wrong guesses.
10569 - If we're trying to flush the last bytes on a connection (for
10570 example, when answering a directory request), reset the
10571 time-to-give-up timeout every time we manage to write something
10573 - Reject router descriptors with out-of-range bandwidthcapacity or
10574 bandwidthburst values.
10575 - If we can't expand our list of entry guards (e.g. because we're
10576 using bridges or we have StrictEntryNodes set), don't mark relays
10577 down when they fail a directory request. Otherwise we're too quick
10578 to mark all our entry points down.
10579 - Authorities no longer send back "400 you're unreachable please fix
10580 it" errors to Tor servers that aren't online all the time. We're
10581 supposed to tolerate these servers now.
10582 - Let directory authorities startup even when they can't generate
10583 a descriptor immediately, e.g. because they don't know their
10585 - Correctly enforce that elements of directory objects do not appear
10586 more often than they are allowed to appear.
10587 - Stop allowing hibernating servers to be "stable" or "fast".
10588 - On Windows, we were preventing other processes from reading
10589 cached-routers while Tor was running. (Reported by janbar)
10590 - Check return values from pthread_mutex functions.
10591 - When opening /dev/null in finish_daemonize(), do not pass the
10592 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
10593 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
10595 o Controller features:
10596 - The GETCONF command now escapes and quotes configuration values
10597 that don't otherwise fit into the torrc file.
10598 - The SETCONF command now handles quoted values correctly.
10599 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
10600 ask about source, timestamp of arrival, purpose, etc. We need
10601 something like this to help Vidalia not do GeoIP lookups on bridge
10603 - Allow multiple HashedControlPassword config lines, to support
10604 multiple controller passwords.
10605 - Accept LF instead of CRLF on controller, since some software has a
10606 hard time generating real Internet newlines.
10607 - Add GETINFO values for the server status events
10608 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
10610 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
10611 GETINFO for Torstat to use until it can switch to using extrainfos.
10612 - New config option CookieAuthFile to choose a new location for the
10613 cookie authentication file, and config option
10614 CookieAuthFileGroupReadable to make it group-readable.
10615 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
10616 match requests to applications. Patch from Robert Hogan.
10617 - Add a RESOLVE command to launch hostname lookups. Original patch
10619 - Add GETINFO status/enough-dir-info to let controllers tell whether
10620 Tor has downloaded sufficient directory information. Patch from Tup.
10621 - You can now use the ControlSocket option to tell Tor to listen for
10622 controller connections on Unix domain sockets on systems that
10623 support them. Patch from Peter Palfrader.
10624 - New "GETINFO address-mappings/*" command to get address mappings
10625 with expiry information. "addr-mappings/*" is now deprecated.
10627 - Add a new config option __DisablePredictedCircuits designed for
10628 use by the controller, when we don't want Tor to build any circuits
10630 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
10631 so we can exit from the middle of the circuit.
10632 - Implement "getinfo status/circuit-established".
10633 - Implement "getinfo status/version/..." so a controller can tell
10634 whether the current version is recommended, and whether any versions
10635 are good, and how many authorities agree. Patch from "shibz".
10636 - Controllers should now specify cache=no or cache=yes when using
10637 the +POSTDESCRIPTOR command.
10638 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
10639 Robert Hogan. Fixes the first part of bug 681.
10640 - When reporting clock skew, and we know that the clock is _at least
10641 as skewed_ as some value, but we don't know the actual value,
10642 report the value as a "minimum skew."
10644 o Controller bugfixes:
10645 - Generate "STATUS_SERVER" events rather than misspelled
10646 "STATUS_SEVER" events. Caught by mwenge.
10647 - Reject controller commands over 1MB in length, so rogue
10648 processes can't run us out of memory.
10649 - Change the behavior of "getinfo status/good-server-descriptor"
10650 so it doesn't return failure when any authority disappears.
10651 - Send NAMESERVER_STATUS messages for a single failed nameserver
10653 - When the DANGEROUS_VERSION controller status event told us we're
10654 running an obsolete version, it used the string "OLD" to describe
10655 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
10656 "OBSOLETE" in both cases.
10657 - Respond to INT and TERM SIGNAL commands before we execute the
10658 signal, in case the signal shuts us down. We had a patch in
10659 0.1.2.1-alpha that tried to do this by queueing the response on
10660 the connection's buffer before shutting down, but that really
10661 isn't the same thing at all. Bug located by Matt Edman.
10662 - Provide DNS expiry times in GMT, not in local time. For backward
10663 compatibility, ADDRMAP events only provide GMT expiry in an extended
10664 field. "GETINFO address-mappings" always does the right thing.
10665 - Use CRLF line endings properly in NS events.
10666 - Make 'getinfo fingerprint' return a 551 error if we're not a
10667 server, so we match what the control spec claims we do. Reported
10669 - Fix a typo in an error message when extendcircuit fails that
10670 caused us to not follow the \r\n-based delimiter protocol. Reported
10672 - When tunneling an encrypted directory connection, and its first
10673 circuit fails, do not leave it unattached and ask the controller
10674 to deal. Fixes the second part of bug 681.
10675 - Treat some 403 responses from directory servers as INFO rather than
10676 WARN-severity events.
10678 o Portability / building / compiling:
10679 - When building with --enable-gcc-warnings, check for whether Apple's
10680 warning "-Wshorten-64-to-32" is available.
10681 - Support compilation to target iPhone; patch from cjacker huang.
10682 To build for iPhone, pass the --enable-iphone option to configure.
10683 - Port Tor to build and run correctly on Windows CE systems, using
10684 the wcecompat library. Contributed by Valerio Lupi.
10685 - Detect non-ASCII platforms (if any still exist) and refuse to
10686 build there: some of our code assumes that 'A' is 65 and so on.
10687 - Clear up some MIPSPro compiler warnings.
10688 - Make autoconf search for libevent, openssl, and zlib consistently.
10689 - Update deprecated macros in configure.in.
10690 - When warning about missing headers, tell the user to let us
10691 know if the compile succeeds anyway, so we can downgrade the
10693 - Include the current subversion revision as part of the version
10694 string: either fetch it directly if we're in an SVN checkout, do
10695 some magic to guess it if we're in an SVK checkout, or use
10696 the last-detected version if we're building from a .tar.gz.
10697 Use this version consistently in log messages.
10698 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
10699 - Read resolv.conf files correctly on platforms where read() returns
10700 partial results on small file reads.
10701 - Build without verbose warnings even on gcc 4.2 and 4.3.
10702 - On Windows, correctly detect errors when listing the contents of
10703 a directory. Fix from lodger.
10704 - Run 'make test' as part of 'make dist', so we stop releasing so
10705 many development snapshots that fail their unit tests.
10706 - Add support to detect Libevent versions in the 1.4.x series
10708 - Add command-line arguments to unit-test executable so that we can
10709 invoke any chosen test from the command line rather than having
10710 to run the whole test suite at once; and so that we can turn on
10711 logging for the unit tests.
10712 - Do not automatically run configure from autogen.sh. This
10713 non-standard behavior tended to annoy people who have built other
10715 - Fix a macro/CPP interaction that was confusing some compilers:
10716 some GCCs don't like #if/#endif pairs inside macro arguments.
10718 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
10719 Fixes bug 704; fix from Steven Murdoch.
10720 - Correctly detect transparent proxy support on Linux hosts that
10721 require in.h to be included before netfilter_ipv4.h. Patch
10724 o Logging improvements:
10725 - When we haven't had any application requests lately, don't bother
10726 logging that we have expired a bunch of descriptors.
10727 - When attempting to open a logfile fails, tell us why.
10728 - Only log guard node status when guard node status has changed.
10729 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
10730 make "INFO" 75% less verbose.
10731 - When SafeLogging is disabled, log addresses along with all TLS
10733 - Report TLS "zero return" case as a "clean close" and "IO error"
10734 as a "close". Stop calling closes "unexpected closes": existing
10735 Tors don't use SSL_close(), so having a connection close without
10736 the TLS shutdown handshake is hardly unexpected.
10737 - When we receive a consensus from the future, warn about skew.
10738 - Make "not enough dir info yet" warnings describe *why* Tor feels
10739 it doesn't have enough directory info yet.
10740 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
10741 consumers. (We already do this on HUP.)
10742 - Give more descriptive well-formedness errors for out-of-range
10743 hidden service descriptor/protocol versions.
10744 - Stop recommending that every server operator send mail to tor-ops.
10745 Resolves bug 597. Bugfix on 0.1.2.x.
10746 - Improve skew reporting: try to give the user a better log message
10747 about how skewed they are, and how much this matters.
10748 - New --quiet command-line option to suppress the default console log.
10749 Good in combination with --hash-password.
10750 - Don't complain that "your server has not managed to confirm that its
10751 ports are reachable" if we haven't been able to build any circuits
10753 - Detect the reason for failing to mmap a descriptor file we just
10754 wrote, and give a more useful log message. Fixes bug 533.
10755 - Always prepend "Bug: " to any log message about a bug.
10756 - When dumping memory usage, list bytes used in buffer memory
10758 - When running with dmalloc, dump more stats on hup and on exit.
10759 - Put a platform string (e.g. "Linux i686") in the startup log
10760 message, so when people paste just their logs, we know if it's
10761 OpenBSD or Windows or what.
10762 - When logging memory usage, break down memory used in buffers by
10764 - When we are reporting the DirServer line we just parsed, we were
10765 logging the second stanza of the key fingerprint, not the first.
10766 - Even though Windows is equally happy with / and \ as path separators,
10767 try to use \ consistently on Windows and / consistently on Unix: it
10768 makes the log messages nicer.
10769 - On OSX, stop warning the user that kqueue support in libevent is
10770 "experimental", since it seems to have worked fine for ages.
10772 o Contributed scripts and tools:
10773 - Update linux-tor-prio.sh script to allow QoS based on the uid of
10774 the Tor process. Patch from Marco Bonetti with tweaks from Mike
10776 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
10777 Unix users an easy way to script their Tor process (e.g. by
10778 adjusting bandwidth based on the time of the day).
10779 - In the exitlist script, only consider the most recently published
10780 server descriptor for each server. Also, when the user requests
10781 a list of servers that _reject_ connections to a given address,
10782 explicitly exclude the IPs that also have servers that accept
10783 connections to that address. Resolves bug 405.
10784 - Include a new contrib/tor-exit-notice.html file that exit relay
10785 operators can put on their website to help reduce abuse queries.
10787 o Newly deprecated features:
10788 - The status/version/num-versioning and status/version/num-concurring
10789 GETINFO controller options are no longer useful in the v3 directory
10790 protocol: treat them as deprecated, and warn when they're used.
10791 - The RedirectExits config option is now deprecated.
10793 o Removed features:
10794 - Drop the old code to choke directory connections when the
10795 corresponding OR connections got full: thanks to the cell queue
10796 feature, OR conns don't get full any more.
10797 - Remove the old "dns worker" server DNS code: it hasn't been default
10798 since 0.1.2.2-alpha, and all the servers are using the new
10800 - Remove the code to generate the oldest (v1) directory format.
10801 - Remove support for the old bw_accounting file: we've been storing
10802 bandwidth accounting information in the state file since
10803 0.1.2.5-alpha. This may result in bandwidth accounting errors
10804 if you try to upgrade from 0.1.1.x or earlier, or if you try to
10805 downgrade to 0.1.1.x or earlier.
10806 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
10807 it, it had no AES, and it hasn't seen any security patches since
10809 - Stop overloading the circuit_t.onionskin field for both "onionskin
10810 from a CREATE cell that we are waiting for a cpuworker to be
10811 assigned" and "onionskin from an EXTEND cell that we are going to
10812 send to an OR as soon as we are connected". Might help with bug 600.
10813 - Remove the tor_strpartition() function: its logic was confused,
10814 and it was only used for one thing that could be implemented far
10816 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
10817 and TorControl.py, as they use the old v0 controller protocol,
10818 and are obsoleted by TorFlow anyway.
10819 - Drop support for v1 rendezvous descriptors, since we never used
10820 them anyway, and the code has probably rotted by now. Based on
10821 patch from Karsten Loesing.
10822 - Stop allowing address masks that do not correspond to bit prefixes.
10823 We have warned about these for a really long time; now it's time
10824 to reject them. (Patch from croup.)
10825 - Remove an optimization in the AES counter-mode code that assumed
10826 that the counter never exceeded 2^68. When the counter can be set
10827 arbitrarily as an IV (as it is by Karsten's new hidden services
10828 code), this assumption no longer holds.
10829 - Disable the SETROUTERPURPOSE controller command: it is now
10833 Changes in version 0.1.2.19 - 2008-01-17
10834 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
10835 exit policy a little bit more conservative so it's safer to run an
10836 exit relay on a home system, and fixes a variety of smaller issues.
10839 - Exit policies now reject connections that are addressed to a
10840 relay's public (external) IP address too, unless
10841 ExitPolicyRejectPrivate is turned off. We do this because too
10842 many relays are running nearby to services that trust them based
10843 on network address.
10846 - When the clock jumps forward a lot, do not allow the bandwidth
10847 buckets to become negative. Fixes bug 544.
10848 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
10849 on every successful resolve. Reported by Mike Perry.
10850 - Purge old entries from the "rephist" database and the hidden
10851 service descriptor database even when DirPort is zero.
10852 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
10853 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
10854 crashing or mis-answering these requests.
10855 - When we decide to send a 503 response to a request for servers, do
10856 not then also send the server descriptors: this defeats the whole
10857 purpose. Fixes bug 539.
10860 - Changing the ExitPolicyRejectPrivate setting should cause us to
10861 rebuild our server descriptor.
10862 - Fix handling of hex nicknames when answering controller requests for
10863 networkstatus by name, or when deciding whether to warn about
10864 unknown routers in a config option. (Patch from mwenge.)
10865 - Fix a couple of hard-to-trigger autoconf problems that could result
10866 in really weird results on platforms whose sys/types.h files define
10867 nonstandard integer types.
10868 - Don't try to create the datadir when running --verify-config or
10869 --hash-password. Resolves bug 540.
10870 - If we were having problems getting a particular descriptor from the
10871 directory caches, and then we learned about a new descriptor for
10872 that router, we weren't resetting our failure count. Reported
10874 - Although we fixed bug 539 (where servers would send HTTP status 503
10875 responses _and_ send a body too), there are still servers out there
10876 that haven't upgraded. Therefore, make clients parse such bodies
10877 when they receive them.
10878 - Run correctly on systems where rlim_t is larger than unsigned long.
10879 This includes some 64-bit systems.
10880 - Run correctly on platforms (like some versions of OS X 10.5) where
10881 the real limit for number of open files is OPEN_FILES, not rlim_max
10882 from getrlimit(RLIMIT_NOFILES).
10883 - Avoid a spurious free on base64 failure.
10884 - Avoid segfaults on certain complex invocations of
10885 router_get_by_hexdigest().
10886 - Fix rare bug on REDIRECTSTREAM control command when called with no
10887 port set: it could erroneously report an error when none had
10891 Changes in version 0.1.2.18 - 2007-10-28
10892 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
10893 hidden service introduction that were causing huge delays, and a big
10894 bug that was causing some servers to disappear from the network status
10895 lists for a few hours each day.
10897 o Major bugfixes (crashes):
10898 - If a connection is shut down abruptly because of something that
10899 happened inside connection_flushed_some(), do not call
10900 connection_finished_flushing(). Should fix bug 451:
10901 "connection_stop_writing: Assertion conn->write_event failed"
10902 Bugfix on 0.1.2.7-alpha.
10903 - Fix possible segfaults in functions called from
10904 rend_process_relay_cell().
10906 o Major bugfixes (hidden services):
10907 - Hidden services were choosing introduction points uniquely by
10908 hexdigest, but when constructing the hidden service descriptor
10909 they merely wrote the (potentially ambiguous) nickname.
10910 - Clients now use the v2 intro format for hidden service
10911 connections: they specify their chosen rendezvous point by identity
10912 digest rather than by (potentially ambiguous) nickname. These
10913 changes could speed up hidden service connections dramatically.
10915 o Major bugfixes (other):
10916 - Stop publishing a new server descriptor just because we get a
10917 HUP signal. This led (in a roundabout way) to some servers getting
10918 dropped from the networkstatus lists for a few hours each day.
10919 - When looking for a circuit to cannibalize, consider family as well
10920 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
10921 circuit cannibalization).
10922 - When a router wasn't listed in a new networkstatus, we were leaving
10923 the flags for that router alone -- meaning it remained Named,
10924 Running, etc -- even though absence from the networkstatus means
10925 that it shouldn't be considered to exist at all anymore. Now we
10926 clear all the flags for routers that fall out of the networkstatus
10927 consensus. Fixes bug 529.
10930 - Don't try to access (or alter) the state file when running
10931 --list-fingerprint or --verify-config or --hash-password. Resolves
10933 - When generating information telling us how to extend to a given
10934 router, do not try to include the nickname if it is
10935 absent. Resolves bug 467.
10936 - Fix a user-triggerable segfault in expand_filename(). (There isn't
10937 a way to trigger this remotely.)
10938 - When sending a status event to the controller telling it that an
10939 OR address is reachable, set the port correctly. (Previously we
10940 were reporting the dir port.)
10941 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
10942 command. Bugfix on 0.1.2.17.
10943 - When loading bandwidth history, do not believe any information in
10944 the future. Fixes bug 434.
10945 - When loading entry guard information, do not believe any information
10947 - When we have our clock set far in the future and generate an
10948 onion key, then re-set our clock to be correct, we should not stop
10949 the onion key from getting rotated.
10950 - On some platforms, accept() can return a broken address. Detect
10951 this more quietly, and deal accordingly. Fixes bug 483.
10952 - It's not actually an error to find a non-pending entry in the DNS
10953 cache when canceling a pending resolve. Don't log unless stuff
10954 is fishy. Resolves bug 463.
10955 - Don't reset trusted dir server list when we set a configuration
10956 option. Patch from Robert Hogan.
10959 Changes in version 0.1.2.17 - 2007-08-30
10960 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
10961 X bundles. Vidalia 0.0.14 makes authentication required for the
10962 ControlPort in the default configuration, which addresses important
10963 security risks. Everybody who uses Vidalia (or another controller)
10966 In addition, this Tor update fixes major load balancing problems with
10967 path selection, which should speed things up a lot once many people
10970 o Major bugfixes (security):
10971 - We removed support for the old (v0) control protocol. It has been
10972 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
10973 become more of a headache than it's worth.
10975 o Major bugfixes (load balancing):
10976 - When choosing nodes for non-guard positions, weight guards
10977 proportionally less, since they already have enough load. Patch
10979 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
10980 will allow fast Tor servers to get more attention.
10981 - When we're upgrading from an old Tor version, forget our current
10982 guards and pick new ones according to the new weightings. These
10983 three load balancing patches could raise effective network capacity
10984 by a factor of four. Thanks to Mike Perry for measurements.
10986 o Major bugfixes (stream expiration):
10987 - Expire not-yet-successful application streams in all cases if
10988 they've been around longer than SocksTimeout. Right now there are
10989 some cases where the stream will live forever, demanding a new
10990 circuit every 15 seconds. Fixes bug 454; reported by lodger.
10992 o Minor features (controller):
10993 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
10994 is valid before any authentication has been received. It tells
10995 a controller what kind of authentication is expected, and what
10996 protocol is spoken. Implements proposal 119.
10998 o Minor bugfixes (performance):
10999 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
11000 greatly speeding up loading cached-routers from disk on startup.
11001 - Disable sentinel-based debugging for buffer code: we squashed all
11002 the bugs that this was supposed to detect a long time ago, and now
11003 its only effect is to change our buffer sizes from nice powers of
11004 two (which platform mallocs tend to like) to values slightly over
11005 powers of two (which make some platform mallocs sad).
11007 o Minor bugfixes (misc):
11008 - If exit bandwidth ever exceeds one third of total bandwidth, then
11009 use the correct formula to weight exit nodes when choosing paths.
11010 Based on patch from Mike Perry.
11011 - Choose perfectly fairly among routers when choosing by bandwidth and
11012 weighting by fraction of bandwidth provided by exits. Previously, we
11013 would choose with only approximate fairness, and correct ourselves
11014 if we ran off the end of the list.
11015 - If we require CookieAuthentication but we fail to write the
11016 cookie file, we would warn but not exit, and end up in a state
11017 where no controller could authenticate. Now we exit.
11018 - If we require CookieAuthentication, stop generating a new cookie
11019 every time we change any piece of our config.
11020 - Refuse to start with certain directory authority keys, and
11021 encourage people using them to stop.
11022 - Terminate multi-line control events properly. Original patch
11024 - Fix a minor memory leak when we fail to find enough suitable
11025 servers to choose a circuit.
11026 - Stop leaking part of the descriptor when we run into a particularly
11027 unparseable piece of it.
11030 Changes in version 0.1.2.16 - 2007-08-01
11031 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
11032 remote attacker in certain situations to rewrite the user's torrc
11033 configuration file. This can completely compromise anonymity of users
11034 in most configurations, including those running the Vidalia bundles,
11035 TorK, etc. Or worse.
11037 o Major security fixes:
11038 - Close immediately after missing authentication on control port;
11039 do not allow multiple authentication attempts.
11042 Changes in version 0.1.2.15 - 2007-07-17
11043 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
11044 problems, fixes compilation on BSD, and fixes a variety of other
11045 bugs. Everybody should upgrade.
11047 o Major bugfixes (compilation):
11048 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
11050 o Major bugfixes (crashes):
11051 - Try even harder not to dereference the first character after
11052 an mmap(). Reported by lodger.
11053 - Fix a crash bug in directory authorities when we re-number the
11054 routerlist while inserting a new router.
11055 - When the cached-routers file is an even multiple of the page size,
11056 don't run off the end and crash. (Fixes bug 455; based on idea
11058 - Fix eventdns.c behavior on Solaris: It is critical to include
11059 orconfig.h _before_ sys/types.h, so that we can get the expected
11060 definition of _FILE_OFFSET_BITS.
11062 o Major bugfixes (security):
11063 - Fix a possible buffer overrun when using BSD natd support. Bug
11065 - When sending destroy cells from a circuit's origin, don't include
11066 the reason for tearing down the circuit. The spec says we didn't,
11067 and now we actually don't. Reported by lodger.
11068 - Keep streamids from different exits on a circuit separate. This
11069 bug may have allowed other routers on a given circuit to inject
11070 cells into streams. Reported by lodger; fixes bug 446.
11071 - If there's a never-before-connected-to guard node in our list,
11072 never choose any guards past it. This way we don't expand our
11073 guard list unless we need to.
11075 o Minor bugfixes (guard nodes):
11076 - Weight guard selection by bandwidth, so that low-bandwidth nodes
11077 don't get overused as guards.
11079 o Minor bugfixes (directory):
11080 - Correctly count the number of authorities that recommend each
11081 version. Previously, we were under-counting by 1.
11082 - Fix a potential crash bug when we load many server descriptors at
11083 once and some of them make others of them obsolete. Fixes bug 458.
11085 o Minor bugfixes (hidden services):
11086 - Stop tearing down the whole circuit when the user asks for a
11087 connection to a port that the hidden service didn't configure.
11090 o Minor bugfixes (misc):
11091 - On Windows, we were preventing other processes from reading
11092 cached-routers while Tor was running. Reported by janbar.
11093 - Fix a possible (but very unlikely) bug in picking routers by
11094 bandwidth. Add a log message to confirm that it is in fact
11095 unlikely. Patch from lodger.
11096 - Backport a couple of memory leak fixes.
11097 - Backport miscellaneous cosmetic bugfixes.
11100 Changes in version 0.1.2.14 - 2007-05-25
11101 Tor 0.1.2.14 changes the addresses of two directory authorities (this
11102 change especially affects those who serve or use hidden services),
11103 and fixes several other crash- and security-related bugs.
11105 o Directory authority changes:
11106 - Two directory authorities (moria1 and moria2) just moved to new
11107 IP addresses. This change will particularly affect those who serve
11108 or use hidden services.
11110 o Major bugfixes (crashes):
11111 - If a directory server runs out of space in the connection table
11112 as it's processing a begin_dir request, it will free the exit stream
11113 but leave it attached to the circuit, leading to unpredictable
11114 behavior. (Reported by seeess, fixes bug 425.)
11115 - Fix a bug in dirserv_remove_invalid() that would cause authorities
11116 to corrupt memory under some really unlikely scenarios.
11117 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
11118 - Avoid segfaults when reading from mmaped descriptor file. (Reported
11121 o Major bugfixes (security):
11122 - When choosing an entry guard for a circuit, avoid using guards
11123 that are in the same family as the chosen exit -- not just guards
11124 that are exactly the chosen exit. (Reported by lodger.)
11126 o Major bugfixes (resource management):
11127 - If a directory authority is down, skip it when deciding where to get
11128 networkstatus objects or descriptors. Otherwise we keep asking
11129 every 10 seconds forever. Fixes bug 384.
11130 - Count it as a failure if we fetch a valid network-status but we
11131 don't want to keep it. Otherwise we'll keep fetching it and keep
11132 not wanting to keep it. Fixes part of bug 422.
11133 - If all of our dirservers have given us bad or no networkstatuses
11134 lately, then stop hammering them once per minute even when we
11135 think they're failed. Fixes another part of bug 422.
11138 - Actually set the purpose correctly for descriptors inserted with
11139 purpose=controller.
11140 - When we have k non-v2 authorities in our DirServer config,
11141 we ignored the last k authorities in the list when updating our
11143 - Correctly back-off from requesting router descriptors that we are
11144 having a hard time downloading.
11145 - Read resolv.conf files correctly on platforms where read() returns
11146 partial results on small file reads.
11147 - Don't rebuild the entire router store every time we get 32K of
11148 routers: rebuild it when the journal gets very large, or when
11149 the gaps in the store get very large.
11152 - When routers publish SVN revisions in their router descriptors,
11153 authorities now include those versions correctly in networkstatus
11155 - Warn when using a version of libevent before 1.3b to run a server on
11156 OSX or BSD: these versions interact badly with userspace threads.
11159 Changes in version 0.1.2.13 - 2007-04-24
11160 This release features some major anonymity fixes, such as safer path
11161 selection; better client performance; faster bootstrapping, better
11162 address detection, and better DNS support for servers; write limiting as
11163 well as read limiting to make servers easier to run; and a huge pile of
11164 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
11166 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
11167 of the Freenode IRC network, remembering his patience and vision for
11168 free speech on the Internet.
11170 o Major features, client performance:
11171 - Weight directory requests by advertised bandwidth. Now we can
11172 let servers enable write limiting but still allow most clients to
11173 succeed at their directory requests. (We still ignore weights when
11174 choosing a directory authority; I hope this is a feature.)
11175 - Stop overloading exit nodes -- avoid choosing them for entry or
11176 middle hops when the total bandwidth available from non-exit nodes
11177 is much higher than the total bandwidth available from exit nodes.
11178 - Rather than waiting a fixed amount of time between retrying
11179 application connections, we wait only 10 seconds for the first,
11180 10 seconds for the second, and 15 seconds for each retry after
11181 that. Hopefully this will improve the expected user experience.
11182 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
11183 to open a stream fails; now we do in more cases. This should
11184 make clients able to find a good exit faster in some cases, since
11185 unhandleable requests will now get an error rather than timing out.
11187 o Major features, client functionality:
11188 - Implement BEGIN_DIR cells, so we can connect to a directory
11189 server via TLS to do encrypted directory requests rather than
11190 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
11191 config options if you like. For now, this feature only works if
11192 you already have a descriptor for the destination dirserver.
11193 - Add support for transparent application connections: this basically
11194 bundles the functionality of trans-proxy-tor into the Tor
11195 mainline. Now hosts with compliant pf/netfilter implementations
11196 can redirect TCP connections straight to Tor without diverting
11197 through SOCKS. (Based on patch from tup.)
11198 - Add support for using natd; this allows FreeBSDs earlier than
11199 5.1.2 to have ipfw send connections through Tor without using
11200 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
11202 o Major features, servers:
11203 - Setting up a dyndns name for your server is now optional: servers
11204 with no hostname or IP address will learn their IP address by
11205 asking the directory authorities. This code only kicks in when you
11206 would normally have exited with a "no address" error. Nothing's
11207 authenticated, so use with care.
11208 - Directory servers now spool server descriptors, v1 directories,
11209 and v2 networkstatus objects to buffers as needed rather than en
11210 masse. They also mmap the cached-routers files. These steps save
11212 - Stop requiring clients to have well-formed certificates, and stop
11213 checking nicknames in certificates. (Clients have certificates so
11214 that they can look like Tor servers, but in the future we might want
11215 to allow them to look like regular TLS clients instead. Nicknames
11216 in certificates serve no purpose other than making our protocol
11217 easier to recognize on the wire.) Implements proposal 106.
11219 o Improvements on DNS support:
11220 - Add "eventdns" asynchronous dns library originally based on code
11221 from Adam Langley. Now we can discard the old rickety dnsworker
11222 concept, and support a wider variety of DNS functions. Allows
11223 multithreaded builds on NetBSD and OpenBSD again.
11224 - Add server-side support for "reverse" DNS lookups (using PTR
11225 records so clients can determine the canonical hostname for a given
11226 IPv4 address). Only supported by servers using eventdns; servers
11227 now announce in their descriptors if they don't support eventdns.
11228 - Workaround for name servers (like Earthlink's) that hijack failing
11229 DNS requests and replace the no-such-server answer with a "helpful"
11230 redirect to an advertising-driven search portal. Also work around
11231 DNS hijackers who "helpfully" decline to hijack known-invalid
11232 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
11233 lets you turn it off.
11234 - Servers now check for the case when common DNS requests are going to
11235 wildcarded addresses (i.e. all getting the same answer), and change
11236 their exit policy to reject *:* if it's happening.
11237 - When asked to resolve a hostname, don't use non-exit servers unless
11238 requested to do so. This allows servers with broken DNS to be
11239 useful to the network.
11240 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
11241 useless IPv6 DNS resolves.
11242 - Specify and implement client-side SOCKS5 interface for reverse DNS
11243 lookups (see doc/socks-extensions.txt). Also cache them.
11244 - When we change nameservers or IP addresses, reset and re-launch
11245 our tests for DNS hijacking.
11247 o Improvements on reachability testing:
11248 - Servers send out a burst of long-range padding cells once they've
11249 established that they're reachable. Spread them over 4 circuits,
11250 so hopefully a few will be fast. This exercises bandwidth and
11251 bootstraps them into the directory more quickly.
11252 - When we find our DirPort to be reachable, publish a new descriptor
11253 so we'll tell the world (reported by pnx).
11254 - Directory authorities now only decide that routers are reachable
11255 if their identity keys are as expected.
11256 - Do DirPort reachability tests less often, since a single test
11257 chews through many circuits before giving up.
11258 - Avoid some false positives during reachability testing: don't try
11259 to test via a server that's on the same /24 network as us.
11260 - Start publishing one minute or so after we find our ORPort
11261 to be reachable. This will help reduce the number of descriptors
11262 we have for ourselves floating around, since it's quite likely
11263 other things (e.g. DirPort) will change during that minute too.
11264 - Routers no longer try to rebuild long-term connections to directory
11265 authorities, and directory authorities no longer try to rebuild
11266 long-term connections to all servers. We still don't hang up
11267 connections in these two cases though -- we need to look at it
11268 more carefully to avoid flapping, and we likely need to wait til
11269 0.1.1.x is obsolete.
11271 o Improvements on rate limiting:
11272 - Enable write limiting as well as read limiting. Now we sacrifice
11273 capacity if we're pushing out lots of directory traffic, rather
11274 than overrunning the user's intended bandwidth limits.
11275 - Include TLS overhead when counting bandwidth usage; previously, we
11276 would count only the bytes sent over TLS, but not the bytes used
11278 - Servers decline directory requests much more aggressively when
11279 they're low on bandwidth. Otherwise they end up queueing more and
11280 more directory responses, which can't be good for latency.
11281 - But never refuse directory requests from local addresses.
11282 - Be willing to read or write on local connections (e.g. controller
11283 connections) even when the global rate limiting buckets are empty.
11284 - Flush local controller connection buffers periodically as we're
11285 writing to them, so we avoid queueing 4+ megabytes of data before
11287 - Revise and clean up the torrc.sample that we ship with; add
11288 a section for BandwidthRate and BandwidthBurst.
11290 o Major features, NT services:
11291 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
11292 command-line flag so that admins can override the default by saying
11293 "tor --service install --user "SomeUser"". This will not affect
11294 existing installed services. Also, warn the user that the service
11295 will look for its configuration file in the service user's
11296 %appdata% directory. (We can't do the "hardwire the user's appdata
11297 directory" trick any more, since we may not have read access to that
11299 - Support running the Tor service with a torrc not in the same
11300 directory as tor.exe and default to using the torrc located in
11301 the %appdata%\Tor\ of the user who installed the service. Patch
11303 - Add an --ignore-missing-torrc command-line option so that we can
11304 get the "use sensible defaults if the configuration file doesn't
11305 exist" behavior even when specifying a torrc location on the
11307 - When stopping an NT service, wait up to 10 sec for it to actually
11308 stop. (Patch from Matt Edman; resolves bug 295.)
11310 o Directory authority improvements:
11311 - Stop letting hibernating or obsolete servers affect uptime and
11313 - Stop listing hibernating servers in the v1 directory.
11314 - Authorities no longer recommend exits as guards if this would shift
11315 too much load to the exit nodes.
11316 - Authorities now specify server versions in networkstatus. This adds
11317 about 2% to the size of compressed networkstatus docs, and allows
11318 clients to tell which servers support BEGIN_DIR and which don't.
11319 The implementation is forward-compatible with a proposed future
11320 protocol version scheme not tied to Tor versions.
11321 - DirServer configuration lines now have an orport= option so
11322 clients can open encrypted tunnels to the authorities without
11323 having downloaded their descriptors yet. Enabled for moria1,
11324 moria2, tor26, and lefkada now in the default configuration.
11325 - Add a BadDirectory flag to network status docs so that authorities
11326 can (eventually) tell clients about caches they believe to be
11327 broken. Not used yet.
11328 - Allow authorities to list nodes as bad exits in their
11329 approved-routers file by fingerprint or by address. If most
11330 authorities set a BadExit flag for a server, clients don't think
11331 of it as a general-purpose exit. Clients only consider authorities
11332 that advertise themselves as listing bad exits.
11333 - Patch from Steve Hildrey: Generate network status correctly on
11334 non-versioning dirservers.
11335 - Have directory authorities allow larger amounts of drift in uptime
11336 without replacing the server descriptor: previously, a server that
11337 restarted every 30 minutes could have 48 "interesting" descriptors
11339 - Reserve the nickname "Unnamed" for routers that can't pick
11340 a hostname: any router can call itself Unnamed; directory
11341 authorities will never allocate Unnamed to any particular router;
11342 clients won't believe that any router is the canonical Unnamed.
11344 o Directory mirrors and clients:
11345 - Discard any v1 directory info that's over 1 month old (for
11346 directories) or over 1 week old (for running-routers lists).
11347 - Clients track responses with status 503 from dirservers. After a
11348 dirserver has given us a 503, we try not to use it until an hour has
11349 gone by, or until we have no dirservers that haven't given us a 503.
11350 - When we get a 503 from a directory, and we're not a server, we no
11351 longer count the failure against the total number of failures
11352 allowed for the object we're trying to download.
11353 - Prepare for servers to publish descriptors less often: never
11354 discard a descriptor simply for being too old until either it is
11355 recommended by no authorities, or until we get a better one for
11356 the same router. Make caches consider retaining old recommended
11357 routers for even longer.
11358 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
11359 headers for content, so that we can work better in the presence of
11360 caching HTTP proxies.
11361 - Stop fetching descriptors if you're not a dir mirror and you
11362 haven't tried to establish any circuits lately. (This currently
11363 causes some dangerous behavior, because when you start up again
11364 you'll use your ancient server descriptors.)
11366 o Major fixes, crashes:
11367 - Stop crashing when the controller asks us to resetconf more than
11368 one config option at once. (Vidalia 0.0.11 does this.)
11369 - Fix a longstanding obscure crash bug that could occur when we run
11370 out of DNS worker processes, if we're not using eventdns. (Resolves
11372 - Fix an assert that could trigger if a controller quickly set then
11373 cleared EntryNodes. (Bug found by Udo van den Heuvel.)
11374 - Avoid crash when telling controller about stream-status and a
11375 stream is detached.
11376 - Avoid sending junk to controllers or segfaulting when a controller
11377 uses EVENT_NEW_DESC with verbose nicknames.
11378 - Stop triggering asserts if the controller tries to extend hidden
11379 service circuits (reported by mwenge).
11380 - If we start a server with ClientOnly 1, then set ClientOnly to 0
11381 and hup, stop triggering an assert based on an empty onion_key.
11382 - Mask out all signals in sub-threads; only the libevent signal
11383 handler should be processing them. This should prevent some crashes
11384 on some machines using pthreads. (Patch from coderman.)
11385 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
11387 o Major fixes, anonymity/security:
11388 - Automatically avoid picking more than one node from the same
11389 /16 network when constructing a circuit. Add an
11390 "EnforceDistinctSubnets" option to let people disable it if they
11391 want to operate private test networks on a single subnet.
11392 - When generating bandwidth history, round down to the nearest
11393 1k. When storing accounting data, round up to the nearest 1k.
11394 - When we're running as a server, remember when we last rotated onion
11395 keys, so that we will rotate keys once they're a week old even if
11396 we never stay up for a week ourselves.
11397 - If a client asked for a server by name, and there's a named server
11398 in our network-status but we don't have its descriptor yet, we
11399 could return an unnamed server instead.
11400 - Reject (most) attempts to use Tor circuits with length one. (If
11401 many people start using Tor as a one-hop proxy, exit nodes become
11402 a more attractive target for compromise.)
11403 - Just because your DirPort is open doesn't mean people should be
11404 able to remotely teach you about hidden service descriptors. Now
11405 only accept rendezvous posts if you've got HSAuthoritativeDir set.
11406 - Fix a potential race condition in the rpm installer. Found by
11408 - Do not log IPs with TLS failures for incoming TLS
11409 connections. (Fixes bug 382.)
11411 o Major fixes, other:
11412 - If our system clock jumps back in time, don't publish a negative
11413 uptime in the descriptor.
11414 - When we start during an accounting interval before it's time to wake
11415 up, remember to wake up at the correct time. (May fix bug 342.)
11416 - Previously, we would cache up to 16 old networkstatus documents
11417 indefinitely, if they came from nontrusted authorities. Now we
11418 discard them if they are more than 10 days old.
11419 - When we have a state file we cannot parse, tell the user and
11420 move it aside. Now we avoid situations where the user starts
11421 Tor in 1904, Tor writes a state file with that timestamp in it,
11422 the user fixes her clock, and Tor refuses to start.
11423 - Publish a new descriptor after we hup/reload. This is important
11424 if our config has changed such that we'll want to start advertising
11425 our DirPort now, etc.
11426 - If we are using an exit enclave and we can't connect, e.g. because
11427 its webserver is misconfigured to not listen on localhost, then
11428 back off and try connecting from somewhere else before we fail.
11430 o New config options or behaviors:
11431 - When EntryNodes are configured, rebuild the guard list to contain,
11432 in order: the EntryNodes that were guards before; the rest of the
11433 EntryNodes; the nodes that were guards before.
11434 - Do not warn when individual nodes in the configuration's EntryNodes,
11435 ExitNodes, etc are down: warn only when all possible nodes
11436 are down. (Fixes bug 348.)
11437 - Put a lower-bound on MaxAdvertisedBandwidth.
11438 - Start using the state file to store bandwidth accounting data:
11439 the bw_accounting file is now obsolete. We'll keep generating it
11440 for a while for people who are still using 0.1.2.4-alpha.
11441 - Try to batch changes to the state file so that we do as few
11442 disk writes as possible while still storing important things in
11444 - The state file and the bw_accounting file get saved less often when
11445 the AvoidDiskWrites config option is set.
11446 - Make PIDFile work on Windows.
11447 - Add internal descriptions for a bunch of configuration options:
11448 accessible via controller interface and in comments in saved
11450 - Reject *:563 (NNTPS) in the default exit policy. We already reject
11451 NNTP by default, so this seems like a sensible addition.
11452 - Clients now reject hostnames with invalid characters. This should
11453 avoid some inadvertent info leaks. Add an option
11454 AllowNonRFC953Hostnames to disable this behavior, in case somebody
11455 is running a private network with hosts called @, !, and #.
11456 - Check for addresses with invalid characters at the exit as well,
11457 and warn less verbosely when they fail. You can override this by
11458 setting ServerDNSAllowNonRFC953Addresses to 1.
11459 - Remove some options that have been deprecated since at least
11460 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
11461 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
11462 to set log options. Mark PathlenCoinWeight as obsolete.
11463 - Stop accepting certain malformed ports in configured exit policies.
11464 - When the user uses bad syntax in the Log config line, stop
11465 suggesting other bad syntax as a replacement.
11466 - Add new config option "ResolvConf" to let the server operator
11467 choose an alternate resolve.conf file when using eventdns.
11468 - If one of our entry guards is on the ExcludeNodes list, or the
11469 directory authorities don't think it's a good guard, treat it as
11470 if it were unlisted: stop using it as a guard, and throw it off
11471 the guards list if it stays that way for a long time.
11472 - Allow directory authorities to be marked separately as authorities
11473 for the v1 directory protocol, the v2 directory protocol, and
11474 as hidden service directories, to make it easier to retire old
11475 authorities. V1 authorities should set "HSAuthoritativeDir 1"
11476 to continue being hidden service authorities too.
11477 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
11478 - Make TrackExitHosts case-insensitive, and fix the behavior of
11479 ".suffix" TrackExitHosts items to avoid matching in the middle of
11481 - New DirPort behavior: if you have your dirport set, you download
11482 descriptors aggressively like a directory mirror, whether or not
11483 your ORPort is set.
11486 - Create a new file ReleaseNotes which was the old ChangeLog. The
11487 new ChangeLog file now includes the notes for all development
11489 - Add a new address-spec.txt document to describe our special-case
11490 addresses: .exit, .onion, and .noconnnect.
11491 - Fork the v1 directory protocol into its own spec document,
11492 and mark dir-spec.txt as the currently correct (v2) spec.
11494 o Packaging, porting, and contrib
11495 - "tor --verify-config" now exits with -1(255) or 0 depending on
11496 whether the config options are bad or good.
11497 - The Debian package now uses --verify-config when (re)starting,
11498 to distinguish configuration errors from other errors.
11499 - Adapt a patch from goodell to let the contrib/exitlist script
11500 take arguments rather than require direct editing.
11501 - Prevent the contrib/exitlist script from printing the same
11502 result more than once.
11503 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
11504 - In the hidden service example in torrc.sample, stop recommending
11505 esoteric and discouraged hidden service options.
11506 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
11507 values before failing, and always enables eventdns.
11508 - Try to detect Windows correctly when cross-compiling.
11509 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
11510 Try to fix this in configure.in by checking for most functions
11511 before we check for libevent.
11512 - Update RPMs to require libevent 1.2.
11513 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
11514 or later. Log when we are doing this, so we can diagnose it when
11515 it fails. (Also, recommend libevent 1.1b for kqueue and
11516 win32 methods; deprecate libevent 1.0b harder; make libevent
11517 recommendation system saner.)
11518 - Build with recent (1.3+) libevents on platforms that do not
11519 define the nonstandard types "u_int8_t" and friends.
11520 - Remove architecture from OS X builds. The official builds are
11521 now universal binaries.
11522 - Run correctly on OS X platforms with case-sensitive filesystems.
11523 - Correctly set maximum connection limit on Cygwin. (This time
11525 - Start compiling on MinGW on Windows (patches from Mike Chiussi
11527 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
11528 - Finally fix the openssl warnings from newer gccs that believe that
11529 ignoring a return value is okay, but casting a return value and
11530 then ignoring it is a sign of madness.
11531 - On architectures where sizeof(int)>4, still clamp declarable
11532 bandwidth to INT32_MAX.
11534 o Minor features, controller:
11535 - Warn the user when an application uses the obsolete binary v0
11536 control protocol. We're planning to remove support for it during
11537 the next development series, so it's good to give people some
11539 - Add STREAM_BW events to report per-entry-stream bandwidth
11540 use. (Patch from Robert Hogan.)
11541 - Rate-limit SIGNEWNYM signals in response to controllers that
11542 impolitely generate them for every single stream. (Patch from
11543 mwenge; closes bug 394.)
11544 - Add a REMAP status to stream events to note that a stream's
11545 address has changed because of a cached address or a MapAddress
11547 - Make REMAP stream events have a SOURCE (cache or exit), and
11548 make them generated in every case where we get a successful
11549 connected or resolved cell.
11550 - Track reasons for OR connection failure; make these reasons
11551 available via the controller interface. (Patch from Mike Perry.)
11552 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
11553 can learn when clients are sending malformed hostnames to Tor.
11554 - Specify and implement some of the controller status events.
11555 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
11556 - Reimplement GETINFO so that info/names stays in sync with the
11558 - Implement "GETINFO fingerprint".
11559 - Implement "SETEVENTS GUARD" so controllers can get updates on
11560 entry guard status as it changes.
11561 - Make all connections to addresses of the form ".noconnect"
11562 immediately get closed. This lets application/controller combos
11563 successfully test whether they're talking to the same Tor by
11564 watching for STREAM events.
11565 - Add a REASON field to CIRC events; for backward compatibility, this
11566 field is sent only to controllers that have enabled the extended
11567 event format. Also, add additional reason codes to explain why
11568 a given circuit has been destroyed or truncated. (Patches from
11570 - Add a REMOTE_REASON field to extended CIRC events to tell the
11571 controller why a remote OR told us to close a circuit.
11572 - Stream events also now have REASON and REMOTE_REASON fields,
11573 working much like those for circuit events.
11574 - There's now a GETINFO ns/... field so that controllers can ask Tor
11575 about the current status of a router.
11576 - A new event type "NS" to inform a controller when our opinion of
11577 a router's status has changed.
11578 - Add a GETINFO events/names and GETINFO features/names so controllers
11579 can tell which events and features are supported.
11580 - A new CLEARDNSCACHE signal to allow controllers to clear the
11581 client-side DNS cache without expiring circuits.
11582 - Fix CIRC controller events so that controllers can learn the
11583 identity digests of non-Named servers used in circuit paths.
11584 - Let controllers ask for more useful identifiers for servers. Instead
11585 of learning identity digests for un-Named servers and nicknames
11586 for Named servers, the new identifiers include digest, nickname,
11587 and indication of Named status. Off by default; see control-spec.txt
11588 for more information.
11589 - Add a "getinfo address" controller command so it can display Tor's
11590 best guess to the user.
11591 - New controller event to alert the controller when our server
11592 descriptor has changed.
11593 - Give more meaningful errors on controller authentication failure.
11594 - Export the default exit policy via the control port, so controllers
11595 don't need to guess what it is / will be later.
11597 o Minor bugfixes, controller:
11598 - When creating a circuit via the controller, send a 'launched'
11599 event when we're done, so we follow the spec better.
11600 - Correct the control spec to match how the code actually responds
11601 to 'getinfo addr-mappings/*'. Reported by daejees.
11602 - The control spec described a GUARDS event, but the code
11603 implemented a GUARD event. Standardize on GUARD, but let people
11604 ask for GUARDS too. Reported by daejees.
11605 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
11606 clear the corresponding on_circuit variable, and remember later
11607 that we don't need to send a redundant CLOSED event. (Resolves part
11609 - Report events where a resolve succeeded or where we got a socks
11610 protocol error correctly, rather than calling both of them
11612 - Change reported stream target addresses to IP consistently when
11613 we finally get the IP from an exit node.
11614 - Send log messages to the controller even if they happen to be very
11616 - Flush ERR-level controller status events just like we currently
11617 flush ERR-level log events, so that a Tor shutdown doesn't prevent
11618 the controller from learning about current events.
11619 - Report the circuit number correctly in STREAM CLOSED events. Bug
11620 reported by Mike Perry.
11621 - Do not report bizarre values for results of accounting GETINFOs
11622 when the last second's write or read exceeds the allotted bandwidth.
11623 - Report "unrecognized key" rather than an empty string when the
11624 controller tries to fetch a networkstatus that doesn't exist.
11625 - When the controller does a "GETINFO network-status", tell it
11626 about even those routers whose descriptors are very old, and use
11627 long nicknames where appropriate.
11628 - Fix handling of verbose nicknames with ORCONN controller events:
11629 make them show up exactly when requested, rather than exactly when
11631 - Controller signals now work on non-Unix platforms that don't define
11632 SIGUSR1 and SIGUSR2 the way we expect.
11633 - Respond to SIGNAL command before we execute the signal, in case
11634 the signal shuts us down. Suggested by Karsten Loesing.
11635 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
11637 o Minor features, code performance:
11638 - Major performance improvement on inserting descriptors: change
11639 algorithm from O(n^2) to O(n).
11640 - Do not rotate onion key immediately after setting it for the first
11642 - Call router_have_min_dir_info half as often. (This is showing up in
11643 some profiles, but not others.)
11644 - When using GCC, make log_debug never get called at all, and its
11645 arguments never get evaluated, when no debug logs are configured.
11646 (This is showing up in some profiles, but not others.)
11647 - Statistics dumped by -USR2 now include a breakdown of public key
11648 operations, for profiling.
11649 - Make the common memory allocation path faster on machines where
11650 malloc(0) returns a pointer.
11651 - Split circuit_t into origin_circuit_t and or_circuit_t, and
11652 split connection_t into edge, or, dir, control, and base structs.
11653 These will save quite a bit of memory on busy servers, and they'll
11654 also help us track down bugs in the code and bugs in the spec.
11655 - Use OpenSSL's AES implementation on platforms where it's faster.
11656 This could save us as much as 10% CPU usage.
11658 o Minor features, descriptors and descriptor handling:
11659 - Avoid duplicate entries on MyFamily line in server descriptor.
11660 - When Tor receives a router descriptor that it asked for, but
11661 no longer wants (because it has received fresh networkstatuses
11662 in the meantime), do not warn the user. Cache the descriptor if
11663 we're a cache; drop it if we aren't.
11664 - Servers no longer ever list themselves in their "family" line,
11665 even if configured to do so. This makes it easier to configure
11666 family lists conveniently.
11668 o Minor fixes, confusing/misleading log messages:
11669 - Display correct results when reporting which versions are
11670 recommended, and how recommended they are. (Resolves bug 383.)
11671 - Inform the server operator when we decide not to advertise a
11672 DirPort due to AccountingMax enabled or a low BandwidthRate.
11673 - Only include function names in log messages for info/debug messages.
11674 For notice/warn/err, the content of the message should be clear on
11675 its own, and printing the function name only confuses users.
11676 - Remove even more protocol-related warnings from Tor server logs,
11677 such as bad TLS handshakes and malformed begin cells.
11678 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
11679 when the IP address is mapped through MapAddress to a hostname.
11680 - Fix misleading log messages: an entry guard that is "unlisted",
11681 as well as not known to be "down" (because we've never heard
11682 of it), is not therefore "up".
11684 o Minor fixes, old/obsolete behavior:
11685 - Start assuming we can use a create_fast cell if we don't know
11686 what version a router is running.
11687 - We no longer look for identity and onion keys in "identity.key" and
11688 "onion.key" -- these were replaced by secret_id_key and
11689 secret_onion_key in 0.0.8pre1.
11690 - We no longer require unrecognized directory entries to be
11692 - Drop compatibility with obsolete Tors that permit create cells
11693 to have the wrong circ_id_type.
11694 - Remove code to special-case "-cvs" ending, since it has not
11695 actually mattered since 0.0.9.
11696 - Don't re-write the fingerprint file every restart, unless it has
11699 o Minor fixes, misc client-side behavior:
11700 - Always remove expired routers and networkstatus docs before checking
11701 whether we have enough information to build circuits. (Fixes
11703 - When computing clock skew from directory HTTP headers, consider what
11704 time it was when we finished asking for the directory, not what
11706 - Make our socks5 handling more robust to broken socks clients:
11707 throw out everything waiting on the buffer in between socks
11708 handshake phases, since they can't possibly (so the theory
11709 goes) have predicted what we plan to respond to them.
11710 - Expire socks connections if they spend too long waiting for the
11711 handshake to finish. Previously we would let them sit around for
11712 days, if the connecting application didn't close them either.
11713 - And if the socks handshake hasn't started, don't send a
11714 "DNS resolve socks failed" handshake reply; just close it.
11715 - If the user asks to use invalid exit nodes, be willing to use
11717 - Track unreachable entry guards correctly: don't conflate
11718 'unreachable by us right now' with 'listed as down by the directory
11719 authorities'. With the old code, if a guard was unreachable by us
11720 but listed as running, it would clog our guard list forever.
11721 - Behave correctly in case we ever have a network with more than
11722 2GB/s total advertised capacity.
11723 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
11724 - Fix a memory leak when we ask for "all" networkstatuses and we
11725 get one we don't recognize.
11728 Changes in version 0.1.1.26 - 2006-12-14
11729 o Security bugfixes:
11730 - Stop sending the HttpProxyAuthenticator string to directory
11731 servers when directory connections are tunnelled through Tor.
11732 - Clients no longer store bandwidth history in the state file.
11733 - Do not log introduction points for hidden services if SafeLogging
11737 - Fix an assert failure when a directory authority sets
11738 AuthDirRejectUnlisted and then receives a descriptor from an
11739 unlisted router (reported by seeess).
11742 Changes in version 0.1.1.25 - 2006-11-04
11744 - When a client asks us to resolve (rather than connect to)
11745 an address, and we have a cached answer, give them the cached
11746 answer. Previously, we would give them no answer at all.
11747 - We were building exactly the wrong circuits when we predict
11748 hidden service requirements, meaning Tor would have to build all
11749 its circuits on demand.
11750 - If none of our live entry guards have a high uptime, but we
11751 require a guard with a high uptime, try adding a new guard before
11752 we give up on the requirement. This patch should make long-lived
11753 connections more stable on average.
11754 - When testing reachability of our DirPort, don't launch new
11755 tests when there's already one in progress -- unreachable
11756 servers were stacking up dozens of testing streams.
11758 o Security bugfixes:
11759 - When the user sends a NEWNYM signal, clear the client-side DNS
11760 cache too. Otherwise we continue to act on previous information.
11763 - Avoid a memory corruption bug when creating a hash table for
11765 - Avoid possibility of controller-triggered crash when misusing
11766 certain commands from a v0 controller on platforms that do not
11767 handle printf("%s",NULL) gracefully.
11768 - Avoid infinite loop on unexpected controller input.
11769 - Don't log spurious warnings when we see a circuit close reason we
11770 don't recognize; it's probably just from a newer version of Tor.
11771 - Add Vidalia to the OS X uninstaller script, so when we uninstall
11772 Tor/Privoxy we also uninstall Vidalia.
11775 Changes in version 0.1.1.24 - 2006-09-29
11777 - Allow really slow clients to not hang up five minutes into their
11778 directory downloads (suggested by Adam J. Richter).
11779 - Fix major performance regression from 0.1.0.x: instead of checking
11780 whether we have enough directory information every time we want to
11781 do something, only check when the directory information has changed.
11782 This should improve client CPU usage by 25-50%.
11783 - Don't crash if, after a server has been running for a while,
11784 it can't resolve its hostname.
11785 - When a client asks us to resolve (not connect to) an address,
11786 and we have a cached answer, give them the cached answer.
11787 Previously, we would give them no answer at all.
11790 - Allow Tor to start when RunAsDaemon is set but no logs are set.
11791 - Don't crash when the controller receives a third argument to an
11792 "extendcircuit" request.
11793 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
11794 response; fix error code when "getinfo dir/status/" fails.
11795 - Fix configure.in to not produce broken configure files with
11796 more recent versions of autoconf. Thanks to Clint for his auto*
11798 - Fix security bug on NetBSD that could allow someone to force
11799 uninitialized RAM to be sent to a server's DNS resolver. This
11800 only affects NetBSD and other platforms that do not bounds-check
11802 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
11803 methods: these are known to be buggy.
11804 - If we're a directory mirror and we ask for "all" network status
11805 documents, we would discard status documents from authorities
11806 we don't recognize.
11809 Changes in version 0.1.1.23 - 2006-07-30
11811 - Fast Tor servers, especially exit nodes, were triggering asserts
11812 due to a bug in handling the list of pending DNS resolves. Some
11813 bugs still remain here; we're hunting them.
11814 - Entry guards could crash clients by sending unexpected input.
11815 - More fixes on reachability testing: if you find yourself reachable,
11816 then don't ever make any client requests (so you stop predicting
11817 circuits), then hup or have your clock jump, then later your IP
11818 changes, you won't think circuits are working, so you won't try to
11819 test reachability, so you won't publish.
11822 - Avoid a crash if the controller does a resetconf firewallports
11823 and then a setconf fascistfirewall=1.
11824 - Avoid an integer underflow when the dir authority decides whether
11825 a router is stable: we might wrongly label it stable, and compute
11826 a slightly wrong median stability, when a descriptor is published
11828 - Fix a place where we might trigger an assert if we can't build our
11829 own server descriptor yet.
11832 Changes in version 0.1.1.22 - 2006-07-05
11834 - Fix a big bug that was causing servers to not find themselves
11835 reachable if they changed IP addresses. Since only 0.1.1.22+
11836 servers can do reachability testing correctly, now we automatically
11837 make sure to test via one of these.
11838 - Fix to allow clients and mirrors to learn directory info from
11839 descriptor downloads that get cut off partway through.
11840 - Directory authorities had a bug in deciding if a newly published
11841 descriptor was novel enough to make everybody want a copy -- a few
11842 servers seem to be publishing new descriptors many times a minute.
11844 - Fix a rare bug that was causing some servers to complain about
11845 "closing wedged cpuworkers" and skip some circuit create requests.
11846 - Make the Exit flag in directory status documents actually work.
11849 Changes in version 0.1.1.21 - 2006-06-10
11850 o Crash and assert fixes from 0.1.1.20:
11851 - Fix a rare crash on Tor servers that have enabled hibernation.
11852 - Fix a seg fault on startup for Tor networks that use only one
11853 directory authority.
11854 - Fix an assert from a race condition that occurs on Tor servers
11855 while exiting, where various threads are trying to log that they're
11856 exiting, and delete the logs, at the same time.
11857 - Make our unit tests pass again on certain obscure platforms.
11860 - Add support for building SUSE RPM packages.
11861 - Speed up initial bootstrapping for clients: if we are making our
11862 first ever connection to any entry guard, then don't mark it down
11864 - When only one Tor server in the network is labelled as a guard,
11865 and we've already picked him, we would cycle endlessly picking him
11866 again, being unhappy about it, etc. Now we specifically exclude
11867 current guards when picking a new guard.
11868 - Servers send create cells more reliably after the TLS connection
11869 is established: we were sometimes forgetting to send half of them
11870 when we had more than one pending.
11871 - If we get a create cell that asks us to extend somewhere, but the
11872 Tor server there doesn't match the expected digest, we now send
11873 a destroy cell back, rather than silently doing nothing.
11874 - Make options->RedirectExit work again.
11875 - Make cookie authentication for the controller work again.
11876 - Stop being picky about unusual characters in the arguments to
11877 mapaddress. It's none of our business.
11878 - Add a new config option "TestVia" that lets you specify preferred
11879 middle hops to use for test circuits. Perhaps this will let me
11880 debug the reachability problems better.
11882 o Log / documentation fixes:
11883 - If we're a server and some peer has a broken TLS certificate, don't
11884 log about it unless ProtocolWarnings is set, i.e., we want to hear
11885 about protocol violations by others.
11886 - Fix spelling of VirtualAddrNetwork in man page.
11887 - Add a better explanation at the top of the autogenerated torrc file
11888 about what happened to our old torrc.
11891 Changes in version 0.1.1.20 - 2006-05-23
11892 o Crash and assert fixes from 0.1.0.17:
11893 - Fix assert bug in close_logs() on exit: when we close and delete
11894 logs, remove them all from the global "logfiles" list.
11895 - Fix an assert error when we're out of space in the connection_list
11896 and we try to post a hidden service descriptor (reported by Peter
11898 - Fix a rare assert error when we've tried all intro points for
11899 a hidden service and we try fetching the service descriptor again:
11900 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed".
11901 - Setconf SocksListenAddress kills Tor if it fails to bind. Now back
11902 out and refuse the setconf if it would fail.
11903 - If you specify a relative torrc path and you set RunAsDaemon in
11904 your torrc, then it chdir()'s to the new directory. If you then
11905 HUP, it tries to load the new torrc location, fails, and exits.
11906 The fix: no longer allow a relative path to torrc when using -f.
11907 - Check for integer overflows in more places, when adding elements
11908 to smartlists. This could possibly prevent a buffer overflow
11909 on malicious huge inputs.
11911 o Security fixes, major:
11912 - When we're printing strings from the network, don't try to print
11913 non-printable characters. Now we're safer against shell escape
11914 sequence exploits, and also against attacks to fool users into
11915 misreading their logs.
11916 - Implement entry guards: automatically choose a handful of entry
11917 nodes and stick with them for all circuits. Only pick new guards
11918 when the ones you have are unsuitable, and if the old guards
11919 become suitable again, switch back. This will increase security
11920 dramatically against certain end-point attacks. The EntryNodes
11921 config option now provides some hints about which entry guards you
11922 want to use most; and StrictEntryNodes means to only use those.
11923 Fixes CVE-2006-0414.
11924 - Implement exit enclaves: if we know an IP address for the
11925 destination, and there's a running Tor server at that address
11926 which allows exit to the destination, then extend the circuit to
11927 that exit first. This provides end-to-end encryption and end-to-end
11928 authentication. Also, if the user wants a .exit address or enclave,
11929 use 4 hops rather than 3, and cannibalize a general circ for it
11931 - Obey our firewall options more faithfully:
11932 . If we can't get to a dirserver directly, try going via Tor.
11933 . Don't ever try to connect (as a client) to a place our
11934 firewall options forbid.
11935 . If we specify a proxy and also firewall options, obey the
11936 firewall options even when we're using the proxy: some proxies
11937 can only proxy to certain destinations.
11938 - Make clients regenerate their keys when their IP address changes.
11939 - For the OS X package's modified privoxy config file, comment
11940 out the "logfile" line so we don't log everything passed
11942 - Our TLS handshakes were generating a single public/private
11943 keypair for the TLS context, rather than making a new one for
11944 each new connection. Oops. (But we were still rotating them
11945 periodically, so it's not so bad.)
11946 - When we were cannibalizing a circuit with a particular exit
11947 node in mind, we weren't checking to see if that exit node was
11948 already present earlier in the circuit. Now we are.
11949 - Require server descriptors to list IPv4 addresses -- hostnames
11950 are no longer allowed. This also fixes potential vulnerabilities
11951 to servers providing hostnames as their address and then
11952 preferentially resolving them so they can partition users.
11953 - Our logic to decide if the OR we connected to was the right guy
11954 was brittle and maybe open to a mitm for invalid routers.
11956 o Security fixes, minor:
11957 - Adjust tor-spec.txt to parameterize cell and key lengths. Now
11958 Ian Goldberg can prove things about our handshake protocol more
11960 - Make directory authorities generate a separate "guard" flag to
11961 mean "would make a good entry guard". Clients now honor the
11962 is_guard flag rather than looking at is_fast or is_stable.
11963 - Try to list MyFamily elements by key, not by nickname, and warn
11964 if we've not heard of a server.
11965 - Start using RAND_bytes rather than RAND_pseudo_bytes from
11966 OpenSSL. Also, reseed our entropy every hour, not just at
11967 startup. And add entropy in 512-bit chunks, not 160-bit chunks.
11968 - Refuse server descriptors where the fingerprint line doesn't match
11969 the included identity key. Tor doesn't care, but other apps (and
11970 humans) might actually be trusting the fingerprint line.
11971 - We used to kill the circuit when we receive a relay command we
11972 don't recognize. Now we just drop that cell.
11973 - Fix a bug found by Lasse Overlier: when we were making internal
11974 circuits (intended to be cannibalized later for rendezvous and
11975 introduction circuits), we were picking them so that they had
11976 useful exit nodes. There was no need for this, and it actually
11977 aids some statistical attacks.
11978 - Start treating internal circuits and exit circuits separately.
11979 It's important to keep them separate because internal circuits
11980 have their last hops picked like middle hops, rather than like
11981 exit hops. So exiting on them will break the user's expectations.
11982 - Fix a possible way to DoS dirservers.
11983 - When the client asked for a rendezvous port that the hidden
11984 service didn't want to provide, we were sending an IP address
11985 back along with the end cell. Fortunately, it was zero. But stop
11988 o Packaging improvements:
11989 - Implement --with-libevent-dir option to ./configure. Improve
11990 search techniques to find libevent, and use those for openssl too.
11991 - Fix a couple of bugs in OpenSSL detection. Deal better when
11992 there are multiple SSLs installed with different versions.
11993 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
11994 - On non-gcc compilers (e.g. Solaris's cc), use "-g -O" instead of
11996 - Make unit tests (and other invocations that aren't the real Tor)
11997 run without launching listeners, creating subdirectories, and so on.
11998 - The OS X installer was adding a symlink for tor_resolve but
11999 the binary was called tor-resolve (reported by Thomas Hardly).
12000 - Now we can target arch and OS in rpm builds (contributed by
12001 Phobos). Also make the resulting dist-rpm filename match the
12003 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
12004 if you log to syslog and want something other than LOG_DAEMON.
12005 - Fix the torify (tsocks) config file to not use Tor for localhost
12007 - Start shipping socks-extensions.txt, tor-doc-unix.html,
12008 tor-doc-server.html, and stylesheet.css in the tarball.
12009 - Stop shipping tor-doc.html, INSTALL, and README in the tarball.
12010 They are useless now.
12011 - Add Peter Palfrader's contributed check-tor script. It lets you
12012 easily check whether a given server (referenced by nickname)
12013 is reachable by you.
12014 - Add BSD-style contributed startup script "rc.subr" from Peter
12017 o Directory improvements -- new directory protocol:
12018 - See tor/doc/dir-spec.txt for all the juicy details. Key points:
12019 - Authorities and caches publish individual descriptors (by
12020 digest, by fingerprint, by "all", and by "tell me yours").
12021 - Clients don't download or use the old directory anymore. Now they
12022 download network-statuses from the directory authorities, and
12023 fetch individual server descriptors as needed from mirrors.
12024 - Clients don't download descriptors of non-running servers.
12025 - Download descriptors by digest, not by fingerprint. Caches try to
12026 download all listed digests from authorities; clients try to
12027 download "best" digests from caches. This avoids partitioning
12028 and isolating attacks better.
12029 - Only upload a new server descriptor when options change, 18
12030 hours have passed, uptime is reset, or bandwidth changes a lot.
12031 - Directory authorities silently throw away new descriptors that
12032 haven't changed much if the timestamps are similar. We do this to
12033 tolerate older Tor servers that upload a new descriptor every 15
12034 minutes. (It seemed like a good idea at the time.)
12035 - Clients choose directory servers from the network status lists,
12036 not from their internal list of router descriptors. Now they can
12037 go to caches directly rather than needing to go to authorities
12038 to bootstrap the first set of descriptors.
12039 - When picking a random directory, prefer non-authorities if any
12041 - Add a new flag to network-status indicating whether the server
12042 can answer v2 directory requests too.
12043 - Directory mirrors now cache up to 16 unrecognized network-status
12044 docs, so new directory authorities will be cached too.
12045 - Stop parsing, storing, or using running-routers output (but
12046 mirrors still cache and serve it).
12047 - Clients consider a threshold of "versioning" directory authorities
12048 before deciding whether to warn the user that he's obsolete.
12049 - Authorities publish separate sorted lists of recommended versions
12050 for clients and for servers.
12051 - Change DirServers config line to note which dirs are v1 authorities.
12052 - Put nicknames on the DirServer line, so we can refer to them
12053 without requiring all our users to memorize their IP addresses.
12054 - Remove option when getting directory cache to see whether they
12055 support running-routers; they all do now. Replace it with one
12056 to see whether caches support v2 stuff.
12057 - Stop listing down or invalid nodes in the v1 directory. This
12058 reduces its bulk by about 1/3, and reduces load on mirrors.
12059 - Mirrors no longer cache the v1 directory as often.
12060 - If we as a directory mirror don't know of any v1 directory
12061 authorities, then don't try to cache any v1 directories.
12063 o Other directory improvements:
12064 - Add lefkada.eecs.harvard.edu and tor.dizum.com as fourth and
12065 fifth authoritative directory servers.
12066 - Directory authorities no longer require an open connection from
12067 a server to consider him "reachable". We need this change because
12068 when we add new directory authorities, old servers won't know not
12069 to hang up on them.
12070 - Dir authorities now do their own external reachability testing
12071 of each server, and only list as running the ones they found to
12072 be reachable. We also send back warnings to the server's logs if
12073 it uploads a descriptor that we already believe is unreachable.
12074 - Spread the directory authorities' reachability testing over the
12075 entire testing interval, so we don't try to do 500 TLS's at once
12077 - Make the "stable" router flag in network-status be the median of
12078 the uptimes of running valid servers, and make clients pay
12079 attention to the network-status flags. Thus the cutoff adapts
12080 to the stability of the network as a whole, making IRC, IM, etc
12081 connections more reliable.
12082 - Make the v2 dir's "Fast" flag based on relative capacity, just
12083 like "Stable" is based on median uptime. Name everything in the
12084 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
12085 - Retry directory requests if we fail to get an answer we like
12086 from a given dirserver (we were retrying before, but only if
12087 we fail to connect).
12088 - Return a robots.txt on our dirport to discourage google indexing.
12090 o Controller protocol improvements:
12091 - Revised controller protocol (version 1) that uses ascii rather
12092 than binary: tor/doc/control-spec.txt. Add supporting libraries
12093 in python and java and c# so you can use the controller from your
12094 applications without caring how our protocol works.
12095 - Allow the DEBUG controller event to work again. Mark certain log
12096 entries as "don't tell this to controllers", so we avoid cycles.
12097 - New controller function "getinfo accounting", to ask how
12098 many bytes we've used in this time period.
12099 - Add a "resetconf" command so you can set config options like
12100 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
12101 a config option in the torrc with no value, then it clears it
12102 entirely (rather than setting it to its default).
12103 - Add a "getinfo config-file" to tell us where torrc is. Also
12104 expose guard nodes, config options/names.
12105 - Add a "quit" command (when when using the controller manually).
12106 - Add a new signal "newnym" to "change pseudonyms" -- that is, to
12107 stop using any currently-dirty circuits for new streams, so we
12108 don't link new actions to old actions. This also occurs on HUP
12109 or "signal reload".
12110 - If we would close a stream early (e.g. it asks for a .exit that
12111 we know would refuse it) but the LeaveStreamsUnattached config
12112 option is set by the controller, then don't close it.
12113 - Add a new controller event type "authdir_newdescs" that allows
12114 controllers to get all server descriptors that were uploaded to
12115 a router in its role as directory authority.
12116 - New controller option "getinfo desc/all-recent" to fetch the
12117 latest server descriptor for every router that Tor knows about.
12118 - Fix the controller's "attachstream 0" command to treat conn like
12119 it just connected, doing address remapping, handling .exit and
12120 .onion idioms, and so on. Now we're more uniform in making sure
12121 that the controller hears about new and closing connections.
12122 - Permit transitioning from ORPort==0 to ORPort!=0, and back, from
12123 the controller. Also, rotate dns and cpu workers if the controller
12124 changes options that will affect them; and initialize the dns
12125 worker cache tree whether or not we start out as a server.
12126 - Add a new circuit purpose 'controller' to let the controller ask
12127 for a circuit that Tor won't try to use. Extend the "extendcircuit"
12128 controller command to let you specify the purpose if you're starting
12129 a new circuit. Add a new "setcircuitpurpose" controller command to
12130 let you change a circuit's purpose after it's been created.
12131 - Let the controller ask for "getinfo dir/server/foo" so it can ask
12132 directly rather than connecting to the dir port. "getinfo
12133 dir/status/foo" also works, but currently only if your DirPort
12135 - Let the controller tell us about certain router descriptors
12136 that it doesn't want Tor to use in circuits. Implement
12137 "setrouterpurpose" and modify "+postdescriptor" to do this.
12138 - If the controller's *setconf commands fail, collect an error
12139 message in a string and hand it back to the controller -- don't
12140 just tell them to go read their logs.
12142 o Scalability, resource management, and performance:
12143 - Fix a major load balance bug: we were round-robin reading in 16 KB
12144 chunks, and servers with bandwidthrate of 20 KB, while downloading
12145 a 600 KB directory, would starve their other connections. Now we
12146 try to be a bit more fair.
12147 - Be more conservative about whether to advertise our DirPort.
12148 The main change is to not advertise if we're running at capacity
12149 and either a) we could hibernate ever or b) our capacity is low
12150 and we're using a default DirPort.
12151 - We weren't cannibalizing circuits correctly for
12152 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
12153 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
12154 build those from scratch. This should make hidden services faster.
12155 - Predict required circuits better, with an eye toward making hidden
12156 services faster on the service end.
12157 - Compress exit policies even more: look for duplicate lines and
12159 - Generate 18.0.0.0/8 address policy format in descs when we can;
12160 warn when the mask is not reducible to a bit-prefix.
12161 - There used to be two ways to specify your listening ports in a
12162 server descriptor: on the "router" line and with a separate "ports"
12163 line. Remove support for the "ports" line.
12164 - Reduce memory requirements in our structs by changing the order
12165 of fields. Replace balanced trees with hash tables. Inline
12166 bottleneck smartlist functions. Add a "Map from digest to void*"
12167 abstraction so we can do less hex encoding/decoding, and use it
12168 in router_get_by_digest(). Many other CPU and memory improvements.
12169 - Allow tor_gzip_uncompress to extract as much as possible from
12170 truncated compressed data. Try to extract as many
12171 descriptors as possible from truncated http responses (when
12172 purpose is DIR_PURPOSE_FETCH_ROUTERDESC).
12173 - Make circ->onionskin a pointer, not a static array. moria2 was using
12174 125000 circuit_t's after it had been up for a few weeks, which
12175 translates to 20+ megs of wasted space.
12176 - The private half of our EDH handshake keys are now chosen out
12177 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
12178 - Stop doing the complex voodoo overkill checking for insecure
12179 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
12180 - Do round-robin writes for TLS of at most 16 kB per write. This
12181 might be more fair on loaded Tor servers.
12182 - Do not use unaligned memory access on alpha, mips, or mipsel.
12183 It *works*, but is very slow, so we treat them as if it doesn't.
12185 o Other bugfixes and improvements:
12186 - Start storing useful information to $DATADIR/state, so we can
12187 remember things across invocations of Tor. Retain unrecognized
12188 lines so we can be forward-compatible, and write a TorVersion line
12189 so we can be backward-compatible.
12190 - If ORPort is set, Address is not explicitly set, and our hostname
12191 resolves to a private IP address, try to use an interface address
12192 if it has a public address. Now Windows machines that think of
12193 themselves as localhost can guess their address.
12194 - Regenerate our local descriptor if it's dirty and we try to use
12195 it locally (e.g. if it changes during reachability detection).
12196 This was causing some Tor servers to keep publishing the same
12197 initial descriptor forever.
12198 - Tor servers with dynamic IP addresses were needing to wait 18
12199 hours before they could start doing reachability testing using
12200 the new IP address and ports. This is because they were using
12201 the internal descriptor to learn what to test, yet they were only
12202 rebuilding the descriptor once they decided they were reachable.
12203 - It turns out we couldn't bootstrap a network since we added
12204 reachability detection in 0.1.0.1-rc. Good thing the Tor network
12205 has never gone down. Add an AssumeReachable config option to let
12206 servers and authorities bootstrap. When we're trying to build a
12207 high-uptime or high-bandwidth circuit but there aren't enough
12208 suitable servers, try being less picky rather than simply failing.
12209 - Newly bootstrapped Tor networks couldn't establish hidden service
12210 circuits until they had nodes with high uptime. Be more tolerant.
12211 - Really busy servers were keeping enough circuits open on stable
12212 connections that they were wrapping around the circuit_id
12213 space. (It's only two bytes.) This exposed a bug where we would
12214 feel free to reuse a circuit_id even if it still exists but has
12215 been marked for close. Try to fix this bug. Some bug remains.
12216 - When we fail to bind or listen on an incoming or outgoing
12217 socket, we now close it before refusing, rather than just
12218 leaking it. (Thanks to Peter Palfrader for finding.)
12219 - Fix a file descriptor leak in start_daemon().
12220 - On Windows, you can't always reopen a port right after you've
12221 closed it. So change retry_listeners() to only close and re-open
12222 ports that have changed.
12223 - Workaround a problem with some http proxies that refuse GET
12224 requests that specify "Content-Length: 0". Reported by Adrian.
12225 - Recover better from TCP connections to Tor servers that are
12226 broken but don't tell you (it happens!); and rotate TLS
12227 connections once a week.
12228 - Fix a scary-looking but apparently harmless bug where circuits
12229 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
12230 servers, and never switch to state CIRCUIT_STATE_OPEN.
12231 - Check for even more Windows version flags when writing the platform
12232 string in server descriptors, and note any we don't recognize.
12233 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
12234 get a better idea of why their circuits failed. Not used yet.
12235 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
12236 We don't use them yet, but maybe one day our DNS resolver will be
12237 able to discover them.
12238 - Let people type "tor --install" as well as "tor -install" when they
12239 want to make it an NT service.
12240 - Looks like we were never delivering deflated (i.e. compressed)
12241 running-routers lists, even when asked. Oops.
12242 - We were leaking some memory every time the client changed IPs.
12243 - Clean up more of the OpenSSL memory when exiting, so we can detect
12244 memory leaks better.
12245 - Never call free() on tor_malloc()d memory. This will help us
12246 use dmalloc to detect memory leaks.
12247 - Some Tor servers process billions of cells per day. These
12248 statistics are now uint64_t's.
12249 - Check [X-]Forwarded-For headers in HTTP requests when generating
12250 log messages. This lets people run dirservers (and caches) behind
12251 Apache but still know which IP addresses are causing warnings.
12252 - Fix minor integer overflow in calculating when we expect to use up
12253 our bandwidth allocation before hibernating.
12254 - Lower the minimum required number of file descriptors to 1000,
12255 so we can have some overhead for Valgrind on Linux, where the
12256 default ulimit -n is 1024.
12257 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
12258 and its existence is confusing some users.
12260 o Config option fixes:
12261 - Add a new config option ExitPolicyRejectPrivate which defaults
12262 to on. Now all exit policies will begin with rejecting private
12263 addresses, unless the server operator explicitly turns it off.
12264 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB.
12265 - Add new ReachableORAddresses and ReachableDirAddresses options
12266 that understand address policies. FascistFirewall is now a synonym
12267 for "ReachableORAddresses *:443", "ReachableDirAddresses *:80".
12268 - Start calling it FooListenAddress rather than FooBindAddress,
12269 since few of our users know what it means to bind an address
12271 - If the user gave Tor an odd number of command-line arguments,
12272 we were silently ignoring the last one. Now we complain and fail.
12273 This wins the oldest-bug prize -- this bug has been present since
12274 November 2002, as released in Tor 0.0.0.
12275 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
12276 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
12277 it would silently ignore the 6668.
12278 - If we get a linelist or linelist_s config option from the torrc,
12279 e.g. ExitPolicy, and it has no value, warn and skip rather than
12280 silently resetting it to its default.
12281 - Setconf was appending items to linelists, not clearing them.
12282 - Add MyFamily to torrc.sample in the server section, so operators
12283 will be more likely to learn that it exists.
12284 - Make ContactInfo mandatory for authoritative directory servers.
12285 - MaxConn has been obsolete for a while now. Document the ConnLimit
12286 config option, which is a *minimum* number of file descriptors
12287 that must be available else Tor refuses to start.
12288 - Get rid of IgnoreVersion undocumented config option, and make us
12289 only warn, never exit, when we're running an obsolete version.
12290 - Make MonthlyAccountingStart config option truly obsolete now.
12291 - Correct the man page entry on TrackHostExitsExpire.
12292 - Let directory authorities start even if they don't specify an
12293 Address config option.
12294 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
12295 reflect the updated flags in our v2 dir protocol.
12297 o Config option features:
12298 - Add a new config option FastFirstHopPK (on by default) so clients
12299 do a trivial crypto handshake for their first hop, since TLS has
12300 already taken care of confidentiality and authentication.
12301 - Let the user set ControlListenAddress in the torrc. This can be
12302 dangerous, but there are some cases (like a secured LAN) where it
12304 - New config options to help controllers: FetchServerDescriptors
12305 and FetchHidServDescriptors for whether to fetch server
12306 info and hidserv info or let the controller do it, and
12307 PublishServerDescriptor and PublishHidServDescriptors.
12308 - Also let the controller set the __AllDirActionsPrivate config
12309 option if you want all directory fetches/publishes to happen via
12310 Tor (it assumes your controller bootstraps your circuits).
12311 - Add "HardwareAccel" config option: support for crypto hardware
12312 accelerators via OpenSSL. Off by default, until we find somebody
12313 smart who can test it for us. (It appears to produce seg faults
12314 in at least some cases.)
12315 - New config option "AuthDirRejectUnlisted" for directory authorities
12316 as a panic button: if we get flooded with unusable servers we can
12317 revert to only listing servers in the approved-routers file.
12318 - Directory authorities can now reject/invalidate by key and IP,
12319 with the config options "AuthDirInvalid" and "AuthDirReject", or
12320 by marking a fingerprint as "!reject" or "!invalid" (as its
12321 nickname) in the approved-routers file. This is useful since
12322 currently we automatically list servers as running and usable
12323 even if we know they're jerks.
12324 - Add a new config option TestSocks so people can see whether their
12325 applications are using socks4, socks4a, socks5-with-ip, or
12326 socks5-with-fqdn. This way they don't have to keep mucking
12327 with tcpdump and wondering if something got cached somewhere.
12328 - Add "private:*" as an alias in configuration for policies. Now
12329 you can simplify your exit policy rather than needing to list
12330 every single internal or nonroutable network space.
12331 - Accept "private:*" in routerdesc exit policies; not generated yet
12332 because older Tors do not understand it.
12333 - Add configuration option "V1AuthoritativeDirectory 1" which
12334 moria1, moria2, and tor26 have set.
12335 - Implement an option, VirtualAddrMask, to set which addresses
12336 get handed out in response to mapaddress requests. This works
12337 around a bug in tsocks where 127.0.0.0/8 is never socksified.
12338 - Add a new config option FetchUselessDescriptors, off by default,
12339 for when you plan to run "exitlist" on your client and you want
12340 to know about even the non-running descriptors.
12341 - SocksTimeout: How long do we let a socks connection wait
12342 unattached before we fail it?
12343 - CircuitBuildTimeout: Cull non-open circuits that were born
12344 at least this many seconds ago.
12345 - CircuitIdleTimeout: Cull open clean circuits that were born
12346 at least this many seconds ago.
12347 - New config option SafeSocks to reject all application connections
12348 using unsafe socks protocols. Defaults to off.
12350 o Improved and clearer log messages:
12351 - Reduce clutter in server logs. We're going to try to make
12352 them actually usable now. New config option ProtocolWarnings that
12353 lets you hear about how _other Tors_ are breaking the protocol. Off
12355 - Divide log messages into logging domains. Once we put some sort
12356 of interface on this, it will let people looking at more verbose
12357 log levels specify the topics they want to hear more about.
12358 - Log server fingerprint on startup, so new server operators don't
12359 have to go hunting around their filesystem for it.
12360 - Provide dire warnings to any users who set DirServer manually;
12361 move it out of torrc.sample and into torrc.complete.
12362 - Make the log message less scary when all the dirservers are
12363 temporarily unreachable.
12364 - When tor_socketpair() fails in Windows, give a reasonable
12365 Windows-style errno back.
12366 - Improve tor_gettimeofday() granularity on windows.
12367 - We were printing the number of idle dns workers incorrectly when
12369 - Handle duplicate lines in approved-routers files without warning.
12370 - We were whining about using socks4 or socks5-with-local-lookup
12371 even when it's an IP address in the "virtual" range we designed
12372 exactly for this case.
12373 - Check for named servers when looking them up by nickname;
12374 warn when we're calling a non-named server by its nickname;
12375 don't warn twice about the same name.
12376 - Downgrade the dirserver log messages when whining about
12378 - Correct "your server is reachable" log entries to indicate that
12379 it was self-testing that told us so.
12380 - If we're trying to be a Tor server and running Windows 95/98/ME
12381 as a server, explain that we'll likely crash.
12382 - Provide a more useful warn message when our onion queue gets full:
12383 the CPU is too slow or the exit policy is too liberal.
12384 - Don't warn when we receive a 503 from a dirserver/cache -- this
12385 will pave the way for them being able to refuse if they're busy.
12386 - When we fail to bind a listener, try to provide a more useful
12387 log message: e.g., "Is Tor already running?"
12388 - Only start testing reachability once we've established a
12389 circuit. This will make startup on dir authorities less noisy.
12390 - Don't try to upload hidden service descriptors until we have
12391 established a circuit.
12392 - Tor didn't warn when it failed to open a log file.
12393 - Warn when listening on a public address for socks. We suspect a
12394 lot of people are setting themselves up as open socks proxies,
12395 and they have no idea that jerks on the Internet are using them,
12396 since they simply proxy the traffic into the Tor network.
12397 - Give a useful message when people run Tor as the wrong user,
12398 rather than telling them to start chowning random directories.
12399 - Fix a harmless bug that was causing Tor servers to log
12400 "Got an end because of misc error, but we're not an AP. Closing."
12401 - Fix wrong log message when you add a "HiddenServiceNodes" config
12402 line without any HiddenServiceDir line (reported by Chris Thomas).
12403 - Directory authorities now stop whining so loudly about bad
12404 descriptors that they fetch from other dirservers. So when there's
12405 a log complaint, it's for sure from a freshly uploaded descriptor.
12406 - When logging via syslog, include the pid whenever we provide
12407 a log entry. Suggested by Todd Fries.
12408 - When we're shutting down and we do something like try to post a
12409 server descriptor or rendezvous descriptor, don't complain that
12410 we seem to be unreachable. Of course we are, we're shutting down.
12411 - Change log line for unreachability to explicitly suggest /etc/hosts
12412 as the culprit. Also make it clearer what IP address and ports we're
12413 testing for reachability.
12414 - Put quotes around user-supplied strings when logging so users are
12415 more likely to realize if they add bad characters (like quotes)
12417 - NT service patch from Matt Edman to improve error messages on Win32.
12420 Changes in version 0.1.0.17 - 2006-02-17
12421 o Crash bugfixes on 0.1.0.x:
12422 - When servers with a non-zero DirPort came out of hibernation,
12423 sometimes they would trigger an assert.
12425 o Other important bugfixes:
12426 - On platforms that don't have getrlimit (like Windows), we were
12427 artificially constraining ourselves to a max of 1024
12428 connections. Now just assume that we can handle as many as 15000
12429 connections. Hopefully this won't cause other problems.
12431 o Backported features:
12432 - When we're a server, a client asks for an old-style directory,
12433 and our write bucket is empty, don't give it to him. This way
12434 small servers can continue to serve the directory *sometimes*,
12435 without getting overloaded.
12436 - Whenever you get a 503 in response to a directory fetch, try
12437 once more. This will become important once servers start sending
12438 503's whenever they feel busy.
12439 - Fetch a new directory every 120 minutes, not every 40 minutes.
12440 Now that we have hundreds of thousands of users running the old
12441 directory algorithm, it's starting to hurt a lot.
12442 - Bump up the period for forcing a hidden service descriptor upload
12443 from 20 minutes to 1 hour.
12446 Changes in version 0.1.0.16 - 2006-01-02
12447 o Crash bugfixes on 0.1.0.x:
12448 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
12449 corrupting the heap, losing FDs, or crashing when we need to resize
12450 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
12451 - It turns out sparc64 platforms crash on unaligned memory access
12452 too -- so detect and avoid this.
12453 - Handle truncated compressed data correctly (by detecting it and
12455 - Fix possible-but-unlikely free(NULL) in control.c.
12456 - When we were closing connections, there was a rare case that
12457 stomped on memory, triggering seg faults and asserts.
12458 - Avoid potential infinite recursion when building a descriptor. (We
12459 don't know that it ever happened, but better to fix it anyway.)
12460 - We were neglecting to unlink marked circuits from soon-to-close OR
12461 connections, which caused some rare scribbling on freed memory.
12462 - Fix a memory stomping race bug when closing the joining point of two
12463 rendezvous circuits.
12464 - Fix an assert in time parsing found by Steven Murdoch.
12466 o Other bugfixes on 0.1.0.x:
12467 - When we're doing reachability testing, provide more useful log
12468 messages so the operator knows what to expect.
12469 - Do not check whether DirPort is reachable when we are suppressing
12470 advertising it because of hibernation.
12471 - When building with -static or on Solaris, we sometimes needed -ldl.
12472 - One of the dirservers (tor26) changed its IP address.
12473 - When we're deciding whether a stream has enough circuits around
12474 that can handle it, count the freshly dirty ones and not the ones
12475 that are so dirty they won't be able to handle it.
12476 - When we're expiring old circuits, we had a logic error that caused
12477 us to close new rendezvous circuits rather than old ones.
12478 - Give a more helpful log message when you try to change ORPort via
12479 the controller: you should upgrade Tor if you want that to work.
12480 - We were failing to parse Tor versions that start with "Tor ".
12481 - Tolerate faulty streams better: when a stream fails for reason
12482 exitpolicy, stop assuming that the router is lying about his exit
12483 policy. When a stream fails for reason misc, allow it to retry just
12484 as if it was resolvefailed. When a stream has failed three times,
12485 reset its failure count so we can try again and get all three tries.
12488 Changes in version 0.1.0.15 - 2005-09-23
12489 o Bugfixes on 0.1.0.x:
12490 - Reject ports 465 and 587 (spam targets) in default exit policy.
12491 - Don't crash when we don't have any spare file descriptors and we
12492 try to spawn a dns or cpu worker.
12493 - Get rid of IgnoreVersion undocumented config option, and make us
12494 only warn, never exit, when we're running an obsolete version.
12495 - Don't try to print a null string when your server finds itself to
12496 be unreachable and the Address config option is empty.
12497 - Make the numbers in read-history and write-history into uint64s,
12498 so they don't overflow and publish negatives in the descriptor.
12499 - Fix a minor memory leak in smartlist_string_remove().
12500 - We were only allowing ourselves to upload a server descriptor at
12501 most every 20 minutes, even if it changed earlier than that.
12502 - Clean up log entries that pointed to old URLs.
12505 Changes in version 0.1.0.14 - 2005-08-08
12506 o Bugfixes on 0.1.0.x:
12507 - Fix the other half of the bug with crypto handshakes
12509 - Fix an assert trigger if you send a 'signal term' via the
12510 controller when it's listening for 'event info' messages.
12513 Changes in version 0.1.0.13 - 2005-08-04
12514 o Bugfixes on 0.1.0.x:
12515 - Fix a critical bug in the security of our crypto handshakes.
12516 - Fix a size_t underflow in smartlist_join_strings2() that made
12517 it do bad things when you hand it an empty smartlist.
12518 - Fix Windows installer to ship Tor license (thanks to Aphex for
12519 pointing out this oversight) and put a link to the doc directory
12521 - Explicitly set no-unaligned-access for sparc: it turns out the
12522 new gcc's let you compile broken code, but that doesn't make it
12526 Changes in version 0.1.0.12 - 2005-07-18
12527 o New directory servers:
12528 - tor26 has changed IP address.
12530 o Bugfixes on 0.1.0.x:
12531 - Fix a possible double-free in tor_gzip_uncompress().
12532 - When --disable-threads is set, do not search for or link against
12533 pthreads libraries.
12534 - Don't trigger an assert if an authoritative directory server
12535 claims its dirport is 0.
12536 - Fix bug with removing Tor as an NT service: some people were
12537 getting "The service did not return an error." Thanks to Matt
12541 Changes in version 0.1.0.11 - 2005-06-30
12542 o Bugfixes on 0.1.0.x:
12543 - Fix major security bug: servers were disregarding their
12544 exit policies if clients behaved unexpectedly.
12545 - Make OS X init script check for missing argument, so we don't
12546 confuse users who invoke it incorrectly.
12547 - Fix a seg fault in "tor --hash-password foo".
12548 - The MAPADDRESS control command was broken.
12551 Changes in version 0.1.0.10 - 2005-06-14
12553 - Make NT services work and start on startup on Win32 (based on
12554 patch by Matt Edman). See the FAQ entry for details.
12555 - Make 'platform' string in descriptor more accurate for Win32
12556 servers, so it's not just "unknown platform".
12557 - REUSEADDR on normal platforms means you can rebind to the port
12558 right after somebody else has let it go. But REUSEADDR on Win32
12559 means you can bind to the port _even when somebody else already
12560 has it bound_! So, don't do that on Win32.
12561 - Clean up the log messages when starting on Win32 with no config
12563 - Allow seeding the RNG on Win32 even when you're not running as
12564 Administrator. If seeding the RNG on Win32 fails, quit.
12566 o Assert / crash bugs:
12567 - Refuse relay cells that claim to have a length larger than the
12568 maximum allowed. This prevents a potential attack that could read
12569 arbitrary memory (e.g. keys) from an exit server's process
12571 - If unofficial Tor clients connect and send weird TLS certs, our
12572 Tor server triggers an assert. Stop asserting, and start handling
12573 TLS errors better in other situations too.
12574 - Fix a race condition that can trigger an assert when we have a
12575 pending create cell and an OR connection attempt fails.
12578 - Use pthreads for worker processes rather than forking. This was
12579 forced because when we forked, we ended up wasting a lot of
12580 duplicate ram over time.
12581 - Also switch to foo_r versions of some library calls to allow
12582 reentry and threadsafeness.
12583 - Implement --disable-threads configure option. Disable threads on
12584 netbsd and openbsd by default, because they have no reentrant
12585 resolver functions (!), and on solaris since it has other
12587 - Fix possible bug on threading platforms (e.g. win32) which was
12588 leaking a file descriptor whenever a cpuworker or dnsworker died.
12589 - Fix a minor memory leak when somebody establishes an introduction
12590 point at your Tor server.
12591 - Fix possible memory leak in tor_lookup_hostname(). (Thanks to
12593 - Add ./configure --with-dmalloc option, to track memory leaks.
12594 - And try to free all memory on closing, so we can detect what
12597 o Protocol correctness:
12598 - When we've connected to an OR and handshaked but didn't like
12599 the result, we were closing the conn without sending destroy
12600 cells back for pending circuits. Now send those destroys.
12601 - Start sending 'truncated' cells back rather than destroy cells
12602 if the circuit closes in front of you. This means we won't have
12603 to abandon partially built circuits.
12604 - Handle changed router status correctly when dirserver reloads
12605 fingerprint file. We used to be dropping all unverified descriptors
12606 right then. The bug was hidden because we would immediately
12607 fetch a directory from another dirserver, which would include the
12608 descriptors we just dropped.
12609 - Revise tor-spec to add more/better stream end reasons.
12610 - Revise all calls to connection_edge_end to avoid sending 'misc',
12611 and to take errno into account where possible.
12612 - Client now retries when streams end early for 'hibernating' or
12613 'resource limit' reasons, rather than failing them.
12614 - Try to be more zealous about calling connection_edge_end when
12615 things go bad with edge conns in connection.c.
12617 o Robustness improvements:
12618 - Better handling for heterogeneous / unreliable nodes:
12619 - Annotate circuits with whether they aim to contain high uptime
12620 nodes and/or high capacity nodes. When building circuits, choose
12622 - This means that every single node in an intro rend circuit,
12623 not just the last one, will have a minimum uptime.
12624 - New config option LongLivedPorts to indicate application streams
12625 that will want high uptime circuits.
12626 - Servers reset uptime when a dir fetch entirely fails. This
12627 hopefully reflects stability of the server's network connectivity.
12628 - If somebody starts his tor server in Jan 2004 and then fixes his
12629 clock, don't make his published uptime be a year.
12630 - Reset published uptime when we wake up from hibernation.
12631 - Introduce a notion of 'internal' circs, which are chosen without
12632 regard to the exit policy of the last hop. Intro and rendezvous
12633 circs must be internal circs, to avoid leaking information. Resolve
12634 and connect streams can use internal circs if they want.
12635 - New circuit pooling algorithm: keep track of what destination ports
12636 we've used recently (start out assuming we'll want to use 80), and
12637 make sure to have enough circs around to satisfy these ports. Also
12638 make sure to have 2 internal circs around if we've required internal
12639 circs lately (and with high uptime if we've seen that lately too).
12640 - Turn addr_policy_compare from a tristate to a quadstate; this should
12641 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
12642 for google.com" problem.
12643 - When a client asks us for a dir mirror and we don't have one,
12644 launch an attempt to get a fresh one.
12645 - First cut at support for "create-fast" cells. Clients can use
12646 these when extending to their first hop, since the TLS already
12647 provides forward secrecy and authentication. Not enabled on
12650 o Reachability testing.
12651 - Your Tor server will automatically try to see if its ORPort and
12652 DirPort are reachable from the outside, and it won't upload its
12653 descriptor until it decides at least ORPort is reachable (when
12654 DirPort is not yet found reachable, publish it as zero).
12655 - When building testing circs for ORPort testing, use only
12656 high-bandwidth nodes, so fewer circuits fail.
12657 - Notice when our IP changes, and reset stats/uptime/reachability.
12658 - Authdirservers don't do ORPort reachability detection, since
12659 they're in clique mode, so it will be rare to find a server not
12660 already connected to them.
12661 - Authdirservers now automatically approve nodes running 0.1.0.2-rc
12665 - Now we allow two unverified servers with the same nickname
12666 but different keys. But if a nickname is verified, only that
12667 nickname+key are allowed.
12668 - If you're an authdirserver connecting to an address:port,
12669 and it's not the OR you were expecting, forget about that
12670 descriptor. If he *was* the one you were expecting, then forget
12671 about all other descriptors for that address:port.
12672 - Allow servers to publish descriptors from 12 hours in the future.
12673 Corollary: only whine about clock skew from the dirserver if
12674 he's a trusted dirserver (since now even verified servers could
12675 have quite wrong clocks).
12676 - Require servers that use the default dirservers to have public IP
12677 addresses. We have too many servers that are configured with private
12678 IPs and their admins never notice the log entries complaining that
12679 their descriptors are being rejected.
12681 o Efficiency improvements:
12682 - Use libevent. Now we can use faster async cores (like epoll, kpoll,
12683 and /dev/poll), and hopefully work better on Windows too.
12684 - Apple's OS X 10.4.0 ships with a broken kqueue API, and using
12685 kqueue on 10.3.9 causes kernel panics. Don't use kqueue on OS X.
12686 - Find libevent even if it's hiding in /usr/local/ and your
12687 CFLAGS and LDFLAGS don't tell you to look there.
12688 - Be able to link with libevent as a shared library (the default
12689 after 1.0d), even if it's hiding in /usr/local/lib and even
12690 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
12691 assuming you're running gcc. Otherwise fail and give a useful
12693 - Switch to a new buffer management algorithm, which tries to avoid
12694 reallocing and copying quite as much. In first tests it looks like
12695 it uses *more* memory on average, but less cpu.
12696 - Switch our internal buffers implementation to use a ring buffer,
12697 to hopefully improve performance for fast servers a lot.
12698 - Reenable the part of the code that tries to flush as soon as an
12699 OR outbuf has a full TLS record available. Perhaps this will make
12700 OR outbufs not grow as huge except in rare cases, thus saving lots
12701 of CPU time plus memory.
12702 - Improve performance for dirservers: stop re-parsing the whole
12703 directory every time you regenerate it.
12704 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
12705 it much faster to look up a circuit for each relay cell.
12706 - Remove most calls to assert_all_pending_dns_resolves_ok(),
12707 since they're eating our cpu on exit nodes.
12708 - Stop wasting time doing a case insensitive comparison for every
12709 dns name every time we do any lookup. Canonicalize the names to
12710 lowercase when you first see them.
12713 - Handle unavailable hidden services better. Handle slow or busy
12714 hidden services better.
12715 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
12716 circ as necessary, if there are any completed ones lying around
12717 when we try to launch one.
12718 - Make hidden services try to establish a rendezvous for 30 seconds
12719 after fetching the descriptor, rather than for n (where n=3)
12720 attempts to build a circuit.
12721 - Adjust maximum skew and age for rendezvous descriptors: let skew
12722 be 48 hours rather than 90 minutes.
12723 - Reject malformed .onion addresses rather then passing them on as
12724 normal web requests.
12727 - More Tor controller support. See
12728 http://tor.eff.org/doc/control-spec.txt for all the new features,
12729 including signals to emulate unix signals from any platform;
12730 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
12731 closestream; closecircuit; etc.
12732 - Encode hashed controller passwords in hex instead of base64,
12733 to make it easier to write controllers.
12734 - Revise control spec and implementation to allow all log messages to
12735 be sent to controller with their severities intact (suggested by
12736 Matt Edman). Disable debug-level logs while delivering a debug-level
12737 log to the controller, to prevent loop. Update TorControl to handle
12738 new log event types.
12740 o New config options/defaults:
12741 - Begin scrubbing sensitive strings from logs by default. Turn off
12742 the config option SafeLogging if you need to do debugging.
12743 - New exit policy: accept most low-numbered ports, rather than
12744 rejecting most low-numbered ports.
12745 - Put a note in the torrc about abuse potential with the default
12747 - Add support for CONNECTing through https proxies, with "HttpsProxy"
12749 - Add HttpProxyAuthenticator and HttpsProxyAuthenticator support
12750 based on patch from Adam Langley (basic auth only).
12751 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
12752 the fast servers that have been joining lately. (Clients are now
12753 willing to load balance over up to 2 MB of advertised bandwidth
12755 - New config option MaxAdvertisedBandwidth which lets you advertise
12756 a low bandwidthrate (to not attract as many circuits) while still
12757 allowing a higher bandwidthrate in reality.
12758 - Require BandwidthRate to be at least 20kB/s for servers.
12759 - Add a NoPublish config option, so you can be a server (e.g. for
12760 testing running Tor servers in other Tor networks) without
12761 publishing your descriptor to the primary dirservers.
12762 - Add a new AddressMap config directive to rewrite incoming socks
12763 addresses. This lets you, for example, declare an implicit
12764 required exit node for certain sites.
12765 - Add a new TrackHostExits config directive to trigger addressmaps
12766 for certain incoming socks addresses -- for sites that break when
12767 your exit keeps changing (based on patch from Mike Perry).
12768 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
12769 which describes how often we retry making new circuits if current
12770 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
12771 how long we're willing to make use of an already-dirty circuit.
12772 - Change compiled-in SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to
12773 a config option "ShutdownWaitLength" (when using kill -INT on
12775 - Fix an edge case in parsing config options: if they say "--"
12776 on the commandline, it's not a config option (thanks weasel).
12777 - New config option DirAllowPrivateAddresses for authdirservers.
12778 Now by default they refuse router descriptors that have non-IP or
12779 private-IP addresses.
12780 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
12781 smart" default value: low for servers and high for clients.
12782 - Some people were putting "Address " in their torrc, and they had
12783 a buggy resolver that resolved " " to 0.0.0.0. Oops.
12784 - If DataDir is ~/.tor, and that expands to /.tor, then default to
12785 LOCALSTATEDIR/tor instead.
12786 - Implement --verify-config command-line option to check if your torrc
12787 is valid without actually launching Tor.
12789 o Logging improvements:
12790 - When dirservers refuse a server descriptor, we now log its
12791 contactinfo, platform, and the poster's IP address.
12792 - Only warn once per nickname from add_nickname_list_to_smartlist()
12793 per failure, so an entrynode or exitnode choice that's down won't
12795 - When we're connecting to an OR and he's got a different nickname/key
12796 than we were expecting, only complain loudly if we're an OP or a
12797 dirserver. Complaining loudly to the OR admins just confuses them.
12798 - Whine at you if you're a server and you don't set your contactinfo.
12799 - Warn when exit policy implicitly allows local addresses.
12800 - Give a better warning when some other server advertises an
12801 ORPort that is actually an apache running ssl.
12802 - If we get an incredibly skewed timestamp from a dirserver mirror
12803 that isn't a verified OR, don't warn -- it's probably him that's
12805 - When a dirserver causes you to give a warn, mention which dirserver
12807 - Initialize libevent later in the startup process, so the logs are
12808 already established by the time we start logging libevent warns.
12809 - Use correct errno on win32 if libevent fails.
12810 - Check and warn about known-bad/slow libevent versions.
12811 - Stop warning about sigpipes in the logs. We're going to
12812 pretend that getting these occassionally is normal and fine.
12814 o New contrib scripts:
12815 - New experimental script tor/contrib/exitlist: a simple python
12816 script to parse directories and find Tor nodes that exit to listed
12818 - New experimental script tor/contrib/ExerciseServer.py (needs more
12819 work) that uses the controller interface to build circuits and
12820 fetch pages over them. This will help us bootstrap servers that
12821 have lots of capacity but haven't noticed it yet.
12822 - New experimental script tor/contrib/PathDemo.py (needs more work)
12823 that uses the controller interface to let you choose whole paths
12825 "<hostname>.<path,separated by dots>.<length of path>.path"
12826 - New contributed script "privoxy-tor-toggle" to toggle whether
12827 Privoxy uses Tor. Seems to be configured for Debian by default.
12828 - Have torctl.in/tor.sh.in check for location of su binary (needed
12832 - chdir() to your datadirectory at the *end* of the daemonize process,
12833 not the beginning. This was a problem because the first time you
12834 run tor, if your datadir isn't there, and you have runasdaemon set
12835 to 1, it will try to chdir to it before it tries to create it. Oops.
12836 - Fix several double-mark-for-close bugs, e.g. where we were finding
12837 a conn for a cell even if that conn is already marked for close.
12838 - Stop most cases of hanging up on a socks connection without sending
12840 - Fix a bug in the RPM package: set home directory for _tor to
12841 something more reasonable when first installing.
12842 - Stop putting nodename in the Platform string in server descriptors.
12843 It doesn't actually help, and it is confusing/upsetting some people.
12844 - When using preferred entry or exit nodes, ignore whether the
12845 circuit wants uptime or capacity. They asked for the nodes, they
12847 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
12848 artificially capped at 500kB.
12849 - Cache local dns resolves correctly even when they're .exit
12851 - If we're hibernating and we get a SIGINT, exit immediately.
12852 - tor-resolve requests were ignoring .exit if there was a working circuit
12853 they could use instead.
12854 - Pay more attention to the ClientOnly config option.
12855 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in certain
12856 installer screens; and don't put stuff into StartupItems unless
12857 the user asks you to.
12860 - Rewrite address "serifos.exit" to "externalIP.serifos.exit"
12861 rather than just rejecting it.
12862 - If our clock jumps forward by 100 seconds or more, assume something
12863 has gone wrong with our network and abandon all not-yet-used circs.
12864 - When an application is using socks5, give him the whole variety of
12865 potential socks5 responses (connect refused, host unreachable, etc),
12866 rather than just "success" or "failure".
12867 - A more sane version numbering system. See
12868 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
12869 - Change version parsing logic: a version is "obsolete" if it is not
12870 recommended and (1) there is a newer recommended version in the
12871 same series, or (2) there are no recommended versions in the same
12872 series, but there are some recommended versions in a newer series.
12873 A version is "new" if it is newer than any recommended version in
12875 - Report HTTP reasons to client when getting a response from directory
12876 servers -- so you can actually know what went wrong.
12877 - Reject odd-looking addresses at the client (e.g. addresses that
12878 contain a colon), rather than having the server drop them because
12880 - Stop publishing socksport in the directory, since it's not
12881 actually meant to be public. For compatibility, publish a 0 there
12883 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
12884 cookies to disk and doesn't log each web request to disk. (Thanks
12885 to Brett Carrington for pointing this out.)
12886 - Add OSX uninstall instructions. An actual uninstall script will
12888 - Add "opt hibernating 1" to server descriptor to make it clearer
12889 whether the server is hibernating.
12892 Changes in version 0.0.9.10 - 2005-06-16
12893 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
12894 - Refuse relay cells that claim to have a length larger than the
12895 maximum allowed. This prevents a potential attack that could read
12896 arbitrary memory (e.g. keys) from an exit server's process
12900 Changes in version 0.0.9.9 - 2005-04-23
12901 o Bugfixes on 0.0.9.x:
12902 - If unofficial Tor clients connect and send weird TLS certs, our
12903 Tor server triggers an assert. This release contains a minimal
12904 backport from the broader fix that we put into 0.1.0.4-rc.
12907 Changes in version 0.0.9.8 - 2005-04-07
12908 o Bugfixes on 0.0.9.x:
12909 - We have a bug that I haven't found yet. Sometimes, very rarely,
12910 cpuworkers get stuck in the 'busy' state, even though the cpuworker
12911 thinks of itself as idle. This meant that no new circuits ever got
12912 established. Here's a workaround to kill any cpuworker that's been
12913 busy for more than 100 seconds.
12916 Changes in version 0.0.9.7 - 2005-04-01
12917 o Bugfixes on 0.0.9.x:
12918 - Fix another race crash bug (thanks to Glenn Fink for reporting).
12919 - Compare identity to identity, not to nickname, when extending to
12920 a router not already in the directory. This was preventing us from
12921 extending to unknown routers. Oops.
12922 - Make sure to create OS X Tor user in <500 range, so we aren't
12923 creating actual system users.
12924 - Note where connection-that-hasn't-sent-end was marked, and fix
12925 a few really loud instances of this harmless bug (it's fixed more
12929 Changes in version 0.0.9.6 - 2005-03-24
12930 o Bugfixes on 0.0.9.x (crashes and asserts):
12931 - Add new end stream reasons to maintainance branch. Fix bug where
12932 reason (8) could trigger an assert. Prevent bug from recurring.
12933 - Apparently win32 stat wants paths to not end with a slash.
12934 - Fix assert triggers in assert_cpath_layer_ok(), where we were
12935 blowing away the circuit that conn->cpath_layer points to, then
12936 checking to see if the circ is well-formed. Backport check to make
12937 sure we dont use the cpath on a closed connection.
12938 - Prevent circuit_resume_edge_reading_helper() from trying to package
12939 inbufs for marked-for-close streams.
12940 - Don't crash on hup if your options->address has become unresolvable.
12941 - Some systems (like OS X) sometimes accept() a connection and tell
12942 you the remote host is 0.0.0.0:0. If this happens, due to some
12943 other mis-features, we get confused; so refuse the conn for now.
12945 o Bugfixes on 0.0.9.x (other):
12946 - Fix harmless but scary "Unrecognized content encoding" warn message.
12947 - Add new stream error reason: TORPROTOCOL reason means "you are not
12948 speaking a version of Tor I understand; say bye-bye to your stream."
12949 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
12950 into the future, now that we are more tolerant of skew. This
12951 resolves a bug where a Tor server would refuse to cache a directory
12952 because all the directories it gets are too far in the future;
12953 yet the Tor server never logs any complaints about clock skew.
12954 - Mac packaging magic: make man pages useable, and do not overwrite
12955 existing torrc files.
12956 - Make OS X log happily to /var/log/tor/tor.log
12959 Changes in version 0.0.9.5 - 2005-02-22
12960 o Bugfixes on 0.0.9.x:
12961 - Fix an assert race at exit nodes when resolve requests fail.
12962 - Stop picking unverified dir mirrors--it only leads to misery.
12963 - Patch from Matt Edman to make NT services work better. Service
12964 support is still not compiled into the executable by default.
12965 - Patch from Dmitri Bely so the Tor service runs better under
12966 the win32 SYSTEM account.
12967 - Make tor-resolve actually work (?) on Win32.
12968 - Fix a sign bug when getrlimit claims to have 4+ billion
12969 file descriptors available.
12970 - Stop refusing to start when bandwidthburst == bandwidthrate.
12971 - When create cells have been on the onion queue more than five
12972 seconds, just send back a destroy and take them off the list.
12975 Changes in version 0.0.9.4 - 2005-02-03
12976 o Bugfixes on 0.0.9:
12977 - Fix an assert bug that took down most of our servers: when
12978 a server claims to have 1 GB of bandwidthburst, don't
12980 - Don't crash as badly if we have spawned the max allowed number
12981 of dnsworkers, or we're out of file descriptors.
12982 - Block more file-sharing ports in the default exit policy.
12983 - MaxConn is now automatically set to the hard limit of max
12984 file descriptors we're allowed (ulimit -n), minus a few for
12986 - Give a clearer message when servers need to raise their
12987 ulimit -n when they start running out of file descriptors.
12988 - SGI Compatibility patches from Jan Schaumann.
12989 - Tolerate a corrupt cached directory better.
12990 - When a dirserver hasn't approved your server, list which one.
12991 - Go into soft hibernation after 95% of the bandwidth is used,
12992 not 99%. This is especially important for daily hibernators who
12993 have a small accounting max. Hopefully it will result in fewer
12994 cut connections when the hard hibernation starts.
12995 - Load-balance better when using servers that claim more than
12996 800kB/s of capacity.
12997 - Make NT services work (experimental, only used if compiled in).
13000 Changes in version 0.0.9.3 - 2005-01-21
13001 o Bugfixes on 0.0.9:
13002 - Backport the cpu use fixes from main branch, so busy servers won't
13003 need as much processor time.
13004 - Work better when we go offline and then come back, or when we
13005 run Tor at boot before the network is up. We do this by
13006 optimistically trying to fetch a new directory whenever an
13007 application request comes in and we think we're offline -- the
13008 human is hopefully a good measure of when the network is back.
13009 - Backport some minimal hidserv bugfixes: keep rend circuits open as
13010 long as you keep using them; actually publish hidserv descriptors
13011 shortly after they change, rather than waiting 20-40 minutes.
13012 - Enable Mac startup script by default.
13013 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
13014 - When you update AllowUnverifiedNodes or FirewallPorts via the
13015 controller's setconf feature, we were always appending, never
13017 - When you update HiddenServiceDir via setconf, it was screwing up
13018 the order of reading the lines, making it fail.
13019 - Do not rewrite a cached directory back to the cache; otherwise we
13020 will think it is recent and not fetch a newer one on startup.
13021 - Workaround for webservers that lie about Content-Encoding: Tor
13022 now tries to autodetect compressed directories and compression
13023 itself. This lets us Proxypass dir fetches through apache.
13026 Changes in version 0.0.9.2 - 2005-01-04
13027 o Bugfixes on 0.0.9 (crashes and asserts):
13028 - Fix an assert on startup when the disk is full and you're logging
13030 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
13031 style address, then we'd crash.
13032 - Fix an assert trigger when the running-routers string we get from
13033 a dirserver is broken.
13034 - Make worker threads start and run on win32. Now win32 servers
13036 - Bandaid (not actually fix, but now it doesn't crash) an assert
13037 where the dns worker dies mysteriously and the main Tor process
13038 doesn't remember anything about the address it was resolving.
13040 o Bugfixes on 0.0.9 (Win32):
13041 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
13042 name out of the warning/assert messages.
13043 - Fix a superficial "unhandled error on read" bug on win32.
13044 - The win32 installer no longer requires a click-through for our
13045 license, since our Free Software license grants rights but does not
13047 - Win32: When connecting to a dirserver fails, try another one
13048 immediately. (This was already working for non-win32 Tors.)
13049 - Stop trying to parse $HOME on win32 when hunting for default
13051 - Make tor-resolve.c work on win32 by calling network_init().
13053 o Bugfixes on 0.0.9 (other):
13054 - Make 0.0.9.x build on Solaris again.
13055 - Due to a fencepost error, we were blowing away the \n when reporting
13056 confvalue items in the controller. So asking for multiple config
13057 values at once couldn't work.
13058 - When listing circuits that are pending on an opening OR connection,
13059 if we're an OR we were listing circuits that *end* at us as
13060 being pending on every listener, dns/cpu worker, etc. Stop that.
13061 - Dirservers were failing to create 'running-routers' or 'directory'
13062 strings if we had more than some threshold of routers. Fix them so
13063 they can handle any number of routers.
13064 - Fix a superficial "Duplicate mark for close" bug.
13065 - Stop checking for clock skew for OR connections, even for servers.
13066 - Fix a fencepost error that was chopping off the last letter of any
13067 nickname that is the maximum allowed nickname length.
13068 - Update URLs in log messages so they point to the new website.
13069 - Fix a potential problem in mangling server private keys while
13070 writing to disk (not triggered yet, as far as we know).
13071 - Include the licenses for other free software we include in Tor,
13072 now that we're shipping binary distributions more regularly.
13075 Changes in version 0.0.9.1 - 2004-12-15
13076 o Bugfixes on 0.0.9:
13077 - Make hibernation actually work.
13078 - Make HashedControlPassword config option work.
13079 - When we're reporting event circuit status to a controller,
13080 don't use the stream status code.
13083 Changes in version 0.0.9 - 2004-12-12
13084 o Bugfixes on 0.0.8.1 (Crashes and asserts):
13085 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
13086 write() call will fail and we handle it there.
13087 - When we run out of disk space, or other log writing error, don't
13088 crash. Just stop logging to that log and continue.
13089 - Fix isspace() and friends so they still make Solaris happy
13090 but also so they don't trigger asserts on win32.
13091 - Fix assert failure on malformed socks4a requests.
13092 - Fix an assert bug where a hidden service provider would fail if
13093 the first hop of his rendezvous circuit was down.
13094 - Better handling of size_t vs int, so we're more robust on 64
13097 o Bugfixes on 0.0.8.1 (Win32):
13098 - Make windows sockets actually non-blocking (oops), and handle
13099 win32 socket errors better.
13100 - Fix parse_iso_time on platforms without strptime (eg win32).
13101 - win32: when being multithreaded, leave parent fdarray open.
13102 - Better handling of winsock includes on non-MSV win32 compilers.
13103 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
13105 - Make unit tests work on win32.
13107 o Bugfixes on 0.0.8.1 (Path selection and streams):
13108 - Calculate timeout for waiting for a connected cell from the time
13109 we sent the begin cell, not from the time the stream started. If
13110 it took a long time to establish the circuit, we would time out
13111 right after sending the begin cell.
13112 - Fix router_compare_addr_to_addr_policy: it was not treating a port
13113 of * as always matching, so we were picking reject *:* nodes as
13114 exit nodes too. Oops.
13115 - When read() failed on a stream, we would close it without sending
13116 back an end. So 'connection refused' would simply be ignored and
13117 the user would get no response.
13118 - Stop a sigpipe: when an 'end' cell races with eof from the app,
13119 we shouldn't hold-open-until-flush if the eof arrived first.
13120 - Let resolve conns retry/expire also, rather than sticking around
13122 - Fix more dns related bugs: send back resolve_failed and end cells
13123 more reliably when the resolve fails, rather than closing the
13124 circuit and then trying to send the cell. Also attach dummy resolve
13125 connections to a circuit *before* calling dns_resolve(), to fix
13126 a bug where cached answers would never be sent in RESOLVED cells.
13128 o Bugfixes on 0.0.8.1 (Circuits):
13129 - Finally fix a bug that's been plaguing us for a year:
13130 With high load, circuit package window was reaching 0. Whenever
13131 we got a circuit-level sendme, we were reading a lot on each
13132 socket, but only writing out a bit. So we would eventually reach
13133 eof. This would be noticed and acted on even when there were still
13134 bytes sitting in the inbuf.
13135 - Use identity comparison, not nickname comparison, to choose which
13136 half of circuit-ID-space each side gets to use. This is needed
13137 because sometimes we think of a router as a nickname, and sometimes
13138 as a hex ID, and we can't predict what the other side will do.
13140 o Bugfixes on 0.0.8.1 (Other):
13141 - Fix a whole slew of memory leaks.
13142 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
13143 - If we are using select, make sure we stay within FD_SETSIZE.
13144 - When poll() is interrupted, we shouldn't believe the revents values.
13145 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
13146 and smartlist_len, which are two major profiling offenders.
13147 - If do_hup fails, actually notice.
13148 - Flush the log file descriptor after we print "Tor opening log file",
13149 so we don't see those messages days later.
13150 - Hidden service operators now correctly handle version 1 style
13151 INTRODUCE1 cells (nobody generates them still, so not a critical
13153 - Handle more errnos from accept() without closing the listener.
13154 Some OpenBSD machines were closing their listeners because
13155 they ran out of file descriptors.
13156 - Some people had wrapped their tor client/server in a script
13157 that would restart it whenever it died. This did not play well
13158 with our "shut down if your version is obsolete" code. Now people
13159 don't fetch a new directory if their local cached version is
13161 - Make our autogen.sh work on ksh as well as bash.
13162 - Better torrc example lines for dirbindaddress and orbindaddress.
13163 - Improved bounds checking on parsed ints (e.g. config options and
13164 the ones we find in directories.)
13165 - Stop using separate defaults for no-config-file and
13166 empty-config-file. Now you have to explicitly turn off SocksPort,
13167 if you don't want it open.
13168 - We were starting to daemonize before we opened our logs, so if
13169 there were any problems opening logs, we would complain to stderr,
13170 which wouldn't work, and then mysteriously exit.
13171 - If a verified OR connects to us before he's uploaded his descriptor,
13172 or we verify him and hup but he still has the original TLS
13173 connection, then conn->nickname is still set like he's unverified.
13175 o Code security improvements, inspired by Ilja:
13176 - tor_snprintf wrapper over snprintf with consistent (though not C99)
13178 - Replace sprintf with tor_snprintf. (I think they were all safe, but
13180 - Replace strcpy/strncpy with strlcpy in more places.
13181 - Avoid strcat; use tor_snprintf or strlcat instead.
13183 o Features (circuits and streams):
13184 - New circuit building strategy: keep a list of ports that we've
13185 used in the past 6 hours, and always try to have 2 circuits open
13186 or on the way that will handle each such port. Seed us with port
13187 80 so web users won't complain that Tor is "slow to start up".
13188 - Make kill -USR1 dump more useful stats about circuits.
13189 - When warning about retrying or giving up, print the address, so
13190 the user knows which one it's talking about.
13191 - If you haven't used a clean circuit in an hour, throw it away,
13192 just to be on the safe side. (This means after 6 hours a totally
13193 unused Tor client will have no circuits open.)
13194 - Support "foo.nickname.exit" addresses, to let Alice request the
13195 address "foo" as viewed by exit node "nickname". Based on a patch
13196 from Geoff Goodell.
13197 - If your requested entry or exit node has advertised bandwidth 0,
13199 - Be more greedy about filling up relay cells -- we try reading again
13200 once we've processed the stuff we read, in case enough has arrived
13201 to fill the last cell completely.
13202 - Refuse application socks connections to port 0.
13203 - Use only 0.0.9pre1 and later servers for resolve cells.
13205 o Features (bandwidth):
13206 - Hibernation: New config option "AccountingMax" lets you
13207 set how many bytes per month (in each direction) you want to
13208 allow your server to consume. Rather than spreading those
13209 bytes out evenly over the month, we instead hibernate for some
13210 of the month and pop up at a deterministic time, work until
13211 the bytes are consumed, then hibernate again. Config option
13212 "MonthlyAccountingStart" lets you specify which day of the month
13213 your billing cycle starts on.
13214 - Implement weekly/monthly/daily accounting: now you specify your
13215 hibernation properties by
13216 AccountingMax N bytes|KB|MB|GB|TB
13217 AccountingStart day|week|month [day] HH:MM
13218 Defaults to "month 1 0:00".
13219 - Let bandwidth and interval config options be specified as 5 bytes,
13220 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
13222 o Features (directories):
13223 - New "router-status" line in directory, to better bind each verified
13224 nickname to its identity key.
13225 - Clients can ask dirservers for /dir.z to get a compressed version
13226 of the directory. Only works for servers running 0.0.9, of course.
13227 - Make clients cache directories and use them to seed their router
13228 lists at startup. This means clients have a datadir again.
13229 - Respond to content-encoding headers by trying to uncompress as
13231 - Clients and servers now fetch running-routers; cache
13232 running-routers; compress running-routers; serve compressed
13234 - Make moria2 advertise a dirport of 80, so people behind firewalls
13235 will be able to get a directory.
13236 - Http proxy support
13237 - Dirservers translate requests for http://%s:%d/x to /x
13238 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
13239 be routed through this host.
13240 - Clients ask for /tor/x rather than /x for new enough dirservers.
13241 This way we can one day coexist peacefully with apache.
13242 - Clients specify a "Host: %s%d" http header, to be compatible
13243 with more proxies, and so running squid on an exit node can work.
13244 - Protect dirservers from overzealous descriptor uploading -- wait
13245 10 seconds after directory gets dirty, before regenerating.
13247 o Features (packages and install):
13248 - Add NSI installer contributed by J Doe.
13249 - Apply NT service patch from Osamu Fujino. Still needs more work.
13250 - Commit VC6 and VC7 workspace/project files.
13251 - Commit a tor.spec for making RPM files, with help from jbash.
13252 - Add contrib/torctl.in contributed by Glenn Fink.
13253 - Make expand_filename handle ~ and ~username.
13254 - Use autoconf to enable largefile support where necessary. Use
13255 ftello where available, since ftell can fail at 2GB.
13256 - Ship src/win32/ in the tarball, so people can use it to build.
13257 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
13260 o Features (ui controller):
13261 - Control interface: a separate program can now talk to your
13262 client/server over a socket, and get/set config options, receive
13263 notifications of circuits and streams starting/finishing/dying,
13264 bandwidth used, etc. The next step is to get some GUIs working.
13265 Let us know if you want to help out. See doc/control-spec.txt .
13266 - Ship a contrib/tor-control.py as an example script to interact
13267 with the control port.
13268 - "tor --hash-password zzyxz" will output a salted password for
13269 use in authenticating to the control interface.
13270 - Implement the control-spec's SAVECONF command, to write your
13271 configuration to torrc.
13272 - Get cookie authentication for the controller closer to working.
13273 - When set_conf changes our server descriptor, upload a new copy.
13274 But don't upload it too often if there are frequent changes.
13276 o Features (config and command-line):
13277 - Deprecate unofficial config option abbreviations, and abbreviations
13278 not on the command line.
13279 - Configuration infrastructure support for warning on obsolete
13281 - Give a slightly more useful output for "tor -h".
13282 - Break DirFetchPostPeriod into:
13283 - DirFetchPeriod for fetching full directory,
13284 - StatusFetchPeriod for fetching running-routers,
13285 - DirPostPeriod for posting server descriptor,
13286 - RendPostPeriod for posting hidden service descriptors.
13287 - New log format in config:
13288 "Log minsev[-maxsev] stdout|stderr|syslog" or
13289 "Log minsev[-maxsev] file /var/foo"
13290 - DirPolicy config option, to let people reject incoming addresses
13291 from their dirserver.
13292 - "tor --list-fingerprint" will list your identity key fingerprint
13294 - Make tor --version --version dump the cvs Id of every file.
13295 - New 'MyFamily nick1,...' config option for a server to
13296 specify other servers that shouldn't be used in the same circuit
13297 with it. Only believed if nick1 also specifies us.
13298 - New 'NodeFamily nick1,nick2,...' config option for a client to
13299 specify nodes that it doesn't want to use in the same circuit.
13300 - New 'Redirectexit pattern address:port' config option for a
13301 server to redirect exit connections, e.g. to a local squid.
13302 - Add "pass" target for RedirectExit, to make it easier to break
13303 out of a sequence of RedirectExit rules.
13304 - Make the dirservers file obsolete.
13305 - Include a dir-signing-key token in directories to tell the
13306 parsing entity which key is being used to sign.
13307 - Remove the built-in bulky default dirservers string.
13308 - New config option "Dirserver %s:%d [fingerprint]", which can be
13309 repeated as many times as needed. If no dirservers specified,
13310 default to moria1,moria2,tor26.
13311 - Make 'Routerfile' config option obsolete.
13312 - Discourage people from setting their dirfetchpostperiod more often
13313 than once per minute.
13315 o Features (other):
13316 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
13317 get back to normal.)
13318 - Accept *:706 (silc) in default exit policy.
13319 - Implement new versioning format for post 0.1.
13320 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
13321 log more informatively.
13322 - Check clock skew for verified servers, but allow unverified
13323 servers and clients to have any clock skew.
13324 - Make sure the hidden service descriptors are at a random offset
13325 from each other, to hinder linkability.
13326 - Clients now generate a TLS cert too, in preparation for having
13327 them act more like real nodes.
13328 - Add a pure-C tor-resolve implementation.
13329 - Use getrlimit and friends to ensure we can reach MaxConn (currently
13330 1024) file descriptors.
13331 - Raise the max dns workers from 50 to 100.
13334 Changes in version 0.0.8.1 - 2004-10-13
13336 - Fix a seg fault that can be triggered remotely for Tor
13337 clients/servers with an open dirport.
13338 - Fix a rare assert trigger, where routerinfos for entries in
13339 our cpath would expire while we're building the path.
13340 - Fix a bug in OutboundBindAddress so it (hopefully) works.
13341 - Fix a rare seg fault for people running hidden services on
13342 intermittent connections.
13343 - Fix a bug in parsing opt keywords with objects.
13344 - Fix a stale pointer assert bug when a stream detaches and
13346 - Fix a string format vulnerability (probably not exploitable)
13347 in reporting stats locally.
13348 - Fix an assert trigger: sometimes launching circuits can fail
13349 immediately, e.g. because too many circuits have failed recently.
13350 - Fix a compile warning on 64 bit platforms.
13353 Changes in version 0.0.8 - 2004-08-25
13355 - Made our unit tests compile again on OpenBSD 3.5, and tor
13356 itself compile again on OpenBSD on a sparc64.
13357 - We were neglecting milliseconds when logging on win32, so
13358 everything appeared to happen at the beginning of each second.
13359 - Check directory signature _before_ you decide whether you're
13360 you're running an obsolete version and should exit.
13361 - Check directory signature _before_ you parse the running-routers
13362 list to decide who's running.
13363 - Check return value of fclose while writing to disk, so we don't
13364 end up with broken files when servers run out of disk space.
13365 - Port it to SunOS 5.9 / Athena
13366 - Fix two bugs in saving onion keys to disk when rotating, so
13367 hopefully we'll get fewer people using old onion keys.
13368 - Remove our mostly unused -- and broken -- hex_encode()
13369 function. Use base16_encode() instead. (Thanks to Timo Lindfors
13370 for pointing out this bug.)
13371 - Only pick and establish intro points after we've gotten a
13373 - Fix assert triggers: if the other side returns an address 0.0.0.0,
13374 don't put it into the client dns cache.
13375 - If a begin failed due to exit policy, but we believe the IP
13376 address should have been allowed, switch that router to exitpolicy
13377 reject *:* until we get our next directory.
13379 o Protocol changes:
13380 - 'Extend' relay cell payloads now include the digest of the
13381 intended next hop's identity key. Now we can verify that we're
13382 extending to the right router, and also extend to routers we
13383 hadn't heard of before.
13386 - Tor nodes can now act as relays (with an advertised ORPort)
13387 without being manually verified by the dirserver operators.
13388 - Uploaded descriptors of unverified routers are now accepted
13389 by the dirservers, and included in the directory.
13390 - Verified routers are listed by nickname in the running-routers
13391 list; unverified routers are listed as "$<fingerprint>".
13392 - We now use hash-of-identity-key in most places rather than
13393 nickname or addr:port, for improved security/flexibility.
13394 - AllowUnverifiedNodes config option to let circuits choose no-name
13395 routers in entry,middle,exit,introduction,rendezvous positions.
13396 Allow middle and rendezvous positions by default.
13397 - When picking unverified routers, skip those with low uptime and/or
13398 low bandwidth, depending on what properties you care about.
13399 - ClientOnly option for nodes that never want to become servers.
13400 - Directory caching.
13401 - "AuthoritativeDir 1" option for the official dirservers.
13402 - Now other nodes (clients and servers) will cache the latest
13403 directory they've pulled down.
13404 - They can enable their DirPort to serve it to others.
13405 - Clients will pull down a directory from any node with an open
13406 DirPort, and check the signature/timestamp correctly.
13407 - Authoritative dirservers now fetch directories from other
13408 authdirservers, to stay better synced.
13409 - Running-routers list tells who's down also, along with noting
13410 if they're verified (listed by nickname) or unverified (listed
13412 - Allow dirservers to serve running-router list separately.
13413 This isn't used yet.
13414 - You can now fetch $DIRURL/running-routers to get just the
13415 running-routers line, not the whole descriptor list. (But
13416 clients don't use this yet.)
13417 - Clients choose nodes proportional to advertised bandwidth.
13418 - Clients avoid using nodes with low uptime as introduction points.
13419 - Handle servers with dynamic IP addresses: don't just replace
13420 options->Address with the resolved one at startup, and
13421 detect our address right before we make a routerinfo each time.
13422 - 'FascistFirewall' option to pick dirservers and ORs on specific
13423 ports; plus 'FirewallPorts' config option to tell FascistFirewall
13424 which ports are open. (Defaults to 80,443)
13425 - Try other dirservers immediately if the one you try is down. This
13426 should tolerate down dirservers better now.
13427 - ORs connect-on-demand to other ORs
13428 - If you get an extend cell to an OR you're not connected to,
13429 connect, handshake, and forward the create cell.
13430 - The authoritative dirservers stay connected to everybody,
13431 and everybody stays connected to 0.0.7 servers, but otherwise
13432 clients/servers expire unused connections after 5 minutes.
13433 - When servers get a sigint, they delay 30 seconds (refusing new
13434 connections) then exit. A second sigint causes immediate exit.
13435 - File and name management:
13436 - Look for .torrc if no CONFDIR "torrc" is found.
13437 - If no datadir is defined, then choose, make, and secure ~/.tor
13439 - If torrc not found, exitpolicy reject *:*.
13440 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
13441 - If no nickname is defined, derive default from hostname.
13442 - Rename secret key files, e.g. identity.key -> secret_id_key,
13443 to discourage people from mailing their identity key to tor-ops.
13444 - Refuse to build a circuit before the directory has arrived --
13445 it won't work anyway, since you won't know the right onion keys
13447 - Parse tor version numbers so we can do an is-newer-than check
13448 rather than an is-in-the-list check.
13449 - New socks command 'resolve', to let us shim gethostbyname()
13451 - A 'tor_resolve' script to access the socks resolve functionality.
13452 - A new socks-extensions.txt doc file to describe our
13453 interpretation and extensions to the socks protocols.
13454 - Add a ContactInfo option, which gets published in descriptor.
13455 - Write tor version at the top of each log file
13456 - New docs in the tarball:
13458 - Document that you should proxy your SSL traffic too.
13459 - Log a warning if the user uses an unsafe socks variant, so people
13460 are more likely to learn about privoxy or socat.
13461 - Log a warning if you're running an unverified server, to let you
13462 know you might want to get it verified.
13463 - Change the default exit policy to reject the default edonkey,
13464 kazaa, gnutella ports.
13465 - Add replace_file() to util.[ch] to handle win32's rename().
13466 - Publish OR uptime in descriptor (and thus in directory) too.
13467 - Remember used bandwidth (both in and out), and publish 15-minute
13468 snapshots for the past day into our descriptor.
13469 - Be more aggressive about trying to make circuits when the network
13470 has changed (e.g. when you unsuspend your laptop).
13471 - Check for time skew on http headers; report date in response to
13473 - If the entrynode config line has only one node, don't pick it as
13475 - Add strict{entry|exit}nodes config options. If set to 1, then
13476 we refuse to build circuits that don't include the specified entry
13478 - OutboundBindAddress config option, to bind to a specific
13479 IP address for outgoing connect()s.
13480 - End truncated log entries (e.g. directories) with "[truncated]".
13483 Changes in version 0.0.7.3 - 2004-08-12
13484 o Stop dnsworkers from triggering an assert failure when you
13485 ask them to resolve the host "".
13488 Changes in version 0.0.7.2 - 2004-07-07
13489 o A better fix for the 0.0.0.0 problem, that will hopefully
13490 eliminate the remaining related assertion failures.
13493 Changes in version 0.0.7.1 - 2004-07-04
13494 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
13495 since internally we use 0.0.0.0 to signify "not yet resolved".
13498 Changes in version 0.0.7 - 2004-06-07
13499 o Fixes for crashes and other obnoxious bugs:
13500 - Fix an epipe bug: sometimes when directory connections failed
13501 to connect, we would give them a chance to flush before closing
13503 - When we detached from a circuit because of resolvefailed, we
13504 would immediately try the same circuit twice more, and then
13505 give up on the resolve thinking we'd tried three different
13507 - Limit the number of intro circuits we'll attempt to build for a
13508 hidden service per 15-minute period.
13509 - Check recommended-software string *early*, before actually parsing
13510 the directory. Thus we can detect an obsolete version and exit,
13511 even if the new directory format doesn't parse.
13512 o Fixes for security bugs:
13513 - Remember which nodes are dirservers when you startup, and if a
13514 random OR enables his dirport, don't automatically assume he's
13515 a trusted dirserver.
13517 - Directory connections were asking the wrong poll socket to
13518 start writing, and not asking themselves to start writing.
13519 - When we detached from a circuit because we sent a begin but
13520 didn't get a connected, we would use it again the first time;
13521 but after that we would correctly switch to a different one.
13522 - Stop warning when the first onion decrypt attempt fails; they
13523 will sometimes legitimately fail now that we rotate keys.
13524 - Override unaligned-access-ok check when $host_cpu is ia64 or
13525 arm. Apparently they allow it but the kernel whines.
13526 - Dirservers try to reconnect periodically too, in case connections
13528 - Fix some memory leaks in directory servers.
13529 - Allow backslash in Win32 filenames.
13530 - Made Tor build complain-free on FreeBSD, hopefully without
13531 breaking other BSD builds. We'll see.
13532 - Check directory signatures based on name of signer, not on whom
13533 we got the directory from. This will let us cache directories more
13535 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
13538 - Doxygen markup on all functions and global variables.
13539 - Make directory functions update routerlist, not replace it. So
13540 now directory disagreements are not so critical a problem.
13541 - Remove the upper limit on number of descriptors in a dirserver's
13542 directory (not that we were anywhere close).
13543 - Allow multiple logfiles at different severity ranges.
13544 - Allow *BindAddress to specify ":port" rather than setting *Port
13545 separately. Allow multiple instances of each BindAddress config
13546 option, so you can bind to multiple interfaces if you want.
13547 - Allow multiple exit policy lines, which are processed in order.
13548 Now we don't need that huge line with all the commas in it.
13549 - Enable accept/reject policies on SOCKS connections, so you can bind
13550 to 0.0.0.0 but still control who can use your OP.
13551 - Updated the man page to reflect these features.
13554 Changes in version 0.0.6.2 - 2004-05-16
13555 o Our integrity-checking digest was checking only the most recent cell,
13556 not the previous cells like we'd thought.
13557 Thanks to Stefan Mark for finding the flaw!
13560 Changes in version 0.0.6.1 - 2004-05-06
13561 o Fix two bugs in our AES counter-mode implementation (this affected
13562 onion-level stream encryption, but not TLS-level). It turns
13563 out we were doing something much more akin to a 16-character
13564 polyalphabetic cipher. Oops.
13565 Thanks to Stefan Mark for finding the flaw!
13566 o Retire moria3 as a directory server, and add tor26 as a directory
13570 Changes in version 0.0.6 - 2004-05-02
13572 - Hidden services and rendezvous points are implemented. Go to
13573 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
13574 hidden services. (This only works via a socks4a proxy such as
13575 Privoxy, and currently it's quite slow.)
13576 - We now rotate link (tls context) keys and onion keys.
13577 - CREATE cells now include oaep padding, so you can tell
13578 if you decrypted them correctly.
13579 - Retry stream correctly when we fail to connect because of
13580 exit-policy-reject (should try another) or can't-resolve-address.
13581 - When we hup a dirserver and we've *removed* a server from the
13582 approved-routers list, now we remove that server from the
13583 in-memory directories too.
13584 - Add bandwidthburst to server descriptor.
13585 - Directories now say which dirserver signed them.
13586 - Use a tor_assert macro that logs failed assertions too.
13587 - Since we don't support truncateds much, don't bother sending them;
13588 just close the circ.
13589 - Fetch randomness from /dev/urandom better (not via fopen/fread)
13590 - Better debugging for tls errors
13591 - Set Content-Type on the directory and hidserv descriptor.
13592 - Remove IVs from cipher code, since AES-ctr has none.
13594 - Fix an assert trigger for exit nodes that's been plaguing us since
13595 the days of 0.0.2prexx (thanks weasel!)
13596 - Fix a bug where we were closing tls connections intermittently.
13597 It turns out openssl keeps its errors around -- so if an error
13598 happens, and you don't ask about it, and then another openssl
13599 operation happens and succeeds, and you ask if there was an error,
13600 it tells you about the first error.
13601 - Fix a bug that's been lurking since 27 may 03 (!)
13602 When passing back a destroy cell, we would use the wrong circ id.
13603 - Don't crash if a conn that sent a begin has suddenly lost its circuit.
13604 - Some versions of openssl have an SSL_pending function that erroneously
13605 returns bytes when there is a non-application record pending.
13606 - Win32 fixes. Tor now compiles on win32 with no warnings/errors.
13607 o We were using an array of length zero in a few places.
13608 o Win32's gethostbyname can't resolve an IP to an IP.
13609 o Win32's close can't close a socket.
13610 o Handle windows socket errors correctly.
13612 - check for <sys/limits.h> so we build on FreeBSD again, and
13613 <machine/limits.h> for NetBSD.
13616 Changes in version 0.0.5 - 2004-03-30
13617 o Install torrc as torrc.sample -- we no longer clobber your
13619 o Fix mangled-state bug in directory fetching (was causing sigpipes).
13620 o Only build circuits after we've fetched the directory: clients were
13621 using only the directory servers before they'd fetched a directory.
13622 This also means longer startup time; so it goes.
13623 o Fix an assert trigger where an OP would fail to handshake, and we'd
13624 expect it to have a nickname.
13625 o Work around a tsocks bug: do a socks reject when AP connection dies
13626 early, else tsocks goes into an infinite loop.
13627 o Hold socks connection open until reply is flushed (if possible)
13628 o Make exit nodes resolve IPs to IPs immediately, rather than asking
13629 the dns farm to do it.
13630 o Fix c99 aliasing warnings in rephist.c
13631 o Don't include server descriptors that are older than 24 hours in the
13633 o Give socks 'reject' replies their whole 15s to attempt to flush,
13634 rather than seeing the 60s timeout and assuming the flush had failed.
13635 o Clean automake droppings from the cvs repository
13636 o Add in a 'notice' log level for things the operator should hear
13637 but that aren't warnings
13640 Changes in version 0.0.4 - 2004-03-26
13641 o When connecting to a dirserver or OR and the network is down,
13645 Changes in version 0.0.3 - 2004-03-26
13646 o Warn and fail if server chose a nickname with illegal characters
13647 o Port to Solaris and Sparc:
13648 - include missing header fcntl.h
13649 - have autoconf find -lsocket -lnsl automatically
13650 - deal with hardware word alignment
13651 - make uname() work (solaris has a different return convention)
13652 - switch from using signal() to sigaction()
13653 o Preliminary work on reputation system:
13654 - Keep statistics on success/fail of connect attempts; they're published
13655 by kill -USR1 currently.
13656 - Add a RunTesting option to try to learn link state by creating test
13657 circuits, even when SocksPort is off.
13658 - Remove unused open circuits when there are too many.
13661 Changes in version 0.0.2 - 2004-03-19
13662 - Include strlcpy and strlcat for safer string ops
13663 - define INADDR_NONE so we compile (but still not run) on solaris
13666 Changes in version 0.0.2pre27 - 2004-03-14
13668 - Allow internal tor networks (we were rejecting internal IPs,
13669 now we allow them if they're set explicitly).
13670 - And fix a few endian issues.
13673 Changes in version 0.0.2pre26 - 2004-03-14
13675 - If a stream times out after 15s without a connected cell, don't
13676 try that circuit again: try a new one.
13677 - Retry streams at most 4 times. Then give up.
13678 - When a dirserver gets a descriptor from an unknown router, it
13679 logs its fingerprint (so the dirserver operator can choose to
13680 accept it even without mail from the server operator).
13681 - Inform unapproved servers when we reject their descriptors.
13682 - Make tor build on Windows again. It works as a client, who knows
13684 - Clearer instructions in the torrc for how to set up a server.
13685 - Be more efficient about reading fd's when our global token bucket
13686 (used for rate limiting) becomes empty.
13688 - Stop asserting that computers always go forward in time. It's
13690 - When we sent a cell (e.g. destroy) and then marked an OR connection
13691 expired, we might close it before finishing a flush if the other
13692 side isn't reading right then.
13693 - Don't allow dirservers to start if they haven't defined
13694 RecommendedVersions
13695 - We were caching transient dns failures. Oops.
13696 - Prevent servers from publishing an internal IP as their address.
13697 - Address a strcat vulnerability in circuit.c
13700 Changes in version 0.0.2pre25 - 2004-03-04
13702 - Put the OR's IP in its router descriptor, not its fqdn. That way
13703 we'll stop being stalled by gethostbyname for nodes with flaky dns,
13706 - If the user typed in an address that didn't resolve, the server
13710 Changes in version 0.0.2pre24 - 2004-03-03
13712 - Fix an assertion failure in dns.c, where we were trying to dequeue
13713 a pending dns resolve even if it wasn't pending
13714 - Fix a spurious socks5 warning about still trying to write after the
13715 connection is finished.
13716 - Hold certain marked_for_close connections open until they're finished
13717 flushing, rather than losing bytes by closing them too early.
13718 - Correctly report the reason for ending a stream
13719 - Remove some duplicate calls to connection_mark_for_close
13720 - Put switch_id and start_daemon earlier in the boot sequence, so it
13721 will actually try to chdir() to options.DataDirectory
13722 - Make 'make test' exit(1) if a test fails; fix some unit tests
13723 - Make tor fail when you use a config option it doesn't know about,
13724 rather than warn and continue.
13725 - Make --version work
13726 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
13729 Changes in version 0.0.2pre23 - 2004-02-29
13731 - Print a statement when the first circ is finished, so the user
13732 knows it's working.
13733 - If a relay cell is unrecognized at the end of the circuit,
13734 send back a destroy. (So attacks to mutate cells are more
13736 - New config option 'excludenodes' to avoid certain nodes for circuits.
13737 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
13738 so you can collect coredumps there.
13740 - Fix a bug in tls flushing where sometimes data got wedged and
13741 didn't flush until more data got sent. Hopefully this bug was
13742 a big factor in the random delays we were seeing.
13743 - Make 'connected' cells include the resolved IP, so the client
13744 dns cache actually gets populated.
13745 - Disallow changing from ORPort=0 to ORPort>0 on hup.
13746 - When we time-out on a stream and detach from the circuit, send an
13747 end cell down it first.
13748 - Only warn about an unknown router (in exitnodes, entrynodes,
13749 excludenodes) after we've fetched a directory.
13752 Changes in version 0.0.2pre22 - 2004-02-26
13754 - Servers publish less revealing uname information in descriptors.
13755 - More memory tracking and assertions, to crash more usefully when
13757 - If the default torrc isn't there, just use some default defaults.
13758 Plus provide an internal dirservers file if they don't have one.
13759 - When the user tries to use Tor as an http proxy, give them an http
13760 501 failure explaining that we're a socks proxy.
13761 - Dump a new router.desc on hup, to help confused people who change
13762 their exit policies and then wonder why router.desc doesn't reflect
13764 - Clean up the generic tor.sh init script that we ship with.
13766 - If the exit stream is pending on the resolve, and a destroy arrives,
13767 then the stream wasn't getting removed from the pending list. I
13768 think this was the one causing recent server crashes.
13769 - Use a more robust poll on OSX 10.3, since their poll is flaky.
13770 - When it couldn't resolve any dirservers, it was useless from then on.
13771 Now it reloads the RouterFile (or default dirservers) if it has no
13773 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
13774 many users don't even *have* a /usr/local/sbin/.
13777 Changes in version 0.0.2pre21 - 2004-02-18
13779 - There's a ChangeLog file that actually reflects the changelog.
13780 - There's a 'torify' wrapper script, with an accompanying
13781 tor-tsocks.conf, that simplifies the process of using tsocks for
13782 tor. It even has a man page.
13783 - The tor binary gets installed to sbin rather than bin now.
13784 - Retry streams where the connected cell hasn't arrived in 15 seconds
13785 - Clean up exit policy handling -- get the default out of the torrc,
13786 so we can update it without forcing each server operator to fix
13788 - Allow imaps and pop3s in default exit policy
13790 - Prevent picking middleman nodes as the last node in the circuit
13793 Changes in version 0.0.2pre20 - 2004-01-30
13795 - We now have a deb package, and it's in debian unstable. Go to
13796 it, apt-getters. :)
13797 - I've split the TotalBandwidth option into BandwidthRate (how many
13798 bytes per second you want to allow, long-term) and
13799 BandwidthBurst (how many bytes you will allow at once before the cap
13800 kicks in). This better token bucket approach lets you, say, set
13801 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
13802 performance while not exceeding your monthly bandwidth quota.
13803 - Push out a tls record's worth of data once you've got it, rather
13804 than waiting until you've read everything waiting to be read. This
13805 may improve performance by pipelining better. We'll see.
13806 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
13807 from failed circuits (if they haven't been connected yet) and attach
13809 - Expire old streams that haven't managed to connect. Some day we'll
13810 have them reattach to new circuits instead.
13813 - Fix several memory leaks that were causing servers to become bloated
13815 - Fix a few very rare assert triggers. A few more remain.
13816 - Setuid to User _before_ complaining about running as root.
13819 Changes in version 0.0.2pre19 - 2004-01-07
13821 - Fix deadlock condition in dns farm. We were telling a child to die by
13822 closing the parent's file descriptor to him. But newer children were
13823 inheriting the open file descriptor from the parent, and since they
13824 weren't closing it, the socket never closed, so the child never read
13825 eof, so he never knew to exit. Similarly, dns workers were holding
13826 open other sockets, leading to all sorts of chaos.
13827 - New cleaner daemon() code for forking and backgrounding.
13828 - If you log to a file, it now prints an entry at the top of the
13829 logfile so you know it's working.
13830 - The onionskin challenge length was 30 bytes longer than necessary.
13831 - Started to patch up the spec so it's not quite so out of date.
13834 Changes in version 0.0.2pre18 - 2004-01-02
13836 - Fix endian issues with the 'integrity' field in the relay header.
13837 - Fix a potential bug where connections in state
13838 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
13841 Changes in version 0.0.2pre17 - 2003-12-30
13843 - Made --debuglogfile (or any second log file, actually) work.
13844 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
13845 adversary could force us into an infinite loop.
13848 - Each onionskin handshake now includes a hash of the computed key,
13849 to prove the server's identity and help perfect forward secrecy.
13850 - Changed cell size from 256 to 512 bytes (working toward compatibility
13852 - Changed cell length to 2 bytes, and moved it to the relay header.
13853 - Implemented end-to-end integrity checking for the payloads of
13855 - Separated streamid from 'recognized' (otherwise circuits will get
13856 messed up when we try to have streams exit from the middle). We
13857 use the integrity-checking to confirm that a cell is addressed to
13859 - Randomize the initial circid and streamid values, so an adversary who
13860 breaks into a node can't learn how many circuits or streams have
13864 Changes in version 0.0.2pre16 - 2003-12-14
13866 - Fixed a bug that made HUP trigger an assert
13867 - Fixed a bug where a circuit that immediately failed wasn't being
13868 counted as a failed circuit in counting retries.
13871 - Now we close the circuit when we get a truncated cell: otherwise we're
13872 open to an anonymity attack where a bad node in the path truncates
13873 the circuit and then we open streams at him.
13874 - Add port ranges to exit policies
13875 - Add a conservative default exit policy
13876 - Warn if you're running tor as root
13877 - on HUP, retry OR connections and close/rebind listeners
13878 - options.EntryNodes: try these nodes first when picking the first node
13879 - options.ExitNodes: if your best choices happen to include any of
13880 your preferred exit nodes, you choose among just those preferred
13882 - options.ExcludedNodes: nodes that are never picked in path building
13885 Changes in version 0.0.2pre15 - 2003-12-03
13886 o Robustness and bugfixes:
13887 - Sometimes clients would cache incorrect DNS resolves, which would
13888 really screw things up.
13889 - An OP that goes offline would slowly leak all its sockets and stop
13891 - A wide variety of bugfixes in exit node selection, exit policy
13892 handling, and processing pending streams when a new circuit is
13894 - Pick nodes for a path only from those the directory says are up
13895 - Choose randomly from all running dirservers, not always the first one
13896 - Increase allowed http header size for directory fetch.
13897 - Stop writing to stderr (if we're daemonized it will be closed).
13898 - Enable -g always, so cores will be more useful to me.
13899 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
13902 - Wrote a man page. It lists commonly used options.
13905 - Change default loglevel to warn.
13906 - Make PidFile default to null rather than littering in your CWD.
13907 - OnionRouter config option is now obsolete. Instead it just checks
13909 - Moved to a single unified torrc file for both clients and servers.
13912 Changes in version 0.0.2pre14 - 2003-11-29
13913 o Robustness and bugfixes:
13914 - Force the admin to make the DataDirectory himself
13915 - to get ownership/permissions right
13916 - so clients no longer make a DataDirectory and then never use it
13917 - fix bug where a client who was offline for 45 minutes would never
13918 pull down a directory again
13919 - fix (or at least hide really well) the dns assert bug that was
13920 causing server crashes
13921 - warnings and improved robustness wrt clockskew for certs
13922 - use the native daemon(3) to daemonize, when available
13923 - exit if bind() fails
13924 - exit if neither socksport nor orport is defined
13925 - include our own tor_timegm (Win32 doesn't have its own)
13926 - bugfix for win32 with lots of connections
13927 - fix minor bias in PRNG
13928 - make dirserver more robust to corrupt cached directory
13931 - Wrote the design document (woo)
13933 o Circuit building and exit policies:
13934 - Circuits no longer try to use nodes that the directory has told them
13936 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
13937 bitcounts (18.0.0.0/8).
13938 - Make AP connections standby for a circuit if no suitable circuit
13939 exists, rather than failing
13940 - Circuits choose exit node based on addr/port, exit policies, and
13941 which AP connections are standing by
13942 - Bump min pathlen from 2 to 3
13943 - Relay end cells have a payload to describe why the stream ended.
13944 - If the stream failed because of exit policy, try again with a new
13946 - Clients have a dns cache to remember resolved addresses.
13947 - Notice more quickly when we have no working circuits
13950 - APPort is now called SocksPort
13951 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
13953 - RecommendedVersions is now a config variable rather than
13954 hardcoded (for dirservers)
13955 - Reloads config on HUP
13956 - Usage info on -h or --help
13957 - If you set User and Group config vars, it'll setu/gid to them.
13959 Changes in version 0.0.2pre13 - 2003-10-19
13960 o General stability:
13961 - SSL_write no longer fails when it returns WANTWRITE and the number
13962 of bytes in the buf has changed by the next SSL_write call.
13963 - Fix segfault fetching directory when network is down
13964 - Fix a variety of minor memory leaks
13965 - Dirservers reload the fingerprints file on HUP, so I don't have
13966 to take down the network when I approve a new router
13967 - Default server config file has explicit Address line to specify fqdn
13970 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
13971 - Make listener connections not ever alloc bufs
13973 o Autoconf improvements:
13974 - don't clobber an external CFLAGS in ./configure
13975 - Make install now works
13976 - create var/lib/tor on make install
13977 - autocreate a tor.sh initscript to help distribs
13978 - autocreate the torrc and sample-server-torrc with correct paths
13980 o Log files and Daemonizing now work:
13981 - If --DebugLogFile is specified, log to it at -l debug
13982 - If --LogFile is specified, use it instead of commandline
13983 - If --RunAsDaemon is set, tor forks and backgrounds on startup