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.7.7 - 2017-03-03
6 Tor 0.2.7.7 backports a number of security fixes from later Tor
7 releases. Anybody running Tor 0.2.7.6 or earlier should upgrade to
8 this release, if for some reason they cannot upgrade to a later
11 Note that support for Tor 0.2.7.x is ending this year: we will not issue
12 any fixes for the Tor 0.2.7.x series after 1 August 2017. If you need
13 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
15 o Directory authority changes (backport from 0.2.8.5-rc):
16 - Urras is no longer a directory authority. Closes ticket 19271.
18 o Directory authority changes (backport from 0.2.9.2-alpha):
19 - The "Tonga" bridge authority has been retired; the new bridge
20 authority is "Bifroest". Closes tickets 19728 and 19690.
22 o Directory authority key updates (backport from 0.2.8.1-alpha):
23 - Update the V3 identity key for the dannenberg directory authority:
24 it was changed on 18 November 2015. Closes task 17906. Patch
27 o Major bugfixes (parsing, security, backport from 0.2.9.8):
28 - Fix a bug in parsing that could cause clients to read a single
29 byte past the end of an allocated region. This bug could be used
30 to cause hardened clients (built with --enable-expensive-hardening)
31 to crash if they tried to visit a hostile hidden service. Non-
32 hardened clients are only affected depending on the details of
33 their platform's memory allocator. Fixes bug 21018; bugfix on
34 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
35 2016-12-002 and as CVE-2016-1254.
37 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
38 - Stop a crash that could occur when a client running with DNSPort
39 received a query with multiple address types, and the first
40 address type was not supported. Found and fixed by Scott Dial.
41 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
42 - Prevent a class of security bugs caused by treating the contents
43 of a buffer chunk as if they were a NUL-terminated string. At
44 least one such bug seems to be present in all currently used
45 versions of Tor, and would allow an attacker to remotely crash
46 most Tor instances, especially those compiled with extra compiler
47 hardening. With this defense in place, such bugs can't crash Tor,
48 though we should still fix them as they occur. Closes ticket
49 20384 (TROVE-2016-10-001).
51 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
52 - Avoid a difficult-to-trigger heap corruption attack when extending
53 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
54 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
55 Reported by Guido Vranken.
57 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
58 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
59 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
61 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
62 - If OpenSSL fails to generate an RSA key, do not retain a dangling
63 pointer to the previous (uninitialized) key value. The impact here
64 should be limited to a difficult-to-trigger crash, if OpenSSL is
65 running an engine that makes key generation failures possible, or
66 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
67 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
70 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
71 - Fix an integer underflow bug when comparing malformed Tor
72 versions. This bug could crash Tor when built with
73 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
74 0.2.9.8, which were built with -ftrapv by default. In other cases
75 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
76 on 0.0.8pre1. Found by OSS-Fuzz.
78 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
79 - Make memwipe() do nothing when passed a NULL pointer or buffer of
80 zero size. Check size argument to memwipe() for underflow. Fixes
81 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
84 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
85 - Make Tor survive errors involving connections without a
86 corresponding event object. Previously we'd fail with an
87 assertion; now we produce a log message. Related to bug 16248.
89 o Minor features (geoip):
90 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
94 Changes in version 0.2.7.6 - 2015-12-10
95 Tor version 0.2.7.6 fixes a major bug in entry guard selection, as
96 well as a minor bug in hidden service reliability.
98 o Major bugfixes (guard selection):
99 - Actually look at the Guard flag when selecting a new directory
100 guard. When we implemented the directory guard design, we
101 accidentally started treating all relays as if they have the Guard
102 flag during guard selection, leading to weaker anonymity and worse
103 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
106 o Minor features (geoip):
107 - Update geoip and geoip6 to the December 1 2015 Maxmind GeoLite2
110 o Minor bugfixes (compilation):
111 - When checking for net/pfvar.h, include netinet/in.h if possible.
112 This fixes transparent proxy detection on OpenBSD. Fixes bug
113 17551; bugfix on 0.1.2.1-alpha. Patch from "rubiate".
114 - Fix a compilation warning with Clang 3.6: Do not check the
115 presence of an address which can never be NULL. Fixes bug 17781.
117 o Minor bugfixes (correctness):
118 - When displaying an IPv6 exit policy, include the mask bits
119 correctly even when the number is greater than 31. Fixes bug
120 16056; bugfix on 0.2.4.7-alpha. Patch from "gturner".
121 - The wrong list was used when looking up expired intro points in a
122 rend service object, causing what we think could be reachability
123 issues for hidden services, and triggering a BUG log. Fixes bug
124 16702; bugfix on 0.2.7.2-alpha.
125 - Fix undefined behavior in the tor_cert_checksig function. Fixes
126 bug 17722; bugfix on 0.2.7.2-alpha.
129 Changes in version 0.2.7.5 - 2015-11-20
130 The Tor 0.2.7 release series is dedicated to the memory of Tor user
131 and privacy advocate Caspar Bowden (1961-2015). Caspar worked
132 tirelessly to advocate human rights regardless of national borders,
133 and oppose the encroachments of mass surveillance. He opposed national
134 exceptionalism, he brought clarity to legal and policy debates, he
135 understood and predicted the impact of mass surveillance on the world,
136 and he laid the groundwork for resisting it. While serving on the Tor
137 Project's board of directors, he brought us his uncompromising focus
138 on technical excellence in the service of humankind. Caspar was an
139 inimitable force for good and a wonderful friend. He was kind,
140 humorous, generous, gallant, and believed we should protect one
141 another without exception. We honor him here for his ideals, his
142 efforts, and his accomplishments. Please honor his memory with works
143 that would make him proud.
145 Tor 0.2.7.5 is the first stable release in the Tor 0.2.7 series.
147 The 0.2.7 series adds a more secure identity key type for relays,
148 improves cryptography performance, resolves several longstanding
149 hidden-service performance issues, improves controller support for
150 hidden services, and includes small bugfixes and performance
151 improvements throughout the program. This release series also includes
152 more tests than before, and significant simplifications to which parts
153 of Tor invoke which others. For a full list of changes, see below.
155 o New system requirements:
156 - Tor no longer includes workarounds to support Libevent versions
157 before 1.3e. Libevent 2.0 or later is recommended. Closes
159 - Tor no longer supports copies of OpenSSL that are missing support
160 for Elliptic Curve Cryptography. (We began using ECC when
161 available in 0.2.4.8-alpha, for more safe and efficient key
162 negotiation.) In particular, support for at least one of P256 or
163 P224 is now required, with manual configuration needed if only
164 P224 is available. Resolves ticket 16140.
165 - Tor no longer supports versions of OpenSSL before 1.0. (If you are
166 on an operating system that has not upgraded to OpenSSL 1.0 or
167 later, and you compile Tor from source, you will need to install a
168 more recent OpenSSL to link Tor against.) These versions of
169 OpenSSL are still supported by the OpenSSL, but the numerous
170 cryptographic improvements in later OpenSSL releases makes them a
171 clear choice. Resolves ticket 16034.
173 o Major features (controller):
174 - Add the ADD_ONION and DEL_ONION commands that allow the creation
175 and management of hidden services via the controller. Closes
177 - New "GETINFO onions/current" and "GETINFO onions/detached"
178 commands to get information about hidden services created via the
179 controller. Part of ticket 6411.
180 - New HSFETCH command to launch a request for a hidden service
181 descriptor. Closes ticket 14847.
182 - New HSPOST command to upload a hidden service descriptor. Closes
183 ticket 3523. Patch by "DonnchaC".
185 o Major features (Ed25519 identity keys, Proposal 220):
186 - Add support for offline encrypted Ed25519 master keys. To use this
187 feature on your tor relay, run "tor --keygen" to make a new master
188 key (or to make a new signing key if you already have a master
189 key). Closes ticket 13642.
190 - All relays now maintain a stronger identity key, using the Ed25519
191 elliptic curve signature format. This master key is designed so
192 that it can be kept offline. Relays also generate an online
193 signing key, and a set of other Ed25519 keys and certificates.
194 These are all automatically regenerated and rotated as needed.
195 Implements part of ticket 12498.
196 - Directory authorities now vote on Ed25519 identity keys along with
197 RSA1024 keys. Implements part of ticket 12498.
198 - Directory authorities track which Ed25519 identity keys have been
199 used with which RSA1024 identity keys, and do not allow them to
200 vary freely. Implements part of ticket 12498.
201 - Microdescriptors now include Ed25519 identity keys. Implements
202 part of ticket 12498.
203 - Add a --newpass option to allow changing or removing the
204 passphrase of an encrypted key with tor --keygen. Implements part
206 - Add a new OfflineMasterKey option to tell Tor never to try loading
207 or generating a secret Ed25519 identity key. You can use this in
208 combination with tor --keygen to manage offline and/or encrypted
209 Ed25519 keys. Implements ticket 16944.
210 - On receiving a HUP signal, check to see whether the Ed25519
211 signing key has changed, and reload it if so. Closes ticket 16790.
212 - Significant usability improvements for Ed25519 key management. Log
213 messages are better, and the code can recover from far more
214 failure conditions. Thanks to "s7r" for reporting and diagnosing
217 o Major features (ECC performance):
218 - Improve the runtime speed of Ed25519 signature verification by
219 using Ed25519-donna's batch verification support. Implements
221 - Improve the speed of Ed25519 operations and Curve25519 keypair
222 generation when built targeting 32 bit x86 platforms with SSE2
223 available. Implements ticket 16535.
224 - Improve the runtime speed of Ed25519 operations by using the
225 public-domain Ed25519-donna by Andrew M. ("floodyberry").
226 Implements ticket 16467.
227 - Improve the runtime speed of the ntor handshake by using an
228 optimized curve25519 basepoint scalarmult implementation from the
229 public-domain Ed25519-donna by Andrew M. ("floodyberry"), based on
230 ideas by Adam Langley. Implements ticket 9663.
232 o Major features (Hidden services):
233 - Hidden services, if using the EntryNodes option, are required to
234 use more than one EntryNode, in order to avoid a guard discovery
235 attack. (This would only affect people who had configured hidden
236 services and manually specified the EntryNodes option with a
237 single entry-node. The impact was that it would be easy to
238 remotely identify the guard node used by such a hidden service.
239 See ticket for more information.) Fixes ticket 14917.
240 - Add the torrc option HiddenServiceNumIntroductionPoints, to
241 specify a fixed number of introduction points. Its maximum value
242 is 10 and default is 3. Using this option can increase a hidden
243 service's reliability under load, at the cost of making it more
244 visible that the hidden service is facing extra load. Closes
246 - Remove the adaptive algorithm for choosing the number of
247 introduction points, which used to change the number of
248 introduction points (poorly) depending on the number of
249 connections the HS sees. Closes ticket 4862.
251 o Major features (onion key cross-certification):
252 - Relay descriptors now include signatures of their own identity
253 keys, made using the TAP and ntor onion keys. These signatures
254 allow relays to prove ownership of their own onion keys. Because
255 of this change, microdescriptors will no longer need to include
256 RSA identity keys. Implements proposal 228; closes ticket 12499.
258 o Major bugfixes (client-side privacy, also in 0.2.6.9):
259 - Properly separate out each SOCKSPort when applying stream
260 isolation. The error occurred because each port's session group
261 was being overwritten by a default value when the listener
262 connection was initialized. Fixes bug 16247; bugfix on
263 0.2.6.3-alpha. Patch by "jojelino".
265 o Major bugfixes (hidden service clients, stability, also in 0.2.6.10):
266 - Stop refusing to store updated hidden service descriptors on a
267 client. This reverts commit 9407040c59218 (which indeed fixed bug
268 14219, but introduced a major hidden service reachability
269 regression detailed in bug 16381). This is a temporary fix since
270 we can live with the minor issue in bug 14219 (it just results in
271 some load on the network) but the regression of 16381 is too much
272 of a setback. First-round fix for bug 16381; bugfix
275 o Major bugfixes (hidden services):
276 - Revert commit that made directory authorities assign the HSDir
277 flag to relay without a DirPort; this was bad because such relays
278 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
279 on tor-0.2.6.3-alpha.
280 - When cannibalizing a circuit for an introduction point, always
281 extend to the chosen exit node (creating a 4 hop circuit).
282 Previously Tor would use the current circuit exit node, which
283 changed the original choice of introduction point, and could cause
284 the hidden service to skip excluded introduction points or
285 reconnect to a skipped introduction point. Fixes bug 16260; bugfix
288 o Major bugfixes (memory leaks):
289 - Fix a memory leak in ed25519 batch signature checking. Fixes bug
290 17398; bugfix on 0.2.6.1-alpha.
292 o Major bugfixes (open file limit):
293 - The open file limit wasn't checked before calling
294 tor_accept_socket_nonblocking(), which would make Tor exceed the
295 limit. Now, before opening a new socket, Tor validates the open
296 file limit just before, and if the max has been reached, return an
297 error. Fixes bug 16288; bugfix on 0.1.1.1-alpha.
299 o Major bugfixes (security, correctness):
300 - Fix an error that could cause us to read 4 bytes before the
301 beginning of an openssl string. This bug could be used to cause
302 Tor to crash on systems with unusual malloc implementations, or
303 systems with unusual hardening installed. Fixes bug 17404; bugfix
306 o Major bugfixes (stability, also in 0.2.6.10):
307 - Stop crashing with an assertion failure when parsing certain kinds
308 of malformed or truncated microdescriptors. Fixes bug 16400;
309 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
310 by "cypherpunks_backup".
311 - Stop random client-side assertion failures that could occur when
312 connecting to a busy hidden service, or connecting to a hidden
313 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
316 o Minor features (client, SOCKS):
317 - Add GroupWritable and WorldWritable options to unix-socket based
318 SocksPort and ControlPort options. These options apply to a single
319 socket, and override {Control,Socks}SocketsGroupWritable. Closes
321 - Relax the validation done to hostnames in SOCKS5 requests, and
322 allow a single trailing '.' to cope with clients that pass FQDNs
323 using that syntax to explicitly indicate that the domain name is
324 fully-qualified. Fixes bug 16674; bugfix on 0.2.6.2-alpha.
325 - Relax the validation of hostnames in SOCKS5 requests, allowing the
326 character '_' to appear, in order to cope with domains observed in
327 the wild that are serving non-RFC compliant records. Resolves
330 o Minor features (client-side privacy):
331 - New KeepAliveIsolateSOCKSAuth option to indefinitely extend circuit
332 lifespan when IsolateSOCKSAuth and streams with SOCKS
333 authentication are attached to the circuit. This allows
334 applications like TorBrowser to manage circuit lifetime on their
335 own. Implements feature 15482.
336 - When logging malformed hostnames from SOCKS5 requests, respect
337 SafeLogging configuration. Fixes bug 16891; bugfix on 0.1.1.16-rc.
339 o Minor features (clock-jump tolerance):
340 - Recover better when our clock jumps back many hours, like might
341 happen for Tails or Whonix users who start with a very wrong
342 hardware clock, use Tor to discover a more accurate time, and then
343 fix their clock. Resolves part of ticket 8766.
345 o Minor features (command-line interface):
346 - Make --hash-password imply --hush to prevent unnecessary noise.
347 Closes ticket 15542. Patch from "cypherpunks".
348 - Print a warning whenever we find a relative file path being used
349 as torrc option. Resolves issue 14018.
351 o Minor features (compilation):
352 - Give a warning as early as possible when trying to build with an
353 unsupported OpenSSL version. Closes ticket 16901.
354 - Use C99 variadic macros when the compiler is not GCC. This avoids
355 failing compilations on MSVC, and fixes a log-file-based race
356 condition in our old workarounds. Original patch from Gisle Vanem.
358 o Minor features (control protocol):
359 - Support network-liveness GETINFO key and NETWORK_LIVENESS event in
360 the control protocol. Resolves ticket 15358.
362 o Minor features (controller):
363 - Add DirAuthority lines for default directory authorities to the
364 output of the "GETINFO config/defaults" command if not already
365 present. Implements ticket 14840.
366 - Controllers can now use "GETINFO hs/client/desc/id/..." to
367 retrieve items from the client's hidden service descriptor cache.
369 - Implement a new controller command "GETINFO status/fresh-relay-
370 descs" to fetch a descriptor/extrainfo pair that was generated on
371 demand just for the controller's use. Implements ticket 14784.
373 o Minor features (directory authorities):
374 - Directory authorities no longer vote against the "Fast", "Stable",
375 and "HSDir" flags just because they were going to vote against
376 "Running": if the consensus turns out to be that the router was
377 running, then the authority's vote should count. Patch from Peter
378 Retzlaff; closes issue 8712.
380 o Minor features (directory authorities, security, also in 0.2.6.9):
381 - The HSDir flag given by authorities now requires the Stable flag.
382 For the current network, this results in going from 2887 to 2806
383 HSDirs. Also, it makes it harder for an attacker to launch a sybil
384 attack by raising the effort for a relay to become Stable to
385 require at the very least 7 days, while maintaining the 96 hours
386 uptime requirement for HSDir. Implements ticket 8243.
388 o Minor features (DoS-resistance):
389 - Make it harder for attackers to overload hidden services with
390 introductions, by blocking multiple introduction requests on the
391 same circuit. Resolves ticket 15515.
393 o Minor features (geoip):
394 - Update geoip and geoip6 to the October 9 2015 Maxmind GeoLite2
397 o Minor features (hidden services):
398 - Add the new options "HiddenServiceMaxStreams" and
399 "HiddenServiceMaxStreamsCloseCircuit" to allow hidden services to
400 limit the maximum number of simultaneous streams per circuit, and
401 optionally tear down the circuit when the limit is exceeded. Part
403 - Client now uses an introduction point failure cache to know when
404 to fetch or keep a descriptor in their cache. Previously, failures
405 were recorded implicitly, but not explicitly remembered. Closes
407 - Relays need to have the Fast flag to get the HSDir flag. As this
408 is being written, we'll go from 2745 HSDirs down to 2342, a ~14%
409 drop. This change should make some attacks against the hidden
410 service directory system harder. Fixes ticket 15963.
411 - Turn on hidden service statistics collection by setting the torrc
412 option HiddenServiceStatistics to "1" by default. (This keeps
413 track only of the fraction of traffic used by hidden services, and
414 the total number of hidden services in existence.) Closes
416 - To avoid leaking HS popularity, don't cycle the introduction point
417 when we've handled a fixed number of INTRODUCE2 cells but instead
418 cycle it when a random number of introductions is reached, thus
419 making it more difficult for an attacker to find out the amount of
420 clients that have used the introduction point for a specific HS.
423 o Minor features (logging):
424 - Include the Tor version in all LD_BUG log messages, since people
425 tend to cut and paste those into the bugtracker. Implements
428 o Minor features (pluggable transports):
429 - When launching managed pluggable transports on Linux systems,
430 attempt to have the kernel deliver a SIGTERM on tor exit if the
431 pluggable transport process is still running. Resolves
433 - When launching managed pluggable transports, setup a valid open
434 stdin in the child process that can be used to detect if tor has
435 terminated. The "TOR_PT_EXIT_ON_STDIN_CLOSE" environment variable
436 can be used by implementations to detect this new behavior.
437 Resolves ticket 15435.
439 o Minor bugfixes (torrc exit policies):
440 - In each instance above, usage advice is provided to avoid the
441 message. Resolves ticket 16069. Patch by "teor". Fixes part of bug
442 16069; bugfix on 0.2.4.7-alpha.
443 - In torrc, "accept6 *" and "reject6 *" ExitPolicy lines now only
444 produce IPv6 wildcard addresses. Previously they would produce
445 both IPv4 and IPv6 wildcard addresses. Patch by "teor". Fixes part
446 of bug 16069; bugfix on 0.2.4.7-alpha.
447 - When parsing torrc ExitPolicies, we now issue an info-level
448 message when expanding an "accept/reject *" line to include both
449 IPv4 and IPv6 wildcard addresses. Related to ticket 16069.
450 - When parsing torrc ExitPolicies, we now warn for a number of cases
451 where the user's intent is likely to differ from Tor's actual
452 behavior. These include: using an IPv4 address with an accept6 or
453 reject6 line; using "private" on an accept6 or reject6 line; and
454 including any ExitPolicy lines after accept *:* or reject *:*.
455 Related to ticket 16069.
457 o Minor bugfixes (command-line interface):
458 - When "--quiet" is provided along with "--validate-config", do not
459 write anything to stdout on success. Fixes bug 14994; bugfix
461 - When complaining about bad arguments to "--dump-config", use
463 - Print usage information for --dump-config when it is used without
464 an argument. Also, fix the error message to use different wording
465 and add newline at the end. Fixes bug 15541; bugfix
468 o Minor bugfixes (compilation):
469 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
470 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
471 - Repair compilation with the most recent (unreleased, alpha)
472 vesions of OpenSSL 1.1. Fixes part of ticket 17237.
474 o Minor bugfixes (compilation, also in 0.2.6.9):
475 - Build with --enable-systemd correctly when libsystemd is
476 installed, but systemd is not. Fixes bug 16164; bugfix on
477 0.2.6.3-alpha. Patch from Peter Palfrader.
479 o Minor bugfixes (configuration, unit tests):
480 - Only add the default fallback directories when the DirAuthorities,
481 AlternateDirAuthority, and FallbackDir directory config options
482 are set to their defaults. The default fallback directory list is
483 currently empty, this fix will only change tor's behavior when it
484 has default fallback directories. Includes unit tests for
485 consider_adding_dir_servers(). Fixes bug 15642; bugfix on
486 90f6071d8dc0 in 0.2.4.7-alpha. Patch by "teor".
488 o Minor bugfixes (controller):
489 - Add the descriptor ID in each HS_DESC control event. It was
490 missing, but specified in control-spec.txt. Fixes bug 15881;
491 bugfix on 0.2.5.2-alpha.
493 o Minor bugfixes (correctness):
494 - For correctness, avoid modifying a constant string in
495 handle_control_postdescriptor. Fixes bug 15546; bugfix
497 - Remove side-effects from tor_assert() calls. This was harmless,
498 because we never disable assertions, but it is bad style and
499 unnecessary. Fixes bug 15211; bugfix on 0.2.5.5, 0.2.2.36,
501 - When calling channel_free_list(), avoid calling smartlist_remove()
502 while inside a FOREACH loop. This partially reverts commit
503 17356fe7fd96af where the correct SMARTLIST_DEL_CURRENT was
504 incorrectly removed. Fixes bug 16924; bugfix on 0.2.4.4-alpha.
506 o Minor bugfixes (crypto error-handling, also in 0.2.6.10):
507 - Check for failures from crypto_early_init, and refuse to continue.
508 A previous typo meant that we could keep going with an
509 uninitialized crypto library, and would have OpenSSL initialize
510 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
511 when implementing ticket 4900. Patch by "teor".
513 o Minor bugfixes (hidden service):
514 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
515 a client authorized hidden service. Fixes bug 15823; bugfix
517 - Remove an extraneous newline character from the end of hidden
518 service descriptors. Fixes bug 15296; bugfix on 0.2.0.10-alpha.
520 o Minor bugfixes (Linux seccomp2 sandbox):
521 - Use the sandbox in tor_open_cloexec whether or not O_CLOEXEC is
522 defined. Patch by "teor". Fixes bug 16515; bugfix on 0.2.3.1-alpha.
523 - Allow bridge authorities to run correctly under the seccomp2
524 sandbox. Fixes bug 16964; bugfix on 0.2.5.1-alpha.
525 - Add the "hidserv-stats" filename to our sandbox filter for the
526 HiddenServiceStatistics option to work properly. Fixes bug 17354;
527 bugfix on tor-0.2.6.2-alpha. Patch from David Goulet.
529 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.10):
530 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
531 these when eventfd2() support is missing. Fixes bug 16363; bugfix
532 on 0.2.6.3-alpha. Patch from "teor".
534 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.9):
535 - Allow systemd connections to work with the Linux seccomp2 sandbox
536 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
538 - Fix sandboxing to work when running as a relay, by allowing the
539 renaming of secret_id_key, and allowing the eventfd2 and futex
540 syscalls. Fixes bug 16244; bugfix on 0.2.6.1-alpha. Patch by
543 o Minor bugfixes (logging):
544 - When building Tor under Clang, do not include an extra set of
545 parentheses in log messages that include function names. Fixes bug
546 15269; bugfix on every released version of Tor when compiled with
549 o Minor bugfixes (network):
550 - When attempting to use fallback technique for network interface
551 lookup, disregard loopback and multicast addresses since they are
552 unsuitable for public communications.
554 o Minor bugfixes (open file limit):
555 - Fix set_max_file_descriptors() to set by default the max open file
556 limit to the current limit when setrlimit() fails. Fixes bug
557 16274; bugfix on tor- 0.2.0.10-alpha. Patch by dgoulet.
559 o Minor bugfixes (portability):
560 - Check correctly for Windows socket errors in the workqueue
561 backend. Fixes bug 16741; bugfix on 0.2.6.3-alpha.
562 - Try harder to normalize the exit status of the Tor process to the
563 standard-provided range. Fixes bug 16975; bugfix on every version
565 - Use libexecinfo on FreeBSD to enable backtrace support. Fixes part
566 of bug 17151; bugfix on 0.2.5.2-alpha. Patch from Marcin Cieślak.
568 o Minor bugfixes (relay):
569 - Ensure that worker threads actually exit when a fatal error or
570 shutdown is indicated. This fix doesn't currently affect the
571 behavior of Tor, because Tor workers never indicates fatal error
572 or shutdown except in the unit tests. Fixes bug 16868; bugfix
574 - Fix a rarely-encountered memory leak when failing to initialize
575 the thread pool. Fixes bug 16631; bugfix on 0.2.6.3-alpha. Patch
577 - Unblock threads before releasing the work queue mutex to ensure
578 predictable scheduling behavior. Fixes bug 16644; bugfix
581 o Minor bugfixes (security, exit policies):
582 - ExitPolicyRejectPrivate now also rejects the relay's published
583 IPv6 address (if any), and any publicly routable IPv4 or IPv6
584 addresses on any local interfaces. ticket 17027. Patch by "teor".
585 Fixes bug 17027; bugfix on 0.2.0.11-alpha.
587 o Minor bugfixes (statistics):
588 - Disregard the ConnDirectionStatistics torrc options when Tor is
589 not a relay since in that mode of operation no sensible data is
590 being collected and because Tor might run into measurement hiccups
591 when running as a client for some time, then becoming a relay.
592 Fixes bug 15604; bugfix on 0.2.2.35.
594 o Minor bugfixes (systemd):
595 - Tor's systemd unit file no longer contains extraneous spaces.
596 These spaces would sometimes confuse tools like deb-systemd-
597 helper. Fixes bug 16162; bugfix on 0.2.5.5-alpha.
599 o Minor bugfixes (test networks):
600 - When self-testing reachability, use ExtendAllowPrivateAddresses to
601 determine if local/private addresses imply reachability. The
602 previous fix used TestingTorNetwork, which implies
603 ExtendAllowPrivateAddresses, but this excluded rare configurations
604 where ExtendAllowPrivateAddresses is set but TestingTorNetwork is
605 not. Fixes bug 15771; bugfix on 0.2.6.1-alpha. Patch by "teor",
606 issue discovered by CJ Ess.
608 o Minor bugfixes (tests, also in 0.2.6.9):
609 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
610 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
612 o Code simplification and refactoring:
613 - Change the function that's called when we need to retry all
614 downloads so that it only reschedules the downloads to happen
615 immediately, rather than launching them all at once itself. This
616 further simplifies Tor's callgraph.
617 - Define WINVER and _WIN32_WINNT centrally, in orconfig.h, in order
618 to ensure they remain consistent and visible everywhere.
619 - Move some format-parsing functions out of crypto.c and
620 crypto_curve25519.c into crypto_format.c and/or util_format.c.
621 - Move the client-only parts of init_keys() into a separate
622 function. Closes ticket 16763.
623 - Move the hacky fallback code out of get_interface_address6() into
624 separate function and get it covered with unit-tests. Resolves
626 - Refactor hidden service client-side cache lookup to intelligently
627 report its various failure cases, and disentangle failure cases
628 involving a lack of introduction points. Closes ticket 14391.
629 - Remove some vestigial workarounds for the MSVC6 compiler. We
630 haven't supported that in ages.
631 - Remove the unused "nulterminate" argument from buf_pullup().
632 - Simplify the microdesc_free() implementation so that it no longer
633 appears (to code analysis tools) to potentially invoke a huge
634 suite of other microdesc functions.
635 - Simply the control graph further by deferring the inner body of
636 directory_all_unreachable() into a callback. Closes ticket 16762.
637 - The link authentication code has been refactored for better
638 testability and reliability. It now uses code generated with the
639 "trunnel" binary encoding generator, to reduce the risk of bugs
640 due to programmer error. Done as part of ticket 12498.
641 - Treat the loss of an owning controller as equivalent to a SIGTERM
642 signal. This removes a tiny amount of duplicated code, and
643 simplifies our callgraph. Closes ticket 16788.
644 - Use our own Base64 encoder instead of OpenSSL's, to allow more
645 control over the output. Part of ticket 15652.
646 - When generating an event to send to the controller, we no longer
647 put the event over the network immediately. Instead, we queue
648 these events, and use a Libevent callback to deliver them. This
649 change simplifies Tor's callgraph by reducing the number of
650 functions from which all other Tor functions are reachable. Closes
652 - Wrap Windows-only C files inside '#ifdef _WIN32' so that tools
653 that try to scan or compile every file on Unix won't decide that
657 - Fix capitalization of SOCKS in sample torrc. Closes ticket 15609.
658 - Improve the descriptions of statistics-related torrc options in
659 the manpage to describe rationale and possible uses cases. Fixes
661 - Improve the layout and formatting of ./configure --help messages.
662 Closes ticket 15024. Patch from "cypherpunks".
663 - Include a specific and (hopefully) accurate documentation of the
664 torrc file's meta-format in doc/torrc_format.txt. This is mainly
665 of interest to people writing programs to parse or generate torrc
666 files. This document is not a commitment to long-term
667 compatibility; some aspects of the current format are a bit
668 ridiculous. Closes ticket 2325.
669 - Include the TUNING document in our source tarball. It is referred
670 to in the ChangeLog and an error message. Fixes bug 16929; bugfix
672 - Note that HiddenServicePorts can take a unix domain socket. Closes
674 - Recommend a 40 GB example AccountingMax in torrc.sample rather
675 than a 4 GB max. Closes ticket 16742.
676 - Standardize on the term "server descriptor" in the manual page.
677 Previously, we had used "router descriptor", "server descriptor",
678 and "relay descriptor" interchangeably. Part of ticket 14987.
679 - Advise users on how to configure separate IPv4 and IPv6 exit
680 policies in the manpage and sample torrcs. Related to ticket 16069.
681 - Fix an error in the manual page and comments for
682 TestingDirAuthVoteHSDir[IsStrict], which suggested that a HSDir
683 required "ORPort connectivity". While this is true, it is in no
684 way unique to the HSDir flag. Of all the flags, only HSDirs need a
685 DirPort configured in order for the authorities to assign that
686 particular flag. Patch by "teor". Fixed as part of 14882; bugfix
688 - Fix the usage message of tor-resolve(1) so that it no longer lists
689 the removed -F option. Fixes bug 16913; bugfix on 0.2.2.28-beta.
692 - Remove `USE_OPENSSL_BASE64` and the corresponding fallback code
693 and always use the internal Base64 decoder. The internal decoder
694 has been part of tor since tor-0.2.0.10-alpha, and no one should
695 be using the OpenSSL one. Part of ticket 15652.
696 - Remove the 'tor_strclear()' function; use memwipe() instead.
698 - Remove the code that would try to aggressively flush controller
699 connections while writing to them. This code was introduced in
700 0.1.2.7-alpha, in order to keep output buffers from exceeding
701 their limits. But there is no longer a maximum output buffer size,
702 and flushing data in this way caused some undesirable recursions
703 in our call graph. Closes ticket 16480.
704 - The internal pure-C tor-fw-helper tool is now removed from the Tor
705 distribution, in favor of the pure-Go clone available from
706 https://gitweb.torproject.org/tor-fw-helper.git/ . The libraries
707 used by the C tor-fw-helper are not, in our opinion, very
708 confidence- inspiring in their secure-programming techniques.
712 - Remove the (seldom-used) DynamicDHGroups feature. For anti-
713 fingerprinting we now recommend pluggable transports; for forward-
714 secrecy in TLS, we now use the P-256 group. Closes ticket 13736.
715 - Remove the HidServDirectoryV2 option. Now all relays offer to
716 store hidden service descriptors. Related to 16543.
717 - Remove the VoteOnHidServDirectoriesV2 option, since all
718 authorities have long set it to 1. Closes ticket 16543.
719 - Remove the undocumented "--digests" command-line option. It
720 complicated our build process, caused subtle build issues on
721 multiple platforms, and is now redundant since we started
722 including git version identifiers. Closes ticket 14742.
723 - Tor no longer contains checks for ancient directory cache versions
724 that didn't know about microdescriptors.
725 - Tor no longer contains workarounds for stat files generated by
726 super-old versions of Tor that didn't choose guards sensibly.
729 - The test-network.sh script now supports performance testing.
730 Requires corresponding chutney performance testing changes. Patch
731 by "teor". Closes ticket 14175.
732 - Add a new set of callgraph analysis scripts that use clang to
733 produce a list of which Tor functions are reachable from which
734 other Tor functions. We're planning to use these to help simplify
735 our code structure by identifying illogical dependencies.
736 - Add new 'test-full' and 'test-full-online' targets to run all
737 tests, including integration tests with stem and chutney.
738 - Autodetect CHUTNEY_PATH if the chutney and Tor sources are side-
739 by-side in the same parent directory. Closes ticket 16903. Patch
741 - Document use of coverity, clang static analyzer, and clang dynamic
742 undefined behavior and address sanitizers in doc/HACKING. Include
743 detailed usage instructions in the blacklist. Patch by "teor".
745 - Make "bridges+hs" the default test network. This tests almost all
746 tor functionality during make test-network, while allowing tests
747 to succeed on non-IPv6 systems. Requires chutney commit 396da92 in
748 test-network-bridges-hs. Closes tickets 16945 (tor) and 16946
749 (chutney). Patches by "teor".
750 - Make the test-workqueue test work on Windows by initializing the
751 network before we begin.
752 - New make target (make test-network-all) to run multiple applicable
753 chutney test cases. Patch from Teor; closes 16953.
754 - Now that OpenSSL has its own scrypt implementation, add an unit
755 test that checks for interoperability between libscrypt_scrypt()
756 and OpenSSL's EVP_PBE_scrypt() so that we could not use libscrypt
757 and rely on EVP_PBE_scrypt() whenever possible. Resolves
759 - The link authentication protocol code now has extensive tests.
760 - The relay descriptor signature testing code now has
762 - The test_workqueue program now runs faster, and is enabled by
763 default as a part of "make check".
764 - Unit test dns_resolve(), dns_clip_ttl() and dns_get_expiry_ttl()
765 functions in dns.c. Implements a portion of ticket 16831.
766 - Use environment variables rather than autoconf substitutions to
767 send variables from the build system to the test scripts. This
768 change should be easier to maintain, and cause 'make distcheck' to
769 work better than before. Fixes bug 17148.
770 - When building Tor with testing coverage enabled, run Chutney tests
771 (if any) using the 'tor-cov' coverage binary.
772 - When running test-network or test-stem, check for the absence of
773 stem/chutney before doing any build operations.
774 - Add a test to verify that the compiler does not eliminate our
775 memwipe() implementation. Closes ticket 15377.
776 - Add make rule `check-changes` to verify the format of changes
777 files. Closes ticket 15180.
778 - Add unit tests for control_event_is_interesting(). Add a compile-
779 time check that the number of events doesn't exceed the capacity
780 of control_event_t.event_mask. Closes ticket 15431, checks for
781 bugs similar to 13085. Patch by "teor".
782 - Command-line argument tests moved to Stem. Resolves ticket 14806.
783 - Integrate the ntor, backtrace, and zero-length keys tests into the
784 automake test suite. Closes ticket 15344.
785 - Remove assertions during builds to determine Tor's test coverage.
786 We don't want to trigger these even in assertions, so including
787 them artificially makes our branch coverage look worse than it is.
788 This patch provides the new test-stem-full and coverage-html-full
789 configure options. Implements ticket 15400.
790 - New TestingDirAuthVote{Exit,Guard,HSDir}IsStrict flags to
791 explicitly manage consensus flags in testing networks. Patch by
792 "robgjansen", modified by "teor". Implements part of ticket 14882.
793 - Check for matching value in server response in ntor_ref.py. Fixes
794 bug 15591; bugfix on 0.2.4.8-alpha. Reported and fixed
796 - Set the severity correctly when testing
797 get_interface_addresses_ifaddrs() and
798 get_interface_addresses_win32(), so that the tests fail gracefully
799 instead of triggering an assertion. Fixes bug 15759; bugfix on
800 0.2.6.3-alpha. Reported by Nicolas Derive.
803 Changes in version 0.2.6.10 - 2015-07-12
804 Tor version 0.2.6.10 fixes some significant stability and hidden
805 service client bugs, bulletproofs the cryptography init process, and
806 fixes a bug when using the sandbox code with some older versions of
807 Linux. Everyone running an older version, especially an older version
808 of 0.2.6, should upgrade.
810 o Major bugfixes (hidden service clients, stability):
811 - Stop refusing to store updated hidden service descriptors on a
812 client. This reverts commit 9407040c59218 (which indeed fixed bug
813 14219, but introduced a major hidden service reachability
814 regression detailed in bug 16381). This is a temporary fix since
815 we can live with the minor issue in bug 14219 (it just results in
816 some load on the network) but the regression of 16381 is too much
817 of a setback. First-round fix for bug 16381; bugfix
820 o Major bugfixes (stability):
821 - Stop crashing with an assertion failure when parsing certain kinds
822 of malformed or truncated microdescriptors. Fixes bug 16400;
823 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
824 by "cypherpunks_backup".
825 - Stop random client-side assertion failures that could occur when
826 connecting to a busy hidden service, or connecting to a hidden
827 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
830 o Minor features (geoip):
831 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
832 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
834 o Minor bugfixes (crypto error-handling):
835 - Check for failures from crypto_early_init, and refuse to continue.
836 A previous typo meant that we could keep going with an
837 uninitialized crypto library, and would have OpenSSL initialize
838 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
839 when implementing ticket 4900. Patch by "teor".
841 o Minor bugfixes (Linux seccomp2 sandbox):
842 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
843 these when eventfd2() support is missing. Fixes bug 16363; bugfix
844 on 0.2.6.3-alpha. Patch from "teor".
847 Changes in version 0.2.6.9 - 2015-06-11
848 Tor 0.2.6.9 fixes a regression in the circuit isolation code, increases the
849 requirements for receiving an HSDir flag, and addresses some other small
850 bugs in the systemd and sandbox code. Clients using circuit isolation
851 should upgrade; all directory authorities should upgrade.
853 o Major bugfixes (client-side privacy):
854 - Properly separate out each SOCKSPort when applying stream
855 isolation. The error occurred because each port's session group was
856 being overwritten by a default value when the listener connection
857 was initialized. Fixes bug 16247; bugfix on 0.2.6.3-alpha. Patch
860 o Minor feature (directory authorities, security):
861 - The HSDir flag given by authorities now requires the Stable flag.
862 For the current network, this results in going from 2887 to 2806
863 HSDirs. Also, it makes it harder for an attacker to launch a sybil
864 attack by raising the effort for a relay to become Stable which
865 takes at the very least 7 days to do so and by keeping the 96
866 hours uptime requirement for HSDir. Implements ticket 8243.
868 o Minor bugfixes (compilation):
869 - Build with --enable-systemd correctly when libsystemd is
870 installed, but systemd is not. Fixes bug 16164; bugfix on
871 0.2.6.3-alpha. Patch from Peter Palfrader.
873 o Minor bugfixes (Linux seccomp2 sandbox):
874 - Fix sandboxing to work when running as a relaymby renaming of
875 secret_id_key, and allowing the eventfd2 and futex syscalls. Fixes
876 bug 16244; bugfix on 0.2.6.1-alpha. Patch by Peter Palfrader.
877 - Allow systemd connections to work with the Linux seccomp2 sandbox
878 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
881 o Minor bugfixes (tests):
882 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
883 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
886 Changes in version 0.2.6.8 - 2015-05-21
887 Tor 0.2.6.8 fixes a bit of dodgy code in parsing INTRODUCE2 cells, and
888 fixes an authority-side bug in assigning the HSDir flag. All directory
889 authorities should upgrade.
891 o Major bugfixes (hidden services, backport from 0.2.7.1-alpha):
892 - Revert commit that made directory authorities assign the HSDir
893 flag to relay without a DirPort; this was bad because such relays
894 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
895 on tor-0.2.6.3-alpha.
897 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
898 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
899 a client authorized hidden service. Fixes bug 15823; bugfix
902 o Minor features (geoip):
903 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
904 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
908 Changes in version 0.2.6.7 - 2015-04-06
909 Tor 0.2.6.7 fixes two security issues that could be used by an
910 attacker to crash hidden services, or crash clients visiting hidden
911 services. Hidden services should upgrade as soon as possible; clients
912 should upgrade whenever packages become available.
914 This release also contains two simple improvements to make hidden
915 services a bit less vulnerable to denial-of-service attacks.
917 o Major bugfixes (security, hidden service):
918 - Fix an issue that would allow a malicious client to trigger an
919 assertion failure and halt a hidden service. Fixes bug 15600;
920 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
921 - Fix a bug that could cause a client to crash with an assertion
922 failure when parsing a malformed hidden service descriptor. Fixes
923 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
925 o Minor features (DoS-resistance, hidden service):
926 - Introduction points no longer allow multiple INTRODUCE1 cells to
927 arrive on the same circuit. This should make it more expensive for
928 attackers to overwhelm hidden services with introductions.
929 Resolves ticket 15515.
930 - Decrease the amount of reattempts that a hidden service performs
931 when its rendezvous circuits fail. This reduces the computational
932 cost for running a hidden service under heavy load. Resolves
936 Changes in version 0.2.5.12 - 2015-04-06
937 Tor 0.2.5.12 backports two fixes from 0.2.6.7 for security issues that
938 could be used by an attacker to crash hidden services, or crash clients
939 visiting hidden services. Hidden services should upgrade as soon as
940 possible; clients should upgrade whenever packages become available.
942 This release also backports a simple improvement to make hidden
943 services a bit less vulnerable to denial-of-service attacks.
945 o Major bugfixes (security, hidden service):
946 - Fix an issue that would allow a malicious client to trigger an
947 assertion failure and halt a hidden service. Fixes bug 15600;
948 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
949 - Fix a bug that could cause a client to crash with an assertion
950 failure when parsing a malformed hidden service descriptor. Fixes
951 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
953 o Minor features (DoS-resistance, hidden service):
954 - Introduction points no longer allow multiple INTRODUCE1 cells to
955 arrive on the same circuit. This should make it more expensive for
956 attackers to overwhelm hidden services with introductions.
957 Resolves ticket 15515.
960 Changes in version 0.2.4.27 - 2015-04-06
961 Tor 0.2.4.27 backports two fixes from 0.2.6.7 for security issues that
962 could be used by an attacker to crash hidden services, or crash clients
963 visiting hidden services. Hidden services should upgrade as soon as
964 possible; clients should upgrade whenever packages become available.
966 This release also backports a simple improvement to make hidden
967 services a bit less vulnerable to denial-of-service attacks.
969 o Major bugfixes (security, hidden service):
970 - Fix an issue that would allow a malicious client to trigger an
971 assertion failure and halt a hidden service. Fixes bug 15600;
972 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
973 - Fix a bug that could cause a client to crash with an assertion
974 failure when parsing a malformed hidden service descriptor. Fixes
975 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
977 o Minor features (DoS-resistance, hidden service):
978 - Introduction points no longer allow multiple INTRODUCE1 cells to
979 arrive on the same circuit. This should make it more expensive for
980 attackers to overwhelm hidden services with introductions.
981 Resolves ticket 15515.
984 Changes in version 0.2.6.6 - 2015-03-24
985 Tor 0.2.6.6 is the first stable release in the 0.2.6 series.
987 It adds numerous safety, security, correctness, and performance
988 improvements. Client programs can be configured to use more kinds of
989 sockets, AutomapHosts works better, the multithreading backend is
990 improved, cell transmission is refactored, test coverage is much
991 higher, more denial-of-service attacks are handled, guard selection is
992 improved to handle long-term guards better, pluggable transports
993 should work a bit better, and some annoying hidden service performance
994 bugs should be addressed.
996 o New compiler and system requirements:
997 - Tor 0.2.6.x requires that your compiler support more of the C99
998 language standard than before. The 'configure' script now detects
999 whether your compiler supports C99 mid-block declarations and
1000 designated initializers. If it does not, Tor will not compile.
1002 We may revisit this requirement if it turns out that a significant
1003 number of people need to build Tor with compilers that don't
1004 bother implementing a 15-year-old standard. Closes ticket 13233.
1005 - Tor no longer supports systems without threading support. When we
1006 began working on Tor, there were several systems that didn't have
1007 threads, or where the thread support wasn't able to run the
1008 threads of a single process on multiple CPUs. That no longer
1009 holds: every system where Tor needs to run well now has threading
1010 support. Resolves ticket 12439.
1012 o Deprecated versions and removed support:
1013 - Tor relays older than 0.2.4.18-rc are no longer allowed to
1014 advertise themselves on the network. Closes ticket 13555.
1015 - Tor clients no longer support connecting to hidden services
1016 running on Tor 0.2.2.x and earlier; the Support022HiddenServices
1017 option has been removed. (There shouldn't be any hidden services
1018 running these versions on the network.) Closes ticket 7803.
1020 o Directory authority changes:
1021 - The directory authority Faravahar has a new IP address. This
1022 closes ticket 14487.
1023 - Remove turtles as a directory authority.
1024 - Add longclaw as a new (v3) directory authority. This implements
1025 ticket 13296. This keeps the directory authority count at 9.
1027 o Major features (bridges):
1028 - Expose the outgoing upstream HTTP/SOCKS proxy to pluggable
1029 transports if they are configured via the "TOR_PT_PROXY"
1030 environment variable. Implements proposal 232. Resolves
1033 o Major features (changed defaults):
1034 - Prevent relay operators from unintentionally running exits: When a
1035 relay is configured as an exit node, we now warn the user unless
1036 the "ExitRelay" option is set to 1. We warn even more loudly if
1037 the relay is configured with the default exit policy, since this
1038 can indicate accidental misconfiguration. Setting "ExitRelay 0"
1039 stops Tor from running as an exit relay. Closes ticket 10067.
1041 o Major features (client performance, hidden services):
1042 - Allow clients to use optimistic data when connecting to a hidden
1043 service, which should remove a round-trip from hidden service
1044 initialization. See proposal 181 for details. Implements
1047 o Major features (directory system):
1048 - Upon receiving an unparseable directory object, if its digest
1049 matches what we expected, then don't try to download it again.
1050 Previously, when we got a descriptor we didn't like, we would keep
1051 trying to download it over and over. Closes ticket 11243.
1052 - When downloading server- or microdescriptors from a directory
1053 server, we no longer launch multiple simultaneous requests to the
1054 same server. This reduces load on the directory servers,
1055 especially when directory guards are in use. Closes ticket 9969.
1056 - When downloading server- or microdescriptors over a tunneled
1057 connection, do not limit the length of our requests to what the
1058 Squid proxy is willing to handle. Part of ticket 9969.
1059 - Authorities can now vote on the correct digests and latest
1060 versions for different software packages. This allows packages
1061 that include Tor to use the Tor authority system as a way to get
1062 notified of updates and their correct digests. Implements proposal
1063 227. Closes ticket 10395.
1065 o Major features (guards):
1066 - Introduce the Guardfraction feature to improves load balancing on
1067 guard nodes. Specifically, it aims to reduce the traffic gap that
1068 guard nodes experience when they first get the Guard flag. This is
1069 a required step if we want to increase the guard lifetime to 9
1070 months or greater. Closes ticket 9321.
1072 o Major features (hidden services):
1073 - Make HS port scanning more difficult by immediately closing the
1074 circuit when a user attempts to connect to a nonexistent port.
1075 Closes ticket 13667.
1076 - Add a HiddenServiceStatistics option that allows Tor relays to
1077 gather and publish statistics about the overall size and volume of
1078 hidden service usage. Specifically, when this option is turned on,
1079 an HSDir will publish an approximate number of hidden services
1080 that have published descriptors to it the past 24 hours. Also, if
1081 a relay has acted as a hidden service rendezvous point, it will
1082 publish the approximate amount of rendezvous cells it has relayed
1083 the past 24 hours. The statistics themselves are obfuscated so
1084 that the exact values cannot be derived. For more details see
1085 proposal 238, "Better hidden service stats from Tor relays". This
1086 feature is currently disabled by default. Implements feature 13192.
1088 o Major features (performance):
1089 - Make the CPU worker implementation more efficient by avoiding the
1090 kernel and lengthening pipelines. The original implementation used
1091 sockets to transfer data from the main thread to the workers, and
1092 didn't allow any thread to be assigned more than a single piece of
1093 work at once. The new implementation avoids communications
1094 overhead by making requests in shared memory, avoiding kernel IO
1095 where possible, and keeping more requests in flight at once.
1096 Implements ticket 9682.
1098 o Major features (relay):
1099 - Raise the minimum acceptable configured bandwidth rate for bridges
1100 to 50 KiB/sec and for relays to 75 KiB/sec. (The old values were
1101 20 KiB/sec.) Closes ticket 13822.
1102 - Complete revision of the code that relays use to decide which cell
1103 to send next. Formerly, we selected the best circuit to write on
1104 each channel, but we didn't select among channels in any
1105 sophisticated way. Now, we choose the best circuits globally from
1106 among those whose channels are ready to deliver traffic.
1108 This patch implements a new inter-cmux comparison API, a global
1109 high/low watermark mechanism and a global scheduler loop for
1110 transmission prioritization across all channels as well as among
1111 circuits on one channel. This schedule is currently tuned to
1112 (tolerantly) avoid making changes in network performance, but it
1113 should form the basis for major circuit performance increases in
1114 the future. Code by Andrea; tuning by Rob Jansen; implements
1117 o Major features (sample torrc):
1118 - Add a new, infrequently-changed "torrc.minimal". This file is
1119 similar to torrc.sample, but it will change as infrequently as
1120 possible, for the benefit of users whose systems prompt them for
1121 intervention whenever a default configuration file is changed.
1122 Making this change allows us to update torrc.sample to be a more
1123 generally useful "sample torrc".
1125 o Major features (security, unix domain sockets):
1126 - Allow SocksPort to be an AF_UNIX Unix Domain Socket. Now high risk
1127 applications can reach Tor without having to create AF_INET or
1128 AF_INET6 sockets, meaning they can completely disable their
1129 ability to make non-Tor network connections. To create a socket of
1130 this type, use "SocksPort unix:/path/to/socket". Implements
1132 - Support mapping hidden service virtual ports to AF_UNIX sockets.
1133 The syntax is "HiddenServicePort 80 unix:/path/to/socket".
1134 Implements ticket 11485.
1136 o Major bugfixes (client, automap):
1137 - Repair automapping with IPv6 addresses. This automapping should
1138 have worked previously, but one piece of debugging code that we
1139 inserted to detect a regression actually caused the regression to
1140 manifest itself again. Fixes bug 13811 and bug 12831; bugfix on
1141 0.2.4.7-alpha. Diagnosed and fixed by Francisco Blas
1144 o Major bugfixes (crash, OSX, security):
1145 - Fix a remote denial-of-service opportunity caused by a bug in
1146 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
1149 o Major bugfixes (directory authorities):
1150 - Do not assign the HSDir flag to relays if they are not Valid, or
1151 currently hibernating. Fixes 12573; bugfix on 0.2.0.10-alpha.
1153 o Major bugfixes (directory bandwidth performance):
1154 - Don't flush the zlib buffer aggressively when compressing
1155 directory information for clients. This should save about 7% of
1156 the bandwidth currently used for compressed descriptors and
1157 microdescriptors. Fixes bug 11787; bugfix on 0.1.1.23.
1159 o Major bugfixes (exit node stability):
1160 - Fix an assertion failure that could occur under high DNS load.
1161 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
1162 diagnosed and fixed by "cypherpunks".
1164 o Major bugfixes (FreeBSD IPFW transparent proxy):
1165 - Fix address detection with FreeBSD transparent proxies, when
1166 "TransProxyType ipfw" is in use. Fixes bug 15064; bugfix
1169 o Major bugfixes (hidden services):
1170 - When closing an introduction circuit that was opened in parallel
1171 with others, don't mark the introduction point as unreachable.
1172 Previously, the first successful connection to an introduction
1173 point would make the other introduction points get marked as
1174 having timed out. Fixes bug 13698; bugfix on 0.0.6rc2.
1176 o Major bugfixes (Linux seccomp2 sandbox):
1177 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
1178 crash during attempts to call wait4. Fixes bug 15088; bugfix on
1179 0.2.5.1-alpha. Patch from "sanic".
1181 o Major bugfixes (mixed relay-client operation):
1182 - When running as a relay and client at the same time (not
1183 recommended), if we decide not to use a new guard because we want
1184 to retry older guards, only close the locally-originating circuits
1185 passing through that guard. Previously we would close all the
1186 circuits through that guard. Fixes bug 9819; bugfix on
1187 0.2.1.1-alpha. Reported by "skruffy".
1189 o Major bugfixes (pluggable transports):
1190 - Initialize the extended OR Port authentication cookie before
1191 launching pluggable transports. This prevents a race condition
1192 that occured when server-side pluggable transports would cache the
1193 authentication cookie before it has been (re)generated. Fixes bug
1194 15240; bugfix on 0.2.5.1-alpha.
1196 o Major bugfixes (relay, stability, possible security):
1197 - Fix a bug that could lead to a relay crashing with an assertion
1198 failure if a buffer of exactly the wrong layout is passed to
1199 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
1200 0.2.0.10-alpha. Patch from "cypherpunks".
1201 - Do not assert if the 'data' pointer on a buffer is advanced to the
1202 very end of the buffer; log a BUG message instead. Only assert if
1203 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
1205 o Minor features (build):
1206 - New --disable-system-torrc compile-time option to prevent Tor from
1207 looking for the system-wide torrc or torrc-defaults files.
1208 Resolves ticket 13037.
1210 o Minor features (client):
1211 - Clients are now willing to send optimistic data (before they
1212 receive a 'connected' cell) to relays of any version. (Relays
1213 without support for optimistic data are no longer supported on the
1214 Tor network.) Resolves ticket 13153.
1216 o Minor features (client):
1217 - Validate hostnames in SOCKS5 requests more strictly. If SafeSocks
1218 is enabled, reject requests with IP addresses as hostnames.
1219 Resolves ticket 13315.
1221 o Minor features (controller):
1222 - Add a "SIGNAL HEARTBEAT" controller command that tells Tor to
1223 write an unscheduled heartbeat message to the log. Implements
1225 - Include SOCKS_USERNAME and SOCKS_PASSWORD values in controller
1226 events so controllers can observe circuit isolation inputs. Closes
1228 - ControlPort now supports the unix:/path/to/socket syntax as an
1229 alternative to the ControlSocket option, for consistency with
1230 SocksPort and HiddenServicePort. Closes ticket 14451.
1231 - New "GETINFO bw-event-cache" to get information about recent
1232 bandwidth events. Closes ticket 14128. Useful for controllers to
1233 get recent bandwidth history after the fix for ticket 13988.
1234 - Messages about problems in the bootstrap process now include
1235 information about the server we were trying to connect to when we
1236 noticed the problem. Closes ticket 15006.
1238 o Minor features (Denial of service resistance):
1239 - Count the total number of bytes used storing hidden service
1240 descriptors against the value of MaxMemInQueues. If we're low on
1241 memory, and more than 20% of our memory is used holding hidden
1242 service descriptors, free them until no more than 10% of our
1243 memory holds hidden service descriptors. Free the least recently
1244 fetched descriptors first. Resolves ticket 13806.
1245 - When we have recently been under memory pressure (over 3/4 of
1246 MaxMemInQueues is allocated), then allocate smaller zlib objects
1247 for small requests. Closes ticket 11791.
1249 o Minor features (directory authorities):
1250 - Don't list relays with a bandwidth estimate of 0 in the consensus.
1251 Implements a feature proposed during discussion of bug 13000.
1252 - In tor-gencert, report an error if the user provides the same
1253 argument more than once.
1254 - If a directory authority can't find a best consensus method in the
1255 votes that it holds, it now falls back to its favorite consensus
1256 method. Previously, it fell back to method 1. Neither of these is
1257 likely to get enough signatures, but "fall back to favorite"
1258 doesn't require us to maintain support an obsolete consensus
1259 method. Implements part of proposal 215.
1261 o Minor features (geoip):
1262 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
1263 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
1266 o Minor features (guard nodes):
1267 - Reduce the time delay before saving guard status to disk from 10
1268 minutes to 30 seconds (or from one hour to 10 minutes if
1269 AvoidDiskWrites is set). Closes ticket 12485.
1271 o Minor features (heartbeat):
1272 - On relays, report how many connections we negotiated using each
1273 version of the Tor link protocols. This information will let us
1274 know if removing support for very old versions of the Tor
1275 protocols is harming the network. Closes ticket 15212.
1277 o Minor features (hidden service):
1278 - Make Sybil attacks against hidden services harder by changing the
1279 minimum time required to get the HSDir flag from 25 hours up to 96
1280 hours. Addresses ticket 14149.
1281 - New option "HiddenServiceAllowUnknownPorts" to allow hidden
1282 services to disable the anti-scanning feature introduced in
1283 0.2.6.2-alpha. With this option not set, a connection to an
1284 unlisted port closes the circuit. With this option set, only a
1285 RELAY_DONE cell is sent. Closes ticket 14084.
1286 - When re-enabling the network, don't try to build introduction
1287 circuits until we have successfully built a circuit. This makes
1288 hidden services come up faster when the network is re-enabled.
1289 Patch from "akwizgran". Closes ticket 13447.
1290 - When we fail to retrieve a hidden service descriptor, send the
1291 controller an "HS_DESC FAILED" controller event. Implements
1293 - New HiddenServiceDirGroupReadable option to cause hidden service
1294 directories and hostname files to be created group-readable. Patch
1295 from "anon", David Stainton, and "meejah". Closes ticket 11291.
1297 o Minor features (interface):
1298 - Implement "-f -" command-line option to read torrc configuration
1299 from standard input, if you don't want to store the torrc file in
1300 the file system. Implements feature 13865.
1302 o Minor features (logging):
1303 - Add a count of unique clients to the bridge heartbeat message.
1304 Resolves ticket 6852.
1305 - Suppress "router info incompatible with extra info" message when
1306 reading extrainfo documents from cache. (This message got loud
1307 around when we closed bug 9812 in 0.2.6.2-alpha.) Closes
1309 - Elevate hidden service authorized-client message from DEBUG to
1310 INFO. Closes ticket 14015.
1311 - On Unix-like systems, you can now use named pipes as the target of
1312 the Log option, and other options that try to append to files.
1313 Closes ticket 12061. Patch from "carlo von lynX".
1314 - When opening a log file at startup, send it every log message that
1315 we generated between startup and opening it. Previously, log
1316 messages that were generated before opening the log file were only
1317 logged to stdout. Closes ticket 6938.
1318 - Add a TruncateLogFile option to overwrite logs instead of
1319 appending to them. Closes ticket 5583.
1320 - Quiet some log messages in the heartbeat and at startup. Closes
1323 o Minor features (portability, Solaris):
1324 - Threads are no longer disabled by default on Solaris; we believe
1325 that the versions of Solaris with broken threading support are all
1326 obsolete by now. Resolves ticket 9495.
1328 o Minor features (relay):
1329 - Re-check our address after we detect a changed IP address from
1330 getsockname(). This ensures that the controller command "GETINFO
1331 address" will report the correct value. Resolves ticket 11582.
1333 - A new AccountingRule option lets Relays set whether they'd like
1334 AccountingMax to be applied separately to inbound and outbound
1335 traffic, or applied to the sum of inbound and outbound traffic.
1336 Resolves ticket 961. Patch by "chobe".
1337 - When identity keypair is generated for first time, log a
1338 congratulatory message that links to the new relay lifecycle
1339 document. Implements feature 10427.
1341 o Minor features (security, memory wiping):
1342 - Ensure we securely wipe keys from memory after
1343 crypto_digest_get_digest and init_curve25519_keypair_from_file
1344 have finished using them. Resolves ticket 13477.
1346 o Minor features (security, out-of-memory handling):
1347 - When handling an out-of-memory condition, allocate less memory for
1348 temporary data structures. Fixes issue 10115.
1349 - When handling an out-of-memory condition, consider more types of
1350 buffers, including those on directory connections, and zlib
1351 buffers. Resolves ticket 11792.
1353 o Minor features (stability):
1354 - Add assertions in our hash-table iteration code to check for
1355 corrupted values that could cause infinite loops. Closes
1358 o Minor features (systemd):
1359 - Various improvements and modernizations in systemd hardening
1360 support. Closes ticket 13805. Patch from Craig Andrews.
1361 - Where supported, when running with systemd, report successful
1362 startup to systemd. Part of ticket 11016. Patch by Michael Scherer.
1363 - When running with systemd, support systemd watchdog messages. Part
1364 of ticket 11016. Patch by Michael Scherer.
1366 o Minor features (testing networks):
1367 - Add the TestingDirAuthVoteExit option, which lists nodes to assign
1368 the "Exit" flag regardless of their uptime, bandwidth, or exit
1369 policy. TestingTorNetwork must be set for this option to have any
1370 effect. Previously, authorities would take up to 35 minutes to
1371 give nodes the Exit flag in a test network. Partially implements
1373 - Drop the minimum RendPostPeriod on a testing network to 5 seconds,
1374 and the default on a testing network to 2 minutes. Drop the
1375 MIN_REND_INITIAL_POST_DELAY on a testing network to 5 seconds, but
1376 keep the default on a testing network at 30 seconds. This reduces
1377 HS bootstrap time to around 25 seconds. Also, change the default
1378 time in test-network.sh to match. Closes ticket 13401. Patch
1380 - Create TestingDirAuthVoteHSDir to correspond to
1381 TestingDirAuthVoteExit/Guard. Ensures that authorities vote the
1382 HSDir flag for the listed relays regardless of uptime or ORPort
1383 connectivity. Respects the value of VoteOnHidServDirectoriesV2.
1384 Partial implementation for ticket 14067. Patch by "teor".
1386 o Minor features (tor2web mode):
1387 - Introduce the config option Tor2webRendezvousPoints, which allows
1388 clients in Tor2webMode to select a specific Rendezvous Point to be
1389 used in HS circuits. This might allow better performance for
1390 Tor2Web nodes. Implements ticket 12844.
1392 o Minor features (transparent proxy):
1393 - Update the transparent proxy option checks to allow for both ipfw
1394 and pf on OS X. Closes ticket 14002.
1395 - Use the correct option when using IPv6 with transparent proxy
1396 support on Linux. Resolves 13808. Patch by Francisco Blas
1399 o Minor features (validation):
1400 - Check all date/time values passed to tor_timegm and
1401 parse_rfc1123_time for validity, taking leap years into account.
1402 Improves HTTP header validation. Implemented with bug 13476.
1403 - In correct_tm(), limit the range of values returned by system
1404 localtime(_r) and gmtime(_r) to be between the years 1 and 8099.
1405 This means we don't have to deal with negative or too large dates,
1406 even if a clock is wrong. Otherwise we might fail to read a file
1407 written by us which includes such a date. Fixes bug 13476.
1408 - Stop allowing invalid address patterns like "*/24" that contain
1409 both a wildcard address and a bit prefix length. This affects all
1410 our address-range parsing code. Fixes bug 7484; bugfix
1413 o Minor bugfixes (bridge clients):
1414 - When configured to use a bridge without an identity digest (not
1415 recommended), avoid launching an extra channel to it when
1416 bootstrapping. Fixes bug 7733; bugfix on 0.2.4.4-alpha.
1418 o Minor bugfixes (bridges):
1419 - When DisableNetwork is set, do not launch pluggable transport
1420 plugins, and if any are running, terminate them. Fixes bug 13213;
1421 bugfix on 0.2.3.6-alpha.
1423 o Minor bugfixes (C correctness):
1424 - Fix several instances of possible integer overflow/underflow/NaN.
1425 Fixes bug 13104; bugfix on 0.2.3.1-alpha and later. Patches
1427 - In circuit_build_times_calculate_timeout() in circuitstats.c,
1428 avoid dividing by zero in the pareto calculations. This traps
1429 under clang's "undefined-trap" sanitizer. Fixes bug 13290; bugfix
1431 - Fix an integer overflow in format_time_interval(). Fixes bug
1432 13393; bugfix on 0.2.0.10-alpha.
1433 - Set the correct day of year value when the system's localtime(_r)
1434 or gmtime(_r) functions fail to set struct tm. Not externally
1435 visible. Fixes bug 13476; bugfix on 0.0.2pre14.
1436 - Avoid unlikely signed integer overflow in tor_timegm on systems
1437 with 32-bit time_t. Fixes bug 13476; bugfix on 0.0.2pre14.
1439 o Minor bugfixes (certificate handling):
1440 - If an authority operator accidentally makes a signing certificate
1441 with a future publication time, do not discard its real signing
1442 certificates. Fixes bug 11457; bugfix on 0.2.0.3-alpha.
1443 - Remove any old authority certificates that have been superseded
1444 for at least two days. Previously, we would keep superseded
1445 certificates until they expired, if they were published close in
1446 time to the certificate that superseded them. Fixes bug 11454;
1447 bugfix on 0.2.1.8-alpha.
1449 o Minor bugfixes (client):
1450 - Fix smartlist_choose_node_by_bandwidth() so that relays with the
1451 BadExit flag are not considered worthy candidates. Fixes bug
1452 13066; bugfix on 0.1.2.3-alpha.
1453 - Use the consensus schedule for downloading consensuses, and not
1454 the generic schedule. Fixes bug 11679; bugfix on 0.2.2.6-alpha.
1455 - Handle unsupported or malformed SOCKS5 requests properly by
1456 responding with the appropriate error message before closing the
1457 connection. Fixes bugs 12971 and 13314; bugfix on 0.0.2pre13.
1459 o Minor bugfixes (client, automapping):
1460 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
1461 no value follows the option. Fixes bug 14142; bugfix on
1462 0.2.4.7-alpha. Patch by "teor".
1463 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
1464 14195; bugfix on 0.1.0.1-rc.
1465 - Prevent changes to other options from removing the wildcard value
1466 "." from "AutomapHostsSuffixes". Fixes bug 12509; bugfix
1468 - Allow MapAddress and AutomapHostsOnResolve to work together when
1469 an address is mapped into another address type (like .onion) that
1470 must be automapped at resolve time. Fixes bug 7555; bugfix
1473 o Minor bugfixes (client, bridges):
1474 - When we are using bridges and we had a network connectivity
1475 problem, only retry connecting to our currently configured
1476 bridges, not all bridges we know about and remember using. Fixes
1477 bug 14216; bugfix on 0.2.2.17-alpha.
1479 o Minor bugfixes (client, DNS):
1480 - Report the correct cached DNS expiration times on SOCKS port or in
1481 DNS replies. Previously, we would report everything as "never
1482 expires." Fixes bug 14193; bugfix on 0.2.3.17-beta.
1483 - Avoid a small memory leak when we find a cached answer for a
1484 reverse DNS lookup in a client-side DNS cache. (Remember, client-
1485 side DNS caching is off by default, and is not recommended.) Fixes
1486 bug 14259; bugfix on 0.2.0.1-alpha.
1488 o Minor bugfixes (client, IPv6):
1489 - Reject socks requests to literal IPv6 addresses when IPv6Traffic
1490 flag is not set; and not because the NoIPv4Traffic flag was set.
1491 Previously we'd looked at the NoIPv4Traffic flag for both types of
1492 literal addresses. Fixes bug 14280; bugfix on 0.2.4.7-alpha.
1494 o Minor bugfixes (client, microdescriptors):
1495 - Use a full 256 bits of the SHA256 digest of a microdescriptor when
1496 computing which microdescriptors to download. This keeps us from
1497 erroneous download behavior if two microdescriptor digests ever
1498 have the same first 160 bits. Fixes part of bug 13399; bugfix
1500 - Reset a router's status if its microdescriptor digest changes,
1501 even if the first 160 bits remain the same. Fixes part of bug
1502 13399; bugfix on 0.2.3.1-alpha.
1504 o Minor bugfixes (client, torrc):
1505 - Stop modifying the value of our DirReqStatistics torrc option just
1506 because we're not a bridge or relay. This bug was causing Tor
1507 Browser users to write "DirReqStatistics 0" in their torrc files
1508 as if they had chosen to change the config. Fixes bug 4244; bugfix
1510 - When GeoIPExcludeUnknown is enabled, do not incorrectly decide
1511 that our options have changed every time we SIGHUP. Fixes bug
1512 9801; bugfix on 0.2.4.10-alpha. Patch from "qwerty1".
1514 o Minor bugfixes (compilation):
1515 - Fix a compilation warning on s390. Fixes bug 14988; bugfix
1517 - Silence clang warnings under --enable-expensive-hardening,
1518 including implicit truncation of 64 bit values to 32 bit, const
1519 char assignment to self, tautological compare, and additional
1520 parentheses around equality tests. Fixes bug 13577; bugfix
1522 - Fix a clang warning about checking whether an address in the
1523 middle of a structure is NULL. Fixes bug 14001; bugfix
1525 - The address of an array in the middle of a structure will always
1526 be non-NULL. clang recognises this and complains. Disable the
1527 tautologous and redundant check to silence this warning. Fixes bug
1528 14001; bugfix on 0.2.1.2-alpha.
1529 - Compile correctly with (unreleased) OpenSSL 1.1.0 headers.
1530 Addresses ticket 14188.
1531 - Build without warnings with the stock OpenSSL srtp.h header, which
1532 has a duplicate declaration of SSL_get_selected_srtp_profile().
1533 Fixes bug 14220; this is OpenSSL's bug, not ours.
1534 - Do not compile any code related to Tor2Web mode when Tor2Web mode
1535 is not enabled at compile time. Previously, this code was included
1536 in a disabled state. See discussion on ticket 12844.
1537 - Allow our configure script to build correctly with autoconf 2.62
1538 again. Fixes bug 12693; bugfix on 0.2.5.2-alpha.
1539 - Improve the error message from ./configure to make it clear that
1540 when asciidoc has not been found, the user will have to either add
1541 --disable-asciidoc argument or install asciidoc. Resolves
1544 o Minor bugfixes (controller):
1545 - Report "down" in response to the "GETINFO entry-guards" command
1546 when relays are down with an unreachable_since value. Previously,
1547 we would report "up". Fixes bug 14184; bugfix on 0.1.2.2-alpha.
1548 - Avoid crashing on a malformed EXTENDCIRCUIT command. Fixes bug
1549 14116; bugfix on 0.2.2.9-alpha.
1551 o Minor bugfixes (controller):
1552 - Return an error when the second or later arguments of the
1553 "setevents" controller command are invalid events. Previously we
1554 would return success while silently skipping invalid events. Fixes
1555 bug 13205; bugfix on 0.2.3.2-alpha. Reported by "fpxnns".
1557 o Minor bugfixes (directory authority):
1558 - Allow directory authorities to fetch more data from one another if
1559 they find themselves missing lots of votes. Previously, they had
1560 been bumping against the 10 MB queued data limit. Fixes bug 14261;
1561 bugfix on 0.1.2.5-alpha.
1562 - Do not attempt to download extrainfo documents which we will be
1563 unable to validate with a matching server descriptor. Fixes bug
1564 13762; bugfix on 0.2.0.1-alpha.
1565 - Fix a bug that was truncating AUTHDIR_NEWDESC events sent to the
1566 control port. Fixes bug 14953; bugfix on 0.2.0.1-alpha.
1567 - Enlarge the buffer to read bwauth generated files to avoid an
1568 issue when parsing the file in dirserv_read_measured_bandwidths().
1569 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
1570 - When running as a v3 directory authority, advertise that you serve
1571 extra-info documents so that clients who want them can find them
1572 from you too. Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
1574 o Minor bugfixes (directory system):
1575 - Always believe that v3 directory authorities serve extra-info
1576 documents, whether they advertise "caches-extra-info" or not.
1577 Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
1578 - Check the BRIDGE_DIRINFO flag bitwise rather than using equality.
1579 Previously, directories offering BRIDGE_DIRINFO and some other
1580 flag (i.e. microdescriptors or extrainfo) would be ignored when
1581 looking for bridges. Partially fixes bug 13163; bugfix
1584 o Minor bugfixes (file handling):
1585 - Stop failing when key files are zero-length. Instead, generate new
1586 keys, and overwrite the empty key files. Fixes bug 13111; bugfix
1587 on all versions of Tor. Patch by "teor".
1588 - Stop generating a fresh .old RSA onion key file when the .old file
1589 is missing. Fixes part of 13111; bugfix on 0.0.6rc1.
1590 - Avoid overwriting .old key files with empty key files.
1591 - Skip loading zero-length extrainfo store, router store, stats,
1592 state, and key files.
1593 - Avoid crashing when trying to reload a torrc specified as a
1594 relative path with RunAsDaemon turned on. Fixes bug 13397; bugfix
1597 o Minor bugfixes (hidden services):
1598 - Close the introduction circuit when we have no more usable intro
1599 points, instead of waiting for it to time out. This also ensures
1600 that no follow-up HS descriptor fetch is triggered when the
1601 circuit eventually times out. Fixes bug 14224; bugfix on 0.0.6.
1602 - When fetching a hidden service descriptor for a down service that
1603 was recently up, do not keep refetching until we try the same
1604 replica twice in a row. Fixes bug 14219; bugfix on 0.2.0.10-alpha.
1605 - Correctly send a controller event when we find that a rendezvous
1606 circuit has finished. Fixes bug 13936; bugfix on 0.1.1.5-alpha.
1607 - Pre-check directory permissions for new hidden-services to avoid
1608 at least one case of "Bug: Acting on config options left us in a
1609 broken state. Dying." Fixes bug 13942; bugfix on 0.0.6pre1.
1610 - When fetching hidden service descriptors, we now check not only
1611 for whether we got the hidden service we had in mind, but also
1612 whether we got the particular descriptors we wanted. This prevents
1613 a class of inefficient but annoying DoS attacks by hidden service
1614 directories. Fixes bug 13214; bugfix on 0.2.1.6-alpha. Reported
1617 o Minor bugfixes (Linux seccomp2 sandbox):
1618 - Make transparent proxy support work along with the seccomp2
1619 sandbox. Fixes part of bug 13808; bugfix on 0.2.5.1-alpha. Patch
1620 by Francisco Blas Izquierdo Riera.
1621 - Fix a memory leak in tor-resolve when running with the sandbox
1622 enabled. Fixes bug 14050; bugfix on 0.2.5.9-rc.
1623 - Allow glibc fatal errors to be sent to stderr before Tor exits.
1624 Previously, glibc would try to write them to /dev/tty, and the
1625 sandbox would trap the call and make Tor exit prematurely. Fixes
1626 bug 14759; bugfix on 0.2.5.1-alpha.
1628 o Minor bugfixes (logging):
1629 - Avoid crashing when there are more log domains than entries in
1630 domain_list. Bugfix on 0.2.3.1-alpha.
1631 - Downgrade warnings about RSA signature failures to info log level.
1632 Emit a warning when an extra info document is found incompatible
1633 with a corresponding router descriptor. Fixes bug 9812; bugfix
1635 - Make connection_ap_handshake_attach_circuit() log the circuit ID
1636 correctly. Fixes bug 13701; bugfix on 0.0.6.
1638 o Minor bugfixes (networking):
1639 - Check for orconns and use connection_or_close_for_error() rather
1640 than connection_mark_for_close() directly in the getsockopt()
1641 failure case of connection_handle_write_impl(). Fixes bug 11302;
1642 bugfix on 0.2.4.4-alpha.
1644 o Minor bugfixes (parsing):
1645 - Stop accepting milliseconds (or other junk) at the end of
1646 descriptor publication times. Fixes bug 9286; bugfix on 0.0.2pre25.
1647 - Support two-number and three-number version numbers correctly, in
1648 case we change the Tor versioning system in the future. Fixes bug
1649 13661; bugfix on 0.0.8pre1.
1651 o Minor bugfixes (portability):
1652 - Fix the ioctl()-based network interface lookup code so that it
1653 will work on systems that have variable-length struct ifreq, for
1655 - Use the correct datatype in the SipHash-2-4 function to prevent
1656 compilers from assuming any sort of alignment. Fixes bug 15436;
1657 bugfix on 0.2.5.3-alpha.
1659 o Minor bugfixes (preventative security, C safety):
1660 - When reading a hexadecimal, base-32, or base-64 encoded value from
1661 a string, always overwrite the whole output buffer. This prevents
1662 some bugs where we would look at (but fortunately, not reveal)
1663 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
1665 - Clear all memory targetted by tor_addr_{to,from}_sockaddr(), not
1666 just the part that's used. This makes it harder for data leak bugs
1667 to occur in the event of other programming failures. Resolves
1670 o Minor bugfixes (relay):
1671 - When generating our family list, remove spaces from around the
1672 entries. Fixes bug 12728; bugfix on 0.2.1.7-alpha.
1673 - If our previous bandwidth estimate was 0 bytes, allow publishing a
1674 new relay descriptor immediately. Fixes bug 13000; bugfix
1677 o Minor bugfixes (shutdown):
1678 - When shutting down, always call event_del() on lingering read or
1679 write events before freeing them. Otherwise, we risk double-frees
1680 or read-after-frees in event_base_free(). Fixes bug 12985; bugfix
1683 o Minor bugfixes (small memory leaks):
1684 - Avoid leaking memory when using IPv6 virtual address mappings.
1685 Fixes bug 14123; bugfix on 0.2.4.7-alpha. Patch by Tom van
1688 o Minor bugfixes (statistics):
1689 - Increase period over which bandwidth observations are aggregated
1690 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
1692 o Minor bugfixes (systemd support):
1693 - Run correctly under systemd with the RunAsDaemon option set. Fixes
1694 part of bug 14141; bugfix on 0.2.5.7-rc. Patch from Tomasz Torcz.
1695 - Inform the systemd supervisor about more changes in the Tor
1696 process status. Implements part of ticket 14141. Patch from
1699 o Minor bugfixes (testing networks):
1700 - Fix TestingDirAuthVoteGuard to properly give out Guard flags in a
1701 testing network. Fixes bug 13064; bugfix on 0.2.5.2-alpha.
1702 - Stop using the default authorities in networks which provide both
1703 AlternateDirAuthority and AlternateBridgeAuthority. Partially
1704 fixes bug 13163; bugfix on 0.2.0.13-alpha.
1706 o Minor bugfixes (testing networks, fast startup):
1707 - Allow Tor to build circuits using a consensus with no exits. If
1708 the consensus has no exits (typical of a bootstrapping test
1709 network), allow Tor to build circuits once enough descriptors have
1710 been downloaded. This assists in bootstrapping a testing Tor
1711 network. Fixes bug 13718; bugfix on 0.2.4.10-alpha. Patch
1713 - When V3AuthVotingInterval is low, give a lower If-Modified-Since
1714 header to directory servers. This allows us to obtain consensuses
1715 promptly when the consensus interval is very short. This assists
1716 in bootstrapping a testing Tor network. Fixes parts of bugs 13718
1717 and 13963; bugfix on 0.2.0.3-alpha. Patch by "teor".
1718 - Stop assuming that private addresses are local when checking
1719 reachability in a TestingTorNetwork. Instead, when testing, assume
1720 all OR connections are remote. (This is necessary due to many test
1721 scenarios running all relays on localhost.) This assists in
1722 bootstrapping a testing Tor network. Fixes bug 13924; bugfix on
1723 0.1.0.1-rc. Patch by "teor".
1724 - Avoid building exit circuits from a consensus with no exits. Now
1725 thanks to our fix for 13718, we accept a no-exit network as not
1726 wholly lost, but we need to remember not to try to build exit
1727 circuits on it. Closes ticket 13814; patch by "teor".
1728 - Stop requiring exits to have non-zero bandwithcapacity in a
1729 TestingTorNetwork. Instead, when TestingMinExitFlagThreshold is 0,
1730 ignore exit bandwidthcapacity. This assists in bootstrapping a
1731 testing Tor network. Fixes parts of bugs 13718 and 13839; bugfix
1732 on 0.2.0.3-alpha. Patch by "teor".
1733 - Add "internal" to some bootstrap statuses when no exits are
1734 available. If the consensus does not contain Exits, Tor will only
1735 build internal circuits. In this case, relevant statuses will
1736 contain the word "internal" as indicated in the Tor control-
1737 spec.txt. When bootstrap completes, Tor will be ready to build
1738 internal circuits. If a future consensus contains Exits, exit
1739 circuits may become available. Fixes part of bug 13718; bugfix on
1740 0.2.4.10-alpha. Patch by "teor".
1741 - Decrease minimum consensus interval to 10 seconds when
1742 TestingTorNetwork is set, or 5 seconds for the first consensus.
1743 Fix assumptions throughout the code that assume larger intervals.
1744 Fixes bugs 13718 and 13823; bugfix on 0.2.0.3-alpha. Patch
1746 - Avoid excluding guards from path building in minimal test
1747 networks, when we're in a test network and excluding guards would
1748 exclude all relays. This typically occurs in incredibly small tor
1749 networks, and those using "TestingAuthVoteGuard *". Fixes part of
1750 bug 13718; bugfix on 0.1.1.11-alpha. Patch by "teor".
1752 o Minor bugfixes (testing):
1753 - Avoid a side-effect in a tor_assert() in the unit tests. Fixes bug
1754 15188; bugfix on 0.1.2.3-alpha. Patch from Tom van der Woerdt.
1755 - Stop spawn test failures due to a race condition between the
1756 SIGCHLD handler updating the process status, and the test reading
1757 it. Fixes bug 13291; bugfix on 0.2.3.3-alpha.
1758 - Avoid passing an extra backslash when creating a temporary
1759 directory for running the unit tests on Windows. Fixes bug 12392;
1760 bugfix on 0.2.2.25-alpha. Patch from Gisle Vanem.
1762 o Minor bugfixes (TLS):
1763 - Check more thoroughly throughout the TLS code for possible
1764 unlogged TLS errors. Possible diagnostic or fix for bug 13319.
1766 o Minor bugfixes (transparent proxy):
1767 - Use getsockname, not getsockopt, to retrieve the address for a
1768 TPROXY-redirected connection. Fixes bug 13796; bugfix
1771 o Minor bugfixes (windows):
1772 - Remove code to special-case handling of NTE_BAD_KEYSET when
1773 acquiring windows CryptoAPI context. This error can't actually
1774 occur for the parameters we're providing. Fixes bug 10816; bugfix
1777 o Minor bugfixes (zlib):
1778 - Avoid truncating a zlib stream when trying to finalize it with an
1779 empty output buffer. Fixes bug 11824; bugfix on 0.1.1.23.
1781 o Code simplification and refactoring:
1782 - Change the entry_is_live() function to take named bitfield
1783 elements instead of an unnamed list of booleans. Closes
1785 - Refactor and unit-test entry_is_time_to_retry() in entrynodes.c.
1786 Resolves ticket 12205.
1787 - Use calloc and reallocarray functions instead of multiply-
1788 then-malloc. This makes it less likely for us to fall victim to an
1789 integer overflow attack when allocating. Resolves ticket 12855.
1790 - Use the standard macro name SIZE_MAX, instead of our
1792 - Document usage of the NO_DIRINFO and ALL_DIRINFO flags clearly in
1793 functions which take them as arguments. Replace 0 with NO_DIRINFO
1794 in a function call for clarity. Seeks to prevent future issues
1796 - Avoid 4 null pointer errors under clang static analysis by using
1797 tor_assert() to prove that the pointers aren't null. Fixes
1799 - Rework the API of policies_parse_exit_policy() to use a bitmask to
1800 represent parsing options, instead of a confusing mess of
1801 booleans. Resolves ticket 8197.
1802 - Introduce a helper function to parse ExitPolicy in
1803 or_options_t structure.
1804 - Move fields related to isolating and configuring client ports into
1805 a shared structure. Previously, they were duplicated across
1806 port_cfg_t, listener_connection_t, and edge_connection_t. Failure
1807 to copy them correctly had been the cause of at least one bug in
1808 the past. Closes ticket 8546.
1809 - Refactor the get_interface_addresses_raw() doom-function into
1810 multiple smaller and simpler subfunctions. Cover the resulting
1811 subfunctions with unit-tests. Fixes a significant portion of
1813 - Remove workaround in dirserv_thinks_router_is_hs_dir() that was
1814 only for version <= 0.2.2.24 which is now deprecated. Closes
1816 - Remove a test for a long-defunct broken version-one
1818 - Refactor main loop to extract the 'loop' part. This makes it
1819 easier to run Tor under Shadow. Closes ticket 15176.
1820 - Stop using can_complete_circuits as a global variable; access it
1821 with a function instead.
1822 - Avoid using operators directly as macro arguments: this lets us
1823 apply coccinelle transformations to our codebase more directly.
1824 Closes ticket 13172.
1825 - Combine the functions used to parse ClientTransportPlugin and
1826 ServerTransportPlugin into a single function. Closes ticket 6456.
1827 - Add inline functions and convenience macros for inspecting channel
1828 state. Refactor the code to use convenience macros instead of
1829 checking channel state directly. Fixes issue 7356.
1830 - Document all members of was_router_added_t and rename
1831 ROUTER_WAS_NOT_NEW to ROUTER_IS_ALREADY_KNOWN to make it less
1832 confusable with ROUTER_WAS_TOO_OLD. Fixes issue 13644.
1833 - In connection_exit_begin_conn(), use END_CIRC_REASON_TORPROTOCOL
1834 constant instead of hardcoded value. Fixes issue 13840.
1835 - Refactor our generic strmap and digestmap types into a single
1836 implementation, so that we can add a new digest256map
1840 - Add a doc/TUNING document with tips for handling large numbers of
1841 TCP connections when running busy Tor relay. Update the warning
1842 message to point to this file when running out of sockets
1843 operating system is allowing to use simultaneously. Resolves
1845 - Adding section on OpenBSD to our TUNING document. Thanks to mmcc
1846 for writing the OpenBSD-specific tips. Resolves ticket 13702.
1847 - Make the tor-resolve documentation match its help string and its
1848 options. Resolves part of ticket 14325.
1849 - Log a more useful error message from tor-resolve when failing to
1850 look up a hidden service address. Resolves part of ticket 14325.
1851 - Document the bridge-authority-only 'networkstatus-bridges' file.
1852 Closes ticket 13713; patch from "tom".
1853 - Fix typo in PredictedPortsRelevanceTime option description in
1854 manpage. Resolves issue 13707.
1855 - Stop suggesting that users specify relays by nickname: it isn't a
1856 good idea. Also, properly cross-reference how to specify relays in
1857 all parts of manual documenting options that take a list of
1858 relays. Closes ticket 13381.
1859 - Clarify the HiddenServiceDir option description in manpage to make
1860 it clear that relative paths are taken with respect to the current
1861 working directory. Also clarify that this behavior is not
1862 guaranteed to remain indefinitely. Fixes issue 13913.
1864 o Distribution (systemd):
1865 - systemd unit file: only allow tor to write to /var/lib/tor and
1866 /var/log/tor. The rest of the filesystem is accessible for reading
1867 only. Patch by intrigeri; resolves ticket 12751.
1868 - systemd unit file: ensure that the process and all its children
1869 can never gain new privileges. Patch by intrigeri; resolves
1871 - systemd unit file: set up /var/run/tor as writable for the Tor
1872 service. Patch by intrigeri; resolves ticket 13196.
1874 o Downgraded warnings:
1875 - Don't warn when we've attempted to contact a relay using the wrong
1876 ntor onion key. Closes ticket 9635.
1879 - Remove some lingering dead code that once supported mempools.
1880 Mempools were disabled by default in 0.2.5, and removed entirely
1881 in 0.2.6.3-alpha. Closes more of ticket 14848; patch
1884 o Removed features (directory authorities):
1885 - Remove code that prevented authorities from listing Tor relays
1886 affected by CVE-2011-2769 as guards. These relays are already
1887 rejected altogether due to the minimum version requirement of
1888 0.2.3.16-alpha. Closes ticket 13152.
1889 - The "AuthDirRejectUnlisted" option no longer has any effect, as
1890 the fingerprints file (approved-routers) has been deprecated.
1891 - Directory authorities do not support being Naming dirauths anymore.
1892 The "NamingAuthoritativeDir" config option is now obsolete.
1893 - Directory authorities do not support giving out the BadDirectory
1895 - Directory authorities no longer advertise or support consensus
1896 methods 1 through 12 inclusive. These consensus methods were
1897 obsolete and/or insecure: maintaining the ability to support them
1898 served no good purpose. Implements part of proposal 215; closes
1902 - To avoid confusion with the "ExitRelay" option, "ExitNode" is no
1903 longer silently accepted as an alias for "ExitNodes".
1904 - The --enable-mempool and --enable-buf-freelists options, which
1905 were originally created to work around bad malloc implementations,
1906 no longer exist. They were off-by-default in 0.2.5. Closes
1908 - We no longer remind the user about configuration options that have
1909 been obsolete since 0.2.3.x or earlier. Patch by Adrien Bak.
1910 - Remove our old, non-weighted bandwidth-based node selection code.
1911 Previously, we used it as a fallback when we couldn't perform
1912 weighted bandwidth-based node selection. But that would only
1913 happen in the cases where we had no consensus, or when we had a
1914 consensus generated by buggy or ancient directory authorities. In
1915 either case, it's better to use the more modern, better maintained
1916 algorithm, with reasonable defaults for the weights. Closes
1918 - Remove the --disable-curve25519 configure option. Relays and
1919 clients now are required to support curve25519 and the
1921 - The old "StrictEntryNodes" and "StrictExitNodes" options, which
1922 used to be deprecated synonyms for "StrictNodes", are now marked
1923 obsolete. Resolves ticket 12226.
1924 - Clients don't understand the BadDirectory flag in the consensus
1925 anymore, and ignore it.
1927 o Removed platform support:
1928 - We no longer include special code to build on Windows CE; as far
1929 as we know, nobody has used Tor on Windows CE in a very long time.
1930 Closes ticket 11446.
1932 o Testing (test-network.sh):
1933 - Stop using "echo -n", as some shells' built-in echo doesn't
1934 support "-n". Instead, use "/bin/echo -n". Partially fixes
1936 - Stop an apparent test-network hang when used with make -j2. Fixes
1938 - Add a --delay option to test-network.sh, which configures the
1939 delay before the chutney network tests for data transmission.
1940 Partially implements ticket 13161.
1943 - Test that tor does not fail when key files are zero-length. Check
1944 that tor generates new keys, and overwrites the empty key files.
1945 - Test that tor generates new keys when keys are missing
1946 (existing behavior).
1947 - Test that tor does not overwrite key files that already contain
1948 data (existing behavior). Tests bug 13111. Patch by "teor".
1949 - New "make test-stem" target to run stem integration tests.
1950 Requires that the "STEM_SOURCE_DIR" environment variable be set.
1951 Closes ticket 14107.
1952 - Make the test_cmdline_args.py script work correctly on Windows.
1953 Patch from Gisle Vanem.
1954 - Move the slower unit tests into a new "./src/test/test-slow"
1955 binary that can be run independently of the other tests. Closes
1957 - New tests for many parts of channel, relay, and circuitmux
1958 functionality. Code by Andrea; part of 9262.
1959 - New tests for parse_transport_line(). Part of ticket 6456.
1960 - In the unit tests, use chgrp() to change the group of the unit
1961 test temporary directory to the current user, so that the sticky
1962 bit doesn't interfere with tests that check directory groups.
1964 - Add unit tests for resolve_my_addr(). Part of ticket 12376; patch
1966 - Refactor the function that chooses guard nodes so that it can more
1967 easily be tested; write some tests for it.
1968 - Fix and re-enable the fgets_eagain unit test. Fixes bug 12503;
1969 bugfix on 0.2.3.1-alpha. Patch from "cypherpunks."
1970 - Create unit tests for format_time_interval(). With bug 13393.
1971 - Add unit tests for tor_timegm signed overflow, tor_timegm and
1972 parse_rfc1123_time validity checks, correct_tm year clamping. Unit
1973 tests (visible) fixes in bug 13476.
1974 - Add a "coverage-html" make target to generate HTML-visualized
1975 coverage results when building with --enable-coverage. (Requires
1976 lcov.) Patch from Kevin Murray.
1977 - Enable the backtrace handler (where supported) when running the
1979 - Revise all unit tests that used the legacy test_* macros to
1980 instead use the recommended tt_* macros. This patch was generated
1981 with coccinelle, to avoid manual errors. Closes ticket 13119.
1983 Changes in version 0.2.5.11 - 2015-03-17
1984 Tor 0.2.5.11 is the second stable release in the 0.2.5 series.
1986 It backports several bugfixes from the 0.2.6 branch, including a
1987 couple of medium-level security fixes for relays and exit nodes.
1988 It also updates the list of directory authorities.
1990 o Directory authority changes:
1991 - Remove turtles as a directory authority.
1992 - Add longclaw as a new (v3) directory authority. This implements
1993 ticket 13296. This keeps the directory authority count at 9.
1994 - The directory authority Faravahar has a new IP address. This
1995 closes ticket 14487.
1997 o Major bugfixes (crash, OSX, security):
1998 - Fix a remote denial-of-service opportunity caused by a bug in
1999 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
2002 o Major bugfixes (relay, stability, possible security):
2003 - Fix a bug that could lead to a relay crashing with an assertion
2004 failure if a buffer of exactly the wrong layout was passed to
2005 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
2006 0.2.0.10-alpha. Patch from 'cypherpunks'.
2007 - Do not assert if the 'data' pointer on a buffer is advanced to the
2008 very end of the buffer; log a BUG message instead. Only assert if
2009 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
2011 o Major bugfixes (exit node stability):
2012 - Fix an assertion failure that could occur under high DNS load.
2013 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
2014 diagnosed and fixed by "cypherpunks".
2016 o Major bugfixes (Linux seccomp2 sandbox):
2017 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
2018 crash during attempts to call wait4. Fixes bug 15088; bugfix on
2019 0.2.5.1-alpha. Patch from "sanic".
2021 o Minor features (controller):
2022 - New "GETINFO bw-event-cache" to get information about recent
2023 bandwidth events. Closes ticket 14128. Useful for controllers to
2024 get recent bandwidth history after the fix for ticket 13988.
2026 o Minor features (geoip):
2027 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
2028 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
2031 o Minor bugfixes (client, automapping):
2032 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
2033 no value follows the option. Fixes bug 14142; bugfix on
2034 0.2.4.7-alpha. Patch by "teor".
2035 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
2036 14195; bugfix on 0.1.0.1-rc.
2038 o Minor bugfixes (compilation):
2039 - Build without warnings with the stock OpenSSL srtp.h header, which
2040 has a duplicate declaration of SSL_get_selected_srtp_profile().
2041 Fixes bug 14220; this is OpenSSL's bug, not ours.
2043 o Minor bugfixes (directory authority):
2044 - Allow directory authorities to fetch more data from one another if
2045 they find themselves missing lots of votes. Previously, they had
2046 been bumping against the 10 MB queued data limit. Fixes bug 14261;
2047 bugfix on 0.1.2.5-alpha.
2048 - Enlarge the buffer to read bwauth generated files to avoid an
2049 issue when parsing the file in dirserv_read_measured_bandwidths().
2050 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
2052 o Minor bugfixes (statistics):
2053 - Increase period over which bandwidth observations are aggregated
2054 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
2056 o Minor bugfixes (preventative security, C safety):
2057 - When reading a hexadecimal, base-32, or base-64 encoded value from
2058 a string, always overwrite the whole output buffer. This prevents
2059 some bugs where we would look at (but fortunately, not reveal)
2060 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
2064 Changes in version 0.2.4.26 - 2015-03-17
2065 Tor 0.2.4.26 includes an updated list of directory authorities. It
2066 also backports a couple of stability and security bugfixes from 0.2.5
2069 o Directory authority changes:
2070 - Remove turtles as a directory authority.
2071 - Add longclaw as a new (v3) directory authority. This implements
2072 ticket 13296. This keeps the directory authority count at 9.
2073 - The directory authority Faravahar has a new IP address. This
2074 closes ticket 14487.
2076 o Major bugfixes (exit node stability, also in 0.2.6.3-alpha):
2077 - Fix an assertion failure that could occur under high DNS load.
2078 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
2079 diagnosed and fixed by "cypherpunks".
2081 o Major bugfixes (relay, stability, possible security, also in 0.2.6.4-rc):
2082 - Fix a bug that could lead to a relay crashing with an assertion
2083 failure if a buffer of exactly the wrong layout was passed to
2084 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
2085 0.2.0.10-alpha. Patch from 'cypherpunks'.
2086 - Do not assert if the 'data' pointer on a buffer is advanced to the
2087 very end of the buffer; log a BUG message instead. Only assert if
2088 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
2090 o Minor features (geoip):
2091 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
2092 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
2095 Changes in version 0.2.5.10 - 2014-10-24
2096 Tor 0.2.5.10 is the first stable release in the 0.2.5 series.
2098 It adds several new security features, including improved
2099 denial-of-service resistance for relays, new compiler hardening
2100 options, and a system-call sandbox for hardened installations on Linux
2101 (requires seccomp2). The controller protocol has several new features,
2102 resolving IPv6 addresses should work better than before, and relays
2103 should be a little more CPU-efficient. We've added support for more
2104 OpenBSD and FreeBSD transparent proxy types. We've improved the build
2105 system and testing infrastructure to allow unit testing of more parts
2106 of the Tor codebase. Finally, we've addressed several nagging pluggable
2107 transport usability issues, and included numerous other small bugfixes
2108 and features mentioned below.
2110 This release marks end-of-life for Tor 0.2.3.x; those Tor versions
2111 have accumulated many known flaws; everyone should upgrade.
2113 o Major features (security):
2114 - The ntor handshake is now on-by-default, no matter what the
2115 directory authorities recommend. Implements ticket 8561.
2116 - Make the "tor-gencert" tool used by directory authority operators
2117 create 2048-bit signing keys by default (rather than 1024-bit, since
2118 1024-bit is uncomfortably small these days). Addresses ticket 10324.
2119 - Warn about attempts to run hidden services and relays in the same
2120 process: that's probably not a good idea. Closes ticket 12908.
2121 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
2122 today support TLS 1.0 or later, so we can safely turn off support
2123 for this old (and insecure) protocol. Fixes bug 13426.
2125 o Major features (relay security, DoS-resistance):
2126 - When deciding whether we have run out of memory and we need to
2127 close circuits, also consider memory allocated in buffers for
2128 streams attached to each circuit.
2130 This change, which extends an anti-DoS feature introduced in
2131 0.2.4.13-alpha and improved in 0.2.4.14-alpha, lets Tor exit relays
2132 better resist more memory-based DoS attacks than before. Since the
2133 MaxMemInCellQueues option now applies to all queues, it is renamed
2134 to MaxMemInQueues. This feature fixes bug 10169.
2135 - Avoid hash-flooding denial-of-service attacks by using the secure
2136 SipHash-2-4 hash function for our hashtables. Without this
2137 feature, an attacker could degrade performance of a targeted
2138 client or server by flooding their data structures with a large
2139 number of entries to be stored at the same hash table position,
2140 thereby slowing down the Tor instance. With this feature, hash
2141 table positions are derived from a randomized cryptographic key,
2142 and an attacker cannot predict which entries will collide. Closes
2144 - If you don't specify MaxMemInQueues yourself, Tor now tries to
2145 pick a good value based on your total system memory. Previously,
2146 the default was always 8 GB. You can still override the default by
2147 setting MaxMemInQueues yourself. Resolves ticket 11396.
2149 o Major features (bridges and pluggable transports):
2150 - Add support for passing arguments to managed pluggable transport
2151 proxies. Implements ticket 3594.
2152 - Bridges now track GeoIP information and the number of their users
2153 even when pluggable transports are in use, and report usage
2154 statistics in their extra-info descriptors. Resolves tickets 4773
2156 - Don't launch pluggable transport proxies if we don't have any
2157 bridges configured that would use them. Now we can list many
2158 pluggable transports, and Tor will dynamically start one when it
2159 hears a bridge address that needs it. Resolves ticket 5018.
2160 - The bridge directory authority now assigns status flags (Stable,
2161 Guard, etc) to bridges based on thresholds calculated over all
2162 Running bridges. Now bridgedb can finally make use of its features
2163 to e.g. include at least one Stable bridge in its answers. Fixes
2166 o Major features (controller):
2167 - Extend ORCONN controller event to include an "ID" parameter,
2168 and add four new controller event types CONN_BW, CIRC_BW,
2169 CELL_STATS, and TB_EMPTY that show connection and circuit usage.
2170 The new events are emitted in private Tor networks only, with the
2171 goal of being able to better track performance and load during
2172 full-network simulations. Implements proposal 218 and ticket 7359.
2174 o Major features (relay performance):
2175 - Speed up server-side lookups of rendezvous and introduction point
2176 circuits by using hashtables instead of linear searches. These
2177 functions previously accounted between 3 and 7% of CPU usage on
2178 some busy relays. Resolves ticket 9841.
2179 - Avoid wasting CPU when extending a circuit over a channel that is
2180 nearly out of circuit IDs. Previously, we would do a linear scan
2181 over possible circuit IDs before finding one or deciding that we
2182 had exhausted our possibilities. Now, we try at most 64 random
2183 circuit IDs before deciding that we probably won't succeed. Fixes
2184 a possible root cause of ticket 11553.
2186 o Major features (seccomp2 sandbox, Linux only):
2187 - Use the seccomp2 syscall filtering facility on Linux to limit
2188 which system calls Tor can invoke. This is an experimental,
2189 Linux-only feature to provide defense-in-depth against unknown
2190 attacks. To try turning it on, set "Sandbox 1" in your torrc
2191 file. Please be ready to report bugs. We hope to add support
2192 for better sandboxing in the future, including more fine-grained
2193 filters, better division of responsibility, and support for more
2194 platforms. This work has been done by Cristian-Matei Toader for
2195 Google Summer of Code. Resolves tickets 11351 and 11465.
2197 o Major features (testing networks):
2198 - Make testing Tor networks bootstrap better: lower directory fetch
2199 retry schedules and maximum interval without directory requests,
2200 and raise maximum download tries. Implements ticket 6752.
2201 - Add make target 'test-network' to run tests on a Chutney network.
2202 Implements ticket 8530.
2204 o Major features (other):
2205 - On some platforms (currently: recent OSX versions, glibc-based
2206 platforms that support the ELF format, and a few other
2207 Unix-like operating systems), Tor can now dump stack traces
2208 when a crash occurs or an assertion fails. By default, traces
2209 are dumped to stderr (if possible) and to any logs that are
2210 reporting errors. Implements ticket 9299.
2212 o Deprecated versions:
2213 - Tor 0.2.3.x has reached end-of-life; it has received no patches or
2214 attention for some while.
2216 o Major bugfixes (security, directory authorities):
2217 - Directory authorities now include a digest of each relay's
2218 identity key as a part of its microdescriptor.
2220 This is a workaround for bug 11743 (reported by "cypherpunks"),
2221 where Tor clients do not support receiving multiple
2222 microdescriptors with the same SHA256 digest in the same
2223 consensus. When clients receive a consensus like this, they only
2224 use one of the relays. Without this fix, a hostile relay could
2225 selectively disable some client use of target relays by
2226 constructing a router descriptor with a different identity and the
2227 same microdescriptor parameters and getting the authorities to
2228 list it in a microdescriptor consensus. This fix prevents an
2229 attacker from causing a microdescriptor collision, because the
2230 router's identity is not forgeable.
2232 o Major bugfixes (openssl bug workaround):
2233 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
2234 1.0.1j, built with the 'no-ssl3' configuration option. Fixes
2235 bug 13471. This is a workaround for an OpenSSL bug.
2237 o Major bugfixes (client):
2238 - Perform circuit cleanup operations even when circuit
2239 construction operations are disabled (because the network is
2240 disabled, or because there isn't enough directory information).
2241 Previously, when we were not building predictive circuits, we
2242 were not closing expired circuits either. Fixes bug 8387; bugfix on
2243 0.1.1.11-alpha. This bug became visible in 0.2.4.10-alpha when we
2244 became more strict about when we have "enough directory information
2247 o Major bugfixes (client, pluggable transports):
2248 - When managing pluggable transports, use OS notification facilities
2249 to learn if they have crashed, and don't attempt to kill any
2250 process that has already exited. Fixes bug 8746; bugfix
2253 o Major bugfixes (relay denial of service):
2254 - Instead of writing destroy cells directly to outgoing connection
2255 buffers, queue them and intersperse them with other outgoing cells.
2256 This can prevent a set of resource starvation conditions where too
2257 many pending destroy cells prevent data cells from actually getting
2258 delivered. Reported by "oftc_must_be_destroyed". Fixes bug 7912;
2259 bugfix on 0.2.0.1-alpha.
2261 o Major bugfixes (relay):
2262 - Avoid queuing or sending destroy cells for circuit ID zero when we
2263 fail to send a CREATE cell. Fixes bug 12848; bugfix on 0.0.8pre1.
2264 Found and fixed by "cypherpunks".
2265 - Fix ORPort reachability detection on relays running behind a
2266 proxy, by correctly updating the "local" mark on the controlling
2267 channel when changing the address of an or_connection_t after the
2268 handshake. Fixes bug 12160; bugfix on 0.2.4.4-alpha.
2269 - Use a direct dirport connection when uploading non-anonymous
2270 descriptors to the directory authorities. Previously, relays would
2271 incorrectly use tunnel connections under a fairly wide variety of
2272 circumstances. Fixes bug 11469; bugfix on 0.2.4.3-alpha.
2273 - When a circuit accidentally has the same circuit ID for its
2274 forward and reverse direction, correctly detect the direction of
2275 cells using that circuit. Previously, this bug made roughly one
2276 circuit in a million non-functional. Fixes bug 12195; this is a
2277 bugfix on every version of Tor.
2279 o Minor features (security):
2280 - New --enable-expensive-hardening option to enable security
2281 hardening options that consume nontrivial amounts of CPU and
2282 memory. Right now, this includes AddressSanitizer and UbSan, which
2283 are supported in newer versions of GCC and Clang. Closes ticket
2285 - Authorities now assign the Guard flag to the fastest 25% of the
2286 network (it used to be the fastest 50%). Also raise the consensus
2287 weight that guarantees the Guard flag from 250 to 2000. For the
2288 current network, this results in about 1100 guards, down from 2500.
2289 This step paves the way for moving the number of entry guards
2290 down to 1 (proposal 236) while still providing reasonable expected
2291 performance for most users. Implements ticket 12690.
2293 o Minor features (security, memory management):
2294 - Memory allocation tricks (mempools and buffer freelists) are now
2295 disabled by default. You can turn them back on with
2296 --enable-mempools and --enable-buf-freelists respectively. We're
2297 disabling these features because malloc performance is good enough
2298 on most platforms, and a similar feature in OpenSSL exacerbated
2299 exploitation of the Heartbleed attack. Resolves ticket 11476.
2301 o Minor features (bridge client):
2302 - Report a more useful failure message when we can't connect to a
2303 bridge because we don't have the right pluggable transport
2304 configured. Resolves ticket 9665. Patch from Fábio J. Bertinatto.
2306 o Minor features (bridge):
2307 - Add an ExtORPortCookieAuthFileGroupReadable option to make the
2308 cookie file for the ExtORPort g+r by default.
2310 o Minor features (bridges, pluggable transports):
2311 - Bridges now write the SHA1 digest of their identity key
2312 fingerprint (that is, a hash of a hash of their public key) to
2313 notice-level logs, and to a new hashed-fingerprint file. This
2314 information will help bridge operators look up their bridge in
2315 Globe and similar tools. Resolves ticket 10884.
2316 - Improve the message that Tor displays when running as a bridge
2317 using pluggable transports without an Extended ORPort listener.
2318 Also, log the message in the log file too. Resolves ticket 11043.
2319 - Add threshold cutoffs to the networkstatus document created by
2320 the Bridge Authority. Fixes bug 1117.
2321 - On Windows, spawn background processes using the CREATE_NO_WINDOW
2322 flag. Now Tor Browser Bundle 3.5 with pluggable transports enabled
2323 doesn't pop up a blank console window. (In Tor Browser Bundle 2.x,
2324 Vidalia set this option for us.) Implements ticket 10297.
2326 o Minor features (build):
2327 - The configure script has a --disable-seccomp option to turn off
2328 support for libseccomp on systems that have it, in case it (or
2329 Tor's use of it) is broken. Resolves ticket 11628.
2330 - Assume that a user using ./configure --host wants to cross-compile,
2331 and give an error if we cannot find a properly named
2332 tool-chain. Add a --disable-tool-name-check option to proceed
2333 nevertheless. Addresses ticket 9869. Patch by Benedikt Gollatz.
2334 - If we run ./configure and the compiler recognizes -fstack-protector
2335 but the linker rejects it, warn the user about a potentially missing
2336 libssp package. Addresses ticket 9948. Patch from Benedikt Gollatz.
2337 - Add support for `--library-versions` flag. Implements ticket 6384.
2338 - Return the "unexpected sendme" warnings to a warn severity, but make
2339 them rate limited, to help diagnose ticket 8093.
2340 - Detect a missing asciidoc, and warn the user about it, during
2341 configure rather than at build time. Fixes issue 6506. Patch from
2344 o Minor features (client):
2345 - Add a new option, PredictedPortsRelevanceTime, to control how long
2346 after having received a request to connect to a given port Tor
2347 will try to keep circuits ready in anticipation of future requests
2348 for that port. Patch from "unixninja92"; implements ticket 9176.
2350 o Minor features (config options and command line):
2351 - Add an --allow-missing-torrc commandline option that tells Tor to
2352 run even if the configuration file specified by -f is not available.
2353 Implements ticket 10060.
2354 - Add support for the TPROXY transparent proxying facility on Linux.
2355 See documentation for the new TransProxyType option for more
2356 details. Implementation by "thomo". Closes ticket 10582.
2358 o Minor features (config options):
2359 - Config (torrc) lines now handle fingerprints which are missing
2360 their initial '$'. Resolves ticket 4341; improvement over 0.0.9pre5.
2361 - Support a --dump-config option to print some or all of the
2362 configured options. Mainly useful for debugging the command-line
2363 option parsing code. Helps resolve ticket 4647.
2364 - Raise awareness of safer logging: notify user of potentially
2365 unsafe config options, like logging more verbosely than severity
2366 "notice" or setting SafeLogging to 0. Resolves ticket 5584.
2367 - Add a new configuration option TestingV3AuthVotingStartOffset
2368 that bootstraps a network faster by changing the timing for
2369 consensus votes. Addresses ticket 8532.
2370 - Add a new torrc option "ServerTransportOptions" that allows
2371 bridge operators to pass configuration parameters to their
2372 pluggable transports. Resolves ticket 8929.
2373 - The config (torrc) file now accepts bandwidth and space limits in
2374 bits as well as bytes. (Anywhere that you can say "2 Kilobytes",
2375 you can now say "16 kilobits", and so on.) Resolves ticket 9214.
2378 o Minor features (controller):
2379 - Make the entire exit policy available from the control port via
2380 GETINFO exit-policy/*. Implements enhancement 7952. Patch from
2382 - Because of the fix for ticket 11396, the real limit for memory
2383 usage may no longer match the configured MaxMemInQueues value. The
2384 real limit is now exposed via GETINFO limits/max-mem-in-queues.
2385 - Add a new "HS_DESC" controller event that reports activities
2386 related to hidden service descriptors. Resolves ticket 8510.
2387 - New "DROPGUARDS" controller command to forget all current entry
2388 guards. Not recommended for ordinary use, since replacing guards
2389 too frequently makes several attacks easier. Resolves ticket 9934;
2391 - Implement the TRANSPORT_LAUNCHED control port event that
2392 notifies controllers about new launched pluggable
2393 transports. Resolves ticket 5609.
2395 o Minor features (diagnostic):
2396 - When logging a warning because of bug 7164, additionally check the
2397 hash table for consistency (as proposed on ticket 11737). This may
2398 help diagnose bug 7164.
2399 - When we log a heartbeat, log how many one-hop circuits we have
2400 that are at least 30 minutes old, and log status information about
2401 a few of them. This is an attempt to track down bug 8387.
2402 - When encountering an unexpected CR while writing text to a file on
2403 Windows, log the name of the file. Should help diagnosing
2405 - Give more specific warnings when a client notices that an onion
2406 handshake has failed. Fixes ticket 9635.
2407 - Add significant new logging code to attempt to diagnose bug 12184,
2408 where relays seem to run out of available circuit IDs.
2409 - Improve the diagnostic log message for bug 8387 even further to
2410 try to improve our odds of figuring out why one-hop directory
2411 circuits sometimes do not get closed.
2412 - Add more log messages to diagnose bug 7164, which causes
2413 intermittent "microdesc_free() called but md was still referenced"
2414 warnings. We now include more information, to figure out why we
2415 might be cleaning a microdescriptor for being too old if it's
2416 still referenced by a live node_t object.
2417 - Log current accounting state (bytes sent and received + remaining
2418 time for the current accounting period) in the relay's heartbeat
2419 message. Implements ticket 5526; patch from Peter Retzlaff.
2421 o Minor features (geoip):
2422 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
2425 o Minor features (interface):
2426 - Generate a warning if any ports are listed in the SocksPolicy,
2427 DirPolicy, AuthDirReject, AuthDirInvalid, AuthDirBadDir, or
2428 AuthDirBadExit options. (These options only support address
2429 ranges.) Fixes part of ticket 11108.
2431 o Minor features (kernel API usage):
2432 - Use the SOCK_NONBLOCK socket type, if supported, to open nonblocking
2433 sockets in a single system call. Implements ticket 5129.
2435 o Minor features (log messages):
2436 - When ServerTransportPlugin is set on a bridge, Tor can write more
2437 useful statistics about bridge use in its extrainfo descriptors,
2438 but only if the Extended ORPort ("ExtORPort") is set too. Add a
2439 log message to inform the user in this case. Resolves ticket 9651.
2440 - When receiving a new controller connection, log the origin address.
2441 Resolves ticket 9698; patch from "sigpipe".
2442 - When logging OpenSSL engine status at startup, log the status of
2443 more engines. Fixes ticket 10043; patch from Joshua Datko.
2445 o Minor features (log verbosity):
2446 - Demote the message that we give when a flushing connection times
2447 out for too long from NOTICE to INFO. It was usually meaningless.
2448 Resolves ticket 5286.
2449 - Don't log so many notice-level bootstrapping messages at startup
2450 about downloading descriptors. Previously, we'd log a notice
2451 whenever we learned about more routers. Now, we only log a notice
2452 at every 5% of progress. Fixes bug 9963.
2453 - Warn less verbosely when receiving a malformed
2454 ESTABLISH_RENDEZVOUS cell. Fixes ticket 11279.
2456 o Minor features (performance):
2457 - If we're using the pure-C 32-bit curve25519_donna implementation
2458 of curve25519, build it with the -fomit-frame-pointer option to
2459 make it go faster on register-starved hosts. This improves our
2460 handshake performance by about 6% on i386 hosts without nacl.
2463 o Minor features (relay):
2464 - If a circuit timed out for at least 3 minutes, check if we have a
2465 new external IP address, and publish a new descriptor with the new
2466 IP address if it changed. Resolves ticket 2454.
2468 o Minor features (testing):
2469 - If Python is installed, "make check" now runs extra tests beyond
2470 the unit test scripts.
2471 - When bootstrapping a test network, sometimes very few relays get
2472 the Guard flag. Now a new option "TestingDirAuthVoteGuard" can
2473 specify a set of relays which should be voted Guard regardless of
2474 their uptime or bandwidth. Addresses ticket 9206.
2476 o Minor features (transparent proxy, *BSD):
2477 - Support FreeBSD's ipfw firewall interface for TransPort ports on
2478 FreeBSD. To enable it, set "TransProxyType ipfw". Resolves ticket
2479 10267; patch from "yurivict".
2480 - Support OpenBSD's divert-to rules with the pf firewall for
2481 transparent proxy ports. To enable it, set "TransProxyType
2482 pf-divert". This allows Tor to run a TransPort transparent proxy
2483 port on OpenBSD 4.4 or later without root privileges. See the
2484 pf.conf(5) manual page for information on configuring pf to use
2485 divert-to rules. Closes ticket 10896; patch from Dana Koch.
2487 o Minor bugfixes (bridge client):
2488 - Stop accepting bridge lines containing hostnames. Doing so would
2489 cause clients to perform DNS requests on the hostnames, which was
2490 not sensible behavior. Fixes bug 10801; bugfix on 0.2.0.1-alpha.
2492 o Minor bugfixes (bridges):
2493 - Avoid potential crashes or bad behavior when launching a
2494 server-side managed proxy with ORPort or ExtORPort temporarily
2495 disabled. Fixes bug 9650; bugfix on 0.2.3.16-alpha.
2496 - Fix a bug where the first connection works to a bridge that uses a
2497 pluggable transport with client-side parameters, but we don't send
2498 the client-side parameters on subsequent connections. (We don't
2499 use any pluggable transports with client-side parameters yet,
2500 but ScrambleSuit will soon become the first one.) Fixes bug 9162;
2501 bugfix on 0.2.0.3-alpha. Based on a patch from "rl1987".
2503 o Minor bugfixes (build, auxiliary programs):
2504 - Stop preprocessing the "torify" script with autoconf, since
2505 it no longer refers to LOCALSTATEDIR. Fixes bug 5505; patch
2507 - The tor-fw-helper program now follows the standard convention and
2508 exits with status code "0" on success. Fixes bug 9030; bugfix on
2509 0.2.3.1-alpha. Patch by Arlo Breault.
2510 - Corrected ./configure advice for what openssl dev package you should
2511 install on Debian. Fixes bug 9207; bugfix on 0.2.0.1-alpha.
2513 o Minor bugfixes (client):
2514 - Avoid "Tried to open a socket with DisableNetwork set" warnings
2515 when starting a client with bridges configured and DisableNetwork
2516 set. (Tor launcher starts Tor with DisableNetwork set the first
2517 time it runs.) Fixes bug 10405; bugfix on 0.2.3.9-alpha.
2518 - Improve the log message when we can't connect to a hidden service
2519 because all of the hidden service directory nodes hosting its
2520 descriptor are excluded. Improves on our fix for bug 10722, which
2521 was a bugfix on 0.2.0.10-alpha.
2522 - Raise a control port warning when we fail to connect to all of
2523 our bridges. Previously, we didn't inform the controller, and
2524 the bootstrap process would stall. Fixes bug 11069; bugfix on
2526 - Exit immediately when a process-owning controller exits.
2527 Previously, tor relays would wait for a little while after their
2528 controller exited, as if they had gotten an INT signal -- but this
2529 was problematic, since there was no feedback for the user. To do a
2530 clean shutdown, controllers should send an INT signal and give Tor
2531 a chance to clean up. Fixes bug 10449; bugfix on 0.2.2.28-beta.
2532 - Stop attempting to connect to bridges before our pluggable
2533 transports are configured (harmless but resulted in some erroneous
2534 log messages). Fixes bug 11156; bugfix on 0.2.3.2-alpha.
2535 - Fix connections to IPv6 addresses over SOCKS5. Previously, we were
2536 generating incorrect SOCKS5 responses, and confusing client
2537 applications. Fixes bug 10987; bugfix on 0.2.4.7-alpha.
2539 o Minor bugfixes (client, DNSPort):
2540 - When using DNSPort, try to respond to AAAA requests with AAAA
2541 answers. Previously, we hadn't looked at the request type when
2542 deciding which answer type to prefer. Fixes bug 10468; bugfix on
2544 - When receiving a DNS query for an unsupported record type, reply
2545 with no answer rather than with a NOTIMPL error. This behavior
2546 isn't correct either, but it will break fewer client programs, we
2547 hope. Fixes bug 10268; bugfix on 0.2.0.1-alpha. Original patch
2550 o Minor bugfixes (client, logging during bootstrap):
2551 - Only report the first fatal bootstrap error on a given OR
2552 connection. This stops us from telling the controller bogus error
2553 messages like "DONE". Fixes bug 10431; bugfix on 0.2.1.1-alpha.
2554 - Avoid generating spurious warnings when starting with
2555 DisableNetwork enabled. Fixes bug 11200 and bug 10405; bugfix on
2558 o Minor bugfixes (closing OR connections):
2559 - If write_to_buf() in connection_write_to_buf_impl_() ever fails,
2560 check if it's an or_connection_t and correctly call
2561 connection_or_close_for_error() rather than
2562 connection_mark_for_close() directly. Fixes bug 11304; bugfix on
2564 - When closing all connections on setting DisableNetwork to 1, use
2565 connection_or_close_normally() rather than closing OR connections
2566 out from under the channel layer. Fixes bug 11306; bugfix on
2569 o Minor bugfixes (code correctness):
2570 - Previously we used two temporary files when writing descriptors to
2571 disk; now we only use one. Fixes bug 1376.
2572 - Remove an erroneous (but impossible and thus harmless) pointer
2573 comparison that would have allowed compilers to skip a bounds
2574 check in channeltls.c. Fixes bugs 10313 and 9980; bugfix on
2575 0.2.0.10-alpha. Noticed by Jared L Wong and David Fifield.
2576 - Fix an always-true assertion in pluggable transports code so it
2577 actually checks what it was trying to check. Fixes bug 10046;
2578 bugfix on 0.2.3.9-alpha. Found by "dcb".
2580 o Minor bugfixes (command line):
2581 - Use a single command-line parser for parsing torrc options on the
2582 command line and for finding special command-line options to avoid
2583 inconsistent behavior for torrc option arguments that have the same
2584 names as command-line options. Fixes bugs 4647 and 9578; bugfix on
2586 - No longer allow 'tor --hash-password' with no arguments. Fixes bug
2587 9573; bugfix on 0.0.9pre5.
2589 o Minor bugfixes (compilation):
2590 - Compile correctly with builds and forks of OpenSSL (such as
2591 LibreSSL) that disable compression. Fixes bug 12602; bugfix on
2592 0.2.1.1-alpha. Patch from "dhill".
2593 - Restore the ability to compile Tor with V2_HANDSHAKE_SERVER
2594 turned off (that is, without support for v2 link handshakes). Fixes
2595 bug 4677; bugfix on 0.2.3.2-alpha. Patch from "piet".
2596 - In routerlist_assert_ok(), don't take the address of a
2597 routerinfo's cache_info member unless that routerinfo is non-NULL.
2598 Fixes bug 13096; bugfix on 0.1.1.9-alpha. Patch by "teor".
2599 - Fix a large number of false positive warnings from the clang
2600 analyzer static analysis tool. This should make real warnings
2601 easier for clang analyzer to find. Patch from "teor". Closes
2603 - Resolve GCC complaints on OpenBSD about discarding constness in
2604 TO_{ORIGIN,OR}_CIRCUIT functions. Fixes part of bug 11633; bugfix
2605 on 0.1.1.23. Patch from Dana Koch.
2606 - Resolve clang complaints on OpenBSD with -Wshorten-64-to-32 due to
2607 treatment of long and time_t as comparable types. Fixes part of
2608 bug 11633. Patch from Dana Koch.
2609 - When deciding whether to build the 64-bit curve25519
2610 implementation, detect platforms where we can compile 128-bit
2611 arithmetic but cannot link it. Fixes bug 11729; bugfix on
2612 0.2.4.8-alpha. Patch from "conradev".
2613 - Fix compilation when DNS_CACHE_DEBUG is enabled. Fixes bug 11761;
2614 bugfix on 0.2.3.13-alpha. Found by "cypherpunks".
2615 - Fix compilation with dmalloc. Fixes bug 11605; bugfix
2617 - Build and run correctly on systems like OpenBSD-current that have
2618 patched OpenSSL to remove get_cipher_by_char and/or its
2619 implementations. Fixes issue 13325.
2621 o Minor bugfixes (controller and command-line):
2622 - If changing a config option via "setconf" fails in a recoverable
2623 way, we used to nonetheless write our new control ports to the
2624 file described by the "ControlPortWriteToFile" option. Now we only
2625 write out that file if we successfully switch to the new config
2626 option. Fixes bug 5605; bugfix on 0.2.2.26-beta. Patch from "Ryman".
2628 o Minor bugfixes (directory server):
2629 - No longer accept malformed http headers when parsing urls from
2630 headers. Now we reply with Bad Request ("400"). Fixes bug 2767;
2631 bugfix on 0.0.6pre1.
2632 - When sending a compressed set of descriptors or microdescriptors,
2633 make sure to finalize the zlib stream. Previously, we would write
2634 all the compressed data, but if the last descriptor we wanted to
2635 send was missing or too old, we would not mark the stream as
2636 finished. This caused problems for decompression tools. Fixes bug
2637 11648; bugfix on 0.1.1.23.
2639 o Minor bugfixes (hidden service):
2640 - Only retry attempts to connect to a chosen rendezvous point 8
2641 times, not 30. Fixes bug 4241; bugfix on 0.1.0.1-rc.
2643 o Minor bugfixes (interface):
2644 - Reject relative control socket paths and emit a warning. Previously,
2645 single-component control socket paths would be rejected, but Tor
2646 would not log why it could not validate the config. Fixes bug 9258;
2647 bugfix on 0.2.3.16-alpha.
2649 o Minor bugfixes (log messages):
2650 - Fix a bug where clients using bridges would report themselves
2651 as 50% bootstrapped even without a live consensus document.
2652 Fixes bug 9922; bugfix on 0.2.1.1-alpha.
2653 - Suppress a warning where, if there's only one directory authority
2654 in the network, we would complain that votes and signatures cannot
2655 be uploaded to other directory authorities. Fixes bug 10842;
2656 bugfix on 0.2.2.26-beta.
2657 - Report bootstrapping progress correctly when we're downloading
2658 microdescriptors. We had updated our "do we have enough microdescs
2659 to begin building circuits?" logic most recently in 0.2.4.10-alpha
2660 (see bug 5956), but we left the bootstrap status event logic at
2661 "how far through getting 1/4 of them are we?" Fixes bug 9958;
2662 bugfix on 0.2.2.36, which is where they diverged (see bug 5343).
2664 o Minor bugfixes (logging):
2665 - Downgrade "Unexpected onionskin length after decryption" warning
2666 to a protocol-warn, since there's nothing relay operators can do
2667 about a client that sends them a malformed create cell. Resolves
2668 bug 12996; bugfix on 0.0.6rc1.
2669 - Log more specific warnings when we get an ESTABLISH_RENDEZVOUS
2670 cell on a cannibalized or non-OR circuit. Resolves ticket 12997.
2671 - When logging information about an EXTEND2 or EXTENDED2 cell, log
2672 their names correctly. Fixes part of bug 12700; bugfix
2674 - When logging information about a relay cell whose command we don't
2675 recognize, log its command as an integer. Fixes part of bug 12700;
2676 bugfix on 0.2.1.10-alpha.
2677 - Escape all strings from the directory connection before logging
2678 them. Fixes bug 13071; bugfix on 0.1.1.15. Patch from "teor".
2679 - Squelch a spurious LD_BUG message "No origin circuit for
2680 successful SOCKS stream" in certain hidden service failure cases;
2682 - Downgrade the severity of the 'unexpected sendme cell from client'
2683 from 'warn' to 'protocol warning'. Closes ticket 8093.
2685 o Minor bugfixes (misc code correctness):
2686 - In munge_extrainfo_into_routerinfo(), check the return value of
2687 memchr(). This would have been a serious issue if we ever passed
2688 it a non-extrainfo. Fixes bug 8791; bugfix on 0.2.0.6-alpha. Patch
2690 - On the chance that somebody manages to build Tor on a
2691 platform where time_t is unsigned, correct the way that
2692 microdesc_add_to_cache() handles negative time arguments.
2693 Fixes bug 8042; bugfix on 0.2.3.1-alpha.
2694 - Fix various instances of undefined behavior in channeltls.c,
2695 tor_memmem(), and eventdns.c that would cause us to construct
2696 pointers to memory outside an allocated object. (These invalid
2697 pointers were not accessed, but C does not even allow them to
2698 exist.) Fixes bug 10363; bugfixes on 0.1.1.1-alpha, 0.1.2.1-alpha,
2699 0.2.0.10-alpha, and 0.2.3.6-alpha. Reported by "bobnomnom".
2700 - Use the AddressSanitizer and Ubsan sanitizers (in clang-3.4) to
2701 fix some miscellaneous errors in our tests and codebase. Fixes bug
2702 11232. Bugfixes on versions back as far as 0.2.1.11-alpha.
2703 - Always check return values for unlink, munmap, UnmapViewOfFile;
2704 check strftime return values more often. In some cases all we can
2705 do is report a warning, but this may help prevent deeper bugs from
2706 going unnoticed. Closes ticket 8787; bugfixes on many, many tor
2708 - Fix numerous warnings from the clang "scan-build" static analyzer.
2709 Some of these are programming style issues; some of them are false
2710 positives that indicated awkward code; some are undefined behavior
2711 cases related to constructing (but not using) invalid pointers;
2712 some are assumptions about API behavior; some are (harmlessly)
2713 logging sizeof(ptr) bytes from a token when sizeof(*ptr) would be
2714 correct; and one or two are genuine bugs that weren't reachable
2715 from the rest of the program. Fixes bug 8793; bugfixes on many,
2718 o Minor bugfixes (node selection):
2719 - If ExcludeNodes is set, consider non-excluded hidden service
2720 directory servers before excluded ones. Do not consider excluded
2721 hidden service directory servers at all if StrictNodes is
2722 set. (Previously, we would sometimes decide to connect to those
2723 servers, and then realize before we initiated a connection that
2724 we had excluded them.) Fixes bug 10722; bugfix on 0.2.0.10-alpha.
2726 - If we set the ExitNodes option but it doesn't include any nodes
2727 that have the Exit flag, we would choose not to bootstrap. Now we
2728 bootstrap so long as ExitNodes includes nodes which can exit to
2729 some port. Fixes bug 10543; bugfix on 0.2.4.10-alpha.
2731 o Minor bugfixes (performance):
2732 - Avoid a bug where every successful connection made us recompute
2733 the flag telling us whether we have sufficient information to
2734 build circuits. Previously, we would forget our cached value
2735 whenever we successfully opened a channel (or marked a router as
2736 running or not running for any other reason), regardless of
2737 whether we had previously believed the router to be running. This
2738 forced us to run an expensive update operation far too often.
2739 Fixes bug 12170; bugfix on 0.1.2.1-alpha.
2740 - Avoid using tor_memeq() for checking relay cell integrity. This
2741 removes a possible performance bottleneck. Fixes part of bug
2742 12169; bugfix on 0.2.1.31.
2744 o Minor bugfixes (platform-specific):
2745 - When dumping a malformed directory object to disk, save it in
2746 binary mode on Windows, not text mode. Fixes bug 11342; bugfix on
2748 - Don't report failures from make_socket_reuseable() on incoming
2749 sockets on OSX: this can happen when incoming connections close
2750 early. Fixes bug 10081.
2752 o Minor bugfixes (pluggable transports):
2753 - Avoid another 60-second delay when starting Tor in a pluggable-
2754 transport-using configuration when we already have cached
2755 descriptors for our bridges. Fixes bug 11965; bugfix
2758 o Minor bugfixes (protocol correctness):
2759 - When receiving a VERSIONS cell with an odd number of bytes, close
2760 the connection immediately since the cell is malformed. Fixes bug
2761 10365; bugfix on 0.2.0.10-alpha. Spotted by "bobnomnom"; fix by
2764 o Minor bugfixes (relay, other):
2765 - We now drop CREATE cells for already-existent circuit IDs and for
2766 zero-valued circuit IDs, regardless of other factors that might
2767 otherwise have called for DESTROY cells. Fixes bug 12191; bugfix
2769 - When rejecting DATA cells for stream_id zero, still count them
2770 against the circuit's deliver window so that we don't fail to send
2771 a SENDME. Fixes bug 11246; bugfix on 0.2.4.10-alpha.
2773 o Minor bugfixes (relay, threading):
2774 - Check return code on spawn_func() in cpuworker code, so that we
2775 don't think we've spawned a nonworking cpuworker and write junk to
2776 it forever. Fix related to bug 4345; bugfix on all released Tor
2777 versions. Found by "skruffy".
2778 - Use a pthread_attr to make sure that spawn_func() cannot return an
2779 error while at the same time launching a thread. Fix related to
2780 bug 4345; bugfix on all released Tor versions. Reported
2783 o Minor bugfixes (relays and bridges):
2784 - Avoid crashing on a malformed resolv.conf file when running a
2785 relay using Libevent 1. Fixes bug 8788; bugfix on 0.1.1.23.
2786 - Non-exit relays no longer launch mock DNS requests to check for
2787 DNS hijacking. This has been unnecessary since 0.2.1.7-alpha, when
2788 non-exit relays stopped servicing DNS requests. Fixes bug 965;
2789 bugfix on 0.2.1.7-alpha. Patch from Matt Pagan.
2790 - Bridges now report complete directory request statistics. Related
2791 to bug 5824; bugfix on 0.2.2.1-alpha.
2792 - Bridges now never collect statistics that were designed for
2793 relays. Fixes bug 5824; bugfix on 0.2.3.8-alpha.
2795 o Minor bugfixes (testing):
2796 - Fix all valgrind warnings produced by the unit tests. There were
2797 over a thousand memory leak warnings previously, mostly produced
2798 by forgetting to free things in the unit test code. Fixes bug
2799 11618, bugfixes on many versions of Tor.
2801 o Minor bugfixes (tor-fw-helper):
2802 - Give a correct log message when tor-fw-helper fails to launch.
2803 (Previously, we would say something like "tor-fw-helper sent us a
2804 string we could not parse".) Fixes bug 9781; bugfix
2807 o Minor bugfixes (trivial memory leaks):
2808 - Fix a small memory leak when signing a directory object. Fixes bug
2809 11275; bugfix on 0.2.4.13-alpha.
2810 - Resolve some memory leaks found by coverity in the unit tests, on
2811 exit in tor-gencert, and on a failure to compute digests for our
2812 own keys when generating a v3 networkstatus vote. These leaks
2813 should never have affected anyone in practice.
2815 o Code simplification and refactoring:
2816 - Remove some old fallback code designed to keep Tor clients working
2817 in a network with only two working relays. Elsewhere in the code we
2818 have long since stopped supporting such networks, so there wasn't
2819 much point in keeping it around. Addresses ticket 9926.
2820 - Reject 0-length EXTEND2 cells more explicitly. Fixes bug 10536;
2821 bugfix on 0.2.4.8-alpha. Reported by "cypherpunks".
2822 - Extract the common duplicated code for creating a subdirectory
2823 of the data directory and writing to a file in it. Fixes ticket
2824 4282; patch from Peter Retzlaff.
2825 - Since OpenSSL 0.9.7, the i2d_*() functions support allocating output
2826 buffer. Avoid calling twice: i2d_RSAPublicKey(), i2d_DHparams(),
2827 i2d_X509(), and i2d_PublicKey(). Resolves ticket 5170.
2828 - Add a set of accessor functions for the circuit timeout data
2829 structure. Fixes ticket 6153; patch from "piet".
2830 - Clean up exit paths from connection_listener_new(). Closes ticket
2831 8789. Patch from Arlo Breault.
2832 - Since we rely on OpenSSL 0.9.8 now, we can use EVP_PKEY_cmp()
2833 and drop our own custom pkey_eq() implementation. Fixes bug 9043.
2834 - Use a doubly-linked list to implement the global circuit list.
2835 Resolves ticket 9108. Patch from Marek Majkowski.
2836 - Remove contrib/id_to_fp.c since it wasn't used anywhere.
2837 - Remove constants and tests for PKCS1 padding; it's insecure and
2838 shouldn't be used for anything new. Fixes bug 8792; patch
2840 - Remove instances of strcpy() from the unit tests. They weren't
2841 hurting anything, since they were only in the unit tests, but it's
2842 embarassing to have strcpy() in the code at all, and some analysis
2843 tools don't like it. Fixes bug 8790; bugfix on 0.2.3.6-alpha and
2844 0.2.3.8-alpha. Patch from Arlo Breault.
2845 - Remove is_internal_IP() function. Resolves ticket 4645.
2846 - Remove unused function circuit_dump_by_chan from circuitlist.c.
2847 Closes issue 9107; patch from "marek".
2848 - Change our use of the ENUM_BF macro to avoid declarations that
2850 - Get rid of router->address, since in all cases it was just the
2851 string representation of router->addr. Resolves ticket 5528.
2854 - Adjust the URLs in the README to refer to the new locations of
2855 several documents on the website. Fixes bug 12830. Patch from
2857 - Document 'reject6' and 'accept6' ExitPolicy entries. Resolves
2859 - Update manpage to describe some of the files you can expect to
2860 find in Tor's DataDirectory. Addresses ticket 9839.
2861 - Clean up several option names in the manpage to match their real
2862 names, add the missing documentation for a couple of testing and
2863 directory authority options, remove the documentation for a
2864 V2-directory fetching option that no longer exists. Resolves
2866 - Correct the documenation so that it lists the correct directory
2867 for the stats files. (They are in a subdirectory called "stats",
2869 - In the manpage, move more authority-only options into the
2870 directory authority section so that operators of regular directory
2871 caches don't get confused.
2872 - Fix the layout of the SOCKSPort flags in the manpage. Fixes bug
2873 11061; bugfix on 0.2.4.7-alpha.
2874 - Resolve warnings from Doxygen.
2875 - Document in the manpage that "KBytes" may also be written as
2876 "kilobytes" or "KB", that "Kbits" may also be written as
2877 "kilobits", and so forth. Closes ticket 9222.
2878 - Document that the ClientOnly config option overrides ORPort.
2879 Our old explanation made ClientOnly sound as though it did
2880 nothing at all. Resolves bug 9059.
2881 - Explain that SocksPolicy, DirPolicy, and similar options don't
2882 take port arguments. Fixes the other part of ticket 11108.
2883 - Fix a comment about the rend_server_descriptor_t.protocols field
2884 to more accurately describe its range. Also, make that field
2885 unsigned, to more accurately reflect its usage. Fixes bug 9099;
2886 bugfix on 0.2.1.5-alpha.
2887 - Fix the manpage's description of HiddenServiceAuthorizeClient:
2888 the maximum client name length is 16, not 19. Fixes bug 11118;
2889 bugfix on 0.2.1.6-alpha.
2892 - The contrib directory has been sorted and tidied. Before, it was
2893 an unsorted dumping ground for useful and not-so-useful things.
2894 Now, it is divided based on functionality, and the items which
2895 seemed to be nonfunctional or useless have been removed. Resolves
2896 ticket 8966; based on patches from "rl1987".
2898 o Removed code and features:
2899 - Clients now reject any directory authority certificates lacking
2900 a dir-key-crosscert element. These have been included since
2901 0.2.1.9-alpha, so there's no real reason for them to be optional
2902 any longer. Completes proposal 157. Resolves ticket 10162.
2903 - Remove all code that existed to support the v2 directory system,
2904 since there are no longer any v2 directory authorities. Resolves
2906 - Remove the HSAuthoritativeDir and AlternateHSAuthority torrc
2907 options, which were used for designating authorities as "Hidden
2908 service authorities". There has been no use of hidden service
2909 authorities since 0.2.2.1-alpha, when we stopped uploading or
2910 downloading v0 hidden service descriptors. Fixes bug 10881; also
2911 part of a fix for bug 10841.
2912 - Remove /tor/dbg-stability.txt URL that was meant to help debug WFU
2913 and MTBF calculations, but that nobody was using. Fixes bug 11742.
2914 - The TunnelDirConns and PreferTunnelledDirConns options no longer
2915 exist; tunneled directory connections have been available since
2916 0.1.2.5-alpha, and turning them off is not a good idea. This is a
2917 brute-force fix for 10849, where "TunnelDirConns 0" would break
2919 - Remove all code for the long unused v1 directory protocol.
2920 Resolves ticket 11070.
2921 - Remove all remaining code related to version-0 hidden service
2922 descriptors: they have not been in use since 0.2.2.1-alpha. Fixes
2923 the rest of bug 10841.
2924 - Remove migration code from when we renamed the "cached-routers"
2925 file to "cached-descriptors" back in 0.2.0.8-alpha. This
2926 incidentally resolves ticket 6502 by cleaning up the related code
2927 a bit. Patch from Akshay Hebbar.
2929 o Test infrastructure:
2930 - Tor now builds each source file in two modes: a mode that avoids
2931 exposing identifiers needlessly, and another mode that exposes
2932 more identifiers for testing. This lets the compiler do better at
2933 optimizing the production code, while enabling us to take more
2934 radical measures to let the unit tests test things.
2935 - The production builds no longer include functions used only in
2936 the unit tests; all functions exposed from a module only for
2937 unit-testing are now static in production builds.
2938 - Add an --enable-coverage configuration option to make the unit
2939 tests (and a new src/or/tor-cov target) to build with gcov test
2941 - Update to the latest version of tinytest.
2942 - Improve the tinytest implementation of string operation tests so
2943 that comparisons with NULL strings no longer crash the tests; they
2944 now just fail, normally. Fixes bug 9004; bugfix on 0.2.2.4-alpha.
2945 - New macros in test.h to simplify writing mock-functions for unit
2946 tests. Part of ticket 11507. Patch from Dana Koch.
2947 - We now have rudimentary function mocking support that our unit
2948 tests can use to test functions in isolation. Function mocking
2949 lets the tests temporarily replace a function's dependencies with
2950 stub functions, so that the tests can check the function without
2951 invoking the other functions it calls.
2954 - Complete tests for the status.c module. Resolves ticket 11507.
2955 Patch from Dana Koch.
2956 - Add more unit tests for the <circid,channel>->circuit map, and
2957 the destroy-cell-tracking code to fix bug 7912.
2958 - Unit tests for failing cases of the TAP onion handshake.
2959 - More unit tests for address-manipulation functions.
2961 o Distribution (systemd):
2962 - Include a tor.service file in contrib/dist for use with systemd.
2963 Some distributions will be able to use this file unmodified;
2964 others will need to tweak it, or write their own. Patch from Jamie
2965 Nguyen; resolves ticket 8368.
2966 - Verify configuration file via ExecStartPre in the systemd unit
2967 file. Patch from intrigeri; resolves ticket 12730.
2968 - Explicitly disable RunAsDaemon in the systemd unit file. Our
2969 current systemd unit uses "Type = simple", so systemd does not
2970 expect tor to fork. If the user has "RunAsDaemon 1" in their
2971 torrc, then things won't work as expected. This is e.g. the case
2972 on Debian (and derivatives), since there we pass "--defaults-torrc
2973 /usr/share/tor/tor-service-defaults-torrc" (that contains
2974 "RunAsDaemon 1") by default. Patch by intrigeri; resolves
2978 Changes in version 0.2.4.25 - 2014-10-20
2979 Tor 0.2.4.25 disables SSL3 in response to the recent "POODLE" attack
2980 (even though POODLE does not affect Tor). It also works around a crash
2981 bug caused by some operating systems' response to the "POODLE" attack
2982 (which does affect Tor).
2984 o Major security fixes (also in 0.2.5.9-rc):
2985 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
2986 today support TLS 1.0 or later, so we can safely turn off support
2987 for this old (and insecure) protocol. Fixes bug 13426.
2989 o Major bugfixes (openssl bug workaround, also in 0.2.5.9-rc):
2990 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
2991 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
2992 13471. This is a workaround for an OpenSSL bug.
2995 Changes in version 0.2.4.24 - 2014-09-22
2996 Tor 0.2.4.24 fixes a bug that affects consistency and speed when
2997 connecting to hidden services, and it updates the location of one of
2998 the directory authorities.
3001 - Clients now send the correct address for their chosen rendezvous
3002 point when trying to access a hidden service. They used to send
3003 the wrong address, which would still work some of the time because
3004 they also sent the identity digest of the rendezvous point, and if
3005 the hidden service happened to try connecting to the rendezvous
3006 point from a relay that already had a connection open to it,
3007 the relay would reuse that connection. Now connections to hidden
3008 services should be more robust and faster. Also, this bug meant
3009 that clients were leaking to the hidden service whether they were
3010 on a little-endian (common) or big-endian (rare) system, which for
3011 some users might have reduced their anonymity. Fixes bug 13151;
3012 bugfix on 0.2.1.5-alpha.
3014 o Directory authority changes:
3015 - Change IP address for gabelmoo (v3 directory authority).
3017 o Minor features (geoip):
3018 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
3022 Changes in version 0.2.4.23 - 2014-07-28
3023 Tor 0.2.4.23 brings us a big step closer to slowing down the risk from
3024 guard rotation, and also backports several important fixes from the
3025 Tor 0.2.5 alpha release series.
3028 - Clients now look at the "usecreatefast" consensus parameter to
3029 decide whether to use CREATE_FAST or CREATE cells for the first hop
3030 of their circuit. This approach can improve security on connections
3031 where Tor's circuit handshake is stronger than the available TLS
3032 connection security levels, but the tradeoff is more computational
3033 load on guard relays. Implements proposal 221. Resolves ticket 9386.
3034 - Make the number of entry guards configurable via a new
3035 NumEntryGuards consensus parameter, and the number of directory
3036 guards configurable via a new NumDirectoryGuards consensus
3037 parameter. Implements ticket 12688.
3040 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
3041 implementation that caused incorrect results on 32-bit
3042 implementations when certain malformed inputs were used along with
3043 a small class of private ntor keys. This bug does not currently
3044 appear to allow an attacker to learn private keys or impersonate a
3045 Tor server, but it could provide a means to distinguish 32-bit Tor
3046 implementations from 64-bit Tor implementations. Fixes bug 12694;
3047 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
3051 - Warn and drop the circuit if we receive an inbound 'relay early'
3052 cell. Those used to be normal to receive on hidden service circuits
3053 due to bug 1038, but the buggy Tor versions are long gone from
3054 the network so we can afford to resume watching for them. Resolves
3055 the rest of bug 1038; bugfix on 0.2.1.19.
3056 - Correct a confusing error message when trying to extend a circuit
3057 via the control protocol but we don't know a descriptor or
3058 microdescriptor for one of the specified relays. Fixes bug 12718;
3059 bugfix on 0.2.3.1-alpha.
3060 - Avoid an illegal read from stack when initializing the TLS
3061 module using a version of OpenSSL without all of the ciphers
3062 used by the v2 link handshake. Fixes bug 12227; bugfix on
3063 0.2.4.8-alpha. Found by "starlight".
3066 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
3070 Changes in version 0.2.4.22 - 2014-05-16
3071 Tor 0.2.4.22 backports numerous high-priority fixes from the Tor 0.2.5
3072 alpha release series. These include blocking all authority signing
3073 keys that may have been affected by the OpenSSL "heartbleed" bug,
3074 choosing a far more secure set of TLS ciphersuites by default, closing
3075 a couple of memory leaks that could be used to run a target relay out
3076 of RAM, and several others.
3078 o Major features (security, backport from 0.2.5.4-alpha):
3079 - Block authority signing keys that were used on authorities
3080 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
3081 don't have any evidence that these keys _were_ compromised; we're
3082 doing this to be prudent.) Resolves ticket 11464.
3084 o Major bugfixes (security, OOM):
3085 - Fix a memory leak that could occur if a microdescriptor parse
3086 fails during the tokenizing step. This bug could enable a memory
3087 exhaustion attack by directory servers. Fixes bug 11649; bugfix
3090 o Major bugfixes (TLS cipher selection, backport from 0.2.5.4-alpha):
3091 - The relay ciphersuite list is now generated automatically based on
3092 uniform criteria, and includes all OpenSSL ciphersuites with
3093 acceptable strength and forward secrecy. Previously, we had left
3094 some perfectly fine ciphersuites unsupported due to omission or
3095 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
3096 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
3097 - Relays now trust themselves to have a better view than clients of
3098 which TLS ciphersuites are better than others. (Thanks to bug
3099 11513, the relay list is now well-considered, whereas the client
3100 list has been chosen mainly for anti-fingerprinting purposes.)
3101 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
3102 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
3103 AES128. Resolves ticket 11528.
3104 - Clients now try to advertise the same list of ciphersuites as
3105 Firefox 28. This change enables selection of (fast) GCM
3106 ciphersuites, disables some strange old ciphers, and stops
3107 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
3108 Resolves ticket 11438.
3110 o Minor bugfixes (configuration, security):
3111 - When running a hidden service, do not allow TunneledDirConns 0:
3112 trying to set that option together with a hidden service would
3113 otherwise prevent the hidden service from running, and also make
3114 it publish its descriptors directly over HTTP. Fixes bug 10849;
3115 bugfix on 0.2.1.1-alpha.
3117 o Minor bugfixes (controller, backport from 0.2.5.4-alpha):
3118 - Avoid sending a garbage value to the controller when a circuit is
3119 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
3121 o Minor bugfixes (exit relay, backport from 0.2.5.4-alpha):
3122 - Stop leaking memory when we successfully resolve a PTR record.
3123 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
3125 o Minor bugfixes (bridge client, backport from 0.2.5.4-alpha):
3126 - Avoid 60-second delays in the bootstrapping process when Tor is
3127 launching for a second time while using bridges. Fixes bug 9229;
3128 bugfix on 0.2.0.3-alpha.
3130 o Minor bugfixes (relays and bridges, backport from 0.2.5.4-alpha):
3131 - Give the correct URL in the warning message when trying to run a
3132 relay on an ancient version of Windows. Fixes bug 9393.
3134 o Minor bugfixes (compilation):
3135 - Fix a compilation error when compiling with --disable-curve25519.
3136 Fixes bug 9700; bugfix on 0.2.4.17-rc.
3139 - Downgrade the warning severity for the the "md was still
3140 referenced 1 node(s)" warning. Tor 0.2.5.4-alpha has better code
3141 for trying to diagnose this bug, and the current warning in
3142 earlier versions of tor achieves nothing useful. Addresses warning
3145 o Minor features (log verbosity, backport from 0.2.5.4-alpha):
3146 - When we run out of usable circuit IDs on a channel, log only one
3147 warning for the whole channel, and describe how many circuits
3148 there were on the channel. Fixes part of ticket 11553.
3150 o Minor features (security, backport from 0.2.5.4-alpha):
3151 - Decrease the lower limit of MaxMemInCellQueues to 256 MBytes (but
3152 leave the default at 8GBytes), to better support Raspberry Pi
3153 users. Fixes bug 9686; bugfix on 0.2.4.14-alpha.
3155 o Documentation (backport from 0.2.5.4-alpha):
3156 - Correctly document that we search for a system torrc file before
3157 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
3161 Changes in version 0.2.4.21 - 2014-02-28
3162 Tor 0.2.4.21 further improves security against potential adversaries who
3163 find breaking 1024-bit crypto doable, and backports several stability
3164 and robustness patches from the 0.2.5 branch.
3166 o Major features (client security):
3167 - When we choose a path for a 3-hop circuit, make sure it contains
3168 at least one relay that supports the NTor circuit extension
3169 handshake. Otherwise, there is a chance that we're building
3170 a circuit that's worth attacking by an adversary who finds
3171 breaking 1024-bit crypto doable, and that chance changes the game
3172 theory. Implements ticket 9777.
3175 - Do not treat streams that fail with reason
3176 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
3177 since it could also indicate an ENETUNREACH connection error. Fixes
3178 part of bug 10777; bugfix on 0.2.4.8-alpha.
3180 o Code simplification and refactoring:
3181 - Remove data structures which were introduced to implement the
3182 CellStatistics option: they are now redundant with the new timestamp
3183 field in the regular packed_cell_t data structure, which we did
3184 in 0.2.4.18-rc in order to resolve bug 9093. Resolves ticket 10870.
3187 - Always clear OpenSSL bignums before freeing them -- even bignums
3188 that don't contain secrets. Resolves ticket 10793. Patch by
3190 - Build without warnings under clang 3.4. (We have some macros that
3191 define static functions only some of which will get used later in
3192 the module. Starting with clang 3.4, these give a warning unless the
3193 unused attribute is set on them.) Resolves ticket 10904.
3194 - Update geoip and geoip6 files to the February 7 2014 Maxmind
3195 GeoLite2 Country database.
3198 - Set the listen() backlog limit to the largest actually supported
3199 on the system, not to the value in a header file. Fixes bug 9716;
3200 bugfix on every released Tor.
3201 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
3202 exit node as a NOROUTE error, not an INTERNAL error, since they
3203 can apparently happen when trying to connect to the wrong sort
3204 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
3205 - Fix build warnings about missing "a2x" comment when building the
3206 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
3207 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
3208 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
3209 not entirely remove it from the connection lists. Fixes bug 9602;
3210 bugfix on 0.2.4.4-alpha.
3211 - Fix a segmentation fault in our benchmark code when running with
3212 Fedora's OpenSSL package, or any other OpenSSL that provides
3213 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
3214 - Turn "circuit handshake stats since last time" log messages into a
3215 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
3217 o Documentation fixes:
3218 - Document that all but one DirPort entry must have the NoAdvertise
3219 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
3222 Changes in version 0.2.4.20 - 2013-12-22
3223 Tor 0.2.4.20 fixes potentially poor random number generation for users
3224 who 1) use OpenSSL 1.0.0 or later, 2) set "HardwareAccel 1" in their
3225 torrc file, 3) have "Sandy Bridge" or "Ivy Bridge" Intel processors,
3226 and 4) have no state file in their DataDirectory (as would happen on
3227 first start). Users who generated relay or hidden service identity
3228 keys in such a situation should discard them and generate new ones.
3230 This release also fixes a logic error that caused Tor clients to build
3231 many more preemptive circuits than they actually need.
3234 - Do not allow OpenSSL engines to replace the PRNG, even when
3235 HardwareAccel is set. The only default builtin PRNG engine uses
3236 the Intel RDRAND instruction to replace the entire PRNG, and
3237 ignores all attempts to seed it with more entropy. That's
3238 cryptographically stupid: the right response to a new alleged
3239 entropy source is never to discard all previously used entropy
3240 sources. Fixes bug 10402; works around behavior introduced in
3241 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
3243 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
3244 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
3245 - Avoid launching spurious extra circuits when a stream is pending.
3246 This fixes a bug where any circuit that _wasn't_ unusable for new
3247 streams would be treated as if it were, causing extra circuits to
3248 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
3251 - Avoid a crash bug when starting with a corrupted microdescriptor
3252 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
3253 - If we fail to dump a previously cached microdescriptor to disk, avoid
3254 freeing duplicate data later on. Fixes bug 10423; bugfix on
3255 0.2.4.13-alpha. Spotted by "bobnomnom".
3258 Changes in version 0.2.4.19 - 2013-12-11
3259 The Tor 0.2.4 release series is dedicated to the memory of Aaron Swartz
3260 (1986-2013). Aaron worked on diverse projects including helping to guide
3261 Creative Commons, playing a key role in stopping SOPA/PIPA, bringing
3262 transparency to the U.S government's PACER documents, and contributing
3263 design and development for Tor and Tor2Web. Aaron was one of the latest
3264 martyrs in our collective fight for civil liberties and human rights,
3265 and his death is all the more painful because he was one of us.
3267 Tor 0.2.4.19, the first stable release in the 0.2.4 branch, features
3268 a new circuit handshake and link encryption that use ECC to provide
3269 better security and efficiency; makes relays better manage circuit
3270 creation requests; uses "directory guards" to reduce client enumeration
3271 risks; makes bridges collect and report statistics about the pluggable
3272 transports they support; cleans up and improves our geoip database;
3273 gets much closer to IPv6 support for clients, bridges, and relays; makes
3274 directory authorities use measured bandwidths rather than advertised
3275 ones when computing flags and thresholds; disables client-side DNS
3276 caching to reduce tracking risks; and fixes a big bug in bridge
3277 reachability testing. This release introduces two new design
3278 abstractions in the code: a new "channel" abstraction between circuits
3279 and or_connections to allow for implementing alternate relay-to-relay
3280 transports, and a new "circuitmux" abstraction storing the queue of
3281 circuits for a channel. The release also includes many stability,
3282 security, and privacy fixes.
3284 o Major features (new circuit handshake):
3285 - Tor now supports a new circuit extension handshake designed by Ian
3286 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
3287 circuit extension handshake, later called "TAP", was a bit slow
3288 (especially on the relay side), had a fragile security proof, and
3289 used weaker keys than we'd now prefer. The new circuit handshake
3290 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
3291 function, making it significantly more secure than the older
3292 handshake, and significantly faster. Tor can use one of two built-in
3293 pure-C curve25519-donna implementations by Adam Langley, or it
3294 can link against the "nacl" library for a tuned version if present.
3296 The built-in version is very fast for 64-bit systems when building
3297 with GCC. The built-in 32-bit version is still faster than the
3298 old TAP protocol, but using libnacl is better on most such hosts.
3300 Implements proposal 216; closes ticket 7202.
3302 o Major features (better link encryption):
3303 - Relays can now enable the ECDHE TLS ciphersuites when available
3304 and appropriate. These ciphersuites let us negotiate forward-secure
3305 TLS secret keys more safely and more efficiently than with our
3306 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
3307 public relays prefer the (faster) P224 group, and bridges prefer
3308 the (more common) P256 group; you can override this with the
3311 This feature requires clients running 0.2.3.17-beta or later,
3312 and requires both sides to be running OpenSSL 1.0.0 or later
3313 with ECC support. OpenSSL 1.0.1, with the compile-time option
3314 "enable-ec_nistp_64_gcc_128", is highly recommended.
3316 Implements the relay side of proposal 198; closes ticket 7200.
3318 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
3319 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
3320 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
3321 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
3322 them to solve bug 6033.)
3324 o Major features (relay performance):
3325 - Instead of limiting the number of queued onionskins (aka circuit
3326 create requests) to a fixed, hard-to-configure number, we limit
3327 the size of the queue based on how many we expect to be able to
3328 process in a given amount of time. We estimate the time it will
3329 take to process an onionskin based on average processing time
3330 of previous onionskins. Closes ticket 7291. You'll never have to
3331 configure MaxOnionsPending again.
3332 - Relays process the new "NTor" circuit-level handshake requests
3333 with higher priority than the old "TAP" circuit-level handshake
3334 requests. We still process some TAP requests to not totally starve
3335 0.2.3 clients when NTor becomes popular. A new consensus parameter
3336 "NumNTorsPerTAP" lets us tune the balance later if we need to.
3337 Implements ticket 9574.
3339 o Major features (client bootstrapping resilience):
3340 - Add a new "FallbackDir" torrc option to use when we can't use
3341 a directory mirror from the consensus (either because we lack a
3342 consensus, or because they're all down). Currently, all authorities
3343 are fallbacks by default, and there are no other default fallbacks,
3344 but that will change. This option will allow us to give clients a
3345 longer list of servers to try to get a consensus from when first
3346 connecting to the Tor network, and thereby reduce load on the
3347 directory authorities. Implements proposal 206, "Preconfigured
3348 directory sources for bootstrapping". We also removed the old
3349 "FallbackNetworkstatus" option, since we never got it working well
3350 enough to use it. Closes bug 572.
3351 - If we have no circuits open, use a relaxed timeout (the
3352 95th-percentile cutoff) until a circuit succeeds. This heuristic
3353 should allow Tor to succeed at building circuits even when the
3354 network connection drastically changes. Should help with bug 3443.
3356 o Major features (use of guards):
3357 - Support directory guards (proposal 207): when possible, clients now
3358 use their entry guards for non-anonymous directory requests. This
3359 can help prevent client enumeration. Note that this behavior only
3360 works when we have a usable consensus directory, and when options
3361 about what to download are more or less standard. In the future we
3362 should re-bootstrap from our guards, rather than re-bootstrapping
3363 from the preconfigured list of directory sources that ships with
3364 Tor. Resolves ticket 6526.
3365 - Raise the default time that a client keeps an entry guard from
3366 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
3367 2012 paper. (We would make it even longer, but we need better client
3368 load balancing first.) Also, make the guard lifetime controllable
3369 via a new GuardLifetime torrc option and a GuardLifetime consensus
3370 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
3372 o Major features (bridges with pluggable transports):
3373 - Bridges now report the pluggable transports they support to the
3374 bridge authority, so it can pass the supported transports on to
3375 bridgedb and/or eventually do reachability testing. Implements
3377 - Automatically forward the TCP ports of pluggable transport
3378 proxies using tor-fw-helper if PortForwarding is enabled. Implements
3381 o Major features (geoip database):
3382 - Maxmind began labelling Tor relays as being in country "A1",
3383 which breaks by-country node selection inside Tor. Now we use a
3384 script to replace "A1" ("Anonymous Proxy") entries in our geoip
3385 file with real country codes. This script fixes about 90% of "A1"
3386 entries automatically and uses manual country code assignments to
3387 fix the remaining 10%. See src/config/README.geoip for details.
3389 - Add GeoIP database for IPv6 addresses. The new config option
3391 - Update to the October 2 2013 Maxmind GeoLite Country database.
3393 o Major features (IPv6):
3394 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
3395 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
3396 to happen. Implements ticket 5535.
3397 - All kind of relays, not just bridges, can now advertise an IPv6
3398 OR port. Implements ticket 6362.
3399 - Relays can now exit to IPv6 addresses: make sure that you have IPv6
3400 connectivity, then set the IPv6Exit flag to 1. Also make sure your
3401 exit policy reads as you would like: the address * applies to all
3402 address families, whereas *4 is IPv4 address only, and *6 is IPv6
3403 addresses only. On the client side, you'll need to wait for enough
3404 exits to support IPv6, apply the "IPv6Traffic" flag to a SocksPort,
3405 and use Socks5. Closes ticket 5547, implements proposal 117 as
3406 revised in proposal 208.
3407 - Bridge authorities now accept IPv6 bridge addresses and include
3408 them in network status documents. Implements ticket 5534.
3409 - Directory authorities vote on IPv6 OR ports. Implements ticket 6363.
3411 o Major features (directory authorities):
3412 - Directory authorities now prefer using measured bandwidths to
3413 advertised ones when computing flags and thresholds. Resolves
3415 - Directory authorities that vote measured bandwidths about more
3416 than a threshold number of relays now treat relays with
3417 unmeasured bandwidths as having bandwidth 0 when computing their
3418 flags. Resolves ticket 8435.
3419 - Directory authorities now support a new consensus method (17)
3420 where they cap the published bandwidth of relays for which
3421 insufficient bandwidth measurements exist. Fixes part of bug 2286.
3422 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
3423 serve any v2 directory information. Now we can test disabling the
3424 old deprecated v2 directory format, and see whether doing so has
3425 any effect on network load. Begins to fix bug 6783.
3427 o Major features (build and portability):
3428 - Switch to a nonrecursive Makefile structure. Now instead of each
3429 Makefile.am invoking other Makefile.am's, there is a master
3430 Makefile.am that includes the others. This change makes our build
3431 process slightly more maintainable, and improves parallelism for
3432 building with make -j. Original patch by Stewart Smith; various
3433 fixes by Jim Meyering.
3434 - Where available, we now use automake's "silent" make rules by
3435 default, so that warnings are easier to spot. You can get the old
3436 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
3437 - Resume building correctly with MSVC and Makefile.nmake. This patch
3438 resolves numerous bugs and fixes reported by ultramage, including
3439 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
3441 o Security features:
3442 - Switch to a completely time-invariant approach for picking nodes
3443 weighted by bandwidth. Our old approach would run through the
3444 part of the loop after it had made its choice slightly slower
3445 than it ran through the part of the loop before it had made its
3446 choice. Addresses ticket 6538.
3447 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
3448 by tor2web clients allows hidden services to identify tor2web
3449 clients through their repeated selection of the same rendezvous
3450 and introduction point circuit endpoints (their guards). Resolves
3453 o Major bugfixes (relay denial of service):
3454 - When we have too much memory queued in circuits (according to a new
3455 MaxMemInCellQueues option), close the circuits that have the oldest
3456 queued cells, on the theory that those are most responsible for
3457 us running low on memory. This prevents us from running out of
3458 memory as a relay if circuits fill up faster than they can be
3459 drained. Fixes bugs 9063 and 9093; bugfix on the 54th commit of
3460 Tor. This bug is a further fix beyond bug 6252, whose fix was
3461 merged into 0.2.3.21-rc.
3462 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
3463 ID: these could be used to create unexpected streams and circuits
3464 which would count as "present" to some parts of Tor but "absent"
3465 to others, leading to zombie circuits and streams or to a bandwidth
3466 denial-of-service. Fixes bug 7889; bugfix on every released version
3467 of Tor. Reported by "oftc_must_be_destroyed".
3468 - Avoid a bug where our response to TLS renegotiation under certain
3469 network conditions could lead to a busy-loop, with 100% CPU
3470 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
3472 o Major bugfixes (asserts, crashes, leaks):
3473 - Prevent the get_freelists() function from running off the end of
3474 the list of freelists if it somehow gets an unrecognized
3475 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
3477 - Avoid a memory leak where we would leak a consensus body when we
3478 find that a consensus which we couldn't previously verify due to
3479 missing certificates is now verifiable. Fixes bug 8719; bugfix
3481 - If we are unable to save a microdescriptor to the journal, do not
3482 drop it from memory and then reattempt downloading it. Fixes bug
3483 9645; bugfix on 0.2.2.6-alpha.
3484 - Fix an assertion failure that would occur when disabling the
3485 ORPort setting on a running Tor process while accounting was
3486 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
3487 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
3488 when an exit connection with optimistic data succeeds immediately
3489 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
3491 - Fix a memory leak that would occur whenever a configuration
3492 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
3494 o Major bugfixes (relay rate limiting):
3495 - When a TLS write is partially successful but incomplete, remember
3496 that the flushed part has been flushed, and notice that bytes were
3497 actually written. Reported and fixed pseudonymously. Fixes bug 7708;
3498 bugfix on Tor 0.1.0.5-rc.
3499 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
3500 to 1GB/1GB. The previous defaults were intended to be "basically
3501 infinite", but it turns out they're now limiting our 100mbit+
3502 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
3503 last time we raised it).
3504 - No longer stop reading or writing on cpuworker connections when
3505 our rate limiting buckets go empty. Now we should handle circuit
3506 handshake requests more promptly. Resolves bug 9731.
3508 o Major bugfixes (client-side privacy):
3509 - When we mark a circuit as unusable for new circuits, have it
3510 continue to be unusable for new circuits even if MaxCircuitDirtiness
3511 is increased too much at the wrong time, or the system clock jumps
3512 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
3513 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
3514 which have resolved to internal addresses") is set, apply that
3515 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
3516 - When an exit relay rejects a stream with reason "exit policy", but
3517 we only know an exit policy summary (e.g. from the microdesc
3518 consensus) for it, do not mark the relay as useless for all exiting.
3519 Instead, mark just the circuit as unsuitable for that particular
3520 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
3522 o Major bugfixes (stream isolation):
3523 - Allow applications to get proper stream isolation with
3524 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
3525 username/password authentication also offer "no authentication". Tor
3526 had previously preferred "no authentication", so the applications
3527 never actually sent Tor their auth details. Now Tor selects
3528 username/password authentication if it's offered. You can disable
3529 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
3530 bug 8117; bugfix on 0.2.3.3-alpha.
3531 - Follow the socks5 protocol when offering username/password
3532 authentication. The fix for bug 8117 exposed this bug, and it
3533 turns out real-world applications like Pidgin do care. Bugfix on
3534 0.2.3.2-alpha; fixes bug 8879.
3536 o Major bugfixes (client circuit building):
3537 - Alter circuit build timeout measurement to start at the point
3538 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
3539 initialization). This should make our timeout measurements more
3540 uniform. Previously, we were sometimes including ORconn setup time
3541 in our circuit build time measurements. Should resolve bug 3443.
3542 - If the circuit build timeout logic is disabled (via the consensus,
3543 or because we are an authority), then don't build testing circuits.
3544 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
3546 o Major bugfixes (client-side DNS):
3547 - Turn off the client-side DNS cache by default. Updating and using
3548 the DNS cache is now configurable on a per-client-port
3549 level. SOCKSPort, DNSPort, etc lines may now contain
3550 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
3551 cache these types of DNS answers when we receive them from an
3552 exit node in response to an application request on this port, and
3553 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
3554 cached DNS answers of these types, we shouldn't use them. It's
3555 potentially risky to use cached DNS answers at the client, since
3556 doing so can indicate to one exit what answers we've gotten
3557 for DNS lookups in the past. With IPv6, this becomes especially
3558 problematic. Using cached DNS answers for requests on the same
3559 circuit would present less linkability risk, since all traffic
3560 on a circuit is already linkable, but it would also provide
3561 little performance benefit: the exit node caches DNS replies
3562 too. Implements a simplified version of Proposal 205. Implements
3565 o Major bugfixes (hidden service privacy):
3566 - Limit hidden service descriptors to at most ten introduction
3567 points, to slow one kind of guard enumeration. Fixes bug 9002;
3568 bugfix on 0.1.1.11-alpha.
3570 o Major bugfixes (directory fetching):
3571 - If the time to download the next old-style networkstatus is in
3572 the future, do not decline to consider whether to download the
3573 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
3575 - We used to always request authority certificates by identity digest,
3576 meaning we'd get the newest one even when we wanted one with a
3577 different signing key. Then we would complain about being given
3578 a certificate we already had, and never get the one we really
3579 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
3580 resource to request the one we want. Fixes bug 5595; bugfix on
3583 o Major bugfixes (bridge reachability):
3584 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
3585 previously they did not, which prevented them from receiving
3586 successful connections from relays for self-test or bandwidth
3587 testing. Also, when a relay is extending a circuit to a bridge,
3588 it needs to send a NETINFO cell, even when the bridge hasn't sent
3589 an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
3591 o Major bugfixes (control interface):
3592 - When receiving a new configuration file via the control port's
3593 LOADCONF command, do not treat the defaults file as absent.
3594 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
3596 o Major bugfixes (directory authorities):
3597 - Stop marking every relay as having been down for one hour every
3598 time we restart a directory authority. These artificial downtimes
3599 were messing with our Stable and Guard flag calculations. Fixes
3600 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
3601 - When computing directory thresholds, ignore any rejected-as-sybil
3602 nodes during the computation so that they can't influence Fast,
3603 Guard, etc. (We should have done this for proposal 109.) Fixes
3605 - When marking a node as a likely sybil, reset its uptime metrics
3606 to zero, so that it cannot time towards getting marked as Guard,
3607 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
3609 - Fix a bug in the voting algorithm that could yield incorrect results
3610 when a non-naming authority declared too many flags. Fixes bug 9200;
3611 bugfix on 0.2.0.3-alpha.
3613 o Internal abstraction features:
3614 - Introduce new channel_t abstraction between circuits and
3615 or_connection_t to allow for implementing alternate OR-to-OR
3616 transports. A channel_t is an abstract object which can either be a
3617 cell-bearing channel, which is responsible for authenticating and
3618 handshaking with the remote OR and transmitting cells to and from
3619 it, or a listening channel, which spawns new cell-bearing channels
3620 at the request of remote ORs. Implements part of ticket 6465.
3621 - Make a channel_tls_t subclass of channel_t, adapting it to the
3622 existing or_connection_t code. The V2/V3 protocol handshaking
3623 code which formerly resided in command.c has been moved below the
3624 channel_t abstraction layer and may be found in channeltls.c now.
3625 Implements the rest of ticket 6465.
3626 - Introduce new circuitmux_t storing the queue of circuits for
3627 a channel; this encapsulates and abstracts the queue logic and
3628 circuit selection policy, and allows the latter to be overridden
3629 easily by switching out a policy object. The existing EWMA behavior
3630 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
3632 o New build requirements:
3633 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
3634 strongly recommended.
3635 - Tor maintainers now require Automake version 1.9 or later to build
3636 Tor from the Git repository. (Automake is not required when building
3637 from a source distribution.)
3639 o Minor features (protocol):
3640 - No longer include the "opt" prefix when generating routerinfos
3641 or v2 directories: it has been needless since Tor 0.1.2. Closes
3643 - Reject EXTEND cells sent to nonexistent streams. According to the
3644 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
3645 we were only checking for stream IDs that were currently in use.
3646 Found while hunting for more instances of bug 6271. Bugfix on
3647 0.0.2pre8, which introduced incremental circuit construction.
3648 - Tor relays and clients now support a better CREATE/EXTEND cell
3649 format, allowing the sender to specify multiple address, identity,
3650 and handshake types. Implements Robert Ransom's proposal 200;
3652 - Reject as invalid most directory objects containing a NUL.
3653 Belt-and-suspender fix for bug 8037.
3655 o Minor features (security):
3656 - Clear keys and key-derived material left on the stack in
3657 rendservice.c and rendclient.c. Check return value of
3658 crypto_pk_write_private_key_to_string() in rend_service_load_keys().
3659 These fixes should make us more forward-secure against cold-boot
3660 attacks and the like. Fixes bug 2385.
3661 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
3662 Irix's random() only return 15 bits; Solaris's random() returns more
3663 bits but its RAND_MAX says it only returns 15, and so on. Motivated
3664 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
3666 o Minor features (control protocol):
3667 - Add a "GETINFO signal/names" control port command. Implements
3669 - Provide default values for all options via "GETINFO config/defaults".
3670 Implements ticket 4971.
3671 - Allow an optional $ before the node identity digest in the
3672 controller command GETINFO ns/id/<identity>, for consistency with
3673 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
3674 - Add CACHED keyword to ADDRMAP events in the control protocol
3675 to indicate whether a DNS result will be cached or not. Resolves
3677 - Generate bootstrapping status update events correctly when fetching
3678 microdescriptors. Fixes bug 9927.
3680 o Minor features (path selection):
3681 - When deciding whether we have enough descriptors to build circuits,
3682 instead of looking at raw relay counts, look at which fraction
3683 of (bandwidth-weighted) paths we're able to build. This approach
3684 keeps clients from building circuits if their paths are likely to
3685 stand out statistically. The default fraction of paths needed is
3686 taken from the consensus directory; you can override it with the
3687 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
3688 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
3689 and we have GeoIP information, also exclude all nodes with unknown
3690 countries "??" and "A1". This behavior is controlled by the
3691 new GeoIPExcludeUnknown option: you can make such nodes always
3692 excluded with "GeoIPExcludeUnknown 1", and disable the feature
3693 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
3694 gets you the default behavior. Implements feature 7706.
3696 o Minor features (hidden services):
3697 - Improve circuit build timeout handling for hidden services.
3698 In particular: adjust build timeouts more accurately depending
3699 upon the number of hop-RTTs that a particular circuit type
3700 undergoes. Additionally, launch intro circuits in parallel
3701 if they timeout, and take the first one to reply as valid.
3702 - The Tor client now ignores sub-domain components of a .onion
3703 address. This change makes HTTP "virtual" hosting
3704 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
3705 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
3706 hosted on the same hidden service. Implements proposal 204.
3707 - Enable Tor to read configuration, state, and key information from
3708 a FIFO. Previously Tor would only read from files with a positive
3709 stat.st_size. Code from meejah; fixes bug 6044.
3711 o Minor features (clients):
3712 - Teach bridge-using clients to avoid 0.2.2.x bridges when making
3713 microdescriptor-related dir requests, and only fall back to normal
3714 descriptors if none of their bridges can handle microdescriptors
3715 (as opposed to the fix in ticket 4013, which caused them to fall
3716 back to normal descriptors if *any* of their bridges preferred
3717 them). Resolves ticket 4994.
3718 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
3719 TCP ports to forward. In the past it only accepted two ports:
3720 the ORPort and the DirPort.
3722 o Minor features (protecting client timestamps):
3723 - Clients no longer send timestamps in their NETINFO cells. These were
3724 not used for anything, and they provided one small way for clients
3725 to be distinguished from each other as they moved from network to
3726 network or behind NAT. Implements part of proposal 222.
3727 - Clients now round timestamps in INTRODUCE cells down to the nearest
3728 10 minutes. If a new Support022HiddenServices option is set to 0, or
3729 if it's set to "auto" and the feature is disabled in the consensus,
3730 the timestamp is sent as 0 instead. Implements part of proposal 222.
3731 - Stop sending timestamps in AUTHENTICATE cells. This is not such
3732 a big deal from a security point of view, but it achieves no actual
3733 good purpose, and isn't needed. Implements part of proposal 222.
3734 - Reduce down accuracy of timestamps in hidden service descriptors.
3735 Implements part of proposal 222.
3737 o Minor features (bridges):
3738 - Make bridge relays check once a minute for whether their IP
3739 address has changed, rather than only every 15 minutes. Resolves
3741 - Bridge statistics now count bridge clients connecting over IPv6:
3742 bridge statistics files now list "bridge-ip-versions" and
3743 extra-info documents list "geoip6-db-digest". The control protocol
3744 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
3745 implementation by "shkoo", addressing ticket 5055.
3746 - Add a new torrc option "ServerTransportListenAddr" to let bridge
3747 operators select the address where their pluggable transports will
3748 listen for connections. Resolves ticket 7013.
3749 - Randomize the lifetime of our SSL link certificate, so censors can't
3750 use the static value for filtering Tor flows. Resolves ticket 8443;
3751 related to ticket 4014 which was included in 0.2.2.33.
3753 o Minor features (relays):
3754 - Option OutboundBindAddress can be specified multiple times and
3755 accepts IPv6 addresses. Resolves ticket 6876.
3757 o Minor features (IPv6, client side):
3758 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
3759 prefer to hand out virtual IPv6 addresses, since there are more of
3760 them and we can't run out. To override this behavior and make IPv4
3761 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
3762 or DNSPort you're using for resolving. Implements ticket 7571.
3763 - AutomapHostsOnResolve responses are now randomized, to avoid
3764 annoying situations where Tor is restarted and applications
3765 connect to the wrong addresses.
3766 - Never try more than 1000 times to pick a new virtual address when
3767 AutomapHostsOnResolve is set. That's good enough so long as we
3768 aren't close to handing out our entire virtual address space;
3769 if you're getting there, it's best to switch to IPv6 virtual
3772 o Minor features (IPv6, relay/authority side):
3773 - New config option "AuthDirHasIPv6Connectivity 1" that directory
3774 authorities should set if they have IPv6 connectivity and want to
3775 do reachability tests for IPv6 relays. Implements feature 5974.
3776 - A relay with an IPv6 OR port now sends that address in NETINFO
3777 cells (in addition to its other address). Implements ticket 6364.
3779 o Minor features (directory authorities):
3780 - Directory authorities no long accept descriptors for any version of
3781 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
3782 These versions are insecure, unsupported, or both. Implements
3784 - When directory authorities are computing thresholds for flags,
3785 never let the threshold for the Fast flag fall below 4096
3786 bytes. Also, do not consider nodes with extremely low bandwidths
3787 when deciding thresholds for various directory flags. This change
3788 should raise our threshold for Fast relays, possibly in turn
3789 improving overall network performance; see ticket 1854. Resolves
3791 - Directory authorities now include inside each vote a statement of
3792 the performance thresholds they used when assigning flags.
3793 Implements ticket 8151.
3794 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
3795 in directory authority votes to describe whether they have enough
3796 measured bandwidths to ignore advertised (relay descriptor)
3797 bandwidth claims. Resolves ticket 8711.
3799 o Minor features (path bias detection):
3800 - Path Use Bias: Perform separate accounting for successful circuit
3801 use. Keep separate statistics on stream attempt rates versus stream
3802 success rates for each guard. Provide configurable thresholds to
3803 determine when to emit log messages or disable use of guards that
3804 fail too many stream attempts. Resolves ticket 7802.
3805 - Create three levels of Path Bias log messages, as opposed to just
3806 two. These are configurable via consensus as well as via the torrc
3807 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
3808 The default values are 0.70, 0.50, and 0.30 respectively.
3809 - Separate the log message levels from the decision to drop guards,
3810 which also is available via torrc option PathBiasDropGuards.
3811 PathBiasDropGuards still defaults to 0 (off).
3812 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
3813 in combination with PathBiasExtremeRate.
3814 - Increase the default values for PathBiasScaleThreshold and
3815 PathBiasCircThreshold from (200, 20) to (300, 150).
3816 - Add in circuit usage accounting to path bias. If we try to use a
3817 built circuit but fail for any reason, it counts as path bias.
3818 Certain classes of circuits where the adversary gets to pick your
3819 destination node are exempt from this accounting. Usage accounting
3820 can be specifically disabled via consensus parameter or torrc.
3821 - Convert all internal path bias state to double-precision floating
3822 point, to avoid roundoff error and other issues.
3823 - Only record path bias information for circuits that have completed
3824 *two* hops. Assuming end-to-end tagging is the attack vector, this
3825 makes us more resilient to ambient circuit failure without any
3826 detection capability loss.
3828 o Minor features (build):
3829 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
3830 dhill. Resolves ticket 6982.
3831 - Compile on win64 using mingw64. Fixes bug 7260; patches from
3833 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
3834 separate error codes; or at least, don't break for that reason.
3835 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
3837 o Build improvements (autotools):
3838 - Warn if building on a platform with an unsigned time_t: there
3839 are too many places where Tor currently assumes that time_t can
3840 hold negative values. We'd like to fix them all, but probably
3842 - Do not report status verbosely from autogen.sh unless the -v flag
3843 is specified. Fixes issue 4664. Patch from Onizuka.
3844 - Detect and reject attempts to build Tor with threading support
3845 when OpenSSL has been compiled without threading support.
3847 - Try to detect if we are ever building on a platform where
3848 memset(...,0,...) does not set the value of a double to 0.0. Such
3849 platforms are permitted by the C standard, though in practice
3850 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
3851 currently support them, but it's better to detect them and fail
3852 than to perform erroneously.
3853 - We no longer warn so much when generating manpages from their
3855 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
3856 the signs of types during autoconf. This is better than our old
3857 approach, which didn't work when cross-compiling.
3859 o Minor features (log messages, warnings):
3860 - Detect when we're running with a version of OpenSSL other than the
3861 one we compiled with. This conflict has occasionally given people
3862 hard-to-track-down errors.
3863 - Warn users who run hidden services on a Tor client with
3864 UseEntryGuards disabled that their hidden services will be
3865 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
3866 attack which motivated Tor to support entry guards in the first
3867 place). Resolves ticket 6889.
3868 - Warn when we are binding low ports when hibernation is enabled;
3869 previously we had warned when we were _advertising_ low ports with
3870 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
3871 - Issue a warning when running with the bufferevents backend enabled.
3872 It's still not stable, and people should know that they're likely
3873 to hit unexpected problems. Closes ticket 9147.
3875 o Minor features (log messages, notices):
3876 - Refactor resolve_my_address() so it returns the method by which we
3877 decided our public IP address (explicitly configured, resolved from
3878 explicit hostname, guessed from interfaces, learned by gethostname).
3879 Now we can provide more helpful log messages when a relay guesses
3880 its IP address incorrectly (e.g. due to unexpected lines in
3881 /etc/hosts). Resolves ticket 2267.
3882 - Track how many "TAP" and "NTor" circuit handshake requests we get,
3883 and how many we complete, and log it every hour to help relay
3884 operators follow trends in network load. Addresses ticket 9658.
3886 o Minor features (log messages, diagnostics):
3887 - If we fail to free a microdescriptor because of bug 7164, log
3888 the filename and line number from which we tried to free it.
3889 - We compute the overhead from passing onionskins back and forth to
3890 cpuworkers, and report it when dumping statistics in response to
3891 SIGUSR1. Supports ticket 7291.
3892 - Add another diagnostic to the heartbeat message: track and log
3893 overhead that TLS is adding to the data we write. If this is
3894 high, we are sending too little data to SSL_write at a time.
3895 Diagnostic for bug 7707.
3896 - Log packaged cell fullness as part of the heartbeat message.
3897 Diagnosis to try to determine the extent of bug 7743.
3898 - Add more detail to a log message about relaxed timeouts, to help
3900 - When learning a fingerprint for a bridge, log its corresponding
3901 transport type. Implements ticket 7896.
3902 - Warn more aggressively when flushing microdescriptors to a
3903 microdescriptor cache fails, in an attempt to mitigate bug 8031,
3904 or at least make it more diagnosable.
3905 - Improve the log message when "Bug/attack: unexpected sendme cell
3906 from client" occurs, to help us track bug 8093.
3907 - Improve debugging output to help track down bug 8185 ("Bug:
3908 outgoing relay cell has n_chan==NULL. Dropping.")
3910 o Minor features (log messages, quieter bootstrapping):
3911 - Log fewer lines at level "notice" about our OpenSSL and Libevent
3912 versions and capabilities when everything is going right. Resolves
3913 part of ticket 6736.
3914 - Omit the first heartbeat log message, because it never has anything
3915 useful to say, and it clutters up the bootstrapping messages.
3916 Resolves ticket 6758.
3917 - Don't log about reloading the microdescriptor cache at startup. Our
3918 bootstrap warnings are supposed to tell the user when there's a
3919 problem, and our bootstrap notices say when there isn't. Resolves
3920 ticket 6759; bugfix on 0.2.2.6-alpha.
3921 - Don't log "I learned some more directory information" when we're
3922 reading cached directory information. Reserve it for when new
3923 directory information arrives in response to a fetch. Resolves
3925 - Don't complain about bootstrapping problems while hibernating.
3926 These complaints reflect a general code problem, but not one
3927 with any problematic effects (no connections are actually
3928 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
3930 o Minor features (testing):
3931 - In our testsuite, create temporary directories with a bit more
3932 entropy in their name to make name collisions less likely. Fixes
3934 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
3935 (P-256) Diffie-Hellman handshakes to src/or/bench.
3936 - Add benchmark functions to test onion handshake performance.
3939 - The DirServer option is now DirAuthority, for consistency with
3940 current naming patterns. You can still use the old DirServer form.
3942 o Minor bugfixes (protocol):
3943 - Fix the handling of a TRUNCATE cell when it arrives while the
3944 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
3945 - When a Tor client gets a "truncated" relay cell, the first byte of
3946 its payload specifies why the circuit was truncated. We were
3947 ignoring this 'reason' byte when tearing down the circuit, resulting
3948 in the controller not being told why the circuit closed. Now we
3949 pass the reason from the truncated cell to the controller. Bugfix
3950 on 0.1.2.3-alpha; fixes bug 7039.
3951 - Fix a misframing issue when reading the version numbers in a
3952 VERSIONS cell. Previously we would recognize [00 01 00 02] as
3953 'version 1, version 2, and version 0x100', when it should have
3954 only included versions 1 and 2. Fixes bug 8059; bugfix on
3955 0.2.0.10-alpha. Reported pseudonymously.
3956 - Make the format and order of STREAM events for DNS lookups
3957 consistent among the various ways to launch DNS lookups. Fixes
3958 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy".
3960 o Minor bugfixes (syscalls and disk interaction):
3961 - Always check the return values of functions fcntl() and
3962 setsockopt(). We don't believe these are ever actually failing in
3963 practice, but better safe than sorry. Also, checking these return
3964 values should please analysis tools like Coverity. Patch from
3965 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
3966 - Avoid double-closing the listener socket in our socketpair()
3967 replacement (used on Windows) in the case where the addresses on
3968 our opened sockets don't match what we expected. Fixes bug 9400;
3969 bugfix on 0.0.2pre7. Found by Coverity.
3970 - Correctly store microdescriptors and extrainfo descriptors that
3971 include an internal NUL byte. Fixes bug 8037; bugfix on
3972 0.2.0.1-alpha. Bug reported by "cypherpunks".
3973 - If for some reason we fail to write a microdescriptor while
3974 rebuilding the cache, do not let the annotations from that
3975 microdescriptor linger in the cache file, and do not let the
3976 microdescriptor stay recorded as present in its old location.
3977 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
3978 - Use direct writes rather than stdio when building microdescriptor
3979 caches, in an attempt to mitigate bug 8031, or at least make it
3982 o Minor fixes (config options):
3983 - Warn and fail if a server is configured not to advertise any
3984 ORPorts at all. (We need *something* to put in our descriptor,
3985 or we just won't work.)
3986 - Behave correctly when the user disables LearnCircuitBuildTimeout
3987 but doesn't tell us what they would like the timeout to be. Fixes
3988 bug 6304; bugfix on 0.2.2.14-alpha.
3989 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
3990 to start with a triple-underscore so the controller won't touch it.
3991 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
3992 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
3993 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
3994 - When autodetecting the number of CPUs, use the number of available
3995 CPUs in preference to the number of configured CPUs. Inform the
3996 user if this reduces the number of available CPUs. Fixes bug 8002;
3997 bugfix on 0.2.3.1-alpha.
3998 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
3999 - Make it an error when you set EntryNodes but disable UseGuardNodes,
4000 since it will (surprisingly to some users) ignore EntryNodes. Fixes
4001 bug 8180; bugfix on 0.2.3.11-alpha.
4002 - Avoid overflows when the user sets MaxCircuitDirtiness to a
4003 ridiculously high value, by imposing a (ridiculously high) 30-day
4004 maximum on MaxCircuitDirtiness.
4006 o Minor bugfixes (control protocol):
4007 - Stop sending a stray "(null)" in some cases for the server status
4008 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
4010 - The ADDRMAP command can no longer generate an ill-formed error
4011 code on a failed MAPADDRESS. It now says "internal" rather than
4012 an English sentence fragment with spaces in the middle. Bugfix on
4015 o Minor bugfixes (clients / edges):
4016 - When we receive a RELAY_END cell with the reason DONE, or with no
4017 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
4018 status as "connection refused". Previously we reported these cases
4019 as success but then immediately closed the connection. Fixes bug
4020 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
4021 - If the guard we choose first doesn't answer, we would try the
4022 second guard, but once we connected to the second guard we would
4023 abandon it and retry the first one, slowing down bootstrapping.
4024 The fix is to treat all our initially chosen guards as acceptable
4025 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
4026 - When choosing which stream on a formerly stalled circuit to wake
4027 first, make better use of the platform's weak RNG. Previously,
4028 we had been using the % ("modulo") operator to try to generate a
4029 1/N chance of picking each stream, but this behaves badly with
4030 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
4033 o Minor bugfixes (path bias detection):
4034 - If the state file's path bias counts are invalid (presumably from a
4035 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
4036 additional checks and log messages to the scaling of Path Bias
4037 counts, in case there still are remaining issues with scaling.
4038 Should help resolve bug 8235.
4039 - Prevent rounding error in path bias counts when scaling
4040 them down, and use the correct scale factor default. Also demote
4041 some path bias related log messages down a level and make others
4042 less scary sounding. Fixes bug 6647. Bugfix on 0.2.3.17-beta.
4043 - Remove a source of rounding error during path bias count scaling;
4044 don't count cannibalized circuits as used for path bias until we
4045 actually try to use them; and fix a circuit_package_relay_cell()
4046 warning message about n_chan==NULL. Fixes bug 7802.
4047 - Paste the description for PathBias parameters from the man
4048 page into or.h, so the code documents them too. Fixes bug 7982;
4049 bugfix on 0.2.3.17-beta.
4051 o Minor bugfixes (relays):
4052 - Stop trying to resolve our hostname so often (e.g. every time we
4053 think about doing a directory fetch). Now we reuse the cached
4054 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
4055 and 2410 (bugfix on 0.1.2.2-alpha).
4056 - When examining the list of network interfaces to find our address,
4057 do not consider non-running or disabled network interfaces. Fixes
4058 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
4060 o Minor bugfixes (blocking resistance):
4061 - Only disable TLS session ticket support when running as a TLS
4062 server. Now clients will blend better with regular Firefox
4063 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
4065 o Minor bugfixes (IPv6):
4066 - Use square brackets around IPv6 addresses in numerous places
4067 that needed them, including log messages, HTTPS CONNECT proxy
4068 requests, TransportProxy statefile entries, and pluggable transport
4069 extra-info lines. Fixes bug 7011; patch by David Fifield.
4071 o Minor bugfixes (directory authorities):
4072 - Reject consensus votes with more than 64 known-flags. We aren't even
4073 close to that limit yet, and our code doesn't handle it correctly.
4074 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
4075 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
4076 bugfix on 0.2.0.3-alpha.
4078 o Minor bugfixes (memory leaks):
4079 - Avoid leaking memory if we fail to compute a consensus signature
4080 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
4081 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
4082 on 0.2.1.1-alpha; fixes bug 7816.
4083 - Fix a memory leak during safe-cookie controller authentication.
4084 Bugfix on 0.2.3.13-alpha; fixes bug 7816.
4085 - Free some more still-in-use memory at exit, to make hunting for
4086 memory leaks easier. Resolves bug 7029.
4088 o Minor bugfixes (code correctness):
4089 - Increase the width of the field used to remember a connection's
4090 link protocol version to two bytes. Harmless for now, since the
4091 only currently recognized versions are one byte long. Reported
4092 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
4093 - Fix a crash when debugging unit tests on Windows: deallocate a
4094 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
4095 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
4096 - When detecting the largest possible file descriptor (in order to
4097 close all file descriptors when launching a new program), actually
4098 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
4099 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
4101 - Avoid a crash if we fail to generate an extrainfo descriptor.
4102 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
4104 - Avoid an off-by-one error when checking buffer boundaries when
4105 formatting the exit status of a pluggable transport helper.
4106 This is probably not an exploitable bug, but better safe than
4107 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
4109 - Get rid of a couple of harmless clang warnings, where we compared
4110 enums to ints. These warnings are newly introduced in clang 3.2.
4112 o Minor bugfixes (code cleanliness):
4113 - Avoid use of reserved identifiers in our C code. The C standard
4114 doesn't like us declaring anything that starts with an
4115 underscore, so let's knock it off before we get in trouble. Fix
4116 for bug 1031; bugfix on the first Tor commit.
4117 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
4118 with large values. This situation was untriggered, but nevertheless
4119 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
4120 - Fix an impossible buffer overrun in the AES unit tests. Fixes
4121 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
4122 - Fix handling of rendezvous client authorization types over 8.
4123 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
4124 - Remove a couple of extraneous semicolons that were upsetting the
4125 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
4126 bugfix on 0.2.2.1-alpha.
4127 - When complaining about a client port on a public address, log
4128 which address we're complaining about. Fixes bug 4020; bugfix on
4129 0.2.3.3-alpha. Patch by Tom Fitzhenry.
4131 o Minor bugfixes (log messages, warnings):
4132 - If we encounter a write failure on a SOCKS connection before we
4133 finish our SOCKS handshake, don't warn that we closed the
4134 connection before we could send a SOCKS reply. Fixes bug 8427;
4135 bugfix on 0.1.0.1-rc.
4136 - Fix a directory authority warn caused when we have a large amount
4137 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
4138 - Downgrade "Failed to hand off onionskin" messages to "debug"
4139 severity, since they're typically redundant with the "Your computer
4140 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
4141 - Avoid spurious warnings when configuring multiple client ports of
4142 which only some are nonlocal. Previously, we had claimed that some
4143 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
4146 o Minor bugfixes (log messages, other):
4147 - Fix log messages and comments to avoid saying "GMT" when we mean
4148 "UTC". Fixes bug 6113.
4149 - When rejecting a configuration because we were unable to parse a
4150 quoted string, log an actual error message. Fixes bug 7950; bugfix
4152 - Correctly recognize that [::1] is a loopback address. Fixes
4153 bug 8377; bugfix on 0.2.1.3-alpha.
4154 - Don't log inappropriate heartbeat messages when hibernating: a
4155 hibernating node is _expected_ to drop out of the consensus,
4156 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
4157 bugfix on 0.2.3.1-alpha.
4158 - Eliminate several instances where we use "Nickname=ID" to refer to
4159 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
4160 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
4163 o Minor bugfixes (build):
4164 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
4165 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
4166 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
4168 o Documentation fixes:
4169 - Make the torify manpage no longer refer to tsocks; torify hasn't
4170 supported tsocks since 0.2.3.14-alpha.
4171 - Make the tor manpage no longer reference tsocks.
4172 - Fix the GeoIPExcludeUnknown documentation to refer to
4173 ExcludeExitNodes rather than the currently nonexistent
4174 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
4175 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
4177 - Say "KBytes" rather than "KB" in the man page (for various values
4178 of K), to further reduce confusion about whether Tor counts in
4179 units of memory or fractions of units of memory. Resolves ticket 7054.
4180 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
4181 names match. Fixes bug 7768.
4182 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
4183 message is logged at notice, not at info.
4184 - Clarify the usage and risks of setting the ContactInfo torrc line
4185 for your relay or bridge. Resolves ticket 9854.
4186 - Add anchors to the manpage so we can link to the html version of
4187 the documentation for specific options. Resolves ticket 9866.
4188 - Replace remaining references to DirServer in man page and
4189 log entries. Resolves ticket 10124.
4192 - Stop exporting estimates of v2 and v3 directory traffic shares
4193 in extrainfo documents. They were unneeded and sometimes inaccurate.
4194 Also stop exporting any v2 directory request statistics. Resolves
4196 - Drop support for detecting and warning about versions of Libevent
4197 before 1.3e. Nothing reasonable ships with them any longer; warning
4198 the user about them shouldn't be needed. Resolves ticket 6826.
4199 - Now that all versions before 0.2.2.x are disallowed, we no longer
4200 need to work around their missing features. Remove a bunch of
4204 - The tor-tsocks.conf is no longer distributed or installed. We
4205 recommend that tsocks users use torsocks instead. Resolves
4207 - Remove some of the older contents of doc/ as obsolete; move others
4208 to torspec.git. Fixes bug 8965.
4210 o Code simplification:
4211 - Avoid using character buffers when constructing most directory
4212 objects: this approach was unwieldy and error-prone. Instead,
4213 build smartlists of strings, and concatenate them when done.
4214 - Rename "isin" functions to "contains", for grammar. Resolves
4216 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
4217 with the natural logarithm function from the system libm. Resolves
4219 - Start using OpenBSD's implementation of queue.h, so that we don't
4220 need to hand-roll our own pointer and list structures whenever we
4221 need them. (We can't rely on a sys/queue.h, since some operating
4222 systems don't have them, and the ones that do have them don't all
4223 present the same extensions.)
4224 - Start using OpenBSD's implementation of queue.h (originally by
4226 - Enhance our internal sscanf replacement so that we can eliminate
4227 the last remaining uses of the system sscanf. (Though those uses
4228 of sscanf were safe, sscanf itself is generally error prone, so
4229 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
4231 - Replace all calls to snprintf() outside of src/ext with
4232 tor_snprintf(). Also remove the #define to replace snprintf with
4233 _snprintf on Windows; they have different semantics, and all of
4234 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
4237 - Add a wrapper function for the common "log a message with a
4239 - Split the onion.c file into separate modules for the onion queue
4240 and the different handshakes it supports.
4241 - Move the client-side address-map/virtual-address/DNS-cache code
4242 out of connection_edge.c into a new addressmap.c module.
4243 - Move the entry node code from circuitbuild.c to its own file.
4244 - Move the circuit build timeout tracking code from circuitbuild.c
4246 - Source files taken from other packages now reside in src/ext;
4247 previously they were scattered around the rest of Tor.
4248 - Move the generic "config" code into a new file, and have "config.c"
4249 hold only torrc- and state-related code. Resolves ticket 6823.
4250 - Move the core of our "choose a weighted element at random" logic
4251 into its own function, and give it unit tests. Now the logic is
4252 testable, and a little less fragile too.
4253 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
4254 - Move last_reachable and testing_since from routerinfo_t to node_t.
4255 Implements ticket 5529.
4256 - Add replaycache_t structure, functions and unit tests, then refactor
4257 rend_service_introduce() to be more clear to read, improve, debug,
4258 and test. Resolves bug 6177.
4261 - Remove some now-needless code that tried to aggressively flush
4262 OR connections as data was added to them. Since 0.2.0.1-alpha, our
4263 cell queue logic has saved us from the failure mode that this code
4264 was supposed to prevent. Removing this code will limit the number
4265 of baroque control flow paths through Tor's network logic. Reported
4266 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
4267 - Remove unused code for parsing v1 directories and "running routers"
4268 documents. Fixes bug 6887.
4269 - Remove the marshalling/unmarshalling code for sending requests to
4270 cpuworkers over a socket, and instead just send structs. The
4271 recipient will always be the same Tor binary as the sender, so
4272 any encoding is overkill.
4273 - Remove the testing_since field of node_t, which hasn't been used
4274 for anything since 0.2.0.9-alpha.
4275 - Finally remove support for malloc_good_size and malloc_usable_size.
4276 We had hoped that these functions would let us eke a little more
4277 memory out of our malloc implementation. Unfortunately, the only
4278 implementations that provided these functions are also ones that
4279 are already efficient about not overallocation: they never got us
4280 more than 7 or so bytes per allocation. Removing them saves us a
4281 little code complexity and a nontrivial amount of build complexity.
4284 Changes in version 0.2.3.25 - 2012-11-19
4285 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
4286 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
4287 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
4288 programmer, and friend. Unstinting in his dedication to the cause of
4289 freedom, he inspired and helped many of us as we began our work on
4290 anonymity, and inspires us still. Please honor his memory by writing
4291 software to protect people's freedoms, and by helping others to do so.
4293 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
4294 significantly reduced directory overhead (via microdescriptors),
4295 enormous crypto performance improvements for fast relays on new
4296 enough hardware, a new v3 TLS handshake protocol that can better
4297 resist fingerprinting, support for protocol obfuscation plugins (aka
4298 pluggable transports), better scalability for hidden services, IPv6
4299 support for bridges, performance improvements like allowing clients
4300 to skip the first round-trip on the circuit ("optimistic data") and
4301 refilling token buckets more often, a new "stream isolation" design
4302 to isolate different applications on different circuits, and many
4303 stability, security, and privacy fixes.
4305 Major features (v3 directory protocol):
4306 - Clients now use microdescriptors instead of regular descriptors
4307 to build circuits. Microdescriptors are authority-generated
4308 summaries of regular descriptors' contents, designed to change very
4309 rarely (see proposal 158 for details). This feature is designed
4310 to save bandwidth, especially for clients on slow internet
4311 connections. Use "UseMicrodescriptors 0" to disable it.
4312 - Caches now download, cache, and serve microdescriptors, as well
4313 as multiple "flavors" of the consensus, including a flavor that
4314 describes microdescriptors.
4316 o Major features (build hardening):
4317 - Enable gcc and ld hardening by default. Resolves ticket 5210.
4319 o Major features (relay scaling):
4320 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
4321 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
4322 vectorized AES implementations as appropriate. These can be much,
4323 much faster than other AES implementations.
4324 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
4325 implementation. It makes AES_CTR about 7% faster than our old one
4326 (which was about 10% faster than the one OpenSSL used to provide).
4327 Resolves ticket 4526.
4328 - Use OpenSSL's EVP interface for AES encryption, so that all AES
4329 operations can use hardware acceleration (if present). Resolves
4331 - Unconditionally use OpenSSL's AES implementation instead of our
4332 old built-in one. OpenSSL's AES has been better for a while, and
4333 relatively few servers should still be on any version of OpenSSL
4334 that doesn't have good optimized assembly AES.
4336 o Major features (blocking resistance):
4337 - Update TLS cipher list to match Firefox 8 and later. Resolves
4339 - Remove support for clients falsely claiming to support standard
4340 ciphersuites that they can actually provide. As of modern OpenSSL
4341 versions, it's not necessary to fake any standard ciphersuite,
4342 and doing so prevents us from using better ciphersuites in the
4343 future, since servers can't know whether an advertised ciphersuite
4344 is really supported or not. Some hosts -- notably, ones with very
4345 old versions of OpenSSL or where OpenSSL has been built with ECC
4346 disabled -- will stand out because of this change; TBB users should
4347 not be affected. Implements the client side of proposal 198.
4348 - Implement a new handshake protocol (v3) for authenticating Tors to
4349 each other over TLS. It should be more resistant to fingerprinting
4350 than previous protocols, and should require less TLS hacking for
4351 future Tor implementations. Implements proposal 176.
4352 - Allow variable-length padding cells, to disguise the length of
4353 Tor's TLS records. Implements part of proposal 184.
4354 - While we're trying to bootstrap, record how many TLS connections
4355 fail in each state, and report which states saw the most failures
4356 in response to any bootstrap failures. This feature may speed up
4357 diagnosis of censorship events. Implements ticket 3116.
4359 o Major features (pluggable transports):
4360 - Clients and bridges can now be configured to use a separate
4361 "transport" proxy. This approach makes the censorship arms race
4362 easier by allowing bridges to use protocol obfuscation plugins.
4363 Implements proposal 180 (tickets 2841 and 3472).
4365 o Major features (DoS resistance):
4366 - Now that Tor 0.2.0.x is completely deprecated, enable the final
4367 part of "Proposal 110: Avoiding infinite length circuits" by
4368 refusing all circuit-extend requests that do not use a relay_early
4369 cell. This change helps Tor resist a class of denial-of-service
4370 attacks by limiting the maximum circuit length.
4371 - Tear down the circuit if we get an unexpected SENDME cell. Clients
4372 could use this trick to make their circuits receive cells faster
4373 than our flow control would have allowed, or to gum up the network,
4374 or possibly to do targeted memory denial-of-service attacks on
4375 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
4376 from July 2002, before the release of Tor 0.0.0.
4378 o Major features (hidden services):
4379 - Adjust the number of introduction points that a hidden service
4380 will try to maintain based on how long its introduction points
4381 remain in use and how many introductions they handle. Fixes
4383 - Add a "tor2web mode" for clients that want to connect to hidden
4384 services non-anonymously (and possibly more quickly). As a safety
4385 measure to try to keep users from turning this on without knowing
4386 what they are doing, tor2web mode must be explicitly enabled at
4387 compile time, and a copy of Tor compiled to run in tor2web mode
4388 cannot be used as a normal Tor client. Implements feature 2553.
4390 o Major features (IPv6):
4391 - Clients can now connect to private bridges over IPv6. Bridges
4392 still need at least one IPv4 address in order to connect to
4393 other relays. Note that we don't yet handle the case where the
4394 user has two bridge lines for the same bridge (one IPv4, one
4395 IPv6). Implements parts of proposal 186.
4397 o Major features (directory authorities):
4398 - Use a more secure consensus parameter voting algorithm. Now at
4399 least three directory authorities or a majority of them must
4400 vote on a given parameter before it will be included in the
4401 consensus. Implements proposal 178.
4402 - Remove the artificially low cutoff of 20KB to guarantee the Fast
4403 flag. In the past few years the average relay speed has picked
4404 up, and while the "top 7/8 of the network get the Fast flag" and
4405 "all relays with 20KB or more of capacity get the Fast flag" rules
4406 used to have the same result, now the top 7/8 of the network has
4407 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
4409 o Major features (performance):
4410 - Exit nodes now accept and queue data on not-yet-connected streams.
4411 Previously, the client wasn't allowed to send data until the
4412 stream was connected, which slowed down all connections. This
4413 change will enable clients to perform a "fast-start" on streams
4414 and send data without having to wait for a confirmation that the
4415 stream has opened. Patch from Ian Goldberg; implements the server
4416 side of Proposal 174.
4417 - When using an exit relay running 0.2.3.x, clients can now
4418 "optimistically" send data before the exit relay reports that
4419 the stream has opened. This saves a round trip when starting
4420 connections where the client speaks first (such as web browsing).
4421 This behavior is controlled by a consensus parameter (currently
4422 disabled). To turn it on or off manually, use the "OptimisticData"
4423 torrc option. Implements proposal 181; code by Ian Goldberg.
4424 - Add a new TokenBucketRefillInterval option to refill token buckets
4425 more frequently than once per second. This should improve network
4426 performance, alleviate queueing problems, and make traffic less
4427 bursty. Implements proposal 183; closes ticket 3630. Design by
4428 Florian Tschorsch and Björn Scheuermann; implementation by
4430 - Raise the threshold of server descriptors needed (75%) and exit
4431 server descriptors needed (50%) before we will declare ourselves
4432 bootstrapped. This will make clients start building circuits a
4433 little later, but makes the initially constructed circuits less
4434 skewed and less in conflict with further directory fetches. Fixes
4437 o Major features (relays):
4438 - Relays now try regenerating and uploading their descriptor more
4439 frequently if they are not listed in the consensus, or if the
4440 version of their descriptor listed in the consensus is too
4441 old. This fix should prevent situations where a server declines
4442 to re-publish itself because it has done so too recently, even
4443 though the authorities decided not to list its recent-enough
4444 descriptor. Fix for bug 3327.
4446 o Major features (stream isolation):
4447 - You can now configure Tor so that streams from different
4448 applications are isolated on different circuits, to prevent an
4449 attacker who sees your streams as they leave an exit node from
4450 linking your sessions to one another. To do this, choose some way
4451 to distinguish the applications: have them connect to different
4452 SocksPorts, or have one of them use SOCKS4 while the other uses
4453 SOCKS5, or have them pass different authentication strings to the
4454 SOCKS proxy. Then, use the new SocksPort syntax to configure the
4455 degree of isolation you need. This implements Proposal 171.
4456 - There's a new syntax for specifying multiple client ports (such as
4457 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
4458 multiple *Port entries with full addr:port syntax on each.
4459 The old *ListenAddress format is still supported, but you can't
4460 mix it with the new *Port syntax.
4462 o Major features (bufferevents):
4463 - Tor can now optionally build with the "bufferevents" buffered IO
4464 backend provided by Libevent 2. To use this feature, make sure you
4465 have the latest possible version of Libevent, and pass the
4466 --enable-bufferevents flag to configure when building Tor from
4467 source. This feature will make our networking code more flexible,
4468 let us stack layers on each other, and let us use more efficient
4469 zero-copy transports where available.
4470 - Add experimental support for running on Windows with IOCP and no
4471 kernel-space socket buffers. This feature is controlled by a new
4472 "UserspaceIOCPBuffers" config option (off by default), which has
4473 no effect unless Tor has been built with bufferevents enabled,
4474 you're running on Windows, and you've set "DisableIOCP 0". In the
4475 long run, this may help solve or mitigate bug 98.
4477 o Major features (path selection):
4478 - The EntryNodes option can now include country codes like {de} or IP
4479 addresses or network masks. Previously we had disallowed these
4480 options because we didn't have an efficient way to keep the list up
4481 to date. Addresses ticket 1982, but see bug 2798 for an unresolved
4484 o Major features (port forwarding):
4485 - Add support for automatic port mapping on the many home routers
4486 that support NAT-PMP or UPnP. To build the support code, you'll
4487 need to have the libnatpnp library and/or the libminiupnpc library,
4488 and you'll need to enable the feature specifically by passing
4489 "--enable-upnp" and/or "--enable-natpnp" to ./configure. To turn
4490 it on, use the new PortForwarding option.
4492 o Major features (logging):
4493 - Add a new 'Heartbeat' log message type to periodically log a message
4494 describing Tor's status at level Notice. This feature is meant for
4495 operators who log at notice, and want to make sure that their Tor
4496 server is still working. Implementation by George Kadianakis.
4497 - Make logging resolution configurable with a new LogTimeGranularity
4498 option, and change the default from 1 millisecond to 1 second.
4499 Implements enhancement 1668.
4501 o Major features (other):
4502 - New "DisableNetwork" config option to prevent Tor from launching any
4503 connections or accepting any connections except on a control port.
4504 Bundles and controllers can set this option before letting Tor talk
4505 to the rest of the network, for example to prevent any connections
4506 to a non-bridge address. Packages like Orbot can also use this
4507 option to instruct Tor to save power when the network is off.
4508 - Try to use system facilities for enumerating local interface
4509 addresses, before falling back to our old approach (which was
4510 binding a UDP socket, and calling getsockname() on it). That
4511 approach was scaring OS X users whose draconian firewall
4512 software warned about binding to UDP sockets regardless of
4513 whether packets were sent. Now we try to use getifaddrs(),
4514 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
4515 system supports. Resolves ticket 1827.
4516 - Add experimental support for a "defaults" torrc file to be parsed
4517 before the regular torrc. Torrc options override the defaults file's
4518 options in the same way that the command line overrides the torrc.
4519 The SAVECONF controller command saves only those options which
4520 differ between the current configuration and the defaults file. HUP
4521 reloads both files. Implements task 4552.
4523 o New directory authorities:
4524 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
4525 authority. Closes ticket 5749.
4527 o Security/privacy fixes:
4528 - Avoid read-from-freed-memory and double-free bugs that could occur
4529 when a DNS request fails while launching it. Fixes bug 6480;
4530 bugfix on 0.2.0.1-alpha.
4531 - Reject any attempt to extend to an internal address. Without
4532 this fix, a router could be used to probe addresses on an internal
4533 network to see whether they were accepting connections. Fixes bug
4534 6710; bugfix on 0.0.8pre1.
4535 - Close any connection that sends unrecognized junk before the TLS
4536 handshake. Solves an issue noted in bug 4369.
4537 - The advertised platform of a relay now includes only its operating
4538 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not
4539 its service pack level (for Windows) or its CPU architecture
4540 (for Unix). Also drop the "git-XYZ" tag in the version. Packagers
4541 can insert an extra string in the platform line by setting the
4542 preprocessor variable TOR_BUILD_TAG. Resolves bug 2988.
4543 - Disable TLS session tickets. OpenSSL's implementation was giving
4544 our TLS session keys the lifetime of our TLS context objects, when
4545 perfect forward secrecy would want us to discard anything that
4546 could decrypt a link connection as soon as the link connection
4547 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
4548 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
4549 - Tor tries to wipe potentially sensitive data after using it, so
4550 that if some subsequent security failure exposes Tor's memory,
4551 the damage will be limited. But we had a bug where the compiler
4552 was eliminating these wipe operations when it decided that the
4553 memory was no longer visible to a (correctly running) program,
4554 hence defeating our attempt at defense in depth. We fix that
4555 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
4556 is unlikely to optimize away. Future versions of Tor may use
4557 a less ridiculously heavy approach for this. Fixes bug 7352.
4558 Reported in an article by Andrey Karpov.
4560 o Major bugfixes (crashes and asserts):
4561 - Avoid a pair of double-free and use-after-mark bugs that can
4562 occur with certain timings in canceled and re-received DNS
4563 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
4564 - Fix a denial of service attack by which any directory authority
4565 could crash all the others, or by which a single v2 directory
4566 authority could crash everybody downloading v2 directory
4567 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
4568 - Fix an assert that directory authorities could trigger on sighup
4569 during some configuration state transitions. We now don't treat
4570 it as a fatal error when the new descriptor we just generated in
4571 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
4572 - Avoid segfault when starting up having run with an extremely old
4573 version of Tor and parsing its state file. Fixes bug 6801; bugfix
4576 o Major bugfixes (clients):
4577 - If we are unable to find any exit that supports our predicted ports,
4578 stop calling them predicted, so that we don't loop and build
4579 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
4580 which introduced predicted ports.
4581 - Check at each new consensus whether our entry guards were picked
4582 long enough ago that we should rotate them. Previously, we only
4583 did this check at startup, which could lead to us holding a guard
4584 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
4585 - When fetching a bridge descriptor from a bridge authority,
4586 always do so anonymously, whether we have been able to open
4587 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
4588 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
4589 but we'll need to wait for bug 6010 before it's actually usable.
4591 o Major bugfixes (directory voting):
4592 - Check more thoroughly to prevent a rogue authority from
4593 double-voting on any consensus directory parameter. Previously,
4594 authorities would crash in this case if the total number of
4595 votes for any parameter exceeded the number of active voters,
4596 but would let it pass otherwise. Partially fixes bug 5786; bugfix
4598 - When computing weight parameters, behave more robustly in the
4599 presence of a bad bwweightscale value. Previously, the authorities
4600 would crash if they agreed on a sufficiently broken weight_scale
4601 value; now, they use a reasonable default and carry on. Fixes the
4602 rest of bug 5786; bugfix on 0.2.2.17-alpha.
4603 - If authorities are unable to get a v2 consensus document from other
4604 directory authorities, they no longer fall back to fetching
4605 them from regular directory caches. Fixes bug 5635; bugfix on
4606 0.2.2.26-beta, where routers stopped downloading v2 consensus
4609 o Major bugfixes (relays):
4610 - Fix a bug handling SENDME cells on nonexistent streams that could
4611 result in bizarre window values. Report and patch contributed
4612 pseudonymously. Fixes part of bug 6271. This bug was introduced
4613 before the first Tor release, in svn commit r152.
4614 - Don't update the AccountingSoftLimitHitAt state file entry whenever
4615 tor gets started. This prevents a wrong average bandwidth
4616 estimate, which would cause relays to always start a new accounting
4617 interval at the earliest possible moment. Fixes bug 2003; bugfix
4618 on 0.2.2.7-alpha. Reported by Bryon Eldridge, who also helped
4619 immensely in tracking this bug down.
4620 - Fix a possible crash bug when checking for deactivated circuits
4621 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
4622 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
4623 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
4624 connections. This change should allow busy exit relays to stop
4625 running out of available sockets as quickly. Fixes bug 4950;
4626 bugfix on 0.2.2.26-beta.
4628 o Major bugfixes (blocking resistance):
4629 - Bridges no longer include their address in NETINFO cells on outgoing
4630 OR connections, to allow them to blend in better with clients.
4631 Removes another avenue for enumerating bridges. Reported by
4632 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
4633 cells were introduced.
4634 - Warn the user when HTTPProxy, but no other proxy type, is
4635 configured. This can cause surprising behavior: it doesn't send
4636 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
4637 directory traffic only. Resolves ticket 4663.
4639 o Major bugfixes (hidden services):
4640 - Improve hidden service robustness: when an attempt to connect to
4641 a hidden service ends, be willing to refetch its hidden service
4642 descriptors from each of the HSDir relays responsible for them
4643 immediately. Previously, we would not consider refetching the
4644 service's descriptors from each HSDir for 15 minutes after the last
4645 fetch, which was inconvenient if the hidden service was not running
4646 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
4647 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
4648 They used to check that the timestamp was within 30 minutes
4649 of their system clock, so they could cap the size of their
4650 replay-detection cache, but that approach unnecessarily refused
4651 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
4652 the v3 intro-point protocol (the first one which sent a timestamp
4653 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
4654 - When one of a hidden service's introduction points appears to be
4655 unreachable, stop trying it. Previously, we would keep trying
4656 to build circuits to the introduction point until we lost the
4657 descriptor, usually because the user gave up and restarted Tor.
4658 Fixes part of bug 3825.
4660 o Changes to default torrc file:
4661 - Stop listing "socksport 9050" in torrc.sample. We open a socks
4662 port on 9050 by default anyway, so this should not change anything
4664 - Stop mentioning the deprecated *ListenAddress options in
4665 torrc.sample. Fixes bug 5438.
4666 - Document unit of bandwidth-related options in sample torrc.
4668 - Fix broken URLs in the sample torrc file, and tell readers about
4669 the OutboundBindAddress, ExitPolicyRejectPrivate, and
4670 PublishServerDescriptor options. Addresses bug 4652.
4672 o Minor features (directory authorities):
4673 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
4674 change when the authority is deciding whether to accept a newly
4675 uploaded descriptor. Implements ticket 6423.
4676 - Directory authorities are now a little more lenient at accepting
4677 older router descriptors, or newer router descriptors that don't
4678 make big changes. This should help ameliorate past and future
4679 issues where routers think they have uploaded valid descriptors,
4680 but the authorities don't think so. Fix for ticket 2479.
4681 - Authority operators can now vote for all relays in a given
4682 set of countries to be BadDir/BadExit/Invalid/Rejected.
4683 - Provide two consensus parameters (FastFlagMinThreshold and
4684 FastFlagMaxThreshold) to control the range of allowable bandwidths
4685 for the Fast directory flag. These allow authorities to run
4686 experiments on appropriate requirements for being a "Fast" node.
4687 The AuthDirFastGuarantee config value still applies. Implements
4690 o Minor features (bridges / bridge authorities):
4691 - Make bridge SSL certificates a bit more stealthy by using random
4692 serial numbers, in the same fashion as OpenSSL when generating
4693 self-signed certificates. Implements ticket 4584.
4694 - Tag a bridge's descriptor as "never to be sent unencrypted".
4695 This shouldn't matter, since bridges don't open non-anonymous
4696 connections to the bridge authority and don't allow unencrypted
4697 directory connections from clients, but we might as well make
4698 sure. Closes bug 5139.
4699 - The Bridge Authority now writes statistics on how many bridge
4700 descriptors it gave out in total, and how many unique descriptors
4701 it gave out. It also lists how often the most and least commonly
4702 fetched descriptors were given out, as well as the median and
4703 25th/75th percentile. Implements tickets 4200 and 4294.
4705 o Minor features (IPv6):
4706 - Make the code that clients use to detect an address change be
4707 IPv6-aware, so that it won't fill clients' logs with error
4708 messages when trying to get the IPv4 address of an IPv6
4709 connection. Implements ticket 5537.
4710 - Relays now understand an IPv6 address when they get one from a
4711 directory server. Resolves ticket 4875.
4713 o Minor features (hidden services):
4714 - Expire old or over-used hidden service introduction points.
4715 Required by fix for bug 3460.
4716 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
4717 public key replay-detection cache from 60 minutes to 5 minutes. This
4718 replay-detection cache is now used only to detect multiple
4719 INTRODUCE2 cells specifying the same rendezvous point, so we can
4720 avoid launching multiple simultaneous attempts to connect to it.
4721 - When a hidden service's introduction point times out, consider
4722 trying it again during the next attempt to connect to the
4723 HS. Previously, we would not try it again unless a newly fetched
4724 descriptor contained it. Required by fixes for bugs 1297 and 3825.
4726 o Minor features (relays):
4727 - Relays now include a reason for regenerating their descriptors
4728 in an HTTP header when uploading to the authorities. This will
4729 make it easier to debug descriptor-upload issues in the future.
4730 - Turn on directory request statistics by default and include them in
4731 extra-info descriptors. Don't break if we have no GeoIP database.
4732 - Replace files in stats/ rather than appending to them. Now that we
4733 include statistics in extra-info descriptors, it makes no sense to
4734 keep old statistics forever. Implements ticket 2930.
4735 - Relays that set "ConnDirectionStatistics 1" write statistics on the
4736 bidirectional use of connections to disk every 24 hours.
4737 - Add a GeoIP file digest to the extra-info descriptor. Implements
4740 o Minor features (new config options):
4741 - New config option "DynamicDHGroups" (disabled by default) provides
4742 each bridge with a unique prime DH modulus to be used during
4743 SSL handshakes. This option attempts to help against censors
4744 who might use the Apache DH modulus as a static identifier for
4745 bridges. Addresses ticket 4548.
4746 - New config option "DisableDebuggerAttachment" (on by default)
4747 to prevent basic debugging attachment attempts by other processes.
4748 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
4749 - Ordinarily, Tor does not count traffic from private addresses (like
4750 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
4751 There is now a new option, CountPrivateBandwidth, to disable this
4752 behavior. Patch from Daniel Cagara.
4754 o Minor features (different behavior for old config options):
4755 - Allow MapAddress directives to specify matches against super-domains,
4756 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
4757 Implements issue 933.
4758 - Don't disable the DirPort when we cannot exceed our AccountingMax
4759 limit during this interval because the effective bandwidthrate is
4760 low enough. This is useful in a situation where AccountMax is only
4761 used as an additional safeguard or to provide statistics.
4762 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
4763 implements ticket 3439.
4764 - When configuring a large set of nodes in EntryNodes, and there are
4765 enough of them listed as Guard so that we don't need to consider
4766 the non-guard entries, prefer the ones listed with the Guard flag.
4767 - If you set the NumCPUs option to 0, Tor will now try to detect how
4768 many CPUs you have. This is the new default behavior.
4769 - The NodeFamily option -- which let you declare that you want to
4770 consider nodes to be part of a family whether they list themselves
4771 that way or not -- now allows IP address ranges and country codes.
4773 o Minor features (new command-line config behavior):
4774 - Slightly change behavior of "list" options (that is, config
4775 options that can appear more than once) when they appear both in
4776 torrc and on the command line. Previously, the command-line options
4777 would be appended to the ones from torrc. Now, the command-line
4778 options override the torrc options entirely. This new behavior
4779 allows the user to override list options (like exit policies and
4780 ports to listen on) from the command line, rather than simply
4781 appending to the list.
4782 - You can get the old (appending) command-line behavior for "list"
4783 options by prefixing the option name with a "+".
4784 - You can remove all the values for a "list" option from the command
4785 line without adding any new ones by prefixing the option name
4788 o Minor features (controller, new events):
4789 - Extend the control protocol to report flags that control a circuit's
4790 path selection in CIRC events and in replies to 'GETINFO
4791 circuit-status'. Implements part of ticket 2411.
4792 - Extend the control protocol to report the hidden service address
4793 and current state of a hidden-service-related circuit in CIRC
4794 events and in replies to 'GETINFO circuit-status'. Implements part
4796 - Include the creation time of a circuit in CIRC and CIRC2
4797 control-port events and the list produced by the 'GETINFO
4798 circuit-status' control-port command.
4799 - Add a new CONF_CHANGED event so that controllers can be notified
4800 of any configuration changes made by other controllers, or by the
4801 user. Implements ticket 1692.
4802 - Add a new SIGNAL event to the controller interface so that
4803 controllers can be notified when Tor handles a signal. Resolves
4804 issue 1955. Patch by John Brooks.
4806 o Minor features (controller, new getinfo options):
4807 - Expose our view of whether we have gone dormant to the controller,
4808 via a new "GETINFO dormant" value. Torbutton and other controllers
4809 can use this to avoid doing periodic requests through Tor while
4810 it's dormant (bug 4718). Resolves ticket 5954.
4811 - Add a new GETINFO option to get total bytes read and written. Patch
4812 from pipe, revised by atagar. Resolves ticket 2345.
4813 - Implement new GETINFO controller fields to provide information about
4814 the Tor process's pid, euid, username, and resource limits.
4816 o Minor features (controller, other):
4817 - Allow controllers to request an event notification whenever a
4818 circuit is cannibalized or its purpose is changed. Implements
4819 part of ticket 3457.
4820 - Use absolute path names when reporting the torrc filename in the
4821 control protocol, so a controller can more easily find the torrc
4822 file. Resolves bug 1101.
4823 - When reporting the path to the cookie file to the controller,
4824 give an absolute path. Resolves ticket 4881.
4826 o Minor features (log messages):
4827 - Add more information to a log statement that might help track down
4828 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
4829 non-IP address" messages (or any Bug messages, for that matter!),
4830 please let us know about it.
4831 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
4832 EntryNodes will have no effect. Resolves issue 2571.
4833 - Try to make the introductory warning message that Tor prints on
4834 startup more useful for actually finding help and information.
4835 Resolves ticket 2474.
4836 - When the system call to create a listener socket fails, log the
4837 error message explaining why. This may help diagnose bug 4027.
4839 o Minor features (other):
4840 - When we fail to initialize Libevent, retry with IOCP disabled so we
4841 don't need to turn on multi-threading support in Libevent, which in
4842 turn requires a working socketpair(). This is a workaround for bug
4843 4457, which affects Libevent versions from 2.0.1-alpha through
4845 - When starting as root and then changing our UID via the User
4846 control option, and we have a ControlSocket configured, make sure
4847 that the ControlSocket is owned by the same account that Tor will
4848 run under. Implements ticket 3421; fix by Jérémy Bobbio.
4849 - Accept attempts to include a password authenticator in the
4850 handshake, as supported by SOCKS5. This handles SOCKS clients that
4851 don't know how to omit a password when authenticating. Resolves
4853 - Check for and recover from inconsistency in the microdescriptor
4854 cache. This will make it harder for us to accidentally free a
4855 microdescriptor without removing it from the appropriate data
4856 structures. Fixes issue 3135; issue noted by "wanoskarnet".
4857 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
4859 o Minor bugfixes (code security):
4860 - Prevent a null-pointer dereference when receiving a data cell
4861 for a nonexistent stream when the circuit in question has an
4862 empty deliver window. We don't believe this is triggerable,
4863 since we don't currently allow deliver windows to become empty,
4864 but the logic is tricky enough that it's better to make the code
4865 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
4866 - Fix a (harmless) integer overflow in cell statistics reported by
4867 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
4868 - Fix our implementation of crypto_random_hostname() so it can't
4869 overflow on ridiculously large inputs. (No Tor version has ever
4870 provided this kind of bad inputs, but let's be correct in depth.)
4871 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
4872 - Add a (probably redundant) memory clear between iterations of
4873 the router status voting loop, to prevent future coding errors
4874 where data might leak between iterations of the loop. Resolves
4877 o Minor bugfixes (wrapper functions):
4878 - Abort if tor_vasprintf() fails in connection_printf_to_buf() (a
4879 utility function used in the control-port code). This shouldn't
4880 ever happen unless Tor is completely out of memory, but if it did
4881 happen and Tor somehow recovered from it, Tor could have sent a log
4882 message to a control port in the middle of a reply to a controller
4883 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
4884 - Fix some (not actually triggerable) buffer size checks in usage of
4885 tor_inet_ntop(). Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
4887 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
4888 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
4889 - Enforce correct return behavior of tor_vsscanf() when the '%%'
4890 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
4891 - Make our replacement implementation of strtok_r() compatible with
4892 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
4893 bugfix on 0.2.2.1-alpha.
4894 - Find more places in the code that should have been testing for
4895 invalid sockets using the SOCKET_OK macro. Required for a fix
4896 for bug 4533. Bugfix on 0.2.2.28-beta.
4898 o Minor bugfixes (code correctness):
4899 - Check return value of fputs() when writing authority certificate
4900 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
4901 - When building Tor on Windows with -DUNICODE (not default), ensure
4902 that error messages, filenames, and DNS server names are always
4903 NUL-terminated when we convert them to a single-byte encoding.
4904 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
4905 - Fix a memory leak when trying to launch a DNS request when the
4906 nameservers are unconfigurable. Fixes bug 5916; bugfix on Tor
4908 - Correct file sizes when reading binary files on Cygwin, to avoid
4909 a bug where Tor would fail to read its state file. Fixes bug 6844;
4910 bugfix on 0.1.2.7-alpha.
4911 - Make sure to set *socket_error in all error cases in
4912 connection_connect(), so it can't produce a warning about
4913 errno being zero from errno_to_orconn_end_reason(). Bugfix on
4914 0.2.1.1-alpha; resolves ticket 6028.
4915 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
4916 bug 4532; found by "troll_un".
4918 o Minor bugfixes (clients):
4919 - Allow one-hop directory-fetching circuits the full "circuit build
4920 timeout" period, rather than just half of it, before failing them
4921 and marking the relay down. This fix should help reduce cases where
4922 clients declare relays (or worse, bridges) unreachable because
4923 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
4924 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
4926 - Ensure we don't cannibalize circuits that are longer than three hops
4927 already, so we don't end up making circuits with 5 or more
4928 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
4929 0.1.0.1-rc which introduced cannibalization.
4931 o Minor bugfixes (relays):
4932 - Don't publish a new relay descriptor when we reload our onion key,
4933 unless the onion key has actually changed. Fixes bug 3263 and
4934 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
4935 - When relays refuse a "create" cell because their queue of pending
4936 create cells is too big (typically because their cpu can't keep up
4937 with the arrival rate), send back reason "resource limit" rather
4938 than reason "internal", so network measurement scripts can get a
4939 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
4940 - Exit nodes don't need to fetch certificates for authorities that
4941 they don't recognize; only directory authorities, bridges,
4942 and caches need to do that. Fixes part of bug 2297; bugfix on
4945 o Minor bugfixes (directory authority / mirrors):
4946 - Avoid O(n^2) performance characteristics when parsing a large
4947 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
4948 - Authorities no longer include any router in their microdescriptor
4949 consensuses for which they couldn't generate or agree on a
4950 microdescriptor. Fixes the second piece of bug 6404; fix on
4952 - When checking for requested signatures on the latest consensus
4953 before serving it to a client, make sure to check the right
4954 consensus flavor. Bugfix on 0.2.2.6-alpha.
4955 - Fix an edge case where TestingTorNetwork is set but the authorities
4956 and relays all have an uptime of zero, so the private Tor network
4957 could briefly lack support for hidden services. Fixes bug 3886;
4958 bugfix on 0.2.2.18-alpha.
4959 - Directory caches no longer refuse to clean out descriptors because
4960 of missing v2 networkstatus documents, unless they're configured
4961 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
4962 0.2.2.26-beta. Patch by Daniel Bryg.
4963 - Don't serve or accept v2 hidden service descriptors over a relay's
4964 DirPort. It's never correct to do so, and disabling it might
4965 make it more annoying to exploit any bugs that turn up in the
4966 descriptor-parsing code. Fixes bug 7149.
4968 o Minor bugfixes (hidden services, client-side):
4969 - Assert that hidden-service-related operations are not performed
4970 using single-hop circuits. Previously, Tor would assert that
4971 client-side streams are not attached to single-hop circuits,
4972 but not that other sensitive operations on the client and service
4973 side are not performed using single-hop circuits. Fixes bug 3332;
4975 - Avoid undefined behavior when parsing the list of supported
4976 rendezvous/introduction protocols in a hidden service descriptor.
4977 Previously, Tor would have confused (as-yet-unused) protocol version
4978 numbers greater than 32 with lower ones on many platforms. Fixes
4979 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
4980 - Don't close hidden service client circuits which have almost
4981 finished connecting to their destination when they reach
4982 the normal circuit-build timeout. Previously, we would close
4983 introduction circuits which are waiting for an acknowledgement
4984 from the introduction point, and rendezvous circuits which have
4985 been specified in an INTRODUCE1 cell sent to a hidden service,
4986 after the normal CBT. Now, we mark them as 'timed out', and launch
4987 another rendezvous attempt in parallel. This behavior change can
4988 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
4989 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
4991 o Minor bugfixes (hidden services, service-side):
4992 - Don't close hidden-service-side rendezvous circuits when they
4993 reach the normal circuit-build timeout. This behavior change can
4994 be disabled using the new
4995 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
4996 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
4997 - Don't launch more than 10 service-side introduction-point circuits
4998 for a hidden service in five minutes. Previously, we would consider
4999 launching more introduction-point circuits if at least one second
5000 had passed without any introduction-point circuits failing. Fixes
5001 bug 4607; bugfix on 0.0.7pre1.
5003 o Minor bugfixes (config option behavior):
5004 - If the user tries to set MyFamily on a bridge, refuse to
5005 do so, and warn about the security implications. Fixes bug 4657;
5006 bugfix on 0.2.0.3-alpha.
5007 - The "--quiet" and "--hush" options now apply not only to Tor's
5008 behavior before logs are configured, but also to Tor's behavior in
5009 the absense of configured logs. Fixes bug 3550; bugfix on
5011 - Change the AllowDotExit rules so they should actually work.
5012 We now enforce AllowDotExit only immediately after receiving an
5013 address via SOCKS or DNSPort: other sources are free to provide
5014 .exit addresses after the resolution occurs. Fixes bug 3940;
5015 bugfix on 0.2.2.1-alpha.
5016 - Make "LearnCircuitBuildTimeout 0" work more reliably. Specifically,
5017 don't depend on the consensus parameters or compute adaptive
5018 timeouts when it is disabled. Fixes bug 5049; bugfix on
5020 - After we pick a directory mirror, we would refuse to use it if
5021 it's in our ExcludeExitNodes list, resulting in mysterious failures
5022 to bootstrap for people who just wanted to avoid exiting from
5023 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
5024 - When told to add a bridge with the same digest as a preexisting
5025 bridge but a different addr:port, change the addr:port as
5026 requested. Previously we would not notice the change. Fixes half
5027 of bug 5603; fix on 0.2.2.26-beta.
5029 o Minor bugfixes (controller):
5030 - Allow manual 'authenticate' commands to the controller interface
5031 from netcat (nc) as well as telnet. We were rejecting them because
5032 they didn't come with the expected whitespace at the end of the
5033 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
5034 - Report a real bootstrap problem to the controller on router
5035 identity mismatch. Previously we just said "foo", which probably
5036 made a lot of sense at the time. Fixes bug 4169; bugfix on
5038 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
5039 option is set to 0 (which Vidalia version 0.2.16 now does when
5040 a SAVECONF attempt fails), perform other actions that SIGHUP
5041 usually causes (like reopening the logs). Fixes bug 5095; bugfix
5043 - Correctly handle checking the permissions on the parent
5044 directory of a control socket in the root directory. Bug found
5045 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
5047 - End AUTHCHALLENGE error messages (in the control protocol) with
5048 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36.
5050 o Minor bugfixes (network reading/writing):
5051 - Disable writing on marked-for-close connections when they are
5052 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
5053 bug 5263; bugfix on 0.0.2pre13, where we first added a special
5054 case for flushing marked connections.
5055 - Make sure that there are no unhandled pending TLS errors before
5056 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
5057 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
5058 Bugfix on 0.1.0.5-rc; fixes bug 4528.
5059 - Detect SSL handshake even when the initial attempt to write the
5060 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
5061 - If the client fails to set a reasonable set of ciphersuites
5062 during its v2 handshake renegotiation, allow the renegotiation to
5063 continue nevertheless (i.e. send all the required certificates).
5064 Fixes bug 4591; bugfix on 0.2.0.20-rc.
5066 o Minor bugfixes (other):
5067 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
5068 resource exhaustion, so that clients can adjust their load to
5069 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
5070 started using END_STREAM_REASON_RESOURCELIMIT.
5071 - Don't check for whether the address we're using for outbound
5072 connections has changed until after the outbound connection has
5073 completed. On Windows, getsockname() doesn't succeed until the
5074 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
5075 - Don't hold a Windows file handle open for every file mapping;
5076 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
5078 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
5079 bugfix on 0.2.1.10-alpha.
5080 - If we fail to write a microdescriptor to the disk cache, do not
5081 continue replacing the old microdescriptor file. Fixes bug 2954;
5082 bugfix on 0.2.2.6-alpha.
5084 o Minor bugfixes (log messages, path selection):
5085 - Downgrade "set buildtimeout to low value" messages to "info"
5086 severity; they were never an actual problem, there was never
5087 anything reasonable to do about them, and they tended to spam logs
5088 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
5089 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
5090 more information to it, so that we can track it down in case it
5091 returns again. Mitigates bug 5235.
5092 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
5093 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
5094 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
5095 - Issue a log message if a guard completes less than 40% of your
5096 circuits. Threshold is configurable by torrc option
5097 PathBiasNoticeRate and consensus parameter pb_noticepct. There is
5098 additional, off-by-default code to disable guards which fail too
5099 many circuits. Addresses ticket 5458.
5101 o Minor bugfixes (log messages, client):
5102 - Downgrade "Got a certificate, but we already have it" log messages
5103 from warning to info, except when we're a dirauth. Fixes bug 5238;
5104 bugfix on 0.2.1.7-alpha.
5105 - Fix the log message describing how we work around discovering
5106 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
5107 4837; bugfix on 0.2.2.9-alpha.
5108 - When logging about a disallowed .exit name, do not also call it
5109 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
5110 - Fix a log message suggesting that people contact a non-existent
5111 email address. Fixes bug 3448.
5112 - Rephrase the log message emitted if the TestSocks check is
5113 successful. Patch from Fabian Keil; fixes bug 4094.
5114 - Log (at debug level) whenever a circuit's purpose is changed.
5115 - Log SSL state transitions at log level DEBUG, log domain
5116 HANDSHAKE. This can be useful for debugging censorship events.
5117 Implements ticket 3264.
5118 - We now log which torrc file we're using on startup. Implements
5120 - Rate-limit log messages when asked to connect anonymously to
5121 a private address. When these hit, they tended to hit fast and
5122 often. Also, don't bother trying to connect to addresses that we
5123 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
5124 reply makes us think we have been lied to, even when the address the
5125 client tried to connect to was "localhost." Resolves ticket 2822.
5127 o Minor bugfixes (log messages, non-client):
5128 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
5129 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
5130 - Don't log that we have "decided to publish new relay descriptor"
5131 unless we are actually publishing a descriptor. Fixes bug 3942;
5132 bugfix on 0.2.2.28-beta.
5133 - Log which authority we're missing votes from when we go to fetch
5134 them from the other auths.
5135 - Replace "Sending publish request" log messages with "Launching
5136 upload", so that they no longer confusingly imply that we're
5137 sending something to a directory we might not even be connected
5138 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
5139 - Warn when Tor is configured to use accounting in a way that can
5140 link a hidden service to some other hidden service or public
5141 address. Resolves ticket 6490.
5142 - Fix a minor formatting issue in one of tor-gencert's error messages.
5146 - Update to the latest version of the tinytest unit testing framework.
5147 This includes a couple of bugfixes that can be relevant for
5148 running forked unit tests on Windows, and removes all reserved
5150 - Avoid a false positive in the util/threads unit test by increasing
5151 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
5152 - Make it possible to set the TestingTorNetwork configuration
5153 option using AlternateDirAuthority and AlternateBridgeAuthority
5154 as an alternative to setting DirServer. Addresses ticket 6377.
5155 - Add a unit test for the environment_variable_names_equal() function.
5156 - A wide variety of new unit tests by Esteban Manchado Velázquez.
5157 - Numerous new unit tests for functions in util.c and address.c by
5159 - The long-disabled benchmark tests are now split into their own
5160 ./src/test/bench binary.
5161 - The benchmark tests can now use more accurate timers than
5162 gettimeofday() when such timers are available.
5163 - Use tt_assert(), not tor_assert(), for checking for test failures.
5164 This makes the unit tests more able to go on in the event that
5167 o Build improvements:
5168 - Use the dead_strip option when building Tor on OS X. This reduces
5169 binary size by almost 19% when linking openssl and libevent
5170 statically, which we do for Tor Browser Bundle.
5171 - Provide a better error message about possible OSX Asciidoc failure
5172 reasons. Fixes bug 6436.
5173 - Detect attempts to build Tor on (as yet hypothetical) versions
5174 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
5175 fix for bug 4533. Bugfix on 0.2.2.28-beta.
5176 - On Windows, we now define the _WIN32_WINNT macros only if they
5177 are not already defined. This lets the person building Tor decide,
5178 if they want, to require a later version of Windows.
5179 - Our autogen.sh script now uses autoreconf to launch autoconf,
5180 automake, and so on. This is more robust against some of the failure
5181 modes associated with running the autotools pieces on their own.
5182 - Running "make version" now displays the version of Tor that
5183 we're about to build. Idea from katmagic; resolves issue 4400.
5184 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
5185 on 0.2.2.4-alpha; fixes bug 3427.
5186 - New --enable-static-tor configure option for building Tor as
5187 statically as possible. Idea, general hackery and thoughts from
5188 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
5190 - Limited, experimental support for building with nmake and MSVC.
5192 o Build requirements:
5193 - Building Tor with bufferevent support now requires Libevent
5194 2.0.13-stable or later. Previous versions of Libevent had bugs in
5195 SSL-related bufferevents and related issues that would make Tor
5196 work badly with bufferevents. Requiring 2.0.13-stable also allows
5197 Tor with bufferevents to take advantage of Libevent APIs
5198 introduced after 2.0.8-rc.
5199 - Our build system requires automake 1.6 or later to create the
5200 Makefile.in files. Previously, you could have used 1.4.
5201 This only affects developers and people building Tor from git;
5202 people who build Tor from the source distribution without changing
5203 the Makefile.am files should be fine.
5204 - Detect when we try to build on a platform that doesn't define
5205 AF_UNSPEC to 0. We don't work there, so refuse to compile.
5207 o Build fixes (compile/link):
5208 - Format more doubles with %f, not %lf. Patch from grarpamp to make
5209 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
5211 - When building with --enable-static-tor on OpenBSD, do not
5212 erroneously attempt to link -lrt. Fixes bug 5103.
5213 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
5214 that IPv6 stuff will compile on MSVC, and compilation issues
5215 will be easier to track down. Fixes bug 5861.
5216 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
5217 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
5218 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
5219 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
5221 o Build fixes (other):
5222 - Use the _WIN32 macro throughout our code to detect Windows.
5223 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
5225 - Properly handle the case where the build-tree is not the same
5226 as the source tree when generating src/common/common_sha1.i,
5227 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
5228 bugfix on 0.2.0.1-alpha.
5229 - During configure, search for library containing cos function as
5230 libm lives in libcore on some platforms (BeOS/Haiku). Linking
5231 against libm was hard-coded before. Fixes the first part of bug
5232 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
5234 - Prevent a false positive from the check-spaces script, by disabling
5235 the "whitespace between function name and (" check for functions
5238 o Packaging (RPM) changes:
5239 - Update our default RPM spec files to work with mock and rpmbuild
5240 on RHEL/Fedora. They have an updated set of dependencies and
5241 conflicts, a fix for an ancient typo when creating the "_tor"
5242 user, and better instructions. Thanks to Ondrej Mikle for the
5243 patch series. Fixes bug 6043.
5244 - On OpenSUSE, create the /var/run/tor directory on startup if it
5245 is not already created. Patch from Andreas Stieger. Fixes bug 2573.
5247 o Code refactoring (safety):
5248 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
5249 10 lines. Also, don't nest them. Doing so in the past has
5250 led to hard-to-debug code. The new style is to use the
5251 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
5252 - Use macros to indicate OpenSSL versions, so we don't need to worry
5253 about accidental hexadecimal bit shifts.
5254 - Use tor_sscanf() in place of scanf() in more places through the
5255 code. This makes us a little more locale-independent, and
5256 should help shut up code-analysis tools that can't tell
5257 a safe sscanf string from a dangerous one.
5258 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
5259 - Use the smartlist_add_asprintf() alias more consistently.
5261 o Code refactoring (consolidate):
5262 - A major revision to our internal node-selecting and listing logic.
5263 Tor already had at least two major ways to look at the question of
5264 "which Tor servers do we know about": a list of router descriptors,
5265 and a list of entries in the current consensus. With
5266 microdescriptors, we're adding a third. Having so many systems
5267 without an abstraction layer over them was hurting the codebase.
5268 Now, we have a new "node_t" abstraction that presents a consistent
5269 interface to a client's view of a Tor node, and holds (nearly) all
5270 of the mutable state formerly in routerinfo_t and routerstatus_t.
5271 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
5272 Libevent's notion of cached time when possible.
5273 - Remove duplicate code for invoking getrlimit() from control.c.
5274 - Use OpenSSL's built-in SSL_state_string_long() instead of our
5275 own homebrewed ssl_state_to_string() replacement. Patch from
5276 Emile Snyder. Fixes bug 4653.
5277 - Change the symmetric cipher interface so that creating and
5278 initializing a stream cipher are no longer separate functions.
5280 o Code refactoring (separate):
5281 - Make a new "entry connection" struct as an internal subtype of "edge
5282 connection", to simplify the code and make exit connections smaller.
5283 - Split connection_about_to_close() into separate functions for each
5285 - Rewrite the listener-selection logic so that parsing which ports
5286 we want to listen on is now separate from binding to the ports
5289 o Code refactoring (name changes):
5290 - Rename a handful of old identifiers, mostly related to crypto
5291 structures and crypto functions. By convention, our "create an
5292 object" functions are called "type_new()", our "free an object"
5293 functions are called "type_free()", and our types indicate that
5294 they are types only with a final "_t". But a handful of older
5295 types and functions broke these rules, with function names like
5296 "type_create" or "subsystem_op_type", or with type names like
5298 - Rename Tor functions that turn strings into addresses, so that
5299 "parse" indicates that no hostname resolution occurs, and
5300 "lookup" indicates that hostname resolution may occur. This
5301 should help prevent mistakes in the future. Fixes bug 3512.
5302 - Use the name "CERTS" consistently to refer to the new cell type;
5303 we were calling it CERT in some places and CERTS in others.
5304 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
5305 invalid value, rather than just -1.
5306 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
5307 can pick them up when the tests aren't disabled. Bugfix on
5308 0.2.2.4-alpha which introduced tinytest.
5310 o Code refactoring (other):
5311 - Defensively refactor rend_mid_rendezvous() so that protocol
5312 violations and length checks happen in the beginning. Fixes
5314 - Remove the pure attribute from all functions that used it
5315 previously. In many cases we assigned it incorrectly, because the
5316 functions might assert or call impure functions, and we don't have
5317 evidence that keeping the pure attribute is worthwhile. Implements
5318 changes suggested in ticket 4421.
5319 - Move the replay-detection cache for the RSA-encrypted parts of
5320 INTRODUCE2 cells to the introduction point data structures.
5321 Previously, we would use one replay-detection cache per hidden
5322 service. Required by fix for bug 3460.
5323 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
5324 no longer link against Libevent: they never used it, but
5325 our library structure used to force them to link it.
5327 o Removed features and files:
5328 - Remove all internal support for unpadded RSA. We never used it, and
5329 it would be a bad idea to start.
5330 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
5332 - Remove some redundant #include directives throughout the code.
5333 Patch from Andrea Gelmini.
5334 - Remove some old code to remember statistics about which descriptors
5335 we've served as a directory mirror. The feature wasn't used and
5336 is outdated now that microdescriptors are around.
5337 - Remove some old code to work around even older versions of Tor that
5338 used forked processes to handle DNS requests. Such versions of Tor
5339 are no longer in use as relays.
5340 - The "torify" script no longer supports the "tsocks" socksifier
5341 tool, since tsocks doesn't support DNS and UDP right for Tor.
5342 Everyone should be using torsocks instead. Fixes bugs 3530 and
5343 5180. Based on a patch by "ugh".
5344 - Remove the torrc.bridge file: we don't use it for anything, and
5345 it had become badly desynchronized from torrc.sample. Resolves
5349 - Begin a doc/state-contents.txt file to explain the contents of
5350 the Tor state file. Fixes bug 2987.
5351 - Clarify the documentation for the Alternate*Authority options.
5353 - Document the --defaults-torrc option, and the new semantics for
5354 overriding, extending, and clearing lists of options. Closes
5356 - Add missing man page documentation for consensus and microdesc
5357 files. Resolves ticket 6732.
5358 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
5360 o Documentation fixes:
5361 - Improve the manual's documentation for the NT Service command-line
5362 options. Addresses ticket 3964.
5363 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
5364 - Document the changes to the ORPort and DirPort options, and the
5365 fact that {OR/Dir}ListenAddress is now unnecessary (and
5366 therefore deprecated). Resolves ticket 5597.
5367 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
5368 - Clarify that hidden services are TCP only. Fixes bug 6024.
5371 Changes in version 0.2.2.39 - 2012-09-11
5372 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
5376 - Fix an assertion failure in tor_timegm() that could be triggered
5377 by a badly formatted directory object. Bug found by fuzzing with
5378 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
5379 - Do not crash when comparing an address with port value 0 to an
5380 address policy. This bug could have been used to cause a remote
5381 assertion failure by or against directory authorities, or to
5382 allow some applications to crash clients. Fixes bug 6690; bugfix
5386 Changes in version 0.2.2.38 - 2012-08-12
5387 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
5388 attack that could in theory leak path information.
5391 - Avoid an uninitialized memory read when reading a vote or consensus
5392 document that has an unrecognized flavor name. This read could
5393 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
5394 - Try to leak less information about what relays a client is
5395 choosing to a side-channel attacker. Previously, a Tor client would
5396 stop iterating through the list of available relays as soon as it
5397 had chosen one, thus finishing a little earlier when it picked
5398 a router earlier in the list. If an attacker can recover this
5399 timing information (nontrivial but not proven to be impossible),
5400 they could learn some coarse-grained information about which relays
5401 a client was picking (middle nodes in particular are likelier to
5402 be affected than exits). The timing attack might be mitigated by
5403 other factors (see bug 6537 for some discussion), but it's best
5404 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
5407 Changes in version 0.2.2.37 - 2012-06-06
5408 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
5409 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
5413 - Work around a bug in OpenSSL that broke renegotiation with TLS
5414 1.1 and TLS 1.2. Without this workaround, all attempts to speak
5415 the v2 Tor connection protocol when both sides were using OpenSSL
5416 1.0.1 would fail. Resolves ticket 6033.
5417 - When waiting for a client to renegotiate, don't allow it to add
5418 any bytes to the input buffer. This fixes a potential DoS issue.
5419 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
5420 - Fix an edge case where if we fetch or publish a hidden service
5421 descriptor, we might build a 4-hop circuit and then use that circuit
5422 for exiting afterwards -- even if the new last hop doesn't obey our
5423 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
5426 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
5427 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
5430 - Tell GCC and Clang to check for any errors in format strings passed
5431 to the tor_v*(print|scan)f functions.
5434 Changes in version 0.2.2.36 - 2012-05-24
5435 Tor 0.2.2.36 updates the addresses for two of the eight directory
5436 authorities, fixes some potential anonymity and security issues,
5437 and fixes several crash bugs.
5439 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
5440 known flaws, and nobody should be using them. You should upgrade. If
5441 you're using a Linux or BSD and its packages are obsolete, stop using
5442 those packages and upgrade anyway.
5444 o Directory authority changes:
5445 - Change IP address for maatuska (v3 directory authority).
5446 - Change IP address for ides (v3 directory authority), and rename
5450 - When building or running with any version of OpenSSL earlier
5451 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
5452 versions have a bug (CVE-2011-4576) in which their block cipher
5453 padding includes uninitialized data, potentially leaking sensitive
5454 information to any peer with whom they make a SSLv3 connection. Tor
5455 does not use SSL v3 by default, but a hostile client or server
5456 could force an SSLv3 connection in order to gain information that
5457 they shouldn't have been able to get. The best solution here is to
5458 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
5459 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
5460 to make sure that the bug can't happen.
5461 - Never use a bridge or a controller-supplied node as an exit, even
5462 if its exit policy allows it. Found by wanoskarnet. Fixes bug
5463 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
5464 and 0.2.0.3-alpha (for bridge-purpose descriptors).
5465 - Only build circuits if we have a sufficient threshold of the total
5466 descriptors that are marked in the consensus with the "Exit"
5467 flag. This mitigates an attack proposed by wanoskarnet, in which
5468 all of a client's bridges collude to restrict the exit nodes that
5469 the client knows about. Fixes bug 5343.
5470 - Provide controllers with a safer way to implement the cookie
5471 authentication mechanism. With the old method, if another locally
5472 running program could convince a controller that it was the Tor
5473 process, then that program could trick the controller into telling
5474 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
5475 authentication method uses a challenge-response approach to prevent
5476 this attack. Fixes bug 5185; implements proposal 193.
5479 - Avoid logging uninitialized data when unable to decode a hidden
5480 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
5481 - Avoid a client-side assertion failure when receiving an INTRODUCE2
5482 cell on a general purpose circuit. Fixes bug 5644; bugfix on
5484 - Fix builds when the path to sed, openssl, or sha1sum contains
5485 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
5487 - Correct our replacements for the timeradd() and timersub() functions
5488 on platforms that lack them (for example, Windows). The timersub()
5489 function is used when expiring circuits, while timeradd() is
5490 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
5491 bugfix on 0.2.2.24-alpha.
5492 - Fix the SOCKET_OK test that we use to tell when socket
5493 creation fails so that it works on Win64. Fixes part of bug 4533;
5494 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
5497 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
5498 Fixes bug 5346; bugfix on 0.0.8pre3.
5499 - Make our number-parsing functions always treat too-large values
5500 as an error, even when those values exceed the width of the
5501 underlying type. Previously, if the caller provided these
5502 functions with minima or maxima set to the extreme values of the
5503 underlying integer type, these functions would return those
5504 values on overflow rather than treating overflow as an error.
5505 Fixes part of bug 5786; bugfix on 0.0.9.
5506 - Older Linux kernels erroneously respond to strange nmap behavior
5507 by having accept() return successfully with a zero-length
5508 socket. When this happens, just close the connection. Previously,
5509 we would try harder to learn the remote address: but there was
5510 no such remote address to learn, and our method for trying to
5511 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
5512 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
5513 - Correct parsing of certain date types in parse_http_time().
5514 Without this patch, If-Modified-Since would behave
5515 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
5516 Esteban Manchado Velázques.
5517 - Change the BridgePassword feature (part of the "bridge community"
5518 design, which is not yet implemented) to use a time-independent
5519 comparison. The old behavior might have allowed an adversary
5520 to use timing to guess the BridgePassword value. Fixes bug 5543;
5521 bugfix on 0.2.0.14-alpha.
5522 - Detect and reject certain misformed escape sequences in
5523 configuration values. Previously, these values would cause us
5524 to crash if received in a torrc file or over an authenticated
5525 control port. Bug found by Esteban Manchado Velázquez, and
5526 independently by Robert Connolly from Matta Consulting who further
5527 noted that it allows a post-authentication heap overflow. Patch
5528 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
5529 bugfix on 0.2.0.16-alpha.
5530 - Fix a compile warning when using the --enable-openbsd-malloc
5531 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
5532 - During configure, detect when we're building with clang version
5533 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
5534 CFLAGS. clang doesn't support them yet.
5535 - When sending an HTTP/1.1 proxy request, include a Host header.
5536 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
5537 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
5538 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
5539 - If we hit the error case where routerlist_insert() replaces an
5540 existing (old) server descriptor, make sure to remove that
5541 server descriptor from the old_routers list. Fix related to bug
5542 1776. Bugfix on 0.2.2.18-alpha.
5544 o Minor bugfixes (documentation and log messages):
5545 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
5546 Fixes bug 4856; bugfix on Tor 0.0.6.
5547 - Update "ClientOnly" man page entry to explain that there isn't
5548 really any point to messing with it. Resolves ticket 5005.
5549 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
5550 directory authority option (introduced in Tor 0.2.2.34).
5551 - Downgrade the "We're missing a certificate" message from notice
5552 to info: people kept mistaking it for a real problem, whereas it
5553 is seldom the problem even when we are failing to bootstrap. Fixes
5554 bug 5067; bugfix on 0.2.0.10-alpha.
5555 - Correctly spell "connect" in a log message on failure to create a
5556 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
5557 - Clarify the behavior of MaxCircuitDirtiness with hidden service
5558 circuits. Fixes issue 5259.
5561 - Directory authorities now reject versions of Tor older than
5562 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
5563 inclusive. These versions accounted for only a small fraction of
5564 the Tor network, and have numerous known security issues. Resolves
5566 - Update to the May 1 2012 Maxmind GeoLite Country database.
5569 - When sending or relaying a RELAY_EARLY cell, we used to convert
5570 it to a RELAY cell if the connection was using the v1 link
5571 protocol. This was a workaround for older versions of Tor, which
5572 didn't handle RELAY_EARLY cells properly. Now that all supported
5573 versions can handle RELAY_EARLY cells, and now that we're enforcing
5574 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
5575 remove this workaround. Addresses bug 4786.
5578 Changes in version 0.2.2.35 - 2011-12-16
5579 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
5580 buffers code. Absolutely everybody should upgrade.
5582 The bug relied on an incorrect calculation when making data continuous
5583 in one of our IO buffers, if the first chunk of the buffer was
5584 misaligned by just the wrong amount. The miscalculation would allow an
5585 attacker to overflow a piece of heap-allocated memory. To mount this
5586 attack, the attacker would need to either open a SOCKS connection to
5587 Tor's SocksPort (usually restricted to localhost), or target a Tor
5588 instance configured to make its connections through a SOCKS proxy
5589 (which Tor does not do by default).
5591 Good security practice requires that all heap-overflow bugs should be
5592 presumed to be exploitable until proven otherwise, so we are treating
5593 this as a potential code execution attack. Please upgrade immediately!
5594 This bug does not affect bufferevents-based builds of Tor. Special
5595 thanks to "Vektor" for reporting this issue to us!
5597 Tor 0.2.2.35 also fixes several bugs in previous versions, including
5598 crash bugs for unusual configurations, and a long-term bug that
5599 would prevent Tor from starting on Windows machines with draconian
5602 With this release, we remind everyone that 0.2.0.x has reached its
5603 formal end-of-life. Those Tor versions have many known flaws, and
5604 nobody should be using them. You should upgrade -- ideally to the
5605 0.2.2.x series. If you're using a Linux or BSD and its packages are
5606 obsolete, stop using those packages and upgrade anyway.
5608 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
5609 longer receive support after some time in early 2012.
5612 - Fix a heap overflow bug that could occur when trying to pull
5613 data into the first chunk of a buffer, when that chunk had
5614 already had some data drained from it. Fixes CVE-2011-2778;
5615 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
5616 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
5617 that it doesn't attempt to allocate a socketpair. This could cause
5618 some problems on Windows systems with overzealous firewalls. Fix for
5619 bug 4457; workaround for Libevent versions 2.0.1-alpha through
5621 - If we mark an OR connection for close based on a cell we process,
5622 don't process any further cells on it. We already avoid further
5623 reads on marked-for-close connections, but now we also discard the
5624 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
5625 which was the first version where we might mark a connection for
5626 close based on processing a cell on it.
5627 - Correctly sanity-check that we don't underflow on a memory
5628 allocation (and then assert) for hidden service introduction
5629 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
5630 bugfix on 0.2.1.5-alpha.
5631 - Fix a memory leak when we check whether a hidden service
5632 descriptor has any usable introduction points left. Fixes bug
5633 4424. Bugfix on 0.2.2.25-alpha.
5634 - Don't crash when we're running as a relay and don't have a GeoIP
5635 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
5636 we've had in the 0.2.3.x branch already.
5637 - When running as a client, do not print a misleading (and plain
5638 wrong) log message that we're collecting "directory request"
5639 statistics: clients don't collect statistics. Also don't create a
5640 useless (because empty) stats file in the stats/ directory. Fixes
5641 bug 4353; bugfix on 0.2.2.34.
5644 - Detect failure to initialize Libevent. This fix provides better
5645 detection for future instances of bug 4457.
5646 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
5647 function. This was eating up hideously large amounts of time on some
5648 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
5649 - Resolve an integer overflow bug in smartlist_ensure_capacity().
5650 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
5652 - Don't warn about unused log_mutex in log.c when building with
5653 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
5654 0.1.0.6-rc which introduced --disable-threads.
5655 - When configuring, starting, or stopping an NT service, stop
5656 immediately after the service configuration attempt has succeeded
5657 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
5658 - When sending a NETINFO cell, include the original address
5659 received for the other side, not its canonical address. Found
5660 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
5661 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
5662 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
5663 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
5664 occurred when a client tried to fetch a descriptor for a bridge
5665 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
5666 - Backport fixes for a pair of compilation warnings on Windows.
5667 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
5668 - If we had ever tried to call tor_addr_to_str on an address of
5669 unknown type, we would have done a strdup on an uninitialized
5670 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
5671 Reported by "troll_un".
5672 - Correctly detect and handle transient lookup failures from
5673 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
5674 Reported by "troll_un".
5675 - Fix null-pointer access that could occur if TLS allocation failed.
5676 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
5677 - Use tor_socket_t type for listener argument to accept(). Fixes bug
5678 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
5681 - Add two new config options for directory authorities:
5682 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
5683 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
5684 that is always sufficient to satisfy the bandwidth requirement for
5685 the Guard flag. Now it will be easier for researchers to simulate
5686 Tor networks with different values. Resolves ticket 4484.
5687 - When Tor ignores a hidden service specified in its configuration,
5688 include the hidden service's directory in the warning message.
5689 Previously, we would only tell the user that some hidden service
5690 was ignored. Bugfix on 0.0.6; fixes bug 4426.
5691 - Update to the December 6 2011 Maxmind GeoLite Country database.
5693 o Packaging changes:
5694 - Make it easier to automate expert package builds on Windows,
5695 by removing an absolute path from makensis.exe command.
5698 Changes in version 0.2.1.32 - 2011-12-16
5699 Tor 0.2.1.32 backports important security and privacy fixes for
5700 oldstable. This release is intended only for package maintainers and
5701 others who cannot use the 0.2.2 stable series. All others should be
5702 using Tor 0.2.2.x or newer.
5704 The Tor 0.2.1.x series will reach formal end-of-life some time in
5705 early 2012; we will stop releasing patches for it then.
5707 o Major bugfixes (also included in 0.2.2.x):
5708 - Correctly sanity-check that we don't underflow on a memory
5709 allocation (and then assert) for hidden service introduction
5710 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
5711 bugfix on 0.2.1.5-alpha.
5712 - Fix a heap overflow bug that could occur when trying to pull
5713 data into the first chunk of a buffer, when that chunk had
5714 already had some data drained from it. Fixes CVE-2011-2778;
5715 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
5718 - Update to the December 6 2011 Maxmind GeoLite Country database.
5721 Changes in version 0.2.2.34 - 2011-10-26
5722 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
5723 can deanonymize Tor users. Everybody should upgrade.
5725 The attack relies on four components: 1) Clients reuse their TLS cert
5726 when talking to different relays, so relays can recognize a user by
5727 the identity key in her cert. 2) An attacker who knows the client's
5728 identity key can probe each guard relay to see if that identity key
5729 is connected to that guard relay right now. 3) A variety of active
5730 attacks in the literature (starting from "Low-Cost Traffic Analysis
5731 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
5732 discover the guard relays that a Tor user visiting the website is using.
5733 4) Clients typically pick three guards at random, so the set of guards
5734 for a given user could well be a unique fingerprint for her. This
5735 release fixes components #1 and #2, which is enough to block the attack;
5736 the other two remain as open research problems. Special thanks to
5737 "frosty_un" for reporting the issue to us!
5739 Clients should upgrade so they are no longer recognizable by the TLS
5740 certs they present. Relays should upgrade so they no longer allow a
5741 remote attacker to probe them to test whether unpatched clients are
5742 currently connected to them.
5744 This release also fixes several vulnerabilities that allow an attacker
5745 to enumerate bridge relays. Some bridge enumeration attacks still
5746 remain; see for example proposal 188.
5748 o Privacy/anonymity fixes (clients):
5749 - Clients and bridges no longer send TLS certificate chains on
5750 outgoing OR connections. Previously, each client or bridge would
5751 use the same cert chain for all outgoing OR connections until
5752 its IP address changes, which allowed any relay that the client
5753 or bridge contacted to determine which entry guards it is using.
5754 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
5755 - If a relay receives a CREATE_FAST cell on a TLS connection, it
5756 no longer considers that connection as suitable for satisfying a
5757 circuit EXTEND request. Now relays can protect clients from the
5758 CVE-2011-2768 issue even if the clients haven't upgraded yet.
5759 - Directory authorities no longer assign the Guard flag to relays
5760 that haven't upgraded to the above "refuse EXTEND requests
5761 to client connections" fix. Now directory authorities can
5762 protect clients from the CVE-2011-2768 issue even if neither
5763 the clients nor the relays have upgraded yet. There's a new
5764 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
5765 to let us transition smoothly, else tomorrow there would be no
5768 o Privacy/anonymity fixes (bridge enumeration):
5769 - Bridge relays now do their directory fetches inside Tor TLS
5770 connections, like all the other clients do, rather than connecting
5771 directly to the DirPort like public relays do. Removes another
5772 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
5773 - Bridges relays now build circuits for themselves in a more similar
5774 way to how clients build them. Removes another avenue for
5775 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
5776 when bridges were introduced.
5777 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
5778 that they initiated. Relays could distinguish incoming bridge
5779 connections from client connections, creating another avenue for
5780 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
5781 Found by "frosty_un".
5784 - Fix a crash bug when changing node restrictions while a DNS lookup
5785 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
5787 - Don't launch a useless circuit after failing to use one of a
5788 hidden service's introduction points. Previously, we would
5789 launch a new introduction circuit, but not set the hidden service
5790 which that circuit was intended to connect to, so it would never
5791 actually be used. A different piece of code would then create a
5792 new introduction circuit correctly. Bug reported by katmagic and
5793 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
5796 - Change an integer overflow check in the OpenBSD_Malloc code so
5797 that GCC is less likely to eliminate it as impossible. Patch
5798 from Mansour Moufid. Fixes bug 4059.
5799 - When a hidden service turns an extra service-side introduction
5800 circuit into a general-purpose circuit, free the rend_data and
5801 intro_key fields first, so we won't leak memory if the circuit
5802 is cannibalized for use as another service-side introduction
5803 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
5804 - Bridges now skip DNS self-tests, to act a little more stealthily.
5805 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
5806 bridges. Patch by "warms0x".
5807 - Fix internal bug-checking logic that was supposed to catch
5808 failures in digest generation so that it will fail more robustly
5809 if we ask for a nonexistent algorithm. Found by Coverity Scan.
5810 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
5811 - Report any failure in init_keys() calls launched because our
5812 IP address has changed. Spotted by Coverity Scan. Bugfix on
5813 0.1.1.4-alpha; fixes CID 484.
5815 o Minor bugfixes (log messages and documentation):
5816 - Remove a confusing dollar sign from the example fingerprint in the
5817 man page, and also make the example fingerprint a valid one. Fixes
5818 bug 4309; bugfix on 0.2.1.3-alpha.
5819 - The next version of Windows will be called Windows 8, and it has
5820 a major version of 6, minor version of 2. Correctly identify that
5821 version instead of calling it "Very recent version". Resolves
5822 ticket 4153; reported by funkstar.
5823 - Downgrade log messages about circuit timeout calibration from
5824 "notice" to "info": they don't require or suggest any human
5825 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
5826 bugfix on 0.2.2.14-alpha.
5829 - Turn on directory request statistics by default and include them in
5830 extra-info descriptors. Don't break if we have no GeoIP database.
5831 Backported from 0.2.3.1-alpha; implements ticket 3951.
5832 - Update to the October 4 2011 Maxmind GeoLite Country database.
5835 Changes in version 0.2.1.31 - 2011-10-26
5836 Tor 0.2.1.31 backports important security and privacy fixes for
5837 oldstable. This release is intended only for package maintainers and
5838 others who cannot use the 0.2.2 stable series. All others should be
5839 using Tor 0.2.2.x or newer.
5841 o Security fixes (also included in 0.2.2.x):
5842 - Replace all potentially sensitive memory comparison operations
5843 with versions whose runtime does not depend on the data being
5844 compared. This will help resist a class of attacks where an
5845 adversary can use variations in timing information to learn
5846 sensitive data. Fix for one case of bug 3122. (Safe memcmp
5847 implementation by Robert Ransom based partially on code by DJB.)
5848 - Fix an assert in parsing router descriptors containing IPv6
5849 addresses. This one took down the directory authorities when
5850 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
5852 o Privacy/anonymity fixes (also included in 0.2.2.x):
5853 - Clients and bridges no longer send TLS certificate chains on
5854 outgoing OR connections. Previously, each client or bridge would
5855 use the same cert chain for all outgoing OR connections until
5856 its IP address changes, which allowed any relay that the client
5857 or bridge contacted to determine which entry guards it is using.
5858 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
5859 - If a relay receives a CREATE_FAST cell on a TLS connection, it
5860 no longer considers that connection as suitable for satisfying a
5861 circuit EXTEND request. Now relays can protect clients from the
5862 CVE-2011-2768 issue even if the clients haven't upgraded yet.
5863 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
5864 that they initiated. Relays could distinguish incoming bridge
5865 connections from client connections, creating another avenue for
5866 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
5867 Found by "frosty_un".
5868 - When receiving a hidden service descriptor, check that it is for
5869 the hidden service we wanted. Previously, Tor would store any
5870 hidden service descriptors that a directory gave it, whether it
5871 wanted them or not. This wouldn't have let an attacker impersonate
5872 a hidden service, but it did let directories pre-seed a client
5873 with descriptors that it didn't want. Bugfix on 0.0.6.
5874 - Avoid linkability based on cached hidden service descriptors: forget
5875 all hidden service descriptors cached as a client when processing a
5876 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
5877 - Make the bridge directory authority refuse to answer directory
5878 requests for "all" descriptors. It used to include bridge
5879 descriptors in its answer, which was a major information leak.
5880 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
5881 - Don't attach new streams to old rendezvous circuits after SIGNAL
5882 NEWNYM. Previously, we would keep using an existing rendezvous
5883 circuit if it remained open (i.e. if it were kept open by a
5884 long-lived stream, or if a new stream were attached to it before
5885 Tor could notice that it was old and no longer in use). Bugfix on
5886 0.1.1.15-rc; fixes bug 3375.
5888 o Minor bugfixes (also included in 0.2.2.x):
5889 - When we restart our relay, we might get a successful connection
5890 from the outside before we've started our reachability tests,
5891 triggering a warning: "ORPort found reachable, but I have no
5892 routerinfo yet. Failing to inform controller of success." This
5893 bug was harmless unless Tor is running under a controller
5894 like Vidalia, in which case the controller would never get a
5895 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
5897 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
5898 enabled. Fixes bug 1526.
5899 - Remove undocumented option "-F" from tor-resolve: it hasn't done
5900 anything since 0.2.1.16-rc.
5901 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
5902 None of the cases where we did this before were wrong, but by making
5903 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
5904 - Fix a rare crash bug that could occur when a client was configured
5905 with a large number of bridges. Fixes bug 2629; bugfix on
5906 0.2.1.2-alpha. Bugfix by trac user "shitlei".
5907 - Correct the warning displayed when a rendezvous descriptor exceeds
5908 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
5910 - Fix an uncommon assertion failure when running with DNSPort under
5911 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
5912 - When warning about missing zlib development packages during compile,
5913 give the correct package names. Bugfix on 0.2.0.1-alpha.
5914 - Require that introduction point keys and onion keys have public
5915 exponent 65537. Bugfix on 0.2.0.10-alpha.
5916 - Do not crash when our configuration file becomes unreadable, for
5917 example due to a permissions change, between when we start up
5918 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
5920 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
5922 - Always NUL-terminate the sun_path field of a sockaddr_un before
5923 passing it to the kernel. (Not a security issue: kernels are
5924 smart enough to reject bad sockaddr_uns.) Found by Coverity;
5925 CID #428. Bugfix on Tor 0.2.0.3-alpha.
5926 - Don't stack-allocate the list of supplementary GIDs when we're
5927 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
5928 could take up to 256K, which is way too much stack. Found by
5929 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
5931 o Minor bugfixes (only in 0.2.1.x):
5932 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
5933 rely on them. Bugfix on 0.2.1.30.
5934 - Use git revisions instead of svn revisions when generating our
5935 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
5937 o Minor features (also included in 0.2.2.x):
5938 - Adjust the expiration time on our SSL session certificates to
5939 better match SSL certs seen in the wild. Resolves ticket 4014.
5940 - Allow nameservers with IPv6 address. Resolves bug 2574.
5941 - Update to the October 4 2011 Maxmind GeoLite Country database.
5944 Changes in version 0.2.2.33 - 2011-09-13
5945 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
5946 TLS handshake that makes relays and bridges that run this new version
5947 reachable from Iran again.
5950 - Avoid an assertion failure when reloading a configuration with
5951 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
5952 3923; bugfix on 0.2.2.25-alpha.
5954 o Minor features (security):
5955 - Check for replays of the public-key encrypted portion of an
5956 INTRODUCE1 cell, in addition to the current check for replays of
5957 the g^x value. This prevents a possible class of active attacks
5958 by an attacker who controls both an introduction point and a
5959 rendezvous point, and who uses the malleability of AES-CTR to
5960 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
5961 that these attacks are infeasible (requiring the attacker to send
5962 on the order of zettabytes of altered cells in a short interval),
5963 but we'd rather block them off in case there are any classes of
5964 this attack that we missed. Reported by Willem Pinckaers.
5967 - Adjust the expiration time on our SSL session certificates to
5968 better match SSL certs seen in the wild. Resolves ticket 4014.
5969 - Change the default required uptime for a relay to be accepted as
5970 a HSDir (hidden service directory) from 24 hours to 25 hours.
5971 Improves on 0.2.0.10-alpha; resolves ticket 2649.
5972 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
5973 authorities to abstain from voting on assignment of the HSDir
5974 consensus flag. Related to bug 2649.
5975 - Update to the September 6 2011 Maxmind GeoLite Country database.
5977 o Minor bugfixes (documentation and log messages):
5978 - Correct the man page to explain that HashedControlPassword and
5979 CookieAuthentication can both be set, in which case either method
5980 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
5981 when we decided to allow these config options to both be set. Issue
5983 - Demote the 'replay detected' log message emitted when a hidden
5984 service receives the same Diffie-Hellman public key in two different
5985 INTRODUCE2 cells to info level. A normal Tor client can cause that
5986 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
5987 fixes part of bug 2442.
5988 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
5989 level. There is nothing that a hidden service's operator can do
5990 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
5992 - Clarify a log message specifying the characters permitted in
5993 HiddenServiceAuthorizeClient client names. Previously, the log
5994 message said that "[A-Za-z0-9+-_]" were permitted; that could have
5995 given the impression that every ASCII character between "+" and "_"
5996 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
5999 - Provide a substitute implementation of lround() for MSVC, which
6000 apparently lacks it. Patch from Gisle Vanem.
6001 - Clean up some code issues that prevented Tor from building on older
6002 BSDs. Fixes bug 3894; reported by "grarpamp".
6003 - Search for a platform-specific version of "ar" when cross-compiling.
6004 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
6007 Changes in version 0.2.2.32 - 2011-08-27
6008 The Tor 0.2.2 release series is dedicated to the memory of Andreas
6009 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
6010 a founder of the PETS community, a leader in our field, a mentor,
6011 and a friend. He left us with these words: "I had the possibility
6012 to contribute to this world that is not as it should be. I hope I
6013 could help in some areas to make the world a better place, and that
6014 I could also encourage other people to be engaged in improving the
6015 world. Please, stay engaged. This world needs you, your love, your
6016 initiative -- now I cannot be part of that anymore."
6018 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
6019 ready. More than two years in the making, this release features improved
6020 client performance and hidden service reliability, better compatibility
6021 for Android, correct behavior for bridges that listen on more than
6022 one address, more extensible and flexible directory object handling,
6023 better reporting of network statistics, improved code security, and
6024 many many other features and bugfixes.
6026 o Major features (client performance):
6027 - When choosing which cells to relay first, relays now favor circuits
6028 that have been quiet recently, to provide lower latency for
6029 low-volume circuits. By default, relays enable or disable this
6030 feature based on a setting in the consensus. They can override
6031 this default by using the new "CircuitPriorityHalflife" config
6032 option. Design and code by Ian Goldberg, Can Tang, and Chris
6034 - Directory authorities now compute consensus weightings that instruct
6035 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
6036 and no flag. Clients use these weightings to distribute network load
6037 more evenly across these different relay types. The weightings are
6038 in the consensus so we can change them globally in the future. Extra
6039 thanks to "outofwords" for finding some nasty security bugs in
6040 the first implementation of this feature.
6042 o Major features (client performance, circuit build timeout):
6043 - Tor now tracks how long it takes to build client-side circuits
6044 over time, and adapts its timeout to local network performance.
6045 Since a circuit that takes a long time to build will also provide
6046 bad performance, we get significant latency improvements by
6047 discarding the slowest 20% of circuits. Specifically, Tor creates
6048 circuits more aggressively than usual until it has enough data
6049 points for a good timeout estimate. Implements proposal 151.
6050 - Circuit build timeout constants can be controlled by consensus
6051 parameters. We set good defaults for these parameters based on
6052 experimentation on broadband and simulated high-latency links.
6053 - Circuit build time learning can be disabled via consensus parameter
6054 or by the client via a LearnCircuitBuildTimeout config option. We
6055 also automatically disable circuit build time calculation if either
6056 AuthoritativeDirectory is set, or if we fail to write our state
6057 file. Implements ticket 1296.
6059 o Major features (relays use their capacity better):
6060 - Set SO_REUSEADDR socket option on all sockets, not just
6061 listeners. This should help busy exit nodes avoid running out of
6062 useable ports just because all the ports have been used in the
6063 near past. Resolves issue 2850.
6064 - Relays now save observed peak bandwidth throughput rates to their
6065 state file (along with total usage, which was already saved),
6066 so that they can determine their correct estimated bandwidth on
6067 restart. Resolves bug 1863, where Tor relays would reset their
6068 estimated bandwidth to 0 after restarting.
6069 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
6070 should give us approximately 40-50% more Guard-flagged nodes,
6071 improving the anonymity the Tor network can provide and also
6072 decreasing the dropoff in throughput that relays experience when
6073 they first get the Guard flag.
6074 - Directory authorities now take changes in router IP address and
6075 ORPort into account when determining router stability. Previously,
6076 if a router changed its IP or ORPort, the authorities would not
6077 treat it as having any downtime for the purposes of stability
6078 calculation, whereas clients would experience downtime since the
6079 change would take a while to propagate to them. Resolves issue 1035.
6080 - New AccelName and AccelDir options add support for dynamic OpenSSL
6081 hardware crypto acceleration engines.
6083 o Major features (relays control their load better):
6084 - Exit relays now try harder to block exit attempts from unknown
6085 relays, to make it harder for people to use them as one-hop proxies
6086 a la tortunnel. Controlled by the refuseunknownexits consensus
6087 parameter (currently enabled), or you can override it on your
6088 relay with the RefuseUnknownExits torrc option. Resolves bug 1751;
6089 based on a variant of proposal 163.
6090 - Add separate per-conn write limiting to go with the per-conn read
6091 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
6092 but never per-conn write limits.
6093 - New consensus params "bwconnrate" and "bwconnburst" to let us
6094 rate-limit client connections as they enter the network. It's
6095 controlled in the consensus so we can turn it on and off for
6096 experiments. It's starting out off. Based on proposal 163.
6098 o Major features (controllers):
6099 - Export GeoIP information on bridge usage to controllers even if we
6100 have not yet been running for 24 hours. Now Vidalia bridge operators
6101 can get more accurate and immediate feedback about their
6102 contributions to the network.
6103 - Add an __OwningControllerProcess configuration option and a
6104 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
6105 that when it exits, Tor will shut down. Implements feature 3049.
6107 o Major features (directory authorities):
6108 - Directory authorities now create, vote on, and serve multiple
6109 parallel formats of directory data as part of their voting process.
6110 Partially implements Proposal 162: "Publish the consensus in
6112 - Directory authorities now agree on and publish small summaries
6113 of router information that clients can use in place of regular
6114 server descriptors. This transition will allow Tor 0.2.3 clients
6115 to use far less bandwidth for downloading information about the
6116 network. Begins the implementation of Proposal 158: "Clients
6117 download consensus + microdescriptors".
6118 - The directory voting system is now extensible to use multiple hash
6119 algorithms for signatures and resource selection. Newer formats
6120 are signed with SHA256, with a possibility for moving to a better
6121 hash algorithm in the future.
6122 - Directory authorities can now vote on arbitary integer values as
6123 part of the consensus process. This is designed to help set
6124 network-wide parameters. Implements proposal 167.
6126 o Major features and bugfixes (node selection):
6127 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
6128 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and Strict*Nodes
6129 options. Previously, we had been ambiguous in describing what
6130 counted as an "exit" node, and what operations exactly "StrictNodes
6131 0" would permit. This created confusion when people saw nodes built
6132 through unexpected circuits, and made it hard to tell real bugs from
6133 surprises. Now the intended behavior is:
6134 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
6135 a node that delivers user traffic outside the Tor network.
6136 . "Entry", in the context of EntryNodes, means a node used as the
6137 first hop of a multihop circuit. It doesn't include direct
6138 connections to directory servers.
6139 . "ExcludeNodes" applies to all nodes.
6140 . "StrictNodes" changes the behavior of ExcludeNodes only. When
6141 StrictNodes is set, Tor should avoid all nodes listed in
6142 ExcludeNodes, even when it will make user requests fail. When
6143 StrictNodes is *not* set, then Tor should follow ExcludeNodes
6144 whenever it can, except when it must use an excluded node to
6145 perform self-tests, connect to a hidden service, provide a
6146 hidden service, fulfill a .exit request, upload directory
6147 information, or fetch directory information.
6148 Collectively, the changes to implement the behavior fix bug 1090.
6149 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
6150 change during a config reload, mark and discard all our origin
6151 circuits. This fix should address edge cases where we change the
6152 config options and but then choose a circuit that we created before
6154 - Make EntryNodes config option much more aggressive even when
6155 StrictNodes is not set. Before it would prepend your requested
6156 entrynodes to your list of guard nodes, but feel free to use others
6157 after that. Now it chooses only from your EntryNodes if any of
6158 those are available, and only falls back to others if a) they're
6159 all down and b) StrictNodes is not set.
6160 - Now we refresh your entry guards from EntryNodes at each consensus
6161 fetch -- rather than just at startup and then they slowly rot as
6162 the network changes.
6163 - Add support for the country code "{??}" in torrc options like
6164 ExcludeNodes, to indicate all routers of unknown country. Closes
6166 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
6167 a node is listed in both, it's treated as excluded.
6168 - ExcludeNodes now applies to directory nodes -- as a preference if
6169 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
6170 Don't exclude all the directory authorities and set StrictNodes to 1
6171 unless you really want your Tor to break.
6172 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
6173 - ExcludeExitNodes now overrides .exit requests.
6174 - We don't use bridges listed in ExcludeNodes.
6175 - When StrictNodes is 1:
6176 . We now apply ExcludeNodes to hidden service introduction points
6177 and to rendezvous points selected by hidden service users. This
6178 can make your hidden service less reliable: use it with caution!
6179 . If we have used ExcludeNodes on ourself, do not try relay
6180 reachability self-tests.
6181 . If we have excluded all the directory authorities, we will not
6182 even try to upload our descriptor if we're a relay.
6183 . Do not honor .exit requests to an excluded node.
6184 - When the set of permitted nodes changes, we now remove any mappings
6185 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
6187 - We never cannibalize a circuit that had excluded nodes on it, even
6188 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
6189 - Improve log messages related to excluded nodes.
6191 o Major features (misc):
6192 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
6193 to help Tor build correctly for Android phones.
6194 - The options SocksPort, ControlPort, and so on now all accept a
6195 value "auto" that opens a socket on an OS-selected port. A
6196 new ControlPortWriteToFile option tells Tor to write its
6197 actual control port or ports to a chosen file. If the option
6198 ControlPortFileGroupReadable is set, the file is created as
6199 group-readable. Now users can run two Tor clients on the same
6200 system without needing to manually mess with parameters. Resolves
6201 part of ticket 3076.
6202 - Tor now supports tunneling all of its outgoing connections over
6203 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
6204 configuration options. Code by Christopher Davis.
6206 o Code security improvements:
6207 - Replace all potentially sensitive memory comparison operations
6208 with versions whose runtime does not depend on the data being
6209 compared. This will help resist a class of attacks where an
6210 adversary can use variations in timing information to learn
6211 sensitive data. Fix for one case of bug 3122. (Safe memcmp
6212 implementation by Robert Ransom based partially on code by DJB.)
6213 - Enable Address Space Layout Randomization (ASLR) and Data Execution
6214 Prevention (DEP) by default on Windows to make it harder for
6215 attackers to exploit vulnerabilities. Patch from John Brooks.
6216 - New "--enable-gcc-hardening" ./configure flag (off by default)
6217 to turn on gcc compile time hardening options. It ensures
6218 that signed ints have defined behavior (-fwrapv), enables
6219 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
6220 with canaries (-fstack-protector-all), turns on ASLR protection if
6221 supported by the kernel (-fPIE, -pie), and adds additional security
6222 related warnings. Verified to work on Mac OS X and Debian Lenny.
6223 - New "--enable-linker-hardening" ./configure flag (off by default)
6224 to turn on ELF specific hardening features (relro, now). This does
6225 not work with Mac OS X or any other non-ELF binary format.
6226 - Always search the Windows system directory for system DLLs, and
6227 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
6228 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
6229 current and future memory pages via mlockall(). On supported
6230 platforms (modern Linux and probably BSD but not Windows or OS X),
6231 this should effectively disable any and all attempts to page out
6232 memory. This option requires that you start your Tor as root --
6233 if you use DisableAllSwap, please consider using the User option
6234 to properly reduce the privileges of your Tor.
6236 o Major bugfixes (crashes):
6237 - Fix crash bug on platforms where gmtime and localtime can return
6238 NULL. Windows 7 users were running into this one. Fixes part of bug
6239 2077. Bugfix on all versions of Tor. Found by boboper.
6240 - Introduce minimum/maximum values that clients will believe
6241 from the consensus. Now we'll have a better chance to avoid crashes
6242 or worse when a consensus param has a weird value.
6243 - Fix a rare crash bug that could occur when a client was configured
6244 with a large number of bridges. Fixes bug 2629; bugfix on
6245 0.2.1.2-alpha. Bugfix by trac user "shitlei".
6246 - Do not crash when our configuration file becomes unreadable, for
6247 example due to a permissions change, between when we start up
6248 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
6250 - If we're in the pathological case where there's no exit bandwidth
6251 but there is non-exit bandwidth, or no guard bandwidth but there
6252 is non-guard bandwidth, don't crash during path selection. Bugfix
6254 - Fix a crash bug when trying to initialize the evdns module in
6255 Libevent 2. Bugfix on 0.2.1.16-rc.
6257 o Major bugfixes (stability):
6258 - Fix an assert in parsing router descriptors containing IPv6
6259 addresses. This one took down the directory authorities when
6260 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
6261 - Fix an uncommon assertion failure when running with DNSPort under
6262 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
6263 - Treat an unset $HOME like an empty $HOME rather than triggering an
6264 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
6265 - More gracefully handle corrupt state files, removing asserts
6266 in favor of saving a backup and resetting state.
6267 - Instead of giving an assertion failure on an internal mismatch
6268 on estimated freelist size, just log a BUG warning and try later.
6269 Mitigates but does not fix bug 1125.
6270 - Fix an assert that got triggered when using the TestingTorNetwork
6271 configuration option and then issuing a GETINFO config-text control
6272 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
6273 - If the cached cert file is unparseable, warn but don't exit.
6275 o Privacy fixes (relays/bridges):
6276 - Don't list Windows capabilities in relay descriptors. We never made
6277 use of them, and maybe it's a bad idea to publish them. Bugfix
6279 - If the Nickname configuration option isn't given, Tor would pick a
6280 nickname based on the local hostname as the nickname for a relay.
6281 Because nicknames are not very important in today's Tor and the
6282 "Unnamed" nickname has been implemented, this is now problematic
6283 behavior: It leaks information about the hostname without being
6284 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
6285 introduced the Unnamed nickname. Reported by tagnaq.
6286 - Maintain separate TLS contexts and certificates for incoming and
6287 outgoing connections in bridge relays. Previously we would use the
6288 same TLS contexts and certs for incoming and outgoing connections.
6289 Bugfix on 0.2.0.3-alpha; addresses bug 988.
6290 - Maintain separate identity keys for incoming and outgoing TLS
6291 contexts in bridge relays. Previously we would use the same
6292 identity keys for incoming and outgoing TLS contexts. Bugfix on
6293 0.2.0.3-alpha; addresses the other half of bug 988.
6294 - Make the bridge directory authority refuse to answer directory
6295 requests for "all descriptors". It used to include bridge
6296 descriptors in its answer, which was a major information leak.
6297 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
6299 o Privacy fixes (clients):
6300 - When receiving a hidden service descriptor, check that it is for
6301 the hidden service we wanted. Previously, Tor would store any
6302 hidden service descriptors that a directory gave it, whether it
6303 wanted them or not. This wouldn't have let an attacker impersonate
6304 a hidden service, but it did let directories pre-seed a client
6305 with descriptors that it didn't want. Bugfix on 0.0.6.
6306 - Start the process of disabling ".exit" address notation, since it
6307 can be used for a variety of esoteric application-level attacks
6308 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
6310 - Reject attempts at the client side to open connections to private
6311 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
6312 a randomly chosen exit node. Attempts to do so are always
6313 ill-defined, generally prevented by exit policies, and usually
6314 in error. This will also help to detect loops in transparent
6315 proxy configurations. You can disable this feature by setting
6316 "ClientRejectInternalAddresses 0" in your torrc.
6317 - Log a notice when we get a new control connection. Now it's easier
6318 for security-conscious users to recognize when a local application
6319 is knocking on their controller door. Suggested by bug 1196.
6321 o Privacy fixes (newnym):
6322 - Avoid linkability based on cached hidden service descriptors: forget
6323 all hidden service descriptors cached as a client when processing a
6324 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
6325 - On SIGHUP, do not clear out all TrackHostExits mappings, client
6326 DNS cache entries, and virtual address mappings: that's what
6327 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
6328 - Don't attach new streams to old rendezvous circuits after SIGNAL
6329 NEWNYM. Previously, we would keep using an existing rendezvous
6330 circuit if it remained open (i.e. if it were kept open by a
6331 long-lived stream, or if a new stream were attached to it before
6332 Tor could notice that it was old and no longer in use). Bugfix on
6333 0.1.1.15-rc; fixes bug 3375.
6335 o Major bugfixes (relay bandwidth accounting):
6336 - Fix a bug that could break accounting on 64-bit systems with large
6337 time_t values, making them hibernate for impossibly long intervals.
6338 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
6339 - Fix a bug in bandwidth accounting that could make us use twice
6340 the intended bandwidth when our interval start changes due to
6341 daylight saving time. Now we tolerate skew in stored vs computed
6342 interval starts: if the start of the period changes by no more than
6343 50% of the period's duration, we remember bytes that we transferred
6344 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
6346 o Major bugfixes (bridges):
6347 - Bridges now use "reject *:*" as their default exit policy. Bugfix
6348 on 0.2.0.3-alpha. Fixes bug 1113.
6349 - If you configure your bridge with a known identity fingerprint,
6350 and the bridge authority is unreachable (as it is in at least
6351 one country now), fall back to directly requesting the descriptor
6352 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
6354 - Fix a bug where bridge users who configure the non-canonical
6355 address of a bridge automatically switch to its canonical
6356 address. If a bridge listens at more than one address, it
6357 should be able to advertise those addresses independently and
6358 any non-blocked addresses should continue to work. Bugfix on Tor
6359 0.2.0.3-alpha. Fixes bug 2510.
6360 - If you configure Tor to use bridge A, and then quit and
6361 configure Tor to use bridge B instead (or if you change Tor
6362 to use bridge B via the controller), it would happily continue
6363 to use bridge A if it's still reachable. While this behavior is
6364 a feature if your goal is connectivity, in some scenarios it's a
6365 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
6366 - When the controller configures a new bridge, don't wait 10 to 60
6367 seconds before trying to fetch its descriptor. Bugfix on
6368 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
6370 o Major bugfixes (directory authorities):
6371 - Many relays have been falling out of the consensus lately because
6372 not enough authorities know about their descriptor for them to get
6373 a majority of votes. When we deprecated the v2 directory protocol,
6374 we got rid of the only way that v3 authorities can hear from each
6375 other about other descriptors. Now authorities examine every v3
6376 vote for new descriptors, and fetch them from that authority. Bugfix
6378 - Authorities could be tricked into giving out the Exit flag to relays
6379 that didn't allow exiting to any ports. This bug could screw
6380 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
6381 1238. Bug discovered by Martin Kowalczyk.
6382 - If all authorities restart at once right before a consensus vote,
6383 nobody will vote about "Running", and clients will get a consensus
6384 with no usable relays. Instead, authorities refuse to build a
6385 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
6387 o Major bugfixes (stream-level fairness):
6388 - When receiving a circuit-level SENDME for a blocked circuit, try
6389 to package cells fairly from all the streams that had previously
6390 been blocked on that circuit. Previously, we had started with the
6391 oldest stream, and allowed each stream to potentially exhaust
6392 the circuit's package window. This gave older streams on any
6393 given circuit priority over newer ones. Fixes bug 1937. Detected
6394 originally by Camilo Viecco. This bug was introduced before the
6395 first Tor release, in svn commit r152: it is the new winner of
6396 the longest-lived bug prize.
6397 - Fix a stream fairness bug that would cause newer streams on a given
6398 circuit to get preference when reading bytes from the origin or
6399 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
6400 introduced before the first Tor release, in svn revision r152.
6401 - When the exit relay got a circuit-level sendme cell, it started
6402 reading on the exit streams, even if had 500 cells queued in the
6403 circuit queue already, so the circuit queue just grew and grew in
6404 some cases. We fix this by not re-enabling reading on receipt of a
6405 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
6406 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
6408 - Newly created streams were allowed to read cells onto circuits,
6409 even if the circuit's cell queue was blocked and waiting to drain.
6410 This created potential unfairness, as older streams would be
6411 blocked, but newer streams would gladly fill the queue completely.
6412 We add code to detect this situation and prevent any stream from
6413 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
6416 o Major bugfixes (hidden services):
6417 - Apply circuit timeouts to opened hidden-service-related circuits
6418 based on the correct start time. Previously, we would apply the
6419 circuit build timeout based on time since the circuit's creation;
6420 it was supposed to be applied based on time since the circuit
6421 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
6422 - Improve hidden service robustness: When we find that we have
6423 extended a hidden service's introduction circuit to a relay not
6424 listed as an introduction point in the HS descriptor we currently
6425 have, retry with an introduction point from the current
6426 descriptor. Previously we would just give up. Fixes bugs 1024 and
6427 1930; bugfix on 0.2.0.10-alpha.
6428 - Directory authorities now use data collected from their own
6429 uptime observations when choosing whether to assign the HSDir flag
6430 to relays, instead of trusting the uptime value the relay reports in
6431 its descriptor. This change helps prevent an attack where a small
6432 set of nodes with frequently-changing identity keys can blackhole
6433 a hidden service. (Only authorities need upgrade; others will be
6434 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
6435 - Stop assigning the HSDir flag to relays that disable their
6436 DirPort (and thus will refuse to answer directory requests). This
6437 fix should dramatically improve the reachability of hidden services:
6438 hidden services and hidden service clients pick six HSDir relays
6439 to store and retrieve the hidden service descriptor, and currently
6440 about half of the HSDir relays will refuse to work. Bugfix on
6441 0.2.0.10-alpha; fixes part of bug 1693.
6443 o Major bugfixes (misc):
6444 - Clients now stop trying to use an exit node associated with a given
6445 destination by TrackHostExits if they fail to reach that exit node.
6446 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
6447 - Fix a regression that caused Tor to rebind its ports if it receives
6448 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
6449 - Remove an extra pair of quotation marks around the error
6450 message in control-port STATUS_GENERAL BUG events. Bugfix on
6451 0.1.2.6-alpha; fixes bug 3732.
6453 o Minor features (relays):
6454 - Ensure that no empty [dirreq-](read|write)-history lines are added
6455 to an extrainfo document. Implements ticket 2497.
6456 - When bandwidth accounting is enabled, be more generous with how
6457 much bandwidth we'll use up before entering "soft hibernation".
6458 Previously, we'd refuse new connections and circuits once we'd
6459 used up 95% of our allotment. Now, we use up 95% of our allotment,
6460 AND make sure that we have no more than 500MB (or 3 hours of
6461 expected traffic, whichever is lower) remaining before we enter
6463 - Relays now log the reason for publishing a new relay descriptor,
6464 so we have a better chance of hunting down instances of bug 1810.
6465 Resolves ticket 3252.
6466 - Log a little more clearly about the times at which we're no longer
6467 accepting new connections (e.g. due to hibernating). Resolves
6469 - When AllowSingleHopExits is set, print a warning to explain to the
6470 relay operator why most clients are avoiding her relay.
6471 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
6472 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
6473 clients are already deprecated because of security bugs.
6475 o Minor features (network statistics):
6476 - Directory mirrors that set "DirReqStatistics 1" write statistics
6477 about directory requests to disk every 24 hours. As compared to the
6478 "--enable-geoip-stats" ./configure flag in 0.2.1.x, there are a few
6479 improvements: 1) stats are written to disk exactly every 24 hours;
6480 2) estimated shares of v2 and v3 requests are determined as mean
6481 values, not at the end of a measurement period; 3) unresolved
6482 requests are listed with country code '??'; 4) directories also
6483 measure download times.
6484 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
6485 number of exit streams and transferred bytes per port to disk every
6487 - Relays that set "CellStatistics 1" write statistics on how long
6488 cells spend in their circuit queues to disk every 24 hours.
6489 - Entry nodes that set "EntryStatistics 1" write statistics on the
6490 rough number and origins of connecting clients to disk every 24
6492 - Relays that write any of the above statistics to disk and set
6493 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
6494 their extra-info documents. Implements proposal 166.
6496 o Minor features (GeoIP and statistics):
6497 - Provide a log message stating which geoip file we're parsing
6498 instead of just stating that we're parsing the geoip file.
6499 Implements ticket 2432.
6500 - Make sure every relay writes a state file at least every 12 hours.
6501 Previously, a relay could go for weeks without writing its state
6502 file, and on a crash could lose its bandwidth history, capacity
6503 estimates, client country statistics, and so on. Addresses bug 3012.
6504 - Relays report the number of bytes spent on answering directory
6505 requests in extra-info descriptors similar to {read,write}-history.
6506 Implements enhancement 1790.
6507 - Report only the top 10 ports in exit-port stats in order not to
6508 exceed the maximum extra-info descriptor length of 50 KB. Implements
6510 - If writing the state file to disk fails, wait up to an hour before
6511 retrying again, rather than trying again each second. Fixes bug
6512 2346; bugfix on Tor 0.1.1.3-alpha.
6513 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
6514 when we switch from being a public relay to a bridge. Otherwise
6515 there will still be clients that see the relay in their consensus,
6516 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes
6518 - Update to the August 2 2011 Maxmind GeoLite Country database.
6520 o Minor features (clients):
6521 - When expiring circuits, use microsecond timers rather than
6522 one-second timers. This can avoid an unpleasant situation where a
6523 circuit is launched near the end of one second and expired right
6524 near the beginning of the next, and prevent fluctuations in circuit
6526 - If we've configured EntryNodes and our network goes away and/or all
6527 our entrynodes get marked down, optimistically retry them all when
6528 a new socks application request appears. Fixes bug 1882.
6529 - Always perform router selections using weighted relay bandwidth,
6530 even if we don't need a high capacity circuit at the time. Non-fast
6531 circuits now only differ from fast ones in that they can use relays
6532 not marked with the Fast flag. This "feature" could turn out to
6533 be a horrible bug; we should investigate more before it goes into
6535 - When we run out of directory information such that we can't build
6536 circuits, but then get enough that we can build circuits, log when
6537 we actually construct a circuit, so the user has a better chance of
6538 knowing what's going on. Fixes bug 1362.
6539 - Log SSL state transitions at debug level during handshake, and
6540 include SSL states in error messages. This may help debug future
6541 SSL handshake issues.
6543 o Minor features (directory authorities):
6544 - When a router changes IP address or port, authorities now launch
6545 a new reachability test for it. Implements ticket 1899.
6546 - Directory authorities now reject relays running any versions of
6547 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
6548 known bugs that keep RELAY_EARLY cells from working on rendezvous
6549 circuits. Followup to fix for bug 2081.
6550 - Directory authorities now reject relays running any version of Tor
6551 older than 0.2.0.26-rc. That version is the earliest that fetches
6552 current directory information correctly. Fixes bug 2156.
6553 - Directory authorities now do an immediate reachability check as soon
6554 as they hear about a new relay. This change should slightly reduce
6555 the time between setting up a relay and getting listed as running
6556 in the consensus. It should also improve the time between setting
6557 up a bridge and seeing use by bridge users.
6558 - Directory authorities no longer launch a TLS connection to every
6559 relay as they startup. Now that we have 2k+ descriptors cached,
6560 the resulting network hiccup is becoming a burden. Besides,
6561 authorities already avoid voting about Running for the first half
6562 hour of their uptime.
6563 - Directory authorities now log the source of a rejected POSTed v3
6564 networkstatus vote, so we can track failures better.
6565 - Backport code from 0.2.3.x that allows directory authorities to
6566 clean their microdescriptor caches. Needed to resolve bug 2230.
6568 o Minor features (hidden services):
6569 - Use computed circuit-build timeouts to decide when to launch
6570 parallel introduction circuits for hidden services. (Previously,
6571 we would retry after 15 seconds.)
6572 - Don't allow v0 hidden service authorities to act as clients.
6573 Required by fix for bug 3000.
6574 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
6575 by fix for bug 3000.
6576 - Make hidden services work better in private Tor networks by not
6577 requiring any uptime to join the hidden service descriptor
6578 DHT. Implements ticket 2088.
6579 - Log (at info level) when purging pieces of hidden-service-client
6580 state because of SIGNAL NEWNYM.
6582 o Minor features (controller interface):
6583 - New "GETINFO net/listeners/(type)" controller command to return
6584 a list of addresses and ports that are bound for listeners for a
6585 given connection type. This is useful when the user has configured
6586 "SocksPort auto" and the controller needs to know which port got
6587 chosen. Resolves another part of ticket 3076.
6588 - Have the controller interface give a more useful message than
6589 "Internal Error" in response to failed GETINFO requests.
6590 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
6591 event, to give information on the current rate of circuit timeouts
6592 over our stored history.
6593 - The 'EXTENDCIRCUIT' control port command can now be used with
6594 a circ id of 0 and no path. This feature will cause Tor to build
6595 a new 'fast' general purpose circuit using its own path selection
6597 - Added a BUILDTIMEOUT_SET controller event to describe changes
6598 to the circuit build timeout.
6599 - New controller command "getinfo config-text". It returns the
6600 contents that Tor would write if you send it a SAVECONF command,
6601 so the controller can write the file to disk itself.
6603 o Minor features (controller protocol):
6604 - Add a new ControlSocketsGroupWritable configuration option: when
6605 it is turned on, ControlSockets are group-writeable by the default
6606 group of the current user. Patch by Jérémy Bobbio; implements
6608 - Tor now refuses to create a ControlSocket in a directory that is
6609 world-readable (or group-readable if ControlSocketsGroupWritable
6610 is 0). This is necessary because some operating systems do not
6611 enforce permissions on an AF_UNIX sockets. Permissions on the
6612 directory holding the socket, however, seems to work everywhere.
6613 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
6614 not. This would lead to a cookie that is still not group readable.
6615 Closes bug 1843. Suggested by katmagic.
6616 - Future-proof the controller protocol a bit by ignoring keyword
6617 arguments we do not recognize.
6619 o Minor features (more useful logging):
6620 - Revise most log messages that refer to nodes by nickname to
6621 instead use the "$key=nickname at address" format. This should be
6622 more useful, especially since nicknames are less and less likely
6623 to be unique. Resolves ticket 3045.
6624 - When an HTTPS proxy reports "403 Forbidden", we now explain
6625 what it means rather than calling it an unexpected status code.
6626 Closes bug 2503. Patch from Michael Yakubovich.
6627 - Rate-limit a warning about failures to download v2 networkstatus
6628 documents. Resolves part of bug 1352.
6629 - Rate-limit the "your application is giving Tor only an IP address"
6630 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
6631 - Rate-limit "Failed to hand off onionskin" warnings.
6632 - When logging a rate-limited warning, we now mention how many messages
6633 got suppressed since the last warning.
6634 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
6635 2 no signature, 4 required" messages about consensus signatures
6636 easier to read, and make sure they get logged at the same severity
6637 as the messages explaining which keys are which. Fixes bug 1290.
6638 - Don't warn when we have a consensus that we can't verify because
6639 of missing certificates, unless those certificates are ones
6640 that we have been trying and failing to download. Fixes bug 1145.
6642 o Minor features (log domains):
6643 - Add documentation for configuring logging at different severities in
6644 different log domains. We've had this feature since 0.2.1.1-alpha,
6645 but for some reason it never made it into the manpage. Fixes
6647 - Make it simpler to specify "All log domains except for A and B".
6648 Previously you needed to say "[*,~A,~B]". Now you can just say
6650 - Add a "LogMessageDomains 1" option to include the domains of log
6651 messages along with the messages. Without this, there's no way
6652 to use log domains without reading the source or doing a lot
6654 - Add a new "Handshake" log domain for activities that happen
6655 during the TLS handshake.
6657 o Minor features (build process):
6658 - Make compilation with clang possible when using
6659 "--enable-gcc-warnings" by removing two warning options that clang
6660 hasn't implemented yet and by fixing a few warnings. Resolves
6662 - Detect platforms that brokenly use a signed size_t, and refuse to
6663 build there. Found and analyzed by doorss and rransom.
6664 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
6666 - Add support for statically linking zlib by specifying
6667 "--enable-static-zlib", to go with our support for statically
6668 linking openssl and libevent. Resolves bug 1358.
6669 - Instead of adding the svn revision to the Tor version string, report
6670 the git commit (when we're building from a git checkout).
6671 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
6673 - New --digests command-line switch to output the digests of the
6674 source files Tor was built with.
6675 - Generate our manpage and HTML documentation using Asciidoc. This
6676 change should make it easier to maintain the documentation, and
6677 produce nicer HTML. The build process fails if asciidoc cannot
6678 be found and building with asciidoc isn't disabled (via the
6679 "--disable-asciidoc" argument to ./configure. Skipping the manpage
6680 speeds up the build considerably.
6682 o Minor features (options / torrc):
6683 - Warn when the same option is provided more than once in a torrc
6684 file, on the command line, or in a single SETCONF statement, and
6685 the option is one that only accepts a single line. Closes bug 1384.
6686 - Warn when the user configures two HiddenServiceDir lines that point
6687 to the same directory. Bugfix on 0.0.6 (the version introducing
6688 HiddenServiceDir); fixes bug 3289.
6689 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
6690 do individual connection-level rate limiting of clients. The torrc
6691 config options with the same names trump the consensus params, if
6692 both are present. Replaces the old "bwconnrate" and "bwconnburst"
6693 consensus params which were broken from 0.2.2.7-alpha through
6694 0.2.2.14-alpha. Closes bug 1947.
6695 - New config option "WarnUnsafeSocks 0" disables the warning that
6696 occurs whenever Tor receives a socks handshake using a version of
6697 the socks protocol that can only provide an IP address (rather
6698 than a hostname). Setups that do DNS locally over Tor are fine,
6699 and we shouldn't spam the logs in that case.
6700 - New config option "CircuitStreamTimeout" to override our internal
6701 timeout schedule for how many seconds until we detach a stream from
6702 a circuit and try a new circuit. If your network is particularly
6703 slow, you might want to set this to a number like 60.
6704 - New options for SafeLogging to allow scrubbing only log messages
6705 generated while acting as a relay. Specify "SafeLogging relay" if
6706 you want to ensure that only messages known to originate from
6707 client use of the Tor process will be logged unsafely.
6708 - Time and memory units in the configuration file can now be set to
6709 fractional units. For example, "2.5 GB" is now a valid value for
6711 - Support line continuations in the torrc config file. If a line
6712 ends with a single backslash character, the newline is ignored, and
6713 the configuration value is treated as continuing on the next line.
6716 o Minor features (unit tests):
6717 - Revise our unit tests to use the "tinytest" framework, so we
6718 can run tests in their own processes, have smarter setup/teardown
6719 code, and so on. The unit test code has moved to its own
6720 subdirectory, and has been split into multiple modules.
6721 - Add a unit test for cross-platform directory-listing code.
6722 - Add some forgotten return value checks during unit tests. Found
6724 - Use GetTempDir to find the proper temporary directory location on
6725 Windows when generating temporary files for the unit tests. Patch
6728 o Minor features (misc):
6729 - The "torify" script now uses torsocks where available.
6730 - Make Libevent log messages get delivered to controllers later,
6731 and not from inside the Libevent log handler. This prevents unsafe
6732 reentrant Libevent calls while still letting the log messages
6734 - Certain Tor clients (such as those behind check.torproject.org) may
6735 want to fetch the consensus in an extra early manner. To enable this
6736 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
6737 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
6738 as only certain clients who must have this information sooner should
6740 - Expand homedirs passed to tor-checkkey. This should silence a
6741 coverity complaint about passing a user-supplied string into
6742 open() without checking it.
6743 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
6744 used on bridges, and it makes bridge scanning somewhat easier.
6745 - Create the /var/run/tor directory on startup on OpenSUSE if it is
6746 not already created. Patch from Andreas Stieger. Fixes bug 2573.
6748 o Minor bugfixes (relays):
6749 - When a relay decides that its DNS is too broken for it to serve
6750 as an exit server, it advertised itself as a non-exit, but
6751 continued to act as an exit. This could create accidental
6752 partitioning opportunities for users. Instead, if a relay is
6753 going to advertise reject *:* as its exit policy, it should
6754 really act with exit policy "reject *:*". Fixes bug 2366.
6755 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
6756 - Publish a router descriptor even if generating an extra-info
6757 descriptor fails. Previously we would not publish a router
6758 descriptor without an extra-info descriptor; this can cause fast
6759 exit relays collecting exit-port statistics to drop from the
6760 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
6761 - When we're trying to guess whether we know our IP address as
6762 a relay, we would log various ways that we failed to guess
6763 our address, but never log that we ended up guessing it
6764 successfully. Now add a log line to help confused and anxious
6765 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
6766 - For bandwidth accounting, calculate our expected bandwidth rate
6767 based on the time during which we were active and not in
6768 soft-hibernation during the last interval. Previously, we were
6769 also considering the time spent in soft-hibernation. If this
6770 was a long time, we would wind up underestimating our bandwidth
6771 by a lot, and skewing our wakeup time towards the start of the
6772 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
6773 - Demote a confusing TLS warning that relay operators might get when
6774 someone tries to talk to their ORPort. It is not the operator's
6775 fault, nor can they do anything about it. Fixes bug 1364; bugfix
6777 - Change "Application request when we're believed to be offline."
6778 notice to "Application request when we haven't used client
6779 functionality lately.", to clarify that it's not an error. Bugfix
6780 on 0.0.9.3; fixes bug 1222.
6782 o Minor bugfixes (bridges):
6783 - When a client starts or stops using bridges, never use a circuit
6784 that was built before the configuration change. This behavior could
6785 put at risk a user who uses bridges to ensure that her traffic
6786 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
6788 - Do not reset the bridge descriptor download status every time we
6789 re-parse our configuration or get a configuration change. Fixes
6790 bug 3019; bugfix on 0.2.0.3-alpha.
6791 - Users couldn't configure a regular relay to be their bridge. It
6792 didn't work because when Tor fetched the bridge descriptor, it found
6793 that it already had it, and didn't realize that the purpose of the
6794 descriptor had changed. Now we replace routers with a purpose other
6795 than bridge with bridge descriptors when fetching them. Bugfix on
6796 0.1.1.9-alpha. Fixes bug 1776.
6797 - In the special case where you configure a public exit relay as your
6798 bridge, Tor would be willing to use that exit relay as the last
6799 hop in your circuit as well. Now we fail that circuit instead.
6800 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
6802 o Minor bugfixes (clients):
6803 - We now ask the other side of a stream (the client or the exit)
6804 for more data on that stream when the amount of queued data on
6805 that stream dips low enough. Previously, we wouldn't ask the
6806 other side for more data until either it sent us more data (which
6807 it wasn't supposed to do if it had exhausted its window!) or we
6808 had completely flushed all our queued data. This flow control fix
6809 should improve throughput. Fixes bug 2756; bugfix on the earliest
6810 released versions of Tor (svn commit r152).
6811 - When a client finds that an origin circuit has run out of 16-bit
6812 stream IDs, we now mark it as unusable for new streams. Previously,
6813 we would try to close the entire circuit. Bugfix on 0.0.6.
6814 - Make it explicit that we don't cannibalize one-hop circuits. This
6815 happens in the wild, but doesn't turn out to be a problem because
6816 we fortunately don't use those circuits. Many thanks to outofwords
6817 for the initial analysis and to swissknife who confirmed that
6818 two-hop circuits are actually created.
6819 - Resolve an edge case in path weighting that could make us misweight
6820 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
6821 - Make the DNSPort option work with libevent 2.x. Don't alter the
6822 behavior for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
6824 o Minor bugfixes (directory authorities):
6825 - Make directory authorities more accurate at recording when
6826 relays that have failed several reachability tests became
6827 unreachable, so we can provide more accuracy at assigning Stable,
6828 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
6829 - Directory authorities are now more robust to hops back in time
6830 when calculating router stability. Previously, if a run of uptime
6831 or downtime appeared to be negative, the calculation could give
6832 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
6834 - Directory authorities will now attempt to download consensuses
6835 if their own efforts to make a live consensus have failed. This
6836 change means authorities that restart will fetch a valid
6837 consensus, and it means authorities that didn't agree with the
6838 current consensus will still fetch and serve it if it has enough
6839 signatures. Bugfix on 0.2.0.9-alpha; fixes bug 1300.
6840 - Never vote for a server as "Running" if we have a descriptor for
6841 it claiming to be hibernating, and that descriptor was published
6842 more recently than our last contact with the server. Bugfix on
6843 0.2.0.3-alpha; fixes bug 911.
6844 - Directory authorities no longer change their opinion of, or vote on,
6845 whether a router is Running, unless they have themselves been
6846 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
6849 o Minor bugfixes (hidden services):
6850 - Log malformed requests for rendezvous descriptors as protocol
6851 warnings, not warnings. Also, use a more informative log message
6852 in case someone sees it at log level warning without prior
6853 info-level messages. Fixes bug 2748; bugfix on 0.2.0.10-alpha.
6854 - Accept hidden service descriptors if we think we might be a hidden
6855 service directory, regardless of what our consensus says. This
6856 helps robustness, since clients and hidden services can sometimes
6857 have a more up-to-date view of the network consensus than we do,
6858 and if they think that the directory authorities list us a HSDir,
6859 we might actually be one. Related to bug 2732; bugfix on
6861 - Correct the warning displayed when a rendezvous descriptor exceeds
6862 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
6864 - Clients and hidden services now use HSDir-flagged relays for hidden
6865 service descriptor downloads and uploads even if the relays have no
6866 DirPort set and the client has disabled TunnelDirConns. This will
6867 eventually allow us to give the HSDir flag to relays with no
6868 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
6869 - Only limit the lengths of single HS descriptors, even when multiple
6870 HS descriptors are published to an HSDir relay in a single POST
6871 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
6873 o Minor bugfixes (controllers):
6874 - Allow GETINFO fingerprint to return a fingerprint even when
6875 we have not yet built a router descriptor. Fixes bug 3577;
6876 bugfix on 0.2.0.1-alpha.
6877 - Send a SUCCEEDED stream event to the controller when a reverse
6878 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
6879 discovered by katmagic.
6880 - Remove a trailing asterisk from "exit-policy/default" in the
6881 output of the control port command "GETINFO info/names". Bugfix
6883 - Make the SIGNAL DUMP controller command work on FreeBSD. Fixes bug
6884 2917. Bugfix on 0.1.1.1-alpha.
6885 - When we restart our relay, we might get a successful connection
6886 from the outside before we've started our reachability tests,
6887 triggering a warning: "ORPort found reachable, but I have no
6888 routerinfo yet. Failing to inform controller of success." This
6889 bug was harmless unless Tor is running under a controller
6890 like Vidalia, in which case the controller would never get a
6891 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
6893 - When a controller changes TrackHostExits, remove mappings for
6894 hosts that should no longer have their exits tracked. Bugfix on
6896 - When a controller changes VirtualAddrNetwork, remove any mappings
6897 for hosts that were automapped to the old network. Bugfix on
6899 - When a controller changes one of the AutomapHosts* options, remove
6900 any mappings for hosts that should no longer be automapped. Bugfix
6902 - Fix an off-by-one error in calculating some controller command
6903 argument lengths. Fortunately, this mistake is harmless since
6904 the controller code does redundant NUL termination too. Found by
6905 boboper. Bugfix on 0.1.1.1-alpha.
6906 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
6907 would return "551 Internal error" rather than "552 Unrecognized key
6908 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
6909 - Don't spam the controller with events when we have no file
6910 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
6911 for log messages was already solved from bug 748.)
6912 - Emit a GUARD DROPPED controller event for a case we missed.
6913 - Ensure DNS requests launched by "RESOLVE" commands from the
6914 controller respect the __LeaveStreamsUnattached setconf options. The
6915 same goes for requests launched via DNSPort or transparent
6916 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
6918 o Minor bugfixes (config options):
6919 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
6920 Change the limit to 512 characters by removing base64 newlines.
6921 Fixes bug 2752. Fix by Michael Yakubovich.
6922 - Complain if PublishServerDescriptor is given multiple arguments that
6923 include 0 or 1. This configuration will be rejected in the future.
6924 Bugfix on 0.2.0.1-alpha; closes bug 1107.
6925 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
6926 Bugfix on 0.2.0.13-alpha; closes bug 928.
6928 o Minor bugfixes (log subsystem fixes):
6929 - When unable to format an address as a string, report its value
6930 as "???" rather than reusing the last formatted address. Bugfix
6932 - Be more consistent in our treatment of file system paths. "~" should
6933 get expanded to the user's home directory in the Log config option.
6934 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
6935 feature for the -f and --DataDirectory options.
6937 o Minor bugfixes (memory management):
6938 - Don't stack-allocate the list of supplementary GIDs when we're
6939 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
6940 could take up to 256K, which is way too much stack. Found by
6941 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
6942 - Save a couple bytes in memory allocation every time we escape
6943 certain characters in a string. Patch from Florian Zumbiehl.
6945 o Minor bugfixes (protocol correctness):
6946 - When checking for 1024-bit keys, check for 1024 bits, not 128
6947 bytes. This allows Tor to correctly discard keys of length 1017
6948 through 1023. Bugfix on 0.0.9pre5.
6949 - Require that introduction point keys and onion handshake keys
6950 have a public exponent of 65537. Starts to fix bug 3207; bugfix
6952 - Handle SOCKS messages longer than 128 bytes long correctly, rather
6953 than waiting forever for them to finish. Fixes bug 2330; bugfix
6954 on 0.2.0.16-alpha. Found by doorss.
6955 - Never relay a cell for a circuit we have already destroyed.
6956 Between marking a circuit as closeable and finally closing it,
6957 it may have been possible for a few queued cells to get relayed,
6958 even though they would have been immediately dropped by the next
6959 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
6960 - Never queue a cell for a circuit that's already been marked
6962 - Fix a spec conformance issue: the network-status-version token
6963 must be the first token in a v3 consensus or vote. Discovered by
6964 "parakeep". Bugfix on 0.2.0.3-alpha.
6965 - A networkstatus vote must contain exactly one signature. Spec
6966 conformance issue. Bugfix on 0.2.0.3-alpha.
6967 - When asked about a DNS record type we don't support via a
6968 client DNSPort, reply with NOTIMPL rather than an empty
6969 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
6970 - Make more fields in the controller protocol case-insensitive, since
6971 control-spec.txt said they were.
6973 o Minor bugfixes (log messages):
6974 - Fix a log message that said "bits" while displaying a value in
6975 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
6977 - Downgrade "no current certificates known for authority" message from
6978 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
6979 - Correctly describe errors that occur when generating a TLS object.
6980 Previously we would attribute them to a failure while generating a
6981 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
6983 - Fix an instance where a Tor directory mirror might accidentally
6984 log the IP address of a misbehaving Tor client. Bugfix on
6986 - Stop logging at severity 'warn' when some other Tor client tries
6987 to establish a circuit with us using weak DH keys. It's a protocol
6988 violation, but that doesn't mean ordinary users need to hear about
6989 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
6990 - If your relay can't keep up with the number of incoming create
6991 cells, it would log one warning per failure into your logs. Limit
6992 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
6994 o Minor bugfixes (build fixes):
6995 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
6996 - When warning about missing zlib development packages during compile,
6997 give the correct package names. Bugfix on 0.2.0.1-alpha.
6998 - Fix warnings that newer versions of autoconf produce during
6999 ./autogen.sh. These warnings appear to be harmless in our case,
7000 but they were extremely verbose. Fixes bug 2020.
7001 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
7004 o Minor bugfixes (portability):
7005 - Write several files in text mode, on OSes that distinguish text
7006 mode from binary mode (namely, Windows). These files are:
7007 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
7008 that collect those statistics; 'client_keys' and 'hostname' for
7009 hidden services that use authentication; and (in the tor-gencert
7010 utility) newly generated identity and signing keys. Previously,
7011 we wouldn't specify text mode or binary mode, leading to an
7012 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
7013 the DirRecordUsageByCountry option which would have triggered
7014 the assertion failure was added), although this assertion failure
7015 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
7016 - Selectively disable deprecation warnings on OS X because Lion
7017 started deprecating the shipped copy of openssl. Fixes bug 3643.
7018 - Use a wide type to hold sockets when built for 64-bit Windows.
7020 - Fix an issue that prevented static linking of libevent on
7021 some platforms (notably Linux). Fixes bug 2698; bugfix on 0.2.1.23,
7022 where we introduced the "--with-static-libevent" configure option.
7023 - Fix a bug with our locking implementation on Windows that couldn't
7024 correctly detect when a file was already locked. Fixes bug 2504,
7025 bugfix on 0.2.1.6-alpha.
7026 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
7028 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
7029 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
7032 o Minor bugfixes (code correctness):
7033 - Always NUL-terminate the sun_path field of a sockaddr_un before
7034 passing it to the kernel. (Not a security issue: kernels are
7035 smart enough to reject bad sockaddr_uns.) Found by Coverity;
7036 CID #428. Bugfix on Tor 0.2.0.3-alpha.
7037 - Make connection_printf_to_buf()'s behavior sane. Its callers
7038 expect it to emit a CRLF iff the format string ends with CRLF;
7039 it actually emitted a CRLF iff (a) the format string ended with
7040 CRLF or (b) the resulting string was over 1023 characters long or
7041 (c) the format string did not end with CRLF *and* the resulting
7042 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
7043 fixes part of bug 3407.
7044 - Make send_control_event_impl()'s behavior sane. Its callers
7045 expect it to always emit a CRLF at the end of the string; it
7046 might have emitted extra control characters as well. Bugfix on
7047 0.1.1.9-alpha; fixes another part of bug 3407.
7048 - Make crypto_rand_int() check the value of its input correctly.
7049 Previously, it accepted values up to UINT_MAX, but could return a
7050 negative number if given a value above INT_MAX+1. Found by George
7051 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
7052 - Fix a potential null-pointer dereference while computing a
7053 consensus. Bugfix on tor-0.2.0.3-alpha, found with the help of
7055 - If we fail to compute the identity digest of a v3 legacy keypair,
7056 warn, and don't use a buffer-full of junk instead. Bugfix on
7057 0.2.1.1-alpha; fixes bug 3106.
7058 - Resolve an untriggerable issue in smartlist_string_num_isin(),
7059 where if the function had ever in the future been used to check
7060 for the presence of a too-large number, it would have given an
7061 incorrect result. (Fortunately, we only used it for 16-bit
7062 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
7063 - Be more careful about reporting the correct error from a failed
7064 connect() system call. Under some circumstances, it was possible to
7065 look at an incorrect value for errno when sending the end reason.
7066 Bugfix on 0.1.0.1-rc.
7067 - Correctly handle an "impossible" overflow cases in connection byte
7068 counting, where we write or read more than 4GB on an edge connection
7069 in a single second. Bugfix on 0.1.2.8-beta.
7070 - Avoid a double mark-for-free warning when failing to attach a
7071 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
7073 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
7074 found by "cypherpunks". This bug was introduced before the first
7075 Tor release, in svn commit r110.
7076 - Fix a bug in bandwidth history state parsing that could have been
7077 triggered if a future version of Tor ever changed the timing
7078 granularity at which bandwidth history is measured. Bugfix on
7080 - Add assertions to check for overflow in arguments to
7081 base32_encode() and base32_decode(); fix a signed-unsigned
7082 comparison there too. These bugs are not actually reachable in Tor,
7083 but it's good to prevent future errors too. Found by doorss.
7084 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
7086 - Set target port in get_interface_address6() correctly. Bugfix
7087 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
7088 - Fix an impossible-to-actually-trigger buffer overflow in relay
7089 descriptor generation. Bugfix on 0.1.0.15.
7090 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
7092 o Minor bugfixes (code improvements):
7093 - After we free an internal connection structure, overwrite it
7094 with a different memory value than we use for overwriting a freed
7095 internal circuit structure. Should help with debugging. Suggested
7097 - If OpenSSL fails to make a duplicate of a private or public key, log
7098 an error message and try to exit cleanly. May help with debugging
7099 if bug 1209 ever remanifests.
7100 - Some options used different conventions for uppercasing of acronyms
7101 when comparing manpage and source. Fix those in favor of the
7102 manpage, as it makes sense to capitalize acronyms.
7103 - Take a first step towards making or.h smaller by splitting out
7104 function definitions for all source files in src/or/. Leave
7105 structures and defines in or.h for now.
7106 - Remove a few dead assignments during router parsing. Found by
7108 - Don't use 1-bit wide signed bit fields. Found by coverity.
7109 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
7110 None of the cases where we did this before were wrong, but by making
7111 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
7112 - The memarea code now uses a sentinel value at the end of each area
7113 to make sure nothing writes beyond the end of an area. This might
7114 help debug some conceivable causes of bug 930.
7115 - Always treat failure to allocate an RSA key as an unrecoverable
7117 - Add some more defensive programming for architectures that can't
7118 handle unaligned integer accesses. We don't know of any actual bugs
7119 right now, but that's the best time to fix them. Fixes bug 1943.
7121 o Minor bugfixes (misc):
7122 - Fix a rare bug in rend_fn unit tests: we would fail a test when
7123 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
7124 on 0.2.0.10-alpha; fixes bug 1808.
7125 - Where available, use Libevent 2.0's periodic timers so that our
7126 once-per-second cleanup code gets called even more closely to
7127 once per second than it would otherwise. Fixes bug 943.
7128 - Ignore OutboundBindAddress when connecting to localhost.
7129 Connections to localhost need to come _from_ localhost, or else
7130 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
7132 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
7134 - If any of the v3 certs we download are unparseable, we should
7135 actually notice the failure so we don't retry indefinitely. Bugfix
7136 on 0.2.0.x; reported by "rotator".
7137 - When Tor fails to parse a descriptor of any kind, dump it to disk.
7138 Might help diagnosing bug 1051.
7139 - Make our 'torify' script more portable; if we have only one of
7140 'torsocks' or 'tsocks' installed, don't complain to the user;
7141 and explain our warning about tsocks better.
7142 - Fix some urls in the exit notice file and make it XHTML1.1 strict
7143 compliant. Based on a patch from Christian Kujau.
7145 o Documentation changes:
7146 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
7147 - Resolve all doxygen warnings except those for missing documentation.
7149 - Add doxygen documentation for more functions, fields, and types.
7150 - Convert the HACKING file to asciidoc, and add a few new sections
7151 to it, explaining how we use Git, how we make changelogs, and
7152 what should go in a patch.
7153 - Document the default socks host and port (127.0.0.1:9050) for
7155 - Removed some unnecessary files from the source distribution. The
7156 AUTHORS file has now been merged into the people page on the
7157 website. The roadmaps and design doc can now be found in the
7158 projects directory in svn.
7160 o Deprecated and removed features (config):
7161 - Remove the torrc.complete file. It hasn't been kept up to date
7162 and users will have better luck checking out the manpage.
7163 - Remove the HSAuthorityRecordStats option that version 0 hidden
7164 service authorities could use to track statistics of overall v0
7165 hidden service usage.
7166 - Remove the obsolete "NoPublish" option; it has been flagged
7167 as obsolete and has produced a warning since 0.1.1.18-rc.
7168 - Caches no longer download and serve v2 networkstatus documents
7169 unless FetchV2Networkstatus flag is set: these documents haven't
7170 haven't been used by clients or relays since 0.2.0.x. Resolves
7173 o Deprecated and removed features (controller):
7174 - The controller no longer accepts the old obsolete "addr-mappings/"
7175 or "unregistered-servers-" GETINFO values.
7176 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
7177 always on; using them is necessary for correct forward-compatible
7180 o Deprecated and removed features (misc):
7181 - Hidden services no longer publish version 0 descriptors, and clients
7182 do not request or use version 0 descriptors. However, the old hidden
7183 service authorities still accept and serve version 0 descriptors
7184 when contacted by older hidden services/clients.
7185 - Remove undocumented option "-F" from tor-resolve: it hasn't done
7186 anything since 0.2.1.16-rc.
7187 - Remove everything related to building the expert bundle for OS X.
7188 It has confused many users, doesn't work right on OS X 10.6,
7189 and is hard to get rid of once installed. Resolves bug 1274.
7190 - Remove support for .noconnect style addresses. Nobody was using
7191 them, and they provided another avenue for detecting Tor users
7192 via application-level web tricks.
7193 - When we fixed bug 1038 we had to put in a restriction not to send
7194 RELAY_EARLY cells on rend circuits. This was necessary as long
7195 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
7196 active. Now remove this obsolete check. Resolves bug 2081.
7197 - Remove workaround code to handle directory responses from servers
7198 that had bug 539 (they would send HTTP status 503 responses _and_
7199 send a body too). Since only server versions before
7200 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
7201 keep the workaround in place.
7202 - Remove the old 'fuzzy time' logic. It was supposed to be used for
7203 handling calculations where we have a known amount of clock skew and
7204 an allowed amount of unknown skew. But we only used it in three
7205 places, and we never adjusted the known/unknown skew values. This is
7206 still something we might want to do someday, but if we do, we'll
7207 want to do it differently.
7208 - Remove the "--enable-iphone" option to ./configure. According to
7209 reports from Marco Bonetti, Tor builds fine without any special
7210 tweaking on recent iPhone SDK versions.
7213 Changes in version 0.2.1.30 - 2011-02-23
7214 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
7215 change is a slight tweak to Tor's TLS handshake that makes relays
7216 and bridges that run this new version reachable from Iran again.
7217 We don't expect this tweak will win the arms race long-term, but it
7218 buys us time until we roll out a better solution.
7221 - Stop sending a CLOCK_SKEW controller status event whenever
7222 we fetch directory information from a relay that has a wrong clock.
7223 Instead, only inform the controller when it's a trusted authority
7224 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
7225 the rest of bug 1074.
7226 - Fix a bounds-checking error that could allow an attacker to
7227 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
7229 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
7230 Tor would ignore their RelayBandwidthBurst setting,
7231 potentially using more bandwidth than expected. Bugfix on
7232 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
7233 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
7234 hidserv" in her torrc. The 'hidserv' argument never controlled
7235 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
7238 - Adjust our TLS Diffie-Hellman parameters to match those used by
7240 - Update to the February 1 2011 Maxmind GeoLite Country database.
7243 - Check for and reject overly long directory certificates and
7244 directory tokens before they have a chance to hit any assertions.
7245 Bugfix on 0.2.1.28. Found by "doorss".
7246 - Bring the logic that gathers routerinfos and assesses the
7247 acceptability of circuits into line. This prevents a Tor OP from
7248 getting locked in a cycle of choosing its local OR as an exit for a
7249 path (due to a .exit request) and then rejecting the circuit because
7250 its OR is not listed yet. It also prevents Tor clients from using an
7251 OR running in the same instance as an exit (due to a .exit request)
7252 if the OR does not meet the same requirements expected of an OR
7253 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
7255 o Packaging changes:
7256 - Stop shipping the Tor specs files and development proposal documents
7257 in the tarball. They are now in a separate git repository at
7258 git://git.torproject.org/torspec.git
7259 - Do not include Git version tags as though they are SVN tags when
7260 generating a tarball from inside a repository that has switched
7261 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
7264 Changes in version 0.2.1.29 - 2011-01-15
7265 Tor 0.2.1.29 continues our recent code security audit work. The main
7266 fix resolves a remote heap overflow vulnerability that can allow remote
7267 code execution. Other fixes address a variety of assert and crash bugs,
7268 most of which we think are hard to exploit remotely.
7270 o Major bugfixes (security):
7271 - Fix a heap overflow bug where an adversary could cause heap
7272 corruption. This bug probably allows remote code execution
7273 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
7275 - Prevent a denial-of-service attack by disallowing any
7276 zlib-compressed data whose compression factor is implausibly
7277 high. Fixes part of bug 2324; reported by "doorss".
7278 - Zero out a few more keys in memory before freeing them. Fixes
7279 bug 2384 and part of bug 2385. These key instances found by
7280 "cypherpunks", based on Andrew Case's report about being able
7281 to find sensitive data in Tor's memory space if you have enough
7282 permissions. Bugfix on 0.0.2pre9.
7284 o Major bugfixes (crashes):
7285 - Prevent calls to Libevent from inside Libevent log handlers.
7286 This had potential to cause a nasty set of crashes, especially
7287 if running Libevent with debug logging enabled, and running
7288 Tor with a controller watching for low-severity log messages.
7289 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
7290 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
7291 underflow errors there too. Fixes the other part of bug 2324.
7292 - Fix a bug where we would assert if we ever had a
7293 cached-descriptors.new file (or another file read directly into
7294 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
7295 on 0.2.1.25. Found by doorss.
7296 - Fix some potential asserts and parsing issues with grossly
7297 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
7300 o Minor bugfixes (other):
7301 - Fix a bug with handling misformed replies to reverse DNS lookup
7302 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
7303 bug reported by doorss.
7304 - Fix compilation on mingw when a pthreads compatibility library
7305 has been installed. (We don't want to use it, so we shouldn't
7306 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
7307 - Fix a bug where we would declare that we had run out of virtual
7308 addresses when the address space was only half-exhausted. Bugfix
7310 - Correctly handle the case where AutomapHostsOnResolve is set but
7311 no virtual addresses are available. Fixes bug 2328; bugfix on
7312 0.1.2.1-alpha. Bug found by doorss.
7313 - Correctly handle wrapping around when we run out of virtual
7314 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
7317 - Update to the January 1 2011 Maxmind GeoLite Country database.
7318 - Introduce output size checks on all of our decryption functions.
7321 - Tor does not build packages correctly with Automake 1.6 and earlier;
7322 added a check to Makefile.am to make sure that we're building with
7323 Automake 1.7 or later.
7324 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
7325 because we built it with a too-old version of automake. Thus that
7326 release broke ./configure --enable-openbsd-malloc, which is popular
7327 among really fast exit relays on Linux.
7330 Changes in version 0.2.1.28 - 2010-12-17
7331 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
7332 exploitable bugs. We also took this opportunity to change the IP address
7333 for one of our directory authorities, and to update the geoip database
7337 - Fix a remotely exploitable bug that could be used to crash instances
7338 of Tor remotely by overflowing on the heap. Remote-code execution
7339 hasn't been confirmed, but can't be ruled out. Everyone should
7340 upgrade. Bugfix on the 0.1.1 series and later.
7342 o Directory authority changes:
7343 - Change IP address and ports for gabelmoo (v3 directory authority).
7346 - Update to the December 1 2010 Maxmind GeoLite Country database.
7349 Changes in version 0.2.1.27 - 2010-11-23
7350 Yet another OpenSSL security patch broke its compatibility with Tor:
7351 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
7352 also took this opportunity to fix several crash bugs, integrate a new
7353 directory authority, and update the bundled GeoIP database.
7356 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
7357 No longer set the tlsext_host_name extension on server SSL objects;
7358 but continue to set it on client SSL objects. Our goal in setting
7359 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
7360 bugfix on 0.2.1.1-alpha.
7361 - Do not log messages to the controller while shrinking buffer
7362 freelists. Doing so would sometimes make the controller connection
7363 try to allocate a buffer chunk, which would mess up the internals
7364 of the freelist and cause an assertion failure. Fixes bug 1125;
7365 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
7366 - Learn our external IP address when we're a relay or bridge, even if
7367 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
7368 where we introduced bridge relays that don't need to publish to
7369 be useful. Fixes bug 2050.
7370 - Do even more to reject (and not just ignore) annotations on
7371 router descriptors received anywhere but from the cache. Previously
7372 we would ignore such annotations at first, but cache them to disk
7373 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
7374 - When you're using bridges and your network goes away and your
7375 bridges get marked as down, recover when you attempt a new socks
7376 connection (if the network is back), rather than waiting up to an
7377 hour to try fetching new descriptors for your bridges. Bugfix on
7378 0.2.0.3-alpha; fixes bug 1981.
7381 - Move to the November 2010 Maxmind GeoLite country db (rather
7382 than the June 2009 ip-to-country GeoIP db) for our statistics that
7383 count how many users relays are seeing from each country. Now we'll
7384 have more accurate data, especially for many African countries.
7386 o New directory authorities:
7387 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
7391 - Fix an assertion failure that could occur in directory caches or
7392 bridge users when using a very short voting interval on a testing
7393 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
7395 - Enforce multiplicity rules when parsing annotations. Bugfix on
7396 0.2.0.8-alpha. Found by piebeer.
7397 - Allow handshaking OR connections to take a full KeepalivePeriod
7398 seconds to handshake. Previously, we would close them after
7399 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
7400 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
7402 - When building with --enable-gcc-warnings on OpenBSD, disable
7403 warnings in system headers. This makes --enable-gcc-warnings
7404 pass on OpenBSD 4.8.
7407 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
7408 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
7409 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
7410 Servers can start sending this code when enough clients recognize
7411 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
7412 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
7413 Patch from mingw-san.
7416 - Remove the old debian/ directory from the main Tor distribution.
7417 The official Tor-for-debian git repository lives at the URL
7418 https://git.torproject.org/debian/tor.git
7419 - Stop shipping the old doc/website/ directory in the tarball. We
7420 changed the website format in late 2010, and what we shipped in
7421 0.2.1.26 really wasn't that useful anyway.
7424 Changes in version 0.2.1.26 - 2010-05-02
7425 Tor 0.2.1.26 addresses the recent connection and memory overload
7426 problems we've been seeing on relays, especially relays with their
7427 DirPort open. If your relay has been crashing, or you turned it off
7428 because it used too many resources, give this release a try.
7430 This release also fixes yet another instance of broken OpenSSL libraries
7431 that was causing some relays to drop out of the consensus.
7434 - Teach relays to defend themselves from connection overload. Relays
7435 now close idle circuits early if it looks like they were intended
7436 for directory fetches. Relays are also more aggressive about closing
7437 TLS connections that have no circuits on them. Such circuits are
7438 unlikely to be re-used, and tens of thousands of them were piling
7439 up at the fast relays, causing the relays to run out of sockets
7440 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
7441 their directory fetches over TLS).
7442 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
7443 that claim to be earlier than 0.9.8m, but which have in reality
7444 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
7445 behavior. Possible fix for some cases of bug 1346.
7446 - Directory mirrors were fetching relay descriptors only from v2
7447 directory authorities, rather than v3 authorities like they should.
7448 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
7449 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
7452 - Finally get rid of the deprecated and now harmful notion of "clique
7453 mode", where directory authorities maintain TLS connections to
7457 - In the util/threads test, no longer free the test_mutex before all
7458 worker threads have finished. Bugfix on 0.2.1.6-alpha.
7459 - The master thread could starve the worker threads quite badly on
7460 certain systems, causing them to run only partially in the allowed
7461 window. This resulted in test failures. Now the master thread sleeps
7462 occasionally for a few microseconds while the two worker-threads
7463 compete for the mutex. Bugfix on 0.2.0.1-alpha.
7466 Changes in version 0.2.1.25 - 2010-03-16
7467 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
7468 prevent relays from guessing their IP address correctly. It also fixes
7469 several minor potential security bugs.
7472 - Fix a regression from our patch for bug 1244 that caused relays
7473 to guess their IP address incorrectly if they didn't set Address
7474 in their torrc and/or their address fails to resolve. Bugfix on
7475 0.2.1.23; fixes bug 1269.
7476 - When freeing a session key, zero it out completely. We only zeroed
7477 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
7478 patched by ekir. Fixes bug 1254.
7481 - Fix a dereference-then-NULL-check sequence when publishing
7482 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
7484 - Fix another dereference-then-NULL-check sequence. Bugfix on
7485 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
7486 - Make sure we treat potentially not NUL-terminated strings correctly.
7487 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
7490 Changes in version 0.2.1.24 - 2010-02-21
7491 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
7495 - Work correctly out-of-the-box with even more vendor-patched versions
7496 of OpenSSL. In particular, make it so Debian and OS X don't need
7497 customized patches to run/build.
7500 Changes in version 0.2.1.23 - 2010-02-13
7501 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
7502 again on the latest OS X, and updates the location of a directory
7505 o Major bugfixes (performance):
7506 - We were selecting our guards uniformly at random, and then weighting
7507 which of our guards we'd use uniformly at random. This imbalance
7508 meant that Tor clients were severely limited on throughput (and
7509 probably latency too) by the first hop in their circuit. Now we
7510 select guards weighted by currently advertised bandwidth. We also
7511 automatically discard guards picked using the old algorithm. Fixes
7512 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
7515 - Make Tor work again on the latest OS X: when deciding whether to
7516 use strange flags to turn TLS renegotiation on, detect the OpenSSL
7517 version at run-time, not compile time. We need to do this because
7518 Apple doesn't update its dev-tools headers when it updates its
7519 libraries in a security patch.
7520 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
7521 that could happen on 32-bit platforms with 64-bit time_t. Also fix
7522 a memory leak when requesting a hidden service descriptor we've
7523 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
7527 - Refactor resolve_my_address() to not use gethostbyname() anymore.
7528 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
7531 - Avoid a mad rush at the beginning of each month when each client
7532 rotates half of its guards. Instead we spread the rotation out
7533 throughout the month, but we still avoid leaving a precise timestamp
7534 in the state file about when we first picked the guard. Improves
7535 over the behavior introduced in 0.1.2.17.
7538 Changes in version 0.2.1.22 - 2010-01-19
7539 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
7540 authorities -- it would tell you its whole history of bridge descriptors
7541 if you make the right directory request. This stable update also
7542 rotates two of the seven v3 directory authority keys and locations.
7544 o Directory authority changes:
7545 - Rotate keys (both v3 identity and relay identity) for moria1
7549 - Stop bridge directory authorities from answering dbg-stability.txt
7550 directory queries, which would let people fetch a list of all
7551 bridge identities they track. Bugfix on 0.2.1.6-alpha.
7554 Changes in version 0.2.1.21 - 2009-12-21
7555 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
7556 library. If you use Tor on Linux / Unix and you're getting SSL
7557 renegotiation errors, upgrading should help. We also recommend an
7558 upgrade if you're an exit relay.
7561 - Work around a security feature in OpenSSL 0.9.8l that prevents our
7562 handshake from working unless we explicitly tell OpenSSL that we
7563 are using SSL renegotiation safely. We are, of course, but OpenSSL
7564 0.9.8l won't work unless we say we are.
7565 - Avoid crashing if the client is trying to upload many bytes and the
7566 circuit gets torn down at the same time, or if the flip side
7567 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
7570 - Do not refuse to learn about authority certs and v2 networkstatus
7571 documents that are older than the latest consensus. This bug might
7572 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
7573 Spotted and fixed by xmux.
7574 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
7575 trigger platform-specific option misparsing case found by Coverity
7577 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
7578 trigger assert. Fixes bug 1173.
7581 Changes in version 0.2.1.20 - 2009-10-15
7582 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
7583 services at once, prepares for more performance improvements, and
7584 fixes a bunch of smaller bugs.
7586 The Windows and OS X bundles also include a more recent Vidalia,
7587 and switch from Privoxy to Polipo.
7589 The OS X installers are now drag and drop. It's best to un-install
7590 Tor/Vidalia and then install this new bundle, rather than upgrade. If
7591 you want to upgrade, you'll need to update the paths for Tor and Polipo
7592 in the Vidalia Settings window.
7595 - Send circuit or stream sendme cells when our window has decreased
7596 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
7597 by Karsten when testing the "reduce circuit window" performance
7598 patch. Bugfix on the 54th commit on Tor -- from July 2002,
7599 before the release of Tor 0.0.0. This is the new winner of the
7601 - Fix a remotely triggerable memory leak when a consensus document
7602 contains more than one signature from the same voter. Bugfix on
7604 - Avoid segfault in rare cases when finishing an introduction circuit
7605 as a client and finding out that we don't have an introduction key
7606 for it. Fixes bug 1073. Reported by Aaron Swartz.
7609 - Tor now reads the "circwindow" parameter out of the consensus,
7610 and uses that value for its circuit package window rather than the
7611 default of 1000 cells. Begins the implementation of proposal 168.
7613 o New directory authorities:
7614 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
7616 - Move moria1 and tonga to alternate IP addresses.
7619 - Fix a signed/unsigned compile warning in 0.2.1.19.
7620 - Fix possible segmentation fault on directory authorities. Bugfix on
7622 - Fix an extremely rare infinite recursion bug that could occur if
7623 we tried to log a message after shutting down the log subsystem.
7624 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
7625 - Fix an obscure bug where hidden services on 64-bit big-endian
7626 systems might mis-read the timestamp in v3 introduce cells, and
7627 refuse to connect back to the client. Discovered by "rotor".
7628 Bugfix on 0.2.1.6-alpha.
7629 - We were triggering a CLOCK_SKEW controller status event whenever
7630 we connect via the v2 connection protocol to any relay that has
7631 a wrong clock. Instead, we should only inform the controller when
7632 it's a trusted authority that claims our clock is wrong. Bugfix
7633 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
7634 - We were telling the controller about CHECKING_REACHABILITY and
7635 REACHABILITY_FAILED status events whenever we launch a testing
7636 circuit or notice that one has failed. Instead, only tell the
7637 controller when we want to inform the user of overall success or
7638 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
7640 - Don't warn when we're using a circuit that ends with a node
7641 excluded in ExcludeExitNodes, but the circuit is not used to access
7642 the outside world. This should help fix bug 1090. Bugfix on
7644 - Work around a small memory leak in some versions of OpenSSL that
7645 stopped the memory used by the hostname TLS extension from being
7649 - Add a "getinfo status/accepted-server-descriptor" controller
7650 command, which is the recommended way for controllers to learn
7651 whether our server descriptor has been successfully received by at
7652 least on directory authority. Un-recommend good-server-descriptor
7653 getinfo and status events until we have a better design for them.
7656 Changes in version 0.2.1.19 - 2009-07-28
7657 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
7661 - Make accessing hidden services on 0.2.1.x work right again.
7662 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
7663 part of patch provided by "optimist".
7666 - When a relay/bridge is writing out its identity key fingerprint to
7667 the "fingerprint" file and to its logs, write it without spaces. Now
7668 it will look like the fingerprints in our bridges documentation,
7669 and confuse fewer users.
7672 - Relays no longer publish a new server descriptor if they change
7673 their MaxAdvertisedBandwidth config option but it doesn't end up
7674 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
7675 fixes bug 1026. Patch from Sebastian.
7676 - Avoid leaking memory every time we get a create cell but we have
7677 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
7678 fixes bug 1034. Reported by BarkerJr.
7681 Changes in version 0.2.1.18 - 2009-07-24
7682 Tor 0.2.1.18 lays the foundations for performance improvements,
7683 adds status events to help users diagnose bootstrap problems, adds
7684 optional authentication/authorization for hidden services, fixes a
7685 variety of potential anonymity problems, and includes a huge pile of
7686 other features and bug fixes.
7688 o Major features (clients):
7689 - Start sending "bootstrap phase" status events to the controller,
7690 so it can keep the user informed of progress fetching directory
7691 information and establishing circuits. Also inform the controller
7692 if we think we're stuck at a particular bootstrap phase. Implements
7694 - Clients replace entry guards that were chosen more than a few months
7695 ago. This change should significantly improve client performance,
7696 especially once more people upgrade, since relays that have been
7697 a guard for a long time are currently overloaded.
7698 - Network status consensus documents and votes now contain bandwidth
7699 information for each relay. Clients use the bandwidth values
7700 in the consensus, rather than the bandwidth values in each
7701 relay descriptor. This approach opens the door to more accurate
7702 bandwidth estimates once the directory authorities start doing
7703 active measurements. Implements part of proposal 141.
7705 o Major features (relays):
7706 - Disable and refactor some debugging checks that forced a linear scan
7707 over the whole server-side DNS cache. These accounted for over 50%
7708 of CPU time on a relatively busy exit node's gprof profile. Also,
7709 disable some debugging checks that appeared in exit node profile
7710 data. Found by Jacob.
7711 - New DirPortFrontPage option that takes an html file and publishes
7712 it as "/" on the DirPort. Now relay operators can provide a
7713 disclaimer without needing to set up a separate webserver. There's
7714 a sample disclaimer in contrib/tor-exit-notice.html.
7716 o Major features (hidden services):
7717 - Make it possible to build hidden services that only certain clients
7718 are allowed to connect to. This is enforced at several points,
7719 so that unauthorized clients are unable to send INTRODUCE cells
7720 to the service, or even (depending on the type of authentication)
7721 to learn introduction points. This feature raises the bar for
7722 certain kinds of active attacks against hidden services. Design
7723 and code by Karsten Loesing. Implements proposal 121.
7724 - Relays now store and serve v2 hidden service descriptors by default,
7725 i.e., the new default value for HidServDirectoryV2 is 1. This is
7726 the last step in proposal 114, which aims to make hidden service
7727 lookups more reliable.
7729 o Major features (path selection):
7730 - ExitNodes and Exclude*Nodes config options now allow you to restrict
7731 by country code ("{US}") or IP address or address pattern
7732 ("255.128.0.0/16"). Patch from Robert Hogan. It still needs some
7733 refinement to decide what config options should take priority if
7734 you ask to both use a particular node and exclude it.
7736 o Major features (misc):
7737 - When building a consensus, do not include routers that are down.
7738 This cuts down 30% to 40% on consensus size. Implements proposal
7740 - New TestingTorNetwork config option to allow adjustment of
7741 previously constant values that could slow bootstrapping. Implements
7742 proposal 135. Patch from Karsten.
7743 - Convert many internal address representations to optionally hold
7744 IPv6 addresses. Generate and accept IPv6 addresses in many protocol
7745 elements. Make resolver code handle nameservers located at IPv6
7747 - More work on making our TLS handshake blend in: modify the list
7748 of ciphers advertised by OpenSSL in client mode to even more
7749 closely resemble a common web browser. We cheat a little so that
7750 we can advertise ciphers that the locally installed OpenSSL doesn't
7752 - Use the TLS1 hostname extension to more closely resemble browser
7755 o Security fixes (anonymity/entropy):
7756 - Never use a connection with a mismatched address to extend a
7757 circuit, unless that connection is canonical. A canonical
7758 connection is one whose address is authenticated by the router's
7759 identity key, either in a NETINFO cell or in a router descriptor.
7760 - Implement most of proposal 110: The first K cells to be sent
7761 along a circuit are marked as special "early" cells; only K "early"
7762 cells will be allowed. Once this code is universal, we can block
7763 certain kinds of denial-of-service attack by requiring that EXTEND
7764 commands must be sent using an "early" cell.
7765 - Resume using OpenSSL's RAND_poll() for better (and more portable)
7766 cross-platform entropy collection again. We used to use it, then
7767 stopped using it because of a bug that could crash systems that
7768 called RAND_poll when they had a lot of fds open. It looks like the
7769 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
7770 at startup, and to call RAND_poll() when we reseed later only if
7771 we have a non-buggy OpenSSL version.
7772 - When the client is choosing entry guards, now it selects at most
7773 one guard from a given relay family. Otherwise we could end up with
7774 all of our entry points into the network run by the same operator.
7775 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
7776 - Do not use or believe expired v3 authority certificates. Patch
7777 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
7778 - Drop begin cells to a hidden service if they come from the middle
7779 of a circuit. Patch from lark.
7780 - When we erroneously receive two EXTEND cells for the same circuit
7781 ID on the same connection, drop the second. Patch from lark.
7782 - Authorities now vote for the Stable flag for any router whose
7783 weighted MTBF is at least 5 days, regardless of the mean MTBF.
7784 - Clients now never report any stream end reason except 'MISC'.
7785 Implements proposal 148.
7787 o Major bugfixes (crashes):
7788 - Parse dates and IPv4 addresses in a locale- and libc-independent
7789 manner, to avoid platform-dependent behavior on malformed input.
7790 - Fix a crash that occurs on exit nodes when a nameserver request
7791 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
7792 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
7794 - Do not assume that a stack-allocated character array will be
7795 64-bit aligned on platforms that demand that uint64_t access is
7796 aligned. Possible fix for bug 604.
7797 - Resolve a very rare crash bug that could occur when the user forced
7798 a nameserver reconfiguration during the middle of a nameserver
7799 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
7800 - Avoid a "0 divided by 0" calculation when calculating router uptime
7801 at directory authorities. Bugfix on 0.2.0.8-alpha.
7802 - Fix an assertion bug in parsing policy-related options; possible fix
7804 - Rate-limit too-many-sockets messages: when they happen, they happen
7805 a lot and end up filling up the disk. Resolves bug 748.
7806 - Fix a race condition that could cause crashes or memory corruption
7807 when running as a server with a controller listening for log
7809 - Avoid crashing when we have a policy specified in a DirPolicy or
7810 SocksPolicy or ReachableAddresses option with ports set on it,
7811 and we re-load the policy. May fix bug 996.
7812 - Fix an assertion failure on 64-bit platforms when we allocated
7813 memory right up to the end of a memarea, then realigned the memory
7814 one step beyond the end. Fixes a possible cause of bug 930.
7815 - Protect the count of open sockets with a mutex, so we can't
7816 corrupt it when two threads are closing or opening sockets at once.
7817 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
7819 o Major bugfixes (clients):
7820 - Discard router descriptors as we load them if they are more than
7821 five days old. Otherwise if Tor is off for a long time and then
7822 starts with cached descriptors, it will try to use the onion keys
7823 in those obsolete descriptors when building circuits. Fixes bug 887.
7824 - When we choose to abandon a new entry guard because we think our
7825 older ones might be better, close any circuits pending on that
7826 new entry guard connection. This fix should make us recover much
7827 faster when our network is down and then comes back. Bugfix on
7828 0.1.2.8-beta; found by lodger.
7829 - When Tor clients restart after 1-5 days, they discard all their
7830 cached descriptors as too old, but they still use the cached
7831 consensus document. This approach is good for robustness, but
7832 bad for performance: since they don't know any bandwidths, they
7833 end up choosing at random rather than weighting their choice by
7834 speed. Fixed by the above feature of putting bandwidths in the
7837 o Major bugfixes (relays):
7838 - Relays were falling out of the networkstatus consensus for
7839 part of a day if they changed their local config but the
7840 authorities discarded their new descriptor as "not sufficiently
7841 different". Now directory authorities accept a descriptor as changed
7842 if BandwidthRate or BandwidthBurst changed. Partial fix for bug 962;
7844 - Ensure that two circuits can never exist on the same connection
7845 with the same circuit ID, even if one is marked for close. This
7846 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
7847 - Directory authorities were neglecting to mark relays down in their
7848 internal histories if the relays fall off the routerlist without
7849 ever being found unreachable. So there were relays in the histories
7850 that haven't been seen for eight months, and are listed as being
7851 up for eight months. This wreaked havoc on the "median wfu" and
7852 "median mtbf" calculations, in turn making Guard and Stable flags
7853 wrong, hurting network performance. Fixes bugs 696 and 969. Bugfix
7856 o Major bugfixes (hidden services):
7857 - When establishing a hidden service, introduction points that
7858 originate from cannibalized circuits were completely ignored
7859 and not included in rendezvous service descriptors. This might
7860 have been another reason for delay in making a hidden service
7861 available. Bugfix from long ago (0.0.9.x?)
7863 o Major bugfixes (memory and resource management):
7864 - Fixed some memory leaks -- some quite frequent, some almost
7865 impossible to trigger -- based on results from Coverity.
7866 - Speed up parsing and cut down on memory fragmentation by using
7867 stack-style allocations for parsing directory objects. Previously,
7868 this accounted for over 40% of allocations from within Tor's code
7869 on a typical directory cache.
7870 - Use a Bloom filter rather than a digest-based set to track which
7871 descriptors we need to keep around when we're cleaning out old
7872 router descriptors. This speeds up the computation significantly,
7873 and may reduce fragmentation.
7875 o New/changed config options:
7876 - Now NodeFamily and MyFamily config options allow spaces in
7877 identity fingerprints, so it's easier to paste them in.
7878 Suggested by Lucky Green.
7879 - Allow ports 465 and 587 in the default exit policy again. We had
7880 rejected them in 0.1.0.15, because back in 2005 they were commonly
7881 misconfigured and ended up as spam targets. We hear they are better
7882 locked down these days.
7883 - Make TrackHostExit mappings expire a while after their last use, not
7884 after their creation. Patch from Robert Hogan.
7885 - Add an ExcludeExitNodes option so users can list a set of nodes
7886 that should be be excluded from the exit node position, but
7887 allowed elsewhere. Implements proposal 151.
7888 - New --hush command-line option similar to --quiet. While --quiet
7889 disables all logging to the console on startup, --hush limits the
7890 output to messages of warning and error severity.
7891 - New configure/torrc options (--enable-geoip-stats,
7892 DirRecordUsageByCountry) to record how many IPs we've served
7893 directory info to in each country code, how many status documents
7894 total we've sent to each country code, and what share of the total
7895 directory requests we should expect to see.
7896 - Make outbound DNS packets respect the OutboundBindAddress setting.
7897 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
7898 - Allow separate log levels to be configured for different logging
7899 domains. For example, this allows one to log all notices, warnings,
7900 or errors, plus all memory management messages of level debug or
7901 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
7902 - Update to the "June 3 2009" ip-to-country file.
7904 o Minor features (relays):
7905 - Raise the minimum rate limiting to be a relay from 20000 bytes
7906 to 20480 bytes (aka 20KB/s), to match our documentation. Also
7907 update directory authorities so they always assign the Fast flag
7908 to relays with 20KB/s of capacity. Now people running relays won't
7909 suddenly find themselves not seeing any use, if the network gets
7911 - If we're a relay and we change our IP address, be more verbose
7912 about the reason that made us change. Should help track down
7913 further bugs for relays on dynamic IP addresses.
7914 - Exit servers can now answer resolve requests for ip6.arpa addresses.
7915 - Implement most of Proposal 152: allow specialized servers to permit
7916 single-hop circuits, and clients to use those servers to build
7917 single-hop circuits when using a specialized controller. Patch
7918 from Josh Albrecht. Resolves feature request 768.
7919 - When relays do their initial bandwidth measurement, don't limit
7920 to just our entry guards for the test circuits. Otherwise we tend
7921 to have multiple test circuits going through a single entry guard,
7922 which makes our bandwidth test less accurate. Fixes part of bug 654;
7923 patch contributed by Josh Albrecht.
7925 o Minor features (directory authorities):
7926 - Try not to open more than one descriptor-downloading connection
7927 to an authority at once. This should reduce load on directory
7928 authorities. Fixes bug 366.
7929 - Add cross-certification to newly generated certificates, so that
7930 a signing key is enough information to look up a certificate. Start
7931 serving certificates by <identity digest, signing key digest>
7932 pairs. Implements proposal 157.
7933 - When a directory authority downloads a descriptor that it then
7934 immediately rejects, do not retry downloading it right away. Should
7935 save some bandwidth on authorities. Fix for bug 888. Patch by
7937 - Directory authorities now serve a /tor/dbg-stability.txt URL to
7938 help debug WFU and MTBF calculations.
7939 - In directory authorities' approved-routers files, allow
7940 fingerprints with or without space.
7942 o Minor features (directory mirrors):
7943 - When a download gets us zero good descriptors, do not notify
7944 Tor that new directory information has arrived.
7945 - Servers support a new URL scheme for consensus downloads that
7946 allows the client to specify which authorities are trusted.
7947 The server then only sends the consensus if the client will trust
7948 it. Otherwise a 404 error is sent back. Clients use this
7949 new scheme when the server supports it (meaning it's running
7950 0.2.1.1-alpha or later). Implements proposal 134.
7952 o Minor features (bridges):
7953 - If the bridge config line doesn't specify a port, assume 443.
7954 This makes bridge lines a bit smaller and easier for users to
7956 - If we're using bridges and our network goes away, be more willing
7957 to forgive our bridges and try again when we get an application
7960 o Minor features (hidden services):
7961 - When the client launches an introduction circuit, retry with a
7962 new circuit after 30 seconds rather than 60 seconds.
7963 - Launch a second client-side introduction circuit in parallel
7964 after a delay of 15 seconds (based on work by Christian Wilms).
7965 - Hidden services start out building five intro circuits rather
7966 than three, and when the first three finish they publish a service
7967 descriptor using those. Now we publish our service descriptor much
7968 faster after restart.
7969 - Drop the requirement to have an open dir port for storing and
7970 serving v2 hidden service descriptors.
7972 o Minor features (build and packaging):
7973 - On Linux, use the prctl call to re-enable core dumps when the User
7975 - Try to make sure that the version of Libevent we're running with
7976 is binary-compatible with the one we built with. May address bug
7978 - Add a new --enable-local-appdata configuration switch to change
7979 the default location of the datadir on win32 from APPDATA to
7980 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
7981 entirely. Patch from coderman.
7982 - Build correctly against versions of OpenSSL 0.9.8 or later that
7983 are built without support for deprecated functions.
7984 - On platforms with a maximum syslog string length, truncate syslog
7985 messages to that length ourselves, rather than relying on the
7986 system to do it for us.
7987 - Automatically detect MacOSX versions earlier than 10.4.0, and
7988 disable kqueue from inside Tor when running with these versions.
7989 We previously did this from the startup script, but that was no
7990 help to people who didn't use the startup script. Resolves bug 863.
7991 - Build correctly when configured to build outside the main source
7992 path. Patch from Michael Gold.
7993 - Disable GCC's strict alias optimization by default, to avoid the
7994 likelihood of its introducing subtle bugs whenever our code violates
7995 the letter of C99's alias rules.
7996 - Change the contrib/tor.logrotate script so it makes the new
7997 logs as "_tor:_tor" rather than the default, which is generally
7998 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
7999 - Change our header file guard macros to be less likely to conflict
8000 with system headers. Adam Langley noticed that we were conflicting
8001 with log.h on Android.
8002 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
8003 and stop using a warning that had become unfixably verbose under
8005 - Use a lockfile to make sure that two Tor processes are not
8006 simultaneously running with the same datadir.
8007 - Allow OpenSSL to use dynamic locks if it wants.
8008 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
8010 o Minor features (controllers):
8011 - When generating circuit events with verbose nicknames for
8012 controllers, try harder to look up nicknames for routers on a
8013 circuit. (Previously, we would look in the router descriptors we had
8014 for nicknames, but not in the consensus.) Partial fix for bug 941.
8015 - New controller event NEWCONSENSUS that lists the networkstatus
8016 lines for every recommended relay. Now controllers like Torflow
8017 can keep up-to-date on which relays they should be using.
8018 - New controller event "clients_seen" to report a geoip-based summary
8019 of which countries we've seen clients from recently. Now controllers
8020 like Vidalia can show bridge operators that they're actually making
8022 - Add a 'getinfo status/clients-seen' controller command, in case
8023 controllers want to hear clients_seen events but connect late.
8024 - New CONSENSUS_ARRIVED event to note when a new consensus has
8025 been fetched and validated.
8026 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
8027 controllers to prevent SIGHUP from reloading the configuration.
8029 - Return circuit purposes in response to GETINFO circuit-status.
8031 - Serve the latest v3 networkstatus consensus via the control
8032 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
8033 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
8034 controller can query our current bootstrap state in case it attaches
8035 partway through and wants to catch up.
8036 - Provide circuit purposes along with circuit events to the controller.
8038 o Minor features (tools):
8039 - Do not have tor-resolve automatically refuse all .onion addresses;
8040 if AutomapHostsOnResolve is set in your torrc, this will work fine.
8041 - Add a -p option to tor-resolve for specifying the SOCKS port: some
8042 people find host:port too confusing.
8043 - Print the SOCKS5 error message string as well as the error code
8044 when a tor-resolve request fails. Patch from Jacob.
8046 o Minor bugfixes (memory and resource management):
8047 - Clients no longer cache certificates for authorities they do not
8048 recognize. Bugfix on 0.2.0.9-alpha.
8049 - Do not use C's stdio library for writing to log files. This will
8050 improve logging performance by a minute amount, and will stop
8051 leaking fds when our disk is full. Fixes bug 861.
8052 - Stop erroneous use of O_APPEND in cases where we did not in fact
8053 want to re-seek to the end of a file before every last write().
8054 - Fix a small alignment and memory-wasting bug on buffer chunks.
8056 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
8057 to avoid unused RAM in buffer chunks and memory pools.
8058 - Reduce the default smartlist size from 32 to 16; it turns out that
8059 most smartlists hold around 8-12 elements tops.
8060 - Make dumpstats() log the fullness and size of openssl-internal
8062 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
8063 patch to their OpenSSL, turn it on to save memory on servers. This
8064 patch will (with any luck) get included in a mainline distribution
8066 - Fix a memory leak when v3 directory authorities load their keys
8067 and cert from disk. Bugfix on 0.2.0.1-alpha.
8068 - Stop using malloc_usable_size() to use more area than we had
8069 actually allocated: it was safe, but made valgrind really unhappy.
8070 - Make the assert_circuit_ok() function work correctly on circuits that
8071 have already been marked for close.
8072 - Fix uninitialized size field for memory area allocation: may improve
8073 memory performance during directory parsing.
8075 o Minor bugfixes (clients):
8076 - Stop reloading the router list from disk for no reason when we
8077 run out of reachable directory mirrors. Once upon a time reloading
8078 it would set the 'is_running' flag back to 1 for them. It hasn't
8079 done that for a long time.
8080 - When we had picked an exit node for a connection, but marked it as
8081 "optional", and it turned out we had no onion key for the exit,
8082 stop wanting that exit and try again. This situation may not
8083 be possible now, but will probably become feasible with proposal
8084 158. Spotted by rovv. Fixes another case of bug 752.
8085 - Fix a bug in address parsing that was preventing bridges or hidden
8086 service targets from being at IPv6 addresses.
8087 - Do not remove routers as too old if we do not have any consensus
8088 document. Bugfix on 0.2.0.7-alpha.
8089 - When an exit relay resolves a stream address to a local IP address,
8090 do not just keep retrying that same exit relay over and
8091 over. Instead, just close the stream. Addresses bug 872. Bugfix
8092 on 0.2.0.32. Patch from rovv.
8093 - Made Tor a little less aggressive about deleting expired
8094 certificates. Partial fix for bug 854.
8095 - Treat duplicate certificate fetches as failures, so that we do
8096 not try to re-fetch an expired certificate over and over and over.
8097 - Do not say we're fetching a certificate when we'll in fact skip it
8098 because of a pending download.
8099 - If we have correct permissions on $datadir, we complain to stdout
8100 and fail to start. But dangerous permissions on
8101 $datadir/cached-status/ would cause us to open a log and complain
8102 there. Now complain to stdout and fail to start in both cases. Fixes
8103 bug 820, reported by seeess.
8105 o Minor bugfixes (bridges):
8106 - When we made bridge authorities stop serving bridge descriptors over
8107 unencrypted links, we also broke DirPort reachability testing for
8108 bridges. So bridges with a non-zero DirPort were printing spurious
8109 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
8110 - Don't allow a bridge to publish its router descriptor to a
8111 non-bridge directory authority. Fixes part of bug 932.
8112 - When we change to or from being a bridge, reset our counts of
8113 client usage by country. Fixes bug 932.
8115 o Minor bugfixes (relays):
8116 - Log correct error messages for DNS-related network errors on
8118 - Actually return -1 in the error case for read_bandwidth_usage().
8119 Harmless bug, since we currently don't care about the return value
8120 anywhere. Bugfix on 0.2.0.9-alpha.
8121 - Provide a more useful log message if bug 977 (related to buffer
8122 freelists) ever reappears, and do not crash right away.
8123 - We were already rejecting relay begin cells with destination port
8124 of 0. Now also reject extend cells with destination port or address
8125 of 0. Suggested by lark.
8126 - When we can't transmit a DNS request due to a network error, retry
8127 it after a while, and eventually transmit a failing response to
8128 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
8129 - Solve a bug that kept hardware crypto acceleration from getting
8130 enabled when accounting was turned on. Fixes bug 907. Bugfix on
8132 - When a canonical connection appears later in our internal list
8133 than a noncanonical one for a given OR ID, always use the
8134 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
8136 - Avoid some nasty corner cases in the logic for marking connections
8137 as too old or obsolete or noncanonical for circuits. Partial
8139 - Fix another interesting corner-case of bug 891 spotted by rovv:
8140 Previously, if two hosts had different amounts of clock drift, and
8141 one of them created a new connection with just the wrong timing,
8142 the other might decide to deprecate the new connection erroneously.
8143 Bugfix on 0.1.1.13-alpha.
8144 - If one win32 nameserver fails to get added, continue adding the
8145 rest, and don't automatically fail.
8146 - Fix a bug where an unreachable relay would establish enough
8147 reachability testing circuits to do a bandwidth test -- if
8148 we already have a connection to the middle hop of the testing
8149 circuit, then it could establish the last hop by using the existing
8150 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
8151 circuits no longer use entry guards in 0.2.1.3-alpha.
8153 o Minor bugfixes (directory authorities):
8154 - Limit uploaded directory documents to be 16M rather than 500K.
8155 The directory authorities were refusing v3 consensus votes from
8156 other authorities, since the votes are now 504K. Fixes bug 959;
8157 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
8158 - Directory authorities should never send a 503 "busy" response to
8159 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
8161 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
8162 headers. Bugfix on 0.2.0.10-alpha.
8164 o Minor bugfixes (hidden services):
8165 - When we can't find an intro key for a v2 hidden service descriptor,
8166 fall back to the v0 hidden service descriptor and log a bug message.
8167 Workaround for bug 1024.
8168 - In very rare situations new hidden service descriptors were
8169 published earlier than 30 seconds after the last change to the
8170 service. (We currently think that a hidden service descriptor
8171 that's been stable for 30 seconds is worth publishing.)
8172 - If a hidden service sends us an END cell, do not consider
8173 retrying the connection; just close it. Patch from rovv.
8174 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
8175 service directories if they have no advertised dir port. Bugfix
8178 o Minor bugfixes (tools):
8179 - In the torify(1) manpage, mention that tsocks will leak your
8182 o Minor bugfixes (controllers):
8183 - If the controller claimed responsibility for a stream, but that
8184 stream never finished making its connection, it would live
8185 forever in circuit_wait state. Now we close it after SocksTimeout
8186 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
8187 - Make DNS resolved controller events into "CLOSED", not
8188 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
8190 - The control port would close the connection before flushing long
8191 replies, such as the network consensus, if a QUIT command was issued
8192 before the reply had completed. Now, the control port flushes all
8193 pending replies before closing the connection. Also fix a spurious
8194 warning when a QUIT command is issued after a malformed or rejected
8195 AUTHENTICATE command, but before the connection was closed. Patch
8196 by Marcus Griep. Fixes bugs 1015 and 1016.
8197 - Fix a bug that made stream bandwidth get misreported to the
8200 o Deprecated and removed features:
8201 - The old "tor --version --version" command, which would print out
8202 the subversion "Id" of most of the source files, is now removed. It
8203 turned out to be less useful than we'd expected, and harder to
8205 - RedirectExits has been removed. It was deprecated since
8207 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
8208 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
8209 - Cell pools are now always enabled; --disable-cell-pools is ignored.
8210 - Directory mirrors no longer fetch the v1 directory or
8211 running-routers files. They are obsolete, and nobody asks for them
8212 anymore. This is the first step to making v1 authorities obsolete.
8213 - Take out the TestVia config option, since it was a workaround for
8214 a bug that was fixed in Tor 0.1.1.21.
8215 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
8216 HiddenServiceExcludeNodes as obsolete: they never worked properly,
8217 and nobody seems to be using them. Fixes bug 754. Bugfix on
8218 0.1.0.1-rc. Patch from Christian Wilms.
8219 - Remove all backward-compatibility code for relays running
8220 versions of Tor so old that they no longer work at all on the
8223 o Code simplifications and refactoring:
8224 - Tool-assisted documentation cleanup. Nearly every function or
8225 static variable in Tor should have its own documentation now.
8226 - Rename the confusing or_is_obsolete field to the more appropriate
8227 is_bad_for_new_circs, and move it to or_connection_t where it
8229 - Move edge-only flags from connection_t to edge_connection_t: not
8230 only is this better coding, but on machines of plausible alignment,
8231 it should save 4-8 bytes per connection_t. "Every little bit helps."
8232 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
8233 for consistency; keep old option working for backward compatibility.
8234 - Simplify the code for finding connections to use for a circuit.
8235 - Revise the connection_new functions so that a more typesafe variant
8236 exists. This will work better with Coverity, and let us find any
8237 actual mistakes we're making here.
8238 - Refactor unit testing logic so that dmalloc can be used sensibly
8239 with unit tests to check for memory leaks.
8240 - Move all hidden-service related fields from connection and circuit
8241 structure to substructures: this way they won't eat so much memory.
8242 - Squeeze 2-5% out of client performance (according to oprofile) by
8243 improving the implementation of some policy-manipulation functions.
8244 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
8245 be more efficient. Formerly it was quadratic in the number of
8246 servers; now it should be linear. Fixes bug 509.
8247 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
8248 and n_conn_id_digest fields into a separate structure that's
8249 only needed when the circuit has not yet attached to an n_conn.
8250 - Optimize out calls to time(NULL) that occur for every IO operation,
8251 or for every cell. On systems like Windows where time() is a
8252 slow syscall, this fix will be slightly helpful.
8255 Changes in version 0.2.0.35 - 2009-06-24
8257 - Avoid crashing in the presence of certain malformed descriptors.
8258 Found by lark, and by automated fuzzing.
8259 - Fix an edge case where a malicious exit relay could convince a
8260 controller that the client's DNS question resolves to an internal IP
8261 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
8264 - Finally fix the bug where dynamic-IP relays disappear when their
8265 IP address changes: directory mirrors were mistakenly telling
8266 them their old address if they asked via begin_dir, so they
8267 never got an accurate answer about their new address, so they
8268 just vanished after a day. For belt-and-suspenders, relays that
8269 don't set Address in their config now avoid using begin_dir for
8270 all direct connections. Should fix bugs 827, 883, and 900.
8271 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
8272 that would occur on some exit nodes when DNS failures and timeouts
8273 occurred in certain patterns. Fix for bug 957.
8276 - When starting with a cache over a few days old, do not leak
8277 memory for the obsolete router descriptors in it. Bugfix on
8278 0.2.0.33; fixes bug 672.
8279 - Hidden service clients didn't use a cached service descriptor that
8280 was older than 15 minutes, but wouldn't fetch a new one either,
8281 because there was already one in the cache. Now, fetch a v2
8282 descriptor unless the same descriptor was added to the cache within
8283 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
8286 Changes in version 0.2.0.34 - 2009-02-08
8287 Tor 0.2.0.34 features several more security-related fixes. You should
8288 upgrade, especially if you run an exit relay (remote crash) or a
8289 directory authority (remote infinite loop), or you're on an older
8290 (pre-XP) or not-recently-patched Windows (remote exploit).
8292 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
8293 have many known flaws, and nobody should be using them. You should
8294 upgrade. If you're using a Linux or BSD and its packages are obsolete,
8295 stop using those packages and upgrade anyway.
8298 - Fix an infinite-loop bug on handling corrupt votes under certain
8299 circumstances. Bugfix on 0.2.0.8-alpha.
8300 - Fix a temporary DoS vulnerability that could be performed by
8301 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
8302 - Avoid a potential crash on exit nodes when processing malformed
8303 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
8304 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
8305 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
8308 - Fix compilation on systems where time_t is a 64-bit integer.
8309 Patch from Matthias Drochner.
8310 - Don't consider expiring already-closed client connections. Fixes
8311 bug 893. Bugfix on 0.0.2pre20.
8314 Changes in version 0.2.0.33 - 2009-01-21
8315 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
8316 useful to users. It also finally fixes a bug where a relay or client
8317 that's been off for many days would take a long time to bootstrap.
8319 This update also fixes an important security-related bug reported by
8320 Ilja van Sprundel. You should upgrade. (We'll send out more details
8321 about the bug once people have had some time to upgrade.)
8324 - Fix a heap-corruption bug that may be remotely triggerable on
8325 some platforms. Reported by Ilja van Sprundel.
8328 - When a stream at an exit relay is in state "resolving" or
8329 "connecting" and it receives an "end" relay cell, the exit relay
8330 would silently ignore the end cell and not close the stream. If
8331 the client never closes the circuit, then the exit relay never
8332 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
8334 - When sending CREATED cells back for a given circuit, use a 64-bit
8335 connection ID to find the right connection, rather than an addr:port
8336 combination. Now that we can have multiple OR connections between
8337 the same ORs, it is no longer possible to use addr:port to uniquely
8338 identify a connection.
8339 - Bridge relays that had DirPort set to 0 would stop fetching
8340 descriptors shortly after startup, and then briefly resume
8341 after a new bandwidth test and/or after publishing a new bridge
8342 descriptor. Bridge users that try to bootstrap from them would
8343 get a recent networkstatus but would get descriptors from up to
8344 18 hours earlier, meaning most of the descriptors were obsolete
8345 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
8346 - Prevent bridge relays from serving their 'extrainfo' document
8347 to anybody who asks, now that extrainfo docs include potentially
8348 sensitive aggregated client geoip summaries. Bugfix on
8350 - If the cached networkstatus consensus is more than five days old,
8351 discard it rather than trying to use it. In theory it could be
8352 useful because it lists alternate directory mirrors, but in practice
8353 it just means we spend many minutes trying directory mirrors that
8354 are long gone from the network. Also discard router descriptors as
8355 we load them if they are more than five days old, since the onion
8356 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
8359 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
8360 could make gcc generate non-functional binary search code. Bugfix
8362 - Build correctly on platforms without socklen_t.
8363 - Compile without warnings on solaris.
8364 - Avoid potential crash on internal error during signature collection.
8365 Fixes bug 864. Patch from rovv.
8366 - Correct handling of possible malformed authority signing key
8367 certificates with internal signature types. Fixes bug 880.
8368 Bugfix on 0.2.0.3-alpha.
8369 - Fix a hard-to-trigger resource leak when logging credential status.
8371 - When we can't initialize DNS because the network is down, do not
8372 automatically stop Tor from starting. Instead, we retry failed
8373 dns_init() every 10 minutes, and change the exit policy to reject
8374 *:* until one succeeds. Fixes bug 691.
8375 - Use 64 bits instead of 32 bits for connection identifiers used with
8376 the controller protocol, to greatly reduce risk of identifier reuse.
8377 - When we're choosing an exit node for a circuit, and we have
8378 no pending streams, choose a good general exit rather than one that
8379 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
8380 - Fix another case of assuming, when a specific exit is requested,
8381 that we know more than the user about what hosts it allows.
8382 Fixes one case of bug 752. Patch from rovv.
8383 - Clip the MaxCircuitDirtiness config option to a minimum of 10
8384 seconds. Warn the user if lower values are given in the
8385 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
8386 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
8387 user if lower values are given in the configuration. Bugfix on
8388 0.1.1.17-rc. Patch by Sebastian.
8389 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
8390 the cache because we already had a v0 descriptor with the same ID.
8391 Bugfix on 0.2.0.18-alpha.
8392 - Fix a race condition when freeing keys shared between main thread
8393 and CPU workers that could result in a memory leak. Bugfix on
8394 0.1.0.1-rc. Fixes bug 889.
8395 - Send a valid END cell back when a client tries to connect to a
8396 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
8397 840. Patch from rovv.
8398 - Check which hops rendezvous stream cells are associated with to
8399 prevent possible guess-the-streamid injection attacks from
8400 intermediate hops. Fixes another case of bug 446. Based on patch
8402 - If a broken client asks a non-exit router to connect somewhere,
8403 do not even do the DNS lookup before rejecting the connection.
8404 Fixes another case of bug 619. Patch from rovv.
8405 - When a relay gets a create cell it can't decrypt (e.g. because it's
8406 using the wrong onion key), we were dropping it and letting the
8407 client time out. Now actually answer with a destroy cell. Fixes
8408 bug 904. Bugfix on 0.0.2pre8.
8410 o Minor bugfixes (hidden services):
8411 - Do not throw away existing introduction points on SIGHUP. Bugfix on
8412 0.0.6pre1. Patch by Karsten. Fixes bug 874.
8415 - Report the case where all signatures in a detached set are rejected
8416 differently than the case where there is an error handling the
8418 - When we realize that another process has modified our cached
8419 descriptors, print out a more useful error message rather than
8420 triggering an assertion. Fixes bug 885. Patch from Karsten.
8421 - Implement the 0x20 hack to better resist DNS poisoning: set the
8422 case on outgoing DNS requests randomly, and reject responses that do
8423 not match the case correctly. This logic can be disabled with the
8424 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
8425 of servers that do not reliably preserve case in replies. See
8426 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
8428 - Check DNS replies for more matching fields to better resist DNS
8430 - Never use OpenSSL compression: it wastes RAM and CPU trying to
8431 compress cells, which are basically all encrypted, compressed, or
8435 Changes in version 0.2.0.32 - 2008-11-20
8436 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
8437 packages (and maybe other packages) noticed by Theo de Raadt, fixes
8438 a smaller security flaw that might allow an attacker to access local
8439 services, further improves hidden service performance, and fixes a
8440 variety of other issues.
8443 - The "User" and "Group" config options did not clear the
8444 supplementary group entries for the Tor process. The "User" option
8445 is now more robust, and we now set the groups to the specified
8446 user's primary group. The "Group" option is now ignored. For more
8447 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
8448 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
8449 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
8450 - The "ClientDNSRejectInternalAddresses" config option wasn't being
8451 consistently obeyed: if an exit relay refuses a stream because its
8452 exit policy doesn't allow it, we would remember what IP address
8453 the relay said the destination address resolves to, even if it's
8454 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
8457 - Fix a DOS opportunity during the voting signature collection process
8458 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
8460 o Major bugfixes (hidden services):
8461 - When fetching v0 and v2 rendezvous service descriptors in parallel,
8462 we were failing the whole hidden service request when the v0
8463 descriptor fetch fails, even if the v2 fetch is still pending and
8464 might succeed. Similarly, if the last v2 fetch fails, we were
8465 failing the whole hidden service request even if a v0 fetch is
8466 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
8467 - When extending a circuit to a hidden service directory to upload a
8468 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
8469 requests failed, because the router descriptor has not been
8470 downloaded yet. In these cases, do not attempt to upload the
8471 rendezvous descriptor, but wait until the router descriptor is
8472 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
8473 descriptor from a hidden service directory for which the router
8474 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
8478 - Fix several infrequent memory leaks spotted by Coverity.
8479 - When testing for libevent functions, set the LDFLAGS variable
8480 correctly. Found by Riastradh.
8481 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
8482 bootstrapping with tunneled directory connections. Bugfix on
8483 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
8484 - When asked to connect to A.B.exit:80, if we don't know the IP for A
8485 and we know that server B rejects most-but-not all connections to
8486 port 80, we would previously reject the connection. Now, we assume
8487 the user knows what they were asking for. Fixes bug 752. Bugfix
8488 on 0.0.9rc5. Diagnosed by BarkerJr.
8489 - If we overrun our per-second write limits a little, count this as
8490 having used up our write allocation for the second, and choke
8491 outgoing directory writes. Previously, we had only counted this when
8492 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
8493 Bugfix on 0.2.0.x (??).
8494 - Remove the old v2 directory authority 'lefkada' from the default
8495 list. It has been gone for many months.
8496 - Stop doing unaligned memory access that generated bus errors on
8497 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
8498 - Make USR2 log-level switch take effect immediately. Bugfix on
8501 o Minor bugfixes (controller):
8502 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
8503 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
8506 Changes in version 0.2.0.31 - 2008-09-03
8507 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
8508 a big bug we're seeing where in rare cases traffic from one Tor stream
8509 gets mixed into another stream, and fixes a variety of smaller issues.
8512 - Make sure that two circuits can never exist on the same connection
8513 with the same circuit ID, even if one is marked for close. This
8514 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
8515 - Relays now reject risky extend cells: if the extend cell includes
8516 a digest of all zeroes, or asks to extend back to the relay that
8517 sent the extend cell, tear down the circuit. Ideas suggested
8519 - If not enough of our entry guards are available so we add a new
8520 one, we might use the new one even if it overlapped with the
8521 current circuit's exit relay (or its family). Anonymity bugfix
8522 pointed out by rovv.
8525 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
8526 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
8527 - Correctly detect the presence of the linux/netfilter_ipv4.h header
8528 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
8529 - Pick size of default geoip filename string correctly on windows.
8530 Fixes bug 806. Bugfix on 0.2.0.30.
8531 - Make the autoconf script accept the obsolete --with-ssl-dir
8532 option as an alias for the actually-working --with-openssl-dir
8533 option. Fix the help documentation to recommend --with-openssl-dir.
8534 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
8535 - When using the TransPort option on OpenBSD, and using the User
8536 option to change UID and drop privileges, make sure to open
8537 /dev/pf before dropping privileges. Fixes bug 782. Patch from
8538 Christopher Davis. Bugfix on 0.1.2.1-alpha.
8539 - Try to attach connections immediately upon receiving a RENDEZVOUS2
8540 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
8541 on the client side when connecting to a hidden service. Bugfix
8542 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
8543 - When closing an application-side connection because its circuit is
8544 getting torn down, generate the stream event correctly. Bugfix on
8545 0.1.2.x. Anonymous patch.
8548 Changes in version 0.2.0.30 - 2008-07-15
8549 This new stable release switches to a more efficient directory
8550 distribution design, adds features to make connections to the Tor
8551 network harder to block, allows Tor to act as a DNS proxy, adds separate
8552 rate limiting for relayed traffic to make it easier for clients to
8553 become relays, fixes a variety of potential anonymity problems, and
8554 includes the usual huge pile of other features and bug fixes.
8556 o New v3 directory design:
8557 - Tor now uses a new way to learn about and distribute information
8558 about the network: the directory authorities vote on a common
8559 network status document rather than each publishing their own
8560 opinion. Now clients and caches download only one networkstatus
8561 document to bootstrap, rather than downloading one for each
8562 authority. Clients only download router descriptors listed in
8563 the consensus. Implements proposal 101; see doc/spec/dir-spec.txt
8565 - Set up moria1, tor26, and dizum as v3 directory authorities
8566 in addition to being v2 authorities. Also add three new ones:
8567 ides (run by Mike Perry), gabelmoo (run by Karsten Loesing), and
8568 dannenberg (run by CCC).
8569 - Switch to multi-level keys for directory authorities: now their
8570 long-term identity key can be kept offline, and they periodically
8571 generate a new signing key. Clients fetch the "key certificates"
8572 to keep up to date on the right keys. Add a standalone tool
8573 "tor-gencert" to generate key certificates. Implements proposal 103.
8574 - Add a new V3AuthUseLegacyKey config option to make it easier for
8575 v3 authorities to change their identity keys if another bug like
8576 Debian's OpenSSL RNG flaw appears.
8577 - Authorities and caches fetch the v2 networkstatus documents
8578 less often, now that v3 is recommended.
8580 o Make Tor connections stand out less on the wire:
8581 - Use an improved TLS handshake designed by Steven Murdoch in proposal
8582 124, as revised in proposal 130. The new handshake is meant to
8583 be harder for censors to fingerprint, and it adds the ability
8584 to detect certain kinds of man-in-the-middle traffic analysis
8585 attacks. The new handshake format includes version negotiation for
8586 OR connections as described in proposal 105, which will allow us
8587 to improve Tor's link protocol more safely in the future.
8588 - Enable encrypted directory connections by default for non-relays,
8589 so censor tools that block Tor directory connections based on their
8590 plaintext patterns will no longer work. This means Tor works in
8591 certain censored countries by default again.
8592 - Stop including recognizeable strings in the commonname part of
8593 Tor's x509 certificates.
8595 o Implement bridge relays:
8596 - Bridge relays (or "bridges" for short) are Tor relays that aren't
8597 listed in the main Tor directory. Since there is no complete public
8598 list of them, even an ISP that is filtering connections to all the
8599 known Tor relays probably won't be able to block all the bridges.
8600 See doc/design-paper/blocking.pdf and proposal 125 for details.
8601 - New config option BridgeRelay that specifies you want to be a
8602 bridge relay rather than a normal relay. When BridgeRelay is set
8603 to 1, then a) you cache dir info even if your DirPort ins't on,
8604 and b) the default for PublishServerDescriptor is now "bridge"
8605 rather than "v2,v3".
8606 - New config option "UseBridges 1" for clients that want to use bridge
8607 relays instead of ordinary entry guards. Clients then specify
8608 bridge relays by adding "Bridge" lines to their config file. Users
8609 can learn about a bridge relay either manually through word of
8610 mouth, or by one of our rate-limited mechanisms for giving out
8611 bridge addresses without letting an attacker easily enumerate them
8612 all. See https://www.torproject.org/bridges for details.
8613 - Bridge relays behave like clients with respect to time intervals
8614 for downloading new v3 consensus documents -- otherwise they
8615 stand out. Bridge users now wait until the end of the interval,
8616 so their bridge relay will be sure to have a new consensus document.
8618 o Implement bridge directory authorities:
8619 - Bridge authorities are like normal directory authorities, except
8620 they don't serve a list of known bridges. Therefore users that know
8621 a bridge's fingerprint can fetch a relay descriptor for that bridge,
8622 including fetching updates e.g. if the bridge changes IP address,
8623 yet an attacker can't just fetch a list of all the bridges.
8624 - Set up Tonga as the default bridge directory authority.
8625 - Bridge authorities refuse to serve bridge descriptors or other
8626 bridge information over unencrypted connections (that is, when
8627 responding to direct DirPort requests rather than begin_dir cells.)
8628 - Bridge directory authorities do reachability testing on the
8629 bridges they know. They provide router status summaries to the
8630 controller via "getinfo ns/purpose/bridge", and also dump summaries
8631 to a file periodically, so we can keep internal stats about which
8632 bridges are functioning.
8633 - If bridge users set the UpdateBridgesFromAuthority config option,
8634 but the digest they ask for is a 404 on the bridge authority,
8635 they fall back to contacting the bridge directly.
8636 - Bridges always use begin_dir to publish their server descriptor to
8637 the bridge authority using an anonymous encrypted tunnel.
8638 - Early work on a "bridge community" design: if bridge authorities set
8639 the BridgePassword config option, they will serve a snapshot of
8640 known bridge routerstatuses from their DirPort to anybody who
8641 knows that password. Unset by default.
8642 - Tor now includes an IP-to-country GeoIP file, so bridge relays can
8643 report sanitized aggregated summaries in their extra-info documents
8644 privately to the bridge authority, listing which countries are
8645 able to reach them. We hope this mechanism will let us learn when
8646 certain countries start trying to block bridges.
8647 - Bridge authorities write bridge descriptors to disk, so they can
8648 reload them after a reboot. They can also export the descriptors
8649 to other programs, so we can distribute them to blocked users via
8650 the BridgeDB interface, e.g. via https://bridges.torproject.org/
8651 and bridges@torproject.org.
8653 o Tor can be a DNS proxy:
8654 - The new client-side DNS proxy feature replaces the need for
8655 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
8656 for DNS requests on port 9999, use the Tor network to resolve them
8657 anonymously, and send the reply back like a regular DNS server.
8658 The code still only implements a subset of DNS.
8659 - Add a new AutomapHostsOnResolve option: when it is enabled, any
8660 resolve request for hosts matching a given pattern causes Tor to
8661 generate an internal virtual address mapping for that host. This
8662 allows DNSPort to work sensibly with hidden service users. By
8663 default, .exit and .onion addresses are remapped; the list of
8664 patterns can be reconfigured with AutomapHostsSuffixes.
8665 - Add an "-F" option to tor-resolve to force a resolve for a .onion
8666 address. Thanks to the AutomapHostsOnResolve option, this is no
8667 longer a completely silly thing to do.
8669 o Major features (relay usability):
8670 - New config options RelayBandwidthRate and RelayBandwidthBurst:
8671 a separate set of token buckets for relayed traffic. Right now
8672 relayed traffic is defined as answers to directory requests, and
8673 OR connections that don't have any local circuits on them. See
8674 proposal 111 for details.
8675 - Create listener connections before we setuid to the configured
8676 User and Group. Now non-Windows users can choose port values
8677 under 1024, start Tor as root, and have Tor bind those ports
8678 before it changes to another UID. (Windows users could already
8680 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
8681 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
8682 on "vserver" accounts. Patch from coderman.
8684 o Major features (directory authorities):
8685 - Directory authorities track weighted fractional uptime and weighted
8686 mean-time-between failures for relays. WFU is suitable for deciding
8687 whether a node is "usually up", while MTBF is suitable for deciding
8688 whether a node is "likely to stay up." We need both, because
8689 "usually up" is a good requirement for guards, while "likely to
8690 stay up" is a good requirement for long-lived connections.
8691 - Directory authorities use a new formula for selecting which relays
8692 to advertise as Guards: they must be in the top 7/8 in terms of
8693 how long we have known about them, and above the median of those
8694 nodes in terms of weighted fractional uptime.
8695 - Directory authorities use a new formula for selecting which relays
8696 to advertise as Stable: when we have 4 or more days of data, use
8697 median measured MTBF rather than median declared uptime. Implements
8699 - Directory authorities accept and serve "extra info" documents for
8700 routers. Routers now publish their bandwidth-history lines in the
8701 extra-info docs rather than the main descriptor. This step saves
8702 60% (!) on compressed router descriptor downloads. Servers upload
8703 extra-info docs to any authority that accepts them; directory
8704 authorities now allow multiple router descriptors and/or extra
8705 info documents to be uploaded in a single go. Authorities, and
8706 caches that have been configured to download extra-info documents,
8707 download them as needed. Implements proposal 104.
8708 - Authorities now list relays who have the same nickname as
8709 a different named relay, but list them with a new flag:
8710 "Unnamed". Now we can make use of relays that happen to pick the
8711 same nickname as a server that registered two years ago and then
8712 disappeared. Implements proposal 122.
8713 - Store routers in a file called cached-descriptors instead of in
8714 cached-routers. Initialize cached-descriptors from cached-routers
8715 if the old format is around. The new format allows us to store
8716 annotations along with descriptors, to record the time we received
8717 each descriptor, its source, and its purpose: currently one of
8718 general, controller, or bridge.
8720 o Major features (other):
8721 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
8722 Tor can warn and/or refuse connections to ports commonly used with
8723 vulnerable-plaintext protocols. Currently we warn on ports 23,
8724 109, 110, and 143, but we don't reject any. Based on proposal 129
8725 by Kevin Bauer and Damon McCoy.
8726 - Integrate Karsten Loesing's Google Summer of Code project to publish
8727 hidden service descriptors on a set of redundant relays that are a
8728 function of the hidden service address. Now we don't have to rely
8729 on three central hidden service authorities for publishing and
8730 fetching every hidden service descriptor. Implements proposal 114.
8731 - Allow tunnelled directory connections to ask for an encrypted
8732 "begin_dir" connection or an anonymized "uses a full Tor circuit"
8733 connection independently. Now we can make anonymized begin_dir
8734 connections for (e.g.) more secure hidden service posting and
8737 o Major bugfixes (crashes and assert failures):
8738 - Stop imposing an arbitrary maximum on the number of file descriptors
8739 used for busy servers. Bug reported by Olaf Selke; patch from
8741 - Avoid possible failures when generating a directory with routers
8742 with over-long versions strings, or too many flags set.
8743 - Fix a rare assert error when we're closing one of our threads:
8744 use a mutex to protect the list of logs, so we never write to the
8745 list as it's being freed. Fixes the very rare bug 575, which is
8746 kind of the revenge of bug 222.
8747 - Avoid segfault in the case where a badly behaved v2 versioning
8748 directory sends a signed networkstatus with missing client-versions.
8749 - When we hit an EOF on a log (probably because we're shutting down),
8750 don't try to remove the log from the list: just mark it as
8751 unusable. (Bulletproofs against bug 222.)
8753 o Major bugfixes (code security fixes):
8754 - Detect size overflow in zlib code. Reported by Justin Ferguson and
8756 - Rewrite directory tokenization code to never run off the end of
8757 a string. Fixes bug 455. Patch from croup.
8758 - Be more paranoid about overwriting sensitive memory on free(),
8759 as a defensive programming tactic to ensure forward secrecy.
8761 o Major bugfixes (anonymity fixes):
8762 - Reject requests for reverse-dns lookup of names that are in
8763 a private address space. Patch from lodger.
8764 - Never report that we've used more bandwidth than we're willing to
8765 relay: it leaks how much non-relay traffic we're using. Resolves
8767 - As a client, do not believe any server that tells us that an
8768 address maps to an internal address space.
8769 - Warn about unsafe ControlPort configurations.
8770 - Directory authorities now call routers Fast if their bandwidth is
8771 at least 100KB/s, and consider their bandwidth adequate to be a
8772 Guard if it is at least 250KB/s, no matter the medians. This fix
8773 complements proposal 107.
8774 - Directory authorities now never mark more than 2 servers per IP as
8775 Valid and Running (or 5 on addresses shared by authorities).
8776 Implements proposal 109, by Kevin Bauer and Damon McCoy.
8777 - If we're a relay, avoid picking ourselves as an introduction point,
8778 a rendezvous point, or as the final hop for internal circuits. Bug
8779 reported by taranis and lodger.
8780 - Exit relays that are used as a client can now reach themselves
8781 using the .exit notation, rather than just launching an infinite
8782 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
8783 - Fix a bug where, when we were choosing the 'end stream reason' to
8784 put in our relay end cell that we send to the exit relay, Tor
8785 clients on Windows were sometimes sending the wrong 'reason'. The
8786 anonymity problem is that exit relays may be able to guess whether
8787 the client is running Windows, thus helping partition the anonymity
8788 set. Down the road we should stop sending reasons to exit relays,
8789 or otherwise prevent future versions of this bug.
8790 - Only update guard status (usable / not usable) once we have
8791 enough directory information. This was causing us to discard all our
8792 guards on startup if we hadn't been running for a few weeks. Fixes
8794 - When our directory information has been expired for a while, stop
8795 being willing to build circuits using it. Fixes bug 401.
8797 o Major bugfixes (peace of mind for relay operators)
8798 - Non-exit relays no longer answer "resolve" relay cells, so they
8799 can't be induced to do arbitrary DNS requests. (Tor clients already
8800 avoid using non-exit relays for resolve cells, but now servers
8801 enforce this too.) Fixes bug 619. Patch from lodger.
8802 - When we setconf ClientOnly to 1, close any current OR and Dir
8803 listeners. Reported by mwenge.
8805 o Major bugfixes (other):
8806 - If we only ever used Tor for hidden service lookups or posts, we
8807 would stop building circuits and start refusing connections after
8808 24 hours, since we falsely believed that Tor was dormant. Reported
8810 - Add a new __HashedControlSessionPassword option for controllers
8811 to use for one-off session password hashes that shouldn't get
8812 saved to disk by SAVECONF --- Vidalia users were accumulating a
8813 pile of HashedControlPassword lines in their torrc files, one for
8814 each time they had restarted Tor and then clicked Save. Make Tor
8815 automatically convert "HashedControlPassword" to this new option but
8816 only when it's given on the command line. Partial fix for bug 586.
8817 - Patch from "Andrew S. Lists" to catch when we contact a directory
8818 mirror at IP address X and he says we look like we're coming from
8819 IP address X. Otherwise this would screw up our address detection.
8820 - Reject uploaded descriptors and extrainfo documents if they're
8821 huge. Otherwise we'll cache them all over the network and it'll
8822 clog everything up. Suggested by Aljosha Judmayer.
8823 - When a hidden service was trying to establish an introduction point,
8824 and Tor *did* manage to reuse one of the preemptively built
8825 circuits, it didn't correctly remember which one it used,
8826 so it asked for another one soon after, until there were no
8827 more preemptive circuits, at which point it launched one from
8828 scratch. Bugfix on 0.0.9.x.
8830 o Rate limiting and load balancing improvements:
8831 - When we add data to a write buffer in response to the data on that
8832 write buffer getting low because of a flush, do not consider the
8833 newly added data as a candidate for immediate flushing, but rather
8834 make it wait until the next round of writing. Otherwise, we flush
8835 and refill recursively, and a single greedy TLS connection can
8836 eat all of our bandwidth.
8837 - When counting the number of bytes written on a TLS connection,
8838 look at the BIO actually used for writing to the network, not
8839 at the BIO used (sometimes) to buffer data for the network.
8840 Looking at different BIOs could result in write counts on the
8841 order of ULONG_MAX. Fixes bug 614.
8842 - If we change our MaxAdvertisedBandwidth and then reload torrc,
8843 Tor won't realize it should publish a new relay descriptor. Fixes
8844 bug 688, reported by mfr.
8845 - Avoid using too little bandwidth when our clock skips a few seconds.
8846 - Choose which bridge to use proportional to its advertised bandwidth,
8847 rather than uniformly at random. This should speed up Tor for
8848 bridge users. Also do this for people who set StrictEntryNodes.
8850 o Bootstrapping faster and building circuits more intelligently:
8851 - Fix bug 660 that was preventing us from knowing that we should
8852 preemptively build circuits to handle expected directory requests.
8853 - When we're checking if we have enough dir info for each relay
8854 to begin establishing circuits, make sure that we actually have
8855 the descriptor listed in the consensus, not just any descriptor.
8856 - Correctly notify one-hop connections when a circuit build has
8857 failed. Possible fix for bug 669. Found by lodger.
8858 - Clients now hold circuitless TLS connections open for 1.5 times
8859 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
8860 rebuild a new circuit over them within that timeframe. Previously,
8861 they held them open only for KeepalivePeriod (5 minutes).
8863 o Performance improvements (memory):
8864 - Add OpenBSD malloc code from "phk" as an optional malloc
8865 replacement on Linux: some glibc libraries do very poorly with
8866 Tor's memory allocation patterns. Pass --enable-openbsd-malloc to
8867 ./configure to get the replacement malloc code.
8868 - Switch our old ring buffer implementation for one more like that
8869 used by free Unix kernels. The wasted space in a buffer with 1mb
8870 of data will now be more like 8k than 1mb. The new implementation
8871 also avoids realloc();realloc(); patterns that can contribute to
8872 memory fragmentation.
8873 - Change the way that Tor buffers data that it is waiting to write.
8874 Instead of queueing data cells in an enormous ring buffer for each
8875 client->OR or OR->OR connection, we now queue cells on a separate
8876 queue for each circuit. This lets us use less slack memory, and
8877 will eventually let us be smarter about prioritizing different kinds
8879 - Reference-count and share copies of address policy entries; only 5%
8880 of them were actually distinct.
8881 - Tune parameters for cell pool allocation to minimize amount of
8883 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
8884 for every single inactive connection_t. Free items from the
8885 4k/16k-buffer free lists when they haven't been used for a while.
8886 - Make memory debugging information describe more about history
8887 of cell allocation, so we can help reduce our memory use.
8888 - Be even more aggressive about releasing RAM from small
8889 empty buffers. Thanks to our free-list code, this shouldn't be too
8890 performance-intensive.
8891 - Log malloc statistics from mallinfo() on platforms where it exists.
8892 - Use memory pools to allocate cells with better speed and memory
8893 efficiency, especially on platforms where malloc() is inefficient.
8894 - Add a --with-tcmalloc option to the configure script to link
8895 against tcmalloc (if present). Does not yet search for non-system
8898 o Performance improvements (socket management):
8899 - Count the number of open sockets separately from the number of
8900 active connection_t objects. This will let us avoid underusing
8901 our allocated connection limit.
8902 - We no longer use socket pairs to link an edge connection to an
8903 anonymous directory connection or a DirPort test connection.
8904 Instead, we track the link internally and transfer the data
8905 in-process. This saves two sockets per "linked" connection (at the
8906 client and at the server), and avoids the nasty Windows socketpair()
8908 - We were leaking a file descriptor if Tor started with a zero-length
8909 cached-descriptors file. Patch by "freddy77".
8911 o Performance improvements (CPU use):
8912 - Never walk through the list of logs if we know that no log target
8913 is interested in a given message.
8914 - Call routerlist_remove_old_routers() much less often. This should
8915 speed startup, especially on directory caches.
8916 - Base64 decoding was actually showing up on our profile when parsing
8917 the initial descriptor file; switch to an in-process all-at-once
8918 implementation that's about 3.5x times faster than calling out to
8920 - Use a slightly simpler string hashing algorithm (copying Python's
8921 instead of Java's) and optimize our digest hashing algorithm to take
8922 advantage of 64-bit platforms and to remove some possibly-costly
8924 - When implementing AES counter mode, update only the portions of the
8925 counter buffer that need to change, and don't keep separate
8926 network-order and host-order counters on big-endian hosts (where
8928 - Add an in-place version of aes_crypt() so that we can avoid doing a
8929 needless memcpy() call on each cell payload.
8930 - Use Critical Sections rather than Mutexes for synchronizing threads
8931 on win32; Mutexes are heavier-weight, and designed for synchronizing
8934 o Performance improvements (bandwidth use):
8935 - Don't try to launch new descriptor downloads quite so often when we
8936 already have enough directory information to build circuits.
8937 - Version 1 directories are no longer generated in full. Instead,
8938 authorities generate and serve "stub" v1 directories that list
8939 no servers. This will stop Tor versions 0.1.0.x and earlier from
8940 working, but (for security reasons) nobody should be running those
8942 - Avoid going directly to the directory authorities even if you're a
8943 relay, if you haven't found yourself reachable yet or if you've
8944 decided not to advertise your dirport yet. Addresses bug 556.
8945 - If we've gone 12 hours since our last bandwidth check, and we
8946 estimate we have less than 50KB bandwidth capacity but we could
8947 handle more, do another bandwidth test.
8948 - Support "If-Modified-Since" when answering HTTP requests for
8949 directories, running-routers documents, and v2 and v3 networkstatus
8950 documents. (There's no need to support it for router descriptors,
8951 since those are downloaded by descriptor digest.)
8952 - Stop fetching directory info so aggressively if your DirPort is
8953 on but your ORPort is off; stop fetching v2 dir info entirely.
8954 You can override these choices with the new FetchDirInfoEarly
8957 o Changed config option behavior (features):
8958 - Configuration files now accept C-style strings as values. This
8959 helps encode characters not allowed in the current configuration
8960 file format, such as newline or #. Addresses bug 557.
8961 - Add hidden services and DNSPorts to the list of things that make
8962 Tor accept that it has running ports. Change starting Tor with no
8963 ports from a fatal error to a warning; we might change it back if
8964 this turns out to confuse anybody. Fixes bug 579.
8965 - Make PublishServerDescriptor default to 1, so the default doesn't
8966 have to change as we invent new directory protocol versions.
8967 - Allow people to say PreferTunnelledDirConns rather than
8968 PreferTunneledDirConns, for those alternate-spellers out there.
8969 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
8970 accommodate the growing number of servers that use the default
8971 and are reaching it.
8972 - Make it possible to enable HashedControlPassword and
8973 CookieAuthentication at the same time.
8974 - When a TrackHostExits-chosen exit fails too many times in a row,
8975 stop using it. Fixes bug 437.
8977 o Changed config option behavior (bugfixes):
8978 - Do not read the configuration file when we've only been told to
8979 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
8980 based on patch from Sebastian Hahn.
8981 - Actually validate the options passed to AuthDirReject,
8982 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
8983 - Make "ClientOnly 1" config option disable directory ports too.
8984 - Don't stop fetching descriptors when FetchUselessDescriptors is
8985 set, even if we stop asking for circuits. Bug reported by tup
8987 - Servers used to decline to publish their DirPort if their
8988 BandwidthRate or MaxAdvertisedBandwidth were below a threshold. Now
8989 they look only at BandwidthRate and RelayBandwidthRate.
8990 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
8991 minus 1 byte: the actual maximum declared bandwidth.
8992 - Make "TrackHostExits ." actually work. Bugfix on 0.1.0.x.
8993 - Make the NodeFamilies config option work. (Reported by
8994 lodger -- it has never actually worked, even though we added it
8996 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
8997 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
8999 o New config options:
9000 - New configuration options AuthDirMaxServersPerAddr and
9001 AuthDirMaxServersperAuthAddr to override default maximum number
9002 of servers allowed on a single IP address. This is important for
9003 running a test network on a single host.
9004 - Three new config options (AlternateDirAuthority,
9005 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
9006 user selectively replace the default directory authorities by type,
9007 rather than the all-or-nothing replacement that DirServer offers.
9008 - New config options AuthDirBadDir and AuthDirListBadDirs for
9009 authorities to mark certain relays as "bad directories" in the
9010 networkstatus documents. Also supports the "!baddir" directive in
9011 the approved-routers file.
9012 - New config option V2AuthoritativeDirectory that all v2 directory
9013 authorities must set. This lets v3 authorities choose not to serve
9014 v2 directory information.
9016 o Minor features (other):
9017 - When we're not serving v2 directory information, there is no reason
9018 to actually keep any around. Remove the obsolete files and directory
9019 on startup if they are very old and we aren't going to serve them.
9020 - When we negotiate a v2 link-layer connection (not yet implemented),
9021 accept RELAY_EARLY cells and turn them into RELAY cells if we've
9022 negotiated a v1 connection for their next step. Initial steps for
9024 - When we have no consensus, check FallbackNetworkstatusFile (defaults
9025 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
9026 we can start out knowing some directory caches. We don't ship with
9027 a fallback consensus by default though, because it was making
9028 bootstrapping take too long while we tried many down relays.
9029 - Authorities send back an X-Descriptor-Not-New header in response to
9030 an accepted-but-discarded descriptor upload. Partially implements
9032 - If we find a cached-routers file that's been sitting around for more
9033 than 28 days unmodified, then most likely it's a leftover from
9034 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
9036 - When we (as a cache) download a descriptor because it was listed
9037 in a consensus, remember when the consensus was supposed to expire,
9038 and don't expire the descriptor until then.
9039 - Optionally (if built with -DEXPORTMALLINFO) export the output
9040 of mallinfo via http, as tor/mallinfo.txt. Only accessible
9042 - Tag every guard node in our state file with the version that
9043 we believe added it, or with our own version if we add it. This way,
9044 if a user temporarily runs an old version of Tor and then switches
9045 back to a new one, she doesn't automatically lose her guards.
9046 - When somebody requests a list of statuses or servers, and we have
9047 none of those, return a 404 rather than an empty 200.
9048 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
9050 - Add an HSAuthorityRecordStats option that hidden service authorities
9051 can use to track statistics of overall hidden service usage without
9052 logging information that would be as useful to an attacker.
9053 - Allow multiple HiddenServicePort directives with the same virtual
9054 port; when they occur, the user is sent round-robin to one
9055 of the target ports chosen at random. Partially fixes bug 393 by
9056 adding limited ad-hoc round-robining.
9057 - Revamp file-writing logic so we don't need to have the entire
9058 contents of a file in memory at once before we write to disk. Tor,
9061 o Minor bugfixes (other):
9062 - Alter the code that tries to recover from unhandled write
9063 errors, to not try to flush onto a socket that's given us
9065 - Directory mirrors no longer include a guess at the client's IP
9066 address if the connection appears to be coming from the same /24
9067 network; it was producing too many wrong guesses.
9068 - If we're trying to flush the last bytes on a connection (for
9069 example, when answering a directory request), reset the
9070 time-to-give-up timeout every time we manage to write something
9072 - Reject router descriptors with out-of-range bandwidthcapacity or
9073 bandwidthburst values.
9074 - If we can't expand our list of entry guards (e.g. because we're
9075 using bridges or we have StrictEntryNodes set), don't mark relays
9076 down when they fail a directory request. Otherwise we're too quick
9077 to mark all our entry points down.
9078 - Authorities no longer send back "400 you're unreachable please fix
9079 it" errors to Tor servers that aren't online all the time. We're
9080 supposed to tolerate these servers now.
9081 - Let directory authorities startup even when they can't generate
9082 a descriptor immediately, e.g. because they don't know their
9084 - Correctly enforce that elements of directory objects do not appear
9085 more often than they are allowed to appear.
9086 - Stop allowing hibernating servers to be "stable" or "fast".
9087 - On Windows, we were preventing other processes from reading
9088 cached-routers while Tor was running. (Reported by janbar)
9089 - Check return values from pthread_mutex functions.
9090 - When opening /dev/null in finish_daemonize(), do not pass the
9091 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
9092 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
9094 o Controller features:
9095 - The GETCONF command now escapes and quotes configuration values
9096 that don't otherwise fit into the torrc file.
9097 - The SETCONF command now handles quoted values correctly.
9098 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
9099 ask about source, timestamp of arrival, purpose, etc. We need
9100 something like this to help Vidalia not do GeoIP lookups on bridge
9102 - Allow multiple HashedControlPassword config lines, to support
9103 multiple controller passwords.
9104 - Accept LF instead of CRLF on controller, since some software has a
9105 hard time generating real Internet newlines.
9106 - Add GETINFO values for the server status events
9107 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
9109 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
9110 GETINFO for Torstat to use until it can switch to using extrainfos.
9111 - New config option CookieAuthFile to choose a new location for the
9112 cookie authentication file, and config option
9113 CookieAuthFileGroupReadable to make it group-readable.
9114 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
9115 match requests to applications. Patch from Robert Hogan.
9116 - Add a RESOLVE command to launch hostname lookups. Original patch
9118 - Add GETINFO status/enough-dir-info to let controllers tell whether
9119 Tor has downloaded sufficient directory information. Patch from Tup.
9120 - You can now use the ControlSocket option to tell Tor to listen for
9121 controller connections on Unix domain sockets on systems that
9122 support them. Patch from Peter Palfrader.
9123 - New "GETINFO address-mappings/*" command to get address mappings
9124 with expiry information. "addr-mappings/*" is now deprecated.
9126 - Add a new config option __DisablePredictedCircuits designed for
9127 use by the controller, when we don't want Tor to build any circuits
9129 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
9130 so we can exit from the middle of the circuit.
9131 - Implement "getinfo status/circuit-established".
9132 - Implement "getinfo status/version/..." so a controller can tell
9133 whether the current version is recommended, and whether any versions
9134 are good, and how many authorities agree. Patch from "shibz".
9135 - Controllers should now specify cache=no or cache=yes when using
9136 the +POSTDESCRIPTOR command.
9137 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
9138 Robert Hogan. Fixes the first part of bug 681.
9139 - When reporting clock skew, and we know that the clock is _at least
9140 as skewed_ as some value, but we don't know the actual value,
9141 report the value as a "minimum skew."
9143 o Controller bugfixes:
9144 - Generate "STATUS_SERVER" events rather than misspelled
9145 "STATUS_SEVER" events. Caught by mwenge.
9146 - Reject controller commands over 1MB in length, so rogue
9147 processes can't run us out of memory.
9148 - Change the behavior of "getinfo status/good-server-descriptor"
9149 so it doesn't return failure when any authority disappears.
9150 - Send NAMESERVER_STATUS messages for a single failed nameserver
9152 - When the DANGEROUS_VERSION controller status event told us we're
9153 running an obsolete version, it used the string "OLD" to describe
9154 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
9155 "OBSOLETE" in both cases.
9156 - Respond to INT and TERM SIGNAL commands before we execute the
9157 signal, in case the signal shuts us down. We had a patch in
9158 0.1.2.1-alpha that tried to do this by queueing the response on
9159 the connection's buffer before shutting down, but that really
9160 isn't the same thing at all. Bug located by Matt Edman.
9161 - Provide DNS expiry times in GMT, not in local time. For backward
9162 compatibility, ADDRMAP events only provide GMT expiry in an extended
9163 field. "GETINFO address-mappings" always does the right thing.
9164 - Use CRLF line endings properly in NS events.
9165 - Make 'getinfo fingerprint' return a 551 error if we're not a
9166 server, so we match what the control spec claims we do. Reported
9168 - Fix a typo in an error message when extendcircuit fails that
9169 caused us to not follow the \r\n-based delimiter protocol. Reported
9171 - When tunneling an encrypted directory connection, and its first
9172 circuit fails, do not leave it unattached and ask the controller
9173 to deal. Fixes the second part of bug 681.
9174 - Treat some 403 responses from directory servers as INFO rather than
9175 WARN-severity events.
9177 o Portability / building / compiling:
9178 - When building with --enable-gcc-warnings, check for whether Apple's
9179 warning "-Wshorten-64-to-32" is available.
9180 - Support compilation to target iPhone; patch from cjacker huang.
9181 To build for iPhone, pass the --enable-iphone option to configure.
9182 - Port Tor to build and run correctly on Windows CE systems, using
9183 the wcecompat library. Contributed by Valerio Lupi.
9184 - Detect non-ASCII platforms (if any still exist) and refuse to
9185 build there: some of our code assumes that 'A' is 65 and so on.
9186 - Clear up some MIPSPro compiler warnings.
9187 - Make autoconf search for libevent, openssl, and zlib consistently.
9188 - Update deprecated macros in configure.in.
9189 - When warning about missing headers, tell the user to let us
9190 know if the compile succeeds anyway, so we can downgrade the
9192 - Include the current subversion revision as part of the version
9193 string: either fetch it directly if we're in an SVN checkout, do
9194 some magic to guess it if we're in an SVK checkout, or use
9195 the last-detected version if we're building from a .tar.gz.
9196 Use this version consistently in log messages.
9197 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
9198 - Read resolv.conf files correctly on platforms where read() returns
9199 partial results on small file reads.
9200 - Build without verbose warnings even on gcc 4.2 and 4.3.
9201 - On Windows, correctly detect errors when listing the contents of
9202 a directory. Fix from lodger.
9203 - Run 'make test' as part of 'make dist', so we stop releasing so
9204 many development snapshots that fail their unit tests.
9205 - Add support to detect Libevent versions in the 1.4.x series
9207 - Add command-line arguments to unit-test executable so that we can
9208 invoke any chosen test from the command line rather than having
9209 to run the whole test suite at once; and so that we can turn on
9210 logging for the unit tests.
9211 - Do not automatically run configure from autogen.sh. This
9212 non-standard behavior tended to annoy people who have built other
9214 - Fix a macro/CPP interaction that was confusing some compilers:
9215 some GCCs don't like #if/#endif pairs inside macro arguments.
9217 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
9218 Fixes bug 704; fix from Steven Murdoch.
9219 - Correctly detect transparent proxy support on Linux hosts that
9220 require in.h to be included before netfilter_ipv4.h. Patch
9223 o Logging improvements:
9224 - When we haven't had any application requests lately, don't bother
9225 logging that we have expired a bunch of descriptors.
9226 - When attempting to open a logfile fails, tell us why.
9227 - Only log guard node status when guard node status has changed.
9228 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
9229 make "INFO" 75% less verbose.
9230 - When SafeLogging is disabled, log addresses along with all TLS
9232 - Report TLS "zero return" case as a "clean close" and "IO error"
9233 as a "close". Stop calling closes "unexpected closes": existing
9234 Tors don't use SSL_close(), so having a connection close without
9235 the TLS shutdown handshake is hardly unexpected.
9236 - When we receive a consensus from the future, warn about skew.
9237 - Make "not enough dir info yet" warnings describe *why* Tor feels
9238 it doesn't have enough directory info yet.
9239 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
9240 consumers. (We already do this on HUP.)
9241 - Give more descriptive well-formedness errors for out-of-range
9242 hidden service descriptor/protocol versions.
9243 - Stop recommending that every server operator send mail to tor-ops.
9244 Resolves bug 597. Bugfix on 0.1.2.x.
9245 - Improve skew reporting: try to give the user a better log message
9246 about how skewed they are, and how much this matters.
9247 - New --quiet command-line option to suppress the default console log.
9248 Good in combination with --hash-password.
9249 - Don't complain that "your server has not managed to confirm that its
9250 ports are reachable" if we haven't been able to build any circuits
9252 - Detect the reason for failing to mmap a descriptor file we just
9253 wrote, and give a more useful log message. Fixes bug 533.
9254 - Always prepend "Bug: " to any log message about a bug.
9255 - When dumping memory usage, list bytes used in buffer memory
9257 - When running with dmalloc, dump more stats on hup and on exit.
9258 - Put a platform string (e.g. "Linux i686") in the startup log
9259 message, so when people paste just their logs, we know if it's
9260 OpenBSD or Windows or what.
9261 - When logging memory usage, break down memory used in buffers by
9263 - When we are reporting the DirServer line we just parsed, we were
9264 logging the second stanza of the key fingerprint, not the first.
9265 - Even though Windows is equally happy with / and \ as path separators,
9266 try to use \ consistently on Windows and / consistently on Unix: it
9267 makes the log messages nicer.
9268 - On OSX, stop warning the user that kqueue support in libevent is
9269 "experimental", since it seems to have worked fine for ages.
9271 o Contributed scripts and tools:
9272 - Update linux-tor-prio.sh script to allow QoS based on the uid of
9273 the Tor process. Patch from Marco Bonetti with tweaks from Mike
9275 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
9276 Unix users an easy way to script their Tor process (e.g. by
9277 adjusting bandwidth based on the time of the day).
9278 - In the exitlist script, only consider the most recently published
9279 server descriptor for each server. Also, when the user requests
9280 a list of servers that _reject_ connections to a given address,
9281 explicitly exclude the IPs that also have servers that accept
9282 connections to that address. Resolves bug 405.
9283 - Include a new contrib/tor-exit-notice.html file that exit relay
9284 operators can put on their website to help reduce abuse queries.
9286 o Newly deprecated features:
9287 - The status/version/num-versioning and status/version/num-concurring
9288 GETINFO controller options are no longer useful in the v3 directory
9289 protocol: treat them as deprecated, and warn when they're used.
9290 - The RedirectExits config option is now deprecated.
9293 - Drop the old code to choke directory connections when the
9294 corresponding OR connections got full: thanks to the cell queue
9295 feature, OR conns don't get full any more.
9296 - Remove the old "dns worker" server DNS code: it hasn't been default
9297 since 0.1.2.2-alpha, and all the servers are using the new
9299 - Remove the code to generate the oldest (v1) directory format.
9300 - Remove support for the old bw_accounting file: we've been storing
9301 bandwidth accounting information in the state file since
9302 0.1.2.5-alpha. This may result in bandwidth accounting errors
9303 if you try to upgrade from 0.1.1.x or earlier, or if you try to
9304 downgrade to 0.1.1.x or earlier.
9305 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
9306 it, it had no AES, and it hasn't seen any security patches since
9308 - Stop overloading the circuit_t.onionskin field for both "onionskin
9309 from a CREATE cell that we are waiting for a cpuworker to be
9310 assigned" and "onionskin from an EXTEND cell that we are going to
9311 send to an OR as soon as we are connected". Might help with bug 600.
9312 - Remove the tor_strpartition() function: its logic was confused,
9313 and it was only used for one thing that could be implemented far
9315 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
9316 and TorControl.py, as they use the old v0 controller protocol,
9317 and are obsoleted by TorFlow anyway.
9318 - Drop support for v1 rendezvous descriptors, since we never used
9319 them anyway, and the code has probably rotted by now. Based on
9320 patch from Karsten Loesing.
9321 - Stop allowing address masks that do not correspond to bit prefixes.
9322 We have warned about these for a really long time; now it's time
9323 to reject them. (Patch from croup.)
9324 - Remove an optimization in the AES counter-mode code that assumed
9325 that the counter never exceeded 2^68. When the counter can be set
9326 arbitrarily as an IV (as it is by Karsten's new hidden services
9327 code), this assumption no longer holds.
9328 - Disable the SETROUTERPURPOSE controller command: it is now
9332 Changes in version 0.1.2.19 - 2008-01-17
9333 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
9334 exit policy a little bit more conservative so it's safer to run an
9335 exit relay on a home system, and fixes a variety of smaller issues.
9338 - Exit policies now reject connections that are addressed to a
9339 relay's public (external) IP address too, unless
9340 ExitPolicyRejectPrivate is turned off. We do this because too
9341 many relays are running nearby to services that trust them based
9345 - When the clock jumps forward a lot, do not allow the bandwidth
9346 buckets to become negative. Fixes bug 544.
9347 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
9348 on every successful resolve. Reported by Mike Perry.
9349 - Purge old entries from the "rephist" database and the hidden
9350 service descriptor database even when DirPort is zero.
9351 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
9352 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
9353 crashing or mis-answering these requests.
9354 - When we decide to send a 503 response to a request for servers, do
9355 not then also send the server descriptors: this defeats the whole
9356 purpose. Fixes bug 539.
9359 - Changing the ExitPolicyRejectPrivate setting should cause us to
9360 rebuild our server descriptor.
9361 - Fix handling of hex nicknames when answering controller requests for
9362 networkstatus by name, or when deciding whether to warn about
9363 unknown routers in a config option. (Patch from mwenge.)
9364 - Fix a couple of hard-to-trigger autoconf problems that could result
9365 in really weird results on platforms whose sys/types.h files define
9366 nonstandard integer types.
9367 - Don't try to create the datadir when running --verify-config or
9368 --hash-password. Resolves bug 540.
9369 - If we were having problems getting a particular descriptor from the
9370 directory caches, and then we learned about a new descriptor for
9371 that router, we weren't resetting our failure count. Reported
9373 - Although we fixed bug 539 (where servers would send HTTP status 503
9374 responses _and_ send a body too), there are still servers out there
9375 that haven't upgraded. Therefore, make clients parse such bodies
9376 when they receive them.
9377 - Run correctly on systems where rlim_t is larger than unsigned long.
9378 This includes some 64-bit systems.
9379 - Run correctly on platforms (like some versions of OS X 10.5) where
9380 the real limit for number of open files is OPEN_FILES, not rlim_max
9381 from getrlimit(RLIMIT_NOFILES).
9382 - Avoid a spurious free on base64 failure.
9383 - Avoid segfaults on certain complex invocations of
9384 router_get_by_hexdigest().
9385 - Fix rare bug on REDIRECTSTREAM control command when called with no
9386 port set: it could erroneously report an error when none had
9390 Changes in version 0.1.2.18 - 2007-10-28
9391 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
9392 hidden service introduction that were causing huge delays, and a big
9393 bug that was causing some servers to disappear from the network status
9394 lists for a few hours each day.
9396 o Major bugfixes (crashes):
9397 - If a connection is shut down abruptly because of something that
9398 happened inside connection_flushed_some(), do not call
9399 connection_finished_flushing(). Should fix bug 451:
9400 "connection_stop_writing: Assertion conn->write_event failed"
9401 Bugfix on 0.1.2.7-alpha.
9402 - Fix possible segfaults in functions called from
9403 rend_process_relay_cell().
9405 o Major bugfixes (hidden services):
9406 - Hidden services were choosing introduction points uniquely by
9407 hexdigest, but when constructing the hidden service descriptor
9408 they merely wrote the (potentially ambiguous) nickname.
9409 - Clients now use the v2 intro format for hidden service
9410 connections: they specify their chosen rendezvous point by identity
9411 digest rather than by (potentially ambiguous) nickname. These
9412 changes could speed up hidden service connections dramatically.
9414 o Major bugfixes (other):
9415 - Stop publishing a new server descriptor just because we get a
9416 HUP signal. This led (in a roundabout way) to some servers getting
9417 dropped from the networkstatus lists for a few hours each day.
9418 - When looking for a circuit to cannibalize, consider family as well
9419 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
9420 circuit cannibalization).
9421 - When a router wasn't listed in a new networkstatus, we were leaving
9422 the flags for that router alone -- meaning it remained Named,
9423 Running, etc -- even though absence from the networkstatus means
9424 that it shouldn't be considered to exist at all anymore. Now we
9425 clear all the flags for routers that fall out of the networkstatus
9426 consensus. Fixes bug 529.
9429 - Don't try to access (or alter) the state file when running
9430 --list-fingerprint or --verify-config or --hash-password. Resolves
9432 - When generating information telling us how to extend to a given
9433 router, do not try to include the nickname if it is
9434 absent. Resolves bug 467.
9435 - Fix a user-triggerable segfault in expand_filename(). (There isn't
9436 a way to trigger this remotely.)
9437 - When sending a status event to the controller telling it that an
9438 OR address is reachable, set the port correctly. (Previously we
9439 were reporting the dir port.)
9440 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
9441 command. Bugfix on 0.1.2.17.
9442 - When loading bandwidth history, do not believe any information in
9443 the future. Fixes bug 434.
9444 - When loading entry guard information, do not believe any information
9446 - When we have our clock set far in the future and generate an
9447 onion key, then re-set our clock to be correct, we should not stop
9448 the onion key from getting rotated.
9449 - On some platforms, accept() can return a broken address. Detect
9450 this more quietly, and deal accordingly. Fixes bug 483.
9451 - It's not actually an error to find a non-pending entry in the DNS
9452 cache when canceling a pending resolve. Don't log unless stuff
9453 is fishy. Resolves bug 463.
9454 - Don't reset trusted dir server list when we set a configuration
9455 option. Patch from Robert Hogan.
9458 Changes in version 0.1.2.17 - 2007-08-30
9459 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
9460 X bundles. Vidalia 0.0.14 makes authentication required for the
9461 ControlPort in the default configuration, which addresses important
9462 security risks. Everybody who uses Vidalia (or another controller)
9465 In addition, this Tor update fixes major load balancing problems with
9466 path selection, which should speed things up a lot once many people
9469 o Major bugfixes (security):
9470 - We removed support for the old (v0) control protocol. It has been
9471 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
9472 become more of a headache than it's worth.
9474 o Major bugfixes (load balancing):
9475 - When choosing nodes for non-guard positions, weight guards
9476 proportionally less, since they already have enough load. Patch
9478 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
9479 will allow fast Tor servers to get more attention.
9480 - When we're upgrading from an old Tor version, forget our current
9481 guards and pick new ones according to the new weightings. These
9482 three load balancing patches could raise effective network capacity
9483 by a factor of four. Thanks to Mike Perry for measurements.
9485 o Major bugfixes (stream expiration):
9486 - Expire not-yet-successful application streams in all cases if
9487 they've been around longer than SocksTimeout. Right now there are
9488 some cases where the stream will live forever, demanding a new
9489 circuit every 15 seconds. Fixes bug 454; reported by lodger.
9491 o Minor features (controller):
9492 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
9493 is valid before any authentication has been received. It tells
9494 a controller what kind of authentication is expected, and what
9495 protocol is spoken. Implements proposal 119.
9497 o Minor bugfixes (performance):
9498 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
9499 greatly speeding up loading cached-routers from disk on startup.
9500 - Disable sentinel-based debugging for buffer code: we squashed all
9501 the bugs that this was supposed to detect a long time ago, and now
9502 its only effect is to change our buffer sizes from nice powers of
9503 two (which platform mallocs tend to like) to values slightly over
9504 powers of two (which make some platform mallocs sad).
9506 o Minor bugfixes (misc):
9507 - If exit bandwidth ever exceeds one third of total bandwidth, then
9508 use the correct formula to weight exit nodes when choosing paths.
9509 Based on patch from Mike Perry.
9510 - Choose perfectly fairly among routers when choosing by bandwidth and
9511 weighting by fraction of bandwidth provided by exits. Previously, we
9512 would choose with only approximate fairness, and correct ourselves
9513 if we ran off the end of the list.
9514 - If we require CookieAuthentication but we fail to write the
9515 cookie file, we would warn but not exit, and end up in a state
9516 where no controller could authenticate. Now we exit.
9517 - If we require CookieAuthentication, stop generating a new cookie
9518 every time we change any piece of our config.
9519 - Refuse to start with certain directory authority keys, and
9520 encourage people using them to stop.
9521 - Terminate multi-line control events properly. Original patch
9523 - Fix a minor memory leak when we fail to find enough suitable
9524 servers to choose a circuit.
9525 - Stop leaking part of the descriptor when we run into a particularly
9526 unparseable piece of it.
9529 Changes in version 0.1.2.16 - 2007-08-01
9530 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
9531 remote attacker in certain situations to rewrite the user's torrc
9532 configuration file. This can completely compromise anonymity of users
9533 in most configurations, including those running the Vidalia bundles,
9534 TorK, etc. Or worse.
9536 o Major security fixes:
9537 - Close immediately after missing authentication on control port;
9538 do not allow multiple authentication attempts.
9541 Changes in version 0.1.2.15 - 2007-07-17
9542 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
9543 problems, fixes compilation on BSD, and fixes a variety of other
9544 bugs. Everybody should upgrade.
9546 o Major bugfixes (compilation):
9547 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
9549 o Major bugfixes (crashes):
9550 - Try even harder not to dereference the first character after
9551 an mmap(). Reported by lodger.
9552 - Fix a crash bug in directory authorities when we re-number the
9553 routerlist while inserting a new router.
9554 - When the cached-routers file is an even multiple of the page size,
9555 don't run off the end and crash. (Fixes bug 455; based on idea
9557 - Fix eventdns.c behavior on Solaris: It is critical to include
9558 orconfig.h _before_ sys/types.h, so that we can get the expected
9559 definition of _FILE_OFFSET_BITS.
9561 o Major bugfixes (security):
9562 - Fix a possible buffer overrun when using BSD natd support. Bug
9564 - When sending destroy cells from a circuit's origin, don't include
9565 the reason for tearing down the circuit. The spec says we didn't,
9566 and now we actually don't. Reported by lodger.
9567 - Keep streamids from different exits on a circuit separate. This
9568 bug may have allowed other routers on a given circuit to inject
9569 cells into streams. Reported by lodger; fixes bug 446.
9570 - If there's a never-before-connected-to guard node in our list,
9571 never choose any guards past it. This way we don't expand our
9572 guard list unless we need to.
9574 o Minor bugfixes (guard nodes):
9575 - Weight guard selection by bandwidth, so that low-bandwidth nodes
9576 don't get overused as guards.
9578 o Minor bugfixes (directory):
9579 - Correctly count the number of authorities that recommend each
9580 version. Previously, we were under-counting by 1.
9581 - Fix a potential crash bug when we load many server descriptors at
9582 once and some of them make others of them obsolete. Fixes bug 458.
9584 o Minor bugfixes (hidden services):
9585 - Stop tearing down the whole circuit when the user asks for a
9586 connection to a port that the hidden service didn't configure.
9589 o Minor bugfixes (misc):
9590 - On Windows, we were preventing other processes from reading
9591 cached-routers while Tor was running. Reported by janbar.
9592 - Fix a possible (but very unlikely) bug in picking routers by
9593 bandwidth. Add a log message to confirm that it is in fact
9594 unlikely. Patch from lodger.
9595 - Backport a couple of memory leak fixes.
9596 - Backport miscellaneous cosmetic bugfixes.
9599 Changes in version 0.1.2.14 - 2007-05-25
9600 Tor 0.1.2.14 changes the addresses of two directory authorities (this
9601 change especially affects those who serve or use hidden services),
9602 and fixes several other crash- and security-related bugs.
9604 o Directory authority changes:
9605 - Two directory authorities (moria1 and moria2) just moved to new
9606 IP addresses. This change will particularly affect those who serve
9607 or use hidden services.
9609 o Major bugfixes (crashes):
9610 - If a directory server runs out of space in the connection table
9611 as it's processing a begin_dir request, it will free the exit stream
9612 but leave it attached to the circuit, leading to unpredictable
9613 behavior. (Reported by seeess, fixes bug 425.)
9614 - Fix a bug in dirserv_remove_invalid() that would cause authorities
9615 to corrupt memory under some really unlikely scenarios.
9616 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
9617 - Avoid segfaults when reading from mmaped descriptor file. (Reported
9620 o Major bugfixes (security):
9621 - When choosing an entry guard for a circuit, avoid using guards
9622 that are in the same family as the chosen exit -- not just guards
9623 that are exactly the chosen exit. (Reported by lodger.)
9625 o Major bugfixes (resource management):
9626 - If a directory authority is down, skip it when deciding where to get
9627 networkstatus objects or descriptors. Otherwise we keep asking
9628 every 10 seconds forever. Fixes bug 384.
9629 - Count it as a failure if we fetch a valid network-status but we
9630 don't want to keep it. Otherwise we'll keep fetching it and keep
9631 not wanting to keep it. Fixes part of bug 422.
9632 - If all of our dirservers have given us bad or no networkstatuses
9633 lately, then stop hammering them once per minute even when we
9634 think they're failed. Fixes another part of bug 422.
9637 - Actually set the purpose correctly for descriptors inserted with
9639 - When we have k non-v2 authorities in our DirServer config,
9640 we ignored the last k authorities in the list when updating our
9642 - Correctly back-off from requesting router descriptors that we are
9643 having a hard time downloading.
9644 - Read resolv.conf files correctly on platforms where read() returns
9645 partial results on small file reads.
9646 - Don't rebuild the entire router store every time we get 32K of
9647 routers: rebuild it when the journal gets very large, or when
9648 the gaps in the store get very large.
9651 - When routers publish SVN revisions in their router descriptors,
9652 authorities now include those versions correctly in networkstatus
9654 - Warn when using a version of libevent before 1.3b to run a server on
9655 OSX or BSD: these versions interact badly with userspace threads.
9658 Changes in version 0.1.2.13 - 2007-04-24
9659 This release features some major anonymity fixes, such as safer path
9660 selection; better client performance; faster bootstrapping, better
9661 address detection, and better DNS support for servers; write limiting as
9662 well as read limiting to make servers easier to run; and a huge pile of
9663 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
9665 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
9666 of the Freenode IRC network, remembering his patience and vision for
9667 free speech on the Internet.
9669 o Major features, client performance:
9670 - Weight directory requests by advertised bandwidth. Now we can
9671 let servers enable write limiting but still allow most clients to
9672 succeed at their directory requests. (We still ignore weights when
9673 choosing a directory authority; I hope this is a feature.)
9674 - Stop overloading exit nodes -- avoid choosing them for entry or
9675 middle hops when the total bandwidth available from non-exit nodes
9676 is much higher than the total bandwidth available from exit nodes.
9677 - Rather than waiting a fixed amount of time between retrying
9678 application connections, we wait only 10 seconds for the first,
9679 10 seconds for the second, and 15 seconds for each retry after
9680 that. Hopefully this will improve the expected user experience.
9681 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
9682 to open a stream fails; now we do in more cases. This should
9683 make clients able to find a good exit faster in some cases, since
9684 unhandleable requests will now get an error rather than timing out.
9686 o Major features, client functionality:
9687 - Implement BEGIN_DIR cells, so we can connect to a directory
9688 server via TLS to do encrypted directory requests rather than
9689 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
9690 config options if you like. For now, this feature only works if
9691 you already have a descriptor for the destination dirserver.
9692 - Add support for transparent application connections: this basically
9693 bundles the functionality of trans-proxy-tor into the Tor
9694 mainline. Now hosts with compliant pf/netfilter implementations
9695 can redirect TCP connections straight to Tor without diverting
9696 through SOCKS. (Based on patch from tup.)
9697 - Add support for using natd; this allows FreeBSDs earlier than
9698 5.1.2 to have ipfw send connections through Tor without using
9699 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
9701 o Major features, servers:
9702 - Setting up a dyndns name for your server is now optional: servers
9703 with no hostname or IP address will learn their IP address by
9704 asking the directory authorities. This code only kicks in when you
9705 would normally have exited with a "no address" error. Nothing's
9706 authenticated, so use with care.
9707 - Directory servers now spool server descriptors, v1 directories,
9708 and v2 networkstatus objects to buffers as needed rather than en
9709 masse. They also mmap the cached-routers files. These steps save
9711 - Stop requiring clients to have well-formed certificates, and stop
9712 checking nicknames in certificates. (Clients have certificates so
9713 that they can look like Tor servers, but in the future we might want
9714 to allow them to look like regular TLS clients instead. Nicknames
9715 in certificates serve no purpose other than making our protocol
9716 easier to recognize on the wire.) Implements proposal 106.
9718 o Improvements on DNS support:
9719 - Add "eventdns" asynchronous dns library originally based on code
9720 from Adam Langley. Now we can discard the old rickety dnsworker
9721 concept, and support a wider variety of DNS functions. Allows
9722 multithreaded builds on NetBSD and OpenBSD again.
9723 - Add server-side support for "reverse" DNS lookups (using PTR
9724 records so clients can determine the canonical hostname for a given
9725 IPv4 address). Only supported by servers using eventdns; servers
9726 now announce in their descriptors if they don't support eventdns.
9727 - Workaround for name servers (like Earthlink's) that hijack failing
9728 DNS requests and replace the no-such-server answer with a "helpful"
9729 redirect to an advertising-driven search portal. Also work around
9730 DNS hijackers who "helpfully" decline to hijack known-invalid
9731 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
9732 lets you turn it off.
9733 - Servers now check for the case when common DNS requests are going to
9734 wildcarded addresses (i.e. all getting the same answer), and change
9735 their exit policy to reject *:* if it's happening.
9736 - When asked to resolve a hostname, don't use non-exit servers unless
9737 requested to do so. This allows servers with broken DNS to be
9738 useful to the network.
9739 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
9740 useless IPv6 DNS resolves.
9741 - Specify and implement client-side SOCKS5 interface for reverse DNS
9742 lookups (see doc/socks-extensions.txt). Also cache them.
9743 - When we change nameservers or IP addresses, reset and re-launch
9744 our tests for DNS hijacking.
9746 o Improvements on reachability testing:
9747 - Servers send out a burst of long-range padding cells once they've
9748 established that they're reachable. Spread them over 4 circuits,
9749 so hopefully a few will be fast. This exercises bandwidth and
9750 bootstraps them into the directory more quickly.
9751 - When we find our DirPort to be reachable, publish a new descriptor
9752 so we'll tell the world (reported by pnx).
9753 - Directory authorities now only decide that routers are reachable
9754 if their identity keys are as expected.
9755 - Do DirPort reachability tests less often, since a single test
9756 chews through many circuits before giving up.
9757 - Avoid some false positives during reachability testing: don't try
9758 to test via a server that's on the same /24 network as us.
9759 - Start publishing one minute or so after we find our ORPort
9760 to be reachable. This will help reduce the number of descriptors
9761 we have for ourselves floating around, since it's quite likely
9762 other things (e.g. DirPort) will change during that minute too.
9763 - Routers no longer try to rebuild long-term connections to directory
9764 authorities, and directory authorities no longer try to rebuild
9765 long-term connections to all servers. We still don't hang up
9766 connections in these two cases though -- we need to look at it
9767 more carefully to avoid flapping, and we likely need to wait til
9768 0.1.1.x is obsolete.
9770 o Improvements on rate limiting:
9771 - Enable write limiting as well as read limiting. Now we sacrifice
9772 capacity if we're pushing out lots of directory traffic, rather
9773 than overrunning the user's intended bandwidth limits.
9774 - Include TLS overhead when counting bandwidth usage; previously, we
9775 would count only the bytes sent over TLS, but not the bytes used
9777 - Servers decline directory requests much more aggressively when
9778 they're low on bandwidth. Otherwise they end up queueing more and
9779 more directory responses, which can't be good for latency.
9780 - But never refuse directory requests from local addresses.
9781 - Be willing to read or write on local connections (e.g. controller
9782 connections) even when the global rate limiting buckets are empty.
9783 - Flush local controller connection buffers periodically as we're
9784 writing to them, so we avoid queueing 4+ megabytes of data before
9786 - Revise and clean up the torrc.sample that we ship with; add
9787 a section for BandwidthRate and BandwidthBurst.
9789 o Major features, NT services:
9790 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
9791 command-line flag so that admins can override the default by saying
9792 "tor --service install --user "SomeUser"". This will not affect
9793 existing installed services. Also, warn the user that the service
9794 will look for its configuration file in the service user's
9795 %appdata% directory. (We can't do the "hardwire the user's appdata
9796 directory" trick any more, since we may not have read access to that
9798 - Support running the Tor service with a torrc not in the same
9799 directory as tor.exe and default to using the torrc located in
9800 the %appdata%\Tor\ of the user who installed the service. Patch
9802 - Add an --ignore-missing-torrc command-line option so that we can
9803 get the "use sensible defaults if the configuration file doesn't
9804 exist" behavior even when specifying a torrc location on the
9806 - When stopping an NT service, wait up to 10 sec for it to actually
9807 stop. (Patch from Matt Edman; resolves bug 295.)
9809 o Directory authority improvements:
9810 - Stop letting hibernating or obsolete servers affect uptime and
9812 - Stop listing hibernating servers in the v1 directory.
9813 - Authorities no longer recommend exits as guards if this would shift
9814 too much load to the exit nodes.
9815 - Authorities now specify server versions in networkstatus. This adds
9816 about 2% to the size of compressed networkstatus docs, and allows
9817 clients to tell which servers support BEGIN_DIR and which don't.
9818 The implementation is forward-compatible with a proposed future
9819 protocol version scheme not tied to Tor versions.
9820 - DirServer configuration lines now have an orport= option so
9821 clients can open encrypted tunnels to the authorities without
9822 having downloaded their descriptors yet. Enabled for moria1,
9823 moria2, tor26, and lefkada now in the default configuration.
9824 - Add a BadDirectory flag to network status docs so that authorities
9825 can (eventually) tell clients about caches they believe to be
9826 broken. Not used yet.
9827 - Allow authorities to list nodes as bad exits in their
9828 approved-routers file by fingerprint or by address. If most
9829 authorities set a BadExit flag for a server, clients don't think
9830 of it as a general-purpose exit. Clients only consider authorities
9831 that advertise themselves as listing bad exits.
9832 - Patch from Steve Hildrey: Generate network status correctly on
9833 non-versioning dirservers.
9834 - Have directory authorities allow larger amounts of drift in uptime
9835 without replacing the server descriptor: previously, a server that
9836 restarted every 30 minutes could have 48 "interesting" descriptors
9838 - Reserve the nickname "Unnamed" for routers that can't pick
9839 a hostname: any router can call itself Unnamed; directory
9840 authorities will never allocate Unnamed to any particular router;
9841 clients won't believe that any router is the canonical Unnamed.
9843 o Directory mirrors and clients:
9844 - Discard any v1 directory info that's over 1 month old (for
9845 directories) or over 1 week old (for running-routers lists).
9846 - Clients track responses with status 503 from dirservers. After a
9847 dirserver has given us a 503, we try not to use it until an hour has
9848 gone by, or until we have no dirservers that haven't given us a 503.
9849 - When we get a 503 from a directory, and we're not a server, we no
9850 longer count the failure against the total number of failures
9851 allowed for the object we're trying to download.
9852 - Prepare for servers to publish descriptors less often: never
9853 discard a descriptor simply for being too old until either it is
9854 recommended by no authorities, or until we get a better one for
9855 the same router. Make caches consider retaining old recommended
9856 routers for even longer.
9857 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
9858 headers for content, so that we can work better in the presence of
9859 caching HTTP proxies.
9860 - Stop fetching descriptors if you're not a dir mirror and you
9861 haven't tried to establish any circuits lately. (This currently
9862 causes some dangerous behavior, because when you start up again
9863 you'll use your ancient server descriptors.)
9865 o Major fixes, crashes:
9866 - Stop crashing when the controller asks us to resetconf more than
9867 one config option at once. (Vidalia 0.0.11 does this.)
9868 - Fix a longstanding obscure crash bug that could occur when we run
9869 out of DNS worker processes, if we're not using eventdns. (Resolves
9871 - Fix an assert that could trigger if a controller quickly set then
9872 cleared EntryNodes. (Bug found by Udo van den Heuvel.)
9873 - Avoid crash when telling controller about stream-status and a
9875 - Avoid sending junk to controllers or segfaulting when a controller
9876 uses EVENT_NEW_DESC with verbose nicknames.
9877 - Stop triggering asserts if the controller tries to extend hidden
9878 service circuits (reported by mwenge).
9879 - If we start a server with ClientOnly 1, then set ClientOnly to 0
9880 and hup, stop triggering an assert based on an empty onion_key.
9881 - Mask out all signals in sub-threads; only the libevent signal
9882 handler should be processing them. This should prevent some crashes
9883 on some machines using pthreads. (Patch from coderman.)
9884 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
9886 o Major fixes, anonymity/security:
9887 - Automatically avoid picking more than one node from the same
9888 /16 network when constructing a circuit. Add an
9889 "EnforceDistinctSubnets" option to let people disable it if they
9890 want to operate private test networks on a single subnet.
9891 - When generating bandwidth history, round down to the nearest
9892 1k. When storing accounting data, round up to the nearest 1k.
9893 - When we're running as a server, remember when we last rotated onion
9894 keys, so that we will rotate keys once they're a week old even if
9895 we never stay up for a week ourselves.
9896 - If a client asked for a server by name, and there's a named server
9897 in our network-status but we don't have its descriptor yet, we
9898 could return an unnamed server instead.
9899 - Reject (most) attempts to use Tor circuits with length one. (If
9900 many people start using Tor as a one-hop proxy, exit nodes become
9901 a more attractive target for compromise.)
9902 - Just because your DirPort is open doesn't mean people should be
9903 able to remotely teach you about hidden service descriptors. Now
9904 only accept rendezvous posts if you've got HSAuthoritativeDir set.
9905 - Fix a potential race condition in the rpm installer. Found by
9907 - Do not log IPs with TLS failures for incoming TLS
9908 connections. (Fixes bug 382.)
9910 o Major fixes, other:
9911 - If our system clock jumps back in time, don't publish a negative
9912 uptime in the descriptor.
9913 - When we start during an accounting interval before it's time to wake
9914 up, remember to wake up at the correct time. (May fix bug 342.)
9915 - Previously, we would cache up to 16 old networkstatus documents
9916 indefinitely, if they came from nontrusted authorities. Now we
9917 discard them if they are more than 10 days old.
9918 - When we have a state file we cannot parse, tell the user and
9919 move it aside. Now we avoid situations where the user starts
9920 Tor in 1904, Tor writes a state file with that timestamp in it,
9921 the user fixes her clock, and Tor refuses to start.
9922 - Publish a new descriptor after we hup/reload. This is important
9923 if our config has changed such that we'll want to start advertising
9924 our DirPort now, etc.
9925 - If we are using an exit enclave and we can't connect, e.g. because
9926 its webserver is misconfigured to not listen on localhost, then
9927 back off and try connecting from somewhere else before we fail.
9929 o New config options or behaviors:
9930 - When EntryNodes are configured, rebuild the guard list to contain,
9931 in order: the EntryNodes that were guards before; the rest of the
9932 EntryNodes; the nodes that were guards before.
9933 - Do not warn when individual nodes in the configuration's EntryNodes,
9934 ExitNodes, etc are down: warn only when all possible nodes
9935 are down. (Fixes bug 348.)
9936 - Put a lower-bound on MaxAdvertisedBandwidth.
9937 - Start using the state file to store bandwidth accounting data:
9938 the bw_accounting file is now obsolete. We'll keep generating it
9939 for a while for people who are still using 0.1.2.4-alpha.
9940 - Try to batch changes to the state file so that we do as few
9941 disk writes as possible while still storing important things in
9943 - The state file and the bw_accounting file get saved less often when
9944 the AvoidDiskWrites config option is set.
9945 - Make PIDFile work on Windows.
9946 - Add internal descriptions for a bunch of configuration options:
9947 accessible via controller interface and in comments in saved
9949 - Reject *:563 (NNTPS) in the default exit policy. We already reject
9950 NNTP by default, so this seems like a sensible addition.
9951 - Clients now reject hostnames with invalid characters. This should
9952 avoid some inadvertent info leaks. Add an option
9953 AllowNonRFC953Hostnames to disable this behavior, in case somebody
9954 is running a private network with hosts called @, !, and #.
9955 - Check for addresses with invalid characters at the exit as well,
9956 and warn less verbosely when they fail. You can override this by
9957 setting ServerDNSAllowNonRFC953Addresses to 1.
9958 - Remove some options that have been deprecated since at least
9959 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
9960 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
9961 to set log options. Mark PathlenCoinWeight as obsolete.
9962 - Stop accepting certain malformed ports in configured exit policies.
9963 - When the user uses bad syntax in the Log config line, stop
9964 suggesting other bad syntax as a replacement.
9965 - Add new config option "ResolvConf" to let the server operator
9966 choose an alternate resolve.conf file when using eventdns.
9967 - If one of our entry guards is on the ExcludeNodes list, or the
9968 directory authorities don't think it's a good guard, treat it as
9969 if it were unlisted: stop using it as a guard, and throw it off
9970 the guards list if it stays that way for a long time.
9971 - Allow directory authorities to be marked separately as authorities
9972 for the v1 directory protocol, the v2 directory protocol, and
9973 as hidden service directories, to make it easier to retire old
9974 authorities. V1 authorities should set "HSAuthoritativeDir 1"
9975 to continue being hidden service authorities too.
9976 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
9977 - Make TrackExitHosts case-insensitive, and fix the behavior of
9978 ".suffix" TrackExitHosts items to avoid matching in the middle of
9980 - New DirPort behavior: if you have your dirport set, you download
9981 descriptors aggressively like a directory mirror, whether or not
9985 - Create a new file ReleaseNotes which was the old ChangeLog. The
9986 new ChangeLog file now includes the notes for all development
9988 - Add a new address-spec.txt document to describe our special-case
9989 addresses: .exit, .onion, and .noconnnect.
9990 - Fork the v1 directory protocol into its own spec document,
9991 and mark dir-spec.txt as the currently correct (v2) spec.
9993 o Packaging, porting, and contrib
9994 - "tor --verify-config" now exits with -1(255) or 0 depending on
9995 whether the config options are bad or good.
9996 - The Debian package now uses --verify-config when (re)starting,
9997 to distinguish configuration errors from other errors.
9998 - Adapt a patch from goodell to let the contrib/exitlist script
9999 take arguments rather than require direct editing.
10000 - Prevent the contrib/exitlist script from printing the same
10001 result more than once.
10002 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
10003 - In the hidden service example in torrc.sample, stop recommending
10004 esoteric and discouraged hidden service options.
10005 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
10006 values before failing, and always enables eventdns.
10007 - Try to detect Windows correctly when cross-compiling.
10008 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
10009 Try to fix this in configure.in by checking for most functions
10010 before we check for libevent.
10011 - Update RPMs to require libevent 1.2.
10012 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
10013 or later. Log when we are doing this, so we can diagnose it when
10014 it fails. (Also, recommend libevent 1.1b for kqueue and
10015 win32 methods; deprecate libevent 1.0b harder; make libevent
10016 recommendation system saner.)
10017 - Build with recent (1.3+) libevents on platforms that do not
10018 define the nonstandard types "u_int8_t" and friends.
10019 - Remove architecture from OS X builds. The official builds are
10020 now universal binaries.
10021 - Run correctly on OS X platforms with case-sensitive filesystems.
10022 - Correctly set maximum connection limit on Cygwin. (This time
10024 - Start compiling on MinGW on Windows (patches from Mike Chiussi
10026 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
10027 - Finally fix the openssl warnings from newer gccs that believe that
10028 ignoring a return value is okay, but casting a return value and
10029 then ignoring it is a sign of madness.
10030 - On architectures where sizeof(int)>4, still clamp declarable
10031 bandwidth to INT32_MAX.
10033 o Minor features, controller:
10034 - Warn the user when an application uses the obsolete binary v0
10035 control protocol. We're planning to remove support for it during
10036 the next development series, so it's good to give people some
10038 - Add STREAM_BW events to report per-entry-stream bandwidth
10039 use. (Patch from Robert Hogan.)
10040 - Rate-limit SIGNEWNYM signals in response to controllers that
10041 impolitely generate them for every single stream. (Patch from
10042 mwenge; closes bug 394.)
10043 - Add a REMAP status to stream events to note that a stream's
10044 address has changed because of a cached address or a MapAddress
10046 - Make REMAP stream events have a SOURCE (cache or exit), and
10047 make them generated in every case where we get a successful
10048 connected or resolved cell.
10049 - Track reasons for OR connection failure; make these reasons
10050 available via the controller interface. (Patch from Mike Perry.)
10051 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
10052 can learn when clients are sending malformed hostnames to Tor.
10053 - Specify and implement some of the controller status events.
10054 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
10055 - Reimplement GETINFO so that info/names stays in sync with the
10057 - Implement "GETINFO fingerprint".
10058 - Implement "SETEVENTS GUARD" so controllers can get updates on
10059 entry guard status as it changes.
10060 - Make all connections to addresses of the form ".noconnect"
10061 immediately get closed. This lets application/controller combos
10062 successfully test whether they're talking to the same Tor by
10063 watching for STREAM events.
10064 - Add a REASON field to CIRC events; for backward compatibility, this
10065 field is sent only to controllers that have enabled the extended
10066 event format. Also, add additional reason codes to explain why
10067 a given circuit has been destroyed or truncated. (Patches from
10069 - Add a REMOTE_REASON field to extended CIRC events to tell the
10070 controller why a remote OR told us to close a circuit.
10071 - Stream events also now have REASON and REMOTE_REASON fields,
10072 working much like those for circuit events.
10073 - There's now a GETINFO ns/... field so that controllers can ask Tor
10074 about the current status of a router.
10075 - A new event type "NS" to inform a controller when our opinion of
10076 a router's status has changed.
10077 - Add a GETINFO events/names and GETINFO features/names so controllers
10078 can tell which events and features are supported.
10079 - A new CLEARDNSCACHE signal to allow controllers to clear the
10080 client-side DNS cache without expiring circuits.
10081 - Fix CIRC controller events so that controllers can learn the
10082 identity digests of non-Named servers used in circuit paths.
10083 - Let controllers ask for more useful identifiers for servers. Instead
10084 of learning identity digests for un-Named servers and nicknames
10085 for Named servers, the new identifiers include digest, nickname,
10086 and indication of Named status. Off by default; see control-spec.txt
10087 for more information.
10088 - Add a "getinfo address" controller command so it can display Tor's
10089 best guess to the user.
10090 - New controller event to alert the controller when our server
10091 descriptor has changed.
10092 - Give more meaningful errors on controller authentication failure.
10093 - Export the default exit policy via the control port, so controllers
10094 don't need to guess what it is / will be later.
10096 o Minor bugfixes, controller:
10097 - When creating a circuit via the controller, send a 'launched'
10098 event when we're done, so we follow the spec better.
10099 - Correct the control spec to match how the code actually responds
10100 to 'getinfo addr-mappings/*'. Reported by daejees.
10101 - The control spec described a GUARDS event, but the code
10102 implemented a GUARD event. Standardize on GUARD, but let people
10103 ask for GUARDS too. Reported by daejees.
10104 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
10105 clear the corresponding on_circuit variable, and remember later
10106 that we don't need to send a redundant CLOSED event. (Resolves part
10108 - Report events where a resolve succeeded or where we got a socks
10109 protocol error correctly, rather than calling both of them
10111 - Change reported stream target addresses to IP consistently when
10112 we finally get the IP from an exit node.
10113 - Send log messages to the controller even if they happen to be very
10115 - Flush ERR-level controller status events just like we currently
10116 flush ERR-level log events, so that a Tor shutdown doesn't prevent
10117 the controller from learning about current events.
10118 - Report the circuit number correctly in STREAM CLOSED events. Bug
10119 reported by Mike Perry.
10120 - Do not report bizarre values for results of accounting GETINFOs
10121 when the last second's write or read exceeds the allotted bandwidth.
10122 - Report "unrecognized key" rather than an empty string when the
10123 controller tries to fetch a networkstatus that doesn't exist.
10124 - When the controller does a "GETINFO network-status", tell it
10125 about even those routers whose descriptors are very old, and use
10126 long nicknames where appropriate.
10127 - Fix handling of verbose nicknames with ORCONN controller events:
10128 make them show up exactly when requested, rather than exactly when
10130 - Controller signals now work on non-Unix platforms that don't define
10131 SIGUSR1 and SIGUSR2 the way we expect.
10132 - Respond to SIGNAL command before we execute the signal, in case
10133 the signal shuts us down. Suggested by Karsten Loesing.
10134 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
10136 o Minor features, code performance:
10137 - Major performance improvement on inserting descriptors: change
10138 algorithm from O(n^2) to O(n).
10139 - Do not rotate onion key immediately after setting it for the first
10141 - Call router_have_min_dir_info half as often. (This is showing up in
10142 some profiles, but not others.)
10143 - When using GCC, make log_debug never get called at all, and its
10144 arguments never get evaluated, when no debug logs are configured.
10145 (This is showing up in some profiles, but not others.)
10146 - Statistics dumped by -USR2 now include a breakdown of public key
10147 operations, for profiling.
10148 - Make the common memory allocation path faster on machines where
10149 malloc(0) returns a pointer.
10150 - Split circuit_t into origin_circuit_t and or_circuit_t, and
10151 split connection_t into edge, or, dir, control, and base structs.
10152 These will save quite a bit of memory on busy servers, and they'll
10153 also help us track down bugs in the code and bugs in the spec.
10154 - Use OpenSSL's AES implementation on platforms where it's faster.
10155 This could save us as much as 10% CPU usage.
10157 o Minor features, descriptors and descriptor handling:
10158 - Avoid duplicate entries on MyFamily line in server descriptor.
10159 - When Tor receives a router descriptor that it asked for, but
10160 no longer wants (because it has received fresh networkstatuses
10161 in the meantime), do not warn the user. Cache the descriptor if
10162 we're a cache; drop it if we aren't.
10163 - Servers no longer ever list themselves in their "family" line,
10164 even if configured to do so. This makes it easier to configure
10165 family lists conveniently.
10167 o Minor fixes, confusing/misleading log messages:
10168 - Display correct results when reporting which versions are
10169 recommended, and how recommended they are. (Resolves bug 383.)
10170 - Inform the server operator when we decide not to advertise a
10171 DirPort due to AccountingMax enabled or a low BandwidthRate.
10172 - Only include function names in log messages for info/debug messages.
10173 For notice/warn/err, the content of the message should be clear on
10174 its own, and printing the function name only confuses users.
10175 - Remove even more protocol-related warnings from Tor server logs,
10176 such as bad TLS handshakes and malformed begin cells.
10177 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
10178 when the IP address is mapped through MapAddress to a hostname.
10179 - Fix misleading log messages: an entry guard that is "unlisted",
10180 as well as not known to be "down" (because we've never heard
10181 of it), is not therefore "up".
10183 o Minor fixes, old/obsolete behavior:
10184 - Start assuming we can use a create_fast cell if we don't know
10185 what version a router is running.
10186 - We no longer look for identity and onion keys in "identity.key" and
10187 "onion.key" -- these were replaced by secret_id_key and
10188 secret_onion_key in 0.0.8pre1.
10189 - We no longer require unrecognized directory entries to be
10191 - Drop compatibility with obsolete Tors that permit create cells
10192 to have the wrong circ_id_type.
10193 - Remove code to special-case "-cvs" ending, since it has not
10194 actually mattered since 0.0.9.
10195 - Don't re-write the fingerprint file every restart, unless it has
10198 o Minor fixes, misc client-side behavior:
10199 - Always remove expired routers and networkstatus docs before checking
10200 whether we have enough information to build circuits. (Fixes
10202 - When computing clock skew from directory HTTP headers, consider what
10203 time it was when we finished asking for the directory, not what
10205 - Make our socks5 handling more robust to broken socks clients:
10206 throw out everything waiting on the buffer in between socks
10207 handshake phases, since they can't possibly (so the theory
10208 goes) have predicted what we plan to respond to them.
10209 - Expire socks connections if they spend too long waiting for the
10210 handshake to finish. Previously we would let them sit around for
10211 days, if the connecting application didn't close them either.
10212 - And if the socks handshake hasn't started, don't send a
10213 "DNS resolve socks failed" handshake reply; just close it.
10214 - If the user asks to use invalid exit nodes, be willing to use
10216 - Track unreachable entry guards correctly: don't conflate
10217 'unreachable by us right now' with 'listed as down by the directory
10218 authorities'. With the old code, if a guard was unreachable by us
10219 but listed as running, it would clog our guard list forever.
10220 - Behave correctly in case we ever have a network with more than
10221 2GB/s total advertised capacity.
10222 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
10223 - Fix a memory leak when we ask for "all" networkstatuses and we
10224 get one we don't recognize.
10227 Changes in version 0.1.1.26 - 2006-12-14
10228 o Security bugfixes:
10229 - Stop sending the HttpProxyAuthenticator string to directory
10230 servers when directory connections are tunnelled through Tor.
10231 - Clients no longer store bandwidth history in the state file.
10232 - Do not log introduction points for hidden services if SafeLogging
10236 - Fix an assert failure when a directory authority sets
10237 AuthDirRejectUnlisted and then receives a descriptor from an
10238 unlisted router (reported by seeess).
10241 Changes in version 0.1.1.25 - 2006-11-04
10243 - When a client asks us to resolve (rather than connect to)
10244 an address, and we have a cached answer, give them the cached
10245 answer. Previously, we would give them no answer at all.
10246 - We were building exactly the wrong circuits when we predict
10247 hidden service requirements, meaning Tor would have to build all
10248 its circuits on demand.
10249 - If none of our live entry guards have a high uptime, but we
10250 require a guard with a high uptime, try adding a new guard before
10251 we give up on the requirement. This patch should make long-lived
10252 connections more stable on average.
10253 - When testing reachability of our DirPort, don't launch new
10254 tests when there's already one in progress -- unreachable
10255 servers were stacking up dozens of testing streams.
10257 o Security bugfixes:
10258 - When the user sends a NEWNYM signal, clear the client-side DNS
10259 cache too. Otherwise we continue to act on previous information.
10262 - Avoid a memory corruption bug when creating a hash table for
10264 - Avoid possibility of controller-triggered crash when misusing
10265 certain commands from a v0 controller on platforms that do not
10266 handle printf("%s",NULL) gracefully.
10267 - Avoid infinite loop on unexpected controller input.
10268 - Don't log spurious warnings when we see a circuit close reason we
10269 don't recognize; it's probably just from a newer version of Tor.
10270 - Add Vidalia to the OS X uninstaller script, so when we uninstall
10271 Tor/Privoxy we also uninstall Vidalia.
10274 Changes in version 0.1.1.24 - 2006-09-29
10276 - Allow really slow clients to not hang up five minutes into their
10277 directory downloads (suggested by Adam J. Richter).
10278 - Fix major performance regression from 0.1.0.x: instead of checking
10279 whether we have enough directory information every time we want to
10280 do something, only check when the directory information has changed.
10281 This should improve client CPU usage by 25-50%.
10282 - Don't crash if, after a server has been running for a while,
10283 it can't resolve its hostname.
10284 - When a client asks us to resolve (not connect to) an address,
10285 and we have a cached answer, give them the cached answer.
10286 Previously, we would give them no answer at all.
10289 - Allow Tor to start when RunAsDaemon is set but no logs are set.
10290 - Don't crash when the controller receives a third argument to an
10291 "extendcircuit" request.
10292 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
10293 response; fix error code when "getinfo dir/status/" fails.
10294 - Fix configure.in to not produce broken configure files with
10295 more recent versions of autoconf. Thanks to Clint for his auto*
10297 - Fix security bug on NetBSD that could allow someone to force
10298 uninitialized RAM to be sent to a server's DNS resolver. This
10299 only affects NetBSD and other platforms that do not bounds-check
10301 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
10302 methods: these are known to be buggy.
10303 - If we're a directory mirror and we ask for "all" network status
10304 documents, we would discard status documents from authorities
10305 we don't recognize.
10308 Changes in version 0.1.1.23 - 2006-07-30
10310 - Fast Tor servers, especially exit nodes, were triggering asserts
10311 due to a bug in handling the list of pending DNS resolves. Some
10312 bugs still remain here; we're hunting them.
10313 - Entry guards could crash clients by sending unexpected input.
10314 - More fixes on reachability testing: if you find yourself reachable,
10315 then don't ever make any client requests (so you stop predicting
10316 circuits), then hup or have your clock jump, then later your IP
10317 changes, you won't think circuits are working, so you won't try to
10318 test reachability, so you won't publish.
10321 - Avoid a crash if the controller does a resetconf firewallports
10322 and then a setconf fascistfirewall=1.
10323 - Avoid an integer underflow when the dir authority decides whether
10324 a router is stable: we might wrongly label it stable, and compute
10325 a slightly wrong median stability, when a descriptor is published
10327 - Fix a place where we might trigger an assert if we can't build our
10328 own server descriptor yet.
10331 Changes in version 0.1.1.22 - 2006-07-05
10333 - Fix a big bug that was causing servers to not find themselves
10334 reachable if they changed IP addresses. Since only 0.1.1.22+
10335 servers can do reachability testing correctly, now we automatically
10336 make sure to test via one of these.
10337 - Fix to allow clients and mirrors to learn directory info from
10338 descriptor downloads that get cut off partway through.
10339 - Directory authorities had a bug in deciding if a newly published
10340 descriptor was novel enough to make everybody want a copy -- a few
10341 servers seem to be publishing new descriptors many times a minute.
10343 - Fix a rare bug that was causing some servers to complain about
10344 "closing wedged cpuworkers" and skip some circuit create requests.
10345 - Make the Exit flag in directory status documents actually work.
10348 Changes in version 0.1.1.21 - 2006-06-10
10349 o Crash and assert fixes from 0.1.1.20:
10350 - Fix a rare crash on Tor servers that have enabled hibernation.
10351 - Fix a seg fault on startup for Tor networks that use only one
10352 directory authority.
10353 - Fix an assert from a race condition that occurs on Tor servers
10354 while exiting, where various threads are trying to log that they're
10355 exiting, and delete the logs, at the same time.
10356 - Make our unit tests pass again on certain obscure platforms.
10359 - Add support for building SUSE RPM packages.
10360 - Speed up initial bootstrapping for clients: if we are making our
10361 first ever connection to any entry guard, then don't mark it down
10363 - When only one Tor server in the network is labelled as a guard,
10364 and we've already picked him, we would cycle endlessly picking him
10365 again, being unhappy about it, etc. Now we specifically exclude
10366 current guards when picking a new guard.
10367 - Servers send create cells more reliably after the TLS connection
10368 is established: we were sometimes forgetting to send half of them
10369 when we had more than one pending.
10370 - If we get a create cell that asks us to extend somewhere, but the
10371 Tor server there doesn't match the expected digest, we now send
10372 a destroy cell back, rather than silently doing nothing.
10373 - Make options->RedirectExit work again.
10374 - Make cookie authentication for the controller work again.
10375 - Stop being picky about unusual characters in the arguments to
10376 mapaddress. It's none of our business.
10377 - Add a new config option "TestVia" that lets you specify preferred
10378 middle hops to use for test circuits. Perhaps this will let me
10379 debug the reachability problems better.
10381 o Log / documentation fixes:
10382 - If we're a server and some peer has a broken TLS certificate, don't
10383 log about it unless ProtocolWarnings is set, i.e., we want to hear
10384 about protocol violations by others.
10385 - Fix spelling of VirtualAddrNetwork in man page.
10386 - Add a better explanation at the top of the autogenerated torrc file
10387 about what happened to our old torrc.
10390 Changes in version 0.1.1.20 - 2006-05-23
10391 o Crash and assert fixes from 0.1.0.17:
10392 - Fix assert bug in close_logs() on exit: when we close and delete
10393 logs, remove them all from the global "logfiles" list.
10394 - Fix an assert error when we're out of space in the connection_list
10395 and we try to post a hidden service descriptor (reported by Peter
10397 - Fix a rare assert error when we've tried all intro points for
10398 a hidden service and we try fetching the service descriptor again:
10399 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed".
10400 - Setconf SocksListenAddress kills Tor if it fails to bind. Now back
10401 out and refuse the setconf if it would fail.
10402 - If you specify a relative torrc path and you set RunAsDaemon in
10403 your torrc, then it chdir()'s to the new directory. If you then
10404 HUP, it tries to load the new torrc location, fails, and exits.
10405 The fix: no longer allow a relative path to torrc when using -f.
10406 - Check for integer overflows in more places, when adding elements
10407 to smartlists. This could possibly prevent a buffer overflow
10408 on malicious huge inputs.
10410 o Security fixes, major:
10411 - When we're printing strings from the network, don't try to print
10412 non-printable characters. Now we're safer against shell escape
10413 sequence exploits, and also against attacks to fool users into
10414 misreading their logs.
10415 - Implement entry guards: automatically choose a handful of entry
10416 nodes and stick with them for all circuits. Only pick new guards
10417 when the ones you have are unsuitable, and if the old guards
10418 become suitable again, switch back. This will increase security
10419 dramatically against certain end-point attacks. The EntryNodes
10420 config option now provides some hints about which entry guards you
10421 want to use most; and StrictEntryNodes means to only use those.
10422 Fixes CVE-2006-0414.
10423 - Implement exit enclaves: if we know an IP address for the
10424 destination, and there's a running Tor server at that address
10425 which allows exit to the destination, then extend the circuit to
10426 that exit first. This provides end-to-end encryption and end-to-end
10427 authentication. Also, if the user wants a .exit address or enclave,
10428 use 4 hops rather than 3, and cannibalize a general circ for it
10430 - Obey our firewall options more faithfully:
10431 . If we can't get to a dirserver directly, try going via Tor.
10432 . Don't ever try to connect (as a client) to a place our
10433 firewall options forbid.
10434 . If we specify a proxy and also firewall options, obey the
10435 firewall options even when we're using the proxy: some proxies
10436 can only proxy to certain destinations.
10437 - Make clients regenerate their keys when their IP address changes.
10438 - For the OS X package's modified privoxy config file, comment
10439 out the "logfile" line so we don't log everything passed
10441 - Our TLS handshakes were generating a single public/private
10442 keypair for the TLS context, rather than making a new one for
10443 each new connection. Oops. (But we were still rotating them
10444 periodically, so it's not so bad.)
10445 - When we were cannibalizing a circuit with a particular exit
10446 node in mind, we weren't checking to see if that exit node was
10447 already present earlier in the circuit. Now we are.
10448 - Require server descriptors to list IPv4 addresses -- hostnames
10449 are no longer allowed. This also fixes potential vulnerabilities
10450 to servers providing hostnames as their address and then
10451 preferentially resolving them so they can partition users.
10452 - Our logic to decide if the OR we connected to was the right guy
10453 was brittle and maybe open to a mitm for invalid routers.
10455 o Security fixes, minor:
10456 - Adjust tor-spec.txt to parameterize cell and key lengths. Now
10457 Ian Goldberg can prove things about our handshake protocol more
10459 - Make directory authorities generate a separate "guard" flag to
10460 mean "would make a good entry guard". Clients now honor the
10461 is_guard flag rather than looking at is_fast or is_stable.
10462 - Try to list MyFamily elements by key, not by nickname, and warn
10463 if we've not heard of a server.
10464 - Start using RAND_bytes rather than RAND_pseudo_bytes from
10465 OpenSSL. Also, reseed our entropy every hour, not just at
10466 startup. And add entropy in 512-bit chunks, not 160-bit chunks.
10467 - Refuse server descriptors where the fingerprint line doesn't match
10468 the included identity key. Tor doesn't care, but other apps (and
10469 humans) might actually be trusting the fingerprint line.
10470 - We used to kill the circuit when we receive a relay command we
10471 don't recognize. Now we just drop that cell.
10472 - Fix a bug found by Lasse Overlier: when we were making internal
10473 circuits (intended to be cannibalized later for rendezvous and
10474 introduction circuits), we were picking them so that they had
10475 useful exit nodes. There was no need for this, and it actually
10476 aids some statistical attacks.
10477 - Start treating internal circuits and exit circuits separately.
10478 It's important to keep them separate because internal circuits
10479 have their last hops picked like middle hops, rather than like
10480 exit hops. So exiting on them will break the user's expectations.
10481 - Fix a possible way to DoS dirservers.
10482 - When the client asked for a rendezvous port that the hidden
10483 service didn't want to provide, we were sending an IP address
10484 back along with the end cell. Fortunately, it was zero. But stop
10487 o Packaging improvements:
10488 - Implement --with-libevent-dir option to ./configure. Improve
10489 search techniques to find libevent, and use those for openssl too.
10490 - Fix a couple of bugs in OpenSSL detection. Deal better when
10491 there are multiple SSLs installed with different versions.
10492 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
10493 - On non-gcc compilers (e.g. Solaris's cc), use "-g -O" instead of
10495 - Make unit tests (and other invocations that aren't the real Tor)
10496 run without launching listeners, creating subdirectories, and so on.
10497 - The OS X installer was adding a symlink for tor_resolve but
10498 the binary was called tor-resolve (reported by Thomas Hardly).
10499 - Now we can target arch and OS in rpm builds (contributed by
10500 Phobos). Also make the resulting dist-rpm filename match the
10502 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
10503 if you log to syslog and want something other than LOG_DAEMON.
10504 - Fix the torify (tsocks) config file to not use Tor for localhost
10506 - Start shipping socks-extensions.txt, tor-doc-unix.html,
10507 tor-doc-server.html, and stylesheet.css in the tarball.
10508 - Stop shipping tor-doc.html, INSTALL, and README in the tarball.
10509 They are useless now.
10510 - Add Peter Palfrader's contributed check-tor script. It lets you
10511 easily check whether a given server (referenced by nickname)
10512 is reachable by you.
10513 - Add BSD-style contributed startup script "rc.subr" from Peter
10516 o Directory improvements -- new directory protocol:
10517 - See tor/doc/dir-spec.txt for all the juicy details. Key points:
10518 - Authorities and caches publish individual descriptors (by
10519 digest, by fingerprint, by "all", and by "tell me yours").
10520 - Clients don't download or use the old directory anymore. Now they
10521 download network-statuses from the directory authorities, and
10522 fetch individual server descriptors as needed from mirrors.
10523 - Clients don't download descriptors of non-running servers.
10524 - Download descriptors by digest, not by fingerprint. Caches try to
10525 download all listed digests from authorities; clients try to
10526 download "best" digests from caches. This avoids partitioning
10527 and isolating attacks better.
10528 - Only upload a new server descriptor when options change, 18
10529 hours have passed, uptime is reset, or bandwidth changes a lot.
10530 - Directory authorities silently throw away new descriptors that
10531 haven't changed much if the timestamps are similar. We do this to
10532 tolerate older Tor servers that upload a new descriptor every 15
10533 minutes. (It seemed like a good idea at the time.)
10534 - Clients choose directory servers from the network status lists,
10535 not from their internal list of router descriptors. Now they can
10536 go to caches directly rather than needing to go to authorities
10537 to bootstrap the first set of descriptors.
10538 - When picking a random directory, prefer non-authorities if any
10540 - Add a new flag to network-status indicating whether the server
10541 can answer v2 directory requests too.
10542 - Directory mirrors now cache up to 16 unrecognized network-status
10543 docs, so new directory authorities will be cached too.
10544 - Stop parsing, storing, or using running-routers output (but
10545 mirrors still cache and serve it).
10546 - Clients consider a threshold of "versioning" directory authorities
10547 before deciding whether to warn the user that he's obsolete.
10548 - Authorities publish separate sorted lists of recommended versions
10549 for clients and for servers.
10550 - Change DirServers config line to note which dirs are v1 authorities.
10551 - Put nicknames on the DirServer line, so we can refer to them
10552 without requiring all our users to memorize their IP addresses.
10553 - Remove option when getting directory cache to see whether they
10554 support running-routers; they all do now. Replace it with one
10555 to see whether caches support v2 stuff.
10556 - Stop listing down or invalid nodes in the v1 directory. This
10557 reduces its bulk by about 1/3, and reduces load on mirrors.
10558 - Mirrors no longer cache the v1 directory as often.
10559 - If we as a directory mirror don't know of any v1 directory
10560 authorities, then don't try to cache any v1 directories.
10562 o Other directory improvements:
10563 - Add lefkada.eecs.harvard.edu and tor.dizum.com as fourth and
10564 fifth authoritative directory servers.
10565 - Directory authorities no longer require an open connection from
10566 a server to consider him "reachable". We need this change because
10567 when we add new directory authorities, old servers won't know not
10568 to hang up on them.
10569 - Dir authorities now do their own external reachability testing
10570 of each server, and only list as running the ones they found to
10571 be reachable. We also send back warnings to the server's logs if
10572 it uploads a descriptor that we already believe is unreachable.
10573 - Spread the directory authorities' reachability testing over the
10574 entire testing interval, so we don't try to do 500 TLS's at once
10576 - Make the "stable" router flag in network-status be the median of
10577 the uptimes of running valid servers, and make clients pay
10578 attention to the network-status flags. Thus the cutoff adapts
10579 to the stability of the network as a whole, making IRC, IM, etc
10580 connections more reliable.
10581 - Make the v2 dir's "Fast" flag based on relative capacity, just
10582 like "Stable" is based on median uptime. Name everything in the
10583 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
10584 - Retry directory requests if we fail to get an answer we like
10585 from a given dirserver (we were retrying before, but only if
10586 we fail to connect).
10587 - Return a robots.txt on our dirport to discourage google indexing.
10589 o Controller protocol improvements:
10590 - Revised controller protocol (version 1) that uses ascii rather
10591 than binary: tor/doc/control-spec.txt. Add supporting libraries
10592 in python and java and c# so you can use the controller from your
10593 applications without caring how our protocol works.
10594 - Allow the DEBUG controller event to work again. Mark certain log
10595 entries as "don't tell this to controllers", so we avoid cycles.
10596 - New controller function "getinfo accounting", to ask how
10597 many bytes we've used in this time period.
10598 - Add a "resetconf" command so you can set config options like
10599 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
10600 a config option in the torrc with no value, then it clears it
10601 entirely (rather than setting it to its default).
10602 - Add a "getinfo config-file" to tell us where torrc is. Also
10603 expose guard nodes, config options/names.
10604 - Add a "quit" command (when when using the controller manually).
10605 - Add a new signal "newnym" to "change pseudonyms" -- that is, to
10606 stop using any currently-dirty circuits for new streams, so we
10607 don't link new actions to old actions. This also occurs on HUP
10608 or "signal reload".
10609 - If we would close a stream early (e.g. it asks for a .exit that
10610 we know would refuse it) but the LeaveStreamsUnattached config
10611 option is set by the controller, then don't close it.
10612 - Add a new controller event type "authdir_newdescs" that allows
10613 controllers to get all server descriptors that were uploaded to
10614 a router in its role as directory authority.
10615 - New controller option "getinfo desc/all-recent" to fetch the
10616 latest server descriptor for every router that Tor knows about.
10617 - Fix the controller's "attachstream 0" command to treat conn like
10618 it just connected, doing address remapping, handling .exit and
10619 .onion idioms, and so on. Now we're more uniform in making sure
10620 that the controller hears about new and closing connections.
10621 - Permit transitioning from ORPort==0 to ORPort!=0, and back, from
10622 the controller. Also, rotate dns and cpu workers if the controller
10623 changes options that will affect them; and initialize the dns
10624 worker cache tree whether or not we start out as a server.
10625 - Add a new circuit purpose 'controller' to let the controller ask
10626 for a circuit that Tor won't try to use. Extend the "extendcircuit"
10627 controller command to let you specify the purpose if you're starting
10628 a new circuit. Add a new "setcircuitpurpose" controller command to
10629 let you change a circuit's purpose after it's been created.
10630 - Let the controller ask for "getinfo dir/server/foo" so it can ask
10631 directly rather than connecting to the dir port. "getinfo
10632 dir/status/foo" also works, but currently only if your DirPort
10634 - Let the controller tell us about certain router descriptors
10635 that it doesn't want Tor to use in circuits. Implement
10636 "setrouterpurpose" and modify "+postdescriptor" to do this.
10637 - If the controller's *setconf commands fail, collect an error
10638 message in a string and hand it back to the controller -- don't
10639 just tell them to go read their logs.
10641 o Scalability, resource management, and performance:
10642 - Fix a major load balance bug: we were round-robin reading in 16 KB
10643 chunks, and servers with bandwidthrate of 20 KB, while downloading
10644 a 600 KB directory, would starve their other connections. Now we
10645 try to be a bit more fair.
10646 - Be more conservative about whether to advertise our DirPort.
10647 The main change is to not advertise if we're running at capacity
10648 and either a) we could hibernate ever or b) our capacity is low
10649 and we're using a default DirPort.
10650 - We weren't cannibalizing circuits correctly for
10651 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
10652 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
10653 build those from scratch. This should make hidden services faster.
10654 - Predict required circuits better, with an eye toward making hidden
10655 services faster on the service end.
10656 - Compress exit policies even more: look for duplicate lines and
10658 - Generate 18.0.0.0/8 address policy format in descs when we can;
10659 warn when the mask is not reducible to a bit-prefix.
10660 - There used to be two ways to specify your listening ports in a
10661 server descriptor: on the "router" line and with a separate "ports"
10662 line. Remove support for the "ports" line.
10663 - Reduce memory requirements in our structs by changing the order
10664 of fields. Replace balanced trees with hash tables. Inline
10665 bottleneck smartlist functions. Add a "Map from digest to void*"
10666 abstraction so we can do less hex encoding/decoding, and use it
10667 in router_get_by_digest(). Many other CPU and memory improvements.
10668 - Allow tor_gzip_uncompress to extract as much as possible from
10669 truncated compressed data. Try to extract as many
10670 descriptors as possible from truncated http responses (when
10671 purpose is DIR_PURPOSE_FETCH_ROUTERDESC).
10672 - Make circ->onionskin a pointer, not a static array. moria2 was using
10673 125000 circuit_t's after it had been up for a few weeks, which
10674 translates to 20+ megs of wasted space.
10675 - The private half of our EDH handshake keys are now chosen out
10676 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
10677 - Stop doing the complex voodoo overkill checking for insecure
10678 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
10679 - Do round-robin writes for TLS of at most 16 kB per write. This
10680 might be more fair on loaded Tor servers.
10681 - Do not use unaligned memory access on alpha, mips, or mipsel.
10682 It *works*, but is very slow, so we treat them as if it doesn't.
10684 o Other bugfixes and improvements:
10685 - Start storing useful information to $DATADIR/state, so we can
10686 remember things across invocations of Tor. Retain unrecognized
10687 lines so we can be forward-compatible, and write a TorVersion line
10688 so we can be backward-compatible.
10689 - If ORPort is set, Address is not explicitly set, and our hostname
10690 resolves to a private IP address, try to use an interface address
10691 if it has a public address. Now Windows machines that think of
10692 themselves as localhost can guess their address.
10693 - Regenerate our local descriptor if it's dirty and we try to use
10694 it locally (e.g. if it changes during reachability detection).
10695 This was causing some Tor servers to keep publishing the same
10696 initial descriptor forever.
10697 - Tor servers with dynamic IP addresses were needing to wait 18
10698 hours before they could start doing reachability testing using
10699 the new IP address and ports. This is because they were using
10700 the internal descriptor to learn what to test, yet they were only
10701 rebuilding the descriptor once they decided they were reachable.
10702 - It turns out we couldn't bootstrap a network since we added
10703 reachability detection in 0.1.0.1-rc. Good thing the Tor network
10704 has never gone down. Add an AssumeReachable config option to let
10705 servers and authorities bootstrap. When we're trying to build a
10706 high-uptime or high-bandwidth circuit but there aren't enough
10707 suitable servers, try being less picky rather than simply failing.
10708 - Newly bootstrapped Tor networks couldn't establish hidden service
10709 circuits until they had nodes with high uptime. Be more tolerant.
10710 - Really busy servers were keeping enough circuits open on stable
10711 connections that they were wrapping around the circuit_id
10712 space. (It's only two bytes.) This exposed a bug where we would
10713 feel free to reuse a circuit_id even if it still exists but has
10714 been marked for close. Try to fix this bug. Some bug remains.
10715 - When we fail to bind or listen on an incoming or outgoing
10716 socket, we now close it before refusing, rather than just
10717 leaking it. (Thanks to Peter Palfrader for finding.)
10718 - Fix a file descriptor leak in start_daemon().
10719 - On Windows, you can't always reopen a port right after you've
10720 closed it. So change retry_listeners() to only close and re-open
10721 ports that have changed.
10722 - Workaround a problem with some http proxies that refuse GET
10723 requests that specify "Content-Length: 0". Reported by Adrian.
10724 - Recover better from TCP connections to Tor servers that are
10725 broken but don't tell you (it happens!); and rotate TLS
10726 connections once a week.
10727 - Fix a scary-looking but apparently harmless bug where circuits
10728 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
10729 servers, and never switch to state CIRCUIT_STATE_OPEN.
10730 - Check for even more Windows version flags when writing the platform
10731 string in server descriptors, and note any we don't recognize.
10732 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
10733 get a better idea of why their circuits failed. Not used yet.
10734 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
10735 We don't use them yet, but maybe one day our DNS resolver will be
10736 able to discover them.
10737 - Let people type "tor --install" as well as "tor -install" when they
10738 want to make it an NT service.
10739 - Looks like we were never delivering deflated (i.e. compressed)
10740 running-routers lists, even when asked. Oops.
10741 - We were leaking some memory every time the client changed IPs.
10742 - Clean up more of the OpenSSL memory when exiting, so we can detect
10743 memory leaks better.
10744 - Never call free() on tor_malloc()d memory. This will help us
10745 use dmalloc to detect memory leaks.
10746 - Some Tor servers process billions of cells per day. These
10747 statistics are now uint64_t's.
10748 - Check [X-]Forwarded-For headers in HTTP requests when generating
10749 log messages. This lets people run dirservers (and caches) behind
10750 Apache but still know which IP addresses are causing warnings.
10751 - Fix minor integer overflow in calculating when we expect to use up
10752 our bandwidth allocation before hibernating.
10753 - Lower the minimum required number of file descriptors to 1000,
10754 so we can have some overhead for Valgrind on Linux, where the
10755 default ulimit -n is 1024.
10756 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
10757 and its existence is confusing some users.
10759 o Config option fixes:
10760 - Add a new config option ExitPolicyRejectPrivate which defaults
10761 to on. Now all exit policies will begin with rejecting private
10762 addresses, unless the server operator explicitly turns it off.
10763 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB.
10764 - Add new ReachableORAddresses and ReachableDirAddresses options
10765 that understand address policies. FascistFirewall is now a synonym
10766 for "ReachableORAddresses *:443", "ReachableDirAddresses *:80".
10767 - Start calling it FooListenAddress rather than FooBindAddress,
10768 since few of our users know what it means to bind an address
10770 - If the user gave Tor an odd number of command-line arguments,
10771 we were silently ignoring the last one. Now we complain and fail.
10772 This wins the oldest-bug prize -- this bug has been present since
10773 November 2002, as released in Tor 0.0.0.
10774 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
10775 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
10776 it would silently ignore the 6668.
10777 - If we get a linelist or linelist_s config option from the torrc,
10778 e.g. ExitPolicy, and it has no value, warn and skip rather than
10779 silently resetting it to its default.
10780 - Setconf was appending items to linelists, not clearing them.
10781 - Add MyFamily to torrc.sample in the server section, so operators
10782 will be more likely to learn that it exists.
10783 - Make ContactInfo mandatory for authoritative directory servers.
10784 - MaxConn has been obsolete for a while now. Document the ConnLimit
10785 config option, which is a *minimum* number of file descriptors
10786 that must be available else Tor refuses to start.
10787 - Get rid of IgnoreVersion undocumented config option, and make us
10788 only warn, never exit, when we're running an obsolete version.
10789 - Make MonthlyAccountingStart config option truly obsolete now.
10790 - Correct the man page entry on TrackHostExitsExpire.
10791 - Let directory authorities start even if they don't specify an
10792 Address config option.
10793 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
10794 reflect the updated flags in our v2 dir protocol.
10796 o Config option features:
10797 - Add a new config option FastFirstHopPK (on by default) so clients
10798 do a trivial crypto handshake for their first hop, since TLS has
10799 already taken care of confidentiality and authentication.
10800 - Let the user set ControlListenAddress in the torrc. This can be
10801 dangerous, but there are some cases (like a secured LAN) where it
10803 - New config options to help controllers: FetchServerDescriptors
10804 and FetchHidServDescriptors for whether to fetch server
10805 info and hidserv info or let the controller do it, and
10806 PublishServerDescriptor and PublishHidServDescriptors.
10807 - Also let the controller set the __AllDirActionsPrivate config
10808 option if you want all directory fetches/publishes to happen via
10809 Tor (it assumes your controller bootstraps your circuits).
10810 - Add "HardwareAccel" config option: support for crypto hardware
10811 accelerators via OpenSSL. Off by default, until we find somebody
10812 smart who can test it for us. (It appears to produce seg faults
10813 in at least some cases.)
10814 - New config option "AuthDirRejectUnlisted" for directory authorities
10815 as a panic button: if we get flooded with unusable servers we can
10816 revert to only listing servers in the approved-routers file.
10817 - Directory authorities can now reject/invalidate by key and IP,
10818 with the config options "AuthDirInvalid" and "AuthDirReject", or
10819 by marking a fingerprint as "!reject" or "!invalid" (as its
10820 nickname) in the approved-routers file. This is useful since
10821 currently we automatically list servers as running and usable
10822 even if we know they're jerks.
10823 - Add a new config option TestSocks so people can see whether their
10824 applications are using socks4, socks4a, socks5-with-ip, or
10825 socks5-with-fqdn. This way they don't have to keep mucking
10826 with tcpdump and wondering if something got cached somewhere.
10827 - Add "private:*" as an alias in configuration for policies. Now
10828 you can simplify your exit policy rather than needing to list
10829 every single internal or nonroutable network space.
10830 - Accept "private:*" in routerdesc exit policies; not generated yet
10831 because older Tors do not understand it.
10832 - Add configuration option "V1AuthoritativeDirectory 1" which
10833 moria1, moria2, and tor26 have set.
10834 - Implement an option, VirtualAddrMask, to set which addresses
10835 get handed out in response to mapaddress requests. This works
10836 around a bug in tsocks where 127.0.0.0/8 is never socksified.
10837 - Add a new config option FetchUselessDescriptors, off by default,
10838 for when you plan to run "exitlist" on your client and you want
10839 to know about even the non-running descriptors.
10840 - SocksTimeout: How long do we let a socks connection wait
10841 unattached before we fail it?
10842 - CircuitBuildTimeout: Cull non-open circuits that were born
10843 at least this many seconds ago.
10844 - CircuitIdleTimeout: Cull open clean circuits that were born
10845 at least this many seconds ago.
10846 - New config option SafeSocks to reject all application connections
10847 using unsafe socks protocols. Defaults to off.
10849 o Improved and clearer log messages:
10850 - Reduce clutter in server logs. We're going to try to make
10851 them actually usable now. New config option ProtocolWarnings that
10852 lets you hear about how _other Tors_ are breaking the protocol. Off
10854 - Divide log messages into logging domains. Once we put some sort
10855 of interface on this, it will let people looking at more verbose
10856 log levels specify the topics they want to hear more about.
10857 - Log server fingerprint on startup, so new server operators don't
10858 have to go hunting around their filesystem for it.
10859 - Provide dire warnings to any users who set DirServer manually;
10860 move it out of torrc.sample and into torrc.complete.
10861 - Make the log message less scary when all the dirservers are
10862 temporarily unreachable.
10863 - When tor_socketpair() fails in Windows, give a reasonable
10864 Windows-style errno back.
10865 - Improve tor_gettimeofday() granularity on windows.
10866 - We were printing the number of idle dns workers incorrectly when
10868 - Handle duplicate lines in approved-routers files without warning.
10869 - We were whining about using socks4 or socks5-with-local-lookup
10870 even when it's an IP address in the "virtual" range we designed
10871 exactly for this case.
10872 - Check for named servers when looking them up by nickname;
10873 warn when we're calling a non-named server by its nickname;
10874 don't warn twice about the same name.
10875 - Downgrade the dirserver log messages when whining about
10877 - Correct "your server is reachable" log entries to indicate that
10878 it was self-testing that told us so.
10879 - If we're trying to be a Tor server and running Windows 95/98/ME
10880 as a server, explain that we'll likely crash.
10881 - Provide a more useful warn message when our onion queue gets full:
10882 the CPU is too slow or the exit policy is too liberal.
10883 - Don't warn when we receive a 503 from a dirserver/cache -- this
10884 will pave the way for them being able to refuse if they're busy.
10885 - When we fail to bind a listener, try to provide a more useful
10886 log message: e.g., "Is Tor already running?"
10887 - Only start testing reachability once we've established a
10888 circuit. This will make startup on dir authorities less noisy.
10889 - Don't try to upload hidden service descriptors until we have
10890 established a circuit.
10891 - Tor didn't warn when it failed to open a log file.
10892 - Warn when listening on a public address for socks. We suspect a
10893 lot of people are setting themselves up as open socks proxies,
10894 and they have no idea that jerks on the Internet are using them,
10895 since they simply proxy the traffic into the Tor network.
10896 - Give a useful message when people run Tor as the wrong user,
10897 rather than telling them to start chowning random directories.
10898 - Fix a harmless bug that was causing Tor servers to log
10899 "Got an end because of misc error, but we're not an AP. Closing."
10900 - Fix wrong log message when you add a "HiddenServiceNodes" config
10901 line without any HiddenServiceDir line (reported by Chris Thomas).
10902 - Directory authorities now stop whining so loudly about bad
10903 descriptors that they fetch from other dirservers. So when there's
10904 a log complaint, it's for sure from a freshly uploaded descriptor.
10905 - When logging via syslog, include the pid whenever we provide
10906 a log entry. Suggested by Todd Fries.
10907 - When we're shutting down and we do something like try to post a
10908 server descriptor or rendezvous descriptor, don't complain that
10909 we seem to be unreachable. Of course we are, we're shutting down.
10910 - Change log line for unreachability to explicitly suggest /etc/hosts
10911 as the culprit. Also make it clearer what IP address and ports we're
10912 testing for reachability.
10913 - Put quotes around user-supplied strings when logging so users are
10914 more likely to realize if they add bad characters (like quotes)
10916 - NT service patch from Matt Edman to improve error messages on Win32.
10919 Changes in version 0.1.0.17 - 2006-02-17
10920 o Crash bugfixes on 0.1.0.x:
10921 - When servers with a non-zero DirPort came out of hibernation,
10922 sometimes they would trigger an assert.
10924 o Other important bugfixes:
10925 - On platforms that don't have getrlimit (like Windows), we were
10926 artificially constraining ourselves to a max of 1024
10927 connections. Now just assume that we can handle as many as 15000
10928 connections. Hopefully this won't cause other problems.
10930 o Backported features:
10931 - When we're a server, a client asks for an old-style directory,
10932 and our write bucket is empty, don't give it to him. This way
10933 small servers can continue to serve the directory *sometimes*,
10934 without getting overloaded.
10935 - Whenever you get a 503 in response to a directory fetch, try
10936 once more. This will become important once servers start sending
10937 503's whenever they feel busy.
10938 - Fetch a new directory every 120 minutes, not every 40 minutes.
10939 Now that we have hundreds of thousands of users running the old
10940 directory algorithm, it's starting to hurt a lot.
10941 - Bump up the period for forcing a hidden service descriptor upload
10942 from 20 minutes to 1 hour.
10945 Changes in version 0.1.0.16 - 2006-01-02
10946 o Crash bugfixes on 0.1.0.x:
10947 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
10948 corrupting the heap, losing FDs, or crashing when we need to resize
10949 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
10950 - It turns out sparc64 platforms crash on unaligned memory access
10951 too -- so detect and avoid this.
10952 - Handle truncated compressed data correctly (by detecting it and
10954 - Fix possible-but-unlikely free(NULL) in control.c.
10955 - When we were closing connections, there was a rare case that
10956 stomped on memory, triggering seg faults and asserts.
10957 - Avoid potential infinite recursion when building a descriptor. (We
10958 don't know that it ever happened, but better to fix it anyway.)
10959 - We were neglecting to unlink marked circuits from soon-to-close OR
10960 connections, which caused some rare scribbling on freed memory.
10961 - Fix a memory stomping race bug when closing the joining point of two
10962 rendezvous circuits.
10963 - Fix an assert in time parsing found by Steven Murdoch.
10965 o Other bugfixes on 0.1.0.x:
10966 - When we're doing reachability testing, provide more useful log
10967 messages so the operator knows what to expect.
10968 - Do not check whether DirPort is reachable when we are suppressing
10969 advertising it because of hibernation.
10970 - When building with -static or on Solaris, we sometimes needed -ldl.
10971 - One of the dirservers (tor26) changed its IP address.
10972 - When we're deciding whether a stream has enough circuits around
10973 that can handle it, count the freshly dirty ones and not the ones
10974 that are so dirty they won't be able to handle it.
10975 - When we're expiring old circuits, we had a logic error that caused
10976 us to close new rendezvous circuits rather than old ones.
10977 - Give a more helpful log message when you try to change ORPort via
10978 the controller: you should upgrade Tor if you want that to work.
10979 - We were failing to parse Tor versions that start with "Tor ".
10980 - Tolerate faulty streams better: when a stream fails for reason
10981 exitpolicy, stop assuming that the router is lying about his exit
10982 policy. When a stream fails for reason misc, allow it to retry just
10983 as if it was resolvefailed. When a stream has failed three times,
10984 reset its failure count so we can try again and get all three tries.
10987 Changes in version 0.1.0.15 - 2005-09-23
10988 o Bugfixes on 0.1.0.x:
10989 - Reject ports 465 and 587 (spam targets) in default exit policy.
10990 - Don't crash when we don't have any spare file descriptors and we
10991 try to spawn a dns or cpu worker.
10992 - Get rid of IgnoreVersion undocumented config option, and make us
10993 only warn, never exit, when we're running an obsolete version.
10994 - Don't try to print a null string when your server finds itself to
10995 be unreachable and the Address config option is empty.
10996 - Make the numbers in read-history and write-history into uint64s,
10997 so they don't overflow and publish negatives in the descriptor.
10998 - Fix a minor memory leak in smartlist_string_remove().
10999 - We were only allowing ourselves to upload a server descriptor at
11000 most every 20 minutes, even if it changed earlier than that.
11001 - Clean up log entries that pointed to old URLs.
11004 Changes in version 0.1.0.14 - 2005-08-08
11005 o Bugfixes on 0.1.0.x:
11006 - Fix the other half of the bug with crypto handshakes
11008 - Fix an assert trigger if you send a 'signal term' via the
11009 controller when it's listening for 'event info' messages.
11012 Changes in version 0.1.0.13 - 2005-08-04
11013 o Bugfixes on 0.1.0.x:
11014 - Fix a critical bug in the security of our crypto handshakes.
11015 - Fix a size_t underflow in smartlist_join_strings2() that made
11016 it do bad things when you hand it an empty smartlist.
11017 - Fix Windows installer to ship Tor license (thanks to Aphex for
11018 pointing out this oversight) and put a link to the doc directory
11020 - Explicitly set no-unaligned-access for sparc: it turns out the
11021 new gcc's let you compile broken code, but that doesn't make it
11025 Changes in version 0.1.0.12 - 2005-07-18
11026 o New directory servers:
11027 - tor26 has changed IP address.
11029 o Bugfixes on 0.1.0.x:
11030 - Fix a possible double-free in tor_gzip_uncompress().
11031 - When --disable-threads is set, do not search for or link against
11032 pthreads libraries.
11033 - Don't trigger an assert if an authoritative directory server
11034 claims its dirport is 0.
11035 - Fix bug with removing Tor as an NT service: some people were
11036 getting "The service did not return an error." Thanks to Matt
11040 Changes in version 0.1.0.11 - 2005-06-30
11041 o Bugfixes on 0.1.0.x:
11042 - Fix major security bug: servers were disregarding their
11043 exit policies if clients behaved unexpectedly.
11044 - Make OS X init script check for missing argument, so we don't
11045 confuse users who invoke it incorrectly.
11046 - Fix a seg fault in "tor --hash-password foo".
11047 - The MAPADDRESS control command was broken.
11050 Changes in version 0.1.0.10 - 2005-06-14
11052 - Make NT services work and start on startup on Win32 (based on
11053 patch by Matt Edman). See the FAQ entry for details.
11054 - Make 'platform' string in descriptor more accurate for Win32
11055 servers, so it's not just "unknown platform".
11056 - REUSEADDR on normal platforms means you can rebind to the port
11057 right after somebody else has let it go. But REUSEADDR on Win32
11058 means you can bind to the port _even when somebody else already
11059 has it bound_! So, don't do that on Win32.
11060 - Clean up the log messages when starting on Win32 with no config
11062 - Allow seeding the RNG on Win32 even when you're not running as
11063 Administrator. If seeding the RNG on Win32 fails, quit.
11065 o Assert / crash bugs:
11066 - Refuse relay cells that claim to have a length larger than the
11067 maximum allowed. This prevents a potential attack that could read
11068 arbitrary memory (e.g. keys) from an exit server's process
11070 - If unofficial Tor clients connect and send weird TLS certs, our
11071 Tor server triggers an assert. Stop asserting, and start handling
11072 TLS errors better in other situations too.
11073 - Fix a race condition that can trigger an assert when we have a
11074 pending create cell and an OR connection attempt fails.
11077 - Use pthreads for worker processes rather than forking. This was
11078 forced because when we forked, we ended up wasting a lot of
11079 duplicate ram over time.
11080 - Also switch to foo_r versions of some library calls to allow
11081 reentry and threadsafeness.
11082 - Implement --disable-threads configure option. Disable threads on
11083 netbsd and openbsd by default, because they have no reentrant
11084 resolver functions (!), and on solaris since it has other
11086 - Fix possible bug on threading platforms (e.g. win32) which was
11087 leaking a file descriptor whenever a cpuworker or dnsworker died.
11088 - Fix a minor memory leak when somebody establishes an introduction
11089 point at your Tor server.
11090 - Fix possible memory leak in tor_lookup_hostname(). (Thanks to
11092 - Add ./configure --with-dmalloc option, to track memory leaks.
11093 - And try to free all memory on closing, so we can detect what
11096 o Protocol correctness:
11097 - When we've connected to an OR and handshaked but didn't like
11098 the result, we were closing the conn without sending destroy
11099 cells back for pending circuits. Now send those destroys.
11100 - Start sending 'truncated' cells back rather than destroy cells
11101 if the circuit closes in front of you. This means we won't have
11102 to abandon partially built circuits.
11103 - Handle changed router status correctly when dirserver reloads
11104 fingerprint file. We used to be dropping all unverified descriptors
11105 right then. The bug was hidden because we would immediately
11106 fetch a directory from another dirserver, which would include the
11107 descriptors we just dropped.
11108 - Revise tor-spec to add more/better stream end reasons.
11109 - Revise all calls to connection_edge_end to avoid sending 'misc',
11110 and to take errno into account where possible.
11111 - Client now retries when streams end early for 'hibernating' or
11112 'resource limit' reasons, rather than failing them.
11113 - Try to be more zealous about calling connection_edge_end when
11114 things go bad with edge conns in connection.c.
11116 o Robustness improvements:
11117 - Better handling for heterogeneous / unreliable nodes:
11118 - Annotate circuits with whether they aim to contain high uptime
11119 nodes and/or high capacity nodes. When building circuits, choose
11121 - This means that every single node in an intro rend circuit,
11122 not just the last one, will have a minimum uptime.
11123 - New config option LongLivedPorts to indicate application streams
11124 that will want high uptime circuits.
11125 - Servers reset uptime when a dir fetch entirely fails. This
11126 hopefully reflects stability of the server's network connectivity.
11127 - If somebody starts his tor server in Jan 2004 and then fixes his
11128 clock, don't make his published uptime be a year.
11129 - Reset published uptime when we wake up from hibernation.
11130 - Introduce a notion of 'internal' circs, which are chosen without
11131 regard to the exit policy of the last hop. Intro and rendezvous
11132 circs must be internal circs, to avoid leaking information. Resolve
11133 and connect streams can use internal circs if they want.
11134 - New circuit pooling algorithm: keep track of what destination ports
11135 we've used recently (start out assuming we'll want to use 80), and
11136 make sure to have enough circs around to satisfy these ports. Also
11137 make sure to have 2 internal circs around if we've required internal
11138 circs lately (and with high uptime if we've seen that lately too).
11139 - Turn addr_policy_compare from a tristate to a quadstate; this should
11140 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
11141 for google.com" problem.
11142 - When a client asks us for a dir mirror and we don't have one,
11143 launch an attempt to get a fresh one.
11144 - First cut at support for "create-fast" cells. Clients can use
11145 these when extending to their first hop, since the TLS already
11146 provides forward secrecy and authentication. Not enabled on
11149 o Reachability testing.
11150 - Your Tor server will automatically try to see if its ORPort and
11151 DirPort are reachable from the outside, and it won't upload its
11152 descriptor until it decides at least ORPort is reachable (when
11153 DirPort is not yet found reachable, publish it as zero).
11154 - When building testing circs for ORPort testing, use only
11155 high-bandwidth nodes, so fewer circuits fail.
11156 - Notice when our IP changes, and reset stats/uptime/reachability.
11157 - Authdirservers don't do ORPort reachability detection, since
11158 they're in clique mode, so it will be rare to find a server not
11159 already connected to them.
11160 - Authdirservers now automatically approve nodes running 0.1.0.2-rc
11164 - Now we allow two unverified servers with the same nickname
11165 but different keys. But if a nickname is verified, only that
11166 nickname+key are allowed.
11167 - If you're an authdirserver connecting to an address:port,
11168 and it's not the OR you were expecting, forget about that
11169 descriptor. If he *was* the one you were expecting, then forget
11170 about all other descriptors for that address:port.
11171 - Allow servers to publish descriptors from 12 hours in the future.
11172 Corollary: only whine about clock skew from the dirserver if
11173 he's a trusted dirserver (since now even verified servers could
11174 have quite wrong clocks).
11175 - Require servers that use the default dirservers to have public IP
11176 addresses. We have too many servers that are configured with private
11177 IPs and their admins never notice the log entries complaining that
11178 their descriptors are being rejected.
11180 o Efficiency improvements:
11181 - Use libevent. Now we can use faster async cores (like epoll, kpoll,
11182 and /dev/poll), and hopefully work better on Windows too.
11183 - Apple's OS X 10.4.0 ships with a broken kqueue API, and using
11184 kqueue on 10.3.9 causes kernel panics. Don't use kqueue on OS X.
11185 - Find libevent even if it's hiding in /usr/local/ and your
11186 CFLAGS and LDFLAGS don't tell you to look there.
11187 - Be able to link with libevent as a shared library (the default
11188 after 1.0d), even if it's hiding in /usr/local/lib and even
11189 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
11190 assuming you're running gcc. Otherwise fail and give a useful
11192 - Switch to a new buffer management algorithm, which tries to avoid
11193 reallocing and copying quite as much. In first tests it looks like
11194 it uses *more* memory on average, but less cpu.
11195 - Switch our internal buffers implementation to use a ring buffer,
11196 to hopefully improve performance for fast servers a lot.
11197 - Reenable the part of the code that tries to flush as soon as an
11198 OR outbuf has a full TLS record available. Perhaps this will make
11199 OR outbufs not grow as huge except in rare cases, thus saving lots
11200 of CPU time plus memory.
11201 - Improve performance for dirservers: stop re-parsing the whole
11202 directory every time you regenerate it.
11203 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
11204 it much faster to look up a circuit for each relay cell.
11205 - Remove most calls to assert_all_pending_dns_resolves_ok(),
11206 since they're eating our cpu on exit nodes.
11207 - Stop wasting time doing a case insensitive comparison for every
11208 dns name every time we do any lookup. Canonicalize the names to
11209 lowercase when you first see them.
11212 - Handle unavailable hidden services better. Handle slow or busy
11213 hidden services better.
11214 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
11215 circ as necessary, if there are any completed ones lying around
11216 when we try to launch one.
11217 - Make hidden services try to establish a rendezvous for 30 seconds
11218 after fetching the descriptor, rather than for n (where n=3)
11219 attempts to build a circuit.
11220 - Adjust maximum skew and age for rendezvous descriptors: let skew
11221 be 48 hours rather than 90 minutes.
11222 - Reject malformed .onion addresses rather then passing them on as
11223 normal web requests.
11226 - More Tor controller support. See
11227 http://tor.eff.org/doc/control-spec.txt for all the new features,
11228 including signals to emulate unix signals from any platform;
11229 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
11230 closestream; closecircuit; etc.
11231 - Encode hashed controller passwords in hex instead of base64,
11232 to make it easier to write controllers.
11233 - Revise control spec and implementation to allow all log messages to
11234 be sent to controller with their severities intact (suggested by
11235 Matt Edman). Disable debug-level logs while delivering a debug-level
11236 log to the controller, to prevent loop. Update TorControl to handle
11237 new log event types.
11239 o New config options/defaults:
11240 - Begin scrubbing sensitive strings from logs by default. Turn off
11241 the config option SafeLogging if you need to do debugging.
11242 - New exit policy: accept most low-numbered ports, rather than
11243 rejecting most low-numbered ports.
11244 - Put a note in the torrc about abuse potential with the default
11246 - Add support for CONNECTing through https proxies, with "HttpsProxy"
11248 - Add HttpProxyAuthenticator and HttpsProxyAuthenticator support
11249 based on patch from Adam Langley (basic auth only).
11250 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
11251 the fast servers that have been joining lately. (Clients are now
11252 willing to load balance over up to 2 MB of advertised bandwidth
11254 - New config option MaxAdvertisedBandwidth which lets you advertise
11255 a low bandwidthrate (to not attract as many circuits) while still
11256 allowing a higher bandwidthrate in reality.
11257 - Require BandwidthRate to be at least 20kB/s for servers.
11258 - Add a NoPublish config option, so you can be a server (e.g. for
11259 testing running Tor servers in other Tor networks) without
11260 publishing your descriptor to the primary dirservers.
11261 - Add a new AddressMap config directive to rewrite incoming socks
11262 addresses. This lets you, for example, declare an implicit
11263 required exit node for certain sites.
11264 - Add a new TrackHostExits config directive to trigger addressmaps
11265 for certain incoming socks addresses -- for sites that break when
11266 your exit keeps changing (based on patch from Mike Perry).
11267 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
11268 which describes how often we retry making new circuits if current
11269 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
11270 how long we're willing to make use of an already-dirty circuit.
11271 - Change compiled-in SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to
11272 a config option "ShutdownWaitLength" (when using kill -INT on
11274 - Fix an edge case in parsing config options: if they say "--"
11275 on the commandline, it's not a config option (thanks weasel).
11276 - New config option DirAllowPrivateAddresses for authdirservers.
11277 Now by default they refuse router descriptors that have non-IP or
11278 private-IP addresses.
11279 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
11280 smart" default value: low for servers and high for clients.
11281 - Some people were putting "Address " in their torrc, and they had
11282 a buggy resolver that resolved " " to 0.0.0.0. Oops.
11283 - If DataDir is ~/.tor, and that expands to /.tor, then default to
11284 LOCALSTATEDIR/tor instead.
11285 - Implement --verify-config command-line option to check if your torrc
11286 is valid without actually launching Tor.
11288 o Logging improvements:
11289 - When dirservers refuse a server descriptor, we now log its
11290 contactinfo, platform, and the poster's IP address.
11291 - Only warn once per nickname from add_nickname_list_to_smartlist()
11292 per failure, so an entrynode or exitnode choice that's down won't
11294 - When we're connecting to an OR and he's got a different nickname/key
11295 than we were expecting, only complain loudly if we're an OP or a
11296 dirserver. Complaining loudly to the OR admins just confuses them.
11297 - Whine at you if you're a server and you don't set your contactinfo.
11298 - Warn when exit policy implicitly allows local addresses.
11299 - Give a better warning when some other server advertises an
11300 ORPort that is actually an apache running ssl.
11301 - If we get an incredibly skewed timestamp from a dirserver mirror
11302 that isn't a verified OR, don't warn -- it's probably him that's
11304 - When a dirserver causes you to give a warn, mention which dirserver
11306 - Initialize libevent later in the startup process, so the logs are
11307 already established by the time we start logging libevent warns.
11308 - Use correct errno on win32 if libevent fails.
11309 - Check and warn about known-bad/slow libevent versions.
11310 - Stop warning about sigpipes in the logs. We're going to
11311 pretend that getting these occassionally is normal and fine.
11313 o New contrib scripts:
11314 - New experimental script tor/contrib/exitlist: a simple python
11315 script to parse directories and find Tor nodes that exit to listed
11317 - New experimental script tor/contrib/ExerciseServer.py (needs more
11318 work) that uses the controller interface to build circuits and
11319 fetch pages over them. This will help us bootstrap servers that
11320 have lots of capacity but haven't noticed it yet.
11321 - New experimental script tor/contrib/PathDemo.py (needs more work)
11322 that uses the controller interface to let you choose whole paths
11324 "<hostname>.<path,separated by dots>.<length of path>.path"
11325 - New contributed script "privoxy-tor-toggle" to toggle whether
11326 Privoxy uses Tor. Seems to be configured for Debian by default.
11327 - Have torctl.in/tor.sh.in check for location of su binary (needed
11331 - chdir() to your datadirectory at the *end* of the daemonize process,
11332 not the beginning. This was a problem because the first time you
11333 run tor, if your datadir isn't there, and you have runasdaemon set
11334 to 1, it will try to chdir to it before it tries to create it. Oops.
11335 - Fix several double-mark-for-close bugs, e.g. where we were finding
11336 a conn for a cell even if that conn is already marked for close.
11337 - Stop most cases of hanging up on a socks connection without sending
11339 - Fix a bug in the RPM package: set home directory for _tor to
11340 something more reasonable when first installing.
11341 - Stop putting nodename in the Platform string in server descriptors.
11342 It doesn't actually help, and it is confusing/upsetting some people.
11343 - When using preferred entry or exit nodes, ignore whether the
11344 circuit wants uptime or capacity. They asked for the nodes, they
11346 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
11347 artificially capped at 500kB.
11348 - Cache local dns resolves correctly even when they're .exit
11350 - If we're hibernating and we get a SIGINT, exit immediately.
11351 - tor-resolve requests were ignoring .exit if there was a working circuit
11352 they could use instead.
11353 - Pay more attention to the ClientOnly config option.
11354 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in certain
11355 installer screens; and don't put stuff into StartupItems unless
11356 the user asks you to.
11359 - Rewrite address "serifos.exit" to "externalIP.serifos.exit"
11360 rather than just rejecting it.
11361 - If our clock jumps forward by 100 seconds or more, assume something
11362 has gone wrong with our network and abandon all not-yet-used circs.
11363 - When an application is using socks5, give him the whole variety of
11364 potential socks5 responses (connect refused, host unreachable, etc),
11365 rather than just "success" or "failure".
11366 - A more sane version numbering system. See
11367 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
11368 - Change version parsing logic: a version is "obsolete" if it is not
11369 recommended and (1) there is a newer recommended version in the
11370 same series, or (2) there are no recommended versions in the same
11371 series, but there are some recommended versions in a newer series.
11372 A version is "new" if it is newer than any recommended version in
11374 - Report HTTP reasons to client when getting a response from directory
11375 servers -- so you can actually know what went wrong.
11376 - Reject odd-looking addresses at the client (e.g. addresses that
11377 contain a colon), rather than having the server drop them because
11379 - Stop publishing socksport in the directory, since it's not
11380 actually meant to be public. For compatibility, publish a 0 there
11382 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
11383 cookies to disk and doesn't log each web request to disk. (Thanks
11384 to Brett Carrington for pointing this out.)
11385 - Add OSX uninstall instructions. An actual uninstall script will
11387 - Add "opt hibernating 1" to server descriptor to make it clearer
11388 whether the server is hibernating.
11391 Changes in version 0.0.9.10 - 2005-06-16
11392 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
11393 - Refuse relay cells that claim to have a length larger than the
11394 maximum allowed. This prevents a potential attack that could read
11395 arbitrary memory (e.g. keys) from an exit server's process
11399 Changes in version 0.0.9.9 - 2005-04-23
11400 o Bugfixes on 0.0.9.x:
11401 - If unofficial Tor clients connect and send weird TLS certs, our
11402 Tor server triggers an assert. This release contains a minimal
11403 backport from the broader fix that we put into 0.1.0.4-rc.
11406 Changes in version 0.0.9.8 - 2005-04-07
11407 o Bugfixes on 0.0.9.x:
11408 - We have a bug that I haven't found yet. Sometimes, very rarely,
11409 cpuworkers get stuck in the 'busy' state, even though the cpuworker
11410 thinks of itself as idle. This meant that no new circuits ever got
11411 established. Here's a workaround to kill any cpuworker that's been
11412 busy for more than 100 seconds.
11415 Changes in version 0.0.9.7 - 2005-04-01
11416 o Bugfixes on 0.0.9.x:
11417 - Fix another race crash bug (thanks to Glenn Fink for reporting).
11418 - Compare identity to identity, not to nickname, when extending to
11419 a router not already in the directory. This was preventing us from
11420 extending to unknown routers. Oops.
11421 - Make sure to create OS X Tor user in <500 range, so we aren't
11422 creating actual system users.
11423 - Note where connection-that-hasn't-sent-end was marked, and fix
11424 a few really loud instances of this harmless bug (it's fixed more
11428 Changes in version 0.0.9.6 - 2005-03-24
11429 o Bugfixes on 0.0.9.x (crashes and asserts):
11430 - Add new end stream reasons to maintainance branch. Fix bug where
11431 reason (8) could trigger an assert. Prevent bug from recurring.
11432 - Apparently win32 stat wants paths to not end with a slash.
11433 - Fix assert triggers in assert_cpath_layer_ok(), where we were
11434 blowing away the circuit that conn->cpath_layer points to, then
11435 checking to see if the circ is well-formed. Backport check to make
11436 sure we dont use the cpath on a closed connection.
11437 - Prevent circuit_resume_edge_reading_helper() from trying to package
11438 inbufs for marked-for-close streams.
11439 - Don't crash on hup if your options->address has become unresolvable.
11440 - Some systems (like OS X) sometimes accept() a connection and tell
11441 you the remote host is 0.0.0.0:0. If this happens, due to some
11442 other mis-features, we get confused; so refuse the conn for now.
11444 o Bugfixes on 0.0.9.x (other):
11445 - Fix harmless but scary "Unrecognized content encoding" warn message.
11446 - Add new stream error reason: TORPROTOCOL reason means "you are not
11447 speaking a version of Tor I understand; say bye-bye to your stream."
11448 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
11449 into the future, now that we are more tolerant of skew. This
11450 resolves a bug where a Tor server would refuse to cache a directory
11451 because all the directories it gets are too far in the future;
11452 yet the Tor server never logs any complaints about clock skew.
11453 - Mac packaging magic: make man pages useable, and do not overwrite
11454 existing torrc files.
11455 - Make OS X log happily to /var/log/tor/tor.log
11458 Changes in version 0.0.9.5 - 2005-02-22
11459 o Bugfixes on 0.0.9.x:
11460 - Fix an assert race at exit nodes when resolve requests fail.
11461 - Stop picking unverified dir mirrors--it only leads to misery.
11462 - Patch from Matt Edman to make NT services work better. Service
11463 support is still not compiled into the executable by default.
11464 - Patch from Dmitri Bely so the Tor service runs better under
11465 the win32 SYSTEM account.
11466 - Make tor-resolve actually work (?) on Win32.
11467 - Fix a sign bug when getrlimit claims to have 4+ billion
11468 file descriptors available.
11469 - Stop refusing to start when bandwidthburst == bandwidthrate.
11470 - When create cells have been on the onion queue more than five
11471 seconds, just send back a destroy and take them off the list.
11474 Changes in version 0.0.9.4 - 2005-02-03
11475 o Bugfixes on 0.0.9:
11476 - Fix an assert bug that took down most of our servers: when
11477 a server claims to have 1 GB of bandwidthburst, don't
11479 - Don't crash as badly if we have spawned the max allowed number
11480 of dnsworkers, or we're out of file descriptors.
11481 - Block more file-sharing ports in the default exit policy.
11482 - MaxConn is now automatically set to the hard limit of max
11483 file descriptors we're allowed (ulimit -n), minus a few for
11485 - Give a clearer message when servers need to raise their
11486 ulimit -n when they start running out of file descriptors.
11487 - SGI Compatibility patches from Jan Schaumann.
11488 - Tolerate a corrupt cached directory better.
11489 - When a dirserver hasn't approved your server, list which one.
11490 - Go into soft hibernation after 95% of the bandwidth is used,
11491 not 99%. This is especially important for daily hibernators who
11492 have a small accounting max. Hopefully it will result in fewer
11493 cut connections when the hard hibernation starts.
11494 - Load-balance better when using servers that claim more than
11495 800kB/s of capacity.
11496 - Make NT services work (experimental, only used if compiled in).
11499 Changes in version 0.0.9.3 - 2005-01-21
11500 o Bugfixes on 0.0.9:
11501 - Backport the cpu use fixes from main branch, so busy servers won't
11502 need as much processor time.
11503 - Work better when we go offline and then come back, or when we
11504 run Tor at boot before the network is up. We do this by
11505 optimistically trying to fetch a new directory whenever an
11506 application request comes in and we think we're offline -- the
11507 human is hopefully a good measure of when the network is back.
11508 - Backport some minimal hidserv bugfixes: keep rend circuits open as
11509 long as you keep using them; actually publish hidserv descriptors
11510 shortly after they change, rather than waiting 20-40 minutes.
11511 - Enable Mac startup script by default.
11512 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
11513 - When you update AllowUnverifiedNodes or FirewallPorts via the
11514 controller's setconf feature, we were always appending, never
11516 - When you update HiddenServiceDir via setconf, it was screwing up
11517 the order of reading the lines, making it fail.
11518 - Do not rewrite a cached directory back to the cache; otherwise we
11519 will think it is recent and not fetch a newer one on startup.
11520 - Workaround for webservers that lie about Content-Encoding: Tor
11521 now tries to autodetect compressed directories and compression
11522 itself. This lets us Proxypass dir fetches through apache.
11525 Changes in version 0.0.9.2 - 2005-01-04
11526 o Bugfixes on 0.0.9 (crashes and asserts):
11527 - Fix an assert on startup when the disk is full and you're logging
11529 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
11530 style address, then we'd crash.
11531 - Fix an assert trigger when the running-routers string we get from
11532 a dirserver is broken.
11533 - Make worker threads start and run on win32. Now win32 servers
11535 - Bandaid (not actually fix, but now it doesn't crash) an assert
11536 where the dns worker dies mysteriously and the main Tor process
11537 doesn't remember anything about the address it was resolving.
11539 o Bugfixes on 0.0.9 (Win32):
11540 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
11541 name out of the warning/assert messages.
11542 - Fix a superficial "unhandled error on read" bug on win32.
11543 - The win32 installer no longer requires a click-through for our
11544 license, since our Free Software license grants rights but does not
11546 - Win32: When connecting to a dirserver fails, try another one
11547 immediately. (This was already working for non-win32 Tors.)
11548 - Stop trying to parse $HOME on win32 when hunting for default
11550 - Make tor-resolve.c work on win32 by calling network_init().
11552 o Bugfixes on 0.0.9 (other):
11553 - Make 0.0.9.x build on Solaris again.
11554 - Due to a fencepost error, we were blowing away the \n when reporting
11555 confvalue items in the controller. So asking for multiple config
11556 values at once couldn't work.
11557 - When listing circuits that are pending on an opening OR connection,
11558 if we're an OR we were listing circuits that *end* at us as
11559 being pending on every listener, dns/cpu worker, etc. Stop that.
11560 - Dirservers were failing to create 'running-routers' or 'directory'
11561 strings if we had more than some threshold of routers. Fix them so
11562 they can handle any number of routers.
11563 - Fix a superficial "Duplicate mark for close" bug.
11564 - Stop checking for clock skew for OR connections, even for servers.
11565 - Fix a fencepost error that was chopping off the last letter of any
11566 nickname that is the maximum allowed nickname length.
11567 - Update URLs in log messages so they point to the new website.
11568 - Fix a potential problem in mangling server private keys while
11569 writing to disk (not triggered yet, as far as we know).
11570 - Include the licenses for other free software we include in Tor,
11571 now that we're shipping binary distributions more regularly.
11574 Changes in version 0.0.9.1 - 2004-12-15
11575 o Bugfixes on 0.0.9:
11576 - Make hibernation actually work.
11577 - Make HashedControlPassword config option work.
11578 - When we're reporting event circuit status to a controller,
11579 don't use the stream status code.
11582 Changes in version 0.0.9 - 2004-12-12
11583 o Bugfixes on 0.0.8.1 (Crashes and asserts):
11584 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
11585 write() call will fail and we handle it there.
11586 - When we run out of disk space, or other log writing error, don't
11587 crash. Just stop logging to that log and continue.
11588 - Fix isspace() and friends so they still make Solaris happy
11589 but also so they don't trigger asserts on win32.
11590 - Fix assert failure on malformed socks4a requests.
11591 - Fix an assert bug where a hidden service provider would fail if
11592 the first hop of his rendezvous circuit was down.
11593 - Better handling of size_t vs int, so we're more robust on 64
11596 o Bugfixes on 0.0.8.1 (Win32):
11597 - Make windows sockets actually non-blocking (oops), and handle
11598 win32 socket errors better.
11599 - Fix parse_iso_time on platforms without strptime (eg win32).
11600 - win32: when being multithreaded, leave parent fdarray open.
11601 - Better handling of winsock includes on non-MSV win32 compilers.
11602 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
11604 - Make unit tests work on win32.
11606 o Bugfixes on 0.0.8.1 (Path selection and streams):
11607 - Calculate timeout for waiting for a connected cell from the time
11608 we sent the begin cell, not from the time the stream started. If
11609 it took a long time to establish the circuit, we would time out
11610 right after sending the begin cell.
11611 - Fix router_compare_addr_to_addr_policy: it was not treating a port
11612 of * as always matching, so we were picking reject *:* nodes as
11613 exit nodes too. Oops.
11614 - When read() failed on a stream, we would close it without sending
11615 back an end. So 'connection refused' would simply be ignored and
11616 the user would get no response.
11617 - Stop a sigpipe: when an 'end' cell races with eof from the app,
11618 we shouldn't hold-open-until-flush if the eof arrived first.
11619 - Let resolve conns retry/expire also, rather than sticking around
11621 - Fix more dns related bugs: send back resolve_failed and end cells
11622 more reliably when the resolve fails, rather than closing the
11623 circuit and then trying to send the cell. Also attach dummy resolve
11624 connections to a circuit *before* calling dns_resolve(), to fix
11625 a bug where cached answers would never be sent in RESOLVED cells.
11627 o Bugfixes on 0.0.8.1 (Circuits):
11628 - Finally fix a bug that's been plaguing us for a year:
11629 With high load, circuit package window was reaching 0. Whenever
11630 we got a circuit-level sendme, we were reading a lot on each
11631 socket, but only writing out a bit. So we would eventually reach
11632 eof. This would be noticed and acted on even when there were still
11633 bytes sitting in the inbuf.
11634 - Use identity comparison, not nickname comparison, to choose which
11635 half of circuit-ID-space each side gets to use. This is needed
11636 because sometimes we think of a router as a nickname, and sometimes
11637 as a hex ID, and we can't predict what the other side will do.
11639 o Bugfixes on 0.0.8.1 (Other):
11640 - Fix a whole slew of memory leaks.
11641 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
11642 - If we are using select, make sure we stay within FD_SETSIZE.
11643 - When poll() is interrupted, we shouldn't believe the revents values.
11644 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
11645 and smartlist_len, which are two major profiling offenders.
11646 - If do_hup fails, actually notice.
11647 - Flush the log file descriptor after we print "Tor opening log file",
11648 so we don't see those messages days later.
11649 - Hidden service operators now correctly handle version 1 style
11650 INTRODUCE1 cells (nobody generates them still, so not a critical
11652 - Handle more errnos from accept() without closing the listener.
11653 Some OpenBSD machines were closing their listeners because
11654 they ran out of file descriptors.
11655 - Some people had wrapped their tor client/server in a script
11656 that would restart it whenever it died. This did not play well
11657 with our "shut down if your version is obsolete" code. Now people
11658 don't fetch a new directory if their local cached version is
11660 - Make our autogen.sh work on ksh as well as bash.
11661 - Better torrc example lines for dirbindaddress and orbindaddress.
11662 - Improved bounds checking on parsed ints (e.g. config options and
11663 the ones we find in directories.)
11664 - Stop using separate defaults for no-config-file and
11665 empty-config-file. Now you have to explicitly turn off SocksPort,
11666 if you don't want it open.
11667 - We were starting to daemonize before we opened our logs, so if
11668 there were any problems opening logs, we would complain to stderr,
11669 which wouldn't work, and then mysteriously exit.
11670 - If a verified OR connects to us before he's uploaded his descriptor,
11671 or we verify him and hup but he still has the original TLS
11672 connection, then conn->nickname is still set like he's unverified.
11674 o Code security improvements, inspired by Ilja:
11675 - tor_snprintf wrapper over snprintf with consistent (though not C99)
11677 - Replace sprintf with tor_snprintf. (I think they were all safe, but
11679 - Replace strcpy/strncpy with strlcpy in more places.
11680 - Avoid strcat; use tor_snprintf or strlcat instead.
11682 o Features (circuits and streams):
11683 - New circuit building strategy: keep a list of ports that we've
11684 used in the past 6 hours, and always try to have 2 circuits open
11685 or on the way that will handle each such port. Seed us with port
11686 80 so web users won't complain that Tor is "slow to start up".
11687 - Make kill -USR1 dump more useful stats about circuits.
11688 - When warning about retrying or giving up, print the address, so
11689 the user knows which one it's talking about.
11690 - If you haven't used a clean circuit in an hour, throw it away,
11691 just to be on the safe side. (This means after 6 hours a totally
11692 unused Tor client will have no circuits open.)
11693 - Support "foo.nickname.exit" addresses, to let Alice request the
11694 address "foo" as viewed by exit node "nickname". Based on a patch
11695 from Geoff Goodell.
11696 - If your requested entry or exit node has advertised bandwidth 0,
11698 - Be more greedy about filling up relay cells -- we try reading again
11699 once we've processed the stuff we read, in case enough has arrived
11700 to fill the last cell completely.
11701 - Refuse application socks connections to port 0.
11702 - Use only 0.0.9pre1 and later servers for resolve cells.
11704 o Features (bandwidth):
11705 - Hibernation: New config option "AccountingMax" lets you
11706 set how many bytes per month (in each direction) you want to
11707 allow your server to consume. Rather than spreading those
11708 bytes out evenly over the month, we instead hibernate for some
11709 of the month and pop up at a deterministic time, work until
11710 the bytes are consumed, then hibernate again. Config option
11711 "MonthlyAccountingStart" lets you specify which day of the month
11712 your billing cycle starts on.
11713 - Implement weekly/monthly/daily accounting: now you specify your
11714 hibernation properties by
11715 AccountingMax N bytes|KB|MB|GB|TB
11716 AccountingStart day|week|month [day] HH:MM
11717 Defaults to "month 1 0:00".
11718 - Let bandwidth and interval config options be specified as 5 bytes,
11719 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
11721 o Features (directories):
11722 - New "router-status" line in directory, to better bind each verified
11723 nickname to its identity key.
11724 - Clients can ask dirservers for /dir.z to get a compressed version
11725 of the directory. Only works for servers running 0.0.9, of course.
11726 - Make clients cache directories and use them to seed their router
11727 lists at startup. This means clients have a datadir again.
11728 - Respond to content-encoding headers by trying to uncompress as
11730 - Clients and servers now fetch running-routers; cache
11731 running-routers; compress running-routers; serve compressed
11733 - Make moria2 advertise a dirport of 80, so people behind firewalls
11734 will be able to get a directory.
11735 - Http proxy support
11736 - Dirservers translate requests for http://%s:%d/x to /x
11737 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
11738 be routed through this host.
11739 - Clients ask for /tor/x rather than /x for new enough dirservers.
11740 This way we can one day coexist peacefully with apache.
11741 - Clients specify a "Host: %s%d" http header, to be compatible
11742 with more proxies, and so running squid on an exit node can work.
11743 - Protect dirservers from overzealous descriptor uploading -- wait
11744 10 seconds after directory gets dirty, before regenerating.
11746 o Features (packages and install):
11747 - Add NSI installer contributed by J Doe.
11748 - Apply NT service patch from Osamu Fujino. Still needs more work.
11749 - Commit VC6 and VC7 workspace/project files.
11750 - Commit a tor.spec for making RPM files, with help from jbash.
11751 - Add contrib/torctl.in contributed by Glenn Fink.
11752 - Make expand_filename handle ~ and ~username.
11753 - Use autoconf to enable largefile support where necessary. Use
11754 ftello where available, since ftell can fail at 2GB.
11755 - Ship src/win32/ in the tarball, so people can use it to build.
11756 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
11759 o Features (ui controller):
11760 - Control interface: a separate program can now talk to your
11761 client/server over a socket, and get/set config options, receive
11762 notifications of circuits and streams starting/finishing/dying,
11763 bandwidth used, etc. The next step is to get some GUIs working.
11764 Let us know if you want to help out. See doc/control-spec.txt .
11765 - Ship a contrib/tor-control.py as an example script to interact
11766 with the control port.
11767 - "tor --hash-password zzyxz" will output a salted password for
11768 use in authenticating to the control interface.
11769 - Implement the control-spec's SAVECONF command, to write your
11770 configuration to torrc.
11771 - Get cookie authentication for the controller closer to working.
11772 - When set_conf changes our server descriptor, upload a new copy.
11773 But don't upload it too often if there are frequent changes.
11775 o Features (config and command-line):
11776 - Deprecate unofficial config option abbreviations, and abbreviations
11777 not on the command line.
11778 - Configuration infrastructure support for warning on obsolete
11780 - Give a slightly more useful output for "tor -h".
11781 - Break DirFetchPostPeriod into:
11782 - DirFetchPeriod for fetching full directory,
11783 - StatusFetchPeriod for fetching running-routers,
11784 - DirPostPeriod for posting server descriptor,
11785 - RendPostPeriod for posting hidden service descriptors.
11786 - New log format in config:
11787 "Log minsev[-maxsev] stdout|stderr|syslog" or
11788 "Log minsev[-maxsev] file /var/foo"
11789 - DirPolicy config option, to let people reject incoming addresses
11790 from their dirserver.
11791 - "tor --list-fingerprint" will list your identity key fingerprint
11793 - Make tor --version --version dump the cvs Id of every file.
11794 - New 'MyFamily nick1,...' config option for a server to
11795 specify other servers that shouldn't be used in the same circuit
11796 with it. Only believed if nick1 also specifies us.
11797 - New 'NodeFamily nick1,nick2,...' config option for a client to
11798 specify nodes that it doesn't want to use in the same circuit.
11799 - New 'Redirectexit pattern address:port' config option for a
11800 server to redirect exit connections, e.g. to a local squid.
11801 - Add "pass" target for RedirectExit, to make it easier to break
11802 out of a sequence of RedirectExit rules.
11803 - Make the dirservers file obsolete.
11804 - Include a dir-signing-key token in directories to tell the
11805 parsing entity which key is being used to sign.
11806 - Remove the built-in bulky default dirservers string.
11807 - New config option "Dirserver %s:%d [fingerprint]", which can be
11808 repeated as many times as needed. If no dirservers specified,
11809 default to moria1,moria2,tor26.
11810 - Make 'Routerfile' config option obsolete.
11811 - Discourage people from setting their dirfetchpostperiod more often
11812 than once per minute.
11814 o Features (other):
11815 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
11816 get back to normal.)
11817 - Accept *:706 (silc) in default exit policy.
11818 - Implement new versioning format for post 0.1.
11819 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
11820 log more informatively.
11821 - Check clock skew for verified servers, but allow unverified
11822 servers and clients to have any clock skew.
11823 - Make sure the hidden service descriptors are at a random offset
11824 from each other, to hinder linkability.
11825 - Clients now generate a TLS cert too, in preparation for having
11826 them act more like real nodes.
11827 - Add a pure-C tor-resolve implementation.
11828 - Use getrlimit and friends to ensure we can reach MaxConn (currently
11829 1024) file descriptors.
11830 - Raise the max dns workers from 50 to 100.
11833 Changes in version 0.0.8.1 - 2004-10-13
11835 - Fix a seg fault that can be triggered remotely for Tor
11836 clients/servers with an open dirport.
11837 - Fix a rare assert trigger, where routerinfos for entries in
11838 our cpath would expire while we're building the path.
11839 - Fix a bug in OutboundBindAddress so it (hopefully) works.
11840 - Fix a rare seg fault for people running hidden services on
11841 intermittent connections.
11842 - Fix a bug in parsing opt keywords with objects.
11843 - Fix a stale pointer assert bug when a stream detaches and
11845 - Fix a string format vulnerability (probably not exploitable)
11846 in reporting stats locally.
11847 - Fix an assert trigger: sometimes launching circuits can fail
11848 immediately, e.g. because too many circuits have failed recently.
11849 - Fix a compile warning on 64 bit platforms.
11852 Changes in version 0.0.8 - 2004-08-25
11854 - Made our unit tests compile again on OpenBSD 3.5, and tor
11855 itself compile again on OpenBSD on a sparc64.
11856 - We were neglecting milliseconds when logging on win32, so
11857 everything appeared to happen at the beginning of each second.
11858 - Check directory signature _before_ you decide whether you're
11859 you're running an obsolete version and should exit.
11860 - Check directory signature _before_ you parse the running-routers
11861 list to decide who's running.
11862 - Check return value of fclose while writing to disk, so we don't
11863 end up with broken files when servers run out of disk space.
11864 - Port it to SunOS 5.9 / Athena
11865 - Fix two bugs in saving onion keys to disk when rotating, so
11866 hopefully we'll get fewer people using old onion keys.
11867 - Remove our mostly unused -- and broken -- hex_encode()
11868 function. Use base16_encode() instead. (Thanks to Timo Lindfors
11869 for pointing out this bug.)
11870 - Only pick and establish intro points after we've gotten a
11872 - Fix assert triggers: if the other side returns an address 0.0.0.0,
11873 don't put it into the client dns cache.
11874 - If a begin failed due to exit policy, but we believe the IP
11875 address should have been allowed, switch that router to exitpolicy
11876 reject *:* until we get our next directory.
11878 o Protocol changes:
11879 - 'Extend' relay cell payloads now include the digest of the
11880 intended next hop's identity key. Now we can verify that we're
11881 extending to the right router, and also extend to routers we
11882 hadn't heard of before.
11885 - Tor nodes can now act as relays (with an advertised ORPort)
11886 without being manually verified by the dirserver operators.
11887 - Uploaded descriptors of unverified routers are now accepted
11888 by the dirservers, and included in the directory.
11889 - Verified routers are listed by nickname in the running-routers
11890 list; unverified routers are listed as "$<fingerprint>".
11891 - We now use hash-of-identity-key in most places rather than
11892 nickname or addr:port, for improved security/flexibility.
11893 - AllowUnverifiedNodes config option to let circuits choose no-name
11894 routers in entry,middle,exit,introduction,rendezvous positions.
11895 Allow middle and rendezvous positions by default.
11896 - When picking unverified routers, skip those with low uptime and/or
11897 low bandwidth, depending on what properties you care about.
11898 - ClientOnly option for nodes that never want to become servers.
11899 - Directory caching.
11900 - "AuthoritativeDir 1" option for the official dirservers.
11901 - Now other nodes (clients and servers) will cache the latest
11902 directory they've pulled down.
11903 - They can enable their DirPort to serve it to others.
11904 - Clients will pull down a directory from any node with an open
11905 DirPort, and check the signature/timestamp correctly.
11906 - Authoritative dirservers now fetch directories from other
11907 authdirservers, to stay better synced.
11908 - Running-routers list tells who's down also, along with noting
11909 if they're verified (listed by nickname) or unverified (listed
11911 - Allow dirservers to serve running-router list separately.
11912 This isn't used yet.
11913 - You can now fetch $DIRURL/running-routers to get just the
11914 running-routers line, not the whole descriptor list. (But
11915 clients don't use this yet.)
11916 - Clients choose nodes proportional to advertised bandwidth.
11917 - Clients avoid using nodes with low uptime as introduction points.
11918 - Handle servers with dynamic IP addresses: don't just replace
11919 options->Address with the resolved one at startup, and
11920 detect our address right before we make a routerinfo each time.
11921 - 'FascistFirewall' option to pick dirservers and ORs on specific
11922 ports; plus 'FirewallPorts' config option to tell FascistFirewall
11923 which ports are open. (Defaults to 80,443)
11924 - Try other dirservers immediately if the one you try is down. This
11925 should tolerate down dirservers better now.
11926 - ORs connect-on-demand to other ORs
11927 - If you get an extend cell to an OR you're not connected to,
11928 connect, handshake, and forward the create cell.
11929 - The authoritative dirservers stay connected to everybody,
11930 and everybody stays connected to 0.0.7 servers, but otherwise
11931 clients/servers expire unused connections after 5 minutes.
11932 - When servers get a sigint, they delay 30 seconds (refusing new
11933 connections) then exit. A second sigint causes immediate exit.
11934 - File and name management:
11935 - Look for .torrc if no CONFDIR "torrc" is found.
11936 - If no datadir is defined, then choose, make, and secure ~/.tor
11938 - If torrc not found, exitpolicy reject *:*.
11939 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
11940 - If no nickname is defined, derive default from hostname.
11941 - Rename secret key files, e.g. identity.key -> secret_id_key,
11942 to discourage people from mailing their identity key to tor-ops.
11943 - Refuse to build a circuit before the directory has arrived --
11944 it won't work anyway, since you won't know the right onion keys
11946 - Parse tor version numbers so we can do an is-newer-than check
11947 rather than an is-in-the-list check.
11948 - New socks command 'resolve', to let us shim gethostbyname()
11950 - A 'tor_resolve' script to access the socks resolve functionality.
11951 - A new socks-extensions.txt doc file to describe our
11952 interpretation and extensions to the socks protocols.
11953 - Add a ContactInfo option, which gets published in descriptor.
11954 - Write tor version at the top of each log file
11955 - New docs in the tarball:
11957 - Document that you should proxy your SSL traffic too.
11958 - Log a warning if the user uses an unsafe socks variant, so people
11959 are more likely to learn about privoxy or socat.
11960 - Log a warning if you're running an unverified server, to let you
11961 know you might want to get it verified.
11962 - Change the default exit policy to reject the default edonkey,
11963 kazaa, gnutella ports.
11964 - Add replace_file() to util.[ch] to handle win32's rename().
11965 - Publish OR uptime in descriptor (and thus in directory) too.
11966 - Remember used bandwidth (both in and out), and publish 15-minute
11967 snapshots for the past day into our descriptor.
11968 - Be more aggressive about trying to make circuits when the network
11969 has changed (e.g. when you unsuspend your laptop).
11970 - Check for time skew on http headers; report date in response to
11972 - If the entrynode config line has only one node, don't pick it as
11974 - Add strict{entry|exit}nodes config options. If set to 1, then
11975 we refuse to build circuits that don't include the specified entry
11977 - OutboundBindAddress config option, to bind to a specific
11978 IP address for outgoing connect()s.
11979 - End truncated log entries (e.g. directories) with "[truncated]".
11982 Changes in version 0.0.7.3 - 2004-08-12
11983 o Stop dnsworkers from triggering an assert failure when you
11984 ask them to resolve the host "".
11987 Changes in version 0.0.7.2 - 2004-07-07
11988 o A better fix for the 0.0.0.0 problem, that will hopefully
11989 eliminate the remaining related assertion failures.
11992 Changes in version 0.0.7.1 - 2004-07-04
11993 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
11994 since internally we use 0.0.0.0 to signify "not yet resolved".
11997 Changes in version 0.0.7 - 2004-06-07
11998 o Fixes for crashes and other obnoxious bugs:
11999 - Fix an epipe bug: sometimes when directory connections failed
12000 to connect, we would give them a chance to flush before closing
12002 - When we detached from a circuit because of resolvefailed, we
12003 would immediately try the same circuit twice more, and then
12004 give up on the resolve thinking we'd tried three different
12006 - Limit the number of intro circuits we'll attempt to build for a
12007 hidden service per 15-minute period.
12008 - Check recommended-software string *early*, before actually parsing
12009 the directory. Thus we can detect an obsolete version and exit,
12010 even if the new directory format doesn't parse.
12011 o Fixes for security bugs:
12012 - Remember which nodes are dirservers when you startup, and if a
12013 random OR enables his dirport, don't automatically assume he's
12014 a trusted dirserver.
12016 - Directory connections were asking the wrong poll socket to
12017 start writing, and not asking themselves to start writing.
12018 - When we detached from a circuit because we sent a begin but
12019 didn't get a connected, we would use it again the first time;
12020 but after that we would correctly switch to a different one.
12021 - Stop warning when the first onion decrypt attempt fails; they
12022 will sometimes legitimately fail now that we rotate keys.
12023 - Override unaligned-access-ok check when $host_cpu is ia64 or
12024 arm. Apparently they allow it but the kernel whines.
12025 - Dirservers try to reconnect periodically too, in case connections
12027 - Fix some memory leaks in directory servers.
12028 - Allow backslash in Win32 filenames.
12029 - Made Tor build complain-free on FreeBSD, hopefully without
12030 breaking other BSD builds. We'll see.
12031 - Check directory signatures based on name of signer, not on whom
12032 we got the directory from. This will let us cache directories more
12034 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
12037 - Doxygen markup on all functions and global variables.
12038 - Make directory functions update routerlist, not replace it. So
12039 now directory disagreements are not so critical a problem.
12040 - Remove the upper limit on number of descriptors in a dirserver's
12041 directory (not that we were anywhere close).
12042 - Allow multiple logfiles at different severity ranges.
12043 - Allow *BindAddress to specify ":port" rather than setting *Port
12044 separately. Allow multiple instances of each BindAddress config
12045 option, so you can bind to multiple interfaces if you want.
12046 - Allow multiple exit policy lines, which are processed in order.
12047 Now we don't need that huge line with all the commas in it.
12048 - Enable accept/reject policies on SOCKS connections, so you can bind
12049 to 0.0.0.0 but still control who can use your OP.
12050 - Updated the man page to reflect these features.
12053 Changes in version 0.0.6.2 - 2004-05-16
12054 o Our integrity-checking digest was checking only the most recent cell,
12055 not the previous cells like we'd thought.
12056 Thanks to Stefan Mark for finding the flaw!
12059 Changes in version 0.0.6.1 - 2004-05-06
12060 o Fix two bugs in our AES counter-mode implementation (this affected
12061 onion-level stream encryption, but not TLS-level). It turns
12062 out we were doing something much more akin to a 16-character
12063 polyalphabetic cipher. Oops.
12064 Thanks to Stefan Mark for finding the flaw!
12065 o Retire moria3 as a directory server, and add tor26 as a directory
12069 Changes in version 0.0.6 - 2004-05-02
12071 - Hidden services and rendezvous points are implemented. Go to
12072 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
12073 hidden services. (This only works via a socks4a proxy such as
12074 Privoxy, and currently it's quite slow.)
12075 - We now rotate link (tls context) keys and onion keys.
12076 - CREATE cells now include oaep padding, so you can tell
12077 if you decrypted them correctly.
12078 - Retry stream correctly when we fail to connect because of
12079 exit-policy-reject (should try another) or can't-resolve-address.
12080 - When we hup a dirserver and we've *removed* a server from the
12081 approved-routers list, now we remove that server from the
12082 in-memory directories too.
12083 - Add bandwidthburst to server descriptor.
12084 - Directories now say which dirserver signed them.
12085 - Use a tor_assert macro that logs failed assertions too.
12086 - Since we don't support truncateds much, don't bother sending them;
12087 just close the circ.
12088 - Fetch randomness from /dev/urandom better (not via fopen/fread)
12089 - Better debugging for tls errors
12090 - Set Content-Type on the directory and hidserv descriptor.
12091 - Remove IVs from cipher code, since AES-ctr has none.
12093 - Fix an assert trigger for exit nodes that's been plaguing us since
12094 the days of 0.0.2prexx (thanks weasel!)
12095 - Fix a bug where we were closing tls connections intermittently.
12096 It turns out openssl keeps its errors around -- so if an error
12097 happens, and you don't ask about it, and then another openssl
12098 operation happens and succeeds, and you ask if there was an error,
12099 it tells you about the first error.
12100 - Fix a bug that's been lurking since 27 may 03 (!)
12101 When passing back a destroy cell, we would use the wrong circ id.
12102 - Don't crash if a conn that sent a begin has suddenly lost its circuit.
12103 - Some versions of openssl have an SSL_pending function that erroneously
12104 returns bytes when there is a non-application record pending.
12105 - Win32 fixes. Tor now compiles on win32 with no warnings/errors.
12106 o We were using an array of length zero in a few places.
12107 o Win32's gethostbyname can't resolve an IP to an IP.
12108 o Win32's close can't close a socket.
12109 o Handle windows socket errors correctly.
12111 - check for <sys/limits.h> so we build on FreeBSD again, and
12112 <machine/limits.h> for NetBSD.
12115 Changes in version 0.0.5 - 2004-03-30
12116 o Install torrc as torrc.sample -- we no longer clobber your
12118 o Fix mangled-state bug in directory fetching (was causing sigpipes).
12119 o Only build circuits after we've fetched the directory: clients were
12120 using only the directory servers before they'd fetched a directory.
12121 This also means longer startup time; so it goes.
12122 o Fix an assert trigger where an OP would fail to handshake, and we'd
12123 expect it to have a nickname.
12124 o Work around a tsocks bug: do a socks reject when AP connection dies
12125 early, else tsocks goes into an infinite loop.
12126 o Hold socks connection open until reply is flushed (if possible)
12127 o Make exit nodes resolve IPs to IPs immediately, rather than asking
12128 the dns farm to do it.
12129 o Fix c99 aliasing warnings in rephist.c
12130 o Don't include server descriptors that are older than 24 hours in the
12132 o Give socks 'reject' replies their whole 15s to attempt to flush,
12133 rather than seeing the 60s timeout and assuming the flush had failed.
12134 o Clean automake droppings from the cvs repository
12135 o Add in a 'notice' log level for things the operator should hear
12136 but that aren't warnings
12139 Changes in version 0.0.4 - 2004-03-26
12140 o When connecting to a dirserver or OR and the network is down,
12144 Changes in version 0.0.3 - 2004-03-26
12145 o Warn and fail if server chose a nickname with illegal characters
12146 o Port to Solaris and Sparc:
12147 - include missing header fcntl.h
12148 - have autoconf find -lsocket -lnsl automatically
12149 - deal with hardware word alignment
12150 - make uname() work (solaris has a different return convention)
12151 - switch from using signal() to sigaction()
12152 o Preliminary work on reputation system:
12153 - Keep statistics on success/fail of connect attempts; they're published
12154 by kill -USR1 currently.
12155 - Add a RunTesting option to try to learn link state by creating test
12156 circuits, even when SocksPort is off.
12157 - Remove unused open circuits when there are too many.
12160 Changes in version 0.0.2 - 2004-03-19
12161 - Include strlcpy and strlcat for safer string ops
12162 - define INADDR_NONE so we compile (but still not run) on solaris
12165 Changes in version 0.0.2pre27 - 2004-03-14
12167 - Allow internal tor networks (we were rejecting internal IPs,
12168 now we allow them if they're set explicitly).
12169 - And fix a few endian issues.
12172 Changes in version 0.0.2pre26 - 2004-03-14
12174 - If a stream times out after 15s without a connected cell, don't
12175 try that circuit again: try a new one.
12176 - Retry streams at most 4 times. Then give up.
12177 - When a dirserver gets a descriptor from an unknown router, it
12178 logs its fingerprint (so the dirserver operator can choose to
12179 accept it even without mail from the server operator).
12180 - Inform unapproved servers when we reject their descriptors.
12181 - Make tor build on Windows again. It works as a client, who knows
12183 - Clearer instructions in the torrc for how to set up a server.
12184 - Be more efficient about reading fd's when our global token bucket
12185 (used for rate limiting) becomes empty.
12187 - Stop asserting that computers always go forward in time. It's
12189 - When we sent a cell (e.g. destroy) and then marked an OR connection
12190 expired, we might close it before finishing a flush if the other
12191 side isn't reading right then.
12192 - Don't allow dirservers to start if they haven't defined
12193 RecommendedVersions
12194 - We were caching transient dns failures. Oops.
12195 - Prevent servers from publishing an internal IP as their address.
12196 - Address a strcat vulnerability in circuit.c
12199 Changes in version 0.0.2pre25 - 2004-03-04
12201 - Put the OR's IP in its router descriptor, not its fqdn. That way
12202 we'll stop being stalled by gethostbyname for nodes with flaky dns,
12205 - If the user typed in an address that didn't resolve, the server
12209 Changes in version 0.0.2pre24 - 2004-03-03
12211 - Fix an assertion failure in dns.c, where we were trying to dequeue
12212 a pending dns resolve even if it wasn't pending
12213 - Fix a spurious socks5 warning about still trying to write after the
12214 connection is finished.
12215 - Hold certain marked_for_close connections open until they're finished
12216 flushing, rather than losing bytes by closing them too early.
12217 - Correctly report the reason for ending a stream
12218 - Remove some duplicate calls to connection_mark_for_close
12219 - Put switch_id and start_daemon earlier in the boot sequence, so it
12220 will actually try to chdir() to options.DataDirectory
12221 - Make 'make test' exit(1) if a test fails; fix some unit tests
12222 - Make tor fail when you use a config option it doesn't know about,
12223 rather than warn and continue.
12224 - Make --version work
12225 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
12228 Changes in version 0.0.2pre23 - 2004-02-29
12230 - Print a statement when the first circ is finished, so the user
12231 knows it's working.
12232 - If a relay cell is unrecognized at the end of the circuit,
12233 send back a destroy. (So attacks to mutate cells are more
12235 - New config option 'excludenodes' to avoid certain nodes for circuits.
12236 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
12237 so you can collect coredumps there.
12239 - Fix a bug in tls flushing where sometimes data got wedged and
12240 didn't flush until more data got sent. Hopefully this bug was
12241 a big factor in the random delays we were seeing.
12242 - Make 'connected' cells include the resolved IP, so the client
12243 dns cache actually gets populated.
12244 - Disallow changing from ORPort=0 to ORPort>0 on hup.
12245 - When we time-out on a stream and detach from the circuit, send an
12246 end cell down it first.
12247 - Only warn about an unknown router (in exitnodes, entrynodes,
12248 excludenodes) after we've fetched a directory.
12251 Changes in version 0.0.2pre22 - 2004-02-26
12253 - Servers publish less revealing uname information in descriptors.
12254 - More memory tracking and assertions, to crash more usefully when
12256 - If the default torrc isn't there, just use some default defaults.
12257 Plus provide an internal dirservers file if they don't have one.
12258 - When the user tries to use Tor as an http proxy, give them an http
12259 501 failure explaining that we're a socks proxy.
12260 - Dump a new router.desc on hup, to help confused people who change
12261 their exit policies and then wonder why router.desc doesn't reflect
12263 - Clean up the generic tor.sh init script that we ship with.
12265 - If the exit stream is pending on the resolve, and a destroy arrives,
12266 then the stream wasn't getting removed from the pending list. I
12267 think this was the one causing recent server crashes.
12268 - Use a more robust poll on OSX 10.3, since their poll is flaky.
12269 - When it couldn't resolve any dirservers, it was useless from then on.
12270 Now it reloads the RouterFile (or default dirservers) if it has no
12272 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
12273 many users don't even *have* a /usr/local/sbin/.
12276 Changes in version 0.0.2pre21 - 2004-02-18
12278 - There's a ChangeLog file that actually reflects the changelog.
12279 - There's a 'torify' wrapper script, with an accompanying
12280 tor-tsocks.conf, that simplifies the process of using tsocks for
12281 tor. It even has a man page.
12282 - The tor binary gets installed to sbin rather than bin now.
12283 - Retry streams where the connected cell hasn't arrived in 15 seconds
12284 - Clean up exit policy handling -- get the default out of the torrc,
12285 so we can update it without forcing each server operator to fix
12287 - Allow imaps and pop3s in default exit policy
12289 - Prevent picking middleman nodes as the last node in the circuit
12292 Changes in version 0.0.2pre20 - 2004-01-30
12294 - We now have a deb package, and it's in debian unstable. Go to
12295 it, apt-getters. :)
12296 - I've split the TotalBandwidth option into BandwidthRate (how many
12297 bytes per second you want to allow, long-term) and
12298 BandwidthBurst (how many bytes you will allow at once before the cap
12299 kicks in). This better token bucket approach lets you, say, set
12300 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
12301 performance while not exceeding your monthly bandwidth quota.
12302 - Push out a tls record's worth of data once you've got it, rather
12303 than waiting until you've read everything waiting to be read. This
12304 may improve performance by pipelining better. We'll see.
12305 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
12306 from failed circuits (if they haven't been connected yet) and attach
12308 - Expire old streams that haven't managed to connect. Some day we'll
12309 have them reattach to new circuits instead.
12312 - Fix several memory leaks that were causing servers to become bloated
12314 - Fix a few very rare assert triggers. A few more remain.
12315 - Setuid to User _before_ complaining about running as root.
12318 Changes in version 0.0.2pre19 - 2004-01-07
12320 - Fix deadlock condition in dns farm. We were telling a child to die by
12321 closing the parent's file descriptor to him. But newer children were
12322 inheriting the open file descriptor from the parent, and since they
12323 weren't closing it, the socket never closed, so the child never read
12324 eof, so he never knew to exit. Similarly, dns workers were holding
12325 open other sockets, leading to all sorts of chaos.
12326 - New cleaner daemon() code for forking and backgrounding.
12327 - If you log to a file, it now prints an entry at the top of the
12328 logfile so you know it's working.
12329 - The onionskin challenge length was 30 bytes longer than necessary.
12330 - Started to patch up the spec so it's not quite so out of date.
12333 Changes in version 0.0.2pre18 - 2004-01-02
12335 - Fix endian issues with the 'integrity' field in the relay header.
12336 - Fix a potential bug where connections in state
12337 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
12340 Changes in version 0.0.2pre17 - 2003-12-30
12342 - Made --debuglogfile (or any second log file, actually) work.
12343 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
12344 adversary could force us into an infinite loop.
12347 - Each onionskin handshake now includes a hash of the computed key,
12348 to prove the server's identity and help perfect forward secrecy.
12349 - Changed cell size from 256 to 512 bytes (working toward compatibility
12351 - Changed cell length to 2 bytes, and moved it to the relay header.
12352 - Implemented end-to-end integrity checking for the payloads of
12354 - Separated streamid from 'recognized' (otherwise circuits will get
12355 messed up when we try to have streams exit from the middle). We
12356 use the integrity-checking to confirm that a cell is addressed to
12358 - Randomize the initial circid and streamid values, so an adversary who
12359 breaks into a node can't learn how many circuits or streams have
12363 Changes in version 0.0.2pre16 - 2003-12-14
12365 - Fixed a bug that made HUP trigger an assert
12366 - Fixed a bug where a circuit that immediately failed wasn't being
12367 counted as a failed circuit in counting retries.
12370 - Now we close the circuit when we get a truncated cell: otherwise we're
12371 open to an anonymity attack where a bad node in the path truncates
12372 the circuit and then we open streams at him.
12373 - Add port ranges to exit policies
12374 - Add a conservative default exit policy
12375 - Warn if you're running tor as root
12376 - on HUP, retry OR connections and close/rebind listeners
12377 - options.EntryNodes: try these nodes first when picking the first node
12378 - options.ExitNodes: if your best choices happen to include any of
12379 your preferred exit nodes, you choose among just those preferred
12381 - options.ExcludedNodes: nodes that are never picked in path building
12384 Changes in version 0.0.2pre15 - 2003-12-03
12385 o Robustness and bugfixes:
12386 - Sometimes clients would cache incorrect DNS resolves, which would
12387 really screw things up.
12388 - An OP that goes offline would slowly leak all its sockets and stop
12390 - A wide variety of bugfixes in exit node selection, exit policy
12391 handling, and processing pending streams when a new circuit is
12393 - Pick nodes for a path only from those the directory says are up
12394 - Choose randomly from all running dirservers, not always the first one
12395 - Increase allowed http header size for directory fetch.
12396 - Stop writing to stderr (if we're daemonized it will be closed).
12397 - Enable -g always, so cores will be more useful to me.
12398 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
12401 - Wrote a man page. It lists commonly used options.
12404 - Change default loglevel to warn.
12405 - Make PidFile default to null rather than littering in your CWD.
12406 - OnionRouter config option is now obsolete. Instead it just checks
12408 - Moved to a single unified torrc file for both clients and servers.
12411 Changes in version 0.0.2pre14 - 2003-11-29
12412 o Robustness and bugfixes:
12413 - Force the admin to make the DataDirectory himself
12414 - to get ownership/permissions right
12415 - so clients no longer make a DataDirectory and then never use it
12416 - fix bug where a client who was offline for 45 minutes would never
12417 pull down a directory again
12418 - fix (or at least hide really well) the dns assert bug that was
12419 causing server crashes
12420 - warnings and improved robustness wrt clockskew for certs
12421 - use the native daemon(3) to daemonize, when available
12422 - exit if bind() fails
12423 - exit if neither socksport nor orport is defined
12424 - include our own tor_timegm (Win32 doesn't have its own)
12425 - bugfix for win32 with lots of connections
12426 - fix minor bias in PRNG
12427 - make dirserver more robust to corrupt cached directory
12430 - Wrote the design document (woo)
12432 o Circuit building and exit policies:
12433 - Circuits no longer try to use nodes that the directory has told them
12435 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
12436 bitcounts (18.0.0.0/8).
12437 - Make AP connections standby for a circuit if no suitable circuit
12438 exists, rather than failing
12439 - Circuits choose exit node based on addr/port, exit policies, and
12440 which AP connections are standing by
12441 - Bump min pathlen from 2 to 3
12442 - Relay end cells have a payload to describe why the stream ended.
12443 - If the stream failed because of exit policy, try again with a new
12445 - Clients have a dns cache to remember resolved addresses.
12446 - Notice more quickly when we have no working circuits
12449 - APPort is now called SocksPort
12450 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
12452 - RecommendedVersions is now a config variable rather than
12453 hardcoded (for dirservers)
12454 - Reloads config on HUP
12455 - Usage info on -h or --help
12456 - If you set User and Group config vars, it'll setu/gid to them.
12458 Changes in version 0.0.2pre13 - 2003-10-19
12459 o General stability:
12460 - SSL_write no longer fails when it returns WANTWRITE and the number
12461 of bytes in the buf has changed by the next SSL_write call.
12462 - Fix segfault fetching directory when network is down
12463 - Fix a variety of minor memory leaks
12464 - Dirservers reload the fingerprints file on HUP, so I don't have
12465 to take down the network when I approve a new router
12466 - Default server config file has explicit Address line to specify fqdn
12469 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
12470 - Make listener connections not ever alloc bufs
12472 o Autoconf improvements:
12473 - don't clobber an external CFLAGS in ./configure
12474 - Make install now works
12475 - create var/lib/tor on make install
12476 - autocreate a tor.sh initscript to help distribs
12477 - autocreate the torrc and sample-server-torrc with correct paths
12479 o Log files and Daemonizing now work:
12480 - If --DebugLogFile is specified, log to it at -l debug
12481 - If --LogFile is specified, use it instead of commandline
12482 - If --RunAsDaemon is set, tor forks and backgrounds on startup