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.3.1.8 - 2017-10-25
6 Tor 0.3.1.8 is the second stable release in the 0.3.1 series.
7 It includes several bugfixes, including a bugfix for a crash issue
8 that had affected relays under memory pressure. It also adds
9 a new directory authority, Bastet.
11 o Directory authority changes:
12 - Add "Bastet" as a ninth directory authority to the default list.
14 - The directory authority "Longclaw" has changed its IP address.
17 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
18 - Fix a timing-based assertion failure that could occur when the
19 circuit out-of-memory handler freed a connection's output buffer.
20 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
22 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
23 - Remove longclaw's IPv6 address, as it will soon change. Authority
24 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
25 3/8 directory authorities with IPv6 addresses, but there are also
26 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
28 o Minor features (geoip):
29 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
32 o Minor bugfixes (compilation, backport from 0.3.2.2-alpha):
33 - Fix a compilation warning when building with zstd support on
34 32-bit platforms. Fixes bug 23568; bugfix on 0.3.1.1-alpha. Found
35 and fixed by Andreas Stieger.
37 o Minor bugfixes (compression, backport from 0.3.2.2-alpha):
38 - Handle a pathological case when decompressing Zstandard data when
39 the output buffer size is zero. Fixes bug 23551; bugfix
42 o Minor bugfixes (directory authority, backport from 0.3.2.1-alpha):
43 - Remove the length limit on HTTP status lines that authorities can
44 send in their replies. Fixes bug 23499; bugfix on 0.3.1.6-rc.
46 o Minor bugfixes (hidden service, relay, backport from 0.3.2.2-alpha):
47 - Avoid a possible double close of a circuit by the intro point on
48 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
49 bugfix on 0.3.0.1-alpha.
51 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
52 - Clear the address when node_get_prim_orport() returns early.
53 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
55 o Minor bugfixes (unit tests, backport from 0.3.2.2-alpha):
56 - Fix additional channelpadding unit test failures by using mocked
57 time instead of actual time for all tests. Fixes bug 23608; bugfix
61 Changes in version 0.3.1.7 - 2017-09-18
62 Tor 0.3.1.7 is the first stable release in the 0.3.1 series.
64 With the 0.3.1 series, Tor now serves and downloads directory
65 information in more compact formats, to save on bandwidth overhead. It
66 also contains a new padding system to resist netflow-based traffic
67 analysis, and experimental support for building parts of Tor in Rust
68 (though no parts of Tor are in Rust yet). There are also numerous
69 small features, bugfixes on earlier release series, and groundwork for
70 the hidden services revamp of 0.3.2.
72 This release also includes a fix for TROVE-2017-008, a security bug
73 that affects hidden services running with the SafeLogging option
74 disabled. For more information, see
75 https://trac.torproject.org/projects/tor/ticket/23490
77 Per our stable release policy, we plan to support each stable release
78 series for at least the next nine months, or for three months after
79 the first stable release of the next series: whichever is longer. If
80 you need a release with long-term support, we recommend that you stay
81 with the 0.2.9 series.
83 Below is a list of the changes since 0.3.0. For a list of all
84 changes since 0.3.1.6-rc, see the ChangeLog file.
87 - To build with zstd and lzma support, Tor now requires the
88 pkg-config tool at build time.
90 o Major bugfixes (security, hidden services, loggging):
91 - Fix a bug where we could log uninitialized stack when a certain
92 hidden service error occurred while SafeLogging was disabled.
93 Fixes bug #23490; bugfix on 0.2.7.2-alpha.
94 This is also tracked as TROVE-2017-008 and CVE-2017-0380.
96 o Major features (build system, continuous integration):
97 - Tor's repository now includes a Travis Continuous Integration (CI)
98 configuration file (.travis.yml). This is meant to help new
99 developers and contributors who fork Tor to a Github repository be
100 better able to test their changes, and understand what we expect
101 to pass. To use this new build feature, you must fork Tor to your
102 Github account, then go into the "Integrations" menu in the
103 repository settings for your fork and enable Travis, then push
104 your changes. Closes ticket 22636.
106 o Major features (directory protocol):
107 - Tor relays and authorities can now serve clients an abbreviated
108 version of the consensus document, containing only the changes
109 since an older consensus document that the client holds. Clients
110 now request these documents when available. When both client and
111 server use this new protocol, they will use far less bandwidth (up
112 to 94% less) to keep the client's consensus up-to-date. Implements
113 proposal 140; closes ticket 13339. Based on work by Daniel MartÃ.
114 - Tor can now compress directory traffic with lzma or with zstd
115 compression algorithms, which can deliver better bandwidth
116 performance. Because lzma is computationally expensive, it's only
117 used for documents that can be compressed once and served many
118 times. Support for these algorithms requires that tor is built
119 with the libzstd and/or liblzma libraries available. Implements
120 proposal 278; closes ticket 21662.
121 - Relays now perform the more expensive compression operations, and
122 consensus diff generation, in worker threads. This separation
123 avoids delaying the main thread when a new consensus arrives.
125 o Major features (experimental):
126 - Tor can now build modules written in Rust. To turn this on, pass
127 the "--enable-rust" flag to the configure script. It's not time to
128 get excited yet: currently, there is no actual Rust functionality
129 beyond some simple glue code, and a notice at startup to tell you
130 that Rust is running. Still, we hope that programmers and
131 packagers will try building Tor with Rust support, so that we can
132 find issues and solve portability problems. Closes ticket 22106.
134 o Major features (traffic analysis resistance):
135 - Connections between clients and relays now send a padding cell in
136 each direction every 1.5 to 9.5 seconds (tunable via consensus
137 parameters). This padding will not resist specialized
138 eavesdroppers, but it should be enough to make many ISPs' routine
139 network flow logging less useful in traffic analysis against
142 Padding is negotiated using Tor's link protocol, so both relays
143 and clients must upgrade for this to take effect. Clients may
144 still send padding despite the relay's version by setting
145 ConnectionPadding 1 in torrc, and may disable padding by setting
146 ConnectionPadding 0 in torrc. Padding may be minimized for mobile
147 users with the torrc option ReducedConnectionPadding. Implements
148 Proposal 251 and Section 2 of Proposal 254; closes ticket 16861.
149 - Relays will publish 24 hour totals of padding and non-padding cell
150 counts to their extra-info descriptors, unless PaddingStatistics 0
151 is set in torrc. These 24 hour totals are also rounded to
154 o Major bugfixes (hidden service, relay, security):
155 - Fix a remotely triggerable assertion failure when a hidden service
156 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
157 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
158 - Fix a remotely triggerable assertion failure caused by receiving a
159 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
160 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
163 o Major bugfixes (path selection, security):
164 - When choosing which guard to use for a circuit, avoid the exit's
165 family along with the exit itself. Previously, the new guard
166 selection logic avoided the exit, but did not consider its family.
167 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
168 006 and CVE-2017-0377.
170 o Major bugfixes (connection usage):
171 - We use NETINFO cells to try to determine if both relays involved
172 in a connection will agree on the canonical status of that
173 connection. We prefer the connections where this is the case for
174 extend cells, and try to close connections where relays disagree
175 on their canonical status early. Also, we now prefer the oldest
176 valid connection for extend cells. These two changes should reduce
177 the number of long-term connections that are kept open between
178 relays. Fixes bug 17604; bugfix on 0.2.5.5-alpha.
179 - Relays now log hourly statistics (look for
180 "channel_check_for_duplicates" lines) on the total number of
181 connections to other relays. If the number of connections per
182 relay is unexpectedly large, this log message is at notice level.
183 Otherwise it is at info.
185 o Major bugfixes (entry guards):
186 - When starting with an old consensus, do not add new entry guards
187 unless the consensus is "reasonably live" (under 1 day old). Fixes
188 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
189 - Don't block bootstrapping when a primary bridge is offline and we
190 can't get its descriptor. Fixes bug 22325; fixes one case of bug
191 21969; bugfix on 0.3.0.3-alpha.
193 o Major bugfixes (linux TPROXY support):
194 - Fix a typo that had prevented TPROXY-based transparent proxying
195 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
196 Patch from "d4fq0fQAgoJ".
198 o Major bugfixes (openbsd, denial-of-service):
199 - Avoid an assertion failure bug affecting our implementation of
200 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
201 handling of "0xx" differs from what we had expected. Fixes bug
202 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
204 o Major bugfixes (relay, link handshake):
205 - When performing the v3 link handshake on a TLS connection, report
206 that we have the x509 certificate that we actually used on that
207 connection, even if we have changed certificates since that
208 connection was first opened. Previously, we would claim to have
209 used our most recent x509 link certificate, which would sometimes
210 make the link handshake fail. Fixes one case of bug 22460; bugfix
213 o Major bugfixes (relays, key management):
214 - Regenerate link and authentication certificates whenever the key
215 that signs them changes; also, regenerate link certificates
216 whenever the signed key changes. Previously, these processes were
217 only weakly coupled, and we relays could (for minutes to hours)
218 wind up with an inconsistent set of keys and certificates, which
219 other relays would not accept. Fixes two cases of bug 22460;
220 bugfix on 0.3.0.1-alpha.
221 - When sending an Ed25519 signing->link certificate in a CERTS cell,
222 send the certificate that matches the x509 certificate that we
223 used on the TLS connection. Previously, there was a race condition
224 if the TLS context rotated after we began the TLS handshake but
225 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
228 o Minor features (security, windows):
229 - Enable a couple of pieces of Windows hardening: one
230 (HeapEnableTerminationOnCorruption) that has been on-by-default
231 since Windows 8, and unavailable before Windows 7; and one
232 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
233 affect us, but shouldn't do any harm. Closes ticket 21953.
235 o Minor features (bridge authority):
236 - Add "fingerprint" lines to the networkstatus-bridges file produced
237 by bridge authorities. Closes ticket 22207.
239 o Minor features (code style):
240 - Add "Falls through" comments to our codebase, in order to silence
241 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
242 Stieger. Closes ticket 22446.
244 o Minor features (config options):
245 - Allow "%include" directives in torrc configuration files. These
246 directives import the settings from other files, or from all the
247 files in a directory. Closes ticket 1922. Code by Daniel Pinto.
248 - Make SAVECONF return an error when overwriting a torrc that has
249 includes. Using SAVECONF with the FORCE option will allow it to
250 overwrite torrc even if includes are used. Related to ticket 1922.
251 - Add "GETINFO config-can-saveconf" to tell controllers if SAVECONF
252 will work without the FORCE option. Related to ticket 1922.
254 o Minor features (controller):
255 - Warn the first time that a controller requests data in the long-
256 deprecated 'GETINFO network-status' format. Closes ticket 21703.
258 o Minor features (defaults):
259 - The default value for UseCreateFast is now 0: clients which
260 haven't yet received a consensus document will now use a proper
261 ntor handshake to talk to their directory servers whenever they
262 can. Closes ticket 21407.
263 - Onion key rotation and expiry intervals are now defined as a
264 network consensus parameter, per proposal 274. The default
265 lifetime of an onion key is increased from 7 to 28 days. Old onion
266 keys will expire after 7 days by default. This change will make
267 consensus diffs much smaller, and save significant bandwidth.
270 o Minor features (defensive programming):
271 - Create a pair of consensus parameters, nf_pad_tor2web and
272 nf_pad_single_onion, to disable netflow padding in the consensus
273 for non-anonymous connections in case the overhead is high. Closes
276 o Minor features (diagnostic):
277 - Add a stack trace to the bug warnings that can be logged when
278 trying to send an outgoing relay cell with n_chan == 0. Diagnostic
279 attempt for bug 23105.
280 - Add logging messages to try to diagnose a rare bug that seems to
281 generate RSA->Ed25519 cross-certificates dated in the 1970s. We
282 think this is happening because of incorrect system clocks, but
283 we'd like to know for certain. Diagnostic for bug 22466.
284 - Avoid an assertion failure, and log a better error message, when
285 unable to remove a file from the consensus cache on Windows.
286 Attempts to mitigate and diagnose bug 22752.
288 o Minor features (directory authority):
289 - Improve the message that authorities report to relays that present
290 RSA/Ed25519 keypairs that conflict with previously pinned keys.
293 o Minor features (directory cache, consensus diff):
294 - Add a new MaxConsensusAgeForDiffs option to allow directory cache
295 operators with low-resource environments to adjust the number of
296 consensuses they'll store and generate diffs from. Most cache
297 operators should leave it unchanged. Helps to work around
300 o Minor features (fallback directory list):
301 - Update the fallback directory mirror whitelist and blacklist based
302 on operator emails. Closes task 21121.
303 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
304 December 2016 (of which ~126 were still functional) with a list of
305 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
306 2017. Resolves ticket 21564.
308 o Minor features (geoip):
309 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
312 o Minor features (hidden services, logging):
313 - Log a message when a hidden service descriptor has fewer
314 introduction points than specified in
315 HiddenServiceNumIntroductionPoints. Closes tickets 21598.
316 - Log a message when a hidden service reaches its introduction point
317 circuit limit, and when that limit is reset. Follow up to ticket
318 21594; closes ticket 21622.
319 - Warn user if multiple entries in EntryNodes and at least one
320 HiddenService are used together. Pinning EntryNodes along with a
321 hidden service can be possibly harmful; for instance see ticket
322 14917 or 21155. Closes ticket 21155.
324 o Minor features (linux seccomp2 sandbox):
325 - We now have a document storage backend compatible with the Linux
326 seccomp2 sandbox. This backend is used for consensus documents and
327 diffs between them; in the long term, we'd like to use it for
328 unparseable directory material too. Closes ticket 21645
329 - Increase the maximum allowed size passed to mprotect(PROT_WRITE)
330 from 1MB to 16MB. This was necessary with the glibc allocator in
331 order to allow worker threads to allocate more memory -- which in
332 turn is necessary because of our new use of worker threads for
333 compression. Closes ticket 22096.
335 o Minor features (logging):
336 - Log files are no longer created world-readable by default.
337 (Previously, most distributors would store the logs in a non-
338 world-readable location to prevent inappropriate access. This
339 change is an extra precaution.) Closes ticket 21729; patch
342 o Minor features (performance):
343 - Our Keccak (SHA-3) implementation now accesses memory more
344 efficiently, especially on little-endian systems. Closes
346 - Add an O(1) implementation of channel_find_by_global_id(), to
347 speed some controller functions.
349 o Minor features (relay, configuration):
350 - The MyFamily option may now be repeated as many times as desired,
351 for relays that want to configure large families. Closes ticket
352 4998; patch by Daniel Pinto.
354 o Minor features (relay, performance):
355 - Always start relays with at least two worker threads, to prevent
356 priority inversion on slow tasks. Part of the fix for bug 22883.
357 - Allow background work to be queued with different priorities, so
358 that a big pile of slow low-priority jobs will not starve out
359 higher priority jobs. This lays the groundwork for a fix for
362 o Minor features (safety):
363 - Add an explicit check to extrainfo_parse_entry_from_string() for
364 NULL inputs. We don't believe this can actually happen, but it may
365 help silence a warning from the Clang analyzer. Closes
368 o Minor features (testing):
369 - Add more tests for compression backend initialization. Closes
371 - Add a "--disable-memory-sentinels" feature to help with fuzzing.
372 When Tor is compiled with this option, we disable a number of
373 redundant memory-safety failsafes that are intended to stop bugs
374 from becoming security issues. This makes it easier to hunt for
375 bugs that would be security issues without the failsafes turned
376 on. Closes ticket 21439.
377 - Add a general event-tracing instrumentation support to Tor. This
378 subsystem will enable developers and researchers to add fine-
379 grained instrumentation to their Tor instances, for use when
380 examining Tor network performance issues. There are no trace
381 events yet, and event-tracing is off by default unless enabled at
382 compile time. Implements ticket 13802.
383 - Improve our version parsing tests: add tests for typical version
384 components, add tests for invalid versions, including numeric
385 range and non-numeric prefixes. Unit tests 21278, 21450, and
386 21507. Partially implements 21470.
388 o Minor bugfixes (bandwidth accounting):
389 - Roll over monthly accounting at the configured hour and minute,
390 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
391 Found by Andrey Karpov with PVS-Studio.
393 o Minor bugfixes (code correctness):
394 - Accurately identify client connections by their lack of peer
395 authentication. This means that we bail out earlier if asked to
396 extend to a client. Follow-up to 21407. Fixes bug 21406; bugfix
399 o Minor bugfixes (compilation warnings):
400 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug
401 22915; bugfix on 0.2.8.1-alpha.
402 - Fix warnings when building with libscrypt and openssl scrypt
403 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
404 - When building with certain versions of the mingw C header files,
405 avoid float-conversion warnings when calling the C functions
406 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
409 o Minor bugfixes (compilation):
410 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
411 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
413 o Minor bugfixes (compression):
414 - When spooling compressed data to an output buffer, don't try to
415 spool more data when there is no more data to spool and we are not
416 trying to flush the input. Previously, we would sometimes launch
417 compression requests with nothing to do, which interferes with our
418 22672 checks. Fixes bug 22719; bugfix on 0.2.0.16-alpha.
420 o Minor bugfixes (configuration):
421 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
422 bug 22252; bugfix on 0.2.9.3-alpha.
424 o Minor bugfixes (connection lifespan):
425 - Allow more control over how long TLS connections are kept open:
426 unify CircuitIdleTimeout and PredictedPortsRelevanceTime into a
427 single option called CircuitsAvailableTimeout. Also, allow the
428 consensus to control the default values for both this preference
429 and the lifespan of relay-to-relay connections. Fixes bug 17592;
430 bugfix on 0.2.5.5-alpha.
431 - Increase the initial circuit build timeout testing frequency, to
432 help ensure that ReducedConnectionPadding clients finish learning
433 a timeout before their orconn would expire. The initial testing
434 rate was set back in the days of TAP and before the Tor Browser
435 updater, when we had to be much more careful about new clients
436 making lots of circuits. With this change, a circuit build timeout
437 is learned in about 15-20 minutes, instead of 100-120 minutes.
439 o Minor bugfixes (controller):
440 - Do not crash when receiving a HSPOST command with an empty body.
441 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
442 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
443 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
444 - GETINFO onions/current and onions/detached no longer respond with
445 551 on empty lists. Fixes bug 21329; bugfix on 0.2.7.1-alpha.
446 - Trigger HS descriptor events on the control port when the client
447 fails to pick a hidden service directory for a hidden service.
448 This can happen if all the hidden service directories are in
449 ExcludeNodes, or they have all been queried within the last 15
450 minutes. Fixes bug 22042; bugfix on 0.2.5.2-alpha.
452 o Minor bugfixes (correctness):
453 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
454 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
456 o Minor bugfixes (coverity build support):
457 - Avoid Coverity build warnings related to our BUG() macro. By
458 default, Coverity treats BUG() as the Linux kernel does: an
459 instant abort(). We need to override that so our BUG() macro
460 doesn't prevent Coverity from analyzing functions that use it.
461 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
463 o Minor bugfixes (defensive programming):
464 - Detect and break out of infinite loops in our compression code. We
465 don't think that any such loops exist now, but it's best to be
466 safe. Closes ticket 22672.
467 - Fix a memset() off the end of an array when packing cells. This
468 bug should be harmless in practice, since the corrupted bytes are
469 still in the same structure, and are always padding bytes,
470 ignored, or immediately overwritten, depending on compiler
471 behavior. Nevertheless, because the memset()'s purpose is to make
472 sure that any other cell-handling bugs can't expose bytes to the
473 network, we need to fix it. Fixes bug 22737; bugfix on
474 0.2.4.11-alpha. Fixes CID 1401591.
476 o Minor bugfixes (directory authority):
477 - When a directory authority rejects a descriptor or extrainfo with
478 a given digest, mark that digest as undownloadable, so that we do
479 not attempt to download it again over and over. We previously
480 tried to avoid downloading such descriptors by other means, but we
481 didn't notice if we accidentally downloaded one anyway. This
482 behavior became problematic in 0.2.7.2-alpha, when authorities
483 began pinning Ed25519 keys. Fixes bug 22349; bugfix
485 - When rejecting a router descriptor for running an obsolete version
486 of Tor without ntor support, warn about the obsolete tor version,
487 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
488 - Prevent the shared randomness subsystem from asserting when
489 initialized by a bridge authority with an incomplete configuration
490 file. Fixes bug 21586; bugfix on 0.2.9.8.
492 o Minor bugfixes (error reporting, windows):
493 - When formatting Windows error messages, use the English format to
494 avoid codepage issues. Fixes bug 22520; bugfix on 0.1.2.8-alpha.
497 o Minor bugfixes (exit-side DNS):
498 - Fix an untriggerable assertion that checked the output of a
499 libevent DNS error, so that the assertion actually behaves as
500 expected. Fixes bug 22244; bugfix on 0.2.0.20-rc. Found by Andrey
501 Karpov using PVS-Studio.
503 o Minor bugfixes (fallback directories):
504 - Make the usage example in updateFallbackDirs.py actually work, and
505 explain what it does. Fixes bug 22270; bugfix on 0.3.0.3-alpha.
506 - Decrease the guard flag average required to be a fallback. This
507 allows us to keep relays that have their guard flag removed when
508 they restart. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
509 - Decrease the minimum number of fallbacks to 100. Fixes bug 20913;
510 bugfix on 0.2.8.1-alpha.
511 - Make sure fallback directory mirrors have the same address, port,
512 and relay identity key for at least 30 days before they are
513 selected. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
515 o Minor bugfixes (file limits, osx):
516 - When setting the maximum number of connections allowed by the OS,
517 always allow some extra file descriptors for other files. Fixes
518 bug 22797; bugfix on 0.2.0.10-alpha.
520 o Minor bugfixes (hidden services):
521 - Increase the number of circuits that a service is allowed to
522 open over a specific period of time. The value was lower than it
523 should be (8 vs 12) in the normal case of 3 introduction points.
524 Fixes bug 22159; bugfix on 0.3.0.5-rc.
525 - Fix a BUG warning during HSv3 descriptor decoding that could be
526 cause by a specially crafted descriptor. Fixes bug 23233; bugfix
527 on 0.3.0.1-alpha. Bug found by "haxxpop".
528 - Stop printing a cryptic warning when a hidden service gets a
529 request to connect to a virtual port that it hasn't configured.
530 Fixes bug 16706; bugfix on 0.2.6.3-alpha.
531 - Simplify hidden service descriptor creation by using an existing
532 flag to check if an introduction point is established. Fixes bug
533 21599; bugfix on 0.2.7.2-alpha.
535 o Minor bugfixes (link handshake):
536 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
537 months, and regenerate it when it is within one month of expiring.
538 Previously, we had generated this certificate at startup with a
539 ten-year lifetime, but that could lead to weird behavior when Tor
540 was started with a grossly inaccurate clock. Mitigates bug 22466;
541 mitigation on 0.3.0.1-alpha.
543 o Minor bugfixes (linux seccomp2 sandbox):
544 - Avoid a sandbox failure when trying to re-bind to a socket and
545 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
546 - Permit the fchmod system call, to avoid crashing on startup when
547 starting with the seccomp2 sandbox and an unexpected set of
548 permissions on the data directory or its contents. Fixes bug
549 22516; bugfix on 0.2.5.4-alpha.
551 o Minor bugfixes (logging):
552 - When decompressing, do not warn if we fail to decompress using a
553 compression method that we merely guessed. Fixes part of bug
554 22670; bugfix on 0.1.1.14-alpha.
555 - When decompressing, treat mismatch between content-encoding and
556 actual compression type as a protocol warning. Fixes part of bug
557 22670; bugfix on 0.1.1.9-alpha.
558 - Downgrade "assigned_to_cpuworker failed" message to info-level
559 severity. In every case that can reach it, either a better warning
560 has already been logged, or no warning is warranted. Fixes bug
561 22356; bugfix on 0.2.6.3-alpha.
562 - Log a better message when a directory authority replies to an
563 upload with an unexpected status code. Fixes bug 11121; bugfix
565 - Downgrade a log statement about unexpected relay cells from "bug"
566 to "protocol warning", because there is at least one use case
567 where it can be triggered by a buggy tor implementation. Fixes bug
568 21293; bugfix on 0.1.1.14-alpha.
570 o Minor bugfixes (logging, relay):
571 - Remove a forgotten debugging message when an introduction point
572 successfully establishes a hidden service prop224 circuit with
574 - Change three other log_warn() for an introduction point to
575 protocol warnings, because they can be failure from the network
576 and are not relevant to the operator. Fixes bug 23078; bugfix on
577 0.3.0.1-alpha and 0.3.0.2-alpha.
579 o Minor bugfixes (relay):
580 - Inform the geoip and rephist modules about all requests, even on
581 relays that are only fetching microdescriptors. Fixes a bug
582 related to 21585; bugfix on 0.3.0.1-alpha.
584 o Minor bugfixes (memory leaks):
585 - Fix a small memory leak at exit from the backtrace handler code.
586 Fixes bug 21788; bugfix on 0.2.5.2-alpha. Patch from Daniel Pinto.
587 - When directory authorities reject a router descriptor due to
588 keypinning, free the router descriptor rather than leaking the
589 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
590 - Fix a small memory leak when validating a configuration that uses
591 two or more AF_UNIX sockets for the same port type. Fixes bug
592 23053; bugfix on 0.2.6.3-alpha. This is CID 1415725.
594 o Minor bugfixes (process behavior):
595 - When exiting because of an error, always exit with a nonzero exit
596 status. Previously, we would fail to report an error in our exit
597 status in cases related to __OwningControllerProcess failure,
598 lockfile contention, and Ed25519 key initialization. Fixes bug
599 22720; bugfix on versions 0.2.1.6-alpha, 0.2.2.28-beta, and
600 0.2.7.2-alpha respectively. Reported by "f55jwk4f"; patch
603 o Minor bugfixes (robustness, error handling):
604 - Improve our handling of the cases where OpenSSL encounters a
605 memory error while encoding keys and certificates. We haven't
606 observed these errors in the wild, but if they do happen, we now
607 detect and respond better. Fixes bug 19418; bugfix on all versions
608 of Tor. Reported by Guido Vranken.
610 o Minor bugfixes (testing):
611 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
612 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
613 - Use unbuffered I/O for utility functions around the
614 process_handle_t type. This fixes unit test failures reported on
615 OpenBSD and FreeBSD. Fixes bug 21654; bugfix on 0.2.3.1-alpha.
616 - Make display of captured unit test log messages consistent. Fixes
617 bug 21510; bugfix on 0.2.9.3-alpha.
618 - Make test-network.sh always call chutney's test-network.sh.
619 Previously, this only worked on systems which had bash installed,
620 due to some bash-specific code in the script. Fixes bug 19699;
621 bugfix on 0.3.0.4-rc. Follow-up to ticket 21581.
622 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
623 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
624 - The unit tests now pass on systems where localhost is misconfigured
625 to some IPv4 address other than 127.0.0.1. Fixes bug 6298; bugfix
628 o Minor bugfixes (voting consistency):
629 - Reject version numbers with non-numeric prefixes (such as +, -, or
630 whitespace). Disallowing whitespace prevents differential version
631 parsing between POSIX-based and Windows platforms. Fixes bug 21507
632 and part of 21508; bugfix on 0.0.8pre1.
634 o Minor bugfixes (Windows service):
635 - When running as a Windows service, set the ID of the main thread
636 correctly. Failure to do so made us fail to send log messages to
637 the controller in 0.2.1.16-rc, slowed down controller event
638 delivery in 0.2.7.3-rc and later, and crash with an assertion
639 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
640 Patch and diagnosis from "Vort".
642 o Minor bugfixes (windows, relay):
643 - Resolve "Failure from drain_fd: No error" warnings on Windows
644 relays. Fixes bug 21540; bugfix on 0.2.6.3-alpha.
646 o Code simplification and refactoring:
647 - Break up the 630-line function connection_dir_client_reached_eof()
648 into a dozen smaller functions. This change should help
649 maintainability and readability of the client directory code.
650 - Isolate our use of the openssl headers so that they are only
651 included from our crypto wrapper modules, and from tests that
652 examine those modules' internals. Closes ticket 21841.
653 - Simplify our API to launch directory requests, making it more
654 extensible and less error-prone. Now it's easier to add extra
655 headers to directory requests. Closes ticket 21646.
656 - Our base64 decoding functions no longer overestimate the output
657 space that they need when parsing unpadded inputs. Closes
659 - Remove unused "ROUTER_ADDED_NOTIFY_GENERATOR" internal value.
660 Resolves ticket 22213.
661 - The logic that directory caches use to spool request to clients,
662 serving them one part at a time so as not to allocate too much
663 memory, has been refactored for consistency. Previously there was
664 a separate spooling implementation per type of spoolable data. Now
665 there is one common spooling implementation, with extensible data
666 types. Closes ticket 21651.
667 - Tor's compression module now supports multiple backends. Part of
668 the implementation for proposal 278; closes ticket 21663.
671 - Add a manpage description for the key-pinning-journal file. Closes
673 - Correctly note that bandwidth accounting values are stored in the
674 state file, and the bw_accounting file is now obsolete. Closes
676 - Document more of the files in the Tor data directory, including
677 cached-extrainfo, secret_onion_key{,_ntor}.old, hidserv-stats,
678 approved-routers, sr-random, and diff-cache. Found while fixing
680 - Clarify the manpage for the (deprecated) torify script. Closes
682 - Clarify the behavior of the KeepAliveIsolateSOCKSAuth sub-option.
684 - Correct documentation about the default DataDirectory value.
686 - Document the default behavior of NumEntryGuards and
687 NumDirectoryGuards correctly. Fixes bug 21715; bugfix
689 - Document key=value pluggable transport arguments for Bridge lines
690 in torrc. Fixes bug 20341; bugfix on 0.2.5.1-alpha.
691 - Note that bandwidth-limiting options don't affect TCP headers or
692 DNS. Closes ticket 17170.
694 o Removed features (configuration options, all in ticket 22060):
695 - These configuration options are now marked Obsolete, and no longer
696 have any effect: AllowInvalidNodes, AllowSingleHopCircuits,
697 AllowSingleHopExits, ExcludeSingleHopRelays, FastFirstHopPK,
698 TLSECGroup, WarnUnsafeSocks. They were first marked as deprecated
699 in 0.2.9.2-alpha and have now been removed. The previous default
700 behavior is now always chosen; the previous (less secure) non-
701 default behavior is now unavailable.
702 - CloseHSClientCircuitsImmediatelyOnTimeout and
703 CloseHSServiceRendCircuitsImmediatelyOnTimeout were deprecated in
704 0.2.9.2-alpha and now have been removed. HS circuits never close
705 on circuit build timeout; they have a longer timeout period.
706 - {Control,DNS,Dir,Socks,Trans,NATD,OR}ListenAddress were deprecated
707 in 0.2.9.2-alpha and now have been removed. Use the ORPort option
708 (and others) to configure listen-only and advertise-only addresses.
710 o Removed features (tools):
711 - We've removed the tor-checkkey tool from src/tools. Long ago, we
712 used it to help people detect RSA keys that were generated by
713 versions of Debian affected by CVE-2008-0166. But those keys have
714 been out of circulation for ages, and this tool is no longer
715 required. Closes ticket 21842.
718 Changes in version 0.3.0.8 - 2017-06-08
719 Tor 0.3.0.8 fixes a pair of bugs that would allow an attacker to
720 remotely crash a hidden service with an assertion failure. Anyone
721 running a hidden service should upgrade to this version, or to some
722 other version with fixes for TROVE-2017-004 and TROVE-2017-005.
724 Tor 0.3.0.8 also includes fixes for several key management bugs
725 that sometimes made relays unreliable, as well as several other
726 bugfixes described below.
728 o Major bugfixes (hidden service, relay, security, backport
730 - Fix a remotely triggerable assertion failure when a hidden service
731 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
732 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
733 - Fix a remotely triggerable assertion failure caused by receiving a
734 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
735 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
738 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
739 - When performing the v3 link handshake on a TLS connection, report
740 that we have the x509 certificate that we actually used on that
741 connection, even if we have changed certificates since that
742 connection was first opened. Previously, we would claim to have
743 used our most recent x509 link certificate, which would sometimes
744 make the link handshake fail. Fixes one case of bug 22460; bugfix
747 o Major bugfixes (relays, key management, backport from 0.3.1.3-alpha):
748 - Regenerate link and authentication certificates whenever the key
749 that signs them changes; also, regenerate link certificates
750 whenever the signed key changes. Previously, these processes were
751 only weakly coupled, and we relays could (for minutes to hours)
752 wind up with an inconsistent set of keys and certificates, which
753 other relays would not accept. Fixes two cases of bug 22460;
754 bugfix on 0.3.0.1-alpha.
755 - When sending an Ed25519 signing->link certificate in a CERTS cell,
756 send the certificate that matches the x509 certificate that we
757 used on the TLS connection. Previously, there was a race condition
758 if the TLS context rotated after we began the TLS handshake but
759 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
762 o Major bugfixes (hidden service v3, backport from 0.3.1.1-alpha):
763 - Stop rejecting v3 hidden service descriptors because their size
764 did not match an old padding rule. Fixes bug 22447; bugfix on
767 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
768 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
769 December 2016 (of which ~126 were still functional) with a list of
770 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
771 2017. Resolves ticket 21564.
773 o Minor bugfixes (configuration, backport from 0.3.1.1-alpha):
774 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
775 bug 22252; bugfix on 0.2.9.3-alpha.
777 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
778 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
779 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
781 o Minor bugfixes (link handshake, backport from 0.3.1.3-alpha):
782 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
783 months, and regenerate it when it is within one month of expiring.
784 Previously, we had generated this certificate at startup with a
785 ten-year lifetime, but that could lead to weird behavior when Tor
786 was started with a grossly inaccurate clock. Mitigates bug 22466;
787 mitigation on 0.3.0.1-alpha.
789 o Minor bugfixes (memory leak, directory authority, backport from
791 - When directory authorities reject a router descriptor due to
792 keypinning, free the router descriptor rather than leaking the
793 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
796 Changes in version 0.2.9.11 - 2017-06-08
797 Tor 0.2.9.11 backports a fix for a bug that would allow an attacker to
798 remotely crash a hidden service with an assertion failure. Anyone
799 running a hidden service should upgrade to this version, or to some
800 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
801 are not affected by TROVE-2017-004.)
803 Tor 0.2.9.11 also backports fixes for several key management bugs
804 that sometimes made relays unreliable, as well as several other
805 bugfixes described below.
807 o Major bugfixes (hidden service, relay, security, backport
809 - Fix a remotely triggerable assertion failure caused by receiving a
810 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
811 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
814 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
815 - When performing the v3 link handshake on a TLS connection, report
816 that we have the x509 certificate that we actually used on that
817 connection, even if we have changed certificates since that
818 connection was first opened. Previously, we would claim to have
819 used our most recent x509 link certificate, which would sometimes
820 make the link handshake fail. Fixes one case of bug 22460; bugfix
823 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
824 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
825 December 2016 (of which ~126 were still functional) with a list of
826 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
827 2017. Resolves ticket 21564.
829 o Minor features (future-proofing, backport from 0.3.0.7):
830 - Tor no longer refuses to download microdescriptors or descriptors if
831 they are listed as "published in the future". This change will
832 eventually allow us to stop listing meaningful "published" dates
833 in microdescriptor consensuses, and thereby allow us to reduce the
834 resources required to download consensus diffs by over 50%.
835 Implements part of ticket 21642; implements part of proposal 275.
837 o Minor features (directory authorities, backport from 0.3.0.4-rc)
838 - Directory authorities now reject relays running versions
839 0.2.9.1-alpha through 0.2.9.4-alpha, because those relays
840 suffer from bug 20499 and don't keep their consensus cache
841 up-to-date. Resolves ticket 20509.
843 o Minor features (geoip):
844 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
847 o Minor bugfixes (control port, backport from 0.3.0.6):
848 - The GETINFO extra-info/digest/<digest> command was broken because
849 of a wrong base16 decode return value check, introduced when
850 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
852 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
853 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
854 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
856 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.0.7):
857 - The getpid() system call is now permitted under the Linux seccomp2
858 sandbox, to avoid crashing with versions of OpenSSL (and other
859 libraries) that attempt to learn the process's PID by using the
860 syscall rather than the VDSO code. Fixes bug 21943; bugfix
863 o Minor bugfixes (memory leak, directory authority, backport
865 - When directory authorities reject a router descriptor due to
866 keypinning, free the router descriptor rather than leaking the
867 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
869 Changes in version 0.2.8.14 - 2017-06-08
870 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
871 remotely crash a hidden service with an assertion failure. Anyone
872 running a hidden service should upgrade to this version, or to some
873 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
874 are not affected by TROVE-2017-004.)
876 o Major bugfixes (hidden service, relay, security):
877 - Fix a remotely triggerable assertion failure caused by receiving a
878 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
879 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
882 o Minor features (geoip):
883 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
886 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
887 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
888 December 2016 (of which ~126 were still functional) with a list of
889 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
890 2017. Resolves ticket 21564.
892 o Minor bugfixes (correctness):
893 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
894 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
896 Changes in version 0.2.7.8 - 2017-06-08
897 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
898 remotely crash a hidden service with an assertion failure. Anyone
899 running a hidden service should upgrade to this version, or to some
900 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
901 are not affected by TROVE-2017-004.)
903 o Major bugfixes (hidden service, relay, security):
904 - Fix a remotely triggerable assertion failure caused by receiving a
905 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
906 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
909 o Minor features (geoip):
910 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
913 o Minor bugfixes (correctness):
914 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
915 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
918 Changes in version 0.2.6.12 - 2017-06-08
919 Tor 0.2.6.12 backports a fix for a bug that would allow an attacker to
920 remotely crash a hidden service with an assertion failure. Anyone
921 running a hidden service should upgrade to this version, or to some
922 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
923 are not affected by TROVE-2017-004.)
925 o Major bugfixes (hidden service, relay, security):
926 - Fix a remotely triggerable assertion failure caused by receiving a
927 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
928 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
931 o Minor features (geoip):
932 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
935 o Minor bugfixes (correctness):
936 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
937 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
939 Changes in version 0.2.5.14 - 2017-06-08
940 Tor 0.2.5.14 backports a fix for a bug that would allow an attacker to
941 remotely crash a hidden service with an assertion failure. Anyone
942 running a hidden service should upgrade to this version, or to some
943 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
944 are not affected by TROVE-2017-004.)
946 o Major bugfixes (hidden service, relay, security):
947 - Fix a remotely triggerable assertion failure caused by receiving a
948 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
949 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
952 o Minor features (geoip):
953 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
956 o Minor bugfixes (correctness):
957 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
958 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
960 Changes in version 0.2.4.29 - 2017-06-08
961 Tor 0.2.4.29 backports a fix for a bug that would allow an attacker to
962 remotely crash a hidden service with an assertion failure. Anyone
963 running a hidden service should upgrade to this version, or to some
964 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
965 are not affected by TROVE-2017-004.)
967 o Major bugfixes (hidden service, relay, security):
968 - Fix a remotely triggerable assertion failure caused by receiving a
969 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
970 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
973 o Minor features (geoip):
974 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
977 o Minor bugfixes (correctness):
978 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
979 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
982 Changes in version 0.3.0.7 - 2017-05-15
983 Tor 0.3.0.7 fixes a medium-severity security bug in earlier versions
984 of Tor 0.3.0.x, where an attacker could cause a Tor relay process
985 to exit. Relays running earlier versions of Tor 0.3.0.x should upgrade;
986 clients are not affected.
988 o Major bugfixes (hidden service directory, security):
989 - Fix an assertion failure in the hidden service directory code, which
990 could be used by an attacker to remotely cause a Tor relay process to
991 exit. Relays running earlier versions of Tor 0.3.0.x should upgrade.
992 should upgrade. This security issue is tracked as TROVE-2017-002.
993 Fixes bug 22246; bugfix on 0.3.0.1-alpha.
996 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
999 o Minor features (future-proofing):
1000 - Tor no longer refuses to download microdescriptors or descriptors
1001 if they are listed as "published in the future". This change will
1002 eventually allow us to stop listing meaningful "published" dates
1003 in microdescriptor consensuses, and thereby allow us to reduce the
1004 resources required to download consensus diffs by over 50%.
1005 Implements part of ticket 21642; implements part of proposal 275.
1007 o Minor bugfixes (Linux seccomp2 sandbox):
1008 - The getpid() system call is now permitted under the Linux seccomp2
1009 sandbox, to avoid crashing with versions of OpenSSL (and other
1010 libraries) that attempt to learn the process's PID by using the
1011 syscall rather than the VDSO code. Fixes bug 21943; bugfix
1015 Changes in version 0.3.0.6 - 2017-04-26
1016 Tor 0.3.0.6 is the first stable release of the Tor 0.3.0 series.
1018 With the 0.3.0 series, clients and relays now use Ed25519 keys to
1019 authenticate their link connections to relays, rather than the old
1020 RSA1024 keys that they used before. (Circuit crypto has been
1021 Curve25519-authenticated since 0.2.4.8-alpha.) We have also replaced
1022 the guard selection and replacement algorithm to behave more robustly
1023 in the presence of unreliable networks, and to resist guard-
1026 This series also includes numerous other small features and bugfixes,
1027 along with more groundwork for the upcoming hidden-services revamp.
1029 Per our stable release policy, we plan to support the Tor 0.3.0
1030 release series for at least the next nine months, or for three months
1031 after the first stable release of the 0.3.1 series: whichever is
1032 longer. If you need a release with long-term support, we recommend
1033 that you stay with the 0.2.9 series.
1035 Below are the changes since 0.2.9.10. For a list of only the changes
1036 since 0.3.0.5-rc, see the ChangeLog file.
1038 o Major features (directory authority, security):
1039 - The default for AuthDirPinKeys is now 1: directory authorities
1040 will reject relays where the RSA identity key matches a previously
1041 seen value, but the Ed25519 key has changed. Closes ticket 18319.
1043 o Major features (guard selection algorithm):
1044 - Tor's guard selection algorithm has been redesigned from the
1045 ground up, to better support unreliable networks and restrictive
1046 sets of entry nodes, and to better resist guard-capture attacks by
1047 hostile local networks. Implements proposal 271; closes
1050 o Major features (next-generation hidden services):
1051 - Relays can now handle v3 ESTABLISH_INTRO cells as specified by
1052 prop224 aka "Next Generation Hidden Services". Service and clients
1053 don't use this functionality yet. Closes ticket 19043. Based on
1054 initial code by Alec Heifetz.
1055 - Relays now support the HSDir version 3 protocol, so that they can
1056 can store and serve v3 descriptors. This is part of the next-
1057 generation onion service work detailled in proposal 224. Closes
1060 o Major features (protocol, ed25519 identity keys):
1061 - Clients now support including Ed25519 identity keys in the EXTEND2
1062 cells they generate. By default, this is controlled by a consensus
1063 parameter, currently disabled. You can turn this feature on for
1064 testing by setting ExtendByEd25519ID in your configuration. This
1065 might make your traffic appear different than the traffic
1066 generated by other users, however. Implements part of ticket
1067 15056; part of proposal 220.
1068 - Relays now understand requests to extend to other relays by their
1069 Ed25519 identity keys. When an Ed25519 identity key is included in
1070 an EXTEND2 cell, the relay will only extend the circuit if the
1071 other relay can prove ownership of that identity. Implements part
1072 of ticket 15056; part of proposal 220.
1073 - Relays now use Ed25519 to prove their Ed25519 identities and to
1074 one another, and to clients. This algorithm is faster and more
1075 secure than the RSA-based handshake we've been doing until now.
1076 Implements the second big part of proposal 220; Closes
1079 o Major features (security):
1080 - Change the algorithm used to decide DNS TTLs on client and server
1081 side, to better resist DNS-based correlation attacks like the
1082 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
1083 Feamster. Now relays only return one of two possible DNS TTL
1084 values, and clients are willing to believe DNS TTL values up to 3
1085 hours long. Closes ticket 19769.
1087 o Major bugfixes (client, onion service, also in 0.2.9.9):
1088 - Fix a client-side onion service reachability bug, where multiple
1089 socks requests to an onion service (or a single slow request)
1090 could cause us to mistakenly mark some of the service's
1091 introduction points as failed, and we cache that failure so
1092 eventually we run out and can't reach the service. Also resolves a
1093 mysterious "Remote server sent bogus reason code 65021" log
1094 warning. The bug was introduced in ticket 17218, where we tried to
1095 remember the circuit end reason as a uint16_t, which mangled
1096 negative values. Partially fixes bug 21056 and fixes bug 20307;
1097 bugfix on 0.2.8.1-alpha.
1099 o Major bugfixes (crash, directory connections):
1100 - Fix a rare crash when sending a begin cell on a circuit whose
1101 linked directory connection had already been closed. Fixes bug
1102 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
1104 o Major bugfixes (directory authority):
1105 - During voting, when marking a relay as a probable sybil, do not
1106 clear its BadExit flag: sybils can still be bad in other ways
1107 too. (We still clear the other flags.) Fixes bug 21108; bugfix
1110 o Major bugfixes (DNS):
1111 - Fix a bug that prevented exit nodes from caching DNS records for
1112 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
1114 o Major bugfixes (IPv6 Exits):
1115 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
1116 any IPv6 addresses. Instead, only reject a port over IPv6 if the
1117 exit policy rejects that port on more than an IPv6 /16 of
1118 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
1119 which rejected a relay's own IPv6 address by default. Fixes bug
1120 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
1122 o Major bugfixes (parsing):
1123 - Fix an integer underflow bug when comparing malformed Tor
1124 versions. This bug could crash Tor when built with
1125 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
1126 0.2.9.8, which were built with -ftrapv by default. In other cases
1127 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
1128 on 0.0.8pre1. Found by OSS-Fuzz.
1129 - When parsing a malformed content-length field from an HTTP
1130 message, do not read off the end of the buffer. This bug was a
1131 potential remote denial-of-service attack against Tor clients and
1132 relays. A workaround was released in October 2016, to prevent this
1133 bug from crashing Tor. This is a fix for the underlying issue,
1134 which should no longer matter (if you applied the earlier patch).
1135 Fixes bug 20894; bugfix on 0.2.0.16-alpha. Bug found by fuzzing
1136 using AFL (http://lcamtuf.coredump.cx/afl/).
1138 o Major bugfixes (scheduler):
1139 - Actually compare circuit policies in ewma_cmp_cmux(). This bug
1140 caused the channel scheduler to behave more or less randomly,
1141 rather than preferring channels with higher-priority circuits.
1142 Fixes bug 20459; bugfix on 0.2.6.2-alpha.
1144 o Major bugfixes (security, also in 0.2.9.9):
1145 - Downgrade the "-ftrapv" option from "always on" to "only on when
1146 --enable-expensive-hardening is provided." This hardening option,
1147 like others, can turn survivable bugs into crashes--and having it
1148 on by default made a (relatively harmless) integer overflow bug
1149 into a denial-of-service bug. Fixes bug 21278 (TROVE-2017-001);
1150 bugfix on 0.2.9.1-alpha.
1152 o Minor feature (client):
1153 - Enable IPv6 traffic on the SocksPort by default. To disable this,
1154 a user will have to specify "NoIPv6Traffic". Closes ticket 21269.
1156 o Minor feature (fallback scripts):
1157 - Add a check_existing mode to updateFallbackDirs.py, which checks
1158 if fallbacks in the hard-coded list are working. Closes ticket
1159 20174. Patch by haxxpop.
1161 o Minor feature (protocol versioning):
1162 - Add new protocol version for proposal 224. HSIntro now advertises
1163 version "3-4" and HSDir version "1-2". Fixes ticket 20656.
1165 o Minor features (ciphersuite selection):
1166 - Allow relays to accept a wider range of ciphersuites, including
1167 chacha20-poly1305 and AES-CCM. Closes the other part of 15426.
1168 - Clients now advertise a list of ciphersuites closer to the ones
1169 preferred by Firefox. Closes part of ticket 15426.
1171 o Minor features (controller):
1172 - Add "GETINFO sr/current" and "GETINFO sr/previous" keys, to expose
1173 shared-random values to the controller. Closes ticket 19925.
1174 - When HSFETCH arguments cannot be parsed, say "Invalid argument"
1175 rather than "unrecognized." Closes ticket 20389; patch from
1178 o Minor features (controller, configuration):
1179 - Each of the *Port options, such as SocksPort, ORPort, ControlPort,
1180 and so on, now comes with a __*Port variant that will not be saved
1181 to the torrc file by the controller's SAVECONF command. This
1182 change allows TorBrowser to set up a single-use domain socket for
1183 each time it launches Tor. Closes ticket 20956.
1184 - The GETCONF command can now query options that may only be
1185 meaningful in context-sensitive lists. This allows the controller
1186 to query the mixed SocksPort/__SocksPort style options introduced
1187 in feature 20956. Implements ticket 21300.
1189 o Minor features (diagnostic, directory client):
1190 - Warn when we find an unexpected inconsistency in directory
1191 download status objects. Prevents some negative consequences of
1194 o Minor features (directory authorities):
1195 - Directory authorities now reject descriptors that claim to be
1196 malformed versions of Tor. Helps prevent exploitation of
1198 - Reject version numbers with components that exceed INT32_MAX.
1199 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
1200 Fixes bug 21450; bugfix on 0.0.8pre1.
1202 o Minor features (directory authority):
1203 - Add a new authority-only AuthDirTestEd25519LinkKeys option (on by
1204 default) to control whether authorities should try to probe relays
1205 by their Ed25519 link keys. This option will go away in a few
1206 releases--unless we encounter major trouble in our ed25519 link
1207 protocol rollout, in which case it will serve as a safety option.
1209 o Minor features (directory cache):
1210 - Relays and bridges will now refuse to serve the consensus they
1211 have if they know it is too old for a client to use. Closes
1214 o Minor features (ed25519 link handshake):
1215 - Advertise support for the ed25519 link handshake using the
1216 subprotocol-versions mechanism, so that clients can tell which
1217 relays can identity themselves by Ed25519 ID. Closes ticket 20552.
1219 o Minor features (entry guards):
1220 - Add UseEntryGuards to TEST_OPTIONS_DEFAULT_VALUES in order to not
1221 break regression tests.
1222 - Require UseEntryGuards when UseBridges is set, in order to make
1223 sure bridges aren't bypassed. Resolves ticket 20502.
1225 o Minor features (fallback directories):
1226 - Allow 3 fallback relays per operator, which is safe now that we
1227 are choosing 200 fallback relays. Closes ticket 20912.
1228 - Annotate updateFallbackDirs.py with the bandwidth and consensus
1229 weight for each candidate fallback. Closes ticket 20878.
1230 - Display the relay fingerprint when downloading consensuses from
1231 fallbacks. Closes ticket 20908.
1232 - Exclude relays affected by bug 20499 from the fallback list.
1233 Exclude relays from the fallback list if they are running versions
1234 known to be affected by bug 20499, or if in our tests they deliver
1235 a stale consensus (i.e. one that expired more than 24 hours ago).
1236 Closes ticket 20539.
1237 - Make it easier to change the output sort order of fallbacks.
1238 Closes ticket 20822.
1239 - Reduce the minimum fallback bandwidth to 1 MByte/s. Part of
1241 - Require fallback directories to have the same address and port for
1242 7 days (now that we have enough relays with this stability).
1243 Relays whose OnionOO stability timer is reset on restart by bug
1244 18050 should upgrade to Tor 0.2.8.7 or later, which has a fix for
1245 this issue. Closes ticket 20880; maintains short-term fix
1247 - Require fallbacks to have flags for 90% of the time (weighted
1248 decaying average), rather than 95%. This allows at least 73% of
1249 clients to bootstrap in the first 5 seconds without contacting an
1250 authority. Part of ticket 18828.
1251 - Select 200 fallback directories for each release. Closes
1254 o Minor features (fingerprinting resistence, authentication):
1255 - Extend the length of RSA keys used for TLS link authentication to
1256 2048 bits. (These weren't used for forward secrecy; for forward
1257 secrecy, we used P256.) Closes ticket 13752.
1259 o Minor features (geoip):
1260 - Update geoip and geoip6 to the April 4 2017 Maxmind GeoLite2
1263 o Minor features (geoip, also in 0.2.9.9):
1264 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
1267 o Minor features (infrastructure):
1268 - Implement smartlist_add_strdup() function. Replaces the use of
1269 smartlist_add(sl, tor_strdup(str)). Closes ticket 20048.
1271 o Minor features (linting):
1272 - Enhance the changes file linter to warn on Tor versions that are
1273 prefixed with "tor-". Closes ticket 21096.
1275 o Minor features (logging):
1276 - In several places, describe unset ed25519 keys as "<unset>",
1277 rather than the scary "AAAAAAAA...AAA". Closes ticket 21037.
1279 o Minor features (portability, compilation):
1280 - Autoconf now checks to determine if OpenSSL structures are opaque,
1281 instead of explicitly checking for OpenSSL version numbers. Part
1283 - Support building with recent LibreSSL code that uses opaque
1284 structures. Closes ticket 21359.
1286 o Minor features (relay):
1287 - We now allow separation of exit and relay traffic to different
1288 source IP addresses, using the OutboundBindAddressExit and
1289 OutboundBindAddressOR options respectively. Closes ticket 17975.
1290 Written by Michael Sonntag.
1292 o Minor features (reliability, crash):
1293 - Try better to detect problems in buffers where they might grow (or
1294 think they have grown) over 2 GB in size. Diagnostic for
1297 o Minor features (testing):
1298 - During 'make test-network-all', if tor logs any warnings, ask
1299 chutney to output them. Requires a recent version of chutney with
1300 the 21572 patch. Implements 21570.
1302 o Minor bugfix (control protocol):
1303 - The reply to a "GETINFO config/names" request via the control
1304 protocol now spells the type "Dependent" correctly. This is a
1305 breaking change in the control protocol. (The field seems to be
1306 ignored by the most common known controllers.) Fixes bug 18146;
1307 bugfix on 0.1.1.4-alpha.
1308 - The GETINFO extra-info/digest/<digest> command was broken because
1309 of a wrong base16 decode return value check, introduced when
1310 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
1312 o Minor bugfix (logging):
1313 - Don't recommend the use of Tor2web in non-anonymous mode.
1314 Recommending Tor2web is a bad idea because the client loses all
1315 anonymity. Tor2web should only be used in specific cases by users
1316 who *know* and understand the issues. Fixes bug 21294; bugfix
1319 o Minor bugfixes (bug resilience):
1320 - Fix an unreachable size_t overflow in base64_decode(). Fixes bug
1321 19222; bugfix on 0.2.0.9-alpha. Found by Guido Vranken; fixed by
1322 Hans Jerry Illikainen.
1324 o Minor bugfixes (build):
1325 - Replace obsolete Autoconf macros with their modern equivalent and
1326 prevent similar issues in the future. Fixes bug 20990; bugfix
1329 o Minor bugfixes (certificate expiration time):
1330 - Avoid using link certificates that don't become valid till some
1331 time in the future. Fixes bug 21420; bugfix on 0.2.4.11-alpha
1333 o Minor bugfixes (client):
1334 - Always recover from failures in extend_info_from_node(), in an
1335 attempt to prevent any recurrence of bug 21242. Fixes bug 21372;
1336 bugfix on 0.2.3.1-alpha.
1337 - When clients that use bridges start up with a cached consensus on
1338 disk, they were ignoring it and downloading a new one. Now they
1339 use the cached one. Fixes bug 20269; bugfix on 0.2.3.12-alpha.
1341 o Minor bugfixes (code correctness):
1342 - Repair a couple of (unreachable or harmless) cases of the risky
1343 comparison-by-subtraction pattern that caused bug 21278.
1345 o Minor bugfixes (config):
1346 - Don't assert on startup when trying to get the options list and
1347 LearnCircuitBuildTimeout is set to 0: we are currently parsing the
1348 options so of course they aren't ready yet. Fixes bug 21062;
1349 bugfix on 0.2.9.3-alpha.
1351 o Minor bugfixes (configuration):
1352 - Accept non-space whitespace characters after the severity level in
1353 the `Log` option. Fixes bug 19965; bugfix on 0.2.1.1-alpha.
1354 - Support "TByte" and "TBytes" units in options given in bytes.
1355 "TB", "terabyte(s)", "TBit(s)" and "terabit(s)" were already
1356 supported. Fixes bug 20622; bugfix on 0.2.0.14-alpha.
1358 o Minor bugfixes (configure, autoconf):
1359 - Rename the configure option --enable-expensive-hardening to
1360 --enable-fragile-hardening. Expensive hardening makes the tor
1361 daemon abort when some kinds of issues are detected. Thus, it
1362 makes tor more at risk of remote crashes but safer against RCE or
1363 heartbleed bug category. We now try to explain this issue in a
1364 message from the configure script. Fixes bug 21290; bugfix
1367 o Minor bugfixes (consensus weight):
1368 - Add new consensus method that initializes bw weights to 1 instead
1369 of 0. This prevents a zero weight from making it all the way to
1370 the end (happens in small testing networks) and causing an error.
1371 Fixes bug 14881; bugfix on 0.2.2.17-alpha.
1373 o Minor bugfixes (crash prevention):
1374 - Fix an (currently untriggerable, but potentially dangerous) crash
1375 bug when base32-encoding inputs whose sizes are not a multiple of
1376 5. Fixes bug 21894; bugfix on 0.2.9.1-alpha.
1378 o Minor bugfixes (dead code):
1379 - Remove a redundant check for PidFile changes at runtime in
1380 options_transition_allowed(): this check is already performed
1381 regardless of whether the sandbox is active. Fixes bug 21123;
1382 bugfix on 0.2.5.4-alpha.
1384 o Minor bugfixes (descriptors):
1385 - Correctly recognise downloaded full descriptors as valid, even
1386 when using microdescriptors as circuits. This affects clients with
1387 FetchUselessDescriptors set, and may affect directory authorities.
1388 Fixes bug 20839; bugfix on 0.2.3.2-alpha.
1390 o Minor bugfixes (directory mirrors):
1391 - Allow relays to use directory mirrors without a DirPort: these
1392 relays need to be contacted over their ORPorts using a begindir
1393 connection. Fixes one case of bug 20711; bugfix on 0.2.8.2-alpha.
1394 - Clarify the message logged when a remote relay is unexpectedly
1395 missing an ORPort or DirPort: users were confusing this with a
1396 local port. Fixes another case of bug 20711; bugfix
1399 o Minor bugfixes (directory system):
1400 - Bridges and relays now use microdescriptors (like clients do)
1401 rather than old-style router descriptors. Now bridges will blend
1402 in with clients in terms of the circuits they build. Fixes bug
1403 6769; bugfix on 0.2.3.2-alpha.
1404 - Download all consensus flavors, descriptors, and authority
1405 certificates when FetchUselessDescriptors is set, regardless of
1406 whether tor is a directory cache or not. Fixes bug 20667; bugfix
1407 on all recent tor versions.
1409 o Minor bugfixes (documentation):
1410 - Update the tor manual page to document every option that can not
1411 be changed while tor is running. Fixes bug 21122.
1413 o Minor bugfixes (ed25519 certificates):
1414 - Correctly interpret ed25519 certificates that would expire some
1415 time after 19 Jan 2038. Fixes bug 20027; bugfix on 0.2.7.2-alpha.
1417 o Minor bugfixes (fallback directories):
1418 - Avoid checking fallback candidates' DirPorts if they are down in
1419 OnionOO. When a relay operator has multiple relays, this
1420 prioritizes relays that are up over relays that are down. Fixes
1421 bug 20926; bugfix on 0.2.8.3-alpha.
1422 - Stop failing when OUTPUT_COMMENTS is True in updateFallbackDirs.py.
1423 Fixes bug 20877; bugfix on 0.2.8.3-alpha.
1424 - Stop failing when a relay has no uptime data in
1425 updateFallbackDirs.py. Fixes bug 20945; bugfix on 0.2.8.1-alpha.
1427 o Minor bugfixes (hidden service):
1428 - Clean up the code for expiring intro points with no associated
1429 circuits. It was causing, rarely, a service with some expiring
1430 introduction points to not open enough additional introduction
1431 points. Fixes part of bug 21302; bugfix on 0.2.7.2-alpha.
1432 - Resolve two possible underflows which could lead to creating and
1433 closing a lot of introduction point circuits in a non-stop loop.
1434 Fixes bug 21302; bugfix on 0.2.7.2-alpha.
1435 - Stop setting the torrc option HiddenServiceStatistics to "0" just
1436 because we're not a bridge or relay. Instead, we preserve whatever
1437 value the user set (or didn't set). Fixes bug 21150; bugfix
1440 o Minor bugfixes (hidden services):
1441 - Make hidden services check for failed intro point connections,
1442 even when they have exceeded their intro point creation limit.
1443 Fixes bug 21596; bugfix on 0.2.7.2-alpha. Reported by Alec Muffett.
1444 - Make hidden services with 8 to 10 introduction points check for
1445 failed circuits immediately after startup. Previously, they would
1446 wait for 5 minutes before performing their first checks. Fixes bug
1447 21594; bugfix on 0.2.3.9-alpha. Reported by Alec Muffett.
1448 - Stop ignoring misconfigured hidden services. Instead, refuse to
1449 start tor until the misconfigurations have been corrected. Fixes
1450 bug 20559; bugfix on multiple commits in 0.2.7.1-alpha
1453 o Minor bugfixes (IPv6):
1454 - Make IPv6-using clients try harder to find an IPv6 directory
1455 server. Fixes bug 20999; bugfix on 0.2.8.2-alpha.
1456 - When IPv6 addresses have not been downloaded yet (microdesc
1457 consensus documents don't list relay IPv6 addresses), use hard-
1458 coded addresses for authorities, fallbacks, and configured
1459 bridges. Now IPv6-only clients can use microdescriptors. Fixes bug
1460 20996; bugfix on b167e82 from 19608 in 0.2.8.5-alpha.
1462 o Minor bugfixes (memory leak at exit):
1463 - Fix a small harmless memory leak at exit of the previously unused
1464 RSA->Ed identity cross-certificate. Fixes bug 17779; bugfix
1467 o Minor bugfixes (onion services):
1468 - Allow the number of introduction points to be as low as 0, rather
1469 than as low as 3. Fixes bug 21033; bugfix on 0.2.7.2-alpha.
1471 o Minor bugfixes (portability):
1472 - Use "OpenBSD" compiler macro instead of "OPENBSD" or "__OpenBSD__".
1473 It is supported by OpenBSD itself, and also by most OpenBSD
1474 variants (such as Bitrig). Fixes bug 20980; bugfix
1477 o Minor bugfixes (portability, also in 0.2.9.9):
1478 - Avoid crashing when Tor is built using headers that contain
1479 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
1480 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
1482 - Fix Libevent detection on platforms without Libevent 1 headers
1483 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
1485 o Minor bugfixes (relay):
1486 - Avoid a double-marked-circuit warning that could happen when we
1487 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
1489 - Honor DataDirectoryGroupReadable when tor is a relay. Previously,
1490 initializing the keys would reset the DataDirectory to 0700
1491 instead of 0750 even if DataDirectoryGroupReadable was set to 1.
1492 Fixes bug 19953; bugfix on 0.0.2pre16. Patch by "redfish".
1494 o Minor bugfixes (testing):
1495 - Fix Raspbian build issues related to missing socket errno in
1496 test_util.c. Fixes bug 21116; bugfix on 0.2.8.2. Patch by "hein".
1497 - Remove undefined behavior from the backtrace generator by removing
1498 its signal handler. Fixes bug 21026; bugfix on 0.2.5.2-alpha.
1499 - Use bash in src/test/test-network.sh. This ensures we reliably
1500 call chutney's newer tools/test-network.sh when available. Fixes
1501 bug 21562; bugfix on 0.2.9.1-alpha.
1503 o Minor bugfixes (tor-resolve):
1504 - The tor-resolve command line tool now rejects hostnames over 255
1505 characters in length. Previously, it would silently truncate them,
1506 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
1507 Patch by "junglefowl".
1509 o Minor bugfixes (unit tests):
1510 - Allow the unit tests to pass even when DNS lookups of bogus
1511 addresses do not fail as expected. Fixes bug 20862 and 20863;
1512 bugfix on unit tests introduced in 0.2.8.1-alpha
1513 through 0.2.9.4-alpha.
1515 o Minor bugfixes (util):
1516 - When finishing writing a file to disk, if we were about to replace
1517 the file with the temporary file created before and we fail to
1518 replace it, remove the temporary file so it doesn't stay on disk.
1519 Fixes bug 20646; bugfix on 0.2.0.7-alpha. Patch by fk.
1521 o Minor bugfixes (Windows services):
1522 - Be sure to initialize the monotonic time subsystem before using
1523 it, even when running as an NT service. Fixes bug 21356; bugfix
1526 o Minor bugfixes (Windows):
1527 - Check for getpagesize before using it to mmap files. This fixes
1528 compilation in some MinGW environments. Fixes bug 20530; bugfix on
1529 0.1.2.1-alpha. Reported by "ice".
1531 o Code simplification and refactoring:
1532 - Abolish all global guard context in entrynodes.c; replace with new
1533 guard_selection_t structure as preparation for proposal 271.
1534 Closes ticket 19858.
1535 - Extract magic numbers in circuituse.c into defined variables.
1536 - Introduce rend_service_is_ephemeral() that tells if given onion
1537 service is ephemeral. Replace unclear NULL-checkings for service
1538 directory with this function. Closes ticket 20526.
1539 - Refactor circuit_is_available_for_use to remove unnecessary check.
1540 - Refactor circuit_predict_and_launch_new for readability and
1541 testability. Closes ticket 18873.
1542 - Refactor code to manipulate global_origin_circuit_list into
1543 separate functions. Closes ticket 20921.
1544 - Refactor large if statement in purpose_needs_anonymity to use
1545 switch statement instead. Closes part of ticket 20077.
1546 - Refactor the hashing API to return negative values for errors, as
1547 is done as throughout the codebase. Closes ticket 20717.
1548 - Remove data structures that were used to index or_connection
1549 objects by their RSA identity digests. These structures are fully
1550 redundant with the similar structures used in the
1551 channel abstraction.
1552 - Remove duplicate code in the channel_write_*cell() functions.
1553 Closes ticket 13827; patch from Pingl.
1554 - Remove redundant behavior of is_sensitive_dir_purpose, refactor to
1555 use only purpose_needs_anonymity. Closes part of ticket 20077.
1556 - The code to generate and parse EXTEND and EXTEND2 cells has been
1557 replaced with code automatically generated by the
1560 o Documentation (formatting):
1561 - Clean up formatting of tor.1 man page and HTML doc, where <pre>
1562 blocks were incorrectly appearing. Closes ticket 20885.
1564 o Documentation (man page):
1565 - Clarify many options in tor.1 and add some min/max values for
1566 HiddenService options. Closes ticket 21058.
1569 - Change '1' to 'weight_scale' in consensus bw weights calculation
1570 comments, as that is reality. Closes ticket 20273. Patch
1572 - Clarify that when ClientRejectInternalAddresses is enabled (which
1573 is the default), multicast DNS hostnames for machines on the local
1574 network (of the form *.local) are also rejected. Closes
1576 - Correct the value for AuthDirGuardBWGuarantee in the manpage, from
1577 250 KBytes to 2 MBytes. Fixes bug 20435; bugfix on 0.2.5.6-alpha.
1578 - Include the "TBits" unit in Tor's man page. Fixes part of bug
1579 20622; bugfix on 0.2.5.1-alpha.
1580 - Small fixes to the fuzzing documentation. Closes ticket 21472.
1581 - Stop the man page from incorrectly stating that HiddenServiceDir
1582 must already exist. Fixes 20486.
1583 - Update the description of the directory server options in the
1584 manual page, to clarify that a relay no longer needs to set
1585 DirPort in order to be a directory cache. Closes ticket 21720.
1588 - The AuthDirMaxServersPerAuthAddr option no longer exists: The same
1589 limit for relays running on a single IP applies to authority IP
1590 addresses as well as to non-authority IP addresses. Closes
1592 - The UseDirectoryGuards torrc option no longer exists: all users
1593 that use entry guards will also use directory guards. Related to
1594 proposal 271; implements part of ticket 20831.
1597 - Add tests for networkstatus_compute_bw_weights_v10.
1598 - Add unit tests circuit_predict_and_launch_new.
1599 - Extract dummy_origin_circuit_new so it can be used by other
1601 - New unit tests for tor_htonll(). Closes ticket 19563. Patch
1602 from "overcaffeinated".
1603 - Perform the coding style checks when running the tests and fail
1604 when coding style violations are found. Closes ticket 5500.
1607 Changes in version 0.2.8.13 - 2017-03-03
1608 Tor 0.2.8.13 backports a security fix from later Tor
1609 releases. Anybody running Tor 0.2.8.12 or earlier should upgrade to this
1610 this release, if for some reason they cannot upgrade to a later
1611 release series, and if they build Tor with the --enable-expensive-hardening
1614 Note that support for Tor 0.2.8.x is ending next year: we will not issue
1615 any fixes for the Tor 0.2.8.x series after 1 Jan 2018. If you need
1616 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
1618 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
1619 - Fix an integer underflow bug when comparing malformed Tor
1620 versions. This bug could crash Tor when built with
1621 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
1622 0.2.9.8, which were built with -ftrapv by default. In other cases
1623 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
1624 on 0.0.8pre1. Found by OSS-Fuzz.
1626 o Minor features (geoip):
1627 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
1631 Changes in version 0.2.7.7 - 2017-03-03
1632 Tor 0.2.7.7 backports a number of security fixes from later Tor
1633 releases. Anybody running Tor 0.2.7.6 or earlier should upgrade to
1634 this release, if for some reason they cannot upgrade to a later
1637 Note that support for Tor 0.2.7.x is ending this year: we will not issue
1638 any fixes for the Tor 0.2.7.x series after 1 August 2017. If you need
1639 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
1641 o Directory authority changes (backport from 0.2.8.5-rc):
1642 - Urras is no longer a directory authority. Closes ticket 19271.
1644 o Directory authority changes (backport from 0.2.9.2-alpha):
1645 - The "Tonga" bridge authority has been retired; the new bridge
1646 authority is "Bifroest". Closes tickets 19728 and 19690.
1648 o Directory authority key updates (backport from 0.2.8.1-alpha):
1649 - Update the V3 identity key for the dannenberg directory authority:
1650 it was changed on 18 November 2015. Closes task 17906. Patch
1653 o Major bugfixes (parsing, security, backport from 0.2.9.8):
1654 - Fix a bug in parsing that could cause clients to read a single
1655 byte past the end of an allocated region. This bug could be used
1656 to cause hardened clients (built with --enable-expensive-hardening)
1657 to crash if they tried to visit a hostile hidden service. Non-
1658 hardened clients are only affected depending on the details of
1659 their platform's memory allocator. Fixes bug 21018; bugfix on
1660 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
1661 2016-12-002 and as CVE-2016-1254.
1663 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
1664 - Stop a crash that could occur when a client running with DNSPort
1665 received a query with multiple address types, and the first
1666 address type was not supported. Found and fixed by Scott Dial.
1667 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
1668 - Prevent a class of security bugs caused by treating the contents
1669 of a buffer chunk as if they were a NUL-terminated string. At
1670 least one such bug seems to be present in all currently used
1671 versions of Tor, and would allow an attacker to remotely crash
1672 most Tor instances, especially those compiled with extra compiler
1673 hardening. With this defense in place, such bugs can't crash Tor,
1674 though we should still fix them as they occur. Closes ticket
1675 20384 (TROVE-2016-10-001).
1677 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
1678 - Avoid a difficult-to-trigger heap corruption attack when extending
1679 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
1680 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
1681 Reported by Guido Vranken.
1683 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
1684 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
1685 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
1687 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
1688 - If OpenSSL fails to generate an RSA key, do not retain a dangling
1689 pointer to the previous (uninitialized) key value. The impact here
1690 should be limited to a difficult-to-trigger crash, if OpenSSL is
1691 running an engine that makes key generation failures possible, or
1692 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
1693 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
1696 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
1697 - Fix an integer underflow bug when comparing malformed Tor
1698 versions. This bug could crash Tor when built with
1699 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
1700 0.2.9.8, which were built with -ftrapv by default. In other cases
1701 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
1702 on 0.0.8pre1. Found by OSS-Fuzz.
1704 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
1705 - Make memwipe() do nothing when passed a NULL pointer or buffer of
1706 zero size. Check size argument to memwipe() for underflow. Fixes
1707 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
1710 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
1711 - Make Tor survive errors involving connections without a
1712 corresponding event object. Previously we'd fail with an
1713 assertion; now we produce a log message. Related to bug 16248.
1715 o Minor features (geoip):
1716 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
1720 Changes in version 0.2.6.11 - 2017-03-03
1721 Tor 0.2.6.11 backports a number of security fixes from later Tor
1722 releases. Anybody running Tor 0.2.6.10 or earlier should upgrade to
1723 this release, if for some reason they cannot upgrade to a later
1726 Note that support for Tor 0.2.6.x is ending this year: we will not issue
1727 any fixes for the Tor 0.2.6.x series after 1 August 2017. If you need
1728 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
1730 o Directory authority changes (backport from 0.2.8.5-rc):
1731 - Urras is no longer a directory authority. Closes ticket 19271.
1733 o Directory authority changes (backport from 0.2.9.2-alpha):
1734 - The "Tonga" bridge authority has been retired; the new bridge
1735 authority is "Bifroest". Closes tickets 19728 and 19690.
1737 o Directory authority key updates (backport from 0.2.8.1-alpha):
1738 - Update the V3 identity key for the dannenberg directory authority:
1739 it was changed on 18 November 2015. Closes task 17906. Patch
1742 o Major features (security fixes, backport from 0.2.9.4-alpha):
1743 - Prevent a class of security bugs caused by treating the contents
1744 of a buffer chunk as if they were a NUL-terminated string. At
1745 least one such bug seems to be present in all currently used
1746 versions of Tor, and would allow an attacker to remotely crash
1747 most Tor instances, especially those compiled with extra compiler
1748 hardening. With this defense in place, such bugs can't crash Tor,
1749 though we should still fix them as they occur. Closes ticket
1750 20384 (TROVE-2016-10-001).
1752 o Major bugfixes (parsing, security, backport from 0.2.9.8):
1753 - Fix a bug in parsing that could cause clients to read a single
1754 byte past the end of an allocated region. This bug could be used
1755 to cause hardened clients (built with --enable-expensive-hardening)
1756 to crash if they tried to visit a hostile hidden service. Non-
1757 hardened clients are only affected depending on the details of
1758 their platform's memory allocator. Fixes bug 21018; bugfix on
1759 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
1760 2016-12-002 and as CVE-2016-1254.
1762 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
1763 - Stop a crash that could occur when a client running with DNSPort
1764 received a query with multiple address types, and the first
1765 address type was not supported. Found and fixed by Scott Dial.
1766 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
1768 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
1769 - Fix an error that could cause us to read 4 bytes before the
1770 beginning of an openssl string. This bug could be used to cause
1771 Tor to crash on systems with unusual malloc implementations, or
1772 systems with unusual hardening installed. Fixes bug 17404; bugfix
1775 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
1776 - Avoid a difficult-to-trigger heap corruption attack when extending
1777 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
1778 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
1779 Reported by Guido Vranken.
1781 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
1782 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
1783 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
1785 o Major bugfixes (guard selection, backport from 0.2.7.6):
1786 - Actually look at the Guard flag when selecting a new directory
1787 guard. When we implemented the directory guard design, we
1788 accidentally started treating all relays as if they have the Guard
1789 flag during guard selection, leading to weaker anonymity and worse
1790 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
1793 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
1794 - If OpenSSL fails to generate an RSA key, do not retain a dangling
1795 pointer to the previous (uninitialized) key value. The impact here
1796 should be limited to a difficult-to-trigger crash, if OpenSSL is
1797 running an engine that makes key generation failures possible, or
1798 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
1799 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
1802 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
1803 - Fix an integer underflow bug when comparing malformed Tor
1804 versions. This bug could crash Tor when built with
1805 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
1806 0.2.9.8, which were built with -ftrapv by default. In other cases
1807 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
1808 on 0.0.8pre1. Found by OSS-Fuzz.
1810 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
1811 - Make memwipe() do nothing when passed a NULL pointer or buffer of
1812 zero size. Check size argument to memwipe() for underflow. Fixes
1813 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
1816 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
1817 - Make Tor survive errors involving connections without a
1818 corresponding event object. Previously we'd fail with an
1819 assertion; now we produce a log message. Related to bug 16248.
1821 o Minor features (geoip):
1822 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
1825 o Minor bugfixes (compilation, backport from 0.2.7.6):
1826 - Fix a compilation warning with Clang 3.6: Do not check the
1827 presence of an address which can never be NULL. Fixes bug 17781.
1830 Changes in version 0.2.5.13 - 2017-03-03
1831 Tor 0.2.5.13 backports a number of security fixes from later Tor
1832 releases. Anybody running Tor 0.2.5.13 or earlier should upgrade to
1833 this release, if for some reason they cannot upgrade to a later
1836 Note that support for Tor 0.2.5.x is ending next year: we will not issue
1837 any fixes for the Tor 0.2.5.x series after 1 May 2018. If you need
1838 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
1840 o Directory authority changes (backport from 0.2.8.5-rc):
1841 - Urras is no longer a directory authority. Closes ticket 19271.
1843 o Directory authority changes (backport from 0.2.9.2-alpha):
1844 - The "Tonga" bridge authority has been retired; the new bridge
1845 authority is "Bifroest". Closes tickets 19728 and 19690.
1847 o Directory authority key updates (backport from 0.2.8.1-alpha):
1848 - Update the V3 identity key for the dannenberg directory authority:
1849 it was changed on 18 November 2015. Closes task 17906. Patch
1852 o Major features (security fixes, backport from 0.2.9.4-alpha):
1853 - Prevent a class of security bugs caused by treating the contents
1854 of a buffer chunk as if they were a NUL-terminated string. At
1855 least one such bug seems to be present in all currently used
1856 versions of Tor, and would allow an attacker to remotely crash
1857 most Tor instances, especially those compiled with extra compiler
1858 hardening. With this defense in place, such bugs can't crash Tor,
1859 though we should still fix them as they occur. Closes ticket
1860 20384 (TROVE-2016-10-001).
1862 o Major bugfixes (parsing, security, backport from 0.2.9.8):
1863 - Fix a bug in parsing that could cause clients to read a single
1864 byte past the end of an allocated region. This bug could be used
1865 to cause hardened clients (built with --enable-expensive-hardening)
1866 to crash if they tried to visit a hostile hidden service. Non-
1867 hardened clients are only affected depending on the details of
1868 their platform's memory allocator. Fixes bug 21018; bugfix on
1869 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
1870 2016-12-002 and as CVE-2016-1254.
1872 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
1873 - Stop a crash that could occur when a client running with DNSPort
1874 received a query with multiple address types, and the first
1875 address type was not supported. Found and fixed by Scott Dial.
1876 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
1878 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
1879 - Fix an error that could cause us to read 4 bytes before the
1880 beginning of an openssl string. This bug could be used to cause
1881 Tor to crash on systems with unusual malloc implementations, or
1882 systems with unusual hardening installed. Fixes bug 17404; bugfix
1885 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
1886 - Avoid a difficult-to-trigger heap corruption attack when extending
1887 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
1888 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
1889 Reported by Guido Vranken.
1891 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
1892 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
1893 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
1895 o Major bugfixes (guard selection, backport from 0.2.7.6):
1896 - Actually look at the Guard flag when selecting a new directory
1897 guard. When we implemented the directory guard design, we
1898 accidentally started treating all relays as if they have the Guard
1899 flag during guard selection, leading to weaker anonymity and worse
1900 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
1903 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
1904 - If OpenSSL fails to generate an RSA key, do not retain a dangling
1905 pointer to the previous (uninitialized) key value. The impact here
1906 should be limited to a difficult-to-trigger crash, if OpenSSL is
1907 running an engine that makes key generation failures possible, or
1908 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
1909 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
1912 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
1913 - Fix an integer underflow bug when comparing malformed Tor
1914 versions. This bug could crash Tor when built with
1915 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
1916 0.2.9.8, which were built with -ftrapv by default. In other cases
1917 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
1918 on 0.0.8pre1. Found by OSS-Fuzz.
1920 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
1921 - Make memwipe() do nothing when passed a NULL pointer or buffer of
1922 zero size. Check size argument to memwipe() for underflow. Fixes
1923 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
1926 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
1927 - Make Tor survive errors involving connections without a
1928 corresponding event object. Previously we'd fail with an
1929 assertion; now we produce a log message. Related to bug 16248.
1931 o Minor features (geoip):
1932 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
1935 o Minor bugfixes (compilation, backport from 0.2.7.6):
1936 - Fix a compilation warning with Clang 3.6: Do not check the
1937 presence of an address which can never be NULL. Fixes bug 17781.
1939 o Minor bugfixes (crypto error-handling, backport from 0.2.7.2-alpha):
1940 - Check for failures from crypto_early_init, and refuse to continue.
1941 A previous typo meant that we could keep going with an
1942 uninitialized crypto library, and would have OpenSSL initialize
1943 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
1944 when implementing ticket 4900. Patch by "teor".
1946 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
1947 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
1948 a client authorized hidden service. Fixes bug 15823; bugfix
1952 Changes in version 0.2.4.28 - 2017-03-03
1953 Tor 0.2.4.28 backports a number of security fixes from later Tor
1954 releases. Anybody running Tor 0.2.4.27 or earlier should upgrade to
1955 this release, if for some reason they cannot upgrade to a later
1958 Note that support for Tor 0.2.4.x is ending soon: we will not issue
1959 any fixes for the Tor 0.2.4.x series after 1 August 2017. If you need
1960 a Tor release series with long-term support, we recommend Tor 0.2.9.x.
1962 o Directory authority changes (backport from 0.2.8.5-rc):
1963 - Urras is no longer a directory authority. Closes ticket 19271.
1965 o Directory authority changes (backport from 0.2.9.2-alpha):
1966 - The "Tonga" bridge authority has been retired; the new bridge
1967 authority is "Bifroest". Closes tickets 19728 and 19690.
1969 o Directory authority key updates (backport from 0.2.8.1-alpha):
1970 - Update the V3 identity key for the dannenberg directory authority:
1971 it was changed on 18 November 2015. Closes task 17906. Patch
1974 o Major features (security fixes, backport from 0.2.9.4-alpha):
1975 - Prevent a class of security bugs caused by treating the contents
1976 of a buffer chunk as if they were a NUL-terminated string. At
1977 least one such bug seems to be present in all currently used
1978 versions of Tor, and would allow an attacker to remotely crash
1979 most Tor instances, especially those compiled with extra compiler
1980 hardening. With this defense in place, such bugs can't crash Tor,
1981 though we should still fix them as they occur. Closes ticket
1982 20384 (TROVE-2016-10-001).
1984 o Major bugfixes (parsing, security, backport from 0.2.9.8):
1985 - Fix a bug in parsing that could cause clients to read a single
1986 byte past the end of an allocated region. This bug could be used
1987 to cause hardened clients (built with --enable-expensive-hardening)
1988 to crash if they tried to visit a hostile hidden service. Non-
1989 hardened clients are only affected depending on the details of
1990 their platform's memory allocator. Fixes bug 21018; bugfix on
1991 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
1992 2016-12-002 and as CVE-2016-1254.
1994 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
1995 - Fix an error that could cause us to read 4 bytes before the
1996 beginning of an openssl string. This bug could be used to cause
1997 Tor to crash on systems with unusual malloc implementations, or
1998 systems with unusual hardening installed. Fixes bug 17404; bugfix
2001 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
2002 - Avoid a difficult-to-trigger heap corruption attack when extending
2003 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
2004 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
2005 Reported by Guido Vranken.
2007 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
2008 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
2009 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
2011 o Major bugfixes (guard selection, backport from 0.2.7.6):
2012 - Actually look at the Guard flag when selecting a new directory
2013 guard. When we implemented the directory guard design, we
2014 accidentally started treating all relays as if they have the Guard
2015 flag during guard selection, leading to weaker anonymity and worse
2016 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
2019 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
2020 - If OpenSSL fails to generate an RSA key, do not retain a dangling
2021 pointer to the previous (uninitialized) key value. The impact here
2022 should be limited to a difficult-to-trigger crash, if OpenSSL is
2023 running an engine that makes key generation failures possible, or
2024 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
2025 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
2028 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
2029 - Fix an integer underflow bug when comparing malformed Tor
2030 versions. This bug could crash Tor when built with
2031 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
2032 0.2.9.8, which were built with -ftrapv by default. In other cases
2033 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
2034 on 0.0.8pre1. Found by OSS-Fuzz.
2036 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
2037 - Make memwipe() do nothing when passed a NULL pointer or buffer of
2038 zero size. Check size argument to memwipe() for underflow. Fixes
2039 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
2042 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
2043 - Make Tor survive errors involving connections without a
2044 corresponding event object. Previously we'd fail with an
2045 assertion; now we produce a log message. Related to bug 16248.
2047 o Minor features (DoS-resistance, backport from 0.2.7.1-alpha):
2048 - Make it harder for attackers to overload hidden services with
2049 introductions, by blocking multiple introduction requests on the
2050 same circuit. Resolves ticket 15515.
2052 o Minor features (geoip):
2053 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
2056 o Minor bugfixes (compilation, backport from 0.2.7.6):
2057 - Fix a compilation warning with Clang 3.6: Do not check the
2058 presence of an address which can never be NULL. Fixes bug 17781.
2060 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
2061 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
2062 a client authorized hidden service. Fixes bug 15823; bugfix
2066 Changes in version 0.2.9.10 - 2017-03-01
2067 Tor 0.2.9.10 backports a security fix from later Tor release. It also
2068 includes fixes for some major issues affecting directory authorities,
2069 LibreSSL compatibility, and IPv6 correctness.
2071 The Tor 0.2.9.x release series is now marked as a long-term-support
2072 series. We intend to backport security fixes to 0.2.9.x until at
2073 least January of 2020.
2075 o Major bugfixes (directory authority, 0.3.0.3-alpha):
2076 - During voting, when marking a relay as a probable sybil, do not
2077 clear its BadExit flag: sybils can still be bad in other ways
2078 too. (We still clear the other flags.) Fixes bug 21108; bugfix
2081 o Major bugfixes (IPv6 Exits, backport from 0.3.0.3-alpha):
2082 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
2083 any IPv6 addresses. Instead, only reject a port over IPv6 if the
2084 exit policy rejects that port on more than an IPv6 /16 of
2085 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
2086 which rejected a relay's own IPv6 address by default. Fixes bug
2087 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
2089 o Major bugfixes (parsing, also in 0.3.0.4-rc):
2090 - Fix an integer underflow bug when comparing malformed Tor
2091 versions. This bug could crash Tor when built with
2092 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
2093 0.2.9.8, which were built with -ftrapv by default. In other cases
2094 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
2095 on 0.0.8pre1. Found by OSS-Fuzz.
2097 o Minor features (directory authorities, also in 0.3.0.4-rc):
2098 - Directory authorities now reject descriptors that claim to be
2099 malformed versions of Tor. Helps prevent exploitation of
2101 - Reject version numbers with components that exceed INT32_MAX.
2102 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
2103 Fixes bug 21450; bugfix on 0.0.8pre1.
2105 o Minor features (geoip):
2106 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
2109 o Minor features (portability, compilation, backport from 0.3.0.3-alpha):
2110 - Autoconf now checks to determine if OpenSSL structures are opaque,
2111 instead of explicitly checking for OpenSSL version numbers. Part
2113 - Support building with recent LibreSSL code that uses opaque
2114 structures. Closes ticket 21359.
2116 o Minor bugfixes (code correctness, also in 0.3.0.4-rc):
2117 - Repair a couple of (unreachable or harmless) cases of the risky
2118 comparison-by-subtraction pattern that caused bug 21278.
2120 o Minor bugfixes (tor-resolve, backport from 0.3.0.3-alpha):
2121 - The tor-resolve command line tool now rejects hostnames over 255
2122 characters in length. Previously, it would silently truncate them,
2123 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
2124 Patch by "junglefowl".
2127 Changes in version 0.2.9.9 - 2017-01-23
2128 Tor 0.2.9.9 fixes a denial-of-service bug where an attacker could
2129 cause relays and clients to crash, even if they were not built with
2130 the --enable-expensive-hardening option. This bug affects all 0.2.9.x
2131 versions, and also affects 0.3.0.1-alpha: all relays running an affected
2132 version should upgrade.
2134 This release also resolves a client-side onion service reachability
2135 bug, and resolves a pair of small portability issues.
2137 o Major bugfixes (security):
2138 - Downgrade the "-ftrapv" option from "always on" to "only on when
2139 --enable-expensive-hardening is provided." This hardening option,
2140 like others, can turn survivable bugs into crashes -- and having
2141 it on by default made a (relatively harmless) integer overflow bug
2142 into a denial-of-service bug. Fixes bug 21278 (TROVE-2017-001);
2143 bugfix on 0.2.9.1-alpha.
2145 o Major bugfixes (client, onion service):
2146 - Fix a client-side onion service reachability bug, where multiple
2147 socks requests to an onion service (or a single slow request)
2148 could cause us to mistakenly mark some of the service's
2149 introduction points as failed, and we cache that failure so
2150 eventually we run out and can't reach the service. Also resolves a
2151 mysterious "Remote server sent bogus reason code 65021" log
2152 warning. The bug was introduced in ticket 17218, where we tried to
2153 remember the circuit end reason as a uint16_t, which mangled
2154 negative values. Partially fixes bug 21056 and fixes bug 20307;
2155 bugfix on 0.2.8.1-alpha.
2157 o Minor features (geoip):
2158 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
2161 o Minor bugfixes (portability):
2162 - Avoid crashing when Tor is built using headers that contain
2163 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
2164 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
2166 - Fix Libevent detection on platforms without Libevent 1 headers
2167 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
2170 Changes in version 0.2.8.12 - 2016-12-19
2171 Tor 0.2.8.12 backports a fix for a medium-severity issue (bug 21018
2172 below) where Tor clients could crash when attempting to visit a
2173 hostile hidden service. Clients are recommended to upgrade as packages
2174 become available for their systems.
2176 It also includes an updated list of fallback directories, backported
2179 Now that the Tor 0.2.9 series is stable, only major bugfixes will be
2180 backported to 0.2.8 in the future.
2182 o Major bugfixes (parsing, security, backported from 0.2.9.8):
2183 - Fix a bug in parsing that could cause clients to read a single
2184 byte past the end of an allocated region. This bug could be used
2185 to cause hardened clients (built with --enable-expensive-hardening)
2186 to crash if they tried to visit a hostile hidden service. Non-
2187 hardened clients are only affected depending on the details of
2188 their platform's memory allocator. Fixes bug 21018; bugfix on
2189 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
2190 2016-12-002 and as CVE-2016-1254.
2192 o Minor features (fallback directory list, backported from 0.2.9.8):
2193 - Replace the 81 remaining fallbacks of the 100 originally
2194 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
2195 fallbacks (123 new, 54 existing, 27 removed) generated in December
2196 2016. Resolves ticket 20170.
2198 o Minor features (geoip, backported from 0.2.9.7-rc):
2199 - Update geoip and geoip6 to the December 7 2016 Maxmind GeoLite2
2203 Changes in version 0.2.9.8 - 2016-12-19
2204 Tor 0.2.9.8 is the first stable release of the Tor 0.2.9 series.
2206 The Tor 0.2.9 series makes mandatory a number of security features
2207 that were formerly optional. It includes support for a new shared-
2208 randomness protocol that will form the basis for next generation
2209 hidden services, includes a single-hop hidden service mode for
2210 optimizing .onion services that don't actually want to be hidden,
2211 tries harder not to overload the directory authorities with excessive
2212 downloads, and supports a better protocol versioning scheme for
2213 improved compatibility with other implementations of the Tor protocol.
2215 And of course, there are numerous other bugfixes and improvements.
2217 This release also includes a fix for a medium-severity issue (bug
2218 21018 below) where Tor clients could crash when attempting to visit a
2219 hostile hidden service. Clients are recommended to upgrade as packages
2220 become available for their systems.
2222 Below are listed the changes since Tor 0.2.8.11. For a list of
2223 changes since 0.2.9.7-rc, see the ChangeLog file.
2225 o New system requirements:
2226 - When building with OpenSSL, Tor now requires version 1.0.1 or
2227 later. OpenSSL 1.0.0 and earlier are no longer supported by the
2228 OpenSSL team, and should not be used. Closes ticket 20303.
2229 - Tor now requires Libevent version 2.0.10-stable or later. Older
2230 versions of Libevent have less efficient backends for several
2231 platforms, and lack the DNS code that we use for our server-side
2232 DNS support. This implements ticket 19554.
2233 - Tor now requires zlib version 1.2 or later, for security,
2234 efficiency, and (eventually) gzip support. (Back when we started,
2235 zlib 1.1 and zlib 1.0 were still found in the wild. 1.2 was
2236 released in 2003. We recommend the latest version.)
2238 o Deprecated features:
2239 - A number of DNS-cache-related sub-options for client ports are now
2240 deprecated for security reasons, and may be removed in a future
2241 version of Tor. (We believe that client-side DNS caching is a bad
2242 idea for anonymity, and you should not turn it on.) The options
2243 are: CacheDNS, CacheIPv4DNS, CacheIPv6DNS, UseDNSCache,
2244 UseIPv4Cache, and UseIPv6Cache.
2245 - A number of options are deprecated for security reasons, and may
2246 be removed in a future version of Tor. The options are:
2247 AllowDotExit, AllowInvalidNodes, AllowSingleHopCircuits,
2248 AllowSingleHopExits, ClientDNSRejectInternalAddresses,
2249 CloseHSClientCircuitsImmediatelyOnTimeout,
2250 CloseHSServiceRendCircuitsImmediatelyOnTimeout,
2251 ExcludeSingleHopRelays, FastFirstHopPK, TLSECGroup,
2252 UseNTorHandshake, and WarnUnsafeSocks.
2253 - The *ListenAddress options are now deprecated as unnecessary: the
2254 corresponding *Port options should be used instead. These options
2255 may someday be removed. The affected options are:
2256 ControlListenAddress, DNSListenAddress, DirListenAddress,
2257 NATDListenAddress, ORListenAddress, SocksListenAddress,
2258 and TransListenAddress.
2260 o Major bugfixes (parsing, security, new since 0.2.9.7-rc):
2261 - Fix a bug in parsing that could cause clients to read a single
2262 byte past the end of an allocated region. This bug could be used
2263 to cause hardened clients (built with --enable-expensive-hardening)
2264 to crash if they tried to visit a hostile hidden service. Non-
2265 hardened clients are only affected depending on the details of
2266 their platform's memory allocator. Fixes bug 21018; bugfix on
2267 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
2268 2016-12-002 and as CVE-2016-1254.
2270 o Major features (build, hardening):
2271 - Tor now builds with -ftrapv by default on compilers that support
2272 it. This option detects signed integer overflow (which C forbids),
2273 and turns it into a hard-failure. We do not apply this option to
2274 code that needs to run in constant time to avoid side-channels;
2275 instead, we use -fwrapv in that code. Closes ticket 17983.
2276 - When --enable-expensive-hardening is selected, stop applying the
2277 clang/gcc sanitizers to code that needs to run in constant time.
2278 Although we are aware of no introduced side-channels, we are not
2279 able to prove that there are none. Related to ticket 17983.
2281 o Major features (circuit building, security):
2282 - Authorities, relays, and clients now require ntor keys in all
2283 descriptors, for all hops (except for rare hidden service protocol
2284 cases), for all circuits, and for all other roles. Part of
2286 - Authorities, relays, and clients only use ntor, except for
2287 rare cases in the hidden service protocol. Part of ticket 19163.
2289 o Major features (compilation):
2290 - Our big list of extra GCC warnings is now enabled by default when
2291 building with GCC (or with anything like Clang that claims to be
2292 GCC-compatible). To make all warnings into fatal compilation
2293 errors, pass --enable-fatal-warnings to configure. Closes
2295 - Use the Autoconf macro AC_USE_SYSTEM_EXTENSIONS to automatically
2296 turn on C and POSIX extensions. (Previously, we attempted to do
2297 this on an ad hoc basis.) Closes ticket 19139.
2299 o Major features (directory authorities, hidden services):
2300 - Directory authorities can now perform the shared randomness
2301 protocol specified by proposal 250. Using this protocol, directory
2302 authorities generate a global fresh random value every day. In the
2303 future, this value will be used by hidden services to select
2304 HSDirs. This release implements the directory authority feature;
2305 the hidden service side will be implemented in the future as part
2306 of proposal 224. Resolves ticket 16943; implements proposal 250.
2308 o Major features (downloading, random exponential backoff):
2309 - When we fail to download an object from a directory service, wait
2310 for an (exponentially increasing) randomized amount of time before
2311 retrying, rather than a fixed interval as we did before. This
2312 prevents a group of Tor instances from becoming too synchronized,
2313 or a single Tor instance from becoming too predictable, in its
2314 download schedule. Closes ticket 15942.
2316 o Major features (resource management):
2317 - Tor can now notice it is about to run out of sockets, and
2318 preemptively close connections of lower priority. (This feature is
2319 off by default for now, since the current prioritizing method is
2320 yet not mature enough. You can enable it by setting
2321 "DisableOOSCheck 0", but watch out: it might close some sockets
2322 you would rather have it keep.) Closes ticket 18640.
2324 o Major features (single-hop "hidden" services):
2325 - Add experimental HiddenServiceSingleHopMode and
2326 HiddenServiceNonAnonymousMode options. When both are set to 1,
2327 every hidden service on that Tor instance becomes a non-anonymous
2328 Single Onion Service. Single Onions make one-hop (direct)
2329 connections to their introduction and rendezvous points. One-hop
2330 circuits make Single Onion servers easily locatable, but clients
2331 remain location-anonymous. This is compatible with the existing
2332 hidden service implementation, and works on the current Tor
2333 network without any changes to older relays or clients. Implements
2334 proposal 260, completes ticket 17178. Patch by teor and asn.
2336 o Major features (subprotocol versions):
2337 - Tor directory authorities now vote on a set of recommended
2338 "subprotocol versions", and on a set of required subprotocol
2339 versions. Clients and relays that lack support for a _required_
2340 subprotocol version will not start; those that lack support for a
2341 _recommended_ subprotocol version will warn the user to upgrade.
2342 This change allows compatible implementations of the Tor protocol(s)
2343 to exist without pretending to be 100% bug-compatible with
2344 particular releases of Tor itself. Closes ticket 19958; implements
2345 part of proposal 264.
2347 o Major bugfixes (circuit building):
2348 - Hidden service client-to-intro-point and service-to-rendezvous-
2349 point circuits use the TAP key supplied by the protocol, to avoid
2350 epistemic attacks. Fixes bug 19163; bugfix on 0.2.4.18-rc.
2352 o Major bugfixes (download scheduling):
2353 - Avoid resetting download status for consensuses hourly, since we
2354 already have another, smarter retry mechanism. Fixes bug 8625;
2355 bugfix on 0.2.0.9-alpha.
2356 - If a consensus expires while we are waiting for certificates to
2357 download, stop waiting for certificates.
2358 - If we stop waiting for certificates less than a minute after we
2359 started downloading them, do not consider the certificate download
2360 failure a separate failure. Fixes bug 20533; bugfix
2362 - When using exponential backoff in test networks, use a lower
2363 exponent, so the delays do not vary as much. This helps test
2364 networks bootstrap consistently. Fixes bug 20597; bugfix on 20499.
2366 o Major bugfixes (exit policies):
2367 - Avoid disclosing exit outbound bind addresses, configured port
2368 bind addresses, and local interface addresses in relay descriptors
2369 by default under ExitPolicyRejectPrivate. Instead, only reject
2370 these (otherwise unlisted) addresses if
2371 ExitPolicyRejectLocalInterfaces is set. Fixes bug 18456; bugfix on
2372 0.2.7.2-alpha. Patch by teor.
2374 o Major bugfixes (hidden services):
2375 - Allow Tor clients with appropriate controllers to work with
2376 FetchHidServDescriptors set to 0. Previously, this option also
2377 disabled descriptor cache lookup, thus breaking hidden services
2378 entirely. Fixes bug 18704; bugfix on 0.2.0.20-rc. Patch by "twim".
2379 - Clients now require hidden services to include the TAP keys for
2380 their intro points in the hidden service descriptor. This prevents
2381 an inadvertent upgrade to ntor, which a malicious hidden service
2382 could use to distinguish clients by consensus version. Fixes bug
2383 20012; bugfix on 0.2.4.8-alpha. Patch by teor.
2385 o Major bugfixes (relay, resolver, logging):
2386 - For relays that don't know their own address, avoid attempting a
2387 local hostname resolve for each descriptor we download. This
2388 will cut down on the number of "Success: chose address 'x.x.x.x'"
2389 log lines, and also avoid confusing clock jumps if the resolver
2390 is slow. Fixes bugs 20423 and 20610; bugfix on 0.2.8.1-alpha.
2392 o Minor features (port flags):
2393 - Add new flags to the *Port options to give finer control over which
2394 requests are allowed. The flags are NoDNSRequest, NoOnionTraffic,
2395 and the synthetic flag OnionTrafficOnly, which is equivalent to
2396 NoDNSRequest, NoIPv4Traffic, and NoIPv6Traffic. Closes enhancement
2397 18693; patch by "teor".
2399 o Minor features (build, hardening):
2400 - Detect and work around a libclang_rt problem that would prevent
2401 clang from finding __mulodi4() on some 32-bit platforms, and thus
2402 keep -ftrapv from linking on those systems. Closes ticket 19079.
2403 - When building on a system without runtime support for the runtime
2404 hardening options, try to log a useful warning at configuration
2405 time, rather than an incomprehensible warning at link time. If
2406 expensive hardening was requested, this warning becomes an error.
2407 Closes ticket 18895.
2409 o Minor features (client, directory):
2410 - Since authorities now omit all routers that lack the Running and
2411 Valid flags, we assume that any relay listed in the consensus must
2412 have those flags. Closes ticket 20001; implements part of
2415 o Minor features (code safety):
2416 - In our integer-parsing functions, ensure that the maximum value we
2417 allow is no smaller than the minimum value. Closes ticket 19063;
2418 patch from "U+039b".
2420 o Minor features (compilation, portability):
2421 - Compile correctly on MacOS 10.12 (aka "Sierra"). Closes
2424 o Minor features (config):
2425 - Warn users when descriptor and port addresses are inconsistent.
2426 Mitigates bug 13953; patch by teor.
2428 o Minor features (controller):
2429 - Allow controllers to configure basic client authorization on
2430 hidden services when they create them with the ADD_ONION controller
2431 command. Implements ticket 15588. Patch by "special".
2432 - Fire a STATUS_SERVER controller event whenever the hibernation
2433 status changes between "awake"/"soft"/"hard". Closes ticket 18685.
2434 - Implement new GETINFO queries for all downloads that use
2435 download_status_t to schedule retries. This allows controllers to
2436 examine the schedule for pending downloads. Closes ticket 19323.
2438 o Minor features (development tools, etags):
2439 - Teach the "make tags" Makefile target how to correctly find
2440 "MOCK_IMPL" function definitions. Patch from nherring; closes
2443 o Minor features (directory authority):
2444 - After voting, if the authorities decide that a relay is not
2445 "Valid", they no longer include it in the consensus at all. Closes
2446 ticket 20002; implements part of proposal 272.
2447 - Directory authorities now only give the Guard flag to a relay if
2448 they are also giving it the Stable flag. This change allows us to
2449 simplify path selection for clients. It should have minimal effect
2450 in practice, since >99% of Guards already have the Stable flag.
2451 Implements ticket 18624.
2452 - Directory authorities now write their v3-status-votes file out to
2453 disk earlier in the consensus process, so we have a record of the
2454 votes even if we abort the consensus process. Resolves
2457 o Minor features (fallback directory list, new since 0.2.9.7-rc):
2458 - Replace the 81 remaining fallbacks of the 100 originally
2459 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
2460 fallbacks (123 new, 54 existing, 27 removed) generated in December
2461 2016. Resolves ticket 20170.
2463 o Minor features (hidden service):
2464 - Stop being so strict about the payload length of "rendezvous1"
2465 cells. We used to be locked in to the "TAP" handshake length, and
2466 now we can handle better handshakes like "ntor". Resolves
2469 o Minor features (infrastructure, time):
2470 - Tor now includes an improved timer backend, so that we can
2471 efficiently support tens or hundreds of thousands of concurrent
2472 timers, as will be needed for some of our planned anti-traffic-
2473 analysis work. This code is based on William Ahern's "timeout.c"
2474 project, which implements a "tickless hierarchical timing wheel".
2475 Closes ticket 18365.
2476 - Tor now uses the operating system's monotonic timers (where
2477 available) for internal fine-grained timing. Previously we would
2478 look at the system clock, and then attempt to compensate for the
2479 clock running backwards. Closes ticket 18908.
2481 o Minor features (logging):
2482 - Add a set of macros to check nonfatal assertions, for internal
2483 use. Migrating more of our checks to these should help us avoid
2484 needless crash bugs. Closes ticket 18613.
2485 - Provide a more useful warning message when configured with an
2486 invalid Nickname. Closes ticket 18300; patch from "icanhasaccount".
2487 - When dumping unparseable router descriptors, optionally store them
2488 in separate files, named by digest, up to a configurable size
2489 limit. You can change the size limit by setting the
2490 MaxUnparseableDescSizeToLog option, and disable this feature by
2491 setting that option to 0. Closes ticket 18322.
2493 o Minor features (performance):
2494 - Change the "optimistic data" extension from "off by default" to
2495 "on by default". The default was ordinarily overridden by a
2496 consensus option, but when clients were bootstrapping for the
2497 first time, they would not have a consensus to get the option
2498 from. Changing this default saves a round-trip during startup.
2499 Closes ticket 18815.
2501 o Minor features (relay, usability):
2502 - When the directory authorities refuse a bad relay's descriptor,
2503 encourage the relay operator to contact us. Many relay operators
2504 won't notice this line in their logs, but it's a win if even a few
2505 learn why we don't like what their relay was doing. Resolves
2508 o Minor features (security, TLS):
2509 - Servers no longer support clients that lack AES ciphersuites.
2510 (3DES is no longer considered an acceptable cipher.) We believe
2511 that no such Tor clients currently exist, since Tor has required
2512 OpenSSL 0.9.7 or later since 2009. Closes ticket 19998.
2514 o Minor features (testing):
2515 - Disable memory protections on OpenBSD when performing our unit
2516 tests for memwipe(). The test deliberately invokes undefined
2517 behavior, and the OpenBSD protections interfere with this. Patch
2518 from "rubiate". Closes ticket 20066.
2519 - Move the test-network.sh script to chutney, and modify tor's test-
2520 network.sh to call the (newer) chutney version when available.
2521 Resolves ticket 19116. Patch by teor.
2522 - Use the lcov convention for marking lines as unreachable, so that
2523 we don't count them when we're generating test coverage data.
2524 Update our coverage tools to understand this convention. Closes
2526 - Our link-handshake unit tests now check that when invalid
2527 handshakes fail, they fail with the error messages we expected.
2528 - Our unit testing code that captures log messages no longer
2529 prevents them from being written out if the user asked for them
2530 (by passing --debug or --info or --notice or --warn to the "test"
2531 binary). This change prevents us from missing unexpected log
2532 messages simply because we were looking for others. Related to
2534 - The unit tests now log all warning messages with the "BUG" flag.
2535 Previously, they only logged errors by default. This change will
2536 help us make our testing code more correct, and make sure that we
2537 only hit this code when we mean to. In the meantime, however,
2538 there will be more warnings in the unit test logs than before.
2539 This is preparatory work for ticket 19999.
2540 - The unit tests now treat any failure of a "tor_assert_nonfatal()"
2541 assertion as a test failure.
2542 - We've done significant work to make the unit tests run faster.
2544 o Minor features (testing, ipv6):
2545 - Add the hs-ipv6 chutney target to make test-network-all's IPv6
2546 tests. Remove bridges+hs, as it's somewhat redundant. This
2547 requires a recent chutney version that supports IPv6 clients,
2548 relays, and authorities. Closes ticket 20069; patch by teor.
2549 - Add the single-onion and single-onion-ipv6 chutney targets to
2550 "make test-network-all". This requires a recent chutney version
2551 with the single onion network flavors (git c72a652 or later).
2552 Closes ticket 20072; patch by teor.
2554 o Minor features (Tor2web):
2555 - Make Tor2web clients respect ReachableAddresses. This feature was
2556 inadvertently enabled in 0.2.8.6, then removed by bugfix 19973 on
2557 0.2.8.7. Implements feature 20034. Patch by teor.
2559 o Minor features (unix domain sockets):
2560 - When configuring a unix domain socket for a SocksPort,
2561 ControlPort, or Hidden service, you can now wrap the address in
2562 quotes, using C-style escapes inside the quotes. This allows unix
2563 domain socket paths to contain spaces. Resolves ticket 18753.
2565 o Minor features (user interface):
2566 - Tor now supports the ability to declare options deprecated, so
2567 that we can recommend that people stop using them. Previously, this
2568 was done in an ad-hoc way. There is a new --list-deprecated-options
2569 command-line option to list all of the deprecated options. Closes
2572 o Minor features (virtual addresses):
2573 - Increase the maximum number of bits for the IPv6 virtual network
2574 prefix from 16 to 104. In this way, the condition for address
2575 allocation is less restrictive. Closes ticket 20151; feature
2578 o Minor bug fixes (circuits):
2579 - Use the CircuitBuildTimeout option whenever
2580 LearnCircuitBuildTimeout is disabled. Previously, we would respect
2581 the option when a user disabled it, but not when it was disabled
2582 because some other option was set. Fixes bug 20073; bugfix on
2583 0.2.4.12-alpha. Patch by teor.
2585 o Minor bugfixes (build):
2586 - The current Git revision when building from a local repository is
2587 now detected correctly when using git worktrees. Fixes bug 20492;
2588 bugfix on 0.2.3.9-alpha.
2590 o Minor bugfixes (relay address discovery):
2591 - Stop reordering IP addresses returned by the OS. This makes it
2592 more likely that Tor will guess the same relay IP address every
2593 time. Fixes issue 20163; bugfix on 0.2.7.1-alpha, ticket 17027.
2594 Reported by René Mayrhofer, patch by "cypherpunks".
2596 o Minor bugfixes (memory allocation):
2597 - Change how we allocate memory for large chunks on buffers, to
2598 avoid a (currently impossible) integer overflow, and to waste less
2599 space when allocating unusually large chunks. Fixes bug 20081;
2600 bugfix on 0.2.0.16-alpha. Issue identified by Guido Vranken.
2602 o Minor bugfixes (bootstrap):
2603 - Remember the directory server we fetched the consensus or previous
2604 certificates from, and use it to fetch future authority
2605 certificates. This change improves bootstrapping performance.
2606 Fixes bug 18963; bugfix on 0.2.8.1-alpha.
2608 o Minor bugfixes (circuits):
2609 - Make sure extend_info_from_router() is only called on servers.
2610 Fixes bug 19639; bugfix on 0.2.8.1-alpha.
2612 o Minor bugfixes (client, fascistfirewall):
2613 - Avoid spurious warnings when ReachableAddresses or FascistFirewall
2614 is set. Fixes bug 20306; bugfix on 0.2.8.2-alpha.
2616 o Minor bugfixes (client, unix domain sockets):
2617 - Disable IsolateClientAddr when using AF_UNIX backed SocksPorts as
2618 the client address is meaningless. Fixes bug 20261; bugfix
2621 o Minor bugfixes (code style):
2622 - Fix an integer signedness conversion issue in the case conversion
2623 tables. Fixes bug 19168; bugfix on 0.2.1.11-alpha.
2625 o Minor bugfixes (compilation):
2626 - Build correctly on versions of libevent2 without support for
2627 evutil_secure_rng_add_bytes(). Fixes bug 19904; bugfix
2629 - When building with Clang, use a full set of GCC warnings.
2630 (Previously, we included only a subset, because of the way we
2631 detected them.) Fixes bug 19216; bugfix on 0.2.0.1-alpha.
2632 - Detect Libevent2 functions correctly on systems that provide
2633 libevent2, but where libevent1 is linked with -levent. Fixes bug
2634 19904; bugfix on 0.2.2.24-alpha. Patch from Rubiate.
2635 - Run correctly when built on Windows build environments that
2636 require _vcsprintf(). Fixes bug 20560; bugfix on 0.2.2.11-alpha.
2638 o Minor bugfixes (configuration):
2639 - When parsing quoted configuration values from the torrc file,
2640 handle Windows line endings correctly. Fixes bug 19167; bugfix on
2641 0.2.0.16-alpha. Patch from "Pingl".
2643 o Minor bugfixes (directory authority):
2644 - Authorities now sort the "package" lines in their votes, for ease
2645 of debugging. (They are already sorted in consensus documents.)
2646 Fixes bug 18840; bugfix on 0.2.6.3-alpha.
2647 - Die with a more useful error when the operator forgets to place
2648 the authority_signing_key file into the keys directory. This
2649 avoids an uninformative assert & traceback about having an invalid
2650 key. Fixes bug 20065; bugfix on 0.2.0.1-alpha.
2651 - When allowing private addresses, mark Exits that only exit to
2652 private locations as such. Fixes bug 20064; bugfix
2654 - When parsing a detached signature, make sure we use the length of
2655 the digest algorithm instead of a hardcoded DIGEST256_LEN in
2656 order to avoid comparing bytes out-of-bounds with a smaller digest
2657 length such as SHA1. Fixes bug 19066; bugfix on 0.2.2.6-alpha.
2659 o Minor bugfixes (getpass):
2660 - Defensively fix a non-triggerable heap corruption at do_getpass()
2661 to protect ourselves from mistakes in the future. Fixes bug
2662 19223; bugfix on 0.2.7.3-rc. Bug found by Guido Vranken, patch
2665 o Minor bugfixes (guard selection):
2666 - Don't mark guards as unreachable if connection_connect() fails.
2667 That function fails for local reasons, so it shouldn't reveal
2668 anything about the status of the guard. Fixes bug 14334; bugfix
2670 - Use a single entry guard even if the NumEntryGuards consensus
2671 parameter is not provided. Fixes bug 17688; bugfix
2674 o Minor bugfixes (hidden services):
2675 - Increase the minimum number of internal circuits we preemptively
2676 build from 2 to 3, so a circuit is available when a client
2677 connects to another onion service. Fixes bug 13239; bugfix
2679 - Allow hidden services to run on IPv6 addresses even when the
2680 IPv6Exit option is not set. Fixes bug 18357; bugfix
2682 - Stop logging intro point details to the client log on certain
2683 error conditions. Fixed as part of bug 20012; bugfix on
2684 0.2.4.8-alpha. Patch by teor.
2685 - When deleting an ephemeral hidden service, close its intro points
2686 even if they are not completely open. Fixes bug 18604; bugfix
2688 - When configuring hidden services, check every hidden service
2689 directory's permissions. Previously, we only checked the last
2690 hidden service. Fixes bug 20529; bugfix on 0.2.6.2-alpha.
2692 o Minor bugfixes (IPv6, testing):
2693 - Check for IPv6 correctly on Linux when running test networks.
2694 Fixes bug 19905; bugfix on 0.2.7.3-rc; patch by teor.
2696 o Minor bugfixes (Linux seccomp2 sandbox):
2697 - Add permission to run the sched_yield() and sigaltstack() system
2698 calls, in order to support versions of Tor compiled with asan or
2699 ubsan code that use these calls. Now "sandbox 1" and
2700 "--enable-expensive-hardening" should be compatible on more
2701 systems. Fixes bug 20063; bugfix on 0.2.5.1-alpha.
2703 o Minor bugfixes (logging):
2704 - Downgrade a harmless log message about the
2705 pending_entry_connections list from "warn" to "info". Mitigates
2707 - Log a more accurate message when we fail to dump a microdescriptor.
2708 Fixes bug 17758; bugfix on 0.2.2.8-alpha. Patch from Daniel Pinto.
2709 - When logging a directory ownership mismatch, log the owning
2710 username correctly. Fixes bug 19578; bugfix on 0.2.2.29-beta.
2711 - When we are unable to remove the bw_accounting file, do not warn
2712 if the reason we couldn't remove it was that it didn't exist.
2713 Fixes bug 19964; bugfix on 0.2.5.4-alpha. Patch from pastly.
2715 o Minor bugfixes (memory leak):
2716 - Fix a series of slow memory leaks related to parsing torrc files
2717 and options. Fixes bug 19466; bugfix on 0.2.1.6-alpha.
2718 - Avoid a small memory leak when informing worker threads about
2719 rotated onion keys. Fixes bug 20401; bugfix on 0.2.6.3-alpha.
2720 - Fix a small memory leak when receiving AF_UNIX connections on a
2721 SocksPort. Fixes bug 20716; bugfix on 0.2.6.3-alpha.
2722 - When moving a signed descriptor object from a source to an
2723 existing destination, free the allocated memory inside that
2724 destination object. Fixes bug 20715; bugfix on 0.2.8.3-alpha.
2725 - Fix a memory leak and use-after-free error when removing entries
2726 from the sandbox's getaddrinfo() cache. Fixes bug 20710; bugfix on
2727 0.2.5.5-alpha. Patch from "cypherpunks".
2728 - Fix a small, uncommon memory leak that could occur when reading a
2729 truncated ed25519 key file. Fixes bug 18956; bugfix
2732 o Minor bugfixes (option parsing):
2733 - Count unix sockets when counting client listeners (SOCKS, Trans,
2734 NATD, and DNS). This has no user-visible behavior changes: these
2735 options are set once, and never read. Required for correct
2736 behavior in ticket 17178. Fixes bug 19677; bugfix on
2737 0.2.6.3-alpha. Patch by teor.
2739 o Minor bugfixes (options):
2740 - Check the consistency of UseEntryGuards and EntryNodes more
2741 reliably. Fixes bug 20074; bugfix on 0.2.4.12-alpha. Patch
2743 - Stop changing the configured value of UseEntryGuards on
2744 authorities and Tor2web clients. Fixes bug 20074; bugfix on
2745 commits 51fc6799 in 0.1.1.16-rc and acda1735 in 0.2.4.3-alpha.
2748 o Minor bugfixes (relay):
2749 - Ensure relays don't make multiple connections during bootstrap.
2750 Fixes bug 20591; bugfix on 0.2.8.1-alpha.
2751 - Do not try to parallelize workers more than 16x without the user
2752 explicitly configuring us to do so, even if we do detect more than
2753 16 CPU cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
2755 o Minor bugfixes (testing):
2756 - The test-stem and test-network makefile targets now depend only on
2757 the tor binary that they are testing. Previously, they depended on
2758 "make all". Fixes bug 18240; bugfix on 0.2.8.2-alpha. Based on a
2759 patch from "cypherpunks".
2760 - Allow clients to retry HSDirs much faster in test networks. Fixes
2761 bug 19702; bugfix on 0.2.7.1-alpha. Patch by teor.
2762 - Avoid a unit test failure on systems with over 16 detectable CPU
2763 cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
2764 - Let backtrace tests work correctly under AddressSanitizer:
2765 disable ASAN's detection of segmentation faults while running
2766 test_bt.sh, so that we can make sure that our own backtrace
2767 generation code works. Fixes bug 18934; bugfix
2768 on 0.2.5.2-alpha. Patch from "cypherpunks".
2769 - Fix the test-network-all target on out-of-tree builds by using the
2770 correct path to the test driver script. Fixes bug 19421; bugfix
2772 - Stop spurious failures in the local interface address discovery
2773 unit tests. Fixes bug 20634; bugfix on 0.2.8.1-alpha; patch by
2775 - Use ECDHE ciphers instead of ECDH in tortls tests. LibreSSL has
2776 removed the ECDH ciphers which caused the tests to fail on
2777 platforms which use it. Fixes bug 20460; bugfix on 0.2.8.1-alpha.
2778 - The tor_tls_server_info_callback unit test no longer crashes when
2779 debug-level logging is turned on. Fixes bug 20041; bugfix
2782 o Minor bugfixes (time):
2783 - Improve overflow checks in tv_udiff and tv_mdiff. Fixes bug 19483;
2784 bugfix on all released tor versions.
2785 - When computing the difference between two times in milliseconds,
2786 we now round to the nearest millisecond correctly. Previously, we
2787 could sometimes round in the wrong direction. Fixes bug 19428;
2788 bugfix on 0.2.2.2-alpha.
2790 o Minor bugfixes (Tor2web):
2791 - Prevent Tor2web clients from running hidden services: these services
2792 are not anonymous due to the one-hop client paths. Fixes bug
2793 19678. Patch by teor.
2795 o Minor bugfixes (user interface):
2796 - Display a more accurate number of suppressed messages in the log
2797 rate-limiter. Previously, there was a potential integer overflow
2798 in the counter. Now, if the number of messages hits a maximum, the
2799 rate-limiter doesn't count any further. Fixes bug 19435; bugfix
2801 - Fix a typo in the passphrase prompt for the ed25519 identity key.
2802 Fixes bug 19503; bugfix on 0.2.7.2-alpha.
2804 o Code simplification and refactoring:
2805 - Remove redundant declarations of the MIN macro. Closes
2807 - Rename tor_dup_addr() to tor_addr_to_str_dup() to avoid confusion.
2808 Closes ticket 18462; patch from "icanhasaccount".
2809 - Split the 600-line directory_handle_command_get function into
2810 separate functions for different URL types. Closes ticket 16698.
2813 - Add module-level internal documentation for 36 C files that
2814 previously didn't have a high-level overview. Closes ticket 20385.
2815 - Correct the IPv6 syntax in our documentation for the
2816 VirtualAddrNetworkIPv6 torrc option. Closes ticket 19743.
2817 - Correct the minimum bandwidth value in torrc.sample, and queue a
2818 corresponding change for torrc.minimal. Closes ticket 20085.
2819 - Fix spelling of "--enable-tor2web-mode" in the manpage. Closes
2820 ticket 19153. Patch from "U+039b".
2821 - Module-level documentation for several more modules. Closes
2822 tickets 19287 and 19290.
2823 - Document the --passphrase-fd option in the tor manpage. Fixes bug
2824 19504; bugfix on 0.2.7.3-rc.
2825 - Document the default PathsNeededToBuildCircuits value that's used
2826 by clients when the directory authorities don't set
2827 min_paths_for_circs_pct. Fixes bug 20117; bugfix on 0.2.4.10-alpha.
2828 Patch by teor, reported by Jesse V.
2829 - Fix manual for the User option: it takes a username, not a UID.
2830 Fixes bug 19122; bugfix on 0.0.2pre16 (the first version to have
2832 - Fix the description of the --passphrase-fd option in the
2833 tor-gencert manpage. The option is used to pass the number of a
2834 file descriptor to read the passphrase from, not to read the file
2835 descriptor from. Fixes bug 19505; bugfix on 0.2.0.20-alpha.
2838 - We no longer include the (dead, deprecated) bufferevent code in
2839 Tor. Closes ticket 19450. Based on a patch from "U+039b".
2842 - Remove support for "GET /tor/bytes.txt" DirPort request, and
2843 "GETINFO dir-usage" controller request, which were only available
2844 via a compile-time option in Tor anyway. Feature was added in
2845 0.2.2.1-alpha. Resolves ticket 19035.
2846 - There is no longer a compile-time option to disable support for
2847 TransPort. (If you don't want TransPort, just don't use it.) Patch
2848 from "U+039b". Closes ticket 19449.
2851 - Run more workqueue tests as part of "make check". These had
2852 previously been implemented, but you needed to know special
2853 command-line options to enable them.
2854 - We now have unit tests for our code to reject zlib "compression
2855 bombs". (Fortunately, the code works fine.)
2858 Changes in version 0.2.8.11 - 2016-12-08
2859 Tor 0.2.8.11 backports fixes for additional portability issues that
2860 could prevent Tor from building correctly on OSX Sierra, or with
2861 OpenSSL 1.1. Affected users should upgrade; others can safely stay
2864 o Minor bugfixes (portability):
2865 - Avoid compilation errors when building on OSX Sierra. Sierra began
2866 to support the getentropy() and clock_gettime() APIs, but created
2867 a few problems in doing so. Tor 0.2.9 has a more thorough set of
2868 workarounds; in 0.2.8, we are just using the /dev/urandom and mach
2869 monotonic time interfaces. Fixes bug 20865. Bugfix
2872 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
2873 - Fix compilation with OpenSSL 1.1 and less commonly-used CPU
2874 architectures. Closes ticket 20588.
2877 Changes in version 0.2.8.10 - 2016-12-02
2878 Tor 0.2.8.10 backports a fix for a bug that would sometimes make clients
2879 unusable after they left standby mode. It also backports fixes for
2880 a few portability issues and a small but problematic memory leak.
2882 o Major bugfixes (client reliability, backport from 0.2.9.5-alpha):
2883 - When Tor leaves standby because of a new application request, open
2884 circuits as needed to serve that request. Previously, we would
2885 potentially wait a very long time. Fixes part of bug 19969; bugfix
2888 o Major bugfixes (client performance, backport from 0.2.9.5-alpha):
2889 - Clients now respond to new application stream requests immediately
2890 when they arrive, rather than waiting up to one second before
2891 starting to handle them. Fixes part of bug 19969; bugfix
2894 o Minor bugfixes (portability, backport from 0.2.9.6-rc):
2895 - Work around a bug in the OSX 10.12 SDK that would prevent us from
2896 successfully targeting earlier versions of OSX. Resolves
2899 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
2900 - Fix implicit conversion warnings under OpenSSL 1.1. Fixes bug
2901 20551; bugfix on 0.2.1.1-alpha.
2903 o Minor bugfixes (relay, backport from 0.2.9.5-alpha):
2904 - Work around a memory leak in OpenSSL 1.1 when encoding public
2905 keys. Fixes bug 20553; bugfix on 0.0.2pre8.
2907 o Minor features (geoip):
2908 - Update geoip and geoip6 to the November 3 2016 Maxmind GeoLite2
2912 Changes in version 0.2.8.9 - 2016-10-17
2913 Tor 0.2.8.9 backports a fix for a security hole in previous versions
2914 of Tor that would allow a remote attacker to crash a Tor client,
2915 hidden service, relay, or authority. All Tor users should upgrade to
2916 this version, or to 0.2.9.4-alpha. Patches will be released for older
2919 o Major features (security fixes, also in 0.2.9.4-alpha):
2920 - Prevent a class of security bugs caused by treating the contents
2921 of a buffer chunk as if they were a NUL-terminated string. At
2922 least one such bug seems to be present in all currently used
2923 versions of Tor, and would allow an attacker to remotely crash
2924 most Tor instances, especially those compiled with extra compiler
2925 hardening. With this defense in place, such bugs can't crash Tor,
2926 though we should still fix them as they occur. Closes ticket
2927 20384 (TROVE-2016-10-001).
2929 o Minor features (geoip):
2930 - Update geoip and geoip6 to the October 4 2016 Maxmind GeoLite2
2934 Changes in version 0.2.8.8 - 2016-09-23
2935 Tor 0.2.8.8 fixes two crash bugs present in previous versions of the
2936 0.2.8.x series. Relays running 0.2.8.x should upgrade, as should users
2937 who select public relays as their bridges.
2939 o Major bugfixes (crash):
2940 - Fix a complicated crash bug that could affect Tor clients
2941 configured to use bridges when replacing a networkstatus consensus
2942 in which one of their bridges was mentioned. OpenBSD users saw
2943 more crashes here, but all platforms were potentially affected.
2944 Fixes bug 20103; bugfix on 0.2.8.2-alpha.
2946 o Major bugfixes (relay, OOM handler):
2947 - Fix a timing-dependent assertion failure that could occur when we
2948 tried to flush from a circuit after having freed its cells because
2949 of an out-of-memory condition. Fixes bug 20203; bugfix on
2950 0.2.8.1-alpha. Thanks to "cypherpunks" for help diagnosing
2953 o Minor feature (fallback directories):
2954 - Remove broken fallbacks from the hard-coded fallback directory
2955 list. Closes ticket 20190; patch by teor.
2957 o Minor features (geoip):
2958 - Update geoip and geoip6 to the September 6 2016 Maxmind GeoLite2
2962 Changes in version 0.2.8.7 - 2016-08-24
2963 Tor 0.2.8.7 fixes an important bug related to the ReachableAddresses
2964 option in 0.2.8.6, and replaces a retiring bridge authority. Everyone
2965 who sets the ReachableAddresses option, and all bridges, are strongly
2966 encouraged to upgrade.
2968 o Directory authority changes:
2969 - The "Tonga" bridge authority has been retired; the new bridge
2970 authority is "Bifroest". Closes tickets 19728 and 19690.
2972 o Major bugfixes (client, security):
2973 - Only use the ReachableAddresses option to restrict the first hop
2974 in a path. In earlier versions of 0.2.8.x, it would apply to
2975 every hop in the path, with a possible degradation in anonymity
2976 for anyone using an uncommon ReachableAddress setting. Fixes bug
2977 19973; bugfix on 0.2.8.2-alpha.
2979 o Minor features (geoip):
2980 - Update geoip and geoip6 to the August 2 2016 Maxmind GeoLite2
2983 o Minor bugfixes (compilation):
2984 - Remove an inappropriate "inline" in tortls.c that was causing
2985 warnings on older versions of GCC. Fixes bug 19903; bugfix
2988 o Minor bugfixes (fallback directories):
2989 - Avoid logging a NULL string pointer when loading fallback
2990 directory information. Fixes bug 19947; bugfix on 0.2.4.7-alpha
2991 and 0.2.8.1-alpha. Report and patch by "rubiate".
2994 Changes in version 0.2.8.6 - 2016-08-02
2996 Tor 0.2.8.6 is the first stable version of the Tor 0.2.8 series.
2998 The Tor 0.2.8 series improves client bootstrapping performance,
2999 completes the authority-side implementation of improved identity
3000 keys for relays, and includes numerous bugfixes and performance
3001 improvements throughout the program. This release continues to
3002 improve the coverage of Tor's test suite. For a full list of
3003 changes since Tor 0.2.7, see the ReleaseNotes file.
3005 Below is a list of the changes since Tor 0.2.7.
3007 o New system requirements:
3008 - Tor no longer attempts to support platforms where the "time_t"
3009 type is unsigned. (To the best of our knowledge, only OpenVMS does
3010 this, and Tor has never actually built on OpenVMS.) Closes
3012 - Tor no longer supports versions of OpenSSL with a broken
3013 implementation of counter mode. (This bug was present in OpenSSL
3014 1.0.0, and was fixed in OpenSSL 1.0.0a.) Tor still detects, but no
3015 longer runs with, these versions.
3016 - Tor now uses Autoconf version 2.63 or later, and Automake 1.11 or
3017 later (released in 2008 and 2009 respectively). If you are
3018 building Tor from the git repository instead of from the source
3019 distribution, and your tools are older than this, you will need to
3020 upgrade. Closes ticket 17732.
3022 o Directory authority changes:
3023 - Update the V3 identity key for the dannenberg directory authority:
3024 it was changed on 18 November 2015. Closes task 17906. Patch
3026 - Urras is no longer a directory authority. Closes ticket 19271.
3028 o Major features (directory system):
3029 - Include a trial list of default fallback directories, based on an
3030 opt-in survey of suitable relays. Doing this should make clients
3031 bootstrap more quickly and reliably, and reduce the load on the
3032 directory authorities. Closes ticket 15775. Patch by teor.
3033 Candidates identified using an OnionOO script by weasel, teor,
3034 gsathya, and karsten.
3035 - Previously only relays that explicitly opened a directory port
3036 (DirPort) accepted directory requests from clients. Now all
3037 relays, with and without a DirPort, accept and serve tunneled
3038 directory requests that they receive through their ORPort. You can
3039 disable this behavior using the new DirCache option. Closes
3041 - When bootstrapping multiple consensus downloads at a time, use the
3042 first one that starts downloading, and close the rest. This
3043 reduces failures when authorities or fallback directories are slow
3044 or down. Together with the code for feature 15775, this feature
3045 should reduces failures due to fallback churn. Implements ticket
3046 4483. Patch by teor. Implements IPv4 portions of proposal 210 by
3049 o Major features (security, Linux):
3050 - When Tor starts as root on Linux and is told to switch user ID, it
3051 can now retain the capability to bind to low ports. By default,
3052 Tor will do this only when it's switching user ID and some low
3053 ports have been configured. You can change this behavior with the
3054 new option KeepBindCapabilities. Closes ticket 8195.
3056 o Major bugfixes (client, bootstrapping):
3057 - Check if bootstrap consensus downloads are still needed when the
3058 linked connection attaches. This prevents tor making unnecessary
3059 begindir-style connections, which are the only directory
3060 connections tor clients make since the fix for 18483 was merged.
3061 - Fix some edge cases where consensus download connections may not
3062 have been closed, even though they were not needed. Related to fix
3064 - Make relays retry consensus downloads the correct number of times,
3065 rather than the more aggressive client retry count. Fixes part of
3068 o Major bugfixes (dns proxy mode, crash):
3069 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
3070 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
3072 o Major bugfixes (ed25519, voting):
3073 - Actually enable support for authorities to match routers by their
3074 Ed25519 identities. Previously, the code had been written, but
3075 some debugging code that had accidentally been left in the
3076 codebase made it stay turned off. Fixes bug 17702; bugfix
3078 - When collating votes by Ed25519 identities, authorities now
3079 include a "NoEdConsensus" flag if the ed25519 value (or lack
3080 thereof) for a server does not reflect the majority consensus.
3081 Related to bug 17668; bugfix on 0.2.7.2-alpha.
3082 - When generating a vote with keypinning disabled, never include two
3083 entries for the same ed25519 identity. This bug was causing
3084 authorities to generate votes that they could not parse when a
3085 router violated key pinning by changing its RSA identity but
3086 keeping its Ed25519 identity. Fixes bug 17668; fixes part of bug
3087 18318. Bugfix on 0.2.7.2-alpha.
3089 o Major bugfixes (key management):
3090 - If OpenSSL fails to generate an RSA key, do not retain a dangling
3091 pointer to the previous (uninitialized) key value. The impact here
3092 should be limited to a difficult-to-trigger crash, if OpenSSL is
3093 running an engine that makes key generation failures possible, or
3094 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
3095 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
3098 o Major bugfixes (security, client, DNS proxy):
3099 - Stop a crash that could occur when a client running with DNSPort
3100 received a query with multiple address types, and the first
3101 address type was not supported. Found and fixed by Scott Dial.
3102 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
3104 o Major bugfixes (security, compilation):
3105 - Correctly detect compiler flags on systems where _FORTIFY_SOURCE
3106 is predefined. Previously, our use of -D_FORTIFY_SOURCE would
3107 cause a compiler warning, thereby making other checks fail, and
3108 needlessly disabling compiler-hardening support. Fixes one case of
3109 bug 18841; bugfix on 0.2.3.17-beta. Patch from "trudokal".
3110 - Repair hardened builds under the clang compiler. Previously, our
3111 use of _FORTIFY_SOURCE would conflict with clang's address
3112 sanitizer. Fixes bug 14821; bugfix on 0.2.5.4-alpha.
3114 o Major bugfixes (security, pointers):
3115 - Avoid a difficult-to-trigger heap corruption attack when extending
3116 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
3117 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
3118 Reported by Guido Vranken.
3120 o Major bugfixes (testing):
3121 - Fix a bug that would block 'make test-network-all' on systems where
3122 IPv6 packets were lost. Fixes bug 19008; bugfix on 0.2.7.3-rc.
3124 o Major bugfixes (user interface):
3125 - Correctly give a warning in the cases where a relay is specified
3126 by nickname, and one such relay is found, but it is not officially
3127 Named. Fixes bug 19203; bugfix on 0.2.3.1-alpha.
3129 o Minor features (accounting):
3130 - Added two modes to the AccountingRule option: One for limiting
3131 only the number of bytes sent ("AccountingRule out"), and one for
3132 limiting only the number of bytes received ("AccountingRule in").
3133 Closes ticket 15989; patch from "unixninja92".
3135 o Minor features (bug-resistance):
3136 - Make Tor survive errors involving connections without a
3137 corresponding event object. Previously we'd fail with an
3138 assertion; now we produce a log message. Related to bug 16248.
3139 - Use tor_snprintf() and tor_vsnprintf() even in external and low-
3140 level code, to harden against accidental failures to NUL-
3141 terminate. Part of ticket 17852. Patch from jsturgix. Found
3144 o Minor features (build):
3145 - Detect systems with FreeBSD-derived kernels (such as GNU/kFreeBSD)
3146 as having possible IPFW support. Closes ticket 18448. Patch from
3148 - Since our build process now uses "make distcheck", we no longer
3149 force "make dist" to depend on "make check". Closes ticket 17893;
3150 patch from "cypherpunks".
3151 - Tor now builds once again with the recent OpenSSL 1.1 development
3152 branch (tested against 1.1.0-pre5 and 1.1.0-pre6-dev). We have been
3153 tracking OpenSSL 1.1 development as it has progressed, and fixing
3154 numerous compatibility issues as they arose. See tickets
3155 17549, 17921, 17984, 19499, and 18286.
3156 - When building manual pages, set the timezone to "UTC", so that the
3157 output is reproducible. Fixes bug 19558; bugfix on 0.2.2.9-alpha.
3158 Patch from intrigeri.
3160 o Minor features (clients):
3161 - Make clients, onion services, and bridge relays always use an
3162 encrypted begindir connection for directory requests. Resolves
3163 ticket 18483. Patch by teor.
3165 o Minor features (controller):
3166 - Add 'GETINFO exit-policy/reject-private/[default,relay]', so
3167 controllers can examine the the reject rules added by
3168 ExitPolicyRejectPrivate. This makes it easier for stem to display
3170 - Adds the FallbackDir entries to 'GETINFO config/defaults'. Closes
3171 tickets 16774 and 17817. Patch by George Tankersley.
3172 - New 'GETINFO hs/service/desc/id/' command to retrieve a hidden
3173 service descriptor from a service's local hidden service
3174 descriptor cache. Closes ticket 14846.
3176 o Minor features (crypto):
3177 - Add SHA3 and SHAKE support to crypto.c. Closes ticket 17783.
3178 - Add SHA512 support to crypto.c. Closes ticket 17663; patch from
3180 - Improve performance when hashing non-multiple of 8 sized buffers,
3181 based on Andrew Moon's public domain SipHash-2-4 implementation.
3182 Fixes bug 17544; bugfix on 0.2.5.3-alpha.
3183 - Validate the hard-coded Diffie-Hellman parameters and ensure that
3184 p is a safe prime, and g is a suitable generator. Closes
3186 - When allocating a digest state object, allocate no more space than
3187 we actually need. Previously, we would allocate as much space as
3188 the state for the largest algorithm would need. This change saves
3189 up to 672 bytes per circuit. Closes ticket 17796.
3191 o Minor features (directory downloads):
3192 - Add UseDefaultFallbackDirs, which enables any hard-coded fallback
3193 directory mirrors. The default is 1; set it to 0 to disable
3194 fallbacks. Implements ticket 17576. Patch by teor.
3195 - Wait for busy authorities and fallback directories to become non-
3196 busy when bootstrapping. (A similar change was made in 6c443e987d
3197 for directory caches chosen from the consensus.) Closes ticket
3198 17864; patch by teor.
3200 o Minor features (geoip):
3201 - Update geoip and geoip6 to the July 6 2016 Maxmind GeoLite2
3204 o Minor features (hidden service directory):
3205 - Streamline relay-side hsdir handling: when relays consider whether
3206 to accept an uploaded hidden service descriptor, they no longer
3207 check whether they are one of the relays in the network that is
3208 "supposed" to handle that descriptor. Implements ticket 18332.
3210 o Minor features (IPv6):
3211 - Add ClientPreferIPv6DirPort, which is set to 0 by default. If set
3212 to 1, tor prefers IPv6 directory addresses.
3213 - Add ClientUseIPv4, which is set to 1 by default. If set to 0, tor
3214 avoids using IPv4 for client OR and directory connections.
3215 - Add address policy assume_action support for IPv6 addresses.
3216 - Add an argument 'ipv6=address:orport' to the DirAuthority and
3217 FallbackDir torrc options, to specify an IPv6 address for an
3218 authority or fallback directory. Add hard-coded ipv6 addresses for
3219 directory authorities that have them. Closes ticket 17327; patch
3220 from Nick Mathewson and teor.
3221 - Allow users to configure directory authorities and fallback
3222 directory servers with IPv6 addresses and ORPorts. Resolves
3224 - Limit IPv6 mask bits to 128.
3225 - Make tor_ersatz_socketpair work on IPv6-only systems. Fixes bug
3226 17638; bugfix on 0.0.2pre8. Patch by teor.
3227 - Try harder to obey the IP version restrictions "ClientUseIPv4 0",
3228 "ClientUseIPv6 0", "ClientPreferIPv6ORPort", and
3229 "ClientPreferIPv6DirPort". Closes ticket 17840; patch by teor.
3230 - Warn when comparing against an AF_UNSPEC address in a policy, it's
3231 almost always a bug. Closes ticket 17863; patch by teor.
3232 - routerset_parse now accepts IPv6 literal addresses. Fixes bug
3233 17060; bugfix on 0.2.1.3-alpha. Patch by teor.
3235 o Minor features (Linux seccomp2 sandbox):
3236 - Reject attempts to change our Address with "Sandbox 1" enabled.
3237 Changing Address with Sandbox turned on would never actually work,
3238 but previously it would fail in strange and confusing ways. Found
3241 o Minor features (logging):
3242 - When logging to syslog, allow a tag to be added to the syslog
3243 identity (the string prepended to every log message). The tag can
3244 be configured with SyslogIdentityTag and defaults to none. Setting
3245 it to "foo" will cause logs to be tagged as "Tor-foo". Closes
3248 o Minor features (portability):
3249 - Use timingsafe_memcmp() where available. Closes ticket 17944;
3250 patch from <logan@hackers.mu>.
3252 o Minor features (relay, address discovery):
3253 - Add a family argument to get_interface_addresses_raw() and
3254 subfunctions to make network interface address interogation more
3255 efficient. Now Tor can specifically ask for IPv4, IPv6 or both
3256 types of interfaces from the operating system. Resolves
3258 - When get_interface_address6_list(.,AF_UNSPEC,.) is called and
3259 fails to enumerate interface addresses using the platform-specific
3260 API, have it rely on the UDP socket fallback technique to try and
3261 find out what IP addresses (both IPv4 and IPv6) our machine has.
3262 Resolves ticket 17951.
3264 o Minor features (replay cache):
3265 - The replay cache now uses SHA256 instead of SHA1. Implements
3266 feature 8961. Patch by teor, issue reported by rransom.
3268 o Minor features (robustness):
3269 - Exit immediately with an error message if the code attempts to use
3270 Libevent without having initialized it. This should resolve some
3271 frequently-made mistakes in our unit tests. Closes ticket 18241.
3273 o Minor features (security, clock):
3274 - Warn when the system clock appears to move back in time (when the
3275 state file was last written in the future). Tor doesn't know that
3276 consensuses have expired if the clock is in the past. Patch by
3277 teor. Implements ticket 17188.
3279 o Minor features (security, exit policies):
3280 - ExitPolicyRejectPrivate now rejects more private addresses by
3281 default. Specifically, it now rejects the relay's outbound bind
3282 addresses (if configured), and the relay's configured port
3283 addresses (such as ORPort and DirPort). Fixes bug 17027; bugfix on
3284 0.2.0.11-alpha. Patch by teor.
3286 o Minor features (security, memory erasure):
3287 - Make memwipe() do nothing when passed a NULL pointer or buffer of
3288 zero size. Check size argument to memwipe() for underflow. Fixes
3289 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
3291 - Set the unused entries in a smartlist to NULL. This helped catch
3292 a (harmless) bug, and shouldn't affect performance too much.
3293 Implements ticket 17026.
3294 - Use SecureMemoryWipe() function to securely clean memory on
3295 Windows. Previously we'd use OpenSSL's OPENSSL_cleanse() function.
3296 Implements feature 17986.
3297 - Use explicit_bzero or memset_s when present. Previously, we'd use
3298 OpenSSL's OPENSSL_cleanse() function. Closes ticket 7419; patches
3299 from <logan@hackers.mu> and <selven@hackers.mu>.
3301 o Minor features (security, RNG):
3302 - Adjust Tor's use of OpenSSL's RNG APIs so that they absolutely,
3303 positively are not allowed to fail. Previously we depended on
3304 internal details of OpenSSL's behavior. Closes ticket 17686.
3305 - Never use the system entropy output directly for anything besides
3306 seeding the PRNG. When we want to generate important keys, instead
3307 of using system entropy directly, we now hash it with the PRNG
3308 stream. This may help resist certain attacks based on broken OS
3309 entropy implementations. Closes part of ticket 17694.
3310 - Use modern system calls (like getentropy() or getrandom()) to
3311 generate strong entropy on platforms that have them. Closes
3314 o Minor features (security, win32):
3315 - Set SO_EXCLUSIVEADDRUSE on Win32 to avoid a local port-stealing
3316 attack. Fixes bug 18123; bugfix on all tor versions. Patch
3319 o Minor features (unix domain sockets):
3320 - Add a new per-socket option, RelaxDirModeCheck, to allow creating
3321 Unix domain sockets without checking the permissions on the parent
3322 directory. (Tor checks permissions by default because some
3323 operating systems only check permissions on the parent directory.
3324 However, some operating systems do look at permissions on the
3325 socket, and tor's default check is unneeded.) Closes ticket 18458.
3328 o Minor features (unix file permissions):
3329 - Defer creation of Unix sockets until after setuid. This avoids
3330 needing CAP_CHOWN and CAP_FOWNER when using systemd's
3331 CapabilityBoundingSet, or chown and fowner when using SELinux.
3332 Implements part of ticket 17562. Patch from Jamie Nguyen.
3333 - If any directory created by Tor is marked as group readable, the
3334 filesystem group is allowed to be either the default GID or the
3335 root user. Allowing root to read the DataDirectory prevents the
3336 need for CAP_READ_SEARCH when using systemd's
3337 CapabilityBoundingSet, or dac_read_search when using SELinux.
3338 Implements part of ticket 17562. Patch from Jamie Nguyen.
3339 - Introduce a new DataDirectoryGroupReadable option. If it is set to
3340 1, the DataDirectory will be made readable by the default GID.
3341 Implements part of ticket 17562. Patch from Jamie Nguyen.
3343 o Minor bugfixes (accounting):
3344 - The max bandwidth when using 'AccountRule sum' is now correctly
3345 logged. Fixes bug 18024; bugfix on 0.2.6.1-alpha. Patch
3348 o Minor bugfixes (assert, portability):
3349 - Fix an assertion failure in memarea.c on systems where "long" is
3350 shorter than the size of a pointer. Fixes bug 18716; bugfix
3353 o Minor bugfixes (bootstrap):
3354 - Consistently use the consensus download schedule for authority
3355 certificates. Fixes bug 18816; bugfix on 0.2.4.13-alpha.
3357 o Minor bugfixes (build):
3358 - Avoid spurious failures from configure files related to calling
3359 exit(0) in TOR_SEARCH_LIBRARY. Fixes bug 18626; bugfix on
3360 0.2.0.1-alpha. Patch from "cypherpunks".
3361 - Do not link the unit tests against both the testing and non-
3362 testing versions of the static libraries. Fixes bug 18490; bugfix
3364 - Resolve warnings when building on systems that are concerned with
3365 signed char. Fixes bug 18728; bugfix on 0.2.7.2-alpha
3367 - Silence spurious clang-scan warnings in the ed25519_donna code by
3368 explicitly initializing some objects. Fixes bug 18384; bugfix on
3369 0.2.7.2-alpha. Patch by teor.
3370 - When libscrypt.h is found, but no libscrypt library can be linked,
3371 treat libscrypt as absent. Fixes bug 19161; bugfix
3373 - Cause the unit tests to compile correctly on mingw64 versions that
3374 lack sscanf. Fixes bug 19213; bugfix on 0.2.7.1-alpha.
3375 - Don't try to use the pthread_condattr_setclock() function unless
3376 it actually exists. Fixes compilation on NetBSD-6.x. Fixes bug
3377 17819; bugfix on 0.2.6.3-alpha.
3378 - Fix backtrace compilation on FreeBSD. Fixes bug 17827; bugfix
3380 - Fix search for libevent libraries on OpenBSD (and other systems
3381 that install libevent 1 and libevent 2 in parallel). Fixes bug
3382 16651; bugfix on 0.1.0.7-rc. Patch from "rubiate".
3383 - Isolate environment variables meant for tests from the rest of the
3384 build system. Fixes bug 17818; bugfix on 0.2.7.3-rc.
3385 - Mark all object files that include micro-revision.i as depending
3386 on it, so as to make parallel builds more reliable. Fixes bug
3387 17826; bugfix on 0.2.5.1-alpha.
3388 - Remove config.log only from make distclean, not from make clean.
3389 Fixes bug 17924; bugfix on 0.2.4.1-alpha.
3390 - Replace usage of 'INLINE' with 'inline'. Fixes bug 17804; bugfix
3392 - Remove an #endif from configure.ac so that we correctly detect the
3393 presence of in6_addr.s6_addr32. Fixes bug 17923; bugfix
3396 o Minor bugfixes (client, bootstrap):
3397 - Count receipt of new microdescriptors as progress towards
3398 bootstrapping. Previously, with EntryNodes set, Tor might not
3399 successfully repopulate the guard set on bootstrapping. Fixes bug
3400 16825; bugfix on 0.2.3.1-alpha.
3402 o Minor bugfixes (code correctness):
3403 - Fix a bad memory handling bug that would occur if we had queued a
3404 cell on a channel's incoming queue. Fortunately, we can't actually
3405 queue a cell like that as our code is constructed today, but it's
3406 best to avoid this kind of error, even if there isn't any code
3407 that triggers it today. Fixes bug 18570; bugfix on 0.2.4.4-alpha.
3408 - Assert that allocated memory held by the reputation code is freed
3409 according to its internal counters. Fixes bug 17753; bugfix
3411 - Assert when the TLS contexts fail to initialize. Fixes bug 17683;
3413 - Update to the latest version of Trunnel, which tries harder to
3414 avoid generating code that can invoke memcpy(p,NULL,0). Bug found
3415 by clang address sanitizer. Fixes bug 18373; bugfix
3417 - When closing an entry connection, generate a warning if we should
3418 have sent an end cell for it but we haven't. Fixes bug 17876;
3419 bugfix on 0.2.3.2-alpha.
3421 o Minor bugfixes (configuration):
3422 - Fix a tiny memory leak when parsing a port configuration ending in
3423 ":auto". Fixes bug 18374; bugfix on 0.2.3.3-alpha.
3425 o Minor bugfixes (containers):
3426 - If we somehow attempt to construct a heap with more than
3427 1073741822 elements, avoid an integer overflow when maintaining
3428 the heap property. Fixes bug 18296; bugfix on 0.1.2.1-alpha.
3430 o Minor bugfixes (controller, microdescriptors):
3431 - Make GETINFO dir/status-vote/current/consensus conform to the
3432 control specification by returning "551 Could not open cached
3433 consensus..." when not caching consensuses. Fixes bug 18920;
3434 bugfix on 0.2.2.6-alpha.
3436 o Minor bugfixes (crypto):
3437 - Check the return value of HMAC() and assert on failure. Fixes bug
3438 17658; bugfix on 0.2.3.6-alpha. Patch by teor.
3440 o Minor bugfixes (directories):
3441 - When fetching extrainfo documents, compare their SHA256 digests
3442 and Ed25519 signing key certificates with the routerinfo that led
3443 us to fetch them, rather than with the most recent routerinfo.
3444 Otherwise we generate many spurious warnings about mismatches.
3445 Fixes bug 17150; bugfix on 0.2.7.2-alpha.
3446 - When generating a URL for a directory server on an IPv6 address,
3447 wrap the IPv6 address in square brackets. Fixes bug 18051; bugfix
3448 on 0.2.3.9-alpha. Patch from Malek.
3450 o Minor bugfixes (downloading):
3451 - Predict more correctly whether we'll be downloading over HTTP when
3452 we determine the maximum length of a URL. This should avoid a
3453 "BUG" warning about the Squid HTTP proxy and its URL limits. Fixes
3456 o Minor bugfixes (exit policies, security):
3457 - Refresh an exit relay's exit policy when interface addresses
3458 change. Previously, tor only refreshed the exit policy when the
3459 configured external address changed. Fixes bug 18208; bugfix on
3460 0.2.7.3-rc. Patch by teor.
3462 o Minor bugfixes (fallback directories):
3463 - Mark fallbacks as "too busy" when they return a 503 response,
3464 rather than just marking authorities. Fixes bug 17572; bugfix on
3465 0.2.4.7-alpha. Patch by teor.
3466 - When requesting extrainfo descriptors from a trusted directory
3467 server, check whether it is an authority or a fallback directory
3468 which supports extrainfo descriptors. Fixes bug 18489; bugfix on
3469 0.2.4.7-alpha. Reported by atagar, patch by teor.
3471 o Minor bugfixes (hidden service, client):
3472 - Handle the case where the user makes several fast consecutive
3473 requests to the same .onion address. Previously, the first six
3474 requests would each trigger a descriptor fetch, each picking a
3475 directory (there are 6 overall) and the seventh one would fail
3476 because no directories were left, thereby triggering a close on
3477 all current directory connections asking for the hidden service.
3478 The solution here is to not close the connections if we have
3479 pending directory fetches. Fixes bug 15937; bugfix
3482 o Minor bugfixes (hidden service, control port):
3483 - Add the onion address to the HS_DESC event for the UPLOADED action
3484 both on success or failure. It was previously hardcoded with
3485 UNKNOWN. Fixes bug 16023; bugfix on 0.2.7.2-alpha.
3487 o Minor bugfixes (hidden service, directory):
3488 - Bridges now refuse "rendezvous2" (hidden service descriptor)
3489 publish attempts. Suggested by ticket 18332.
3491 o Minor bugfixes (IPv6):
3492 - Update the limits in max_dl_per_request for IPv6 address length.
3493 Fixes bug 17573; bugfix on 0.2.1.5-alpha.
3495 o Minor bugfixes (Linux seccomp2 sandbox):
3496 - Allow more syscalls when running with "Sandbox 1" enabled:
3497 sysinfo, getsockopt(SO_SNDBUF), and setsockopt(SO_SNDBUFFORCE). On
3498 some systems, these are required for Tor to start. Fixes bug
3499 18397; bugfix on 0.2.5.1-alpha. Patch from Daniel Pinto.
3500 - Allow IPPROTO_UDP datagram sockets when running with "Sandbox 1",
3501 so that get_interface_address6_via_udp_socket_hack() can work.
3502 Fixes bug 19660; bugfix on 0.2.5.1-alpha.
3503 - Allow the setrlimit syscall, and the prlimit and prlimit64
3504 syscalls, which some libc implementations use under the hood.
3505 Fixes bug 15221; bugfix on 0.2.5.1-alpha.
3506 - Avoid a 10-second delay when starting as a client with "Sandbox 1"
3507 enabled and no DNS resolvers configured. This should help TAILS
3508 start up faster. Fixes bug 18548; bugfix on 0.2.5.1-alpha.
3509 - Fix a crash when using offline master ed25519 keys with the Linux
3510 seccomp2 sandbox enabled. Fixes bug 17675; bugfix on 0.2.7.3-rc.
3511 - Allow statistics to be written to disk when "Sandbox 1" is
3512 enabled. Fixes bugs 19556 and 19957; bugfix on 0.2.5.1-alpha and
3513 0.2.6.1-alpha respectively.
3515 o Minor bugfixes (logging):
3516 - In log messages that include a function name, use __FUNCTION__
3517 instead of __PRETTY_FUNCTION__. In GCC, these are synonymous, but
3518 with clang __PRETTY_FUNCTION__ has extra information we don't
3519 need. Fixes bug 16563; bugfix on 0.0.2pre8. Fix by Tom van
3521 - Remove needless quotes from a log message about unparseable
3522 addresses. Fixes bug 17843; bugfix on 0.2.3.3-alpha.
3523 - Scrub service name in "unrecognized service ID" log messages.
3524 Fixes bug 18600; bugfix on 0.2.4.11-alpha.
3525 - When logging information about an unparsable networkstatus vote or
3526 consensus, do not say "vote" when we mean consensus. Fixes bug
3527 18368; bugfix on 0.2.0.8-alpha.
3528 - When we can't generate a signing key because OfflineMasterKey is
3529 set, do not imply that we should have been able to load it. Fixes
3530 bug 18133; bugfix on 0.2.7.2-alpha.
3531 - When logging a malformed hostname received through socks4, scrub
3532 it if SafeLogging says we should. Fixes bug 17419; bugfix
3535 o Minor bugfixes (memory safety):
3536 - Avoid freeing an uninitialized pointer when opening a socket fails
3537 in get_interface_addresses_ioctl(). Fixes bug 18454; bugfix on
3538 0.2.3.11-alpha. Reported by toralf and "cypherpunks", patch
3540 - Fix a memory leak in "tor --list-fingerprint". Fixes part of bug
3541 18672; bugfix on 0.2.5.1-alpha.
3542 - Fix a memory leak in tor-gencert. Fixes part of bug 18672; bugfix
3545 o Minor bugfixes (pluggable transports):
3546 - Avoid reporting a spurious error when we decide that we don't need
3547 to terminate a pluggable transport because it has already exited.
3548 Fixes bug 18686; bugfix on 0.2.5.5-alpha.
3550 o Minor bugfixes (pointer arithmetic):
3551 - Fix a bug in memarea_alloc() that could have resulted in remote
3552 heap write access, if Tor had ever passed an unchecked size to
3553 memarea_alloc(). Fortunately, all the sizes we pass to
3554 memarea_alloc() are pre-checked to be less than 128 kilobytes.
3555 Fixes bug 19150; bugfix on 0.2.1.1-alpha. Bug found by
3558 o Minor bugfixes (private directory):
3559 - Prevent a race condition when creating private directories. Fixes
3560 part of bug 17852; bugfix on 0.0.2pre13. Part of ticket 17852.
3561 Patch from jsturgix. Found with Flawfinder.
3563 o Minor bugfixes (relays):
3564 - Check that both the ORPort and DirPort (if present) are reachable
3565 before publishing a relay descriptor. Otherwise, relays publish a
3566 descriptor with DirPort 0 when the DirPort reachability test takes
3567 longer than the ORPort reachability test. Fixes bug 18050; bugfix
3568 on 0.1.0.1-rc. Reported by "starlight", patch by teor.
3569 - Resolve some edge cases where we might launch an ORPort
3570 reachability check even when DisableNetwork is set. Noticed while
3571 fixing bug 18616; bugfix on 0.2.3.9-alpha.
3573 o Minor bugfixes (relays, hidden services):
3574 - Refuse connection requests to private OR addresses unless
3575 ExtendAllowPrivateAddresses is set. Previously, tor would connect,
3576 then refuse to send any cells to a private address. Fixes bugs
3577 17674 and 8976; bugfix on 0.2.3.21-rc. Patch by teor.
3579 o Minor bugfixes (security, hidden services):
3580 - Prevent hidden services connecting to client-supplied rendezvous
3581 addresses that are reserved as internal or multicast. Fixes bug
3582 8976; bugfix on 0.2.3.21-rc. Patch by dgoulet and teor.
3584 o Minor bugfixes (statistics):
3585 - Consistently check for overflow in round_*_to_next_multiple_of
3586 functions, and add unit tests with additional and maximal values.
3587 Fixes part of bug 13192; bugfix on 0.2.2.1-alpha.
3588 - Handle edge cases in the laplace functions: avoid division by
3589 zero, avoid taking the log of zero, and silence clang type
3590 conversion warnings using round and trunc. Add unit tests for edge
3591 cases with maximal values. Fixes part of bug 13192; bugfix
3593 - We now include consensus downloads via IPv6 in our directory-
3594 request statistics. Fixes bug 18460; bugfix on 0.2.3.14-alpha.
3596 o Minor bugfixes (test networks, IPv6):
3597 - Allow internal IPv6 addresses in descriptors in test networks.
3598 Fixes bug 17153; bugfix on 0.2.3.16-alpha. Patch by teor, reported
3601 o Minor bugfixes (testing):
3602 - Check the full results of SHA256 and SHA512 digests in the unit
3603 tests. Bugfix on 0.2.2.4-alpha. Patch by teor.
3604 - Fix a memory leak in the ntor test. Fixes bug 17778; bugfix
3606 - Fix a small memory leak that would occur when the
3607 TestingEnableCellStatsEvent option was turned on. Fixes bug 18673;
3608 bugfix on 0.2.5.2-alpha.
3609 - Make unit tests pass on IPv6-only systems, and systems without
3610 localhost addresses (like some FreeBSD jails). Fixes bug 17632;
3611 bugfix on 0.2.7.3-rc. Patch by teor.
3612 - The test for log_heartbeat was incorrectly failing in timezones
3613 with non-integer offsets. Instead of comparing the end of the time
3614 string against a constant, compare it to the output of
3615 format_local_iso_time when given the correct input. Fixes bug
3616 18039; bugfix on 0.2.5.4-alpha.
3617 - We no longer disable assertions in the unit tests when coverage is
3618 enabled. Instead, we require you to say --disable-asserts-in-tests
3619 to the configure script if you need assertions disabled in the
3620 unit tests (for example, if you want to perform branch coverage).
3621 Fixes bug 18242; bugfix on 0.2.7.1-alpha.
3623 o Minor bugfixes (time handling):
3624 - When correcting a corrupt 'struct tm' value, fill in the tm_wday
3625 field. Otherwise, our unit tests crash on Windows. Fixes bug
3626 18977; bugfix on 0.2.2.25-alpha.
3627 - Avoid overflow in tor_timegm when parsing dates in and after 2038
3628 on platforms with 32-bit time_t. Fixes bug 18479; bugfix on
3629 0.0.2pre14. Patch by teor.
3631 o Minor bugfixes (tor-gencert):
3632 - Correctly handle the case where an authority operator enters a
3633 passphrase but sends an EOF before sending a newline. Fixes bug
3634 17443; bugfix on 0.2.0.20-rc. Found by junglefowl.
3636 o Code simplification and refactoring:
3637 - Clean up a little duplicated code in
3638 crypto_expand_key_material_TAP(). Closes ticket 17587; patch
3640 - Decouple the list of streams waiting to be attached to circuits
3641 from the overall connection list. This change makes it possible to
3642 attach streams quickly while simplifying Tor's callgraph and
3643 avoiding O(N) scans of the entire connection list. Closes
3645 - Extract the more complicated parts of circuit_mark_for_close()
3646 into a new function that we run periodically before circuits are
3647 freed. This change removes more than half of the functions
3648 currently in the "blob". Closes ticket 17218.
3649 - Move logging of redundant policy entries in
3650 policies_parse_exit_policy_internal into its own function. Closes
3651 ticket 17608; patch from "juce".
3652 - Quote all the string interpolations in configure.ac -- even those
3653 which we are pretty sure can't contain spaces. Closes ticket
3654 17744. Patch from zerosion.
3655 - Remove code for configuring OpenSSL dynamic locks; OpenSSL doesn't
3656 use them. Closes ticket 17926.
3657 - Remove specialized code for non-inplace AES_CTR. 99% of our AES is
3658 inplace, so there's no need to have a separate implementation for
3659 the non-inplace code. Closes ticket 18258. Patch from Malek.
3660 - Simplify return types for some crypto functions that can't
3661 actually fail. Patch from Hassan Alsibyani. Closes ticket 18259.
3662 - When a direct directory request fails immediately on launch,
3663 instead of relaunching that request from inside the code that
3664 launches it, instead mark the connection for teardown. This change
3665 simplifies Tor's callback and prevents the directory-request
3666 launching code from invoking itself recursively. Closes
3670 - Add a description of the correct use of the '--keygen' command-
3671 line option. Closes ticket 17583; based on text by 's7r'.
3672 - Change build messages to refer to "Fedora" instead of "Fedora
3673 Core", and "dnf" instead of "yum". Closes tickets 18459 and 18426.
3674 Patches from "icanhasaccount" and "cypherpunks".
3675 - Document the contents of the 'datadir/keys' subdirectory in the
3676 manual page. Closes ticket 17621.
3677 - Document the minimum HeartbeatPeriod value. Closes ticket 15638.
3678 - Explain actual minima for BandwidthRate. Closes ticket 16382.
3679 - Fix a minor formatting typo in the manpage. Closes ticket 17791.
3680 - Mention torspec URL in the manpage and point the reader to it
3681 whenever we mention a document that belongs in torspce. Fixes
3683 - Stop recommending use of nicknames to identify relays in our
3684 MapAddress documentation. Closes ticket 18312.
3687 - Remove client-side support for connecting to Tor relays running
3688 versions of Tor before 0.2.3.6-alpha. These relays didn't support
3689 the v3 TLS handshake protocol, and are no longer allowed on the
3690 Tor network. Implements the client side of ticket 11150. Based on
3691 patches by Tom van der Woerdt.
3692 - We no longer maintain an internal freelist in memarea.c.
3693 Allocators should be good enough to make this code unnecessary,
3694 and it's doubtful that it ever had any performance benefit.
3697 - Add unit tests to check for common RNG failure modes, such as
3698 returning all zeroes, identical values, or incrementing values
3699 (OpenSSL's rand_predictable feature). Patch by teor.
3700 - Always test both ed25519 backends, so that we can be sure that our
3701 batch-open replacement code works. Part of ticket 16794.
3702 - Cover dns_resolve_impl() in dns.c with unit tests. Implements a
3703 portion of ticket 16831.
3704 - Fix several warnings from clang's address sanitizer produced in
3706 - Log more information when the backtrace tests fail. Closes ticket
3707 17892. Patch from "cypherpunks."
3708 - More unit tests for compat_libevent.c, procmon.c, tortls.c,
3709 util_format.c, directory.c, and options_validate.c. Closes tickets
3710 17075, 17082, 17084, 17003, and 17076 respectively. Patches from
3712 - Treat backtrace test failures as expected on FreeBSD until we
3713 solve bug 17808. Closes ticket 18204.
3714 - Unit tests for directory_handle_command_get. Closes ticket 17004.
3715 Patch from Reinaldo de Souza Jr.
3718 Changes in version 0.2.7.6 - 2015-12-10
3719 Tor version 0.2.7.6 fixes a major bug in entry guard selection, as
3720 well as a minor bug in hidden service reliability.
3722 o Major bugfixes (guard selection):
3723 - Actually look at the Guard flag when selecting a new directory
3724 guard. When we implemented the directory guard design, we
3725 accidentally started treating all relays as if they have the Guard
3726 flag during guard selection, leading to weaker anonymity and worse
3727 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
3730 o Minor features (geoip):
3731 - Update geoip and geoip6 to the December 1 2015 Maxmind GeoLite2
3734 o Minor bugfixes (compilation):
3735 - When checking for net/pfvar.h, include netinet/in.h if possible.
3736 This fixes transparent proxy detection on OpenBSD. Fixes bug
3737 17551; bugfix on 0.1.2.1-alpha. Patch from "rubiate".
3738 - Fix a compilation warning with Clang 3.6: Do not check the
3739 presence of an address which can never be NULL. Fixes bug 17781.
3741 o Minor bugfixes (correctness):
3742 - When displaying an IPv6 exit policy, include the mask bits
3743 correctly even when the number is greater than 31. Fixes bug
3744 16056; bugfix on 0.2.4.7-alpha. Patch from "gturner".
3745 - The wrong list was used when looking up expired intro points in a
3746 rend service object, causing what we think could be reachability
3747 issues for hidden services, and triggering a BUG log. Fixes bug
3748 16702; bugfix on 0.2.7.2-alpha.
3749 - Fix undefined behavior in the tor_cert_checksig function. Fixes
3750 bug 17722; bugfix on 0.2.7.2-alpha.
3753 Changes in version 0.2.7.5 - 2015-11-20
3754 The Tor 0.2.7 release series is dedicated to the memory of Tor user
3755 and privacy advocate Caspar Bowden (1961-2015). Caspar worked
3756 tirelessly to advocate human rights regardless of national borders,
3757 and oppose the encroachments of mass surveillance. He opposed national
3758 exceptionalism, he brought clarity to legal and policy debates, he
3759 understood and predicted the impact of mass surveillance on the world,
3760 and he laid the groundwork for resisting it. While serving on the Tor
3761 Project's board of directors, he brought us his uncompromising focus
3762 on technical excellence in the service of humankind. Caspar was an
3763 inimitable force for good and a wonderful friend. He was kind,
3764 humorous, generous, gallant, and believed we should protect one
3765 another without exception. We honor him here for his ideals, his
3766 efforts, and his accomplishments. Please honor his memory with works
3767 that would make him proud.
3769 Tor 0.2.7.5 is the first stable release in the Tor 0.2.7 series.
3771 The 0.2.7 series adds a more secure identity key type for relays,
3772 improves cryptography performance, resolves several longstanding
3773 hidden-service performance issues, improves controller support for
3774 hidden services, and includes small bugfixes and performance
3775 improvements throughout the program. This release series also includes
3776 more tests than before, and significant simplifications to which parts
3777 of Tor invoke which others. For a full list of changes, see below.
3779 o New system requirements:
3780 - Tor no longer includes workarounds to support Libevent versions
3781 before 1.3e. Libevent 2.0 or later is recommended. Closes
3783 - Tor no longer supports copies of OpenSSL that are missing support
3784 for Elliptic Curve Cryptography. (We began using ECC when
3785 available in 0.2.4.8-alpha, for more safe and efficient key
3786 negotiation.) In particular, support for at least one of P256 or
3787 P224 is now required, with manual configuration needed if only
3788 P224 is available. Resolves ticket 16140.
3789 - Tor no longer supports versions of OpenSSL before 1.0. (If you are
3790 on an operating system that has not upgraded to OpenSSL 1.0 or
3791 later, and you compile Tor from source, you will need to install a
3792 more recent OpenSSL to link Tor against.) These versions of
3793 OpenSSL are still supported by the OpenSSL, but the numerous
3794 cryptographic improvements in later OpenSSL releases makes them a
3795 clear choice. Resolves ticket 16034.
3797 o Major features (controller):
3798 - Add the ADD_ONION and DEL_ONION commands that allow the creation
3799 and management of hidden services via the controller. Closes
3801 - New "GETINFO onions/current" and "GETINFO onions/detached"
3802 commands to get information about hidden services created via the
3803 controller. Part of ticket 6411.
3804 - New HSFETCH command to launch a request for a hidden service
3805 descriptor. Closes ticket 14847.
3806 - New HSPOST command to upload a hidden service descriptor. Closes
3807 ticket 3523. Patch by "DonnchaC".
3809 o Major features (Ed25519 identity keys, Proposal 220):
3810 - Add support for offline encrypted Ed25519 master keys. To use this
3811 feature on your tor relay, run "tor --keygen" to make a new master
3812 key (or to make a new signing key if you already have a master
3813 key). Closes ticket 13642.
3814 - All relays now maintain a stronger identity key, using the Ed25519
3815 elliptic curve signature format. This master key is designed so
3816 that it can be kept offline. Relays also generate an online
3817 signing key, and a set of other Ed25519 keys and certificates.
3818 These are all automatically regenerated and rotated as needed.
3819 Implements part of ticket 12498.
3820 - Directory authorities now vote on Ed25519 identity keys along with
3821 RSA1024 keys. Implements part of ticket 12498.
3822 - Directory authorities track which Ed25519 identity keys have been
3823 used with which RSA1024 identity keys, and do not allow them to
3824 vary freely. Implements part of ticket 12498.
3825 - Microdescriptors now include Ed25519 identity keys. Implements
3826 part of ticket 12498.
3827 - Add a --newpass option to allow changing or removing the
3828 passphrase of an encrypted key with tor --keygen. Implements part
3830 - Add a new OfflineMasterKey option to tell Tor never to try loading
3831 or generating a secret Ed25519 identity key. You can use this in
3832 combination with tor --keygen to manage offline and/or encrypted
3833 Ed25519 keys. Implements ticket 16944.
3834 - On receiving a HUP signal, check to see whether the Ed25519
3835 signing key has changed, and reload it if so. Closes ticket 16790.
3836 - Significant usability improvements for Ed25519 key management. Log
3837 messages are better, and the code can recover from far more
3838 failure conditions. Thanks to "s7r" for reporting and diagnosing
3841 o Major features (ECC performance):
3842 - Improve the runtime speed of Ed25519 signature verification by
3843 using Ed25519-donna's batch verification support. Implements
3845 - Improve the speed of Ed25519 operations and Curve25519 keypair
3846 generation when built targeting 32 bit x86 platforms with SSE2
3847 available. Implements ticket 16535.
3848 - Improve the runtime speed of Ed25519 operations by using the
3849 public-domain Ed25519-donna by Andrew M. ("floodyberry").
3850 Implements ticket 16467.
3851 - Improve the runtime speed of the ntor handshake by using an
3852 optimized curve25519 basepoint scalarmult implementation from the
3853 public-domain Ed25519-donna by Andrew M. ("floodyberry"), based on
3854 ideas by Adam Langley. Implements ticket 9663.
3856 o Major features (Hidden services):
3857 - Hidden services, if using the EntryNodes option, are required to
3858 use more than one EntryNode, in order to avoid a guard discovery
3859 attack. (This would only affect people who had configured hidden
3860 services and manually specified the EntryNodes option with a
3861 single entry-node. The impact was that it would be easy to
3862 remotely identify the guard node used by such a hidden service.
3863 See ticket for more information.) Fixes ticket 14917.
3864 - Add the torrc option HiddenServiceNumIntroductionPoints, to
3865 specify a fixed number of introduction points. Its maximum value
3866 is 10 and default is 3. Using this option can increase a hidden
3867 service's reliability under load, at the cost of making it more
3868 visible that the hidden service is facing extra load. Closes
3870 - Remove the adaptive algorithm for choosing the number of
3871 introduction points, which used to change the number of
3872 introduction points (poorly) depending on the number of
3873 connections the HS sees. Closes ticket 4862.
3875 o Major features (onion key cross-certification):
3876 - Relay descriptors now include signatures of their own identity
3877 keys, made using the TAP and ntor onion keys. These signatures
3878 allow relays to prove ownership of their own onion keys. Because
3879 of this change, microdescriptors will no longer need to include
3880 RSA identity keys. Implements proposal 228; closes ticket 12499.
3882 o Major bugfixes (client-side privacy, also in 0.2.6.9):
3883 - Properly separate out each SOCKSPort when applying stream
3884 isolation. The error occurred because each port's session group
3885 was being overwritten by a default value when the listener
3886 connection was initialized. Fixes bug 16247; bugfix on
3887 0.2.6.3-alpha. Patch by "jojelino".
3889 o Major bugfixes (hidden service clients, stability, also in 0.2.6.10):
3890 - Stop refusing to store updated hidden service descriptors on a
3891 client. This reverts commit 9407040c59218 (which indeed fixed bug
3892 14219, but introduced a major hidden service reachability
3893 regression detailed in bug 16381). This is a temporary fix since
3894 we can live with the minor issue in bug 14219 (it just results in
3895 some load on the network) but the regression of 16381 is too much
3896 of a setback. First-round fix for bug 16381; bugfix
3899 o Major bugfixes (hidden services):
3900 - Revert commit that made directory authorities assign the HSDir
3901 flag to relay without a DirPort; this was bad because such relays
3902 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
3904 - When cannibalizing a circuit for an introduction point, always
3905 extend to the chosen exit node (creating a 4 hop circuit).
3906 Previously Tor would use the current circuit exit node, which
3907 changed the original choice of introduction point, and could cause
3908 the hidden service to skip excluded introduction points or
3909 reconnect to a skipped introduction point. Fixes bug 16260; bugfix
3912 o Major bugfixes (memory leaks):
3913 - Fix a memory leak in ed25519 batch signature checking. Fixes bug
3914 17398; bugfix on 0.2.6.1-alpha.
3916 o Major bugfixes (open file limit):
3917 - The open file limit wasn't checked before calling
3918 tor_accept_socket_nonblocking(), which would make Tor exceed the
3919 limit. Now, before opening a new socket, Tor validates the open
3920 file limit just before, and if the max has been reached, return an
3921 error. Fixes bug 16288; bugfix on 0.1.1.1-alpha.
3923 o Major bugfixes (security, correctness):
3924 - Fix an error that could cause us to read 4 bytes before the
3925 beginning of an openssl string. This bug could be used to cause
3926 Tor to crash on systems with unusual malloc implementations, or
3927 systems with unusual hardening installed. Fixes bug 17404; bugfix
3930 o Major bugfixes (stability, also in 0.2.6.10):
3931 - Stop crashing with an assertion failure when parsing certain kinds
3932 of malformed or truncated microdescriptors. Fixes bug 16400;
3933 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
3934 by "cypherpunks_backup".
3935 - Stop random client-side assertion failures that could occur when
3936 connecting to a busy hidden service, or connecting to a hidden
3937 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
3940 o Minor features (client, SOCKS):
3941 - Add GroupWritable and WorldWritable options to unix-socket based
3942 SocksPort and ControlPort options. These options apply to a single
3943 socket, and override {Control,Socks}SocketsGroupWritable. Closes
3945 - Relax the validation done to hostnames in SOCKS5 requests, and
3946 allow a single trailing '.' to cope with clients that pass FQDNs
3947 using that syntax to explicitly indicate that the domain name is
3948 fully-qualified. Fixes bug 16674; bugfix on 0.2.6.2-alpha.
3949 - Relax the validation of hostnames in SOCKS5 requests, allowing the
3950 character '_' to appear, in order to cope with domains observed in
3951 the wild that are serving non-RFC compliant records. Resolves
3954 o Minor features (client-side privacy):
3955 - New KeepAliveIsolateSOCKSAuth option to indefinitely extend circuit
3956 lifespan when IsolateSOCKSAuth and streams with SOCKS
3957 authentication are attached to the circuit. This allows
3958 applications like TorBrowser to manage circuit lifetime on their
3959 own. Implements feature 15482.
3960 - When logging malformed hostnames from SOCKS5 requests, respect
3961 SafeLogging configuration. Fixes bug 16891; bugfix on 0.1.1.16-rc.
3963 o Minor features (clock-jump tolerance):
3964 - Recover better when our clock jumps back many hours, like might
3965 happen for Tails or Whonix users who start with a very wrong
3966 hardware clock, use Tor to discover a more accurate time, and then
3967 fix their clock. Resolves part of ticket 8766.
3969 o Minor features (command-line interface):
3970 - Make --hash-password imply --hush to prevent unnecessary noise.
3971 Closes ticket 15542. Patch from "cypherpunks".
3972 - Print a warning whenever we find a relative file path being used
3973 as torrc option. Resolves issue 14018.
3975 o Minor features (compilation):
3976 - Give a warning as early as possible when trying to build with an
3977 unsupported OpenSSL version. Closes ticket 16901.
3978 - Use C99 variadic macros when the compiler is not GCC. This avoids
3979 failing compilations on MSVC, and fixes a log-file-based race
3980 condition in our old workarounds. Original patch from Gisle Vanem.
3982 o Minor features (control protocol):
3983 - Support network-liveness GETINFO key and NETWORK_LIVENESS event in
3984 the control protocol. Resolves ticket 15358.
3986 o Minor features (controller):
3987 - Add DirAuthority lines for default directory authorities to the
3988 output of the "GETINFO config/defaults" command if not already
3989 present. Implements ticket 14840.
3990 - Controllers can now use "GETINFO hs/client/desc/id/..." to
3991 retrieve items from the client's hidden service descriptor cache.
3992 Closes ticket 14845.
3993 - Implement a new controller command "GETINFO status/fresh-relay-
3994 descs" to fetch a descriptor/extrainfo pair that was generated on
3995 demand just for the controller's use. Implements ticket 14784.
3997 o Minor features (directory authorities):
3998 - Directory authorities no longer vote against the "Fast", "Stable",
3999 and "HSDir" flags just because they were going to vote against
4000 "Running": if the consensus turns out to be that the router was
4001 running, then the authority's vote should count. Patch from Peter
4002 Retzlaff; closes issue 8712.
4004 o Minor features (directory authorities, security, also in 0.2.6.9):
4005 - The HSDir flag given by authorities now requires the Stable flag.
4006 For the current network, this results in going from 2887 to 2806
4007 HSDirs. Also, it makes it harder for an attacker to launch a sybil
4008 attack by raising the effort for a relay to become Stable to
4009 require at the very least 7 days, while maintaining the 96 hours
4010 uptime requirement for HSDir. Implements ticket 8243.
4012 o Minor features (DoS-resistance):
4013 - Make it harder for attackers to overload hidden services with
4014 introductions, by blocking multiple introduction requests on the
4015 same circuit. Resolves ticket 15515.
4017 o Minor features (geoip):
4018 - Update geoip and geoip6 to the October 9 2015 Maxmind GeoLite2
4021 o Minor features (hidden services):
4022 - Add the new options "HiddenServiceMaxStreams" and
4023 "HiddenServiceMaxStreamsCloseCircuit" to allow hidden services to
4024 limit the maximum number of simultaneous streams per circuit, and
4025 optionally tear down the circuit when the limit is exceeded. Part
4027 - Client now uses an introduction point failure cache to know when
4028 to fetch or keep a descriptor in their cache. Previously, failures
4029 were recorded implicitly, but not explicitly remembered. Closes
4031 - Relays need to have the Fast flag to get the HSDir flag. As this
4032 is being written, we'll go from 2745 HSDirs down to 2342, a ~14%
4033 drop. This change should make some attacks against the hidden
4034 service directory system harder. Fixes ticket 15963.
4035 - Turn on hidden service statistics collection by setting the torrc
4036 option HiddenServiceStatistics to "1" by default. (This keeps
4037 track only of the fraction of traffic used by hidden services, and
4038 the total number of hidden services in existence.) Closes
4040 - To avoid leaking HS popularity, don't cycle the introduction point
4041 when we've handled a fixed number of INTRODUCE2 cells but instead
4042 cycle it when a random number of introductions is reached, thus
4043 making it more difficult for an attacker to find out the amount of
4044 clients that have used the introduction point for a specific HS.
4045 Closes ticket 15745.
4047 o Minor features (logging):
4048 - Include the Tor version in all LD_BUG log messages, since people
4049 tend to cut and paste those into the bugtracker. Implements
4052 o Minor features (pluggable transports):
4053 - When launching managed pluggable transports on Linux systems,
4054 attempt to have the kernel deliver a SIGTERM on tor exit if the
4055 pluggable transport process is still running. Resolves
4057 - When launching managed pluggable transports, setup a valid open
4058 stdin in the child process that can be used to detect if tor has
4059 terminated. The "TOR_PT_EXIT_ON_STDIN_CLOSE" environment variable
4060 can be used by implementations to detect this new behavior.
4061 Resolves ticket 15435.
4063 o Minor bugfixes (torrc exit policies):
4064 - In each instance above, usage advice is provided to avoid the
4065 message. Resolves ticket 16069. Patch by "teor". Fixes part of bug
4066 16069; bugfix on 0.2.4.7-alpha.
4067 - In torrc, "accept6 *" and "reject6 *" ExitPolicy lines now only
4068 produce IPv6 wildcard addresses. Previously they would produce
4069 both IPv4 and IPv6 wildcard addresses. Patch by "teor". Fixes part
4070 of bug 16069; bugfix on 0.2.4.7-alpha.
4071 - When parsing torrc ExitPolicies, we now issue an info-level
4072 message when expanding an "accept/reject *" line to include both
4073 IPv4 and IPv6 wildcard addresses. Related to ticket 16069.
4074 - When parsing torrc ExitPolicies, we now warn for a number of cases
4075 where the user's intent is likely to differ from Tor's actual
4076 behavior. These include: using an IPv4 address with an accept6 or
4077 reject6 line; using "private" on an accept6 or reject6 line; and
4078 including any ExitPolicy lines after accept *:* or reject *:*.
4079 Related to ticket 16069.
4081 o Minor bugfixes (command-line interface):
4082 - When "--quiet" is provided along with "--validate-config", do not
4083 write anything to stdout on success. Fixes bug 14994; bugfix
4085 - When complaining about bad arguments to "--dump-config", use
4087 - Print usage information for --dump-config when it is used without
4088 an argument. Also, fix the error message to use different wording
4089 and add newline at the end. Fixes bug 15541; bugfix
4092 o Minor bugfixes (compilation):
4093 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
4094 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
4095 - Repair compilation with the most recent (unreleased, alpha)
4096 vesions of OpenSSL 1.1. Fixes part of ticket 17237.
4098 o Minor bugfixes (compilation, also in 0.2.6.9):
4099 - Build with --enable-systemd correctly when libsystemd is
4100 installed, but systemd is not. Fixes bug 16164; bugfix on
4101 0.2.6.3-alpha. Patch from Peter Palfrader.
4103 o Minor bugfixes (configuration, unit tests):
4104 - Only add the default fallback directories when the DirAuthorities,
4105 AlternateDirAuthority, and FallbackDir directory config options
4106 are set to their defaults. The default fallback directory list is
4107 currently empty, this fix will only change tor's behavior when it
4108 has default fallback directories. Includes unit tests for
4109 consider_adding_dir_servers(). Fixes bug 15642; bugfix on
4110 90f6071d8dc0 in 0.2.4.7-alpha. Patch by "teor".
4112 o Minor bugfixes (controller):
4113 - Add the descriptor ID in each HS_DESC control event. It was
4114 missing, but specified in control-spec.txt. Fixes bug 15881;
4115 bugfix on 0.2.5.2-alpha.
4117 o Minor bugfixes (correctness):
4118 - For correctness, avoid modifying a constant string in
4119 handle_control_postdescriptor. Fixes bug 15546; bugfix
4121 - Remove side-effects from tor_assert() calls. This was harmless,
4122 because we never disable assertions, but it is bad style and
4123 unnecessary. Fixes bug 15211; bugfix on 0.2.5.5, 0.2.2.36,
4125 - When calling channel_free_list(), avoid calling smartlist_remove()
4126 while inside a FOREACH loop. This partially reverts commit
4127 17356fe7fd96af where the correct SMARTLIST_DEL_CURRENT was
4128 incorrectly removed. Fixes bug 16924; bugfix on 0.2.4.4-alpha.
4130 o Minor bugfixes (crypto error-handling, also in 0.2.6.10):
4131 - Check for failures from crypto_early_init, and refuse to continue.
4132 A previous typo meant that we could keep going with an
4133 uninitialized crypto library, and would have OpenSSL initialize
4134 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
4135 when implementing ticket 4900. Patch by "teor".
4137 o Minor bugfixes (hidden service):
4138 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
4139 a client authorized hidden service. Fixes bug 15823; bugfix
4141 - Remove an extraneous newline character from the end of hidden
4142 service descriptors. Fixes bug 15296; bugfix on 0.2.0.10-alpha.
4144 o Minor bugfixes (Linux seccomp2 sandbox):
4145 - Use the sandbox in tor_open_cloexec whether or not O_CLOEXEC is
4146 defined. Patch by "teor". Fixes bug 16515; bugfix on 0.2.3.1-alpha.
4147 - Allow bridge authorities to run correctly under the seccomp2
4148 sandbox. Fixes bug 16964; bugfix on 0.2.5.1-alpha.
4149 - Add the "hidserv-stats" filename to our sandbox filter for the
4150 HiddenServiceStatistics option to work properly. Fixes bug 17354;
4151 bugfix on 0.2.6.2-alpha. Patch from David Goulet.
4153 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.10):
4154 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
4155 these when eventfd2() support is missing. Fixes bug 16363; bugfix
4156 on 0.2.6.3-alpha. Patch from "teor".
4158 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.9):
4159 - Allow systemd connections to work with the Linux seccomp2 sandbox
4160 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
4162 - Fix sandboxing to work when running as a relay, by allowing the
4163 renaming of secret_id_key, and allowing the eventfd2 and futex
4164 syscalls. Fixes bug 16244; bugfix on 0.2.6.1-alpha. Patch by
4167 o Minor bugfixes (logging):
4168 - When building Tor under Clang, do not include an extra set of
4169 parentheses in log messages that include function names. Fixes bug
4170 15269; bugfix on every released version of Tor when compiled with
4171 recent enough Clang.
4173 o Minor bugfixes (network):
4174 - When attempting to use fallback technique for network interface
4175 lookup, disregard loopback and multicast addresses since they are
4176 unsuitable for public communications.
4178 o Minor bugfixes (open file limit):
4179 - Fix set_max_file_descriptors() to set by default the max open file
4180 limit to the current limit when setrlimit() fails. Fixes bug
4181 16274; bugfix on tor- 0.2.0.10-alpha. Patch by dgoulet.
4183 o Minor bugfixes (portability):
4184 - Check correctly for Windows socket errors in the workqueue
4185 backend. Fixes bug 16741; bugfix on 0.2.6.3-alpha.
4186 - Try harder to normalize the exit status of the Tor process to the
4187 standard-provided range. Fixes bug 16975; bugfix on every version
4189 - Use libexecinfo on FreeBSD to enable backtrace support. Fixes part
4190 of bug 17151; bugfix on 0.2.5.2-alpha. Patch from Marcin Cieślak.
4192 o Minor bugfixes (relay):
4193 - Ensure that worker threads actually exit when a fatal error or
4194 shutdown is indicated. This fix doesn't currently affect the
4195 behavior of Tor, because Tor workers never indicates fatal error
4196 or shutdown except in the unit tests. Fixes bug 16868; bugfix
4198 - Fix a rarely-encountered memory leak when failing to initialize
4199 the thread pool. Fixes bug 16631; bugfix on 0.2.6.3-alpha. Patch
4201 - Unblock threads before releasing the work queue mutex to ensure
4202 predictable scheduling behavior. Fixes bug 16644; bugfix
4205 o Minor bugfixes (security, exit policies):
4206 - ExitPolicyRejectPrivate now also rejects the relay's published
4207 IPv6 address (if any), and any publicly routable IPv4 or IPv6
4208 addresses on any local interfaces. ticket 17027. Patch by "teor".
4209 Fixes bug 17027; bugfix on 0.2.0.11-alpha.
4211 o Minor bugfixes (statistics):
4212 - Disregard the ConnDirectionStatistics torrc options when Tor is
4213 not a relay since in that mode of operation no sensible data is
4214 being collected and because Tor might run into measurement hiccups
4215 when running as a client for some time, then becoming a relay.
4216 Fixes bug 15604; bugfix on 0.2.2.35.
4218 o Minor bugfixes (systemd):
4219 - Tor's systemd unit file no longer contains extraneous spaces.
4220 These spaces would sometimes confuse tools like deb-systemd-
4221 helper. Fixes bug 16162; bugfix on 0.2.5.5-alpha.
4223 o Minor bugfixes (test networks):
4224 - When self-testing reachability, use ExtendAllowPrivateAddresses to
4225 determine if local/private addresses imply reachability. The
4226 previous fix used TestingTorNetwork, which implies
4227 ExtendAllowPrivateAddresses, but this excluded rare configurations
4228 where ExtendAllowPrivateAddresses is set but TestingTorNetwork is
4229 not. Fixes bug 15771; bugfix on 0.2.6.1-alpha. Patch by "teor",
4230 issue discovered by CJ Ess.
4232 o Minor bugfixes (tests, also in 0.2.6.9):
4233 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
4234 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
4236 o Code simplification and refactoring:
4237 - Change the function that's called when we need to retry all
4238 downloads so that it only reschedules the downloads to happen
4239 immediately, rather than launching them all at once itself. This
4240 further simplifies Tor's callgraph.
4241 - Define WINVER and _WIN32_WINNT centrally, in orconfig.h, in order
4242 to ensure they remain consistent and visible everywhere.
4243 - Move some format-parsing functions out of crypto.c and
4244 crypto_curve25519.c into crypto_format.c and/or util_format.c.
4245 - Move the client-only parts of init_keys() into a separate
4246 function. Closes ticket 16763.
4247 - Move the hacky fallback code out of get_interface_address6() into
4248 separate function and get it covered with unit-tests. Resolves
4250 - Refactor hidden service client-side cache lookup to intelligently
4251 report its various failure cases, and disentangle failure cases
4252 involving a lack of introduction points. Closes ticket 14391.
4253 - Remove some vestigial workarounds for the MSVC6 compiler. We
4254 haven't supported that in ages.
4255 - Remove the unused "nulterminate" argument from buf_pullup().
4256 - Simplify the microdesc_free() implementation so that it no longer
4257 appears (to code analysis tools) to potentially invoke a huge
4258 suite of other microdesc functions.
4259 - Simply the control graph further by deferring the inner body of
4260 directory_all_unreachable() into a callback. Closes ticket 16762.
4261 - The link authentication code has been refactored for better
4262 testability and reliability. It now uses code generated with the
4263 "trunnel" binary encoding generator, to reduce the risk of bugs
4264 due to programmer error. Done as part of ticket 12498.
4265 - Treat the loss of an owning controller as equivalent to a SIGTERM
4266 signal. This removes a tiny amount of duplicated code, and
4267 simplifies our callgraph. Closes ticket 16788.
4268 - Use our own Base64 encoder instead of OpenSSL's, to allow more
4269 control over the output. Part of ticket 15652.
4270 - When generating an event to send to the controller, we no longer
4271 put the event over the network immediately. Instead, we queue
4272 these events, and use a Libevent callback to deliver them. This
4273 change simplifies Tor's callgraph by reducing the number of
4274 functions from which all other Tor functions are reachable. Closes
4276 - Wrap Windows-only C files inside '#ifdef _WIN32' so that tools
4277 that try to scan or compile every file on Unix won't decide that
4281 - Fix capitalization of SOCKS in sample torrc. Closes ticket 15609.
4282 - Improve the descriptions of statistics-related torrc options in
4283 the manpage to describe rationale and possible uses cases. Fixes
4285 - Improve the layout and formatting of ./configure --help messages.
4286 Closes ticket 15024. Patch from "cypherpunks".
4287 - Include a specific and (hopefully) accurate documentation of the
4288 torrc file's meta-format in doc/torrc_format.txt. This is mainly
4289 of interest to people writing programs to parse or generate torrc
4290 files. This document is not a commitment to long-term
4291 compatibility; some aspects of the current format are a bit
4292 ridiculous. Closes ticket 2325.
4293 - Include the TUNING document in our source tarball. It is referred
4294 to in the ChangeLog and an error message. Fixes bug 16929; bugfix
4296 - Note that HiddenServicePorts can take a unix domain socket. Closes
4298 - Recommend a 40 GB example AccountingMax in torrc.sample rather
4299 than a 4 GB max. Closes ticket 16742.
4300 - Standardize on the term "server descriptor" in the manual page.
4301 Previously, we had used "router descriptor", "server descriptor",
4302 and "relay descriptor" interchangeably. Part of ticket 14987.
4303 - Advise users on how to configure separate IPv4 and IPv6 exit
4304 policies in the manpage and sample torrcs. Related to ticket 16069.
4305 - Fix an error in the manual page and comments for
4306 TestingDirAuthVoteHSDir[IsStrict], which suggested that a HSDir
4307 required "ORPort connectivity". While this is true, it is in no
4308 way unique to the HSDir flag. Of all the flags, only HSDirs need a
4309 DirPort configured in order for the authorities to assign that
4310 particular flag. Patch by "teor". Fixed as part of 14882; bugfix
4312 - Fix the usage message of tor-resolve(1) so that it no longer lists
4313 the removed -F option. Fixes bug 16913; bugfix on 0.2.2.28-beta.
4316 - Remove `USE_OPENSSL_BASE64` and the corresponding fallback code
4317 and always use the internal Base64 decoder. The internal decoder
4318 has been part of tor since 0.2.0.10-alpha, and no one should
4319 be using the OpenSSL one. Part of ticket 15652.
4320 - Remove the 'tor_strclear()' function; use memwipe() instead.
4321 Closes ticket 14922.
4322 - Remove the code that would try to aggressively flush controller
4323 connections while writing to them. This code was introduced in
4324 0.1.2.7-alpha, in order to keep output buffers from exceeding
4325 their limits. But there is no longer a maximum output buffer size,
4326 and flushing data in this way caused some undesirable recursions
4327 in our call graph. Closes ticket 16480.
4328 - The internal pure-C tor-fw-helper tool is now removed from the Tor
4329 distribution, in favor of the pure-Go clone available from
4330 https://gitweb.torproject.org/tor-fw-helper.git/ . The libraries
4331 used by the C tor-fw-helper are not, in our opinion, very
4332 confidence- inspiring in their secure-programming techniques.
4333 Closes ticket 13338.
4336 - Remove the (seldom-used) DynamicDHGroups feature. For anti-
4337 fingerprinting we now recommend pluggable transports; for forward-
4338 secrecy in TLS, we now use the P-256 group. Closes ticket 13736.
4339 - Remove the HidServDirectoryV2 option. Now all relays offer to
4340 store hidden service descriptors. Related to 16543.
4341 - Remove the VoteOnHidServDirectoriesV2 option, since all
4342 authorities have long set it to 1. Closes ticket 16543.
4343 - Remove the undocumented "--digests" command-line option. It
4344 complicated our build process, caused subtle build issues on
4345 multiple platforms, and is now redundant since we started
4346 including git version identifiers. Closes ticket 14742.
4347 - Tor no longer contains checks for ancient directory cache versions
4348 that didn't know about microdescriptors.
4349 - Tor no longer contains workarounds for stat files generated by
4350 super-old versions of Tor that didn't choose guards sensibly.
4353 - The test-network.sh script now supports performance testing.
4354 Requires corresponding chutney performance testing changes. Patch
4355 by "teor". Closes ticket 14175.
4356 - Add a new set of callgraph analysis scripts that use clang to
4357 produce a list of which Tor functions are reachable from which
4358 other Tor functions. We're planning to use these to help simplify
4359 our code structure by identifying illogical dependencies.
4360 - Add new 'test-full' and 'test-full-online' targets to run all
4361 tests, including integration tests with stem and chutney.
4362 - Autodetect CHUTNEY_PATH if the chutney and Tor sources are side-
4363 by-side in the same parent directory. Closes ticket 16903. Patch
4365 - Document use of coverity, clang static analyzer, and clang dynamic
4366 undefined behavior and address sanitizers in doc/HACKING. Include
4367 detailed usage instructions in the blacklist. Patch by "teor".
4368 Closes ticket 15817.
4369 - Make "bridges+hs" the default test network. This tests almost all
4370 tor functionality during make test-network, while allowing tests
4371 to succeed on non-IPv6 systems. Requires chutney commit 396da92 in
4372 test-network-bridges-hs. Closes tickets 16945 (tor) and 16946
4373 (chutney). Patches by "teor".
4374 - Make the test-workqueue test work on Windows by initializing the
4375 network before we begin.
4376 - New make target (make test-network-all) to run multiple applicable
4377 chutney test cases. Patch from Teor; closes 16953.
4378 - Now that OpenSSL has its own scrypt implementation, add an unit
4379 test that checks for interoperability between libscrypt_scrypt()
4380 and OpenSSL's EVP_PBE_scrypt() so that we could not use libscrypt
4381 and rely on EVP_PBE_scrypt() whenever possible. Resolves
4383 - The link authentication protocol code now has extensive tests.
4384 - The relay descriptor signature testing code now has
4386 - The test_workqueue program now runs faster, and is enabled by
4387 default as a part of "make check".
4388 - Unit test dns_resolve(), dns_clip_ttl() and dns_get_expiry_ttl()
4389 functions in dns.c. Implements a portion of ticket 16831.
4390 - Use environment variables rather than autoconf substitutions to
4391 send variables from the build system to the test scripts. This
4392 change should be easier to maintain, and cause 'make distcheck' to
4393 work better than before. Fixes bug 17148.
4394 - When building Tor with testing coverage enabled, run Chutney tests
4395 (if any) using the 'tor-cov' coverage binary.
4396 - When running test-network or test-stem, check for the absence of
4397 stem/chutney before doing any build operations.
4398 - Add a test to verify that the compiler does not eliminate our
4399 memwipe() implementation. Closes ticket 15377.
4400 - Add make rule `check-changes` to verify the format of changes
4401 files. Closes ticket 15180.
4402 - Add unit tests for control_event_is_interesting(). Add a compile-
4403 time check that the number of events doesn't exceed the capacity
4404 of control_event_t.event_mask. Closes ticket 15431, checks for
4405 bugs similar to 13085. Patch by "teor".
4406 - Command-line argument tests moved to Stem. Resolves ticket 14806.
4407 - Integrate the ntor, backtrace, and zero-length keys tests into the
4408 automake test suite. Closes ticket 15344.
4409 - Remove assertions during builds to determine Tor's test coverage.
4410 We don't want to trigger these even in assertions, so including
4411 them artificially makes our branch coverage look worse than it is.
4412 This patch provides the new test-stem-full and coverage-html-full
4413 configure options. Implements ticket 15400.
4414 - New TestingDirAuthVote{Exit,Guard,HSDir}IsStrict flags to
4415 explicitly manage consensus flags in testing networks. Patch by
4416 "robgjansen", modified by "teor". Implements part of ticket 14882.
4417 - Check for matching value in server response in ntor_ref.py. Fixes
4418 bug 15591; bugfix on 0.2.4.8-alpha. Reported and fixed
4420 - Set the severity correctly when testing
4421 get_interface_addresses_ifaddrs() and
4422 get_interface_addresses_win32(), so that the tests fail gracefully
4423 instead of triggering an assertion. Fixes bug 15759; bugfix on
4424 0.2.6.3-alpha. Reported by Nicolas Derive.
4426 Changes in version 0.2.6.10 - 2015-07-12
4427 Tor version 0.2.6.10 fixes some significant stability and hidden
4428 service client bugs, bulletproofs the cryptography init process, and
4429 fixes a bug when using the sandbox code with some older versions of
4430 Linux. Everyone running an older version, especially an older version
4431 of 0.2.6, should upgrade.
4433 o Major bugfixes (hidden service clients, stability):
4434 - Stop refusing to store updated hidden service descriptors on a
4435 client. This reverts commit 9407040c59218 (which indeed fixed bug
4436 14219, but introduced a major hidden service reachability
4437 regression detailed in bug 16381). This is a temporary fix since
4438 we can live with the minor issue in bug 14219 (it just results in
4439 some load on the network) but the regression of 16381 is too much
4440 of a setback. First-round fix for bug 16381; bugfix
4443 o Major bugfixes (stability):
4444 - Stop crashing with an assertion failure when parsing certain kinds
4445 of malformed or truncated microdescriptors. Fixes bug 16400;
4446 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
4447 by "cypherpunks_backup".
4448 - Stop random client-side assertion failures that could occur when
4449 connecting to a busy hidden service, or connecting to a hidden
4450 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
4453 o Minor features (geoip):
4454 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
4455 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
4457 o Minor bugfixes (crypto error-handling):
4458 - Check for failures from crypto_early_init, and refuse to continue.
4459 A previous typo meant that we could keep going with an
4460 uninitialized crypto library, and would have OpenSSL initialize
4461 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
4462 when implementing ticket 4900. Patch by "teor".
4464 o Minor bugfixes (Linux seccomp2 sandbox):
4465 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
4466 these when eventfd2() support is missing. Fixes bug 16363; bugfix
4467 on 0.2.6.3-alpha. Patch from "teor".
4470 Changes in version 0.2.6.9 - 2015-06-11
4471 Tor 0.2.6.9 fixes a regression in the circuit isolation code, increases the
4472 requirements for receiving an HSDir flag, and addresses some other small
4473 bugs in the systemd and sandbox code. Clients using circuit isolation
4474 should upgrade; all directory authorities should upgrade.
4476 o Major bugfixes (client-side privacy):
4477 - Properly separate out each SOCKSPort when applying stream
4478 isolation. The error occurred because each port's session group was
4479 being overwritten by a default value when the listener connection
4480 was initialized. Fixes bug 16247; bugfix on 0.2.6.3-alpha. Patch
4483 o Minor feature (directory authorities, security):
4484 - The HSDir flag given by authorities now requires the Stable flag.
4485 For the current network, this results in going from 2887 to 2806
4486 HSDirs. Also, it makes it harder for an attacker to launch a sybil
4487 attack by raising the effort for a relay to become Stable which
4488 takes at the very least 7 days to do so and by keeping the 96
4489 hours uptime requirement for HSDir. Implements ticket 8243.
4491 o Minor bugfixes (compilation):
4492 - Build with --enable-systemd correctly when libsystemd is
4493 installed, but systemd is not. Fixes bug 16164; bugfix on
4494 0.2.6.3-alpha. Patch from Peter Palfrader.
4496 o Minor bugfixes (Linux seccomp2 sandbox):
4497 - Fix sandboxing to work when running as a relaymby renaming of
4498 secret_id_key, and allowing the eventfd2 and futex syscalls. Fixes
4499 bug 16244; bugfix on 0.2.6.1-alpha. Patch by Peter Palfrader.
4500 - Allow systemd connections to work with the Linux seccomp2 sandbox
4501 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
4504 o Minor bugfixes (tests):
4505 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
4506 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
4509 Changes in version 0.2.6.8 - 2015-05-21
4510 Tor 0.2.6.8 fixes a bit of dodgy code in parsing INTRODUCE2 cells, and
4511 fixes an authority-side bug in assigning the HSDir flag. All directory
4512 authorities should upgrade.
4514 o Major bugfixes (hidden services, backport from 0.2.7.1-alpha):
4515 - Revert commit that made directory authorities assign the HSDir
4516 flag to relay without a DirPort; this was bad because such relays
4517 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
4520 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
4521 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
4522 a client authorized hidden service. Fixes bug 15823; bugfix
4525 o Minor features (geoip):
4526 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
4527 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
4531 Changes in version 0.2.6.7 - 2015-04-06
4532 Tor 0.2.6.7 fixes two security issues that could be used by an
4533 attacker to crash hidden services, or crash clients visiting hidden
4534 services. Hidden services should upgrade as soon as possible; clients
4535 should upgrade whenever packages become available.
4537 This release also contains two simple improvements to make hidden
4538 services a bit less vulnerable to denial-of-service attacks.
4540 o Major bugfixes (security, hidden service):
4541 - Fix an issue that would allow a malicious client to trigger an
4542 assertion failure and halt a hidden service. Fixes bug 15600;
4543 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
4544 - Fix a bug that could cause a client to crash with an assertion
4545 failure when parsing a malformed hidden service descriptor. Fixes
4546 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
4548 o Minor features (DoS-resistance, hidden service):
4549 - Introduction points no longer allow multiple INTRODUCE1 cells to
4550 arrive on the same circuit. This should make it more expensive for
4551 attackers to overwhelm hidden services with introductions.
4552 Resolves ticket 15515.
4553 - Decrease the amount of reattempts that a hidden service performs
4554 when its rendezvous circuits fail. This reduces the computational
4555 cost for running a hidden service under heavy load. Resolves
4559 Changes in version 0.2.5.12 - 2015-04-06
4560 Tor 0.2.5.12 backports two fixes from 0.2.6.7 for security issues that
4561 could be used by an attacker to crash hidden services, or crash clients
4562 visiting hidden services. Hidden services should upgrade as soon as
4563 possible; clients should upgrade whenever packages become available.
4565 This release also backports a simple improvement to make hidden
4566 services a bit less vulnerable to denial-of-service attacks.
4568 o Major bugfixes (security, hidden service):
4569 - Fix an issue that would allow a malicious client to trigger an
4570 assertion failure and halt a hidden service. Fixes bug 15600;
4571 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
4572 - Fix a bug that could cause a client to crash with an assertion
4573 failure when parsing a malformed hidden service descriptor. Fixes
4574 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
4576 o Minor features (DoS-resistance, hidden service):
4577 - Introduction points no longer allow multiple INTRODUCE1 cells to
4578 arrive on the same circuit. This should make it more expensive for
4579 attackers to overwhelm hidden services with introductions.
4580 Resolves ticket 15515.
4583 Changes in version 0.2.4.27 - 2015-04-06
4584 Tor 0.2.4.27 backports two fixes from 0.2.6.7 for security issues that
4585 could be used by an attacker to crash hidden services, or crash clients
4586 visiting hidden services. Hidden services should upgrade as soon as
4587 possible; clients should upgrade whenever packages become available.
4589 This release also backports a simple improvement to make hidden
4590 services a bit less vulnerable to denial-of-service attacks.
4592 o Major bugfixes (security, hidden service):
4593 - Fix an issue that would allow a malicious client to trigger an
4594 assertion failure and halt a hidden service. Fixes bug 15600;
4595 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
4596 - Fix a bug that could cause a client to crash with an assertion
4597 failure when parsing a malformed hidden service descriptor. Fixes
4598 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
4600 o Minor features (DoS-resistance, hidden service):
4601 - Introduction points no longer allow multiple INTRODUCE1 cells to
4602 arrive on the same circuit. This should make it more expensive for
4603 attackers to overwhelm hidden services with introductions.
4604 Resolves ticket 15515.
4607 Changes in version 0.2.6.6 - 2015-03-24
4608 Tor 0.2.6.6 is the first stable release in the 0.2.6 series.
4610 It adds numerous safety, security, correctness, and performance
4611 improvements. Client programs can be configured to use more kinds of
4612 sockets, AutomapHosts works better, the multithreading backend is
4613 improved, cell transmission is refactored, test coverage is much
4614 higher, more denial-of-service attacks are handled, guard selection is
4615 improved to handle long-term guards better, pluggable transports
4616 should work a bit better, and some annoying hidden service performance
4617 bugs should be addressed.
4619 o New compiler and system requirements:
4620 - Tor 0.2.6.x requires that your compiler support more of the C99
4621 language standard than before. The 'configure' script now detects
4622 whether your compiler supports C99 mid-block declarations and
4623 designated initializers. If it does not, Tor will not compile.
4625 We may revisit this requirement if it turns out that a significant
4626 number of people need to build Tor with compilers that don't
4627 bother implementing a 15-year-old standard. Closes ticket 13233.
4628 - Tor no longer supports systems without threading support. When we
4629 began working on Tor, there were several systems that didn't have
4630 threads, or where the thread support wasn't able to run the
4631 threads of a single process on multiple CPUs. That no longer
4632 holds: every system where Tor needs to run well now has threading
4633 support. Resolves ticket 12439.
4635 o Deprecated versions and removed support:
4636 - Tor relays older than 0.2.4.18-rc are no longer allowed to
4637 advertise themselves on the network. Closes ticket 13555.
4638 - Tor clients no longer support connecting to hidden services
4639 running on Tor 0.2.2.x and earlier; the Support022HiddenServices
4640 option has been removed. (There shouldn't be any hidden services
4641 running these versions on the network.) Closes ticket 7803.
4643 o Directory authority changes:
4644 - The directory authority Faravahar has a new IP address. This
4645 closes ticket 14487.
4646 - Remove turtles as a directory authority.
4647 - Add longclaw as a new (v3) directory authority. This implements
4648 ticket 13296. This keeps the directory authority count at 9.
4650 o Major features (bridges):
4651 - Expose the outgoing upstream HTTP/SOCKS proxy to pluggable
4652 transports if they are configured via the "TOR_PT_PROXY"
4653 environment variable. Implements proposal 232. Resolves
4656 o Major features (changed defaults):
4657 - Prevent relay operators from unintentionally running exits: When a
4658 relay is configured as an exit node, we now warn the user unless
4659 the "ExitRelay" option is set to 1. We warn even more loudly if
4660 the relay is configured with the default exit policy, since this
4661 can indicate accidental misconfiguration. Setting "ExitRelay 0"
4662 stops Tor from running as an exit relay. Closes ticket 10067.
4664 o Major features (client performance, hidden services):
4665 - Allow clients to use optimistic data when connecting to a hidden
4666 service, which should remove a round-trip from hidden service
4667 initialization. See proposal 181 for details. Implements
4670 o Major features (directory system):
4671 - Upon receiving an unparseable directory object, if its digest
4672 matches what we expected, then don't try to download it again.
4673 Previously, when we got a descriptor we didn't like, we would keep
4674 trying to download it over and over. Closes ticket 11243.
4675 - When downloading server- or microdescriptors from a directory
4676 server, we no longer launch multiple simultaneous requests to the
4677 same server. This reduces load on the directory servers,
4678 especially when directory guards are in use. Closes ticket 9969.
4679 - When downloading server- or microdescriptors over a tunneled
4680 connection, do not limit the length of our requests to what the
4681 Squid proxy is willing to handle. Part of ticket 9969.
4682 - Authorities can now vote on the correct digests and latest
4683 versions for different software packages. This allows packages
4684 that include Tor to use the Tor authority system as a way to get
4685 notified of updates and their correct digests. Implements proposal
4686 227. Closes ticket 10395.
4688 o Major features (guards):
4689 - Introduce the Guardfraction feature to improves load balancing on
4690 guard nodes. Specifically, it aims to reduce the traffic gap that
4691 guard nodes experience when they first get the Guard flag. This is
4692 a required step if we want to increase the guard lifetime to 9
4693 months or greater. Closes ticket 9321.
4695 o Major features (hidden services):
4696 - Make HS port scanning more difficult by immediately closing the
4697 circuit when a user attempts to connect to a nonexistent port.
4698 Closes ticket 13667.
4699 - Add a HiddenServiceStatistics option that allows Tor relays to
4700 gather and publish statistics about the overall size and volume of
4701 hidden service usage. Specifically, when this option is turned on,
4702 an HSDir will publish an approximate number of hidden services
4703 that have published descriptors to it the past 24 hours. Also, if
4704 a relay has acted as a hidden service rendezvous point, it will
4705 publish the approximate amount of rendezvous cells it has relayed
4706 the past 24 hours. The statistics themselves are obfuscated so
4707 that the exact values cannot be derived. For more details see
4708 proposal 238, "Better hidden service stats from Tor relays". This
4709 feature is currently disabled by default. Implements feature 13192.
4711 o Major features (performance):
4712 - Make the CPU worker implementation more efficient by avoiding the
4713 kernel and lengthening pipelines. The original implementation used
4714 sockets to transfer data from the main thread to the workers, and
4715 didn't allow any thread to be assigned more than a single piece of
4716 work at once. The new implementation avoids communications
4717 overhead by making requests in shared memory, avoiding kernel IO
4718 where possible, and keeping more requests in flight at once.
4719 Implements ticket 9682.
4721 o Major features (relay):
4722 - Raise the minimum acceptable configured bandwidth rate for bridges
4723 to 50 KiB/sec and for relays to 75 KiB/sec. (The old values were
4724 20 KiB/sec.) Closes ticket 13822.
4725 - Complete revision of the code that relays use to decide which cell
4726 to send next. Formerly, we selected the best circuit to write on
4727 each channel, but we didn't select among channels in any
4728 sophisticated way. Now, we choose the best circuits globally from
4729 among those whose channels are ready to deliver traffic.
4731 This patch implements a new inter-cmux comparison API, a global
4732 high/low watermark mechanism and a global scheduler loop for
4733 transmission prioritization across all channels as well as among
4734 circuits on one channel. This schedule is currently tuned to
4735 (tolerantly) avoid making changes in network performance, but it
4736 should form the basis for major circuit performance increases in
4737 the future. Code by Andrea; tuning by Rob Jansen; implements
4740 o Major features (sample torrc):
4741 - Add a new, infrequently-changed "torrc.minimal". This file is
4742 similar to torrc.sample, but it will change as infrequently as
4743 possible, for the benefit of users whose systems prompt them for
4744 intervention whenever a default configuration file is changed.
4745 Making this change allows us to update torrc.sample to be a more
4746 generally useful "sample torrc".
4748 o Major features (security, unix domain sockets):
4749 - Allow SocksPort to be an AF_UNIX Unix Domain Socket. Now high risk
4750 applications can reach Tor without having to create AF_INET or
4751 AF_INET6 sockets, meaning they can completely disable their
4752 ability to make non-Tor network connections. To create a socket of
4753 this type, use "SocksPort unix:/path/to/socket". Implements
4755 - Support mapping hidden service virtual ports to AF_UNIX sockets.
4756 The syntax is "HiddenServicePort 80 unix:/path/to/socket".
4757 Implements ticket 11485.
4759 o Major bugfixes (client, automap):
4760 - Repair automapping with IPv6 addresses. This automapping should
4761 have worked previously, but one piece of debugging code that we
4762 inserted to detect a regression actually caused the regression to
4763 manifest itself again. Fixes bug 13811 and bug 12831; bugfix on
4764 0.2.4.7-alpha. Diagnosed and fixed by Francisco Blas
4767 o Major bugfixes (crash, OSX, security):
4768 - Fix a remote denial-of-service opportunity caused by a bug in
4769 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
4772 o Major bugfixes (directory authorities):
4773 - Do not assign the HSDir flag to relays if they are not Valid, or
4774 currently hibernating. Fixes 12573; bugfix on 0.2.0.10-alpha.
4776 o Major bugfixes (directory bandwidth performance):
4777 - Don't flush the zlib buffer aggressively when compressing
4778 directory information for clients. This should save about 7% of
4779 the bandwidth currently used for compressed descriptors and
4780 microdescriptors. Fixes bug 11787; bugfix on 0.1.1.23.
4782 o Major bugfixes (exit node stability):
4783 - Fix an assertion failure that could occur under high DNS load.
4784 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
4785 diagnosed and fixed by "cypherpunks".
4787 o Major bugfixes (FreeBSD IPFW transparent proxy):
4788 - Fix address detection with FreeBSD transparent proxies, when
4789 "TransProxyType ipfw" is in use. Fixes bug 15064; bugfix
4792 o Major bugfixes (hidden services):
4793 - When closing an introduction circuit that was opened in parallel
4794 with others, don't mark the introduction point as unreachable.
4795 Previously, the first successful connection to an introduction
4796 point would make the other introduction points get marked as
4797 having timed out. Fixes bug 13698; bugfix on 0.0.6rc2.
4799 o Major bugfixes (Linux seccomp2 sandbox):
4800 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
4801 crash during attempts to call wait4. Fixes bug 15088; bugfix on
4802 0.2.5.1-alpha. Patch from "sanic".
4804 o Major bugfixes (mixed relay-client operation):
4805 - When running as a relay and client at the same time (not
4806 recommended), if we decide not to use a new guard because we want
4807 to retry older guards, only close the locally-originating circuits
4808 passing through that guard. Previously we would close all the
4809 circuits through that guard. Fixes bug 9819; bugfix on
4810 0.2.1.1-alpha. Reported by "skruffy".
4812 o Major bugfixes (pluggable transports):
4813 - Initialize the extended OR Port authentication cookie before
4814 launching pluggable transports. This prevents a race condition
4815 that occured when server-side pluggable transports would cache the
4816 authentication cookie before it has been (re)generated. Fixes bug
4817 15240; bugfix on 0.2.5.1-alpha.
4819 o Major bugfixes (relay, stability, possible security):
4820 - Fix a bug that could lead to a relay crashing with an assertion
4821 failure if a buffer of exactly the wrong layout is passed to
4822 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
4823 0.2.0.10-alpha. Patch from "cypherpunks".
4824 - Do not assert if the 'data' pointer on a buffer is advanced to the
4825 very end of the buffer; log a BUG message instead. Only assert if
4826 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
4828 o Minor features (build):
4829 - New --disable-system-torrc compile-time option to prevent Tor from
4830 looking for the system-wide torrc or torrc-defaults files.
4831 Resolves ticket 13037.
4833 o Minor features (client):
4834 - Clients are now willing to send optimistic data (before they
4835 receive a 'connected' cell) to relays of any version. (Relays
4836 without support for optimistic data are no longer supported on the
4837 Tor network.) Resolves ticket 13153.
4839 o Minor features (client):
4840 - Validate hostnames in SOCKS5 requests more strictly. If SafeSocks
4841 is enabled, reject requests with IP addresses as hostnames.
4842 Resolves ticket 13315.
4844 o Minor features (controller):
4845 - Add a "SIGNAL HEARTBEAT" controller command that tells Tor to
4846 write an unscheduled heartbeat message to the log. Implements
4848 - Include SOCKS_USERNAME and SOCKS_PASSWORD values in controller
4849 events so controllers can observe circuit isolation inputs. Closes
4851 - ControlPort now supports the unix:/path/to/socket syntax as an
4852 alternative to the ControlSocket option, for consistency with
4853 SocksPort and HiddenServicePort. Closes ticket 14451.
4854 - New "GETINFO bw-event-cache" to get information about recent
4855 bandwidth events. Closes ticket 14128. Useful for controllers to
4856 get recent bandwidth history after the fix for ticket 13988.
4857 - Messages about problems in the bootstrap process now include
4858 information about the server we were trying to connect to when we
4859 noticed the problem. Closes ticket 15006.
4861 o Minor features (Denial of service resistance):
4862 - Count the total number of bytes used storing hidden service
4863 descriptors against the value of MaxMemInQueues. If we're low on
4864 memory, and more than 20% of our memory is used holding hidden
4865 service descriptors, free them until no more than 10% of our
4866 memory holds hidden service descriptors. Free the least recently
4867 fetched descriptors first. Resolves ticket 13806.
4868 - When we have recently been under memory pressure (over 3/4 of
4869 MaxMemInQueues is allocated), then allocate smaller zlib objects
4870 for small requests. Closes ticket 11791.
4872 o Minor features (directory authorities):
4873 - Don't list relays with a bandwidth estimate of 0 in the consensus.
4874 Implements a feature proposed during discussion of bug 13000.
4875 - In tor-gencert, report an error if the user provides the same
4876 argument more than once.
4877 - If a directory authority can't find a best consensus method in the
4878 votes that it holds, it now falls back to its favorite consensus
4879 method. Previously, it fell back to method 1. Neither of these is
4880 likely to get enough signatures, but "fall back to favorite"
4881 doesn't require us to maintain support an obsolete consensus
4882 method. Implements part of proposal 215.
4884 o Minor features (geoip):
4885 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
4886 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
4889 o Minor features (guard nodes):
4890 - Reduce the time delay before saving guard status to disk from 10
4891 minutes to 30 seconds (or from one hour to 10 minutes if
4892 AvoidDiskWrites is set). Closes ticket 12485.
4894 o Minor features (heartbeat):
4895 - On relays, report how many connections we negotiated using each
4896 version of the Tor link protocols. This information will let us
4897 know if removing support for very old versions of the Tor
4898 protocols is harming the network. Closes ticket 15212.
4900 o Minor features (hidden service):
4901 - Make Sybil attacks against hidden services harder by changing the
4902 minimum time required to get the HSDir flag from 25 hours up to 96
4903 hours. Addresses ticket 14149.
4904 - New option "HiddenServiceAllowUnknownPorts" to allow hidden
4905 services to disable the anti-scanning feature introduced in
4906 0.2.6.2-alpha. With this option not set, a connection to an
4907 unlisted port closes the circuit. With this option set, only a
4908 RELAY_DONE cell is sent. Closes ticket 14084.
4909 - When re-enabling the network, don't try to build introduction
4910 circuits until we have successfully built a circuit. This makes
4911 hidden services come up faster when the network is re-enabled.
4912 Patch from "akwizgran". Closes ticket 13447.
4913 - When we fail to retrieve a hidden service descriptor, send the
4914 controller an "HS_DESC FAILED" controller event. Implements
4916 - New HiddenServiceDirGroupReadable option to cause hidden service
4917 directories and hostname files to be created group-readable. Patch
4918 from "anon", David Stainton, and "meejah". Closes ticket 11291.
4920 o Minor features (interface):
4921 - Implement "-f -" command-line option to read torrc configuration
4922 from standard input, if you don't want to store the torrc file in
4923 the file system. Implements feature 13865.
4925 o Minor features (logging):
4926 - Add a count of unique clients to the bridge heartbeat message.
4927 Resolves ticket 6852.
4928 - Suppress "router info incompatible with extra info" message when
4929 reading extrainfo documents from cache. (This message got loud
4930 around when we closed bug 9812 in 0.2.6.2-alpha.) Closes
4932 - Elevate hidden service authorized-client message from DEBUG to
4933 INFO. Closes ticket 14015.
4934 - On Unix-like systems, you can now use named pipes as the target of
4935 the Log option, and other options that try to append to files.
4936 Closes ticket 12061. Patch from "carlo von lynX".
4937 - When opening a log file at startup, send it every log message that
4938 we generated between startup and opening it. Previously, log
4939 messages that were generated before opening the log file were only
4940 logged to stdout. Closes ticket 6938.
4941 - Add a TruncateLogFile option to overwrite logs instead of
4942 appending to them. Closes ticket 5583.
4943 - Quiet some log messages in the heartbeat and at startup. Closes
4946 o Minor features (portability, Solaris):
4947 - Threads are no longer disabled by default on Solaris; we believe
4948 that the versions of Solaris with broken threading support are all
4949 obsolete by now. Resolves ticket 9495.
4951 o Minor features (relay):
4952 - Re-check our address after we detect a changed IP address from
4953 getsockname(). This ensures that the controller command "GETINFO
4954 address" will report the correct value. Resolves ticket 11582.
4956 - A new AccountingRule option lets Relays set whether they'd like
4957 AccountingMax to be applied separately to inbound and outbound
4958 traffic, or applied to the sum of inbound and outbound traffic.
4959 Resolves ticket 961. Patch by "chobe".
4960 - When identity keypair is generated for first time, log a
4961 congratulatory message that links to the new relay lifecycle
4962 document. Implements feature 10427.
4964 o Minor features (security, memory wiping):
4965 - Ensure we securely wipe keys from memory after
4966 crypto_digest_get_digest and init_curve25519_keypair_from_file
4967 have finished using them. Resolves ticket 13477.
4969 o Minor features (security, out-of-memory handling):
4970 - When handling an out-of-memory condition, allocate less memory for
4971 temporary data structures. Fixes issue 10115.
4972 - When handling an out-of-memory condition, consider more types of
4973 buffers, including those on directory connections, and zlib
4974 buffers. Resolves ticket 11792.
4976 o Minor features (stability):
4977 - Add assertions in our hash-table iteration code to check for
4978 corrupted values that could cause infinite loops. Closes
4981 o Minor features (systemd):
4982 - Various improvements and modernizations in systemd hardening
4983 support. Closes ticket 13805. Patch from Craig Andrews.
4984 - Where supported, when running with systemd, report successful
4985 startup to systemd. Part of ticket 11016. Patch by Michael Scherer.
4986 - When running with systemd, support systemd watchdog messages. Part
4987 of ticket 11016. Patch by Michael Scherer.
4989 o Minor features (testing networks):
4990 - Add the TestingDirAuthVoteExit option, which lists nodes to assign
4991 the "Exit" flag regardless of their uptime, bandwidth, or exit
4992 policy. TestingTorNetwork must be set for this option to have any
4993 effect. Previously, authorities would take up to 35 minutes to
4994 give nodes the Exit flag in a test network. Partially implements
4996 - Drop the minimum RendPostPeriod on a testing network to 5 seconds,
4997 and the default on a testing network to 2 minutes. Drop the
4998 MIN_REND_INITIAL_POST_DELAY on a testing network to 5 seconds, but
4999 keep the default on a testing network at 30 seconds. This reduces
5000 HS bootstrap time to around 25 seconds. Also, change the default
5001 time in test-network.sh to match. Closes ticket 13401. Patch
5003 - Create TestingDirAuthVoteHSDir to correspond to
5004 TestingDirAuthVoteExit/Guard. Ensures that authorities vote the
5005 HSDir flag for the listed relays regardless of uptime or ORPort
5006 connectivity. Respects the value of VoteOnHidServDirectoriesV2.
5007 Partial implementation for ticket 14067. Patch by "teor".
5009 o Minor features (tor2web mode):
5010 - Introduce the config option Tor2webRendezvousPoints, which allows
5011 clients in Tor2webMode to select a specific Rendezvous Point to be
5012 used in HS circuits. This might allow better performance for
5013 Tor2Web nodes. Implements ticket 12844.
5015 o Minor features (transparent proxy):
5016 - Update the transparent proxy option checks to allow for both ipfw
5017 and pf on OS X. Closes ticket 14002.
5018 - Use the correct option when using IPv6 with transparent proxy
5019 support on Linux. Resolves 13808. Patch by Francisco Blas
5022 o Minor features (validation):
5023 - Check all date/time values passed to tor_timegm and
5024 parse_rfc1123_time for validity, taking leap years into account.
5025 Improves HTTP header validation. Implemented with bug 13476.
5026 - In correct_tm(), limit the range of values returned by system
5027 localtime(_r) and gmtime(_r) to be between the years 1 and 8099.
5028 This means we don't have to deal with negative or too large dates,
5029 even if a clock is wrong. Otherwise we might fail to read a file
5030 written by us which includes such a date. Fixes bug 13476.
5031 - Stop allowing invalid address patterns like "*/24" that contain
5032 both a wildcard address and a bit prefix length. This affects all
5033 our address-range parsing code. Fixes bug 7484; bugfix
5036 o Minor bugfixes (bridge clients):
5037 - When configured to use a bridge without an identity digest (not
5038 recommended), avoid launching an extra channel to it when
5039 bootstrapping. Fixes bug 7733; bugfix on 0.2.4.4-alpha.
5041 o Minor bugfixes (bridges):
5042 - When DisableNetwork is set, do not launch pluggable transport
5043 plugins, and if any are running, terminate them. Fixes bug 13213;
5044 bugfix on 0.2.3.6-alpha.
5046 o Minor bugfixes (C correctness):
5047 - Fix several instances of possible integer overflow/underflow/NaN.
5048 Fixes bug 13104; bugfix on 0.2.3.1-alpha and later. Patches
5050 - In circuit_build_times_calculate_timeout() in circuitstats.c,
5051 avoid dividing by zero in the pareto calculations. This traps
5052 under clang's "undefined-trap" sanitizer. Fixes bug 13290; bugfix
5054 - Fix an integer overflow in format_time_interval(). Fixes bug
5055 13393; bugfix on 0.2.0.10-alpha.
5056 - Set the correct day of year value when the system's localtime(_r)
5057 or gmtime(_r) functions fail to set struct tm. Not externally
5058 visible. Fixes bug 13476; bugfix on 0.0.2pre14.
5059 - Avoid unlikely signed integer overflow in tor_timegm on systems
5060 with 32-bit time_t. Fixes bug 13476; bugfix on 0.0.2pre14.
5062 o Minor bugfixes (certificate handling):
5063 - If an authority operator accidentally makes a signing certificate
5064 with a future publication time, do not discard its real signing
5065 certificates. Fixes bug 11457; bugfix on 0.2.0.3-alpha.
5066 - Remove any old authority certificates that have been superseded
5067 for at least two days. Previously, we would keep superseded
5068 certificates until they expired, if they were published close in
5069 time to the certificate that superseded them. Fixes bug 11454;
5070 bugfix on 0.2.1.8-alpha.
5072 o Minor bugfixes (client):
5073 - Fix smartlist_choose_node_by_bandwidth() so that relays with the
5074 BadExit flag are not considered worthy candidates. Fixes bug
5075 13066; bugfix on 0.1.2.3-alpha.
5076 - Use the consensus schedule for downloading consensuses, and not
5077 the generic schedule. Fixes bug 11679; bugfix on 0.2.2.6-alpha.
5078 - Handle unsupported or malformed SOCKS5 requests properly by
5079 responding with the appropriate error message before closing the
5080 connection. Fixes bugs 12971 and 13314; bugfix on 0.0.2pre13.
5082 o Minor bugfixes (client, automapping):
5083 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
5084 no value follows the option. Fixes bug 14142; bugfix on
5085 0.2.4.7-alpha. Patch by "teor".
5086 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
5087 14195; bugfix on 0.1.0.1-rc.
5088 - Prevent changes to other options from removing the wildcard value
5089 "." from "AutomapHostsSuffixes". Fixes bug 12509; bugfix
5091 - Allow MapAddress and AutomapHostsOnResolve to work together when
5092 an address is mapped into another address type (like .onion) that
5093 must be automapped at resolve time. Fixes bug 7555; bugfix
5096 o Minor bugfixes (client, bridges):
5097 - When we are using bridges and we had a network connectivity
5098 problem, only retry connecting to our currently configured
5099 bridges, not all bridges we know about and remember using. Fixes
5100 bug 14216; bugfix on 0.2.2.17-alpha.
5102 o Minor bugfixes (client, DNS):
5103 - Report the correct cached DNS expiration times on SOCKS port or in
5104 DNS replies. Previously, we would report everything as "never
5105 expires." Fixes bug 14193; bugfix on 0.2.3.17-beta.
5106 - Avoid a small memory leak when we find a cached answer for a
5107 reverse DNS lookup in a client-side DNS cache. (Remember, client-
5108 side DNS caching is off by default, and is not recommended.) Fixes
5109 bug 14259; bugfix on 0.2.0.1-alpha.
5111 o Minor bugfixes (client, IPv6):
5112 - Reject socks requests to literal IPv6 addresses when IPv6Traffic
5113 flag is not set; and not because the NoIPv4Traffic flag was set.
5114 Previously we'd looked at the NoIPv4Traffic flag for both types of
5115 literal addresses. Fixes bug 14280; bugfix on 0.2.4.7-alpha.
5117 o Minor bugfixes (client, microdescriptors):
5118 - Use a full 256 bits of the SHA256 digest of a microdescriptor when
5119 computing which microdescriptors to download. This keeps us from
5120 erroneous download behavior if two microdescriptor digests ever
5121 have the same first 160 bits. Fixes part of bug 13399; bugfix
5123 - Reset a router's status if its microdescriptor digest changes,
5124 even if the first 160 bits remain the same. Fixes part of bug
5125 13399; bugfix on 0.2.3.1-alpha.
5127 o Minor bugfixes (client, torrc):
5128 - Stop modifying the value of our DirReqStatistics torrc option just
5129 because we're not a bridge or relay. This bug was causing Tor
5130 Browser users to write "DirReqStatistics 0" in their torrc files
5131 as if they had chosen to change the config. Fixes bug 4244; bugfix
5133 - When GeoIPExcludeUnknown is enabled, do not incorrectly decide
5134 that our options have changed every time we SIGHUP. Fixes bug
5135 9801; bugfix on 0.2.4.10-alpha. Patch from "qwerty1".
5137 o Minor bugfixes (compilation):
5138 - Fix a compilation warning on s390. Fixes bug 14988; bugfix
5140 - Silence clang warnings under --enable-expensive-hardening,
5141 including implicit truncation of 64 bit values to 32 bit, const
5142 char assignment to self, tautological compare, and additional
5143 parentheses around equality tests. Fixes bug 13577; bugfix
5145 - Fix a clang warning about checking whether an address in the
5146 middle of a structure is NULL. Fixes bug 14001; bugfix
5148 - The address of an array in the middle of a structure will always
5149 be non-NULL. clang recognises this and complains. Disable the
5150 tautologous and redundant check to silence this warning. Fixes bug
5151 14001; bugfix on 0.2.1.2-alpha.
5152 - Compile correctly with (unreleased) OpenSSL 1.1.0 headers.
5153 Addresses ticket 14188.
5154 - Build without warnings with the stock OpenSSL srtp.h header, which
5155 has a duplicate declaration of SSL_get_selected_srtp_profile().
5156 Fixes bug 14220; this is OpenSSL's bug, not ours.
5157 - Do not compile any code related to Tor2Web mode when Tor2Web mode
5158 is not enabled at compile time. Previously, this code was included
5159 in a disabled state. See discussion on ticket 12844.
5160 - Allow our configure script to build correctly with autoconf 2.62
5161 again. Fixes bug 12693; bugfix on 0.2.5.2-alpha.
5162 - Improve the error message from ./configure to make it clear that
5163 when asciidoc has not been found, the user will have to either add
5164 --disable-asciidoc argument or install asciidoc. Resolves
5167 o Minor bugfixes (controller):
5168 - Report "down" in response to the "GETINFO entry-guards" command
5169 when relays are down with an unreachable_since value. Previously,
5170 we would report "up". Fixes bug 14184; bugfix on 0.1.2.2-alpha.
5171 - Avoid crashing on a malformed EXTENDCIRCUIT command. Fixes bug
5172 14116; bugfix on 0.2.2.9-alpha.
5174 o Minor bugfixes (controller):
5175 - Return an error when the second or later arguments of the
5176 "setevents" controller command are invalid events. Previously we
5177 would return success while silently skipping invalid events. Fixes
5178 bug 13205; bugfix on 0.2.3.2-alpha. Reported by "fpxnns".
5180 o Minor bugfixes (directory authority):
5181 - Allow directory authorities to fetch more data from one another if
5182 they find themselves missing lots of votes. Previously, they had
5183 been bumping against the 10 MB queued data limit. Fixes bug 14261;
5184 bugfix on 0.1.2.5-alpha.
5185 - Do not attempt to download extrainfo documents which we will be
5186 unable to validate with a matching server descriptor. Fixes bug
5187 13762; bugfix on 0.2.0.1-alpha.
5188 - Fix a bug that was truncating AUTHDIR_NEWDESC events sent to the
5189 control port. Fixes bug 14953; bugfix on 0.2.0.1-alpha.
5190 - Enlarge the buffer to read bwauth generated files to avoid an
5191 issue when parsing the file in dirserv_read_measured_bandwidths().
5192 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
5193 - When running as a v3 directory authority, advertise that you serve
5194 extra-info documents so that clients who want them can find them
5195 from you too. Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
5197 o Minor bugfixes (directory system):
5198 - Always believe that v3 directory authorities serve extra-info
5199 documents, whether they advertise "caches-extra-info" or not.
5200 Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
5201 - Check the BRIDGE_DIRINFO flag bitwise rather than using equality.
5202 Previously, directories offering BRIDGE_DIRINFO and some other
5203 flag (i.e. microdescriptors or extrainfo) would be ignored when
5204 looking for bridges. Partially fixes bug 13163; bugfix
5207 o Minor bugfixes (file handling):
5208 - Stop failing when key files are zero-length. Instead, generate new
5209 keys, and overwrite the empty key files. Fixes bug 13111; bugfix
5210 on all versions of Tor. Patch by "teor".
5211 - Stop generating a fresh .old RSA onion key file when the .old file
5212 is missing. Fixes part of 13111; bugfix on 0.0.6rc1.
5213 - Avoid overwriting .old key files with empty key files.
5214 - Skip loading zero-length extrainfo store, router store, stats,
5215 state, and key files.
5216 - Avoid crashing when trying to reload a torrc specified as a
5217 relative path with RunAsDaemon turned on. Fixes bug 13397; bugfix
5220 o Minor bugfixes (hidden services):
5221 - Close the introduction circuit when we have no more usable intro
5222 points, instead of waiting for it to time out. This also ensures
5223 that no follow-up HS descriptor fetch is triggered when the
5224 circuit eventually times out. Fixes bug 14224; bugfix on 0.0.6.
5225 - When fetching a hidden service descriptor for a down service that
5226 was recently up, do not keep refetching until we try the same
5227 replica twice in a row. Fixes bug 14219; bugfix on 0.2.0.10-alpha.
5228 - Correctly send a controller event when we find that a rendezvous
5229 circuit has finished. Fixes bug 13936; bugfix on 0.1.1.5-alpha.
5230 - Pre-check directory permissions for new hidden-services to avoid
5231 at least one case of "Bug: Acting on config options left us in a
5232 broken state. Dying." Fixes bug 13942; bugfix on 0.0.6pre1.
5233 - When fetching hidden service descriptors, we now check not only
5234 for whether we got the hidden service we had in mind, but also
5235 whether we got the particular descriptors we wanted. This prevents
5236 a class of inefficient but annoying DoS attacks by hidden service
5237 directories. Fixes bug 13214; bugfix on 0.2.1.6-alpha. Reported
5240 o Minor bugfixes (Linux seccomp2 sandbox):
5241 - Make transparent proxy support work along with the seccomp2
5242 sandbox. Fixes part of bug 13808; bugfix on 0.2.5.1-alpha. Patch
5243 by Francisco Blas Izquierdo Riera.
5244 - Fix a memory leak in tor-resolve when running with the sandbox
5245 enabled. Fixes bug 14050; bugfix on 0.2.5.9-rc.
5246 - Allow glibc fatal errors to be sent to stderr before Tor exits.
5247 Previously, glibc would try to write them to /dev/tty, and the
5248 sandbox would trap the call and make Tor exit prematurely. Fixes
5249 bug 14759; bugfix on 0.2.5.1-alpha.
5251 o Minor bugfixes (logging):
5252 - Avoid crashing when there are more log domains than entries in
5253 domain_list. Bugfix on 0.2.3.1-alpha.
5254 - Downgrade warnings about RSA signature failures to info log level.
5255 Emit a warning when an extra info document is found incompatible
5256 with a corresponding router descriptor. Fixes bug 9812; bugfix
5258 - Make connection_ap_handshake_attach_circuit() log the circuit ID
5259 correctly. Fixes bug 13701; bugfix on 0.0.6.
5261 o Minor bugfixes (networking):
5262 - Check for orconns and use connection_or_close_for_error() rather
5263 than connection_mark_for_close() directly in the getsockopt()
5264 failure case of connection_handle_write_impl(). Fixes bug 11302;
5265 bugfix on 0.2.4.4-alpha.
5267 o Minor bugfixes (parsing):
5268 - Stop accepting milliseconds (or other junk) at the end of
5269 descriptor publication times. Fixes bug 9286; bugfix on 0.0.2pre25.
5270 - Support two-number and three-number version numbers correctly, in
5271 case we change the Tor versioning system in the future. Fixes bug
5272 13661; bugfix on 0.0.8pre1.
5274 o Minor bugfixes (portability):
5275 - Fix the ioctl()-based network interface lookup code so that it
5276 will work on systems that have variable-length struct ifreq, for
5278 - Use the correct datatype in the SipHash-2-4 function to prevent
5279 compilers from assuming any sort of alignment. Fixes bug 15436;
5280 bugfix on 0.2.5.3-alpha.
5282 o Minor bugfixes (preventative security, C safety):
5283 - When reading a hexadecimal, base-32, or base-64 encoded value from
5284 a string, always overwrite the whole output buffer. This prevents
5285 some bugs where we would look at (but fortunately, not reveal)
5286 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
5288 - Clear all memory targetted by tor_addr_{to,from}_sockaddr(), not
5289 just the part that's used. This makes it harder for data leak bugs
5290 to occur in the event of other programming failures. Resolves
5293 o Minor bugfixes (relay):
5294 - When generating our family list, remove spaces from around the
5295 entries. Fixes bug 12728; bugfix on 0.2.1.7-alpha.
5296 - If our previous bandwidth estimate was 0 bytes, allow publishing a
5297 new relay descriptor immediately. Fixes bug 13000; bugfix
5300 o Minor bugfixes (shutdown):
5301 - When shutting down, always call event_del() on lingering read or
5302 write events before freeing them. Otherwise, we risk double-frees
5303 or read-after-frees in event_base_free(). Fixes bug 12985; bugfix
5306 o Minor bugfixes (small memory leaks):
5307 - Avoid leaking memory when using IPv6 virtual address mappings.
5308 Fixes bug 14123; bugfix on 0.2.4.7-alpha. Patch by Tom van
5311 o Minor bugfixes (statistics):
5312 - Increase period over which bandwidth observations are aggregated
5313 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
5315 o Minor bugfixes (systemd support):
5316 - Run correctly under systemd with the RunAsDaemon option set. Fixes
5317 part of bug 14141; bugfix on 0.2.5.7-rc. Patch from Tomasz Torcz.
5318 - Inform the systemd supervisor about more changes in the Tor
5319 process status. Implements part of ticket 14141. Patch from
5322 o Minor bugfixes (testing networks):
5323 - Fix TestingDirAuthVoteGuard to properly give out Guard flags in a
5324 testing network. Fixes bug 13064; bugfix on 0.2.5.2-alpha.
5325 - Stop using the default authorities in networks which provide both
5326 AlternateDirAuthority and AlternateBridgeAuthority. Partially
5327 fixes bug 13163; bugfix on 0.2.0.13-alpha.
5329 o Minor bugfixes (testing networks, fast startup):
5330 - Allow Tor to build circuits using a consensus with no exits. If
5331 the consensus has no exits (typical of a bootstrapping test
5332 network), allow Tor to build circuits once enough descriptors have
5333 been downloaded. This assists in bootstrapping a testing Tor
5334 network. Fixes bug 13718; bugfix on 0.2.4.10-alpha. Patch
5336 - When V3AuthVotingInterval is low, give a lower If-Modified-Since
5337 header to directory servers. This allows us to obtain consensuses
5338 promptly when the consensus interval is very short. This assists
5339 in bootstrapping a testing Tor network. Fixes parts of bugs 13718
5340 and 13963; bugfix on 0.2.0.3-alpha. Patch by "teor".
5341 - Stop assuming that private addresses are local when checking
5342 reachability in a TestingTorNetwork. Instead, when testing, assume
5343 all OR connections are remote. (This is necessary due to many test
5344 scenarios running all relays on localhost.) This assists in
5345 bootstrapping a testing Tor network. Fixes bug 13924; bugfix on
5346 0.1.0.1-rc. Patch by "teor".
5347 - Avoid building exit circuits from a consensus with no exits. Now
5348 thanks to our fix for 13718, we accept a no-exit network as not
5349 wholly lost, but we need to remember not to try to build exit
5350 circuits on it. Closes ticket 13814; patch by "teor".
5351 - Stop requiring exits to have non-zero bandwithcapacity in a
5352 TestingTorNetwork. Instead, when TestingMinExitFlagThreshold is 0,
5353 ignore exit bandwidthcapacity. This assists in bootstrapping a
5354 testing Tor network. Fixes parts of bugs 13718 and 13839; bugfix
5355 on 0.2.0.3-alpha. Patch by "teor".
5356 - Add "internal" to some bootstrap statuses when no exits are
5357 available. If the consensus does not contain Exits, Tor will only
5358 build internal circuits. In this case, relevant statuses will
5359 contain the word "internal" as indicated in the Tor control-
5360 spec.txt. When bootstrap completes, Tor will be ready to build
5361 internal circuits. If a future consensus contains Exits, exit
5362 circuits may become available. Fixes part of bug 13718; bugfix on
5363 0.2.4.10-alpha. Patch by "teor".
5364 - Decrease minimum consensus interval to 10 seconds when
5365 TestingTorNetwork is set, or 5 seconds for the first consensus.
5366 Fix assumptions throughout the code that assume larger intervals.
5367 Fixes bugs 13718 and 13823; bugfix on 0.2.0.3-alpha. Patch
5369 - Avoid excluding guards from path building in minimal test
5370 networks, when we're in a test network and excluding guards would
5371 exclude all relays. This typically occurs in incredibly small tor
5372 networks, and those using "TestingAuthVoteGuard *". Fixes part of
5373 bug 13718; bugfix on 0.1.1.11-alpha. Patch by "teor".
5375 o Minor bugfixes (testing):
5376 - Avoid a side-effect in a tor_assert() in the unit tests. Fixes bug
5377 15188; bugfix on 0.1.2.3-alpha. Patch from Tom van der Woerdt.
5378 - Stop spawn test failures due to a race condition between the
5379 SIGCHLD handler updating the process status, and the test reading
5380 it. Fixes bug 13291; bugfix on 0.2.3.3-alpha.
5381 - Avoid passing an extra backslash when creating a temporary
5382 directory for running the unit tests on Windows. Fixes bug 12392;
5383 bugfix on 0.2.2.25-alpha. Patch from Gisle Vanem.
5385 o Minor bugfixes (TLS):
5386 - Check more thoroughly throughout the TLS code for possible
5387 unlogged TLS errors. Possible diagnostic or fix for bug 13319.
5389 o Minor bugfixes (transparent proxy):
5390 - Use getsockname, not getsockopt, to retrieve the address for a
5391 TPROXY-redirected connection. Fixes bug 13796; bugfix
5394 o Minor bugfixes (windows):
5395 - Remove code to special-case handling of NTE_BAD_KEYSET when
5396 acquiring windows CryptoAPI context. This error can't actually
5397 occur for the parameters we're providing. Fixes bug 10816; bugfix
5400 o Minor bugfixes (zlib):
5401 - Avoid truncating a zlib stream when trying to finalize it with an
5402 empty output buffer. Fixes bug 11824; bugfix on 0.1.1.23.
5404 o Code simplification and refactoring:
5405 - Change the entry_is_live() function to take named bitfield
5406 elements instead of an unnamed list of booleans. Closes
5408 - Refactor and unit-test entry_is_time_to_retry() in entrynodes.c.
5409 Resolves ticket 12205.
5410 - Use calloc and reallocarray functions instead of multiply-
5411 then-malloc. This makes it less likely for us to fall victim to an
5412 integer overflow attack when allocating. Resolves ticket 12855.
5413 - Use the standard macro name SIZE_MAX, instead of our
5415 - Document usage of the NO_DIRINFO and ALL_DIRINFO flags clearly in
5416 functions which take them as arguments. Replace 0 with NO_DIRINFO
5417 in a function call for clarity. Seeks to prevent future issues
5419 - Avoid 4 null pointer errors under clang static analysis by using
5420 tor_assert() to prove that the pointers aren't null. Fixes
5422 - Rework the API of policies_parse_exit_policy() to use a bitmask to
5423 represent parsing options, instead of a confusing mess of
5424 booleans. Resolves ticket 8197.
5425 - Introduce a helper function to parse ExitPolicy in
5426 or_options_t structure.
5427 - Move fields related to isolating and configuring client ports into
5428 a shared structure. Previously, they were duplicated across
5429 port_cfg_t, listener_connection_t, and edge_connection_t. Failure
5430 to copy them correctly had been the cause of at least one bug in
5431 the past. Closes ticket 8546.
5432 - Refactor the get_interface_addresses_raw() doom-function into
5433 multiple smaller and simpler subfunctions. Cover the resulting
5434 subfunctions with unit-tests. Fixes a significant portion of
5436 - Remove workaround in dirserv_thinks_router_is_hs_dir() that was
5437 only for version <= 0.2.2.24 which is now deprecated. Closes
5439 - Remove a test for a long-defunct broken version-one
5441 - Refactor main loop to extract the 'loop' part. This makes it
5442 easier to run Tor under Shadow. Closes ticket 15176.
5443 - Stop using can_complete_circuits as a global variable; access it
5444 with a function instead.
5445 - Avoid using operators directly as macro arguments: this lets us
5446 apply coccinelle transformations to our codebase more directly.
5447 Closes ticket 13172.
5448 - Combine the functions used to parse ClientTransportPlugin and
5449 ServerTransportPlugin into a single function. Closes ticket 6456.
5450 - Add inline functions and convenience macros for inspecting channel
5451 state. Refactor the code to use convenience macros instead of
5452 checking channel state directly. Fixes issue 7356.
5453 - Document all members of was_router_added_t and rename
5454 ROUTER_WAS_NOT_NEW to ROUTER_IS_ALREADY_KNOWN to make it less
5455 confusable with ROUTER_WAS_TOO_OLD. Fixes issue 13644.
5456 - In connection_exit_begin_conn(), use END_CIRC_REASON_TORPROTOCOL
5457 constant instead of hardcoded value. Fixes issue 13840.
5458 - Refactor our generic strmap and digestmap types into a single
5459 implementation, so that we can add a new digest256map
5463 - Add a doc/TUNING document with tips for handling large numbers of
5464 TCP connections when running busy Tor relay. Update the warning
5465 message to point to this file when running out of sockets
5466 operating system is allowing to use simultaneously. Resolves
5468 - Adding section on OpenBSD to our TUNING document. Thanks to mmcc
5469 for writing the OpenBSD-specific tips. Resolves ticket 13702.
5470 - Make the tor-resolve documentation match its help string and its
5471 options. Resolves part of ticket 14325.
5472 - Log a more useful error message from tor-resolve when failing to
5473 look up a hidden service address. Resolves part of ticket 14325.
5474 - Document the bridge-authority-only 'networkstatus-bridges' file.
5475 Closes ticket 13713; patch from "tom".
5476 - Fix typo in PredictedPortsRelevanceTime option description in
5477 manpage. Resolves issue 13707.
5478 - Stop suggesting that users specify relays by nickname: it isn't a
5479 good idea. Also, properly cross-reference how to specify relays in
5480 all parts of manual documenting options that take a list of
5481 relays. Closes ticket 13381.
5482 - Clarify the HiddenServiceDir option description in manpage to make
5483 it clear that relative paths are taken with respect to the current
5484 working directory. Also clarify that this behavior is not
5485 guaranteed to remain indefinitely. Fixes issue 13913.
5487 o Distribution (systemd):
5488 - systemd unit file: only allow tor to write to /var/lib/tor and
5489 /var/log/tor. The rest of the filesystem is accessible for reading
5490 only. Patch by intrigeri; resolves ticket 12751.
5491 - systemd unit file: ensure that the process and all its children
5492 can never gain new privileges. Patch by intrigeri; resolves
5494 - systemd unit file: set up /var/run/tor as writable for the Tor
5495 service. Patch by intrigeri; resolves ticket 13196.
5497 o Downgraded warnings:
5498 - Don't warn when we've attempted to contact a relay using the wrong
5499 ntor onion key. Closes ticket 9635.
5502 - Remove some lingering dead code that once supported mempools.
5503 Mempools were disabled by default in 0.2.5, and removed entirely
5504 in 0.2.6.3-alpha. Closes more of ticket 14848; patch
5507 o Removed features (directory authorities):
5508 - Remove code that prevented authorities from listing Tor relays
5509 affected by CVE-2011-2769 as guards. These relays are already
5510 rejected altogether due to the minimum version requirement of
5511 0.2.3.16-alpha. Closes ticket 13152.
5512 - The "AuthDirRejectUnlisted" option no longer has any effect, as
5513 the fingerprints file (approved-routers) has been deprecated.
5514 - Directory authorities do not support being Naming dirauths anymore.
5515 The "NamingAuthoritativeDir" config option is now obsolete.
5516 - Directory authorities do not support giving out the BadDirectory
5518 - Directory authorities no longer advertise or support consensus
5519 methods 1 through 12 inclusive. These consensus methods were
5520 obsolete and/or insecure: maintaining the ability to support them
5521 served no good purpose. Implements part of proposal 215; closes
5525 - To avoid confusion with the "ExitRelay" option, "ExitNode" is no
5526 longer silently accepted as an alias for "ExitNodes".
5527 - The --enable-mempool and --enable-buf-freelists options, which
5528 were originally created to work around bad malloc implementations,
5529 no longer exist. They were off-by-default in 0.2.5. Closes
5531 - We no longer remind the user about configuration options that have
5532 been obsolete since 0.2.3.x or earlier. Patch by Adrien Bak.
5533 - Remove our old, non-weighted bandwidth-based node selection code.
5534 Previously, we used it as a fallback when we couldn't perform
5535 weighted bandwidth-based node selection. But that would only
5536 happen in the cases where we had no consensus, or when we had a
5537 consensus generated by buggy or ancient directory authorities. In
5538 either case, it's better to use the more modern, better maintained
5539 algorithm, with reasonable defaults for the weights. Closes
5541 - Remove the --disable-curve25519 configure option. Relays and
5542 clients now are required to support curve25519 and the
5544 - The old "StrictEntryNodes" and "StrictExitNodes" options, which
5545 used to be deprecated synonyms for "StrictNodes", are now marked
5546 obsolete. Resolves ticket 12226.
5547 - Clients don't understand the BadDirectory flag in the consensus
5548 anymore, and ignore it.
5550 o Removed platform support:
5551 - We no longer include special code to build on Windows CE; as far
5552 as we know, nobody has used Tor on Windows CE in a very long time.
5553 Closes ticket 11446.
5555 o Testing (test-network.sh):
5556 - Stop using "echo -n", as some shells' built-in echo doesn't
5557 support "-n". Instead, use "/bin/echo -n". Partially fixes
5559 - Stop an apparent test-network hang when used with make -j2. Fixes
5561 - Add a --delay option to test-network.sh, which configures the
5562 delay before the chutney network tests for data transmission.
5563 Partially implements ticket 13161.
5566 - Test that tor does not fail when key files are zero-length. Check
5567 that tor generates new keys, and overwrites the empty key files.
5568 - Test that tor generates new keys when keys are missing
5569 (existing behavior).
5570 - Test that tor does not overwrite key files that already contain
5571 data (existing behavior). Tests bug 13111. Patch by "teor".
5572 - New "make test-stem" target to run stem integration tests.
5573 Requires that the "STEM_SOURCE_DIR" environment variable be set.
5574 Closes ticket 14107.
5575 - Make the test_cmdline_args.py script work correctly on Windows.
5576 Patch from Gisle Vanem.
5577 - Move the slower unit tests into a new "./src/test/test-slow"
5578 binary that can be run independently of the other tests. Closes
5580 - New tests for many parts of channel, relay, and circuitmux
5581 functionality. Code by Andrea; part of 9262.
5582 - New tests for parse_transport_line(). Part of ticket 6456.
5583 - In the unit tests, use chgrp() to change the group of the unit
5584 test temporary directory to the current user, so that the sticky
5585 bit doesn't interfere with tests that check directory groups.
5587 - Add unit tests for resolve_my_addr(). Part of ticket 12376; patch
5589 - Refactor the function that chooses guard nodes so that it can more
5590 easily be tested; write some tests for it.
5591 - Fix and re-enable the fgets_eagain unit test. Fixes bug 12503;
5592 bugfix on 0.2.3.1-alpha. Patch from "cypherpunks."
5593 - Create unit tests for format_time_interval(). With bug 13393.
5594 - Add unit tests for tor_timegm signed overflow, tor_timegm and
5595 parse_rfc1123_time validity checks, correct_tm year clamping. Unit
5596 tests (visible) fixes in bug 13476.
5597 - Add a "coverage-html" make target to generate HTML-visualized
5598 coverage results when building with --enable-coverage. (Requires
5599 lcov.) Patch from Kevin Murray.
5600 - Enable the backtrace handler (where supported) when running the
5602 - Revise all unit tests that used the legacy test_* macros to
5603 instead use the recommended tt_* macros. This patch was generated
5604 with coccinelle, to avoid manual errors. Closes ticket 13119.
5606 Changes in version 0.2.5.11 - 2015-03-17
5607 Tor 0.2.5.11 is the second stable release in the 0.2.5 series.
5609 It backports several bugfixes from the 0.2.6 branch, including a
5610 couple of medium-level security fixes for relays and exit nodes.
5611 It also updates the list of directory authorities.
5613 o Directory authority changes:
5614 - Remove turtles as a directory authority.
5615 - Add longclaw as a new (v3) directory authority. This implements
5616 ticket 13296. This keeps the directory authority count at 9.
5617 - The directory authority Faravahar has a new IP address. This
5618 closes ticket 14487.
5620 o Major bugfixes (crash, OSX, security):
5621 - Fix a remote denial-of-service opportunity caused by a bug in
5622 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
5625 o Major bugfixes (relay, stability, possible security):
5626 - Fix a bug that could lead to a relay crashing with an assertion
5627 failure if a buffer of exactly the wrong layout was passed to
5628 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
5629 0.2.0.10-alpha. Patch from 'cypherpunks'.
5630 - Do not assert if the 'data' pointer on a buffer is advanced to the
5631 very end of the buffer; log a BUG message instead. Only assert if
5632 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
5634 o Major bugfixes (exit node stability):
5635 - Fix an assertion failure that could occur under high DNS load.
5636 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
5637 diagnosed and fixed by "cypherpunks".
5639 o Major bugfixes (Linux seccomp2 sandbox):
5640 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
5641 crash during attempts to call wait4. Fixes bug 15088; bugfix on
5642 0.2.5.1-alpha. Patch from "sanic".
5644 o Minor features (controller):
5645 - New "GETINFO bw-event-cache" to get information about recent
5646 bandwidth events. Closes ticket 14128. Useful for controllers to
5647 get recent bandwidth history after the fix for ticket 13988.
5649 o Minor features (geoip):
5650 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
5651 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
5654 o Minor bugfixes (client, automapping):
5655 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
5656 no value follows the option. Fixes bug 14142; bugfix on
5657 0.2.4.7-alpha. Patch by "teor".
5658 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
5659 14195; bugfix on 0.1.0.1-rc.
5661 o Minor bugfixes (compilation):
5662 - Build without warnings with the stock OpenSSL srtp.h header, which
5663 has a duplicate declaration of SSL_get_selected_srtp_profile().
5664 Fixes bug 14220; this is OpenSSL's bug, not ours.
5666 o Minor bugfixes (directory authority):
5667 - Allow directory authorities to fetch more data from one another if
5668 they find themselves missing lots of votes. Previously, they had
5669 been bumping against the 10 MB queued data limit. Fixes bug 14261;
5670 bugfix on 0.1.2.5-alpha.
5671 - Enlarge the buffer to read bwauth generated files to avoid an
5672 issue when parsing the file in dirserv_read_measured_bandwidths().
5673 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
5675 o Minor bugfixes (statistics):
5676 - Increase period over which bandwidth observations are aggregated
5677 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
5679 o Minor bugfixes (preventative security, C safety):
5680 - When reading a hexadecimal, base-32, or base-64 encoded value from
5681 a string, always overwrite the whole output buffer. This prevents
5682 some bugs where we would look at (but fortunately, not reveal)
5683 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
5687 Changes in version 0.2.4.26 - 2015-03-17
5688 Tor 0.2.4.26 includes an updated list of directory authorities. It
5689 also backports a couple of stability and security bugfixes from 0.2.5
5692 o Directory authority changes:
5693 - Remove turtles as a directory authority.
5694 - Add longclaw as a new (v3) directory authority. This implements
5695 ticket 13296. This keeps the directory authority count at 9.
5696 - The directory authority Faravahar has a new IP address. This
5697 closes ticket 14487.
5699 o Major bugfixes (exit node stability, also in 0.2.6.3-alpha):
5700 - Fix an assertion failure that could occur under high DNS load.
5701 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
5702 diagnosed and fixed by "cypherpunks".
5704 o Major bugfixes (relay, stability, possible security, also in 0.2.6.4-rc):
5705 - Fix a bug that could lead to a relay crashing with an assertion
5706 failure if a buffer of exactly the wrong layout was passed to
5707 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
5708 0.2.0.10-alpha. Patch from 'cypherpunks'.
5709 - Do not assert if the 'data' pointer on a buffer is advanced to the
5710 very end of the buffer; log a BUG message instead. Only assert if
5711 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
5713 o Minor features (geoip):
5714 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
5715 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
5718 Changes in version 0.2.5.10 - 2014-10-24
5719 Tor 0.2.5.10 is the first stable release in the 0.2.5 series.
5721 It adds several new security features, including improved
5722 denial-of-service resistance for relays, new compiler hardening
5723 options, and a system-call sandbox for hardened installations on Linux
5724 (requires seccomp2). The controller protocol has several new features,
5725 resolving IPv6 addresses should work better than before, and relays
5726 should be a little more CPU-efficient. We've added support for more
5727 OpenBSD and FreeBSD transparent proxy types. We've improved the build
5728 system and testing infrastructure to allow unit testing of more parts
5729 of the Tor codebase. Finally, we've addressed several nagging pluggable
5730 transport usability issues, and included numerous other small bugfixes
5731 and features mentioned below.
5733 This release marks end-of-life for Tor 0.2.3.x; those Tor versions
5734 have accumulated many known flaws; everyone should upgrade.
5736 o Major features (security):
5737 - The ntor handshake is now on-by-default, no matter what the
5738 directory authorities recommend. Implements ticket 8561.
5739 - Make the "tor-gencert" tool used by directory authority operators
5740 create 2048-bit signing keys by default (rather than 1024-bit, since
5741 1024-bit is uncomfortably small these days). Addresses ticket 10324.
5742 - Warn about attempts to run hidden services and relays in the same
5743 process: that's probably not a good idea. Closes ticket 12908.
5744 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
5745 today support TLS 1.0 or later, so we can safely turn off support
5746 for this old (and insecure) protocol. Fixes bug 13426.
5748 o Major features (relay security, DoS-resistance):
5749 - When deciding whether we have run out of memory and we need to
5750 close circuits, also consider memory allocated in buffers for
5751 streams attached to each circuit.
5753 This change, which extends an anti-DoS feature introduced in
5754 0.2.4.13-alpha and improved in 0.2.4.14-alpha, lets Tor exit relays
5755 better resist more memory-based DoS attacks than before. Since the
5756 MaxMemInCellQueues option now applies to all queues, it is renamed
5757 to MaxMemInQueues. This feature fixes bug 10169.
5758 - Avoid hash-flooding denial-of-service attacks by using the secure
5759 SipHash-2-4 hash function for our hashtables. Without this
5760 feature, an attacker could degrade performance of a targeted
5761 client or server by flooding their data structures with a large
5762 number of entries to be stored at the same hash table position,
5763 thereby slowing down the Tor instance. With this feature, hash
5764 table positions are derived from a randomized cryptographic key,
5765 and an attacker cannot predict which entries will collide. Closes
5767 - If you don't specify MaxMemInQueues yourself, Tor now tries to
5768 pick a good value based on your total system memory. Previously,
5769 the default was always 8 GB. You can still override the default by
5770 setting MaxMemInQueues yourself. Resolves ticket 11396.
5772 o Major features (bridges and pluggable transports):
5773 - Add support for passing arguments to managed pluggable transport
5774 proxies. Implements ticket 3594.
5775 - Bridges now track GeoIP information and the number of their users
5776 even when pluggable transports are in use, and report usage
5777 statistics in their extra-info descriptors. Resolves tickets 4773
5779 - Don't launch pluggable transport proxies if we don't have any
5780 bridges configured that would use them. Now we can list many
5781 pluggable transports, and Tor will dynamically start one when it
5782 hears a bridge address that needs it. Resolves ticket 5018.
5783 - The bridge directory authority now assigns status flags (Stable,
5784 Guard, etc) to bridges based on thresholds calculated over all
5785 Running bridges. Now bridgedb can finally make use of its features
5786 to e.g. include at least one Stable bridge in its answers. Fixes
5789 o Major features (controller):
5790 - Extend ORCONN controller event to include an "ID" parameter,
5791 and add four new controller event types CONN_BW, CIRC_BW,
5792 CELL_STATS, and TB_EMPTY that show connection and circuit usage.
5793 The new events are emitted in private Tor networks only, with the
5794 goal of being able to better track performance and load during
5795 full-network simulations. Implements proposal 218 and ticket 7359.
5797 o Major features (relay performance):
5798 - Speed up server-side lookups of rendezvous and introduction point
5799 circuits by using hashtables instead of linear searches. These
5800 functions previously accounted between 3 and 7% of CPU usage on
5801 some busy relays. Resolves ticket 9841.
5802 - Avoid wasting CPU when extending a circuit over a channel that is
5803 nearly out of circuit IDs. Previously, we would do a linear scan
5804 over possible circuit IDs before finding one or deciding that we
5805 had exhausted our possibilities. Now, we try at most 64 random
5806 circuit IDs before deciding that we probably won't succeed. Fixes
5807 a possible root cause of ticket 11553.
5809 o Major features (seccomp2 sandbox, Linux only):
5810 - Use the seccomp2 syscall filtering facility on Linux to limit
5811 which system calls Tor can invoke. This is an experimental,
5812 Linux-only feature to provide defense-in-depth against unknown
5813 attacks. To try turning it on, set "Sandbox 1" in your torrc
5814 file. Please be ready to report bugs. We hope to add support
5815 for better sandboxing in the future, including more fine-grained
5816 filters, better division of responsibility, and support for more
5817 platforms. This work has been done by Cristian-Matei Toader for
5818 Google Summer of Code. Resolves tickets 11351 and 11465.
5820 o Major features (testing networks):
5821 - Make testing Tor networks bootstrap better: lower directory fetch
5822 retry schedules and maximum interval without directory requests,
5823 and raise maximum download tries. Implements ticket 6752.
5824 - Add make target 'test-network' to run tests on a Chutney network.
5825 Implements ticket 8530.
5827 o Major features (other):
5828 - On some platforms (currently: recent OSX versions, glibc-based
5829 platforms that support the ELF format, and a few other
5830 Unix-like operating systems), Tor can now dump stack traces
5831 when a crash occurs or an assertion fails. By default, traces
5832 are dumped to stderr (if possible) and to any logs that are
5833 reporting errors. Implements ticket 9299.
5835 o Deprecated versions:
5836 - Tor 0.2.3.x has reached end-of-life; it has received no patches or
5837 attention for some while.
5839 o Major bugfixes (security, directory authorities):
5840 - Directory authorities now include a digest of each relay's
5841 identity key as a part of its microdescriptor.
5843 This is a workaround for bug 11743 (reported by "cypherpunks"),
5844 where Tor clients do not support receiving multiple
5845 microdescriptors with the same SHA256 digest in the same
5846 consensus. When clients receive a consensus like this, they only
5847 use one of the relays. Without this fix, a hostile relay could
5848 selectively disable some client use of target relays by
5849 constructing a router descriptor with a different identity and the
5850 same microdescriptor parameters and getting the authorities to
5851 list it in a microdescriptor consensus. This fix prevents an
5852 attacker from causing a microdescriptor collision, because the
5853 router's identity is not forgeable.
5855 o Major bugfixes (openssl bug workaround):
5856 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
5857 1.0.1j, built with the 'no-ssl3' configuration option. Fixes
5858 bug 13471. This is a workaround for an OpenSSL bug.
5860 o Major bugfixes (client):
5861 - Perform circuit cleanup operations even when circuit
5862 construction operations are disabled (because the network is
5863 disabled, or because there isn't enough directory information).
5864 Previously, when we were not building predictive circuits, we
5865 were not closing expired circuits either. Fixes bug 8387; bugfix on
5866 0.1.1.11-alpha. This bug became visible in 0.2.4.10-alpha when we
5867 became more strict about when we have "enough directory information
5870 o Major bugfixes (client, pluggable transports):
5871 - When managing pluggable transports, use OS notification facilities
5872 to learn if they have crashed, and don't attempt to kill any
5873 process that has already exited. Fixes bug 8746; bugfix
5876 o Major bugfixes (relay denial of service):
5877 - Instead of writing destroy cells directly to outgoing connection
5878 buffers, queue them and intersperse them with other outgoing cells.
5879 This can prevent a set of resource starvation conditions where too
5880 many pending destroy cells prevent data cells from actually getting
5881 delivered. Reported by "oftc_must_be_destroyed". Fixes bug 7912;
5882 bugfix on 0.2.0.1-alpha.
5884 o Major bugfixes (relay):
5885 - Avoid queuing or sending destroy cells for circuit ID zero when we
5886 fail to send a CREATE cell. Fixes bug 12848; bugfix on 0.0.8pre1.
5887 Found and fixed by "cypherpunks".
5888 - Fix ORPort reachability detection on relays running behind a
5889 proxy, by correctly updating the "local" mark on the controlling
5890 channel when changing the address of an or_connection_t after the
5891 handshake. Fixes bug 12160; bugfix on 0.2.4.4-alpha.
5892 - Use a direct dirport connection when uploading non-anonymous
5893 descriptors to the directory authorities. Previously, relays would
5894 incorrectly use tunnel connections under a fairly wide variety of
5895 circumstances. Fixes bug 11469; bugfix on 0.2.4.3-alpha.
5896 - When a circuit accidentally has the same circuit ID for its
5897 forward and reverse direction, correctly detect the direction of
5898 cells using that circuit. Previously, this bug made roughly one
5899 circuit in a million non-functional. Fixes bug 12195; this is a
5900 bugfix on every version of Tor.
5902 o Minor features (security):
5903 - New --enable-expensive-hardening option to enable security
5904 hardening options that consume nontrivial amounts of CPU and
5905 memory. Right now, this includes AddressSanitizer and UbSan, which
5906 are supported in newer versions of GCC and Clang. Closes ticket
5908 - Authorities now assign the Guard flag to the fastest 25% of the
5909 network (it used to be the fastest 50%). Also raise the consensus
5910 weight that guarantees the Guard flag from 250 to 2000. For the
5911 current network, this results in about 1100 guards, down from 2500.
5912 This step paves the way for moving the number of entry guards
5913 down to 1 (proposal 236) while still providing reasonable expected
5914 performance for most users. Implements ticket 12690.
5916 o Minor features (security, memory management):
5917 - Memory allocation tricks (mempools and buffer freelists) are now
5918 disabled by default. You can turn them back on with
5919 --enable-mempools and --enable-buf-freelists respectively. We're
5920 disabling these features because malloc performance is good enough
5921 on most platforms, and a similar feature in OpenSSL exacerbated
5922 exploitation of the Heartbleed attack. Resolves ticket 11476.
5924 o Minor features (bridge client):
5925 - Report a more useful failure message when we can't connect to a
5926 bridge because we don't have the right pluggable transport
5927 configured. Resolves ticket 9665. Patch from Fábio J. Bertinatto.
5929 o Minor features (bridge):
5930 - Add an ExtORPortCookieAuthFileGroupReadable option to make the
5931 cookie file for the ExtORPort g+r by default.
5933 o Minor features (bridges, pluggable transports):
5934 - Bridges now write the SHA1 digest of their identity key
5935 fingerprint (that is, a hash of a hash of their public key) to
5936 notice-level logs, and to a new hashed-fingerprint file. This
5937 information will help bridge operators look up their bridge in
5938 Globe and similar tools. Resolves ticket 10884.
5939 - Improve the message that Tor displays when running as a bridge
5940 using pluggable transports without an Extended ORPort listener.
5941 Also, log the message in the log file too. Resolves ticket 11043.
5942 - Add threshold cutoffs to the networkstatus document created by
5943 the Bridge Authority. Fixes bug 1117.
5944 - On Windows, spawn background processes using the CREATE_NO_WINDOW
5945 flag. Now Tor Browser Bundle 3.5 with pluggable transports enabled
5946 doesn't pop up a blank console window. (In Tor Browser Bundle 2.x,
5947 Vidalia set this option for us.) Implements ticket 10297.
5949 o Minor features (build):
5950 - The configure script has a --disable-seccomp option to turn off
5951 support for libseccomp on systems that have it, in case it (or
5952 Tor's use of it) is broken. Resolves ticket 11628.
5953 - Assume that a user using ./configure --host wants to cross-compile,
5954 and give an error if we cannot find a properly named
5955 tool-chain. Add a --disable-tool-name-check option to proceed
5956 nevertheless. Addresses ticket 9869. Patch by Benedikt Gollatz.
5957 - If we run ./configure and the compiler recognizes -fstack-protector
5958 but the linker rejects it, warn the user about a potentially missing
5959 libssp package. Addresses ticket 9948. Patch from Benedikt Gollatz.
5960 - Add support for `--library-versions` flag. Implements ticket 6384.
5961 - Return the "unexpected sendme" warnings to a warn severity, but make
5962 them rate limited, to help diagnose ticket 8093.
5963 - Detect a missing asciidoc, and warn the user about it, during
5964 configure rather than at build time. Fixes issue 6506. Patch from
5967 o Minor features (client):
5968 - Add a new option, PredictedPortsRelevanceTime, to control how long
5969 after having received a request to connect to a given port Tor
5970 will try to keep circuits ready in anticipation of future requests
5971 for that port. Patch from "unixninja92"; implements ticket 9176.
5973 o Minor features (config options and command line):
5974 - Add an --allow-missing-torrc commandline option that tells Tor to
5975 run even if the configuration file specified by -f is not available.
5976 Implements ticket 10060.
5977 - Add support for the TPROXY transparent proxying facility on Linux.
5978 See documentation for the new TransProxyType option for more
5979 details. Implementation by "thomo". Closes ticket 10582.
5981 o Minor features (config options):
5982 - Config (torrc) lines now handle fingerprints which are missing
5983 their initial '$'. Resolves ticket 4341; improvement over 0.0.9pre5.
5984 - Support a --dump-config option to print some or all of the
5985 configured options. Mainly useful for debugging the command-line
5986 option parsing code. Helps resolve ticket 4647.
5987 - Raise awareness of safer logging: notify user of potentially
5988 unsafe config options, like logging more verbosely than severity
5989 "notice" or setting SafeLogging to 0. Resolves ticket 5584.
5990 - Add a new configuration option TestingV3AuthVotingStartOffset
5991 that bootstraps a network faster by changing the timing for
5992 consensus votes. Addresses ticket 8532.
5993 - Add a new torrc option "ServerTransportOptions" that allows
5994 bridge operators to pass configuration parameters to their
5995 pluggable transports. Resolves ticket 8929.
5996 - The config (torrc) file now accepts bandwidth and space limits in
5997 bits as well as bytes. (Anywhere that you can say "2 Kilobytes",
5998 you can now say "16 kilobits", and so on.) Resolves ticket 9214.
6001 o Minor features (controller):
6002 - Make the entire exit policy available from the control port via
6003 GETINFO exit-policy/*. Implements enhancement 7952. Patch from
6005 - Because of the fix for ticket 11396, the real limit for memory
6006 usage may no longer match the configured MaxMemInQueues value. The
6007 real limit is now exposed via GETINFO limits/max-mem-in-queues.
6008 - Add a new "HS_DESC" controller event that reports activities
6009 related to hidden service descriptors. Resolves ticket 8510.
6010 - New "DROPGUARDS" controller command to forget all current entry
6011 guards. Not recommended for ordinary use, since replacing guards
6012 too frequently makes several attacks easier. Resolves ticket 9934;
6014 - Implement the TRANSPORT_LAUNCHED control port event that
6015 notifies controllers about new launched pluggable
6016 transports. Resolves ticket 5609.
6018 o Minor features (diagnostic):
6019 - When logging a warning because of bug 7164, additionally check the
6020 hash table for consistency (as proposed on ticket 11737). This may
6021 help diagnose bug 7164.
6022 - When we log a heartbeat, log how many one-hop circuits we have
6023 that are at least 30 minutes old, and log status information about
6024 a few of them. This is an attempt to track down bug 8387.
6025 - When encountering an unexpected CR while writing text to a file on
6026 Windows, log the name of the file. Should help diagnosing
6028 - Give more specific warnings when a client notices that an onion
6029 handshake has failed. Fixes ticket 9635.
6030 - Add significant new logging code to attempt to diagnose bug 12184,
6031 where relays seem to run out of available circuit IDs.
6032 - Improve the diagnostic log message for bug 8387 even further to
6033 try to improve our odds of figuring out why one-hop directory
6034 circuits sometimes do not get closed.
6035 - Add more log messages to diagnose bug 7164, which causes
6036 intermittent "microdesc_free() called but md was still referenced"
6037 warnings. We now include more information, to figure out why we
6038 might be cleaning a microdescriptor for being too old if it's
6039 still referenced by a live node_t object.
6040 - Log current accounting state (bytes sent and received + remaining
6041 time for the current accounting period) in the relay's heartbeat
6042 message. Implements ticket 5526; patch from Peter Retzlaff.
6044 o Minor features (geoip):
6045 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
6048 o Minor features (interface):
6049 - Generate a warning if any ports are listed in the SocksPolicy,
6050 DirPolicy, AuthDirReject, AuthDirInvalid, AuthDirBadDir, or
6051 AuthDirBadExit options. (These options only support address
6052 ranges.) Fixes part of ticket 11108.
6054 o Minor features (kernel API usage):
6055 - Use the SOCK_NONBLOCK socket type, if supported, to open nonblocking
6056 sockets in a single system call. Implements ticket 5129.
6058 o Minor features (log messages):
6059 - When ServerTransportPlugin is set on a bridge, Tor can write more
6060 useful statistics about bridge use in its extrainfo descriptors,
6061 but only if the Extended ORPort ("ExtORPort") is set too. Add a
6062 log message to inform the user in this case. Resolves ticket 9651.
6063 - When receiving a new controller connection, log the origin address.
6064 Resolves ticket 9698; patch from "sigpipe".
6065 - When logging OpenSSL engine status at startup, log the status of
6066 more engines. Fixes ticket 10043; patch from Joshua Datko.
6068 o Minor features (log verbosity):
6069 - Demote the message that we give when a flushing connection times
6070 out for too long from NOTICE to INFO. It was usually meaningless.
6071 Resolves ticket 5286.
6072 - Don't log so many notice-level bootstrapping messages at startup
6073 about downloading descriptors. Previously, we'd log a notice
6074 whenever we learned about more routers. Now, we only log a notice
6075 at every 5% of progress. Fixes bug 9963.
6076 - Warn less verbosely when receiving a malformed
6077 ESTABLISH_RENDEZVOUS cell. Fixes ticket 11279.
6079 o Minor features (performance):
6080 - If we're using the pure-C 32-bit curve25519_donna implementation
6081 of curve25519, build it with the -fomit-frame-pointer option to
6082 make it go faster on register-starved hosts. This improves our
6083 handshake performance by about 6% on i386 hosts without nacl.
6086 o Minor features (relay):
6087 - If a circuit timed out for at least 3 minutes, check if we have a
6088 new external IP address, and publish a new descriptor with the new
6089 IP address if it changed. Resolves ticket 2454.
6091 o Minor features (testing):
6092 - If Python is installed, "make check" now runs extra tests beyond
6093 the unit test scripts.
6094 - When bootstrapping a test network, sometimes very few relays get
6095 the Guard flag. Now a new option "TestingDirAuthVoteGuard" can
6096 specify a set of relays which should be voted Guard regardless of
6097 their uptime or bandwidth. Addresses ticket 9206.
6099 o Minor features (transparent proxy, *BSD):
6100 - Support FreeBSD's ipfw firewall interface for TransPort ports on
6101 FreeBSD. To enable it, set "TransProxyType ipfw". Resolves ticket
6102 10267; patch from "yurivict".
6103 - Support OpenBSD's divert-to rules with the pf firewall for
6104 transparent proxy ports. To enable it, set "TransProxyType
6105 pf-divert". This allows Tor to run a TransPort transparent proxy
6106 port on OpenBSD 4.4 or later without root privileges. See the
6107 pf.conf(5) manual page for information on configuring pf to use
6108 divert-to rules. Closes ticket 10896; patch from Dana Koch.
6110 o Minor bugfixes (bridge client):
6111 - Stop accepting bridge lines containing hostnames. Doing so would
6112 cause clients to perform DNS requests on the hostnames, which was
6113 not sensible behavior. Fixes bug 10801; bugfix on 0.2.0.1-alpha.
6115 o Minor bugfixes (bridges):
6116 - Avoid potential crashes or bad behavior when launching a
6117 server-side managed proxy with ORPort or ExtORPort temporarily
6118 disabled. Fixes bug 9650; bugfix on 0.2.3.16-alpha.
6119 - Fix a bug where the first connection works to a bridge that uses a
6120 pluggable transport with client-side parameters, but we don't send
6121 the client-side parameters on subsequent connections. (We don't
6122 use any pluggable transports with client-side parameters yet,
6123 but ScrambleSuit will soon become the first one.) Fixes bug 9162;
6124 bugfix on 0.2.0.3-alpha. Based on a patch from "rl1987".
6126 o Minor bugfixes (build, auxiliary programs):
6127 - Stop preprocessing the "torify" script with autoconf, since
6128 it no longer refers to LOCALSTATEDIR. Fixes bug 5505; patch
6130 - The tor-fw-helper program now follows the standard convention and
6131 exits with status code "0" on success. Fixes bug 9030; bugfix on
6132 0.2.3.1-alpha. Patch by Arlo Breault.
6133 - Corrected ./configure advice for what openssl dev package you should
6134 install on Debian. Fixes bug 9207; bugfix on 0.2.0.1-alpha.
6136 o Minor bugfixes (client):
6137 - Avoid "Tried to open a socket with DisableNetwork set" warnings
6138 when starting a client with bridges configured and DisableNetwork
6139 set. (Tor launcher starts Tor with DisableNetwork set the first
6140 time it runs.) Fixes bug 10405; bugfix on 0.2.3.9-alpha.
6141 - Improve the log message when we can't connect to a hidden service
6142 because all of the hidden service directory nodes hosting its
6143 descriptor are excluded. Improves on our fix for bug 10722, which
6144 was a bugfix on 0.2.0.10-alpha.
6145 - Raise a control port warning when we fail to connect to all of
6146 our bridges. Previously, we didn't inform the controller, and
6147 the bootstrap process would stall. Fixes bug 11069; bugfix on
6149 - Exit immediately when a process-owning controller exits.
6150 Previously, tor relays would wait for a little while after their
6151 controller exited, as if they had gotten an INT signal -- but this
6152 was problematic, since there was no feedback for the user. To do a
6153 clean shutdown, controllers should send an INT signal and give Tor
6154 a chance to clean up. Fixes bug 10449; bugfix on 0.2.2.28-beta.
6155 - Stop attempting to connect to bridges before our pluggable
6156 transports are configured (harmless but resulted in some erroneous
6157 log messages). Fixes bug 11156; bugfix on 0.2.3.2-alpha.
6158 - Fix connections to IPv6 addresses over SOCKS5. Previously, we were
6159 generating incorrect SOCKS5 responses, and confusing client
6160 applications. Fixes bug 10987; bugfix on 0.2.4.7-alpha.
6162 o Minor bugfixes (client, DNSPort):
6163 - When using DNSPort, try to respond to AAAA requests with AAAA
6164 answers. Previously, we hadn't looked at the request type when
6165 deciding which answer type to prefer. Fixes bug 10468; bugfix on
6167 - When receiving a DNS query for an unsupported record type, reply
6168 with no answer rather than with a NOTIMPL error. This behavior
6169 isn't correct either, but it will break fewer client programs, we
6170 hope. Fixes bug 10268; bugfix on 0.2.0.1-alpha. Original patch
6173 o Minor bugfixes (client, logging during bootstrap):
6174 - Only report the first fatal bootstrap error on a given OR
6175 connection. This stops us from telling the controller bogus error
6176 messages like "DONE". Fixes bug 10431; bugfix on 0.2.1.1-alpha.
6177 - Avoid generating spurious warnings when starting with
6178 DisableNetwork enabled. Fixes bug 11200 and bug 10405; bugfix on
6181 o Minor bugfixes (closing OR connections):
6182 - If write_to_buf() in connection_write_to_buf_impl_() ever fails,
6183 check if it's an or_connection_t and correctly call
6184 connection_or_close_for_error() rather than
6185 connection_mark_for_close() directly. Fixes bug 11304; bugfix on
6187 - When closing all connections on setting DisableNetwork to 1, use
6188 connection_or_close_normally() rather than closing OR connections
6189 out from under the channel layer. Fixes bug 11306; bugfix on
6192 o Minor bugfixes (code correctness):
6193 - Previously we used two temporary files when writing descriptors to
6194 disk; now we only use one. Fixes bug 1376.
6195 - Remove an erroneous (but impossible and thus harmless) pointer
6196 comparison that would have allowed compilers to skip a bounds
6197 check in channeltls.c. Fixes bugs 10313 and 9980; bugfix on
6198 0.2.0.10-alpha. Noticed by Jared L Wong and David Fifield.
6199 - Fix an always-true assertion in pluggable transports code so it
6200 actually checks what it was trying to check. Fixes bug 10046;
6201 bugfix on 0.2.3.9-alpha. Found by "dcb".
6203 o Minor bugfixes (command line):
6204 - Use a single command-line parser for parsing torrc options on the
6205 command line and for finding special command-line options to avoid
6206 inconsistent behavior for torrc option arguments that have the same
6207 names as command-line options. Fixes bugs 4647 and 9578; bugfix on
6209 - No longer allow 'tor --hash-password' with no arguments. Fixes bug
6210 9573; bugfix on 0.0.9pre5.
6212 o Minor bugfixes (compilation):
6213 - Compile correctly with builds and forks of OpenSSL (such as
6214 LibreSSL) that disable compression. Fixes bug 12602; bugfix on
6215 0.2.1.1-alpha. Patch from "dhill".
6216 - Restore the ability to compile Tor with V2_HANDSHAKE_SERVER
6217 turned off (that is, without support for v2 link handshakes). Fixes
6218 bug 4677; bugfix on 0.2.3.2-alpha. Patch from "piet".
6219 - In routerlist_assert_ok(), don't take the address of a
6220 routerinfo's cache_info member unless that routerinfo is non-NULL.
6221 Fixes bug 13096; bugfix on 0.1.1.9-alpha. Patch by "teor".
6222 - Fix a large number of false positive warnings from the clang
6223 analyzer static analysis tool. This should make real warnings
6224 easier for clang analyzer to find. Patch from "teor". Closes
6226 - Resolve GCC complaints on OpenBSD about discarding constness in
6227 TO_{ORIGIN,OR}_CIRCUIT functions. Fixes part of bug 11633; bugfix
6228 on 0.1.1.23. Patch from Dana Koch.
6229 - Resolve clang complaints on OpenBSD with -Wshorten-64-to-32 due to
6230 treatment of long and time_t as comparable types. Fixes part of
6231 bug 11633. Patch from Dana Koch.
6232 - When deciding whether to build the 64-bit curve25519
6233 implementation, detect platforms where we can compile 128-bit
6234 arithmetic but cannot link it. Fixes bug 11729; bugfix on
6235 0.2.4.8-alpha. Patch from "conradev".
6236 - Fix compilation when DNS_CACHE_DEBUG is enabled. Fixes bug 11761;
6237 bugfix on 0.2.3.13-alpha. Found by "cypherpunks".
6238 - Fix compilation with dmalloc. Fixes bug 11605; bugfix
6240 - Build and run correctly on systems like OpenBSD-current that have
6241 patched OpenSSL to remove get_cipher_by_char and/or its
6242 implementations. Fixes issue 13325.
6244 o Minor bugfixes (controller and command-line):
6245 - If changing a config option via "setconf" fails in a recoverable
6246 way, we used to nonetheless write our new control ports to the
6247 file described by the "ControlPortWriteToFile" option. Now we only
6248 write out that file if we successfully switch to the new config
6249 option. Fixes bug 5605; bugfix on 0.2.2.26-beta. Patch from "Ryman".
6251 o Minor bugfixes (directory server):
6252 - No longer accept malformed http headers when parsing urls from
6253 headers. Now we reply with Bad Request ("400"). Fixes bug 2767;
6254 bugfix on 0.0.6pre1.
6255 - When sending a compressed set of descriptors or microdescriptors,
6256 make sure to finalize the zlib stream. Previously, we would write
6257 all the compressed data, but if the last descriptor we wanted to
6258 send was missing or too old, we would not mark the stream as
6259 finished. This caused problems for decompression tools. Fixes bug
6260 11648; bugfix on 0.1.1.23.
6262 o Minor bugfixes (hidden service):
6263 - Only retry attempts to connect to a chosen rendezvous point 8
6264 times, not 30. Fixes bug 4241; bugfix on 0.1.0.1-rc.
6266 o Minor bugfixes (interface):
6267 - Reject relative control socket paths and emit a warning. Previously,
6268 single-component control socket paths would be rejected, but Tor
6269 would not log why it could not validate the config. Fixes bug 9258;
6270 bugfix on 0.2.3.16-alpha.
6272 o Minor bugfixes (log messages):
6273 - Fix a bug where clients using bridges would report themselves
6274 as 50% bootstrapped even without a live consensus document.
6275 Fixes bug 9922; bugfix on 0.2.1.1-alpha.
6276 - Suppress a warning where, if there's only one directory authority
6277 in the network, we would complain that votes and signatures cannot
6278 be uploaded to other directory authorities. Fixes bug 10842;
6279 bugfix on 0.2.2.26-beta.
6280 - Report bootstrapping progress correctly when we're downloading
6281 microdescriptors. We had updated our "do we have enough microdescs
6282 to begin building circuits?" logic most recently in 0.2.4.10-alpha
6283 (see bug 5956), but we left the bootstrap status event logic at
6284 "how far through getting 1/4 of them are we?" Fixes bug 9958;
6285 bugfix on 0.2.2.36, which is where they diverged (see bug 5343).
6287 o Minor bugfixes (logging):
6288 - Downgrade "Unexpected onionskin length after decryption" warning
6289 to a protocol-warn, since there's nothing relay operators can do
6290 about a client that sends them a malformed create cell. Resolves
6291 bug 12996; bugfix on 0.0.6rc1.
6292 - Log more specific warnings when we get an ESTABLISH_RENDEZVOUS
6293 cell on a cannibalized or non-OR circuit. Resolves ticket 12997.
6294 - When logging information about an EXTEND2 or EXTENDED2 cell, log
6295 their names correctly. Fixes part of bug 12700; bugfix
6297 - When logging information about a relay cell whose command we don't
6298 recognize, log its command as an integer. Fixes part of bug 12700;
6299 bugfix on 0.2.1.10-alpha.
6300 - Escape all strings from the directory connection before logging
6301 them. Fixes bug 13071; bugfix on 0.1.1.15. Patch from "teor".
6302 - Squelch a spurious LD_BUG message "No origin circuit for
6303 successful SOCKS stream" in certain hidden service failure cases;
6305 - Downgrade the severity of the 'unexpected sendme cell from client'
6306 from 'warn' to 'protocol warning'. Closes ticket 8093.
6308 o Minor bugfixes (misc code correctness):
6309 - In munge_extrainfo_into_routerinfo(), check the return value of
6310 memchr(). This would have been a serious issue if we ever passed
6311 it a non-extrainfo. Fixes bug 8791; bugfix on 0.2.0.6-alpha. Patch
6313 - On the chance that somebody manages to build Tor on a
6314 platform where time_t is unsigned, correct the way that
6315 microdesc_add_to_cache() handles negative time arguments.
6316 Fixes bug 8042; bugfix on 0.2.3.1-alpha.
6317 - Fix various instances of undefined behavior in channeltls.c,
6318 tor_memmem(), and eventdns.c that would cause us to construct
6319 pointers to memory outside an allocated object. (These invalid
6320 pointers were not accessed, but C does not even allow them to
6321 exist.) Fixes bug 10363; bugfixes on 0.1.1.1-alpha, 0.1.2.1-alpha,
6322 0.2.0.10-alpha, and 0.2.3.6-alpha. Reported by "bobnomnom".
6323 - Use the AddressSanitizer and Ubsan sanitizers (in clang-3.4) to
6324 fix some miscellaneous errors in our tests and codebase. Fixes bug
6325 11232. Bugfixes on versions back as far as 0.2.1.11-alpha.
6326 - Always check return values for unlink, munmap, UnmapViewOfFile;
6327 check strftime return values more often. In some cases all we can
6328 do is report a warning, but this may help prevent deeper bugs from
6329 going unnoticed. Closes ticket 8787; bugfixes on many, many tor
6331 - Fix numerous warnings from the clang "scan-build" static analyzer.
6332 Some of these are programming style issues; some of them are false
6333 positives that indicated awkward code; some are undefined behavior
6334 cases related to constructing (but not using) invalid pointers;
6335 some are assumptions about API behavior; some are (harmlessly)
6336 logging sizeof(ptr) bytes from a token when sizeof(*ptr) would be
6337 correct; and one or two are genuine bugs that weren't reachable
6338 from the rest of the program. Fixes bug 8793; bugfixes on many,
6341 o Minor bugfixes (node selection):
6342 - If ExcludeNodes is set, consider non-excluded hidden service
6343 directory servers before excluded ones. Do not consider excluded
6344 hidden service directory servers at all if StrictNodes is
6345 set. (Previously, we would sometimes decide to connect to those
6346 servers, and then realize before we initiated a connection that
6347 we had excluded them.) Fixes bug 10722; bugfix on 0.2.0.10-alpha.
6349 - If we set the ExitNodes option but it doesn't include any nodes
6350 that have the Exit flag, we would choose not to bootstrap. Now we
6351 bootstrap so long as ExitNodes includes nodes which can exit to
6352 some port. Fixes bug 10543; bugfix on 0.2.4.10-alpha.
6354 o Minor bugfixes (performance):
6355 - Avoid a bug where every successful connection made us recompute
6356 the flag telling us whether we have sufficient information to
6357 build circuits. Previously, we would forget our cached value
6358 whenever we successfully opened a channel (or marked a router as
6359 running or not running for any other reason), regardless of
6360 whether we had previously believed the router to be running. This
6361 forced us to run an expensive update operation far too often.
6362 Fixes bug 12170; bugfix on 0.1.2.1-alpha.
6363 - Avoid using tor_memeq() for checking relay cell integrity. This
6364 removes a possible performance bottleneck. Fixes part of bug
6365 12169; bugfix on 0.2.1.31.
6367 o Minor bugfixes (platform-specific):
6368 - When dumping a malformed directory object to disk, save it in
6369 binary mode on Windows, not text mode. Fixes bug 11342; bugfix on
6371 - Don't report failures from make_socket_reuseable() on incoming
6372 sockets on OSX: this can happen when incoming connections close
6373 early. Fixes bug 10081.
6375 o Minor bugfixes (pluggable transports):
6376 - Avoid another 60-second delay when starting Tor in a pluggable-
6377 transport-using configuration when we already have cached
6378 descriptors for our bridges. Fixes bug 11965; bugfix
6381 o Minor bugfixes (protocol correctness):
6382 - When receiving a VERSIONS cell with an odd number of bytes, close
6383 the connection immediately since the cell is malformed. Fixes bug
6384 10365; bugfix on 0.2.0.10-alpha. Spotted by "bobnomnom"; fix by
6387 o Minor bugfixes (relay, other):
6388 - We now drop CREATE cells for already-existent circuit IDs and for
6389 zero-valued circuit IDs, regardless of other factors that might
6390 otherwise have called for DESTROY cells. Fixes bug 12191; bugfix
6392 - When rejecting DATA cells for stream_id zero, still count them
6393 against the circuit's deliver window so that we don't fail to send
6394 a SENDME. Fixes bug 11246; bugfix on 0.2.4.10-alpha.
6396 o Minor bugfixes (relay, threading):
6397 - Check return code on spawn_func() in cpuworker code, so that we
6398 don't think we've spawned a nonworking cpuworker and write junk to
6399 it forever. Fix related to bug 4345; bugfix on all released Tor
6400 versions. Found by "skruffy".
6401 - Use a pthread_attr to make sure that spawn_func() cannot return an
6402 error while at the same time launching a thread. Fix related to
6403 bug 4345; bugfix on all released Tor versions. Reported
6406 o Minor bugfixes (relays and bridges):
6407 - Avoid crashing on a malformed resolv.conf file when running a
6408 relay using Libevent 1. Fixes bug 8788; bugfix on 0.1.1.23.
6409 - Non-exit relays no longer launch mock DNS requests to check for
6410 DNS hijacking. This has been unnecessary since 0.2.1.7-alpha, when
6411 non-exit relays stopped servicing DNS requests. Fixes bug 965;
6412 bugfix on 0.2.1.7-alpha. Patch from Matt Pagan.
6413 - Bridges now report complete directory request statistics. Related
6414 to bug 5824; bugfix on 0.2.2.1-alpha.
6415 - Bridges now never collect statistics that were designed for
6416 relays. Fixes bug 5824; bugfix on 0.2.3.8-alpha.
6418 o Minor bugfixes (testing):
6419 - Fix all valgrind warnings produced by the unit tests. There were
6420 over a thousand memory leak warnings previously, mostly produced
6421 by forgetting to free things in the unit test code. Fixes bug
6422 11618, bugfixes on many versions of Tor.
6424 o Minor bugfixes (tor-fw-helper):
6425 - Give a correct log message when tor-fw-helper fails to launch.
6426 (Previously, we would say something like "tor-fw-helper sent us a
6427 string we could not parse".) Fixes bug 9781; bugfix
6430 o Minor bugfixes (trivial memory leaks):
6431 - Fix a small memory leak when signing a directory object. Fixes bug
6432 11275; bugfix on 0.2.4.13-alpha.
6433 - Resolve some memory leaks found by coverity in the unit tests, on
6434 exit in tor-gencert, and on a failure to compute digests for our
6435 own keys when generating a v3 networkstatus vote. These leaks
6436 should never have affected anyone in practice.
6438 o Code simplification and refactoring:
6439 - Remove some old fallback code designed to keep Tor clients working
6440 in a network with only two working relays. Elsewhere in the code we
6441 have long since stopped supporting such networks, so there wasn't
6442 much point in keeping it around. Addresses ticket 9926.
6443 - Reject 0-length EXTEND2 cells more explicitly. Fixes bug 10536;
6444 bugfix on 0.2.4.8-alpha. Reported by "cypherpunks".
6445 - Extract the common duplicated code for creating a subdirectory
6446 of the data directory and writing to a file in it. Fixes ticket
6447 4282; patch from Peter Retzlaff.
6448 - Since OpenSSL 0.9.7, the i2d_*() functions support allocating output
6449 buffer. Avoid calling twice: i2d_RSAPublicKey(), i2d_DHparams(),
6450 i2d_X509(), and i2d_PublicKey(). Resolves ticket 5170.
6451 - Add a set of accessor functions for the circuit timeout data
6452 structure. Fixes ticket 6153; patch from "piet".
6453 - Clean up exit paths from connection_listener_new(). Closes ticket
6454 8789. Patch from Arlo Breault.
6455 - Since we rely on OpenSSL 0.9.8 now, we can use EVP_PKEY_cmp()
6456 and drop our own custom pkey_eq() implementation. Fixes bug 9043.
6457 - Use a doubly-linked list to implement the global circuit list.
6458 Resolves ticket 9108. Patch from Marek Majkowski.
6459 - Remove contrib/id_to_fp.c since it wasn't used anywhere.
6460 - Remove constants and tests for PKCS1 padding; it's insecure and
6461 shouldn't be used for anything new. Fixes bug 8792; patch
6463 - Remove instances of strcpy() from the unit tests. They weren't
6464 hurting anything, since they were only in the unit tests, but it's
6465 embarassing to have strcpy() in the code at all, and some analysis
6466 tools don't like it. Fixes bug 8790; bugfix on 0.2.3.6-alpha and
6467 0.2.3.8-alpha. Patch from Arlo Breault.
6468 - Remove is_internal_IP() function. Resolves ticket 4645.
6469 - Remove unused function circuit_dump_by_chan from circuitlist.c.
6470 Closes issue 9107; patch from "marek".
6471 - Change our use of the ENUM_BF macro to avoid declarations that
6473 - Get rid of router->address, since in all cases it was just the
6474 string representation of router->addr. Resolves ticket 5528.
6477 - Adjust the URLs in the README to refer to the new locations of
6478 several documents on the website. Fixes bug 12830. Patch from
6480 - Document 'reject6' and 'accept6' ExitPolicy entries. Resolves
6482 - Update manpage to describe some of the files you can expect to
6483 find in Tor's DataDirectory. Addresses ticket 9839.
6484 - Clean up several option names in the manpage to match their real
6485 names, add the missing documentation for a couple of testing and
6486 directory authority options, remove the documentation for a
6487 V2-directory fetching option that no longer exists. Resolves
6489 - Correct the documenation so that it lists the correct directory
6490 for the stats files. (They are in a subdirectory called "stats",
6492 - In the manpage, move more authority-only options into the
6493 directory authority section so that operators of regular directory
6494 caches don't get confused.
6495 - Fix the layout of the SOCKSPort flags in the manpage. Fixes bug
6496 11061; bugfix on 0.2.4.7-alpha.
6497 - Resolve warnings from Doxygen.
6498 - Document in the manpage that "KBytes" may also be written as
6499 "kilobytes" or "KB", that "Kbits" may also be written as
6500 "kilobits", and so forth. Closes ticket 9222.
6501 - Document that the ClientOnly config option overrides ORPort.
6502 Our old explanation made ClientOnly sound as though it did
6503 nothing at all. Resolves bug 9059.
6504 - Explain that SocksPolicy, DirPolicy, and similar options don't
6505 take port arguments. Fixes the other part of ticket 11108.
6506 - Fix a comment about the rend_server_descriptor_t.protocols field
6507 to more accurately describe its range. Also, make that field
6508 unsigned, to more accurately reflect its usage. Fixes bug 9099;
6509 bugfix on 0.2.1.5-alpha.
6510 - Fix the manpage's description of HiddenServiceAuthorizeClient:
6511 the maximum client name length is 16, not 19. Fixes bug 11118;
6512 bugfix on 0.2.1.6-alpha.
6515 - The contrib directory has been sorted and tidied. Before, it was
6516 an unsorted dumping ground for useful and not-so-useful things.
6517 Now, it is divided based on functionality, and the items which
6518 seemed to be nonfunctional or useless have been removed. Resolves
6519 ticket 8966; based on patches from "rl1987".
6521 o Removed code and features:
6522 - Clients now reject any directory authority certificates lacking
6523 a dir-key-crosscert element. These have been included since
6524 0.2.1.9-alpha, so there's no real reason for them to be optional
6525 any longer. Completes proposal 157. Resolves ticket 10162.
6526 - Remove all code that existed to support the v2 directory system,
6527 since there are no longer any v2 directory authorities. Resolves
6529 - Remove the HSAuthoritativeDir and AlternateHSAuthority torrc
6530 options, which were used for designating authorities as "Hidden
6531 service authorities". There has been no use of hidden service
6532 authorities since 0.2.2.1-alpha, when we stopped uploading or
6533 downloading v0 hidden service descriptors. Fixes bug 10881; also
6534 part of a fix for bug 10841.
6535 - Remove /tor/dbg-stability.txt URL that was meant to help debug WFU
6536 and MTBF calculations, but that nobody was using. Fixes bug 11742.
6537 - The TunnelDirConns and PreferTunnelledDirConns options no longer
6538 exist; tunneled directory connections have been available since
6539 0.1.2.5-alpha, and turning them off is not a good idea. This is a
6540 brute-force fix for 10849, where "TunnelDirConns 0" would break
6542 - Remove all code for the long unused v1 directory protocol.
6543 Resolves ticket 11070.
6544 - Remove all remaining code related to version-0 hidden service
6545 descriptors: they have not been in use since 0.2.2.1-alpha. Fixes
6546 the rest of bug 10841.
6547 - Remove migration code from when we renamed the "cached-routers"
6548 file to "cached-descriptors" back in 0.2.0.8-alpha. This
6549 incidentally resolves ticket 6502 by cleaning up the related code
6550 a bit. Patch from Akshay Hebbar.
6552 o Test infrastructure:
6553 - Tor now builds each source file in two modes: a mode that avoids
6554 exposing identifiers needlessly, and another mode that exposes
6555 more identifiers for testing. This lets the compiler do better at
6556 optimizing the production code, while enabling us to take more
6557 radical measures to let the unit tests test things.
6558 - The production builds no longer include functions used only in
6559 the unit tests; all functions exposed from a module only for
6560 unit-testing are now static in production builds.
6561 - Add an --enable-coverage configuration option to make the unit
6562 tests (and a new src/or/tor-cov target) to build with gcov test
6564 - Update to the latest version of tinytest.
6565 - Improve the tinytest implementation of string operation tests so
6566 that comparisons with NULL strings no longer crash the tests; they
6567 now just fail, normally. Fixes bug 9004; bugfix on 0.2.2.4-alpha.
6568 - New macros in test.h to simplify writing mock-functions for unit
6569 tests. Part of ticket 11507. Patch from Dana Koch.
6570 - We now have rudimentary function mocking support that our unit
6571 tests can use to test functions in isolation. Function mocking
6572 lets the tests temporarily replace a function's dependencies with
6573 stub functions, so that the tests can check the function without
6574 invoking the other functions it calls.
6577 - Complete tests for the status.c module. Resolves ticket 11507.
6578 Patch from Dana Koch.
6579 - Add more unit tests for the <circid,channel>->circuit map, and
6580 the destroy-cell-tracking code to fix bug 7912.
6581 - Unit tests for failing cases of the TAP onion handshake.
6582 - More unit tests for address-manipulation functions.
6584 o Distribution (systemd):
6585 - Include a tor.service file in contrib/dist for use with systemd.
6586 Some distributions will be able to use this file unmodified;
6587 others will need to tweak it, or write their own. Patch from Jamie
6588 Nguyen; resolves ticket 8368.
6589 - Verify configuration file via ExecStartPre in the systemd unit
6590 file. Patch from intrigeri; resolves ticket 12730.
6591 - Explicitly disable RunAsDaemon in the systemd unit file. Our
6592 current systemd unit uses "Type = simple", so systemd does not
6593 expect tor to fork. If the user has "RunAsDaemon 1" in their
6594 torrc, then things won't work as expected. This is e.g. the case
6595 on Debian (and derivatives), since there we pass "--defaults-torrc
6596 /usr/share/tor/tor-service-defaults-torrc" (that contains
6597 "RunAsDaemon 1") by default. Patch by intrigeri; resolves
6601 Changes in version 0.2.4.25 - 2014-10-20
6602 Tor 0.2.4.25 disables SSL3 in response to the recent "POODLE" attack
6603 (even though POODLE does not affect Tor). It also works around a crash
6604 bug caused by some operating systems' response to the "POODLE" attack
6605 (which does affect Tor).
6607 o Major security fixes (also in 0.2.5.9-rc):
6608 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
6609 today support TLS 1.0 or later, so we can safely turn off support
6610 for this old (and insecure) protocol. Fixes bug 13426.
6612 o Major bugfixes (openssl bug workaround, also in 0.2.5.9-rc):
6613 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
6614 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
6615 13471. This is a workaround for an OpenSSL bug.
6618 Changes in version 0.2.4.24 - 2014-09-22
6619 Tor 0.2.4.24 fixes a bug that affects consistency and speed when
6620 connecting to hidden services, and it updates the location of one of
6621 the directory authorities.
6624 - Clients now send the correct address for their chosen rendezvous
6625 point when trying to access a hidden service. They used to send
6626 the wrong address, which would still work some of the time because
6627 they also sent the identity digest of the rendezvous point, and if
6628 the hidden service happened to try connecting to the rendezvous
6629 point from a relay that already had a connection open to it,
6630 the relay would reuse that connection. Now connections to hidden
6631 services should be more robust and faster. Also, this bug meant
6632 that clients were leaking to the hidden service whether they were
6633 on a little-endian (common) or big-endian (rare) system, which for
6634 some users might have reduced their anonymity. Fixes bug 13151;
6635 bugfix on 0.2.1.5-alpha.
6637 o Directory authority changes:
6638 - Change IP address for gabelmoo (v3 directory authority).
6640 o Minor features (geoip):
6641 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
6645 Changes in version 0.2.4.23 - 2014-07-28
6646 Tor 0.2.4.23 brings us a big step closer to slowing down the risk from
6647 guard rotation, and also backports several important fixes from the
6648 Tor 0.2.5 alpha release series.
6651 - Clients now look at the "usecreatefast" consensus parameter to
6652 decide whether to use CREATE_FAST or CREATE cells for the first hop
6653 of their circuit. This approach can improve security on connections
6654 where Tor's circuit handshake is stronger than the available TLS
6655 connection security levels, but the tradeoff is more computational
6656 load on guard relays. Implements proposal 221. Resolves ticket 9386.
6657 - Make the number of entry guards configurable via a new
6658 NumEntryGuards consensus parameter, and the number of directory
6659 guards configurable via a new NumDirectoryGuards consensus
6660 parameter. Implements ticket 12688.
6663 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
6664 implementation that caused incorrect results on 32-bit
6665 implementations when certain malformed inputs were used along with
6666 a small class of private ntor keys. This bug does not currently
6667 appear to allow an attacker to learn private keys or impersonate a
6668 Tor server, but it could provide a means to distinguish 32-bit Tor
6669 implementations from 64-bit Tor implementations. Fixes bug 12694;
6670 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
6674 - Warn and drop the circuit if we receive an inbound 'relay early'
6675 cell. Those used to be normal to receive on hidden service circuits
6676 due to bug 1038, but the buggy Tor versions are long gone from
6677 the network so we can afford to resume watching for them. Resolves
6678 the rest of bug 1038; bugfix on 0.2.1.19.
6679 - Correct a confusing error message when trying to extend a circuit
6680 via the control protocol but we don't know a descriptor or
6681 microdescriptor for one of the specified relays. Fixes bug 12718;
6682 bugfix on 0.2.3.1-alpha.
6683 - Avoid an illegal read from stack when initializing the TLS
6684 module using a version of OpenSSL without all of the ciphers
6685 used by the v2 link handshake. Fixes bug 12227; bugfix on
6686 0.2.4.8-alpha. Found by "starlight".
6689 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
6693 Changes in version 0.2.4.22 - 2014-05-16
6694 Tor 0.2.4.22 backports numerous high-priority fixes from the Tor 0.2.5
6695 alpha release series. These include blocking all authority signing
6696 keys that may have been affected by the OpenSSL "heartbleed" bug,
6697 choosing a far more secure set of TLS ciphersuites by default, closing
6698 a couple of memory leaks that could be used to run a target relay out
6699 of RAM, and several others.
6701 o Major features (security, backport from 0.2.5.4-alpha):
6702 - Block authority signing keys that were used on authorities
6703 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
6704 don't have any evidence that these keys _were_ compromised; we're
6705 doing this to be prudent.) Resolves ticket 11464.
6707 o Major bugfixes (security, OOM):
6708 - Fix a memory leak that could occur if a microdescriptor parse
6709 fails during the tokenizing step. This bug could enable a memory
6710 exhaustion attack by directory servers. Fixes bug 11649; bugfix
6713 o Major bugfixes (TLS cipher selection, backport from 0.2.5.4-alpha):
6714 - The relay ciphersuite list is now generated automatically based on
6715 uniform criteria, and includes all OpenSSL ciphersuites with
6716 acceptable strength and forward secrecy. Previously, we had left
6717 some perfectly fine ciphersuites unsupported due to omission or
6718 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
6719 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
6720 - Relays now trust themselves to have a better view than clients of
6721 which TLS ciphersuites are better than others. (Thanks to bug
6722 11513, the relay list is now well-considered, whereas the client
6723 list has been chosen mainly for anti-fingerprinting purposes.)
6724 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
6725 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
6726 AES128. Resolves ticket 11528.
6727 - Clients now try to advertise the same list of ciphersuites as
6728 Firefox 28. This change enables selection of (fast) GCM
6729 ciphersuites, disables some strange old ciphers, and stops
6730 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
6731 Resolves ticket 11438.
6733 o Minor bugfixes (configuration, security):
6734 - When running a hidden service, do not allow TunneledDirConns 0:
6735 trying to set that option together with a hidden service would
6736 otherwise prevent the hidden service from running, and also make
6737 it publish its descriptors directly over HTTP. Fixes bug 10849;
6738 bugfix on 0.2.1.1-alpha.
6740 o Minor bugfixes (controller, backport from 0.2.5.4-alpha):
6741 - Avoid sending a garbage value to the controller when a circuit is
6742 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
6744 o Minor bugfixes (exit relay, backport from 0.2.5.4-alpha):
6745 - Stop leaking memory when we successfully resolve a PTR record.
6746 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
6748 o Minor bugfixes (bridge client, backport from 0.2.5.4-alpha):
6749 - Avoid 60-second delays in the bootstrapping process when Tor is
6750 launching for a second time while using bridges. Fixes bug 9229;
6751 bugfix on 0.2.0.3-alpha.
6753 o Minor bugfixes (relays and bridges, backport from 0.2.5.4-alpha):
6754 - Give the correct URL in the warning message when trying to run a
6755 relay on an ancient version of Windows. Fixes bug 9393.
6757 o Minor bugfixes (compilation):
6758 - Fix a compilation error when compiling with --disable-curve25519.
6759 Fixes bug 9700; bugfix on 0.2.4.17-rc.
6762 - Downgrade the warning severity for the the "md was still
6763 referenced 1 node(s)" warning. Tor 0.2.5.4-alpha has better code
6764 for trying to diagnose this bug, and the current warning in
6765 earlier versions of tor achieves nothing useful. Addresses warning
6768 o Minor features (log verbosity, backport from 0.2.5.4-alpha):
6769 - When we run out of usable circuit IDs on a channel, log only one
6770 warning for the whole channel, and describe how many circuits
6771 there were on the channel. Fixes part of ticket 11553.
6773 o Minor features (security, backport from 0.2.5.4-alpha):
6774 - Decrease the lower limit of MaxMemInCellQueues to 256 MBytes (but
6775 leave the default at 8GBytes), to better support Raspberry Pi
6776 users. Fixes bug 9686; bugfix on 0.2.4.14-alpha.
6778 o Documentation (backport from 0.2.5.4-alpha):
6779 - Correctly document that we search for a system torrc file before
6780 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
6784 Changes in version 0.2.4.21 - 2014-02-28
6785 Tor 0.2.4.21 further improves security against potential adversaries who
6786 find breaking 1024-bit crypto doable, and backports several stability
6787 and robustness patches from the 0.2.5 branch.
6789 o Major features (client security):
6790 - When we choose a path for a 3-hop circuit, make sure it contains
6791 at least one relay that supports the NTor circuit extension
6792 handshake. Otherwise, there is a chance that we're building
6793 a circuit that's worth attacking by an adversary who finds
6794 breaking 1024-bit crypto doable, and that chance changes the game
6795 theory. Implements ticket 9777.
6798 - Do not treat streams that fail with reason
6799 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
6800 since it could also indicate an ENETUNREACH connection error. Fixes
6801 part of bug 10777; bugfix on 0.2.4.8-alpha.
6803 o Code simplification and refactoring:
6804 - Remove data structures which were introduced to implement the
6805 CellStatistics option: they are now redundant with the new timestamp
6806 field in the regular packed_cell_t data structure, which we did
6807 in 0.2.4.18-rc in order to resolve bug 9093. Resolves ticket 10870.
6810 - Always clear OpenSSL bignums before freeing them -- even bignums
6811 that don't contain secrets. Resolves ticket 10793. Patch by
6813 - Build without warnings under clang 3.4. (We have some macros that
6814 define static functions only some of which will get used later in
6815 the module. Starting with clang 3.4, these give a warning unless the
6816 unused attribute is set on them.) Resolves ticket 10904.
6817 - Update geoip and geoip6 files to the February 7 2014 Maxmind
6818 GeoLite2 Country database.
6821 - Set the listen() backlog limit to the largest actually supported
6822 on the system, not to the value in a header file. Fixes bug 9716;
6823 bugfix on every released Tor.
6824 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
6825 exit node as a NOROUTE error, not an INTERNAL error, since they
6826 can apparently happen when trying to connect to the wrong sort
6827 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
6828 - Fix build warnings about missing "a2x" comment when building the
6829 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
6830 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
6831 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
6832 not entirely remove it from the connection lists. Fixes bug 9602;
6833 bugfix on 0.2.4.4-alpha.
6834 - Fix a segmentation fault in our benchmark code when running with
6835 Fedora's OpenSSL package, or any other OpenSSL that provides
6836 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
6837 - Turn "circuit handshake stats since last time" log messages into a
6838 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
6840 o Documentation fixes:
6841 - Document that all but one DirPort entry must have the NoAdvertise
6842 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
6845 Changes in version 0.2.4.20 - 2013-12-22
6846 Tor 0.2.4.20 fixes potentially poor random number generation for users
6847 who 1) use OpenSSL 1.0.0 or later, 2) set "HardwareAccel 1" in their
6848 torrc file, 3) have "Sandy Bridge" or "Ivy Bridge" Intel processors,
6849 and 4) have no state file in their DataDirectory (as would happen on
6850 first start). Users who generated relay or hidden service identity
6851 keys in such a situation should discard them and generate new ones.
6853 This release also fixes a logic error that caused Tor clients to build
6854 many more preemptive circuits than they actually need.
6857 - Do not allow OpenSSL engines to replace the PRNG, even when
6858 HardwareAccel is set. The only default builtin PRNG engine uses
6859 the Intel RDRAND instruction to replace the entire PRNG, and
6860 ignores all attempts to seed it with more entropy. That's
6861 cryptographically stupid: the right response to a new alleged
6862 entropy source is never to discard all previously used entropy
6863 sources. Fixes bug 10402; works around behavior introduced in
6864 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
6866 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
6867 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
6868 - Avoid launching spurious extra circuits when a stream is pending.
6869 This fixes a bug where any circuit that _wasn't_ unusable for new
6870 streams would be treated as if it were, causing extra circuits to
6871 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
6874 - Avoid a crash bug when starting with a corrupted microdescriptor
6875 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
6876 - If we fail to dump a previously cached microdescriptor to disk, avoid
6877 freeing duplicate data later on. Fixes bug 10423; bugfix on
6878 0.2.4.13-alpha. Spotted by "bobnomnom".
6881 Changes in version 0.2.4.19 - 2013-12-11
6882 The Tor 0.2.4 release series is dedicated to the memory of Aaron Swartz
6883 (1986-2013). Aaron worked on diverse projects including helping to guide
6884 Creative Commons, playing a key role in stopping SOPA/PIPA, bringing
6885 transparency to the U.S government's PACER documents, and contributing
6886 design and development for Tor and Tor2Web. Aaron was one of the latest
6887 martyrs in our collective fight for civil liberties and human rights,
6888 and his death is all the more painful because he was one of us.
6890 Tor 0.2.4.19, the first stable release in the 0.2.4 branch, features
6891 a new circuit handshake and link encryption that use ECC to provide
6892 better security and efficiency; makes relays better manage circuit
6893 creation requests; uses "directory guards" to reduce client enumeration
6894 risks; makes bridges collect and report statistics about the pluggable
6895 transports they support; cleans up and improves our geoip database;
6896 gets much closer to IPv6 support for clients, bridges, and relays; makes
6897 directory authorities use measured bandwidths rather than advertised
6898 ones when computing flags and thresholds; disables client-side DNS
6899 caching to reduce tracking risks; and fixes a big bug in bridge
6900 reachability testing. This release introduces two new design
6901 abstractions in the code: a new "channel" abstraction between circuits
6902 and or_connections to allow for implementing alternate relay-to-relay
6903 transports, and a new "circuitmux" abstraction storing the queue of
6904 circuits for a channel. The release also includes many stability,
6905 security, and privacy fixes.
6907 o Major features (new circuit handshake):
6908 - Tor now supports a new circuit extension handshake designed by Ian
6909 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
6910 circuit extension handshake, later called "TAP", was a bit slow
6911 (especially on the relay side), had a fragile security proof, and
6912 used weaker keys than we'd now prefer. The new circuit handshake
6913 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
6914 function, making it significantly more secure than the older
6915 handshake, and significantly faster. Tor can use one of two built-in
6916 pure-C curve25519-donna implementations by Adam Langley, or it
6917 can link against the "nacl" library for a tuned version if present.
6919 The built-in version is very fast for 64-bit systems when building
6920 with GCC. The built-in 32-bit version is still faster than the
6921 old TAP protocol, but using libnacl is better on most such hosts.
6923 Implements proposal 216; closes ticket 7202.
6925 o Major features (better link encryption):
6926 - Relays can now enable the ECDHE TLS ciphersuites when available
6927 and appropriate. These ciphersuites let us negotiate forward-secure
6928 TLS secret keys more safely and more efficiently than with our
6929 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
6930 public relays prefer the (faster) P224 group, and bridges prefer
6931 the (more common) P256 group; you can override this with the
6934 This feature requires clients running 0.2.3.17-beta or later,
6935 and requires both sides to be running OpenSSL 1.0.0 or later
6936 with ECC support. OpenSSL 1.0.1, with the compile-time option
6937 "enable-ec_nistp_64_gcc_128", is highly recommended.
6939 Implements the relay side of proposal 198; closes ticket 7200.
6941 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
6942 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
6943 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
6944 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
6945 them to solve bug 6033.)
6947 o Major features (relay performance):
6948 - Instead of limiting the number of queued onionskins (aka circuit
6949 create requests) to a fixed, hard-to-configure number, we limit
6950 the size of the queue based on how many we expect to be able to
6951 process in a given amount of time. We estimate the time it will
6952 take to process an onionskin based on average processing time
6953 of previous onionskins. Closes ticket 7291. You'll never have to
6954 configure MaxOnionsPending again.
6955 - Relays process the new "NTor" circuit-level handshake requests
6956 with higher priority than the old "TAP" circuit-level handshake
6957 requests. We still process some TAP requests to not totally starve
6958 0.2.3 clients when NTor becomes popular. A new consensus parameter
6959 "NumNTorsPerTAP" lets us tune the balance later if we need to.
6960 Implements ticket 9574.
6962 o Major features (client bootstrapping resilience):
6963 - Add a new "FallbackDir" torrc option to use when we can't use
6964 a directory mirror from the consensus (either because we lack a
6965 consensus, or because they're all down). Currently, all authorities
6966 are fallbacks by default, and there are no other default fallbacks,
6967 but that will change. This option will allow us to give clients a
6968 longer list of servers to try to get a consensus from when first
6969 connecting to the Tor network, and thereby reduce load on the
6970 directory authorities. Implements proposal 206, "Preconfigured
6971 directory sources for bootstrapping". We also removed the old
6972 "FallbackNetworkstatus" option, since we never got it working well
6973 enough to use it. Closes bug 572.
6974 - If we have no circuits open, use a relaxed timeout (the
6975 95th-percentile cutoff) until a circuit succeeds. This heuristic
6976 should allow Tor to succeed at building circuits even when the
6977 network connection drastically changes. Should help with bug 3443.
6979 o Major features (use of guards):
6980 - Support directory guards (proposal 207): when possible, clients now
6981 use their entry guards for non-anonymous directory requests. This
6982 can help prevent client enumeration. Note that this behavior only
6983 works when we have a usable consensus directory, and when options
6984 about what to download are more or less standard. In the future we
6985 should re-bootstrap from our guards, rather than re-bootstrapping
6986 from the preconfigured list of directory sources that ships with
6987 Tor. Resolves ticket 6526.
6988 - Raise the default time that a client keeps an entry guard from
6989 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
6990 2012 paper. (We would make it even longer, but we need better client
6991 load balancing first.) Also, make the guard lifetime controllable
6992 via a new GuardLifetime torrc option and a GuardLifetime consensus
6993 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
6995 o Major features (bridges with pluggable transports):
6996 - Bridges now report the pluggable transports they support to the
6997 bridge authority, so it can pass the supported transports on to
6998 bridgedb and/or eventually do reachability testing. Implements
7000 - Automatically forward the TCP ports of pluggable transport
7001 proxies using tor-fw-helper if PortForwarding is enabled. Implements
7004 o Major features (geoip database):
7005 - Maxmind began labelling Tor relays as being in country "A1",
7006 which breaks by-country node selection inside Tor. Now we use a
7007 script to replace "A1" ("Anonymous Proxy") entries in our geoip
7008 file with real country codes. This script fixes about 90% of "A1"
7009 entries automatically and uses manual country code assignments to
7010 fix the remaining 10%. See src/config/README.geoip for details.
7012 - Add GeoIP database for IPv6 addresses. The new config option
7014 - Update to the October 2 2013 Maxmind GeoLite Country database.
7016 o Major features (IPv6):
7017 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
7018 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
7019 to happen. Implements ticket 5535.
7020 - All kind of relays, not just bridges, can now advertise an IPv6
7021 OR port. Implements ticket 6362.
7022 - Relays can now exit to IPv6 addresses: make sure that you have IPv6
7023 connectivity, then set the IPv6Exit flag to 1. Also make sure your
7024 exit policy reads as you would like: the address * applies to all
7025 address families, whereas *4 is IPv4 address only, and *6 is IPv6
7026 addresses only. On the client side, you'll need to wait for enough
7027 exits to support IPv6, apply the "IPv6Traffic" flag to a SocksPort,
7028 and use Socks5. Closes ticket 5547, implements proposal 117 as
7029 revised in proposal 208.
7030 - Bridge authorities now accept IPv6 bridge addresses and include
7031 them in network status documents. Implements ticket 5534.
7032 - Directory authorities vote on IPv6 OR ports. Implements ticket 6363.
7034 o Major features (directory authorities):
7035 - Directory authorities now prefer using measured bandwidths to
7036 advertised ones when computing flags and thresholds. Resolves
7038 - Directory authorities that vote measured bandwidths about more
7039 than a threshold number of relays now treat relays with
7040 unmeasured bandwidths as having bandwidth 0 when computing their
7041 flags. Resolves ticket 8435.
7042 - Directory authorities now support a new consensus method (17)
7043 where they cap the published bandwidth of relays for which
7044 insufficient bandwidth measurements exist. Fixes part of bug 2286.
7045 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
7046 serve any v2 directory information. Now we can test disabling the
7047 old deprecated v2 directory format, and see whether doing so has
7048 any effect on network load. Begins to fix bug 6783.
7050 o Major features (build and portability):
7051 - Switch to a nonrecursive Makefile structure. Now instead of each
7052 Makefile.am invoking other Makefile.am's, there is a master
7053 Makefile.am that includes the others. This change makes our build
7054 process slightly more maintainable, and improves parallelism for
7055 building with make -j. Original patch by Stewart Smith; various
7056 fixes by Jim Meyering.
7057 - Where available, we now use automake's "silent" make rules by
7058 default, so that warnings are easier to spot. You can get the old
7059 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
7060 - Resume building correctly with MSVC and Makefile.nmake. This patch
7061 resolves numerous bugs and fixes reported by ultramage, including
7062 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
7064 o Security features:
7065 - Switch to a completely time-invariant approach for picking nodes
7066 weighted by bandwidth. Our old approach would run through the
7067 part of the loop after it had made its choice slightly slower
7068 than it ran through the part of the loop before it had made its
7069 choice. Addresses ticket 6538.
7070 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
7071 by tor2web clients allows hidden services to identify tor2web
7072 clients through their repeated selection of the same rendezvous
7073 and introduction point circuit endpoints (their guards). Resolves
7076 o Major bugfixes (relay denial of service):
7077 - When we have too much memory queued in circuits (according to a new
7078 MaxMemInCellQueues option), close the circuits that have the oldest
7079 queued cells, on the theory that those are most responsible for
7080 us running low on memory. This prevents us from running out of
7081 memory as a relay if circuits fill up faster than they can be
7082 drained. Fixes bugs 9063 and 9093; bugfix on the 54th commit of
7083 Tor. This bug is a further fix beyond bug 6252, whose fix was
7084 merged into 0.2.3.21-rc.
7085 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
7086 ID: these could be used to create unexpected streams and circuits
7087 which would count as "present" to some parts of Tor but "absent"
7088 to others, leading to zombie circuits and streams or to a bandwidth
7089 denial-of-service. Fixes bug 7889; bugfix on every released version
7090 of Tor. Reported by "oftc_must_be_destroyed".
7091 - Avoid a bug where our response to TLS renegotiation under certain
7092 network conditions could lead to a busy-loop, with 100% CPU
7093 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
7095 o Major bugfixes (asserts, crashes, leaks):
7096 - Prevent the get_freelists() function from running off the end of
7097 the list of freelists if it somehow gets an unrecognized
7098 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
7100 - Avoid a memory leak where we would leak a consensus body when we
7101 find that a consensus which we couldn't previously verify due to
7102 missing certificates is now verifiable. Fixes bug 8719; bugfix
7104 - If we are unable to save a microdescriptor to the journal, do not
7105 drop it from memory and then reattempt downloading it. Fixes bug
7106 9645; bugfix on 0.2.2.6-alpha.
7107 - Fix an assertion failure that would occur when disabling the
7108 ORPort setting on a running Tor process while accounting was
7109 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
7110 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
7111 when an exit connection with optimistic data succeeds immediately
7112 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
7114 - Fix a memory leak that would occur whenever a configuration
7115 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
7117 o Major bugfixes (relay rate limiting):
7118 - When a TLS write is partially successful but incomplete, remember
7119 that the flushed part has been flushed, and notice that bytes were
7120 actually written. Reported and fixed pseudonymously. Fixes bug 7708;
7121 bugfix on Tor 0.1.0.5-rc.
7122 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
7123 to 1GB/1GB. The previous defaults were intended to be "basically
7124 infinite", but it turns out they're now limiting our 100mbit+
7125 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
7126 last time we raised it).
7127 - No longer stop reading or writing on cpuworker connections when
7128 our rate limiting buckets go empty. Now we should handle circuit
7129 handshake requests more promptly. Resolves bug 9731.
7131 o Major bugfixes (client-side privacy):
7132 - When we mark a circuit as unusable for new circuits, have it
7133 continue to be unusable for new circuits even if MaxCircuitDirtiness
7134 is increased too much at the wrong time, or the system clock jumps
7135 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
7136 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
7137 which have resolved to internal addresses") is set, apply that
7138 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
7139 - When an exit relay rejects a stream with reason "exit policy", but
7140 we only know an exit policy summary (e.g. from the microdesc
7141 consensus) for it, do not mark the relay as useless for all exiting.
7142 Instead, mark just the circuit as unsuitable for that particular
7143 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
7145 o Major bugfixes (stream isolation):
7146 - Allow applications to get proper stream isolation with
7147 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
7148 username/password authentication also offer "no authentication". Tor
7149 had previously preferred "no authentication", so the applications
7150 never actually sent Tor their auth details. Now Tor selects
7151 username/password authentication if it's offered. You can disable
7152 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
7153 bug 8117; bugfix on 0.2.3.3-alpha.
7154 - Follow the socks5 protocol when offering username/password
7155 authentication. The fix for bug 8117 exposed this bug, and it
7156 turns out real-world applications like Pidgin do care. Bugfix on
7157 0.2.3.2-alpha; fixes bug 8879.
7159 o Major bugfixes (client circuit building):
7160 - Alter circuit build timeout measurement to start at the point
7161 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
7162 initialization). This should make our timeout measurements more
7163 uniform. Previously, we were sometimes including ORconn setup time
7164 in our circuit build time measurements. Should resolve bug 3443.
7165 - If the circuit build timeout logic is disabled (via the consensus,
7166 or because we are an authority), then don't build testing circuits.
7167 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
7169 o Major bugfixes (client-side DNS):
7170 - Turn off the client-side DNS cache by default. Updating and using
7171 the DNS cache is now configurable on a per-client-port
7172 level. SOCKSPort, DNSPort, etc lines may now contain
7173 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
7174 cache these types of DNS answers when we receive them from an
7175 exit node in response to an application request on this port, and
7176 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
7177 cached DNS answers of these types, we shouldn't use them. It's
7178 potentially risky to use cached DNS answers at the client, since
7179 doing so can indicate to one exit what answers we've gotten
7180 for DNS lookups in the past. With IPv6, this becomes especially
7181 problematic. Using cached DNS answers for requests on the same
7182 circuit would present less linkability risk, since all traffic
7183 on a circuit is already linkable, but it would also provide
7184 little performance benefit: the exit node caches DNS replies
7185 too. Implements a simplified version of Proposal 205. Implements
7188 o Major bugfixes (hidden service privacy):
7189 - Limit hidden service descriptors to at most ten introduction
7190 points, to slow one kind of guard enumeration. Fixes bug 9002;
7191 bugfix on 0.1.1.11-alpha.
7193 o Major bugfixes (directory fetching):
7194 - If the time to download the next old-style networkstatus is in
7195 the future, do not decline to consider whether to download the
7196 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
7198 - We used to always request authority certificates by identity digest,
7199 meaning we'd get the newest one even when we wanted one with a
7200 different signing key. Then we would complain about being given
7201 a certificate we already had, and never get the one we really
7202 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
7203 resource to request the one we want. Fixes bug 5595; bugfix on
7206 o Major bugfixes (bridge reachability):
7207 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
7208 previously they did not, which prevented them from receiving
7209 successful connections from relays for self-test or bandwidth
7210 testing. Also, when a relay is extending a circuit to a bridge,
7211 it needs to send a NETINFO cell, even when the bridge hasn't sent
7212 an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
7214 o Major bugfixes (control interface):
7215 - When receiving a new configuration file via the control port's
7216 LOADCONF command, do not treat the defaults file as absent.
7217 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
7219 o Major bugfixes (directory authorities):
7220 - Stop marking every relay as having been down for one hour every
7221 time we restart a directory authority. These artificial downtimes
7222 were messing with our Stable and Guard flag calculations. Fixes
7223 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
7224 - When computing directory thresholds, ignore any rejected-as-sybil
7225 nodes during the computation so that they can't influence Fast,
7226 Guard, etc. (We should have done this for proposal 109.) Fixes
7228 - When marking a node as a likely sybil, reset its uptime metrics
7229 to zero, so that it cannot time towards getting marked as Guard,
7230 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
7232 - Fix a bug in the voting algorithm that could yield incorrect results
7233 when a non-naming authority declared too many flags. Fixes bug 9200;
7234 bugfix on 0.2.0.3-alpha.
7236 o Internal abstraction features:
7237 - Introduce new channel_t abstraction between circuits and
7238 or_connection_t to allow for implementing alternate OR-to-OR
7239 transports. A channel_t is an abstract object which can either be a
7240 cell-bearing channel, which is responsible for authenticating and
7241 handshaking with the remote OR and transmitting cells to and from
7242 it, or a listening channel, which spawns new cell-bearing channels
7243 at the request of remote ORs. Implements part of ticket 6465.
7244 - Make a channel_tls_t subclass of channel_t, adapting it to the
7245 existing or_connection_t code. The V2/V3 protocol handshaking
7246 code which formerly resided in command.c has been moved below the
7247 channel_t abstraction layer and may be found in channeltls.c now.
7248 Implements the rest of ticket 6465.
7249 - Introduce new circuitmux_t storing the queue of circuits for
7250 a channel; this encapsulates and abstracts the queue logic and
7251 circuit selection policy, and allows the latter to be overridden
7252 easily by switching out a policy object. The existing EWMA behavior
7253 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
7255 o New build requirements:
7256 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
7257 strongly recommended.
7258 - Tor maintainers now require Automake version 1.9 or later to build
7259 Tor from the Git repository. (Automake is not required when building
7260 from a source distribution.)
7262 o Minor features (protocol):
7263 - No longer include the "opt" prefix when generating routerinfos
7264 or v2 directories: it has been needless since Tor 0.1.2. Closes
7266 - Reject EXTEND cells sent to nonexistent streams. According to the
7267 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
7268 we were only checking for stream IDs that were currently in use.
7269 Found while hunting for more instances of bug 6271. Bugfix on
7270 0.0.2pre8, which introduced incremental circuit construction.
7271 - Tor relays and clients now support a better CREATE/EXTEND cell
7272 format, allowing the sender to specify multiple address, identity,
7273 and handshake types. Implements Robert Ransom's proposal 200;
7275 - Reject as invalid most directory objects containing a NUL.
7276 Belt-and-suspender fix for bug 8037.
7278 o Minor features (security):
7279 - Clear keys and key-derived material left on the stack in
7280 rendservice.c and rendclient.c. Check return value of
7281 crypto_pk_write_private_key_to_string() in rend_service_load_keys().
7282 These fixes should make us more forward-secure against cold-boot
7283 attacks and the like. Fixes bug 2385.
7284 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
7285 Irix's random() only return 15 bits; Solaris's random() returns more
7286 bits but its RAND_MAX says it only returns 15, and so on. Motivated
7287 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
7289 o Minor features (control protocol):
7290 - Add a "GETINFO signal/names" control port command. Implements
7292 - Provide default values for all options via "GETINFO config/defaults".
7293 Implements ticket 4971.
7294 - Allow an optional $ before the node identity digest in the
7295 controller command GETINFO ns/id/<identity>, for consistency with
7296 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
7297 - Add CACHED keyword to ADDRMAP events in the control protocol
7298 to indicate whether a DNS result will be cached or not. Resolves
7300 - Generate bootstrapping status update events correctly when fetching
7301 microdescriptors. Fixes bug 9927.
7303 o Minor features (path selection):
7304 - When deciding whether we have enough descriptors to build circuits,
7305 instead of looking at raw relay counts, look at which fraction
7306 of (bandwidth-weighted) paths we're able to build. This approach
7307 keeps clients from building circuits if their paths are likely to
7308 stand out statistically. The default fraction of paths needed is
7309 taken from the consensus directory; you can override it with the
7310 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
7311 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
7312 and we have GeoIP information, also exclude all nodes with unknown
7313 countries "??" and "A1". This behavior is controlled by the
7314 new GeoIPExcludeUnknown option: you can make such nodes always
7315 excluded with "GeoIPExcludeUnknown 1", and disable the feature
7316 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
7317 gets you the default behavior. Implements feature 7706.
7319 o Minor features (hidden services):
7320 - Improve circuit build timeout handling for hidden services.
7321 In particular: adjust build timeouts more accurately depending
7322 upon the number of hop-RTTs that a particular circuit type
7323 undergoes. Additionally, launch intro circuits in parallel
7324 if they timeout, and take the first one to reply as valid.
7325 - The Tor client now ignores sub-domain components of a .onion
7326 address. This change makes HTTP "virtual" hosting
7327 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
7328 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
7329 hosted on the same hidden service. Implements proposal 204.
7330 - Enable Tor to read configuration, state, and key information from
7331 a FIFO. Previously Tor would only read from files with a positive
7332 stat.st_size. Code from meejah; fixes bug 6044.
7334 o Minor features (clients):
7335 - Teach bridge-using clients to avoid 0.2.2.x bridges when making
7336 microdescriptor-related dir requests, and only fall back to normal
7337 descriptors if none of their bridges can handle microdescriptors
7338 (as opposed to the fix in ticket 4013, which caused them to fall
7339 back to normal descriptors if *any* of their bridges preferred
7340 them). Resolves ticket 4994.
7341 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
7342 TCP ports to forward. In the past it only accepted two ports:
7343 the ORPort and the DirPort.
7345 o Minor features (protecting client timestamps):
7346 - Clients no longer send timestamps in their NETINFO cells. These were
7347 not used for anything, and they provided one small way for clients
7348 to be distinguished from each other as they moved from network to
7349 network or behind NAT. Implements part of proposal 222.
7350 - Clients now round timestamps in INTRODUCE cells down to the nearest
7351 10 minutes. If a new Support022HiddenServices option is set to 0, or
7352 if it's set to "auto" and the feature is disabled in the consensus,
7353 the timestamp is sent as 0 instead. Implements part of proposal 222.
7354 - Stop sending timestamps in AUTHENTICATE cells. This is not such
7355 a big deal from a security point of view, but it achieves no actual
7356 good purpose, and isn't needed. Implements part of proposal 222.
7357 - Reduce down accuracy of timestamps in hidden service descriptors.
7358 Implements part of proposal 222.
7360 o Minor features (bridges):
7361 - Make bridge relays check once a minute for whether their IP
7362 address has changed, rather than only every 15 minutes. Resolves
7364 - Bridge statistics now count bridge clients connecting over IPv6:
7365 bridge statistics files now list "bridge-ip-versions" and
7366 extra-info documents list "geoip6-db-digest". The control protocol
7367 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
7368 implementation by "shkoo", addressing ticket 5055.
7369 - Add a new torrc option "ServerTransportListenAddr" to let bridge
7370 operators select the address where their pluggable transports will
7371 listen for connections. Resolves ticket 7013.
7372 - Randomize the lifetime of our SSL link certificate, so censors can't
7373 use the static value for filtering Tor flows. Resolves ticket 8443;
7374 related to ticket 4014 which was included in 0.2.2.33.
7376 o Minor features (relays):
7377 - Option OutboundBindAddress can be specified multiple times and
7378 accepts IPv6 addresses. Resolves ticket 6876.
7380 o Minor features (IPv6, client side):
7381 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
7382 prefer to hand out virtual IPv6 addresses, since there are more of
7383 them and we can't run out. To override this behavior and make IPv4
7384 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
7385 or DNSPort you're using for resolving. Implements ticket 7571.
7386 - AutomapHostsOnResolve responses are now randomized, to avoid
7387 annoying situations where Tor is restarted and applications
7388 connect to the wrong addresses.
7389 - Never try more than 1000 times to pick a new virtual address when
7390 AutomapHostsOnResolve is set. That's good enough so long as we
7391 aren't close to handing out our entire virtual address space;
7392 if you're getting there, it's best to switch to IPv6 virtual
7395 o Minor features (IPv6, relay/authority side):
7396 - New config option "AuthDirHasIPv6Connectivity 1" that directory
7397 authorities should set if they have IPv6 connectivity and want to
7398 do reachability tests for IPv6 relays. Implements feature 5974.
7399 - A relay with an IPv6 OR port now sends that address in NETINFO
7400 cells (in addition to its other address). Implements ticket 6364.
7402 o Minor features (directory authorities):
7403 - Directory authorities no long accept descriptors for any version of
7404 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
7405 These versions are insecure, unsupported, or both. Implements
7407 - When directory authorities are computing thresholds for flags,
7408 never let the threshold for the Fast flag fall below 4096
7409 bytes. Also, do not consider nodes with extremely low bandwidths
7410 when deciding thresholds for various directory flags. This change
7411 should raise our threshold for Fast relays, possibly in turn
7412 improving overall network performance; see ticket 1854. Resolves
7414 - Directory authorities now include inside each vote a statement of
7415 the performance thresholds they used when assigning flags.
7416 Implements ticket 8151.
7417 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
7418 in directory authority votes to describe whether they have enough
7419 measured bandwidths to ignore advertised (relay descriptor)
7420 bandwidth claims. Resolves ticket 8711.
7422 o Minor features (path bias detection):
7423 - Path Use Bias: Perform separate accounting for successful circuit
7424 use. Keep separate statistics on stream attempt rates versus stream
7425 success rates for each guard. Provide configurable thresholds to
7426 determine when to emit log messages or disable use of guards that
7427 fail too many stream attempts. Resolves ticket 7802.
7428 - Create three levels of Path Bias log messages, as opposed to just
7429 two. These are configurable via consensus as well as via the torrc
7430 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
7431 The default values are 0.70, 0.50, and 0.30 respectively.
7432 - Separate the log message levels from the decision to drop guards,
7433 which also is available via torrc option PathBiasDropGuards.
7434 PathBiasDropGuards still defaults to 0 (off).
7435 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
7436 in combination with PathBiasExtremeRate.
7437 - Increase the default values for PathBiasScaleThreshold and
7438 PathBiasCircThreshold from (200, 20) to (300, 150).
7439 - Add in circuit usage accounting to path bias. If we try to use a
7440 built circuit but fail for any reason, it counts as path bias.
7441 Certain classes of circuits where the adversary gets to pick your
7442 destination node are exempt from this accounting. Usage accounting
7443 can be specifically disabled via consensus parameter or torrc.
7444 - Convert all internal path bias state to double-precision floating
7445 point, to avoid roundoff error and other issues.
7446 - Only record path bias information for circuits that have completed
7447 *two* hops. Assuming end-to-end tagging is the attack vector, this
7448 makes us more resilient to ambient circuit failure without any
7449 detection capability loss.
7451 o Minor features (build):
7452 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
7453 dhill. Resolves ticket 6982.
7454 - Compile on win64 using mingw64. Fixes bug 7260; patches from
7456 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
7457 separate error codes; or at least, don't break for that reason.
7458 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
7460 o Build improvements (autotools):
7461 - Warn if building on a platform with an unsigned time_t: there
7462 are too many places where Tor currently assumes that time_t can
7463 hold negative values. We'd like to fix them all, but probably
7465 - Do not report status verbosely from autogen.sh unless the -v flag
7466 is specified. Fixes issue 4664. Patch from Onizuka.
7467 - Detect and reject attempts to build Tor with threading support
7468 when OpenSSL has been compiled without threading support.
7470 - Try to detect if we are ever building on a platform where
7471 memset(...,0,...) does not set the value of a double to 0.0. Such
7472 platforms are permitted by the C standard, though in practice
7473 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
7474 currently support them, but it's better to detect them and fail
7475 than to perform erroneously.
7476 - We no longer warn so much when generating manpages from their
7478 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
7479 the signs of types during autoconf. This is better than our old
7480 approach, which didn't work when cross-compiling.
7482 o Minor features (log messages, warnings):
7483 - Detect when we're running with a version of OpenSSL other than the
7484 one we compiled with. This conflict has occasionally given people
7485 hard-to-track-down errors.
7486 - Warn users who run hidden services on a Tor client with
7487 UseEntryGuards disabled that their hidden services will be
7488 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
7489 attack which motivated Tor to support entry guards in the first
7490 place). Resolves ticket 6889.
7491 - Warn when we are binding low ports when hibernation is enabled;
7492 previously we had warned when we were _advertising_ low ports with
7493 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
7494 - Issue a warning when running with the bufferevents backend enabled.
7495 It's still not stable, and people should know that they're likely
7496 to hit unexpected problems. Closes ticket 9147.
7498 o Minor features (log messages, notices):
7499 - Refactor resolve_my_address() so it returns the method by which we
7500 decided our public IP address (explicitly configured, resolved from
7501 explicit hostname, guessed from interfaces, learned by gethostname).
7502 Now we can provide more helpful log messages when a relay guesses
7503 its IP address incorrectly (e.g. due to unexpected lines in
7504 /etc/hosts). Resolves ticket 2267.
7505 - Track how many "TAP" and "NTor" circuit handshake requests we get,
7506 and how many we complete, and log it every hour to help relay
7507 operators follow trends in network load. Addresses ticket 9658.
7509 o Minor features (log messages, diagnostics):
7510 - If we fail to free a microdescriptor because of bug 7164, log
7511 the filename and line number from which we tried to free it.
7512 - We compute the overhead from passing onionskins back and forth to
7513 cpuworkers, and report it when dumping statistics in response to
7514 SIGUSR1. Supports ticket 7291.
7515 - Add another diagnostic to the heartbeat message: track and log
7516 overhead that TLS is adding to the data we write. If this is
7517 high, we are sending too little data to SSL_write at a time.
7518 Diagnostic for bug 7707.
7519 - Log packaged cell fullness as part of the heartbeat message.
7520 Diagnosis to try to determine the extent of bug 7743.
7521 - Add more detail to a log message about relaxed timeouts, to help
7523 - When learning a fingerprint for a bridge, log its corresponding
7524 transport type. Implements ticket 7896.
7525 - Warn more aggressively when flushing microdescriptors to a
7526 microdescriptor cache fails, in an attempt to mitigate bug 8031,
7527 or at least make it more diagnosable.
7528 - Improve the log message when "Bug/attack: unexpected sendme cell
7529 from client" occurs, to help us track bug 8093.
7530 - Improve debugging output to help track down bug 8185 ("Bug:
7531 outgoing relay cell has n_chan==NULL. Dropping.")
7533 o Minor features (log messages, quieter bootstrapping):
7534 - Log fewer lines at level "notice" about our OpenSSL and Libevent
7535 versions and capabilities when everything is going right. Resolves
7536 part of ticket 6736.
7537 - Omit the first heartbeat log message, because it never has anything
7538 useful to say, and it clutters up the bootstrapping messages.
7539 Resolves ticket 6758.
7540 - Don't log about reloading the microdescriptor cache at startup. Our
7541 bootstrap warnings are supposed to tell the user when there's a
7542 problem, and our bootstrap notices say when there isn't. Resolves
7543 ticket 6759; bugfix on 0.2.2.6-alpha.
7544 - Don't log "I learned some more directory information" when we're
7545 reading cached directory information. Reserve it for when new
7546 directory information arrives in response to a fetch. Resolves
7548 - Don't complain about bootstrapping problems while hibernating.
7549 These complaints reflect a general code problem, but not one
7550 with any problematic effects (no connections are actually
7551 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
7553 o Minor features (testing):
7554 - In our testsuite, create temporary directories with a bit more
7555 entropy in their name to make name collisions less likely. Fixes
7557 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
7558 (P-256) Diffie-Hellman handshakes to src/or/bench.
7559 - Add benchmark functions to test onion handshake performance.
7562 - The DirServer option is now DirAuthority, for consistency with
7563 current naming patterns. You can still use the old DirServer form.
7565 o Minor bugfixes (protocol):
7566 - Fix the handling of a TRUNCATE cell when it arrives while the
7567 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
7568 - When a Tor client gets a "truncated" relay cell, the first byte of
7569 its payload specifies why the circuit was truncated. We were
7570 ignoring this 'reason' byte when tearing down the circuit, resulting
7571 in the controller not being told why the circuit closed. Now we
7572 pass the reason from the truncated cell to the controller. Bugfix
7573 on 0.1.2.3-alpha; fixes bug 7039.
7574 - Fix a misframing issue when reading the version numbers in a
7575 VERSIONS cell. Previously we would recognize [00 01 00 02] as
7576 'version 1, version 2, and version 0x100', when it should have
7577 only included versions 1 and 2. Fixes bug 8059; bugfix on
7578 0.2.0.10-alpha. Reported pseudonymously.
7579 - Make the format and order of STREAM events for DNS lookups
7580 consistent among the various ways to launch DNS lookups. Fixes
7581 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy".
7583 o Minor bugfixes (syscalls and disk interaction):
7584 - Always check the return values of functions fcntl() and
7585 setsockopt(). We don't believe these are ever actually failing in
7586 practice, but better safe than sorry. Also, checking these return
7587 values should please analysis tools like Coverity. Patch from
7588 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
7589 - Avoid double-closing the listener socket in our socketpair()
7590 replacement (used on Windows) in the case where the addresses on
7591 our opened sockets don't match what we expected. Fixes bug 9400;
7592 bugfix on 0.0.2pre7. Found by Coverity.
7593 - Correctly store microdescriptors and extrainfo descriptors that
7594 include an internal NUL byte. Fixes bug 8037; bugfix on
7595 0.2.0.1-alpha. Bug reported by "cypherpunks".
7596 - If for some reason we fail to write a microdescriptor while
7597 rebuilding the cache, do not let the annotations from that
7598 microdescriptor linger in the cache file, and do not let the
7599 microdescriptor stay recorded as present in its old location.
7600 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
7601 - Use direct writes rather than stdio when building microdescriptor
7602 caches, in an attempt to mitigate bug 8031, or at least make it
7605 o Minor fixes (config options):
7606 - Warn and fail if a server is configured not to advertise any
7607 ORPorts at all. (We need *something* to put in our descriptor,
7608 or we just won't work.)
7609 - Behave correctly when the user disables LearnCircuitBuildTimeout
7610 but doesn't tell us what they would like the timeout to be. Fixes
7611 bug 6304; bugfix on 0.2.2.14-alpha.
7612 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
7613 to start with a triple-underscore so the controller won't touch it.
7614 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
7615 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
7616 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
7617 - When autodetecting the number of CPUs, use the number of available
7618 CPUs in preference to the number of configured CPUs. Inform the
7619 user if this reduces the number of available CPUs. Fixes bug 8002;
7620 bugfix on 0.2.3.1-alpha.
7621 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
7622 - Make it an error when you set EntryNodes but disable UseGuardNodes,
7623 since it will (surprisingly to some users) ignore EntryNodes. Fixes
7624 bug 8180; bugfix on 0.2.3.11-alpha.
7625 - Avoid overflows when the user sets MaxCircuitDirtiness to a
7626 ridiculously high value, by imposing a (ridiculously high) 30-day
7627 maximum on MaxCircuitDirtiness.
7629 o Minor bugfixes (control protocol):
7630 - Stop sending a stray "(null)" in some cases for the server status
7631 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
7633 - The ADDRMAP command can no longer generate an ill-formed error
7634 code on a failed MAPADDRESS. It now says "internal" rather than
7635 an English sentence fragment with spaces in the middle. Bugfix on
7638 o Minor bugfixes (clients / edges):
7639 - When we receive a RELAY_END cell with the reason DONE, or with no
7640 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
7641 status as "connection refused". Previously we reported these cases
7642 as success but then immediately closed the connection. Fixes bug
7643 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
7644 - If the guard we choose first doesn't answer, we would try the
7645 second guard, but once we connected to the second guard we would
7646 abandon it and retry the first one, slowing down bootstrapping.
7647 The fix is to treat all our initially chosen guards as acceptable
7648 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
7649 - When choosing which stream on a formerly stalled circuit to wake
7650 first, make better use of the platform's weak RNG. Previously,
7651 we had been using the % ("modulo") operator to try to generate a
7652 1/N chance of picking each stream, but this behaves badly with
7653 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
7656 o Minor bugfixes (path bias detection):
7657 - If the state file's path bias counts are invalid (presumably from a
7658 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
7659 additional checks and log messages to the scaling of Path Bias
7660 counts, in case there still are remaining issues with scaling.
7661 Should help resolve bug 8235.
7662 - Prevent rounding error in path bias counts when scaling
7663 them down, and use the correct scale factor default. Also demote
7664 some path bias related log messages down a level and make others
7665 less scary sounding. Fixes bug 6647. Bugfix on 0.2.3.17-beta.
7666 - Remove a source of rounding error during path bias count scaling;
7667 don't count cannibalized circuits as used for path bias until we
7668 actually try to use them; and fix a circuit_package_relay_cell()
7669 warning message about n_chan==NULL. Fixes bug 7802.
7670 - Paste the description for PathBias parameters from the man
7671 page into or.h, so the code documents them too. Fixes bug 7982;
7672 bugfix on 0.2.3.17-beta.
7674 o Minor bugfixes (relays):
7675 - Stop trying to resolve our hostname so often (e.g. every time we
7676 think about doing a directory fetch). Now we reuse the cached
7677 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
7678 and 2410 (bugfix on 0.1.2.2-alpha).
7679 - When examining the list of network interfaces to find our address,
7680 do not consider non-running or disabled network interfaces. Fixes
7681 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
7683 o Minor bugfixes (blocking resistance):
7684 - Only disable TLS session ticket support when running as a TLS
7685 server. Now clients will blend better with regular Firefox
7686 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
7688 o Minor bugfixes (IPv6):
7689 - Use square brackets around IPv6 addresses in numerous places
7690 that needed them, including log messages, HTTPS CONNECT proxy
7691 requests, TransportProxy statefile entries, and pluggable transport
7692 extra-info lines. Fixes bug 7011; patch by David Fifield.
7694 o Minor bugfixes (directory authorities):
7695 - Reject consensus votes with more than 64 known-flags. We aren't even
7696 close to that limit yet, and our code doesn't handle it correctly.
7697 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
7698 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
7699 bugfix on 0.2.0.3-alpha.
7701 o Minor bugfixes (memory leaks):
7702 - Avoid leaking memory if we fail to compute a consensus signature
7703 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
7704 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
7705 on 0.2.1.1-alpha; fixes bug 7816.
7706 - Fix a memory leak during safe-cookie controller authentication.
7707 Bugfix on 0.2.3.13-alpha; fixes bug 7816.
7708 - Free some more still-in-use memory at exit, to make hunting for
7709 memory leaks easier. Resolves bug 7029.
7711 o Minor bugfixes (code correctness):
7712 - Increase the width of the field used to remember a connection's
7713 link protocol version to two bytes. Harmless for now, since the
7714 only currently recognized versions are one byte long. Reported
7715 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
7716 - Fix a crash when debugging unit tests on Windows: deallocate a
7717 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
7718 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
7719 - When detecting the largest possible file descriptor (in order to
7720 close all file descriptors when launching a new program), actually
7721 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
7722 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
7724 - Avoid a crash if we fail to generate an extrainfo descriptor.
7725 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
7727 - Avoid an off-by-one error when checking buffer boundaries when
7728 formatting the exit status of a pluggable transport helper.
7729 This is probably not an exploitable bug, but better safe than
7730 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
7732 - Get rid of a couple of harmless clang warnings, where we compared
7733 enums to ints. These warnings are newly introduced in clang 3.2.
7735 o Minor bugfixes (code cleanliness):
7736 - Avoid use of reserved identifiers in our C code. The C standard
7737 doesn't like us declaring anything that starts with an
7738 underscore, so let's knock it off before we get in trouble. Fix
7739 for bug 1031; bugfix on the first Tor commit.
7740 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
7741 with large values. This situation was untriggered, but nevertheless
7742 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
7743 - Fix an impossible buffer overrun in the AES unit tests. Fixes
7744 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
7745 - Fix handling of rendezvous client authorization types over 8.
7746 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
7747 - Remove a couple of extraneous semicolons that were upsetting the
7748 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
7749 bugfix on 0.2.2.1-alpha.
7750 - When complaining about a client port on a public address, log
7751 which address we're complaining about. Fixes bug 4020; bugfix on
7752 0.2.3.3-alpha. Patch by Tom Fitzhenry.
7754 o Minor bugfixes (log messages, warnings):
7755 - If we encounter a write failure on a SOCKS connection before we
7756 finish our SOCKS handshake, don't warn that we closed the
7757 connection before we could send a SOCKS reply. Fixes bug 8427;
7758 bugfix on 0.1.0.1-rc.
7759 - Fix a directory authority warn caused when we have a large amount
7760 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
7761 - Downgrade "Failed to hand off onionskin" messages to "debug"
7762 severity, since they're typically redundant with the "Your computer
7763 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
7764 - Avoid spurious warnings when configuring multiple client ports of
7765 which only some are nonlocal. Previously, we had claimed that some
7766 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
7769 o Minor bugfixes (log messages, other):
7770 - Fix log messages and comments to avoid saying "GMT" when we mean
7771 "UTC". Fixes bug 6113.
7772 - When rejecting a configuration because we were unable to parse a
7773 quoted string, log an actual error message. Fixes bug 7950; bugfix
7775 - Correctly recognize that [::1] is a loopback address. Fixes
7776 bug 8377; bugfix on 0.2.1.3-alpha.
7777 - Don't log inappropriate heartbeat messages when hibernating: a
7778 hibernating node is _expected_ to drop out of the consensus,
7779 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
7780 bugfix on 0.2.3.1-alpha.
7781 - Eliminate several instances where we use "Nickname=ID" to refer to
7782 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
7783 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
7786 o Minor bugfixes (build):
7787 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
7788 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
7789 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
7791 o Documentation fixes:
7792 - Make the torify manpage no longer refer to tsocks; torify hasn't
7793 supported tsocks since 0.2.3.14-alpha.
7794 - Make the tor manpage no longer reference tsocks.
7795 - Fix the GeoIPExcludeUnknown documentation to refer to
7796 ExcludeExitNodes rather than the currently nonexistent
7797 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
7798 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
7800 - Say "KBytes" rather than "KB" in the man page (for various values
7801 of K), to further reduce confusion about whether Tor counts in
7802 units of memory or fractions of units of memory. Resolves ticket 7054.
7803 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
7804 names match. Fixes bug 7768.
7805 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
7806 message is logged at notice, not at info.
7807 - Clarify the usage and risks of setting the ContactInfo torrc line
7808 for your relay or bridge. Resolves ticket 9854.
7809 - Add anchors to the manpage so we can link to the html version of
7810 the documentation for specific options. Resolves ticket 9866.
7811 - Replace remaining references to DirServer in man page and
7812 log entries. Resolves ticket 10124.
7815 - Stop exporting estimates of v2 and v3 directory traffic shares
7816 in extrainfo documents. They were unneeded and sometimes inaccurate.
7817 Also stop exporting any v2 directory request statistics. Resolves
7819 - Drop support for detecting and warning about versions of Libevent
7820 before 1.3e. Nothing reasonable ships with them any longer; warning
7821 the user about them shouldn't be needed. Resolves ticket 6826.
7822 - Now that all versions before 0.2.2.x are disallowed, we no longer
7823 need to work around their missing features. Remove a bunch of
7827 - The tor-tsocks.conf is no longer distributed or installed. We
7828 recommend that tsocks users use torsocks instead. Resolves
7830 - Remove some of the older contents of doc/ as obsolete; move others
7831 to torspec.git. Fixes bug 8965.
7833 o Code simplification:
7834 - Avoid using character buffers when constructing most directory
7835 objects: this approach was unwieldy and error-prone. Instead,
7836 build smartlists of strings, and concatenate them when done.
7837 - Rename "isin" functions to "contains", for grammar. Resolves
7839 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
7840 with the natural logarithm function from the system libm. Resolves
7842 - Start using OpenBSD's implementation of queue.h, so that we don't
7843 need to hand-roll our own pointer and list structures whenever we
7844 need them. (We can't rely on a sys/queue.h, since some operating
7845 systems don't have them, and the ones that do have them don't all
7846 present the same extensions.)
7847 - Start using OpenBSD's implementation of queue.h (originally by
7849 - Enhance our internal sscanf replacement so that we can eliminate
7850 the last remaining uses of the system sscanf. (Though those uses
7851 of sscanf were safe, sscanf itself is generally error prone, so
7852 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
7854 - Replace all calls to snprintf() outside of src/ext with
7855 tor_snprintf(). Also remove the #define to replace snprintf with
7856 _snprintf on Windows; they have different semantics, and all of
7857 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
7860 - Add a wrapper function for the common "log a message with a
7862 - Split the onion.c file into separate modules for the onion queue
7863 and the different handshakes it supports.
7864 - Move the client-side address-map/virtual-address/DNS-cache code
7865 out of connection_edge.c into a new addressmap.c module.
7866 - Move the entry node code from circuitbuild.c to its own file.
7867 - Move the circuit build timeout tracking code from circuitbuild.c
7869 - Source files taken from other packages now reside in src/ext;
7870 previously they were scattered around the rest of Tor.
7871 - Move the generic "config" code into a new file, and have "config.c"
7872 hold only torrc- and state-related code. Resolves ticket 6823.
7873 - Move the core of our "choose a weighted element at random" logic
7874 into its own function, and give it unit tests. Now the logic is
7875 testable, and a little less fragile too.
7876 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
7877 - Move last_reachable and testing_since from routerinfo_t to node_t.
7878 Implements ticket 5529.
7879 - Add replaycache_t structure, functions and unit tests, then refactor
7880 rend_service_introduce() to be more clear to read, improve, debug,
7881 and test. Resolves bug 6177.
7884 - Remove some now-needless code that tried to aggressively flush
7885 OR connections as data was added to them. Since 0.2.0.1-alpha, our
7886 cell queue logic has saved us from the failure mode that this code
7887 was supposed to prevent. Removing this code will limit the number
7888 of baroque control flow paths through Tor's network logic. Reported
7889 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
7890 - Remove unused code for parsing v1 directories and "running routers"
7891 documents. Fixes bug 6887.
7892 - Remove the marshalling/unmarshalling code for sending requests to
7893 cpuworkers over a socket, and instead just send structs. The
7894 recipient will always be the same Tor binary as the sender, so
7895 any encoding is overkill.
7896 - Remove the testing_since field of node_t, which hasn't been used
7897 for anything since 0.2.0.9-alpha.
7898 - Finally remove support for malloc_good_size and malloc_usable_size.
7899 We had hoped that these functions would let us eke a little more
7900 memory out of our malloc implementation. Unfortunately, the only
7901 implementations that provided these functions are also ones that
7902 are already efficient about not overallocation: they never got us
7903 more than 7 or so bytes per allocation. Removing them saves us a
7904 little code complexity and a nontrivial amount of build complexity.
7907 Changes in version 0.2.3.25 - 2012-11-19
7908 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
7909 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
7910 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
7911 programmer, and friend. Unstinting in his dedication to the cause of
7912 freedom, he inspired and helped many of us as we began our work on
7913 anonymity, and inspires us still. Please honor his memory by writing
7914 software to protect people's freedoms, and by helping others to do so.
7916 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
7917 significantly reduced directory overhead (via microdescriptors),
7918 enormous crypto performance improvements for fast relays on new
7919 enough hardware, a new v3 TLS handshake protocol that can better
7920 resist fingerprinting, support for protocol obfuscation plugins (aka
7921 pluggable transports), better scalability for hidden services, IPv6
7922 support for bridges, performance improvements like allowing clients
7923 to skip the first round-trip on the circuit ("optimistic data") and
7924 refilling token buckets more often, a new "stream isolation" design
7925 to isolate different applications on different circuits, and many
7926 stability, security, and privacy fixes.
7928 Major features (v3 directory protocol):
7929 - Clients now use microdescriptors instead of regular descriptors
7930 to build circuits. Microdescriptors are authority-generated
7931 summaries of regular descriptors' contents, designed to change very
7932 rarely (see proposal 158 for details). This feature is designed
7933 to save bandwidth, especially for clients on slow internet
7934 connections. Use "UseMicrodescriptors 0" to disable it.
7935 - Caches now download, cache, and serve microdescriptors, as well
7936 as multiple "flavors" of the consensus, including a flavor that
7937 describes microdescriptors.
7939 o Major features (build hardening):
7940 - Enable gcc and ld hardening by default. Resolves ticket 5210.
7942 o Major features (relay scaling):
7943 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
7944 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
7945 vectorized AES implementations as appropriate. These can be much,
7946 much faster than other AES implementations.
7947 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
7948 implementation. It makes AES_CTR about 7% faster than our old one
7949 (which was about 10% faster than the one OpenSSL used to provide).
7950 Resolves ticket 4526.
7951 - Use OpenSSL's EVP interface for AES encryption, so that all AES
7952 operations can use hardware acceleration (if present). Resolves
7954 - Unconditionally use OpenSSL's AES implementation instead of our
7955 old built-in one. OpenSSL's AES has been better for a while, and
7956 relatively few servers should still be on any version of OpenSSL
7957 that doesn't have good optimized assembly AES.
7959 o Major features (blocking resistance):
7960 - Update TLS cipher list to match Firefox 8 and later. Resolves
7962 - Remove support for clients falsely claiming to support standard
7963 ciphersuites that they can actually provide. As of modern OpenSSL
7964 versions, it's not necessary to fake any standard ciphersuite,
7965 and doing so prevents us from using better ciphersuites in the
7966 future, since servers can't know whether an advertised ciphersuite
7967 is really supported or not. Some hosts -- notably, ones with very
7968 old versions of OpenSSL or where OpenSSL has been built with ECC
7969 disabled -- will stand out because of this change; TBB users should
7970 not be affected. Implements the client side of proposal 198.
7971 - Implement a new handshake protocol (v3) for authenticating Tors to
7972 each other over TLS. It should be more resistant to fingerprinting
7973 than previous protocols, and should require less TLS hacking for
7974 future Tor implementations. Implements proposal 176.
7975 - Allow variable-length padding cells, to disguise the length of
7976 Tor's TLS records. Implements part of proposal 184.
7977 - While we're trying to bootstrap, record how many TLS connections
7978 fail in each state, and report which states saw the most failures
7979 in response to any bootstrap failures. This feature may speed up
7980 diagnosis of censorship events. Implements ticket 3116.
7982 o Major features (pluggable transports):
7983 - Clients and bridges can now be configured to use a separate
7984 "transport" proxy. This approach makes the censorship arms race
7985 easier by allowing bridges to use protocol obfuscation plugins.
7986 Implements proposal 180 (tickets 2841 and 3472).
7988 o Major features (DoS resistance):
7989 - Now that Tor 0.2.0.x is completely deprecated, enable the final
7990 part of "Proposal 110: Avoiding infinite length circuits" by
7991 refusing all circuit-extend requests that do not use a relay_early
7992 cell. This change helps Tor resist a class of denial-of-service
7993 attacks by limiting the maximum circuit length.
7994 - Tear down the circuit if we get an unexpected SENDME cell. Clients
7995 could use this trick to make their circuits receive cells faster
7996 than our flow control would have allowed, or to gum up the network,
7997 or possibly to do targeted memory denial-of-service attacks on
7998 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
7999 from July 2002, before the release of Tor 0.0.0.
8001 o Major features (hidden services):
8002 - Adjust the number of introduction points that a hidden service
8003 will try to maintain based on how long its introduction points
8004 remain in use and how many introductions they handle. Fixes
8006 - Add a "tor2web mode" for clients that want to connect to hidden
8007 services non-anonymously (and possibly more quickly). As a safety
8008 measure to try to keep users from turning this on without knowing
8009 what they are doing, tor2web mode must be explicitly enabled at
8010 compile time, and a copy of Tor compiled to run in tor2web mode
8011 cannot be used as a normal Tor client. Implements feature 2553.
8013 o Major features (IPv6):
8014 - Clients can now connect to private bridges over IPv6. Bridges
8015 still need at least one IPv4 address in order to connect to
8016 other relays. Note that we don't yet handle the case where the
8017 user has two bridge lines for the same bridge (one IPv4, one
8018 IPv6). Implements parts of proposal 186.
8020 o Major features (directory authorities):
8021 - Use a more secure consensus parameter voting algorithm. Now at
8022 least three directory authorities or a majority of them must
8023 vote on a given parameter before it will be included in the
8024 consensus. Implements proposal 178.
8025 - Remove the artificially low cutoff of 20KB to guarantee the Fast
8026 flag. In the past few years the average relay speed has picked
8027 up, and while the "top 7/8 of the network get the Fast flag" and
8028 "all relays with 20KB or more of capacity get the Fast flag" rules
8029 used to have the same result, now the top 7/8 of the network has
8030 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
8032 o Major features (performance):
8033 - Exit nodes now accept and queue data on not-yet-connected streams.
8034 Previously, the client wasn't allowed to send data until the
8035 stream was connected, which slowed down all connections. This
8036 change will enable clients to perform a "fast-start" on streams
8037 and send data without having to wait for a confirmation that the
8038 stream has opened. Patch from Ian Goldberg; implements the server
8039 side of Proposal 174.
8040 - When using an exit relay running 0.2.3.x, clients can now
8041 "optimistically" send data before the exit relay reports that
8042 the stream has opened. This saves a round trip when starting
8043 connections where the client speaks first (such as web browsing).
8044 This behavior is controlled by a consensus parameter (currently
8045 disabled). To turn it on or off manually, use the "OptimisticData"
8046 torrc option. Implements proposal 181; code by Ian Goldberg.
8047 - Add a new TokenBucketRefillInterval option to refill token buckets
8048 more frequently than once per second. This should improve network
8049 performance, alleviate queueing problems, and make traffic less
8050 bursty. Implements proposal 183; closes ticket 3630. Design by
8051 Florian Tschorsch and Björn Scheuermann; implementation by
8053 - Raise the threshold of server descriptors needed (75%) and exit
8054 server descriptors needed (50%) before we will declare ourselves
8055 bootstrapped. This will make clients start building circuits a
8056 little later, but makes the initially constructed circuits less
8057 skewed and less in conflict with further directory fetches. Fixes
8060 o Major features (relays):
8061 - Relays now try regenerating and uploading their descriptor more
8062 frequently if they are not listed in the consensus, or if the
8063 version of their descriptor listed in the consensus is too
8064 old. This fix should prevent situations where a server declines
8065 to re-publish itself because it has done so too recently, even
8066 though the authorities decided not to list its recent-enough
8067 descriptor. Fix for bug 3327.
8069 o Major features (stream isolation):
8070 - You can now configure Tor so that streams from different
8071 applications are isolated on different circuits, to prevent an
8072 attacker who sees your streams as they leave an exit node from
8073 linking your sessions to one another. To do this, choose some way
8074 to distinguish the applications: have them connect to different
8075 SocksPorts, or have one of them use SOCKS4 while the other uses
8076 SOCKS5, or have them pass different authentication strings to the
8077 SOCKS proxy. Then, use the new SocksPort syntax to configure the
8078 degree of isolation you need. This implements Proposal 171.
8079 - There's a new syntax for specifying multiple client ports (such as
8080 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
8081 multiple *Port entries with full addr:port syntax on each.
8082 The old *ListenAddress format is still supported, but you can't
8083 mix it with the new *Port syntax.
8085 o Major features (bufferevents):
8086 - Tor can now optionally build with the "bufferevents" buffered IO
8087 backend provided by Libevent 2. To use this feature, make sure you
8088 have the latest possible version of Libevent, and pass the
8089 --enable-bufferevents flag to configure when building Tor from
8090 source. This feature will make our networking code more flexible,
8091 let us stack layers on each other, and let us use more efficient
8092 zero-copy transports where available.
8093 - Add experimental support for running on Windows with IOCP and no
8094 kernel-space socket buffers. This feature is controlled by a new
8095 "UserspaceIOCPBuffers" config option (off by default), which has
8096 no effect unless Tor has been built with bufferevents enabled,
8097 you're running on Windows, and you've set "DisableIOCP 0". In the
8098 long run, this may help solve or mitigate bug 98.
8100 o Major features (path selection):
8101 - The EntryNodes option can now include country codes like {de} or IP
8102 addresses or network masks. Previously we had disallowed these
8103 options because we didn't have an efficient way to keep the list up
8104 to date. Addresses ticket 1982, but see bug 2798 for an unresolved
8107 o Major features (port forwarding):
8108 - Add support for automatic port mapping on the many home routers
8109 that support NAT-PMP or UPnP. To build the support code, you'll
8110 need to have the libnatpnp library and/or the libminiupnpc library,
8111 and you'll need to enable the feature specifically by passing
8112 "--enable-upnp" and/or "--enable-natpnp" to ./configure. To turn
8113 it on, use the new PortForwarding option.
8115 o Major features (logging):
8116 - Add a new 'Heartbeat' log message type to periodically log a message
8117 describing Tor's status at level Notice. This feature is meant for
8118 operators who log at notice, and want to make sure that their Tor
8119 server is still working. Implementation by George Kadianakis.
8120 - Make logging resolution configurable with a new LogTimeGranularity
8121 option, and change the default from 1 millisecond to 1 second.
8122 Implements enhancement 1668.
8124 o Major features (other):
8125 - New "DisableNetwork" config option to prevent Tor from launching any
8126 connections or accepting any connections except on a control port.
8127 Bundles and controllers can set this option before letting Tor talk
8128 to the rest of the network, for example to prevent any connections
8129 to a non-bridge address. Packages like Orbot can also use this
8130 option to instruct Tor to save power when the network is off.
8131 - Try to use system facilities for enumerating local interface
8132 addresses, before falling back to our old approach (which was
8133 binding a UDP socket, and calling getsockname() on it). That
8134 approach was scaring OS X users whose draconian firewall
8135 software warned about binding to UDP sockets regardless of
8136 whether packets were sent. Now we try to use getifaddrs(),
8137 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
8138 system supports. Resolves ticket 1827.
8139 - Add experimental support for a "defaults" torrc file to be parsed
8140 before the regular torrc. Torrc options override the defaults file's
8141 options in the same way that the command line overrides the torrc.
8142 The SAVECONF controller command saves only those options which
8143 differ between the current configuration and the defaults file. HUP
8144 reloads both files. Implements task 4552.
8146 o New directory authorities:
8147 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
8148 authority. Closes ticket 5749.
8150 o Security/privacy fixes:
8151 - Avoid read-from-freed-memory and double-free bugs that could occur
8152 when a DNS request fails while launching it. Fixes bug 6480;
8153 bugfix on 0.2.0.1-alpha.
8154 - Reject any attempt to extend to an internal address. Without
8155 this fix, a router could be used to probe addresses on an internal
8156 network to see whether they were accepting connections. Fixes bug
8157 6710; bugfix on 0.0.8pre1.
8158 - Close any connection that sends unrecognized junk before the TLS
8159 handshake. Solves an issue noted in bug 4369.
8160 - The advertised platform of a relay now includes only its operating
8161 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not
8162 its service pack level (for Windows) or its CPU architecture
8163 (for Unix). Also drop the "git-XYZ" tag in the version. Packagers
8164 can insert an extra string in the platform line by setting the
8165 preprocessor variable TOR_BUILD_TAG. Resolves bug 2988.
8166 - Disable TLS session tickets. OpenSSL's implementation was giving
8167 our TLS session keys the lifetime of our TLS context objects, when
8168 perfect forward secrecy would want us to discard anything that
8169 could decrypt a link connection as soon as the link connection
8170 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
8171 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
8172 - Tor tries to wipe potentially sensitive data after using it, so
8173 that if some subsequent security failure exposes Tor's memory,
8174 the damage will be limited. But we had a bug where the compiler
8175 was eliminating these wipe operations when it decided that the
8176 memory was no longer visible to a (correctly running) program,
8177 hence defeating our attempt at defense in depth. We fix that
8178 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
8179 is unlikely to optimize away. Future versions of Tor may use
8180 a less ridiculously heavy approach for this. Fixes bug 7352.
8181 Reported in an article by Andrey Karpov.
8183 o Major bugfixes (crashes and asserts):
8184 - Avoid a pair of double-free and use-after-mark bugs that can
8185 occur with certain timings in canceled and re-received DNS
8186 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
8187 - Fix a denial of service attack by which any directory authority
8188 could crash all the others, or by which a single v2 directory
8189 authority could crash everybody downloading v2 directory
8190 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
8191 - Fix an assert that directory authorities could trigger on sighup
8192 during some configuration state transitions. We now don't treat
8193 it as a fatal error when the new descriptor we just generated in
8194 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
8195 - Avoid segfault when starting up having run with an extremely old
8196 version of Tor and parsing its state file. Fixes bug 6801; bugfix
8199 o Major bugfixes (clients):
8200 - If we are unable to find any exit that supports our predicted ports,
8201 stop calling them predicted, so that we don't loop and build
8202 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
8203 which introduced predicted ports.
8204 - Check at each new consensus whether our entry guards were picked
8205 long enough ago that we should rotate them. Previously, we only
8206 did this check at startup, which could lead to us holding a guard
8207 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
8208 - When fetching a bridge descriptor from a bridge authority,
8209 always do so anonymously, whether we have been able to open
8210 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
8211 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
8212 but we'll need to wait for bug 6010 before it's actually usable.
8214 o Major bugfixes (directory voting):
8215 - Check more thoroughly to prevent a rogue authority from
8216 double-voting on any consensus directory parameter. Previously,
8217 authorities would crash in this case if the total number of
8218 votes for any parameter exceeded the number of active voters,
8219 but would let it pass otherwise. Partially fixes bug 5786; bugfix
8221 - When computing weight parameters, behave more robustly in the
8222 presence of a bad bwweightscale value. Previously, the authorities
8223 would crash if they agreed on a sufficiently broken weight_scale
8224 value; now, they use a reasonable default and carry on. Fixes the
8225 rest of bug 5786; bugfix on 0.2.2.17-alpha.
8226 - If authorities are unable to get a v2 consensus document from other
8227 directory authorities, they no longer fall back to fetching
8228 them from regular directory caches. Fixes bug 5635; bugfix on
8229 0.2.2.26-beta, where routers stopped downloading v2 consensus
8232 o Major bugfixes (relays):
8233 - Fix a bug handling SENDME cells on nonexistent streams that could
8234 result in bizarre window values. Report and patch contributed
8235 pseudonymously. Fixes part of bug 6271. This bug was introduced
8236 before the first Tor release, in svn commit r152.
8237 - Don't update the AccountingSoftLimitHitAt state file entry whenever
8238 tor gets started. This prevents a wrong average bandwidth
8239 estimate, which would cause relays to always start a new accounting
8240 interval at the earliest possible moment. Fixes bug 2003; bugfix
8241 on 0.2.2.7-alpha. Reported by Bryon Eldridge, who also helped
8242 immensely in tracking this bug down.
8243 - Fix a possible crash bug when checking for deactivated circuits
8244 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
8245 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
8246 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
8247 connections. This change should allow busy exit relays to stop
8248 running out of available sockets as quickly. Fixes bug 4950;
8249 bugfix on 0.2.2.26-beta.
8251 o Major bugfixes (blocking resistance):
8252 - Bridges no longer include their address in NETINFO cells on outgoing
8253 OR connections, to allow them to blend in better with clients.
8254 Removes another avenue for enumerating bridges. Reported by
8255 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
8256 cells were introduced.
8257 - Warn the user when HTTPProxy, but no other proxy type, is
8258 configured. This can cause surprising behavior: it doesn't send
8259 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
8260 directory traffic only. Resolves ticket 4663.
8262 o Major bugfixes (hidden services):
8263 - Improve hidden service robustness: when an attempt to connect to
8264 a hidden service ends, be willing to refetch its hidden service
8265 descriptors from each of the HSDir relays responsible for them
8266 immediately. Previously, we would not consider refetching the
8267 service's descriptors from each HSDir for 15 minutes after the last
8268 fetch, which was inconvenient if the hidden service was not running
8269 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
8270 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
8271 They used to check that the timestamp was within 30 minutes
8272 of their system clock, so they could cap the size of their
8273 replay-detection cache, but that approach unnecessarily refused
8274 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
8275 the v3 intro-point protocol (the first one which sent a timestamp
8276 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
8277 - When one of a hidden service's introduction points appears to be
8278 unreachable, stop trying it. Previously, we would keep trying
8279 to build circuits to the introduction point until we lost the
8280 descriptor, usually because the user gave up and restarted Tor.
8281 Fixes part of bug 3825.
8283 o Changes to default torrc file:
8284 - Stop listing "socksport 9050" in torrc.sample. We open a socks
8285 port on 9050 by default anyway, so this should not change anything
8287 - Stop mentioning the deprecated *ListenAddress options in
8288 torrc.sample. Fixes bug 5438.
8289 - Document unit of bandwidth-related options in sample torrc.
8291 - Fix broken URLs in the sample torrc file, and tell readers about
8292 the OutboundBindAddress, ExitPolicyRejectPrivate, and
8293 PublishServerDescriptor options. Addresses bug 4652.
8295 o Minor features (directory authorities):
8296 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
8297 change when the authority is deciding whether to accept a newly
8298 uploaded descriptor. Implements ticket 6423.
8299 - Directory authorities are now a little more lenient at accepting
8300 older router descriptors, or newer router descriptors that don't
8301 make big changes. This should help ameliorate past and future
8302 issues where routers think they have uploaded valid descriptors,
8303 but the authorities don't think so. Fix for ticket 2479.
8304 - Authority operators can now vote for all relays in a given
8305 set of countries to be BadDir/BadExit/Invalid/Rejected.
8306 - Provide two consensus parameters (FastFlagMinThreshold and
8307 FastFlagMaxThreshold) to control the range of allowable bandwidths
8308 for the Fast directory flag. These allow authorities to run
8309 experiments on appropriate requirements for being a "Fast" node.
8310 The AuthDirFastGuarantee config value still applies. Implements
8313 o Minor features (bridges / bridge authorities):
8314 - Make bridge SSL certificates a bit more stealthy by using random
8315 serial numbers, in the same fashion as OpenSSL when generating
8316 self-signed certificates. Implements ticket 4584.
8317 - Tag a bridge's descriptor as "never to be sent unencrypted".
8318 This shouldn't matter, since bridges don't open non-anonymous
8319 connections to the bridge authority and don't allow unencrypted
8320 directory connections from clients, but we might as well make
8321 sure. Closes bug 5139.
8322 - The Bridge Authority now writes statistics on how many bridge
8323 descriptors it gave out in total, and how many unique descriptors
8324 it gave out. It also lists how often the most and least commonly
8325 fetched descriptors were given out, as well as the median and
8326 25th/75th percentile. Implements tickets 4200 and 4294.
8328 o Minor features (IPv6):
8329 - Make the code that clients use to detect an address change be
8330 IPv6-aware, so that it won't fill clients' logs with error
8331 messages when trying to get the IPv4 address of an IPv6
8332 connection. Implements ticket 5537.
8333 - Relays now understand an IPv6 address when they get one from a
8334 directory server. Resolves ticket 4875.
8336 o Minor features (hidden services):
8337 - Expire old or over-used hidden service introduction points.
8338 Required by fix for bug 3460.
8339 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
8340 public key replay-detection cache from 60 minutes to 5 minutes. This
8341 replay-detection cache is now used only to detect multiple
8342 INTRODUCE2 cells specifying the same rendezvous point, so we can
8343 avoid launching multiple simultaneous attempts to connect to it.
8344 - When a hidden service's introduction point times out, consider
8345 trying it again during the next attempt to connect to the
8346 HS. Previously, we would not try it again unless a newly fetched
8347 descriptor contained it. Required by fixes for bugs 1297 and 3825.
8349 o Minor features (relays):
8350 - Relays now include a reason for regenerating their descriptors
8351 in an HTTP header when uploading to the authorities. This will
8352 make it easier to debug descriptor-upload issues in the future.
8353 - Turn on directory request statistics by default and include them in
8354 extra-info descriptors. Don't break if we have no GeoIP database.
8355 - Replace files in stats/ rather than appending to them. Now that we
8356 include statistics in extra-info descriptors, it makes no sense to
8357 keep old statistics forever. Implements ticket 2930.
8358 - Relays that set "ConnDirectionStatistics 1" write statistics on the
8359 bidirectional use of connections to disk every 24 hours.
8360 - Add a GeoIP file digest to the extra-info descriptor. Implements
8363 o Minor features (new config options):
8364 - New config option "DynamicDHGroups" (disabled by default) provides
8365 each bridge with a unique prime DH modulus to be used during
8366 SSL handshakes. This option attempts to help against censors
8367 who might use the Apache DH modulus as a static identifier for
8368 bridges. Addresses ticket 4548.
8369 - New config option "DisableDebuggerAttachment" (on by default)
8370 to prevent basic debugging attachment attempts by other processes.
8371 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
8372 - Ordinarily, Tor does not count traffic from private addresses (like
8373 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
8374 There is now a new option, CountPrivateBandwidth, to disable this
8375 behavior. Patch from Daniel Cagara.
8377 o Minor features (different behavior for old config options):
8378 - Allow MapAddress directives to specify matches against super-domains,
8379 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
8380 Implements issue 933.
8381 - Don't disable the DirPort when we cannot exceed our AccountingMax
8382 limit during this interval because the effective bandwidthrate is
8383 low enough. This is useful in a situation where AccountMax is only
8384 used as an additional safeguard or to provide statistics.
8385 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
8386 implements ticket 3439.
8387 - When configuring a large set of nodes in EntryNodes, and there are
8388 enough of them listed as Guard so that we don't need to consider
8389 the non-guard entries, prefer the ones listed with the Guard flag.
8390 - If you set the NumCPUs option to 0, Tor will now try to detect how
8391 many CPUs you have. This is the new default behavior.
8392 - The NodeFamily option -- which let you declare that you want to
8393 consider nodes to be part of a family whether they list themselves
8394 that way or not -- now allows IP address ranges and country codes.
8396 o Minor features (new command-line config behavior):
8397 - Slightly change behavior of "list" options (that is, config
8398 options that can appear more than once) when they appear both in
8399 torrc and on the command line. Previously, the command-line options
8400 would be appended to the ones from torrc. Now, the command-line
8401 options override the torrc options entirely. This new behavior
8402 allows the user to override list options (like exit policies and
8403 ports to listen on) from the command line, rather than simply
8404 appending to the list.
8405 - You can get the old (appending) command-line behavior for "list"
8406 options by prefixing the option name with a "+".
8407 - You can remove all the values for a "list" option from the command
8408 line without adding any new ones by prefixing the option name
8411 o Minor features (controller, new events):
8412 - Extend the control protocol to report flags that control a circuit's
8413 path selection in CIRC events and in replies to 'GETINFO
8414 circuit-status'. Implements part of ticket 2411.
8415 - Extend the control protocol to report the hidden service address
8416 and current state of a hidden-service-related circuit in CIRC
8417 events and in replies to 'GETINFO circuit-status'. Implements part
8419 - Include the creation time of a circuit in CIRC and CIRC2
8420 control-port events and the list produced by the 'GETINFO
8421 circuit-status' control-port command.
8422 - Add a new CONF_CHANGED event so that controllers can be notified
8423 of any configuration changes made by other controllers, or by the
8424 user. Implements ticket 1692.
8425 - Add a new SIGNAL event to the controller interface so that
8426 controllers can be notified when Tor handles a signal. Resolves
8427 issue 1955. Patch by John Brooks.
8429 o Minor features (controller, new getinfo options):
8430 - Expose our view of whether we have gone dormant to the controller,
8431 via a new "GETINFO dormant" value. Torbutton and other controllers
8432 can use this to avoid doing periodic requests through Tor while
8433 it's dormant (bug 4718). Resolves ticket 5954.
8434 - Add a new GETINFO option to get total bytes read and written. Patch
8435 from pipe, revised by atagar. Resolves ticket 2345.
8436 - Implement new GETINFO controller fields to provide information about
8437 the Tor process's pid, euid, username, and resource limits.
8439 o Minor features (controller, other):
8440 - Allow controllers to request an event notification whenever a
8441 circuit is cannibalized or its purpose is changed. Implements
8442 part of ticket 3457.
8443 - Use absolute path names when reporting the torrc filename in the
8444 control protocol, so a controller can more easily find the torrc
8445 file. Resolves bug 1101.
8446 - When reporting the path to the cookie file to the controller,
8447 give an absolute path. Resolves ticket 4881.
8449 o Minor features (log messages):
8450 - Add more information to a log statement that might help track down
8451 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
8452 non-IP address" messages (or any Bug messages, for that matter!),
8453 please let us know about it.
8454 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
8455 EntryNodes will have no effect. Resolves issue 2571.
8456 - Try to make the introductory warning message that Tor prints on
8457 startup more useful for actually finding help and information.
8458 Resolves ticket 2474.
8459 - When the system call to create a listener socket fails, log the
8460 error message explaining why. This may help diagnose bug 4027.
8462 o Minor features (other):
8463 - When we fail to initialize Libevent, retry with IOCP disabled so we
8464 don't need to turn on multi-threading support in Libevent, which in
8465 turn requires a working socketpair(). This is a workaround for bug
8466 4457, which affects Libevent versions from 2.0.1-alpha through
8468 - When starting as root and then changing our UID via the User
8469 control option, and we have a ControlSocket configured, make sure
8470 that the ControlSocket is owned by the same account that Tor will
8471 run under. Implements ticket 3421; fix by Jérémy Bobbio.
8472 - Accept attempts to include a password authenticator in the
8473 handshake, as supported by SOCKS5. This handles SOCKS clients that
8474 don't know how to omit a password when authenticating. Resolves
8476 - Check for and recover from inconsistency in the microdescriptor
8477 cache. This will make it harder for us to accidentally free a
8478 microdescriptor without removing it from the appropriate data
8479 structures. Fixes issue 3135; issue noted by "wanoskarnet".
8480 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
8482 o Minor bugfixes (code security):
8483 - Prevent a null-pointer dereference when receiving a data cell
8484 for a nonexistent stream when the circuit in question has an
8485 empty deliver window. We don't believe this is triggerable,
8486 since we don't currently allow deliver windows to become empty,
8487 but the logic is tricky enough that it's better to make the code
8488 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
8489 - Fix a (harmless) integer overflow in cell statistics reported by
8490 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
8491 - Fix our implementation of crypto_random_hostname() so it can't
8492 overflow on ridiculously large inputs. (No Tor version has ever
8493 provided this kind of bad inputs, but let's be correct in depth.)
8494 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
8495 - Add a (probably redundant) memory clear between iterations of
8496 the router status voting loop, to prevent future coding errors
8497 where data might leak between iterations of the loop. Resolves
8500 o Minor bugfixes (wrapper functions):
8501 - Abort if tor_vasprintf() fails in connection_printf_to_buf() (a
8502 utility function used in the control-port code). This shouldn't
8503 ever happen unless Tor is completely out of memory, but if it did
8504 happen and Tor somehow recovered from it, Tor could have sent a log
8505 message to a control port in the middle of a reply to a controller
8506 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
8507 - Fix some (not actually triggerable) buffer size checks in usage of
8508 tor_inet_ntop(). Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
8510 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
8511 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
8512 - Enforce correct return behavior of tor_vsscanf() when the '%%'
8513 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
8514 - Make our replacement implementation of strtok_r() compatible with
8515 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
8516 bugfix on 0.2.2.1-alpha.
8517 - Find more places in the code that should have been testing for
8518 invalid sockets using the SOCKET_OK macro. Required for a fix
8519 for bug 4533. Bugfix on 0.2.2.28-beta.
8521 o Minor bugfixes (code correctness):
8522 - Check return value of fputs() when writing authority certificate
8523 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
8524 - When building Tor on Windows with -DUNICODE (not default), ensure
8525 that error messages, filenames, and DNS server names are always
8526 NUL-terminated when we convert them to a single-byte encoding.
8527 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
8528 - Fix a memory leak when trying to launch a DNS request when the
8529 nameservers are unconfigurable. Fixes bug 5916; bugfix on Tor
8531 - Correct file sizes when reading binary files on Cygwin, to avoid
8532 a bug where Tor would fail to read its state file. Fixes bug 6844;
8533 bugfix on 0.1.2.7-alpha.
8534 - Make sure to set *socket_error in all error cases in
8535 connection_connect(), so it can't produce a warning about
8536 errno being zero from errno_to_orconn_end_reason(). Bugfix on
8537 0.2.1.1-alpha; resolves ticket 6028.
8538 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
8539 bug 4532; found by "troll_un".
8541 o Minor bugfixes (clients):
8542 - Allow one-hop directory-fetching circuits the full "circuit build
8543 timeout" period, rather than just half of it, before failing them
8544 and marking the relay down. This fix should help reduce cases where
8545 clients declare relays (or worse, bridges) unreachable because
8546 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
8547 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
8549 - Ensure we don't cannibalize circuits that are longer than three hops
8550 already, so we don't end up making circuits with 5 or more
8551 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
8552 0.1.0.1-rc which introduced cannibalization.
8554 o Minor bugfixes (relays):
8555 - Don't publish a new relay descriptor when we reload our onion key,
8556 unless the onion key has actually changed. Fixes bug 3263 and
8557 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
8558 - When relays refuse a "create" cell because their queue of pending
8559 create cells is too big (typically because their cpu can't keep up
8560 with the arrival rate), send back reason "resource limit" rather
8561 than reason "internal", so network measurement scripts can get a
8562 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
8563 - Exit nodes don't need to fetch certificates for authorities that
8564 they don't recognize; only directory authorities, bridges,
8565 and caches need to do that. Fixes part of bug 2297; bugfix on
8568 o Minor bugfixes (directory authority / mirrors):
8569 - Avoid O(n^2) performance characteristics when parsing a large
8570 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
8571 - Authorities no longer include any router in their microdescriptor
8572 consensuses for which they couldn't generate or agree on a
8573 microdescriptor. Fixes the second piece of bug 6404; fix on
8575 - When checking for requested signatures on the latest consensus
8576 before serving it to a client, make sure to check the right
8577 consensus flavor. Bugfix on 0.2.2.6-alpha.
8578 - Fix an edge case where TestingTorNetwork is set but the authorities
8579 and relays all have an uptime of zero, so the private Tor network
8580 could briefly lack support for hidden services. Fixes bug 3886;
8581 bugfix on 0.2.2.18-alpha.
8582 - Directory caches no longer refuse to clean out descriptors because
8583 of missing v2 networkstatus documents, unless they're configured
8584 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
8585 0.2.2.26-beta. Patch by Daniel Bryg.
8586 - Don't serve or accept v2 hidden service descriptors over a relay's
8587 DirPort. It's never correct to do so, and disabling it might
8588 make it more annoying to exploit any bugs that turn up in the
8589 descriptor-parsing code. Fixes bug 7149.
8591 o Minor bugfixes (hidden services, client-side):
8592 - Assert that hidden-service-related operations are not performed
8593 using single-hop circuits. Previously, Tor would assert that
8594 client-side streams are not attached to single-hop circuits,
8595 but not that other sensitive operations on the client and service
8596 side are not performed using single-hop circuits. Fixes bug 3332;
8598 - Avoid undefined behavior when parsing the list of supported
8599 rendezvous/introduction protocols in a hidden service descriptor.
8600 Previously, Tor would have confused (as-yet-unused) protocol version
8601 numbers greater than 32 with lower ones on many platforms. Fixes
8602 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
8603 - Don't close hidden service client circuits which have almost
8604 finished connecting to their destination when they reach
8605 the normal circuit-build timeout. Previously, we would close
8606 introduction circuits which are waiting for an acknowledgement
8607 from the introduction point, and rendezvous circuits which have
8608 been specified in an INTRODUCE1 cell sent to a hidden service,
8609 after the normal CBT. Now, we mark them as 'timed out', and launch
8610 another rendezvous attempt in parallel. This behavior change can
8611 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
8612 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
8614 o Minor bugfixes (hidden services, service-side):
8615 - Don't close hidden-service-side rendezvous circuits when they
8616 reach the normal circuit-build timeout. This behavior change can
8617 be disabled using the new
8618 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
8619 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
8620 - Don't launch more than 10 service-side introduction-point circuits
8621 for a hidden service in five minutes. Previously, we would consider
8622 launching more introduction-point circuits if at least one second
8623 had passed without any introduction-point circuits failing. Fixes
8624 bug 4607; bugfix on 0.0.7pre1.
8626 o Minor bugfixes (config option behavior):
8627 - If the user tries to set MyFamily on a bridge, refuse to
8628 do so, and warn about the security implications. Fixes bug 4657;
8629 bugfix on 0.2.0.3-alpha.
8630 - The "--quiet" and "--hush" options now apply not only to Tor's
8631 behavior before logs are configured, but also to Tor's behavior in
8632 the absense of configured logs. Fixes bug 3550; bugfix on
8634 - Change the AllowDotExit rules so they should actually work.
8635 We now enforce AllowDotExit only immediately after receiving an
8636 address via SOCKS or DNSPort: other sources are free to provide
8637 .exit addresses after the resolution occurs. Fixes bug 3940;
8638 bugfix on 0.2.2.1-alpha.
8639 - Make "LearnCircuitBuildTimeout 0" work more reliably. Specifically,
8640 don't depend on the consensus parameters or compute adaptive
8641 timeouts when it is disabled. Fixes bug 5049; bugfix on
8643 - After we pick a directory mirror, we would refuse to use it if
8644 it's in our ExcludeExitNodes list, resulting in mysterious failures
8645 to bootstrap for people who just wanted to avoid exiting from
8646 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
8647 - When told to add a bridge with the same digest as a preexisting
8648 bridge but a different addr:port, change the addr:port as
8649 requested. Previously we would not notice the change. Fixes half
8650 of bug 5603; fix on 0.2.2.26-beta.
8652 o Minor bugfixes (controller):
8653 - Allow manual 'authenticate' commands to the controller interface
8654 from netcat (nc) as well as telnet. We were rejecting them because
8655 they didn't come with the expected whitespace at the end of the
8656 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
8657 - Report a real bootstrap problem to the controller on router
8658 identity mismatch. Previously we just said "foo", which probably
8659 made a lot of sense at the time. Fixes bug 4169; bugfix on
8661 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
8662 option is set to 0 (which Vidalia version 0.2.16 now does when
8663 a SAVECONF attempt fails), perform other actions that SIGHUP
8664 usually causes (like reopening the logs). Fixes bug 5095; bugfix
8666 - Correctly handle checking the permissions on the parent
8667 directory of a control socket in the root directory. Bug found
8668 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
8670 - End AUTHCHALLENGE error messages (in the control protocol) with
8671 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36.
8673 o Minor bugfixes (network reading/writing):
8674 - Disable writing on marked-for-close connections when they are
8675 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
8676 bug 5263; bugfix on 0.0.2pre13, where we first added a special
8677 case for flushing marked connections.
8678 - Make sure that there are no unhandled pending TLS errors before
8679 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
8680 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
8681 Bugfix on 0.1.0.5-rc; fixes bug 4528.
8682 - Detect SSL handshake even when the initial attempt to write the
8683 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
8684 - If the client fails to set a reasonable set of ciphersuites
8685 during its v2 handshake renegotiation, allow the renegotiation to
8686 continue nevertheless (i.e. send all the required certificates).
8687 Fixes bug 4591; bugfix on 0.2.0.20-rc.
8689 o Minor bugfixes (other):
8690 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
8691 resource exhaustion, so that clients can adjust their load to
8692 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
8693 started using END_STREAM_REASON_RESOURCELIMIT.
8694 - Don't check for whether the address we're using for outbound
8695 connections has changed until after the outbound connection has
8696 completed. On Windows, getsockname() doesn't succeed until the
8697 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
8698 - Don't hold a Windows file handle open for every file mapping;
8699 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
8701 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
8702 bugfix on 0.2.1.10-alpha.
8703 - If we fail to write a microdescriptor to the disk cache, do not
8704 continue replacing the old microdescriptor file. Fixes bug 2954;
8705 bugfix on 0.2.2.6-alpha.
8707 o Minor bugfixes (log messages, path selection):
8708 - Downgrade "set buildtimeout to low value" messages to "info"
8709 severity; they were never an actual problem, there was never
8710 anything reasonable to do about them, and they tended to spam logs
8711 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
8712 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
8713 more information to it, so that we can track it down in case it
8714 returns again. Mitigates bug 5235.
8715 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
8716 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
8717 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
8718 - Issue a log message if a guard completes less than 40% of your
8719 circuits. Threshold is configurable by torrc option
8720 PathBiasNoticeRate and consensus parameter pb_noticepct. There is
8721 additional, off-by-default code to disable guards which fail too
8722 many circuits. Addresses ticket 5458.
8724 o Minor bugfixes (log messages, client):
8725 - Downgrade "Got a certificate, but we already have it" log messages
8726 from warning to info, except when we're a dirauth. Fixes bug 5238;
8727 bugfix on 0.2.1.7-alpha.
8728 - Fix the log message describing how we work around discovering
8729 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
8730 4837; bugfix on 0.2.2.9-alpha.
8731 - When logging about a disallowed .exit name, do not also call it
8732 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
8733 - Fix a log message suggesting that people contact a non-existent
8734 email address. Fixes bug 3448.
8735 - Rephrase the log message emitted if the TestSocks check is
8736 successful. Patch from Fabian Keil; fixes bug 4094.
8737 - Log (at debug level) whenever a circuit's purpose is changed.
8738 - Log SSL state transitions at log level DEBUG, log domain
8739 HANDSHAKE. This can be useful for debugging censorship events.
8740 Implements ticket 3264.
8741 - We now log which torrc file we're using on startup. Implements
8743 - Rate-limit log messages when asked to connect anonymously to
8744 a private address. When these hit, they tended to hit fast and
8745 often. Also, don't bother trying to connect to addresses that we
8746 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
8747 reply makes us think we have been lied to, even when the address the
8748 client tried to connect to was "localhost." Resolves ticket 2822.
8750 o Minor bugfixes (log messages, non-client):
8751 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
8752 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
8753 - Don't log that we have "decided to publish new relay descriptor"
8754 unless we are actually publishing a descriptor. Fixes bug 3942;
8755 bugfix on 0.2.2.28-beta.
8756 - Log which authority we're missing votes from when we go to fetch
8757 them from the other auths.
8758 - Replace "Sending publish request" log messages with "Launching
8759 upload", so that they no longer confusingly imply that we're
8760 sending something to a directory we might not even be connected
8761 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
8762 - Warn when Tor is configured to use accounting in a way that can
8763 link a hidden service to some other hidden service or public
8764 address. Resolves ticket 6490.
8765 - Fix a minor formatting issue in one of tor-gencert's error messages.
8769 - Update to the latest version of the tinytest unit testing framework.
8770 This includes a couple of bugfixes that can be relevant for
8771 running forked unit tests on Windows, and removes all reserved
8773 - Avoid a false positive in the util/threads unit test by increasing
8774 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
8775 - Make it possible to set the TestingTorNetwork configuration
8776 option using AlternateDirAuthority and AlternateBridgeAuthority
8777 as an alternative to setting DirServer. Addresses ticket 6377.
8778 - Add a unit test for the environment_variable_names_equal() function.
8779 - A wide variety of new unit tests by Esteban Manchado Velázquez.
8780 - Numerous new unit tests for functions in util.c and address.c by
8782 - The long-disabled benchmark tests are now split into their own
8783 ./src/test/bench binary.
8784 - The benchmark tests can now use more accurate timers than
8785 gettimeofday() when such timers are available.
8786 - Use tt_assert(), not tor_assert(), for checking for test failures.
8787 This makes the unit tests more able to go on in the event that
8790 o Build improvements:
8791 - Use the dead_strip option when building Tor on OS X. This reduces
8792 binary size by almost 19% when linking openssl and libevent
8793 statically, which we do for Tor Browser Bundle.
8794 - Provide a better error message about possible OSX Asciidoc failure
8795 reasons. Fixes bug 6436.
8796 - Detect attempts to build Tor on (as yet hypothetical) versions
8797 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
8798 fix for bug 4533. Bugfix on 0.2.2.28-beta.
8799 - On Windows, we now define the _WIN32_WINNT macros only if they
8800 are not already defined. This lets the person building Tor decide,
8801 if they want, to require a later version of Windows.
8802 - Our autogen.sh script now uses autoreconf to launch autoconf,
8803 automake, and so on. This is more robust against some of the failure
8804 modes associated with running the autotools pieces on their own.
8805 - Running "make version" now displays the version of Tor that
8806 we're about to build. Idea from katmagic; resolves issue 4400.
8807 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
8808 on 0.2.2.4-alpha; fixes bug 3427.
8809 - New --enable-static-tor configure option for building Tor as
8810 statically as possible. Idea, general hackery and thoughts from
8811 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
8813 - Limited, experimental support for building with nmake and MSVC.
8815 o Build requirements:
8816 - Building Tor with bufferevent support now requires Libevent
8817 2.0.13-stable or later. Previous versions of Libevent had bugs in
8818 SSL-related bufferevents and related issues that would make Tor
8819 work badly with bufferevents. Requiring 2.0.13-stable also allows
8820 Tor with bufferevents to take advantage of Libevent APIs
8821 introduced after 2.0.8-rc.
8822 - Our build system requires automake 1.6 or later to create the
8823 Makefile.in files. Previously, you could have used 1.4.
8824 This only affects developers and people building Tor from git;
8825 people who build Tor from the source distribution without changing
8826 the Makefile.am files should be fine.
8827 - Detect when we try to build on a platform that doesn't define
8828 AF_UNSPEC to 0. We don't work there, so refuse to compile.
8830 o Build fixes (compile/link):
8831 - Format more doubles with %f, not %lf. Patch from grarpamp to make
8832 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
8834 - When building with --enable-static-tor on OpenBSD, do not
8835 erroneously attempt to link -lrt. Fixes bug 5103.
8836 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
8837 that IPv6 stuff will compile on MSVC, and compilation issues
8838 will be easier to track down. Fixes bug 5861.
8839 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
8840 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
8841 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
8842 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
8844 o Build fixes (other):
8845 - Use the _WIN32 macro throughout our code to detect Windows.
8846 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
8848 - Properly handle the case where the build-tree is not the same
8849 as the source tree when generating src/common/common_sha1.i,
8850 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
8851 bugfix on 0.2.0.1-alpha.
8852 - During configure, search for library containing cos function as
8853 libm lives in libcore on some platforms (BeOS/Haiku). Linking
8854 against libm was hard-coded before. Fixes the first part of bug
8855 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
8857 - Prevent a false positive from the check-spaces script, by disabling
8858 the "whitespace between function name and (" check for functions
8861 o Packaging (RPM) changes:
8862 - Update our default RPM spec files to work with mock and rpmbuild
8863 on RHEL/Fedora. They have an updated set of dependencies and
8864 conflicts, a fix for an ancient typo when creating the "_tor"
8865 user, and better instructions. Thanks to Ondrej Mikle for the
8866 patch series. Fixes bug 6043.
8867 - On OpenSUSE, create the /var/run/tor directory on startup if it
8868 is not already created. Patch from Andreas Stieger. Fixes bug 2573.
8870 o Code refactoring (safety):
8871 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
8872 10 lines. Also, don't nest them. Doing so in the past has
8873 led to hard-to-debug code. The new style is to use the
8874 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
8875 - Use macros to indicate OpenSSL versions, so we don't need to worry
8876 about accidental hexadecimal bit shifts.
8877 - Use tor_sscanf() in place of scanf() in more places through the
8878 code. This makes us a little more locale-independent, and
8879 should help shut up code-analysis tools that can't tell
8880 a safe sscanf string from a dangerous one.
8881 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
8882 - Use the smartlist_add_asprintf() alias more consistently.
8884 o Code refactoring (consolidate):
8885 - A major revision to our internal node-selecting and listing logic.
8886 Tor already had at least two major ways to look at the question of
8887 "which Tor servers do we know about": a list of router descriptors,
8888 and a list of entries in the current consensus. With
8889 microdescriptors, we're adding a third. Having so many systems
8890 without an abstraction layer over them was hurting the codebase.
8891 Now, we have a new "node_t" abstraction that presents a consistent
8892 interface to a client's view of a Tor node, and holds (nearly) all
8893 of the mutable state formerly in routerinfo_t and routerstatus_t.
8894 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
8895 Libevent's notion of cached time when possible.
8896 - Remove duplicate code for invoking getrlimit() from control.c.
8897 - Use OpenSSL's built-in SSL_state_string_long() instead of our
8898 own homebrewed ssl_state_to_string() replacement. Patch from
8899 Emile Snyder. Fixes bug 4653.
8900 - Change the symmetric cipher interface so that creating and
8901 initializing a stream cipher are no longer separate functions.
8903 o Code refactoring (separate):
8904 - Make a new "entry connection" struct as an internal subtype of "edge
8905 connection", to simplify the code and make exit connections smaller.
8906 - Split connection_about_to_close() into separate functions for each
8908 - Rewrite the listener-selection logic so that parsing which ports
8909 we want to listen on is now separate from binding to the ports
8912 o Code refactoring (name changes):
8913 - Rename a handful of old identifiers, mostly related to crypto
8914 structures and crypto functions. By convention, our "create an
8915 object" functions are called "type_new()", our "free an object"
8916 functions are called "type_free()", and our types indicate that
8917 they are types only with a final "_t". But a handful of older
8918 types and functions broke these rules, with function names like
8919 "type_create" or "subsystem_op_type", or with type names like
8921 - Rename Tor functions that turn strings into addresses, so that
8922 "parse" indicates that no hostname resolution occurs, and
8923 "lookup" indicates that hostname resolution may occur. This
8924 should help prevent mistakes in the future. Fixes bug 3512.
8925 - Use the name "CERTS" consistently to refer to the new cell type;
8926 we were calling it CERT in some places and CERTS in others.
8927 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
8928 invalid value, rather than just -1.
8929 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
8930 can pick them up when the tests aren't disabled. Bugfix on
8931 0.2.2.4-alpha which introduced tinytest.
8933 o Code refactoring (other):
8934 - Defensively refactor rend_mid_rendezvous() so that protocol
8935 violations and length checks happen in the beginning. Fixes
8937 - Remove the pure attribute from all functions that used it
8938 previously. In many cases we assigned it incorrectly, because the
8939 functions might assert or call impure functions, and we don't have
8940 evidence that keeping the pure attribute is worthwhile. Implements
8941 changes suggested in ticket 4421.
8942 - Move the replay-detection cache for the RSA-encrypted parts of
8943 INTRODUCE2 cells to the introduction point data structures.
8944 Previously, we would use one replay-detection cache per hidden
8945 service. Required by fix for bug 3460.
8946 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
8947 no longer link against Libevent: they never used it, but
8948 our library structure used to force them to link it.
8950 o Removed features and files:
8951 - Remove all internal support for unpadded RSA. We never used it, and
8952 it would be a bad idea to start.
8953 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
8955 - Remove some redundant #include directives throughout the code.
8956 Patch from Andrea Gelmini.
8957 - Remove some old code to remember statistics about which descriptors
8958 we've served as a directory mirror. The feature wasn't used and
8959 is outdated now that microdescriptors are around.
8960 - Remove some old code to work around even older versions of Tor that
8961 used forked processes to handle DNS requests. Such versions of Tor
8962 are no longer in use as relays.
8963 - The "torify" script no longer supports the "tsocks" socksifier
8964 tool, since tsocks doesn't support DNS and UDP right for Tor.
8965 Everyone should be using torsocks instead. Fixes bugs 3530 and
8966 5180. Based on a patch by "ugh".
8967 - Remove the torrc.bridge file: we don't use it for anything, and
8968 it had become badly desynchronized from torrc.sample. Resolves
8972 - Begin a doc/state-contents.txt file to explain the contents of
8973 the Tor state file. Fixes bug 2987.
8974 - Clarify the documentation for the Alternate*Authority options.
8976 - Document the --defaults-torrc option, and the new semantics for
8977 overriding, extending, and clearing lists of options. Closes
8979 - Add missing man page documentation for consensus and microdesc
8980 files. Resolves ticket 6732.
8981 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
8983 o Documentation fixes:
8984 - Improve the manual's documentation for the NT Service command-line
8985 options. Addresses ticket 3964.
8986 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
8987 - Document the changes to the ORPort and DirPort options, and the
8988 fact that {OR/Dir}ListenAddress is now unnecessary (and
8989 therefore deprecated). Resolves ticket 5597.
8990 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
8991 - Clarify that hidden services are TCP only. Fixes bug 6024.
8994 Changes in version 0.2.2.39 - 2012-09-11
8995 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
8999 - Fix an assertion failure in tor_timegm() that could be triggered
9000 by a badly formatted directory object. Bug found by fuzzing with
9001 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
9002 - Do not crash when comparing an address with port value 0 to an
9003 address policy. This bug could have been used to cause a remote
9004 assertion failure by or against directory authorities, or to
9005 allow some applications to crash clients. Fixes bug 6690; bugfix
9009 Changes in version 0.2.2.38 - 2012-08-12
9010 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
9011 attack that could in theory leak path information.
9014 - Avoid an uninitialized memory read when reading a vote or consensus
9015 document that has an unrecognized flavor name. This read could
9016 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
9017 - Try to leak less information about what relays a client is
9018 choosing to a side-channel attacker. Previously, a Tor client would
9019 stop iterating through the list of available relays as soon as it
9020 had chosen one, thus finishing a little earlier when it picked
9021 a router earlier in the list. If an attacker can recover this
9022 timing information (nontrivial but not proven to be impossible),
9023 they could learn some coarse-grained information about which relays
9024 a client was picking (middle nodes in particular are likelier to
9025 be affected than exits). The timing attack might be mitigated by
9026 other factors (see bug 6537 for some discussion), but it's best
9027 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
9030 Changes in version 0.2.2.37 - 2012-06-06
9031 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
9032 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
9036 - Work around a bug in OpenSSL that broke renegotiation with TLS
9037 1.1 and TLS 1.2. Without this workaround, all attempts to speak
9038 the v2 Tor connection protocol when both sides were using OpenSSL
9039 1.0.1 would fail. Resolves ticket 6033.
9040 - When waiting for a client to renegotiate, don't allow it to add
9041 any bytes to the input buffer. This fixes a potential DoS issue.
9042 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
9043 - Fix an edge case where if we fetch or publish a hidden service
9044 descriptor, we might build a 4-hop circuit and then use that circuit
9045 for exiting afterwards -- even if the new last hop doesn't obey our
9046 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
9049 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
9050 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
9053 - Tell GCC and Clang to check for any errors in format strings passed
9054 to the tor_v*(print|scan)f functions.
9057 Changes in version 0.2.2.36 - 2012-05-24
9058 Tor 0.2.2.36 updates the addresses for two of the eight directory
9059 authorities, fixes some potential anonymity and security issues,
9060 and fixes several crash bugs.
9062 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
9063 known flaws, and nobody should be using them. You should upgrade. If
9064 you're using a Linux or BSD and its packages are obsolete, stop using
9065 those packages and upgrade anyway.
9067 o Directory authority changes:
9068 - Change IP address for maatuska (v3 directory authority).
9069 - Change IP address for ides (v3 directory authority), and rename
9073 - When building or running with any version of OpenSSL earlier
9074 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
9075 versions have a bug (CVE-2011-4576) in which their block cipher
9076 padding includes uninitialized data, potentially leaking sensitive
9077 information to any peer with whom they make a SSLv3 connection. Tor
9078 does not use SSL v3 by default, but a hostile client or server
9079 could force an SSLv3 connection in order to gain information that
9080 they shouldn't have been able to get. The best solution here is to
9081 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
9082 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
9083 to make sure that the bug can't happen.
9084 - Never use a bridge or a controller-supplied node as an exit, even
9085 if its exit policy allows it. Found by wanoskarnet. Fixes bug
9086 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
9087 and 0.2.0.3-alpha (for bridge-purpose descriptors).
9088 - Only build circuits if we have a sufficient threshold of the total
9089 descriptors that are marked in the consensus with the "Exit"
9090 flag. This mitigates an attack proposed by wanoskarnet, in which
9091 all of a client's bridges collude to restrict the exit nodes that
9092 the client knows about. Fixes bug 5343.
9093 - Provide controllers with a safer way to implement the cookie
9094 authentication mechanism. With the old method, if another locally
9095 running program could convince a controller that it was the Tor
9096 process, then that program could trick the controller into telling
9097 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
9098 authentication method uses a challenge-response approach to prevent
9099 this attack. Fixes bug 5185; implements proposal 193.
9102 - Avoid logging uninitialized data when unable to decode a hidden
9103 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
9104 - Avoid a client-side assertion failure when receiving an INTRODUCE2
9105 cell on a general purpose circuit. Fixes bug 5644; bugfix on
9107 - Fix builds when the path to sed, openssl, or sha1sum contains
9108 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
9110 - Correct our replacements for the timeradd() and timersub() functions
9111 on platforms that lack them (for example, Windows). The timersub()
9112 function is used when expiring circuits, while timeradd() is
9113 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
9114 bugfix on 0.2.2.24-alpha.
9115 - Fix the SOCKET_OK test that we use to tell when socket
9116 creation fails so that it works on Win64. Fixes part of bug 4533;
9117 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
9120 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
9121 Fixes bug 5346; bugfix on 0.0.8pre3.
9122 - Make our number-parsing functions always treat too-large values
9123 as an error, even when those values exceed the width of the
9124 underlying type. Previously, if the caller provided these
9125 functions with minima or maxima set to the extreme values of the
9126 underlying integer type, these functions would return those
9127 values on overflow rather than treating overflow as an error.
9128 Fixes part of bug 5786; bugfix on 0.0.9.
9129 - Older Linux kernels erroneously respond to strange nmap behavior
9130 by having accept() return successfully with a zero-length
9131 socket. When this happens, just close the connection. Previously,
9132 we would try harder to learn the remote address: but there was
9133 no such remote address to learn, and our method for trying to
9134 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
9135 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
9136 - Correct parsing of certain date types in parse_http_time().
9137 Without this patch, If-Modified-Since would behave
9138 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
9139 Esteban Manchado Velázques.
9140 - Change the BridgePassword feature (part of the "bridge community"
9141 design, which is not yet implemented) to use a time-independent
9142 comparison. The old behavior might have allowed an adversary
9143 to use timing to guess the BridgePassword value. Fixes bug 5543;
9144 bugfix on 0.2.0.14-alpha.
9145 - Detect and reject certain misformed escape sequences in
9146 configuration values. Previously, these values would cause us
9147 to crash if received in a torrc file or over an authenticated
9148 control port. Bug found by Esteban Manchado Velázquez, and
9149 independently by Robert Connolly from Matta Consulting who further
9150 noted that it allows a post-authentication heap overflow. Patch
9151 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
9152 bugfix on 0.2.0.16-alpha.
9153 - Fix a compile warning when using the --enable-openbsd-malloc
9154 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
9155 - During configure, detect when we're building with clang version
9156 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
9157 CFLAGS. clang doesn't support them yet.
9158 - When sending an HTTP/1.1 proxy request, include a Host header.
9159 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
9160 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
9161 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
9162 - If we hit the error case where routerlist_insert() replaces an
9163 existing (old) server descriptor, make sure to remove that
9164 server descriptor from the old_routers list. Fix related to bug
9165 1776. Bugfix on 0.2.2.18-alpha.
9167 o Minor bugfixes (documentation and log messages):
9168 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
9169 Fixes bug 4856; bugfix on Tor 0.0.6.
9170 - Update "ClientOnly" man page entry to explain that there isn't
9171 really any point to messing with it. Resolves ticket 5005.
9172 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
9173 directory authority option (introduced in Tor 0.2.2.34).
9174 - Downgrade the "We're missing a certificate" message from notice
9175 to info: people kept mistaking it for a real problem, whereas it
9176 is seldom the problem even when we are failing to bootstrap. Fixes
9177 bug 5067; bugfix on 0.2.0.10-alpha.
9178 - Correctly spell "connect" in a log message on failure to create a
9179 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
9180 - Clarify the behavior of MaxCircuitDirtiness with hidden service
9181 circuits. Fixes issue 5259.
9184 - Directory authorities now reject versions of Tor older than
9185 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
9186 inclusive. These versions accounted for only a small fraction of
9187 the Tor network, and have numerous known security issues. Resolves
9189 - Update to the May 1 2012 Maxmind GeoLite Country database.
9192 - When sending or relaying a RELAY_EARLY cell, we used to convert
9193 it to a RELAY cell if the connection was using the v1 link
9194 protocol. This was a workaround for older versions of Tor, which
9195 didn't handle RELAY_EARLY cells properly. Now that all supported
9196 versions can handle RELAY_EARLY cells, and now that we're enforcing
9197 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
9198 remove this workaround. Addresses bug 4786.
9201 Changes in version 0.2.2.35 - 2011-12-16
9202 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
9203 buffers code. Absolutely everybody should upgrade.
9205 The bug relied on an incorrect calculation when making data continuous
9206 in one of our IO buffers, if the first chunk of the buffer was
9207 misaligned by just the wrong amount. The miscalculation would allow an
9208 attacker to overflow a piece of heap-allocated memory. To mount this
9209 attack, the attacker would need to either open a SOCKS connection to
9210 Tor's SocksPort (usually restricted to localhost), or target a Tor
9211 instance configured to make its connections through a SOCKS proxy
9212 (which Tor does not do by default).
9214 Good security practice requires that all heap-overflow bugs should be
9215 presumed to be exploitable until proven otherwise, so we are treating
9216 this as a potential code execution attack. Please upgrade immediately!
9217 This bug does not affect bufferevents-based builds of Tor. Special
9218 thanks to "Vektor" for reporting this issue to us!
9220 Tor 0.2.2.35 also fixes several bugs in previous versions, including
9221 crash bugs for unusual configurations, and a long-term bug that
9222 would prevent Tor from starting on Windows machines with draconian
9225 With this release, we remind everyone that 0.2.0.x has reached its
9226 formal end-of-life. Those Tor versions have many known flaws, and
9227 nobody should be using them. You should upgrade -- ideally to the
9228 0.2.2.x series. If you're using a Linux or BSD and its packages are
9229 obsolete, stop using those packages and upgrade anyway.
9231 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
9232 longer receive support after some time in early 2012.
9235 - Fix a heap overflow bug that could occur when trying to pull
9236 data into the first chunk of a buffer, when that chunk had
9237 already had some data drained from it. Fixes CVE-2011-2778;
9238 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
9239 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
9240 that it doesn't attempt to allocate a socketpair. This could cause
9241 some problems on Windows systems with overzealous firewalls. Fix for
9242 bug 4457; workaround for Libevent versions 2.0.1-alpha through
9244 - If we mark an OR connection for close based on a cell we process,
9245 don't process any further cells on it. We already avoid further
9246 reads on marked-for-close connections, but now we also discard the
9247 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
9248 which was the first version where we might mark a connection for
9249 close based on processing a cell on it.
9250 - Correctly sanity-check that we don't underflow on a memory
9251 allocation (and then assert) for hidden service introduction
9252 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
9253 bugfix on 0.2.1.5-alpha.
9254 - Fix a memory leak when we check whether a hidden service
9255 descriptor has any usable introduction points left. Fixes bug
9256 4424. Bugfix on 0.2.2.25-alpha.
9257 - Don't crash when we're running as a relay and don't have a GeoIP
9258 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
9259 we've had in the 0.2.3.x branch already.
9260 - When running as a client, do not print a misleading (and plain
9261 wrong) log message that we're collecting "directory request"
9262 statistics: clients don't collect statistics. Also don't create a
9263 useless (because empty) stats file in the stats/ directory. Fixes
9264 bug 4353; bugfix on 0.2.2.34.
9267 - Detect failure to initialize Libevent. This fix provides better
9268 detection for future instances of bug 4457.
9269 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
9270 function. This was eating up hideously large amounts of time on some
9271 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
9272 - Resolve an integer overflow bug in smartlist_ensure_capacity().
9273 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
9275 - Don't warn about unused log_mutex in log.c when building with
9276 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
9277 0.1.0.6-rc which introduced --disable-threads.
9278 - When configuring, starting, or stopping an NT service, stop
9279 immediately after the service configuration attempt has succeeded
9280 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
9281 - When sending a NETINFO cell, include the original address
9282 received for the other side, not its canonical address. Found
9283 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
9284 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
9285 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
9286 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
9287 occurred when a client tried to fetch a descriptor for a bridge
9288 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
9289 - Backport fixes for a pair of compilation warnings on Windows.
9290 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
9291 - If we had ever tried to call tor_addr_to_str on an address of
9292 unknown type, we would have done a strdup on an uninitialized
9293 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
9294 Reported by "troll_un".
9295 - Correctly detect and handle transient lookup failures from
9296 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
9297 Reported by "troll_un".
9298 - Fix null-pointer access that could occur if TLS allocation failed.
9299 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
9300 - Use tor_socket_t type for listener argument to accept(). Fixes bug
9301 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
9304 - Add two new config options for directory authorities:
9305 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
9306 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
9307 that is always sufficient to satisfy the bandwidth requirement for
9308 the Guard flag. Now it will be easier for researchers to simulate
9309 Tor networks with different values. Resolves ticket 4484.
9310 - When Tor ignores a hidden service specified in its configuration,
9311 include the hidden service's directory in the warning message.
9312 Previously, we would only tell the user that some hidden service
9313 was ignored. Bugfix on 0.0.6; fixes bug 4426.
9314 - Update to the December 6 2011 Maxmind GeoLite Country database.
9316 o Packaging changes:
9317 - Make it easier to automate expert package builds on Windows,
9318 by removing an absolute path from makensis.exe command.
9321 Changes in version 0.2.1.32 - 2011-12-16
9322 Tor 0.2.1.32 backports important security and privacy fixes for
9323 oldstable. This release is intended only for package maintainers and
9324 others who cannot use the 0.2.2 stable series. All others should be
9325 using Tor 0.2.2.x or newer.
9327 The Tor 0.2.1.x series will reach formal end-of-life some time in
9328 early 2012; we will stop releasing patches for it then.
9330 o Major bugfixes (also included in 0.2.2.x):
9331 - Correctly sanity-check that we don't underflow on a memory
9332 allocation (and then assert) for hidden service introduction
9333 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
9334 bugfix on 0.2.1.5-alpha.
9335 - Fix a heap overflow bug that could occur when trying to pull
9336 data into the first chunk of a buffer, when that chunk had
9337 already had some data drained from it. Fixes CVE-2011-2778;
9338 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
9341 - Update to the December 6 2011 Maxmind GeoLite Country database.
9344 Changes in version 0.2.2.34 - 2011-10-26
9345 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
9346 can deanonymize Tor users. Everybody should upgrade.
9348 The attack relies on four components: 1) Clients reuse their TLS cert
9349 when talking to different relays, so relays can recognize a user by
9350 the identity key in her cert. 2) An attacker who knows the client's
9351 identity key can probe each guard relay to see if that identity key
9352 is connected to that guard relay right now. 3) A variety of active
9353 attacks in the literature (starting from "Low-Cost Traffic Analysis
9354 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
9355 discover the guard relays that a Tor user visiting the website is using.
9356 4) Clients typically pick three guards at random, so the set of guards
9357 for a given user could well be a unique fingerprint for her. This
9358 release fixes components #1 and #2, which is enough to block the attack;
9359 the other two remain as open research problems. Special thanks to
9360 "frosty_un" for reporting the issue to us!
9362 Clients should upgrade so they are no longer recognizable by the TLS
9363 certs they present. Relays should upgrade so they no longer allow a
9364 remote attacker to probe them to test whether unpatched clients are
9365 currently connected to them.
9367 This release also fixes several vulnerabilities that allow an attacker
9368 to enumerate bridge relays. Some bridge enumeration attacks still
9369 remain; see for example proposal 188.
9371 o Privacy/anonymity fixes (clients):
9372 - Clients and bridges no longer send TLS certificate chains on
9373 outgoing OR connections. Previously, each client or bridge would
9374 use the same cert chain for all outgoing OR connections until
9375 its IP address changes, which allowed any relay that the client
9376 or bridge contacted to determine which entry guards it is using.
9377 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
9378 - If a relay receives a CREATE_FAST cell on a TLS connection, it
9379 no longer considers that connection as suitable for satisfying a
9380 circuit EXTEND request. Now relays can protect clients from the
9381 CVE-2011-2768 issue even if the clients haven't upgraded yet.
9382 - Directory authorities no longer assign the Guard flag to relays
9383 that haven't upgraded to the above "refuse EXTEND requests
9384 to client connections" fix. Now directory authorities can
9385 protect clients from the CVE-2011-2768 issue even if neither
9386 the clients nor the relays have upgraded yet. There's a new
9387 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
9388 to let us transition smoothly, else tomorrow there would be no
9391 o Privacy/anonymity fixes (bridge enumeration):
9392 - Bridge relays now do their directory fetches inside Tor TLS
9393 connections, like all the other clients do, rather than connecting
9394 directly to the DirPort like public relays do. Removes another
9395 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
9396 - Bridges relays now build circuits for themselves in a more similar
9397 way to how clients build them. Removes another avenue for
9398 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
9399 when bridges were introduced.
9400 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
9401 that they initiated. Relays could distinguish incoming bridge
9402 connections from client connections, creating another avenue for
9403 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
9404 Found by "frosty_un".
9407 - Fix a crash bug when changing node restrictions while a DNS lookup
9408 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
9410 - Don't launch a useless circuit after failing to use one of a
9411 hidden service's introduction points. Previously, we would
9412 launch a new introduction circuit, but not set the hidden service
9413 which that circuit was intended to connect to, so it would never
9414 actually be used. A different piece of code would then create a
9415 new introduction circuit correctly. Bug reported by katmagic and
9416 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
9419 - Change an integer overflow check in the OpenBSD_Malloc code so
9420 that GCC is less likely to eliminate it as impossible. Patch
9421 from Mansour Moufid. Fixes bug 4059.
9422 - When a hidden service turns an extra service-side introduction
9423 circuit into a general-purpose circuit, free the rend_data and
9424 intro_key fields first, so we won't leak memory if the circuit
9425 is cannibalized for use as another service-side introduction
9426 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
9427 - Bridges now skip DNS self-tests, to act a little more stealthily.
9428 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
9429 bridges. Patch by "warms0x".
9430 - Fix internal bug-checking logic that was supposed to catch
9431 failures in digest generation so that it will fail more robustly
9432 if we ask for a nonexistent algorithm. Found by Coverity Scan.
9433 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
9434 - Report any failure in init_keys() calls launched because our
9435 IP address has changed. Spotted by Coverity Scan. Bugfix on
9436 0.1.1.4-alpha; fixes CID 484.
9438 o Minor bugfixes (log messages and documentation):
9439 - Remove a confusing dollar sign from the example fingerprint in the
9440 man page, and also make the example fingerprint a valid one. Fixes
9441 bug 4309; bugfix on 0.2.1.3-alpha.
9442 - The next version of Windows will be called Windows 8, and it has
9443 a major version of 6, minor version of 2. Correctly identify that
9444 version instead of calling it "Very recent version". Resolves
9445 ticket 4153; reported by funkstar.
9446 - Downgrade log messages about circuit timeout calibration from
9447 "notice" to "info": they don't require or suggest any human
9448 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
9449 bugfix on 0.2.2.14-alpha.
9452 - Turn on directory request statistics by default and include them in
9453 extra-info descriptors. Don't break if we have no GeoIP database.
9454 Backported from 0.2.3.1-alpha; implements ticket 3951.
9455 - Update to the October 4 2011 Maxmind GeoLite Country database.
9458 Changes in version 0.2.1.31 - 2011-10-26
9459 Tor 0.2.1.31 backports important security and privacy fixes for
9460 oldstable. This release is intended only for package maintainers and
9461 others who cannot use the 0.2.2 stable series. All others should be
9462 using Tor 0.2.2.x or newer.
9464 o Security fixes (also included in 0.2.2.x):
9465 - Replace all potentially sensitive memory comparison operations
9466 with versions whose runtime does not depend on the data being
9467 compared. This will help resist a class of attacks where an
9468 adversary can use variations in timing information to learn
9469 sensitive data. Fix for one case of bug 3122. (Safe memcmp
9470 implementation by Robert Ransom based partially on code by DJB.)
9471 - Fix an assert in parsing router descriptors containing IPv6
9472 addresses. This one took down the directory authorities when
9473 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
9475 o Privacy/anonymity fixes (also included in 0.2.2.x):
9476 - Clients and bridges no longer send TLS certificate chains on
9477 outgoing OR connections. Previously, each client or bridge would
9478 use the same cert chain for all outgoing OR connections until
9479 its IP address changes, which allowed any relay that the client
9480 or bridge contacted to determine which entry guards it is using.
9481 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
9482 - If a relay receives a CREATE_FAST cell on a TLS connection, it
9483 no longer considers that connection as suitable for satisfying a
9484 circuit EXTEND request. Now relays can protect clients from the
9485 CVE-2011-2768 issue even if the clients haven't upgraded yet.
9486 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
9487 that they initiated. Relays could distinguish incoming bridge
9488 connections from client connections, creating another avenue for
9489 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
9490 Found by "frosty_un".
9491 - When receiving a hidden service descriptor, check that it is for
9492 the hidden service we wanted. Previously, Tor would store any
9493 hidden service descriptors that a directory gave it, whether it
9494 wanted them or not. This wouldn't have let an attacker impersonate
9495 a hidden service, but it did let directories pre-seed a client
9496 with descriptors that it didn't want. Bugfix on 0.0.6.
9497 - Avoid linkability based on cached hidden service descriptors: forget
9498 all hidden service descriptors cached as a client when processing a
9499 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
9500 - Make the bridge directory authority refuse to answer directory
9501 requests for "all" descriptors. It used to include bridge
9502 descriptors in its answer, which was a major information leak.
9503 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
9504 - Don't attach new streams to old rendezvous circuits after SIGNAL
9505 NEWNYM. Previously, we would keep using an existing rendezvous
9506 circuit if it remained open (i.e. if it were kept open by a
9507 long-lived stream, or if a new stream were attached to it before
9508 Tor could notice that it was old and no longer in use). Bugfix on
9509 0.1.1.15-rc; fixes bug 3375.
9511 o Minor bugfixes (also included in 0.2.2.x):
9512 - When we restart our relay, we might get a successful connection
9513 from the outside before we've started our reachability tests,
9514 triggering a warning: "ORPort found reachable, but I have no
9515 routerinfo yet. Failing to inform controller of success." This
9516 bug was harmless unless Tor is running under a controller
9517 like Vidalia, in which case the controller would never get a
9518 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
9520 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
9521 enabled. Fixes bug 1526.
9522 - Remove undocumented option "-F" from tor-resolve: it hasn't done
9523 anything since 0.2.1.16-rc.
9524 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
9525 None of the cases where we did this before were wrong, but by making
9526 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
9527 - Fix a rare crash bug that could occur when a client was configured
9528 with a large number of bridges. Fixes bug 2629; bugfix on
9529 0.2.1.2-alpha. Bugfix by trac user "shitlei".
9530 - Correct the warning displayed when a rendezvous descriptor exceeds
9531 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
9533 - Fix an uncommon assertion failure when running with DNSPort under
9534 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
9535 - When warning about missing zlib development packages during compile,
9536 give the correct package names. Bugfix on 0.2.0.1-alpha.
9537 - Require that introduction point keys and onion keys have public
9538 exponent 65537. Bugfix on 0.2.0.10-alpha.
9539 - Do not crash when our configuration file becomes unreadable, for
9540 example due to a permissions change, between when we start up
9541 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
9543 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
9545 - Always NUL-terminate the sun_path field of a sockaddr_un before
9546 passing it to the kernel. (Not a security issue: kernels are
9547 smart enough to reject bad sockaddr_uns.) Found by Coverity;
9548 CID #428. Bugfix on Tor 0.2.0.3-alpha.
9549 - Don't stack-allocate the list of supplementary GIDs when we're
9550 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
9551 could take up to 256K, which is way too much stack. Found by
9552 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
9554 o Minor bugfixes (only in 0.2.1.x):
9555 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
9556 rely on them. Bugfix on 0.2.1.30.
9557 - Use git revisions instead of svn revisions when generating our
9558 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
9560 o Minor features (also included in 0.2.2.x):
9561 - Adjust the expiration time on our SSL session certificates to
9562 better match SSL certs seen in the wild. Resolves ticket 4014.
9563 - Allow nameservers with IPv6 address. Resolves bug 2574.
9564 - Update to the October 4 2011 Maxmind GeoLite Country database.
9567 Changes in version 0.2.2.33 - 2011-09-13
9568 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
9569 TLS handshake that makes relays and bridges that run this new version
9570 reachable from Iran again.
9573 - Avoid an assertion failure when reloading a configuration with
9574 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
9575 3923; bugfix on 0.2.2.25-alpha.
9577 o Minor features (security):
9578 - Check for replays of the public-key encrypted portion of an
9579 INTRODUCE1 cell, in addition to the current check for replays of
9580 the g^x value. This prevents a possible class of active attacks
9581 by an attacker who controls both an introduction point and a
9582 rendezvous point, and who uses the malleability of AES-CTR to
9583 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
9584 that these attacks are infeasible (requiring the attacker to send
9585 on the order of zettabytes of altered cells in a short interval),
9586 but we'd rather block them off in case there are any classes of
9587 this attack that we missed. Reported by Willem Pinckaers.
9590 - Adjust the expiration time on our SSL session certificates to
9591 better match SSL certs seen in the wild. Resolves ticket 4014.
9592 - Change the default required uptime for a relay to be accepted as
9593 a HSDir (hidden service directory) from 24 hours to 25 hours.
9594 Improves on 0.2.0.10-alpha; resolves ticket 2649.
9595 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
9596 authorities to abstain from voting on assignment of the HSDir
9597 consensus flag. Related to bug 2649.
9598 - Update to the September 6 2011 Maxmind GeoLite Country database.
9600 o Minor bugfixes (documentation and log messages):
9601 - Correct the man page to explain that HashedControlPassword and
9602 CookieAuthentication can both be set, in which case either method
9603 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
9604 when we decided to allow these config options to both be set. Issue
9606 - Demote the 'replay detected' log message emitted when a hidden
9607 service receives the same Diffie-Hellman public key in two different
9608 INTRODUCE2 cells to info level. A normal Tor client can cause that
9609 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
9610 fixes part of bug 2442.
9611 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
9612 level. There is nothing that a hidden service's operator can do
9613 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
9615 - Clarify a log message specifying the characters permitted in
9616 HiddenServiceAuthorizeClient client names. Previously, the log
9617 message said that "[A-Za-z0-9+-_]" were permitted; that could have
9618 given the impression that every ASCII character between "+" and "_"
9619 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
9622 - Provide a substitute implementation of lround() for MSVC, which
9623 apparently lacks it. Patch from Gisle Vanem.
9624 - Clean up some code issues that prevented Tor from building on older
9625 BSDs. Fixes bug 3894; reported by "grarpamp".
9626 - Search for a platform-specific version of "ar" when cross-compiling.
9627 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
9630 Changes in version 0.2.2.32 - 2011-08-27
9631 The Tor 0.2.2 release series is dedicated to the memory of Andreas
9632 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
9633 a founder of the PETS community, a leader in our field, a mentor,
9634 and a friend. He left us with these words: "I had the possibility
9635 to contribute to this world that is not as it should be. I hope I
9636 could help in some areas to make the world a better place, and that
9637 I could also encourage other people to be engaged in improving the
9638 world. Please, stay engaged. This world needs you, your love, your
9639 initiative -- now I cannot be part of that anymore."
9641 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
9642 ready. More than two years in the making, this release features improved
9643 client performance and hidden service reliability, better compatibility
9644 for Android, correct behavior for bridges that listen on more than
9645 one address, more extensible and flexible directory object handling,
9646 better reporting of network statistics, improved code security, and
9647 many many other features and bugfixes.
9649 o Major features (client performance):
9650 - When choosing which cells to relay first, relays now favor circuits
9651 that have been quiet recently, to provide lower latency for
9652 low-volume circuits. By default, relays enable or disable this
9653 feature based on a setting in the consensus. They can override
9654 this default by using the new "CircuitPriorityHalflife" config
9655 option. Design and code by Ian Goldberg, Can Tang, and Chris
9657 - Directory authorities now compute consensus weightings that instruct
9658 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
9659 and no flag. Clients use these weightings to distribute network load
9660 more evenly across these different relay types. The weightings are
9661 in the consensus so we can change them globally in the future. Extra
9662 thanks to "outofwords" for finding some nasty security bugs in
9663 the first implementation of this feature.
9665 o Major features (client performance, circuit build timeout):
9666 - Tor now tracks how long it takes to build client-side circuits
9667 over time, and adapts its timeout to local network performance.
9668 Since a circuit that takes a long time to build will also provide
9669 bad performance, we get significant latency improvements by
9670 discarding the slowest 20% of circuits. Specifically, Tor creates
9671 circuits more aggressively than usual until it has enough data
9672 points for a good timeout estimate. Implements proposal 151.
9673 - Circuit build timeout constants can be controlled by consensus
9674 parameters. We set good defaults for these parameters based on
9675 experimentation on broadband and simulated high-latency links.
9676 - Circuit build time learning can be disabled via consensus parameter
9677 or by the client via a LearnCircuitBuildTimeout config option. We
9678 also automatically disable circuit build time calculation if either
9679 AuthoritativeDirectory is set, or if we fail to write our state
9680 file. Implements ticket 1296.
9682 o Major features (relays use their capacity better):
9683 - Set SO_REUSEADDR socket option on all sockets, not just
9684 listeners. This should help busy exit nodes avoid running out of
9685 useable ports just because all the ports have been used in the
9686 near past. Resolves issue 2850.
9687 - Relays now save observed peak bandwidth throughput rates to their
9688 state file (along with total usage, which was already saved),
9689 so that they can determine their correct estimated bandwidth on
9690 restart. Resolves bug 1863, where Tor relays would reset their
9691 estimated bandwidth to 0 after restarting.
9692 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
9693 should give us approximately 40-50% more Guard-flagged nodes,
9694 improving the anonymity the Tor network can provide and also
9695 decreasing the dropoff in throughput that relays experience when
9696 they first get the Guard flag.
9697 - Directory authorities now take changes in router IP address and
9698 ORPort into account when determining router stability. Previously,
9699 if a router changed its IP or ORPort, the authorities would not
9700 treat it as having any downtime for the purposes of stability
9701 calculation, whereas clients would experience downtime since the
9702 change would take a while to propagate to them. Resolves issue 1035.
9703 - New AccelName and AccelDir options add support for dynamic OpenSSL
9704 hardware crypto acceleration engines.
9706 o Major features (relays control their load better):
9707 - Exit relays now try harder to block exit attempts from unknown
9708 relays, to make it harder for people to use them as one-hop proxies
9709 a la tortunnel. Controlled by the refuseunknownexits consensus
9710 parameter (currently enabled), or you can override it on your
9711 relay with the RefuseUnknownExits torrc option. Resolves bug 1751;
9712 based on a variant of proposal 163.
9713 - Add separate per-conn write limiting to go with the per-conn read
9714 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
9715 but never per-conn write limits.
9716 - New consensus params "bwconnrate" and "bwconnburst" to let us
9717 rate-limit client connections as they enter the network. It's
9718 controlled in the consensus so we can turn it on and off for
9719 experiments. It's starting out off. Based on proposal 163.
9721 o Major features (controllers):
9722 - Export GeoIP information on bridge usage to controllers even if we
9723 have not yet been running for 24 hours. Now Vidalia bridge operators
9724 can get more accurate and immediate feedback about their
9725 contributions to the network.
9726 - Add an __OwningControllerProcess configuration option and a
9727 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
9728 that when it exits, Tor will shut down. Implements feature 3049.
9730 o Major features (directory authorities):
9731 - Directory authorities now create, vote on, and serve multiple
9732 parallel formats of directory data as part of their voting process.
9733 Partially implements Proposal 162: "Publish the consensus in
9735 - Directory authorities now agree on and publish small summaries
9736 of router information that clients can use in place of regular
9737 server descriptors. This transition will allow Tor 0.2.3 clients
9738 to use far less bandwidth for downloading information about the
9739 network. Begins the implementation of Proposal 158: "Clients
9740 download consensus + microdescriptors".
9741 - The directory voting system is now extensible to use multiple hash
9742 algorithms for signatures and resource selection. Newer formats
9743 are signed with SHA256, with a possibility for moving to a better
9744 hash algorithm in the future.
9745 - Directory authorities can now vote on arbitary integer values as
9746 part of the consensus process. This is designed to help set
9747 network-wide parameters. Implements proposal 167.
9749 o Major features and bugfixes (node selection):
9750 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
9751 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and Strict*Nodes
9752 options. Previously, we had been ambiguous in describing what
9753 counted as an "exit" node, and what operations exactly "StrictNodes
9754 0" would permit. This created confusion when people saw nodes built
9755 through unexpected circuits, and made it hard to tell real bugs from
9756 surprises. Now the intended behavior is:
9757 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
9758 a node that delivers user traffic outside the Tor network.
9759 . "Entry", in the context of EntryNodes, means a node used as the
9760 first hop of a multihop circuit. It doesn't include direct
9761 connections to directory servers.
9762 . "ExcludeNodes" applies to all nodes.
9763 . "StrictNodes" changes the behavior of ExcludeNodes only. When
9764 StrictNodes is set, Tor should avoid all nodes listed in
9765 ExcludeNodes, even when it will make user requests fail. When
9766 StrictNodes is *not* set, then Tor should follow ExcludeNodes
9767 whenever it can, except when it must use an excluded node to
9768 perform self-tests, connect to a hidden service, provide a
9769 hidden service, fulfill a .exit request, upload directory
9770 information, or fetch directory information.
9771 Collectively, the changes to implement the behavior fix bug 1090.
9772 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
9773 change during a config reload, mark and discard all our origin
9774 circuits. This fix should address edge cases where we change the
9775 config options and but then choose a circuit that we created before
9777 - Make EntryNodes config option much more aggressive even when
9778 StrictNodes is not set. Before it would prepend your requested
9779 entrynodes to your list of guard nodes, but feel free to use others
9780 after that. Now it chooses only from your EntryNodes if any of
9781 those are available, and only falls back to others if a) they're
9782 all down and b) StrictNodes is not set.
9783 - Now we refresh your entry guards from EntryNodes at each consensus
9784 fetch -- rather than just at startup and then they slowly rot as
9785 the network changes.
9786 - Add support for the country code "{??}" in torrc options like
9787 ExcludeNodes, to indicate all routers of unknown country. Closes
9789 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
9790 a node is listed in both, it's treated as excluded.
9791 - ExcludeNodes now applies to directory nodes -- as a preference if
9792 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
9793 Don't exclude all the directory authorities and set StrictNodes to 1
9794 unless you really want your Tor to break.
9795 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
9796 - ExcludeExitNodes now overrides .exit requests.
9797 - We don't use bridges listed in ExcludeNodes.
9798 - When StrictNodes is 1:
9799 . We now apply ExcludeNodes to hidden service introduction points
9800 and to rendezvous points selected by hidden service users. This
9801 can make your hidden service less reliable: use it with caution!
9802 . If we have used ExcludeNodes on ourself, do not try relay
9803 reachability self-tests.
9804 . If we have excluded all the directory authorities, we will not
9805 even try to upload our descriptor if we're a relay.
9806 . Do not honor .exit requests to an excluded node.
9807 - When the set of permitted nodes changes, we now remove any mappings
9808 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
9810 - We never cannibalize a circuit that had excluded nodes on it, even
9811 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
9812 - Improve log messages related to excluded nodes.
9814 o Major features (misc):
9815 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
9816 to help Tor build correctly for Android phones.
9817 - The options SocksPort, ControlPort, and so on now all accept a
9818 value "auto" that opens a socket on an OS-selected port. A
9819 new ControlPortWriteToFile option tells Tor to write its
9820 actual control port or ports to a chosen file. If the option
9821 ControlPortFileGroupReadable is set, the file is created as
9822 group-readable. Now users can run two Tor clients on the same
9823 system without needing to manually mess with parameters. Resolves
9824 part of ticket 3076.
9825 - Tor now supports tunneling all of its outgoing connections over
9826 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
9827 configuration options. Code by Christopher Davis.
9829 o Code security improvements:
9830 - Replace all potentially sensitive memory comparison operations
9831 with versions whose runtime does not depend on the data being
9832 compared. This will help resist a class of attacks where an
9833 adversary can use variations in timing information to learn
9834 sensitive data. Fix for one case of bug 3122. (Safe memcmp
9835 implementation by Robert Ransom based partially on code by DJB.)
9836 - Enable Address Space Layout Randomization (ASLR) and Data Execution
9837 Prevention (DEP) by default on Windows to make it harder for
9838 attackers to exploit vulnerabilities. Patch from John Brooks.
9839 - New "--enable-gcc-hardening" ./configure flag (off by default)
9840 to turn on gcc compile time hardening options. It ensures
9841 that signed ints have defined behavior (-fwrapv), enables
9842 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
9843 with canaries (-fstack-protector-all), turns on ASLR protection if
9844 supported by the kernel (-fPIE, -pie), and adds additional security
9845 related warnings. Verified to work on Mac OS X and Debian Lenny.
9846 - New "--enable-linker-hardening" ./configure flag (off by default)
9847 to turn on ELF specific hardening features (relro, now). This does
9848 not work with Mac OS X or any other non-ELF binary format.
9849 - Always search the Windows system directory for system DLLs, and
9850 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
9851 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
9852 current and future memory pages via mlockall(). On supported
9853 platforms (modern Linux and probably BSD but not Windows or OS X),
9854 this should effectively disable any and all attempts to page out
9855 memory. This option requires that you start your Tor as root --
9856 if you use DisableAllSwap, please consider using the User option
9857 to properly reduce the privileges of your Tor.
9859 o Major bugfixes (crashes):
9860 - Fix crash bug on platforms where gmtime and localtime can return
9861 NULL. Windows 7 users were running into this one. Fixes part of bug
9862 2077. Bugfix on all versions of Tor. Found by boboper.
9863 - Introduce minimum/maximum values that clients will believe
9864 from the consensus. Now we'll have a better chance to avoid crashes
9865 or worse when a consensus param has a weird value.
9866 - Fix a rare crash bug that could occur when a client was configured
9867 with a large number of bridges. Fixes bug 2629; bugfix on
9868 0.2.1.2-alpha. Bugfix by trac user "shitlei".
9869 - Do not crash when our configuration file becomes unreadable, for
9870 example due to a permissions change, between when we start up
9871 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
9873 - If we're in the pathological case where there's no exit bandwidth
9874 but there is non-exit bandwidth, or no guard bandwidth but there
9875 is non-guard bandwidth, don't crash during path selection. Bugfix
9877 - Fix a crash bug when trying to initialize the evdns module in
9878 Libevent 2. Bugfix on 0.2.1.16-rc.
9880 o Major bugfixes (stability):
9881 - Fix an assert in parsing router descriptors containing IPv6
9882 addresses. This one took down the directory authorities when
9883 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
9884 - Fix an uncommon assertion failure when running with DNSPort under
9885 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
9886 - Treat an unset $HOME like an empty $HOME rather than triggering an
9887 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
9888 - More gracefully handle corrupt state files, removing asserts
9889 in favor of saving a backup and resetting state.
9890 - Instead of giving an assertion failure on an internal mismatch
9891 on estimated freelist size, just log a BUG warning and try later.
9892 Mitigates but does not fix bug 1125.
9893 - Fix an assert that got triggered when using the TestingTorNetwork
9894 configuration option and then issuing a GETINFO config-text control
9895 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
9896 - If the cached cert file is unparseable, warn but don't exit.
9898 o Privacy fixes (relays/bridges):
9899 - Don't list Windows capabilities in relay descriptors. We never made
9900 use of them, and maybe it's a bad idea to publish them. Bugfix
9902 - If the Nickname configuration option isn't given, Tor would pick a
9903 nickname based on the local hostname as the nickname for a relay.
9904 Because nicknames are not very important in today's Tor and the
9905 "Unnamed" nickname has been implemented, this is now problematic
9906 behavior: It leaks information about the hostname without being
9907 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
9908 introduced the Unnamed nickname. Reported by tagnaq.
9909 - Maintain separate TLS contexts and certificates for incoming and
9910 outgoing connections in bridge relays. Previously we would use the
9911 same TLS contexts and certs for incoming and outgoing connections.
9912 Bugfix on 0.2.0.3-alpha; addresses bug 988.
9913 - Maintain separate identity keys for incoming and outgoing TLS
9914 contexts in bridge relays. Previously we would use the same
9915 identity keys for incoming and outgoing TLS contexts. Bugfix on
9916 0.2.0.3-alpha; addresses the other half of bug 988.
9917 - Make the bridge directory authority refuse to answer directory
9918 requests for "all descriptors". It used to include bridge
9919 descriptors in its answer, which was a major information leak.
9920 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
9922 o Privacy fixes (clients):
9923 - When receiving a hidden service descriptor, check that it is for
9924 the hidden service we wanted. Previously, Tor would store any
9925 hidden service descriptors that a directory gave it, whether it
9926 wanted them or not. This wouldn't have let an attacker impersonate
9927 a hidden service, but it did let directories pre-seed a client
9928 with descriptors that it didn't want. Bugfix on 0.0.6.
9929 - Start the process of disabling ".exit" address notation, since it
9930 can be used for a variety of esoteric application-level attacks
9931 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
9933 - Reject attempts at the client side to open connections to private
9934 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
9935 a randomly chosen exit node. Attempts to do so are always
9936 ill-defined, generally prevented by exit policies, and usually
9937 in error. This will also help to detect loops in transparent
9938 proxy configurations. You can disable this feature by setting
9939 "ClientRejectInternalAddresses 0" in your torrc.
9940 - Log a notice when we get a new control connection. Now it's easier
9941 for security-conscious users to recognize when a local application
9942 is knocking on their controller door. Suggested by bug 1196.
9944 o Privacy fixes (newnym):
9945 - Avoid linkability based on cached hidden service descriptors: forget
9946 all hidden service descriptors cached as a client when processing a
9947 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
9948 - On SIGHUP, do not clear out all TrackHostExits mappings, client
9949 DNS cache entries, and virtual address mappings: that's what
9950 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
9951 - Don't attach new streams to old rendezvous circuits after SIGNAL
9952 NEWNYM. Previously, we would keep using an existing rendezvous
9953 circuit if it remained open (i.e. if it were kept open by a
9954 long-lived stream, or if a new stream were attached to it before
9955 Tor could notice that it was old and no longer in use). Bugfix on
9956 0.1.1.15-rc; fixes bug 3375.
9958 o Major bugfixes (relay bandwidth accounting):
9959 - Fix a bug that could break accounting on 64-bit systems with large
9960 time_t values, making them hibernate for impossibly long intervals.
9961 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
9962 - Fix a bug in bandwidth accounting that could make us use twice
9963 the intended bandwidth when our interval start changes due to
9964 daylight saving time. Now we tolerate skew in stored vs computed
9965 interval starts: if the start of the period changes by no more than
9966 50% of the period's duration, we remember bytes that we transferred
9967 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
9969 o Major bugfixes (bridges):
9970 - Bridges now use "reject *:*" as their default exit policy. Bugfix
9971 on 0.2.0.3-alpha. Fixes bug 1113.
9972 - If you configure your bridge with a known identity fingerprint,
9973 and the bridge authority is unreachable (as it is in at least
9974 one country now), fall back to directly requesting the descriptor
9975 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
9977 - Fix a bug where bridge users who configure the non-canonical
9978 address of a bridge automatically switch to its canonical
9979 address. If a bridge listens at more than one address, it
9980 should be able to advertise those addresses independently and
9981 any non-blocked addresses should continue to work. Bugfix on Tor
9982 0.2.0.3-alpha. Fixes bug 2510.
9983 - If you configure Tor to use bridge A, and then quit and
9984 configure Tor to use bridge B instead (or if you change Tor
9985 to use bridge B via the controller), it would happily continue
9986 to use bridge A if it's still reachable. While this behavior is
9987 a feature if your goal is connectivity, in some scenarios it's a
9988 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
9989 - When the controller configures a new bridge, don't wait 10 to 60
9990 seconds before trying to fetch its descriptor. Bugfix on
9991 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
9993 o Major bugfixes (directory authorities):
9994 - Many relays have been falling out of the consensus lately because
9995 not enough authorities know about their descriptor for them to get
9996 a majority of votes. When we deprecated the v2 directory protocol,
9997 we got rid of the only way that v3 authorities can hear from each
9998 other about other descriptors. Now authorities examine every v3
9999 vote for new descriptors, and fetch them from that authority. Bugfix
10001 - Authorities could be tricked into giving out the Exit flag to relays
10002 that didn't allow exiting to any ports. This bug could screw
10003 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
10004 1238. Bug discovered by Martin Kowalczyk.
10005 - If all authorities restart at once right before a consensus vote,
10006 nobody will vote about "Running", and clients will get a consensus
10007 with no usable relays. Instead, authorities refuse to build a
10008 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
10010 o Major bugfixes (stream-level fairness):
10011 - When receiving a circuit-level SENDME for a blocked circuit, try
10012 to package cells fairly from all the streams that had previously
10013 been blocked on that circuit. Previously, we had started with the
10014 oldest stream, and allowed each stream to potentially exhaust
10015 the circuit's package window. This gave older streams on any
10016 given circuit priority over newer ones. Fixes bug 1937. Detected
10017 originally by Camilo Viecco. This bug was introduced before the
10018 first Tor release, in svn commit r152: it is the new winner of
10019 the longest-lived bug prize.
10020 - Fix a stream fairness bug that would cause newer streams on a given
10021 circuit to get preference when reading bytes from the origin or
10022 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
10023 introduced before the first Tor release, in svn revision r152.
10024 - When the exit relay got a circuit-level sendme cell, it started
10025 reading on the exit streams, even if had 500 cells queued in the
10026 circuit queue already, so the circuit queue just grew and grew in
10027 some cases. We fix this by not re-enabling reading on receipt of a
10028 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
10029 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
10031 - Newly created streams were allowed to read cells onto circuits,
10032 even if the circuit's cell queue was blocked and waiting to drain.
10033 This created potential unfairness, as older streams would be
10034 blocked, but newer streams would gladly fill the queue completely.
10035 We add code to detect this situation and prevent any stream from
10036 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
10039 o Major bugfixes (hidden services):
10040 - Apply circuit timeouts to opened hidden-service-related circuits
10041 based on the correct start time. Previously, we would apply the
10042 circuit build timeout based on time since the circuit's creation;
10043 it was supposed to be applied based on time since the circuit
10044 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
10045 - Improve hidden service robustness: When we find that we have
10046 extended a hidden service's introduction circuit to a relay not
10047 listed as an introduction point in the HS descriptor we currently
10048 have, retry with an introduction point from the current
10049 descriptor. Previously we would just give up. Fixes bugs 1024 and
10050 1930; bugfix on 0.2.0.10-alpha.
10051 - Directory authorities now use data collected from their own
10052 uptime observations when choosing whether to assign the HSDir flag
10053 to relays, instead of trusting the uptime value the relay reports in
10054 its descriptor. This change helps prevent an attack where a small
10055 set of nodes with frequently-changing identity keys can blackhole
10056 a hidden service. (Only authorities need upgrade; others will be
10057 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
10058 - Stop assigning the HSDir flag to relays that disable their
10059 DirPort (and thus will refuse to answer directory requests). This
10060 fix should dramatically improve the reachability of hidden services:
10061 hidden services and hidden service clients pick six HSDir relays
10062 to store and retrieve the hidden service descriptor, and currently
10063 about half of the HSDir relays will refuse to work. Bugfix on
10064 0.2.0.10-alpha; fixes part of bug 1693.
10066 o Major bugfixes (misc):
10067 - Clients now stop trying to use an exit node associated with a given
10068 destination by TrackHostExits if they fail to reach that exit node.
10069 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
10070 - Fix a regression that caused Tor to rebind its ports if it receives
10071 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
10072 - Remove an extra pair of quotation marks around the error
10073 message in control-port STATUS_GENERAL BUG events. Bugfix on
10074 0.1.2.6-alpha; fixes bug 3732.
10076 o Minor features (relays):
10077 - Ensure that no empty [dirreq-](read|write)-history lines are added
10078 to an extrainfo document. Implements ticket 2497.
10079 - When bandwidth accounting is enabled, be more generous with how
10080 much bandwidth we'll use up before entering "soft hibernation".
10081 Previously, we'd refuse new connections and circuits once we'd
10082 used up 95% of our allotment. Now, we use up 95% of our allotment,
10083 AND make sure that we have no more than 500MB (or 3 hours of
10084 expected traffic, whichever is lower) remaining before we enter
10086 - Relays now log the reason for publishing a new relay descriptor,
10087 so we have a better chance of hunting down instances of bug 1810.
10088 Resolves ticket 3252.
10089 - Log a little more clearly about the times at which we're no longer
10090 accepting new connections (e.g. due to hibernating). Resolves
10092 - When AllowSingleHopExits is set, print a warning to explain to the
10093 relay operator why most clients are avoiding her relay.
10094 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
10095 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
10096 clients are already deprecated because of security bugs.
10098 o Minor features (network statistics):
10099 - Directory mirrors that set "DirReqStatistics 1" write statistics
10100 about directory requests to disk every 24 hours. As compared to the
10101 "--enable-geoip-stats" ./configure flag in 0.2.1.x, there are a few
10102 improvements: 1) stats are written to disk exactly every 24 hours;
10103 2) estimated shares of v2 and v3 requests are determined as mean
10104 values, not at the end of a measurement period; 3) unresolved
10105 requests are listed with country code '??'; 4) directories also
10106 measure download times.
10107 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
10108 number of exit streams and transferred bytes per port to disk every
10110 - Relays that set "CellStatistics 1" write statistics on how long
10111 cells spend in their circuit queues to disk every 24 hours.
10112 - Entry nodes that set "EntryStatistics 1" write statistics on the
10113 rough number and origins of connecting clients to disk every 24
10115 - Relays that write any of the above statistics to disk and set
10116 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
10117 their extra-info documents. Implements proposal 166.
10119 o Minor features (GeoIP and statistics):
10120 - Provide a log message stating which geoip file we're parsing
10121 instead of just stating that we're parsing the geoip file.
10122 Implements ticket 2432.
10123 - Make sure every relay writes a state file at least every 12 hours.
10124 Previously, a relay could go for weeks without writing its state
10125 file, and on a crash could lose its bandwidth history, capacity
10126 estimates, client country statistics, and so on. Addresses bug 3012.
10127 - Relays report the number of bytes spent on answering directory
10128 requests in extra-info descriptors similar to {read,write}-history.
10129 Implements enhancement 1790.
10130 - Report only the top 10 ports in exit-port stats in order not to
10131 exceed the maximum extra-info descriptor length of 50 KB. Implements
10133 - If writing the state file to disk fails, wait up to an hour before
10134 retrying again, rather than trying again each second. Fixes bug
10135 2346; bugfix on Tor 0.1.1.3-alpha.
10136 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
10137 when we switch from being a public relay to a bridge. Otherwise
10138 there will still be clients that see the relay in their consensus,
10139 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes
10141 - Update to the August 2 2011 Maxmind GeoLite Country database.
10143 o Minor features (clients):
10144 - When expiring circuits, use microsecond timers rather than
10145 one-second timers. This can avoid an unpleasant situation where a
10146 circuit is launched near the end of one second and expired right
10147 near the beginning of the next, and prevent fluctuations in circuit
10149 - If we've configured EntryNodes and our network goes away and/or all
10150 our entrynodes get marked down, optimistically retry them all when
10151 a new socks application request appears. Fixes bug 1882.
10152 - Always perform router selections using weighted relay bandwidth,
10153 even if we don't need a high capacity circuit at the time. Non-fast
10154 circuits now only differ from fast ones in that they can use relays
10155 not marked with the Fast flag. This "feature" could turn out to
10156 be a horrible bug; we should investigate more before it goes into
10158 - When we run out of directory information such that we can't build
10159 circuits, but then get enough that we can build circuits, log when
10160 we actually construct a circuit, so the user has a better chance of
10161 knowing what's going on. Fixes bug 1362.
10162 - Log SSL state transitions at debug level during handshake, and
10163 include SSL states in error messages. This may help debug future
10164 SSL handshake issues.
10166 o Minor features (directory authorities):
10167 - When a router changes IP address or port, authorities now launch
10168 a new reachability test for it. Implements ticket 1899.
10169 - Directory authorities now reject relays running any versions of
10170 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
10171 known bugs that keep RELAY_EARLY cells from working on rendezvous
10172 circuits. Followup to fix for bug 2081.
10173 - Directory authorities now reject relays running any version of Tor
10174 older than 0.2.0.26-rc. That version is the earliest that fetches
10175 current directory information correctly. Fixes bug 2156.
10176 - Directory authorities now do an immediate reachability check as soon
10177 as they hear about a new relay. This change should slightly reduce
10178 the time between setting up a relay and getting listed as running
10179 in the consensus. It should also improve the time between setting
10180 up a bridge and seeing use by bridge users.
10181 - Directory authorities no longer launch a TLS connection to every
10182 relay as they startup. Now that we have 2k+ descriptors cached,
10183 the resulting network hiccup is becoming a burden. Besides,
10184 authorities already avoid voting about Running for the first half
10185 hour of their uptime.
10186 - Directory authorities now log the source of a rejected POSTed v3
10187 networkstatus vote, so we can track failures better.
10188 - Backport code from 0.2.3.x that allows directory authorities to
10189 clean their microdescriptor caches. Needed to resolve bug 2230.
10191 o Minor features (hidden services):
10192 - Use computed circuit-build timeouts to decide when to launch
10193 parallel introduction circuits for hidden services. (Previously,
10194 we would retry after 15 seconds.)
10195 - Don't allow v0 hidden service authorities to act as clients.
10196 Required by fix for bug 3000.
10197 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
10198 by fix for bug 3000.
10199 - Make hidden services work better in private Tor networks by not
10200 requiring any uptime to join the hidden service descriptor
10201 DHT. Implements ticket 2088.
10202 - Log (at info level) when purging pieces of hidden-service-client
10203 state because of SIGNAL NEWNYM.
10205 o Minor features (controller interface):
10206 - New "GETINFO net/listeners/(type)" controller command to return
10207 a list of addresses and ports that are bound for listeners for a
10208 given connection type. This is useful when the user has configured
10209 "SocksPort auto" and the controller needs to know which port got
10210 chosen. Resolves another part of ticket 3076.
10211 - Have the controller interface give a more useful message than
10212 "Internal Error" in response to failed GETINFO requests.
10213 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
10214 event, to give information on the current rate of circuit timeouts
10215 over our stored history.
10216 - The 'EXTENDCIRCUIT' control port command can now be used with
10217 a circ id of 0 and no path. This feature will cause Tor to build
10218 a new 'fast' general purpose circuit using its own path selection
10220 - Added a BUILDTIMEOUT_SET controller event to describe changes
10221 to the circuit build timeout.
10222 - New controller command "getinfo config-text". It returns the
10223 contents that Tor would write if you send it a SAVECONF command,
10224 so the controller can write the file to disk itself.
10226 o Minor features (controller protocol):
10227 - Add a new ControlSocketsGroupWritable configuration option: when
10228 it is turned on, ControlSockets are group-writeable by the default
10229 group of the current user. Patch by Jérémy Bobbio; implements
10231 - Tor now refuses to create a ControlSocket in a directory that is
10232 world-readable (or group-readable if ControlSocketsGroupWritable
10233 is 0). This is necessary because some operating systems do not
10234 enforce permissions on an AF_UNIX sockets. Permissions on the
10235 directory holding the socket, however, seems to work everywhere.
10236 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
10237 not. This would lead to a cookie that is still not group readable.
10238 Closes bug 1843. Suggested by katmagic.
10239 - Future-proof the controller protocol a bit by ignoring keyword
10240 arguments we do not recognize.
10242 o Minor features (more useful logging):
10243 - Revise most log messages that refer to nodes by nickname to
10244 instead use the "$key=nickname at address" format. This should be
10245 more useful, especially since nicknames are less and less likely
10246 to be unique. Resolves ticket 3045.
10247 - When an HTTPS proxy reports "403 Forbidden", we now explain
10248 what it means rather than calling it an unexpected status code.
10249 Closes bug 2503. Patch from Michael Yakubovich.
10250 - Rate-limit a warning about failures to download v2 networkstatus
10251 documents. Resolves part of bug 1352.
10252 - Rate-limit the "your application is giving Tor only an IP address"
10253 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
10254 - Rate-limit "Failed to hand off onionskin" warnings.
10255 - When logging a rate-limited warning, we now mention how many messages
10256 got suppressed since the last warning.
10257 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
10258 2 no signature, 4 required" messages about consensus signatures
10259 easier to read, and make sure they get logged at the same severity
10260 as the messages explaining which keys are which. Fixes bug 1290.
10261 - Don't warn when we have a consensus that we can't verify because
10262 of missing certificates, unless those certificates are ones
10263 that we have been trying and failing to download. Fixes bug 1145.
10265 o Minor features (log domains):
10266 - Add documentation for configuring logging at different severities in
10267 different log domains. We've had this feature since 0.2.1.1-alpha,
10268 but for some reason it never made it into the manpage. Fixes
10270 - Make it simpler to specify "All log domains except for A and B".
10271 Previously you needed to say "[*,~A,~B]". Now you can just say
10273 - Add a "LogMessageDomains 1" option to include the domains of log
10274 messages along with the messages. Without this, there's no way
10275 to use log domains without reading the source or doing a lot
10277 - Add a new "Handshake" log domain for activities that happen
10278 during the TLS handshake.
10280 o Minor features (build process):
10281 - Make compilation with clang possible when using
10282 "--enable-gcc-warnings" by removing two warning options that clang
10283 hasn't implemented yet and by fixing a few warnings. Resolves
10285 - Detect platforms that brokenly use a signed size_t, and refuse to
10286 build there. Found and analyzed by doorss and rransom.
10287 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
10289 - Add support for statically linking zlib by specifying
10290 "--enable-static-zlib", to go with our support for statically
10291 linking openssl and libevent. Resolves bug 1358.
10292 - Instead of adding the svn revision to the Tor version string, report
10293 the git commit (when we're building from a git checkout).
10294 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
10296 - New --digests command-line switch to output the digests of the
10297 source files Tor was built with.
10298 - Generate our manpage and HTML documentation using Asciidoc. This
10299 change should make it easier to maintain the documentation, and
10300 produce nicer HTML. The build process fails if asciidoc cannot
10301 be found and building with asciidoc isn't disabled (via the
10302 "--disable-asciidoc" argument to ./configure. Skipping the manpage
10303 speeds up the build considerably.
10305 o Minor features (options / torrc):
10306 - Warn when the same option is provided more than once in a torrc
10307 file, on the command line, or in a single SETCONF statement, and
10308 the option is one that only accepts a single line. Closes bug 1384.
10309 - Warn when the user configures two HiddenServiceDir lines that point
10310 to the same directory. Bugfix on 0.0.6 (the version introducing
10311 HiddenServiceDir); fixes bug 3289.
10312 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
10313 do individual connection-level rate limiting of clients. The torrc
10314 config options with the same names trump the consensus params, if
10315 both are present. Replaces the old "bwconnrate" and "bwconnburst"
10316 consensus params which were broken from 0.2.2.7-alpha through
10317 0.2.2.14-alpha. Closes bug 1947.
10318 - New config option "WarnUnsafeSocks 0" disables the warning that
10319 occurs whenever Tor receives a socks handshake using a version of
10320 the socks protocol that can only provide an IP address (rather
10321 than a hostname). Setups that do DNS locally over Tor are fine,
10322 and we shouldn't spam the logs in that case.
10323 - New config option "CircuitStreamTimeout" to override our internal
10324 timeout schedule for how many seconds until we detach a stream from
10325 a circuit and try a new circuit. If your network is particularly
10326 slow, you might want to set this to a number like 60.
10327 - New options for SafeLogging to allow scrubbing only log messages
10328 generated while acting as a relay. Specify "SafeLogging relay" if
10329 you want to ensure that only messages known to originate from
10330 client use of the Tor process will be logged unsafely.
10331 - Time and memory units in the configuration file can now be set to
10332 fractional units. For example, "2.5 GB" is now a valid value for
10334 - Support line continuations in the torrc config file. If a line
10335 ends with a single backslash character, the newline is ignored, and
10336 the configuration value is treated as continuing on the next line.
10339 o Minor features (unit tests):
10340 - Revise our unit tests to use the "tinytest" framework, so we
10341 can run tests in their own processes, have smarter setup/teardown
10342 code, and so on. The unit test code has moved to its own
10343 subdirectory, and has been split into multiple modules.
10344 - Add a unit test for cross-platform directory-listing code.
10345 - Add some forgotten return value checks during unit tests. Found
10347 - Use GetTempDir to find the proper temporary directory location on
10348 Windows when generating temporary files for the unit tests. Patch
10351 o Minor features (misc):
10352 - The "torify" script now uses torsocks where available.
10353 - Make Libevent log messages get delivered to controllers later,
10354 and not from inside the Libevent log handler. This prevents unsafe
10355 reentrant Libevent calls while still letting the log messages
10357 - Certain Tor clients (such as those behind check.torproject.org) may
10358 want to fetch the consensus in an extra early manner. To enable this
10359 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
10360 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
10361 as only certain clients who must have this information sooner should
10363 - Expand homedirs passed to tor-checkkey. This should silence a
10364 coverity complaint about passing a user-supplied string into
10365 open() without checking it.
10366 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
10367 used on bridges, and it makes bridge scanning somewhat easier.
10368 - Create the /var/run/tor directory on startup on OpenSUSE if it is
10369 not already created. Patch from Andreas Stieger. Fixes bug 2573.
10371 o Minor bugfixes (relays):
10372 - When a relay decides that its DNS is too broken for it to serve
10373 as an exit server, it advertised itself as a non-exit, but
10374 continued to act as an exit. This could create accidental
10375 partitioning opportunities for users. Instead, if a relay is
10376 going to advertise reject *:* as its exit policy, it should
10377 really act with exit policy "reject *:*". Fixes bug 2366.
10378 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
10379 - Publish a router descriptor even if generating an extra-info
10380 descriptor fails. Previously we would not publish a router
10381 descriptor without an extra-info descriptor; this can cause fast
10382 exit relays collecting exit-port statistics to drop from the
10383 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
10384 - When we're trying to guess whether we know our IP address as
10385 a relay, we would log various ways that we failed to guess
10386 our address, but never log that we ended up guessing it
10387 successfully. Now add a log line to help confused and anxious
10388 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
10389 - For bandwidth accounting, calculate our expected bandwidth rate
10390 based on the time during which we were active and not in
10391 soft-hibernation during the last interval. Previously, we were
10392 also considering the time spent in soft-hibernation. If this
10393 was a long time, we would wind up underestimating our bandwidth
10394 by a lot, and skewing our wakeup time towards the start of the
10395 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
10396 - Demote a confusing TLS warning that relay operators might get when
10397 someone tries to talk to their ORPort. It is not the operator's
10398 fault, nor can they do anything about it. Fixes bug 1364; bugfix
10400 - Change "Application request when we're believed to be offline."
10401 notice to "Application request when we haven't used client
10402 functionality lately.", to clarify that it's not an error. Bugfix
10403 on 0.0.9.3; fixes bug 1222.
10405 o Minor bugfixes (bridges):
10406 - When a client starts or stops using bridges, never use a circuit
10407 that was built before the configuration change. This behavior could
10408 put at risk a user who uses bridges to ensure that her traffic
10409 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
10411 - Do not reset the bridge descriptor download status every time we
10412 re-parse our configuration or get a configuration change. Fixes
10413 bug 3019; bugfix on 0.2.0.3-alpha.
10414 - Users couldn't configure a regular relay to be their bridge. It
10415 didn't work because when Tor fetched the bridge descriptor, it found
10416 that it already had it, and didn't realize that the purpose of the
10417 descriptor had changed. Now we replace routers with a purpose other
10418 than bridge with bridge descriptors when fetching them. Bugfix on
10419 0.1.1.9-alpha. Fixes bug 1776.
10420 - In the special case where you configure a public exit relay as your
10421 bridge, Tor would be willing to use that exit relay as the last
10422 hop in your circuit as well. Now we fail that circuit instead.
10423 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
10425 o Minor bugfixes (clients):
10426 - We now ask the other side of a stream (the client or the exit)
10427 for more data on that stream when the amount of queued data on
10428 that stream dips low enough. Previously, we wouldn't ask the
10429 other side for more data until either it sent us more data (which
10430 it wasn't supposed to do if it had exhausted its window!) or we
10431 had completely flushed all our queued data. This flow control fix
10432 should improve throughput. Fixes bug 2756; bugfix on the earliest
10433 released versions of Tor (svn commit r152).
10434 - When a client finds that an origin circuit has run out of 16-bit
10435 stream IDs, we now mark it as unusable for new streams. Previously,
10436 we would try to close the entire circuit. Bugfix on 0.0.6.
10437 - Make it explicit that we don't cannibalize one-hop circuits. This
10438 happens in the wild, but doesn't turn out to be a problem because
10439 we fortunately don't use those circuits. Many thanks to outofwords
10440 for the initial analysis and to swissknife who confirmed that
10441 two-hop circuits are actually created.
10442 - Resolve an edge case in path weighting that could make us misweight
10443 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
10444 - Make the DNSPort option work with libevent 2.x. Don't alter the
10445 behavior for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
10447 o Minor bugfixes (directory authorities):
10448 - Make directory authorities more accurate at recording when
10449 relays that have failed several reachability tests became
10450 unreachable, so we can provide more accuracy at assigning Stable,
10451 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
10452 - Directory authorities are now more robust to hops back in time
10453 when calculating router stability. Previously, if a run of uptime
10454 or downtime appeared to be negative, the calculation could give
10455 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
10457 - Directory authorities will now attempt to download consensuses
10458 if their own efforts to make a live consensus have failed. This
10459 change means authorities that restart will fetch a valid
10460 consensus, and it means authorities that didn't agree with the
10461 current consensus will still fetch and serve it if it has enough
10462 signatures. Bugfix on 0.2.0.9-alpha; fixes bug 1300.
10463 - Never vote for a server as "Running" if we have a descriptor for
10464 it claiming to be hibernating, and that descriptor was published
10465 more recently than our last contact with the server. Bugfix on
10466 0.2.0.3-alpha; fixes bug 911.
10467 - Directory authorities no longer change their opinion of, or vote on,
10468 whether a router is Running, unless they have themselves been
10469 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
10472 o Minor bugfixes (hidden services):
10473 - Log malformed requests for rendezvous descriptors as protocol
10474 warnings, not warnings. Also, use a more informative log message
10475 in case someone sees it at log level warning without prior
10476 info-level messages. Fixes bug 2748; bugfix on 0.2.0.10-alpha.
10477 - Accept hidden service descriptors if we think we might be a hidden
10478 service directory, regardless of what our consensus says. This
10479 helps robustness, since clients and hidden services can sometimes
10480 have a more up-to-date view of the network consensus than we do,
10481 and if they think that the directory authorities list us a HSDir,
10482 we might actually be one. Related to bug 2732; bugfix on
10484 - Correct the warning displayed when a rendezvous descriptor exceeds
10485 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
10487 - Clients and hidden services now use HSDir-flagged relays for hidden
10488 service descriptor downloads and uploads even if the relays have no
10489 DirPort set and the client has disabled TunnelDirConns. This will
10490 eventually allow us to give the HSDir flag to relays with no
10491 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
10492 - Only limit the lengths of single HS descriptors, even when multiple
10493 HS descriptors are published to an HSDir relay in a single POST
10494 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
10496 o Minor bugfixes (controllers):
10497 - Allow GETINFO fingerprint to return a fingerprint even when
10498 we have not yet built a router descriptor. Fixes bug 3577;
10499 bugfix on 0.2.0.1-alpha.
10500 - Send a SUCCEEDED stream event to the controller when a reverse
10501 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
10502 discovered by katmagic.
10503 - Remove a trailing asterisk from "exit-policy/default" in the
10504 output of the control port command "GETINFO info/names". Bugfix
10506 - Make the SIGNAL DUMP controller command work on FreeBSD. Fixes bug
10507 2917. Bugfix on 0.1.1.1-alpha.
10508 - When we restart our relay, we might get a successful connection
10509 from the outside before we've started our reachability tests,
10510 triggering a warning: "ORPort found reachable, but I have no
10511 routerinfo yet. Failing to inform controller of success." This
10512 bug was harmless unless Tor is running under a controller
10513 like Vidalia, in which case the controller would never get a
10514 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
10516 - When a controller changes TrackHostExits, remove mappings for
10517 hosts that should no longer have their exits tracked. Bugfix on
10519 - When a controller changes VirtualAddrNetwork, remove any mappings
10520 for hosts that were automapped to the old network. Bugfix on
10522 - When a controller changes one of the AutomapHosts* options, remove
10523 any mappings for hosts that should no longer be automapped. Bugfix
10525 - Fix an off-by-one error in calculating some controller command
10526 argument lengths. Fortunately, this mistake is harmless since
10527 the controller code does redundant NUL termination too. Found by
10528 boboper. Bugfix on 0.1.1.1-alpha.
10529 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
10530 would return "551 Internal error" rather than "552 Unrecognized key
10531 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
10532 - Don't spam the controller with events when we have no file
10533 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
10534 for log messages was already solved from bug 748.)
10535 - Emit a GUARD DROPPED controller event for a case we missed.
10536 - Ensure DNS requests launched by "RESOLVE" commands from the
10537 controller respect the __LeaveStreamsUnattached setconf options. The
10538 same goes for requests launched via DNSPort or transparent
10539 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
10541 o Minor bugfixes (config options):
10542 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
10543 Change the limit to 512 characters by removing base64 newlines.
10544 Fixes bug 2752. Fix by Michael Yakubovich.
10545 - Complain if PublishServerDescriptor is given multiple arguments that
10546 include 0 or 1. This configuration will be rejected in the future.
10547 Bugfix on 0.2.0.1-alpha; closes bug 1107.
10548 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
10549 Bugfix on 0.2.0.13-alpha; closes bug 928.
10551 o Minor bugfixes (log subsystem fixes):
10552 - When unable to format an address as a string, report its value
10553 as "???" rather than reusing the last formatted address. Bugfix
10555 - Be more consistent in our treatment of file system paths. "~" should
10556 get expanded to the user's home directory in the Log config option.
10557 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
10558 feature for the -f and --DataDirectory options.
10560 o Minor bugfixes (memory management):
10561 - Don't stack-allocate the list of supplementary GIDs when we're
10562 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
10563 could take up to 256K, which is way too much stack. Found by
10564 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
10565 - Save a couple bytes in memory allocation every time we escape
10566 certain characters in a string. Patch from Florian Zumbiehl.
10568 o Minor bugfixes (protocol correctness):
10569 - When checking for 1024-bit keys, check for 1024 bits, not 128
10570 bytes. This allows Tor to correctly discard keys of length 1017
10571 through 1023. Bugfix on 0.0.9pre5.
10572 - Require that introduction point keys and onion handshake keys
10573 have a public exponent of 65537. Starts to fix bug 3207; bugfix
10575 - Handle SOCKS messages longer than 128 bytes long correctly, rather
10576 than waiting forever for them to finish. Fixes bug 2330; bugfix
10577 on 0.2.0.16-alpha. Found by doorss.
10578 - Never relay a cell for a circuit we have already destroyed.
10579 Between marking a circuit as closeable and finally closing it,
10580 it may have been possible for a few queued cells to get relayed,
10581 even though they would have been immediately dropped by the next
10582 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
10583 - Never queue a cell for a circuit that's already been marked
10585 - Fix a spec conformance issue: the network-status-version token
10586 must be the first token in a v3 consensus or vote. Discovered by
10587 "parakeep". Bugfix on 0.2.0.3-alpha.
10588 - A networkstatus vote must contain exactly one signature. Spec
10589 conformance issue. Bugfix on 0.2.0.3-alpha.
10590 - When asked about a DNS record type we don't support via a
10591 client DNSPort, reply with NOTIMPL rather than an empty
10592 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
10593 - Make more fields in the controller protocol case-insensitive, since
10594 control-spec.txt said they were.
10596 o Minor bugfixes (log messages):
10597 - Fix a log message that said "bits" while displaying a value in
10598 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
10600 - Downgrade "no current certificates known for authority" message from
10601 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
10602 - Correctly describe errors that occur when generating a TLS object.
10603 Previously we would attribute them to a failure while generating a
10604 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
10606 - Fix an instance where a Tor directory mirror might accidentally
10607 log the IP address of a misbehaving Tor client. Bugfix on
10609 - Stop logging at severity 'warn' when some other Tor client tries
10610 to establish a circuit with us using weak DH keys. It's a protocol
10611 violation, but that doesn't mean ordinary users need to hear about
10612 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
10613 - If your relay can't keep up with the number of incoming create
10614 cells, it would log one warning per failure into your logs. Limit
10615 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
10617 o Minor bugfixes (build fixes):
10618 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
10619 - When warning about missing zlib development packages during compile,
10620 give the correct package names. Bugfix on 0.2.0.1-alpha.
10621 - Fix warnings that newer versions of autoconf produce during
10622 ./autogen.sh. These warnings appear to be harmless in our case,
10623 but they were extremely verbose. Fixes bug 2020.
10624 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
10627 o Minor bugfixes (portability):
10628 - Write several files in text mode, on OSes that distinguish text
10629 mode from binary mode (namely, Windows). These files are:
10630 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
10631 that collect those statistics; 'client_keys' and 'hostname' for
10632 hidden services that use authentication; and (in the tor-gencert
10633 utility) newly generated identity and signing keys. Previously,
10634 we wouldn't specify text mode or binary mode, leading to an
10635 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
10636 the DirRecordUsageByCountry option which would have triggered
10637 the assertion failure was added), although this assertion failure
10638 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
10639 - Selectively disable deprecation warnings on OS X because Lion
10640 started deprecating the shipped copy of openssl. Fixes bug 3643.
10641 - Use a wide type to hold sockets when built for 64-bit Windows.
10643 - Fix an issue that prevented static linking of libevent on
10644 some platforms (notably Linux). Fixes bug 2698; bugfix on 0.2.1.23,
10645 where we introduced the "--with-static-libevent" configure option.
10646 - Fix a bug with our locking implementation on Windows that couldn't
10647 correctly detect when a file was already locked. Fixes bug 2504,
10648 bugfix on 0.2.1.6-alpha.
10649 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
10651 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
10652 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
10655 o Minor bugfixes (code correctness):
10656 - Always NUL-terminate the sun_path field of a sockaddr_un before
10657 passing it to the kernel. (Not a security issue: kernels are
10658 smart enough to reject bad sockaddr_uns.) Found by Coverity;
10659 CID #428. Bugfix on Tor 0.2.0.3-alpha.
10660 - Make connection_printf_to_buf()'s behavior sane. Its callers
10661 expect it to emit a CRLF iff the format string ends with CRLF;
10662 it actually emitted a CRLF iff (a) the format string ended with
10663 CRLF or (b) the resulting string was over 1023 characters long or
10664 (c) the format string did not end with CRLF *and* the resulting
10665 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
10666 fixes part of bug 3407.
10667 - Make send_control_event_impl()'s behavior sane. Its callers
10668 expect it to always emit a CRLF at the end of the string; it
10669 might have emitted extra control characters as well. Bugfix on
10670 0.1.1.9-alpha; fixes another part of bug 3407.
10671 - Make crypto_rand_int() check the value of its input correctly.
10672 Previously, it accepted values up to UINT_MAX, but could return a
10673 negative number if given a value above INT_MAX+1. Found by George
10674 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
10675 - Fix a potential null-pointer dereference while computing a
10676 consensus. Bugfix on 0.2.0.3-alpha, found with the help of
10678 - If we fail to compute the identity digest of a v3 legacy keypair,
10679 warn, and don't use a buffer-full of junk instead. Bugfix on
10680 0.2.1.1-alpha; fixes bug 3106.
10681 - Resolve an untriggerable issue in smartlist_string_num_isin(),
10682 where if the function had ever in the future been used to check
10683 for the presence of a too-large number, it would have given an
10684 incorrect result. (Fortunately, we only used it for 16-bit
10685 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
10686 - Be more careful about reporting the correct error from a failed
10687 connect() system call. Under some circumstances, it was possible to
10688 look at an incorrect value for errno when sending the end reason.
10689 Bugfix on 0.1.0.1-rc.
10690 - Correctly handle an "impossible" overflow cases in connection byte
10691 counting, where we write or read more than 4GB on an edge connection
10692 in a single second. Bugfix on 0.1.2.8-beta.
10693 - Avoid a double mark-for-free warning when failing to attach a
10694 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
10696 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
10697 found by "cypherpunks". This bug was introduced before the first
10698 Tor release, in svn commit r110.
10699 - Fix a bug in bandwidth history state parsing that could have been
10700 triggered if a future version of Tor ever changed the timing
10701 granularity at which bandwidth history is measured. Bugfix on
10702 Tor 0.1.1.11-alpha.
10703 - Add assertions to check for overflow in arguments to
10704 base32_encode() and base32_decode(); fix a signed-unsigned
10705 comparison there too. These bugs are not actually reachable in Tor,
10706 but it's good to prevent future errors too. Found by doorss.
10707 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
10709 - Set target port in get_interface_address6() correctly. Bugfix
10710 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
10711 - Fix an impossible-to-actually-trigger buffer overflow in relay
10712 descriptor generation. Bugfix on 0.1.0.15.
10713 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
10715 o Minor bugfixes (code improvements):
10716 - After we free an internal connection structure, overwrite it
10717 with a different memory value than we use for overwriting a freed
10718 internal circuit structure. Should help with debugging. Suggested
10720 - If OpenSSL fails to make a duplicate of a private or public key, log
10721 an error message and try to exit cleanly. May help with debugging
10722 if bug 1209 ever remanifests.
10723 - Some options used different conventions for uppercasing of acronyms
10724 when comparing manpage and source. Fix those in favor of the
10725 manpage, as it makes sense to capitalize acronyms.
10726 - Take a first step towards making or.h smaller by splitting out
10727 function definitions for all source files in src/or/. Leave
10728 structures and defines in or.h for now.
10729 - Remove a few dead assignments during router parsing. Found by
10731 - Don't use 1-bit wide signed bit fields. Found by coverity.
10732 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
10733 None of the cases where we did this before were wrong, but by making
10734 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
10735 - The memarea code now uses a sentinel value at the end of each area
10736 to make sure nothing writes beyond the end of an area. This might
10737 help debug some conceivable causes of bug 930.
10738 - Always treat failure to allocate an RSA key as an unrecoverable
10740 - Add some more defensive programming for architectures that can't
10741 handle unaligned integer accesses. We don't know of any actual bugs
10742 right now, but that's the best time to fix them. Fixes bug 1943.
10744 o Minor bugfixes (misc):
10745 - Fix a rare bug in rend_fn unit tests: we would fail a test when
10746 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
10747 on 0.2.0.10-alpha; fixes bug 1808.
10748 - Where available, use Libevent 2.0's periodic timers so that our
10749 once-per-second cleanup code gets called even more closely to
10750 once per second than it would otherwise. Fixes bug 943.
10751 - Ignore OutboundBindAddress when connecting to localhost.
10752 Connections to localhost need to come _from_ localhost, or else
10753 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
10755 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
10757 - If any of the v3 certs we download are unparseable, we should
10758 actually notice the failure so we don't retry indefinitely. Bugfix
10759 on 0.2.0.x; reported by "rotator".
10760 - When Tor fails to parse a descriptor of any kind, dump it to disk.
10761 Might help diagnosing bug 1051.
10762 - Make our 'torify' script more portable; if we have only one of
10763 'torsocks' or 'tsocks' installed, don't complain to the user;
10764 and explain our warning about tsocks better.
10765 - Fix some urls in the exit notice file and make it XHTML1.1 strict
10766 compliant. Based on a patch from Christian Kujau.
10768 o Documentation changes:
10769 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
10770 - Resolve all doxygen warnings except those for missing documentation.
10772 - Add doxygen documentation for more functions, fields, and types.
10773 - Convert the HACKING file to asciidoc, and add a few new sections
10774 to it, explaining how we use Git, how we make changelogs, and
10775 what should go in a patch.
10776 - Document the default socks host and port (127.0.0.1:9050) for
10778 - Removed some unnecessary files from the source distribution. The
10779 AUTHORS file has now been merged into the people page on the
10780 website. The roadmaps and design doc can now be found in the
10781 projects directory in svn.
10783 o Deprecated and removed features (config):
10784 - Remove the torrc.complete file. It hasn't been kept up to date
10785 and users will have better luck checking out the manpage.
10786 - Remove the HSAuthorityRecordStats option that version 0 hidden
10787 service authorities could use to track statistics of overall v0
10788 hidden service usage.
10789 - Remove the obsolete "NoPublish" option; it has been flagged
10790 as obsolete and has produced a warning since 0.1.1.18-rc.
10791 - Caches no longer download and serve v2 networkstatus documents
10792 unless FetchV2Networkstatus flag is set: these documents haven't
10793 haven't been used by clients or relays since 0.2.0.x. Resolves
10796 o Deprecated and removed features (controller):
10797 - The controller no longer accepts the old obsolete "addr-mappings/"
10798 or "unregistered-servers-" GETINFO values.
10799 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
10800 always on; using them is necessary for correct forward-compatible
10803 o Deprecated and removed features (misc):
10804 - Hidden services no longer publish version 0 descriptors, and clients
10805 do not request or use version 0 descriptors. However, the old hidden
10806 service authorities still accept and serve version 0 descriptors
10807 when contacted by older hidden services/clients.
10808 - Remove undocumented option "-F" from tor-resolve: it hasn't done
10809 anything since 0.2.1.16-rc.
10810 - Remove everything related to building the expert bundle for OS X.
10811 It has confused many users, doesn't work right on OS X 10.6,
10812 and is hard to get rid of once installed. Resolves bug 1274.
10813 - Remove support for .noconnect style addresses. Nobody was using
10814 them, and they provided another avenue for detecting Tor users
10815 via application-level web tricks.
10816 - When we fixed bug 1038 we had to put in a restriction not to send
10817 RELAY_EARLY cells on rend circuits. This was necessary as long
10818 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
10819 active. Now remove this obsolete check. Resolves bug 2081.
10820 - Remove workaround code to handle directory responses from servers
10821 that had bug 539 (they would send HTTP status 503 responses _and_
10822 send a body too). Since only server versions before
10823 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
10824 keep the workaround in place.
10825 - Remove the old 'fuzzy time' logic. It was supposed to be used for
10826 handling calculations where we have a known amount of clock skew and
10827 an allowed amount of unknown skew. But we only used it in three
10828 places, and we never adjusted the known/unknown skew values. This is
10829 still something we might want to do someday, but if we do, we'll
10830 want to do it differently.
10831 - Remove the "--enable-iphone" option to ./configure. According to
10832 reports from Marco Bonetti, Tor builds fine without any special
10833 tweaking on recent iPhone SDK versions.
10836 Changes in version 0.2.1.30 - 2011-02-23
10837 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
10838 change is a slight tweak to Tor's TLS handshake that makes relays
10839 and bridges that run this new version reachable from Iran again.
10840 We don't expect this tweak will win the arms race long-term, but it
10841 buys us time until we roll out a better solution.
10844 - Stop sending a CLOCK_SKEW controller status event whenever
10845 we fetch directory information from a relay that has a wrong clock.
10846 Instead, only inform the controller when it's a trusted authority
10847 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
10848 the rest of bug 1074.
10849 - Fix a bounds-checking error that could allow an attacker to
10850 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
10851 Found by "piebeer".
10852 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
10853 Tor would ignore their RelayBandwidthBurst setting,
10854 potentially using more bandwidth than expected. Bugfix on
10855 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
10856 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
10857 hidserv" in her torrc. The 'hidserv' argument never controlled
10858 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
10861 - Adjust our TLS Diffie-Hellman parameters to match those used by
10863 - Update to the February 1 2011 Maxmind GeoLite Country database.
10866 - Check for and reject overly long directory certificates and
10867 directory tokens before they have a chance to hit any assertions.
10868 Bugfix on 0.2.1.28. Found by "doorss".
10869 - Bring the logic that gathers routerinfos and assesses the
10870 acceptability of circuits into line. This prevents a Tor OP from
10871 getting locked in a cycle of choosing its local OR as an exit for a
10872 path (due to a .exit request) and then rejecting the circuit because
10873 its OR is not listed yet. It also prevents Tor clients from using an
10874 OR running in the same instance as an exit (due to a .exit request)
10875 if the OR does not meet the same requirements expected of an OR
10876 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
10878 o Packaging changes:
10879 - Stop shipping the Tor specs files and development proposal documents
10880 in the tarball. They are now in a separate git repository at
10881 git://git.torproject.org/torspec.git
10882 - Do not include Git version tags as though they are SVN tags when
10883 generating a tarball from inside a repository that has switched
10884 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
10887 Changes in version 0.2.1.29 - 2011-01-15
10888 Tor 0.2.1.29 continues our recent code security audit work. The main
10889 fix resolves a remote heap overflow vulnerability that can allow remote
10890 code execution. Other fixes address a variety of assert and crash bugs,
10891 most of which we think are hard to exploit remotely.
10893 o Major bugfixes (security):
10894 - Fix a heap overflow bug where an adversary could cause heap
10895 corruption. This bug probably allows remote code execution
10896 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
10898 - Prevent a denial-of-service attack by disallowing any
10899 zlib-compressed data whose compression factor is implausibly
10900 high. Fixes part of bug 2324; reported by "doorss".
10901 - Zero out a few more keys in memory before freeing them. Fixes
10902 bug 2384 and part of bug 2385. These key instances found by
10903 "cypherpunks", based on Andrew Case's report about being able
10904 to find sensitive data in Tor's memory space if you have enough
10905 permissions. Bugfix on 0.0.2pre9.
10907 o Major bugfixes (crashes):
10908 - Prevent calls to Libevent from inside Libevent log handlers.
10909 This had potential to cause a nasty set of crashes, especially
10910 if running Libevent with debug logging enabled, and running
10911 Tor with a controller watching for low-severity log messages.
10912 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
10913 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
10914 underflow errors there too. Fixes the other part of bug 2324.
10915 - Fix a bug where we would assert if we ever had a
10916 cached-descriptors.new file (or another file read directly into
10917 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
10918 on 0.2.1.25. Found by doorss.
10919 - Fix some potential asserts and parsing issues with grossly
10920 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
10923 o Minor bugfixes (other):
10924 - Fix a bug with handling misformed replies to reverse DNS lookup
10925 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
10926 bug reported by doorss.
10927 - Fix compilation on mingw when a pthreads compatibility library
10928 has been installed. (We don't want to use it, so we shouldn't
10929 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
10930 - Fix a bug where we would declare that we had run out of virtual
10931 addresses when the address space was only half-exhausted. Bugfix
10933 - Correctly handle the case where AutomapHostsOnResolve is set but
10934 no virtual addresses are available. Fixes bug 2328; bugfix on
10935 0.1.2.1-alpha. Bug found by doorss.
10936 - Correctly handle wrapping around when we run out of virtual
10937 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
10940 - Update to the January 1 2011 Maxmind GeoLite Country database.
10941 - Introduce output size checks on all of our decryption functions.
10944 - Tor does not build packages correctly with Automake 1.6 and earlier;
10945 added a check to Makefile.am to make sure that we're building with
10946 Automake 1.7 or later.
10947 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
10948 because we built it with a too-old version of automake. Thus that
10949 release broke ./configure --enable-openbsd-malloc, which is popular
10950 among really fast exit relays on Linux.
10953 Changes in version 0.2.1.28 - 2010-12-17
10954 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
10955 exploitable bugs. We also took this opportunity to change the IP address
10956 for one of our directory authorities, and to update the geoip database
10960 - Fix a remotely exploitable bug that could be used to crash instances
10961 of Tor remotely by overflowing on the heap. Remote-code execution
10962 hasn't been confirmed, but can't be ruled out. Everyone should
10963 upgrade. Bugfix on the 0.1.1 series and later.
10965 o Directory authority changes:
10966 - Change IP address and ports for gabelmoo (v3 directory authority).
10969 - Update to the December 1 2010 Maxmind GeoLite Country database.
10972 Changes in version 0.2.1.27 - 2010-11-23
10973 Yet another OpenSSL security patch broke its compatibility with Tor:
10974 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
10975 also took this opportunity to fix several crash bugs, integrate a new
10976 directory authority, and update the bundled GeoIP database.
10979 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
10980 No longer set the tlsext_host_name extension on server SSL objects;
10981 but continue to set it on client SSL objects. Our goal in setting
10982 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
10983 bugfix on 0.2.1.1-alpha.
10984 - Do not log messages to the controller while shrinking buffer
10985 freelists. Doing so would sometimes make the controller connection
10986 try to allocate a buffer chunk, which would mess up the internals
10987 of the freelist and cause an assertion failure. Fixes bug 1125;
10988 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
10989 - Learn our external IP address when we're a relay or bridge, even if
10990 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
10991 where we introduced bridge relays that don't need to publish to
10992 be useful. Fixes bug 2050.
10993 - Do even more to reject (and not just ignore) annotations on
10994 router descriptors received anywhere but from the cache. Previously
10995 we would ignore such annotations at first, but cache them to disk
10996 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
10997 - When you're using bridges and your network goes away and your
10998 bridges get marked as down, recover when you attempt a new socks
10999 connection (if the network is back), rather than waiting up to an
11000 hour to try fetching new descriptors for your bridges. Bugfix on
11001 0.2.0.3-alpha; fixes bug 1981.
11004 - Move to the November 2010 Maxmind GeoLite country db (rather
11005 than the June 2009 ip-to-country GeoIP db) for our statistics that
11006 count how many users relays are seeing from each country. Now we'll
11007 have more accurate data, especially for many African countries.
11009 o New directory authorities:
11010 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
11014 - Fix an assertion failure that could occur in directory caches or
11015 bridge users when using a very short voting interval on a testing
11016 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
11018 - Enforce multiplicity rules when parsing annotations. Bugfix on
11019 0.2.0.8-alpha. Found by piebeer.
11020 - Allow handshaking OR connections to take a full KeepalivePeriod
11021 seconds to handshake. Previously, we would close them after
11022 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
11023 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
11025 - When building with --enable-gcc-warnings on OpenBSD, disable
11026 warnings in system headers. This makes --enable-gcc-warnings
11027 pass on OpenBSD 4.8.
11030 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
11031 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
11032 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
11033 Servers can start sending this code when enough clients recognize
11034 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
11035 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
11036 Patch from mingw-san.
11039 - Remove the old debian/ directory from the main Tor distribution.
11040 The official Tor-for-debian git repository lives at the URL
11041 https://git.torproject.org/debian/tor.git
11042 - Stop shipping the old doc/website/ directory in the tarball. We
11043 changed the website format in late 2010, and what we shipped in
11044 0.2.1.26 really wasn't that useful anyway.
11047 Changes in version 0.2.1.26 - 2010-05-02
11048 Tor 0.2.1.26 addresses the recent connection and memory overload
11049 problems we've been seeing on relays, especially relays with their
11050 DirPort open. If your relay has been crashing, or you turned it off
11051 because it used too many resources, give this release a try.
11053 This release also fixes yet another instance of broken OpenSSL libraries
11054 that was causing some relays to drop out of the consensus.
11057 - Teach relays to defend themselves from connection overload. Relays
11058 now close idle circuits early if it looks like they were intended
11059 for directory fetches. Relays are also more aggressive about closing
11060 TLS connections that have no circuits on them. Such circuits are
11061 unlikely to be re-used, and tens of thousands of them were piling
11062 up at the fast relays, causing the relays to run out of sockets
11063 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
11064 their directory fetches over TLS).
11065 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
11066 that claim to be earlier than 0.9.8m, but which have in reality
11067 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
11068 behavior. Possible fix for some cases of bug 1346.
11069 - Directory mirrors were fetching relay descriptors only from v2
11070 directory authorities, rather than v3 authorities like they should.
11071 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
11072 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
11075 - Finally get rid of the deprecated and now harmful notion of "clique
11076 mode", where directory authorities maintain TLS connections to
11080 - In the util/threads test, no longer free the test_mutex before all
11081 worker threads have finished. Bugfix on 0.2.1.6-alpha.
11082 - The master thread could starve the worker threads quite badly on
11083 certain systems, causing them to run only partially in the allowed
11084 window. This resulted in test failures. Now the master thread sleeps
11085 occasionally for a few microseconds while the two worker-threads
11086 compete for the mutex. Bugfix on 0.2.0.1-alpha.
11089 Changes in version 0.2.1.25 - 2010-03-16
11090 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
11091 prevent relays from guessing their IP address correctly. It also fixes
11092 several minor potential security bugs.
11095 - Fix a regression from our patch for bug 1244 that caused relays
11096 to guess their IP address incorrectly if they didn't set Address
11097 in their torrc and/or their address fails to resolve. Bugfix on
11098 0.2.1.23; fixes bug 1269.
11099 - When freeing a session key, zero it out completely. We only zeroed
11100 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
11101 patched by ekir. Fixes bug 1254.
11104 - Fix a dereference-then-NULL-check sequence when publishing
11105 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
11107 - Fix another dereference-then-NULL-check sequence. Bugfix on
11108 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
11109 - Make sure we treat potentially not NUL-terminated strings correctly.
11110 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
11113 Changes in version 0.2.1.24 - 2010-02-21
11114 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
11118 - Work correctly out-of-the-box with even more vendor-patched versions
11119 of OpenSSL. In particular, make it so Debian and OS X don't need
11120 customized patches to run/build.
11123 Changes in version 0.2.1.23 - 2010-02-13
11124 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
11125 again on the latest OS X, and updates the location of a directory
11128 o Major bugfixes (performance):
11129 - We were selecting our guards uniformly at random, and then weighting
11130 which of our guards we'd use uniformly at random. This imbalance
11131 meant that Tor clients were severely limited on throughput (and
11132 probably latency too) by the first hop in their circuit. Now we
11133 select guards weighted by currently advertised bandwidth. We also
11134 automatically discard guards picked using the old algorithm. Fixes
11135 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
11138 - Make Tor work again on the latest OS X: when deciding whether to
11139 use strange flags to turn TLS renegotiation on, detect the OpenSSL
11140 version at run-time, not compile time. We need to do this because
11141 Apple doesn't update its dev-tools headers when it updates its
11142 libraries in a security patch.
11143 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
11144 that could happen on 32-bit platforms with 64-bit time_t. Also fix
11145 a memory leak when requesting a hidden service descriptor we've
11146 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
11150 - Refactor resolve_my_address() to not use gethostbyname() anymore.
11151 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
11154 - Avoid a mad rush at the beginning of each month when each client
11155 rotates half of its guards. Instead we spread the rotation out
11156 throughout the month, but we still avoid leaving a precise timestamp
11157 in the state file about when we first picked the guard. Improves
11158 over the behavior introduced in 0.1.2.17.
11161 Changes in version 0.2.1.22 - 2010-01-19
11162 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
11163 authorities -- it would tell you its whole history of bridge descriptors
11164 if you make the right directory request. This stable update also
11165 rotates two of the seven v3 directory authority keys and locations.
11167 o Directory authority changes:
11168 - Rotate keys (both v3 identity and relay identity) for moria1
11172 - Stop bridge directory authorities from answering dbg-stability.txt
11173 directory queries, which would let people fetch a list of all
11174 bridge identities they track. Bugfix on 0.2.1.6-alpha.
11177 Changes in version 0.2.1.21 - 2009-12-21
11178 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
11179 library. If you use Tor on Linux / Unix and you're getting SSL
11180 renegotiation errors, upgrading should help. We also recommend an
11181 upgrade if you're an exit relay.
11184 - Work around a security feature in OpenSSL 0.9.8l that prevents our
11185 handshake from working unless we explicitly tell OpenSSL that we
11186 are using SSL renegotiation safely. We are, of course, but OpenSSL
11187 0.9.8l won't work unless we say we are.
11188 - Avoid crashing if the client is trying to upload many bytes and the
11189 circuit gets torn down at the same time, or if the flip side
11190 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
11193 - Do not refuse to learn about authority certs and v2 networkstatus
11194 documents that are older than the latest consensus. This bug might
11195 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
11196 Spotted and fixed by xmux.
11197 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
11198 trigger platform-specific option misparsing case found by Coverity
11200 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
11201 trigger assert. Fixes bug 1173.
11204 Changes in version 0.2.1.20 - 2009-10-15
11205 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
11206 services at once, prepares for more performance improvements, and
11207 fixes a bunch of smaller bugs.
11209 The Windows and OS X bundles also include a more recent Vidalia,
11210 and switch from Privoxy to Polipo.
11212 The OS X installers are now drag and drop. It's best to un-install
11213 Tor/Vidalia and then install this new bundle, rather than upgrade. If
11214 you want to upgrade, you'll need to update the paths for Tor and Polipo
11215 in the Vidalia Settings window.
11218 - Send circuit or stream sendme cells when our window has decreased
11219 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
11220 by Karsten when testing the "reduce circuit window" performance
11221 patch. Bugfix on the 54th commit on Tor -- from July 2002,
11222 before the release of Tor 0.0.0. This is the new winner of the
11224 - Fix a remotely triggerable memory leak when a consensus document
11225 contains more than one signature from the same voter. Bugfix on
11227 - Avoid segfault in rare cases when finishing an introduction circuit
11228 as a client and finding out that we don't have an introduction key
11229 for it. Fixes bug 1073. Reported by Aaron Swartz.
11232 - Tor now reads the "circwindow" parameter out of the consensus,
11233 and uses that value for its circuit package window rather than the
11234 default of 1000 cells. Begins the implementation of proposal 168.
11236 o New directory authorities:
11237 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
11239 - Move moria1 and tonga to alternate IP addresses.
11242 - Fix a signed/unsigned compile warning in 0.2.1.19.
11243 - Fix possible segmentation fault on directory authorities. Bugfix on
11245 - Fix an extremely rare infinite recursion bug that could occur if
11246 we tried to log a message after shutting down the log subsystem.
11247 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
11248 - Fix an obscure bug where hidden services on 64-bit big-endian
11249 systems might mis-read the timestamp in v3 introduce cells, and
11250 refuse to connect back to the client. Discovered by "rotor".
11251 Bugfix on 0.2.1.6-alpha.
11252 - We were triggering a CLOCK_SKEW controller status event whenever
11253 we connect via the v2 connection protocol to any relay that has
11254 a wrong clock. Instead, we should only inform the controller when
11255 it's a trusted authority that claims our clock is wrong. Bugfix
11256 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
11257 - We were telling the controller about CHECKING_REACHABILITY and
11258 REACHABILITY_FAILED status events whenever we launch a testing
11259 circuit or notice that one has failed. Instead, only tell the
11260 controller when we want to inform the user of overall success or
11261 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
11263 - Don't warn when we're using a circuit that ends with a node
11264 excluded in ExcludeExitNodes, but the circuit is not used to access
11265 the outside world. This should help fix bug 1090. Bugfix on
11267 - Work around a small memory leak in some versions of OpenSSL that
11268 stopped the memory used by the hostname TLS extension from being
11272 - Add a "getinfo status/accepted-server-descriptor" controller
11273 command, which is the recommended way for controllers to learn
11274 whether our server descriptor has been successfully received by at
11275 least on directory authority. Un-recommend good-server-descriptor
11276 getinfo and status events until we have a better design for them.
11279 Changes in version 0.2.1.19 - 2009-07-28
11280 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
11284 - Make accessing hidden services on 0.2.1.x work right again.
11285 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
11286 part of patch provided by "optimist".
11289 - When a relay/bridge is writing out its identity key fingerprint to
11290 the "fingerprint" file and to its logs, write it without spaces. Now
11291 it will look like the fingerprints in our bridges documentation,
11292 and confuse fewer users.
11295 - Relays no longer publish a new server descriptor if they change
11296 their MaxAdvertisedBandwidth config option but it doesn't end up
11297 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
11298 fixes bug 1026. Patch from Sebastian.
11299 - Avoid leaking memory every time we get a create cell but we have
11300 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
11301 fixes bug 1034. Reported by BarkerJr.
11304 Changes in version 0.2.1.18 - 2009-07-24
11305 Tor 0.2.1.18 lays the foundations for performance improvements,
11306 adds status events to help users diagnose bootstrap problems, adds
11307 optional authentication/authorization for hidden services, fixes a
11308 variety of potential anonymity problems, and includes a huge pile of
11309 other features and bug fixes.
11311 o Major features (clients):
11312 - Start sending "bootstrap phase" status events to the controller,
11313 so it can keep the user informed of progress fetching directory
11314 information and establishing circuits. Also inform the controller
11315 if we think we're stuck at a particular bootstrap phase. Implements
11317 - Clients replace entry guards that were chosen more than a few months
11318 ago. This change should significantly improve client performance,
11319 especially once more people upgrade, since relays that have been
11320 a guard for a long time are currently overloaded.
11321 - Network status consensus documents and votes now contain bandwidth
11322 information for each relay. Clients use the bandwidth values
11323 in the consensus, rather than the bandwidth values in each
11324 relay descriptor. This approach opens the door to more accurate
11325 bandwidth estimates once the directory authorities start doing
11326 active measurements. Implements part of proposal 141.
11328 o Major features (relays):
11329 - Disable and refactor some debugging checks that forced a linear scan
11330 over the whole server-side DNS cache. These accounted for over 50%
11331 of CPU time on a relatively busy exit node's gprof profile. Also,
11332 disable some debugging checks that appeared in exit node profile
11333 data. Found by Jacob.
11334 - New DirPortFrontPage option that takes an html file and publishes
11335 it as "/" on the DirPort. Now relay operators can provide a
11336 disclaimer without needing to set up a separate webserver. There's
11337 a sample disclaimer in contrib/tor-exit-notice.html.
11339 o Major features (hidden services):
11340 - Make it possible to build hidden services that only certain clients
11341 are allowed to connect to. This is enforced at several points,
11342 so that unauthorized clients are unable to send INTRODUCE cells
11343 to the service, or even (depending on the type of authentication)
11344 to learn introduction points. This feature raises the bar for
11345 certain kinds of active attacks against hidden services. Design
11346 and code by Karsten Loesing. Implements proposal 121.
11347 - Relays now store and serve v2 hidden service descriptors by default,
11348 i.e., the new default value for HidServDirectoryV2 is 1. This is
11349 the last step in proposal 114, which aims to make hidden service
11350 lookups more reliable.
11352 o Major features (path selection):
11353 - ExitNodes and Exclude*Nodes config options now allow you to restrict
11354 by country code ("{US}") or IP address or address pattern
11355 ("255.128.0.0/16"). Patch from Robert Hogan. It still needs some
11356 refinement to decide what config options should take priority if
11357 you ask to both use a particular node and exclude it.
11359 o Major features (misc):
11360 - When building a consensus, do not include routers that are down.
11361 This cuts down 30% to 40% on consensus size. Implements proposal
11363 - New TestingTorNetwork config option to allow adjustment of
11364 previously constant values that could slow bootstrapping. Implements
11365 proposal 135. Patch from Karsten.
11366 - Convert many internal address representations to optionally hold
11367 IPv6 addresses. Generate and accept IPv6 addresses in many protocol
11368 elements. Make resolver code handle nameservers located at IPv6
11370 - More work on making our TLS handshake blend in: modify the list
11371 of ciphers advertised by OpenSSL in client mode to even more
11372 closely resemble a common web browser. We cheat a little so that
11373 we can advertise ciphers that the locally installed OpenSSL doesn't
11375 - Use the TLS1 hostname extension to more closely resemble browser
11378 o Security fixes (anonymity/entropy):
11379 - Never use a connection with a mismatched address to extend a
11380 circuit, unless that connection is canonical. A canonical
11381 connection is one whose address is authenticated by the router's
11382 identity key, either in a NETINFO cell or in a router descriptor.
11383 - Implement most of proposal 110: The first K cells to be sent
11384 along a circuit are marked as special "early" cells; only K "early"
11385 cells will be allowed. Once this code is universal, we can block
11386 certain kinds of denial-of-service attack by requiring that EXTEND
11387 commands must be sent using an "early" cell.
11388 - Resume using OpenSSL's RAND_poll() for better (and more portable)
11389 cross-platform entropy collection again. We used to use it, then
11390 stopped using it because of a bug that could crash systems that
11391 called RAND_poll when they had a lot of fds open. It looks like the
11392 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
11393 at startup, and to call RAND_poll() when we reseed later only if
11394 we have a non-buggy OpenSSL version.
11395 - When the client is choosing entry guards, now it selects at most
11396 one guard from a given relay family. Otherwise we could end up with
11397 all of our entry points into the network run by the same operator.
11398 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
11399 - Do not use or believe expired v3 authority certificates. Patch
11400 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
11401 - Drop begin cells to a hidden service if they come from the middle
11402 of a circuit. Patch from lark.
11403 - When we erroneously receive two EXTEND cells for the same circuit
11404 ID on the same connection, drop the second. Patch from lark.
11405 - Authorities now vote for the Stable flag for any router whose
11406 weighted MTBF is at least 5 days, regardless of the mean MTBF.
11407 - Clients now never report any stream end reason except 'MISC'.
11408 Implements proposal 148.
11410 o Major bugfixes (crashes):
11411 - Parse dates and IPv4 addresses in a locale- and libc-independent
11412 manner, to avoid platform-dependent behavior on malformed input.
11413 - Fix a crash that occurs on exit nodes when a nameserver request
11414 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
11415 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
11417 - Do not assume that a stack-allocated character array will be
11418 64-bit aligned on platforms that demand that uint64_t access is
11419 aligned. Possible fix for bug 604.
11420 - Resolve a very rare crash bug that could occur when the user forced
11421 a nameserver reconfiguration during the middle of a nameserver
11422 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
11423 - Avoid a "0 divided by 0" calculation when calculating router uptime
11424 at directory authorities. Bugfix on 0.2.0.8-alpha.
11425 - Fix an assertion bug in parsing policy-related options; possible fix
11427 - Rate-limit too-many-sockets messages: when they happen, they happen
11428 a lot and end up filling up the disk. Resolves bug 748.
11429 - Fix a race condition that could cause crashes or memory corruption
11430 when running as a server with a controller listening for log
11432 - Avoid crashing when we have a policy specified in a DirPolicy or
11433 SocksPolicy or ReachableAddresses option with ports set on it,
11434 and we re-load the policy. May fix bug 996.
11435 - Fix an assertion failure on 64-bit platforms when we allocated
11436 memory right up to the end of a memarea, then realigned the memory
11437 one step beyond the end. Fixes a possible cause of bug 930.
11438 - Protect the count of open sockets with a mutex, so we can't
11439 corrupt it when two threads are closing or opening sockets at once.
11440 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
11442 o Major bugfixes (clients):
11443 - Discard router descriptors as we load them if they are more than
11444 five days old. Otherwise if Tor is off for a long time and then
11445 starts with cached descriptors, it will try to use the onion keys
11446 in those obsolete descriptors when building circuits. Fixes bug 887.
11447 - When we choose to abandon a new entry guard because we think our
11448 older ones might be better, close any circuits pending on that
11449 new entry guard connection. This fix should make us recover much
11450 faster when our network is down and then comes back. Bugfix on
11451 0.1.2.8-beta; found by lodger.
11452 - When Tor clients restart after 1-5 days, they discard all their
11453 cached descriptors as too old, but they still use the cached
11454 consensus document. This approach is good for robustness, but
11455 bad for performance: since they don't know any bandwidths, they
11456 end up choosing at random rather than weighting their choice by
11457 speed. Fixed by the above feature of putting bandwidths in the
11460 o Major bugfixes (relays):
11461 - Relays were falling out of the networkstatus consensus for
11462 part of a day if they changed their local config but the
11463 authorities discarded their new descriptor as "not sufficiently
11464 different". Now directory authorities accept a descriptor as changed
11465 if BandwidthRate or BandwidthBurst changed. Partial fix for bug 962;
11466 patch by Sebastian.
11467 - Ensure that two circuits can never exist on the same connection
11468 with the same circuit ID, even if one is marked for close. This
11469 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
11470 - Directory authorities were neglecting to mark relays down in their
11471 internal histories if the relays fall off the routerlist without
11472 ever being found unreachable. So there were relays in the histories
11473 that haven't been seen for eight months, and are listed as being
11474 up for eight months. This wreaked havoc on the "median wfu" and
11475 "median mtbf" calculations, in turn making Guard and Stable flags
11476 wrong, hurting network performance. Fixes bugs 696 and 969. Bugfix
11479 o Major bugfixes (hidden services):
11480 - When establishing a hidden service, introduction points that
11481 originate from cannibalized circuits were completely ignored
11482 and not included in rendezvous service descriptors. This might
11483 have been another reason for delay in making a hidden service
11484 available. Bugfix from long ago (0.0.9.x?)
11486 o Major bugfixes (memory and resource management):
11487 - Fixed some memory leaks -- some quite frequent, some almost
11488 impossible to trigger -- based on results from Coverity.
11489 - Speed up parsing and cut down on memory fragmentation by using
11490 stack-style allocations for parsing directory objects. Previously,
11491 this accounted for over 40% of allocations from within Tor's code
11492 on a typical directory cache.
11493 - Use a Bloom filter rather than a digest-based set to track which
11494 descriptors we need to keep around when we're cleaning out old
11495 router descriptors. This speeds up the computation significantly,
11496 and may reduce fragmentation.
11498 o New/changed config options:
11499 - Now NodeFamily and MyFamily config options allow spaces in
11500 identity fingerprints, so it's easier to paste them in.
11501 Suggested by Lucky Green.
11502 - Allow ports 465 and 587 in the default exit policy again. We had
11503 rejected them in 0.1.0.15, because back in 2005 they were commonly
11504 misconfigured and ended up as spam targets. We hear they are better
11505 locked down these days.
11506 - Make TrackHostExit mappings expire a while after their last use, not
11507 after their creation. Patch from Robert Hogan.
11508 - Add an ExcludeExitNodes option so users can list a set of nodes
11509 that should be be excluded from the exit node position, but
11510 allowed elsewhere. Implements proposal 151.
11511 - New --hush command-line option similar to --quiet. While --quiet
11512 disables all logging to the console on startup, --hush limits the
11513 output to messages of warning and error severity.
11514 - New configure/torrc options (--enable-geoip-stats,
11515 DirRecordUsageByCountry) to record how many IPs we've served
11516 directory info to in each country code, how many status documents
11517 total we've sent to each country code, and what share of the total
11518 directory requests we should expect to see.
11519 - Make outbound DNS packets respect the OutboundBindAddress setting.
11520 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
11521 - Allow separate log levels to be configured for different logging
11522 domains. For example, this allows one to log all notices, warnings,
11523 or errors, plus all memory management messages of level debug or
11524 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
11525 - Update to the "June 3 2009" ip-to-country file.
11527 o Minor features (relays):
11528 - Raise the minimum rate limiting to be a relay from 20000 bytes
11529 to 20480 bytes (aka 20KB/s), to match our documentation. Also
11530 update directory authorities so they always assign the Fast flag
11531 to relays with 20KB/s of capacity. Now people running relays won't
11532 suddenly find themselves not seeing any use, if the network gets
11534 - If we're a relay and we change our IP address, be more verbose
11535 about the reason that made us change. Should help track down
11536 further bugs for relays on dynamic IP addresses.
11537 - Exit servers can now answer resolve requests for ip6.arpa addresses.
11538 - Implement most of Proposal 152: allow specialized servers to permit
11539 single-hop circuits, and clients to use those servers to build
11540 single-hop circuits when using a specialized controller. Patch
11541 from Josh Albrecht. Resolves feature request 768.
11542 - When relays do their initial bandwidth measurement, don't limit
11543 to just our entry guards for the test circuits. Otherwise we tend
11544 to have multiple test circuits going through a single entry guard,
11545 which makes our bandwidth test less accurate. Fixes part of bug 654;
11546 patch contributed by Josh Albrecht.
11548 o Minor features (directory authorities):
11549 - Try not to open more than one descriptor-downloading connection
11550 to an authority at once. This should reduce load on directory
11551 authorities. Fixes bug 366.
11552 - Add cross-certification to newly generated certificates, so that
11553 a signing key is enough information to look up a certificate. Start
11554 serving certificates by <identity digest, signing key digest>
11555 pairs. Implements proposal 157.
11556 - When a directory authority downloads a descriptor that it then
11557 immediately rejects, do not retry downloading it right away. Should
11558 save some bandwidth on authorities. Fix for bug 888. Patch by
11560 - Directory authorities now serve a /tor/dbg-stability.txt URL to
11561 help debug WFU and MTBF calculations.
11562 - In directory authorities' approved-routers files, allow
11563 fingerprints with or without space.
11565 o Minor features (directory mirrors):
11566 - When a download gets us zero good descriptors, do not notify
11567 Tor that new directory information has arrived.
11568 - Servers support a new URL scheme for consensus downloads that
11569 allows the client to specify which authorities are trusted.
11570 The server then only sends the consensus if the client will trust
11571 it. Otherwise a 404 error is sent back. Clients use this
11572 new scheme when the server supports it (meaning it's running
11573 0.2.1.1-alpha or later). Implements proposal 134.
11575 o Minor features (bridges):
11576 - If the bridge config line doesn't specify a port, assume 443.
11577 This makes bridge lines a bit smaller and easier for users to
11579 - If we're using bridges and our network goes away, be more willing
11580 to forgive our bridges and try again when we get an application
11583 o Minor features (hidden services):
11584 - When the client launches an introduction circuit, retry with a
11585 new circuit after 30 seconds rather than 60 seconds.
11586 - Launch a second client-side introduction circuit in parallel
11587 after a delay of 15 seconds (based on work by Christian Wilms).
11588 - Hidden services start out building five intro circuits rather
11589 than three, and when the first three finish they publish a service
11590 descriptor using those. Now we publish our service descriptor much
11591 faster after restart.
11592 - Drop the requirement to have an open dir port for storing and
11593 serving v2 hidden service descriptors.
11595 o Minor features (build and packaging):
11596 - On Linux, use the prctl call to re-enable core dumps when the User
11598 - Try to make sure that the version of Libevent we're running with
11599 is binary-compatible with the one we built with. May address bug
11601 - Add a new --enable-local-appdata configuration switch to change
11602 the default location of the datadir on win32 from APPDATA to
11603 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
11604 entirely. Patch from coderman.
11605 - Build correctly against versions of OpenSSL 0.9.8 or later that
11606 are built without support for deprecated functions.
11607 - On platforms with a maximum syslog string length, truncate syslog
11608 messages to that length ourselves, rather than relying on the
11609 system to do it for us.
11610 - Automatically detect MacOSX versions earlier than 10.4.0, and
11611 disable kqueue from inside Tor when running with these versions.
11612 We previously did this from the startup script, but that was no
11613 help to people who didn't use the startup script. Resolves bug 863.
11614 - Build correctly when configured to build outside the main source
11615 path. Patch from Michael Gold.
11616 - Disable GCC's strict alias optimization by default, to avoid the
11617 likelihood of its introducing subtle bugs whenever our code violates
11618 the letter of C99's alias rules.
11619 - Change the contrib/tor.logrotate script so it makes the new
11620 logs as "_tor:_tor" rather than the default, which is generally
11621 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
11622 - Change our header file guard macros to be less likely to conflict
11623 with system headers. Adam Langley noticed that we were conflicting
11624 with log.h on Android.
11625 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
11626 and stop using a warning that had become unfixably verbose under
11628 - Use a lockfile to make sure that two Tor processes are not
11629 simultaneously running with the same datadir.
11630 - Allow OpenSSL to use dynamic locks if it wants.
11631 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
11633 o Minor features (controllers):
11634 - When generating circuit events with verbose nicknames for
11635 controllers, try harder to look up nicknames for routers on a
11636 circuit. (Previously, we would look in the router descriptors we had
11637 for nicknames, but not in the consensus.) Partial fix for bug 941.
11638 - New controller event NEWCONSENSUS that lists the networkstatus
11639 lines for every recommended relay. Now controllers like Torflow
11640 can keep up-to-date on which relays they should be using.
11641 - New controller event "clients_seen" to report a geoip-based summary
11642 of which countries we've seen clients from recently. Now controllers
11643 like Vidalia can show bridge operators that they're actually making
11645 - Add a 'getinfo status/clients-seen' controller command, in case
11646 controllers want to hear clients_seen events but connect late.
11647 - New CONSENSUS_ARRIVED event to note when a new consensus has
11648 been fetched and validated.
11649 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
11650 controllers to prevent SIGHUP from reloading the configuration.
11652 - Return circuit purposes in response to GETINFO circuit-status.
11654 - Serve the latest v3 networkstatus consensus via the control
11655 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
11656 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
11657 controller can query our current bootstrap state in case it attaches
11658 partway through and wants to catch up.
11659 - Provide circuit purposes along with circuit events to the controller.
11661 o Minor features (tools):
11662 - Do not have tor-resolve automatically refuse all .onion addresses;
11663 if AutomapHostsOnResolve is set in your torrc, this will work fine.
11664 - Add a -p option to tor-resolve for specifying the SOCKS port: some
11665 people find host:port too confusing.
11666 - Print the SOCKS5 error message string as well as the error code
11667 when a tor-resolve request fails. Patch from Jacob.
11669 o Minor bugfixes (memory and resource management):
11670 - Clients no longer cache certificates for authorities they do not
11671 recognize. Bugfix on 0.2.0.9-alpha.
11672 - Do not use C's stdio library for writing to log files. This will
11673 improve logging performance by a minute amount, and will stop
11674 leaking fds when our disk is full. Fixes bug 861.
11675 - Stop erroneous use of O_APPEND in cases where we did not in fact
11676 want to re-seek to the end of a file before every last write().
11677 - Fix a small alignment and memory-wasting bug on buffer chunks.
11679 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
11680 to avoid unused RAM in buffer chunks and memory pools.
11681 - Reduce the default smartlist size from 32 to 16; it turns out that
11682 most smartlists hold around 8-12 elements tops.
11683 - Make dumpstats() log the fullness and size of openssl-internal
11685 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
11686 patch to their OpenSSL, turn it on to save memory on servers. This
11687 patch will (with any luck) get included in a mainline distribution
11689 - Fix a memory leak when v3 directory authorities load their keys
11690 and cert from disk. Bugfix on 0.2.0.1-alpha.
11691 - Stop using malloc_usable_size() to use more area than we had
11692 actually allocated: it was safe, but made valgrind really unhappy.
11693 - Make the assert_circuit_ok() function work correctly on circuits that
11694 have already been marked for close.
11695 - Fix uninitialized size field for memory area allocation: may improve
11696 memory performance during directory parsing.
11698 o Minor bugfixes (clients):
11699 - Stop reloading the router list from disk for no reason when we
11700 run out of reachable directory mirrors. Once upon a time reloading
11701 it would set the 'is_running' flag back to 1 for them. It hasn't
11702 done that for a long time.
11703 - When we had picked an exit node for a connection, but marked it as
11704 "optional", and it turned out we had no onion key for the exit,
11705 stop wanting that exit and try again. This situation may not
11706 be possible now, but will probably become feasible with proposal
11707 158. Spotted by rovv. Fixes another case of bug 752.
11708 - Fix a bug in address parsing that was preventing bridges or hidden
11709 service targets from being at IPv6 addresses.
11710 - Do not remove routers as too old if we do not have any consensus
11711 document. Bugfix on 0.2.0.7-alpha.
11712 - When an exit relay resolves a stream address to a local IP address,
11713 do not just keep retrying that same exit relay over and
11714 over. Instead, just close the stream. Addresses bug 872. Bugfix
11715 on 0.2.0.32. Patch from rovv.
11716 - Made Tor a little less aggressive about deleting expired
11717 certificates. Partial fix for bug 854.
11718 - Treat duplicate certificate fetches as failures, so that we do
11719 not try to re-fetch an expired certificate over and over and over.
11720 - Do not say we're fetching a certificate when we'll in fact skip it
11721 because of a pending download.
11722 - If we have correct permissions on $datadir, we complain to stdout
11723 and fail to start. But dangerous permissions on
11724 $datadir/cached-status/ would cause us to open a log and complain
11725 there. Now complain to stdout and fail to start in both cases. Fixes
11726 bug 820, reported by seeess.
11728 o Minor bugfixes (bridges):
11729 - When we made bridge authorities stop serving bridge descriptors over
11730 unencrypted links, we also broke DirPort reachability testing for
11731 bridges. So bridges with a non-zero DirPort were printing spurious
11732 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
11733 - Don't allow a bridge to publish its router descriptor to a
11734 non-bridge directory authority. Fixes part of bug 932.
11735 - When we change to or from being a bridge, reset our counts of
11736 client usage by country. Fixes bug 932.
11738 o Minor bugfixes (relays):
11739 - Log correct error messages for DNS-related network errors on
11741 - Actually return -1 in the error case for read_bandwidth_usage().
11742 Harmless bug, since we currently don't care about the return value
11743 anywhere. Bugfix on 0.2.0.9-alpha.
11744 - Provide a more useful log message if bug 977 (related to buffer
11745 freelists) ever reappears, and do not crash right away.
11746 - We were already rejecting relay begin cells with destination port
11747 of 0. Now also reject extend cells with destination port or address
11748 of 0. Suggested by lark.
11749 - When we can't transmit a DNS request due to a network error, retry
11750 it after a while, and eventually transmit a failing response to
11751 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
11752 - Solve a bug that kept hardware crypto acceleration from getting
11753 enabled when accounting was turned on. Fixes bug 907. Bugfix on
11755 - When a canonical connection appears later in our internal list
11756 than a noncanonical one for a given OR ID, always use the
11757 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
11759 - Avoid some nasty corner cases in the logic for marking connections
11760 as too old or obsolete or noncanonical for circuits. Partial
11762 - Fix another interesting corner-case of bug 891 spotted by rovv:
11763 Previously, if two hosts had different amounts of clock drift, and
11764 one of them created a new connection with just the wrong timing,
11765 the other might decide to deprecate the new connection erroneously.
11766 Bugfix on 0.1.1.13-alpha.
11767 - If one win32 nameserver fails to get added, continue adding the
11768 rest, and don't automatically fail.
11769 - Fix a bug where an unreachable relay would establish enough
11770 reachability testing circuits to do a bandwidth test -- if
11771 we already have a connection to the middle hop of the testing
11772 circuit, then it could establish the last hop by using the existing
11773 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
11774 circuits no longer use entry guards in 0.2.1.3-alpha.
11776 o Minor bugfixes (directory authorities):
11777 - Limit uploaded directory documents to be 16M rather than 500K.
11778 The directory authorities were refusing v3 consensus votes from
11779 other authorities, since the votes are now 504K. Fixes bug 959;
11780 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
11781 - Directory authorities should never send a 503 "busy" response to
11782 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
11784 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
11785 headers. Bugfix on 0.2.0.10-alpha.
11787 o Minor bugfixes (hidden services):
11788 - When we can't find an intro key for a v2 hidden service descriptor,
11789 fall back to the v0 hidden service descriptor and log a bug message.
11790 Workaround for bug 1024.
11791 - In very rare situations new hidden service descriptors were
11792 published earlier than 30 seconds after the last change to the
11793 service. (We currently think that a hidden service descriptor
11794 that's been stable for 30 seconds is worth publishing.)
11795 - If a hidden service sends us an END cell, do not consider
11796 retrying the connection; just close it. Patch from rovv.
11797 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
11798 service directories if they have no advertised dir port. Bugfix
11801 o Minor bugfixes (tools):
11802 - In the torify(1) manpage, mention that tsocks will leak your
11805 o Minor bugfixes (controllers):
11806 - If the controller claimed responsibility for a stream, but that
11807 stream never finished making its connection, it would live
11808 forever in circuit_wait state. Now we close it after SocksTimeout
11809 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
11810 - Make DNS resolved controller events into "CLOSED", not
11811 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
11813 - The control port would close the connection before flushing long
11814 replies, such as the network consensus, if a QUIT command was issued
11815 before the reply had completed. Now, the control port flushes all
11816 pending replies before closing the connection. Also fix a spurious
11817 warning when a QUIT command is issued after a malformed or rejected
11818 AUTHENTICATE command, but before the connection was closed. Patch
11819 by Marcus Griep. Fixes bugs 1015 and 1016.
11820 - Fix a bug that made stream bandwidth get misreported to the
11823 o Deprecated and removed features:
11824 - The old "tor --version --version" command, which would print out
11825 the subversion "Id" of most of the source files, is now removed. It
11826 turned out to be less useful than we'd expected, and harder to
11828 - RedirectExits has been removed. It was deprecated since
11830 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
11831 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
11832 - Cell pools are now always enabled; --disable-cell-pools is ignored.
11833 - Directory mirrors no longer fetch the v1 directory or
11834 running-routers files. They are obsolete, and nobody asks for them
11835 anymore. This is the first step to making v1 authorities obsolete.
11836 - Take out the TestVia config option, since it was a workaround for
11837 a bug that was fixed in Tor 0.1.1.21.
11838 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
11839 HiddenServiceExcludeNodes as obsolete: they never worked properly,
11840 and nobody seems to be using them. Fixes bug 754. Bugfix on
11841 0.1.0.1-rc. Patch from Christian Wilms.
11842 - Remove all backward-compatibility code for relays running
11843 versions of Tor so old that they no longer work at all on the
11846 o Code simplifications and refactoring:
11847 - Tool-assisted documentation cleanup. Nearly every function or
11848 static variable in Tor should have its own documentation now.
11849 - Rename the confusing or_is_obsolete field to the more appropriate
11850 is_bad_for_new_circs, and move it to or_connection_t where it
11852 - Move edge-only flags from connection_t to edge_connection_t: not
11853 only is this better coding, but on machines of plausible alignment,
11854 it should save 4-8 bytes per connection_t. "Every little bit helps."
11855 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
11856 for consistency; keep old option working for backward compatibility.
11857 - Simplify the code for finding connections to use for a circuit.
11858 - Revise the connection_new functions so that a more typesafe variant
11859 exists. This will work better with Coverity, and let us find any
11860 actual mistakes we're making here.
11861 - Refactor unit testing logic so that dmalloc can be used sensibly
11862 with unit tests to check for memory leaks.
11863 - Move all hidden-service related fields from connection and circuit
11864 structure to substructures: this way they won't eat so much memory.
11865 - Squeeze 2-5% out of client performance (according to oprofile) by
11866 improving the implementation of some policy-manipulation functions.
11867 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
11868 be more efficient. Formerly it was quadratic in the number of
11869 servers; now it should be linear. Fixes bug 509.
11870 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
11871 and n_conn_id_digest fields into a separate structure that's
11872 only needed when the circuit has not yet attached to an n_conn.
11873 - Optimize out calls to time(NULL) that occur for every IO operation,
11874 or for every cell. On systems like Windows where time() is a
11875 slow syscall, this fix will be slightly helpful.
11878 Changes in version 0.2.0.35 - 2009-06-24
11880 - Avoid crashing in the presence of certain malformed descriptors.
11881 Found by lark, and by automated fuzzing.
11882 - Fix an edge case where a malicious exit relay could convince a
11883 controller that the client's DNS question resolves to an internal IP
11884 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
11887 - Finally fix the bug where dynamic-IP relays disappear when their
11888 IP address changes: directory mirrors were mistakenly telling
11889 them their old address if they asked via begin_dir, so they
11890 never got an accurate answer about their new address, so they
11891 just vanished after a day. For belt-and-suspenders, relays that
11892 don't set Address in their config now avoid using begin_dir for
11893 all direct connections. Should fix bugs 827, 883, and 900.
11894 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
11895 that would occur on some exit nodes when DNS failures and timeouts
11896 occurred in certain patterns. Fix for bug 957.
11899 - When starting with a cache over a few days old, do not leak
11900 memory for the obsolete router descriptors in it. Bugfix on
11901 0.2.0.33; fixes bug 672.
11902 - Hidden service clients didn't use a cached service descriptor that
11903 was older than 15 minutes, but wouldn't fetch a new one either,
11904 because there was already one in the cache. Now, fetch a v2
11905 descriptor unless the same descriptor was added to the cache within
11906 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
11909 Changes in version 0.2.0.34 - 2009-02-08
11910 Tor 0.2.0.34 features several more security-related fixes. You should
11911 upgrade, especially if you run an exit relay (remote crash) or a
11912 directory authority (remote infinite loop), or you're on an older
11913 (pre-XP) or not-recently-patched Windows (remote exploit).
11915 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
11916 have many known flaws, and nobody should be using them. You should
11917 upgrade. If you're using a Linux or BSD and its packages are obsolete,
11918 stop using those packages and upgrade anyway.
11921 - Fix an infinite-loop bug on handling corrupt votes under certain
11922 circumstances. Bugfix on 0.2.0.8-alpha.
11923 - Fix a temporary DoS vulnerability that could be performed by
11924 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
11925 - Avoid a potential crash on exit nodes when processing malformed
11926 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
11927 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
11928 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
11931 - Fix compilation on systems where time_t is a 64-bit integer.
11932 Patch from Matthias Drochner.
11933 - Don't consider expiring already-closed client connections. Fixes
11934 bug 893. Bugfix on 0.0.2pre20.
11937 Changes in version 0.2.0.33 - 2009-01-21
11938 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
11939 useful to users. It also finally fixes a bug where a relay or client
11940 that's been off for many days would take a long time to bootstrap.
11942 This update also fixes an important security-related bug reported by
11943 Ilja van Sprundel. You should upgrade. (We'll send out more details
11944 about the bug once people have had some time to upgrade.)
11947 - Fix a heap-corruption bug that may be remotely triggerable on
11948 some platforms. Reported by Ilja van Sprundel.
11951 - When a stream at an exit relay is in state "resolving" or
11952 "connecting" and it receives an "end" relay cell, the exit relay
11953 would silently ignore the end cell and not close the stream. If
11954 the client never closes the circuit, then the exit relay never
11955 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
11956 reported by "wood".
11957 - When sending CREATED cells back for a given circuit, use a 64-bit
11958 connection ID to find the right connection, rather than an addr:port
11959 combination. Now that we can have multiple OR connections between
11960 the same ORs, it is no longer possible to use addr:port to uniquely
11961 identify a connection.
11962 - Bridge relays that had DirPort set to 0 would stop fetching
11963 descriptors shortly after startup, and then briefly resume
11964 after a new bandwidth test and/or after publishing a new bridge
11965 descriptor. Bridge users that try to bootstrap from them would
11966 get a recent networkstatus but would get descriptors from up to
11967 18 hours earlier, meaning most of the descriptors were obsolete
11968 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
11969 - Prevent bridge relays from serving their 'extrainfo' document
11970 to anybody who asks, now that extrainfo docs include potentially
11971 sensitive aggregated client geoip summaries. Bugfix on
11973 - If the cached networkstatus consensus is more than five days old,
11974 discard it rather than trying to use it. In theory it could be
11975 useful because it lists alternate directory mirrors, but in practice
11976 it just means we spend many minutes trying directory mirrors that
11977 are long gone from the network. Also discard router descriptors as
11978 we load them if they are more than five days old, since the onion
11979 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
11982 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
11983 could make gcc generate non-functional binary search code. Bugfix
11985 - Build correctly on platforms without socklen_t.
11986 - Compile without warnings on solaris.
11987 - Avoid potential crash on internal error during signature collection.
11988 Fixes bug 864. Patch from rovv.
11989 - Correct handling of possible malformed authority signing key
11990 certificates with internal signature types. Fixes bug 880.
11991 Bugfix on 0.2.0.3-alpha.
11992 - Fix a hard-to-trigger resource leak when logging credential status.
11994 - When we can't initialize DNS because the network is down, do not
11995 automatically stop Tor from starting. Instead, we retry failed
11996 dns_init() every 10 minutes, and change the exit policy to reject
11997 *:* until one succeeds. Fixes bug 691.
11998 - Use 64 bits instead of 32 bits for connection identifiers used with
11999 the controller protocol, to greatly reduce risk of identifier reuse.
12000 - When we're choosing an exit node for a circuit, and we have
12001 no pending streams, choose a good general exit rather than one that
12002 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
12003 - Fix another case of assuming, when a specific exit is requested,
12004 that we know more than the user about what hosts it allows.
12005 Fixes one case of bug 752. Patch from rovv.
12006 - Clip the MaxCircuitDirtiness config option to a minimum of 10
12007 seconds. Warn the user if lower values are given in the
12008 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
12009 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
12010 user if lower values are given in the configuration. Bugfix on
12011 0.1.1.17-rc. Patch by Sebastian.
12012 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
12013 the cache because we already had a v0 descriptor with the same ID.
12014 Bugfix on 0.2.0.18-alpha.
12015 - Fix a race condition when freeing keys shared between main thread
12016 and CPU workers that could result in a memory leak. Bugfix on
12017 0.1.0.1-rc. Fixes bug 889.
12018 - Send a valid END cell back when a client tries to connect to a
12019 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
12020 840. Patch from rovv.
12021 - Check which hops rendezvous stream cells are associated with to
12022 prevent possible guess-the-streamid injection attacks from
12023 intermediate hops. Fixes another case of bug 446. Based on patch
12025 - If a broken client asks a non-exit router to connect somewhere,
12026 do not even do the DNS lookup before rejecting the connection.
12027 Fixes another case of bug 619. Patch from rovv.
12028 - When a relay gets a create cell it can't decrypt (e.g. because it's
12029 using the wrong onion key), we were dropping it and letting the
12030 client time out. Now actually answer with a destroy cell. Fixes
12031 bug 904. Bugfix on 0.0.2pre8.
12033 o Minor bugfixes (hidden services):
12034 - Do not throw away existing introduction points on SIGHUP. Bugfix on
12035 0.0.6pre1. Patch by Karsten. Fixes bug 874.
12038 - Report the case where all signatures in a detached set are rejected
12039 differently than the case where there is an error handling the
12041 - When we realize that another process has modified our cached
12042 descriptors, print out a more useful error message rather than
12043 triggering an assertion. Fixes bug 885. Patch from Karsten.
12044 - Implement the 0x20 hack to better resist DNS poisoning: set the
12045 case on outgoing DNS requests randomly, and reject responses that do
12046 not match the case correctly. This logic can be disabled with the
12047 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
12048 of servers that do not reliably preserve case in replies. See
12049 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
12051 - Check DNS replies for more matching fields to better resist DNS
12053 - Never use OpenSSL compression: it wastes RAM and CPU trying to
12054 compress cells, which are basically all encrypted, compressed, or
12058 Changes in version 0.2.0.32 - 2008-11-20
12059 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
12060 packages (and maybe other packages) noticed by Theo de Raadt, fixes
12061 a smaller security flaw that might allow an attacker to access local
12062 services, further improves hidden service performance, and fixes a
12063 variety of other issues.
12066 - The "User" and "Group" config options did not clear the
12067 supplementary group entries for the Tor process. The "User" option
12068 is now more robust, and we now set the groups to the specified
12069 user's primary group. The "Group" option is now ignored. For more
12070 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
12071 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
12072 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
12073 - The "ClientDNSRejectInternalAddresses" config option wasn't being
12074 consistently obeyed: if an exit relay refuses a stream because its
12075 exit policy doesn't allow it, we would remember what IP address
12076 the relay said the destination address resolves to, even if it's
12077 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
12080 - Fix a DOS opportunity during the voting signature collection process
12081 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
12083 o Major bugfixes (hidden services):
12084 - When fetching v0 and v2 rendezvous service descriptors in parallel,
12085 we were failing the whole hidden service request when the v0
12086 descriptor fetch fails, even if the v2 fetch is still pending and
12087 might succeed. Similarly, if the last v2 fetch fails, we were
12088 failing the whole hidden service request even if a v0 fetch is
12089 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
12090 - When extending a circuit to a hidden service directory to upload a
12091 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
12092 requests failed, because the router descriptor has not been
12093 downloaded yet. In these cases, do not attempt to upload the
12094 rendezvous descriptor, but wait until the router descriptor is
12095 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
12096 descriptor from a hidden service directory for which the router
12097 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
12101 - Fix several infrequent memory leaks spotted by Coverity.
12102 - When testing for libevent functions, set the LDFLAGS variable
12103 correctly. Found by Riastradh.
12104 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
12105 bootstrapping with tunneled directory connections. Bugfix on
12106 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
12107 - When asked to connect to A.B.exit:80, if we don't know the IP for A
12108 and we know that server B rejects most-but-not all connections to
12109 port 80, we would previously reject the connection. Now, we assume
12110 the user knows what they were asking for. Fixes bug 752. Bugfix
12111 on 0.0.9rc5. Diagnosed by BarkerJr.
12112 - If we overrun our per-second write limits a little, count this as
12113 having used up our write allocation for the second, and choke
12114 outgoing directory writes. Previously, we had only counted this when
12115 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
12116 Bugfix on 0.2.0.x (??).
12117 - Remove the old v2 directory authority 'lefkada' from the default
12118 list. It has been gone for many months.
12119 - Stop doing unaligned memory access that generated bus errors on
12120 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
12121 - Make USR2 log-level switch take effect immediately. Bugfix on
12124 o Minor bugfixes (controller):
12125 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
12126 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
12129 Changes in version 0.2.0.31 - 2008-09-03
12130 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
12131 a big bug we're seeing where in rare cases traffic from one Tor stream
12132 gets mixed into another stream, and fixes a variety of smaller issues.
12135 - Make sure that two circuits can never exist on the same connection
12136 with the same circuit ID, even if one is marked for close. This
12137 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
12138 - Relays now reject risky extend cells: if the extend cell includes
12139 a digest of all zeroes, or asks to extend back to the relay that
12140 sent the extend cell, tear down the circuit. Ideas suggested
12142 - If not enough of our entry guards are available so we add a new
12143 one, we might use the new one even if it overlapped with the
12144 current circuit's exit relay (or its family). Anonymity bugfix
12145 pointed out by rovv.
12148 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
12149 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
12150 - Correctly detect the presence of the linux/netfilter_ipv4.h header
12151 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
12152 - Pick size of default geoip filename string correctly on windows.
12153 Fixes bug 806. Bugfix on 0.2.0.30.
12154 - Make the autoconf script accept the obsolete --with-ssl-dir
12155 option as an alias for the actually-working --with-openssl-dir
12156 option. Fix the help documentation to recommend --with-openssl-dir.
12157 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
12158 - When using the TransPort option on OpenBSD, and using the User
12159 option to change UID and drop privileges, make sure to open
12160 /dev/pf before dropping privileges. Fixes bug 782. Patch from
12161 Christopher Davis. Bugfix on 0.1.2.1-alpha.
12162 - Try to attach connections immediately upon receiving a RENDEZVOUS2
12163 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
12164 on the client side when connecting to a hidden service. Bugfix
12165 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
12166 - When closing an application-side connection because its circuit is
12167 getting torn down, generate the stream event correctly. Bugfix on
12168 0.1.2.x. Anonymous patch.
12171 Changes in version 0.2.0.30 - 2008-07-15
12172 This new stable release switches to a more efficient directory
12173 distribution design, adds features to make connections to the Tor
12174 network harder to block, allows Tor to act as a DNS proxy, adds separate
12175 rate limiting for relayed traffic to make it easier for clients to
12176 become relays, fixes a variety of potential anonymity problems, and
12177 includes the usual huge pile of other features and bug fixes.
12179 o New v3 directory design:
12180 - Tor now uses a new way to learn about and distribute information
12181 about the network: the directory authorities vote on a common
12182 network status document rather than each publishing their own
12183 opinion. Now clients and caches download only one networkstatus
12184 document to bootstrap, rather than downloading one for each
12185 authority. Clients only download router descriptors listed in
12186 the consensus. Implements proposal 101; see doc/spec/dir-spec.txt
12188 - Set up moria1, tor26, and dizum as v3 directory authorities
12189 in addition to being v2 authorities. Also add three new ones:
12190 ides (run by Mike Perry), gabelmoo (run by Karsten Loesing), and
12191 dannenberg (run by CCC).
12192 - Switch to multi-level keys for directory authorities: now their
12193 long-term identity key can be kept offline, and they periodically
12194 generate a new signing key. Clients fetch the "key certificates"
12195 to keep up to date on the right keys. Add a standalone tool
12196 "tor-gencert" to generate key certificates. Implements proposal 103.
12197 - Add a new V3AuthUseLegacyKey config option to make it easier for
12198 v3 authorities to change their identity keys if another bug like
12199 Debian's OpenSSL RNG flaw appears.
12200 - Authorities and caches fetch the v2 networkstatus documents
12201 less often, now that v3 is recommended.
12203 o Make Tor connections stand out less on the wire:
12204 - Use an improved TLS handshake designed by Steven Murdoch in proposal
12205 124, as revised in proposal 130. The new handshake is meant to
12206 be harder for censors to fingerprint, and it adds the ability
12207 to detect certain kinds of man-in-the-middle traffic analysis
12208 attacks. The new handshake format includes version negotiation for
12209 OR connections as described in proposal 105, which will allow us
12210 to improve Tor's link protocol more safely in the future.
12211 - Enable encrypted directory connections by default for non-relays,
12212 so censor tools that block Tor directory connections based on their
12213 plaintext patterns will no longer work. This means Tor works in
12214 certain censored countries by default again.
12215 - Stop including recognizeable strings in the commonname part of
12216 Tor's x509 certificates.
12218 o Implement bridge relays:
12219 - Bridge relays (or "bridges" for short) are Tor relays that aren't
12220 listed in the main Tor directory. Since there is no complete public
12221 list of them, even an ISP that is filtering connections to all the
12222 known Tor relays probably won't be able to block all the bridges.
12223 See doc/design-paper/blocking.pdf and proposal 125 for details.
12224 - New config option BridgeRelay that specifies you want to be a
12225 bridge relay rather than a normal relay. When BridgeRelay is set
12226 to 1, then a) you cache dir info even if your DirPort ins't on,
12227 and b) the default for PublishServerDescriptor is now "bridge"
12228 rather than "v2,v3".
12229 - New config option "UseBridges 1" for clients that want to use bridge
12230 relays instead of ordinary entry guards. Clients then specify
12231 bridge relays by adding "Bridge" lines to their config file. Users
12232 can learn about a bridge relay either manually through word of
12233 mouth, or by one of our rate-limited mechanisms for giving out
12234 bridge addresses without letting an attacker easily enumerate them
12235 all. See https://www.torproject.org/bridges for details.
12236 - Bridge relays behave like clients with respect to time intervals
12237 for downloading new v3 consensus documents -- otherwise they
12238 stand out. Bridge users now wait until the end of the interval,
12239 so their bridge relay will be sure to have a new consensus document.
12241 o Implement bridge directory authorities:
12242 - Bridge authorities are like normal directory authorities, except
12243 they don't serve a list of known bridges. Therefore users that know
12244 a bridge's fingerprint can fetch a relay descriptor for that bridge,
12245 including fetching updates e.g. if the bridge changes IP address,
12246 yet an attacker can't just fetch a list of all the bridges.
12247 - Set up Tonga as the default bridge directory authority.
12248 - Bridge authorities refuse to serve bridge descriptors or other
12249 bridge information over unencrypted connections (that is, when
12250 responding to direct DirPort requests rather than begin_dir cells.)
12251 - Bridge directory authorities do reachability testing on the
12252 bridges they know. They provide router status summaries to the
12253 controller via "getinfo ns/purpose/bridge", and also dump summaries
12254 to a file periodically, so we can keep internal stats about which
12255 bridges are functioning.
12256 - If bridge users set the UpdateBridgesFromAuthority config option,
12257 but the digest they ask for is a 404 on the bridge authority,
12258 they fall back to contacting the bridge directly.
12259 - Bridges always use begin_dir to publish their server descriptor to
12260 the bridge authority using an anonymous encrypted tunnel.
12261 - Early work on a "bridge community" design: if bridge authorities set
12262 the BridgePassword config option, they will serve a snapshot of
12263 known bridge routerstatuses from their DirPort to anybody who
12264 knows that password. Unset by default.
12265 - Tor now includes an IP-to-country GeoIP file, so bridge relays can
12266 report sanitized aggregated summaries in their extra-info documents
12267 privately to the bridge authority, listing which countries are
12268 able to reach them. We hope this mechanism will let us learn when
12269 certain countries start trying to block bridges.
12270 - Bridge authorities write bridge descriptors to disk, so they can
12271 reload them after a reboot. They can also export the descriptors
12272 to other programs, so we can distribute them to blocked users via
12273 the BridgeDB interface, e.g. via https://bridges.torproject.org/
12274 and bridges@torproject.org.
12276 o Tor can be a DNS proxy:
12277 - The new client-side DNS proxy feature replaces the need for
12278 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
12279 for DNS requests on port 9999, use the Tor network to resolve them
12280 anonymously, and send the reply back like a regular DNS server.
12281 The code still only implements a subset of DNS.
12282 - Add a new AutomapHostsOnResolve option: when it is enabled, any
12283 resolve request for hosts matching a given pattern causes Tor to
12284 generate an internal virtual address mapping for that host. This
12285 allows DNSPort to work sensibly with hidden service users. By
12286 default, .exit and .onion addresses are remapped; the list of
12287 patterns can be reconfigured with AutomapHostsSuffixes.
12288 - Add an "-F" option to tor-resolve to force a resolve for a .onion
12289 address. Thanks to the AutomapHostsOnResolve option, this is no
12290 longer a completely silly thing to do.
12292 o Major features (relay usability):
12293 - New config options RelayBandwidthRate and RelayBandwidthBurst:
12294 a separate set of token buckets for relayed traffic. Right now
12295 relayed traffic is defined as answers to directory requests, and
12296 OR connections that don't have any local circuits on them. See
12297 proposal 111 for details.
12298 - Create listener connections before we setuid to the configured
12299 User and Group. Now non-Windows users can choose port values
12300 under 1024, start Tor as root, and have Tor bind those ports
12301 before it changes to another UID. (Windows users could already
12303 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
12304 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
12305 on "vserver" accounts. Patch from coderman.
12307 o Major features (directory authorities):
12308 - Directory authorities track weighted fractional uptime and weighted
12309 mean-time-between failures for relays. WFU is suitable for deciding
12310 whether a node is "usually up", while MTBF is suitable for deciding
12311 whether a node is "likely to stay up." We need both, because
12312 "usually up" is a good requirement for guards, while "likely to
12313 stay up" is a good requirement for long-lived connections.
12314 - Directory authorities use a new formula for selecting which relays
12315 to advertise as Guards: they must be in the top 7/8 in terms of
12316 how long we have known about them, and above the median of those
12317 nodes in terms of weighted fractional uptime.
12318 - Directory authorities use a new formula for selecting which relays
12319 to advertise as Stable: when we have 4 or more days of data, use
12320 median measured MTBF rather than median declared uptime. Implements
12322 - Directory authorities accept and serve "extra info" documents for
12323 routers. Routers now publish their bandwidth-history lines in the
12324 extra-info docs rather than the main descriptor. This step saves
12325 60% (!) on compressed router descriptor downloads. Servers upload
12326 extra-info docs to any authority that accepts them; directory
12327 authorities now allow multiple router descriptors and/or extra
12328 info documents to be uploaded in a single go. Authorities, and
12329 caches that have been configured to download extra-info documents,
12330 download them as needed. Implements proposal 104.
12331 - Authorities now list relays who have the same nickname as
12332 a different named relay, but list them with a new flag:
12333 "Unnamed". Now we can make use of relays that happen to pick the
12334 same nickname as a server that registered two years ago and then
12335 disappeared. Implements proposal 122.
12336 - Store routers in a file called cached-descriptors instead of in
12337 cached-routers. Initialize cached-descriptors from cached-routers
12338 if the old format is around. The new format allows us to store
12339 annotations along with descriptors, to record the time we received
12340 each descriptor, its source, and its purpose: currently one of
12341 general, controller, or bridge.
12343 o Major features (other):
12344 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
12345 Tor can warn and/or refuse connections to ports commonly used with
12346 vulnerable-plaintext protocols. Currently we warn on ports 23,
12347 109, 110, and 143, but we don't reject any. Based on proposal 129
12348 by Kevin Bauer and Damon McCoy.
12349 - Integrate Karsten Loesing's Google Summer of Code project to publish
12350 hidden service descriptors on a set of redundant relays that are a
12351 function of the hidden service address. Now we don't have to rely
12352 on three central hidden service authorities for publishing and
12353 fetching every hidden service descriptor. Implements proposal 114.
12354 - Allow tunnelled directory connections to ask for an encrypted
12355 "begin_dir" connection or an anonymized "uses a full Tor circuit"
12356 connection independently. Now we can make anonymized begin_dir
12357 connections for (e.g.) more secure hidden service posting and
12360 o Major bugfixes (crashes and assert failures):
12361 - Stop imposing an arbitrary maximum on the number of file descriptors
12362 used for busy servers. Bug reported by Olaf Selke; patch from
12364 - Avoid possible failures when generating a directory with routers
12365 with over-long versions strings, or too many flags set.
12366 - Fix a rare assert error when we're closing one of our threads:
12367 use a mutex to protect the list of logs, so we never write to the
12368 list as it's being freed. Fixes the very rare bug 575, which is
12369 kind of the revenge of bug 222.
12370 - Avoid segfault in the case where a badly behaved v2 versioning
12371 directory sends a signed networkstatus with missing client-versions.
12372 - When we hit an EOF on a log (probably because we're shutting down),
12373 don't try to remove the log from the list: just mark it as
12374 unusable. (Bulletproofs against bug 222.)
12376 o Major bugfixes (code security fixes):
12377 - Detect size overflow in zlib code. Reported by Justin Ferguson and
12379 - Rewrite directory tokenization code to never run off the end of
12380 a string. Fixes bug 455. Patch from croup.
12381 - Be more paranoid about overwriting sensitive memory on free(),
12382 as a defensive programming tactic to ensure forward secrecy.
12384 o Major bugfixes (anonymity fixes):
12385 - Reject requests for reverse-dns lookup of names that are in
12386 a private address space. Patch from lodger.
12387 - Never report that we've used more bandwidth than we're willing to
12388 relay: it leaks how much non-relay traffic we're using. Resolves
12390 - As a client, do not believe any server that tells us that an
12391 address maps to an internal address space.
12392 - Warn about unsafe ControlPort configurations.
12393 - Directory authorities now call routers Fast if their bandwidth is
12394 at least 100KB/s, and consider their bandwidth adequate to be a
12395 Guard if it is at least 250KB/s, no matter the medians. This fix
12396 complements proposal 107.
12397 - Directory authorities now never mark more than 2 servers per IP as
12398 Valid and Running (or 5 on addresses shared by authorities).
12399 Implements proposal 109, by Kevin Bauer and Damon McCoy.
12400 - If we're a relay, avoid picking ourselves as an introduction point,
12401 a rendezvous point, or as the final hop for internal circuits. Bug
12402 reported by taranis and lodger.
12403 - Exit relays that are used as a client can now reach themselves
12404 using the .exit notation, rather than just launching an infinite
12405 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
12406 - Fix a bug where, when we were choosing the 'end stream reason' to
12407 put in our relay end cell that we send to the exit relay, Tor
12408 clients on Windows were sometimes sending the wrong 'reason'. The
12409 anonymity problem is that exit relays may be able to guess whether
12410 the client is running Windows, thus helping partition the anonymity
12411 set. Down the road we should stop sending reasons to exit relays,
12412 or otherwise prevent future versions of this bug.
12413 - Only update guard status (usable / not usable) once we have
12414 enough directory information. This was causing us to discard all our
12415 guards on startup if we hadn't been running for a few weeks. Fixes
12417 - When our directory information has been expired for a while, stop
12418 being willing to build circuits using it. Fixes bug 401.
12420 o Major bugfixes (peace of mind for relay operators)
12421 - Non-exit relays no longer answer "resolve" relay cells, so they
12422 can't be induced to do arbitrary DNS requests. (Tor clients already
12423 avoid using non-exit relays for resolve cells, but now servers
12424 enforce this too.) Fixes bug 619. Patch from lodger.
12425 - When we setconf ClientOnly to 1, close any current OR and Dir
12426 listeners. Reported by mwenge.
12428 o Major bugfixes (other):
12429 - If we only ever used Tor for hidden service lookups or posts, we
12430 would stop building circuits and start refusing connections after
12431 24 hours, since we falsely believed that Tor was dormant. Reported
12433 - Add a new __HashedControlSessionPassword option for controllers
12434 to use for one-off session password hashes that shouldn't get
12435 saved to disk by SAVECONF --- Vidalia users were accumulating a
12436 pile of HashedControlPassword lines in their torrc files, one for
12437 each time they had restarted Tor and then clicked Save. Make Tor
12438 automatically convert "HashedControlPassword" to this new option but
12439 only when it's given on the command line. Partial fix for bug 586.
12440 - Patch from "Andrew S. Lists" to catch when we contact a directory
12441 mirror at IP address X and he says we look like we're coming from
12442 IP address X. Otherwise this would screw up our address detection.
12443 - Reject uploaded descriptors and extrainfo documents if they're
12444 huge. Otherwise we'll cache them all over the network and it'll
12445 clog everything up. Suggested by Aljosha Judmayer.
12446 - When a hidden service was trying to establish an introduction point,
12447 and Tor *did* manage to reuse one of the preemptively built
12448 circuits, it didn't correctly remember which one it used,
12449 so it asked for another one soon after, until there were no
12450 more preemptive circuits, at which point it launched one from
12451 scratch. Bugfix on 0.0.9.x.
12453 o Rate limiting and load balancing improvements:
12454 - When we add data to a write buffer in response to the data on that
12455 write buffer getting low because of a flush, do not consider the
12456 newly added data as a candidate for immediate flushing, but rather
12457 make it wait until the next round of writing. Otherwise, we flush
12458 and refill recursively, and a single greedy TLS connection can
12459 eat all of our bandwidth.
12460 - When counting the number of bytes written on a TLS connection,
12461 look at the BIO actually used for writing to the network, not
12462 at the BIO used (sometimes) to buffer data for the network.
12463 Looking at different BIOs could result in write counts on the
12464 order of ULONG_MAX. Fixes bug 614.
12465 - If we change our MaxAdvertisedBandwidth and then reload torrc,
12466 Tor won't realize it should publish a new relay descriptor. Fixes
12467 bug 688, reported by mfr.
12468 - Avoid using too little bandwidth when our clock skips a few seconds.
12469 - Choose which bridge to use proportional to its advertised bandwidth,
12470 rather than uniformly at random. This should speed up Tor for
12471 bridge users. Also do this for people who set StrictEntryNodes.
12473 o Bootstrapping faster and building circuits more intelligently:
12474 - Fix bug 660 that was preventing us from knowing that we should
12475 preemptively build circuits to handle expected directory requests.
12476 - When we're checking if we have enough dir info for each relay
12477 to begin establishing circuits, make sure that we actually have
12478 the descriptor listed in the consensus, not just any descriptor.
12479 - Correctly notify one-hop connections when a circuit build has
12480 failed. Possible fix for bug 669. Found by lodger.
12481 - Clients now hold circuitless TLS connections open for 1.5 times
12482 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
12483 rebuild a new circuit over them within that timeframe. Previously,
12484 they held them open only for KeepalivePeriod (5 minutes).
12486 o Performance improvements (memory):
12487 - Add OpenBSD malloc code from "phk" as an optional malloc
12488 replacement on Linux: some glibc libraries do very poorly with
12489 Tor's memory allocation patterns. Pass --enable-openbsd-malloc to
12490 ./configure to get the replacement malloc code.
12491 - Switch our old ring buffer implementation for one more like that
12492 used by free Unix kernels. The wasted space in a buffer with 1mb
12493 of data will now be more like 8k than 1mb. The new implementation
12494 also avoids realloc();realloc(); patterns that can contribute to
12495 memory fragmentation.
12496 - Change the way that Tor buffers data that it is waiting to write.
12497 Instead of queueing data cells in an enormous ring buffer for each
12498 client->OR or OR->OR connection, we now queue cells on a separate
12499 queue for each circuit. This lets us use less slack memory, and
12500 will eventually let us be smarter about prioritizing different kinds
12502 - Reference-count and share copies of address policy entries; only 5%
12503 of them were actually distinct.
12504 - Tune parameters for cell pool allocation to minimize amount of
12506 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
12507 for every single inactive connection_t. Free items from the
12508 4k/16k-buffer free lists when they haven't been used for a while.
12509 - Make memory debugging information describe more about history
12510 of cell allocation, so we can help reduce our memory use.
12511 - Be even more aggressive about releasing RAM from small
12512 empty buffers. Thanks to our free-list code, this shouldn't be too
12513 performance-intensive.
12514 - Log malloc statistics from mallinfo() on platforms where it exists.
12515 - Use memory pools to allocate cells with better speed and memory
12516 efficiency, especially on platforms where malloc() is inefficient.
12517 - Add a --with-tcmalloc option to the configure script to link
12518 against tcmalloc (if present). Does not yet search for non-system
12521 o Performance improvements (socket management):
12522 - Count the number of open sockets separately from the number of
12523 active connection_t objects. This will let us avoid underusing
12524 our allocated connection limit.
12525 - We no longer use socket pairs to link an edge connection to an
12526 anonymous directory connection or a DirPort test connection.
12527 Instead, we track the link internally and transfer the data
12528 in-process. This saves two sockets per "linked" connection (at the
12529 client and at the server), and avoids the nasty Windows socketpair()
12531 - We were leaking a file descriptor if Tor started with a zero-length
12532 cached-descriptors file. Patch by "freddy77".
12534 o Performance improvements (CPU use):
12535 - Never walk through the list of logs if we know that no log target
12536 is interested in a given message.
12537 - Call routerlist_remove_old_routers() much less often. This should
12538 speed startup, especially on directory caches.
12539 - Base64 decoding was actually showing up on our profile when parsing
12540 the initial descriptor file; switch to an in-process all-at-once
12541 implementation that's about 3.5x times faster than calling out to
12543 - Use a slightly simpler string hashing algorithm (copying Python's
12544 instead of Java's) and optimize our digest hashing algorithm to take
12545 advantage of 64-bit platforms and to remove some possibly-costly
12547 - When implementing AES counter mode, update only the portions of the
12548 counter buffer that need to change, and don't keep separate
12549 network-order and host-order counters on big-endian hosts (where
12550 they are the same).
12551 - Add an in-place version of aes_crypt() so that we can avoid doing a
12552 needless memcpy() call on each cell payload.
12553 - Use Critical Sections rather than Mutexes for synchronizing threads
12554 on win32; Mutexes are heavier-weight, and designed for synchronizing
12557 o Performance improvements (bandwidth use):
12558 - Don't try to launch new descriptor downloads quite so often when we
12559 already have enough directory information to build circuits.
12560 - Version 1 directories are no longer generated in full. Instead,
12561 authorities generate and serve "stub" v1 directories that list
12562 no servers. This will stop Tor versions 0.1.0.x and earlier from
12563 working, but (for security reasons) nobody should be running those
12565 - Avoid going directly to the directory authorities even if you're a
12566 relay, if you haven't found yourself reachable yet or if you've
12567 decided not to advertise your dirport yet. Addresses bug 556.
12568 - If we've gone 12 hours since our last bandwidth check, and we
12569 estimate we have less than 50KB bandwidth capacity but we could
12570 handle more, do another bandwidth test.
12571 - Support "If-Modified-Since" when answering HTTP requests for
12572 directories, running-routers documents, and v2 and v3 networkstatus
12573 documents. (There's no need to support it for router descriptors,
12574 since those are downloaded by descriptor digest.)
12575 - Stop fetching directory info so aggressively if your DirPort is
12576 on but your ORPort is off; stop fetching v2 dir info entirely.
12577 You can override these choices with the new FetchDirInfoEarly
12580 o Changed config option behavior (features):
12581 - Configuration files now accept C-style strings as values. This
12582 helps encode characters not allowed in the current configuration
12583 file format, such as newline or #. Addresses bug 557.
12584 - Add hidden services and DNSPorts to the list of things that make
12585 Tor accept that it has running ports. Change starting Tor with no
12586 ports from a fatal error to a warning; we might change it back if
12587 this turns out to confuse anybody. Fixes bug 579.
12588 - Make PublishServerDescriptor default to 1, so the default doesn't
12589 have to change as we invent new directory protocol versions.
12590 - Allow people to say PreferTunnelledDirConns rather than
12591 PreferTunneledDirConns, for those alternate-spellers out there.
12592 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
12593 accommodate the growing number of servers that use the default
12594 and are reaching it.
12595 - Make it possible to enable HashedControlPassword and
12596 CookieAuthentication at the same time.
12597 - When a TrackHostExits-chosen exit fails too many times in a row,
12598 stop using it. Fixes bug 437.
12600 o Changed config option behavior (bugfixes):
12601 - Do not read the configuration file when we've only been told to
12602 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
12603 based on patch from Sebastian Hahn.
12604 - Actually validate the options passed to AuthDirReject,
12605 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
12606 - Make "ClientOnly 1" config option disable directory ports too.
12607 - Don't stop fetching descriptors when FetchUselessDescriptors is
12608 set, even if we stop asking for circuits. Bug reported by tup
12610 - Servers used to decline to publish their DirPort if their
12611 BandwidthRate or MaxAdvertisedBandwidth were below a threshold. Now
12612 they look only at BandwidthRate and RelayBandwidthRate.
12613 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
12614 minus 1 byte: the actual maximum declared bandwidth.
12615 - Make "TrackHostExits ." actually work. Bugfix on 0.1.0.x.
12616 - Make the NodeFamilies config option work. (Reported by
12617 lodger -- it has never actually worked, even though we added it
12619 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
12620 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
12622 o New config options:
12623 - New configuration options AuthDirMaxServersPerAddr and
12624 AuthDirMaxServersperAuthAddr to override default maximum number
12625 of servers allowed on a single IP address. This is important for
12626 running a test network on a single host.
12627 - Three new config options (AlternateDirAuthority,
12628 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
12629 user selectively replace the default directory authorities by type,
12630 rather than the all-or-nothing replacement that DirServer offers.
12631 - New config options AuthDirBadDir and AuthDirListBadDirs for
12632 authorities to mark certain relays as "bad directories" in the
12633 networkstatus documents. Also supports the "!baddir" directive in
12634 the approved-routers file.
12635 - New config option V2AuthoritativeDirectory that all v2 directory
12636 authorities must set. This lets v3 authorities choose not to serve
12637 v2 directory information.
12639 o Minor features (other):
12640 - When we're not serving v2 directory information, there is no reason
12641 to actually keep any around. Remove the obsolete files and directory
12642 on startup if they are very old and we aren't going to serve them.
12643 - When we negotiate a v2 link-layer connection (not yet implemented),
12644 accept RELAY_EARLY cells and turn them into RELAY cells if we've
12645 negotiated a v1 connection for their next step. Initial steps for
12647 - When we have no consensus, check FallbackNetworkstatusFile (defaults
12648 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
12649 we can start out knowing some directory caches. We don't ship with
12650 a fallback consensus by default though, because it was making
12651 bootstrapping take too long while we tried many down relays.
12652 - Authorities send back an X-Descriptor-Not-New header in response to
12653 an accepted-but-discarded descriptor upload. Partially implements
12655 - If we find a cached-routers file that's been sitting around for more
12656 than 28 days unmodified, then most likely it's a leftover from
12657 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
12659 - When we (as a cache) download a descriptor because it was listed
12660 in a consensus, remember when the consensus was supposed to expire,
12661 and don't expire the descriptor until then.
12662 - Optionally (if built with -DEXPORTMALLINFO) export the output
12663 of mallinfo via http, as tor/mallinfo.txt. Only accessible
12665 - Tag every guard node in our state file with the version that
12666 we believe added it, or with our own version if we add it. This way,
12667 if a user temporarily runs an old version of Tor and then switches
12668 back to a new one, she doesn't automatically lose her guards.
12669 - When somebody requests a list of statuses or servers, and we have
12670 none of those, return a 404 rather than an empty 200.
12671 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
12673 - Add an HSAuthorityRecordStats option that hidden service authorities
12674 can use to track statistics of overall hidden service usage without
12675 logging information that would be as useful to an attacker.
12676 - Allow multiple HiddenServicePort directives with the same virtual
12677 port; when they occur, the user is sent round-robin to one
12678 of the target ports chosen at random. Partially fixes bug 393 by
12679 adding limited ad-hoc round-robining.
12680 - Revamp file-writing logic so we don't need to have the entire
12681 contents of a file in memory at once before we write to disk. Tor,
12684 o Minor bugfixes (other):
12685 - Alter the code that tries to recover from unhandled write
12686 errors, to not try to flush onto a socket that's given us
12688 - Directory mirrors no longer include a guess at the client's IP
12689 address if the connection appears to be coming from the same /24
12690 network; it was producing too many wrong guesses.
12691 - If we're trying to flush the last bytes on a connection (for
12692 example, when answering a directory request), reset the
12693 time-to-give-up timeout every time we manage to write something
12695 - Reject router descriptors with out-of-range bandwidthcapacity or
12696 bandwidthburst values.
12697 - If we can't expand our list of entry guards (e.g. because we're
12698 using bridges or we have StrictEntryNodes set), don't mark relays
12699 down when they fail a directory request. Otherwise we're too quick
12700 to mark all our entry points down.
12701 - Authorities no longer send back "400 you're unreachable please fix
12702 it" errors to Tor servers that aren't online all the time. We're
12703 supposed to tolerate these servers now.
12704 - Let directory authorities startup even when they can't generate
12705 a descriptor immediately, e.g. because they don't know their
12707 - Correctly enforce that elements of directory objects do not appear
12708 more often than they are allowed to appear.
12709 - Stop allowing hibernating servers to be "stable" or "fast".
12710 - On Windows, we were preventing other processes from reading
12711 cached-routers while Tor was running. (Reported by janbar)
12712 - Check return values from pthread_mutex functions.
12713 - When opening /dev/null in finish_daemonize(), do not pass the
12714 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
12715 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
12717 o Controller features:
12718 - The GETCONF command now escapes and quotes configuration values
12719 that don't otherwise fit into the torrc file.
12720 - The SETCONF command now handles quoted values correctly.
12721 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
12722 ask about source, timestamp of arrival, purpose, etc. We need
12723 something like this to help Vidalia not do GeoIP lookups on bridge
12725 - Allow multiple HashedControlPassword config lines, to support
12726 multiple controller passwords.
12727 - Accept LF instead of CRLF on controller, since some software has a
12728 hard time generating real Internet newlines.
12729 - Add GETINFO values for the server status events
12730 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
12732 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
12733 GETINFO for Torstat to use until it can switch to using extrainfos.
12734 - New config option CookieAuthFile to choose a new location for the
12735 cookie authentication file, and config option
12736 CookieAuthFileGroupReadable to make it group-readable.
12737 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
12738 match requests to applications. Patch from Robert Hogan.
12739 - Add a RESOLVE command to launch hostname lookups. Original patch
12741 - Add GETINFO status/enough-dir-info to let controllers tell whether
12742 Tor has downloaded sufficient directory information. Patch from Tup.
12743 - You can now use the ControlSocket option to tell Tor to listen for
12744 controller connections on Unix domain sockets on systems that
12745 support them. Patch from Peter Palfrader.
12746 - New "GETINFO address-mappings/*" command to get address mappings
12747 with expiry information. "addr-mappings/*" is now deprecated.
12749 - Add a new config option __DisablePredictedCircuits designed for
12750 use by the controller, when we don't want Tor to build any circuits
12752 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
12753 so we can exit from the middle of the circuit.
12754 - Implement "getinfo status/circuit-established".
12755 - Implement "getinfo status/version/..." so a controller can tell
12756 whether the current version is recommended, and whether any versions
12757 are good, and how many authorities agree. Patch from "shibz".
12758 - Controllers should now specify cache=no or cache=yes when using
12759 the +POSTDESCRIPTOR command.
12760 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
12761 Robert Hogan. Fixes the first part of bug 681.
12762 - When reporting clock skew, and we know that the clock is _at least
12763 as skewed_ as some value, but we don't know the actual value,
12764 report the value as a "minimum skew."
12766 o Controller bugfixes:
12767 - Generate "STATUS_SERVER" events rather than misspelled
12768 "STATUS_SEVER" events. Caught by mwenge.
12769 - Reject controller commands over 1MB in length, so rogue
12770 processes can't run us out of memory.
12771 - Change the behavior of "getinfo status/good-server-descriptor"
12772 so it doesn't return failure when any authority disappears.
12773 - Send NAMESERVER_STATUS messages for a single failed nameserver
12775 - When the DANGEROUS_VERSION controller status event told us we're
12776 running an obsolete version, it used the string "OLD" to describe
12777 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
12778 "OBSOLETE" in both cases.
12779 - Respond to INT and TERM SIGNAL commands before we execute the
12780 signal, in case the signal shuts us down. We had a patch in
12781 0.1.2.1-alpha that tried to do this by queueing the response on
12782 the connection's buffer before shutting down, but that really
12783 isn't the same thing at all. Bug located by Matt Edman.
12784 - Provide DNS expiry times in GMT, not in local time. For backward
12785 compatibility, ADDRMAP events only provide GMT expiry in an extended
12786 field. "GETINFO address-mappings" always does the right thing.
12787 - Use CRLF line endings properly in NS events.
12788 - Make 'getinfo fingerprint' return a 551 error if we're not a
12789 server, so we match what the control spec claims we do. Reported
12791 - Fix a typo in an error message when extendcircuit fails that
12792 caused us to not follow the \r\n-based delimiter protocol. Reported
12794 - When tunneling an encrypted directory connection, and its first
12795 circuit fails, do not leave it unattached and ask the controller
12796 to deal. Fixes the second part of bug 681.
12797 - Treat some 403 responses from directory servers as INFO rather than
12798 WARN-severity events.
12800 o Portability / building / compiling:
12801 - When building with --enable-gcc-warnings, check for whether Apple's
12802 warning "-Wshorten-64-to-32" is available.
12803 - Support compilation to target iPhone; patch from cjacker huang.
12804 To build for iPhone, pass the --enable-iphone option to configure.
12805 - Port Tor to build and run correctly on Windows CE systems, using
12806 the wcecompat library. Contributed by Valerio Lupi.
12807 - Detect non-ASCII platforms (if any still exist) and refuse to
12808 build there: some of our code assumes that 'A' is 65 and so on.
12809 - Clear up some MIPSPro compiler warnings.
12810 - Make autoconf search for libevent, openssl, and zlib consistently.
12811 - Update deprecated macros in configure.in.
12812 - When warning about missing headers, tell the user to let us
12813 know if the compile succeeds anyway, so we can downgrade the
12815 - Include the current subversion revision as part of the version
12816 string: either fetch it directly if we're in an SVN checkout, do
12817 some magic to guess it if we're in an SVK checkout, or use
12818 the last-detected version if we're building from a .tar.gz.
12819 Use this version consistently in log messages.
12820 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
12821 - Read resolv.conf files correctly on platforms where read() returns
12822 partial results on small file reads.
12823 - Build without verbose warnings even on gcc 4.2 and 4.3.
12824 - On Windows, correctly detect errors when listing the contents of
12825 a directory. Fix from lodger.
12826 - Run 'make test' as part of 'make dist', so we stop releasing so
12827 many development snapshots that fail their unit tests.
12828 - Add support to detect Libevent versions in the 1.4.x series
12830 - Add command-line arguments to unit-test executable so that we can
12831 invoke any chosen test from the command line rather than having
12832 to run the whole test suite at once; and so that we can turn on
12833 logging for the unit tests.
12834 - Do not automatically run configure from autogen.sh. This
12835 non-standard behavior tended to annoy people who have built other
12837 - Fix a macro/CPP interaction that was confusing some compilers:
12838 some GCCs don't like #if/#endif pairs inside macro arguments.
12840 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
12841 Fixes bug 704; fix from Steven Murdoch.
12842 - Correctly detect transparent proxy support on Linux hosts that
12843 require in.h to be included before netfilter_ipv4.h. Patch
12846 o Logging improvements:
12847 - When we haven't had any application requests lately, don't bother
12848 logging that we have expired a bunch of descriptors.
12849 - When attempting to open a logfile fails, tell us why.
12850 - Only log guard node status when guard node status has changed.
12851 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
12852 make "INFO" 75% less verbose.
12853 - When SafeLogging is disabled, log addresses along with all TLS
12855 - Report TLS "zero return" case as a "clean close" and "IO error"
12856 as a "close". Stop calling closes "unexpected closes": existing
12857 Tors don't use SSL_close(), so having a connection close without
12858 the TLS shutdown handshake is hardly unexpected.
12859 - When we receive a consensus from the future, warn about skew.
12860 - Make "not enough dir info yet" warnings describe *why* Tor feels
12861 it doesn't have enough directory info yet.
12862 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
12863 consumers. (We already do this on HUP.)
12864 - Give more descriptive well-formedness errors for out-of-range
12865 hidden service descriptor/protocol versions.
12866 - Stop recommending that every server operator send mail to tor-ops.
12867 Resolves bug 597. Bugfix on 0.1.2.x.
12868 - Improve skew reporting: try to give the user a better log message
12869 about how skewed they are, and how much this matters.
12870 - New --quiet command-line option to suppress the default console log.
12871 Good in combination with --hash-password.
12872 - Don't complain that "your server has not managed to confirm that its
12873 ports are reachable" if we haven't been able to build any circuits
12875 - Detect the reason for failing to mmap a descriptor file we just
12876 wrote, and give a more useful log message. Fixes bug 533.
12877 - Always prepend "Bug: " to any log message about a bug.
12878 - When dumping memory usage, list bytes used in buffer memory
12880 - When running with dmalloc, dump more stats on hup and on exit.
12881 - Put a platform string (e.g. "Linux i686") in the startup log
12882 message, so when people paste just their logs, we know if it's
12883 OpenBSD or Windows or what.
12884 - When logging memory usage, break down memory used in buffers by
12886 - When we are reporting the DirServer line we just parsed, we were
12887 logging the second stanza of the key fingerprint, not the first.
12888 - Even though Windows is equally happy with / and \ as path separators,
12889 try to use \ consistently on Windows and / consistently on Unix: it
12890 makes the log messages nicer.
12891 - On OSX, stop warning the user that kqueue support in libevent is
12892 "experimental", since it seems to have worked fine for ages.
12894 o Contributed scripts and tools:
12895 - Update linux-tor-prio.sh script to allow QoS based on the uid of
12896 the Tor process. Patch from Marco Bonetti with tweaks from Mike
12898 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
12899 Unix users an easy way to script their Tor process (e.g. by
12900 adjusting bandwidth based on the time of the day).
12901 - In the exitlist script, only consider the most recently published
12902 server descriptor for each server. Also, when the user requests
12903 a list of servers that _reject_ connections to a given address,
12904 explicitly exclude the IPs that also have servers that accept
12905 connections to that address. Resolves bug 405.
12906 - Include a new contrib/tor-exit-notice.html file that exit relay
12907 operators can put on their website to help reduce abuse queries.
12909 o Newly deprecated features:
12910 - The status/version/num-versioning and status/version/num-concurring
12911 GETINFO controller options are no longer useful in the v3 directory
12912 protocol: treat them as deprecated, and warn when they're used.
12913 - The RedirectExits config option is now deprecated.
12915 o Removed features:
12916 - Drop the old code to choke directory connections when the
12917 corresponding OR connections got full: thanks to the cell queue
12918 feature, OR conns don't get full any more.
12919 - Remove the old "dns worker" server DNS code: it hasn't been default
12920 since 0.1.2.2-alpha, and all the servers are using the new
12922 - Remove the code to generate the oldest (v1) directory format.
12923 - Remove support for the old bw_accounting file: we've been storing
12924 bandwidth accounting information in the state file since
12925 0.1.2.5-alpha. This may result in bandwidth accounting errors
12926 if you try to upgrade from 0.1.1.x or earlier, or if you try to
12927 downgrade to 0.1.1.x or earlier.
12928 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
12929 it, it had no AES, and it hasn't seen any security patches since
12931 - Stop overloading the circuit_t.onionskin field for both "onionskin
12932 from a CREATE cell that we are waiting for a cpuworker to be
12933 assigned" and "onionskin from an EXTEND cell that we are going to
12934 send to an OR as soon as we are connected". Might help with bug 600.
12935 - Remove the tor_strpartition() function: its logic was confused,
12936 and it was only used for one thing that could be implemented far
12938 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
12939 and TorControl.py, as they use the old v0 controller protocol,
12940 and are obsoleted by TorFlow anyway.
12941 - Drop support for v1 rendezvous descriptors, since we never used
12942 them anyway, and the code has probably rotted by now. Based on
12943 patch from Karsten Loesing.
12944 - Stop allowing address masks that do not correspond to bit prefixes.
12945 We have warned about these for a really long time; now it's time
12946 to reject them. (Patch from croup.)
12947 - Remove an optimization in the AES counter-mode code that assumed
12948 that the counter never exceeded 2^68. When the counter can be set
12949 arbitrarily as an IV (as it is by Karsten's new hidden services
12950 code), this assumption no longer holds.
12951 - Disable the SETROUTERPURPOSE controller command: it is now
12955 Changes in version 0.1.2.19 - 2008-01-17
12956 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
12957 exit policy a little bit more conservative so it's safer to run an
12958 exit relay on a home system, and fixes a variety of smaller issues.
12961 - Exit policies now reject connections that are addressed to a
12962 relay's public (external) IP address too, unless
12963 ExitPolicyRejectPrivate is turned off. We do this because too
12964 many relays are running nearby to services that trust them based
12965 on network address.
12968 - When the clock jumps forward a lot, do not allow the bandwidth
12969 buckets to become negative. Fixes bug 544.
12970 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
12971 on every successful resolve. Reported by Mike Perry.
12972 - Purge old entries from the "rephist" database and the hidden
12973 service descriptor database even when DirPort is zero.
12974 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
12975 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
12976 crashing or mis-answering these requests.
12977 - When we decide to send a 503 response to a request for servers, do
12978 not then also send the server descriptors: this defeats the whole
12979 purpose. Fixes bug 539.
12982 - Changing the ExitPolicyRejectPrivate setting should cause us to
12983 rebuild our server descriptor.
12984 - Fix handling of hex nicknames when answering controller requests for
12985 networkstatus by name, or when deciding whether to warn about
12986 unknown routers in a config option. (Patch from mwenge.)
12987 - Fix a couple of hard-to-trigger autoconf problems that could result
12988 in really weird results on platforms whose sys/types.h files define
12989 nonstandard integer types.
12990 - Don't try to create the datadir when running --verify-config or
12991 --hash-password. Resolves bug 540.
12992 - If we were having problems getting a particular descriptor from the
12993 directory caches, and then we learned about a new descriptor for
12994 that router, we weren't resetting our failure count. Reported
12996 - Although we fixed bug 539 (where servers would send HTTP status 503
12997 responses _and_ send a body too), there are still servers out there
12998 that haven't upgraded. Therefore, make clients parse such bodies
12999 when they receive them.
13000 - Run correctly on systems where rlim_t is larger than unsigned long.
13001 This includes some 64-bit systems.
13002 - Run correctly on platforms (like some versions of OS X 10.5) where
13003 the real limit for number of open files is OPEN_FILES, not rlim_max
13004 from getrlimit(RLIMIT_NOFILES).
13005 - Avoid a spurious free on base64 failure.
13006 - Avoid segfaults on certain complex invocations of
13007 router_get_by_hexdigest().
13008 - Fix rare bug on REDIRECTSTREAM control command when called with no
13009 port set: it could erroneously report an error when none had
13013 Changes in version 0.1.2.18 - 2007-10-28
13014 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
13015 hidden service introduction that were causing huge delays, and a big
13016 bug that was causing some servers to disappear from the network status
13017 lists for a few hours each day.
13019 o Major bugfixes (crashes):
13020 - If a connection is shut down abruptly because of something that
13021 happened inside connection_flushed_some(), do not call
13022 connection_finished_flushing(). Should fix bug 451:
13023 "connection_stop_writing: Assertion conn->write_event failed"
13024 Bugfix on 0.1.2.7-alpha.
13025 - Fix possible segfaults in functions called from
13026 rend_process_relay_cell().
13028 o Major bugfixes (hidden services):
13029 - Hidden services were choosing introduction points uniquely by
13030 hexdigest, but when constructing the hidden service descriptor
13031 they merely wrote the (potentially ambiguous) nickname.
13032 - Clients now use the v2 intro format for hidden service
13033 connections: they specify their chosen rendezvous point by identity
13034 digest rather than by (potentially ambiguous) nickname. These
13035 changes could speed up hidden service connections dramatically.
13037 o Major bugfixes (other):
13038 - Stop publishing a new server descriptor just because we get a
13039 HUP signal. This led (in a roundabout way) to some servers getting
13040 dropped from the networkstatus lists for a few hours each day.
13041 - When looking for a circuit to cannibalize, consider family as well
13042 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
13043 circuit cannibalization).
13044 - When a router wasn't listed in a new networkstatus, we were leaving
13045 the flags for that router alone -- meaning it remained Named,
13046 Running, etc -- even though absence from the networkstatus means
13047 that it shouldn't be considered to exist at all anymore. Now we
13048 clear all the flags for routers that fall out of the networkstatus
13049 consensus. Fixes bug 529.
13052 - Don't try to access (or alter) the state file when running
13053 --list-fingerprint or --verify-config or --hash-password. Resolves
13055 - When generating information telling us how to extend to a given
13056 router, do not try to include the nickname if it is
13057 absent. Resolves bug 467.
13058 - Fix a user-triggerable segfault in expand_filename(). (There isn't
13059 a way to trigger this remotely.)
13060 - When sending a status event to the controller telling it that an
13061 OR address is reachable, set the port correctly. (Previously we
13062 were reporting the dir port.)
13063 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
13064 command. Bugfix on 0.1.2.17.
13065 - When loading bandwidth history, do not believe any information in
13066 the future. Fixes bug 434.
13067 - When loading entry guard information, do not believe any information
13069 - When we have our clock set far in the future and generate an
13070 onion key, then re-set our clock to be correct, we should not stop
13071 the onion key from getting rotated.
13072 - On some platforms, accept() can return a broken address. Detect
13073 this more quietly, and deal accordingly. Fixes bug 483.
13074 - It's not actually an error to find a non-pending entry in the DNS
13075 cache when canceling a pending resolve. Don't log unless stuff
13076 is fishy. Resolves bug 463.
13077 - Don't reset trusted dir server list when we set a configuration
13078 option. Patch from Robert Hogan.
13081 Changes in version 0.1.2.17 - 2007-08-30
13082 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
13083 X bundles. Vidalia 0.0.14 makes authentication required for the
13084 ControlPort in the default configuration, which addresses important
13085 security risks. Everybody who uses Vidalia (or another controller)
13088 In addition, this Tor update fixes major load balancing problems with
13089 path selection, which should speed things up a lot once many people
13092 o Major bugfixes (security):
13093 - We removed support for the old (v0) control protocol. It has been
13094 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
13095 become more of a headache than it's worth.
13097 o Major bugfixes (load balancing):
13098 - When choosing nodes for non-guard positions, weight guards
13099 proportionally less, since they already have enough load. Patch
13101 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
13102 will allow fast Tor servers to get more attention.
13103 - When we're upgrading from an old Tor version, forget our current
13104 guards and pick new ones according to the new weightings. These
13105 three load balancing patches could raise effective network capacity
13106 by a factor of four. Thanks to Mike Perry for measurements.
13108 o Major bugfixes (stream expiration):
13109 - Expire not-yet-successful application streams in all cases if
13110 they've been around longer than SocksTimeout. Right now there are
13111 some cases where the stream will live forever, demanding a new
13112 circuit every 15 seconds. Fixes bug 454; reported by lodger.
13114 o Minor features (controller):
13115 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
13116 is valid before any authentication has been received. It tells
13117 a controller what kind of authentication is expected, and what
13118 protocol is spoken. Implements proposal 119.
13120 o Minor bugfixes (performance):
13121 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
13122 greatly speeding up loading cached-routers from disk on startup.
13123 - Disable sentinel-based debugging for buffer code: we squashed all
13124 the bugs that this was supposed to detect a long time ago, and now
13125 its only effect is to change our buffer sizes from nice powers of
13126 two (which platform mallocs tend to like) to values slightly over
13127 powers of two (which make some platform mallocs sad).
13129 o Minor bugfixes (misc):
13130 - If exit bandwidth ever exceeds one third of total bandwidth, then
13131 use the correct formula to weight exit nodes when choosing paths.
13132 Based on patch from Mike Perry.
13133 - Choose perfectly fairly among routers when choosing by bandwidth and
13134 weighting by fraction of bandwidth provided by exits. Previously, we
13135 would choose with only approximate fairness, and correct ourselves
13136 if we ran off the end of the list.
13137 - If we require CookieAuthentication but we fail to write the
13138 cookie file, we would warn but not exit, and end up in a state
13139 where no controller could authenticate. Now we exit.
13140 - If we require CookieAuthentication, stop generating a new cookie
13141 every time we change any piece of our config.
13142 - Refuse to start with certain directory authority keys, and
13143 encourage people using them to stop.
13144 - Terminate multi-line control events properly. Original patch
13146 - Fix a minor memory leak when we fail to find enough suitable
13147 servers to choose a circuit.
13148 - Stop leaking part of the descriptor when we run into a particularly
13149 unparseable piece of it.
13152 Changes in version 0.1.2.16 - 2007-08-01
13153 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
13154 remote attacker in certain situations to rewrite the user's torrc
13155 configuration file. This can completely compromise anonymity of users
13156 in most configurations, including those running the Vidalia bundles,
13157 TorK, etc. Or worse.
13159 o Major security fixes:
13160 - Close immediately after missing authentication on control port;
13161 do not allow multiple authentication attempts.
13164 Changes in version 0.1.2.15 - 2007-07-17
13165 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
13166 problems, fixes compilation on BSD, and fixes a variety of other
13167 bugs. Everybody should upgrade.
13169 o Major bugfixes (compilation):
13170 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
13172 o Major bugfixes (crashes):
13173 - Try even harder not to dereference the first character after
13174 an mmap(). Reported by lodger.
13175 - Fix a crash bug in directory authorities when we re-number the
13176 routerlist while inserting a new router.
13177 - When the cached-routers file is an even multiple of the page size,
13178 don't run off the end and crash. (Fixes bug 455; based on idea
13180 - Fix eventdns.c behavior on Solaris: It is critical to include
13181 orconfig.h _before_ sys/types.h, so that we can get the expected
13182 definition of _FILE_OFFSET_BITS.
13184 o Major bugfixes (security):
13185 - Fix a possible buffer overrun when using BSD natd support. Bug
13187 - When sending destroy cells from a circuit's origin, don't include
13188 the reason for tearing down the circuit. The spec says we didn't,
13189 and now we actually don't. Reported by lodger.
13190 - Keep streamids from different exits on a circuit separate. This
13191 bug may have allowed other routers on a given circuit to inject
13192 cells into streams. Reported by lodger; fixes bug 446.
13193 - If there's a never-before-connected-to guard node in our list,
13194 never choose any guards past it. This way we don't expand our
13195 guard list unless we need to.
13197 o Minor bugfixes (guard nodes):
13198 - Weight guard selection by bandwidth, so that low-bandwidth nodes
13199 don't get overused as guards.
13201 o Minor bugfixes (directory):
13202 - Correctly count the number of authorities that recommend each
13203 version. Previously, we were under-counting by 1.
13204 - Fix a potential crash bug when we load many server descriptors at
13205 once and some of them make others of them obsolete. Fixes bug 458.
13207 o Minor bugfixes (hidden services):
13208 - Stop tearing down the whole circuit when the user asks for a
13209 connection to a port that the hidden service didn't configure.
13212 o Minor bugfixes (misc):
13213 - On Windows, we were preventing other processes from reading
13214 cached-routers while Tor was running. Reported by janbar.
13215 - Fix a possible (but very unlikely) bug in picking routers by
13216 bandwidth. Add a log message to confirm that it is in fact
13217 unlikely. Patch from lodger.
13218 - Backport a couple of memory leak fixes.
13219 - Backport miscellaneous cosmetic bugfixes.
13222 Changes in version 0.1.2.14 - 2007-05-25
13223 Tor 0.1.2.14 changes the addresses of two directory authorities (this
13224 change especially affects those who serve or use hidden services),
13225 and fixes several other crash- and security-related bugs.
13227 o Directory authority changes:
13228 - Two directory authorities (moria1 and moria2) just moved to new
13229 IP addresses. This change will particularly affect those who serve
13230 or use hidden services.
13232 o Major bugfixes (crashes):
13233 - If a directory server runs out of space in the connection table
13234 as it's processing a begin_dir request, it will free the exit stream
13235 but leave it attached to the circuit, leading to unpredictable
13236 behavior. (Reported by seeess, fixes bug 425.)
13237 - Fix a bug in dirserv_remove_invalid() that would cause authorities
13238 to corrupt memory under some really unlikely scenarios.
13239 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
13240 - Avoid segfaults when reading from mmaped descriptor file. (Reported
13243 o Major bugfixes (security):
13244 - When choosing an entry guard for a circuit, avoid using guards
13245 that are in the same family as the chosen exit -- not just guards
13246 that are exactly the chosen exit. (Reported by lodger.)
13248 o Major bugfixes (resource management):
13249 - If a directory authority is down, skip it when deciding where to get
13250 networkstatus objects or descriptors. Otherwise we keep asking
13251 every 10 seconds forever. Fixes bug 384.
13252 - Count it as a failure if we fetch a valid network-status but we
13253 don't want to keep it. Otherwise we'll keep fetching it and keep
13254 not wanting to keep it. Fixes part of bug 422.
13255 - If all of our dirservers have given us bad or no networkstatuses
13256 lately, then stop hammering them once per minute even when we
13257 think they're failed. Fixes another part of bug 422.
13260 - Actually set the purpose correctly for descriptors inserted with
13261 purpose=controller.
13262 - When we have k non-v2 authorities in our DirServer config,
13263 we ignored the last k authorities in the list when updating our
13265 - Correctly back-off from requesting router descriptors that we are
13266 having a hard time downloading.
13267 - Read resolv.conf files correctly on platforms where read() returns
13268 partial results on small file reads.
13269 - Don't rebuild the entire router store every time we get 32K of
13270 routers: rebuild it when the journal gets very large, or when
13271 the gaps in the store get very large.
13274 - When routers publish SVN revisions in their router descriptors,
13275 authorities now include those versions correctly in networkstatus
13277 - Warn when using a version of libevent before 1.3b to run a server on
13278 OSX or BSD: these versions interact badly with userspace threads.
13281 Changes in version 0.1.2.13 - 2007-04-24
13282 This release features some major anonymity fixes, such as safer path
13283 selection; better client performance; faster bootstrapping, better
13284 address detection, and better DNS support for servers; write limiting as
13285 well as read limiting to make servers easier to run; and a huge pile of
13286 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
13288 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
13289 of the Freenode IRC network, remembering his patience and vision for
13290 free speech on the Internet.
13292 o Major features, client performance:
13293 - Weight directory requests by advertised bandwidth. Now we can
13294 let servers enable write limiting but still allow most clients to
13295 succeed at their directory requests. (We still ignore weights when
13296 choosing a directory authority; I hope this is a feature.)
13297 - Stop overloading exit nodes -- avoid choosing them for entry or
13298 middle hops when the total bandwidth available from non-exit nodes
13299 is much higher than the total bandwidth available from exit nodes.
13300 - Rather than waiting a fixed amount of time between retrying
13301 application connections, we wait only 10 seconds for the first,
13302 10 seconds for the second, and 15 seconds for each retry after
13303 that. Hopefully this will improve the expected user experience.
13304 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
13305 to open a stream fails; now we do in more cases. This should
13306 make clients able to find a good exit faster in some cases, since
13307 unhandleable requests will now get an error rather than timing out.
13309 o Major features, client functionality:
13310 - Implement BEGIN_DIR cells, so we can connect to a directory
13311 server via TLS to do encrypted directory requests rather than
13312 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
13313 config options if you like. For now, this feature only works if
13314 you already have a descriptor for the destination dirserver.
13315 - Add support for transparent application connections: this basically
13316 bundles the functionality of trans-proxy-tor into the Tor
13317 mainline. Now hosts with compliant pf/netfilter implementations
13318 can redirect TCP connections straight to Tor without diverting
13319 through SOCKS. (Based on patch from tup.)
13320 - Add support for using natd; this allows FreeBSDs earlier than
13321 5.1.2 to have ipfw send connections through Tor without using
13322 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
13324 o Major features, servers:
13325 - Setting up a dyndns name for your server is now optional: servers
13326 with no hostname or IP address will learn their IP address by
13327 asking the directory authorities. This code only kicks in when you
13328 would normally have exited with a "no address" error. Nothing's
13329 authenticated, so use with care.
13330 - Directory servers now spool server descriptors, v1 directories,
13331 and v2 networkstatus objects to buffers as needed rather than en
13332 masse. They also mmap the cached-routers files. These steps save
13334 - Stop requiring clients to have well-formed certificates, and stop
13335 checking nicknames in certificates. (Clients have certificates so
13336 that they can look like Tor servers, but in the future we might want
13337 to allow them to look like regular TLS clients instead. Nicknames
13338 in certificates serve no purpose other than making our protocol
13339 easier to recognize on the wire.) Implements proposal 106.
13341 o Improvements on DNS support:
13342 - Add "eventdns" asynchronous dns library originally based on code
13343 from Adam Langley. Now we can discard the old rickety dnsworker
13344 concept, and support a wider variety of DNS functions. Allows
13345 multithreaded builds on NetBSD and OpenBSD again.
13346 - Add server-side support for "reverse" DNS lookups (using PTR
13347 records so clients can determine the canonical hostname for a given
13348 IPv4 address). Only supported by servers using eventdns; servers
13349 now announce in their descriptors if they don't support eventdns.
13350 - Workaround for name servers (like Earthlink's) that hijack failing
13351 DNS requests and replace the no-such-server answer with a "helpful"
13352 redirect to an advertising-driven search portal. Also work around
13353 DNS hijackers who "helpfully" decline to hijack known-invalid
13354 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
13355 lets you turn it off.
13356 - Servers now check for the case when common DNS requests are going to
13357 wildcarded addresses (i.e. all getting the same answer), and change
13358 their exit policy to reject *:* if it's happening.
13359 - When asked to resolve a hostname, don't use non-exit servers unless
13360 requested to do so. This allows servers with broken DNS to be
13361 useful to the network.
13362 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
13363 useless IPv6 DNS resolves.
13364 - Specify and implement client-side SOCKS5 interface for reverse DNS
13365 lookups (see doc/socks-extensions.txt). Also cache them.
13366 - When we change nameservers or IP addresses, reset and re-launch
13367 our tests for DNS hijacking.
13369 o Improvements on reachability testing:
13370 - Servers send out a burst of long-range padding cells once they've
13371 established that they're reachable. Spread them over 4 circuits,
13372 so hopefully a few will be fast. This exercises bandwidth and
13373 bootstraps them into the directory more quickly.
13374 - When we find our DirPort to be reachable, publish a new descriptor
13375 so we'll tell the world (reported by pnx).
13376 - Directory authorities now only decide that routers are reachable
13377 if their identity keys are as expected.
13378 - Do DirPort reachability tests less often, since a single test
13379 chews through many circuits before giving up.
13380 - Avoid some false positives during reachability testing: don't try
13381 to test via a server that's on the same /24 network as us.
13382 - Start publishing one minute or so after we find our ORPort
13383 to be reachable. This will help reduce the number of descriptors
13384 we have for ourselves floating around, since it's quite likely
13385 other things (e.g. DirPort) will change during that minute too.
13386 - Routers no longer try to rebuild long-term connections to directory
13387 authorities, and directory authorities no longer try to rebuild
13388 long-term connections to all servers. We still don't hang up
13389 connections in these two cases though -- we need to look at it
13390 more carefully to avoid flapping, and we likely need to wait til
13391 0.1.1.x is obsolete.
13393 o Improvements on rate limiting:
13394 - Enable write limiting as well as read limiting. Now we sacrifice
13395 capacity if we're pushing out lots of directory traffic, rather
13396 than overrunning the user's intended bandwidth limits.
13397 - Include TLS overhead when counting bandwidth usage; previously, we
13398 would count only the bytes sent over TLS, but not the bytes used
13400 - Servers decline directory requests much more aggressively when
13401 they're low on bandwidth. Otherwise they end up queueing more and
13402 more directory responses, which can't be good for latency.
13403 - But never refuse directory requests from local addresses.
13404 - Be willing to read or write on local connections (e.g. controller
13405 connections) even when the global rate limiting buckets are empty.
13406 - Flush local controller connection buffers periodically as we're
13407 writing to them, so we avoid queueing 4+ megabytes of data before
13409 - Revise and clean up the torrc.sample that we ship with; add
13410 a section for BandwidthRate and BandwidthBurst.
13412 o Major features, NT services:
13413 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
13414 command-line flag so that admins can override the default by saying
13415 "tor --service install --user "SomeUser"". This will not affect
13416 existing installed services. Also, warn the user that the service
13417 will look for its configuration file in the service user's
13418 %appdata% directory. (We can't do the "hardwire the user's appdata
13419 directory" trick any more, since we may not have read access to that
13421 - Support running the Tor service with a torrc not in the same
13422 directory as tor.exe and default to using the torrc located in
13423 the %appdata%\Tor\ of the user who installed the service. Patch
13425 - Add an --ignore-missing-torrc command-line option so that we can
13426 get the "use sensible defaults if the configuration file doesn't
13427 exist" behavior even when specifying a torrc location on the
13429 - When stopping an NT service, wait up to 10 sec for it to actually
13430 stop. (Patch from Matt Edman; resolves bug 295.)
13432 o Directory authority improvements:
13433 - Stop letting hibernating or obsolete servers affect uptime and
13435 - Stop listing hibernating servers in the v1 directory.
13436 - Authorities no longer recommend exits as guards if this would shift
13437 too much load to the exit nodes.
13438 - Authorities now specify server versions in networkstatus. This adds
13439 about 2% to the size of compressed networkstatus docs, and allows
13440 clients to tell which servers support BEGIN_DIR and which don't.
13441 The implementation is forward-compatible with a proposed future
13442 protocol version scheme not tied to Tor versions.
13443 - DirServer configuration lines now have an orport= option so
13444 clients can open encrypted tunnels to the authorities without
13445 having downloaded their descriptors yet. Enabled for moria1,
13446 moria2, tor26, and lefkada now in the default configuration.
13447 - Add a BadDirectory flag to network status docs so that authorities
13448 can (eventually) tell clients about caches they believe to be
13449 broken. Not used yet.
13450 - Allow authorities to list nodes as bad exits in their
13451 approved-routers file by fingerprint or by address. If most
13452 authorities set a BadExit flag for a server, clients don't think
13453 of it as a general-purpose exit. Clients only consider authorities
13454 that advertise themselves as listing bad exits.
13455 - Patch from Steve Hildrey: Generate network status correctly on
13456 non-versioning dirservers.
13457 - Have directory authorities allow larger amounts of drift in uptime
13458 without replacing the server descriptor: previously, a server that
13459 restarted every 30 minutes could have 48 "interesting" descriptors
13461 - Reserve the nickname "Unnamed" for routers that can't pick
13462 a hostname: any router can call itself Unnamed; directory
13463 authorities will never allocate Unnamed to any particular router;
13464 clients won't believe that any router is the canonical Unnamed.
13466 o Directory mirrors and clients:
13467 - Discard any v1 directory info that's over 1 month old (for
13468 directories) or over 1 week old (for running-routers lists).
13469 - Clients track responses with status 503 from dirservers. After a
13470 dirserver has given us a 503, we try not to use it until an hour has
13471 gone by, or until we have no dirservers that haven't given us a 503.
13472 - When we get a 503 from a directory, and we're not a server, we no
13473 longer count the failure against the total number of failures
13474 allowed for the object we're trying to download.
13475 - Prepare for servers to publish descriptors less often: never
13476 discard a descriptor simply for being too old until either it is
13477 recommended by no authorities, or until we get a better one for
13478 the same router. Make caches consider retaining old recommended
13479 routers for even longer.
13480 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
13481 headers for content, so that we can work better in the presence of
13482 caching HTTP proxies.
13483 - Stop fetching descriptors if you're not a dir mirror and you
13484 haven't tried to establish any circuits lately. (This currently
13485 causes some dangerous behavior, because when you start up again
13486 you'll use your ancient server descriptors.)
13488 o Major fixes, crashes:
13489 - Stop crashing when the controller asks us to resetconf more than
13490 one config option at once. (Vidalia 0.0.11 does this.)
13491 - Fix a longstanding obscure crash bug that could occur when we run
13492 out of DNS worker processes, if we're not using eventdns. (Resolves
13494 - Fix an assert that could trigger if a controller quickly set then
13495 cleared EntryNodes. (Bug found by Udo van den Heuvel.)
13496 - Avoid crash when telling controller about stream-status and a
13497 stream is detached.
13498 - Avoid sending junk to controllers or segfaulting when a controller
13499 uses EVENT_NEW_DESC with verbose nicknames.
13500 - Stop triggering asserts if the controller tries to extend hidden
13501 service circuits (reported by mwenge).
13502 - If we start a server with ClientOnly 1, then set ClientOnly to 0
13503 and hup, stop triggering an assert based on an empty onion_key.
13504 - Mask out all signals in sub-threads; only the libevent signal
13505 handler should be processing them. This should prevent some crashes
13506 on some machines using pthreads. (Patch from coderman.)
13507 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
13509 o Major fixes, anonymity/security:
13510 - Automatically avoid picking more than one node from the same
13511 /16 network when constructing a circuit. Add an
13512 "EnforceDistinctSubnets" option to let people disable it if they
13513 want to operate private test networks on a single subnet.
13514 - When generating bandwidth history, round down to the nearest
13515 1k. When storing accounting data, round up to the nearest 1k.
13516 - When we're running as a server, remember when we last rotated onion
13517 keys, so that we will rotate keys once they're a week old even if
13518 we never stay up for a week ourselves.
13519 - If a client asked for a server by name, and there's a named server
13520 in our network-status but we don't have its descriptor yet, we
13521 could return an unnamed server instead.
13522 - Reject (most) attempts to use Tor circuits with length one. (If
13523 many people start using Tor as a one-hop proxy, exit nodes become
13524 a more attractive target for compromise.)
13525 - Just because your DirPort is open doesn't mean people should be
13526 able to remotely teach you about hidden service descriptors. Now
13527 only accept rendezvous posts if you've got HSAuthoritativeDir set.
13528 - Fix a potential race condition in the rpm installer. Found by
13530 - Do not log IPs with TLS failures for incoming TLS
13531 connections. (Fixes bug 382.)
13533 o Major fixes, other:
13534 - If our system clock jumps back in time, don't publish a negative
13535 uptime in the descriptor.
13536 - When we start during an accounting interval before it's time to wake
13537 up, remember to wake up at the correct time. (May fix bug 342.)
13538 - Previously, we would cache up to 16 old networkstatus documents
13539 indefinitely, if they came from nontrusted authorities. Now we
13540 discard them if they are more than 10 days old.
13541 - When we have a state file we cannot parse, tell the user and
13542 move it aside. Now we avoid situations where the user starts
13543 Tor in 1904, Tor writes a state file with that timestamp in it,
13544 the user fixes her clock, and Tor refuses to start.
13545 - Publish a new descriptor after we hup/reload. This is important
13546 if our config has changed such that we'll want to start advertising
13547 our DirPort now, etc.
13548 - If we are using an exit enclave and we can't connect, e.g. because
13549 its webserver is misconfigured to not listen on localhost, then
13550 back off and try connecting from somewhere else before we fail.
13552 o New config options or behaviors:
13553 - When EntryNodes are configured, rebuild the guard list to contain,
13554 in order: the EntryNodes that were guards before; the rest of the
13555 EntryNodes; the nodes that were guards before.
13556 - Do not warn when individual nodes in the configuration's EntryNodes,
13557 ExitNodes, etc are down: warn only when all possible nodes
13558 are down. (Fixes bug 348.)
13559 - Put a lower-bound on MaxAdvertisedBandwidth.
13560 - Start using the state file to store bandwidth accounting data:
13561 the bw_accounting file is now obsolete. We'll keep generating it
13562 for a while for people who are still using 0.1.2.4-alpha.
13563 - Try to batch changes to the state file so that we do as few
13564 disk writes as possible while still storing important things in
13566 - The state file and the bw_accounting file get saved less often when
13567 the AvoidDiskWrites config option is set.
13568 - Make PIDFile work on Windows.
13569 - Add internal descriptions for a bunch of configuration options:
13570 accessible via controller interface and in comments in saved
13572 - Reject *:563 (NNTPS) in the default exit policy. We already reject
13573 NNTP by default, so this seems like a sensible addition.
13574 - Clients now reject hostnames with invalid characters. This should
13575 avoid some inadvertent info leaks. Add an option
13576 AllowNonRFC953Hostnames to disable this behavior, in case somebody
13577 is running a private network with hosts called @, !, and #.
13578 - Check for addresses with invalid characters at the exit as well,
13579 and warn less verbosely when they fail. You can override this by
13580 setting ServerDNSAllowNonRFC953Addresses to 1.
13581 - Remove some options that have been deprecated since at least
13582 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
13583 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
13584 to set log options. Mark PathlenCoinWeight as obsolete.
13585 - Stop accepting certain malformed ports in configured exit policies.
13586 - When the user uses bad syntax in the Log config line, stop
13587 suggesting other bad syntax as a replacement.
13588 - Add new config option "ResolvConf" to let the server operator
13589 choose an alternate resolve.conf file when using eventdns.
13590 - If one of our entry guards is on the ExcludeNodes list, or the
13591 directory authorities don't think it's a good guard, treat it as
13592 if it were unlisted: stop using it as a guard, and throw it off
13593 the guards list if it stays that way for a long time.
13594 - Allow directory authorities to be marked separately as authorities
13595 for the v1 directory protocol, the v2 directory protocol, and
13596 as hidden service directories, to make it easier to retire old
13597 authorities. V1 authorities should set "HSAuthoritativeDir 1"
13598 to continue being hidden service authorities too.
13599 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
13600 - Make TrackExitHosts case-insensitive, and fix the behavior of
13601 ".suffix" TrackExitHosts items to avoid matching in the middle of
13603 - New DirPort behavior: if you have your dirport set, you download
13604 descriptors aggressively like a directory mirror, whether or not
13605 your ORPort is set.
13608 - Create a new file ReleaseNotes which was the old ChangeLog. The
13609 new ChangeLog file now includes the notes for all development
13611 - Add a new address-spec.txt document to describe our special-case
13612 addresses: .exit, .onion, and .noconnnect.
13613 - Fork the v1 directory protocol into its own spec document,
13614 and mark dir-spec.txt as the currently correct (v2) spec.
13616 o Packaging, porting, and contrib
13617 - "tor --verify-config" now exits with -1(255) or 0 depending on
13618 whether the config options are bad or good.
13619 - The Debian package now uses --verify-config when (re)starting,
13620 to distinguish configuration errors from other errors.
13621 - Adapt a patch from goodell to let the contrib/exitlist script
13622 take arguments rather than require direct editing.
13623 - Prevent the contrib/exitlist script from printing the same
13624 result more than once.
13625 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
13626 - In the hidden service example in torrc.sample, stop recommending
13627 esoteric and discouraged hidden service options.
13628 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
13629 values before failing, and always enables eventdns.
13630 - Try to detect Windows correctly when cross-compiling.
13631 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
13632 Try to fix this in configure.in by checking for most functions
13633 before we check for libevent.
13634 - Update RPMs to require libevent 1.2.
13635 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
13636 or later. Log when we are doing this, so we can diagnose it when
13637 it fails. (Also, recommend libevent 1.1b for kqueue and
13638 win32 methods; deprecate libevent 1.0b harder; make libevent
13639 recommendation system saner.)
13640 - Build with recent (1.3+) libevents on platforms that do not
13641 define the nonstandard types "u_int8_t" and friends.
13642 - Remove architecture from OS X builds. The official builds are
13643 now universal binaries.
13644 - Run correctly on OS X platforms with case-sensitive filesystems.
13645 - Correctly set maximum connection limit on Cygwin. (This time
13647 - Start compiling on MinGW on Windows (patches from Mike Chiussi
13649 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
13650 - Finally fix the openssl warnings from newer gccs that believe that
13651 ignoring a return value is okay, but casting a return value and
13652 then ignoring it is a sign of madness.
13653 - On architectures where sizeof(int)>4, still clamp declarable
13654 bandwidth to INT32_MAX.
13656 o Minor features, controller:
13657 - Warn the user when an application uses the obsolete binary v0
13658 control protocol. We're planning to remove support for it during
13659 the next development series, so it's good to give people some
13661 - Add STREAM_BW events to report per-entry-stream bandwidth
13662 use. (Patch from Robert Hogan.)
13663 - Rate-limit SIGNEWNYM signals in response to controllers that
13664 impolitely generate them for every single stream. (Patch from
13665 mwenge; closes bug 394.)
13666 - Add a REMAP status to stream events to note that a stream's
13667 address has changed because of a cached address or a MapAddress
13669 - Make REMAP stream events have a SOURCE (cache or exit), and
13670 make them generated in every case where we get a successful
13671 connected or resolved cell.
13672 - Track reasons for OR connection failure; make these reasons
13673 available via the controller interface. (Patch from Mike Perry.)
13674 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
13675 can learn when clients are sending malformed hostnames to Tor.
13676 - Specify and implement some of the controller status events.
13677 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
13678 - Reimplement GETINFO so that info/names stays in sync with the
13680 - Implement "GETINFO fingerprint".
13681 - Implement "SETEVENTS GUARD" so controllers can get updates on
13682 entry guard status as it changes.
13683 - Make all connections to addresses of the form ".noconnect"
13684 immediately get closed. This lets application/controller combos
13685 successfully test whether they're talking to the same Tor by
13686 watching for STREAM events.
13687 - Add a REASON field to CIRC events; for backward compatibility, this
13688 field is sent only to controllers that have enabled the extended
13689 event format. Also, add additional reason codes to explain why
13690 a given circuit has been destroyed or truncated. (Patches from
13692 - Add a REMOTE_REASON field to extended CIRC events to tell the
13693 controller why a remote OR told us to close a circuit.
13694 - Stream events also now have REASON and REMOTE_REASON fields,
13695 working much like those for circuit events.
13696 - There's now a GETINFO ns/... field so that controllers can ask Tor
13697 about the current status of a router.
13698 - A new event type "NS" to inform a controller when our opinion of
13699 a router's status has changed.
13700 - Add a GETINFO events/names and GETINFO features/names so controllers
13701 can tell which events and features are supported.
13702 - A new CLEARDNSCACHE signal to allow controllers to clear the
13703 client-side DNS cache without expiring circuits.
13704 - Fix CIRC controller events so that controllers can learn the
13705 identity digests of non-Named servers used in circuit paths.
13706 - Let controllers ask for more useful identifiers for servers. Instead
13707 of learning identity digests for un-Named servers and nicknames
13708 for Named servers, the new identifiers include digest, nickname,
13709 and indication of Named status. Off by default; see control-spec.txt
13710 for more information.
13711 - Add a "getinfo address" controller command so it can display Tor's
13712 best guess to the user.
13713 - New controller event to alert the controller when our server
13714 descriptor has changed.
13715 - Give more meaningful errors on controller authentication failure.
13716 - Export the default exit policy via the control port, so controllers
13717 don't need to guess what it is / will be later.
13719 o Minor bugfixes, controller:
13720 - When creating a circuit via the controller, send a 'launched'
13721 event when we're done, so we follow the spec better.
13722 - Correct the control spec to match how the code actually responds
13723 to 'getinfo addr-mappings/*'. Reported by daejees.
13724 - The control spec described a GUARDS event, but the code
13725 implemented a GUARD event. Standardize on GUARD, but let people
13726 ask for GUARDS too. Reported by daejees.
13727 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
13728 clear the corresponding on_circuit variable, and remember later
13729 that we don't need to send a redundant CLOSED event. (Resolves part
13731 - Report events where a resolve succeeded or where we got a socks
13732 protocol error correctly, rather than calling both of them
13734 - Change reported stream target addresses to IP consistently when
13735 we finally get the IP from an exit node.
13736 - Send log messages to the controller even if they happen to be very
13738 - Flush ERR-level controller status events just like we currently
13739 flush ERR-level log events, so that a Tor shutdown doesn't prevent
13740 the controller from learning about current events.
13741 - Report the circuit number correctly in STREAM CLOSED events. Bug
13742 reported by Mike Perry.
13743 - Do not report bizarre values for results of accounting GETINFOs
13744 when the last second's write or read exceeds the allotted bandwidth.
13745 - Report "unrecognized key" rather than an empty string when the
13746 controller tries to fetch a networkstatus that doesn't exist.
13747 - When the controller does a "GETINFO network-status", tell it
13748 about even those routers whose descriptors are very old, and use
13749 long nicknames where appropriate.
13750 - Fix handling of verbose nicknames with ORCONN controller events:
13751 make them show up exactly when requested, rather than exactly when
13753 - Controller signals now work on non-Unix platforms that don't define
13754 SIGUSR1 and SIGUSR2 the way we expect.
13755 - Respond to SIGNAL command before we execute the signal, in case
13756 the signal shuts us down. Suggested by Karsten Loesing.
13757 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
13759 o Minor features, code performance:
13760 - Major performance improvement on inserting descriptors: change
13761 algorithm from O(n^2) to O(n).
13762 - Do not rotate onion key immediately after setting it for the first
13764 - Call router_have_min_dir_info half as often. (This is showing up in
13765 some profiles, but not others.)
13766 - When using GCC, make log_debug never get called at all, and its
13767 arguments never get evaluated, when no debug logs are configured.
13768 (This is showing up in some profiles, but not others.)
13769 - Statistics dumped by -USR2 now include a breakdown of public key
13770 operations, for profiling.
13771 - Make the common memory allocation path faster on machines where
13772 malloc(0) returns a pointer.
13773 - Split circuit_t into origin_circuit_t and or_circuit_t, and
13774 split connection_t into edge, or, dir, control, and base structs.
13775 These will save quite a bit of memory on busy servers, and they'll
13776 also help us track down bugs in the code and bugs in the spec.
13777 - Use OpenSSL's AES implementation on platforms where it's faster.
13778 This could save us as much as 10% CPU usage.
13780 o Minor features, descriptors and descriptor handling:
13781 - Avoid duplicate entries on MyFamily line in server descriptor.
13782 - When Tor receives a router descriptor that it asked for, but
13783 no longer wants (because it has received fresh networkstatuses
13784 in the meantime), do not warn the user. Cache the descriptor if
13785 we're a cache; drop it if we aren't.
13786 - Servers no longer ever list themselves in their "family" line,
13787 even if configured to do so. This makes it easier to configure
13788 family lists conveniently.
13790 o Minor fixes, confusing/misleading log messages:
13791 - Display correct results when reporting which versions are
13792 recommended, and how recommended they are. (Resolves bug 383.)
13793 - Inform the server operator when we decide not to advertise a
13794 DirPort due to AccountingMax enabled or a low BandwidthRate.
13795 - Only include function names in log messages for info/debug messages.
13796 For notice/warn/err, the content of the message should be clear on
13797 its own, and printing the function name only confuses users.
13798 - Remove even more protocol-related warnings from Tor server logs,
13799 such as bad TLS handshakes and malformed begin cells.
13800 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
13801 when the IP address is mapped through MapAddress to a hostname.
13802 - Fix misleading log messages: an entry guard that is "unlisted",
13803 as well as not known to be "down" (because we've never heard
13804 of it), is not therefore "up".
13806 o Minor fixes, old/obsolete behavior:
13807 - Start assuming we can use a create_fast cell if we don't know
13808 what version a router is running.
13809 - We no longer look for identity and onion keys in "identity.key" and
13810 "onion.key" -- these were replaced by secret_id_key and
13811 secret_onion_key in 0.0.8pre1.
13812 - We no longer require unrecognized directory entries to be
13814 - Drop compatibility with obsolete Tors that permit create cells
13815 to have the wrong circ_id_type.
13816 - Remove code to special-case "-cvs" ending, since it has not
13817 actually mattered since 0.0.9.
13818 - Don't re-write the fingerprint file every restart, unless it has
13821 o Minor fixes, misc client-side behavior:
13822 - Always remove expired routers and networkstatus docs before checking
13823 whether we have enough information to build circuits. (Fixes
13825 - When computing clock skew from directory HTTP headers, consider what
13826 time it was when we finished asking for the directory, not what
13828 - Make our socks5 handling more robust to broken socks clients:
13829 throw out everything waiting on the buffer in between socks
13830 handshake phases, since they can't possibly (so the theory
13831 goes) have predicted what we plan to respond to them.
13832 - Expire socks connections if they spend too long waiting for the
13833 handshake to finish. Previously we would let them sit around for
13834 days, if the connecting application didn't close them either.
13835 - And if the socks handshake hasn't started, don't send a
13836 "DNS resolve socks failed" handshake reply; just close it.
13837 - If the user asks to use invalid exit nodes, be willing to use
13839 - Track unreachable entry guards correctly: don't conflate
13840 'unreachable by us right now' with 'listed as down by the directory
13841 authorities'. With the old code, if a guard was unreachable by us
13842 but listed as running, it would clog our guard list forever.
13843 - Behave correctly in case we ever have a network with more than
13844 2GB/s total advertised capacity.
13845 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
13846 - Fix a memory leak when we ask for "all" networkstatuses and we
13847 get one we don't recognize.
13850 Changes in version 0.1.1.26 - 2006-12-14
13851 o Security bugfixes:
13852 - Stop sending the HttpProxyAuthenticator string to directory
13853 servers when directory connections are tunnelled through Tor.
13854 - Clients no longer store bandwidth history in the state file.
13855 - Do not log introduction points for hidden services if SafeLogging
13859 - Fix an assert failure when a directory authority sets
13860 AuthDirRejectUnlisted and then receives a descriptor from an
13861 unlisted router (reported by seeess).
13864 Changes in version 0.1.1.25 - 2006-11-04
13866 - When a client asks us to resolve (rather than connect to)
13867 an address, and we have a cached answer, give them the cached
13868 answer. Previously, we would give them no answer at all.
13869 - We were building exactly the wrong circuits when we predict
13870 hidden service requirements, meaning Tor would have to build all
13871 its circuits on demand.
13872 - If none of our live entry guards have a high uptime, but we
13873 require a guard with a high uptime, try adding a new guard before
13874 we give up on the requirement. This patch should make long-lived
13875 connections more stable on average.
13876 - When testing reachability of our DirPort, don't launch new
13877 tests when there's already one in progress -- unreachable
13878 servers were stacking up dozens of testing streams.
13880 o Security bugfixes:
13881 - When the user sends a NEWNYM signal, clear the client-side DNS
13882 cache too. Otherwise we continue to act on previous information.
13885 - Avoid a memory corruption bug when creating a hash table for
13887 - Avoid possibility of controller-triggered crash when misusing
13888 certain commands from a v0 controller on platforms that do not
13889 handle printf("%s",NULL) gracefully.
13890 - Avoid infinite loop on unexpected controller input.
13891 - Don't log spurious warnings when we see a circuit close reason we
13892 don't recognize; it's probably just from a newer version of Tor.
13893 - Add Vidalia to the OS X uninstaller script, so when we uninstall
13894 Tor/Privoxy we also uninstall Vidalia.
13897 Changes in version 0.1.1.24 - 2006-09-29
13899 - Allow really slow clients to not hang up five minutes into their
13900 directory downloads (suggested by Adam J. Richter).
13901 - Fix major performance regression from 0.1.0.x: instead of checking
13902 whether we have enough directory information every time we want to
13903 do something, only check when the directory information has changed.
13904 This should improve client CPU usage by 25-50%.
13905 - Don't crash if, after a server has been running for a while,
13906 it can't resolve its hostname.
13907 - When a client asks us to resolve (not connect to) an address,
13908 and we have a cached answer, give them the cached answer.
13909 Previously, we would give them no answer at all.
13912 - Allow Tor to start when RunAsDaemon is set but no logs are set.
13913 - Don't crash when the controller receives a third argument to an
13914 "extendcircuit" request.
13915 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
13916 response; fix error code when "getinfo dir/status/" fails.
13917 - Fix configure.in to not produce broken configure files with
13918 more recent versions of autoconf. Thanks to Clint for his auto*
13920 - Fix security bug on NetBSD that could allow someone to force
13921 uninitialized RAM to be sent to a server's DNS resolver. This
13922 only affects NetBSD and other platforms that do not bounds-check
13924 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
13925 methods: these are known to be buggy.
13926 - If we're a directory mirror and we ask for "all" network status
13927 documents, we would discard status documents from authorities
13928 we don't recognize.
13931 Changes in version 0.1.1.23 - 2006-07-30
13933 - Fast Tor servers, especially exit nodes, were triggering asserts
13934 due to a bug in handling the list of pending DNS resolves. Some
13935 bugs still remain here; we're hunting them.
13936 - Entry guards could crash clients by sending unexpected input.
13937 - More fixes on reachability testing: if you find yourself reachable,
13938 then don't ever make any client requests (so you stop predicting
13939 circuits), then hup or have your clock jump, then later your IP
13940 changes, you won't think circuits are working, so you won't try to
13941 test reachability, so you won't publish.
13944 - Avoid a crash if the controller does a resetconf firewallports
13945 and then a setconf fascistfirewall=1.
13946 - Avoid an integer underflow when the dir authority decides whether
13947 a router is stable: we might wrongly label it stable, and compute
13948 a slightly wrong median stability, when a descriptor is published
13950 - Fix a place where we might trigger an assert if we can't build our
13951 own server descriptor yet.
13954 Changes in version 0.1.1.22 - 2006-07-05
13956 - Fix a big bug that was causing servers to not find themselves
13957 reachable if they changed IP addresses. Since only 0.1.1.22+
13958 servers can do reachability testing correctly, now we automatically
13959 make sure to test via one of these.
13960 - Fix to allow clients and mirrors to learn directory info from
13961 descriptor downloads that get cut off partway through.
13962 - Directory authorities had a bug in deciding if a newly published
13963 descriptor was novel enough to make everybody want a copy -- a few
13964 servers seem to be publishing new descriptors many times a minute.
13966 - Fix a rare bug that was causing some servers to complain about
13967 "closing wedged cpuworkers" and skip some circuit create requests.
13968 - Make the Exit flag in directory status documents actually work.
13971 Changes in version 0.1.1.21 - 2006-06-10
13972 o Crash and assert fixes from 0.1.1.20:
13973 - Fix a rare crash on Tor servers that have enabled hibernation.
13974 - Fix a seg fault on startup for Tor networks that use only one
13975 directory authority.
13976 - Fix an assert from a race condition that occurs on Tor servers
13977 while exiting, where various threads are trying to log that they're
13978 exiting, and delete the logs, at the same time.
13979 - Make our unit tests pass again on certain obscure platforms.
13982 - Add support for building SUSE RPM packages.
13983 - Speed up initial bootstrapping for clients: if we are making our
13984 first ever connection to any entry guard, then don't mark it down
13986 - When only one Tor server in the network is labelled as a guard,
13987 and we've already picked him, we would cycle endlessly picking him
13988 again, being unhappy about it, etc. Now we specifically exclude
13989 current guards when picking a new guard.
13990 - Servers send create cells more reliably after the TLS connection
13991 is established: we were sometimes forgetting to send half of them
13992 when we had more than one pending.
13993 - If we get a create cell that asks us to extend somewhere, but the
13994 Tor server there doesn't match the expected digest, we now send
13995 a destroy cell back, rather than silently doing nothing.
13996 - Make options->RedirectExit work again.
13997 - Make cookie authentication for the controller work again.
13998 - Stop being picky about unusual characters in the arguments to
13999 mapaddress. It's none of our business.
14000 - Add a new config option "TestVia" that lets you specify preferred
14001 middle hops to use for test circuits. Perhaps this will let me
14002 debug the reachability problems better.
14004 o Log / documentation fixes:
14005 - If we're a server and some peer has a broken TLS certificate, don't
14006 log about it unless ProtocolWarnings is set, i.e., we want to hear
14007 about protocol violations by others.
14008 - Fix spelling of VirtualAddrNetwork in man page.
14009 - Add a better explanation at the top of the autogenerated torrc file
14010 about what happened to our old torrc.
14013 Changes in version 0.1.1.20 - 2006-05-23
14014 o Crash and assert fixes from 0.1.0.17:
14015 - Fix assert bug in close_logs() on exit: when we close and delete
14016 logs, remove them all from the global "logfiles" list.
14017 - Fix an assert error when we're out of space in the connection_list
14018 and we try to post a hidden service descriptor (reported by Peter
14020 - Fix a rare assert error when we've tried all intro points for
14021 a hidden service and we try fetching the service descriptor again:
14022 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed".
14023 - Setconf SocksListenAddress kills Tor if it fails to bind. Now back
14024 out and refuse the setconf if it would fail.
14025 - If you specify a relative torrc path and you set RunAsDaemon in
14026 your torrc, then it chdir()'s to the new directory. If you then
14027 HUP, it tries to load the new torrc location, fails, and exits.
14028 The fix: no longer allow a relative path to torrc when using -f.
14029 - Check for integer overflows in more places, when adding elements
14030 to smartlists. This could possibly prevent a buffer overflow
14031 on malicious huge inputs.
14033 o Security fixes, major:
14034 - When we're printing strings from the network, don't try to print
14035 non-printable characters. Now we're safer against shell escape
14036 sequence exploits, and also against attacks to fool users into
14037 misreading their logs.
14038 - Implement entry guards: automatically choose a handful of entry
14039 nodes and stick with them for all circuits. Only pick new guards
14040 when the ones you have are unsuitable, and if the old guards
14041 become suitable again, switch back. This will increase security
14042 dramatically against certain end-point attacks. The EntryNodes
14043 config option now provides some hints about which entry guards you
14044 want to use most; and StrictEntryNodes means to only use those.
14045 Fixes CVE-2006-0414.
14046 - Implement exit enclaves: if we know an IP address for the
14047 destination, and there's a running Tor server at that address
14048 which allows exit to the destination, then extend the circuit to
14049 that exit first. This provides end-to-end encryption and end-to-end
14050 authentication. Also, if the user wants a .exit address or enclave,
14051 use 4 hops rather than 3, and cannibalize a general circ for it
14053 - Obey our firewall options more faithfully:
14054 . If we can't get to a dirserver directly, try going via Tor.
14055 . Don't ever try to connect (as a client) to a place our
14056 firewall options forbid.
14057 . If we specify a proxy and also firewall options, obey the
14058 firewall options even when we're using the proxy: some proxies
14059 can only proxy to certain destinations.
14060 - Make clients regenerate their keys when their IP address changes.
14061 - For the OS X package's modified privoxy config file, comment
14062 out the "logfile" line so we don't log everything passed
14064 - Our TLS handshakes were generating a single public/private
14065 keypair for the TLS context, rather than making a new one for
14066 each new connection. Oops. (But we were still rotating them
14067 periodically, so it's not so bad.)
14068 - When we were cannibalizing a circuit with a particular exit
14069 node in mind, we weren't checking to see if that exit node was
14070 already present earlier in the circuit. Now we are.
14071 - Require server descriptors to list IPv4 addresses -- hostnames
14072 are no longer allowed. This also fixes potential vulnerabilities
14073 to servers providing hostnames as their address and then
14074 preferentially resolving them so they can partition users.
14075 - Our logic to decide if the OR we connected to was the right guy
14076 was brittle and maybe open to a mitm for invalid routers.
14078 o Security fixes, minor:
14079 - Adjust tor-spec.txt to parameterize cell and key lengths. Now
14080 Ian Goldberg can prove things about our handshake protocol more
14082 - Make directory authorities generate a separate "guard" flag to
14083 mean "would make a good entry guard". Clients now honor the
14084 is_guard flag rather than looking at is_fast or is_stable.
14085 - Try to list MyFamily elements by key, not by nickname, and warn
14086 if we've not heard of a server.
14087 - Start using RAND_bytes rather than RAND_pseudo_bytes from
14088 OpenSSL. Also, reseed our entropy every hour, not just at
14089 startup. And add entropy in 512-bit chunks, not 160-bit chunks.
14090 - Refuse server descriptors where the fingerprint line doesn't match
14091 the included identity key. Tor doesn't care, but other apps (and
14092 humans) might actually be trusting the fingerprint line.
14093 - We used to kill the circuit when we receive a relay command we
14094 don't recognize. Now we just drop that cell.
14095 - Fix a bug found by Lasse Overlier: when we were making internal
14096 circuits (intended to be cannibalized later for rendezvous and
14097 introduction circuits), we were picking them so that they had
14098 useful exit nodes. There was no need for this, and it actually
14099 aids some statistical attacks.
14100 - Start treating internal circuits and exit circuits separately.
14101 It's important to keep them separate because internal circuits
14102 have their last hops picked like middle hops, rather than like
14103 exit hops. So exiting on them will break the user's expectations.
14104 - Fix a possible way to DoS dirservers.
14105 - When the client asked for a rendezvous port that the hidden
14106 service didn't want to provide, we were sending an IP address
14107 back along with the end cell. Fortunately, it was zero. But stop
14110 o Packaging improvements:
14111 - Implement --with-libevent-dir option to ./configure. Improve
14112 search techniques to find libevent, and use those for openssl too.
14113 - Fix a couple of bugs in OpenSSL detection. Deal better when
14114 there are multiple SSLs installed with different versions.
14115 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
14116 - On non-gcc compilers (e.g. Solaris's cc), use "-g -O" instead of
14118 - Make unit tests (and other invocations that aren't the real Tor)
14119 run without launching listeners, creating subdirectories, and so on.
14120 - The OS X installer was adding a symlink for tor_resolve but
14121 the binary was called tor-resolve (reported by Thomas Hardly).
14122 - Now we can target arch and OS in rpm builds (contributed by
14123 Phobos). Also make the resulting dist-rpm filename match the
14125 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
14126 if you log to syslog and want something other than LOG_DAEMON.
14127 - Fix the torify (tsocks) config file to not use Tor for localhost
14129 - Start shipping socks-extensions.txt, tor-doc-unix.html,
14130 tor-doc-server.html, and stylesheet.css in the tarball.
14131 - Stop shipping tor-doc.html, INSTALL, and README in the tarball.
14132 They are useless now.
14133 - Add Peter Palfrader's contributed check-tor script. It lets you
14134 easily check whether a given server (referenced by nickname)
14135 is reachable by you.
14136 - Add BSD-style contributed startup script "rc.subr" from Peter
14139 o Directory improvements -- new directory protocol:
14140 - See tor/doc/dir-spec.txt for all the juicy details. Key points:
14141 - Authorities and caches publish individual descriptors (by
14142 digest, by fingerprint, by "all", and by "tell me yours").
14143 - Clients don't download or use the old directory anymore. Now they
14144 download network-statuses from the directory authorities, and
14145 fetch individual server descriptors as needed from mirrors.
14146 - Clients don't download descriptors of non-running servers.
14147 - Download descriptors by digest, not by fingerprint. Caches try to
14148 download all listed digests from authorities; clients try to
14149 download "best" digests from caches. This avoids partitioning
14150 and isolating attacks better.
14151 - Only upload a new server descriptor when options change, 18
14152 hours have passed, uptime is reset, or bandwidth changes a lot.
14153 - Directory authorities silently throw away new descriptors that
14154 haven't changed much if the timestamps are similar. We do this to
14155 tolerate older Tor servers that upload a new descriptor every 15
14156 minutes. (It seemed like a good idea at the time.)
14157 - Clients choose directory servers from the network status lists,
14158 not from their internal list of router descriptors. Now they can
14159 go to caches directly rather than needing to go to authorities
14160 to bootstrap the first set of descriptors.
14161 - When picking a random directory, prefer non-authorities if any
14163 - Add a new flag to network-status indicating whether the server
14164 can answer v2 directory requests too.
14165 - Directory mirrors now cache up to 16 unrecognized network-status
14166 docs, so new directory authorities will be cached too.
14167 - Stop parsing, storing, or using running-routers output (but
14168 mirrors still cache and serve it).
14169 - Clients consider a threshold of "versioning" directory authorities
14170 before deciding whether to warn the user that he's obsolete.
14171 - Authorities publish separate sorted lists of recommended versions
14172 for clients and for servers.
14173 - Change DirServers config line to note which dirs are v1 authorities.
14174 - Put nicknames on the DirServer line, so we can refer to them
14175 without requiring all our users to memorize their IP addresses.
14176 - Remove option when getting directory cache to see whether they
14177 support running-routers; they all do now. Replace it with one
14178 to see whether caches support v2 stuff.
14179 - Stop listing down or invalid nodes in the v1 directory. This
14180 reduces its bulk by about 1/3, and reduces load on mirrors.
14181 - Mirrors no longer cache the v1 directory as often.
14182 - If we as a directory mirror don't know of any v1 directory
14183 authorities, then don't try to cache any v1 directories.
14185 o Other directory improvements:
14186 - Add lefkada.eecs.harvard.edu and tor.dizum.com as fourth and
14187 fifth authoritative directory servers.
14188 - Directory authorities no longer require an open connection from
14189 a server to consider him "reachable". We need this change because
14190 when we add new directory authorities, old servers won't know not
14191 to hang up on them.
14192 - Dir authorities now do their own external reachability testing
14193 of each server, and only list as running the ones they found to
14194 be reachable. We also send back warnings to the server's logs if
14195 it uploads a descriptor that we already believe is unreachable.
14196 - Spread the directory authorities' reachability testing over the
14197 entire testing interval, so we don't try to do 500 TLS's at once
14199 - Make the "stable" router flag in network-status be the median of
14200 the uptimes of running valid servers, and make clients pay
14201 attention to the network-status flags. Thus the cutoff adapts
14202 to the stability of the network as a whole, making IRC, IM, etc
14203 connections more reliable.
14204 - Make the v2 dir's "Fast" flag based on relative capacity, just
14205 like "Stable" is based on median uptime. Name everything in the
14206 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
14207 - Retry directory requests if we fail to get an answer we like
14208 from a given dirserver (we were retrying before, but only if
14209 we fail to connect).
14210 - Return a robots.txt on our dirport to discourage google indexing.
14212 o Controller protocol improvements:
14213 - Revised controller protocol (version 1) that uses ascii rather
14214 than binary: tor/doc/control-spec.txt. Add supporting libraries
14215 in python and java and c# so you can use the controller from your
14216 applications without caring how our protocol works.
14217 - Allow the DEBUG controller event to work again. Mark certain log
14218 entries as "don't tell this to controllers", so we avoid cycles.
14219 - New controller function "getinfo accounting", to ask how
14220 many bytes we've used in this time period.
14221 - Add a "resetconf" command so you can set config options like
14222 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
14223 a config option in the torrc with no value, then it clears it
14224 entirely (rather than setting it to its default).
14225 - Add a "getinfo config-file" to tell us where torrc is. Also
14226 expose guard nodes, config options/names.
14227 - Add a "quit" command (when when using the controller manually).
14228 - Add a new signal "newnym" to "change pseudonyms" -- that is, to
14229 stop using any currently-dirty circuits for new streams, so we
14230 don't link new actions to old actions. This also occurs on HUP
14231 or "signal reload".
14232 - If we would close a stream early (e.g. it asks for a .exit that
14233 we know would refuse it) but the LeaveStreamsUnattached config
14234 option is set by the controller, then don't close it.
14235 - Add a new controller event type "authdir_newdescs" that allows
14236 controllers to get all server descriptors that were uploaded to
14237 a router in its role as directory authority.
14238 - New controller option "getinfo desc/all-recent" to fetch the
14239 latest server descriptor for every router that Tor knows about.
14240 - Fix the controller's "attachstream 0" command to treat conn like
14241 it just connected, doing address remapping, handling .exit and
14242 .onion idioms, and so on. Now we're more uniform in making sure
14243 that the controller hears about new and closing connections.
14244 - Permit transitioning from ORPort==0 to ORPort!=0, and back, from
14245 the controller. Also, rotate dns and cpu workers if the controller
14246 changes options that will affect them; and initialize the dns
14247 worker cache tree whether or not we start out as a server.
14248 - Add a new circuit purpose 'controller' to let the controller ask
14249 for a circuit that Tor won't try to use. Extend the "extendcircuit"
14250 controller command to let you specify the purpose if you're starting
14251 a new circuit. Add a new "setcircuitpurpose" controller command to
14252 let you change a circuit's purpose after it's been created.
14253 - Let the controller ask for "getinfo dir/server/foo" so it can ask
14254 directly rather than connecting to the dir port. "getinfo
14255 dir/status/foo" also works, but currently only if your DirPort
14257 - Let the controller tell us about certain router descriptors
14258 that it doesn't want Tor to use in circuits. Implement
14259 "setrouterpurpose" and modify "+postdescriptor" to do this.
14260 - If the controller's *setconf commands fail, collect an error
14261 message in a string and hand it back to the controller -- don't
14262 just tell them to go read their logs.
14264 o Scalability, resource management, and performance:
14265 - Fix a major load balance bug: we were round-robin reading in 16 KB
14266 chunks, and servers with bandwidthrate of 20 KB, while downloading
14267 a 600 KB directory, would starve their other connections. Now we
14268 try to be a bit more fair.
14269 - Be more conservative about whether to advertise our DirPort.
14270 The main change is to not advertise if we're running at capacity
14271 and either a) we could hibernate ever or b) our capacity is low
14272 and we're using a default DirPort.
14273 - We weren't cannibalizing circuits correctly for
14274 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
14275 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
14276 build those from scratch. This should make hidden services faster.
14277 - Predict required circuits better, with an eye toward making hidden
14278 services faster on the service end.
14279 - Compress exit policies even more: look for duplicate lines and
14281 - Generate 18.0.0.0/8 address policy format in descs when we can;
14282 warn when the mask is not reducible to a bit-prefix.
14283 - There used to be two ways to specify your listening ports in a
14284 server descriptor: on the "router" line and with a separate "ports"
14285 line. Remove support for the "ports" line.
14286 - Reduce memory requirements in our structs by changing the order
14287 of fields. Replace balanced trees with hash tables. Inline
14288 bottleneck smartlist functions. Add a "Map from digest to void*"
14289 abstraction so we can do less hex encoding/decoding, and use it
14290 in router_get_by_digest(). Many other CPU and memory improvements.
14291 - Allow tor_gzip_uncompress to extract as much as possible from
14292 truncated compressed data. Try to extract as many
14293 descriptors as possible from truncated http responses (when
14294 purpose is DIR_PURPOSE_FETCH_ROUTERDESC).
14295 - Make circ->onionskin a pointer, not a static array. moria2 was using
14296 125000 circuit_t's after it had been up for a few weeks, which
14297 translates to 20+ megs of wasted space.
14298 - The private half of our EDH handshake keys are now chosen out
14299 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
14300 - Stop doing the complex voodoo overkill checking for insecure
14301 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
14302 - Do round-robin writes for TLS of at most 16 kB per write. This
14303 might be more fair on loaded Tor servers.
14304 - Do not use unaligned memory access on alpha, mips, or mipsel.
14305 It *works*, but is very slow, so we treat them as if it doesn't.
14307 o Other bugfixes and improvements:
14308 - Start storing useful information to $DATADIR/state, so we can
14309 remember things across invocations of Tor. Retain unrecognized
14310 lines so we can be forward-compatible, and write a TorVersion line
14311 so we can be backward-compatible.
14312 - If ORPort is set, Address is not explicitly set, and our hostname
14313 resolves to a private IP address, try to use an interface address
14314 if it has a public address. Now Windows machines that think of
14315 themselves as localhost can guess their address.
14316 - Regenerate our local descriptor if it's dirty and we try to use
14317 it locally (e.g. if it changes during reachability detection).
14318 This was causing some Tor servers to keep publishing the same
14319 initial descriptor forever.
14320 - Tor servers with dynamic IP addresses were needing to wait 18
14321 hours before they could start doing reachability testing using
14322 the new IP address and ports. This is because they were using
14323 the internal descriptor to learn what to test, yet they were only
14324 rebuilding the descriptor once they decided they were reachable.
14325 - It turns out we couldn't bootstrap a network since we added
14326 reachability detection in 0.1.0.1-rc. Good thing the Tor network
14327 has never gone down. Add an AssumeReachable config option to let
14328 servers and authorities bootstrap. When we're trying to build a
14329 high-uptime or high-bandwidth circuit but there aren't enough
14330 suitable servers, try being less picky rather than simply failing.
14331 - Newly bootstrapped Tor networks couldn't establish hidden service
14332 circuits until they had nodes with high uptime. Be more tolerant.
14333 - Really busy servers were keeping enough circuits open on stable
14334 connections that they were wrapping around the circuit_id
14335 space. (It's only two bytes.) This exposed a bug where we would
14336 feel free to reuse a circuit_id even if it still exists but has
14337 been marked for close. Try to fix this bug. Some bug remains.
14338 - When we fail to bind or listen on an incoming or outgoing
14339 socket, we now close it before refusing, rather than just
14340 leaking it. (Thanks to Peter Palfrader for finding.)
14341 - Fix a file descriptor leak in start_daemon().
14342 - On Windows, you can't always reopen a port right after you've
14343 closed it. So change retry_listeners() to only close and re-open
14344 ports that have changed.
14345 - Workaround a problem with some http proxies that refuse GET
14346 requests that specify "Content-Length: 0". Reported by Adrian.
14347 - Recover better from TCP connections to Tor servers that are
14348 broken but don't tell you (it happens!); and rotate TLS
14349 connections once a week.
14350 - Fix a scary-looking but apparently harmless bug where circuits
14351 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
14352 servers, and never switch to state CIRCUIT_STATE_OPEN.
14353 - Check for even more Windows version flags when writing the platform
14354 string in server descriptors, and note any we don't recognize.
14355 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
14356 get a better idea of why their circuits failed. Not used yet.
14357 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
14358 We don't use them yet, but maybe one day our DNS resolver will be
14359 able to discover them.
14360 - Let people type "tor --install" as well as "tor -install" when they
14361 want to make it an NT service.
14362 - Looks like we were never delivering deflated (i.e. compressed)
14363 running-routers lists, even when asked. Oops.
14364 - We were leaking some memory every time the client changed IPs.
14365 - Clean up more of the OpenSSL memory when exiting, so we can detect
14366 memory leaks better.
14367 - Never call free() on tor_malloc()d memory. This will help us
14368 use dmalloc to detect memory leaks.
14369 - Some Tor servers process billions of cells per day. These
14370 statistics are now uint64_t's.
14371 - Check [X-]Forwarded-For headers in HTTP requests when generating
14372 log messages. This lets people run dirservers (and caches) behind
14373 Apache but still know which IP addresses are causing warnings.
14374 - Fix minor integer overflow in calculating when we expect to use up
14375 our bandwidth allocation before hibernating.
14376 - Lower the minimum required number of file descriptors to 1000,
14377 so we can have some overhead for Valgrind on Linux, where the
14378 default ulimit -n is 1024.
14379 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
14380 and its existence is confusing some users.
14382 o Config option fixes:
14383 - Add a new config option ExitPolicyRejectPrivate which defaults
14384 to on. Now all exit policies will begin with rejecting private
14385 addresses, unless the server operator explicitly turns it off.
14386 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB.
14387 - Add new ReachableORAddresses and ReachableDirAddresses options
14388 that understand address policies. FascistFirewall is now a synonym
14389 for "ReachableORAddresses *:443", "ReachableDirAddresses *:80".
14390 - Start calling it FooListenAddress rather than FooBindAddress,
14391 since few of our users know what it means to bind an address
14393 - If the user gave Tor an odd number of command-line arguments,
14394 we were silently ignoring the last one. Now we complain and fail.
14395 This wins the oldest-bug prize -- this bug has been present since
14396 November 2002, as released in Tor 0.0.0.
14397 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
14398 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
14399 it would silently ignore the 6668.
14400 - If we get a linelist or linelist_s config option from the torrc,
14401 e.g. ExitPolicy, and it has no value, warn and skip rather than
14402 silently resetting it to its default.
14403 - Setconf was appending items to linelists, not clearing them.
14404 - Add MyFamily to torrc.sample in the server section, so operators
14405 will be more likely to learn that it exists.
14406 - Make ContactInfo mandatory for authoritative directory servers.
14407 - MaxConn has been obsolete for a while now. Document the ConnLimit
14408 config option, which is a *minimum* number of file descriptors
14409 that must be available else Tor refuses to start.
14410 - Get rid of IgnoreVersion undocumented config option, and make us
14411 only warn, never exit, when we're running an obsolete version.
14412 - Make MonthlyAccountingStart config option truly obsolete now.
14413 - Correct the man page entry on TrackHostExitsExpire.
14414 - Let directory authorities start even if they don't specify an
14415 Address config option.
14416 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
14417 reflect the updated flags in our v2 dir protocol.
14419 o Config option features:
14420 - Add a new config option FastFirstHopPK (on by default) so clients
14421 do a trivial crypto handshake for their first hop, since TLS has
14422 already taken care of confidentiality and authentication.
14423 - Let the user set ControlListenAddress in the torrc. This can be
14424 dangerous, but there are some cases (like a secured LAN) where it
14426 - New config options to help controllers: FetchServerDescriptors
14427 and FetchHidServDescriptors for whether to fetch server
14428 info and hidserv info or let the controller do it, and
14429 PublishServerDescriptor and PublishHidServDescriptors.
14430 - Also let the controller set the __AllDirActionsPrivate config
14431 option if you want all directory fetches/publishes to happen via
14432 Tor (it assumes your controller bootstraps your circuits).
14433 - Add "HardwareAccel" config option: support for crypto hardware
14434 accelerators via OpenSSL. Off by default, until we find somebody
14435 smart who can test it for us. (It appears to produce seg faults
14436 in at least some cases.)
14437 - New config option "AuthDirRejectUnlisted" for directory authorities
14438 as a panic button: if we get flooded with unusable servers we can
14439 revert to only listing servers in the approved-routers file.
14440 - Directory authorities can now reject/invalidate by key and IP,
14441 with the config options "AuthDirInvalid" and "AuthDirReject", or
14442 by marking a fingerprint as "!reject" or "!invalid" (as its
14443 nickname) in the approved-routers file. This is useful since
14444 currently we automatically list servers as running and usable
14445 even if we know they're jerks.
14446 - Add a new config option TestSocks so people can see whether their
14447 applications are using socks4, socks4a, socks5-with-ip, or
14448 socks5-with-fqdn. This way they don't have to keep mucking
14449 with tcpdump and wondering if something got cached somewhere.
14450 - Add "private:*" as an alias in configuration for policies. Now
14451 you can simplify your exit policy rather than needing to list
14452 every single internal or nonroutable network space.
14453 - Accept "private:*" in routerdesc exit policies; not generated yet
14454 because older Tors do not understand it.
14455 - Add configuration option "V1AuthoritativeDirectory 1" which
14456 moria1, moria2, and tor26 have set.
14457 - Implement an option, VirtualAddrMask, to set which addresses
14458 get handed out in response to mapaddress requests. This works
14459 around a bug in tsocks where 127.0.0.0/8 is never socksified.
14460 - Add a new config option FetchUselessDescriptors, off by default,
14461 for when you plan to run "exitlist" on your client and you want
14462 to know about even the non-running descriptors.
14463 - SocksTimeout: How long do we let a socks connection wait
14464 unattached before we fail it?
14465 - CircuitBuildTimeout: Cull non-open circuits that were born
14466 at least this many seconds ago.
14467 - CircuitIdleTimeout: Cull open clean circuits that were born
14468 at least this many seconds ago.
14469 - New config option SafeSocks to reject all application connections
14470 using unsafe socks protocols. Defaults to off.
14472 o Improved and clearer log messages:
14473 - Reduce clutter in server logs. We're going to try to make
14474 them actually usable now. New config option ProtocolWarnings that
14475 lets you hear about how _other Tors_ are breaking the protocol. Off
14477 - Divide log messages into logging domains. Once we put some sort
14478 of interface on this, it will let people looking at more verbose
14479 log levels specify the topics they want to hear more about.
14480 - Log server fingerprint on startup, so new server operators don't
14481 have to go hunting around their filesystem for it.
14482 - Provide dire warnings to any users who set DirServer manually;
14483 move it out of torrc.sample and into torrc.complete.
14484 - Make the log message less scary when all the dirservers are
14485 temporarily unreachable.
14486 - When tor_socketpair() fails in Windows, give a reasonable
14487 Windows-style errno back.
14488 - Improve tor_gettimeofday() granularity on windows.
14489 - We were printing the number of idle dns workers incorrectly when
14491 - Handle duplicate lines in approved-routers files without warning.
14492 - We were whining about using socks4 or socks5-with-local-lookup
14493 even when it's an IP address in the "virtual" range we designed
14494 exactly for this case.
14495 - Check for named servers when looking them up by nickname;
14496 warn when we're calling a non-named server by its nickname;
14497 don't warn twice about the same name.
14498 - Downgrade the dirserver log messages when whining about
14500 - Correct "your server is reachable" log entries to indicate that
14501 it was self-testing that told us so.
14502 - If we're trying to be a Tor server and running Windows 95/98/ME
14503 as a server, explain that we'll likely crash.
14504 - Provide a more useful warn message when our onion queue gets full:
14505 the CPU is too slow or the exit policy is too liberal.
14506 - Don't warn when we receive a 503 from a dirserver/cache -- this
14507 will pave the way for them being able to refuse if they're busy.
14508 - When we fail to bind a listener, try to provide a more useful
14509 log message: e.g., "Is Tor already running?"
14510 - Only start testing reachability once we've established a
14511 circuit. This will make startup on dir authorities less noisy.
14512 - Don't try to upload hidden service descriptors until we have
14513 established a circuit.
14514 - Tor didn't warn when it failed to open a log file.
14515 - Warn when listening on a public address for socks. We suspect a
14516 lot of people are setting themselves up as open socks proxies,
14517 and they have no idea that jerks on the Internet are using them,
14518 since they simply proxy the traffic into the Tor network.
14519 - Give a useful message when people run Tor as the wrong user,
14520 rather than telling them to start chowning random directories.
14521 - Fix a harmless bug that was causing Tor servers to log
14522 "Got an end because of misc error, but we're not an AP. Closing."
14523 - Fix wrong log message when you add a "HiddenServiceNodes" config
14524 line without any HiddenServiceDir line (reported by Chris Thomas).
14525 - Directory authorities now stop whining so loudly about bad
14526 descriptors that they fetch from other dirservers. So when there's
14527 a log complaint, it's for sure from a freshly uploaded descriptor.
14528 - When logging via syslog, include the pid whenever we provide
14529 a log entry. Suggested by Todd Fries.
14530 - When we're shutting down and we do something like try to post a
14531 server descriptor or rendezvous descriptor, don't complain that
14532 we seem to be unreachable. Of course we are, we're shutting down.
14533 - Change log line for unreachability to explicitly suggest /etc/hosts
14534 as the culprit. Also make it clearer what IP address and ports we're
14535 testing for reachability.
14536 - Put quotes around user-supplied strings when logging so users are
14537 more likely to realize if they add bad characters (like quotes)
14539 - NT service patch from Matt Edman to improve error messages on Win32.
14542 Changes in version 0.1.0.17 - 2006-02-17
14543 o Crash bugfixes on 0.1.0.x:
14544 - When servers with a non-zero DirPort came out of hibernation,
14545 sometimes they would trigger an assert.
14547 o Other important bugfixes:
14548 - On platforms that don't have getrlimit (like Windows), we were
14549 artificially constraining ourselves to a max of 1024
14550 connections. Now just assume that we can handle as many as 15000
14551 connections. Hopefully this won't cause other problems.
14553 o Backported features:
14554 - When we're a server, a client asks for an old-style directory,
14555 and our write bucket is empty, don't give it to him. This way
14556 small servers can continue to serve the directory *sometimes*,
14557 without getting overloaded.
14558 - Whenever you get a 503 in response to a directory fetch, try
14559 once more. This will become important once servers start sending
14560 503's whenever they feel busy.
14561 - Fetch a new directory every 120 minutes, not every 40 minutes.
14562 Now that we have hundreds of thousands of users running the old
14563 directory algorithm, it's starting to hurt a lot.
14564 - Bump up the period for forcing a hidden service descriptor upload
14565 from 20 minutes to 1 hour.
14568 Changes in version 0.1.0.16 - 2006-01-02
14569 o Crash bugfixes on 0.1.0.x:
14570 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
14571 corrupting the heap, losing FDs, or crashing when we need to resize
14572 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
14573 - It turns out sparc64 platforms crash on unaligned memory access
14574 too -- so detect and avoid this.
14575 - Handle truncated compressed data correctly (by detecting it and
14577 - Fix possible-but-unlikely free(NULL) in control.c.
14578 - When we were closing connections, there was a rare case that
14579 stomped on memory, triggering seg faults and asserts.
14580 - Avoid potential infinite recursion when building a descriptor. (We
14581 don't know that it ever happened, but better to fix it anyway.)
14582 - We were neglecting to unlink marked circuits from soon-to-close OR
14583 connections, which caused some rare scribbling on freed memory.
14584 - Fix a memory stomping race bug when closing the joining point of two
14585 rendezvous circuits.
14586 - Fix an assert in time parsing found by Steven Murdoch.
14588 o Other bugfixes on 0.1.0.x:
14589 - When we're doing reachability testing, provide more useful log
14590 messages so the operator knows what to expect.
14591 - Do not check whether DirPort is reachable when we are suppressing
14592 advertising it because of hibernation.
14593 - When building with -static or on Solaris, we sometimes needed -ldl.
14594 - One of the dirservers (tor26) changed its IP address.
14595 - When we're deciding whether a stream has enough circuits around
14596 that can handle it, count the freshly dirty ones and not the ones
14597 that are so dirty they won't be able to handle it.
14598 - When we're expiring old circuits, we had a logic error that caused
14599 us to close new rendezvous circuits rather than old ones.
14600 - Give a more helpful log message when you try to change ORPort via
14601 the controller: you should upgrade Tor if you want that to work.
14602 - We were failing to parse Tor versions that start with "Tor ".
14603 - Tolerate faulty streams better: when a stream fails for reason
14604 exitpolicy, stop assuming that the router is lying about his exit
14605 policy. When a stream fails for reason misc, allow it to retry just
14606 as if it was resolvefailed. When a stream has failed three times,
14607 reset its failure count so we can try again and get all three tries.
14610 Changes in version 0.1.0.15 - 2005-09-23
14611 o Bugfixes on 0.1.0.x:
14612 - Reject ports 465 and 587 (spam targets) in default exit policy.
14613 - Don't crash when we don't have any spare file descriptors and we
14614 try to spawn a dns or cpu worker.
14615 - Get rid of IgnoreVersion undocumented config option, and make us
14616 only warn, never exit, when we're running an obsolete version.
14617 - Don't try to print a null string when your server finds itself to
14618 be unreachable and the Address config option is empty.
14619 - Make the numbers in read-history and write-history into uint64s,
14620 so they don't overflow and publish negatives in the descriptor.
14621 - Fix a minor memory leak in smartlist_string_remove().
14622 - We were only allowing ourselves to upload a server descriptor at
14623 most every 20 minutes, even if it changed earlier than that.
14624 - Clean up log entries that pointed to old URLs.
14627 Changes in version 0.1.0.14 - 2005-08-08
14628 o Bugfixes on 0.1.0.x:
14629 - Fix the other half of the bug with crypto handshakes
14631 - Fix an assert trigger if you send a 'signal term' via the
14632 controller when it's listening for 'event info' messages.
14635 Changes in version 0.1.0.13 - 2005-08-04
14636 o Bugfixes on 0.1.0.x:
14637 - Fix a critical bug in the security of our crypto handshakes.
14638 - Fix a size_t underflow in smartlist_join_strings2() that made
14639 it do bad things when you hand it an empty smartlist.
14640 - Fix Windows installer to ship Tor license (thanks to Aphex for
14641 pointing out this oversight) and put a link to the doc directory
14643 - Explicitly set no-unaligned-access for sparc: it turns out the
14644 new gcc's let you compile broken code, but that doesn't make it
14648 Changes in version 0.1.0.12 - 2005-07-18
14649 o New directory servers:
14650 - tor26 has changed IP address.
14652 o Bugfixes on 0.1.0.x:
14653 - Fix a possible double-free in tor_gzip_uncompress().
14654 - When --disable-threads is set, do not search for or link against
14655 pthreads libraries.
14656 - Don't trigger an assert if an authoritative directory server
14657 claims its dirport is 0.
14658 - Fix bug with removing Tor as an NT service: some people were
14659 getting "The service did not return an error." Thanks to Matt
14663 Changes in version 0.1.0.11 - 2005-06-30
14664 o Bugfixes on 0.1.0.x:
14665 - Fix major security bug: servers were disregarding their
14666 exit policies if clients behaved unexpectedly.
14667 - Make OS X init script check for missing argument, so we don't
14668 confuse users who invoke it incorrectly.
14669 - Fix a seg fault in "tor --hash-password foo".
14670 - The MAPADDRESS control command was broken.
14673 Changes in version 0.1.0.10 - 2005-06-14
14675 - Make NT services work and start on startup on Win32 (based on
14676 patch by Matt Edman). See the FAQ entry for details.
14677 - Make 'platform' string in descriptor more accurate for Win32
14678 servers, so it's not just "unknown platform".
14679 - REUSEADDR on normal platforms means you can rebind to the port
14680 right after somebody else has let it go. But REUSEADDR on Win32
14681 means you can bind to the port _even when somebody else already
14682 has it bound_! So, don't do that on Win32.
14683 - Clean up the log messages when starting on Win32 with no config
14685 - Allow seeding the RNG on Win32 even when you're not running as
14686 Administrator. If seeding the RNG on Win32 fails, quit.
14688 o Assert / crash bugs:
14689 - Refuse relay cells that claim to have a length larger than the
14690 maximum allowed. This prevents a potential attack that could read
14691 arbitrary memory (e.g. keys) from an exit server's process
14693 - If unofficial Tor clients connect and send weird TLS certs, our
14694 Tor server triggers an assert. Stop asserting, and start handling
14695 TLS errors better in other situations too.
14696 - Fix a race condition that can trigger an assert when we have a
14697 pending create cell and an OR connection attempt fails.
14700 - Use pthreads for worker processes rather than forking. This was
14701 forced because when we forked, we ended up wasting a lot of
14702 duplicate ram over time.
14703 - Also switch to foo_r versions of some library calls to allow
14704 reentry and threadsafeness.
14705 - Implement --disable-threads configure option. Disable threads on
14706 netbsd and openbsd by default, because they have no reentrant
14707 resolver functions (!), and on solaris since it has other
14709 - Fix possible bug on threading platforms (e.g. win32) which was
14710 leaking a file descriptor whenever a cpuworker or dnsworker died.
14711 - Fix a minor memory leak when somebody establishes an introduction
14712 point at your Tor server.
14713 - Fix possible memory leak in tor_lookup_hostname(). (Thanks to
14715 - Add ./configure --with-dmalloc option, to track memory leaks.
14716 - And try to free all memory on closing, so we can detect what
14719 o Protocol correctness:
14720 - When we've connected to an OR and handshaked but didn't like
14721 the result, we were closing the conn without sending destroy
14722 cells back for pending circuits. Now send those destroys.
14723 - Start sending 'truncated' cells back rather than destroy cells
14724 if the circuit closes in front of you. This means we won't have
14725 to abandon partially built circuits.
14726 - Handle changed router status correctly when dirserver reloads
14727 fingerprint file. We used to be dropping all unverified descriptors
14728 right then. The bug was hidden because we would immediately
14729 fetch a directory from another dirserver, which would include the
14730 descriptors we just dropped.
14731 - Revise tor-spec to add more/better stream end reasons.
14732 - Revise all calls to connection_edge_end to avoid sending 'misc',
14733 and to take errno into account where possible.
14734 - Client now retries when streams end early for 'hibernating' or
14735 'resource limit' reasons, rather than failing them.
14736 - Try to be more zealous about calling connection_edge_end when
14737 things go bad with edge conns in connection.c.
14739 o Robustness improvements:
14740 - Better handling for heterogeneous / unreliable nodes:
14741 - Annotate circuits with whether they aim to contain high uptime
14742 nodes and/or high capacity nodes. When building circuits, choose
14744 - This means that every single node in an intro rend circuit,
14745 not just the last one, will have a minimum uptime.
14746 - New config option LongLivedPorts to indicate application streams
14747 that will want high uptime circuits.
14748 - Servers reset uptime when a dir fetch entirely fails. This
14749 hopefully reflects stability of the server's network connectivity.
14750 - If somebody starts his tor server in Jan 2004 and then fixes his
14751 clock, don't make his published uptime be a year.
14752 - Reset published uptime when we wake up from hibernation.
14753 - Introduce a notion of 'internal' circs, which are chosen without
14754 regard to the exit policy of the last hop. Intro and rendezvous
14755 circs must be internal circs, to avoid leaking information. Resolve
14756 and connect streams can use internal circs if they want.
14757 - New circuit pooling algorithm: keep track of what destination ports
14758 we've used recently (start out assuming we'll want to use 80), and
14759 make sure to have enough circs around to satisfy these ports. Also
14760 make sure to have 2 internal circs around if we've required internal
14761 circs lately (and with high uptime if we've seen that lately too).
14762 - Turn addr_policy_compare from a tristate to a quadstate; this should
14763 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
14764 for google.com" problem.
14765 - When a client asks us for a dir mirror and we don't have one,
14766 launch an attempt to get a fresh one.
14767 - First cut at support for "create-fast" cells. Clients can use
14768 these when extending to their first hop, since the TLS already
14769 provides forward secrecy and authentication. Not enabled on
14772 o Reachability testing.
14773 - Your Tor server will automatically try to see if its ORPort and
14774 DirPort are reachable from the outside, and it won't upload its
14775 descriptor until it decides at least ORPort is reachable (when
14776 DirPort is not yet found reachable, publish it as zero).
14777 - When building testing circs for ORPort testing, use only
14778 high-bandwidth nodes, so fewer circuits fail.
14779 - Notice when our IP changes, and reset stats/uptime/reachability.
14780 - Authdirservers don't do ORPort reachability detection, since
14781 they're in clique mode, so it will be rare to find a server not
14782 already connected to them.
14783 - Authdirservers now automatically approve nodes running 0.1.0.2-rc
14787 - Now we allow two unverified servers with the same nickname
14788 but different keys. But if a nickname is verified, only that
14789 nickname+key are allowed.
14790 - If you're an authdirserver connecting to an address:port,
14791 and it's not the OR you were expecting, forget about that
14792 descriptor. If he *was* the one you were expecting, then forget
14793 about all other descriptors for that address:port.
14794 - Allow servers to publish descriptors from 12 hours in the future.
14795 Corollary: only whine about clock skew from the dirserver if
14796 he's a trusted dirserver (since now even verified servers could
14797 have quite wrong clocks).
14798 - Require servers that use the default dirservers to have public IP
14799 addresses. We have too many servers that are configured with private
14800 IPs and their admins never notice the log entries complaining that
14801 their descriptors are being rejected.
14803 o Efficiency improvements:
14804 - Use libevent. Now we can use faster async cores (like epoll, kpoll,
14805 and /dev/poll), and hopefully work better on Windows too.
14806 - Apple's OS X 10.4.0 ships with a broken kqueue API, and using
14807 kqueue on 10.3.9 causes kernel panics. Don't use kqueue on OS X.
14808 - Find libevent even if it's hiding in /usr/local/ and your
14809 CFLAGS and LDFLAGS don't tell you to look there.
14810 - Be able to link with libevent as a shared library (the default
14811 after 1.0d), even if it's hiding in /usr/local/lib and even
14812 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
14813 assuming you're running gcc. Otherwise fail and give a useful
14815 - Switch to a new buffer management algorithm, which tries to avoid
14816 reallocing and copying quite as much. In first tests it looks like
14817 it uses *more* memory on average, but less cpu.
14818 - Switch our internal buffers implementation to use a ring buffer,
14819 to hopefully improve performance for fast servers a lot.
14820 - Reenable the part of the code that tries to flush as soon as an
14821 OR outbuf has a full TLS record available. Perhaps this will make
14822 OR outbufs not grow as huge except in rare cases, thus saving lots
14823 of CPU time plus memory.
14824 - Improve performance for dirservers: stop re-parsing the whole
14825 directory every time you regenerate it.
14826 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
14827 it much faster to look up a circuit for each relay cell.
14828 - Remove most calls to assert_all_pending_dns_resolves_ok(),
14829 since they're eating our cpu on exit nodes.
14830 - Stop wasting time doing a case insensitive comparison for every
14831 dns name every time we do any lookup. Canonicalize the names to
14832 lowercase when you first see them.
14835 - Handle unavailable hidden services better. Handle slow or busy
14836 hidden services better.
14837 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
14838 circ as necessary, if there are any completed ones lying around
14839 when we try to launch one.
14840 - Make hidden services try to establish a rendezvous for 30 seconds
14841 after fetching the descriptor, rather than for n (where n=3)
14842 attempts to build a circuit.
14843 - Adjust maximum skew and age for rendezvous descriptors: let skew
14844 be 48 hours rather than 90 minutes.
14845 - Reject malformed .onion addresses rather then passing them on as
14846 normal web requests.
14849 - More Tor controller support. See
14850 http://tor.eff.org/doc/control-spec.txt for all the new features,
14851 including signals to emulate unix signals from any platform;
14852 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
14853 closestream; closecircuit; etc.
14854 - Encode hashed controller passwords in hex instead of base64,
14855 to make it easier to write controllers.
14856 - Revise control spec and implementation to allow all log messages to
14857 be sent to controller with their severities intact (suggested by
14858 Matt Edman). Disable debug-level logs while delivering a debug-level
14859 log to the controller, to prevent loop. Update TorControl to handle
14860 new log event types.
14862 o New config options/defaults:
14863 - Begin scrubbing sensitive strings from logs by default. Turn off
14864 the config option SafeLogging if you need to do debugging.
14865 - New exit policy: accept most low-numbered ports, rather than
14866 rejecting most low-numbered ports.
14867 - Put a note in the torrc about abuse potential with the default
14869 - Add support for CONNECTing through https proxies, with "HttpsProxy"
14871 - Add HttpProxyAuthenticator and HttpsProxyAuthenticator support
14872 based on patch from Adam Langley (basic auth only).
14873 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
14874 the fast servers that have been joining lately. (Clients are now
14875 willing to load balance over up to 2 MB of advertised bandwidth
14877 - New config option MaxAdvertisedBandwidth which lets you advertise
14878 a low bandwidthrate (to not attract as many circuits) while still
14879 allowing a higher bandwidthrate in reality.
14880 - Require BandwidthRate to be at least 20kB/s for servers.
14881 - Add a NoPublish config option, so you can be a server (e.g. for
14882 testing running Tor servers in other Tor networks) without
14883 publishing your descriptor to the primary dirservers.
14884 - Add a new AddressMap config directive to rewrite incoming socks
14885 addresses. This lets you, for example, declare an implicit
14886 required exit node for certain sites.
14887 - Add a new TrackHostExits config directive to trigger addressmaps
14888 for certain incoming socks addresses -- for sites that break when
14889 your exit keeps changing (based on patch from Mike Perry).
14890 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
14891 which describes how often we retry making new circuits if current
14892 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
14893 how long we're willing to make use of an already-dirty circuit.
14894 - Change compiled-in SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to
14895 a config option "ShutdownWaitLength" (when using kill -INT on
14897 - Fix an edge case in parsing config options: if they say "--"
14898 on the commandline, it's not a config option (thanks weasel).
14899 - New config option DirAllowPrivateAddresses for authdirservers.
14900 Now by default they refuse router descriptors that have non-IP or
14901 private-IP addresses.
14902 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
14903 smart" default value: low for servers and high for clients.
14904 - Some people were putting "Address " in their torrc, and they had
14905 a buggy resolver that resolved " " to 0.0.0.0. Oops.
14906 - If DataDir is ~/.tor, and that expands to /.tor, then default to
14907 LOCALSTATEDIR/tor instead.
14908 - Implement --verify-config command-line option to check if your torrc
14909 is valid without actually launching Tor.
14911 o Logging improvements:
14912 - When dirservers refuse a server descriptor, we now log its
14913 contactinfo, platform, and the poster's IP address.
14914 - Only warn once per nickname from add_nickname_list_to_smartlist()
14915 per failure, so an entrynode or exitnode choice that's down won't
14917 - When we're connecting to an OR and he's got a different nickname/key
14918 than we were expecting, only complain loudly if we're an OP or a
14919 dirserver. Complaining loudly to the OR admins just confuses them.
14920 - Whine at you if you're a server and you don't set your contactinfo.
14921 - Warn when exit policy implicitly allows local addresses.
14922 - Give a better warning when some other server advertises an
14923 ORPort that is actually an apache running ssl.
14924 - If we get an incredibly skewed timestamp from a dirserver mirror
14925 that isn't a verified OR, don't warn -- it's probably him that's
14927 - When a dirserver causes you to give a warn, mention which dirserver
14929 - Initialize libevent later in the startup process, so the logs are
14930 already established by the time we start logging libevent warns.
14931 - Use correct errno on win32 if libevent fails.
14932 - Check and warn about known-bad/slow libevent versions.
14933 - Stop warning about sigpipes in the logs. We're going to
14934 pretend that getting these occassionally is normal and fine.
14936 o New contrib scripts:
14937 - New experimental script tor/contrib/exitlist: a simple python
14938 script to parse directories and find Tor nodes that exit to listed
14940 - New experimental script tor/contrib/ExerciseServer.py (needs more
14941 work) that uses the controller interface to build circuits and
14942 fetch pages over them. This will help us bootstrap servers that
14943 have lots of capacity but haven't noticed it yet.
14944 - New experimental script tor/contrib/PathDemo.py (needs more work)
14945 that uses the controller interface to let you choose whole paths
14947 "<hostname>.<path,separated by dots>.<length of path>.path"
14948 - New contributed script "privoxy-tor-toggle" to toggle whether
14949 Privoxy uses Tor. Seems to be configured for Debian by default.
14950 - Have torctl.in/tor.sh.in check for location of su binary (needed
14954 - chdir() to your datadirectory at the *end* of the daemonize process,
14955 not the beginning. This was a problem because the first time you
14956 run tor, if your datadir isn't there, and you have runasdaemon set
14957 to 1, it will try to chdir to it before it tries to create it. Oops.
14958 - Fix several double-mark-for-close bugs, e.g. where we were finding
14959 a conn for a cell even if that conn is already marked for close.
14960 - Stop most cases of hanging up on a socks connection without sending
14962 - Fix a bug in the RPM package: set home directory for _tor to
14963 something more reasonable when first installing.
14964 - Stop putting nodename in the Platform string in server descriptors.
14965 It doesn't actually help, and it is confusing/upsetting some people.
14966 - When using preferred entry or exit nodes, ignore whether the
14967 circuit wants uptime or capacity. They asked for the nodes, they
14969 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
14970 artificially capped at 500kB.
14971 - Cache local dns resolves correctly even when they're .exit
14973 - If we're hibernating and we get a SIGINT, exit immediately.
14974 - tor-resolve requests were ignoring .exit if there was a working circuit
14975 they could use instead.
14976 - Pay more attention to the ClientOnly config option.
14977 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in certain
14978 installer screens; and don't put stuff into StartupItems unless
14979 the user asks you to.
14982 - Rewrite address "serifos.exit" to "externalIP.serifos.exit"
14983 rather than just rejecting it.
14984 - If our clock jumps forward by 100 seconds or more, assume something
14985 has gone wrong with our network and abandon all not-yet-used circs.
14986 - When an application is using socks5, give him the whole variety of
14987 potential socks5 responses (connect refused, host unreachable, etc),
14988 rather than just "success" or "failure".
14989 - A more sane version numbering system. See
14990 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
14991 - Change version parsing logic: a version is "obsolete" if it is not
14992 recommended and (1) there is a newer recommended version in the
14993 same series, or (2) there are no recommended versions in the same
14994 series, but there are some recommended versions in a newer series.
14995 A version is "new" if it is newer than any recommended version in
14997 - Report HTTP reasons to client when getting a response from directory
14998 servers -- so you can actually know what went wrong.
14999 - Reject odd-looking addresses at the client (e.g. addresses that
15000 contain a colon), rather than having the server drop them because
15002 - Stop publishing socksport in the directory, since it's not
15003 actually meant to be public. For compatibility, publish a 0 there
15005 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
15006 cookies to disk and doesn't log each web request to disk. (Thanks
15007 to Brett Carrington for pointing this out.)
15008 - Add OSX uninstall instructions. An actual uninstall script will
15010 - Add "opt hibernating 1" to server descriptor to make it clearer
15011 whether the server is hibernating.
15014 Changes in version 0.0.9.10 - 2005-06-16
15015 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
15016 - Refuse relay cells that claim to have a length larger than the
15017 maximum allowed. This prevents a potential attack that could read
15018 arbitrary memory (e.g. keys) from an exit server's process
15022 Changes in version 0.0.9.9 - 2005-04-23
15023 o Bugfixes on 0.0.9.x:
15024 - If unofficial Tor clients connect and send weird TLS certs, our
15025 Tor server triggers an assert. This release contains a minimal
15026 backport from the broader fix that we put into 0.1.0.4-rc.
15029 Changes in version 0.0.9.8 - 2005-04-07
15030 o Bugfixes on 0.0.9.x:
15031 - We have a bug that I haven't found yet. Sometimes, very rarely,
15032 cpuworkers get stuck in the 'busy' state, even though the cpuworker
15033 thinks of itself as idle. This meant that no new circuits ever got
15034 established. Here's a workaround to kill any cpuworker that's been
15035 busy for more than 100 seconds.
15038 Changes in version 0.0.9.7 - 2005-04-01
15039 o Bugfixes on 0.0.9.x:
15040 - Fix another race crash bug (thanks to Glenn Fink for reporting).
15041 - Compare identity to identity, not to nickname, when extending to
15042 a router not already in the directory. This was preventing us from
15043 extending to unknown routers. Oops.
15044 - Make sure to create OS X Tor user in <500 range, so we aren't
15045 creating actual system users.
15046 - Note where connection-that-hasn't-sent-end was marked, and fix
15047 a few really loud instances of this harmless bug (it's fixed more
15051 Changes in version 0.0.9.6 - 2005-03-24
15052 o Bugfixes on 0.0.9.x (crashes and asserts):
15053 - Add new end stream reasons to maintainance branch. Fix bug where
15054 reason (8) could trigger an assert. Prevent bug from recurring.
15055 - Apparently win32 stat wants paths to not end with a slash.
15056 - Fix assert triggers in assert_cpath_layer_ok(), where we were
15057 blowing away the circuit that conn->cpath_layer points to, then
15058 checking to see if the circ is well-formed. Backport check to make
15059 sure we dont use the cpath on a closed connection.
15060 - Prevent circuit_resume_edge_reading_helper() from trying to package
15061 inbufs for marked-for-close streams.
15062 - Don't crash on hup if your options->address has become unresolvable.
15063 - Some systems (like OS X) sometimes accept() a connection and tell
15064 you the remote host is 0.0.0.0:0. If this happens, due to some
15065 other mis-features, we get confused; so refuse the conn for now.
15067 o Bugfixes on 0.0.9.x (other):
15068 - Fix harmless but scary "Unrecognized content encoding" warn message.
15069 - Add new stream error reason: TORPROTOCOL reason means "you are not
15070 speaking a version of Tor I understand; say bye-bye to your stream."
15071 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
15072 into the future, now that we are more tolerant of skew. This
15073 resolves a bug where a Tor server would refuse to cache a directory
15074 because all the directories it gets are too far in the future;
15075 yet the Tor server never logs any complaints about clock skew.
15076 - Mac packaging magic: make man pages useable, and do not overwrite
15077 existing torrc files.
15078 - Make OS X log happily to /var/log/tor/tor.log
15081 Changes in version 0.0.9.5 - 2005-02-22
15082 o Bugfixes on 0.0.9.x:
15083 - Fix an assert race at exit nodes when resolve requests fail.
15084 - Stop picking unverified dir mirrors--it only leads to misery.
15085 - Patch from Matt Edman to make NT services work better. Service
15086 support is still not compiled into the executable by default.
15087 - Patch from Dmitri Bely so the Tor service runs better under
15088 the win32 SYSTEM account.
15089 - Make tor-resolve actually work (?) on Win32.
15090 - Fix a sign bug when getrlimit claims to have 4+ billion
15091 file descriptors available.
15092 - Stop refusing to start when bandwidthburst == bandwidthrate.
15093 - When create cells have been on the onion queue more than five
15094 seconds, just send back a destroy and take them off the list.
15097 Changes in version 0.0.9.4 - 2005-02-03
15098 o Bugfixes on 0.0.9:
15099 - Fix an assert bug that took down most of our servers: when
15100 a server claims to have 1 GB of bandwidthburst, don't
15102 - Don't crash as badly if we have spawned the max allowed number
15103 of dnsworkers, or we're out of file descriptors.
15104 - Block more file-sharing ports in the default exit policy.
15105 - MaxConn is now automatically set to the hard limit of max
15106 file descriptors we're allowed (ulimit -n), minus a few for
15108 - Give a clearer message when servers need to raise their
15109 ulimit -n when they start running out of file descriptors.
15110 - SGI Compatibility patches from Jan Schaumann.
15111 - Tolerate a corrupt cached directory better.
15112 - When a dirserver hasn't approved your server, list which one.
15113 - Go into soft hibernation after 95% of the bandwidth is used,
15114 not 99%. This is especially important for daily hibernators who
15115 have a small accounting max. Hopefully it will result in fewer
15116 cut connections when the hard hibernation starts.
15117 - Load-balance better when using servers that claim more than
15118 800kB/s of capacity.
15119 - Make NT services work (experimental, only used if compiled in).
15122 Changes in version 0.0.9.3 - 2005-01-21
15123 o Bugfixes on 0.0.9:
15124 - Backport the cpu use fixes from main branch, so busy servers won't
15125 need as much processor time.
15126 - Work better when we go offline and then come back, or when we
15127 run Tor at boot before the network is up. We do this by
15128 optimistically trying to fetch a new directory whenever an
15129 application request comes in and we think we're offline -- the
15130 human is hopefully a good measure of when the network is back.
15131 - Backport some minimal hidserv bugfixes: keep rend circuits open as
15132 long as you keep using them; actually publish hidserv descriptors
15133 shortly after they change, rather than waiting 20-40 minutes.
15134 - Enable Mac startup script by default.
15135 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
15136 - When you update AllowUnverifiedNodes or FirewallPorts via the
15137 controller's setconf feature, we were always appending, never
15139 - When you update HiddenServiceDir via setconf, it was screwing up
15140 the order of reading the lines, making it fail.
15141 - Do not rewrite a cached directory back to the cache; otherwise we
15142 will think it is recent and not fetch a newer one on startup.
15143 - Workaround for webservers that lie about Content-Encoding: Tor
15144 now tries to autodetect compressed directories and compression
15145 itself. This lets us Proxypass dir fetches through apache.
15148 Changes in version 0.0.9.2 - 2005-01-04
15149 o Bugfixes on 0.0.9 (crashes and asserts):
15150 - Fix an assert on startup when the disk is full and you're logging
15152 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
15153 style address, then we'd crash.
15154 - Fix an assert trigger when the running-routers string we get from
15155 a dirserver is broken.
15156 - Make worker threads start and run on win32. Now win32 servers
15158 - Bandaid (not actually fix, but now it doesn't crash) an assert
15159 where the dns worker dies mysteriously and the main Tor process
15160 doesn't remember anything about the address it was resolving.
15162 o Bugfixes on 0.0.9 (Win32):
15163 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
15164 name out of the warning/assert messages.
15165 - Fix a superficial "unhandled error on read" bug on win32.
15166 - The win32 installer no longer requires a click-through for our
15167 license, since our Free Software license grants rights but does not
15169 - Win32: When connecting to a dirserver fails, try another one
15170 immediately. (This was already working for non-win32 Tors.)
15171 - Stop trying to parse $HOME on win32 when hunting for default
15173 - Make tor-resolve.c work on win32 by calling network_init().
15175 o Bugfixes on 0.0.9 (other):
15176 - Make 0.0.9.x build on Solaris again.
15177 - Due to a fencepost error, we were blowing away the \n when reporting
15178 confvalue items in the controller. So asking for multiple config
15179 values at once couldn't work.
15180 - When listing circuits that are pending on an opening OR connection,
15181 if we're an OR we were listing circuits that *end* at us as
15182 being pending on every listener, dns/cpu worker, etc. Stop that.
15183 - Dirservers were failing to create 'running-routers' or 'directory'
15184 strings if we had more than some threshold of routers. Fix them so
15185 they can handle any number of routers.
15186 - Fix a superficial "Duplicate mark for close" bug.
15187 - Stop checking for clock skew for OR connections, even for servers.
15188 - Fix a fencepost error that was chopping off the last letter of any
15189 nickname that is the maximum allowed nickname length.
15190 - Update URLs in log messages so they point to the new website.
15191 - Fix a potential problem in mangling server private keys while
15192 writing to disk (not triggered yet, as far as we know).
15193 - Include the licenses for other free software we include in Tor,
15194 now that we're shipping binary distributions more regularly.
15197 Changes in version 0.0.9.1 - 2004-12-15
15198 o Bugfixes on 0.0.9:
15199 - Make hibernation actually work.
15200 - Make HashedControlPassword config option work.
15201 - When we're reporting event circuit status to a controller,
15202 don't use the stream status code.
15205 Changes in version 0.0.9 - 2004-12-12
15206 o Bugfixes on 0.0.8.1 (Crashes and asserts):
15207 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
15208 write() call will fail and we handle it there.
15209 - When we run out of disk space, or other log writing error, don't
15210 crash. Just stop logging to that log and continue.
15211 - Fix isspace() and friends so they still make Solaris happy
15212 but also so they don't trigger asserts on win32.
15213 - Fix assert failure on malformed socks4a requests.
15214 - Fix an assert bug where a hidden service provider would fail if
15215 the first hop of his rendezvous circuit was down.
15216 - Better handling of size_t vs int, so we're more robust on 64
15219 o Bugfixes on 0.0.8.1 (Win32):
15220 - Make windows sockets actually non-blocking (oops), and handle
15221 win32 socket errors better.
15222 - Fix parse_iso_time on platforms without strptime (eg win32).
15223 - win32: when being multithreaded, leave parent fdarray open.
15224 - Better handling of winsock includes on non-MSV win32 compilers.
15225 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
15227 - Make unit tests work on win32.
15229 o Bugfixes on 0.0.8.1 (Path selection and streams):
15230 - Calculate timeout for waiting for a connected cell from the time
15231 we sent the begin cell, not from the time the stream started. If
15232 it took a long time to establish the circuit, we would time out
15233 right after sending the begin cell.
15234 - Fix router_compare_addr_to_addr_policy: it was not treating a port
15235 of * as always matching, so we were picking reject *:* nodes as
15236 exit nodes too. Oops.
15237 - When read() failed on a stream, we would close it without sending
15238 back an end. So 'connection refused' would simply be ignored and
15239 the user would get no response.
15240 - Stop a sigpipe: when an 'end' cell races with eof from the app,
15241 we shouldn't hold-open-until-flush if the eof arrived first.
15242 - Let resolve conns retry/expire also, rather than sticking around
15244 - Fix more dns related bugs: send back resolve_failed and end cells
15245 more reliably when the resolve fails, rather than closing the
15246 circuit and then trying to send the cell. Also attach dummy resolve
15247 connections to a circuit *before* calling dns_resolve(), to fix
15248 a bug where cached answers would never be sent in RESOLVED cells.
15250 o Bugfixes on 0.0.8.1 (Circuits):
15251 - Finally fix a bug that's been plaguing us for a year:
15252 With high load, circuit package window was reaching 0. Whenever
15253 we got a circuit-level sendme, we were reading a lot on each
15254 socket, but only writing out a bit. So we would eventually reach
15255 eof. This would be noticed and acted on even when there were still
15256 bytes sitting in the inbuf.
15257 - Use identity comparison, not nickname comparison, to choose which
15258 half of circuit-ID-space each side gets to use. This is needed
15259 because sometimes we think of a router as a nickname, and sometimes
15260 as a hex ID, and we can't predict what the other side will do.
15262 o Bugfixes on 0.0.8.1 (Other):
15263 - Fix a whole slew of memory leaks.
15264 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
15265 - If we are using select, make sure we stay within FD_SETSIZE.
15266 - When poll() is interrupted, we shouldn't believe the revents values.
15267 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
15268 and smartlist_len, which are two major profiling offenders.
15269 - If do_hup fails, actually notice.
15270 - Flush the log file descriptor after we print "Tor opening log file",
15271 so we don't see those messages days later.
15272 - Hidden service operators now correctly handle version 1 style
15273 INTRODUCE1 cells (nobody generates them still, so not a critical
15275 - Handle more errnos from accept() without closing the listener.
15276 Some OpenBSD machines were closing their listeners because
15277 they ran out of file descriptors.
15278 - Some people had wrapped their tor client/server in a script
15279 that would restart it whenever it died. This did not play well
15280 with our "shut down if your version is obsolete" code. Now people
15281 don't fetch a new directory if their local cached version is
15283 - Make our autogen.sh work on ksh as well as bash.
15284 - Better torrc example lines for dirbindaddress and orbindaddress.
15285 - Improved bounds checking on parsed ints (e.g. config options and
15286 the ones we find in directories.)
15287 - Stop using separate defaults for no-config-file and
15288 empty-config-file. Now you have to explicitly turn off SocksPort,
15289 if you don't want it open.
15290 - We were starting to daemonize before we opened our logs, so if
15291 there were any problems opening logs, we would complain to stderr,
15292 which wouldn't work, and then mysteriously exit.
15293 - If a verified OR connects to us before he's uploaded his descriptor,
15294 or we verify him and hup but he still has the original TLS
15295 connection, then conn->nickname is still set like he's unverified.
15297 o Code security improvements, inspired by Ilja:
15298 - tor_snprintf wrapper over snprintf with consistent (though not C99)
15300 - Replace sprintf with tor_snprintf. (I think they were all safe, but
15302 - Replace strcpy/strncpy with strlcpy in more places.
15303 - Avoid strcat; use tor_snprintf or strlcat instead.
15305 o Features (circuits and streams):
15306 - New circuit building strategy: keep a list of ports that we've
15307 used in the past 6 hours, and always try to have 2 circuits open
15308 or on the way that will handle each such port. Seed us with port
15309 80 so web users won't complain that Tor is "slow to start up".
15310 - Make kill -USR1 dump more useful stats about circuits.
15311 - When warning about retrying or giving up, print the address, so
15312 the user knows which one it's talking about.
15313 - If you haven't used a clean circuit in an hour, throw it away,
15314 just to be on the safe side. (This means after 6 hours a totally
15315 unused Tor client will have no circuits open.)
15316 - Support "foo.nickname.exit" addresses, to let Alice request the
15317 address "foo" as viewed by exit node "nickname". Based on a patch
15318 from Geoff Goodell.
15319 - If your requested entry or exit node has advertised bandwidth 0,
15321 - Be more greedy about filling up relay cells -- we try reading again
15322 once we've processed the stuff we read, in case enough has arrived
15323 to fill the last cell completely.
15324 - Refuse application socks connections to port 0.
15325 - Use only 0.0.9pre1 and later servers for resolve cells.
15327 o Features (bandwidth):
15328 - Hibernation: New config option "AccountingMax" lets you
15329 set how many bytes per month (in each direction) you want to
15330 allow your server to consume. Rather than spreading those
15331 bytes out evenly over the month, we instead hibernate for some
15332 of the month and pop up at a deterministic time, work until
15333 the bytes are consumed, then hibernate again. Config option
15334 "MonthlyAccountingStart" lets you specify which day of the month
15335 your billing cycle starts on.
15336 - Implement weekly/monthly/daily accounting: now you specify your
15337 hibernation properties by
15338 AccountingMax N bytes|KB|MB|GB|TB
15339 AccountingStart day|week|month [day] HH:MM
15340 Defaults to "month 1 0:00".
15341 - Let bandwidth and interval config options be specified as 5 bytes,
15342 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
15344 o Features (directories):
15345 - New "router-status" line in directory, to better bind each verified
15346 nickname to its identity key.
15347 - Clients can ask dirservers for /dir.z to get a compressed version
15348 of the directory. Only works for servers running 0.0.9, of course.
15349 - Make clients cache directories and use them to seed their router
15350 lists at startup. This means clients have a datadir again.
15351 - Respond to content-encoding headers by trying to uncompress as
15353 - Clients and servers now fetch running-routers; cache
15354 running-routers; compress running-routers; serve compressed
15356 - Make moria2 advertise a dirport of 80, so people behind firewalls
15357 will be able to get a directory.
15358 - Http proxy support
15359 - Dirservers translate requests for http://%s:%d/x to /x
15360 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
15361 be routed through this host.
15362 - Clients ask for /tor/x rather than /x for new enough dirservers.
15363 This way we can one day coexist peacefully with apache.
15364 - Clients specify a "Host: %s%d" http header, to be compatible
15365 with more proxies, and so running squid on an exit node can work.
15366 - Protect dirservers from overzealous descriptor uploading -- wait
15367 10 seconds after directory gets dirty, before regenerating.
15369 o Features (packages and install):
15370 - Add NSI installer contributed by J Doe.
15371 - Apply NT service patch from Osamu Fujino. Still needs more work.
15372 - Commit VC6 and VC7 workspace/project files.
15373 - Commit a tor.spec for making RPM files, with help from jbash.
15374 - Add contrib/torctl.in contributed by Glenn Fink.
15375 - Make expand_filename handle ~ and ~username.
15376 - Use autoconf to enable largefile support where necessary. Use
15377 ftello where available, since ftell can fail at 2GB.
15378 - Ship src/win32/ in the tarball, so people can use it to build.
15379 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
15382 o Features (ui controller):
15383 - Control interface: a separate program can now talk to your
15384 client/server over a socket, and get/set config options, receive
15385 notifications of circuits and streams starting/finishing/dying,
15386 bandwidth used, etc. The next step is to get some GUIs working.
15387 Let us know if you want to help out. See doc/control-spec.txt .
15388 - Ship a contrib/tor-control.py as an example script to interact
15389 with the control port.
15390 - "tor --hash-password zzyxz" will output a salted password for
15391 use in authenticating to the control interface.
15392 - Implement the control-spec's SAVECONF command, to write your
15393 configuration to torrc.
15394 - Get cookie authentication for the controller closer to working.
15395 - When set_conf changes our server descriptor, upload a new copy.
15396 But don't upload it too often if there are frequent changes.
15398 o Features (config and command-line):
15399 - Deprecate unofficial config option abbreviations, and abbreviations
15400 not on the command line.
15401 - Configuration infrastructure support for warning on obsolete
15403 - Give a slightly more useful output for "tor -h".
15404 - Break DirFetchPostPeriod into:
15405 - DirFetchPeriod for fetching full directory,
15406 - StatusFetchPeriod for fetching running-routers,
15407 - DirPostPeriod for posting server descriptor,
15408 - RendPostPeriod for posting hidden service descriptors.
15409 - New log format in config:
15410 "Log minsev[-maxsev] stdout|stderr|syslog" or
15411 "Log minsev[-maxsev] file /var/foo"
15412 - DirPolicy config option, to let people reject incoming addresses
15413 from their dirserver.
15414 - "tor --list-fingerprint" will list your identity key fingerprint
15416 - Make tor --version --version dump the cvs Id of every file.
15417 - New 'MyFamily nick1,...' config option for a server to
15418 specify other servers that shouldn't be used in the same circuit
15419 with it. Only believed if nick1 also specifies us.
15420 - New 'NodeFamily nick1,nick2,...' config option for a client to
15421 specify nodes that it doesn't want to use in the same circuit.
15422 - New 'Redirectexit pattern address:port' config option for a
15423 server to redirect exit connections, e.g. to a local squid.
15424 - Add "pass" target for RedirectExit, to make it easier to break
15425 out of a sequence of RedirectExit rules.
15426 - Make the dirservers file obsolete.
15427 - Include a dir-signing-key token in directories to tell the
15428 parsing entity which key is being used to sign.
15429 - Remove the built-in bulky default dirservers string.
15430 - New config option "Dirserver %s:%d [fingerprint]", which can be
15431 repeated as many times as needed. If no dirservers specified,
15432 default to moria1,moria2,tor26.
15433 - Make 'Routerfile' config option obsolete.
15434 - Discourage people from setting their dirfetchpostperiod more often
15435 than once per minute.
15437 o Features (other):
15438 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
15439 get back to normal.)
15440 - Accept *:706 (silc) in default exit policy.
15441 - Implement new versioning format for post 0.1.
15442 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
15443 log more informatively.
15444 - Check clock skew for verified servers, but allow unverified
15445 servers and clients to have any clock skew.
15446 - Make sure the hidden service descriptors are at a random offset
15447 from each other, to hinder linkability.
15448 - Clients now generate a TLS cert too, in preparation for having
15449 them act more like real nodes.
15450 - Add a pure-C tor-resolve implementation.
15451 - Use getrlimit and friends to ensure we can reach MaxConn (currently
15452 1024) file descriptors.
15453 - Raise the max dns workers from 50 to 100.
15456 Changes in version 0.0.8.1 - 2004-10-13
15458 - Fix a seg fault that can be triggered remotely for Tor
15459 clients/servers with an open dirport.
15460 - Fix a rare assert trigger, where routerinfos for entries in
15461 our cpath would expire while we're building the path.
15462 - Fix a bug in OutboundBindAddress so it (hopefully) works.
15463 - Fix a rare seg fault for people running hidden services on
15464 intermittent connections.
15465 - Fix a bug in parsing opt keywords with objects.
15466 - Fix a stale pointer assert bug when a stream detaches and
15468 - Fix a string format vulnerability (probably not exploitable)
15469 in reporting stats locally.
15470 - Fix an assert trigger: sometimes launching circuits can fail
15471 immediately, e.g. because too many circuits have failed recently.
15472 - Fix a compile warning on 64 bit platforms.
15475 Changes in version 0.0.8 - 2004-08-25
15477 - Made our unit tests compile again on OpenBSD 3.5, and tor
15478 itself compile again on OpenBSD on a sparc64.
15479 - We were neglecting milliseconds when logging on win32, so
15480 everything appeared to happen at the beginning of each second.
15481 - Check directory signature _before_ you decide whether you're
15482 you're running an obsolete version and should exit.
15483 - Check directory signature _before_ you parse the running-routers
15484 list to decide who's running.
15485 - Check return value of fclose while writing to disk, so we don't
15486 end up with broken files when servers run out of disk space.
15487 - Port it to SunOS 5.9 / Athena
15488 - Fix two bugs in saving onion keys to disk when rotating, so
15489 hopefully we'll get fewer people using old onion keys.
15490 - Remove our mostly unused -- and broken -- hex_encode()
15491 function. Use base16_encode() instead. (Thanks to Timo Lindfors
15492 for pointing out this bug.)
15493 - Only pick and establish intro points after we've gotten a
15495 - Fix assert triggers: if the other side returns an address 0.0.0.0,
15496 don't put it into the client dns cache.
15497 - If a begin failed due to exit policy, but we believe the IP
15498 address should have been allowed, switch that router to exitpolicy
15499 reject *:* until we get our next directory.
15501 o Protocol changes:
15502 - 'Extend' relay cell payloads now include the digest of the
15503 intended next hop's identity key. Now we can verify that we're
15504 extending to the right router, and also extend to routers we
15505 hadn't heard of before.
15508 - Tor nodes can now act as relays (with an advertised ORPort)
15509 without being manually verified by the dirserver operators.
15510 - Uploaded descriptors of unverified routers are now accepted
15511 by the dirservers, and included in the directory.
15512 - Verified routers are listed by nickname in the running-routers
15513 list; unverified routers are listed as "$<fingerprint>".
15514 - We now use hash-of-identity-key in most places rather than
15515 nickname or addr:port, for improved security/flexibility.
15516 - AllowUnverifiedNodes config option to let circuits choose no-name
15517 routers in entry,middle,exit,introduction,rendezvous positions.
15518 Allow middle and rendezvous positions by default.
15519 - When picking unverified routers, skip those with low uptime and/or
15520 low bandwidth, depending on what properties you care about.
15521 - ClientOnly option for nodes that never want to become servers.
15522 - Directory caching.
15523 - "AuthoritativeDir 1" option for the official dirservers.
15524 - Now other nodes (clients and servers) will cache the latest
15525 directory they've pulled down.
15526 - They can enable their DirPort to serve it to others.
15527 - Clients will pull down a directory from any node with an open
15528 DirPort, and check the signature/timestamp correctly.
15529 - Authoritative dirservers now fetch directories from other
15530 authdirservers, to stay better synced.
15531 - Running-routers list tells who's down also, along with noting
15532 if they're verified (listed by nickname) or unverified (listed
15534 - Allow dirservers to serve running-router list separately.
15535 This isn't used yet.
15536 - You can now fetch $DIRURL/running-routers to get just the
15537 running-routers line, not the whole descriptor list. (But
15538 clients don't use this yet.)
15539 - Clients choose nodes proportional to advertised bandwidth.
15540 - Clients avoid using nodes with low uptime as introduction points.
15541 - Handle servers with dynamic IP addresses: don't just replace
15542 options->Address with the resolved one at startup, and
15543 detect our address right before we make a routerinfo each time.
15544 - 'FascistFirewall' option to pick dirservers and ORs on specific
15545 ports; plus 'FirewallPorts' config option to tell FascistFirewall
15546 which ports are open. (Defaults to 80,443)
15547 - Try other dirservers immediately if the one you try is down. This
15548 should tolerate down dirservers better now.
15549 - ORs connect-on-demand to other ORs
15550 - If you get an extend cell to an OR you're not connected to,
15551 connect, handshake, and forward the create cell.
15552 - The authoritative dirservers stay connected to everybody,
15553 and everybody stays connected to 0.0.7 servers, but otherwise
15554 clients/servers expire unused connections after 5 minutes.
15555 - When servers get a sigint, they delay 30 seconds (refusing new
15556 connections) then exit. A second sigint causes immediate exit.
15557 - File and name management:
15558 - Look for .torrc if no CONFDIR "torrc" is found.
15559 - If no datadir is defined, then choose, make, and secure ~/.tor
15561 - If torrc not found, exitpolicy reject *:*.
15562 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
15563 - If no nickname is defined, derive default from hostname.
15564 - Rename secret key files, e.g. identity.key -> secret_id_key,
15565 to discourage people from mailing their identity key to tor-ops.
15566 - Refuse to build a circuit before the directory has arrived --
15567 it won't work anyway, since you won't know the right onion keys
15569 - Parse tor version numbers so we can do an is-newer-than check
15570 rather than an is-in-the-list check.
15571 - New socks command 'resolve', to let us shim gethostbyname()
15573 - A 'tor_resolve' script to access the socks resolve functionality.
15574 - A new socks-extensions.txt doc file to describe our
15575 interpretation and extensions to the socks protocols.
15576 - Add a ContactInfo option, which gets published in descriptor.
15577 - Write tor version at the top of each log file
15578 - New docs in the tarball:
15580 - Document that you should proxy your SSL traffic too.
15581 - Log a warning if the user uses an unsafe socks variant, so people
15582 are more likely to learn about privoxy or socat.
15583 - Log a warning if you're running an unverified server, to let you
15584 know you might want to get it verified.
15585 - Change the default exit policy to reject the default edonkey,
15586 kazaa, gnutella ports.
15587 - Add replace_file() to util.[ch] to handle win32's rename().
15588 - Publish OR uptime in descriptor (and thus in directory) too.
15589 - Remember used bandwidth (both in and out), and publish 15-minute
15590 snapshots for the past day into our descriptor.
15591 - Be more aggressive about trying to make circuits when the network
15592 has changed (e.g. when you unsuspend your laptop).
15593 - Check for time skew on http headers; report date in response to
15595 - If the entrynode config line has only one node, don't pick it as
15597 - Add strict{entry|exit}nodes config options. If set to 1, then
15598 we refuse to build circuits that don't include the specified entry
15600 - OutboundBindAddress config option, to bind to a specific
15601 IP address for outgoing connect()s.
15602 - End truncated log entries (e.g. directories) with "[truncated]".
15605 Changes in version 0.0.7.3 - 2004-08-12
15606 o Stop dnsworkers from triggering an assert failure when you
15607 ask them to resolve the host "".
15610 Changes in version 0.0.7.2 - 2004-07-07
15611 o A better fix for the 0.0.0.0 problem, that will hopefully
15612 eliminate the remaining related assertion failures.
15615 Changes in version 0.0.7.1 - 2004-07-04
15616 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
15617 since internally we use 0.0.0.0 to signify "not yet resolved".
15620 Changes in version 0.0.7 - 2004-06-07
15621 o Fixes for crashes and other obnoxious bugs:
15622 - Fix an epipe bug: sometimes when directory connections failed
15623 to connect, we would give them a chance to flush before closing
15625 - When we detached from a circuit because of resolvefailed, we
15626 would immediately try the same circuit twice more, and then
15627 give up on the resolve thinking we'd tried three different
15629 - Limit the number of intro circuits we'll attempt to build for a
15630 hidden service per 15-minute period.
15631 - Check recommended-software string *early*, before actually parsing
15632 the directory. Thus we can detect an obsolete version and exit,
15633 even if the new directory format doesn't parse.
15634 o Fixes for security bugs:
15635 - Remember which nodes are dirservers when you startup, and if a
15636 random OR enables his dirport, don't automatically assume he's
15637 a trusted dirserver.
15639 - Directory connections were asking the wrong poll socket to
15640 start writing, and not asking themselves to start writing.
15641 - When we detached from a circuit because we sent a begin but
15642 didn't get a connected, we would use it again the first time;
15643 but after that we would correctly switch to a different one.
15644 - Stop warning when the first onion decrypt attempt fails; they
15645 will sometimes legitimately fail now that we rotate keys.
15646 - Override unaligned-access-ok check when $host_cpu is ia64 or
15647 arm. Apparently they allow it but the kernel whines.
15648 - Dirservers try to reconnect periodically too, in case connections
15650 - Fix some memory leaks in directory servers.
15651 - Allow backslash in Win32 filenames.
15652 - Made Tor build complain-free on FreeBSD, hopefully without
15653 breaking other BSD builds. We'll see.
15654 - Check directory signatures based on name of signer, not on whom
15655 we got the directory from. This will let us cache directories more
15657 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
15660 - Doxygen markup on all functions and global variables.
15661 - Make directory functions update routerlist, not replace it. So
15662 now directory disagreements are not so critical a problem.
15663 - Remove the upper limit on number of descriptors in a dirserver's
15664 directory (not that we were anywhere close).
15665 - Allow multiple logfiles at different severity ranges.
15666 - Allow *BindAddress to specify ":port" rather than setting *Port
15667 separately. Allow multiple instances of each BindAddress config
15668 option, so you can bind to multiple interfaces if you want.
15669 - Allow multiple exit policy lines, which are processed in order.
15670 Now we don't need that huge line with all the commas in it.
15671 - Enable accept/reject policies on SOCKS connections, so you can bind
15672 to 0.0.0.0 but still control who can use your OP.
15673 - Updated the man page to reflect these features.
15676 Changes in version 0.0.6.2 - 2004-05-16
15677 o Our integrity-checking digest was checking only the most recent cell,
15678 not the previous cells like we'd thought.
15679 Thanks to Stefan Mark for finding the flaw!
15682 Changes in version 0.0.6.1 - 2004-05-06
15683 o Fix two bugs in our AES counter-mode implementation (this affected
15684 onion-level stream encryption, but not TLS-level). It turns
15685 out we were doing something much more akin to a 16-character
15686 polyalphabetic cipher. Oops.
15687 Thanks to Stefan Mark for finding the flaw!
15688 o Retire moria3 as a directory server, and add tor26 as a directory
15692 Changes in version 0.0.6 - 2004-05-02
15694 - Hidden services and rendezvous points are implemented. Go to
15695 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
15696 hidden services. (This only works via a socks4a proxy such as
15697 Privoxy, and currently it's quite slow.)
15698 - We now rotate link (tls context) keys and onion keys.
15699 - CREATE cells now include oaep padding, so you can tell
15700 if you decrypted them correctly.
15701 - Retry stream correctly when we fail to connect because of
15702 exit-policy-reject (should try another) or can't-resolve-address.
15703 - When we hup a dirserver and we've *removed* a server from the
15704 approved-routers list, now we remove that server from the
15705 in-memory directories too.
15706 - Add bandwidthburst to server descriptor.
15707 - Directories now say which dirserver signed them.
15708 - Use a tor_assert macro that logs failed assertions too.
15709 - Since we don't support truncateds much, don't bother sending them;
15710 just close the circ.
15711 - Fetch randomness from /dev/urandom better (not via fopen/fread)
15712 - Better debugging for tls errors
15713 - Set Content-Type on the directory and hidserv descriptor.
15714 - Remove IVs from cipher code, since AES-ctr has none.
15716 - Fix an assert trigger for exit nodes that's been plaguing us since
15717 the days of 0.0.2prexx (thanks weasel!)
15718 - Fix a bug where we were closing tls connections intermittently.
15719 It turns out openssl keeps its errors around -- so if an error
15720 happens, and you don't ask about it, and then another openssl
15721 operation happens and succeeds, and you ask if there was an error,
15722 it tells you about the first error.
15723 - Fix a bug that's been lurking since 27 may 03 (!)
15724 When passing back a destroy cell, we would use the wrong circ id.
15725 - Don't crash if a conn that sent a begin has suddenly lost its circuit.
15726 - Some versions of openssl have an SSL_pending function that erroneously
15727 returns bytes when there is a non-application record pending.
15728 - Win32 fixes. Tor now compiles on win32 with no warnings/errors.
15729 o We were using an array of length zero in a few places.
15730 o Win32's gethostbyname can't resolve an IP to an IP.
15731 o Win32's close can't close a socket.
15732 o Handle windows socket errors correctly.
15734 - check for <sys/limits.h> so we build on FreeBSD again, and
15735 <machine/limits.h> for NetBSD.
15738 Changes in version 0.0.5 - 2004-03-30
15739 o Install torrc as torrc.sample -- we no longer clobber your
15741 o Fix mangled-state bug in directory fetching (was causing sigpipes).
15742 o Only build circuits after we've fetched the directory: clients were
15743 using only the directory servers before they'd fetched a directory.
15744 This also means longer startup time; so it goes.
15745 o Fix an assert trigger where an OP would fail to handshake, and we'd
15746 expect it to have a nickname.
15747 o Work around a tsocks bug: do a socks reject when AP connection dies
15748 early, else tsocks goes into an infinite loop.
15749 o Hold socks connection open until reply is flushed (if possible)
15750 o Make exit nodes resolve IPs to IPs immediately, rather than asking
15751 the dns farm to do it.
15752 o Fix c99 aliasing warnings in rephist.c
15753 o Don't include server descriptors that are older than 24 hours in the
15755 o Give socks 'reject' replies their whole 15s to attempt to flush,
15756 rather than seeing the 60s timeout and assuming the flush had failed.
15757 o Clean automake droppings from the cvs repository
15758 o Add in a 'notice' log level for things the operator should hear
15759 but that aren't warnings
15762 Changes in version 0.0.4 - 2004-03-26
15763 o When connecting to a dirserver or OR and the network is down,
15767 Changes in version 0.0.3 - 2004-03-26
15768 o Warn and fail if server chose a nickname with illegal characters
15769 o Port to Solaris and Sparc:
15770 - include missing header fcntl.h
15771 - have autoconf find -lsocket -lnsl automatically
15772 - deal with hardware word alignment
15773 - make uname() work (solaris has a different return convention)
15774 - switch from using signal() to sigaction()
15775 o Preliminary work on reputation system:
15776 - Keep statistics on success/fail of connect attempts; they're published
15777 by kill -USR1 currently.
15778 - Add a RunTesting option to try to learn link state by creating test
15779 circuits, even when SocksPort is off.
15780 - Remove unused open circuits when there are too many.
15783 Changes in version 0.0.2 - 2004-03-19
15784 - Include strlcpy and strlcat for safer string ops
15785 - define INADDR_NONE so we compile (but still not run) on solaris
15788 Changes in version 0.0.2pre27 - 2004-03-14
15790 - Allow internal tor networks (we were rejecting internal IPs,
15791 now we allow them if they're set explicitly).
15792 - And fix a few endian issues.
15795 Changes in version 0.0.2pre26 - 2004-03-14
15797 - If a stream times out after 15s without a connected cell, don't
15798 try that circuit again: try a new one.
15799 - Retry streams at most 4 times. Then give up.
15800 - When a dirserver gets a descriptor from an unknown router, it
15801 logs its fingerprint (so the dirserver operator can choose to
15802 accept it even without mail from the server operator).
15803 - Inform unapproved servers when we reject their descriptors.
15804 - Make tor build on Windows again. It works as a client, who knows
15806 - Clearer instructions in the torrc for how to set up a server.
15807 - Be more efficient about reading fd's when our global token bucket
15808 (used for rate limiting) becomes empty.
15810 - Stop asserting that computers always go forward in time. It's
15812 - When we sent a cell (e.g. destroy) and then marked an OR connection
15813 expired, we might close it before finishing a flush if the other
15814 side isn't reading right then.
15815 - Don't allow dirservers to start if they haven't defined
15816 RecommendedVersions
15817 - We were caching transient dns failures. Oops.
15818 - Prevent servers from publishing an internal IP as their address.
15819 - Address a strcat vulnerability in circuit.c
15822 Changes in version 0.0.2pre25 - 2004-03-04
15824 - Put the OR's IP in its router descriptor, not its fqdn. That way
15825 we'll stop being stalled by gethostbyname for nodes with flaky dns,
15828 - If the user typed in an address that didn't resolve, the server
15832 Changes in version 0.0.2pre24 - 2004-03-03
15834 - Fix an assertion failure in dns.c, where we were trying to dequeue
15835 a pending dns resolve even if it wasn't pending
15836 - Fix a spurious socks5 warning about still trying to write after the
15837 connection is finished.
15838 - Hold certain marked_for_close connections open until they're finished
15839 flushing, rather than losing bytes by closing them too early.
15840 - Correctly report the reason for ending a stream
15841 - Remove some duplicate calls to connection_mark_for_close
15842 - Put switch_id and start_daemon earlier in the boot sequence, so it
15843 will actually try to chdir() to options.DataDirectory
15844 - Make 'make test' exit(1) if a test fails; fix some unit tests
15845 - Make tor fail when you use a config option it doesn't know about,
15846 rather than warn and continue.
15847 - Make --version work
15848 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
15851 Changes in version 0.0.2pre23 - 2004-02-29
15853 - Print a statement when the first circ is finished, so the user
15854 knows it's working.
15855 - If a relay cell is unrecognized at the end of the circuit,
15856 send back a destroy. (So attacks to mutate cells are more
15858 - New config option 'excludenodes' to avoid certain nodes for circuits.
15859 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
15860 so you can collect coredumps there.
15862 - Fix a bug in tls flushing where sometimes data got wedged and
15863 didn't flush until more data got sent. Hopefully this bug was
15864 a big factor in the random delays we were seeing.
15865 - Make 'connected' cells include the resolved IP, so the client
15866 dns cache actually gets populated.
15867 - Disallow changing from ORPort=0 to ORPort>0 on hup.
15868 - When we time-out on a stream and detach from the circuit, send an
15869 end cell down it first.
15870 - Only warn about an unknown router (in exitnodes, entrynodes,
15871 excludenodes) after we've fetched a directory.
15874 Changes in version 0.0.2pre22 - 2004-02-26
15876 - Servers publish less revealing uname information in descriptors.
15877 - More memory tracking and assertions, to crash more usefully when
15879 - If the default torrc isn't there, just use some default defaults.
15880 Plus provide an internal dirservers file if they don't have one.
15881 - When the user tries to use Tor as an http proxy, give them an http
15882 501 failure explaining that we're a socks proxy.
15883 - Dump a new router.desc on hup, to help confused people who change
15884 their exit policies and then wonder why router.desc doesn't reflect
15886 - Clean up the generic tor.sh init script that we ship with.
15888 - If the exit stream is pending on the resolve, and a destroy arrives,
15889 then the stream wasn't getting removed from the pending list. I
15890 think this was the one causing recent server crashes.
15891 - Use a more robust poll on OSX 10.3, since their poll is flaky.
15892 - When it couldn't resolve any dirservers, it was useless from then on.
15893 Now it reloads the RouterFile (or default dirservers) if it has no
15895 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
15896 many users don't even *have* a /usr/local/sbin/.
15899 Changes in version 0.0.2pre21 - 2004-02-18
15901 - There's a ChangeLog file that actually reflects the changelog.
15902 - There's a 'torify' wrapper script, with an accompanying
15903 tor-tsocks.conf, that simplifies the process of using tsocks for
15904 tor. It even has a man page.
15905 - The tor binary gets installed to sbin rather than bin now.
15906 - Retry streams where the connected cell hasn't arrived in 15 seconds
15907 - Clean up exit policy handling -- get the default out of the torrc,
15908 so we can update it without forcing each server operator to fix
15910 - Allow imaps and pop3s in default exit policy
15912 - Prevent picking middleman nodes as the last node in the circuit
15915 Changes in version 0.0.2pre20 - 2004-01-30
15917 - We now have a deb package, and it's in debian unstable. Go to
15918 it, apt-getters. :)
15919 - I've split the TotalBandwidth option into BandwidthRate (how many
15920 bytes per second you want to allow, long-term) and
15921 BandwidthBurst (how many bytes you will allow at once before the cap
15922 kicks in). This better token bucket approach lets you, say, set
15923 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
15924 performance while not exceeding your monthly bandwidth quota.
15925 - Push out a tls record's worth of data once you've got it, rather
15926 than waiting until you've read everything waiting to be read. This
15927 may improve performance by pipelining better. We'll see.
15928 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
15929 from failed circuits (if they haven't been connected yet) and attach
15931 - Expire old streams that haven't managed to connect. Some day we'll
15932 have them reattach to new circuits instead.
15935 - Fix several memory leaks that were causing servers to become bloated
15937 - Fix a few very rare assert triggers. A few more remain.
15938 - Setuid to User _before_ complaining about running as root.
15941 Changes in version 0.0.2pre19 - 2004-01-07
15943 - Fix deadlock condition in dns farm. We were telling a child to die by
15944 closing the parent's file descriptor to him. But newer children were
15945 inheriting the open file descriptor from the parent, and since they
15946 weren't closing it, the socket never closed, so the child never read
15947 eof, so he never knew to exit. Similarly, dns workers were holding
15948 open other sockets, leading to all sorts of chaos.
15949 - New cleaner daemon() code for forking and backgrounding.
15950 - If you log to a file, it now prints an entry at the top of the
15951 logfile so you know it's working.
15952 - The onionskin challenge length was 30 bytes longer than necessary.
15953 - Started to patch up the spec so it's not quite so out of date.
15956 Changes in version 0.0.2pre18 - 2004-01-02
15958 - Fix endian issues with the 'integrity' field in the relay header.
15959 - Fix a potential bug where connections in state
15960 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
15963 Changes in version 0.0.2pre17 - 2003-12-30
15965 - Made --debuglogfile (or any second log file, actually) work.
15966 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
15967 adversary could force us into an infinite loop.
15970 - Each onionskin handshake now includes a hash of the computed key,
15971 to prove the server's identity and help perfect forward secrecy.
15972 - Changed cell size from 256 to 512 bytes (working toward compatibility
15974 - Changed cell length to 2 bytes, and moved it to the relay header.
15975 - Implemented end-to-end integrity checking for the payloads of
15977 - Separated streamid from 'recognized' (otherwise circuits will get
15978 messed up when we try to have streams exit from the middle). We
15979 use the integrity-checking to confirm that a cell is addressed to
15981 - Randomize the initial circid and streamid values, so an adversary who
15982 breaks into a node can't learn how many circuits or streams have
15986 Changes in version 0.0.2pre16 - 2003-12-14
15988 - Fixed a bug that made HUP trigger an assert
15989 - Fixed a bug where a circuit that immediately failed wasn't being
15990 counted as a failed circuit in counting retries.
15993 - Now we close the circuit when we get a truncated cell: otherwise we're
15994 open to an anonymity attack where a bad node in the path truncates
15995 the circuit and then we open streams at him.
15996 - Add port ranges to exit policies
15997 - Add a conservative default exit policy
15998 - Warn if you're running tor as root
15999 - on HUP, retry OR connections and close/rebind listeners
16000 - options.EntryNodes: try these nodes first when picking the first node
16001 - options.ExitNodes: if your best choices happen to include any of
16002 your preferred exit nodes, you choose among just those preferred
16004 - options.ExcludedNodes: nodes that are never picked in path building
16007 Changes in version 0.0.2pre15 - 2003-12-03
16008 o Robustness and bugfixes:
16009 - Sometimes clients would cache incorrect DNS resolves, which would
16010 really screw things up.
16011 - An OP that goes offline would slowly leak all its sockets and stop
16013 - A wide variety of bugfixes in exit node selection, exit policy
16014 handling, and processing pending streams when a new circuit is
16016 - Pick nodes for a path only from those the directory says are up
16017 - Choose randomly from all running dirservers, not always the first one
16018 - Increase allowed http header size for directory fetch.
16019 - Stop writing to stderr (if we're daemonized it will be closed).
16020 - Enable -g always, so cores will be more useful to me.
16021 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
16024 - Wrote a man page. It lists commonly used options.
16027 - Change default loglevel to warn.
16028 - Make PidFile default to null rather than littering in your CWD.
16029 - OnionRouter config option is now obsolete. Instead it just checks
16031 - Moved to a single unified torrc file for both clients and servers.
16034 Changes in version 0.0.2pre14 - 2003-11-29
16035 o Robustness and bugfixes:
16036 - Force the admin to make the DataDirectory himself
16037 - to get ownership/permissions right
16038 - so clients no longer make a DataDirectory and then never use it
16039 - fix bug where a client who was offline for 45 minutes would never
16040 pull down a directory again
16041 - fix (or at least hide really well) the dns assert bug that was
16042 causing server crashes
16043 - warnings and improved robustness wrt clockskew for certs
16044 - use the native daemon(3) to daemonize, when available
16045 - exit if bind() fails
16046 - exit if neither socksport nor orport is defined
16047 - include our own tor_timegm (Win32 doesn't have its own)
16048 - bugfix for win32 with lots of connections
16049 - fix minor bias in PRNG
16050 - make dirserver more robust to corrupt cached directory
16053 - Wrote the design document (woo)
16055 o Circuit building and exit policies:
16056 - Circuits no longer try to use nodes that the directory has told them
16058 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
16059 bitcounts (18.0.0.0/8).
16060 - Make AP connections standby for a circuit if no suitable circuit
16061 exists, rather than failing
16062 - Circuits choose exit node based on addr/port, exit policies, and
16063 which AP connections are standing by
16064 - Bump min pathlen from 2 to 3
16065 - Relay end cells have a payload to describe why the stream ended.
16066 - If the stream failed because of exit policy, try again with a new
16068 - Clients have a dns cache to remember resolved addresses.
16069 - Notice more quickly when we have no working circuits
16072 - APPort is now called SocksPort
16073 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
16075 - RecommendedVersions is now a config variable rather than
16076 hardcoded (for dirservers)
16077 - Reloads config on HUP
16078 - Usage info on -h or --help
16079 - If you set User and Group config vars, it'll setu/gid to them.
16081 Changes in version 0.0.2pre13 - 2003-10-19
16082 o General stability:
16083 - SSL_write no longer fails when it returns WANTWRITE and the number
16084 of bytes in the buf has changed by the next SSL_write call.
16085 - Fix segfault fetching directory when network is down
16086 - Fix a variety of minor memory leaks
16087 - Dirservers reload the fingerprints file on HUP, so I don't have
16088 to take down the network when I approve a new router
16089 - Default server config file has explicit Address line to specify fqdn
16092 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
16093 - Make listener connections not ever alloc bufs
16095 o Autoconf improvements:
16096 - don't clobber an external CFLAGS in ./configure
16097 - Make install now works
16098 - create var/lib/tor on make install
16099 - autocreate a tor.sh initscript to help distribs
16100 - autocreate the torrc and sample-server-torrc with correct paths
16102 o Log files and Daemonizing now work:
16103 - If --DebugLogFile is specified, log to it at -l debug
16104 - If --LogFile is specified, use it instead of commandline
16105 - If --RunAsDaemon is set, tor forks and backgrounds on startup