1 Changes in 0.4.0.2-alpha - 2019-02-21:
2 Tor 0.4.0.2-alpha is the second alpha in its series; it fixes several
3 bugs from earlier versions, including several that had broken
4 backward compatibility.
6 o Major bugfixes (networking):
7 - Gracefully handle empty username/password fields in SOCKS5
8 username/password auth messsage and allow SOCKS5 handshake to
9 continue. Previously, we had rejected these handshakes, breaking
10 certain applications. Fixes bug 29175; bugfix on 0.3.5.1-alpha.
12 o Major bugfixes (windows, startup):
13 - When reading a consensus file from disk, detect whether it was
14 written in text mode, and re-read it in text mode if so. Always
15 write consensus files in binary mode so that we can map them into
16 memory later. Previously, we had written in text mode, which
17 confused us when we tried to map the file on windows. Fixes bug
18 28614; bugfix on 0.4.0.1-alpha.
20 o Minor features (compilation):
21 - Compile correctly when OpenSSL is built with engine support
22 disabled, or with deprecated APIs disabled. Closes ticket 29026.
23 Patches from "Mangix".
25 o Minor features (developer tooling):
26 - Check that bugfix versions in changes files look like Tor versions
27 from the versions spec. Warn when bugfixes claim to be on a future
28 release. Closes ticket 27761.
29 - Provide a git pre-commit hook that disallows commiting if we have
30 any failures in our code and changelog formatting checks. It is
31 now available in scripts/maint/pre-commit.git-hook. Implements
34 o Minor features (directory authority):
35 - When a directory authority is using a bandwidth file to obtain
36 bandwidth values, include the digest of that file in the vote.
39 o Minor features (geoip):
40 - Update geoip and geoip6 to the February 5 2019 Maxmind GeoLite2
41 Country database. Closes ticket 29478.
43 o Minor features (testing):
44 - Treat all unexpected ERR and BUG messages as test failures. Closes
47 o Minor bugfixes (build, compatibility, rust):
48 - Update Cargo.lock file to match the version made by the latest
49 version of Rust, so that "make distcheck" will pass again. Fixes
50 bug 29244; bugfix on 0.3.3.4-alpha.
52 o Minor bugfixes (compilation):
53 - Fix compilation warnings in test_circuitpadding.c. Fixes bug
54 29169; bugfix on 0.4.0.1-alpha.
55 - Silence a compiler warning in test-memwipe.c on OpenBSD. Fixes bug
56 29145; bugfix on 0.2.9.3-alpha. Patch from Kris Katterjohn.
58 o Minor bugfixes (documentation):
59 - Describe the contents of the v3 onion service client authorization
60 files correctly: They hold public keys, not private keys. Fixes
61 bug 28979; bugfix on 0.3.5.1-alpha. Spotted by "Felixix".
63 o Minor bugfixes (linux seccomp sandbox):
64 - Fix startup crash when experimental sandbox support is enabled.
65 Fixes bug 29150; bugfix on 0.4.0.1-alpha. Patch by Peter Gerber.
67 o Minor bugfixes (logging):
68 - Avoid logging that we are relaxing a circuit timeout when that
69 timeout is fixed. Fixes bug 28698; bugfix on 0.2.4.7-alpha.
70 - Log more information at "warning" level when unable to read a
71 private key; log more information at "info" level when unable to
72 read a public key. We had warnings here before, but they were lost
73 during our NSS work. Fixes bug 29042; bugfix on 0.3.5.1-alpha.
75 o Minor bugfixes (misc):
76 - The amount of total available physical memory is now determined
77 using the sysctl identifier HW_PHYSMEM (rather than HW_USERMEM)
78 when it is defined and a 64-bit variant is not available. Fixes
79 bug 28981; bugfix on 0.2.5.4-alpha. Patch from Kris Katterjohn.
81 o Minor bugfixes (onion services):
82 - Avoid crashing if ClientOnionAuthDir (incorrectly) contains more
83 than one private key for a hidden service. Fixes bug 29040; bugfix
85 - In hs_cache_store_as_client() log an HSDesc we failed to parse at
86 "debug" level. Tor used to log it as a warning, which caused very
87 long log lines to appear for some users. Fixes bug 29135; bugfix
89 - Stop logging "Tried to establish rendezvous on non-OR circuit..."
90 as a warning. Instead, log it as a protocol warning, because there
91 is nothing that relay operators can do to fix it. Fixes bug 29029;
94 o Minor bugfixes (scheduler):
95 - When re-adding channels to the pending list, check the correct
96 channel's sched_heap_idx. This issue has had no effect in mainline
97 Tor, but could have led to bugs down the road in improved versions
98 of our circuit scheduling code. Fixes bug 29508; bugfix
101 o Minor bugfixes (tests):
102 - Fix intermittent failures on an adaptive padding test. Fixes one
103 case of bug 29122; bugfix on 0.4.0.1-alpha.
104 - Disable an unstable circuit-padding test that was failing
105 intermittently because of an ill-defined small histogram. Such
106 histograms will be allowed again after 29298 is implemented. Fixes
107 a second case of bug 29122; bugfix on 0.4.0.1-alpha.
108 - Detect and suppress "bug" warnings from the util/time test on
109 Windows. Fixes bug 29161; bugfix on 0.2.9.3-alpha.
110 - Do not log an error-level message if we fail to find an IPv6
111 network interface from the unit tests. Fixes bug 29160; bugfix
115 - In the manpage entry describing MapAddress torrc setting, use
116 example IP addresses from ranges specified for use in documentation
117 by RFC 5737. Resolves issue 28623.
120 - Remove the old check-tor script. Resolves issue 29072.
123 Changes in version 0.4.0.1-alpha - 2019-01-18
124 Tor 0.4.0.1-alpha is the first release in the new 0.4.0.x series. It
125 introduces improved features for power and bandwidth conservation,
126 more accurate reporting of bootstrap progress for user interfaces, and
127 an experimental backend for an exciting new adaptive padding feature.
128 There is also the usual assortment of bugfixes and minor features, all
131 o Major features (battery management, client, dormant mode):
132 - When Tor is running as a client, and it is unused for a long time,
133 it can now enter a "dormant" state. When Tor is dormant, it avoids
134 network and CPU activity until it is reawoken either by a user
135 request or by a controller command. For more information, see the
136 configuration options starting with "Dormant". Implements tickets
138 - The client's memory of whether it is "dormant", and how long it
139 has spent idle, persists across invocations. Implements
141 - There is a DormantOnFirstStartup option that integrators can use
142 if they expect that in many cases, Tor will be installed but
145 o Major features (bootstrap reporting):
146 - When reporting bootstrap progress, report the first connection
147 uniformly, regardless of whether it's a connection for building
148 application circuits. This allows finer-grained reporting of early
149 progress than previously possible, with the improvements of ticket
150 27169. Closes tickets 27167 and 27103. Addresses ticket 27308.
151 - When reporting bootstrap progress, treat connecting to a proxy or
152 pluggable transport as separate from having successfully used that
153 proxy or pluggable transport to connect to a relay. Closes tickets
156 o Major features (circuit padding):
157 - Implement preliminary support for the circuit padding portion of
158 Proposal 254. The implementation supports Adaptive Padding (aka
159 WTF-PAD) state machines for use between experimental clients and
160 relays. Support is also provided for APE-style state machines that
161 use probability distributions instead of histograms to specify
162 inter-packet delay. At the moment, Tor does not provide any
163 padding state machines that are used in normal operation: for now,
164 this feature exists solely for experimentation. Closes
167 o Major features (refactoring):
168 - Tor now uses an explicit list of its own subsystems when
169 initializing and shutting down. Previously, these systems were
170 managed implicitly in various places throughout the codebase.
171 (There may still be some subsystems using the old system.) Closes
174 o Minor features (bootstrap reporting):
175 - When reporting bootstrap progress, stop distinguishing between
176 situations where only internal paths are available and situations
177 where external paths are available. Previously, Tor would often
178 erroneously report that it had only internal paths. Closes
181 o Minor features (continuous integration):
182 - Log Python version during each Travis CI job. Resolves
185 o Minor features (controller):
186 - Add a DROPOWNERSHIP command to undo the effects of TAKEOWNERSHIP.
187 Implements ticket 28843.
189 o Minor features (developer tooling):
190 - Provide a git hook script to prevent "fixup!" and "squash!"
191 commits from ending up in the master branch, as scripts/main/pre-
192 push.git-hook. Closes ticket 27993.
194 o Minor features (directory authority):
195 - Directory authorities support a new consensus algorithm, under
196 which the family lines in microdescriptors are encoded in a
197 canonical form. This change makes family lines more compressible
198 in transit, and on the client. Closes ticket 28266; implements
201 o Minor features (directory authority, relay):
202 - Authorities now vote on a "StaleDesc" flag to indicate that a
203 relay's descriptor is so old that the relay should upload again
204 soon. Relays treat this flag as a signal to upload a new
205 descriptor. This flag will eventually let us remove the
206 'published' date from routerstatus entries, and make our consensus
207 diffs much smaller. Closes ticket 26770; implements proposal 293.
209 o Minor features (fallback directory mirrors):
210 - Update the fallback whitelist based on operator opt-ins and opt-
211 outs. Closes ticket 24805, patch by Phoul.
213 o Minor features (FreeBSD):
214 - On FreeBSD-based systems, warn relay operators if the
215 "net.inet.ip.random_id" sysctl (IP ID randomization) is disabled.
218 o Minor features (HTTP standards compliance):
219 - Stop sending the header "Content-type: application/octet-stream"
220 along with transparently compressed documents: this confused
221 browsers. Closes ticket 28100.
223 o Minor features (IPv6):
224 - We add an option ClientAutoIPv6ORPort, to make clients randomly
225 prefer a node's IPv4 or IPv6 ORPort. The random preference is set
226 every time a node is loaded from a new consensus or bridge config.
227 We expect that this option will enable clients to bootstrap more
228 quickly without having to determine whether they support IPv4,
229 IPv6, or both. Closes ticket 27490. Patch by Neel Chauhan.
230 - When using addrs_in_same_network_family(), avoid choosing circuit
231 paths that pass through the same IPv6 subnet more than once.
232 Previously, we only checked IPv4 subnets. Closes ticket 24393.
233 Patch by Neel Chauhan.
235 o Minor features (log messages):
236 - Improve log message in v3 onion services that could print out
237 negative revision counters. Closes ticket 27707. Patch
240 o Minor features (memory usage):
241 - Save memory by storing microdescriptor family lists with a more
242 compact representation. Closes ticket 27359.
243 - Tor clients now use mmap() to read consensus files from disk, so
244 that they no longer need keep the full text of a consensus in
245 memory when parsing it or applying a diff. Closes ticket 27244.
247 o Minor features (parsing):
248 - Directory authorities now validate that router descriptors and
249 ExtraInfo documents are in a valid subset of UTF-8, and reject
250 them if they are not. Closes ticket 27367.
252 o Minor features (performance):
253 - Cache the results of summarize_protocol_flags(), so that we don't
254 have to parse the same protocol-versions string over and over.
255 This should save us a huge number of malloc calls on startup, and
256 may reduce memory fragmentation with some allocators. Closes
258 - Remove a needless memset() call from get_token_arguments, thereby
259 speeding up the tokenization of directory objects by about 20%.
261 - Replace parse_short_policy() with a faster implementation, to
262 improve microdescriptor parsing time. Closes ticket 28853.
263 - Speed up directory parsing a little by avoiding use of the non-
264 inlined strcmp_len() function. Closes ticket 28856.
265 - Speed up microdescriptor parsing by about 30%, to help improve
266 startup time. Closes ticket 28839.
268 o Minor features (pluggable transports):
269 - Add support for emitting STATUS updates to Tor's control port from
270 a pluggable transport process. Closes ticket 28846.
271 - Add support for logging to Tor's logging subsystem from a
272 pluggable transport process. Closes ticket 28180.
274 o Minor features (process management):
275 - Add a new process API for handling child processes. This new API
276 allows Tor to have bi-directional communication with child
277 processes on both Unix and Windows. Closes ticket 28179.
278 - Use the subsystem manager to initialize and shut down the process
279 module. Closes ticket 28847.
281 o Minor features (relay):
282 - When listing relay families, list them in canonical form including
283 the relay's own identity, and try to give a more useful set of
284 warnings. Part of ticket 28266 and proposal 298.
286 o Minor features (required protocols):
287 - Before exiting because of a missing required protocol, Tor will
288 now check the publication time of the consensus, and not exit
289 unless the consensus is newer than the Tor program's own release
290 date. Previously, Tor would not check the consensus publication
291 time, and so might exit because of a missing protocol that might
292 no longer be required in a current consensus. Implements proposal
293 297; closes ticket 27735.
295 o Minor features (testing):
296 - Allow a HeartbeatPeriod of less than 30 minutes in testing Tor
297 networks. Closes ticket 28840. Patch by Rob Jansen.
299 o Minor bugfixes (client, clock skew):
300 - Bootstrap successfully even when Tor's clock is behind the clocks
301 on the authorities. Fixes bug 28591; bugfix on 0.2.0.9-alpha.
302 - Select guards even if the consensus has expired, as long as the
303 consensus is still reasonably live. Fixes bug 24661; bugfix
306 o Minor bugfixes (compilation):
307 - Compile correctly on OpenBSD; previously, we were missing some
308 headers required in order to detect it properly. Fixes bug 28938;
309 bugfix on 0.3.5.1-alpha. Patch from Kris Katterjohn.
311 o Minor bugfixes (directory clients):
312 - Mark outdated dirservers when Tor only has a reasonably live
313 consensus. Fixes bug 28569; bugfix on 0.3.2.5-alpha.
315 o Minor bugfixes (directory mirrors):
316 - Even when a directory mirror's clock is behind the clocks on the
317 authorities, we now allow the mirror to serve "future"
318 consensuses. Fixes bug 28654; bugfix on 0.3.0.1-alpha.
320 o Minor bugfixes (DNS):
321 - Gracefully handle an empty or absent resolve.conf file by falling
322 back to using "localhost" as a DNS server (and hoping it works).
323 Previously, we would just stop running as an exit. Fixes bug
324 21900; bugfix on 0.2.1.10-alpha.
326 o Minor bugfixes (guards):
327 - In count_acceptable_nodes(), the minimum number is now one bridge
328 or guard node, and two non-guard nodes for a circuit. Previously,
329 we had added up the sum of all nodes with a descriptor, but that
330 could cause us to build failing circuits when we had either too
331 many bridges or not enough guard nodes. Fixes bug 25885; bugfix on
332 0.3.6.1-alpha. Patch by Neel Chauhan.
334 o Minor bugfixes (IPv6):
335 - Fix tor_ersatz_socketpair on IPv6-only systems. Previously, the
336 IPv6 socket was bound using an address family of AF_INET instead
337 of AF_INET6. Fixes bug 28995; bugfix on 0.3.5.1-alpha. Patch from
340 o Minor bugfixes (logging):
341 - Rework rep_hist_log_link_protocol_counts() to iterate through all
342 link protocol versions when logging incoming/outgoing connection
343 counts. Tor no longer skips version 5, and we won't have to
344 remember to update this function when new link protocol version is
345 developed. Fixes bug 28920; bugfix on 0.2.6.10.
347 o Minor bugfixes (networking):
348 - Introduce additional checks into tor_addr_parse() to reject
349 certain incorrect inputs that previously were not detected. Fixes
350 bug 23082; bugfix on 0.2.0.10-alpha.
352 o Minor bugfixes (onion service v3, client):
353 - Stop logging a "BUG()" warning and stacktrace when we find a SOCKS
354 connection waiting for a descriptor that we actually have in the
355 cache. It turns out that this can actually happen, though it is
356 rare. Now, tor will recover and retry the descriptor. Fixes bug
357 28669; bugfix on 0.3.2.4-alpha.
359 o Minor bugfixes (periodic events):
360 - Refrain from calling routerlist_remove_old_routers() from
361 check_descriptor_callback(). Instead, create a new hourly periodic
362 event. Fixes bug 27929; bugfix on 0.2.8.1-alpha.
364 o Minor bugfixes (pluggable transports):
365 - Make sure that data is continously read from standard output and
366 standard error pipes of a pluggable transport child-process, to
367 avoid deadlocking when a pipe's buffer is full. Fixes bug 26360;
368 bugfix on 0.2.3.6-alpha.
370 o Minor bugfixes (unit tests):
371 - Instead of relying on hs_free_all() to clean up all onion service
372 objects in test_build_descriptors(), we now deallocate them one by
373 one. This lets Coverity know that we are not leaking memory there
374 and fixes CID 1442277. Fixes bug 28989; bugfix on 0.3.5.1-alpha.
376 o Minor bugfixes (usability):
377 - Stop saying "Your Guard ..." in pathbias_measure_{use,close}_rate().
378 Some users took this phrasing to mean that the mentioned guard was
379 under their control or responsibility, which it is not. Fixes bug
380 28895; bugfix on Tor 0.3.0.1-alpha.
382 o Code simplification and refactoring:
383 - Reimplement NETINFO cell parsing and generation to rely on
384 trunnel-generated wire format handling code. Closes ticket 27325.
385 - Remove unnecessary unsafe code from the Rust macro "cstr!". Closes
387 - Rework SOCKS wire format handling to rely on trunnel-generated
388 parsing/generation code. Resolves ticket 27620.
389 - Split out bootstrap progress reporting from control.c into a
390 separate file. Part of ticket 27402.
391 - The .may_include files that we use to describe our directory-by-
392 directory dependency structure now describe a noncircular
393 dependency graph over the directories that they cover. Our
394 checkIncludes.py tool now enforces this noncircularity. Closes
398 - Mention that you cannot add a new onion service if Tor is already
399 running with Sandbox enabled. Closes ticket 28560.
400 - Improve ControlPort documentation. Mention that it accepts
401 address:port pairs, and can be used multiple times. Closes
403 - Document the exact output of "tor --version". Closes ticket 28889.
406 - Stop responding to the 'GETINFO status/version/num-concurring' and
407 'GETINFO status/version/num-versioning' control port commands, as
408 those were deprecated back in 0.2.0.30. Also stop listing them in
409 output of 'GETINFO info/names'. Resolves ticket 28757.
410 - The scripts used to generate and maintain the list of fallback
411 directories have been extracted into a new "fallback-scripts"
412 repository. Closes ticket 27914.
415 - Run shellcheck for scripts in the in scripts/ directory. Closes
417 - Add unit tests for tokenize_string() and get_next_token()
418 functions. Resolves ticket 27625.
420 o Code simplification and refactoring (onion service v3):
421 - Consolidate the authorized client descriptor cookie computation
422 code from client and service into one function. Closes
425 o Code simplification and refactoring (shell scripts):
426 - Cleanup scan-build.sh to silence shellcheck warnings. Closes
428 - Fix issues that shellcheck found in chutney-git-bisect.sh.
429 Resolves ticket 28006.
430 - Fix issues that shellcheck found in updateRustDependencies.sh.
431 Resolves ticket 28012.
432 - Fix shellcheck warnings in cov-diff script. Resolves issue 28009.
433 - Fix shellcheck warnings in run_calltool.sh. Resolves ticket 28011.
434 - Fix shellcheck warnings in run_trunnel.sh. Resolves issue 28010.
435 - Fix shellcheck warnings in scripts/test/coverage. Resolves
439 Changes in version 0.3.3.11 - 2019-01-07
440 Tor 0.3.3.11 backports numerous fixes from later versions of Tor.
441 numerous fixes, including an important fix for anyone using OpenSSL
442 1.1.1. Anyone running an earlier version of Tor 0.3.3 should upgrade
443 to this version, or to a later series.
445 As a reminder, support the Tor 0.3.3 series will end on 22 Feb 2019.
446 We anticipate that this will be the last release of Tor 0.3.3, unless
447 some major bug is before then. Some time between now and then, users
448 should switch to either the Tor 0.3.4 series (supported until at least
449 10 June 2019), or the Tor 0.3.5 series, which will receive long-term
450 support until at least 1 Feb 2022.
452 o Major bugfixes (OpenSSL, portability, backport from 0.3.5.5-alpha):
453 - Fix our usage of named groups when running as a TLS 1.3 client in
454 OpenSSL 1.1.1. Previously, we only initialized EC groups when
455 running as a relay, which caused clients to fail to negotiate TLS
456 1.3 with relays. Fixes bug 28245; bugfix on 0.2.9.15 (when TLS 1.3
459 o Major bugfixes (restart-in-process, backport from 0.3.5.1-alpha):
460 - Fix a use-after-free error that could be caused by passing Tor an
461 impossible set of options that would fail during options_act().
462 Fixes bug 27708; bugfix on 0.3.3.1-alpha.
464 o Minor features (continuous integration, backport from 0.3.5.1-alpha):
465 - Only run one online rust build in Travis, to reduce network
466 errors. Skip offline rust builds on Travis for Linux gcc, because
467 they're redundant. Implements ticket 27252.
468 - Skip gcc on OSX in Travis CI, because it's rarely used. Skip a
469 duplicate hardening-off build in Travis on Tor 0.2.9. Skip gcc on
470 Linux with default settings, because all the non-default builds
471 use gcc on Linux. Implements ticket 27252.
473 o Minor features (continuous integration, backport from 0.3.5.3-alpha):
474 - Use the Travis Homebrew addon to install packages on macOS during
475 Travis CI. The package list is the same, but the Homebrew addon
476 does not do a `brew update` by default. Implements ticket 27738.
478 o Minor features (fallback directory list, backport from 0.3.5.6-rc):
479 - Replace the 150 fallbacks originally introduced in Tor
480 0.3.3.1-alpha in January 2018 (of which ~115 were still
481 functional), with a list of 157 fallbacks (92 new, 65 existing, 85
482 removed) generated in December 2018. Closes ticket 24803.
484 o Minor features (geoip):
485 - Update geoip and geoip6 to the January 3 2019 Maxmind GeoLite2
486 Country database. Closes ticket 29012.
488 o Minor features (OpenSSL bug workaround, backport from 0.3.5.7):
489 - Work around a bug in OpenSSL 1.1.1a, which prevented the TLS 1.3
490 key export function from handling long labels. When this bug is
491 detected, Tor will disable TLS 1.3. We recommend upgrading to a
492 version of OpenSSL without this bug when it becomes available.
495 o Minor bugfixes (relay statistics, backport from 0.3.5.7):
496 - Update relay descriptor on bandwidth changes only when the uptime
497 is smaller than 24h, in order to reduce the efficiency of guard
498 discovery attacks. Fixes bug 24104; bugfix on 0.1.1.6-alpha.
500 o Minor bugfixes (C correctness, backport from 0.3.5.4-alpha):
501 - Avoid undefined behavior in an end-of-string check when parsing
502 the BEGIN line in a directory object. Fixes bug 28202; bugfix
505 o Minor bugfixes (code safety, backport from 0.3.5.3-alpha):
506 - Rewrite our assertion macros so that they no longer suppress the
507 compiler's -Wparentheses warnings. Fixes bug 27709; bugfix
509 o Minor bugfixes (compilation, backport from 0.3.5.5-alpha):
510 - Initialize a variable unconditionally in aes_new_cipher(), since
511 some compilers cannot tell that we always initialize it before
512 use. Fixes bug 28413; bugfix on 0.2.9.3-alpha.
514 o Minor bugfixes (directory authority, backport from 0.3.5.4-alpha):
515 - Log additional info when we get a relay that shares an ed25519 ID
516 with a different relay, instead making a BUG() warning. Fixes bug
517 27800; bugfix on 0.3.2.1-alpha.
519 o Minor bugfixes (directory permissions, backport form 0.3.5.3-alpha):
520 - When a user requests a group-readable DataDirectory, give it to
521 them. Previously, when the DataDirectory and the CacheDirectory
522 were the same, the default setting (0) for
523 CacheDirectoryGroupReadable would override the setting for
524 DataDirectoryGroupReadable. Fixes bug 26913; bugfix
527 o Minor bugfixes (onion service v3, backport from 0.3.5.1-alpha):
528 - When the onion service directory can't be created or has the wrong
529 permissions, do not log a stack trace. Fixes bug 27335; bugfix
532 o Minor bugfixes (onion service v3, backport from 0.3.5.2-alpha):
533 - Close all SOCKS request (for the same .onion) if the newly fetched
534 descriptor is unusable. Before that, we would close only the first
535 one leaving the other hanging and let to time out by themselves.
536 Fixes bug 27410; bugfix on 0.3.2.1-alpha.
538 o Minor bugfixes (onion service v3, backport from 0.3.5.3-alpha):
539 - Don't warn so loudly when Tor is unable to decode an onion
540 descriptor. This can now happen as a normal use case if a client
541 gets a descriptor with client authorization but the client is not
542 authorized. Fixes bug 27550; bugfix on 0.3.5.1-alpha.
544 o Minor bugfixes (onion service v3, backport from 0.3.5.6-rc):
545 - When deleting an ephemeral onion service (DEL_ONION), do not close
546 any rendezvous circuits in order to let the existing client
547 connections finish by themselves or closed by the application. The
548 HS v2 is doing that already so now we have the same behavior for
549 all versions. Fixes bug 28619; bugfix on 0.3.3.1-alpha.
551 o Minor bugfixes (HTTP tunnel):
552 - Fix a bug warning when closing an HTTP tunnel connection due to
553 an HTTP request we couldn't handle. Fixes bug 26470; bugfix on
556 o Minor bugfixes (memory leaks, backport from 0.3.5.5-alpha):
557 - Fix a harmless memory leak in libtorrunner.a. Fixes bug 28419;
558 bugfix on 0.3.3.1-alpha. Patch from Martin Kepplinger.
560 o Minor bugfixes (netflow padding, backport from 0.3.5.1-alpha):
561 - Ensure circuitmux queues are empty before scheduling or sending
562 padding. Fixes bug 25505; bugfix on 0.3.1.1-alpha.
564 o Minor bugfixes (protover, backport from 0.3.5.3-alpha):
565 - Reject protocol names containing bytes other than alphanumeric
566 characters and hyphens ([A-Za-z0-9-]). Fixes bug 27316; bugfix
569 o Minor bugfixes (rust, backport from 0.3.5.1-alpha):
570 - Compute protover votes correctly in the rust version of the
571 protover code. Previously, the protover rewrite in 24031 allowed
572 repeated votes from the same voter for the same protocol version
573 to be counted multiple times in protover_compute_vote(). Fixes bug
574 27649; bugfix on 0.3.3.5-rc.
575 - Reject protover names that contain invalid characters. Fixes bug
576 27687; bugfix on 0.3.3.1-alpha.
578 o Minor bugfixes (rust, backport from 0.3.5.2-alpha):
579 - protover_all_supported() would attempt to allocate up to 16GB on
580 some inputs, leading to a potential memory DoS. Fixes bug 27206;
581 bugfix on 0.3.3.5-rc.
583 o Minor bugfixes (rust, backport from 0.3.5.4-alpha):
584 - Fix a potential null dereference in protover_all_supported(). Add
585 a test for it. Fixes bug 27804; bugfix on 0.3.3.1-alpha.
586 - Return a string that can be safely freed by C code, not one
587 created by the rust allocator, in protover_all_supported(). Fixes
588 bug 27740; bugfix on 0.3.3.1-alpha.
589 - Fix an API mismatch in the rust implementation of
590 protover_compute_vote(). This bug could have caused crashes on any
591 directory authorities running Tor with Rust (which we do not yet
592 recommend). Fixes bug 27741; bugfix on 0.3.3.6.
594 o Minor bugfixes (testing, backport from 0.3.5.1-alpha):
595 - If a unit test running in a subprocess exits abnormally or with a
596 nonzero status code, treat the test as having failed, even if the
597 test reported success. Without this fix, memory leaks don't cause
598 the tests to fail, even with LeakSanitizer. Fixes bug 27658;
599 bugfix on 0.2.2.4-alpha.
601 o Minor bugfixes (testing, backport from 0.3.5.4-alpha):
602 - Treat backtrace test failures as expected on BSD-derived systems
603 (NetBSD, OpenBSD, and macOS/Darwin) until we solve bug 17808.
604 (FreeBSD failures have been treated as expected since 18204 in
605 0.2.8.) Fixes bug 27948; bugfix on 0.2.5.2-alpha.
607 o Minor bugfixes (unit tests, guard selection, backport from 0.3.5.6-rc):
608 - Stop leaking memory in an entry guard unit test. Fixes bug 28554;
609 bugfix on 0.3.0.1-alpha.
612 Changes in version 0.3.4.10 - 2019-01-07
613 Tor 0.3.4.9 is the second stable release in its series; it backports
614 numerous fixes, including an important fix for relays, and for anyone
615 using OpenSSL 1.1.1. Anyone running an earlier version of Tor 0.3.4
618 As a reminder, the Tor 0.3.4 series will be supported until 10 June
619 2019. Some time between now and then, users should switch to the Tor
620 0.3.5 series, which will receive long-term support until at least 1
623 o Major bugfixes (OpenSSL, portability, backport from 0.3.5.5-alpha):
624 - Fix our usage of named groups when running as a TLS 1.3 client in
625 OpenSSL 1.1.1. Previously, we only initialized EC groups when
626 running as a relay, which caused clients to fail to negotiate TLS
627 1.3 with relays. Fixes bug 28245; bugfix on 0.2.9.15 (when TLS 1.3
630 o Major bugfixes (relay, directory, backport from 0.3.5.7):
631 - Always reactivate linked connections in the main loop so long as
632 any linked connection has been active. Previously, connections
633 serving directory information wouldn't get reactivated after the
634 first chunk of data was sent (usually 32KB), which would prevent
635 clients from bootstrapping. Fixes bug 28912; bugfix on
636 0.3.4.1-alpha. Patch by "cypherpunks3".
638 o Minor features (continuous integration, Windows, backport from 0.3.5.6-rc):
639 - Always show the configure and test logs, and upload them as build
640 artifacts, when building for Windows using Appveyor CI.
643 o Minor features (controller, backport from 0.3.5.1-alpha):
644 - For purposes of CIRC_BW-based dropped cell detection, track half-
645 closed stream ids, and allow their ENDs, SENDMEs, DATA and path
646 bias check cells to arrive without counting it as dropped until
647 either the END arrives, or the windows are empty. Closes
650 o Minor features (fallback directory list, backport from 0.3.5.6-rc):
651 - Replace the 150 fallbacks originally introduced in Tor
652 0.3.3.1-alpha in January 2018 (of which ~115 were still
653 functional), with a list of 157 fallbacks (92 new, 65 existing, 85
654 removed) generated in December 2018. Closes ticket 24803.
656 o Minor features (geoip):
657 - Update geoip and geoip6 to the November 6 2018 Maxmind GeoLite2
658 Country database. Closes ticket 28395.
660 o Minor features (OpenSSL bug workaround, backport from 0.3.5.7):
661 - Work around a bug in OpenSSL 1.1.1a, which prevented the TLS 1.3
662 key export function from handling long labels. When this bug is
663 detected, Tor will disable TLS 1.3. We recommend upgrading to a
664 version of OpenSSL without this bug when it becomes available.
667 o Minor bugfixes (compilation, backport from 0.3.5.5-alpha):
668 - Initialize a variable unconditionally in aes_new_cipher(), since
669 some compilers cannot tell that we always initialize it before
670 use. Fixes bug 28413; bugfix on 0.2.9.3-alpha.
672 o Minor bugfixes (connection, relay, backport from 0.3.5.5-alpha):
673 - Avoid a logging a BUG() stacktrace when closing connection held
674 open because the write side is rate limited but not the read side.
675 Now, the connection read side is simply shut down until Tor is
676 able to flush the connection and close it. Fixes bug 27750; bugfix
679 o Minor bugfixes (continuous integration, Windows, backport from 0.3.5.5-alpha):
680 - Manually configure the zstd compiler options, when building using
681 mingw on Appveyor Windows CI. The MSYS2 mingw zstd package does
682 not come with a pkg-config file. Fixes bug 28454; bugfix
684 - Stop using an external OpenSSL install, and stop installing MSYS2
685 packages, when building using mingw on Appveyor Windows CI. Fixes
686 bug 28399; bugfix on 0.3.4.1-alpha.
688 o Minor bugfixes (continuous integration, Windows, backport from 0.3.5.6-rc):
689 - Explicitly specify the path to the OpenSSL library and do not
690 download OpenSSL from Pacman, but instead use the library that is
691 already provided by AppVeyor. Fixes bug 28574; bugfix on master.
693 o Minor bugfixes (directory permissions, backport form 0.3.5.3-alpha):
694 - When a user requests a group-readable DataDirectory, give it to
695 them. Previously, when the DataDirectory and the CacheDirectory
696 were the same, the default setting (0) for
697 CacheDirectoryGroupReadable would override the setting for
698 DataDirectoryGroupReadable. Fixes bug 26913; bugfix
701 o Minor bugfixes (memory leaks, backport from 0.3.5.5-alpha):
702 - Fix a harmless memory leak in libtorrunner.a. Fixes bug 28419;
703 bugfix on 0.3.3.1-alpha. Patch from Martin Kepplinger.
705 o Minor bugfixes (onion service v3, backport from 0.3.5.3-alpha):
706 - Don't warn so loudly when Tor is unable to decode an onion
707 descriptor. This can now happen as a normal use case if a client
708 gets a descriptor with client authorization but the client is not
709 authorized. Fixes bug 27550; bugfix on 0.3.5.1-alpha.
711 o Minor bugfixes (onion service v3, backport from 0.3.5.6-rc):
712 - When deleting an ephemeral onion service (DEL_ONION), do not close
713 any rendezvous circuits in order to let the existing client
714 connections finish by themselves or closed by the application. The
715 HS v2 is doing that already so now we have the same behavior for
716 all versions. Fixes bug 28619; bugfix on 0.3.3.1-alpha.
718 o Minor bugfixes (relay statistics, backport from 0.3.5.7):
719 - Update relay descriptor on bandwidth changes only when the uptime
720 is smaller than 24h, in order to reduce the efficiency of guard
721 discovery attacks. Fixes bug 24104; bugfix on 0.1.1.6-alpha.
723 o Minor bugfixes (unit tests, guard selection, backport from 0.3.5.6-rc):
724 - Stop leaking memory in an entry guard unit test. Fixes bug 28554;
725 bugfix on 0.3.0.1-alpha.
728 Changes in version 0.3.5.7 - 2019-01-07
729 Tor 0.3.5.7 is the first stable release in its series; it includes
730 compilation and portability fixes, and a fix for a severe problem
731 affecting directory caches.
733 The Tor 0.3.5 series includes several new features and performance
734 improvements, including client authorization for v3 onion services,
735 cleanups to bootstrap reporting, support for improved bandwidth-
736 measurement tools, experimental support for NSS in place of OpenSSL,
737 and much more. It also begins a full reorganization of Tor's code
738 layout, for improved modularity and maintainability in the future.
739 Finally, there is the usual set of performance improvements and
740 bugfixes that we try to do in every release series.
742 There are a couple of changes in the 0.3.5 that may affect
743 compatibility. First, the default version for newly created onion
744 services is now v3. Use the HiddenServiceVersion option if you want to
745 override this. Second, some log messages related to bootstrapping have
746 changed; if you use stem, you may need to update to the latest version
747 so it will recognize them.
749 We have designated 0.3.5 as a "long-term support" (LTS) series: we
750 will continue to patch major bugs in typical configurations of 0.3.5
751 until at least 1 Feb 2022. (We do not plan to provide long-term
752 support for embedding, Rust support, NSS support, running a directory
753 authority, or unsupported platforms. For these, you will need to stick
754 with the latest stable release.)
756 Below are the changes since 0.3.5.6-rc. For a complete list of changes
757 since 0.3.4.9, see the ReleaseNotes file.
759 o Major bugfixes (relay, directory):
760 - Always reactivate linked connections in the main loop so long as
761 any linked connection has been active. Previously, connections
762 serving directory information wouldn't get reactivated after the
763 first chunk of data was sent (usually 32KB), which would prevent
764 clients from bootstrapping. Fixes bug 28912; bugfix on
765 0.3.4.1-alpha. Patch by "cypherpunks3".
767 o Minor features (compilation):
768 - When possible, place our warning flags in a separate file, to
769 avoid flooding verbose build logs. Closes ticket 28924.
771 o Minor features (geoip):
772 - Update geoip and geoip6 to the January 3 2019 Maxmind GeoLite2
773 Country database. Closes ticket 29012.
775 o Minor features (OpenSSL bug workaround):
776 - Work around a bug in OpenSSL 1.1.1a, which prevented the TLS 1.3
777 key export function from handling long labels. When this bug is
778 detected, Tor will disable TLS 1.3. We recommend upgrading to a
779 version of OpenSSL without this bug when it becomes available.
782 o Minor features (performance):
783 - Remove about 96% of the work from the function that we run at
784 startup to test our curve25519_basepoint implementation. Since
785 this function has yet to find an actual failure, we now only run
786 it for 8 iterations instead of 200. Based on our profile
787 information, this change should save around 8% of our startup time
788 on typical desktops, and may have a similar effect on other
789 platforms. Closes ticket 28838.
790 - Stop re-validating our hardcoded Diffie-Hellman parameters on
791 every startup. Doing this wasted time and cycles, especially on
792 low-powered devices. Closes ticket 28851.
794 o Minor bugfixes (compilation):
795 - Fix compilation for Android by adding a missing header to
796 freespace.c. Fixes bug 28974; bugfix on 0.3.5.1-alpha.
798 o Minor bugfixes (correctness):
799 - Fix an unreached code path where we checked the value of
800 "hostname" inside send_resolved_hostname_cell(). Previously, we
801 used it before checking it; now we check it first. Fixes bug
802 28879; bugfix on 0.1.2.7-alpha.
804 o Minor bugfixes (testing):
805 - Make sure that test_rebind.py actually obeys its timeout, even
806 when it receives a large number of log messages. Fixes bug 28883;
807 bugfix on 0.3.5.4-alpha.
808 - Stop running stem's unit tests as part of "make test-stem", but
809 continue to run stem's unit and online tests during "make test-
810 stem-full". Fixes bug 28568; bugfix on 0.2.6.3-alpha.
812 o Minor bugfixes (windows services):
813 - Make Tor start correctly as an NT service again: previously it was
814 broken by refactoring. Fixes bug 28612; bugfix on 0.3.5.3-alpha.
816 o Code simplification and refactoring:
817 - When parsing a port configuration, make it more obvious to static
818 analyzer tools that we always initialize the address. Closes
822 Changes in version 0.3.5.6-rc - 2018-12-18
823 Tor 0.3.5.6-rc fixes numerous small bugs in earlier versions of Tor.
824 It is the first release candidate in the 0.3.5.x series; if no further
825 huge bugs are found, our next release may be the stable 0.3.5.x.
827 o Minor features (continuous integration, Windows):
828 - Always show the configure and test logs, and upload them as build
829 artifacts, when building for Windows using Appveyor CI.
832 o Minor features (fallback directory list):
833 - Replace the 150 fallbacks originally introduced in Tor
834 0.3.3.1-alpha in January 2018 (of which ~115 were still
835 functional), with a list of 157 fallbacks (92 new, 65 existing, 85
836 removed) generated in December 2018. Closes ticket 24803.
838 o Minor features (geoip):
839 - Update geoip and geoip6 to the December 5 2018 Maxmind GeoLite2
840 Country database. Closes ticket 28744.
842 o Minor bugfixes (compilation):
843 - Add missing dependency on libgdi32.dll for tor-print-ed-signing-
844 cert.exe on Windows. Fixes bug 28485; bugfix on 0.3.5.1-alpha.
846 o Minor bugfixes (continuous integration, Windows):
847 - Explicitly specify the path to the OpenSSL library and do not
848 download OpenSSL from Pacman, but instead use the library that is
849 already provided by AppVeyor. Fixes bug 28574; bugfix on master.
851 o Minor bugfixes (onion service v3):
852 - When deleting an ephemeral onion service (DEL_ONION), do not close
853 any rendezvous circuits in order to let the existing client
854 connections finish by themselves or closed by the application. The
855 HS v2 is doing that already so now we have the same behavior for
856 all versions. Fixes bug 28619; bugfix on 0.3.3.1-alpha.
858 o Minor bugfixes (restart-in-process, boostrap):
859 - Add missing resets of bootstrap tracking state when shutting down
860 (regression caused by ticket 27169). Fixes bug 28524; bugfix
863 o Minor bugfixes (testing):
864 - Use a separate DataDirectory for the test_rebind script.
865 Previously, this script would run using the default DataDirectory,
866 and sometimes fail. Fixes bug 28562; bugfix on 0.3.5.1-alpha.
867 Patch from Taylor R Campbell.
868 - Stop leaking memory in an entry guard unit test. Fixes bug 28554;
869 bugfix on 0.3.0.1-alpha.
871 o Minor bugfixes (Windows):
872 - Correctly identify Windows 8.1, Windows 10, and Windows Server
873 2008 and later from their NT versions. Fixes bug 28096; bugfix on
874 0.2.2.34; reported by Keifer Bly.
875 - On recent Windows versions, the GetVersionEx() function may report
876 an earlier Windows version than the running OS. To avoid user
877 confusion, add "[or later]" to Tor's version string on affected
878 versions of Windows. Fixes bug 28096; bugfix on 0.2.2.34; reported
880 - Remove Windows versions that were never supported by the
881 GetVersionEx() function. Stop duplicating the latest Windows
882 version in get_uname(). Fixes bug 28096; bugfix on 0.2.2.34;
883 reported by Keifer Bly.
886 - Increase logging and tag all log entries with timestamps in
887 test_rebind.py. Provides diagnostics for issue 28229.
889 o Code simplification and refactoring (shared random, dirauth):
890 - Change many tor_assert() to use BUG() instead. The idea is to not
891 crash a dirauth but rather scream loudly with a stacktrace and let
892 it continue run. The shared random subsystem is very resilient and
893 if anything wrong happens with it, at worst a non coherent value
894 will be put in the vote and discarded by the other authorities.
897 o Documentation (onion services):
898 - Document in the man page that changing ClientOnionAuthDir value or
899 adding a new file in the directory will not work at runtime upon
900 sending a HUP if Sandbox 1. Closes ticket 28128.
901 - Note in the man page that the only real way to fully revoke an
902 onion service v3 client authorization is by restarting the tor
903 process. Closes ticket 28275.
906 Changes in version 0.3.5.5-alpha - 2018-11-16
907 Tor 0.3.5.5-alpha includes numerous bugfixes on earlier releases,
908 including several that we hope to backport to older release series in
911 o Major bugfixes (OpenSSL, portability):
912 - Fix our usage of named groups when running as a TLS 1.3 client in
913 OpenSSL 1.1.1. Previously, we only initialized EC groups when
914 running as a relay, which caused clients to fail to negotiate TLS
915 1.3 with relays. Fixes bug 28245; bugfix on 0.2.9.15 (when TLS 1.3
918 o Minor features (geoip):
919 - Update geoip and geoip6 to the November 6 2018 Maxmind GeoLite2
920 Country database. Closes ticket 28395.
922 o Minor bugfixes (compilation):
923 - Initialize a variable unconditionally in aes_new_cipher(), since
924 some compilers cannot tell that we always initialize it before
925 use. Fixes bug 28413; bugfix on 0.2.9.3-alpha.
927 o Minor bugfixes (connection, relay):
928 - Avoid a logging a BUG() stacktrace when closing connection held
929 open because the write side is rate limited but not the read side.
930 Now, the connection read side is simply shut down until Tor is
931 able to flush the connection and close it. Fixes bug 27750; bugfix
934 o Minor bugfixes (continuous integration, Windows):
935 - Manually configure the zstd compiler options, when building using
936 mingw on Appveyor Windows CI. The MSYS2 mingw zstd package does
937 not come with a pkg-config file. Fixes bug 28454; bugfix
939 - Stop using an external OpenSSL install, and stop installing MSYS2
940 packages, when building using mingw on Appveyor Windows CI. Fixes
941 bug 28399; bugfix on 0.3.4.1-alpha.
943 o Minor bugfixes (documentation):
944 - Make Doxygen work again after the code movement in the 0.3.5
945 source tree. Fixes bug 28435; bugfix on 0.3.5.1-alpha.
947 o Minor bugfixes (Linux seccomp2 sandbox):
948 - Permit the "shutdown()" system call, which is apparently used by
949 OpenSSL under some circumstances. Fixes bug 28183; bugfix
952 o Minor bugfixes (logging):
953 - Stop talking about the Named flag in log messages. Clients have
954 ignored the Named flag since 0.3.2. Fixes bug 28441; bugfix
957 o Minor bugfixes (memory leaks):
958 - Fix a harmless memory leak in libtorrunner.a. Fixes bug 28419;
959 bugfix on 0.3.3.1-alpha. Patch from Martin Kepplinger.
961 o Minor bugfixes (onion services):
962 - On an intro point for a version 3 onion service, stop closing
963 introduction circuits on an NACK. This lets the client decide
964 whether to reuse the circuit or discard it. Previously, we closed
965 intro circuits when sending NACKs. Fixes bug 27841; bugfix on
966 0.3.2.1-alpha. Patch by Neel Chaunan.
967 - When replacing a descriptor in the client cache, make sure to
968 close all client introduction circuits for the old descriptor, so
969 we don't end up with unusable leftover circuits. Fixes bug 27471;
970 bugfix on 0.3.2.1-alpha.
973 Changes in version 0.3.5.4-alpha - 2018-11-08
974 Tor 0.3.5.4-alpha includes numerous bugfixes on earlier versions and
975 improves our continuous integration support. It continues our attempts
976 to stabilize this alpha branch and build it into a foundation for an
977 acceptable long-term-support release.
979 o Major bugfixes (compilation, rust):
980 - Rust tests can now build and run successfully with the
981 --enable-fragile-hardening option enabled. Doing this currently
982 requires the rust beta channel; it will be possible with stable
983 rust once Rust version 1.31 is released. Patch from Alex Crichton.
984 Fixes bugs 27272, 27273, and 27274. Bugfix on 0.3.1.1-alpha.
986 o Major bugfixes (embedding, main loop):
987 - When DisableNetwork becomes set, actually disable periodic events
988 that are already enabled. (Previously, we would refrain from
989 enabling new ones, but we would leave the old ones turned on.)
990 Fixes bug 28348; bugfix on 0.3.4.1-alpha.
992 o Minor features (continuous integration):
993 - Add a Travis CI build for --enable-nss on Linux gcc. Closes
995 - Add new CI job to Travis configuration to run stem-based
996 integration tests. Closes ticket 27913.
998 o Minor features (Windows, continuous integration):
999 - Build tor on Windows Server 2012 R2 and Windows Server 2016 using
1000 Appveyor's CI. Closes ticket 28318.
1002 o Minor bugfixes (C correctness, also in 0.3.4.9):
1003 - Avoid undefined behavior in an end-of-string check when parsing
1004 the BEGIN line in a directory object. Fixes bug 28202; bugfix
1007 o Minor bugfixes (compilation):
1008 - Fix a pair of missing headers on OpenBSD. Fixes bug 28303; bugfix
1009 on 0.3.5.1-alpha. Patch from Kris Katterjohn.
1011 o Minor bugfixes (compilation, OpenSolaris):
1012 - Fix compilation on OpenSolaris and its descendants by adding a
1013 missing include to compat_pthreads.c. Fixes bug 27963; bugfix
1016 o Minor bugfixes (configuration):
1017 - Refuse to start with relative file paths and RunAsDaemon set
1018 (regression from the fix for bug 22731). Fixes bug 28298; bugfix
1021 o Minor bugfixes (directory authority, also in 0.3.4.9):
1022 - Log additional info when we get a relay that shares an ed25519 ID
1023 with a different relay, instead of a BUG() warning with a
1024 backtrace. Fixes bug 27800; bugfix on 0.3.2.1-alpha.
1026 o Minor bugfixes (onion service v3):
1027 - Build the service descriptor's signing key certificate before
1028 uploading, so we always have a fresh one: leaving no chances for
1029 it to expire service side. Fixes bug 27838; bugfix
1032 o Minor bugfixes (onion service v3, client authorization):
1033 - Fix an assert() when adding a client authorization for the first
1034 time and then sending a HUP signal to the service. Before that,
1035 Tor would stop abruptly. Fixes bug 27995; bugfix on 0.3.5.1-alpha.
1037 o Minor bugfixes (onion services):
1038 - Unless we have explicitly set HiddenServiceVersion, detect the
1039 onion service version and then look for invalid options.
1040 Previously, we did the reverse, but that broke existing configs
1041 which were pointed to a v2 service and had options like
1042 HiddenServiceAuthorizeClient set. Fixes bug 28127; bugfix on
1043 0.3.5.1-alpha. Patch by Neel Chauhan.
1045 o Minor bugfixes (portability):
1046 - Make the OPE code (which is used for v3 onion services) run
1047 correctly on big-endian platforms. Fixes bug 28115; bugfix
1050 o Minor bugfixes (protover, rust):
1051 - Reject extra commas in version strings. Fixes bug 27197; bugfix
1054 o Minor bugfixes (relay shutdown, systemd):
1055 - Notify systemd of ShutdownWaitLength so it can be set to longer
1056 than systemd's TimeoutStopSec. In Tor's systemd service file, set
1057 TimeoutSec to 60 seconds to allow Tor some time to shut down.
1058 Fixes bug 28113; bugfix on 0.2.6.2-alpha.
1060 o Minor bugfixes (rust, also in 0.3.4.9):
1061 - Fix a potential null dereference in protover_all_supported(). Add
1062 a test for it. Fixes bug 27804; bugfix on 0.3.3.1-alpha.
1063 - Return a string that can be safely freed by C code, not one
1064 created by the rust allocator, in protover_all_supported(). Fixes
1065 bug 27740; bugfix on 0.3.3.1-alpha.
1067 o Minor bugfixes (rust, directory authority, also in 0.3.4.9):
1068 - Fix an API mismatch in the rust implementation of
1069 protover_compute_vote(). This bug could have caused crashes on any
1070 directory authorities running Tor with Rust (which we do not yet
1071 recommend). Fixes bug 27741; bugfix on 0.3.3.6.
1073 o Minor bugfixes (testing):
1074 - Avoid hangs and race conditions in test_rebind.py. Fixes bug
1075 27968; bugfix on 0.3.5.1-alpha.
1077 o Minor bugfixes (testing, also in 0.3.4.9):
1078 - Treat backtrace test failures as expected on BSD-derived systems
1079 (NetBSD, OpenBSD, and macOS/Darwin) until we solve bug 17808.
1080 (FreeBSD failures have been treated as expected since 18204 in
1081 0.2.8.) Fixes bug 27948; bugfix on 0.2.5.2-alpha.
1083 o Documentation (onion service manpage):
1084 - Improve HSv3 client authorization by making some options more
1085 explicit and detailed. Closes ticket 28026. Patch by Mike Tigas.
1088 Changes in version 0.3.4.9 - 2018-11-02
1089 Tor 0.3.4.9 is the second stable release in its series; it backports
1090 numerous fixes, including a fix for a bandwidth management bug that
1091 was causing memory exhaustion on relays. Anyone running an earlier
1092 version of Tor 0.3.4.9 should upgrade.
1094 o Major bugfixes (compilation, backport from 0.3.5.3-alpha):
1095 - Fix compilation on ARM (and other less-used CPUs) when compiling
1096 with OpenSSL before 1.1. Fixes bug 27781; bugfix on 0.3.4.1-alpha.
1098 o Major bugfixes (mainloop, bootstrap, backport from 0.3.5.3-alpha):
1099 - Make sure Tor bootstraps and works properly if only the
1100 ControlPort is set. Prior to this fix, Tor would only bootstrap
1101 when a client port was set (Socks, Trans, NATD, DNS or HTTPTunnel
1102 port). Fixes bug 27849; bugfix on 0.3.4.1-alpha.
1104 o Major bugfixes (relay, backport from 0.3.5.3-alpha):
1105 - When our write bandwidth limit is exhausted, stop writing on the
1106 connection. Previously, we had a typo in the code that would make
1107 us stop reading instead, leading to relay connections being stuck
1108 indefinitely and consuming kernel RAM. Fixes bug 28089; bugfix
1111 o Major bugfixes (restart-in-process, backport from 0.3.5.1-alpha):
1112 - Fix a use-after-free error that could be caused by passing Tor an
1113 impossible set of options that would fail during options_act().
1114 Fixes bug 27708; bugfix on 0.3.3.1-alpha.
1116 o Minor features (continuous integration, backport from 0.3.5.1-alpha):
1117 - Don't do a distcheck with --disable-module-dirauth in Travis.
1118 Implements ticket 27252.
1119 - Only run one online rust build in Travis, to reduce network
1120 errors. Skip offline rust builds on Travis for Linux gcc, because
1121 they're redundant. Implements ticket 27252.
1122 - Skip gcc on OSX in Travis CI, because it's rarely used. Skip a
1123 duplicate hardening-off build in Travis on Tor 0.2.9. Skip gcc on
1124 Linux with default settings, because all the non-default builds
1125 use gcc on Linux. Implements ticket 27252.
1127 o Minor features (continuous integration, backport from 0.3.5.3-alpha):
1128 - Use the Travis Homebrew addon to install packages on macOS during
1129 Travis CI. The package list is the same, but the Homebrew addon
1130 does not do a `brew update` by default. Implements ticket 27738.
1132 o Minor features (geoip):
1133 - Update geoip and geoip6 to the October 9 2018 Maxmind GeoLite2
1134 Country database. Closes ticket 27991.
1136 o Minor bugfixes (32-bit OSX and iOS, timing, backport from 0.3.5.2-alpha):
1137 - Fix an integer overflow bug in our optimized 32-bit millisecond-
1138 difference algorithm for 32-bit Apple platforms. Previously, it
1139 would overflow when calculating the difference between two times
1140 more than 47 days apart. Fixes part of bug 27139; bugfix
1142 - Improve the precision of our 32-bit millisecond difference
1143 algorithm for 32-bit Apple platforms. Fixes part of bug 27139;
1144 bugfix on 0.3.4.1-alpha.
1145 - Relax the tolerance on the mainloop/update_time_jumps test when
1146 running on 32-bit Apple platforms. Fixes part of bug 27139; bugfix
1149 o Minor bugfixes (C correctness, to appear in 0.3.5.4-alpha):
1150 - Avoid undefined behavior in an end-of-string check when parsing
1151 the BEGIN line in a directory object. Fixes bug 28202; bugfix
1154 o Minor bugfixes (CI, appveyor, to appear in 0.3.5.4-alpha):
1155 - Only install the necessary mingw packages during our appveyor
1156 builds. This change makes the build a little faster, and prevents
1157 a conflict with a preinstalled mingw openssl that appveyor now
1158 ships. Fixes bugs 27943 and 27765; bugfix on 0.3.4.2-alpha.
1160 o Minor bugfixes (code safety, backport from 0.3.5.3-alpha):
1161 - Rewrite our assertion macros so that they no longer suppress the
1162 compiler's -Wparentheses warnings. Fixes bug 27709; bugfix
1164 o Minor bugfixes (continuous integration, backport from 0.3.5.1-alpha):
1165 - Stop reinstalling identical packages in our Windows CI. Fixes bug
1166 27464; bugfix on 0.3.4.1-alpha.
1168 o Minor bugfixes (directory authority, to appear in 0.3.5.4-alpha):
1169 - Log additional info when we get a relay that shares an ed25519 ID
1170 with a different relay, instead making a BUG() warning. Fixes bug
1171 27800; bugfix on 0.3.2.1-alpha.
1173 o Minor bugfixes (directory connection shutdown, backport from 0.3.5.1-alpha):
1174 - Avoid a double-close when shutting down a stalled directory
1175 connection. Fixes bug 26896; bugfix on 0.3.4.1-alpha.
1177 o Minor bugfixes (HTTP tunnel, backport from 0.3.5.1-alpha):
1178 - Fix a bug warning when closing an HTTP tunnel connection due to an
1179 HTTP request we couldn't handle. Fixes bug 26470; bugfix
1182 o Minor bugfixes (netflow padding, backport from 0.3.5.1-alpha):
1183 - Ensure circuitmux queues are empty before scheduling or sending
1184 padding. Fixes bug 25505; bugfix on 0.3.1.1-alpha.
1186 o Minor bugfixes (onion service v3, backport from 0.3.5.1-alpha):
1187 - When the onion service directory can't be created or has the wrong
1188 permissions, do not log a stack trace. Fixes bug 27335; bugfix
1191 o Minor bugfixes (onion service v3, backport from 0.3.5.2-alpha):
1192 - Close all SOCKS request (for the same .onion) if the newly fetched
1193 descriptor is unusable. Before that, we would close only the first
1194 one leaving the other hanging and let to time out by themselves.
1195 Fixes bug 27410; bugfix on 0.3.2.1-alpha.
1197 o Minor bugfixes (onion service v3, backport from 0.3.5.3-alpha):
1198 - When selecting a v3 rendezvous point, don't only look at the
1199 protover, but also check whether the curve25519 onion key is
1200 present. This way we avoid picking a relay that supports the v3
1201 rendezvous but for which we don't have the microdescriptor. Fixes
1202 bug 27797; bugfix on 0.3.2.1-alpha.
1204 o Minor bugfixes (protover, backport from 0.3.5.3-alpha):
1205 - Reject protocol names containing bytes other than alphanumeric
1206 characters and hyphens ([A-Za-z0-9-]). Fixes bug 27316; bugfix
1209 o Minor bugfixes (rust, backport from 0.3.5.1-alpha):
1210 - Compute protover votes correctly in the rust version of the
1211 protover code. Previously, the protover rewrite in 24031 allowed
1212 repeated votes from the same voter for the same protocol version
1213 to be counted multiple times in protover_compute_vote(). Fixes bug
1214 27649; bugfix on 0.3.3.5-rc.
1215 - Reject protover names that contain invalid characters. Fixes bug
1216 27687; bugfix on 0.3.3.1-alpha.
1218 o Minor bugfixes (rust, backport from 0.3.5.2-alpha):
1219 - protover_all_supported() would attempt to allocate up to 16GB on
1220 some inputs, leading to a potential memory DoS. Fixes bug 27206;
1221 bugfix on 0.3.3.5-rc.
1223 o Minor bugfixes (rust, directory authority, to appear in 0.3.5.4-alpha):
1224 - Fix an API mismatch in the rust implementation of
1225 protover_compute_vote(). This bug could have caused crashes on any
1226 directory authorities running Tor with Rust (which we do not yet
1227 recommend). Fixes bug 27741; bugfix on 0.3.3.6.
1229 o Minor bugfixes (rust, to appear in 0.3.5.4-alpha):
1230 - Fix a potential null dereference in protover_all_supported(). Add
1231 a test for it. Fixes bug 27804; bugfix on 0.3.3.1-alpha.
1232 - Return a string that can be safely freed by C code, not one
1233 created by the rust allocator, in protover_all_supported(). Fixes
1234 bug 27740; bugfix on 0.3.3.1-alpha.
1236 o Minor bugfixes (testing, backport from 0.3.5.1-alpha):
1237 - If a unit test running in a subprocess exits abnormally or with a
1238 nonzero status code, treat the test as having failed, even if the
1239 test reported success. Without this fix, memory leaks don't cause
1240 the tests to fail, even with LeakSanitizer. Fixes bug 27658;
1241 bugfix on 0.2.2.4-alpha.
1243 o Minor bugfixes (testing, backport from 0.3.5.3-alpha):
1244 - Make the hs_service tests use the same time source when creating
1245 the introduction point and when testing it. Now tests work better
1246 on very slow systems like ARM or Travis. Fixes bug 27810; bugfix
1249 o Minor bugfixes (testing, to appear in 0.3.5.4-alpha):
1250 - Treat backtrace test failures as expected on BSD-derived systems
1251 (NetBSD, OpenBSD, and macOS/Darwin) until we solve bug 17808.
1252 (FreeBSD failures have been treated as expected since 18204 in
1253 0.2.8.) Fixes bug 27948; bugfix on 0.2.5.2-alpha.
1256 Changes in version 0.3.5.3-alpha - 2018-10-17
1257 Tor 0.3.5.3-alpha fixes several bugs, mostly from previous 0.3.5.x
1258 versions. One important fix for relays addresses a problem with rate-
1259 limiting code from back in 0.3.4.x: If the fix works out, we'll be
1260 backporting it soon. This release is still an alpha, but we hope it's
1261 getting closer and closer to stability.
1263 o Major features (onion services):
1264 - Version 3 onion services can now use the per-service
1265 HiddenServiceExportCircuitID option to differentiate client
1266 circuits. It communicates with the service by using the HAProxy
1267 protocol to assign virtual IP addresses to inbound client
1268 circuits. Closes ticket 4700. Patch by Mahrud Sayrafi.
1270 o Major bugfixes (compilation):
1271 - Fix compilation on ARM (and other less-used CPUs) when compiling
1272 with OpenSSL before 1.1. Fixes bug 27781; bugfix on 0.3.4.1-alpha.
1274 o Major bugfixes (initialization, crash):
1275 - Fix an assertion crash that would stop Tor from starting up if it
1276 tried to activate a periodic event too early. Fixes bug 27861;
1277 bugfix on 0.3.5.1-alpha.
1279 o Major bugfixes (mainloop, bootstrap):
1280 - Make sure Tor bootstraps and works properly if only the
1281 ControlPort is set. Prior to this fix, Tor would only bootstrap
1282 when a client port was set (Socks, Trans, NATD, DNS or HTTPTunnel
1283 port). Fixes bug 27849; bugfix on 0.3.4.1-alpha.
1285 o Major bugfixes (relay):
1286 - When our write bandwidth limit is exhausted, stop writing on the
1287 connection. Previously, we had a typo in the code that would make
1288 us stop reading instead, leading to relay connections being stuck
1289 indefinitely and consuming kernel RAM. Fixes bug 28089; bugfix
1292 o Minor features (continuous integration):
1293 - Use the Travis Homebrew addon to install packages on macOS during
1294 Travis CI. The package list is the same, but the Homebrew addon
1295 does not do a `brew update` by default. Implements ticket 27738.
1296 - Report what program produced the mysterious core file that we
1297 occasionally see on Travis CI during make distcheck. Closes
1300 o Minor features (geoip):
1301 - Update geoip and geoip6 to the October 9 2018 Maxmind GeoLite2
1302 Country database. Closes ticket 27991.
1304 o Minor bugfixes (code safety):
1305 - Rewrite our assertion macros so that they no longer suppress the
1306 compiler's -Wparentheses warnings. Fixes bug 27709; bugfix
1309 o Minor bugfixes (compilation):
1310 - Compile the ed25519-donna code with a correct declaration of
1311 crypto_strongest_rand(). Previously, we built it with one type,
1312 but linked it against another in the unit tests, which caused
1313 compilation failures with LTO enabled. This could have caused
1314 other undefined behavior in the tests. Fixes bug 27728; bugfix
1317 o Minor bugfixes (compilation, netbsd):
1318 - Add a missing include back into procmon.c. Fixes bug 27990; bugfix
1321 o Minor bugfixes (continuous integration, appveyor):
1322 - Install only the necessary mingw packages during our appveyor
1323 builds. This change makes the build a little faster, and prevents
1324 a conflict with a preinstalled mingw openssl that appveyor now
1325 ships. Fixes bugs 27765 and 27943; bugfix on 0.3.4.2-alpha.
1327 o Minor bugfixes (directory permissions):
1328 - When a user requests a group-readable DataDirectory, give it to
1329 them. Previously, when the DataDirectory and the CacheDirectory
1330 were the same, the default setting (0) for
1331 CacheDirectoryGroupReadable would override the setting for
1332 DataDirectoryGroupReadable. Fixes bug 26913; bugfix
1335 o Minor bugfixes (memory leaks):
1336 - Fix a small memory leak when calling Tor with --dump-config. Fixes
1337 bug 27893; bugfix on 0.3.2.1-alpha.
1339 o Minor bugfixes (networking):
1340 - In retry_listeners_ports(), make sure that we're removing a member
1341 of old_conns smartlist at most once. Fixes bug 27808; bugfix
1343 - Refrain from attempting socket rebinding when old and new
1344 listeners are in different address families. Fixes bug 27928;
1345 bugfix on 0.3.5.1-alpha.
1347 o Minor bugfixes (onion service v3):
1348 - Stop dumping a stack trace when trying to connect to an intro
1349 point without having a descriptor for it. Fixes bug 27774; bugfix
1351 - Don't warn so loudly when Tor is unable to decode an onion
1352 descriptor. This can now happen as a normal use case if a client
1353 gets a descriptor with client authorization but the client is not
1354 authorized. Fixes bug 27550; bugfix on 0.3.5.1-alpha.
1355 - When selecting a v3 rendezvous point, don't only look at the
1356 protover, but also check whether the curve25519 onion key is
1357 present. This way we avoid picking a relay that supports the v3
1358 rendezvous but for which we don't have the microdescriptor. Fixes
1359 bug 27797; bugfix on 0.3.2.1-alpha.
1361 o Minor bugfixes (protover):
1362 - Reject protocol names containing bytes other than alphanumeric
1363 characters and hyphens ([A-Za-z0-9-]). Fixes bug 27316; bugfix
1366 o Minor bugfixes (testing):
1367 - Make the hs_service tests use the same time source when creating
1368 the introduction point and when testing it. Now tests work better
1369 on very slow systems like ARM or Travis. Fixes bug 27810; bugfix
1371 - In test_rebind.py, check if the Python version is in the supported
1372 range. Fixes bug 27675; bugfix on 0.3.5.1-alpha.
1374 o Code simplification and refactoring:
1375 - Divide more large Tor source files -- especially ones that span
1376 multiple areas of functionality -- into smaller parts, including
1377 onion.c and main.c. Closes ticket 26747.
1378 - Divide the "routerparse.c" module into separate modules for each
1379 group of parsed objects. Closes ticket 27924.
1380 - Move protover_rust.c to the same place protover.c was moved to.
1381 Closes ticket 27814.
1382 - Split directory.c into separate pieces for client, server, and
1383 common functionality. Closes ticket 26744.
1384 - Split the non-statistics-related parts from the rephist.c and
1385 geoip.c modules. Closes ticket 27892.
1386 - Split the router.c file into relay-only and shared components, to
1387 help with future modularization. Closes ticket 27864.
1390 - In the tor-resolve(1) manpage, fix the reference to socks-
1391 extensions.txt by adding a web URL. Resolves ticket 27853.
1392 - Mention that we require Python to be 2.7 or newer for some
1393 integration tests that we ship with Tor. Resolves ticket 27677.
1396 Changes in version 0.3.5.2-alpha - 2018-09-21
1397 Tor 0.3.5.2-alpha fixes several bugs in 0.3.5.1-alpha, including one
1398 that made Tor think it had run out of sockets. Anybody running a relay
1399 or an onion service on 0.3.5.1-alpha should upgrade.
1401 o Major bugfixes (relay bandwidth statistics):
1402 - When we close relayed circuits, report the data in the circuit
1403 queues as being written in our relay bandwidth stats. This
1404 mitigates guard discovery and other attacks that close circuits
1405 for the explicit purpose of noticing this discrepancy in
1406 statistics. Fixes bug 23512; bugfix on 0.0.8pre3.
1408 o Major bugfixes (socket accounting):
1409 - In our socket accounting code, count a socket as closed even when
1410 it is closed indirectly by the TLS layer. Previously, we would
1411 count these sockets as still in use, and incorrectly believe that
1412 we had run out of sockets. Fixes bug 27795; bugfix
1415 o Minor bugfixes (32-bit OSX and iOS, timing):
1416 - Fix an integer overflow bug in our optimized 32-bit millisecond-
1417 difference algorithm for 32-bit Apple platforms. Previously, it
1418 would overflow when calculating the difference between two times
1419 more than 47 days apart. Fixes part of bug 27139; bugfix
1421 - Improve the precision of our 32-bit millisecond difference
1422 algorithm for 32-bit Apple platforms. Fixes part of bug 27139;
1423 bugfix on 0.3.4.1-alpha.
1424 - Relax the tolerance on the mainloop/update_time_jumps test when
1425 running on 32-bit Apple platforms. Fixes part of bug 27139; bugfix
1428 o Minor bugfixes (onion service v3):
1429 - Close all SOCKS request (for the same .onion) if the newly fetched
1430 descriptor is unusable. Before that, we would close only the first
1431 one leaving the other hanging and let to time out by themselves.
1432 Fixes bug 27410; bugfix on 0.3.2.1-alpha.
1434 o Minor bugfixes (memory leak):
1435 - Fix an unlikely memory leak when trying to read a private key from
1436 a ridiculously large file. Fixes bug 27764; bugfix on
1437 0.3.5.1-alpha. This is CID 1439488.
1439 o Minor bugfixes (NSS):
1440 - Correctly detect failure to open a dummy TCP socket when stealing
1441 ownership of an fd from the NSS layer. Fixes bug 27782; bugfix
1444 o Minor bugfixes (rust):
1445 - protover_all_supported() would attempt to allocate up to 16GB on
1446 some inputs, leading to a potential memory DoS. Fixes bug 27206;
1447 bugfix on 0.3.3.5-rc.
1449 o Minor bugfixes (testing):
1450 - Revise the "conditionvar_timeout" test so that it succeeds even on
1451 heavily loaded systems where the test threads are not scheduled
1452 within 200 msec. Fixes bug 27073; bugfix on 0.2.6.3-alpha.
1454 o Code simplification and refactoring:
1455 - Divide the routerlist.c and dirserv.c modules into smaller parts.
1456 Closes ticket 27799.
1459 Changes in version 0.3.5.1-alpha - 2018-09-18
1460 Tor 0.3.5.1-alpha is the first release of the 0.3.5.x series. It adds
1461 client authorization for modern (v3) onion services, improves
1462 bootstrap reporting, begins reorganizing Tor's codebase, adds optional
1463 support for NSS in place of OpenSSL, and much more.
1465 o Major features (onion services, UI change):
1466 - For a newly created onion service, the default version is now 3.
1467 Tor still supports existing version 2 services, but the operator
1468 now needs to set "HiddenServiceVersion 2" in order to create a new
1469 version 2 service. For existing services, Tor now learns the
1470 version by reading the key file. Closes ticket 27215.
1472 o Major features (relay, UI change):
1473 - Relays no longer run as exits by default. If the "ExitRelay"
1474 option is auto (or unset), and no exit policy is specified with
1475 ExitPolicy or ReducedExitPolicy, we now treat ExitRelay as 0.
1476 Previously in this case, we allowed exit traffic and logged a
1477 warning message. Closes ticket 21530. Patch by Neel Chauhan.
1478 - Tor now validates that the ContactInfo config option is valid UTF-
1479 8 when parsing torrc. Closes ticket 27428.
1481 o Major features (bootstrap):
1482 - Don't report directory progress until after a connection to a
1483 relay or bridge has succeeded. Previously, we'd report 80%
1484 progress based on cached directory information when we couldn't
1485 even connect to the network. Closes ticket 27169.
1487 o Major features (new code layout):
1488 - Nearly all of Tor's source code has been moved around into more
1489 logical places. The "common" directory is now divided into a set
1490 of libraries in "lib", and files in the "or" directory have been
1491 split into "core" (logic absolutely needed for onion routing),
1492 "feature" (independent modules in Tor), and "app" (to configure
1493 and invoke the rest of Tor). See doc/HACKING/CodeStructure.md for
1494 more information. Closes ticket 26481.
1496 This refactoring is not complete: although the libraries have been
1497 refactored to be acyclic, the main body of Tor is still too
1498 interconnected. We will attempt to improve this in the future.
1500 o Major features (onion services v3):
1501 - Implement onion service client authorization at the descriptor
1502 level: only authorized clients can decrypt a service's descriptor
1503 to find out how to contact it. A new torrc option was added to
1504 control this client side: ClientOnionAuthDir <path>. On the
1505 service side, if the "authorized_clients/" directory exists in the
1506 onion service directory path, client configurations are read from
1507 the files within. See the manpage for more details. Closes ticket
1508 27547. Patch done by Suphanat Chunhapanya (haxxpop).
1509 - Improve revision counter generation in next-gen onion services.
1510 Onion services can now scale by hosting multiple instances on
1511 different hosts without synchronization between them, which was
1512 previously impossible because descriptors would get rejected by
1513 HSDirs. Addresses ticket 25552.
1515 o Major features (portability, cryptography, experimental, TLS):
1516 - Tor now has the option to compile with the NSS library instead of
1517 OpenSSL. This feature is experimental, and we expect that bugs may
1518 remain. It is mainly intended for environments where Tor's
1519 performance is not CPU-bound, and where NSS is already known to be
1520 installed. To try it out, configure Tor with the --enable-nss
1521 flag. Closes tickets 26631, 26815, and 26816.
1523 If you are experimenting with this option and using an old cached
1524 consensus, Tor may fail to start. To solve this, delete your
1525 "cached-consensus" and "cached-microdesc-consensus" files,
1526 (if present), and restart Tor.
1528 o Major bugfixes (directory authority):
1529 - Actually check that the address we get from DirAuthority
1530 configuration line is valid IPv4. Explicitly disallow DirAuthority
1531 address to be a DNS hostname. Fixes bug 26488; bugfix
1534 o Major bugfixes (restart-in-process):
1535 - Fix a use-after-free error that could be caused by passing Tor an
1536 impossible set of options that would fail during options_act().
1537 Fixes bug 27708; bugfix on 0.3.3.1-alpha.
1539 o Minor features (admin tools):
1540 - Add a new --key-expiration option to print the expiration date of
1541 the signing cert in an ed25519_signing_cert file. Resolves
1544 o Minor features (build):
1545 - If you pass the "--enable-pic" option to configure, Tor will try
1546 to tell the compiler to build position-independent code suitable
1547 to link into a dynamic library. (The default remains -fPIE, for
1548 code suitable for a relocatable executable.) Closes ticket 23846.
1550 o Minor features (code correctness, testing):
1551 - Tor's build process now includes a "check-includes" make target to
1552 verify that no module of Tor relies on any headers from a higher-
1553 level module. We hope to use this feature over time to help
1554 refactor our codebase. Closes ticket 26447.
1556 o Minor features (code layout):
1557 - We have a new "lowest-level" error-handling API for use by code
1558 invoked from within the logging module. With this interface, the
1559 logging code is no longer at risk of calling into itself if a
1560 failure occurs while it is trying to log something. Closes
1563 o Minor features (compilation):
1564 - Tor's configure script now supports a --with-malloc= option to
1565 select your malloc implementation. Supported options are
1566 "tcmalloc", "jemalloc", "openbsd" (deprecated), and "system" (the
1567 default). Addresses part of ticket 20424. Based on a patch from
1570 o Minor features (config):
1571 - The "auto" keyword in torrc is now case-insensitive. Closes
1574 o Minor features (continuous integration):
1575 - Don't do a distcheck with --disable-module-dirauth in Travis.
1576 Implements ticket 27252.
1577 - Install libcap-dev and libseccomp2-dev so these optional
1578 dependencies get tested on Travis CI. Closes ticket 26560.
1579 - Only run one online rust build in Travis, to reduce network
1580 errors. Skip offline rust builds on Travis for Linux gcc, because
1581 they're redundant. Implements ticket 27252.
1582 - Skip gcc on OSX in Travis CI, because it's rarely used. Skip a
1583 duplicate hardening-off build in Travis on Tor 0.2.9. Skip gcc on
1584 Linux with default settings, because all the non-default builds
1585 use gcc on Linux. Implements ticket 27252.
1587 o Minor features (controller):
1588 - Emit CIRC_BW events as soon as we detect that we processed an
1589 invalid or otherwise dropped cell on a circuit. This allows
1590 vanguards and other controllers to react more quickly to dropped
1591 cells. Closes ticket 27678.
1592 - For purposes of CIRC_BW-based dropped cell detection, track half-
1593 closed stream ids, and allow their ENDs, SENDMEs, DATA and path
1594 bias check cells to arrive without counting it as dropped until
1595 either the END arrives, or the windows are empty. Closes
1597 - Implement a 'GETINFO md/all' controller command to enable getting
1598 all known microdescriptors. Closes ticket 8323.
1599 - The GETINFO command now support an "uptime" argument, to return
1600 Tor's uptime in seconds. Closes ticket 25132.
1602 o Minor features (denial-of-service avoidance):
1603 - Make our OOM handler aware of the DNS cache so that it doesn't
1604 fill up the memory. This check is important for our DoS mitigation
1605 subsystem. Closes ticket 18642. Patch by Neel Chauhan.
1607 o Minor features (development):
1608 - Tor's makefile now supports running the "clippy" Rust style tool
1609 on our Rust code. Closes ticket 22156.
1611 o Minor features (directory authority):
1612 - There is no longer an artificial upper limit on the length of
1613 bandwidth lines. Closes ticket 26223.
1614 - When a bandwidth file is used to obtain the bandwidth measurements,
1615 include this bandwidth file headers in the votes. Closes
1617 - Improved support for networks with only a single authority or a
1618 single fallback directory. Patch from Gabriel Somlo. Closes
1621 o Minor features (embedding API):
1622 - The Tor controller API now supports a function to launch Tor with
1623 a preconstructed owning controller FD, so that embedding
1624 applications don't need to manage controller ports and
1625 authentication. Closes ticket 24204.
1626 - The Tor controller API now has a function that returns the name
1627 and version of the backend implementing the API. Closes
1630 o Minor features (geoip):
1631 - Update geoip and geoip6 to the September 6 2018 Maxmind GeoLite2
1632 Country database. Closes ticket 27631.
1634 o Minor features (memory management):
1635 - Get Libevent to use the same memory allocator as Tor, by calling
1636 event_set_mem_functions() during initialization. Resolves
1639 o Minor features (memory usage):
1640 - When not using them, store legacy TAP public onion keys in DER-
1641 encoded format, rather than as expanded public keys. This should
1642 save several megabytes on typical clients. Closes ticket 27246.
1644 o Minor features (OpenSSL):
1645 - When possible, use RFC5869 HKDF implementation from OpenSSL rather
1646 than our own. Resolves ticket 19979.
1648 o Minor features (Rust, code quality):
1649 - Improve rust code quality in the rust protover implementation by
1650 making it more idiomatic. Includes changing an internal API to
1651 take &str instead of &String. Closes ticket 26492.
1653 o Minor features (testing):
1654 - Add scripts/test/chutney-git-bisect.sh, for bisecting using
1655 chutney. Implements ticket 27211.
1657 o Minor features (tor-resolve):
1658 - The tor-resolve utility can now be used with IPv6 SOCKS proxies.
1659 Side-effect of the refactoring for ticket 26526.
1661 o Minor features (UI):
1662 - Log each included configuration file or directory as we read it,
1663 to provide more visibility about where Tor is reading from. Patch
1664 from Unto Sten; closes ticket 27186.
1665 - Lower log level of "Scheduler type KIST has been enabled" to INFO.
1666 Closes ticket 26703.
1668 o Minor bugfixes (bootstrap):
1669 - Try harder to get descriptors in non-exit test networks, by using
1670 the mid weight for the third hop when there are no exits. Fixes
1671 bug 27237; bugfix on 0.2.6.2-alpha.
1673 o Minor bugfixes (C correctness):
1674 - Avoid casting smartlist index to int implicitly, as it may trigger
1675 a warning (-Wshorten-64-to-32). Fixes bug 26282; bugfix on
1676 0.2.3.13-alpha, 0.2.7.1-alpha and 0.2.1.1-alpha.
1677 - Use time_t for all values in
1678 predicted_ports_prediction_time_remaining(). Rework the code that
1679 computes difference between durations/timestamps. Fixes bug 27165;
1680 bugfix on 0.3.1.1-alpha.
1682 o Minor bugfixes (client, memory usage):
1683 - When not running as a directory cache, there is no need to store
1684 the text of the current consensus networkstatus in RAM.
1685 Previously, however, clients would store it anyway, at a cost of
1686 over 5 MB. Now, they do not. Fixes bug 27247; bugfix
1689 o Minor bugfixes (client, reachableaddresses):
1690 - Instead of adding a "reject *:*" line to ReachableAddresses when
1691 loading the configuration, add one to the policy after parsing it
1692 in parse_reachable_addresses(). This prevents extra "reject *.*"
1693 lines from accumulating on reloads. Fixes bug 20874; bugfix on
1694 0.1.1.5-alpha. Patch by Neel Chauhan.
1696 o Minor bugfixes (code quality):
1697 - Rename sandbox_getaddrinfo() and other functions to no longer
1698 misleadingly suggest that they are sandbox-only. Fixes bug 26525;
1699 bugfix on 0.2.7.1-alpha.
1701 o Minor bugfixes (configuration, Onion Services):
1702 - In rend_service_parse_port_config(), disallow any input to remain
1703 after address-port pair was parsed. This will catch address and
1704 port being whitespace-separated by mistake of the user. Fixes bug
1705 27044; bugfix on 0.2.9.10.
1707 o Minor bugfixes (continuous integration):
1708 - Stop reinstalling identical packages in our Windows CI. Fixes bug
1709 27464; bugfix on 0.3.4.1-alpha.
1711 o Minor bugfixes (controller):
1712 - Consider all routerinfo errors other than "not a server" to be
1713 transient for the purpose of "GETINFO exit-policy/*" controller
1714 request. Print stacktrace in the unlikely case of failing to
1715 recompute routerinfo digest. Fixes bug 27034; bugfix
1718 o Minor bugfixes (directory connection shutdown):
1719 - Avoid a double-close when shutting down a stalled directory
1720 connection. Fixes bug 26896; bugfix on 0.3.4.1-alpha.
1722 o Minor bugfixes (HTTP tunnel):
1723 - Fix a bug warning when closing an HTTP tunnel connection due to an
1724 HTTP request we couldn't handle. Fixes bug 26470; bugfix
1727 o Minor bugfixes (ipv6):
1728 - In addrs_in_same_network_family(), we choose the subnet size based
1729 on the IP version (IPv4 or IPv6). Previously, we chose a fixed
1730 subnet size of /16 for both IPv4 and IPv6 addresses. Fixes bug
1731 15518; bugfix on 0.2.3.1-alpha. Patch by Neel Chauhan.
1733 o Minor bugfixes (logging):
1734 - As a precaution, do an early return from log_addr_has_changed() if
1735 Tor is running as client. Also, log a stack trace for debugging as
1736 this function should only be called when Tor runs as server. Fixes
1737 bug 26892; bugfix on 0.1.1.9-alpha.
1738 - Refrain from mentioning bug 21018 in the logs, as it is already
1739 fixed. Fixes bug 25477; bugfix on 0.2.9.8.
1741 o Minor bugfixes (logging, documentation):
1742 - When SafeLogging is enabled, scrub IP address in
1743 channel_tls_process_netinfo_cell(). Also, add a note to manpage
1744 that scrubbing is not guaranteed on loglevels below Notice. Fixes
1745 bug 26882; bugfix on 0.2.4.10-alpha.
1747 o Minor bugfixes (netflow padding):
1748 - Ensure circuitmux queues are empty before scheduling or sending
1749 padding. Fixes bug 25505; bugfix on 0.3.1.1-alpha.
1751 o Minor bugfixes (onion service v2):
1752 - Log at level "info", not "warning", in the case that we do not
1753 have a consensus when a .onion request comes in. This can happen
1754 normally while bootstrapping. Fixes bug 27040; bugfix
1757 o Minor bugfixes (onion service v3):
1758 - When the onion service directory can't be created or has the wrong
1759 permissions, do not log a stack trace. Fixes bug 27335; bugfix
1762 o Minor bugfixes (OS compatibility):
1763 - Properly handle configuration changes that move a listener to/from
1764 wildcard IP address. If the first attempt to bind a socket fails,
1765 close the old listener and try binding the socket again. Fixes bug
1766 17873; bugfix on 0.0.8pre-1.
1768 o Minor bugfixes (performance)::
1769 - Rework node_is_a_configured_bridge() to no longer call
1770 node_get_all_orports(), which was performing too many memory
1771 allocations. Fixes bug 27224; bugfix on 0.2.3.9.
1773 o Minor bugfixes (relay statistics):
1774 - Update relay descriptor on bandwidth changes only when the uptime
1775 is smaller than 24h, in order to reduce the efficiency of guard
1776 discovery attacks. Fixes bug 24104; bugfix on 0.1.1.6-alpha.
1778 o Minor bugfixes (relays):
1779 - Consider the fact that we'll be making direct connections to our
1780 entry and guard nodes when computing the fraction of nodes that
1781 have their descriptors. Also, if we are using bridges and there is
1782 at least one bridge with a full descriptor, treat the fraction of
1783 guards available as 100%. Fixes bug 25886; bugfix on 0.2.4.10-alpha.
1784 Patch by Neel Chauhan.
1785 - Update the message logged on relays when DirCache is disabled.
1786 Since 0.3.3.5-rc, authorities require DirCache (V2Dir) for the
1787 Guard flag. Fixes bug 24312; bugfix on 0.3.3.5-rc.
1789 o Minor bugfixes (rust, protover):
1790 - Compute protover votes correctly in the rust version of the
1791 protover code. Previously, the protover rewrite in 24031 allowed
1792 repeated votes from the same voter for the same protocol version
1793 to be counted multiple times in protover_compute_vote(). Fixes bug
1794 27649; bugfix on 0.3.3.5-rc.
1795 - Reject protover names that contain invalid characters. Fixes bug
1796 27687; bugfix on 0.3.3.1-alpha.
1798 o Minor bugfixes (testing):
1799 - Fix two unit tests to work when HOME environment variable is not
1800 set. Fixes bug 27096; bugfix on 0.2.8.1-alpha.
1801 - If a unit test running in a subprocess exits abnormally or with a
1802 nonzero status code, treat the test as having failed, even if the
1803 test reported success. Without this fix, memory leaks don't cause
1804 the tests to fail, even with LeakSanitizer. Fixes bug 27658;
1805 bugfix on 0.2.2.4-alpha.
1806 - When logging a version mismatch in our openssl_version tests,
1807 report the actual offending version strings. Fixes bug 26152;
1808 bugfix on 0.2.9.1-alpha.
1809 - Fix forking tests on Windows when there is a space somewhere in
1810 the path. Fixes bug 26437; bugfix on 0.2.2.4-alpha.
1812 o Code simplification and refactoring:
1813 - 'updateFallbackDirs.py' now ignores the blacklist file, as it's not
1814 longer needed. Closes ticket 26502.
1815 - Include paths to header files within Tor are now qualified by
1816 directory within the top-level src directory.
1817 - Many structures have been removed from the centralized "or.h"
1818 header, and moved into their own headers. This will allow us to
1819 reduce the number of places in the code that rely on each
1820 structure's contents and layout. Closes ticket 26383.
1821 - Remove ATTR_NONNULL macro from codebase. Resolves ticket 26527.
1822 - Remove GetAdaptersAddresses_fn_t. The code that used it was
1823 removed as part of the 26481 refactor. Closes ticket 27467.
1824 - Rework Tor SOCKS server code to use Trunnel and benefit from
1825 autogenerated functions for parsing and generating SOCKS wire
1826 format. New implementation is cleaner, more maintainable and
1827 should be less prone to heartbleed-style vulnerabilities.
1828 Implements a significant fraction of ticket 3569.
1829 - Split sampled_guards_update_from_consensus() and
1830 select_entry_guard_for_circuit() into subfunctions. In
1831 entry_guards_update_primary() unite three smartlist enumerations
1832 into one and move smartlist comparison code out of the function.
1833 Closes ticket 21349.
1834 - Tor now assumes that you have standards-conformant stdint.h and
1835 inttypes.h headers when compiling. Closes ticket 26626.
1836 - Unify our bloom filter logic. Previously we had two copies of this
1837 code: one for routerlist filtering, and one for address set
1838 calculations. Closes ticket 26510.
1839 - Use the simpler strcmpstart() helper in
1840 rend_parse_v2_service_descriptor instead of strncmp(). Closes
1842 - Utility functions that can perform a DNS lookup are now wholly
1843 separated from those that can't, in separate headers and C
1844 modules. Closes ticket 26526.
1847 - Copy paragraph and URL to Tor's code of conduct document from
1848 CONTRIBUTING to new CODE_OF_CONDUCT file. Resolves ticket 26638.
1849 - Remove old instructions from INSTALL document. Closes ticket 26588.
1850 - Warn users that they should not include MyFamily line(s) in their
1851 torrc when running Tor bridge. Closes ticket 26908.
1854 - Tor no longer supports building with the dmalloc library. For
1855 debugging memory issues, we suggest using gperftools or msan
1856 instead. Closes ticket 26426.
1857 - Tor no longer attempts to run on Windows environments without the
1858 GetAdaptersAddresses() function. This function has existed since
1859 Windows XP, which is itself already older than we support.
1860 - Remove Tor2web functionality for version 2 onion services. The
1861 Tor2webMode and Tor2webRendezvousPoints options are now obsolete.
1862 (This feature was never shipped in vanilla Tor and it was only
1863 possible to use this feature by building the support at compile
1864 time. Tor2webMode is not implemented for version 3 onion services.)
1865 Closes ticket 26367.
1868 Changes in version 0.2.9.17 - 2018-09-10
1869 Tor 0.2.9.17 backports numerous bugfixes from later versions of Tor.
1871 o Minor features (compatibility, backport from 0.3.4.8):
1872 - Tell OpenSSL to maintain backward compatibility with previous
1873 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
1874 ciphers are disabled by default. Closes ticket 27344.
1876 o Minor features (continuous integration, backport from 0.3.4.7-rc):
1877 - Enable macOS builds in our Travis CI configuration. Closes
1879 - Install libcap-dev and libseccomp2-dev so these optional
1880 dependencies get tested on Travis CI. Closes ticket 26560.
1881 - Run asciidoc during Travis CI. Implements ticket 27087.
1882 - Use ccache in our Travis CI configuration. Closes ticket 26952.
1884 o Minor features (geoip):
1885 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
1886 Country database. Closes ticket 27089.
1888 o Minor bugfixes (compilation, backport from 0.3.4.6-rc):
1889 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
1890 tell the compiler not to include the system malloc implementation.
1891 Fixes bug 20424; bugfix on 0.2.0.20-rc.
1893 o Minor bugfixes (compilation, backport from 0.3.4.7-rc):
1894 - Silence a spurious compiler warning on the GetAdaptersAddresses
1895 function pointer cast. This issue is already fixed by 26481 in
1896 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
1897 bugfix on 0.2.3.11-alpha.
1898 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
1899 supported, and always fails. Some compilers warn about the
1900 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
1903 o Minor bugfixes (compilation, windows, backport from 0.3.4.7-rc):
1904 - Don't link or search for pthreads when building for Windows, even
1905 if we are using build environment (like mingw) that provides a
1906 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
1908 o Minor bugfixes (continuous integration, backport from 0.3.4.6-rc):
1909 - Skip a pair of unreliable key generation tests on Windows, until
1910 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
1911 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
1913 o Minor bugfixes (continuous integration, backport from 0.3.4.7-rc):
1914 - Pass the module flags to distcheck configure, and log the flags
1915 before running configure. (Backported to 0.2.9 and later as a
1916 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
1918 o Minor bugfixes (continuous integration, backport from 0.3.4.8):
1919 - When a Travis build fails, and showing a log fails, keep trying to
1920 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
1921 - When we use echo in Travis, don't pass a --flag as the first
1922 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
1924 o Minor bugfixes (directory authority, backport from 0.3.4.6-rc):
1925 - When voting for recommended versions, make sure that all of the
1926 versions are well-formed and parsable. Fixes bug 26485; bugfix
1929 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.4.7-rc):
1930 - Fix a bug in out sandboxing rules for the openat() syscall.
1931 Previously, no openat() call would be permitted, which would break
1932 filesystem operations on recent glibc versions. Fixes bug 25440;
1933 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
1935 o Minor bugfixes (onion services, backport from 0.3.4.8):
1936 - Silence a spurious compiler warning in
1937 rend_client_send_introduction(). Fixes bug 27463; bugfix
1940 o Minor bugfixes (single onion services, Tor2web, backport from 0.3.4.6-rc):
1941 - Log a protocol warning when single onion services or Tor2web clients
1942 fail to authenticate direct connections to relays.
1943 Fixes bug 26924; bugfix on 0.2.9.1-alpha.
1945 o Minor bugfixes (testing, backport from 0.3.4.6-rc):
1946 - Disable core dumps in test_bt.sh, to avoid failures in "make
1947 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
1949 o Minor bugfixes (testing, chutney, backport from 0.3.4.8):
1950 - Before running make test-network-all, delete old logs and test
1951 result files, to avoid spurious failures. Fixes bug 27295; bugfix
1954 o Minor bugfixes (testing, openssl compatibility, backport from 0.3.4.7-rc):
1955 - Our "tortls/cert_matches_key" unit test no longer relies on
1956 OpenSSL internals. Previously, it relied on unsupported OpenSSL
1957 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
1958 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
1960 o Minor bugfixes (Windows, compilation, backport from 0.3.4.7-rc):
1961 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
1962 27185; bugfix on 0.2.2.2-alpha.
1965 Changes in version 0.3.2.12 - 2018-09-10
1966 Tor 0.3.2.12 backport numerous fixes from later versions of Tor.
1968 o Minor features (compatibility, backport from 0.3.4.8):
1969 - Tell OpenSSL to maintain backward compatibility with previous
1970 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
1971 ciphers are disabled by default. Closes ticket 27344.
1973 o Minor features (continuous integration, backport from 0.3.4.7-rc):
1974 - Enable macOS builds in our Travis CI configuration. Closes
1976 - Install libcap-dev and libseccomp2-dev so these optional
1977 dependencies get tested on Travis CI. Closes ticket 26560.
1978 - Run asciidoc during Travis CI. Implements ticket 27087.
1979 - Use ccache in our Travis CI configuration. Closes ticket 26952.
1981 o Minor features (continuous integration, rust, backport from 0.3.4.7-rc):
1982 - Use cargo cache in our Travis CI configuration. Closes
1985 o Minor features (controller, backport from 0.3.4.6-rc):
1986 - The control port now exposes the list of HTTPTunnelPorts and
1987 ExtOrPorts via GETINFO net/listeners/httptunnel and
1988 net/listeners/extor respectively. Closes ticket 26647.
1990 o Minor features (directory authorities, backport from 0.3.4.7-rc):
1991 - Authorities no longer vote to make the subprotocol version
1992 "LinkAuth=1" a requirement: it is unsupportable with NSS, and
1993 hasn't been needed since Tor 0.3.0.1-alpha. Closes ticket 27286.
1995 o Minor features (geoip):
1996 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
1997 Country database. Closes ticket 27089.
1999 o Minor bugfixes (compilation, backport from 0.3.4.6-rc):
2000 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
2001 tell the compiler not to include the system malloc implementation.
2002 Fixes bug 20424; bugfix on 0.2.0.20-rc.
2003 - Don't try to use a pragma to temporarily disable the
2004 -Wunused-const-variable warning if the compiler doesn't support
2005 it. Fixes bug 26785; bugfix on 0.3.2.11.
2007 o Minor bugfixes (compilation, backport from 0.3.4.7-rc):
2008 - Silence a spurious compiler warning on the GetAdaptersAddresses
2009 function pointer cast. This issue is already fixed by 26481 in
2010 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
2011 bugfix on 0.2.3.11-alpha.
2012 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
2013 supported, and always fails. Some compilers warn about the
2014 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
2017 o Minor bugfixes (compilation, windows, backport from 0.3.4.7-rc):
2018 - Don't link or search for pthreads when building for Windows, even
2019 if we are using build environment (like mingw) that provides a
2020 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
2022 o Minor bugfixes (continuous integration, backport from 0.3.4.6-rc):
2023 - Skip a pair of unreliable key generation tests on Windows, until
2024 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
2025 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
2027 o Minor bugfixes (continuous integration, backport from 0.3.4.7-rc):
2028 - Build with zstd on macOS. Fixes bug 27090; bugfix on 0.3.1.5-alpha.
2029 - Pass the module flags to distcheck configure, and log the flags
2030 before running configure. (Backported to 0.2.9 and later as a
2031 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
2033 o Minor bugfixes (continuous integration, backport from 0.3.4.8):
2034 - When a Travis build fails, and showing a log fails, keep trying to
2035 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
2036 - When we use echo in Travis, don't pass a --flag as the first
2037 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
2039 o Minor bugfixes (directory authority, backport from 0.3.4.6-rc):
2040 - When voting for recommended versions, make sure that all of the
2041 versions are well-formed and parsable. Fixes bug 26485; bugfix
2044 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.4.7-rc):
2045 - Fix a bug in out sandboxing rules for the openat() syscall.
2046 Previously, no openat() call would be permitted, which would break
2047 filesystem operations on recent glibc versions. Fixes bug 25440;
2048 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
2050 o Minor bugfixes (logging, backport from 0.3.4.6-rc):
2051 - Improve the log message when connection initiators fail to
2052 authenticate direct connections to relays. Fixes bug 26927; bugfix
2055 o Minor bugfixes (onion services, backport from 0.3.4.7-rc):
2056 - Fix bug that causes services to not ever rotate their descriptors
2057 if they were getting SIGHUPed often. Fixes bug 26932; bugfix
2060 o Minor bugfixes (onion services, backport from 0.3.4.8):
2061 - Silence a spurious compiler warning in
2062 rend_client_send_introduction(). Fixes bug 27463; bugfix
2065 o Minor bugfixes (rust, backport from 0.3.4.7-rc):
2066 - Backport test_rust.sh from master. Fixes bug 26497; bugfix
2068 - Consistently use ../../.. as a fallback for $abs_top_srcdir in
2069 test_rust.sh. Fixes bug 27093; bugfix on 0.3.4.3-alpha.
2070 - Stop setting $CARGO_HOME. cargo will use the user's $CARGO_HOME, or
2071 $HOME/.cargo by default. Fixes bug 26497; bugfix on 0.3.1.5-alpha.
2073 o Minor bugfixes (single onion services, Tor2web, backport from 0.3.4.6-rc):
2074 - Log a protocol warning when single onion services or Tor2web clients
2075 fail to authenticate direct connections to relays.
2076 Fixes bug 26924; bugfix on 0.2.9.1-alpha.
2078 o Minor bugfixes (testing, backport from 0.3.4.6-rc):
2079 - Disable core dumps in test_bt.sh, to avoid failures in "make
2080 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
2082 o Minor bugfixes (testing, chutney, backport from 0.3.4.8):
2083 - When running make test-network-all, use the mixed+hs-v2 network.
2084 (A previous fix to chutney removed v3 onion services from the
2085 mixed+hs-v23 network, so seeing "mixed+hs-v23" in tests is
2086 confusing.) Fixes bug 27345; bugfix on 0.3.2.1-alpha.
2087 - Before running make test-network-all, delete old logs and test
2088 result files, to avoid spurious failures. Fixes bug 27295; bugfix
2091 o Minor bugfixes (testing, openssl compatibility):
2092 - Our "tortls/cert_matches_key" unit test no longer relies on OpenSSL
2093 internals. Previously, it relied on unsupported OpenSSL behavior in
2094 a way that caused it to crash with OpenSSL 1.0.2p. Fixes bug 27226;
2095 bugfix on 0.2.5.1-alpha.
2097 o Minor bugfixes (testing, openssl compatibility, backport from 0.3.4.7-rc):
2098 - Our "tortls/cert_matches_key" unit test no longer relies on
2099 OpenSSL internals. Previously, it relied on unsupported OpenSSL
2100 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
2101 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
2103 o Minor bugfixes (Windows, compilation, backport from 0.3.4.7-rc):
2104 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
2105 27185; bugfix on 0.2.2.2-alpha.
2108 Changes in version 0.3.3.10 - 2018-09-10
2109 Tor 0.3.3.10 backports numerous fixes from later versions of Tor.
2111 o Minor features (bug workaround, backport from 0.3.4.7-rc):
2112 - Compile correctly on systems that provide the C11 stdatomic.h
2113 header, but where C11 atomic functions don't actually compile.
2114 Closes ticket 26779; workaround for Debian issue 903709.
2116 o Minor features (compatibility, backport from 0.3.4.8):
2117 - Tell OpenSSL to maintain backward compatibility with previous
2118 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
2119 ciphers are disabled by default. Closes ticket 27344.
2121 o Minor features (continuous integration, backport from 0.3.4.7-rc):
2122 - Backport Travis rust distcheck to 0.3.3. Closes ticket 24629.
2123 - Enable macOS builds in our Travis CI configuration. Closes
2125 - Install libcap-dev and libseccomp2-dev so these optional
2126 dependencies get tested on Travis CI. Closes ticket 26560.
2127 - Run asciidoc during Travis CI. Implements ticket 27087.
2128 - Use ccache in our Travis CI configuration. Closes ticket 26952.
2130 o Minor features (continuous integration, rust, backport from 0.3.4.7-rc):
2131 - Use cargo cache in our Travis CI configuration. Closes
2134 o Minor features (controller, backport from 0.3.4.6-rc):
2135 - The control port now exposes the list of HTTPTunnelPorts and
2136 ExtOrPorts via GETINFO net/listeners/httptunnel and
2137 net/listeners/extor respectively. Closes ticket 26647.
2139 o Minor features (directory authorities, backport from 0.3.4.7-rc):
2140 - Authorities no longer vote to make the subprotocol version
2141 "LinkAuth=1" a requirement: it is unsupportable with NSS, and
2142 hasn't been needed since Tor 0.3.0.1-alpha. Closes ticket 27286.
2144 o Minor features (geoip):
2145 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
2146 Country database. Closes ticket 27089.
2148 o Minor bugfixes (compilation, backport from 0.3.4.6-rc):
2149 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
2150 tell the compiler not to include the system malloc implementation.
2151 Fixes bug 20424; bugfix on 0.2.0.20-rc.
2152 - Don't try to use a pragma to temporarily disable the
2153 -Wunused-const-variable warning if the compiler doesn't support
2154 it. Fixes bug 26785; bugfix on 0.3.2.11.
2156 o Minor bugfixes (compilation, backport from 0.3.4.7-rc):
2157 - Silence a spurious compiler warning on the GetAdaptersAddresses
2158 function pointer cast. This issue is already fixed by 26481 in
2159 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
2160 bugfix on 0.2.3.11-alpha.
2161 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
2162 supported, and always fails. Some compilers warn about the
2163 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
2166 o Minor bugfixes (compilation, windows, backport from 0.3.4.7-rc):
2167 - Don't link or search for pthreads when building for Windows, even
2168 if we are using build environment (like mingw) that provides a
2169 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
2171 o Minor bugfixes (continuous integration, backport from 0.3.4.6-rc):
2172 - Skip a pair of unreliable key generation tests on Windows, until
2173 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
2174 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
2176 o Minor bugfixes (continuous integration, backport from 0.3.4.7-rc):
2177 - Build with zstd on macOS. Fixes bug 27090; bugfix on 0.3.1.5-alpha.
2178 - Pass the module flags to distcheck configure, and log the flags
2179 before running configure. (Backported to 0.2.9 and later as a
2180 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
2182 o Minor bugfixes (continuous integration, backport from 0.3.4.8):
2183 - When a Travis build fails, and showing a log fails, keep trying to
2184 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
2185 - When we use echo in Travis, don't pass a --flag as the first
2186 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
2188 o Minor bugfixes (directory authority, backport from 0.3.4.6-rc):
2189 - When voting for recommended versions, make sure that all of the
2190 versions are well-formed and parsable. Fixes bug 26485; bugfix
2193 o Minor bugfixes (in-process restart, backport from 0.3.4.7-rc):
2194 - Always call tor_free_all() when leaving tor_run_main(). When we
2195 did not, restarting tor in-process would cause an assertion
2196 failure. Fixes bug 26948; bugfix on 0.3.3.1-alpha.
2198 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.4.7-rc):
2199 - Fix a bug in our sandboxing rules for the openat() syscall.
2200 Previously, no openat() call would be permitted, which would break
2201 filesystem operations on recent glibc versions. Fixes bug 25440;
2202 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
2204 o Minor bugfixes (logging, backport from 0.3.4.6-rc):
2205 - Improve the log message when connection initiators fail to
2206 authenticate direct connections to relays. Fixes bug 26927; bugfix
2209 o Minor bugfixes (onion services, backport from 0.3.4.7-rc):
2210 - Fix bug that causes services to not ever rotate their descriptors
2211 if they were getting SIGHUPed often. Fixes bug 26932; bugfix
2214 o Minor bugfixes (onion services, backport from 0.3.4.8):
2215 - Silence a spurious compiler warning in
2216 rend_client_send_introduction(). Fixes bug 27463; bugfix
2219 o Minor bugfixes (portability, backport from 0.3.4.6-rc):
2220 - Work around two different bugs in the OS X 10.10 and later SDKs
2221 that would prevent us from successfully targeting earlier versions
2222 of OS X. Fixes bug 26876; bugfix on 0.3.3.1-alpha.
2224 o Minor bugfixes (portability, backport from 0.3.4.7-rc):
2225 - Fix compilation of the unit tests on GNU/Hurd, which does not
2226 define PATH_MAX. Fixes bug 26873; bugfix on 0.3.3.1-alpha. Patch
2229 o Minor bugfixes (rust, backport from 0.3.4.7-rc):
2230 - Backport test_rust.sh from master. Fixes bug 26497; bugfix
2232 - Consistently use ../../.. as a fallback for $abs_top_srcdir in
2233 test_rust.sh. Fixes bug 27093; bugfix on 0.3.4.3-alpha.
2234 - Protover parsing was accepting the presence of whitespace in
2235 version strings, which the C implementation would choke on, e.g.
2236 "Desc=1\t,2". Fixes bug 27177; bugfix on 0.3.3.5-rc.
2237 - Protover parsing was ignoring a 2nd hyphen and everything after
2238 it, accepting entries like "Link=1-5-foo". Fixes bug 27164; bugfix
2240 - Stop setting $CARGO_HOME. cargo will use the user's $CARGO_HOME, or
2241 $HOME/.cargo by default. Fixes bug 26497; bugfix on 0.3.1.5-alpha.
2242 - cd to ${abs_top_builddir}/src/rust before running cargo in
2243 src/test/test_rust.sh. This makes the working directory consistent
2244 between builds and tests. Fixes bug 26497; bugfix on 0.3.3.2-alpha.
2246 o Minor bugfixes (single onion services, Tor2web, backport from 0.3.4.6-rc):
2247 - Log a protocol warning when single onion services or Tor2web clients
2248 fail to authenticate direct connections to relays.
2249 Fixes bug 26924; bugfix on 0.2.9.1-alpha.
2251 o Minor bugfixes (testing, backport from 0.3.4.6-rc):
2252 - Disable core dumps in test_bt.sh, to avoid failures in "make
2253 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
2255 o Minor bugfixes (testing, chutney, backport from 0.3.4.8):
2256 - When running make test-network-all, use the mixed+hs-v2 network.
2257 (A previous fix to chutney removed v3 onion services from the
2258 mixed+hs-v23 network, so seeing "mixed+hs-v23" in tests is
2259 confusing.) Fixes bug 27345; bugfix on 0.3.2.1-alpha.
2260 - Before running make test-network-all, delete old logs and test
2261 result files, to avoid spurious failures. Fixes bug 27295; bugfix
2264 o Minor bugfixes (testing, openssl compatibility, backport from 0.3.4.7-rc):
2265 - Our "tortls/cert_matches_key" unit test no longer relies on
2266 OpenSSL internals. Previously, it relied on unsupported OpenSSL
2267 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
2268 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
2270 o Minor bugfixes (v3 onion services, backport from 0.3.4.6-rc):
2271 - Stop sending ed25519 link specifiers in v3 onion service introduce
2272 cells and descriptors, when the rendezvous or introduction point
2273 doesn't support ed25519 link authentication. Fixes bug 26627;
2274 bugfix on 0.3.2.4-alpha.
2276 o Minor bugfixes (Windows, compilation, backport from 0.3.4.7-rc):
2277 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
2278 27185; bugfix on 0.2.2.2-alpha.
2281 Changes in version 0.3.4.8 - 2018-09-10
2282 Tor 0.3.4.8 is the first stable release in its series; it includes
2283 compilation and portability fixes.
2285 The Tor 0.3.4 series includes improvements for running Tor in
2286 low-power and embedded environments, which should help performance in
2287 general. We've begun work on better modularity, and included preliminary
2288 changes on the directory authority side to accommodate a new bandwidth
2289 measurement system. We've also integrated more continuous-integration
2290 systems into our development process, and made corresponding changes to
2291 Tor's testing infrastructure. Finally, we've continued to refine
2292 our anti-denial-of-service code.
2294 Below are the changes since 0.3.4.7-rc. For a complete list of changes
2295 since 0.3.3.9, see the ReleaseNotes file.
2297 o Minor features (compatibility):
2298 - Tell OpenSSL to maintain backward compatibility with previous
2299 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
2300 ciphers are disabled by default. Closes ticket 27344.
2302 o Minor features (continuous integration):
2303 - Log the compiler path and version during Appveyor builds.
2304 Implements ticket 27449.
2305 - Show config.log and test-suite.log after failed Appveyor builds.
2306 Also upload the zipped full logs as a build artifact. Implements
2309 o Minor bugfixes (compilation):
2310 - Silence a spurious compiler warning on the GetAdaptersAddresses
2311 function pointer cast. This issue is already fixed by 26481 in
2312 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
2313 bugfix on 0.2.3.11-alpha.
2314 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
2315 supported, and always fails. Some compilers warn about the
2316 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
2319 o Minor bugfixes (continuous integration):
2320 - Disable gcc hardening in Appveyor Windows 64-bit builds. As of
2321 August 29 2018, Appveyor images come with gcc 8.2.0 by default.
2322 Executables compiled for 64-bit Windows with this version of gcc
2323 crash when Tor's --enable-gcc-hardening flag is set. Fixes bug
2324 27460; bugfix on 0.3.4.1-alpha.
2325 - When a Travis build fails, and showing a log fails, keep trying to
2326 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
2327 - When we use echo in Travis, don't pass a --flag as the first
2328 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
2330 o Minor bugfixes (onion services):
2331 - Silence a spurious compiler warning in
2332 rend_client_send_introduction(). Fixes bug 27463; bugfix
2335 o Minor bugfixes (testing, chutney):
2336 - When running make test-network-all, use the mixed+hs-v2 network.
2337 (A previous fix to chutney removed v3 onion services from the
2338 mixed+hs-v23 network, so seeing "mixed+hs-v23" in tests is
2339 confusing.) Fixes bug 27345; bugfix on 0.3.2.1-alpha.
2340 - Before running make test-network-all, delete old logs and test
2341 result files, to avoid spurious failures. Fixes bug 27295; bugfix
2344 Changes in version 0.3.4.7-rc - 2018-08-24
2345 Tor 0.3.4.7-rc fixes several small compilation, portability, and
2346 correctness issues in previous versions of Tor. This version is a
2347 release candidate: if no serious bugs are found, we expect that the
2348 stable 0.3.4 release will be (almost) the same as this release.
2350 o Minor features (bug workaround):
2351 - Compile correctly on systems that provide the C11 stdatomic.h
2352 header, but where C11 atomic functions don't actually compile.
2353 Closes ticket 26779; workaround for Debian issue 903709.
2355 o Minor features (continuous integration):
2356 - Backport Travis rust distcheck to 0.3.3. Closes ticket 24629.
2357 - Enable macOS builds in our Travis CI configuration. Closes
2359 - Install libcap-dev and libseccomp2-dev so these optional
2360 dependencies get tested on Travis CI. Closes ticket 26560.
2361 - Only post Appveyor IRC notifications when the build fails.
2362 Implements ticket 27275.
2363 - Run asciidoc during Travis CI. Implements ticket 27087.
2364 - Use ccache in our Travis CI configuration. Closes ticket 26952.
2366 o Minor features (continuous integration, rust):
2367 - Use cargo cache in our Travis CI configuration. Closes
2370 o Minor features (directory authorities):
2371 - Authorities no longer vote to make the subprotocol version
2372 "LinkAuth=1" a requirement: it is unsupportable with NSS, and
2373 hasn't been needed since Tor 0.3.0.1-alpha. Closes ticket 27286.
2375 o Minor features (geoip):
2376 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
2377 Country database. Closes ticket 27089.
2379 o Minor bugfixes (compilation, windows):
2380 - Don't link or search for pthreads when building for Windows, even
2381 if we are using build environment (like mingw) that provides a
2382 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
2384 o Minor bugfixes (continuous integration):
2385 - Improve Appveyor CI IRC logging. Generate correct branches and
2386 URLs for pull requests and tags. Use unambiguous short commits.
2387 Fixes bug 26979; bugfix on master.
2388 - Build with zstd on macOS. Fixes bug 27090; bugfix on 0.3.1.5-alpha.
2389 - Pass the module flags to distcheck configure, and log the flags
2390 before running configure. (Backported to 0.2.9 and later as a
2391 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
2393 o Minor bugfixes (in-process restart):
2394 - Always call tor_free_all() when leaving tor_run_main(). When we
2395 did not, restarting tor in-process would cause an assertion
2396 failure. Fixes bug 26948; bugfix on 0.3.3.1-alpha.
2398 o Minor bugfixes (linux seccomp2 sandbox):
2399 - Fix a bug in out sandboxing rules for the openat() syscall.
2400 Previously, no openat() call would be permitted, which would break
2401 filesystem operations on recent glibc versions. Fixes bug 25440;
2402 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
2404 o Minor bugfixes (onion services):
2405 - Fix bug that causes services to not ever rotate their descriptors
2406 if they were getting SIGHUPed often. Fixes bug 26932; bugfix
2409 o Minor bugfixes (portability):
2410 - Fix compilation of the unit tests on GNU/Hurd, which does not
2411 define PATH_MAX. Fixes bug 26873; bugfix on 0.3.3.1-alpha. Patch
2414 o Minor bugfixes (rust):
2415 - Backport test_rust.sh from master. Fixes bug 26497; bugfix
2417 - Consistently use ../../.. as a fallback for $abs_top_srcdir in
2418 test_rust.sh. Fixes bug 27093; bugfix on 0.3.4.3-alpha.
2419 - Protover parsing was accepting the presence of whitespace in
2420 version strings, which the C implementation would choke on, e.g.
2421 "Desc=1\t,2". Fixes bug 27177; bugfix on 0.3.3.5-rc.
2422 - Protover parsing was ignoring a 2nd hyphen and everything after
2423 it, accepting entries like "Link=1-5-foo". Fixes bug 27164; bugfix
2425 - Stop setting $CARGO_HOME. cargo will use the user's $CARGO_HOME, or
2426 $HOME/.cargo by default. Fixes bug 26497; bugfix on 0.3.1.5-alpha.
2427 - cd to ${abs_top_builddir}/src/rust before running cargo in
2428 src/test/test_rust.sh. This makes the working directory consistent
2429 between builds and tests. Fixes bug 26497; bugfix on 0.3.3.2-alpha.
2431 o Minor bugfixes (testing, bootstrap):
2432 - When calculating bootstrap progress, check exit policies and the
2433 exit flag. Previously, Tor would only check the exit flag, which
2434 caused race conditions in small and fast networks like chutney.
2435 Fixes bug 27236; bugfix on 0.2.6.3-alpha.
2437 o Minor bugfixes (testing, openssl compatibility):
2438 - Our "tortls/cert_matches_key" unit test no longer relies on
2439 OpenSSL internals. Previously, it relied on unsupported OpenSSL
2440 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
2441 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
2443 o Minor bugfixes (Windows, compilation):
2444 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
2445 27185; bugfix on 0.2.2.2-alpha.
2448 Changes in version 0.3.4.6-rc - 2018-08-06
2449 Tor 0.3.4.6-rc fixes several small compilation, portability, and
2450 correctness issues in previous versions of Tor. This version is a
2451 release candidate: if no serious bugs are found, we expect that the
2452 stable 0.3.4 release will be (almost) the same as this release.
2454 o Major bugfixes (event scheduler):
2455 - When we enable a periodic event, schedule it in the event loop
2456 rather than running it immediately. Previously, we would re-run
2457 periodic events immediately in the middle of (for example)
2458 changing our options, with unpredictable effects. Fixes bug 27003;
2459 bugfix on 0.3.4.1-alpha.
2461 o Minor features (compilation):
2462 - When building Tor, prefer to use Python 3 over Python 2, and more
2463 recent (contemplated) versions over older ones. Closes
2465 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
2466 tell the compiler not to include the system malloc implementation.
2467 Fixes bug 20424; bugfix on 0.2.0.20-rc.
2468 - Don't try to use a pragma to temporarily disable the
2469 -Wunused-const-variable warning if the compiler doesn't support
2470 it. Fixes bug 26785; bugfix on 0.3.2.11.
2472 o Minor bugfixes (continuous integration):
2473 - Skip a pair of unreliable key generation tests on Windows, until
2474 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
2475 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
2477 o Minor features (controller):
2478 - The control port now exposes the list of HTTPTunnelPorts and
2479 ExtOrPorts via GETINFO net/listeners/httptunnel and
2480 net/listeners/extor respectively. Closes ticket 26647.
2482 o Minor bugfixes (directory authority):
2483 - When voting for recommended versions, make sure that all of the
2484 versions are well-formed and parsable. Fixes bug 26485; bugfix
2487 o Minor features (geoip):
2488 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
2489 Country database. Closes ticket 26674.
2491 o Minor features (Rust, portability):
2492 - Rust cross-compilation is now supported. Closes ticket 25895.
2494 o Minor bugfixes (compilation):
2495 - Update build system so that tor builds again with --disable-unittests
2496 after recent refactoring. Fixes bug 26789; bugfix on 0.3.4.3-alpha.
2497 - Fix a compilation warning on some versions of GCC when building
2498 code that calls routerinfo_get_my_routerinfo() twice, assuming
2499 that the second call will succeed if the first one did. Fixes bug
2500 26269; bugfix on 0.2.8.2-alpha.
2502 o Minor bugfixes (controller):
2503 - Report the port correctly when a port is configured to bind to
2504 "auto". Fixes bug 26568; bugfix on 0.3.4.1-alpha.
2505 - Parse the "HSADDRESS=" parameter in HSPOST commands properly.
2506 Previously, it was misparsed and ignored. Fixes bug 26523; bugfix
2507 on 0.3.3.1-alpha. Patch by "akwizgran".
2509 o Minor bugfixes (correctness, flow control):
2510 - Upon receiving a stream-level SENDME cell, verify that our window
2511 has not grown too large. Fixes bug 26214; bugfix on svn
2514 o Minor bugfixes (memory, correctness):
2515 - Fix a number of small memory leaks identified by coverity. Fixes
2516 bug 26467; bugfix on numerous Tor versions.
2518 o Minor bugfixes (logging):
2519 - Improve the log message when connection initiators fail to
2520 authenticate direct connections to relays. Fixes bug 26927; bugfix
2523 o Minor bugfixes (portability):
2524 - Avoid a compilation error in test_bwmgt.c on Solaris 10. Fixes bug
2525 26994; bugfix on 0.3.4.1-alpha.
2526 - Work around two different bugs in the OS X 10.10 and later SDKs
2527 that would prevent us from successfully targeting earlier versions
2528 of OS X. Fixes bug 26876; bugfix on 0.3.3.1-alpha.
2530 o Minor bugfixes (single onion services, Tor2web):
2531 - Log a protocol warning when single onion services or Tor2web
2532 clients fail to authenticate direct connections to relays. Fixes
2533 bug 26924; bugfix on 0.2.9.1-alpha.
2535 o Minor bugfixes (testing):
2536 - Disable core dumps in test_bt.sh, to avoid failures in "make
2537 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
2539 o Minor bugfixes (testing, compatibility):
2540 - When running the ntor_ref.py and hs_ntor_ref.py tests, make sure
2541 only to pass strings (rather than "bytes" objects) to the Python
2542 subprocess module. Python 3 on Windows seems to require this.
2543 Fixes bug 26535; bugfix on 0.2.5.5-alpha (for ntor_ref.py) and
2544 0.3.1.1-alpha (for hs_ntor_ref.py).
2546 o Minor bugfixes (v3 onion services):
2547 - Stop sending ed25519 link specifiers in v3 onion service introduce
2548 cells and descriptors, when the rendezvous or introduction point
2549 doesn't support ed25519 link authentication. Fixes bug 26627;
2550 bugfix on 0.3.2.4-alpha.
2553 Changes in version 0.3.4.5-rc - 2018-07-13
2554 Tor 0.3.4.5-rc moves to a new bridge authority, meaning people running
2555 bridge relays should upgrade.
2557 o Directory authority changes:
2558 - The "Bifroest" bridge authority has been retired; the new bridge
2559 authority is "Serge", and it is operated by George from the
2560 TorBSD project. Closes ticket 26771.
2563 Changes in version 0.3.3.9 - 2018-07-13
2564 Tor 0.3.3.9 moves to a new bridge authority, meaning people running
2565 bridge relays should upgrade.
2567 o Directory authority changes:
2568 - The "Bifroest" bridge authority has been retired; the new bridge
2569 authority is "Serge", and it is operated by George from the
2570 TorBSD project. Closes ticket 26771.
2573 Changes in version 0.3.2.11 - 2018-07-13
2574 Tor 0.3.2.11 moves to a new bridge authority, meaning people running
2575 bridge relays should upgrade. We also take this opportunity to backport
2578 o Directory authority changes:
2579 - The "Bifroest" bridge authority has been retired; the new bridge
2580 authority is "Serge", and it is operated by George from the
2581 TorBSD project. Closes ticket 26771.
2583 o Directory authority changes (backport from 0.3.3.7):
2584 - Add an IPv6 address for the "dannenberg" directory authority.
2585 Closes ticket 26343.
2587 o Major bugfixes (directory authorities, backport from 0.3.4.1-alpha):
2588 - When directory authorities read a zero-byte bandwidth file, they
2589 would previously log a warning with the contents of an
2590 uninitialised buffer. They now log a warning about the empty file
2591 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
2593 o Major bugfixes (onion service, backport from 0.3.4.1-alpha):
2594 - Correctly detect when onion services get disabled after HUP. Fixes
2595 bug 25761; bugfix on 0.3.2.1.
2597 o Minor features (sandbox, backport from 0.3.3.4-alpha):
2598 - Explicitly permit the poll() system call when the Linux
2599 seccomp2-based sandbox is enabled: apparently, some versions of
2600 libc use poll() when calling getpwnam(). Closes ticket 25313.
2602 o Minor feature (continuous integration, backport from 0.3.3.5-rc):
2603 - Update the Travis CI configuration to use the stable Rust channel,
2604 now that we have decided to require that. Closes ticket 25714.
2606 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
2607 - Our .travis.yml configuration now includes support for testing the
2608 results of "make distcheck". (It's not uncommon for "make check"
2609 to pass but "make distcheck" to fail.) Closes ticket 25814.
2610 - Our Travis CI configuration now integrates with the Coveralls
2611 coverage analysis tool. Closes ticket 25818.
2613 o Minor features (relay, diagnostic, backport from 0.3.4.3-alpha):
2614 - Add several checks to detect whether Tor relays are uploading
2615 their descriptors without specifying why they regenerated them.
2616 Diagnostic for ticket 25686.
2618 o Minor features (compilation, backport from 0.3.4.4-rc):
2619 - When building Tor, prefer to use Python 3 over Python 2, and more
2620 recent (contemplated) versions over older ones. Closes
2623 o Minor features (geoip):
2624 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
2625 Country database. Closes ticket 26674.
2627 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
2628 - Upon receiving a malformed connected cell, stop processing the
2629 cell immediately. Previously we would mark the connection for
2630 close, but continue processing the cell as if the connection were
2631 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
2633 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
2634 - Allow the nanosleep() system call, which glibc uses to implement
2635 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
2637 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
2638 - When running the hs_ntor_ref.py test, make sure only to pass
2639 strings (rather than "bytes" objects) to the Python subprocess
2640 module. Python 3 on Windows seems to require this. Fixes bug
2641 26535; bugfix on 0.3.1.1-alpha.
2642 - When running the ntor_ref.py test, make sure only to pass strings
2643 (rather than "bytes" objects) to the Python subprocess module.
2644 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
2647 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
2648 - Work around a change in OpenSSL 1.1.1 where return values that
2649 would previously indicate "no password" now indicate an empty
2650 password. Without this workaround, Tor instances running with
2651 OpenSSL 1.1.1 would accept descriptors that other Tor instances
2652 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
2654 o Minor bugfixes (documentation, backport from 0.3.3.5-rc):
2655 - Document that the PerConnBW{Rate,Burst} options will fall back to
2656 their corresponding consensus parameters only if those parameters
2657 are set. Previously we had claimed that these values would always
2658 be set in the consensus. Fixes bug 25296; bugfix on 0.2.2.7-alpha.
2660 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
2661 - Fix a compilation warning on some versions of GCC when building
2662 code that calls routerinfo_get_my_routerinfo() twice, assuming
2663 that the second call will succeed if the first one did. Fixes bug
2664 26269; bugfix on 0.2.8.2-alpha.
2666 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
2667 - Don't consider Tor running as a client if the ControlPort is open,
2668 but no actual client ports are open. Fixes bug 26062; bugfix
2671 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
2672 - Prevent a possible out-of-bounds smartlist read in
2673 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
2675 o Minor bugfixes (C correctness, backport from 0.3.3.4-alpha):
2676 - Fix a very unlikely (impossible, we believe) null pointer
2677 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
2678 Coverity; this is CID 1430932.
2680 o Minor bugfixes (onion service, backport from 0.3.4.1-alpha):
2681 - Fix a memory leak when a v3 onion service is configured and gets a
2682 SIGHUP signal. Fixes bug 25901; bugfix on 0.3.2.1-alpha.
2683 - When parsing the descriptor signature, look for the token plus an
2684 extra white-space at the end. This is more correct but also will
2685 allow us to support new fields that might start with "signature".
2686 Fixes bug 26069; bugfix on 0.3.0.1-alpha.
2688 o Minor bugfixes (relay, backport from 0.3.4.3-alpha):
2689 - Relays now correctly block attempts to re-extend to the previous
2690 relay by Ed25519 identity. Previously they would warn in this
2691 case, but not actually reject the attempt. Fixes bug 26158; bugfix
2694 o Minor bugfixes (relay, crash, backport from 0.3.4.1-alpha):
2695 - Avoid a crash when running with DirPort set but ORPort turned off.
2696 Fixes a case of bug 23693; bugfix on 0.3.1.1-alpha.
2698 o Minor bugfixes (compilation, backport from 0.3.4.2-alpha):
2699 - Silence unused-const-variable warnings in zstd.h with some GCC
2700 versions. Fixes bug 26272; bugfix on 0.3.1.1-alpha.
2702 o Minor bugfixes (testing, backport from 0.3.3.4-alpha):
2703 - Avoid intermittent test failures due to a test that had relied on
2704 onion service introduction point creation finishing within 5
2705 seconds of real clock time. Fixes bug 25450; bugfix
2708 o Minor bugfixes (compilation, backport from 0.3.3.4-alpha):
2709 - Fix a C99 compliance issue in our configuration script that caused
2710 compilation issues when compiling Tor with certain versions of
2711 xtools. Fixes bug 25474; bugfix on 0.3.2.5-alpha.
2713 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
2714 - Fix a number of small memory leaks identified by coverity. Fixes
2715 bug 26467; bugfix on numerous Tor versions.
2717 o Code simplification and refactoring (backport from 0.3.3.5-rc):
2718 - Move the list of default directory authorities to its own file.
2719 Closes ticket 24854. Patch by "beastr0".
2722 Changes in version 0.2.9.16 - 2018-07-13
2723 Tor 0.2.9.16 moves to a new bridge authority, meaning people running
2724 bridge relays should upgrade. We also take this opportunity to backport
2727 o Directory authority changes:
2728 - The "Bifroest" bridge authority has been retired; the new bridge
2729 authority is "Serge", and it is operated by George from the
2730 TorBSD project. Closes ticket 26771.
2732 o Directory authority changes (backport from 0.3.3.7):
2733 - Add an IPv6 address for the "dannenberg" directory authority.
2734 Closes ticket 26343.
2736 o Major bugfixes (directory authorities, backport from 0.3.4.1-alpha):
2737 - When directory authorities read a zero-byte bandwidth file, they
2738 would previously log a warning with the contents of an
2739 uninitialised buffer. They now log a warning about the empty file
2740 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
2742 o Minor features (sandbox, backport from 0.3.3.4-alpha):
2743 - Explicitly permit the poll() system call when the Linux
2744 seccomp2-based sandbox is enabled: apparently, some versions of
2745 libc use poll() when calling getpwnam(). Closes ticket 25313.
2747 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
2748 - Our .travis.yml configuration now includes support for testing the
2749 results of "make distcheck". (It's not uncommon for "make check"
2750 to pass but "make distcheck" to fail.) Closes ticket 25814.
2751 - Our Travis CI configuration now integrates with the Coveralls
2752 coverage analysis tool. Closes ticket 25818.
2754 o Minor features (compilation, backport from 0.3.4.4-rc):
2755 - When building Tor, prefer to use Python 3 over Python 2, and more
2756 recent (contemplated) versions over older ones. Closes
2759 o Minor features (geoip):
2760 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
2761 Country database. Closes ticket 26674.
2763 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
2764 - Upon receiving a malformed connected cell, stop processing the
2765 cell immediately. Previously we would mark the connection for
2766 close, but continue processing the cell as if the connection were
2767 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
2769 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
2770 - Allow the nanosleep() system call, which glibc uses to implement
2771 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
2773 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
2774 - When running the ntor_ref.py test, make sure only to pass strings
2775 (rather than "bytes" objects) to the Python subprocess module.
2776 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
2779 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
2780 - Work around a change in OpenSSL 1.1.1 where return values that
2781 would previously indicate "no password" now indicate an empty
2782 password. Without this workaround, Tor instances running with
2783 OpenSSL 1.1.1 would accept descriptors that other Tor instances
2784 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
2786 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
2787 - Fix a compilation warning on some versions of GCC when building
2788 code that calls routerinfo_get_my_routerinfo() twice, assuming
2789 that the second call will succeed if the first one did. Fixes bug
2790 26269; bugfix on 0.2.8.2-alpha.
2792 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
2793 - Don't consider Tor running as a client if the ControlPort is open,
2794 but no actual client ports are open. Fixes bug 26062; bugfix
2797 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
2798 - Prevent a possible out-of-bounds smartlist read in
2799 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
2801 o Minor bugfixes (C correctness, backport from 0.3.3.4-alpha):
2802 - Fix a very unlikely (impossible, we believe) null pointer
2803 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
2804 Coverity; this is CID 1430932.
2806 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
2807 - Fix a number of small memory leaks identified by coverity. Fixes
2808 bug 26467; bugfix on numerous Tor versions.
2810 o Code simplification and refactoring (backport from 0.3.3.5-rc):
2811 - Move the list of default directory authorities to its own file.
2812 Closes ticket 24854. Patch by "beastr0".
2815 Changes in version 0.3.4.4-rc - 2018-07-09
2816 Tor 0.3.4.4-rc fixes several small compilation, portability, and
2817 correctness issues in previous versions of Tor. This version is a
2818 release candidate: if no serious bugs are found, we expect that the
2819 stable 0.3.4 release will be (almost) the same as this release.
2821 o Minor features (compilation):
2822 - When building Tor, prefer to use Python 3 over Python 2, and more
2823 recent (contemplated) versions over older ones. Closes
2826 o Minor features (geoip):
2827 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
2828 Country database. Closes ticket 26674.
2830 o Minor features (Rust, portability):
2831 - Rust cross-compilation is now supported. Closes ticket 25895.
2833 o Minor bugfixes (compilation):
2834 - Fix a compilation warning on some versions of GCC when building
2835 code that calls routerinfo_get_my_routerinfo() twice, assuming
2836 that the second call will succeed if the first one did. Fixes bug
2837 26269; bugfix on 0.2.8.2-alpha.
2839 o Minor bugfixes (control port):
2840 - Report the port correctly when a port is configured to bind to
2841 "auto". Fixes bug 26568; bugfix on 0.3.4.1-alpha.
2842 - Handle the HSADDRESS= argument to the HSPOST command properly.
2843 (Previously, this argument was misparsed and thus ignored.) Fixes
2844 bug 26523; bugfix on 0.3.3.1-alpha. Patch by "akwizgran".
2846 o Minor bugfixes (correctness, flow control):
2847 - Upon receiving a stream-level SENDME cell, verify that our window
2848 has not grown too large. Fixes bug 26214; bugfix on svn
2851 o Minor bugfixes (memory, correctness):
2852 - Fix a number of small memory leaks identified by coverity. Fixes
2853 bug 26467; bugfix on numerous Tor versions.
2855 o Minor bugfixes (testing, compatibility):
2856 - When running the hs_ntor_ref.py test, make sure only to pass
2857 strings (rather than "bytes" objects) to the Python subprocess
2858 module. Python 3 on Windows seems to require this. Fixes bug
2859 26535; bugfix on 0.3.1.1-alpha.
2860 - When running the ntor_ref.py test, make sure only to pass strings
2861 (rather than "bytes" objects) to the Python subprocess module.
2862 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
2866 Changes in version 0.3.3.8 - 2018-07-09
2867 Tor 0.3.3.8 backports several changes from the 0.3.4.x series, including
2868 fixes for a memory leak affecting directory authorities.
2870 o Major bugfixes (directory authority, backport from 0.3.4.3-alpha):
2871 - Stop leaking memory on directory authorities when planning to
2872 vote. This bug was crashing authorities by exhausting their
2873 memory. Fixes bug 26435; bugfix on 0.3.3.6.
2875 o Major bugfixes (rust, testing, backport from 0.3.4.3-alpha):
2876 - Make sure that failing tests in Rust will actually cause the build
2877 to fail: previously, they were ignored. Fixes bug 26258; bugfix
2880 o Minor features (compilation, backport from 0.3.4.4-rc):
2881 - When building Tor, prefer to use Python 3 over Python 2, and more
2882 recent (contemplated) versions over older ones. Closes
2885 o Minor features (geoip):
2886 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
2887 Country database. Closes ticket 26674.
2889 o Minor features (relay, diagnostic, backport from 0.3.4.3-alpha):
2890 - Add several checks to detect whether Tor relays are uploading
2891 their descriptors without specifying why they regenerated them.
2892 Diagnostic for ticket 25686.
2894 o Minor bugfixes (circuit path selection, backport from 0.3.4.1-alpha):
2895 - Don't count path selection failures as circuit build failures.
2896 This change should eliminate cases where Tor blames its guard or
2897 the network for situations like insufficient microdescriptors
2898 and/or overly restrictive torrc settings. Fixes bug 25705; bugfix
2901 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
2902 - Fix a compilation warning on some versions of GCC when building
2903 code that calls routerinfo_get_my_routerinfo() twice, assuming
2904 that the second call will succeed if the first one did. Fixes bug
2905 26269; bugfix on 0.2.8.2-alpha.
2907 o Minor bugfixes (control port, backport from 0.3.4.4-rc):
2908 - Handle the HSADDRESS= argument to the HSPOST command properly.
2909 (Previously, this argument was misparsed and thus ignored.) Fixes
2910 bug 26523; bugfix on 0.3.3.1-alpha. Patch by "akwizgran".
2912 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
2913 - Fix a number of small memory leaks identified by coverity. Fixes
2914 bug 26467; bugfix on numerous Tor versions.
2916 o Minor bugfixes (relay, backport from 0.3.4.3-alpha):
2917 - Relays now correctly block attempts to re-extend to the previous
2918 relay by Ed25519 identity. Previously they would warn in this
2919 case, but not actually reject the attempt. Fixes bug 26158; bugfix
2922 o Minor bugfixes (restart-in-process, backport from 0.3.4.1-alpha):
2923 - When shutting down, Tor now clears all the flags in the control.c
2924 module. This should prevent a bug where authentication cookies are
2925 not generated on restart. Fixes bug 25512; bugfix on 0.3.3.1-alpha.
2927 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
2928 - When running the hs_ntor_ref.py test, make sure only to pass
2929 strings (rather than "bytes" objects) to the Python subprocess
2930 module. Python 3 on Windows seems to require this. Fixes bug
2931 26535; bugfix on 0.3.1.1-alpha.
2932 - When running the ntor_ref.py test, make sure only to pass strings
2933 (rather than "bytes" objects) to the Python subprocess module.
2934 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
2938 Changes in version 0.3.4.3-alpha - 2018-06-26
2939 Tor 0.3.4.3-alpha fixes several bugs in earlier versions, including
2940 one that was causing stability issues on directory authorities.
2942 o Major bugfixes (directory authority):
2943 - Stop leaking memory on directory authorities when planning to
2944 vote. This bug was crashing authorities by exhausting their
2945 memory. Fixes bug 26435; bugfix on 0.3.3.6.
2947 o Major bugfixes (rust, testing):
2948 - Make sure that failing tests in Rust will actually cause the build
2949 to fail: previously, they were ignored. Fixes bug 26258; bugfix
2952 o Minor feature (directory authorities):
2953 - Stop warning about incomplete bw lines before the first complete
2954 bw line has been found, so that additional header lines can be
2955 ignored. Fixes bug 25960; bugfix on 0.2.2.1-alpha
2957 o Minor features (relay, diagnostic):
2958 - Add several checks to detect whether Tor relays are uploading
2959 their descriptors without specifying why they regenerated them.
2960 Diagnostic for ticket 25686.
2962 o Minor features (unit tests):
2963 - Test complete bandwidth measurements files, and test that
2964 incomplete bandwidth lines only give warnings when the end of the
2965 header has not been detected. Fixes bug 25947; bugfix
2968 o Minor bugfixes (compilation):
2969 - Refrain from compiling unit testing related object files when
2970 --disable-unittests is set to configure script. Fixes bug 24891;
2971 bugfix on 0.2.5.1-alpha.
2972 - When linking the libtor_testing.a library, only include the
2973 dirauth object files once. Previously, they were getting added
2974 twice. Fixes bug 26402; bugfix on 0.3.4.1-alpha.
2975 - The --enable-fatal-warnings flag now affects Rust code as well.
2976 Closes ticket 26245.
2978 o Minor bugfixes (onion services):
2979 - Recompute some consensus information after detecting a clock jump,
2980 or after transitioning from a non-live consensus to a live
2981 consensus. We do this to avoid having an outdated state, and
2982 miscalculating the index for next-generation onion services. Fixes
2983 bug 24977; bugfix on 0.3.2.1-alpha.
2985 o Minor bugfixes (relay):
2986 - Relays now correctly block attempts to re-extend to the previous
2987 relay by Ed25519 identity. Previously they would warn in this
2988 case, but not actually reject the attempt. Fixes bug 26158; bugfix
2991 o Minor bugfixes (testing):
2992 - Fix compilation of the doctests in the Rust crypto crate. Fixes
2993 bug 26415; bugfix on 0.3.4.1-alpha.
2994 - Instead of trying to read the geoip configuration files from
2995 within the unit tests, instead create our own ersatz files with
2996 just enough geoip data in the format we expect. Trying to read
2997 from the source directory created problems on Windows with mingw,
2998 where the build system's paths are not the same as the platform's
2999 paths. Fixes bug 25787; bugfix on 0.3.4.1-alpha.
3000 - Refrain from trying to get an item from an empty smartlist in
3001 test_bridges_clear_bridge_list. Set DEBUG_SMARTLIST in unit tests
3002 to catch improper smartlist usage. Furthermore, enable
3003 DEBUG_SMARTLIST globally when build is configured with fragile
3004 hardening. Fixes bug 26196; bugfix on 0.3.4.1-alpha.
3007 Changes in version 0.3.3.7 - 2018-06-12
3008 Tor 0.3.3.7 backports several changes from the 0.3.4.x series, including
3009 fixes for bugs affecting compatibility and stability.
3011 o Directory authority changes:
3012 - Add an IPv6 address for the "dannenberg" directory authority.
3013 Closes ticket 26343.
3015 o Minor features (geoip):
3016 - Update geoip and geoip6 to the June 7 2018 Maxmind GeoLite2
3017 Country database. Closes ticket 26351.
3019 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
3020 - Work around a change in OpenSSL 1.1.1 where return values that
3021 would previously indicate "no password" now indicate an empty
3022 password. Without this workaround, Tor instances running with
3023 OpenSSL 1.1.1 would accept descriptors that other Tor instances
3024 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
3026 o Minor bugfixes (compilation, backport from 0.3.4.2-alpha):
3027 - Silence unused-const-variable warnings in zstd.h with some GCC
3028 versions. Fixes bug 26272; bugfix on 0.3.1.1-alpha.
3030 o Minor bugfixes (controller, backport from 0.3.4.2-alpha):
3031 - Improve accuracy of the BUILDTIMEOUT_SET control port event's
3032 TIMEOUT_RATE and CLOSE_RATE fields. (We were previously
3033 miscounting the total number of circuits for these field values.)
3034 Fixes bug 26121; bugfix on 0.3.3.1-alpha.
3036 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
3037 - Prevent a possible out-of-bounds smartlist read in
3038 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
3040 o Minor bugfixes (path selection, backport from 0.3.4.1-alpha):
3041 - Only select relays when they have the descriptors we prefer to use
3042 for them. This change fixes a bug where we could select a relay
3043 because it had _some_ descriptor, but reject it later with a
3044 nonfatal assertion error because it didn't have the exact one we
3045 wanted. Fixes bugs 25691 and 25692; bugfix on 0.3.3.4-alpha.
3048 Changes in version 0.3.4.2-alpha - 2018-06-12
3049 Tor 0.3.4.2-alpha fixes several minor bugs in the previous alpha
3050 release, and forward-ports an authority-only security fix from 0.3.3.6.
3052 o Directory authority changes:
3053 - Add an IPv6 address for the "dannenberg" directory authority.
3054 Closes ticket 26343.
3056 o Major bugfixes (security, directory authority, denial-of-service, also in 0.3.3.6):
3057 - Fix a bug that could have allowed an attacker to force a directory
3058 authority to use up all its RAM by passing it a maliciously
3059 crafted protocol versions string. Fixes bug 25517; bugfix on
3060 0.2.9.4-alpha. This issue is also tracked as TROVE-2018-005.
3062 o Minor features (continuous integration):
3063 - Add the necessary configuration files for continuous integration
3064 testing on Windows, via the Appveyor platform. Closes ticket
3065 25549. Patches from Marcin Cieślak and Isis Lovecruft.
3067 o Minor features (geoip):
3068 - Update geoip and geoip6 to the June 7 2018 Maxmind GeoLite2
3069 Country database. Closes ticket 26351.
3071 o Minor bugfixes (compatibility, openssl):
3072 - Work around a change in OpenSSL 1.1.1 where return values that
3073 would previously indicate "no password" now indicate an empty
3074 password. Without this workaround, Tor instances running with
3075 OpenSSL 1.1.1 would accept descriptors that other Tor instances
3076 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
3078 o Minor bugfixes (compilation):
3079 - Silence unused-const-variable warnings in zstd.h with some GCC
3080 versions. Fixes bug 26272; bugfix on 0.3.1.1-alpha.
3081 - Fix compilation when using OpenSSL 1.1.0 with the "no-deprecated"
3082 flag enabled. Fixes bug 26156; bugfix on 0.3.4.1-alpha.
3083 - Avoid a compiler warning when casting the return value of
3084 smartlist_len() to double with DEBUG_SMARTLIST enabled. Fixes bug
3085 26283; bugfix on 0.2.4.10-alpha.
3087 o Minor bugfixes (control port):
3088 - Do not count 0-length RELAY_COMMAND_DATA cells as valid data in
3089 CIRC_BW events. Previously, such cells were counted entirely in
3090 the OVERHEAD field. Now they are not. Fixes bug 26259; bugfix
3093 o Minor bugfixes (controller):
3094 - Improve accuracy of the BUILDTIMEOUT_SET control port event's
3095 TIMEOUT_RATE and CLOSE_RATE fields. (We were previously
3096 miscounting the total number of circuits for these field values.)
3097 Fixes bug 26121; bugfix on 0.3.3.1-alpha.
3099 o Minor bugfixes (hardening):
3100 - Prevent a possible out-of-bounds smartlist read in
3101 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
3103 o Minor bugfixes (onion services):
3104 - Fix a bug that blocked the creation of ephemeral v3 onion
3105 services. Fixes bug 25939; bugfix on 0.3.4.1-alpha.
3107 o Minor bugfixes (test coverage tools):
3108 - Update our "cov-diff" script to handle output from the latest
3109 version of gcov, and to remove extraneous timestamp information
3110 from its output. Fixes bugs 26101 and 26102; bugfix
3114 Changes in version 0.3.3.6 - 2018-05-22
3115 Tor 0.3.3.6 is the first stable release in the 0.3.3 series. It
3116 backports several important fixes from the 0.3.4.1-alpha.
3118 The Tor 0.3.3 series includes controller support and other
3119 improvements for v3 onion services, official support for embedding Tor
3120 within other applications, and our first non-trivial module written in
3121 the Rust programming language. (Rust is still not enabled by default
3122 when building Tor.) And as usual, there are numerous other smaller
3123 bugfixes, features, and improvements.
3125 Below are the changes since 0.3.3.5-rc. For a list of all changes
3126 since 0.3.2.10, see the ReleaseNotes file.
3128 o Major bugfixes (directory authorities, security, backport from 0.3.4.1-alpha):
3129 - When directory authorities read a zero-byte bandwidth file, they
3130 would previously log a warning with the contents of an
3131 uninitialised buffer. They now log a warning about the empty file
3132 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
3134 o Major bugfixes (security, directory authority, denial-of-service):
3135 - Fix a bug that could have allowed an attacker to force a directory
3136 authority to use up all its RAM by passing it a maliciously
3137 crafted protocol versions string. Fixes bug 25517; bugfix on
3138 0.2.9.4-alpha. This issue is also tracked as TROVE-2018-005.
3140 o Major bugfixes (crash, backport from 0.3.4.1-alpha):
3141 - Avoid a rare assertion failure in the circuit build timeout code
3142 if we fail to allow any circuits to actually complete. Fixes bug
3143 25733; bugfix on 0.2.2.2-alpha.
3145 o Major bugfixes (directory authorities, backport from 0.3.4.1-alpha):
3146 - Avoid a crash when testing router reachability on a router that
3147 could have an ed25519 ID, but which does not. Fixes bug 25415;
3148 bugfix on 0.3.3.2-alpha.
3150 o Major bugfixes (onion service, backport from 0.3.4.1-alpha):
3151 - Correctly detect when onion services get disabled after HUP. Fixes
3152 bug 25761; bugfix on 0.3.2.1.
3154 o Major bugfixes (relay, denial of service, backport from 0.3.4.1-alpha):
3155 - Impose a limit on circuit cell queue size. The limit can be
3156 controlled by a consensus parameter. Fixes bug 25226; bugfix
3159 o Minor features (compatibility, backport from 0.3.4.1-alpha):
3160 - Avoid some compilation warnings with recent versions of LibreSSL.
3161 Closes ticket 26006.
3163 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
3164 - Our .travis.yml configuration now includes support for testing the
3165 results of "make distcheck". (It's not uncommon for "make check"
3166 to pass but "make distcheck" to fail.) Closes ticket 25814.
3167 - Our Travis CI configuration now integrates with the Coveralls
3168 coverage analysis tool. Closes ticket 25818.
3170 o Minor features (geoip):
3171 - Update geoip and geoip6 to the May 1 2018 Maxmind GeoLite2 Country
3172 database. Closes ticket 26104.
3174 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
3175 - Don't consider Tor running as a client if the ControlPort is open,
3176 but no actual client ports are open. Fixes bug 26062; bugfix
3179 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
3180 - Upon receiving a malformed connected cell, stop processing the
3181 cell immediately. Previously we would mark the connection for
3182 close, but continue processing the cell as if the connection were
3183 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
3185 o Minor bugfixes (documentation, backport from 0.3.4.1-alpha):
3186 - Stop saying in the manual that clients cache ipv4 dns answers from
3187 exit relays. We haven't used them since 0.2.6.3-alpha, and in
3188 ticket 24050 we stopped even caching them as of 0.3.2.6-alpha, but
3189 we forgot to say so in the man page. Fixes bug 26052; bugfix
3192 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
3193 - Allow the nanosleep() system call, which glibc uses to implement
3194 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
3196 o Minor bugfixes (onion service, backport from 0.3.4.1-alpha):
3197 - Fix a memory leak when a v3 onion service is configured and gets a
3198 SIGHUP signal. Fixes bug 25901; bugfix on 0.3.2.1-alpha.
3199 - When parsing the descriptor signature, look for the token plus an
3200 extra white-space at the end. This is more correct but also will
3201 allow us to support new fields that might start with "signature".
3202 Fixes bug 26069; bugfix on 0.3.0.1-alpha.
3204 o Minor bugfixes (relay, crash, backport from 0.3.4.1-alpha):
3205 - Avoid a crash when running with DirPort set but ORPort turned off.
3206 Fixes a case of bug 23693; bugfix on 0.3.1.1-alpha.
3208 o Documentation (backport from 0.3.4.1-alpha):
3209 - Correct an IPv6 error in the documentation for ExitPolicy. Closes
3210 ticket 25857. Patch from "CTassisF".
3213 Changes in version 0.3.4.1-alpha - 2018-05-17
3214 Tor 0.3.4.1-alpha is the first release in the 0.3.4.x series. It
3215 includes refactoring to begin reducing Tor's binary size and idle CPU
3216 usage on mobile, along with prep work for new bandwidth scanners,
3217 improvements to the experimental "vanguards" feature, and numerous
3218 other small features and bugfixes.
3220 o New system requirements:
3221 - Tor no longer tries to support old operating systems without
3222 mmap() or some local equivalent. Apparently, compilation on such
3223 systems has been broken for some time, without anybody noticing or
3224 complaining. Closes ticket 25398.
3226 o Major feature (directory authority, modularization):
3227 - The directory authority subsystem has been modularized. The code
3228 is now located in src/or/dirauth/, and is compiled in by default.
3229 To disable the module, the configure option
3230 --disable-module-dirauth has been added. This module may be
3231 disabled by default in some future release. Closes ticket 25610.
3233 o Major features (main loop, CPU usage):
3234 - When Tor is disabled (via DisableNetwork or via hibernation), it
3235 no longer needs to run any per-second events. This change should
3236 make it easier for mobile applications to disable Tor while the
3237 device is sleeping, or Tor is not running. Closes ticket 26063.
3238 - Tor no longer enables all of its periodic events by default.
3239 Previously, Tor would enable all possible main loop events,
3240 regardless of whether it needed them. Furthermore, many of these
3241 events are now disabled with Tor is hibernating or DisableNetwork
3242 is set. This is a big step towards reducing client CPU usage by
3243 reducing the amount of wake-ups the daemon does. Closes ticket
3245 - The bandwidth-limitation logic has been refactored so that
3246 bandwidth calculations are performed on-demand, rather than every
3247 TokenBucketRefillInterval milliseconds. This change should improve
3248 the granularity of our bandwidth calculations, and limit the
3249 number of times that the Tor process needs to wake up when it is
3250 idle. Closes ticket 25373.
3251 - Move responsibility for many operations from a once-per-second
3252 callback to a callback that is only scheduled as needed. Moving
3253 this functionality has allowed us to disable the callback when
3254 Tor's network is disabled. Once enough items are removed from our
3255 once-per-second callback, we can eliminate it entirely to conserve
3256 CPU when idle. The functionality removed includes: closing
3257 connections, circuits, and channels (ticket 25932); consensus
3258 voting (25937); flushing log callbacks (25951); honoring delayed
3259 SIGNEWNYM requests (25949); rescanning the consensus cache
3260 (25931); saving the state file to disk (25948); warning relay
3261 operators about unreachable ports (25952); and keeping track of
3262 Tor's uptime (26009).
3264 o Major bugfixes (directory authorities, security):
3265 - When directory authorities read a zero-byte bandwidth file, they
3266 would previously log a warning with the contents of an
3267 uninitialised buffer. They now log a warning about the empty file
3268 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
3270 o Major bugfixes (crash):
3271 - Avoid a rare assertion failure in the circuit build timeout code
3272 if we fail to allow any circuits to actually complete. Fixes bug
3273 25733; bugfix on 0.2.2.2-alpha.
3275 o Major bugfixes (directory authority):
3276 - Avoid a crash when testing router reachability on a router that
3277 could have an ed25519 ID, but which does not. Fixes bug 25415;
3278 bugfix on 0.3.3.2-alpha.
3280 o Major bugfixes (onion service):
3281 - Correctly detect when onion services get disabled after HUP. Fixes
3282 bug 25761; bugfix on 0.3.2.1.
3284 o Major bugfixes (protover, voting):
3285 - Revise Rust implementation of protover to use a more memory-
3286 efficient voting algorithm and corresponding data structures, thus
3287 avoiding a potential (but small impact) DoS attack where specially
3288 crafted protocol strings would expand to several potential
3289 megabytes in memory. In the process, several portions of code were
3290 revised to be methods on new, custom types, rather than functions
3291 taking interchangeable types, thus increasing type safety of the
3292 module. Custom error types and handling were added as well, in
3293 order to facilitate better error dismissal/handling in outside
3294 crates and avoid mistakenly passing an internal error string to C
3295 over the FFI boundary. Many tests were added, and some previous
3296 differences between the C and Rust implementations have been
3297 remedied. Fixes bug 24031; bugfix on 0.3.3.1-alpha.
3299 o Major bugfixes (relay, denial of service):
3300 - Impose a limit on circuit cell queue size. The limit can be
3301 controlled by a consensus parameter. Fixes bug 25226; bugfix
3304 o Minor features (accounting):
3305 - When Tor becomes dormant, it now uses a scheduled event to wake up
3306 at the right time. Previously, we would use the per-second timer
3307 to check whether to wake up, but we no longer have any per-second
3308 timers enabled when the network is disabled. Closes ticket 26064.
3310 o Minor features (code quality):
3311 - Add optional spell-checking for the Tor codebase, using the
3312 "misspell" program. To use this feature, run "make check-typos".
3313 Closes ticket 25024.
3315 o Minor features (compatibility):
3316 - Tor now detects versions of OpenSSL 1.1.0 and later compiled with
3317 the no-deprecated option, and builds correctly with them. Closes
3318 tickets 19429, 19981, and 25353.
3319 - Avoid some compilation warnings with recent versions of LibreSSL.
3320 Closes ticket 26006.
3322 o Minor features (compression, zstd):
3323 - When running with zstd, Tor now considers using advanced functions
3324 that the zstd maintainers have labeled as potentially unstable. To
3325 prevent breakage, Tor will only use this functionality when the
3326 runtime version of the zstd library matches the version with which
3327 Tor was compiled. Closes ticket 25162.
3329 o Minor features (configuration):
3330 - The "DownloadSchedule" options have been renamed to end with
3331 "DownloadInitialDelay". The old names are still allowed, but will
3332 produce a warning. Comma-separated lists are still permitted for
3333 these options, but all values after the first are ignored (as they
3334 have been since 0.2.9). Closes ticket 23354.
3336 o Minor features (continuous integration):
3337 - Our .travis.yml configuration now includes support for testing the
3338 results of "make distcheck". (It's not uncommon for "make check"
3339 to pass but "make distcheck" to fail.) Closes ticket 25814.
3340 - Our Travis CI configuration now integrates with the Coveralls
3341 coverage analysis tool. Closes ticket 25818.
3343 o Minor features (control port):
3344 - Introduce GETINFO "current-time/{local,utc}" to return the local
3345 and UTC times respectively in ISO format. This helps a controller
3346 like Tor Browser detect a time-related error. Closes ticket 25511.
3347 Patch by Neel Chauhan.
3348 - Introduce new fields to the CIRC_BW event. There are two new
3349 fields in each of the read and written directions. The DELIVERED
3350 fields report the total valid data on the circuit, as measured by
3351 the payload sizes of verified and error-checked relay command
3352 cells. The OVERHEAD fields report the total unused bytes in each
3353 of these cells. Closes ticket 25903.
3355 o Minor features (directory authority):
3356 - Directory authorities now open their key-pinning files as O_SYNC,
3357 to limit their chances of accidentally writing partial lines.
3358 Closes ticket 23909.
3360 o Minor features (directory authority, forward compatibility):
3361 - Make the lines of the measured bandwidth file able to contain
3362 their entries in any order. Previously, the node_id entry needed
3363 to come first. Closes ticket 26004.
3365 o Minor features (entry guards):
3366 - Introduce a new torrc option NumPrimaryGuards for controlling the
3367 number of primary guards. Closes ticket 25843.
3369 o Minor features (geoip):
3370 - Update geoip and geoip6 to the May 1 2018 Maxmind GeoLite2 Country
3371 database. Closes ticket 26104.
3373 o Minor features (performance):
3374 - Avoid a needless call to malloc() when processing an incoming
3375 relay cell. Closes ticket 24914.
3376 - Make our timing-wheel code run a tiny bit faster on 32-bit
3377 platforms, by preferring 32-bit math to 64-bit. Closes
3379 - Avoid a needless malloc()/free() pair every time we handle an ntor
3380 handshake. Closes ticket 25150.
3382 o Minor features (testing):
3383 - Add a unit test for voting_schedule_get_start_of_next_interval().
3384 Closes ticket 26014, and helps make unit test coverage
3386 - A new unittests module specifically for testing the functions in
3387 the (new-ish) bridges.c module has been created with new
3388 unittests, raising the code coverage percentages. Closes 25425.
3389 - We now have improved testing for addressmap_get_virtual_address()
3390 function. This should improve our test coverage, and make our test
3391 coverage more deterministic. Closes ticket 25993.
3393 o Minor features (timekeeping, circuit scheduling):
3394 - When keeping track of how busy each circuit have been recently on
3395 a given connection, use coarse-grained monotonic timers rather
3396 than gettimeofday(). This change should marginally increase
3397 accuracy and performance. Implements part of ticket 25927.
3399 o Minor bugfixes (bandwidth management):
3400 - Consider ourselves "low on write bandwidth" if we have exhausted
3401 our write bandwidth some time in the last second. This was the
3402 documented behavior before, but the actual behavior was to change
3403 this value every TokenBucketRefillInterval. Fixes bug 25828;
3404 bugfix on 0.2.3.5-alpha.
3406 o Minor bugfixes (C correctness):
3407 - Add a missing lock acquisition in the shutdown code of the control
3408 subsystem. Fixes bug 25675; bugfix on 0.2.7.3-rc. Found by
3409 Coverity; this is CID 1433643.
3411 o Minor bugfixes (circuit path selection):
3412 - Don't count path selection failures as circuit build failures.
3413 This change should eliminate cases where Tor blames its guard or
3414 the network for situations like insufficient microdescriptors
3415 and/or overly restrictive torrc settings. Fixes bug 25705; bugfix
3418 o Minor bugfixes (client):
3419 - Don't consider Tor running as a client if the ControlPort is open,
3420 but no actual client ports are open. Fixes bug 26062; bugfix
3423 o Minor bugfixes (code style):
3424 - Fixed multiple includes of transports.h in src/or/connection.c
3425 Fixes bug 25261; bugfix on 0.2.5.1-alpha.
3426 - Remove the unused variable n_possible from the function
3427 channel_get_for_extend(). Fixes bug 25645; bugfix on 0.2.4.4-alpha
3429 o Minor bugfixes (control interface):
3430 - Respond with more human-readable error messages to GETINFO exit-
3431 policy/* requests. Also, let controller know if an error is
3432 transient (response code 551) or not (response code 552). Fixes
3433 bug 25852; bugfix on 0.2.8.1-alpha.
3435 o Minor bugfixes (controller):
3436 - Make CIRC_BW event reflect the total of all data sent on a
3437 circuit, including padding and dropped cells. Also fix a mis-
3438 counting bug when STREAM_BW events were enabled. Fixes bug 25400;
3439 bugfix on 0.2.5.2-alpha.
3441 o Minor bugfixes (correctness, client):
3442 - Upon receiving a malformed connected cell, stop processing the cell
3443 immediately. Previously we would mark the connection for close, but
3444 continue processing the cell as if the connection were open. Fixes bug
3445 26072; bugfix on 0.2.4.7-alpha.
3447 o Minor bugfixes (directory client):
3448 - When unverified-consensus is verified, rename it to cached-
3449 consenus. Fixes bug 4187; bugfix on 0.2.0.3-alpha.
3450 - Fixed launching a certificate fetch always during the scheduled
3451 periodic consensus fetch by fetching only in those cases when
3452 consensus are waiting for certs. Fixes bug 24740; bugfix
3455 o Minor bugfixes (documentation):
3456 - Stop saying in the manual that clients cache ipv4 dns answers from
3457 exit relays. We haven't used them since 0.2.6.3-alpha, and in
3458 ticket 24050 we stopped even caching them as of 0.3.2.6-alpha, but
3459 we forgot to say so in the man page. Fixes bug 26052; bugfix
3462 o Minor bugfixes (error reporting):
3463 - Improve tolerance for directory authorities with skewed clocks.
3464 Previously, an authority with a clock more than 60 seconds ahead
3465 could cause a client with a correct clock to warn that the
3466 client's clock was behind. Now the clocks of a majority of
3467 directory authorities have to be ahead of the client before this
3468 warning will occur. Fixes bug 25756; bugfix on 0.2.2.25-alpha.
3470 o Minor bugfixes (Linux seccomp2 sandbox):
3471 - Allow the nanosleep() system call, which glibc uses to implement
3472 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
3474 o Minor bugfixes (onion service):
3475 - Fix a memory leak when a v3 onion service is configured and gets a
3476 SIGHUP signal. Fixes bug 25901; bugfix on 0.3.2.1-alpha.
3477 - When parsing the descriptor signature, look for the token plus an
3478 extra white-space at the end. This is more correct but also will
3479 allow us to support new fields that might start with "signature".
3480 Fixes bug 26069; bugfix on 0.3.0.1-alpha.
3482 o Minor bugfixes (path selection):
3483 - Only select relays when they have the descriptors we prefer to use
3484 for them. This change fixes a bug where we could select a relay
3485 because it had _some_ descriptor, but reject it later with a
3486 nonfatal assertion error because it didn't have the exact one we
3487 wanted. Fixes bugs 25691 and 25692; bugfix on 0.3.3.4-alpha.
3489 o Minor bugfixes (portability):
3490 - Do not align mmap length, as it is not required by POSIX, and the
3491 getpagesize function is deprecated. Fixes bug 25399; bugfix
3494 o Minor bugfixes (portability, FreeBSD):
3495 - In have_enough_mem_for_dircache(), the variable DIRCACHE_MIN_MEM_MB
3496 does not stringify on FreeBSD, so we switch to tor_asprintf().
3497 Fixes bug 20887; bugfix on 0.2.8.1-alpha. Patch by Neel Chauhan.
3499 o Minor bugfixes (relay statistics):
3500 - When a relay is collecting internal statistics about how many
3501 create cell requests it has seen of each type, accurately count
3502 the requests from relays that temporarily fall out of the
3503 consensus. (To be extra conservative, we were already ignoring
3504 requests from clients in our counts, and we continue ignoring them
3505 here.) Fixes bug 24910; bugfix on 0.2.4.17-rc.
3507 o Minor bugfixes (relay, crash):
3508 - Avoid a crash when running with DirPort set but ORPort turned off.
3509 Fixes a case of bug 23693; bugfix on 0.3.1.1-alpha.
3511 o Minor bugfixes (restart-in-process):
3512 - When shutting down, Tor now clears all the flags in the control.c
3513 module. This should prevent a bug where authentication cookies are
3514 not generated on restart. Fixes bug 25512; bugfix on 0.3.3.1-alpha.
3516 o Minor bugfixes (testing):
3517 - When testing workqueue event-cancellation, make sure that we
3518 actually cancel an event, and that cancel each event with equal
3519 probability. (It was previously possible, though extremely
3520 unlikely, for our event-canceling test not to cancel any events.)
3521 Fixes bug 26008; bugfix on 0.2.6.3-alpha.
3522 - Repeat part of the test in test_client_pick_intro() a number of
3523 times, to give it consistent coverage. Fixes bug 25996; bugfix
3525 - Remove randomness from the hs_common/responsible_hsdirs test, so
3526 that it always takes the same path through the function it tests.
3527 Fixes bug 25997; bugfix on 0.3.2.1-alpha.
3528 - Change the behavior of the "channel/outbound" test so that it
3529 never causes a 10-second rollover for the EWMA circuitmux code.
3530 Previously, this behavior would happen randomly, and result in
3531 fluctuating test coverage. Fixes bug 25994; bugfix
3533 - Use X509_new() to allocate certificates that will be freed later
3534 with X509_free(). Previously, some parts of the unit tests had
3535 used tor_malloc_zero(), which is incorrect, and which caused test
3536 failures on Windows when they were built with extra hardening.
3537 Fixes bugs 25943 and 25944; bugfix on 0.2.8.1-alpha. Patch by
3539 - While running the circuit_timeout test, fix the PRNG to a
3540 deterministic AES stream, so that the test coverage from this test
3541 will itself be deterministic. Fixes bug 25995; bugfix
3544 o Minor bugfixes (vanguards):
3545 - Allow the last hop in a vanguard circuit to be the same as our
3546 first, to prevent the adversary from influencing guard node choice
3547 by choice of last hop. Also prevent the creation of A - B - A
3548 paths, or A - A paths, which are forbidden by relays. Fixes bug
3549 25870; bugfix on 0.3.3.1-alpha.
3551 o Code simplification and refactoring:
3552 - Remove duplicate code in parse_{c,s}method_line and bootstrap
3553 their functionalities into a single function. Fixes bug 6236;
3554 bugfix on 0.2.3.6-alpha.
3555 - We remove the PortForwsrding and PortForwardingHelper options,
3556 related functions, and the port_forwarding tests. These options
3557 were used by the now-deprecated Vidalia to help ordinary users
3558 become Tor relays or bridges. Closes ticket 25409. Patch by
3560 - In order to make the OR and dir checking function in router.c less
3561 confusing we renamed some functions and
3562 consider_testing_reachability() has been split into
3563 router_should_check_reachability() and
3564 router_do_reachability_checks(). Also we improved the documentation
3565 in some functions. Closes ticket 18918.
3566 - Initial work to isolate Libevent usage to a handful of modules in
3567 our codebase, to simplify our call structure, and so that we can
3568 more easily change event loops in the future if needed. Closes
3570 - Introduce a function to call getsockname() and return tor_addr_t,
3571 to save a little complexity throughout the codebase. Closes
3573 - Make hsdir_index in node_t a hsdir_index_t rather than a pointer
3574 as hsdir_index is always present. Also, we move hsdir_index_t into
3575 or.h. Closes ticket 23094. Patch by Neel Chauhan.
3576 - Merge functions used for describing nodes and suppress the
3577 functions that do not allocate memory for the output buffer
3578 string. NODE_DESC_BUF_LEN constant and format_node_description()
3579 function cannot be used externally from router.c module anymore.
3580 Closes ticket 25432. Patch by valentecaio.
3581 - Our main loop has been simplified so that all important operations
3582 happen inside events. Previously, some operations had to happen
3583 outside the event loop, to prevent infinite sequences of event
3584 activations. Closes ticket 25374.
3585 - Put a SHA1 public key digest in hs_service_intro_point_t, and use
3586 it in register_intro_circ() and service_intro_point_new(). This
3587 prevents the digest from being re-calculated each time. Closes
3588 ticket 23107. Patch by Neel Chauhan.
3589 - Refactor token-bucket implementations to use a common backend.
3590 Closes ticket 25766.
3591 - Remove extern declaration of stats_n_seconds_working variable from
3592 main, protecting its accesses with get_uptime() and reset_uptime()
3593 functions. Closes ticket 25081, patch by “valentecaio”.
3594 - Remove our previous logic for "cached gettimeofday()" -- our
3595 coarse monotonic timers are fast enough for this purpose, and far
3596 less error-prone. Implements part of ticket 25927.
3597 - Remove the return value for fascist_firewall_choose_address_base(),
3598 and sister functions such as fascist_firewall_choose_address_node()
3599 and fascist_firewall_choose_address_rs(). Also, while we're here,
3600 initialize the ap argument as leaving it uninitialized can pose a
3601 security hazard. Closes ticket 24734. Patch by Neel Chauhan.
3602 - Rename two fields of connection_t struct. timestamp_lastwritten is
3603 renamed to timestamp_last_write_allowed and timestamp_lastread is
3604 renamed to timestamp_last_read_allowed. Closes ticket 24714, patch
3606 - Since Tor requires C99, remove our old workaround code for libc
3607 implementations where free(NULL) doesn't work. Closes ticket 24484.
3608 - Use our standard rate-limiting code to deal with excessive
3609 libevent failures, rather than the hand-rolled logic we had
3610 before. Closes ticket 26016.
3611 - We remove the return value of node_get_prim_orport() and
3612 node_get_prim_dirport(), and introduce node_get_prim_orport() in
3613 node_ipv6_or_preferred() and node_ipv6_dir_preferred() in order to
3614 check for a null address. Closes ticket 23873. Patch by
3616 - We switch to should_record_bridge_info() in
3617 geoip_note_client_seen() and options_need_geoip_info() instead of
3618 accessing the configuration values directly. Fixes bug 25290;
3619 bugfix on 0.2.1.6-alpha. Patch by Neel Chauhan.
3621 o Deprecated features:
3622 - As we are not recommending 0.2.5 anymore, we require relays that
3623 once had an ed25519 key associated with their RSA key to always
3624 have that key, instead of allowing them to drop back to a version
3625 that didn't support ed25519. This means they need to use a new RSA
3626 key if they want to downgrade to an older version of tor without
3627 ed25519. Closes ticket 20522.
3630 - Correct an IPv6 error in the documentation for ExitPolicy. Closes
3631 ticket 25857. Patch from "CTassisF".
3634 - Directory authorities will no longer support voting according to
3635 any consensus method before consensus method 25. This keeps
3636 authorities compatible with all authorities running 0.2.9.8 and
3637 later, and does not break any clients or relays. Implements ticket
3638 24378 and proposal 290.
3639 - The PortForwarding and PortForwardingHelper features have been
3640 removed. The reasoning is, given that implementations of NAT
3641 traversal protocols within common consumer grade routers are
3642 frequently buggy, and that the target audience for a NAT punching
3643 feature is a perhaps less-technically-inclined relay operator,
3644 when the helper fails to setup traversal the problems are usually
3645 deep, ugly, and very router specific, making them horrendously
3646 impossible for technical support to reliable assist with, and thus
3647 resulting in frustration all around. Unfortunately, relay
3648 operators who would like to run relays behind NATs will need to
3649 become more familiar with the port forwarding configurations on
3650 their local router. Closes 25409.
3651 - The TestingEnableTbEmptyEvent option has been removed. It was used
3652 in testing simulations to measure how often connection buckets
3653 were emptied, in order to improve our scheduling, but it has not
3654 been actively used in years. Closes ticket 25760.
3655 - The old "round-robin" circuit multiplexer (circuitmux)
3656 implementation has been removed, along with a fairly large set of
3657 code that existed to support it. It has not been the default
3658 circuitmux since we introduced the "EWMA" circuitmux in 0.2.4.x,
3659 but it still required an unreasonable amount of memory and CPU.
3660 Closes ticket 25268.
3663 Changes in version 0.3.3.5-rc - 2018-04-15
3664 Tor 0.3.3.5-rc fixes various bugs in earlier versions of Tor,
3665 including some that could affect reliability or correctness.
3667 This is the first release candidate in the 0.3.3 series. If we find no
3668 new bugs or regression here, then the first stable 0.3.3 release will
3669 be nearly identical to this one.
3671 o Major bugfixes (security, protover, voting):
3672 - Revise Rust implementation of protover to use a more memory-
3673 efficient voting algorithm and corresponding data structures, thus
3674 avoiding a potential memory-based DoS attack where specially
3675 crafted protocol strings would expand to fill available memory.
3676 Fixes bug 24031; bugfix on 0.3.3.1-alpha.
3678 o Major bugfixes (performance, load balancing):
3679 - Directory authorities no longer vote in favor of the Guard flag
3680 for relays without directory support. Starting in Tor
3681 0.3.0.1-alpha, clients have been avoiding using such relays in the
3682 Guard position, leading to increasingly broken load balancing for
3683 the 5%-or-so of Guards that don't advertise directory support.
3684 Fixes bug 22310; bugfix on 0.3.0.6.
3686 o Minor feature (continuous integration):
3687 - Update the Travis CI configuration to use the stable Rust channel,
3688 now that we have decided to require that. Closes ticket 25714.
3690 o Minor features (config options):
3691 - Change the way the default value for MaxMemInQueues is calculated.
3692 We now use 40% of the hardware RAM if the system has 8 GB RAM or
3693 more. Otherwise we use the former value of 75%. Closes
3696 o Minor features (geoip):
3697 - Update geoip and geoip6 to the April 3 2018 Maxmind GeoLite2
3698 Country database. Closes ticket 25718.
3700 o Minor bugfixes (client):
3701 - When using a listed relay as a bridge, and also using
3702 microdescriptors, and considering that relay as a non-bridge in a
3703 circuit, treat its microdescriptor as a valid source of
3704 information about that relay. This change should prevent a non-
3705 fatal assertion error. Fixes bug 25691; bugfix on 0.3.3.4-alpha.
3707 o Minor bugfixes (controller):
3708 - Restore the correct operation of the RESOLVE command, which had
3709 been broken since we added the ability to enable/disable DNS on
3710 specific listener ports. Fixes bug 25617; bugfix on 0.2.9.3-alpha.
3712 o Minor bugfixes (distribution, compilation, rust):
3713 - Build correctly when the rust dependencies submodule is loaded,
3714 but the TOR_RUST_DEPENDENCIES environment variable is not set.
3715 Fixes bug 25679; bugfix on 0.3.3.1-alpha.
3716 - Actually include all of our Rust source in our source
3717 distributions. (Previously, a few of the files were accidentally
3718 omitted.) Fixes bug 25732; bugfix on 0.3.3.2-alpha.
3720 o Minor bugfixes (documentation):
3721 - Document that the PerConnBW{Rate,Burst} options will fall back to
3722 their corresponding consensus parameters only if those parameters
3723 are set. Previously we had claimed that these values would always
3724 be set in the consensus. Fixes bug 25296; bugfix on 0.2.2.7-alpha.
3725 - Revert a misformatting issue in the ExitPolicy documentation.
3726 Fixes bug 25582; bugfix on 0.3.3.1-alpha.
3728 o Minor bugfixes (exit relay DNS retries):
3729 - Re-attempt timed-out DNS queries 3 times before failure, since our
3730 timeout is 5 seconds for them, but clients wait 10-15. Also allow
3731 slightly more timeouts per resolver when an exit has multiple
3732 resolvers configured. Fixes bug 21394; bugfix on 0.3.1.9.
3734 o Minor bugfixes (onion services):
3735 - Re-instate counting the client HSDir fetch circuits against the
3736 MaxClientCircuitsPending rate limit. Fixes bug 24989; bugfix
3738 - Remove underscores from the _HSLayer{2,3}Nodes options. This
3739 expert-user configuration can now be enabled as HSLayer{2,3}Nodes.
3740 Fixes bug 25581; bugfix on 0.3.3.1-alpha
3742 o Code simplification and refactoring:
3743 - Move the list of default directory authorities to its own file.
3744 Closes ticket 24854. Patch by "beastr0".
3746 o Documentation (manpage, denial of service):
3747 - Provide more detail about the denial-of-service options, by
3748 listing each mitigation and explaining how they relate. Closes
3752 Changes in version 0.3.3.4-alpha - 2018-03-29
3753 Tor 0.3.3.4-alpha includes various bugfixes for issues found during
3754 the alpha testing of earlier releases in its series. We are
3755 approaching a stable 0.3.3.4-alpha release: more testing is welcome!
3757 o New system requirements:
3758 - When built with Rust, Tor now depends on version 0.2.39 of the
3759 libc crate. Closes tickets 25310 and 25664.
3761 o Major bugfixes (relay, connection):
3762 - If we have failed to connect to a relay and received a connection
3763 refused, timeout, or similar error (at the TCP level), do not try
3764 that same address/port again for 60 seconds after the failure has
3765 occurred. Fixes bug 24767; bugfix on 0.0.6.
3767 o Minor features (geoip):
3768 - Update geoip and geoip6 to the March 8 2018 Maxmind GeoLite2
3769 Country database. Closes ticket 25469.
3771 o Minor features (log messages):
3772 - Improve log message in the out-of-memory handler to include
3773 information about memory usage from the different compression
3774 backends. Closes ticket 25372.
3776 o Minor features (sandbox):
3777 - Explicitly permit the poll() system call when the Linux
3778 seccomp2-based sandbox is enabled: apparently, some versions of
3779 libc use poll() when calling getpwnam(). Closes ticket 25313.
3781 o Minor bugfixes (C correctness):
3782 - Fix a very unlikely (impossible, we believe) null pointer
3783 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
3784 Coverity; this is CID 1430932.
3786 o Minor bugfixes (channel, client):
3787 - Better identify client connection when reporting to the geoip
3788 client cache. Fixes bug 24904; bugfix on 0.3.1.7.
3790 o Minor bugfixes (compilation):
3791 - Fix a C99 compliance issue in our configuration script that caused
3792 compilation issues when compiling Tor with certain versions of
3793 xtools. Fixes bug 25474; bugfix on 0.3.2.5-alpha.
3795 o Minor bugfixes (controller, reliability):
3796 - Avoid a (nonfatal) assertion failure when extending a one-hop
3797 circuit from the controller to become a multihop circuit. Fixes
3798 bug 24903; bugfix on 0.2.5.2-alpha.
3800 o Major bugfixes (networking):
3801 - Tor will no longer reject IPv6 address strings from Tor Browser
3802 when they are passed as hostnames in SOCKS5 requests. Fixes bug
3803 25036, bugfix on Tor 0.3.1.2.
3805 o Minor bugfixes (networking):
3806 - string_is_valid_hostname() will not consider IP strings to be
3807 valid hostnames. Fixes bug 25055; bugfix on Tor 0.2.5.5.
3809 o Minor bugfixes (onion service v3):
3810 - Avoid an assertion failure when the next onion service
3811 descriptor rotation type is out of sync with the consensus's
3812 valid-after time. Instead, log a warning message with extra
3813 information, so we can better hunt down the cause of this
3814 assertion. Fixes bug 25306; bugfix on 0.3.2.1-alpha.
3816 o Minor bugfixes (testing):
3817 - Avoid intermittent test failures due to a test that had relied on
3818 onion service introduction point creation finishing within 5
3819 seconds of real clock time. Fixes bug 25450; bugfix
3821 - Rust crates are now automatically detected and tested. Previously,
3822 some crates were not tested by `make test-rust` due to a static
3823 string in the `src/test/test_rust.sh` script specifying which
3824 crates to test. Fixes bug 25560; bugfix on 0.3.3.3-alpha.
3826 o Minor bugfixes (testing, benchmarks):
3827 - Fix a crash when running benchmark tests on win32 systems. The
3828 crash was due to a mutex that wasn't initialized before logging
3829 and options were initialized. Fixes bug 25479; bugfix
3832 o Minor bugfixes (warnings, ipv6):
3833 - Avoid a bug warning that could occur when trying to connect to a
3834 relay over IPv6. This warning would occur on a Tor instance that
3835 downloads router descriptors, but prefers to use microdescriptors.
3836 Fixes bug 25213; bugfix on 0.3.3.1-alpha.
3838 o Code simplification and refactoring:
3839 - Remove the old (deterministic) directory retry logic entirely:
3840 We've used exponential backoff exclusively for some time. Closes
3844 - Improved the documentation of AccountingStart parameter. Closes
3846 - Update the documentation for "Log" to include the current list of
3847 logging domains. Closes ticket 25378.
3850 Changes in version 0.3.1.10 - 2018-03-03
3851 Tor 0.3.1.10 backports a number of bugfixes, including important fixes for
3854 It includes an important security fix for a remote crash attack
3855 against directory authorities, tracked as TROVE-2018-001.
3857 This release also backports our new system for improved resistance to
3858 denial-of-service attacks against relays.
3860 This release also fixes several minor bugs and annoyances from
3863 All directory authorities should upgrade to one of the versions
3864 released today. Relays running 0.3.1.x may wish to update to one of
3865 the versions released today, for the DoS mitigations.
3867 Please note: according to our release calendar, Tor 0.3.1 will no
3868 longer be supported after 1 July 2018. If you will be running Tor
3869 after that date, you should make sure to plan to upgrade to the latest
3870 stable version, or downgrade to 0.2.9 (which will receive long-term
3873 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
3874 - Fix a protocol-list handling bug that could be used to remotely crash
3875 directory authorities with a null-pointer exception. Fixes bug 25074;
3876 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
3879 o Major features (denial-of-service mitigation, backport from 0.3.3.2-alpha):
3880 - Give relays some defenses against the recent network overload. We
3881 start with three defenses (default parameters in parentheses).
3882 First: if a single client address makes too many concurrent
3883 connections (>100), hang up on further connections. Second: if a
3884 single client address makes circuits too quickly (more than 3 per
3885 second, with an allowed burst of 90) while also having too many
3886 connections open (3), refuse new create cells for the next while
3887 (1-2 hours). Third: if a client asks to establish a rendezvous
3888 point to you directly, ignore the request. These defenses can be
3889 manually controlled by new torrc options, but relays will also
3890 take guidance from consensus parameters, so there's no need to
3891 configure anything manually. Implements ticket 24902.
3893 o Minor features (linux seccomp2 sandbox, backport from 0.3.2.5-alpha):
3894 - Update the sandbox rules so that they should now work correctly
3895 with Glibc 2.26. Closes ticket 24315.
3897 o Major bugfixes (onion services, retry behavior, backport from 0.3.3.1-alpha):
3898 - Fix an "off by 2" error in counting rendezvous failures on the
3899 onion service side. While we thought we would stop the rendezvous
3900 attempt after one failed circuit, we were actually making three
3901 circuit attempts before giving up. Now switch to a default of 2,
3902 and allow the consensus parameter "hs_service_max_rdv_failures" to
3903 override. Fixes bug 24895; bugfix on 0.0.6.
3905 o Major bugfixes (protocol versions, backport from 0.3.3.2-alpha):
3906 - Add Link protocol version 5 to the supported protocols list. Fixes
3907 bug 25070; bugfix on 0.3.1.1-alpha.
3909 o Major bugfixes (relay, backport from 0.3.3.1-alpha):
3910 - Fix a set of false positives where relays would consider
3911 connections to other relays as being client-only connections (and
3912 thus e.g. deserving different link padding schemes) if those
3913 relays fell out of the consensus briefly. Now we look only at the
3914 initial handshake and whether the connection authenticated as a
3915 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
3917 o Minor features (denial-of-service avoidance, backport from 0.3.3.2-alpha):
3918 - Make our OOM handler aware of the geoip client history cache so it
3919 doesn't fill up the memory. This check is important for IPv6 and
3920 our DoS mitigation subsystem. Closes ticket 25122.
3922 o Minor feature (relay statistics, backport from 0.3.2.6-alpha):
3923 - Change relay bandwidth reporting stats interval from 4 hours to 24
3924 hours in order to reduce the efficiency of guard discovery
3925 attacks. Fixes ticket 23856.
3927 o Minor features (compatibility, OpenSSL, backport from 0.3.3.3-alpha):
3928 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
3929 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
3930 since they neither disabled TLS 1.3 nor enabled any of the
3931 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
3932 Closes ticket 24978.
3934 o Minor features (fallback directory mirrors, backport from 0.3.2.9):
3935 - The fallback directory list has been re-generated based on the
3936 current status of the network. Tor uses fallback directories to
3937 bootstrap when it doesn't yet have up-to-date directory
3938 information. Closes ticket 24801.
3939 - Make the default DirAuthorityFallbackRate 0.1, so that clients
3940 prefer to bootstrap from fallback directory mirrors. This is a
3941 follow-up to 24679, which removed weights from the default
3942 fallbacks. Implements ticket 24681.
3944 o Minor features (geoip):
3945 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
3948 o Minor bugfix (channel connection, backport from 0.3.3.2-alpha):
3949 - Use the actual observed address of an incoming relay connection,
3950 not the canonical address of the relay from its descriptor, when
3951 making decisions about how to handle the incoming connection.
3952 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
3954 o Minor bugfix (directory authority, backport from 0.3.3.2-alpha):
3955 - Directory authorities, when refusing a descriptor from a rejected
3956 relay, now explicitly tell the relay (in its logs) to set a valid
3957 ContactInfo address and contact the bad-relays@ mailing list.
3958 Fixes bug 25170; bugfix on 0.2.9.1.
3960 o Minor bugfixes (address selection, backport from 0.3.2.9):
3961 - When the fascist_firewall_choose_address_ functions don't find a
3962 reachable address, set the returned address to the null address
3963 and port. This is a precautionary measure, because some callers do
3964 not check the return value. Fixes bug 24736; bugfix
3967 o Major bugfixes (bootstrapping, backport from 0.3.2.5-alpha):
3968 - Fetch descriptors aggressively whenever we lack enough to build
3969 circuits, regardless of how many descriptors we are missing.
3970 Previously, we would delay launching the fetch when we had fewer
3971 than 15 missing descriptors, even if some of those descriptors
3972 were blocking circuits from building. Fixes bug 23985; bugfix on
3973 0.1.1.11-alpha. The effects of this bug became worse in
3974 0.3.0.3-alpha, when we began treating missing descriptors from our
3975 primary guards as a reason to delay circuits.
3976 - Don't try fetching microdescriptors from relays that have failed
3977 to deliver them in the past. Fixes bug 23817; bugfix
3980 o Minor bugfixes (compilation, backport from 0.3.2.7-rc):
3981 - Fix a signed/unsigned comparison warning introduced by our fix to
3982 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
3984 o Minor bugfixes (control port, linux seccomp2 sandbox, backport from 0.3.2.5-alpha):
3985 - Avoid a crash when attempting to use the seccomp2 sandbox together
3986 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
3989 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
3990 - Fix a possible crash on malformed consensus. If a consensus had
3991 contained an unparseable protocol line, it could have made clients
3992 and relays crash with a null-pointer exception. To exploit this
3993 issue, however, an attacker would need to be able to subvert the
3994 directory authority system. Fixes bug 25251; bugfix on
3995 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
3997 o Minor bugfixes (directory cache, backport from 0.3.2.5-alpha):
3998 - Recover better from empty or corrupt files in the consensus cache
3999 directory. Fixes bug 24099; bugfix on 0.3.1.1-alpha.
4000 - When a consensus diff calculation is only partially successful,
4001 only record the successful parts as having succeeded. Partial
4002 success can happen if (for example) one compression method fails
4003 but the others succeed. Previously we misrecorded all the
4004 calculations as having succeeded, which would later cause a
4005 nonfatal assertion failure. Fixes bug 24086; bugfix
4008 o Minor bugfixes (entry guards, backport from 0.3.2.3-alpha):
4009 - Tor now updates its guard state when it reads a consensus
4010 regardless of whether it's missing descriptors. That makes tor use
4011 its primary guards to fetch descriptors in some edge cases where
4012 it would previously have used fallback directories. Fixes bug
4013 23862; bugfix on 0.3.0.1-alpha.
4015 o Minor bugfixes (logging, backport from 0.3.3.2-alpha):
4016 - Don't treat inability to store a cached consensus object as a bug:
4017 it can happen normally when we are out of disk space. Fixes bug
4018 24859; bugfix on 0.3.1.1-alpha.
4020 o Minor bugfixes (memory usage, backport from 0.3.2.8-rc):
4021 - When queuing DESTROY cells on a channel, only queue the circuit-id
4022 and reason fields: not the entire 514-byte cell. This fix should
4023 help mitigate any bugs or attacks that fill up these queues, and
4024 free more RAM for other uses. Fixes bug 24666; bugfix
4027 o Minor bugfixes (network layer, backport from 0.3.2.5-alpha):
4028 - When closing a connection via close_connection_immediately(), we
4029 mark it as "not blocked on bandwidth", to prevent later calls from
4030 trying to unblock it, and give it permission to read. This fixes a
4031 backtrace warning that can happen on relays under various
4032 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
4034 o Minor bugfixes (path selection, backport from 0.3.2.4-alpha):
4035 - When selecting relays by bandwidth, avoid a rounding error that
4036 could sometimes cause load to be imbalanced incorrectly.
4037 Previously, we would always round upwards; now, we round towards
4038 the nearest integer. This had the biggest effect when a relay's
4039 weight adjustments should have given it weight 0, but it got
4040 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
4041 - When calculating the fraction of nodes that have descriptors, and
4042 all nodes in the network have zero bandwidths, count the number of
4043 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
4044 - Actually log the total bandwidth in compute_weighted_bandwidths().
4045 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
4047 o Minor bugfixes (performance, fragile-hardening, backport from 0.3.3.1-alpha):
4048 - Improve the performance of our consensus-diff application code
4049 when Tor is built with the --enable-fragile-hardening option set.
4050 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
4052 o Minor bugfixes (OSX, backport from 0.3.3.1-alpha):
4053 - Don't exit the Tor process if setrlimit() fails to change the file
4054 limit (which can happen sometimes on some versions of OSX). Fixes
4055 bug 21074; bugfix on 0.0.9pre5.
4057 o Minor bugfixes (portability, msvc, backport from 0.3.2.9):
4058 - Fix a bug in the bit-counting parts of our timing-wheel code on
4059 MSVC. (Note that MSVC is still not a supported build platform, due
4060 to cyptographic timing channel risks.) Fixes bug 24633; bugfix
4063 o Minor bugfixes (relay, partial backport):
4064 - Make the internal channel_is_client() function look at what sort
4065 of connection handshake the other side used, rather than whether
4066 the other side ever sent a create_fast cell to us. Backports part
4067 of the fixes from bugs 22805 and 24898.
4069 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
4070 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
4072 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
4073 bugfix on 0.2.9.4-alpha.
4075 o Code simplification and refactoring (backport from 0.3.3.3-alpha):
4076 - Update the "rust dependencies" submodule to be a project-level
4077 repository, rather than a user repository. Closes ticket 25323.
4080 Changes in version 0.2.9.15 - 2018-03-03
4081 Tor 0.2.9.15 backports important security and stability bugfixes from
4084 It includes an important security fix for a remote crash attack
4085 against directory authorities, tracked as TROVE-2018-001.
4087 This release also backports our new system for improved resistance to
4088 denial-of-service attacks against relays.
4090 This release also fixes several minor bugs and annoyances from
4093 All directory authorities should upgrade to one of the versions
4094 released today. Relays running 0.2.9.x may wish to update to one of
4095 the versions released today, for the DoS mitigations.
4097 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
4098 - Fix a protocol-list handling bug that could be used to remotely crash
4099 directory authorities with a null-pointer exception. Fixes bug 25074;
4100 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
4103 o Major features (denial-of-service mitigation):
4104 - Give relays some defenses against the recent network overload. We
4105 start with three defenses (default parameters in parentheses).
4106 First: if a single client address makes too many concurrent
4107 connections (>100), hang up on further connections. Second: if a
4108 single client address makes circuits too quickly (more than 3 per
4109 second, with an allowed burst of 90) while also having too many
4110 connections open (3), refuse new create cells for the next while
4111 (1-2 hours). Third: if a client asks to establish a rendezvous
4112 point to you directly, ignore the request. These defenses can be
4113 manually controlled by new torrc options, but relays will also
4114 take guidance from consensus parameters, so there's no need to
4115 configure anything manually. Implements ticket 24902.
4117 o Major bugfixes (bootstrapping):
4118 - Fetch descriptors aggressively whenever we lack enough to build
4119 circuits, regardless of how many descriptors we are missing.
4120 Previously, we would delay launching the fetch when we had fewer
4121 than 15 missing descriptors, even if some of those descriptors
4122 were blocking circuits from building. Fixes bug 23985; bugfix on
4123 0.1.1.11-alpha. The effects of this bug became worse in
4124 0.3.0.3-alpha, when we began treating missing descriptors from our
4125 primary guards as a reason to delay circuits.
4127 o Major bugfixes (onion services, retry behavior):
4128 - Fix an "off by 2" error in counting rendezvous failures on the
4129 onion service side. While we thought we would stop the rendezvous
4130 attempt after one failed circuit, we were actually making three
4131 circuit attempts before giving up. Now switch to a default of 2,
4132 and allow the consensus parameter "hs_service_max_rdv_failures" to
4133 override. Fixes bug 24895; bugfix on 0.0.6.
4135 o Minor feature (relay statistics):
4136 - Change relay bandwidth reporting stats interval from 4 hours to 24
4137 hours in order to reduce the efficiency of guard discovery
4138 attacks. Fixes ticket 23856.
4140 o Minor features (compatibility, OpenSSL):
4141 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
4142 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
4143 since they neither disabled TLS 1.3 nor enabled any of the
4144 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
4145 Closes ticket 24978.
4147 o Minor features (denial-of-service avoidance):
4148 - Make our OOM handler aware of the geoip client history cache so it
4149 doesn't fill up the memory. This check is important for IPv6 and
4150 our DoS mitigation subsystem. Closes ticket 25122.
4152 o Minor features (fallback directory mirrors):
4153 - The fallback directory list has been re-generated based on the
4154 current status of the network. Tor uses fallback directories to
4155 bootstrap when it doesn't yet have up-to-date directory
4156 information. Closes ticket 24801.
4157 - Make the default DirAuthorityFallbackRate 0.1, so that clients
4158 prefer to bootstrap from fallback directory mirrors. This is a
4159 follow-up to 24679, which removed weights from the default
4160 fallbacks. Implements ticket 24681.
4162 o Minor features (geoip):
4163 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
4166 o Minor features (linux seccomp2 sandbox):
4167 - Update the sandbox rules so that they should now work correctly
4168 with Glibc 2.26. Closes ticket 24315.
4170 o Minor bugfix (channel connection):
4171 - Use the actual observed address of an incoming relay connection,
4172 not the canonical address of the relay from its descriptor, when
4173 making decisions about how to handle the incoming connection.
4174 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
4176 o Minor bugfix (directory authority):
4177 - Directory authorities, when refusing a descriptor from a rejected
4178 relay, now explicitly tell the relay (in its logs) to set a valid
4179 ContactInfo address and contact the bad-relays@ mailing list.
4180 Fixes bug 25170; bugfix on 0.2.9.1.
4182 o Minor bugfixes (address selection):
4183 - When the fascist_firewall_choose_address_ functions don't find a
4184 reachable address, set the returned address to the null address
4185 and port. This is a precautionary measure, because some callers do
4186 not check the return value. Fixes bug 24736; bugfix
4189 o Minor bugfixes (compilation):
4190 - Fix a signed/unsigned comparison warning introduced by our fix to
4191 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
4193 o Minor bugfixes (control port, linux seccomp2 sandbox):
4194 - Avoid a crash when attempting to use the seccomp2 sandbox together
4195 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
4198 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
4199 - Fix a possible crash on malformed consensus. If a consensus had
4200 contained an unparseable protocol line, it could have made clients
4201 and relays crash with a null-pointer exception. To exploit this
4202 issue, however, an attacker would need to be able to subvert the
4203 directory authority system. Fixes bug 25251; bugfix on
4204 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
4206 o Minor bugfixes (memory usage):
4207 - When queuing DESTROY cells on a channel, only queue the circuit-id
4208 and reason fields: not the entire 514-byte cell. This fix should
4209 help mitigate any bugs or attacks that fill up these queues, and
4210 free more RAM for other uses. Fixes bug 24666; bugfix
4213 o Minor bugfixes (network layer):
4214 - When closing a connection via close_connection_immediately(), we
4215 mark it as "not blocked on bandwidth", to prevent later calls from
4216 trying to unblock it, and give it permission to read. This fixes a
4217 backtrace warning that can happen on relays under various
4218 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
4220 o Minor bugfixes (OSX):
4221 - Don't exit the Tor process if setrlimit() fails to change the file
4222 limit (which can happen sometimes on some versions of OSX). Fixes
4223 bug 21074; bugfix on 0.0.9pre5.
4225 o Minor bugfixes (path selection):
4226 - When selecting relays by bandwidth, avoid a rounding error that
4227 could sometimes cause load to be imbalanced incorrectly.
4228 Previously, we would always round upwards; now, we round towards
4229 the nearest integer. This had the biggest effect when a relay's
4230 weight adjustments should have given it weight 0, but it got
4231 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
4232 - When calculating the fraction of nodes that have descriptors, and
4233 all nodes in the network have zero bandwidths, count the number of
4234 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
4235 - Actually log the total bandwidth in compute_weighted_bandwidths().
4236 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
4238 o Minor bugfixes (portability, msvc):
4239 - Fix a bug in the bit-counting parts of our timing-wheel code on
4240 MSVC. (Note that MSVC is still not a supported build platform, due
4241 to cryptographic timing channel risks.) Fixes bug 24633; bugfix
4244 o Minor bugfixes (relay):
4245 - Make the internal channel_is_client() function look at what sort
4246 of connection handshake the other side used, rather than whether
4247 the other side ever sent a create_fast cell to us. Backports part
4248 of the fixes from bugs 22805 and 24898.
4250 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
4251 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
4253 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
4254 bugfix on 0.2.9.4-alpha.
4257 Changes in version 0.3.2.10 - 2018-03-03
4258 Tor 0.3.2.10 is the second stable release in the 0.3.2 series. It
4259 backports a number of bugfixes, including important fixes for security
4262 It includes an important security fix for a remote crash attack
4263 against directory authorities, tracked as TROVE-2018-001.
4265 Additionally, it backports a fix for a bug whose severity we have
4266 upgraded: Bug 24700, which was fixed in 0.3.3.2-alpha, can be remotely
4267 triggered in order to crash relays with a use-after-free pattern. As
4268 such, we are now tracking that bug as TROVE-2018-002 and
4269 CVE-2018-0491, and backporting it to earlier releases. This bug
4270 affected versions 0.3.2.1-alpha through 0.3.2.9, as well as version
4273 This release also backports our new system for improved resistance to
4274 denial-of-service attacks against relays.
4276 This release also fixes several minor bugs and annoyances from
4279 Relays running 0.3.2.x SHOULD upgrade to one of the versions released
4280 today, for the fix to TROVE-2018-002. Directory authorities should
4281 also upgrade. (Relays on earlier versions might want to update too for
4282 the DoS mitigations.)
4284 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
4285 - Fix a protocol-list handling bug that could be used to remotely crash
4286 directory authorities with a null-pointer exception. Fixes bug 25074;
4287 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
4290 o Major bugfixes (scheduler, KIST, denial-of-service, backport from 0.3.3.2-alpha):
4291 - Avoid adding the same channel twice in the KIST scheduler pending
4292 list, which could lead to remote denial-of-service use-after-free
4293 attacks against relays. Fixes bug 24700; bugfix on 0.3.2.1-alpha.
4295 o Major features (denial-of-service mitigation, backport from 0.3.3.2-alpha):
4296 - Give relays some defenses against the recent network overload. We
4297 start with three defenses (default parameters in parentheses).
4298 First: if a single client address makes too many concurrent
4299 connections (>100), hang up on further connections. Second: if a
4300 single client address makes circuits too quickly (more than 3 per
4301 second, with an allowed burst of 90) while also having too many
4302 connections open (3), refuse new create cells for the next while
4303 (1-2 hours). Third: if a client asks to establish a rendezvous
4304 point to you directly, ignore the request. These defenses can be
4305 manually controlled by new torrc options, but relays will also
4306 take guidance from consensus parameters, so there's no need to
4307 configure anything manually. Implements ticket 24902.
4309 o Major bugfixes (onion services, retry behavior, backport from 0.3.3.1-alpha):
4310 - Fix an "off by 2" error in counting rendezvous failures on the
4311 onion service side. While we thought we would stop the rendezvous
4312 attempt after one failed circuit, we were actually making three
4313 circuit attempts before giving up. Now switch to a default of 2,
4314 and allow the consensus parameter "hs_service_max_rdv_failures" to
4315 override. Fixes bug 24895; bugfix on 0.0.6.
4316 - New-style (v3) onion services now obey the "max rendezvous circuit
4317 attempts" logic. Previously they would make as many rendezvous
4318 circuit attempts as they could fit in the MAX_REND_TIMEOUT second
4319 window before giving up. Fixes bug 24894; bugfix on 0.3.2.1-alpha.
4321 o Major bugfixes (protocol versions, backport from 0.3.3.2-alpha):
4322 - Add Link protocol version 5 to the supported protocols list. Fixes
4323 bug 25070; bugfix on 0.3.1.1-alpha.
4325 o Major bugfixes (relay, backport from 0.3.3.1-alpha):
4326 - Fix a set of false positives where relays would consider
4327 connections to other relays as being client-only connections (and
4328 thus e.g. deserving different link padding schemes) if those
4329 relays fell out of the consensus briefly. Now we look only at the
4330 initial handshake and whether the connection authenticated as a
4331 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
4333 o Major bugfixes (scheduler, consensus, backport from 0.3.3.2-alpha):
4334 - The scheduler subsystem was failing to promptly notice changes in
4335 consensus parameters, making it harder to switch schedulers
4336 network-wide. Fixes bug 24975; bugfix on 0.3.2.1-alpha.
4338 o Minor features (denial-of-service avoidance, backport from 0.3.3.2-alpha):
4339 - Make our OOM handler aware of the geoip client history cache so it
4340 doesn't fill up the memory. This check is important for IPv6 and
4341 our DoS mitigation subsystem. Closes ticket 25122.
4343 o Minor features (compatibility, OpenSSL, backport from 0.3.3.3-alpha):
4344 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
4345 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
4346 since they neither disabled TLS 1.3 nor enabled any of the
4347 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
4348 Closes ticket 24978.
4350 o Minor features (geoip):
4351 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
4354 o Minor features (logging, diagnostic, backport from 0.3.3.2-alpha):
4355 - When logging a failure to create an onion service's descriptor,
4356 also log what the problem with the descriptor was. Diagnostic
4359 o Minor bugfix (channel connection, backport from 0.3.3.2-alpha):
4360 - Use the actual observed address of an incoming relay connection,
4361 not the canonical address of the relay from its descriptor, when
4362 making decisions about how to handle the incoming connection.
4363 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
4365 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
4366 - Fix a possible crash on malformed consensus. If a consensus had
4367 contained an unparseable protocol line, it could have made clients
4368 and relays crash with a null-pointer exception. To exploit this
4369 issue, however, an attacker would need to be able to subvert the
4370 directory authority system. Fixes bug 25251; bugfix on
4371 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
4373 o Minor bugfix (directory authority, backport from 0.3.3.2-alpha):
4374 - Directory authorities, when refusing a descriptor from a rejected
4375 relay, now explicitly tell the relay (in its logs) to set a valid
4376 ContactInfo address and contact the bad-relays@ mailing list.
4377 Fixes bug 25170; bugfix on 0.2.9.1.
4379 o Minor bugfixes (build, rust, backport from 0.3.3.1-alpha):
4380 - When building with Rust on OSX, link against libresolv, to work
4381 around the issue at https://github.com/rust-lang/rust/issues/46797.
4382 Fixes bug 24652; bugfix on 0.3.1.1-alpha.
4384 o Minor bugfixes (onion services, backport from 0.3.3.2-alpha):
4385 - Remove a BUG() statement when a client fetches an onion descriptor
4386 that has a lower revision counter than the one in its cache. This
4387 can happen in normal circumstances due to HSDir desync. Fixes bug
4388 24976; bugfix on 0.3.2.1-alpha.
4390 o Minor bugfixes (logging, backport from 0.3.3.2-alpha):
4391 - Don't treat inability to store a cached consensus object as a bug:
4392 it can happen normally when we are out of disk space. Fixes bug
4393 24859; bugfix on 0.3.1.1-alpha.
4395 o Minor bugfixes (performance, fragile-hardening, backport from 0.3.3.1-alpha):
4396 - Improve the performance of our consensus-diff application code
4397 when Tor is built with the --enable-fragile-hardening option set.
4398 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
4400 o Minor bugfixes (OSX, backport from 0.3.3.1-alpha):
4401 - Don't exit the Tor process if setrlimit() fails to change the file
4402 limit (which can happen sometimes on some versions of OSX). Fixes
4403 bug 21074; bugfix on 0.0.9pre5.
4405 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
4406 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
4408 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
4409 bugfix on 0.2.9.4-alpha.
4411 o Minor bugfixes (testing, backport from 0.3.3.1-alpha):
4412 - Fix a memory leak in the scheduler/loop_kist unit test. Fixes bug
4413 25005; bugfix on 0.3.2.7-rc.
4415 o Minor bugfixes (v3 onion services, backport from 0.3.3.2-alpha):
4416 - Look at the "HSRend" protocol version, not the "HSDir" protocol
4417 version, when deciding whether a consensus entry can support the
4418 v3 onion service protocol as a rendezvous point. Fixes bug 25105;
4419 bugfix on 0.3.2.1-alpha.
4421 o Code simplification and refactoring (backport from 0.3.3.3-alpha):
4422 - Update the "rust dependencies" submodule to be a project-level
4423 repository, rather than a user repository. Closes ticket 25323.
4425 o Documentation (backport from 0.3.3.1-alpha)
4426 - Document that operators who run more than one relay or bridge are
4427 expected to set MyFamily and ContactInfo correctly. Closes
4431 Changes in version 0.3.3.3-alpha - 2018-03-03
4432 Tor 0.3.3.3-alpha is the third alpha release for the 0.3.3.x series.
4433 It includes an important security fix for a remote crash attack
4434 against directory authorities tracked as TROVE-2018-001.
4436 Additionally, with this release, we are upgrading the severity of a
4437 bug fixed in 0.3.3.2-alpha. Bug 24700, which was fixed in
4438 0.3.3.2-alpha, can be remotely triggered in order to crash relays with
4439 a use-after-free pattern. As such, we are now tracking that bug as
4440 TROVE-2018-002 and CVE-2018-0491. This bug affected versions
4441 0.3.2.1-alpha through 0.3.2.9, as well as 0.3.3.1-alpha.
4443 This release also fixes several minor bugs and annoyances from
4446 Relays running 0.3.2.x should upgrade to one of the versions released
4447 today, for the fix to TROVE-2018-002. Directory authorities should
4448 also upgrade. (Relays on earlier versions might want to update too for
4449 the DoS mitigations.)
4451 o Major bugfixes (denial-of-service, directory authority):
4452 - Fix a protocol-list handling bug that could be used to remotely crash
4453 directory authorities with a null-pointer exception. Fixes bug 25074;
4454 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
4457 o Minor features (compatibility, OpenSSL):
4458 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
4459 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
4460 since they neither disabled TLS 1.3 nor enabled any of the
4461 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
4462 Closes ticket 24978.
4464 o Minor features (logging):
4465 - Clarify the log messages produced when getrandom() or a related
4466 entropy-generation mechanism gives an error. Closes ticket 25120.
4468 o Minor features (testing):
4469 - Add a "make test-rust" target to run the rust tests only. Closes
4472 o Minor bugfixes (denial-of-service):
4473 - Fix a possible crash on malformed consensus. If a consensus had
4474 contained an unparseable protocol line, it could have made clients
4475 and relays crash with a null-pointer exception. To exploit this
4476 issue, however, an attacker would need to be able to subvert the
4477 directory authority system. Fixes bug 25251; bugfix on
4478 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
4480 o Minor bugfixes (DoS mitigation):
4481 - Add extra safety checks when refilling the circuit creation bucket
4482 to ensure we never set a value above the allowed maximum burst.
4483 Fixes bug 25202; bugfix on 0.3.3.2-alpha.
4484 - When a new consensus arrives, don't update our DoS-mitigation
4485 parameters if we aren't a public relay. Fixes bug 25223; bugfix
4488 o Minor bugfixes (man page, SocksPort):
4489 - Remove dead code from the old "SocksSocket" option, and rename
4490 SocksSocketsGroupWritable to UnixSocksGroupWritable. The old option
4491 still works, but is deprecated. Fixes bug 24343; bugfix on 0.2.6.3.
4493 o Minor bugfixes (performance):
4494 - Reduce the number of circuits that will be opened at once during
4495 the circuit build timeout phase. This is done by increasing the
4496 idle timeout to 3 minutes, and lowering the maximum number of
4497 concurrent learning circuits to 10. Fixes bug 24769; bugfix
4500 o Minor bugfixes (spec conformance):
4501 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
4503 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
4504 bugfix on 0.2.9.4-alpha.
4506 o Minor bugfixes (spec conformance, rust):
4507 - Resolve a denial-of-service issue caused by an infinite loop in
4508 the rust protover code. Fixes bug 25250, bugfix on 0.3.3.1-alpha.
4509 Also tracked as TROVE-2018-003.
4511 o Code simplification and refactoring:
4512 - Update the "rust dependencies" submodule to be a project-level
4513 repository, rather than a user repository. Closes ticket 25323.
4516 Changes in version 0.3.3.2-alpha - 2018-02-10
4517 Tor 0.3.3.2-alpha is the second alpha in the 0.3.3.x series. It
4518 introduces a mechanism to handle the high loads that many relay
4519 operators have been reporting recently. It also fixes several bugs in
4520 older releases. If this new code proves reliable, we plan to backport
4521 it to older supported release series.
4523 o Major features (denial-of-service mitigation):
4524 - Give relays some defenses against the recent network overload. We
4525 start with three defenses (default parameters in parentheses).
4526 First: if a single client address makes too many concurrent
4527 connections (>100), hang up on further connections. Second: if a
4528 single client address makes circuits too quickly (more than 3 per
4529 second, with an allowed burst of 90) while also having too many
4530 connections open (3), refuse new create cells for the next while
4531 (1-2 hours). Third: if a client asks to establish a rendezvous
4532 point to you directly, ignore the request. These defenses can be
4533 manually controlled by new torrc options, but relays will also
4534 take guidance from consensus parameters, so there's no need to
4535 configure anything manually. Implements ticket 24902.
4537 o Major bugfixes (netflow padding):
4538 - Stop adding unneeded channel padding right after we finish
4539 flushing to a connection that has been trying to flush for many
4540 seconds. Instead, treat all partial or complete flushes as
4541 activity on the channel, which will defer the time until we need
4542 to add padding. This fix should resolve confusing and scary log
4543 messages like "Channel padding timeout scheduled 221453ms in the
4544 past." Fixes bug 22212; bugfix on 0.3.1.1-alpha.
4546 o Major bugfixes (protocol versions):
4547 - Add Link protocol version 5 to the supported protocols list. Fixes
4548 bug 25070; bugfix on 0.3.1.1-alpha.
4550 o Major bugfixes (scheduler, consensus):
4551 - The scheduler subsystem was failing to promptly notice changes in
4552 consensus parameters, making it harder to switch schedulers
4553 network-wide. Fixes bug 24975; bugfix on 0.3.2.1-alpha.
4555 o Minor features (denial-of-service avoidance):
4556 - Make our OOM handler aware of the geoip client history cache so it
4557 doesn't fill up the memory. This check is important for IPv6 and
4558 our DoS mitigation subsystem. Closes ticket 25122.
4560 o Minor features (directory authority):
4561 - When directory authorities are unable to add signatures to a
4562 pending consensus, log the reason why. Closes ticket 24849.
4564 o Minor features (geoip):
4565 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
4568 o Minor features (logging, diagnostic):
4569 - When logging a failure to create an onion service's descriptor,
4570 also log what the problem with the descriptor was. Diagnostic for
4573 o Minor bugfix (channel connection):
4574 - Use the actual observed address of an incoming relay connection,
4575 not the canonical address of the relay from its descriptor, when
4576 making decisions about how to handle the incoming connection.
4577 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
4579 o Minor bugfix (directory authority):
4580 - Directory authorities, when refusing a descriptor from a rejected
4581 relay, now explicitly tell the relay (in its logs) to set a valid
4582 ContactInfo address and contact the bad-relays@ mailing list.
4583 Fixes bug 25170; bugfix on 0.2.9.1.
4585 o Minor bugfixes (all versions of Tor):
4586 - Use the "misspell" tool to detect and fix typos throughout the
4587 source code. Fixes bug 23650; bugfix on various versions of Tor.
4588 Patch from Deepesh Pathak.
4590 o Minor bugfixes (circuit, cannibalization):
4591 - Don't cannibalize preemptively-built circuits if we no longer
4592 recognize their first hop. This situation can happen if our Guard
4593 relay went off the consensus after the circuit was created. Fixes
4594 bug 24469; bugfix on 0.0.6.
4596 o Minor bugfixes (correctness):
4597 - Remove a nonworking, unnecessary check to see whether a circuit
4598 hop's identity digest was set when the circuit failed. Fixes bug
4599 24927; bugfix on 0.2.4.4-alpha.
4601 o Minor bugfixes (logging):
4602 - Don't treat inability to store a cached consensus object as a bug:
4603 it can happen normally when we are out of disk space. Fixes bug
4604 24859; bugfix on 0.3.1.1-alpha.
4605 - Fix a (mostly harmless) race condition when invoking
4606 LOG_PROTOCOL_WARN message from a subthread while the torrc options
4607 are changing. Fixes bug 23954; bugfix on 0.1.1.9-alpha.
4609 o Minor bugfixes (onion services):
4610 - Remove a BUG() statement when a client fetches an onion descriptor
4611 that has a lower revision counter than the one in its cache. This
4612 can happen in normal circumstances due to HSDir desync. Fixes bug
4613 24976; bugfix on 0.3.2.1-alpha.
4614 - If we are configured to offer a single onion service, don't log
4615 long-term established one hop rendezvous points in the heartbeat.
4616 Fixes bug 25116; bugfix on 0.2.9.6-rc.
4618 o Minor bugfixes (performance):
4619 - Avoid calling protocol_list_supports_protocol() from inside tight
4620 loops when running with cached routerinfo_t objects. Instead,
4621 summarize the relevant protocols as flags in the routerinfo_t, as
4622 we do for routerstatus_t objects. This change simplifies our code
4623 a little, and saves a large amount of short-term memory allocation
4624 operations. Fixes bug 25008; bugfix on 0.2.9.4-alpha.
4626 o Minor bugfixes (Rust FFI):
4627 - Fix a minor memory leak which would happen whenever the C code
4628 would call the Rust implementation of
4629 protover_get_supported_protocols(). This was due to the C version
4630 returning a static string, whereas the Rust version newly allocated
4631 a CString to pass across the FFI boundary. Consequently, the C
4632 code was not expecting to need to free() what it was given. Fixes
4633 bug 25127; bugfix on 0.3.2.1-alpha.
4635 o Minor bugfixes (scheduler, KIST):
4636 - Avoid adding the same channel twice in the KIST scheduler pending
4637 list, which would waste CPU cycles. Fixes bug 24700; bugfix
4640 o Minor bugfixes (unit test, monotonic time):
4641 - Increase a constant (1msec to 10msec) in the monotonic time test
4642 that makes sure the nsec/usec/msec times read are synchronized.
4643 This change was needed to accommodate slow systems like armel or
4644 when the clock_gettime() is not a VDSO on the running kernel.
4645 Fixes bug 25113; bugfix on 0.2.9.1.
4647 o Minor bugfixes (v3 onion services):
4648 - Look at the "HSRend" protocol version, not the "HSDir" protocol
4649 version, when deciding whether a consensus entry can support the
4650 v3 onion service protocol as a rendezvous point. Fixes bug 25105;
4651 bugfix on 0.3.2.1-alpha.
4653 o Code simplification and refactoring:
4654 - Remove the unused nodelist_recompute_all_hsdir_indices(). Closes
4656 - Remove a series of counters used to track circuit extend attempts
4657 and connection status but that in reality we aren't using for
4658 anything other than stats logged by a SIGUSR1 signal. Closes
4661 o Documentation (man page):
4662 - The HiddenServiceVersion torrc option accepts only one number:
4663 either version 2 or 3. Closes ticket 25026; bugfix
4667 Changes in version 0.3.3.1-alpha - 2018-01-25
4668 Tor 0.3.3.1-alpha is the first release in the 0.3.3.x series. It adds
4669 several new features to Tor, including several improvements to
4670 bootstrapping, and support for an experimental "vanguards" feature to
4671 resist guard discovery attacks. This series also includes better
4672 support for applications that need to embed Tor or manage v3
4675 o Major features (embedding):
4676 - There is now a documented stable API for programs that need to
4677 embed Tor. See tor_api.h for full documentation and known bugs.
4678 Closes ticket 23684.
4679 - Tor now has support for restarting in the same process.
4680 Controllers that run Tor using the "tor_api.h" interface can now
4681 restart Tor after Tor has exited. This support is incomplete,
4682 however: we fixed crash bugs that prevented it from working at
4683 all, but many bugs probably remain, including a possibility of
4684 security issues. Implements ticket 24581.
4686 o Major features (IPv6, directory documents):
4687 - Add consensus method 27, which adds IPv6 ORPorts to the microdesc
4688 consensus. This information makes it easier for IPv6 clients to
4689 bootstrap and choose reachable entry guards. Implements ticket 23826.
4690 - Add consensus method 28, which removes IPv6 ORPorts from
4691 microdescriptors. Now that the consensus contains IPv6 ORPorts, they
4692 are redundant in microdescs. This change will be used by Tor clients
4693 on 0.2.8.x and later. (That is to say, with all Tor clients that
4694 have IPv6 bootstrap and guard support.) Implements ticket 23828.
4695 - Expand the documentation for AuthDirHasIPv6Connectivity when it is
4696 set by different numbers of authorities. Fixes 23870
4699 o Major features (onion service v3, control port):
4700 - The control port now supports commands and events for v3 onion
4701 services. It is now possible to create ephemeral v3 services using
4702 ADD_ONION. Additionally, several events (HS_DESC, HS_DESC_CONTENT,
4703 CIRC and CIRC_MINOR) and commands (GETINFO, HSPOST, ADD_ONION and
4704 DEL_ONION) have been extended to support v3 onion services. Closes
4705 ticket 20699; implements proposal 284.
4707 o Major features (onion services):
4708 - Provide torrc options to pin the second and third hops of onion
4709 service circuits to a list of nodes. The option HSLayer2Guards
4710 pins the second hop, and the option HSLayer3Guards pins the third
4711 hop. These options are for use in conjunction with experiments
4712 with "vanguards" for preventing guard enumeration attacks. Closes
4715 o Major features (rust, portability, experimental):
4716 - Tor now ships with an optional implementation of one of its
4717 smaller modules (protover.c) in the Rust programming language. To
4718 try it out, install a Rust build environment, and configure Tor
4719 with "--enable-rust --enable-cargo-online-mode". This should not
4720 cause any user-visible changes, but should help us gain more
4721 experience with Rust, and plan future Rust integration work.
4722 Implementation by Chelsea Komlo. Closes ticket 22840.
4724 o Minor features (storage, configuration):
4725 - Users can store cached directory documents somewhere other than
4726 the DataDirectory by using the CacheDirectory option. Similarly,
4727 the storage location for relay's keys can be overridden with the
4728 KeyDirectory option. Closes ticket 22703.
4730 o Major features (v3 onion services, ipv6):
4731 - When v3 onion service clients send introduce cells, they now
4732 include the IPv6 address of the rendezvous point, if it has one.
4733 Current v3 onion services running 0.3.2 ignore IPv6 addresses, but
4734 in future Tor versions, IPv6-only v3 single onion services will be
4735 able to use IPv6 addresses to connect directly to the rendezvous
4736 point. Closes ticket 23577. Patch by Neel Chauhan.
4738 o Major bugfixes (onion services, retry behavior):
4739 - Fix an "off by 2" error in counting rendezvous failures on the
4740 onion service side. While we thought we would stop the rendezvous
4741 attempt after one failed circuit, we were actually making three
4742 circuit attempts before giving up. Now switch to a default of 2,
4743 and allow the consensus parameter "hs_service_max_rdv_failures" to
4744 override. Fixes bug 24895; bugfix on 0.0.6.
4745 - New-style (v3) onion services now obey the "max rendezvous circuit
4746 attempts" logic. Previously they would make as many rendezvous
4747 circuit attempts as they could fit in the MAX_REND_TIMEOUT second
4748 window before giving up. Fixes bug 24894; bugfix on 0.3.2.1-alpha.
4750 o Major bugfixes (relays):
4751 - Fix a set of false positives where relays would consider
4752 connections to other relays as being client-only connections (and
4753 thus e.g. deserving different link padding schemes) if those
4754 relays fell out of the consensus briefly. Now we look only at the
4755 initial handshake and whether the connection authenticated as a
4756 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
4758 o Minor feature (IPv6):
4759 - Make IPv6-only clients wait for microdescs for relays, even if we
4760 were previously using descriptors (or were using them as a bridge)
4761 and have a cached descriptor for them. Implements ticket 23827.
4762 - When a consensus has IPv6 ORPorts, make IPv6-only clients use
4763 them, rather than waiting to download microdescriptors.
4764 Implements ticket 23827.
4766 o Minor features (cleanup):
4767 - Tor now deletes the CookieAuthFile and ExtORPortCookieAuthFile
4768 when it stops. Closes ticket 23271.
4770 o Minor features (defensive programming):
4771 - Most of the functions in Tor that free objects have been replaced
4772 with macros that free the objects and set the corresponding
4773 pointers to NULL. This change should help prevent a large class of
4774 dangling pointer bugs. Closes ticket 24337.
4775 - Where possible, the tor_free() macro now only evaluates its input
4776 once. Part of ticket 24337.
4777 - Check that microdesc ed25519 ids are non-zero in
4778 node_get_ed25519_id() before returning them. Implements ticket
4779 24001, patch by "aruna1234".
4781 o Minor features (embedding):
4782 - Tor can now start with a preauthenticated control connection
4783 created by the process that launched it. This feature is meant for
4784 use by programs that want to launch and manage a Tor process
4785 without allowing other programs to manage it as well. For more
4786 information, see the __OwningControllerFD option documented in
4787 control-spec.txt. Closes ticket 23900.
4788 - On most errors that would cause Tor to exit, it now tries to
4789 return from the tor_main() function, rather than calling the
4790 system exit() function. Most users won't notice a difference here,
4791 but it should be significant for programs that run Tor inside
4792 a separate thread: they should now be able to survive Tor's exit
4793 conditions rather than having Tor shut down the entire process.
4794 Closes ticket 23848.
4795 - Applications that want to embed Tor can now tell Tor not to
4796 register any of its own POSIX signal handlers, using the
4797 __DisableSignalHandlers option. Closes ticket 24588.
4799 o Minor features (fallback directory list):
4800 - Avoid selecting fallbacks that change their IP addresses too
4801 often. Select more fallbacks by ignoring the Guard flag, and
4802 allowing lower cutoffs for the Running and V2Dir flags. Also allow
4803 a lower bandwidth, and a higher number of fallbacks per operator
4804 (5% of the list). Implements ticket 24785.
4805 - Update the fallback whitelist and blacklist based on opt-ins and
4806 relay changes. Closes tickets 22321, 24678, 22527, 24135,
4809 o Minor features (fallback directory mirror configuration):
4810 - Add a nickname to each fallback in a C comment. This makes it
4811 easier for operators to find their relays, and allows stem to use
4812 nicknames to identify fallbacks. Implements ticket 24600.
4813 - Add a type and version header to the fallback directory mirror
4814 file. Also add a delimiter to the end of each fallback entry. This
4815 helps external parsers like stem and Relay Search. Implements
4817 - Add an extrainfo cache flag for each fallback in a C comment. This
4818 allows stem to use fallbacks to fetch extra-info documents, rather
4819 than using authorities. Implements ticket 22759.
4820 - Add the generateFallbackDirLine.py script for automatically
4821 generating fallback directory mirror lines from relay fingerprints.
4822 No more typos! Add the lookupFallbackDirContact.py script for
4823 automatically looking up operator contact info from relay
4824 fingerprints. Implements ticket 24706, patch by teor and atagar.
4825 - Reject any fallback directory mirror that serves an expired
4826 consensus. Implements ticket 20942, patch by "minik".
4827 - Remove commas and equals signs from external string inputs to the
4828 fallback list. This avoids format confusion attacks. Implements
4830 - Remove the "weight=10" line from fallback directory mirror
4831 entries. Ticket 24681 will maintain the current fallback weights
4832 by changing Tor's default fallback weight to 10. Implements
4834 - Stop logging excessive information about fallback netblocks.
4835 Implements ticket 24791.
4837 o Minor features (forward-compatibility):
4838 - If a relay supports some link authentication protocol that we do
4839 not recognize, then include that relay's ed25519 key when telling
4840 other relays to extend to it. Previously, we treated future
4841 versions as if they were too old to support ed25519 link
4842 authentication. Closes ticket 20895.
4844 o Minor features (heartbeat):
4845 - Add onion service information to our heartbeat logs, displaying
4846 stats about the activity of configured onion services. Closes
4849 o Minor features (instrumentation, development):
4850 - Add the MainloopStats option to allow developers to get
4851 instrumentation information from the main event loop via the
4852 heartbeat messages. We hope to use this to improve Tor's behavior
4853 when it's trying to sleep. Closes ticket 24605.
4855 o Minor features (log messages):
4856 - Improve a warning message that happens when we fail to re-parse an
4857 old router because of an expired certificate. Closes ticket 20020.
4858 - Make the log more quantitative when we hit MaxMemInQueues
4859 threshold exposing some values. Closes ticket 24501.
4861 o Minor features (logging, android):
4862 - Added support for the Android logging subsystem. Closes
4865 o Minor features (performance):
4866 - Support predictive circuit building for onion service circuits
4867 with multiple layers of guards. Closes ticket 23101.
4868 - Use stdatomic.h where available, rather than mutexes, to implement
4869 atomic_counter_t. Closes ticket 23953.
4871 o Minor features (performance, 32-bit):
4872 - Improve performance on 32-bit systems by avoiding 64-bit division
4873 when calculating the timestamp in milliseconds for channel padding
4874 computations. Implements ticket 24613.
4875 - Improve performance on 32-bit systems by avoiding 64-bit division
4876 when timestamping cells and buffer chunks for OOM calculations.
4877 Implements ticket 24374.
4879 o Minor features (performance, OSX, iOS):
4880 - Use the mach_approximate_time() function (when available) to
4881 implement coarse monotonic time. Having a coarse time function
4882 should avoid a large number of system calls, and improve
4883 performance slightly, especially under load. Closes ticket 24427.
4885 o Minor features (performance, windows):
4886 - Improve performance on Windows Vista and Windows 7 by adjusting
4887 TCP send window size according to the recommendation from
4888 SIO_IDEAL_SEND_BACKLOG_QUERY. Closes ticket 22798. Patch
4891 o Major features (relay):
4892 - Implement an option, ReducedExitPolicy, to allow an Tor exit relay
4893 operator to use a more reasonable ("reduced") exit policy, rather
4894 than the default one. If you want to run an exit node without
4895 thinking too hard about which ports to allow, this one is for you.
4896 Closes ticket 13605. Patch from Neel Chauhan.
4898 o Minor features (testing, debugging, embedding):
4899 - For development purposes, Tor now has a mode in which it runs for
4900 a few seconds, then stops, and starts again without exiting the
4901 process. This mode is meant to help us debug various issues with
4902 ticket 23847. To use this feature, compile with
4903 --enable-restart-debugging, and set the TOR_DEBUG_RESTART
4904 environment variable. This is expected to crash a lot, and is
4905 really meant for developers only. It will likely be removed in a
4906 future release. Implements ticket 24583.
4908 o Minor bugfix (network IPv6 test):
4909 - Tor's test scripts now check if "ping -6 ::1" works when the user
4910 runs "make test-network-all". Fixes bug 24677; bugfix on
4911 0.2.9.3-alpha. Patch by "ffmancera".
4913 o Minor bugfixes (build, rust):
4914 - Fix output of autoconf checks to display success messages for Rust
4915 dependencies and a suitable rustc compiler version. Fixes bug
4916 24612; bugfix on 0.3.1.3-alpha.
4917 - When building with Rust on OSX, link against libresolv, to work
4918 around the issue at https://github.com/rust-lang/rust/issues/46797.
4919 Fixes bug 24652; bugfix on 0.3.1.1-alpha.
4920 - Don't pass the --quiet option to cargo: it seems to suppress some
4921 errors, which is not what we want to do when building. Fixes bug
4922 24518; bugfix on 0.3.1.7.
4923 - Build correctly when building from outside Tor's source tree with
4924 the TOR_RUST_DEPENDENCIES option set. Fixes bug 22768; bugfix
4927 o Minor bugfixes (directory authorities, IPv6):
4928 - When creating a routerstatus (vote) from a routerinfo (descriptor),
4929 set the IPv6 address to the unspecified IPv6 address, and
4930 explicitly initialize the port to zero. Fixes bug 24488; bugfix
4933 o Minor bugfixes (fallback directory mirrors):
4934 - Make updateFallbackDirs.py search harder for python. (Some OSs
4935 don't put it in /usr/bin.) Fixes bug 24708; bugfix
4938 o Minor bugfixes (hibernation, bandwidth accounting, shutdown):
4939 - When hibernating, close connections normally and allow them to
4940 flush. Fixes bug 23571; bugfix on 0.2.4.7-alpha. Also fixes
4942 - Do not attempt to launch self-reachability tests when entering
4943 hibernation. Fixes a case of bug 12062; bugfix on 0.0.9pre5.
4944 - Resolve several bugs related to descriptor fetching on bridge
4945 clients with bandwidth accounting enabled. (This combination is
4946 not recommended!) Fixes a case of bug 12062; bugfix
4948 - When hibernating, do not attempt to launch DNS checks. Fixes a
4949 case of bug 12062; bugfix on 0.1.2.2-alpha.
4950 - When hibernating, do not try to upload or download descriptors.
4951 Fixes a case of bug 12062; bugfix on 0.0.9pre5.
4953 o Minor bugfixes (IPv6, bridges):
4954 - Tor now always sets IPv6 preferences for bridges. Fixes bug 24573;
4955 bugfix on 0.2.8.2-alpha.
4956 - Tor now sets IPv6 address in the routerstatus as well as in the
4957 router descriptors when updating addresses for a bridge. Closes
4958 ticket 24572; bugfix on 0.2.4.5-alpha. Patch by "ffmancera".
4960 o Minor bugfixes (linux seccomp2 sandbox):
4961 - When running with the sandbox enabled, reload configuration files
4962 correctly even when %include was used. Previously we would crash.
4963 Fixes bug 22605; bugfix on 0.3.1. Patch from Daniel Pinto.
4965 o Minor bugfixes (memory leaks):
4966 - Avoid possible at-exit memory leaks related to use of Libevent's
4967 event_base_once() function. (This function tends to leak memory if
4968 the event_base is closed before the event fires.) Fixes bug 24584;
4969 bugfix on 0.2.8.1-alpha.
4970 - Fix a harmless memory leak in tor-resolve. Fixes bug 24582; bugfix
4973 o Minor bugfixes (OSX):
4974 - Don't exit the Tor process if setrlimit() fails to change the file
4975 limit (which can happen sometimes on some versions of OSX). Fixes
4976 bug 21074; bugfix on 0.0.9pre5.
4978 o Minor bugfixes (performance, fragile-hardening):
4979 - Improve the performance of our consensus-diff application code
4980 when Tor is built with the --enable-fragile-hardening option set.
4981 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
4983 o Minor bugfixes (performance, timeouts):
4984 - Consider circuits for timeout as soon as they complete a hop. This
4985 is more accurate than applying the timeout in
4986 circuit_expire_building() because that function is only called
4987 once per second, which is now too slow for typical timeouts on the
4988 current network. Fixes bug 23114; bugfix on 0.2.2.2-alpha.
4989 - Use onion service circuits (and other circuits longer than 3 hops)
4990 to calculate a circuit build timeout. Previously, Tor only
4991 calculated its build timeout based on circuits that planned to be
4992 exactly 3 hops long. With this change, we include measurements
4993 from all circuits at the point where they complete their third
4994 hop. Fixes bug 23100; bugfix on 0.2.2.2-alpha.
4996 o Minor bugfixes (testing):
4997 - Give out Exit flags in bootstrapping networks. Fixes bug 24137;
4998 bugfix on 0.2.3.1-alpha.
4999 - Fix a memory leak in the scheduler/loop_kist unit test. Fixes bug
5000 25005; bugfix on 0.3.2.7-rc.
5002 o Code simplification and refactoring:
5003 - Remove /usr/athena from search path in configure.ac. Closes
5005 - Remove duplicate code in node_has_curve25519_onion_key() and
5006 node_get_curve25519_onion_key(), and add a check for a zero
5007 microdesc curve25519 onion key. Closes ticket 23966, patch by
5008 "aruna1234" and teor.
5009 - Rewrite channel_rsa_id_group_set_badness to reduce temporary
5010 memory allocations with large numbers of OR connections (e.g.
5011 relays). Closes ticket 24119.
5012 - Separate the function that deletes ephemeral files when Tor
5014 - Small changes to Tor's buf_t API to make it suitable for use as a
5015 general-purpose safe string constructor. Closes ticket 22342.
5016 - Switch -Wnormalized=id to -Wnormalized=nfkc in configure.ac to
5017 avoid source code identifier confusion. Closes ticket 24467.
5018 - The tor_git_revision[] constant no longer needs to be redeclared
5019 by everything that links against the rest of Tor. Done as part of
5020 ticket 23845, to simplify our external API.
5021 - We make extend_info_from_node() use node_get_curve25519_onion_key()
5022 introduced in ticket 23577 to access the curve25519 public keys
5023 rather than accessing it directly. Closes ticket 23760. Patch by
5025 - Add a function to log channels' scheduler state changes to aid
5026 debugging efforts. Closes ticket 24531.
5029 - Add documentation on how to build tor with Rust dependencies
5030 without having to be online. Closes ticket 22907; bugfix
5032 - Clarify the behavior of RelayBandwidth{Rate,Burst} with client
5033 traffic. Closes ticket 24318.
5034 - Document that OutboundBindAddress doesn't apply to DNS requests.
5035 Closes ticket 22145. Patch from Aruna Maurya.
5036 - Document that operators who run more than one relay or bridge are
5037 expected to set MyFamily and ContactInfo correctly. Closes
5040 o Code simplification and refactoring (channels):
5041 - Remove the incoming and outgoing channel queues. These were never
5042 used, but still took up a step in our fast path.
5043 - The majority of the channel unit tests have been rewritten and the
5044 code coverage has now been raised to 83.6% for channel.c. Closes
5046 - Remove other dead code from the channel subsystem: All together,
5047 this cleanup has removed more than 1500 lines of code overall and
5048 adding very little except for unit test.
5050 o Code simplification and refactoring (circuit rendezvous):
5051 - Split the client-side rendezvous circuit lookup into two
5052 functions: one that returns only established circuits and another
5053 that returns all kinds of circuits. Closes ticket 23459.
5055 o Code simplification and refactoring (controller):
5056 - Make most of the variables in networkstatus_getinfo_by_purpose()
5057 const. Implements ticket 24489.
5060 Changes in version 0.3.2.9 - 2018-01-09
5061 Tor 0.3.2.9 is the first stable release in the 0.3.2 series.
5063 The 0.3.2 series includes our long-anticipated new onion service
5064 design, with numerous security features. (For more information, see
5065 our blog post at https://blog.torproject.org/fall-harvest.) We also
5066 have a new circuit scheduler algorithm for improved performance on
5067 relays everywhere (see https://blog.torproject.org/kist-and-tell),
5068 along with many smaller features and bugfixes.
5070 Per our stable release policy, we plan to support each stable release
5071 series for at least the next nine months, or for three months after
5072 the first stable release of the next series: whichever is longer. If
5073 you need a release with long-term support, we recommend that you stay
5074 with the 0.2.9 series.
5076 Below is a list of the changes since 0.3.2.8-rc. For a list of all
5077 changes since 0.3.1, see the ReleaseNotes file.
5079 o Minor features (fallback directory mirrors):
5080 - The fallback directory list has been re-generated based on the
5081 current status of the network. Tor uses fallback directories to
5082 bootstrap when it doesn't yet have up-to-date directory
5083 information. Closes ticket 24801.
5084 - Make the default DirAuthorityFallbackRate 0.1, so that clients
5085 prefer to bootstrap from fallback directory mirrors. This is a
5086 follow-up to 24679, which removed weights from the default
5087 fallbacks. Implements ticket 24681.
5089 o Minor features (geoip):
5090 - Update geoip and geoip6 to the January 5 2018 Maxmind GeoLite2
5093 o Minor bugfixes (address selection):
5094 - When the fascist_firewall_choose_address_ functions don't find a
5095 reachable address, set the returned address to the null address
5096 and port. This is a precautionary measure, because some callers do
5097 not check the return value. Fixes bug 24736; bugfix
5100 o Minor bugfixes (compilation):
5101 - Resolve a few shadowed-variable warnings in the onion service
5102 code. Fixes bug 24634; bugfix on 0.3.2.1-alpha.
5104 o Minor bugfixes (portability, msvc):
5105 - Fix a bug in the bit-counting parts of our timing-wheel code on
5106 MSVC. (Note that MSVC is still not a supported build platform, due
5107 to cryptographic timing channel risks.) Fixes bug 24633; bugfix
5111 Changes in version 0.3.2.8-rc - 2017-12-21
5112 Tor 0.3.2.8-rc fixes a pair of bugs in the KIST and KISTLite
5113 schedulers that had led servers under heavy load to overload their
5114 outgoing connections. All relay operators running earlier 0.3.2.x
5115 versions should upgrade. This version also includes a mitigation for
5116 over-full DESTROY queues leading to out-of-memory conditions: if it
5117 works, we will soon backport it to earlier release series.
5119 This is the second release candidate in the 0.3.2 series. If we find
5120 no new bugs or regression here, then the first stable 0.3.2 release
5121 will be nearly identical to this.
5123 o Major bugfixes (KIST, scheduler):
5124 - The KIST scheduler did not correctly account for data already
5125 enqueued in each connection's send socket buffer, particularly in
5126 cases when the TCP/IP congestion window was reduced between
5127 scheduler calls. This situation lead to excessive per-connection
5128 buffering in the kernel, and a potential memory DoS. Fixes bug
5129 24665; bugfix on 0.3.2.1-alpha.
5131 o Minor features (geoip):
5132 - Update geoip and geoip6 to the December 6 2017 Maxmind GeoLite2
5135 o Minor bugfixes (hidden service v3):
5136 - Bump hsdir_spread_store parameter from 3 to 4 in order to increase
5137 the probability of reaching a service for a client missing
5138 microdescriptors. Fixes bug 24425; bugfix on 0.3.2.1-alpha.
5140 o Minor bugfixes (memory usage):
5141 - When queuing DESTROY cells on a channel, only queue the circuit-id
5142 and reason fields: not the entire 514-byte cell. This fix should
5143 help mitigate any bugs or attacks that fill up these queues, and
5144 free more RAM for other uses. Fixes bug 24666; bugfix
5147 o Minor bugfixes (scheduler, KIST):
5148 - Use a sane write limit for KISTLite when writing onto a connection
5149 buffer instead of using INT_MAX and shoving as much as it can.
5150 Because the OOM handler cleans up circuit queues, we are better
5151 off at keeping them in that queue instead of the connection's
5152 buffer. Fixes bug 24671; bugfix on 0.3.2.1-alpha.
5155 Changes in version 0.3.2.7-rc - 2017-12-14
5156 Tor 0.3.2.7-rc fixes various bugs in earlier versions of Tor,
5157 including some that could affect reliability or correctness.
5159 This is the first release candidate in the 0.3.2 series. If we find no
5160 new bugs or regression here, then the first stable 0.3.2. release will
5161 be nearly identical to this.
5163 o Major bugfixes (circuit prediction):
5164 - Fix circuit prediction logic so that a client doesn't treat a port
5165 as being "handled" by a circuit if that circuit already has
5166 isolation settings on it. This change should make Tor clients more
5167 responsive by improving their chances of having a pre-created
5168 circuit ready for use when a request arrives. Fixes bug 18859;
5169 bugfix on 0.2.3.3-alpha.
5171 o Minor features (logging):
5172 - Provide better warnings when the getrandom() syscall fails. Closes
5175 o Minor features (portability):
5176 - Tor now compiles correctly on arm64 with libseccomp-dev installed.
5177 (It doesn't yet work with the sandbox enabled.) Closes
5180 o Minor bugfixes (bridge clients, bootstrap):
5181 - Retry directory downloads when we get our first bridge descriptor
5182 during bootstrap or while reconnecting to the network. Keep
5183 retrying every time we get a bridge descriptor, until we have a
5184 reachable bridge. Fixes part of bug 24367; bugfix on 0.2.0.3-alpha.
5185 - Stop delaying bridge descriptor fetches when we have cached bridge
5186 descriptors. Instead, only delay bridge descriptor fetches when we
5187 have at least one reachable bridge. Fixes part of bug 24367;
5188 bugfix on 0.2.0.3-alpha.
5189 - Stop delaying directory fetches when we have cached bridge
5190 descriptors. Instead, only delay bridge descriptor fetches when
5191 all our bridges are definitely unreachable. Fixes part of bug
5192 24367; bugfix on 0.2.0.3-alpha.
5194 o Minor bugfixes (compilation):
5195 - Fix a signed/unsigned comparison warning introduced by our fix to
5196 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
5198 o Minor bugfixes (correctness):
5199 - Fix several places in our codebase where a C compiler would be
5200 likely to eliminate a check, based on assuming that undefined
5201 behavior had not happened elsewhere in the code. These cases are
5202 usually a sign of redundant checking or dubious arithmetic. Found
5203 by Georg Koppen using the "STACK" tool from Wang, Zeldovich,
5204 Kaashoek, and Solar-Lezama. Fixes bug 24423; bugfix on various
5207 o Minor bugfixes (onion service v3):
5208 - Fix a race where an onion service would launch a new intro circuit
5209 after closing an old one, but fail to register it before freeing
5210 the previously closed circuit. This bug was making the service
5211 unable to find the established intro circuit and thus not upload
5212 its descriptor, thus making a service unavailable for up to 24
5213 hours. Fixes bug 23603; bugfix on 0.3.2.1-alpha.
5215 o Minor bugfixes (scheduler, KIST):
5216 - Properly set the scheduler state of an unopened channel in the
5217 KIST scheduler main loop. This prevents a harmless but annoying
5218 log warning. Fixes bug 24502; bugfix on 0.3.2.4-alpha.
5219 - Avoid a possible integer overflow when computing the available
5220 space on the TCP buffer of a channel. This had no security
5221 implications; but could make KIST allow too many cells on a
5222 saturated connection. Fixes bug 24590; bugfix on 0.3.2.1-alpha.
5223 - Downgrade to "info" a harmless warning about the monotonic time
5224 moving backwards: This can happen on platform not supporting
5225 monotonic time. Fixes bug 23696; bugfix on 0.3.2.1-alpha.
5228 Changes in version 0.3.2.6-alpha - 2017-12-01
5229 This version of Tor is the latest in the 0.3.2 alpha series. It
5230 includes fixes for several important security issues. All Tor users
5231 should upgrade to this release, or to one of the other releases coming
5234 o Major bugfixes (security):
5235 - Fix a denial of service bug where an attacker could use a
5236 malformed directory object to cause a Tor instance to pause while
5237 OpenSSL would try to read a passphrase from the terminal. (Tor
5238 instances run without a terminal, which is the case for most Tor
5239 packages, are not impacted.) Fixes bug 24246; bugfix on every
5240 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
5241 Found by OSS-Fuzz as testcase 6360145429790720.
5242 - Fix a denial of service issue where an attacker could crash a
5243 directory authority using a malformed router descriptor. Fixes bug
5244 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
5246 - When checking for replays in the INTRODUCE1 cell data for a
5247 (legacy) onion service, correctly detect replays in the RSA-
5248 encrypted part of the cell. We were previously checking for
5249 replays on the entire cell, but those can be circumvented due to
5250 the malleability of Tor's legacy hybrid encryption. This fix helps
5251 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
5252 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
5255 o Major bugfixes (security, onion service v2):
5256 - Fix a use-after-free error that could crash v2 Tor onion services
5257 when they failed to open circuits while expiring introduction
5258 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
5259 also tracked as TROVE-2017-013 and CVE-2017-8823.
5261 o Major bugfixes (security, relay):
5262 - When running as a relay, make sure that we never build a path
5263 through ourselves, even in the case where we have somehow lost the
5264 version of our descriptor appearing in the consensus. Fixes part
5265 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
5266 as TROVE-2017-012 and CVE-2017-8822.
5267 - When running as a relay, make sure that we never choose ourselves
5268 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
5269 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
5271 o Minor feature (relay statistics):
5272 - Change relay bandwidth reporting stats interval from 4 hours to 24
5273 hours in order to reduce the efficiency of guard discovery
5274 attacks. Fixes ticket 23856.
5276 o Minor features (directory authority):
5277 - Add an IPv6 address for the "bastet" directory authority. Closes
5280 o Minor bugfixes (client):
5281 - By default, do not enable storage of client-side DNS values. These
5282 values were unused by default previously, but they should not have
5283 been cached at all. Fixes bug 24050; bugfix on 0.2.6.3-alpha.
5286 Changes in version 0.3.1.9 - 2017-12-01:
5287 Tor 0.3.1.9 backports important security and stability fixes from the
5288 0.3.2 development series. All Tor users should upgrade to this
5289 release, or to another of the releases coming out today.
5291 o Major bugfixes (security, backport from 0.3.2.6-alpha):
5292 - Fix a denial of service bug where an attacker could use a
5293 malformed directory object to cause a Tor instance to pause while
5294 OpenSSL would try to read a passphrase from the terminal. (Tor
5295 instances run without a terminal, which is the case for most Tor
5296 packages, are not impacted.) Fixes bug 24246; bugfix on every
5297 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
5298 Found by OSS-Fuzz as testcase 6360145429790720.
5299 - Fix a denial of service issue where an attacker could crash a
5300 directory authority using a malformed router descriptor. Fixes bug
5301 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
5303 - When checking for replays in the INTRODUCE1 cell data for a
5304 (legacy) onion service, correctly detect replays in the RSA-
5305 encrypted part of the cell. We were previously checking for
5306 replays on the entire cell, but those can be circumvented due to
5307 the malleability of Tor's legacy hybrid encryption. This fix helps
5308 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
5309 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
5312 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
5313 - Fix a use-after-free error that could crash v2 Tor onion services
5314 when they failed to open circuits while expiring introduction
5315 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
5316 also tracked as TROVE-2017-013 and CVE-2017-8823.
5318 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
5319 - When running as a relay, make sure that we never build a path
5320 through ourselves, even in the case where we have somehow lost the
5321 version of our descriptor appearing in the consensus. Fixes part
5322 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
5323 as TROVE-2017-012 and CVE-2017-8822.
5324 - When running as a relay, make sure that we never choose ourselves
5325 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
5326 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
5328 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
5329 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
5330 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
5331 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
5332 identifying and finding a workaround to this bug and to Moritz,
5333 Arthur Edelstein, and Roger for helping to track it down and
5336 o Minor features (bridge):
5337 - Bridges now include notice in their descriptors that they are
5338 bridges, and notice of their distribution status, based on their
5339 publication settings. Implements ticket 18329. For more fine-
5340 grained control of how a bridge is distributed, upgrade to 0.3.2.x
5343 o Minor features (directory authority, backport from 0.3.2.6-alpha):
5344 - Add an IPv6 address for the "bastet" directory authority. Closes
5347 o Minor features (geoip):
5348 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
5351 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
5352 - Avoid unnecessary calls to directory_fetches_from_authorities() on
5353 relays, to prevent spurious address resolutions and descriptor
5354 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
5355 bugfix on in 0.2.8.1-alpha.
5357 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
5358 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
5359 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
5361 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
5362 - When a circuit is marked for close, do not attempt to package any
5363 cells for channels on that circuit. Previously, we would detect
5364 this condition lower in the call stack, when we noticed that the
5365 circuit had no attached channel, and log an annoying message.
5366 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
5368 o Minor bugfixes (onion service, backport from 0.3.2.5-alpha):
5369 - Rename the consensus parameter "hsdir-interval" to "hsdir_interval"
5370 so it matches dir-spec.txt. Fixes bug 24262; bugfix
5373 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
5374 - Avoid a crash when transitioning from client mode to bridge mode.
5375 Previously, we would launch the worker threads whenever our
5376 "public server" mode changed, but not when our "server" mode
5377 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
5380 Changes in version 0.3.0.13 - 2017-12-01
5381 Tor 0.3.0.13 backports important security and stability bugfixes from
5382 later Tor releases. All Tor users should upgrade to this release, or
5383 to another of the releases coming out today.
5385 Note: the Tor 0.3.0 series will no longer be supported after 26 Jan
5386 2018. If you need a release with long-term support, please stick with
5387 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
5389 o Major bugfixes (security, backport from 0.3.2.6-alpha):
5390 - Fix a denial of service bug where an attacker could use a
5391 malformed directory object to cause a Tor instance to pause while
5392 OpenSSL would try to read a passphrase from the terminal. (Tor
5393 instances run without a terminal, which is the case for most Tor
5394 packages, are not impacted.) Fixes bug 24246; bugfix on every
5395 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
5396 Found by OSS-Fuzz as testcase 6360145429790720.
5397 - Fix a denial of service issue where an attacker could crash a
5398 directory authority using a malformed router descriptor. Fixes bug
5399 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
5401 - When checking for replays in the INTRODUCE1 cell data for a
5402 (legacy) onion service, correctly detect replays in the RSA-
5403 encrypted part of the cell. We were previously checking for
5404 replays on the entire cell, but those can be circumvented due to
5405 the malleability of Tor's legacy hybrid encryption. This fix helps
5406 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
5407 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
5410 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
5411 - Fix a use-after-free error that could crash v2 Tor onion services
5412 when they failed to open circuits while expiring introduction
5413 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
5414 also tracked as TROVE-2017-013 and CVE-2017-8823.
5416 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
5417 - When running as a relay, make sure that we never build a path
5418 through ourselves, even in the case where we have somehow lost the
5419 version of our descriptor appearing in the consensus. Fixes part
5420 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
5421 as TROVE-2017-012 and CVE-2017-8822.
5422 - When running as a relay, make sure that we never choose ourselves
5423 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
5424 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
5426 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
5427 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
5428 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
5429 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
5430 identifying and finding a workaround to this bug and to Moritz,
5431 Arthur Edelstein, and Roger for helping to track it down and
5434 o Minor features (security, windows, backport from 0.3.1.1-alpha):
5435 - Enable a couple of pieces of Windows hardening: one
5436 (HeapEnableTerminationOnCorruption) that has been on-by-default
5437 since Windows 8, and unavailable before Windows 7; and one
5438 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
5439 affect us, but shouldn't do any harm. Closes ticket 21953.
5441 o Minor features (bridge, backport from 0.3.1.9):
5442 - Bridges now include notice in their descriptors that they are
5443 bridges, and notice of their distribution status, based on their
5444 publication settings. Implements ticket 18329. For more fine-
5445 grained control of how a bridge is distributed, upgrade to 0.3.2.x
5448 o Minor features (directory authority, backport from 0.3.2.6-alpha):
5449 - Add an IPv6 address for the "bastet" directory authority. Closes
5452 o Minor features (geoip):
5453 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
5456 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
5457 - Avoid unnecessary calls to directory_fetches_from_authorities() on
5458 relays, to prevent spurious address resolutions and descriptor
5459 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
5460 bugfix on in 0.2.8.1-alpha.
5462 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
5463 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
5464 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
5466 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
5467 - When a circuit is marked for close, do not attempt to package any
5468 cells for channels on that circuit. Previously, we would detect
5469 this condition lower in the call stack, when we noticed that the
5470 circuit had no attached channel, and log an annoying message.
5471 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
5473 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
5474 - Avoid a crash when transitioning from client mode to bridge mode.
5475 Previously, we would launch the worker threads whenever our
5476 "public server" mode changed, but not when our "server" mode
5477 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
5479 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
5480 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
5481 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
5484 Changes in version 0.2.9.14 - 2017-12-01
5485 Tor 0.3.0.13 backports important security and stability bugfixes from
5486 later Tor releases. All Tor users should upgrade to this release, or
5487 to another of the releases coming out today.
5489 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
5490 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
5491 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
5492 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
5493 identifying and finding a workaround to this bug and to Moritz,
5494 Arthur Edelstein, and Roger for helping to track it down and
5497 o Major bugfixes (security, backport from 0.3.2.6-alpha):
5498 - Fix a denial of service bug where an attacker could use a
5499 malformed directory object to cause a Tor instance to pause while
5500 OpenSSL would try to read a passphrase from the terminal. (Tor
5501 instances run without a terminal, which is the case for most Tor
5502 packages, are not impacted.) Fixes bug 24246; bugfix on every
5503 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
5504 Found by OSS-Fuzz as testcase 6360145429790720.
5505 - Fix a denial of service issue where an attacker could crash a
5506 directory authority using a malformed router descriptor. Fixes bug
5507 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
5509 - When checking for replays in the INTRODUCE1 cell data for a
5510 (legacy) onion service, correctly detect replays in the RSA-
5511 encrypted part of the cell. We were previously checking for
5512 replays on the entire cell, but those can be circumvented due to
5513 the malleability of Tor's legacy hybrid encryption. This fix helps
5514 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
5515 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
5518 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
5519 - Fix a use-after-free error that could crash v2 Tor onion services
5520 when they failed to open circuits while expiring introduction
5521 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
5522 also tracked as TROVE-2017-013 and CVE-2017-8823.
5524 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
5525 - When running as a relay, make sure that we never build a path
5526 through ourselves, even in the case where we have somehow lost the
5527 version of our descriptor appearing in the consensus. Fixes part
5528 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
5529 as TROVE-2017-012 and CVE-2017-8822.
5531 o Minor features (bridge, backport from 0.3.1.9):
5532 - Bridges now include notice in their descriptors that they are
5533 bridges, and notice of their distribution status, based on their
5534 publication settings. Implements ticket 18329. For more fine-
5535 grained control of how a bridge is distributed, upgrade to 0.3.2.x
5538 o Minor features (directory authority, backport from 0.3.2.6-alpha):
5539 - Add an IPv6 address for the "bastet" directory authority. Closes
5542 o Minor features (geoip):
5543 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
5546 o Minor features (security, windows, backport from 0.3.1.1-alpha):
5547 - Enable a couple of pieces of Windows hardening: one
5548 (HeapEnableTerminationOnCorruption) that has been on-by-default
5549 since Windows 8, and unavailable before Windows 7; and one
5550 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
5551 affect us, but shouldn't do any harm. Closes ticket 21953.
5553 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
5554 - Avoid unnecessary calls to directory_fetches_from_authorities() on
5555 relays, to prevent spurious address resolutions and descriptor
5556 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
5557 bugfix on in 0.2.8.1-alpha.
5559 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
5560 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
5561 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
5563 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
5564 - When a circuit is marked for close, do not attempt to package any
5565 cells for channels on that circuit. Previously, we would detect
5566 this condition lower in the call stack, when we noticed that the
5567 circuit had no attached channel, and log an annoying message.
5568 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
5570 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
5571 - Avoid a crash when transitioning from client mode to bridge mode.
5572 Previously, we would launch the worker threads whenever our
5573 "public server" mode changed, but not when our "server" mode
5574 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
5576 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
5577 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
5578 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
5581 Changes in version 0.2.8.17 - 2017-12-01
5582 Tor 0.2.8.17 backports important security and stability bugfixes from
5583 later Tor releases. All Tor users should upgrade to this release, or
5584 to another of the releases coming out today.
5586 Note: the Tor 0.2.8 series will no longer be supported after 1 Jan
5587 2018. If you need a release with long-term support, please upgrade with
5588 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
5590 o Major bugfixes (security, backport from 0.3.2.6-alpha):
5591 - Fix a denial of service bug where an attacker could use a
5592 malformed directory object to cause a Tor instance to pause while
5593 OpenSSL would try to read a passphrase from the terminal. (Tor
5594 instances run without a terminal, which is the case for most Tor
5595 packages, are not impacted.) Fixes bug 24246; bugfix on every
5596 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
5597 Found by OSS-Fuzz as testcase 6360145429790720.
5598 - When checking for replays in the INTRODUCE1 cell data for a
5599 (legacy) onion service, correctly detect replays in the RSA-
5600 encrypted part of the cell. We were previously checking for
5601 replays on the entire cell, but those can be circumvented due to
5602 the malleability of Tor's legacy hybrid encryption. This fix helps
5603 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
5604 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
5607 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
5608 - Fix a use-after-free error that could crash v2 Tor onion services
5609 when they failed to open circuits while expiring introduction
5610 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
5611 also tracked as TROVE-2017-013 and CVE-2017-8823.
5613 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
5614 - When running as a relay, make sure that we never build a path through
5615 ourselves, even in the case where we have somehow lost the version of
5616 our descriptor appearing in the consensus. Fixes part of bug 21534;
5617 bugfix on 0.2.0.1-alpha. This issue is also tracked as TROVE-2017-012
5620 o Minor features (bridge, backport from 0.3.1.9):
5621 - Bridges now include notice in their descriptors that they are
5622 bridges, and notice of their distribution status, based on their
5623 publication settings. Implements ticket 18329. For more fine-
5624 grained control of how a bridge is distributed, upgrade to 0.3.2.x
5627 o Minor features (directory authority, backport from 0.3.2.6-alpha):
5628 - Add an IPv6 address for the "bastet" directory authority. Closes
5631 o Minor features (geoip):
5632 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
5635 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
5636 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
5637 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
5640 Changes in version 0.2.5.16 - 2017-12-01
5641 Tor 0.2.5.13 backports important security and stability bugfixes from
5642 later Tor releases. All Tor users should upgrade to this release, or
5643 to another of the releases coming out today.
5645 Note: the Tor 0.2.5 series will no longer be supported after 1 May
5646 2018. If you need a release with long-term support, please upgrade to
5647 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
5649 o Major bugfixes (security, backport from 0.3.2.6-alpha):
5650 - Fix a denial of service bug where an attacker could use a
5651 malformed directory object to cause a Tor instance to pause while
5652 OpenSSL would try to read a passphrase from the terminal. (Tor
5653 instances run without a terminal, which is the case for most Tor
5654 packages, are not impacted.) Fixes bug 24246; bugfix on every
5655 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
5656 Found by OSS-Fuzz as testcase 6360145429790720.
5657 - When checking for replays in the INTRODUCE1 cell data for a
5658 (legacy) onion service, correctly detect replays in the RSA-
5659 encrypted part of the cell. We were previously checking for
5660 replays on the entire cell, but those can be circumvented due to
5661 the malleability of Tor's legacy hybrid encryption. This fix helps
5662 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
5663 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
5666 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
5667 - When running as a relay, make sure that we never build a path
5668 through ourselves, even in the case where we have somehow lost the
5669 version of our descriptor appearing in the consensus. Fixes part
5670 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
5671 as TROVE-2017-012 and CVE-2017-8822.
5673 o Minor features (bridge, backport from 0.3.1.9):
5674 - Bridges now include notice in their descriptors that they are
5675 bridges, and notice of their distribution status, based on their
5676 publication settings. Implements ticket 18329. For more fine-
5677 grained control of how a bridge is distributed, upgrade to 0.3.2.x
5680 o Minor features (geoip):
5681 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
5685 Changes in version 0.3.2.5-alpha - 2017-11-22
5686 Tor 0.3.2.5-alpha is the fifth alpha release in the 0.3.2.x series. It
5687 fixes several stability and reliability bugs, including a fix for
5688 intermittent bootstrapping failures that some people have been seeing
5689 since the 0.3.0.x series.
5691 Please test this alpha out -- many of these fixes will soon be
5692 backported to stable Tor versions if no additional bugs are found
5695 o Major bugfixes (bootstrapping):
5696 - Fetch descriptors aggressively whenever we lack enough to build
5697 circuits, regardless of how many descriptors we are missing.
5698 Previously, we would delay launching the fetch when we had fewer
5699 than 15 missing descriptors, even if some of those descriptors
5700 were blocking circuits from building. Fixes bug 23985; bugfix on
5701 0.1.1.11-alpha. The effects of this bug became worse in
5702 0.3.0.3-alpha, when we began treating missing descriptors from our
5703 primary guards as a reason to delay circuits.
5704 - Don't try fetching microdescriptors from relays that have failed
5705 to deliver them in the past. Fixes bug 23817; bugfix
5708 o Minor features (directory authority):
5709 - Make the "Exit" flag assignment only depend on whether the exit
5710 policy allows connections to ports 80 and 443. Previously relays
5711 would get the Exit flag if they allowed connections to one of
5712 these ports and also port 6667. Resolves ticket 23637.
5714 o Minor features (geoip):
5715 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
5718 o Minor features (linux seccomp2 sandbox):
5719 - Update the sandbox rules so that they should now work correctly
5720 with Glibc 2.26. Closes ticket 24315.
5722 o Minor features (logging):
5723 - Downgrade a pair of log messages that could occur when an exit's
5724 resolver gave us an unusual (but not forbidden) response. Closes
5726 - Improve the message we log when re-enabling circuit build timeouts
5727 after having received a consensus. Closes ticket 20963.
5729 o Minor bugfixes (compilation):
5730 - Fix a memory leak warning in one of the libevent-related
5731 configuration tests that could occur when manually specifying
5732 -fsanitize=address. Fixes bug 24279; bugfix on 0.3.0.2-alpha.
5733 Found and patched by Alex Xu.
5734 - When detecting OpenSSL on Windows from our configure script, make
5735 sure to try linking with the ws2_32 library. Fixes bug 23783;
5736 bugfix on 0.3.2.2-alpha.
5738 o Minor bugfixes (control port, linux seccomp2 sandbox):
5739 - Avoid a crash when attempting to use the seccomp2 sandbox together
5740 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
5743 o Minor bugfixes (control port, onion services):
5744 - Report "FAILED" instead of "UPLOAD_FAILED" "FAILED" for the
5745 HS_DESC event when a service is not able to upload a descriptor.
5746 Fixes bug 24230; bugfix on 0.2.7.1-alpha.
5748 o Minor bugfixes (directory cache):
5749 - Recover better from empty or corrupt files in the consensus cache
5750 directory. Fixes bug 24099; bugfix on 0.3.1.1-alpha.
5751 - When a consensus diff calculation is only partially successful,
5752 only record the successful parts as having succeeded. Partial
5753 success can happen if (for example) one compression method fails
5754 but the others succeed. Previously we misrecorded all the
5755 calculations as having succeeded, which would later cause a
5756 nonfatal assertion failure. Fixes bug 24086; bugfix
5759 o Minor bugfixes (logging):
5760 - Only log once if we notice that KIST support is gone. Fixes bug
5761 24158; bugfix on 0.3.2.1-alpha.
5762 - Suppress a log notice when relay descriptors arrive. We already
5763 have a bootstrap progress for this so no need to log notice
5764 everytime tor receives relay descriptors. Microdescriptors behave
5765 the same. Fixes bug 23861; bugfix on 0.2.8.2-alpha.
5767 o Minor bugfixes (network layer):
5768 - When closing a connection via close_connection_immediately(), we
5769 mark it as "not blocked on bandwidth", to prevent later calls from
5770 trying to unblock it, and give it permission to read. This fixes a
5771 backtrace warning that can happen on relays under various
5772 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
5774 o Minor bugfixes (onion services):
5775 - The introduction circuit was being timed out too quickly while
5776 waiting for the rendezvous circuit to complete. Keep the intro
5777 circuit around longer instead of timing out and reopening new ones
5778 constantly. Fixes bug 23681; bugfix on 0.2.4.8-alpha.
5779 - Rename the consensus parameter "hsdir-interval" to "hsdir_interval"
5780 so it matches dir-spec.txt. Fixes bug 24262; bugfix
5782 - Silence a warning about failed v3 onion descriptor uploads that
5783 can happen naturally under certain edge cases. Fixes part of bug
5784 23662; bugfix on 0.3.2.1-alpha.
5786 o Minor bugfixes (tests):
5787 - Fix a memory leak in one of the bridge-distribution test cases.
5788 Fixes bug 24345; bugfix on 0.3.2.3-alpha.
5789 - Fix a bug in our fuzzing mock replacement for crypto_pk_checksig(),
5790 to correctly handle cases where a caller gives it an RSA key of
5791 under 160 bits. (This is not actually a bug in Tor itself, but
5792 rather in our fuzzing code.) Fixes bug 24247; bugfix on
5793 0.3.0.3-alpha. Found by OSS-Fuzz as issue 4177.
5796 - Add notes in man page regarding OS support for the various
5797 scheduler types. Attempt to use less jargon in the scheduler
5798 section. Closes ticket 24254.
5801 Changes in version 0.3.2.4-alpha - 2017-11-08
5802 Tor 0.3.2.4-alpha is the fourth alpha release in the 0.3.2.x series.
5803 It fixes several stability and reliability bugs, especially including
5804 a major reliability issue that has been plaguing fast exit relays in
5807 o Major bugfixes (exit relays, DNS):
5808 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
5809 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
5810 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
5811 identifying and finding a workaround to this bug and to Moritz,
5812 Arthur Edelstein, and Roger for helping to track it down and
5815 o Major bugfixes (scheduler, channel):
5816 - Stop processing scheduled channels if they closed while flushing
5817 cells. This can happen if the write on the connection fails
5818 leading to the channel being closed while in the scheduler loop.
5819 Fixes bug 23751; bugfix on 0.3.2.1-alpha.
5821 o Minor features (logging, scheduler):
5822 - Introduce a SCHED_BUG() function to log extra information about
5823 the scheduler state if we ever catch a bug in the scheduler.
5824 Closes ticket 23753.
5826 o Minor features (removed deprecations):
5827 - The ClientDNSRejectInternalAddresses flag can once again be set in
5828 non-testing Tor networks, so long as they do not use the default
5829 directory authorities. This change also removes the deprecation of
5830 this flag from 0.2.9.2-alpha. Closes ticket 21031.
5832 o Minor features (testing):
5833 - Our fuzzing tests now test the encrypted portions of v3 onion
5834 service descriptors. Implements more of 21509.
5836 o Minor bugfixes (directory client):
5837 - On failure to download directory information, delay retry attempts
5838 by a random amount based on the "decorrelated jitter" algorithm.
5839 Our previous delay algorithm tended to produce extra-long delays
5840 too easily. Fixes bug 23816; bugfix on 0.2.9.1-alpha.
5842 o Minor bugfixes (IPv6, v3 single onion services):
5843 - Remove buggy code for IPv6-only v3 single onion services, and
5844 reject attempts to configure them. This release supports IPv4,
5845 dual-stack, and IPv6-only v3 onion services; and IPv4 and dual-
5846 stack v3 single onion services. Fixes bug 23820; bugfix
5849 o Minor bugfixes (logging, relay):
5850 - Give only a protocol warning when the ed25519 key is not
5851 consistent between the descriptor and microdescriptor of a relay.
5852 This can happen, for instance, if the relay has been flagged
5853 NoEdConsensus. Fixes bug 24025; bugfix on 0.3.2.1-alpha.
5855 o Minor bugfixes (manpage, onion service):
5856 - Document that the HiddenServiceNumIntroductionPoints option is
5857 0-10 for v2 services and 0-20 for v3 services. Fixes bug 24115;
5858 bugfix on 0.3.2.1-alpha.
5860 o Minor bugfixes (memory leaks):
5861 - Fix a minor memory leak at exit in the KIST scheduler. This bug
5862 should have no user-visible impact. Fixes bug 23774; bugfix
5864 - Fix a memory leak when decrypting a badly formatted v3 onion
5865 service descriptor. Fixes bug 24150; bugfix on 0.3.2.1-alpha.
5866 Found by OSS-Fuzz; this is OSS-Fuzz issue 3994.
5868 o Minor bugfixes (onion services):
5869 - Cache some needed onion service client information instead of
5870 constantly computing it over and over again. Fixes bug 23623;
5871 bugfix on 0.3.2.1-alpha.
5872 - Properly retry HSv3 descriptor fetches when missing required
5873 directory information. Fixes bug 23762; bugfix on 0.3.2.1-alpha.
5875 o Minor bugfixes (path selection):
5876 - When selecting relays by bandwidth, avoid a rounding error that
5877 could sometimes cause load to be imbalanced incorrectly.
5878 Previously, we would always round upwards; now, we round towards
5879 the nearest integer. This had the biggest effect when a relay's
5880 weight adjustments should have given it weight 0, but it got
5881 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
5882 - When calculating the fraction of nodes that have descriptors, and
5883 all nodes in the network have zero bandwidths, count the number of
5884 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
5885 - Actually log the total bandwidth in compute_weighted_bandwidths().
5886 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
5888 o Minor bugfixes (relay, crash):
5889 - Avoid a crash when transitioning from client mode to bridge mode.
5890 Previously, we would launch the worker threads whenever our
5891 "public server" mode changed, but not when our "server" mode
5892 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
5894 o Minor bugfixes (testing):
5895 - Fix a spurious fuzzing-only use of an uninitialized value. Found
5896 by Brian Carpenter. Fixes bug 24082; bugfix on 0.3.0.3-alpha.
5897 - Test that IPv6-only clients can use microdescriptors when running
5898 "make test-network-all". Requires chutney master 61c28b9 or later.
5899 Closes ticket 24109.
5902 Changes in version 0.3.2.3-alpha - 2017-10-27
5903 Tor 0.3.2.3-alpha is the third release in the 0.3.2 series. It fixes
5904 numerous small bugs in earlier versions of 0.3.2.x, and adds a new
5905 directory authority, Bastet.
5907 o Directory authority changes:
5908 - Add "Bastet" as a ninth directory authority to the default list.
5909 Closes ticket 23910.
5910 - The directory authority "Longclaw" has changed its IP address.
5911 Closes ticket 23592.
5913 o Minor features (bridge):
5914 - Bridge relays can now set the BridgeDistribution config option to
5915 add a "bridge-distribution-request" line to their bridge
5916 descriptor, which tells BridgeDB how they'd like their bridge
5917 address to be given out. (Note that as of Oct 2017, BridgeDB does
5918 not yet implement this feature.) As a side benefit, this feature
5919 provides a way to distinguish bridge descriptors from non-bridge
5920 descriptors. Implements tickets 18329.
5922 o Minor features (client, entry guards):
5923 - Improve log messages when missing descriptors for primary guards.
5924 Resolves ticket 23670.
5926 o Minor features (geoip):
5927 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
5930 o Minor bugfixes (bridge):
5931 - Overwrite the bridge address earlier in the process of retrieving
5932 its descriptor, to make sure we reach it on the configured
5933 address. Fixes bug 20532; bugfix on 0.2.0.10-alpha.
5935 o Minor bugfixes (documentation):
5936 - Document better how to read gcov, and what our gcov postprocessing
5937 scripts do. Fixes bug 23739; bugfix on 0.2.9.1-alpha.
5939 o Minor bugfixes (entry guards):
5940 - Tor now updates its guard state when it reads a consensus
5941 regardless of whether it's missing descriptors. That makes tor use
5942 its primary guards to fetch descriptors in some edge cases where
5943 it would previously have used fallback directories. Fixes bug
5944 23862; bugfix on 0.3.0.1-alpha.
5946 o Minor bugfixes (hidden service client):
5947 - When handling multiple SOCKS request for the same .onion address,
5948 only fetch the service descriptor once.
5949 - When a descriptor fetch fails with a non-recoverable error, close
5950 all pending SOCKS requests for that .onion. Fixes bug 23653;
5951 bugfix on 0.3.2.1-alpha.
5953 o Minor bugfixes (hidden service):
5954 - Always regenerate missing hidden service public key files. Prior
5955 to this, if the public key was deleted from disk, it wouldn't get
5956 recreated. Fixes bug 23748; bugfix on 0.3.2.2-alpha. Patch
5958 - Make sure that we have a usable ed25519 key when the intro point
5959 relay supports ed25519 link authentication. Fixes bug 24002;
5960 bugfix on 0.3.2.1-alpha.
5962 o Minor bugfixes (hidden service, v2):
5963 - When reloading configured hidden services, copy all information
5964 from the old service object. Previously, some data was omitted,
5965 causing delays in descriptor upload, and other bugs. Fixes bug
5966 23790; bugfix on 0.2.1.9-alpha.
5968 o Minor bugfixes (memory safety, defensive programming):
5969 - Clear the target address when node_get_prim_orport() returns
5970 early. Fixes bug 23874; bugfix on 0.2.8.2-alpha.
5972 o Minor bugfixes (relay):
5973 - Avoid a BUG warning when receiving a dubious CREATE cell while an
5974 option transition is in progress. Fixes bug 23952; bugfix
5977 o Minor bugfixes (testing):
5978 - Adjust the GitLab CI configuration to more closely match that of
5979 Travis CI. Fixes bug 23757; bugfix on 0.3.2.2-alpha.
5980 - Prevent scripts/test/coverage from attempting to move gcov output
5981 to the root directory. Fixes bug 23741; bugfix on 0.2.5.1-alpha.
5982 - When running unit tests as root, skip a test that would fail
5983 because it expects a permissions error. This affects some
5984 continuous integration setups. Fixes bug 23758; bugfix
5986 - Stop unconditionally mirroring the tor repository in GitLab CI.
5987 This prevented developers from enabling GitLab CI on master. Fixes
5988 bug 23755; bugfix on 0.3.2.2-alpha.
5989 - Fix the hidden service v3 descriptor decoding fuzzing to use the
5990 latest decoding API correctly. Fixes bug 21509; bugfix
5993 o Minor bugfixes (warnings):
5994 - When we get an HTTP request on a SOCKS port, tell the user about
5995 the new HTTPTunnelPort option. Previously, we would give a "Tor is
5996 not an HTTP Proxy" message, which stopped being true when
5997 HTTPTunnelPort was introduced. Fixes bug 23678; bugfix
6001 Changes in version 0.2.5.15 - 2017-10-25
6002 Tor 0.2.5.15 backports a collection of bugfixes from later Tor release
6003 series. It also adds a new directory authority, Bastet.
6005 Note: the Tor 0.2.5 series will no longer be supported after 1 May
6006 2018. If you need a release with long-term support, please upgrade to
6007 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
6009 o Directory authority changes:
6010 - Add "Bastet" as a ninth directory authority to the default list.
6011 Closes ticket 23910.
6012 - The directory authority "Longclaw" has changed its IP address.
6013 Closes ticket 23592.
6015 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
6016 - Avoid an assertion failure bug affecting our implementation of
6017 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
6018 handling of "0xx" differs from what we had expected. Fixes bug
6019 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
6021 o Minor features (geoip):
6022 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
6025 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
6026 - Fix a memset() off the end of an array when packing cells. This
6027 bug should be harmless in practice, since the corrupted bytes are
6028 still in the same structure, and are always padding bytes,
6029 ignored, or immediately overwritten, depending on compiler
6030 behavior. Nevertheless, because the memset()'s purpose is to make
6031 sure that any other cell-handling bugs can't expose bytes to the
6032 network, we need to fix it. Fixes bug 22737; bugfix on
6033 0.2.4.11-alpha. Fixes CID 1401591.
6035 o Build features (backport from 0.3.1.5-alpha):
6036 - Tor's repository now includes a Travis Continuous Integration (CI)
6037 configuration file (.travis.yml). This is meant to help new
6038 developers and contributors who fork Tor to a Github repository be
6039 better able to test their changes, and understand what we expect
6040 to pass. To use this new build feature, you must fork Tor to your
6041 Github account, then go into the "Integrations" menu in the
6042 repository settings for your fork and enable Travis, then push
6043 your changes. Closes ticket 22636.
6046 Changes in version 0.2.8.16 - 2017-10-25
6047 Tor 0.2.8.16 backports a collection of bugfixes from later Tor release
6048 series, including a bugfix for a crash issue that had affected relays
6049 under memory pressure. It also adds a new directory authority, Bastet.
6051 Note: the Tor 0.2.8 series will no longer be supported after 1 Jan
6052 2018. If you need a release with long-term support, please stick with
6053 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
6055 o Directory authority changes:
6056 - Add "Bastet" as a ninth directory authority to the default list.
6057 Closes ticket 23910.
6058 - The directory authority "Longclaw" has changed its IP address.
6059 Closes ticket 23592.
6061 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
6062 - Fix a timing-based assertion failure that could occur when the
6063 circuit out-of-memory handler freed a connection's output buffer.
6064 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
6066 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
6067 - Remove longclaw's IPv6 address, as it will soon change. Authority
6068 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
6069 3/8 directory authorities with IPv6 addresses, but there are also
6070 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
6072 o Minor features (geoip):
6073 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
6077 Changes in version 0.2.9.13 - 2017-10-25
6078 Tor 0.2.9.13 backports a collection of bugfixes from later Tor release
6079 series, including a bugfix for a crash issue that had affected relays
6080 under memory pressure. It also adds a new directory authority, Bastet.
6082 o Directory authority changes:
6083 - Add "Bastet" as a ninth directory authority to the default list.
6084 Closes ticket 23910.
6085 - The directory authority "Longclaw" has changed its IP address.
6086 Closes ticket 23592.
6088 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
6089 - Fix a timing-based assertion failure that could occur when the
6090 circuit out-of-memory handler freed a connection's output buffer.
6091 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
6093 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
6094 - Remove longclaw's IPv6 address, as it will soon change. Authority
6095 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
6096 3/8 directory authorities with IPv6 addresses, but there are also
6097 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
6099 o Minor features (geoip):
6100 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
6103 o Minor bugfixes (directory authority, backport from 0.3.1.5-alpha):
6104 - When a directory authority rejects a descriptor or extrainfo with
6105 a given digest, mark that digest as undownloadable, so that we do
6106 not attempt to download it again over and over. We previously
6107 tried to avoid downloading such descriptors by other means, but we
6108 didn't notice if we accidentally downloaded one anyway. This
6109 behavior became problematic in 0.2.7.2-alpha, when authorities
6110 began pinning Ed25519 keys. Fixes bug 22349; bugfix
6113 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
6114 - Clear the address when node_get_prim_orport() returns early.
6115 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
6117 o Minor bugfixes (Windows service, backport from 0.3.1.6-rc):
6118 - When running as a Windows service, set the ID of the main thread
6119 correctly. Failure to do so made us fail to send log messages to
6120 the controller in 0.2.1.16-rc, slowed down controller event
6121 delivery in 0.2.7.3-rc and later, and crash with an assertion
6122 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
6123 Patch and diagnosis from "Vort".
6126 Changes in version 0.3.0.12 - 2017-10-25
6127 Tor 0.3.0.12 backports a collection of bugfixes from later Tor release
6128 series, including a bugfix for a crash issue that had affected relays
6129 under memory pressure. It also adds a new directory authority, Bastet.
6131 Note: the Tor 0.3.0 series will no longer be supported after 26 Jan
6132 2018. If you need a release with long-term support, please stick with
6133 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
6135 o Directory authority changes:
6136 - Add "Bastet" as a ninth directory authority to the default list.
6137 Closes ticket 23910.
6138 - The directory authority "Longclaw" has changed its IP address.
6139 Closes ticket 23592.
6141 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
6142 - Fix a timing-based assertion failure that could occur when the
6143 circuit out-of-memory handler freed a connection's output buffer.
6144 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
6146 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
6147 - Remove longclaw's IPv6 address, as it will soon change. Authority
6148 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
6149 3/8 directory authorities with IPv6 addresses, but there are also
6150 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
6152 o Minor features (geoip):
6153 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
6156 o Minor bugfixes (directory authority, backport from 0.3.1.5-alpha):
6157 - When a directory authority rejects a descriptor or extrainfo with
6158 a given digest, mark that digest as undownloadable, so that we do
6159 not attempt to download it again over and over. We previously
6160 tried to avoid downloading such descriptors by other means, but we
6161 didn't notice if we accidentally downloaded one anyway. This
6162 behavior became problematic in 0.2.7.2-alpha, when authorities
6163 began pinning Ed25519 keys. Fixes bug 22349; bugfix
6166 o Minor bugfixes (hidden service, relay, backport from 0.3.2.2-alpha):
6167 - Avoid a possible double close of a circuit by the intro point on
6168 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
6169 bugfix on 0.3.0.1-alpha.
6171 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
6172 - Clear the address when node_get_prim_orport() returns early.
6173 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
6175 o Minor bugfixes (Windows service, backport from 0.3.1.6-rc):
6176 - When running as a Windows service, set the ID of the main thread
6177 correctly. Failure to do so made us fail to send log messages to
6178 the controller in 0.2.1.16-rc, slowed down controller event
6179 delivery in 0.2.7.3-rc and later, and crash with an assertion
6180 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
6181 Patch and diagnosis from "Vort".
6184 Changes in version 0.3.1.8 - 2017-10-25
6185 Tor 0.3.1.8 is the second stable release in the 0.3.1 series.
6186 It includes several bugfixes, including a bugfix for a crash issue
6187 that had affected relays under memory pressure. It also adds
6188 a new directory authority, Bastet.
6190 o Directory authority changes:
6191 - Add "Bastet" as a ninth directory authority to the default list.
6192 Closes ticket 23910.
6193 - The directory authority "Longclaw" has changed its IP address.
6194 Closes ticket 23592.
6196 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
6197 - Fix a timing-based assertion failure that could occur when the
6198 circuit out-of-memory handler freed a connection's output buffer.
6199 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
6201 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
6202 - Remove longclaw's IPv6 address, as it will soon change. Authority
6203 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
6204 3/8 directory authorities with IPv6 addresses, but there are also
6205 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
6207 o Minor features (geoip):
6208 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
6211 o Minor bugfixes (compilation, backport from 0.3.2.2-alpha):
6212 - Fix a compilation warning when building with zstd support on
6213 32-bit platforms. Fixes bug 23568; bugfix on 0.3.1.1-alpha. Found
6214 and fixed by Andreas Stieger.
6216 o Minor bugfixes (compression, backport from 0.3.2.2-alpha):
6217 - Handle a pathological case when decompressing Zstandard data when
6218 the output buffer size is zero. Fixes bug 23551; bugfix
6221 o Minor bugfixes (directory authority, backport from 0.3.2.1-alpha):
6222 - Remove the length limit on HTTP status lines that authorities can
6223 send in their replies. Fixes bug 23499; bugfix on 0.3.1.6-rc.
6225 o Minor bugfixes (hidden service, relay, backport from 0.3.2.2-alpha):
6226 - Avoid a possible double close of a circuit by the intro point on
6227 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
6228 bugfix on 0.3.0.1-alpha.
6230 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
6231 - Clear the address when node_get_prim_orport() returns early.
6232 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
6234 o Minor bugfixes (unit tests, backport from 0.3.2.2-alpha):
6235 - Fix additional channelpadding unit test failures by using mocked
6236 time instead of actual time for all tests. Fixes bug 23608; bugfix
6240 Changes in version 0.3.2.2-alpha - 2017-09-29
6241 Tor 0.3.2.2-alpha is the second release in the 0.3.2 series. This
6242 release fixes several minor bugs in the new scheduler and next-
6243 generation onion services; both features were newly added in the 0.3.2
6244 series. Other fixes in this alpha include several fixes for non-fatal
6245 tracebacks which would appear in logs.
6247 With the aim to stabilise the 0.3.2 series by 15 December 2017, this
6248 alpha does not contain any substantial new features. Minor features
6249 include better testing and logging.
6251 The following comprises the complete list of changes included
6254 o Major bugfixes (relay, crash, assertion failure):
6255 - Fix a timing-based assertion failure that could occur when the
6256 circuit out-of-memory handler freed a connection's output buffer.
6257 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
6259 o Major bugfixes (scheduler):
6260 - If a channel is put into the scheduler's pending list, then it
6261 starts closing, and then if the scheduler runs before it finishes
6262 closing, the scheduler will get stuck trying to flush its cells
6263 while the lower layers refuse to cooperate. Fix that race
6264 condition by giving the scheduler an escape method. Fixes bug
6265 23676; bugfix on 0.3.2.1-alpha.
6267 o Minor features (build, compilation):
6268 - The "check-changes" feature is now part of the "make check" tests;
6269 we'll use it to try to prevent misformed changes files from
6270 accumulating. Closes ticket 23564.
6271 - Tor builds should now fail if there are any mismatches between the
6272 C type representing a configuration variable and the C type the
6273 data-driven parser uses to store a value there. Previously, we
6274 needed to check these by hand, which sometimes led to mistakes.
6275 Closes ticket 23643.
6277 o Minor features (directory authorities):
6278 - Remove longclaw's IPv6 address, as it will soon change. Authority
6279 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
6280 3/8 directory authorities with IPv6 addresses, but there are also
6281 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
6283 o Minor features (hidden service, circuit, logging):
6284 - Improve logging of many callsite in the circuit subsystem to print
6285 the circuit identifier(s).
6286 - Log when we cleanup an intro point from a service so we know when
6287 and for what reason it happened. Closes ticket 23604.
6289 o Minor features (logging):
6290 - Log more circuit information whenever we are about to try to
6291 package a relay cell on a circuit with a nonexistent n_chan.
6292 Attempt to diagnose ticket 8185.
6293 - Improve info-level log identification of particular circuits, to
6294 help with debugging. Closes ticket 23645.
6296 o Minor features (relay):
6297 - When choosing which circuits can be expired as unused, consider
6298 circuits from clients even if those clients used regular CREATE
6299 cells to make them; and do not consider circuits from relays even
6300 if they were made with CREATE_FAST. Part of ticket 22805.
6302 o Minor features (robustness):
6303 - Change several fatal assertions when flushing buffers into non-
6304 fatal assertions, to prevent any recurrence of 23690.
6306 o Minor features (spec conformance, bridge, diagnostic):
6307 - When handling the USERADDR command on an ExtOrPort, warn when the
6308 transports provides a USERADDR with no port. In a future version,
6309 USERADDR commands of this format may be rejected. Detects problems
6310 related to ticket 23080.
6312 o Minor features (testing):
6313 - Add a unit test to make sure that our own generated platform
6314 string will be accepted by directory authorities. Closes
6317 o Minor bugfixes (bootstrapping):
6318 - When warning about state file clock skew, report the correct
6319 direction for the detected skew. Fixes bug 23606; bugfix
6321 - Avoid an assertion failure when logging a state file clock skew
6322 very early in bootstrapping. Fixes bug 23607; bugfix
6325 o Minor bugfixes (build, compilation):
6326 - Fix a compilation warning when building with zstd support on
6327 32-bit platforms. Fixes bug 23568; bugfix on 0.3.1.1-alpha. Found
6328 and fixed by Andreas Stieger.
6329 - When searching for OpenSSL, don't accept any OpenSSL library that
6330 lacks TLSv1_1_method(): Tor doesn't build with those versions.
6331 Additionally, look in /usr/local/opt/openssl, if it's present.
6332 These changes together repair the default build on OSX systems
6333 with Homebrew installed. Fixes bug 23602; bugfix on 0.2.7.2-alpha.
6335 o Minor bugfixes (compression):
6336 - Handle a pathological case when decompressing Zstandard data when
6337 the output buffer size is zero. Fixes bug 23551; bugfix
6340 o Minor bugfixes (documentation):
6341 - Fix manpage to not refer to the obsolete (and misspelled)
6342 UseEntryGuardsAsDirectoryGuards parameter in the description of
6343 NumDirectoryGuards. Fixes bug 23611; bugfix on 0.2.4.8-alpha.
6345 o Minor bugfixes (hidden service v3):
6346 - Don't log an assertion failure when we can't find the right
6347 information to extend to an introduction point. In rare cases,
6348 this could happen, causing a warning, even though tor would
6349 recover gracefully. Fixes bug 23159; bugfix on 0.3.2.1-alpha.
6350 - Pad RENDEZVOUS cell up to the size of the legacy cell which is
6351 much bigger so the rendezvous point can't distinguish which hidden
6352 service protocol is being used. Fixes bug 23420; bugfix
6355 o Minor bugfixes (hidden service, relay):
6356 - Avoid a possible double close of a circuit by the intro point on
6357 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
6358 bugfix on 0.3.0.1-alpha.
6360 o Minor bugfixes (logging, relay shutdown, annoyance):
6361 - When a circuit is marked for close, do not attempt to package any
6362 cells for channels on that circuit. Previously, we would detect
6363 this condition lower in the call stack, when we noticed that the
6364 circuit had no attached channel, and log an annoying message.
6365 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
6367 o Minor bugfixes (scheduler):
6368 - When switching schedulers due to a consensus change, we didn't
6369 give the new scheduler a chance to react to the consensus. Fix
6370 that. Fixes bug 23537; bugfix on 0.3.2.1-alpha.
6371 - Make the KISTSchedRunInterval option a non negative value. With
6372 this, the way to disable KIST through the consensus is to set it
6373 to 0. Fixes bug 23539; bugfix on 0.3.2.1-alpha.
6374 - Only notice log the selected scheduler when we switch scheduler
6375 types. Fixes bug 23552; bugfix on 0.3.2.1-alpha.
6376 - Avoid a compilation warning on macOS in scheduler_ev_add() caused
6377 by a different tv_usec data type. Fixes bug 23575; bugfix
6379 - Make a hard exit if tor is unable to pick a scheduler which can
6380 happen if the user specifies a scheduler type that is not
6381 supported and not other types in Schedulers. Fixes bug 23581;
6382 bugfix on 0.3.2.1-alpha.
6383 - Properly initialize the scheduler last run time counter so it is
6384 not 0 at the first tick. Fixes bug 23696; bugfix on 0.3.2.1-alpha.
6386 o Minor bugfixes (testing):
6387 - Capture and detect several "Result does not fit" warnings in unit
6388 tests on platforms with 32-bit time_t. Fixes bug 21800; bugfix
6390 - Fix additional channelpadding unit test failures by using mocked
6391 time instead of actual time for all tests. Fixes bug 23608; bugfix
6393 - The removal of some old scheduler options caused some tests to
6394 fail on BSD systems. Assume current behavior is correct and make
6395 the tests pass again. Fixes bug 23566; bugfix on 0.3.2.1-alpha.
6397 o Code simplification and refactoring:
6398 - Remove various ways of testing circuits and connections for
6399 "clientness"; instead, favor channel_is_client(). Part of
6402 o Deprecated features:
6403 - The ReachableDirAddresses and ClientPreferIPv6DirPort options are
6404 now deprecated; they do not apply to relays, and they have had no
6405 effect on clients since 0.2.8.x. Closes ticket 19704.
6408 - HiddenServiceVersion man page entry wasn't mentioning the now
6409 supported version 3. Fixes ticket 23580; bugfix on 0.3.2.1-alpha.
6410 - Clarify that the Address option is entirely about setting an
6411 advertised IPv4 address. Closes ticket 18891.
6412 - Clarify the manpage's use of the term "address" to clarify what
6413 kind of address is intended. Closes ticket 21405.
6414 - Document that onion service subdomains are allowed, and ignored.
6415 Closes ticket 18736.
6418 Changes in version 0.3.2.1-alpha - 2017-09-18
6419 Tor 0.3.2.1-alpha is the first release in the 0.3.2.x series. It
6420 includes support for our next-generation ("v3") onion service
6421 protocol, and adds a new circuit scheduler for more responsive
6422 forwarding decisions from relays. There are also numerous other small
6423 features and bugfixes here.
6425 Below are the changes since Tor 0.3.1.7.
6427 o Major feature (scheduler, channel):
6428 - Tor now uses new schedulers to decide which circuits should
6429 deliver cells first, in order to improve congestion at relays. The
6430 first type is called "KIST" ("Kernel Informed Socket Transport"),
6431 and is only available on Linux-like systems: it uses feedback from
6432 the kernel to prevent the kernel's TCP buffers from growing too
6433 full. The second new scheduler type is called "KISTLite": it
6434 behaves the same as KIST, but runs on systems without kernel
6435 support for inspecting TCP implementation details. The old
6436 scheduler is still available, under the name "Vanilla". To change
6437 the default scheduler preference order, use the new "Schedulers"
6438 option. (The default preference order is "KIST,KISTLite,Vanilla".)
6440 Matt Traudt implemented KIST, based on research by Rob Jansen,
6441 John Geddes, Christ Wacek, Micah Sherr, and Paul Syverson. For
6442 more information, see the design paper at
6443 http://www.robgjansen.com/publications/kist-sec2014.pdf and the
6444 followup implementation paper at https://arxiv.org/abs/1709.01044.
6445 Closes ticket 12541.
6447 o Major features (next-generation onion services):
6448 - Tor now supports the next-generation onion services protocol for
6449 clients and services! As part of this release, the core of
6450 proposal 224 has been implemented and is available for
6451 experimentation and testing by our users. This newer version of
6452 onion services ("v3") features many improvements over the legacy
6455 a) Better crypto (replaced SHA1/DH/RSA1024
6456 with SHA3/ed25519/curve25519)
6458 b) Improved directory protocol, leaking much less information to
6461 c) Improved directory protocol, with smaller surface for
6464 d) Better onion address security against impersonation.
6466 e) More extensible introduction/rendezvous protocol.
6468 f) A cleaner and more modular codebase.
6470 You can identify a next-generation onion address by its length:
6471 they are 56 characters long, as in
6472 "4acth47i6kxnvkewtm6q7ib2s3ufpo5sqbsnzjpbi7utijcltosqemad.onion".
6474 In the future, we will release more options and features for v3
6475 onion services, but we first need a testing period, so that the
6476 current codebase matures and becomes more robust. Planned features
6477 include: offline keys, advanced client authorization, improved
6478 guard algorithms, and statistics. For full details, see
6481 Legacy ("v2") onion services will still work for the foreseeable
6482 future, and will remain the default until this new codebase gets
6483 tested and hardened. Service operators who want to experiment with
6484 the new system can use the 'HiddenServiceVersion 3' torrc
6485 directive along with the regular onion service configuration
6486 options. We will publish a blog post about this new feature
6489 o Major bugfixes (usability, control port):
6490 - Report trusted clock skew indications as bootstrap errors, so
6491 controllers can more easily alert users when their clocks are
6492 wrong. Fixes bug 23506; bugfix on 0.1.2.6-alpha.
6494 o Minor features (bug detection):
6495 - Log a warning message with a stack trace for any attempt to call
6496 get_options() during option validation. This pattern has caused
6497 subtle bugs in the past. Closes ticket 22281.
6499 o Minor features (client):
6500 - You can now use Tor as a tunneled HTTP proxy: use the new
6501 HTTPTunnelPort option to open a port that accepts HTTP CONNECT
6502 requests. Closes ticket 22407.
6503 - Add an extra check to make sure that we always use the newer guard
6504 selection code for picking our guards. Closes ticket 22779.
6505 - When downloading (micro)descriptors, don't split the list into
6506 multiple requests unless we want at least 32 descriptors.
6507 Previously, we split at 4, not 32, which led to significant
6508 overhead in HTTP request size and degradation in compression
6509 performance. Closes ticket 23220.
6511 o Minor features (command line):
6512 - Add a new commandline option, --key-expiration, which prints when
6513 the current signing key is going to expire. Implements ticket
6514 17639; patch by Isis Lovecruft.
6516 o Minor features (control port):
6517 - If an application tries to use the control port as an HTTP proxy,
6518 respond with a meaningful "This is the Tor control port" message,
6519 and log the event. Closes ticket 1667. Patch from Ravi
6521 - Provide better error message for GETINFO desc/(id|name) when not
6522 fetching router descriptors. Closes ticket 5847. Patch by
6524 - Add GETINFO "{desc,md}/download-enabled", to inform the controller
6525 whether Tor will try to download router descriptors and
6526 microdescriptors respectively. Closes ticket 22684.
6527 - Added new GETINFO targets "ip-to-country/{ipv4,ipv6}-available",
6528 so controllers can tell whether the geoip databases are loaded.
6529 Closes ticket 23237.
6530 - Adds a timestamp field to the CIRC_BW and STREAM_BW bandwidth
6531 events. Closes ticket 19254. Patch by "DonnchaC".
6533 o Minor features (development support):
6534 - Developers can now generate a call-graph for Tor using the
6535 "calltool" python program, which post-processes object dumps. It
6536 should work okay on many Linux and OSX platforms, and might work
6537 elsewhere too. To run it, install calltool from
6538 https://gitweb.torproject.org/user/nickm/calltool.git and run
6539 "make callgraph". Closes ticket 19307.
6541 o Minor features (ed25519):
6542 - Add validation function to checks for torsion components in
6543 ed25519 public keys, used by prop224 client-side code. Closes
6544 ticket 22006. Math help by Ian Goldberg.
6546 o Minor features (exit relay, DNS):
6547 - Improve the clarity and safety of the log message from evdns when
6548 receiving an apparently spoofed DNS reply. Closes ticket 3056.
6550 o Minor features (integration, hardening):
6551 - Add a new NoExec option to prevent Tor from running other
6552 programs. When this option is set to 1, Tor will never try to run
6553 another program, regardless of the settings of
6554 PortForwardingHelper, ClientTransportPlugin, or
6555 ServerTransportPlugin. Once NoExec is set, it cannot be disabled
6556 without restarting Tor. Closes ticket 22976.
6558 o Minor features (logging):
6559 - Improve the warning message for specifying a relay by nickname.
6560 The previous message implied that nickname registration was still
6561 part of the Tor network design, which it isn't. Closes
6563 - If the sandbox filter fails to load, suggest to the user that
6564 their kernel might not support seccomp2. Closes ticket 23090.
6566 o Minor features (portability):
6567 - Check at configure time whether uint8_t is the same type as
6568 unsigned char. Lots of existing code already makes this
6569 assumption, and there could be strict aliasing issues if the
6570 assumption is violated. Closes ticket 22410.
6572 o Minor features (relay, configuration):
6573 - Reject attempts to use relative file paths when RunAsDaemon is
6574 set. Previously, Tor would accept these, but the directory-
6575 changing step of RunAsDaemon would give strange and/or confusing
6576 results. Closes ticket 22731.
6578 o Minor features (startup, safety):
6579 - When configured to write a PID file, Tor now exits if it is unable
6580 to do so. Previously, it would warn and continue. Closes
6583 o Minor features (static analysis):
6584 - The BUG() macro has been changed slightly so that Coverity no
6585 longer complains about dead code if the bug is impossible. Closes
6588 o Minor features (testing):
6589 - The default chutney network tests now include tests for the v3
6590 hidden service design. Make sure you have the latest version of
6591 chutney if you want to run these. Closes ticket 22437.
6592 - Add a unit test to verify that we can parse a hardcoded v2 hidden
6593 service descriptor. Closes ticket 15554.
6595 o Minor bugfixes (certificate handling):
6596 - Fix a time handling bug in Tor certificates set to expire after
6597 the year 2106. Fixes bug 23055; bugfix on 0.3.0.1-alpha. Found by
6598 Coverity as CID 1415728.
6600 o Minor bugfixes (client, usability):
6601 - Refrain from needlessly rejecting SOCKS5-with-hostnames and
6602 SOCKS4a requests that contain IP address strings, even when
6603 SafeSocks in enabled, as this prevents user from connecting to
6604 known IP addresses without relying on DNS for resolving. SafeSocks
6605 still rejects SOCKS connections that connect to IP addresses when
6606 those addresses are _not_ encoded as hostnames. Fixes bug 22461;
6607 bugfix on Tor 0.2.6.2-alpha.
6609 o Minor bugfixes (code correctness):
6610 - Call htons() in extend_cell_format() for encoding a 16-bit value.
6611 Previously we used ntohs(), which happens to behave the same on
6612 all the platforms we support, but which isn't really correct.
6613 Fixes bug 23106; bugfix on 0.2.4.8-alpha.
6614 - For defense-in-depth, make the controller's write_escaped_data()
6615 function robust to extremely long inputs. Fixes bug 19281; bugfix
6616 on 0.1.1.1-alpha. Reported by Guido Vranken.
6618 o Minor bugfixes (compilation):
6619 - Fix unused-variable warnings in donna's Curve25519 SSE2 code.
6620 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
6622 o Minor bugfixes (consensus expiry):
6623 - Check for adequate directory information correctly. Previously, Tor
6624 would reconsider whether it had sufficient directory information
6625 every 2 minutes. Fixes bug 23091; bugfix on 0.2.0.19-alpha.
6627 o Minor bugfixes (directory protocol):
6628 - Directory servers now include a "Date:" http header for response
6629 codes other than 200. Clients starting with a skewed clock and a
6630 recent consensus were getting "304 Not modified" responses from
6631 directory authorities, so without the Date header, the client
6632 would never hear about a wrong clock. Fixes bug 23499; bugfix
6634 - Make clients wait for 6 seconds before trying to download a
6635 consensus from an authority. Fixes bug 17750; bugfix
6638 o Minor bugfixes (DoS-resistance):
6639 - If future code asks if there are any running bridges, without
6640 checking if bridges are enabled, log a BUG warning rather than
6641 crashing. Fixes bug 23524; bugfix on 0.3.0.1-alpha.
6643 o Minor bugfixes (format strictness):
6644 - Restrict several data formats to decimal. Previously, the
6645 BuildTimeHistogram entries in the state file, the "bw=" entries in
6646 the bandwidth authority file, and the process IDs passed to the
6647 __OwningControllerProcess option could all be specified in hex or
6648 octal as well as in decimal. This was not an intentional feature.
6649 Fixes bug 22802; bugfixes on 0.2.2.1-alpha, 0.2.2.2-alpha,
6652 o Minor bugfixes (heartbeat):
6653 - If we fail to write a heartbeat message, schedule a retry for the
6654 minimum heartbeat interval number of seconds in the future. Fixes
6655 bug 19476; bugfix on 0.2.3.1-alpha.
6657 o Minor bugfixes (linux seccomp2 sandbox, logging):
6658 - Fix some messages on unexpected errors from the seccomp2 library.
6659 Fixes bug 22750; bugfix on 0.2.5.1-alpha. Patch from "cypherpunks".
6661 o Minor bugfixes (logging):
6662 - Remove duplicate log messages regarding opening non-local
6663 SocksPorts upon parsing config and opening listeners at startup.
6664 Fixes bug 4019; bugfix on 0.2.3.3-alpha.
6665 - Use a more comprehensible log message when telling the user
6666 they've excluded every running exit node. Fixes bug 7890; bugfix
6668 - When logging the number of descriptors we intend to download per
6669 directory request, do not log a number higher than then the number
6670 of descriptors we're fetching in total. Fixes bug 19648; bugfix
6672 - When warning about a directory owned by the wrong user, log the
6673 actual name of the user owning the directory. Previously, we'd log
6674 the name of the process owner twice. Fixes bug 23487; bugfix
6676 - The tor specification says hop counts are 1-based, so fix two log
6677 messages that mistakenly logged 0-based hop counts. Fixes bug
6678 18982; bugfix on 0.2.6.2-alpha and 0.2.4.5-alpha. Patch by teor.
6679 Credit to Xiaofan Li for reporting this issue.
6681 o Minor bugfixes (portability):
6682 - Stop using the PATH_MAX variable, which is not defined on GNU
6683 Hurd. Fixes bug 23098; bugfix on 0.3.1.1-alpha.
6685 o Minor bugfixes (relay):
6686 - When uploading our descriptor for the first time after startup,
6687 report the reason for uploading as "Tor just started" rather than
6688 leaving it blank. Fixes bug 22885; bugfix on 0.2.3.4-alpha.
6689 - Avoid unnecessary calls to directory_fetches_from_authorities() on
6690 relays, to prevent spurious address resolutions and descriptor
6691 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
6692 bugfix on in 0.2.8.1-alpha.
6694 o Minor bugfixes (tests):
6695 - Fix a broken unit test for the OutboundAddress option: the parsing
6696 function was never returning an error on failure. Fixes bug 23366;
6697 bugfix on 0.3.0.3-alpha.
6698 - Fix a signed-integer overflow in the unit tests for
6699 dir/download_status_random_backoff, which was untriggered until we
6700 fixed bug 17750. Fixes bug 22924; bugfix on 0.2.9.1-alpha.
6702 o Minor bugfixes (usability, control port):
6703 - Stop making an unnecessary routerlist check in NETINFO clock skew
6704 detection; this was preventing clients from reporting NETINFO clock
6705 skew to controllers. Fixes bug 23532; bugfix on 0.2.4.4-alpha.
6707 o Code simplification and refactoring:
6708 - Extract the code for handling newly-open channels into a separate
6709 function from the general code to handle channel state
6710 transitions. This change simplifies our callgraph, reducing the
6711 size of the largest strongly connected component by roughly a
6712 factor of two. Closes ticket 22608.
6713 - Remove dead code for largely unused statistics on the number of
6714 times we've attempted various public key operations. Fixes bug
6715 19871; bugfix on 0.1.2.4-alpha. Fix by Isis Lovecruft.
6716 - Remove several now-obsolete functions for asking about old
6717 variants directory authority status. Closes ticket 22311; patch
6719 - Remove some of the code that once supported "Named" and "Unnamed"
6720 routers. Authorities no longer vote for these flags. Closes
6722 - Rename the obsolete malleable hybrid_encrypt functions used in TAP
6723 and old hidden services, to indicate that they aren't suitable for
6724 new protocols or formats. Closes ticket 23026.
6725 - Replace our STRUCT_OFFSET() macro with offsetof(). Closes ticket
6726 22521. Patch from Neel Chauhan.
6727 - Split the enormous circuit_send_next_onion_skin() function into
6728 multiple subfunctions. Closes ticket 22804.
6729 - Split the portions of the buffer.c module that handle particular
6730 protocols into separate modules. Part of ticket 23149.
6731 - Use our test macros more consistently, to produce more useful
6732 error messages when our unit tests fail. Add coccinelle patches to
6733 allow us to re-check for test macro uses. Closes ticket 22497.
6735 o Deprecated features:
6736 - Deprecate HTTPProxy/HTTPProxyAuthenticator config options. They
6737 only applies to direct unencrypted HTTP connections to your
6738 directory server, which your Tor probably isn't using. Closes
6742 - Clarify in the manual that "Sandbox 1" is only supported on Linux
6743 kernels. Closes ticket 22677.
6744 - Document all values of PublishServerDescriptor in the manpage.
6745 Closes ticket 15645.
6746 - Improve the documentation for the directory port part of the
6747 DirAuthority line. Closes ticket 20152.
6748 - Restore documentation for the authorities' "approved-routers"
6749 file. Closes ticket 21148.
6752 - The AllowDotExit option has been removed as unsafe. It has been
6753 deprecated since 0.2.9.2-alpha. Closes ticket 23426.
6754 - The ClientDNSRejectInternalAddresses flag can no longer be set on
6755 non-testing networks. It has been deprecated since 0.2.9.2-alpha.
6756 Closes ticket 21031.
6757 - The controller API no longer includes an AUTHDIR_NEWDESCS event:
6758 nobody was using it any longer. Closes ticket 22377.
6761 Changes in version 0.2.8.15 - 2017-09-18
6762 Tor 0.2.8.15 backports a collection of bugfixes from later
6765 Most significantly, it includes a fix for TROVE-2017-008, a
6766 security bug that affects hidden services running with the
6767 SafeLogging option disabled. For more information, see
6768 https://trac.torproject.org/projects/tor/ticket/23490
6770 Note that Tor 0.2.8.x will no longer be supported after 1 Jan
6771 2018. We suggest that you upgrade to the latest stable release if
6772 possible. If you can't, we recommend that you upgrade at least to
6773 0.2.9, which will be supported until 2020.
6775 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
6776 - Avoid an assertion failure bug affecting our implementation of
6777 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
6778 handling of "0xx" differs from what we had expected. Fixes bug
6779 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
6782 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
6785 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
6786 - Backport a fix for an "unused variable" warning that appeared
6787 in some versions of mingw. Fixes bug 22838; bugfix on
6790 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
6791 - Fix a memset() off the end of an array when packing cells. This
6792 bug should be harmless in practice, since the corrupted bytes are
6793 still in the same structure, and are always padding bytes,
6794 ignored, or immediately overwritten, depending on compiler
6795 behavior. Nevertheless, because the memset()'s purpose is to make
6796 sure that any other cell-handling bugs can't expose bytes to the
6797 network, we need to fix it. Fixes bug 22737; bugfix on
6798 0.2.4.11-alpha. Fixes CID 1401591.
6800 o Build features (backport from 0.3.1.5-alpha):
6801 - Tor's repository now includes a Travis Continuous Integration (CI)
6802 configuration file (.travis.yml). This is meant to help new
6803 developers and contributors who fork Tor to a Github repository be
6804 better able to test their changes, and understand what we expect
6805 to pass. To use this new build feature, you must fork Tor to your
6806 Github account, then go into the "Integrations" menu in the
6807 repository settings for your fork and enable Travis, then push
6808 your changes. Closes ticket 22636.
6811 Changes in version 0.2.9.12 - 2017-09-18
6812 Tor 0.2.9.12 backports a collection of bugfixes from later
6815 Most significantly, it includes a fix for TROVE-2017-008, a
6816 security bug that affects hidden services running with the
6817 SafeLogging option disabled. For more information, see
6818 https://trac.torproject.org/projects/tor/ticket/23490
6820 o Major features (security, backport from 0.3.0.2-alpha):
6821 - Change the algorithm used to decide DNS TTLs on client and server
6822 side, to better resist DNS-based correlation attacks like the
6823 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
6824 Feamster. Now relays only return one of two possible DNS TTL
6825 values, and clients are willing to believe DNS TTL values up to 3
6826 hours long. Closes ticket 19769.
6828 o Major bugfixes (crash, directory connections, backport from 0.3.0.5-rc):
6829 - Fix a rare crash when sending a begin cell on a circuit whose
6830 linked directory connection had already been closed. Fixes bug
6831 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
6833 o Major bugfixes (DNS, backport from 0.3.0.2-alpha):
6834 - Fix a bug that prevented exit nodes from caching DNS records for
6835 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
6837 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
6838 - Fix a typo that had prevented TPROXY-based transparent proxying
6839 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
6840 Patch from "d4fq0fQAgoJ".
6842 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
6843 - Avoid an assertion failure bug affecting our implementation of
6844 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
6845 handling of "0xx" differs from what we had expected. Fixes bug
6846 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
6848 o Minor features (code style, backport from 0.3.1.3-alpha):
6849 - Add "Falls through" comments to our codebase, in order to silence
6850 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
6851 Stieger. Closes ticket 22446.
6853 o Minor features (geoip):
6854 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
6857 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.1-alpha):
6858 - Roll over monthly accounting at the configured hour and minute,
6859 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
6860 Found by Andrey Karpov with PVS-Studio.
6862 o Minor bugfixes (compilation, backport from 0.3.1.5-alpha):
6863 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
6864 bugfix on 0.2.8.1-alpha.
6865 - Fix warnings when building with libscrypt and openssl scrypt support
6866 on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
6867 - When building with certain versions the mingw C header files, avoid
6868 float-conversion warnings when calling the C functions isfinite(),
6869 isnan(), and signbit(). Fixes bug 22801; bugfix on 0.2.8.1-alpha.
6871 o Minor bugfixes (compilation, backport from 0.3.1.7):
6872 - Avoid compiler warnings in the unit tests for running tor_sscanf()
6873 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
6875 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
6876 - Backport a fix for an "unused variable" warning that appeared
6877 in some versions of mingw. Fixes bug 22838; bugfix on
6880 o Minor bugfixes (controller, backport from 0.3.1.7):
6881 - Do not crash when receiving a HSPOST command with an empty body.
6882 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
6883 - Do not crash when receiving a POSTDESCRIPTOR command with an
6884 empty body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
6886 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
6887 - Avoid Coverity build warnings related to our BUG() macro. By
6888 default, Coverity treats BUG() as the Linux kernel does: an
6889 instant abort(). We need to override that so our BUG() macro
6890 doesn't prevent Coverity from analyzing functions that use it.
6891 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
6893 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
6894 - Fix a memset() off the end of an array when packing cells. This
6895 bug should be harmless in practice, since the corrupted bytes are
6896 still in the same structure, and are always padding bytes,
6897 ignored, or immediately overwritten, depending on compiler
6898 behavior. Nevertheless, because the memset()'s purpose is to make
6899 sure that any other cell-handling bugs can't expose bytes to the
6900 network, we need to fix it. Fixes bug 22737; bugfix on
6901 0.2.4.11-alpha. Fixes CID 1401591.
6903 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
6904 - When setting the maximum number of connections allowed by the OS,
6905 always allow some extra file descriptors for other files. Fixes
6906 bug 22797; bugfix on 0.2.0.10-alpha.
6908 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
6909 - Avoid a sandbox failure when trying to re-bind to a socket and
6910 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
6912 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
6913 - Permit the fchmod system call, to avoid crashing on startup when
6914 starting with the seccomp2 sandbox and an unexpected set of
6915 permissions on the data directory or its contents. Fixes bug
6916 22516; bugfix on 0.2.5.4-alpha.
6918 o Minor bugfixes (relay, backport from 0.3.0.5-rc):
6919 - Avoid a double-marked-circuit warning that could happen when we
6920 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
6923 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
6924 - Reject version numbers with non-numeric prefixes (such as +, -, or
6925 whitespace). Disallowing whitespace prevents differential version
6926 parsing between POSIX-based and Windows platforms. Fixes bug 21507
6927 and part of 21508; bugfix on 0.0.8pre1.
6929 o Build features (backport from 0.3.1.5-alpha):
6930 - Tor's repository now includes a Travis Continuous Integration (CI)
6931 configuration file (.travis.yml). This is meant to help new
6932 developers and contributors who fork Tor to a Github repository be
6933 better able to test their changes, and understand what we expect
6934 to pass. To use this new build feature, you must fork Tor to your
6935 Github account, then go into the "Integrations" menu in the
6936 repository settings for your fork and enable Travis, then push
6937 your changes. Closes ticket 22636.
6940 Changes in version 0.3.0.11 - 2017-09-18
6941 Tor 0.3.0.11 backports a collection of bugfixes from Tor the 0.3.1
6944 Most significantly, it includes a fix for TROVE-2017-008, a
6945 security bug that affects hidden services running with the
6946 SafeLogging option disabled. For more information, see
6947 https://trac.torproject.org/projects/tor/ticket/23490
6949 o Minor features (code style, backport from 0.3.1.7):
6950 - Add "Falls through" comments to our codebase, in order to silence
6951 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
6952 Stieger. Closes ticket 22446.
6955 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
6958 o Minor bugfixes (compilation, backport from 0.3.1.7):
6959 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
6960 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
6962 o Minor bugfixes (controller, backport from 0.3.1.7):
6963 - Do not crash when receiving a HSPOST command with an empty body.
6964 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
6965 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
6966 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
6968 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
6969 - When setting the maximum number of connections allowed by the OS,
6970 always allow some extra file descriptors for other files. Fixes
6971 bug 22797; bugfix on 0.2.0.10-alpha.
6973 o Minor bugfixes (logging, relay, backport from 0.3.1.6-rc):
6974 - Remove a forgotten debugging message when an introduction point
6975 successfully establishes a hidden service prop224 circuit with
6977 - Change three other log_warn() for an introduction point to
6978 protocol warnings, because they can be failure from the network
6979 and are not relevant to the operator. Fixes bug 23078; bugfix on
6980 0.3.0.1-alpha and 0.3.0.2-alpha.
6983 Changes in version 0.3.1.7 - 2017-09-18
6984 Tor 0.3.1.7 is the first stable release in the 0.3.1 series.
6986 With the 0.3.1 series, Tor now serves and downloads directory
6987 information in more compact formats, to save on bandwidth overhead. It
6988 also contains a new padding system to resist netflow-based traffic
6989 analysis, and experimental support for building parts of Tor in Rust
6990 (though no parts of Tor are in Rust yet). There are also numerous
6991 small features, bugfixes on earlier release series, and groundwork for
6992 the hidden services revamp of 0.3.2.
6994 This release also includes a fix for TROVE-2017-008, a security bug
6995 that affects hidden services running with the SafeLogging option
6996 disabled. For more information, see
6997 https://trac.torproject.org/projects/tor/ticket/23490
6999 Per our stable release policy, we plan to support each stable release
7000 series for at least the next nine months, or for three months after
7001 the first stable release of the next series: whichever is longer. If
7002 you need a release with long-term support, we recommend that you stay
7003 with the 0.2.9 series.
7005 Below is a list of the changes since 0.3.1.6-rc. For a list of all
7006 changes since 0.3.0, see the ReleaseNotes file.
7008 o Major bugfixes (security, hidden services, loggging):
7009 - Fix a bug where we could log uninitialized stack when a certain
7010 hidden service error occurred while SafeLogging was disabled.
7011 Fixes bug #23490; bugfix on 0.2.7.2-alpha. This is also tracked as
7012 TROVE-2017-008 and CVE-2017-0380.
7014 o Minor features (defensive programming):
7015 - Create a pair of consensus parameters, nf_pad_tor2web and
7016 nf_pad_single_onion, to disable netflow padding in the consensus
7017 for non-anonymous connections in case the overhead is high. Closes
7020 o Minor features (diagnostic):
7021 - Add a stack trace to the bug warnings that can be logged when
7022 trying to send an outgoing relay cell with n_chan == 0. Diagnostic
7023 attempt for bug 23105.
7025 o Minor features (geoip):
7026 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
7029 o Minor bugfixes (compilation):
7030 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
7031 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
7033 o Minor bugfixes (controller):
7034 - Do not crash when receiving a HSPOST command with an empty body.
7035 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
7036 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
7037 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
7039 o Minor bugfixes (relay):
7040 - Inform the geoip and rephist modules about all requests, even on
7041 relays that are only fetching microdescriptors. Fixes a bug
7042 related to 21585; bugfix on 0.3.0.1-alpha.
7044 o Minor bugfixes (unit tests):
7045 - Fix a channelpadding unit test failure on slow systems by using
7046 mocked time instead of actual time. Fixes bug 23077; bugfix
7050 Changes in version 0.3.1.6-rc - 2017-09-05
7051 Tor 0.3.1.6-rc fixes a few small bugs and annoyances in the 0.3.1
7052 release series, including a bug that produced weird behavior on
7053 Windows directory caches.
7055 This is the first release candidate in the Tor 0.3.1 series. If we
7056 find no new bugs or regressions here, the first stable 0.3.1 release
7057 will be nearly identical to it.
7059 o Major bugfixes (windows, directory cache):
7060 - On Windows, do not try to delete cached consensus documents and
7061 diffs before they are unmapped from memory--Windows won't allow
7062 that. Instead, allow the consensus cache directory to grow larger,
7063 to hold files that might need to stay around longer. Fixes bug
7064 22752; bugfix on 0.3.1.1-alpha.
7066 o Minor features (directory authority):
7067 - Improve the message that authorities report to relays that present
7068 RSA/Ed25519 keypairs that conflict with previously pinned keys.
7069 Closes ticket 22348.
7071 o Minor features (geoip):
7072 - Update geoip and geoip6 to the August 3 2017 Maxmind GeoLite2
7075 o Minor features (testing):
7076 - Add more tests for compression backend initialization. Closes
7079 o Minor bugfixes (directory cache):
7080 - Fix a memory leak when recovering space in the consensus cache.
7081 Fixes bug 23139; bugfix on 0.3.1.1-alpha.
7083 o Minor bugfixes (hidden service):
7084 - Increase the number of circuits that a service is allowed to
7085 open over a specific period of time. The value was lower than it
7086 should be (8 vs 12) in the normal case of 3 introduction points.
7087 Fixes bug 22159; bugfix on 0.3.0.5-rc.
7088 - Fix a BUG warning during HSv3 descriptor decoding that could be
7089 cause by a specially crafted descriptor. Fixes bug 23233; bugfix
7090 on 0.3.0.1-alpha. Bug found by "haxxpop".
7091 - Rate-limit the log messages if we exceed the maximum number of
7092 allowed intro circuits. Fixes bug 22159; bugfix on 0.3.1.1-alpha.
7094 o Minor bugfixes (logging, relay):
7095 - Remove a forgotten debugging message when an introduction point
7096 successfully establishes a hidden service prop224 circuit with
7098 - Change three other log_warn() for an introduction point to
7099 protocol warnings, because they can be failure from the network
7100 and are not relevant to the operator. Fixes bug 23078; bugfix on
7101 0.3.0.1-alpha and 0.3.0.2-alpha.
7103 o Minor bugfixes (relay):
7104 - When a relay is not running as a directory cache, it will no
7105 longer generate compressed consensuses and consensus diff
7106 information. Previously, this was a waste of disk and CPU. Fixes
7107 bug 23275; bugfix on 0.3.1.1-alpha.
7109 o Minor bugfixes (robustness, error handling):
7110 - Improve our handling of the cases where OpenSSL encounters a
7111 memory error while encoding keys and certificates. We haven't
7112 observed these errors in the wild, but if they do happen, we now
7113 detect and respond better. Fixes bug 19418; bugfix on all versions
7114 of Tor. Reported by Guido Vranken.
7116 o Minor bugfixes (stability):
7117 - Avoid crashing on a double-free when unable to load or process an
7118 included file. Fixes bug 23155; bugfix on 0.3.1.1-alpha. Found
7119 with the clang static analyzer.
7121 o Minor bugfixes (testing):
7122 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
7123 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
7124 - Port the hs_ntor handshake test to work correctly with recent
7125 versions of the pysha3 module. Fixes bug 23071; bugfix
7128 o Minor bugfixes (Windows service):
7129 - When running as a Windows service, set the ID of the main thread
7130 correctly. Failure to do so made us fail to send log messages to
7131 the controller in 0.2.1.16-rc, slowed down controller event
7132 delivery in 0.2.7.3-rc and later, and crash with an assertion
7133 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
7134 Patch and diagnosis from "Vort".
7137 Changes in version 0.3.0.10 - 2017-08-02
7138 Tor 0.3.0.10 backports a collection of small-to-medium bugfixes
7139 from the current Tor alpha series. OpenBSD users and TPROXY users
7140 should upgrade; others are probably okay sticking with 0.3.0.9.
7142 o Major features (build system, continuous integration, backport from 0.3.1.5-alpha):
7143 - Tor's repository now includes a Travis Continuous Integration (CI)
7144 configuration file (.travis.yml). This is meant to help new
7145 developers and contributors who fork Tor to a Github repository be
7146 better able to test their changes, and understand what we expect
7147 to pass. To use this new build feature, you must fork Tor to your
7148 Github account, then go into the "Integrations" menu in the
7149 repository settings for your fork and enable Travis, then push
7150 your changes. Closes ticket 22636.
7152 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
7153 - Fix a typo that had prevented TPROXY-based transparent proxying
7154 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
7155 Patch from "d4fq0fQAgoJ".
7157 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
7158 - Avoid an assertion failure bug affecting our implementation of
7159 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
7160 handling of "0xbar" differs from what we had expected. Fixes bug
7161 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
7163 o Minor features (backport from 0.3.1.5-alpha):
7164 - Update geoip and geoip6 to the July 4 2017 Maxmind GeoLite2
7167 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.2-alpha):
7168 - Roll over monthly accounting at the configured hour and minute,
7169 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
7170 Found by Andrey Karpov with PVS-Studio.
7172 o Minor bugfixes (compilation warnings, backport from 0.3.1.5-alpha):
7173 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
7174 bugfix on 0.2.8.1-alpha.
7175 - Fix warnings when building with libscrypt and openssl scrypt
7176 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
7177 - When building with certain versions of the mingw C header files,
7178 avoid float-conversion warnings when calling the C functions
7179 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
7182 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
7183 - Backport a fix for an "unused variable" warning that appeared
7184 in some versions of mingw. Fixes bug 22838; bugfix on
7187 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
7188 - Avoid Coverity build warnings related to our BUG() macro. By
7189 default, Coverity treats BUG() as the Linux kernel does: an
7190 instant abort(). We need to override that so our BUG() macro
7191 doesn't prevent Coverity from analyzing functions that use it.
7192 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
7194 o Minor bugfixes (directory authority, backport from 0.3.1.1-alpha):
7195 - When rejecting a router descriptor for running an obsolete version
7196 of Tor without ntor support, warn about the obsolete tor version,
7197 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
7199 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
7200 - Avoid a sandbox failure when trying to re-bind to a socket and
7201 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
7203 o Minor bugfixes (unit tests, backport from 0.3.1.5-alpha)
7204 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
7205 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
7208 Changes in version 0.3.1.5-alpha - 2017-08-01
7209 Tor 0.3.1.5-alpha improves the performance of consensus diff
7210 calculation, fixes a crash bug on older versions of OpenBSD, and fixes
7211 several other bugs. If no serious bugs are found in this version, the
7212 next version will be a release candidate.
7214 This release also marks the end of support for the Tor 0.2.4.x,
7215 0.2.6.x, and 0.2.7.x release series. Those releases will receive no
7216 further bug or security fixes. Anyone still running or distributing
7217 one of those versions should upgrade.
7219 o Major features (build system, continuous integration):
7220 - Tor's repository now includes a Travis Continuous Integration (CI)
7221 configuration file (.travis.yml). This is meant to help new
7222 developers and contributors who fork Tor to a Github repository be
7223 better able to test their changes, and understand what we expect
7224 to pass. To use this new build feature, you must fork Tor to your
7225 Github account, then go into the "Integrations" menu in the
7226 repository settings for your fork and enable Travis, then push
7227 your changes. Closes ticket 22636.
7229 o Major bugfixes (openbsd, denial-of-service):
7230 - Avoid an assertion failure bug affecting our implementation of
7231 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
7232 handling of "0xbar" differs from what we had expected. Fixes bug
7233 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
7235 o Major bugfixes (relay, performance):
7236 - Perform circuit handshake operations at a higher priority than we
7237 use for consensus diff creation and compression. This should
7238 prevent circuits from starving when a relay or bridge receives a
7239 new consensus, especially on lower-powered machines. Fixes bug
7240 22883; bugfix on 0.3.1.1-alpha.
7242 o Minor features (bridge authority):
7243 - Add "fingerprint" lines to the networkstatus-bridges file produced
7244 by bridge authorities. Closes ticket 22207.
7246 o Minor features (directory cache, consensus diff):
7247 - Add a new MaxConsensusAgeForDiffs option to allow directory cache
7248 operators with low-resource environments to adjust the number of
7249 consensuses they'll store and generate diffs from. Most cache
7250 operators should leave it unchanged. Helps to work around
7253 o Minor features (geoip):
7254 - Update geoip and geoip6 to the July 4 2017 Maxmind GeoLite2
7257 o Minor features (relay, performance):
7258 - Always start relays with at least two worker threads, to prevent
7259 priority inversion on slow tasks. Part of the fix for bug 22883.
7260 - Allow background work to be queued with different priorities, so
7261 that a big pile of slow low-priority jobs will not starve out
7262 higher priority jobs. This lays the groundwork for a fix for
7265 o Minor bugfixes (build system, rust):
7266 - Fix a problem where Rust toolchains were not being found when
7267 building without --enable-cargo-online-mode, due to setting the
7268 $HOME environment variable instead of $CARGO_HOME. Fixes bug
7269 22830; bugfix on 0.3.1.1-alpha. Fix by Chelsea Komlo.
7271 o Minor bugfixes (compatibility, zstd):
7272 - Write zstd epilogues correctly when the epilogue requires
7273 reallocation of the output buffer, even with zstd 1.3.0.
7274 (Previously, we worked on 1.2.0 and failed with 1.3.0). Fixes bug
7275 22927; bugfix on 0.3.1.1-alpha.
7277 o Minor bugfixes (compilation warnings):
7278 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug
7279 22915; bugfix on 0.2.8.1-alpha.
7280 - Fix warnings when building with libscrypt and openssl scrypt
7281 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
7282 - Compile correctly when both openssl 1.1.0 and libscrypt are
7283 detected. Previously this would cause an error. Fixes bug 22892;
7284 bugfix on 0.3.1.1-alpha.
7285 - When building with certain versions of the mingw C header files,
7286 avoid float-conversion warnings when calling the C functions
7287 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
7290 o Minor bugfixes (coverity build support):
7291 - Avoid Coverity build warnings related to our BUG() macro. By
7292 default, Coverity treats BUG() as the Linux kernel does: an
7293 instant abort(). We need to override that so our BUG() macro
7294 doesn't prevent Coverity from analyzing functions that use it.
7295 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
7297 o Minor bugfixes (directory authority):
7298 - When a directory authority rejects a descriptor or extrainfo with
7299 a given digest, mark that digest as undownloadable, so that we do
7300 not attempt to download it again over and over. We previously
7301 tried to avoid downloading such descriptors by other means, but we
7302 didn't notice if we accidentally downloaded one anyway. This
7303 behavior became problematic in 0.2.7.2-alpha, when authorities
7304 began pinning Ed25519 keys. Fixes bug 22349; bugfix
7307 o Minor bugfixes (error reporting, windows):
7308 - When formatting Windows error messages, use the English format to
7309 avoid codepage issues. Fixes bug 22520; bugfix on 0.1.2.8-alpha.
7312 o Minor bugfixes (file limits, osx):
7313 - When setting the maximum number of connections allowed by the OS,
7314 always allow some extra file descriptors for other files. Fixes
7315 bug 22797; bugfix on 0.2.0.10-alpha.
7317 o Minor bugfixes (linux seccomp2 sandbox):
7318 - Avoid a sandbox failure when trying to re-bind to a socket and
7319 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
7321 o Minor bugfixes (memory leaks):
7322 - Fix a small memory leak when validating a configuration that uses
7323 two or more AF_UNIX sockets for the same port type. Fixes bug
7324 23053; bugfix on 0.2.6.3-alpha. This is CID 1415725.
7326 o Minor bugfixes (unit tests):
7327 - test_consdiff_base64cmp would fail on OS X because while OS X
7328 follows the standard of (less than zero/zero/greater than zero),
7329 it doesn't follow the convention of (-1/0/+1). Make the test
7330 comply with the standard. Fixes bug 22870; bugfix on 0.3.1.1-alpha.
7331 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
7332 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
7335 Changes in version 0.3.1.4-alpha - 2017-06-29
7336 Tor 0.3.1.4-alpha fixes a path selection bug that would allow a client
7337 to use a guard that was in the same network family as a chosen exit
7338 relay. This is a security regression; all clients running earlier
7339 versions of 0.3.0.x or 0.3.1.x should upgrade to 0.3.0.9
7342 This release also fixes several other bugs introduced in 0.3.0.x
7343 and 0.3.1.x, including others that can affect bandwidth usage
7347 - To build with zstd and lzma support, Tor now requires the
7348 pkg-config tool at build time. (This requirement was new in
7349 0.3.1.1-alpha, but was not noted at the time. Noting it here to
7350 close ticket 22623.)
7352 o Major bugfixes (path selection, security):
7353 - When choosing which guard to use for a circuit, avoid the exit's
7354 family along with the exit itself. Previously, the new guard
7355 selection logic avoided the exit, but did not consider its family.
7356 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
7357 006 and CVE-2017-0377.
7359 o Major bugfixes (compression, zstd):
7360 - Correctly detect a full buffer when decompressing a large zstd-
7361 compressed input. Previously, we would sometimes treat a full
7362 buffer as an error. Fixes bug 22628; bugfix on 0.3.1.1-alpha.
7364 o Major bugfixes (directory protocol):
7365 - Ensure that we send "304 Not modified" as HTTP status code when a
7366 client is attempting to fetch a consensus or consensus diff, and
7367 the best one we can send them is one they already have. Fixes bug
7368 22702; bugfix on 0.3.1.1-alpha.
7370 o Major bugfixes (entry guards):
7371 - When starting with an old consensus, do not add new entry guards
7372 unless the consensus is "reasonably live" (under 1 day old). Fixes
7373 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
7375 o Minor features (bug mitigation, diagnostics, logging):
7376 - Avoid an assertion failure, and log a better error message, when
7377 unable to remove a file from the consensus cache on Windows.
7378 Attempts to mitigate and diagnose bug 22752.
7380 o Minor features (geoip):
7381 - Update geoip and geoip6 to the June 8 2017 Maxmind GeoLite2
7384 o Minor bugfixes (compression):
7385 - When compressing or decompressing a buffer, check for a failure to
7386 create a compression object. Fixes bug 22626; bugfix
7388 - When decompressing a buffer, check for extra data after the end of
7389 the compressed data. Fixes bug 22629; bugfix on 0.3.1.1-alpha.
7390 - When decompressing an object received over an anonymous directory
7391 connection, if we have already decompressed it using an acceptable
7392 compression method, do not reject it for looking like an
7393 unacceptable compression method. Fixes part of bug 22670; bugfix
7395 - When serving directory votes compressed with zlib, do not claim to
7396 have compressed them with zstd. Fixes bug 22669; bugfix
7398 - When spooling compressed data to an output buffer, don't try to
7399 spool more data when there is no more data to spool and we are not
7400 trying to flush the input. Previously, we would sometimes launch
7401 compression requests with nothing to do, which interferes with our
7402 22672 checks. Fixes bug 22719; bugfix on 0.2.0.16-alpha.
7404 o Minor bugfixes (defensive programming):
7405 - Detect and break out of infinite loops in our compression code. We
7406 don't think that any such loops exist now, but it's best to be
7407 safe. Closes ticket 22672.
7408 - Fix a memset() off the end of an array when packing cells. This
7409 bug should be harmless in practice, since the corrupted bytes are
7410 still in the same structure, and are always padding bytes,
7411 ignored, or immediately overwritten, depending on compiler
7412 behavior. Nevertheless, because the memset()'s purpose is to make
7413 sure that any other cell-handling bugs can't expose bytes to the
7414 network, we need to fix it. Fixes bug 22737; bugfix on
7415 0.2.4.11-alpha. Fixes CID 1401591.
7417 o Minor bugfixes (linux seccomp2 sandbox):
7418 - Permit the fchmod system call, to avoid crashing on startup when
7419 starting with the seccomp2 sandbox and an unexpected set of
7420 permissions on the data directory or its contents. Fixes bug
7421 22516; bugfix on 0.2.5.4-alpha.
7422 - Fix a crash in the LZMA module, when the sandbox was enabled, and
7423 liblzma would allocate more than 16 MB of memory. We solve this by
7424 bumping the mprotect() limit in the sandbox module from 16 MB to
7425 20 MB. Fixes bug 22751; bugfix on 0.3.1.1-alpha.
7427 o Minor bugfixes (logging):
7428 - When decompressing, do not warn if we fail to decompress using a
7429 compression method that we merely guessed. Fixes part of bug
7430 22670; bugfix on 0.1.1.14-alpha.
7431 - When decompressing, treat mismatch between content-encoding and
7432 actual compression type as a protocol warning. Fixes part of bug
7433 22670; bugfix on 0.1.1.9-alpha.
7434 - Downgrade "assigned_to_cpuworker failed" message to info-level
7435 severity. In every case that can reach it, either a better warning
7436 has already been logged, or no warning is warranted. Fixes bug
7437 22356; bugfix on 0.2.6.3-alpha.
7438 - Demote a warn that was caused by libevent delays to info if
7439 netflow padding is less than 4.5 seconds late, or to notice
7440 if it is more (4.5 seconds is the amount of time that a netflow
7441 record might be emitted after, if we chose the maximum timeout).
7442 Fixes bug 22212; bugfix on 0.3.1.1-alpha.
7444 o Minor bugfixes (process behavior):
7445 - When exiting because of an error, always exit with a nonzero exit
7446 status. Previously, we would fail to report an error in our exit
7447 status in cases related to __OwningControllerProcess failure,
7448 lockfile contention, and Ed25519 key initialization. Fixes bug
7449 22720; bugfix on versions 0.2.1.6-alpha, 0.2.2.28-beta, and
7450 0.2.7.2-alpha respectively. Reported by "f55jwk4f"; patch
7454 - Add a manpage description for the key-pinning-journal file. Closes
7456 - Correctly note that bandwidth accounting values are stored in the
7457 state file, and the bw_accounting file is now obsolete. Closes
7459 - Document more of the files in the Tor data directory, including
7460 cached-extrainfo, secret_onion_key{,_ntor}.old, hidserv-stats,
7461 approved-routers, sr-random, and diff-cache. Found while fixing
7465 Changes in version 0.3.0.9 - 2017-06-29
7466 Tor 0.3.0.9 fixes a path selection bug that would allow a client
7467 to use a guard that was in the same network family as a chosen exit
7468 relay. This is a security regression; all clients running earlier
7469 versions of 0.3.0.x or 0.3.1.x should upgrade to 0.3.0.9 or
7472 This release also backports several other bugfixes from the 0.3.1.x
7475 o Major bugfixes (path selection, security, backport from 0.3.1.4-alpha):
7476 - When choosing which guard to use for a circuit, avoid the exit's
7477 family along with the exit itself. Previously, the new guard
7478 selection logic avoided the exit, but did not consider its family.
7479 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
7480 006 and CVE-2017-0377.
7482 o Major bugfixes (entry guards, backport from 0.3.1.1-alpha):
7483 - Don't block bootstrapping when a primary bridge is offline and we
7484 can't get its descriptor. Fixes bug 22325; fixes one case of bug
7485 21969; bugfix on 0.3.0.3-alpha.
7487 o Major bugfixes (entry guards, backport from 0.3.1.4-alpha):
7488 - When starting with an old consensus, do not add new entry guards
7489 unless the consensus is "reasonably live" (under 1 day old). Fixes
7490 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
7492 o Minor features (geoip):
7493 - Update geoip and geoip6 to the June 8 2017 Maxmind GeoLite2
7496 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
7497 - Reject version numbers with non-numeric prefixes (such as +, -, or
7498 whitespace). Disallowing whitespace prevents differential version
7499 parsing between POSIX-based and Windows platforms. Fixes bug 21507
7500 and part of 21508; bugfix on 0.0.8pre1.
7502 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
7503 - Permit the fchmod system call, to avoid crashing on startup when
7504 starting with the seccomp2 sandbox and an unexpected set of
7505 permissions on the data directory or its contents. Fixes bug
7506 22516; bugfix on 0.2.5.4-alpha.
7508 o Minor bugfixes (defensive programming, backport from 0.3.1.4-alpha):
7509 - Fix a memset() off the end of an array when packing cells. This
7510 bug should be harmless in practice, since the corrupted bytes are
7511 still in the same structure, and are always padding bytes,
7512 ignored, or immediately overwritten, depending on compiler
7513 behavior. Nevertheless, because the memset()'s purpose is to make
7514 sure that any other cell-handling bugs can't expose bytes to the
7515 network, we need to fix it. Fixes bug 22737; bugfix on
7516 0.2.4.11-alpha. Fixes CID 1401591.
7519 Changes in version 0.3.1.3-alpha - 2017-06-08
7520 Tor 0.3.1.3-alpha fixes a pair of bugs that would allow an attacker to
7521 remotely crash a hidden service with an assertion failure. Anyone
7522 running a hidden service should upgrade to this version, or to some
7523 other version with fixes for TROVE-2017-004 and TROVE-2017-005.
7525 Tor 0.3.1.3-alpha also includes fixes for several key management bugs
7526 that sometimes made relays unreliable, as well as several other
7527 bugfixes described below.
7529 o Major bugfixes (hidden service, relay, security):
7530 - Fix a remotely triggerable assertion failure when a hidden service
7531 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
7532 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
7533 - Fix a remotely triggerable assertion failure caused by receiving a
7534 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
7535 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
7538 o Major bugfixes (relay, link handshake):
7539 - When performing the v3 link handshake on a TLS connection, report
7540 that we have the x509 certificate that we actually used on that
7541 connection, even if we have changed certificates since that
7542 connection was first opened. Previously, we would claim to have
7543 used our most recent x509 link certificate, which would sometimes
7544 make the link handshake fail. Fixes one case of bug 22460; bugfix
7547 o Major bugfixes (relays, key management):
7548 - Regenerate link and authentication certificates whenever the key
7549 that signs them changes; also, regenerate link certificates
7550 whenever the signed key changes. Previously, these processes were
7551 only weakly coupled, and we relays could (for minutes to hours)
7552 wind up with an inconsistent set of keys and certificates, which
7553 other relays would not accept. Fixes two cases of bug 22460;
7554 bugfix on 0.3.0.1-alpha.
7555 - When sending an Ed25519 signing->link certificate in a CERTS cell,
7556 send the certificate that matches the x509 certificate that we
7557 used on the TLS connection. Previously, there was a race condition
7558 if the TLS context rotated after we began the TLS handshake but
7559 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
7562 o Major bugfixes (torrc, crash):
7563 - Fix a crash bug when using %include in torrc. Fixes bug 22417;
7564 bugfix on 0.3.1.1-alpha. Patch by Daniel Pinto.
7566 o Minor features (code style):
7567 - Add "Falls through" comments to our codebase, in order to silence
7568 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
7569 Stieger. Closes ticket 22446.
7571 o Minor features (diagnostic):
7572 - Add logging messages to try to diagnose a rare bug that seems to
7573 generate RSA->Ed25519 cross-certificates dated in the 1970s. We
7574 think this is happening because of incorrect system clocks, but
7575 we'd like to know for certain. Diagnostic for bug 22466.
7577 o Minor bugfixes (correctness):
7578 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
7579 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
7581 o Minor bugfixes (directory protocol):
7582 - Check for libzstd >= 1.1, because older versions lack the
7583 necessary streaming API. Fixes bug 22413; bugfix on 0.3.1.1-alpha.
7585 o Minor bugfixes (link handshake):
7586 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
7587 months, and regenerate it when it is within one month of expiring.
7588 Previously, we had generated this certificate at startup with a
7589 ten-year lifetime, but that could lead to weird behavior when Tor
7590 was started with a grossly inaccurate clock. Mitigates bug 22466;
7591 mitigation on 0.3.0.1-alpha.
7593 o Minor bugfixes (storage directories):
7594 - Always check for underflows in the cached storage directory usage.
7595 If the usage does underflow, re-calculate it. Also, avoid a
7596 separate underflow when the usage is not known. Fixes bug 22424;
7597 bugfix on 0.3.1.1-alpha.
7599 o Minor bugfixes (unit tests):
7600 - The unit tests now pass on systems where localhost is misconfigured
7601 to some IPv4 address other than 127.0.0.1. Fixes bug 6298; bugfix
7605 - Clarify the manpage for the (deprecated) torify script. Closes
7608 Changes in version 0.3.0.8 - 2017-06-08
7609 Tor 0.3.0.8 fixes a pair of bugs that would allow an attacker to
7610 remotely crash a hidden service with an assertion failure. Anyone
7611 running a hidden service should upgrade to this version, or to some
7612 other version with fixes for TROVE-2017-004 and TROVE-2017-005.
7614 Tor 0.3.0.8 also includes fixes for several key management bugs
7615 that sometimes made relays unreliable, as well as several other
7616 bugfixes described below.
7618 o Major bugfixes (hidden service, relay, security, backport
7619 from 0.3.1.3-alpha):
7620 - Fix a remotely triggerable assertion failure when a hidden service
7621 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
7622 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
7623 - Fix a remotely triggerable assertion failure caused by receiving a
7624 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
7625 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
7628 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
7629 - When performing the v3 link handshake on a TLS connection, report
7630 that we have the x509 certificate that we actually used on that
7631 connection, even if we have changed certificates since that
7632 connection was first opened. Previously, we would claim to have
7633 used our most recent x509 link certificate, which would sometimes
7634 make the link handshake fail. Fixes one case of bug 22460; bugfix
7637 o Major bugfixes (relays, key management, backport from 0.3.1.3-alpha):
7638 - Regenerate link and authentication certificates whenever the key
7639 that signs them changes; also, regenerate link certificates
7640 whenever the signed key changes. Previously, these processes were
7641 only weakly coupled, and we relays could (for minutes to hours)
7642 wind up with an inconsistent set of keys and certificates, which
7643 other relays would not accept. Fixes two cases of bug 22460;
7644 bugfix on 0.3.0.1-alpha.
7645 - When sending an Ed25519 signing->link certificate in a CERTS cell,
7646 send the certificate that matches the x509 certificate that we
7647 used on the TLS connection. Previously, there was a race condition
7648 if the TLS context rotated after we began the TLS handshake but
7649 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
7652 o Major bugfixes (hidden service v3, backport from 0.3.1.1-alpha):
7653 - Stop rejecting v3 hidden service descriptors because their size
7654 did not match an old padding rule. Fixes bug 22447; bugfix on
7657 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
7658 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
7659 December 2016 (of which ~126 were still functional) with a list of
7660 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
7661 2017. Resolves ticket 21564.
7663 o Minor bugfixes (configuration, backport from 0.3.1.1-alpha):
7664 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
7665 bug 22252; bugfix on 0.2.9.3-alpha.
7667 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
7668 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
7669 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
7671 o Minor bugfixes (link handshake, backport from 0.3.1.3-alpha):
7672 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
7673 months, and regenerate it when it is within one month of expiring.
7674 Previously, we had generated this certificate at startup with a
7675 ten-year lifetime, but that could lead to weird behavior when Tor
7676 was started with a grossly inaccurate clock. Mitigates bug 22466;
7677 mitigation on 0.3.0.1-alpha.
7679 o Minor bugfixes (memory leak, directory authority, backport from
7681 - When directory authorities reject a router descriptor due to
7682 keypinning, free the router descriptor rather than leaking the
7683 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
7686 Changes in version 0.2.9.11 - 2017-06-08
7687 Tor 0.2.9.11 backports a fix for a bug that would allow an attacker to
7688 remotely crash a hidden service with an assertion failure. Anyone
7689 running a hidden service should upgrade to this version, or to some
7690 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
7691 are not affected by TROVE-2017-004.)
7693 Tor 0.2.9.11 also backports fixes for several key management bugs
7694 that sometimes made relays unreliable, as well as several other
7695 bugfixes described below.
7697 o Major bugfixes (hidden service, relay, security, backport
7698 from 0.3.1.3-alpha):
7699 - Fix a remotely triggerable assertion failure caused by receiving a
7700 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
7701 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
7704 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
7705 - When performing the v3 link handshake on a TLS connection, report
7706 that we have the x509 certificate that we actually used on that
7707 connection, even if we have changed certificates since that
7708 connection was first opened. Previously, we would claim to have
7709 used our most recent x509 link certificate, which would sometimes
7710 make the link handshake fail. Fixes one case of bug 22460; bugfix
7713 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
7714 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
7715 December 2016 (of which ~126 were still functional) with a list of
7716 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
7717 2017. Resolves ticket 21564.
7719 o Minor features (future-proofing, backport from 0.3.0.7):
7720 - Tor no longer refuses to download microdescriptors or descriptors if
7721 they are listed as "published in the future". This change will
7722 eventually allow us to stop listing meaningful "published" dates
7723 in microdescriptor consensuses, and thereby allow us to reduce the
7724 resources required to download consensus diffs by over 50%.
7725 Implements part of ticket 21642; implements part of proposal 275.
7727 o Minor features (directory authorities, backport from 0.3.0.4-rc)
7728 - Directory authorities now reject relays running versions
7729 0.2.9.1-alpha through 0.2.9.4-alpha, because those relays
7730 suffer from bug 20499 and don't keep their consensus cache
7731 up-to-date. Resolves ticket 20509.
7733 o Minor features (geoip):
7734 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
7737 o Minor bugfixes (control port, backport from 0.3.0.6):
7738 - The GETINFO extra-info/digest/<digest> command was broken because
7739 of a wrong base16 decode return value check, introduced when
7740 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
7742 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
7743 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
7744 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
7746 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.0.7):
7747 - The getpid() system call is now permitted under the Linux seccomp2
7748 sandbox, to avoid crashing with versions of OpenSSL (and other
7749 libraries) that attempt to learn the process's PID by using the
7750 syscall rather than the VDSO code. Fixes bug 21943; bugfix
7753 o Minor bugfixes (memory leak, directory authority, backport
7754 from 0.3.1.2-alpha):
7755 - When directory authorities reject a router descriptor due to
7756 keypinning, free the router descriptor rather than leaking the
7757 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
7759 Changes in version 0.2.8.14 - 2017-06-08
7760 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
7761 remotely crash a hidden service with an assertion failure. Anyone
7762 running a hidden service should upgrade to this version, or to some
7763 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
7764 are not affected by TROVE-2017-004.)
7766 o Major bugfixes (hidden service, relay, security):
7767 - Fix a remotely triggerable assertion failure caused by receiving a
7768 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
7769 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
7772 o Minor features (geoip):
7773 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
7776 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
7777 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
7778 December 2016 (of which ~126 were still functional) with a list of
7779 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
7780 2017. Resolves ticket 21564.
7782 o Minor bugfixes (correctness):
7783 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
7784 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
7786 Changes in version 0.2.7.8 - 2017-06-08
7787 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
7788 remotely crash a hidden service with an assertion failure. Anyone
7789 running a hidden service should upgrade to this version, or to some
7790 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
7791 are not affected by TROVE-2017-004.)
7793 o Major bugfixes (hidden service, relay, security):
7794 - Fix a remotely triggerable assertion failure caused by receiving a
7795 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
7796 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
7799 o Minor features (geoip):
7800 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
7803 o Minor bugfixes (correctness):
7804 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
7805 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
7808 Changes in version 0.2.6.12 - 2017-06-08
7809 Tor 0.2.6.12 backports a fix for a bug that would allow an attacker to
7810 remotely crash a hidden service with an assertion failure. Anyone
7811 running a hidden service should upgrade to this version, or to some
7812 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
7813 are not affected by TROVE-2017-004.)
7815 o Major bugfixes (hidden service, relay, security):
7816 - Fix a remotely triggerable assertion failure caused by receiving a
7817 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
7818 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
7821 o Minor features (geoip):
7822 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
7825 o Minor bugfixes (correctness):
7826 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
7827 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
7829 Changes in version 0.2.5.14 - 2017-06-08
7830 Tor 0.2.5.14 backports a fix for a bug that would allow an attacker to
7831 remotely crash a hidden service with an assertion failure. Anyone
7832 running a hidden service should upgrade to this version, or to some
7833 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
7834 are not affected by TROVE-2017-004.)
7836 o Major bugfixes (hidden service, relay, security):
7837 - Fix a remotely triggerable assertion failure caused by receiving a
7838 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
7839 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
7842 o Minor features (geoip):
7843 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
7846 o Minor bugfixes (correctness):
7847 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
7848 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
7850 Changes in version 0.2.4.29 - 2017-06-08
7851 Tor 0.2.4.29 backports a fix for a bug that would allow an attacker to
7852 remotely crash a hidden service with an assertion failure. Anyone
7853 running a hidden service should upgrade to this version, or to some
7854 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
7855 are not affected by TROVE-2017-004.)
7857 o Major bugfixes (hidden service, relay, security):
7858 - Fix a remotely triggerable assertion failure caused by receiving a
7859 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
7860 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
7863 o Minor features (geoip):
7864 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
7867 o Minor bugfixes (correctness):
7868 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
7869 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
7872 Changes in version 0.3.1.2-alpha - 2017-05-26
7873 Tor 0.3.1.2-alpha is the second release in the 0.3.1.x series. It
7874 fixes a few bugs found while testing 0.3.1.1-alpha, including a
7875 memory corruption bug that affected relay stability.
7877 o Major bugfixes (crash, relay):
7878 - Fix a memory-corruption bug in relays that set MyFamily.
7879 Previously, they would double-free MyFamily elements when making
7880 the next descriptor or when changing their configuration. Fixes
7881 bug 22368; bugfix on 0.3.1.1-alpha.
7883 o Minor bugfixes (logging):
7884 - Log a better message when a directory authority replies to an
7885 upload with an unexpected status code. Fixes bug 11121; bugfix
7888 o Minor bugfixes (memory leak, directory authority):
7889 - When directory authorities reject a router descriptor due to
7890 keypinning, free the router descriptor rather than leaking the
7891 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
7894 Changes in version 0.3.1.1-alpha - 2017-05-22
7895 Tor 0.3.1.1-alpha is the first release in the 0.3.1.x series. It
7896 reduces the bandwidth usage for Tor's directory protocol, adds some
7897 basic padding to resist netflow-based traffic analysis and to serve as
7898 the basis of other padding in the future, and adds rust support to the
7901 It also contains numerous other small features and improvements to
7902 security, correctness, and performance.
7904 Below are the changes since 0.3.0.7.
7906 o Major features (directory protocol):
7907 - Tor relays and authorities can now serve clients an abbreviated
7908 version of the consensus document, containing only the changes
7909 since an older consensus document that the client holds. Clients
7910 now request these documents when available. When both client and
7911 server use this new protocol, they will use far less bandwidth (up
7912 to 94% less) to keep the client's consensus up-to-date. Implements
7913 proposal 140; closes ticket 13339. Based on work by Daniel Martí.
7914 - Tor can now compress directory traffic with lzma or with zstd
7915 compression algorithms, which can deliver better bandwidth
7916 performance. Because lzma is computationally expensive, it's only
7917 used for documents that can be compressed once and served many
7918 times. Support for these algorithms requires that tor is built
7919 with the libzstd and/or liblzma libraries available. Implements
7920 proposal 278; closes ticket 21662.
7921 - Relays now perform the more expensive compression operations, and
7922 consensus diff generation, in worker threads. This separation
7923 avoids delaying the main thread when a new consensus arrives.
7925 o Major features (experimental):
7926 - Tor can now build modules written in Rust. To turn this on, pass
7927 the "--enable-rust" flag to the configure script. It's not time to
7928 get excited yet: currently, there is no actual Rust functionality
7929 beyond some simple glue code, and a notice at startup to tell you
7930 that Rust is running. Still, we hope that programmers and
7931 packagers will try building Tor with Rust support, so that we can
7932 find issues and solve portability problems. Closes ticket 22106.
7934 o Major features (traffic analysis resistance):
7935 - Connections between clients and relays now send a padding cell in
7936 each direction every 1.5 to 9.5 seconds (tunable via consensus
7937 parameters). This padding will not resist specialized
7938 eavesdroppers, but it should be enough to make many ISPs' routine
7939 network flow logging less useful in traffic analysis against
7942 Padding is negotiated using Tor's link protocol, so both relays
7943 and clients must upgrade for this to take effect. Clients may
7944 still send padding despite the relay's version by setting
7945 ConnectionPadding 1 in torrc, and may disable padding by setting
7946 ConnectionPadding 0 in torrc. Padding may be minimized for mobile
7947 users with the torrc option ReducedConnectionPadding. Implements
7948 Proposal 251 and Section 2 of Proposal 254; closes ticket 16861.
7949 - Relays will publish 24 hour totals of padding and non-padding cell
7950 counts to their extra-info descriptors, unless PaddingStatistics 0
7951 is set in torrc. These 24 hour totals are also rounded to
7954 o Major bugfixes (connection usage):
7955 - We use NETINFO cells to try to determine if both relays involved
7956 in a connection will agree on the canonical status of that
7957 connection. We prefer the connections where this is the case for
7958 extend cells, and try to close connections where relays disagree
7959 on their canonical status early. Also, we now prefer the oldest
7960 valid connection for extend cells. These two changes should reduce
7961 the number of long-term connections that are kept open between
7962 relays. Fixes bug 17604; bugfix on 0.2.5.5-alpha.
7963 - Relays now log hourly statistics (look for
7964 "channel_check_for_duplicates" lines) on the total number of
7965 connections to other relays. If the number of connections per
7966 relay is unexpectedly large, this log message is at notice level.
7967 Otherwise it is at info.
7969 o Major bugfixes (entry guards):
7970 - Don't block bootstrapping when a primary bridge is offline and we
7971 can't get its descriptor. Fixes bug 22325; fixes one case of bug
7972 21969; bugfix on 0.3.0.3-alpha.
7974 o Major bugfixes (linux TPROXY support):
7975 - Fix a typo that had prevented TPROXY-based transparent proxying
7976 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
7977 Patch from "d4fq0fQAgoJ".
7979 o Minor features (security, windows):
7980 - Enable a couple of pieces of Windows hardening: one
7981 (HeapEnableTerminationOnCorruption) that has been on-by-default
7982 since Windows 8, and unavailable before Windows 7; and one
7983 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
7984 affect us, but shouldn't do any harm. Closes ticket 21953.
7986 o Minor features (config options):
7987 - Allow "%include" directives in torrc configuration files. These
7988 directives import the settings from other files, or from all the
7989 files in a directory. Closes ticket 1922. Code by Daniel Pinto.
7990 - Make SAVECONF return an error when overwriting a torrc that has
7991 includes. Using SAVECONF with the FORCE option will allow it to
7992 overwrite torrc even if includes are used. Related to ticket 1922.
7993 - Add "GETINFO config-can-saveconf" to tell controllers if SAVECONF
7994 will work without the FORCE option. Related to ticket 1922.
7996 o Minor features (controller):
7997 - Warn the first time that a controller requests data in the long-
7998 deprecated 'GETINFO network-status' format. Closes ticket 21703.
8000 o Minor features (defaults):
8001 - The default value for UseCreateFast is now 0: clients which
8002 haven't yet received a consensus document will now use a proper
8003 ntor handshake to talk to their directory servers whenever they
8004 can. Closes ticket 21407.
8005 - Onion key rotation and expiry intervals are now defined as a
8006 network consensus parameter, per proposal 274. The default
8007 lifetime of an onion key is increased from 7 to 28 days. Old onion
8008 keys will expire after 7 days by default. This change will make
8009 consensus diffs much smaller, and save significant bandwidth.
8010 Closes ticket 21641.
8012 o Minor features (fallback directory list):
8013 - Update the fallback directory mirror whitelist and blacklist based
8014 on operator emails. Closes task 21121.
8015 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
8016 December 2016 (of which ~126 were still functional) with a list of
8017 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
8018 2017. Resolves ticket 21564.
8020 o Minor features (hidden services, logging):
8021 - Log a message when a hidden service descriptor has fewer
8022 introduction points than specified in
8023 HiddenServiceNumIntroductionPoints. Closes tickets 21598.
8024 - Log a message when a hidden service reaches its introduction point
8025 circuit limit, and when that limit is reset. Follow up to ticket
8026 21594; closes ticket 21622.
8027 - Warn user if multiple entries in EntryNodes and at least one
8028 HiddenService are used together. Pinning EntryNodes along with a
8029 hidden service can be possibly harmful; for instance see ticket
8030 14917 or 21155. Closes ticket 21155.
8032 o Minor features (linux seccomp2 sandbox):
8033 - We now have a document storage backend compatible with the Linux
8034 seccomp2 sandbox. This backend is used for consensus documents and
8035 diffs between them; in the long term, we'd like to use it for
8036 unparseable directory material too. Closes ticket 21645
8037 - Increase the maximum allowed size passed to mprotect(PROT_WRITE)
8038 from 1MB to 16MB. This was necessary with the glibc allocator in
8039 order to allow worker threads to allocate more memory -- which in
8040 turn is necessary because of our new use of worker threads for
8041 compression. Closes ticket 22096.
8043 o Minor features (logging):
8044 - Log files are no longer created world-readable by default.
8045 (Previously, most distributors would store the logs in a non-
8046 world-readable location to prevent inappropriate access. This
8047 change is an extra precaution.) Closes ticket 21729; patch
8050 o Minor features (performance):
8051 - Our Keccak (SHA-3) implementation now accesses memory more
8052 efficiently, especially on little-endian systems. Closes
8054 - Add an O(1) implementation of channel_find_by_global_id(), to
8055 speed some controller functions.
8057 o Minor features (relay, configuration):
8058 - The MyFamily option may now be repeated as many times as desired,
8059 for relays that want to configure large families. Closes ticket
8060 4998; patch by Daniel Pinto.
8062 o Minor features (safety):
8063 - Add an explicit check to extrainfo_parse_entry_from_string() for
8064 NULL inputs. We don't believe this can actually happen, but it may
8065 help silence a warning from the Clang analyzer. Closes
8068 o Minor features (testing):
8069 - Add a "--disable-memory-sentinels" feature to help with fuzzing.
8070 When Tor is compiled with this option, we disable a number of
8071 redundant memory-safety failsafes that are intended to stop bugs
8072 from becoming security issues. This makes it easier to hunt for
8073 bugs that would be security issues without the failsafes turned
8074 on. Closes ticket 21439.
8075 - Add a general event-tracing instrumentation support to Tor. This
8076 subsystem will enable developers and researchers to add fine-
8077 grained instrumentation to their Tor instances, for use when
8078 examining Tor network performance issues. There are no trace
8079 events yet, and event-tracing is off by default unless enabled at
8080 compile time. Implements ticket 13802.
8081 - Improve our version parsing tests: add tests for typical version
8082 components, add tests for invalid versions, including numeric
8083 range and non-numeric prefixes. Unit tests 21278, 21450, and
8084 21507. Partially implements 21470.
8086 o Minor bugfixes (bandwidth accounting):
8087 - Roll over monthly accounting at the configured hour and minute,
8088 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
8089 Found by Andrey Karpov with PVS-Studio.
8091 o Minor bugfixes (code correctness):
8092 - Accurately identify client connections by their lack of peer
8093 authentication. This means that we bail out earlier if asked to
8094 extend to a client. Follow-up to 21407. Fixes bug 21406; bugfix
8097 o Minor bugfixes (configuration):
8098 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
8099 bug 22252; bugfix on 0.2.9.3-alpha.
8101 o Minor bugfixes (connection lifespan):
8102 - Allow more control over how long TLS connections are kept open:
8103 unify CircuitIdleTimeout and PredictedPortsRelevanceTime into a
8104 single option called CircuitsAvailableTimeout. Also, allow the
8105 consensus to control the default values for both this preference
8106 and the lifespan of relay-to-relay connections. Fixes bug 17592;
8107 bugfix on 0.2.5.5-alpha.
8108 - Increase the initial circuit build timeout testing frequency, to
8109 help ensure that ReducedConnectionPadding clients finish learning
8110 a timeout before their orconn would expire. The initial testing
8111 rate was set back in the days of TAP and before the Tor Browser
8112 updater, when we had to be much more careful about new clients
8113 making lots of circuits. With this change, a circuit build timeout
8114 is learned in about 15-20 minutes, instead of 100-120 minutes.
8116 o Minor bugfixes (controller):
8117 - GETINFO onions/current and onions/detached no longer respond with
8118 551 on empty lists. Fixes bug 21329; bugfix on 0.2.7.1-alpha.
8119 - Trigger HS descriptor events on the control port when the client
8120 fails to pick a hidden service directory for a hidden service.
8121 This can happen if all the hidden service directories are in
8122 ExcludeNodes, or they have all been queried within the last 15
8123 minutes. Fixes bug 22042; bugfix on 0.2.5.2-alpha.
8125 o Minor bugfixes (directory authority):
8126 - When rejecting a router descriptor for running an obsolete version
8127 of Tor without ntor support, warn about the obsolete tor version,
8128 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
8129 - Prevent the shared randomness subsystem from asserting when
8130 initialized by a bridge authority with an incomplete configuration
8131 file. Fixes bug 21586; bugfix on 0.2.9.8.
8133 o Minor bugfixes (exit-side DNS):
8134 - Fix an untriggerable assertion that checked the output of a
8135 libevent DNS error, so that the assertion actually behaves as
8136 expected. Fixes bug 22244; bugfix on 0.2.0.20-rc. Found by Andrey
8137 Karpov using PVS-Studio.
8139 o Minor bugfixes (fallback directories):
8140 - Make the usage example in updateFallbackDirs.py actually work, and
8141 explain what it does. Fixes bug 22270; bugfix on 0.3.0.3-alpha.
8142 - Decrease the guard flag average required to be a fallback. This
8143 allows us to keep relays that have their guard flag removed when
8144 they restart. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
8145 - Decrease the minimum number of fallbacks to 100. Fixes bug 20913;
8146 bugfix on 0.2.8.1-alpha.
8147 - Make sure fallback directory mirrors have the same address, port,
8148 and relay identity key for at least 30 days before they are
8149 selected. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
8151 o Minor bugfixes (hidden services):
8152 - Stop printing a cryptic warning when a hidden service gets a
8153 request to connect to a virtual port that it hasn't configured.
8154 Fixes bug 16706; bugfix on 0.2.6.3-alpha.
8155 - Simplify hidden service descriptor creation by using an existing
8156 flag to check if an introduction point is established. Fixes bug
8157 21599; bugfix on 0.2.7.2-alpha.
8159 o Minor bugfixes (memory leak):
8160 - Fix a small memory leak at exit from the backtrace handler code.
8161 Fixes bug 21788; bugfix on 0.2.5.2-alpha. Patch from Daniel Pinto.
8163 o Minor bugfixes (protocol, logging):
8164 - Downgrade a log statement about unexpected relay cells from "bug"
8165 to "protocol warning", because there is at least one use case
8166 where it can be triggered by a buggy tor implementation. Fixes bug
8167 21293; bugfix on 0.1.1.14-alpha.
8169 o Minor bugfixes (testing):
8170 - Use unbuffered I/O for utility functions around the
8171 process_handle_t type. This fixes unit test failures reported on
8172 OpenBSD and FreeBSD. Fixes bug 21654; bugfix on 0.2.3.1-alpha.
8173 - Make display of captured unit test log messages consistent. Fixes
8174 bug 21510; bugfix on 0.2.9.3-alpha.
8175 - Make test-network.sh always call chutney's test-network.sh.
8176 Previously, this only worked on systems which had bash installed,
8177 due to some bash-specific code in the script. Fixes bug 19699;
8178 bugfix on 0.3.0.4-rc. Follow-up to ticket 21581.
8180 o Minor bugfixes (voting consistency):
8181 - Reject version numbers with non-numeric prefixes (such as +, -, or
8182 whitespace). Disallowing whitespace prevents differential version
8183 parsing between POSIX-based and Windows platforms. Fixes bug 21507
8184 and part of 21508; bugfix on 0.0.8pre1.
8186 o Minor bugfixes (windows, relay):
8187 - Resolve "Failure from drain_fd: No error" warnings on Windows
8188 relays. Fixes bug 21540; bugfix on 0.2.6.3-alpha.
8190 o Code simplification and refactoring:
8191 - Break up the 630-line function connection_dir_client_reached_eof()
8192 into a dozen smaller functions. This change should help
8193 maintainability and readability of the client directory code.
8194 - Isolate our use of the openssl headers so that they are only
8195 included from our crypto wrapper modules, and from tests that
8196 examine those modules' internals. Closes ticket 21841.
8197 - Simplify our API to launch directory requests, making it more
8198 extensible and less error-prone. Now it's easier to add extra
8199 headers to directory requests. Closes ticket 21646.
8200 - Our base64 decoding functions no longer overestimate the output
8201 space that they need when parsing unpadded inputs. Closes
8203 - Remove unused "ROUTER_ADDED_NOTIFY_GENERATOR" internal value.
8204 Resolves ticket 22213.
8205 - The logic that directory caches use to spool request to clients,
8206 serving them one part at a time so as not to allocate too much
8207 memory, has been refactored for consistency. Previously there was
8208 a separate spooling implementation per type of spoolable data. Now
8209 there is one common spooling implementation, with extensible data
8210 types. Closes ticket 21651.
8211 - Tor's compression module now supports multiple backends. Part of
8212 the implementation for proposal 278; closes ticket 21663.
8215 - Clarify the behavior of the KeepAliveIsolateSOCKSAuth sub-option.
8216 Closes ticket 21873.
8217 - Correct documentation about the default DataDirectory value.
8218 Closes ticket 21151.
8219 - Document the default behavior of NumEntryGuards and
8220 NumDirectoryGuards correctly. Fixes bug 21715; bugfix
8222 - Document key=value pluggable transport arguments for Bridge lines
8223 in torrc. Fixes bug 20341; bugfix on 0.2.5.1-alpha.
8224 - Note that bandwidth-limiting options don't affect TCP headers or
8225 DNS. Closes ticket 17170.
8227 o Removed features (configuration options, all in ticket 22060):
8228 - These configuration options are now marked Obsolete, and no longer
8229 have any effect: AllowInvalidNodes, AllowSingleHopCircuits,
8230 AllowSingleHopExits, ExcludeSingleHopRelays, FastFirstHopPK,
8231 TLSECGroup, WarnUnsafeSocks. They were first marked as deprecated
8232 in 0.2.9.2-alpha and have now been removed. The previous default
8233 behavior is now always chosen; the previous (less secure) non-
8234 default behavior is now unavailable.
8235 - CloseHSClientCircuitsImmediatelyOnTimeout and
8236 CloseHSServiceRendCircuitsImmediatelyOnTimeout were deprecated in
8237 0.2.9.2-alpha and now have been removed. HS circuits never close
8238 on circuit build timeout; they have a longer timeout period.
8239 - {Control,DNS,Dir,Socks,Trans,NATD,OR}ListenAddress were deprecated
8240 in 0.2.9.2-alpha and now have been removed. Use the ORPort option
8241 (and others) to configure listen-only and advertise-only addresses.
8243 o Removed features (tools):
8244 - We've removed the tor-checkkey tool from src/tools. Long ago, we
8245 used it to help people detect RSA keys that were generated by
8246 versions of Debian affected by CVE-2008-0166. But those keys have
8247 been out of circulation for ages, and this tool is no longer
8248 required. Closes ticket 21842.
8251 Changes in version 0.3.0.7 - 2017-05-15
8252 Tor 0.3.0.7 fixes a medium-severity security bug in earlier versions
8253 of Tor 0.3.0.x, where an attacker could cause a Tor relay process
8254 to exit. Relays running earlier versions of Tor 0.3.0.x should upgrade;
8255 clients are not affected.
8257 o Major bugfixes (hidden service directory, security):
8258 - Fix an assertion failure in the hidden service directory code, which
8259 could be used by an attacker to remotely cause a Tor relay process to
8260 exit. Relays running earlier versions of Tor 0.3.0.x should upgrade.
8261 should upgrade. This security issue is tracked as TROVE-2017-002.
8262 Fixes bug 22246; bugfix on 0.3.0.1-alpha.
8265 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
8268 o Minor features (future-proofing):
8269 - Tor no longer refuses to download microdescriptors or descriptors
8270 if they are listed as "published in the future". This change will
8271 eventually allow us to stop listing meaningful "published" dates
8272 in microdescriptor consensuses, and thereby allow us to reduce the
8273 resources required to download consensus diffs by over 50%.
8274 Implements part of ticket 21642; implements part of proposal 275.
8276 o Minor bugfixes (Linux seccomp2 sandbox):
8277 - The getpid() system call is now permitted under the Linux seccomp2
8278 sandbox, to avoid crashing with versions of OpenSSL (and other
8279 libraries) that attempt to learn the process's PID by using the
8280 syscall rather than the VDSO code. Fixes bug 21943; bugfix
8284 Changes in version 0.3.0.6 - 2017-04-26
8285 Tor 0.3.0.6 is the first stable release of the Tor 0.3.0 series.
8287 With the 0.3.0 series, clients and relays now use Ed25519 keys to
8288 authenticate their link connections to relays, rather than the old
8289 RSA1024 keys that they used before. (Circuit crypto has been
8290 Curve25519-authenticated since 0.2.4.8-alpha.) We have also replaced
8291 the guard selection and replacement algorithm to behave more robustly
8292 in the presence of unreliable networks, and to resist guard-
8295 This series also includes numerous other small features and bugfixes,
8296 along with more groundwork for the upcoming hidden-services revamp.
8298 Per our stable release policy, we plan to support the Tor 0.3.0
8299 release series for at least the next nine months, or for three months
8300 after the first stable release of the 0.3.1 series: whichever is
8301 longer. If you need a release with long-term support, we recommend
8302 that you stay with the 0.2.9 series.
8304 Below are the changes since 0.3.0.5-rc. For a list of all changes
8305 since 0.2.9, see the ReleaseNotes file.
8307 o Minor features (geoip):
8308 - Update geoip and geoip6 to the April 4 2017 Maxmind GeoLite2
8311 o Minor bugfixes (control port):
8312 - The GETINFO extra-info/digest/<digest> command was broken because
8313 of a wrong base16 decode return value check, introduced when
8314 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
8316 o Minor bugfixes (crash prevention):
8317 - Fix a (currently untriggerable, but potentially dangerous) crash
8318 bug when base32-encoding inputs whose sizes are not a multiple of
8319 5. Fixes bug 21894; bugfix on 0.2.9.1-alpha.
8322 Changes in version 0.3.0.5-rc - 2017-04-05
8323 Tor 0.3.0.5-rc fixes a few remaining bugs, large and small, in the
8324 0.3.0 release series.
8326 This is the second release candidate in the Tor 0.3.0 series, and has
8327 much fewer changes than the first. If we find no new bugs or
8328 regressions here, the first stable 0.3.0 release will be nearly
8331 o Major bugfixes (crash, directory connections):
8332 - Fix a rare crash when sending a begin cell on a circuit whose
8333 linked directory connection had already been closed. Fixes bug
8334 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
8336 o Major bugfixes (guard selection):
8337 - Fix a guard selection bug where Tor would refuse to bootstrap in
8338 some cases if the user swapped a bridge for another bridge in
8339 their configuration file. Fixes bug 21771; bugfix on 0.3.0.1-alpha.
8340 Reported by "torvlnt33r".
8342 o Minor features (geoip):
8343 - Update geoip and geoip6 to the March 7 2017 Maxmind GeoLite2
8346 o Minor bugfix (compilation):
8347 - Fix a warning when compiling hs_service.c. Previously, it had no
8348 exported symbols when compiled for libor.a, resulting in a
8349 compilation warning from clang. Fixes bug 21825; bugfix
8352 o Minor bugfixes (hidden services):
8353 - Make hidden services check for failed intro point connections,
8354 even when they have exceeded their intro point creation limit.
8355 Fixes bug 21596; bugfix on 0.2.7.2-alpha. Reported by Alec Muffett.
8356 - Make hidden services with 8 to 10 introduction points check for
8357 failed circuits immediately after startup. Previously, they would
8358 wait for 5 minutes before performing their first checks. Fixes bug
8359 21594; bugfix on 0.2.3.9-alpha. Reported by Alec Muffett.
8361 o Minor bugfixes (memory leaks):
8362 - Fix a memory leak when using GETCONF on a port option. Fixes bug
8363 21682; bugfix on 0.3.0.3-alpha.
8365 o Minor bugfixes (relay):
8366 - Avoid a double-marked-circuit warning that could happen when we
8367 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
8370 o Minor bugfixes (tests):
8371 - Run the entry_guard_parse_from_state_full() test with the time set
8372 to a specific date. (The guard state that this test was parsing
8373 contained guards that had expired since the test was first
8374 written.) Fixes bug 21799; bugfix on 0.3.0.1-alpha.
8377 - Update the description of the directory server options in the
8378 manual page, to clarify that a relay no longer needs to set
8379 DirPort in order to be a directory cache. Closes ticket 21720.
8383 Changes in version 0.2.8.13 - 2017-03-03
8384 Tor 0.2.8.13 backports a security fix from later Tor
8385 releases. Anybody running Tor 0.2.8.12 or earlier should upgrade to this
8386 this release, if for some reason they cannot upgrade to a later
8387 release series, and if they build Tor with the --enable-expensive-hardening
8390 Note that support for Tor 0.2.8.x is ending next year: we will not issue
8391 any fixes for the Tor 0.2.8.x series after 1 Jan 2018. If you need
8392 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
8394 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
8395 - Fix an integer underflow bug when comparing malformed Tor
8396 versions. This bug could crash Tor when built with
8397 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
8398 0.2.9.8, which were built with -ftrapv by default. In other cases
8399 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
8400 on 0.0.8pre1. Found by OSS-Fuzz.
8402 o Minor features (geoip):
8403 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
8407 Changes in version 0.2.7.7 - 2017-03-03
8408 Tor 0.2.7.7 backports a number of security fixes from later Tor
8409 releases. Anybody running Tor 0.2.7.6 or earlier should upgrade to
8410 this release, if for some reason they cannot upgrade to a later
8413 Note that support for Tor 0.2.7.x is ending this year: we will not issue
8414 any fixes for the Tor 0.2.7.x series after 1 August 2017. If you need
8415 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
8417 o Directory authority changes (backport from 0.2.8.5-rc):
8418 - Urras is no longer a directory authority. Closes ticket 19271.
8420 o Directory authority changes (backport from 0.2.9.2-alpha):
8421 - The "Tonga" bridge authority has been retired; the new bridge
8422 authority is "Bifroest". Closes tickets 19728 and 19690.
8424 o Directory authority key updates (backport from 0.2.8.1-alpha):
8425 - Update the V3 identity key for the dannenberg directory authority:
8426 it was changed on 18 November 2015. Closes task 17906. Patch
8429 o Major bugfixes (parsing, security, backport from 0.2.9.8):
8430 - Fix a bug in parsing that could cause clients to read a single
8431 byte past the end of an allocated region. This bug could be used
8432 to cause hardened clients (built with --enable-expensive-hardening)
8433 to crash if they tried to visit a hostile hidden service. Non-
8434 hardened clients are only affected depending on the details of
8435 their platform's memory allocator. Fixes bug 21018; bugfix on
8436 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
8437 2016-12-002 and as CVE-2016-1254.
8439 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
8440 - Stop a crash that could occur when a client running with DNSPort
8441 received a query with multiple address types, and the first
8442 address type was not supported. Found and fixed by Scott Dial.
8443 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
8444 - Prevent a class of security bugs caused by treating the contents
8445 of a buffer chunk as if they were a NUL-terminated string. At
8446 least one such bug seems to be present in all currently used
8447 versions of Tor, and would allow an attacker to remotely crash
8448 most Tor instances, especially those compiled with extra compiler
8449 hardening. With this defense in place, such bugs can't crash Tor,
8450 though we should still fix them as they occur. Closes ticket
8451 20384 (TROVE-2016-10-001).
8453 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
8454 - Avoid a difficult-to-trigger heap corruption attack when extending
8455 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
8456 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
8457 Reported by Guido Vranken.
8459 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
8460 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
8461 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
8463 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
8464 - If OpenSSL fails to generate an RSA key, do not retain a dangling
8465 pointer to the previous (uninitialized) key value. The impact here
8466 should be limited to a difficult-to-trigger crash, if OpenSSL is
8467 running an engine that makes key generation failures possible, or
8468 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
8469 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
8472 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
8473 - Fix an integer underflow bug when comparing malformed Tor
8474 versions. This bug could crash Tor when built with
8475 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
8476 0.2.9.8, which were built with -ftrapv by default. In other cases
8477 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
8478 on 0.0.8pre1. Found by OSS-Fuzz.
8480 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
8481 - Make memwipe() do nothing when passed a NULL pointer or buffer of
8482 zero size. Check size argument to memwipe() for underflow. Fixes
8483 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
8486 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
8487 - Make Tor survive errors involving connections without a
8488 corresponding event object. Previously we'd fail with an
8489 assertion; now we produce a log message. Related to bug 16248.
8491 o Minor features (geoip):
8492 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
8496 Changes in version 0.2.6.11 - 2017-03-03
8497 Tor 0.2.6.11 backports a number of security fixes from later Tor
8498 releases. Anybody running Tor 0.2.6.10 or earlier should upgrade to
8499 this release, if for some reason they cannot upgrade to a later
8502 Note that support for Tor 0.2.6.x is ending this year: we will not issue
8503 any fixes for the Tor 0.2.6.x series after 1 August 2017. If you need
8504 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
8506 o Directory authority changes (backport from 0.2.8.5-rc):
8507 - Urras is no longer a directory authority. Closes ticket 19271.
8509 o Directory authority changes (backport from 0.2.9.2-alpha):
8510 - The "Tonga" bridge authority has been retired; the new bridge
8511 authority is "Bifroest". Closes tickets 19728 and 19690.
8513 o Directory authority key updates (backport from 0.2.8.1-alpha):
8514 - Update the V3 identity key for the dannenberg directory authority:
8515 it was changed on 18 November 2015. Closes task 17906. Patch
8518 o Major features (security fixes, backport from 0.2.9.4-alpha):
8519 - Prevent a class of security bugs caused by treating the contents
8520 of a buffer chunk as if they were a NUL-terminated string. At
8521 least one such bug seems to be present in all currently used
8522 versions of Tor, and would allow an attacker to remotely crash
8523 most Tor instances, especially those compiled with extra compiler
8524 hardening. With this defense in place, such bugs can't crash Tor,
8525 though we should still fix them as they occur. Closes ticket
8526 20384 (TROVE-2016-10-001).
8528 o Major bugfixes (parsing, security, backport from 0.2.9.8):
8529 - Fix a bug in parsing that could cause clients to read a single
8530 byte past the end of an allocated region. This bug could be used
8531 to cause hardened clients (built with --enable-expensive-hardening)
8532 to crash if they tried to visit a hostile hidden service. Non-
8533 hardened clients are only affected depending on the details of
8534 their platform's memory allocator. Fixes bug 21018; bugfix on
8535 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
8536 2016-12-002 and as CVE-2016-1254.
8538 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
8539 - Stop a crash that could occur when a client running with DNSPort
8540 received a query with multiple address types, and the first
8541 address type was not supported. Found and fixed by Scott Dial.
8542 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
8544 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
8545 - Fix an error that could cause us to read 4 bytes before the
8546 beginning of an openssl string. This bug could be used to cause
8547 Tor to crash on systems with unusual malloc implementations, or
8548 systems with unusual hardening installed. Fixes bug 17404; bugfix
8551 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
8552 - Avoid a difficult-to-trigger heap corruption attack when extending
8553 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
8554 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
8555 Reported by Guido Vranken.
8557 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
8558 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
8559 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
8561 o Major bugfixes (guard selection, backport from 0.2.7.6):
8562 - Actually look at the Guard flag when selecting a new directory
8563 guard. When we implemented the directory guard design, we
8564 accidentally started treating all relays as if they have the Guard
8565 flag during guard selection, leading to weaker anonymity and worse
8566 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
8569 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
8570 - If OpenSSL fails to generate an RSA key, do not retain a dangling
8571 pointer to the previous (uninitialized) key value. The impact here
8572 should be limited to a difficult-to-trigger crash, if OpenSSL is
8573 running an engine that makes key generation failures possible, or
8574 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
8575 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
8578 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
8579 - Fix an integer underflow bug when comparing malformed Tor
8580 versions. This bug could crash Tor when built with
8581 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
8582 0.2.9.8, which were built with -ftrapv by default. In other cases
8583 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
8584 on 0.0.8pre1. Found by OSS-Fuzz.
8586 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
8587 - Make memwipe() do nothing when passed a NULL pointer or buffer of
8588 zero size. Check size argument to memwipe() for underflow. Fixes
8589 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
8592 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
8593 - Make Tor survive errors involving connections without a
8594 corresponding event object. Previously we'd fail with an
8595 assertion; now we produce a log message. Related to bug 16248.
8597 o Minor features (geoip):
8598 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
8601 o Minor bugfixes (compilation, backport from 0.2.7.6):
8602 - Fix a compilation warning with Clang 3.6: Do not check the
8603 presence of an address which can never be NULL. Fixes bug 17781.
8606 Changes in version 0.2.5.13 - 2017-03-03
8607 Tor 0.2.5.13 backports a number of security fixes from later Tor
8608 releases. Anybody running Tor 0.2.5.13 or earlier should upgrade to
8609 this release, if for some reason they cannot upgrade to a later
8612 Note that support for Tor 0.2.5.x is ending next year: we will not issue
8613 any fixes for the Tor 0.2.5.x series after 1 May 2018. If you need
8614 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
8616 o Directory authority changes (backport from 0.2.8.5-rc):
8617 - Urras is no longer a directory authority. Closes ticket 19271.
8619 o Directory authority changes (backport from 0.2.9.2-alpha):
8620 - The "Tonga" bridge authority has been retired; the new bridge
8621 authority is "Bifroest". Closes tickets 19728 and 19690.
8623 o Directory authority key updates (backport from 0.2.8.1-alpha):
8624 - Update the V3 identity key for the dannenberg directory authority:
8625 it was changed on 18 November 2015. Closes task 17906. Patch
8628 o Major features (security fixes, backport from 0.2.9.4-alpha):
8629 - Prevent a class of security bugs caused by treating the contents
8630 of a buffer chunk as if they were a NUL-terminated string. At
8631 least one such bug seems to be present in all currently used
8632 versions of Tor, and would allow an attacker to remotely crash
8633 most Tor instances, especially those compiled with extra compiler
8634 hardening. With this defense in place, such bugs can't crash Tor,
8635 though we should still fix them as they occur. Closes ticket
8636 20384 (TROVE-2016-10-001).
8638 o Major bugfixes (parsing, security, backport from 0.2.9.8):
8639 - Fix a bug in parsing that could cause clients to read a single
8640 byte past the end of an allocated region. This bug could be used
8641 to cause hardened clients (built with --enable-expensive-hardening)
8642 to crash if they tried to visit a hostile hidden service. Non-
8643 hardened clients are only affected depending on the details of
8644 their platform's memory allocator. Fixes bug 21018; bugfix on
8645 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
8646 2016-12-002 and as CVE-2016-1254.
8648 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
8649 - Stop a crash that could occur when a client running with DNSPort
8650 received a query with multiple address types, and the first
8651 address type was not supported. Found and fixed by Scott Dial.
8652 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
8654 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
8655 - Fix an error that could cause us to read 4 bytes before the
8656 beginning of an openssl string. This bug could be used to cause
8657 Tor to crash on systems with unusual malloc implementations, or
8658 systems with unusual hardening installed. Fixes bug 17404; bugfix
8661 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
8662 - Avoid a difficult-to-trigger heap corruption attack when extending
8663 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
8664 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
8665 Reported by Guido Vranken.
8667 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
8668 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
8669 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
8671 o Major bugfixes (guard selection, backport from 0.2.7.6):
8672 - Actually look at the Guard flag when selecting a new directory
8673 guard. When we implemented the directory guard design, we
8674 accidentally started treating all relays as if they have the Guard
8675 flag during guard selection, leading to weaker anonymity and worse
8676 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
8679 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
8680 - If OpenSSL fails to generate an RSA key, do not retain a dangling
8681 pointer to the previous (uninitialized) key value. The impact here
8682 should be limited to a difficult-to-trigger crash, if OpenSSL is
8683 running an engine that makes key generation failures possible, or
8684 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
8685 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
8688 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
8689 - Fix an integer underflow bug when comparing malformed Tor
8690 versions. This bug could crash Tor when built with
8691 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
8692 0.2.9.8, which were built with -ftrapv by default. In other cases
8693 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
8694 on 0.0.8pre1. Found by OSS-Fuzz.
8696 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
8697 - Make memwipe() do nothing when passed a NULL pointer or buffer of
8698 zero size. Check size argument to memwipe() for underflow. Fixes
8699 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
8702 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
8703 - Make Tor survive errors involving connections without a
8704 corresponding event object. Previously we'd fail with an
8705 assertion; now we produce a log message. Related to bug 16248.
8707 o Minor features (geoip):
8708 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
8711 o Minor bugfixes (compilation, backport from 0.2.7.6):
8712 - Fix a compilation warning with Clang 3.6: Do not check the
8713 presence of an address which can never be NULL. Fixes bug 17781.
8715 o Minor bugfixes (crypto error-handling, backport from 0.2.7.2-alpha):
8716 - Check for failures from crypto_early_init, and refuse to continue.
8717 A previous typo meant that we could keep going with an
8718 uninitialized crypto library, and would have OpenSSL initialize
8719 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
8720 when implementing ticket 4900. Patch by "teor".
8722 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
8723 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
8724 a client authorized hidden service. Fixes bug 15823; bugfix
8728 Changes in version 0.2.4.28 - 2017-03-03
8729 Tor 0.2.4.28 backports a number of security fixes from later Tor
8730 releases. Anybody running Tor 0.2.4.27 or earlier should upgrade to
8731 this release, if for some reason they cannot upgrade to a later
8734 Note that support for Tor 0.2.4.x is ending soon: we will not issue
8735 any fixes for the Tor 0.2.4.x series after 1 August 2017. If you need
8736 a Tor release series with long-term support, we recommend Tor 0.2.9.x.
8738 o Directory authority changes (backport from 0.2.8.5-rc):
8739 - Urras is no longer a directory authority. Closes ticket 19271.
8741 o Directory authority changes (backport from 0.2.9.2-alpha):
8742 - The "Tonga" bridge authority has been retired; the new bridge
8743 authority is "Bifroest". Closes tickets 19728 and 19690.
8745 o Directory authority key updates (backport from 0.2.8.1-alpha):
8746 - Update the V3 identity key for the dannenberg directory authority:
8747 it was changed on 18 November 2015. Closes task 17906. Patch
8750 o Major features (security fixes, backport from 0.2.9.4-alpha):
8751 - Prevent a class of security bugs caused by treating the contents
8752 of a buffer chunk as if they were a NUL-terminated string. At
8753 least one such bug seems to be present in all currently used
8754 versions of Tor, and would allow an attacker to remotely crash
8755 most Tor instances, especially those compiled with extra compiler
8756 hardening. With this defense in place, such bugs can't crash Tor,
8757 though we should still fix them as they occur. Closes ticket
8758 20384 (TROVE-2016-10-001).
8760 o Major bugfixes (parsing, security, backport from 0.2.9.8):
8761 - Fix a bug in parsing that could cause clients to read a single
8762 byte past the end of an allocated region. This bug could be used
8763 to cause hardened clients (built with --enable-expensive-hardening)
8764 to crash if they tried to visit a hostile hidden service. Non-
8765 hardened clients are only affected depending on the details of
8766 their platform's memory allocator. Fixes bug 21018; bugfix on
8767 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
8768 2016-12-002 and as CVE-2016-1254.
8770 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
8771 - Fix an error that could cause us to read 4 bytes before the
8772 beginning of an openssl string. This bug could be used to cause
8773 Tor to crash on systems with unusual malloc implementations, or
8774 systems with unusual hardening installed. Fixes bug 17404; bugfix
8777 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
8778 - Avoid a difficult-to-trigger heap corruption attack when extending
8779 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
8780 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
8781 Reported by Guido Vranken.
8783 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
8784 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
8785 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
8787 o Major bugfixes (guard selection, backport from 0.2.7.6):
8788 - Actually look at the Guard flag when selecting a new directory
8789 guard. When we implemented the directory guard design, we
8790 accidentally started treating all relays as if they have the Guard
8791 flag during guard selection, leading to weaker anonymity and worse
8792 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
8795 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
8796 - If OpenSSL fails to generate an RSA key, do not retain a dangling
8797 pointer to the previous (uninitialized) key value. The impact here
8798 should be limited to a difficult-to-trigger crash, if OpenSSL is
8799 running an engine that makes key generation failures possible, or
8800 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
8801 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
8804 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
8805 - Fix an integer underflow bug when comparing malformed Tor
8806 versions. This bug could crash Tor when built with
8807 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
8808 0.2.9.8, which were built with -ftrapv by default. In other cases
8809 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
8810 on 0.0.8pre1. Found by OSS-Fuzz.
8812 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
8813 - Make memwipe() do nothing when passed a NULL pointer or buffer of
8814 zero size. Check size argument to memwipe() for underflow. Fixes
8815 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
8818 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
8819 - Make Tor survive errors involving connections without a
8820 corresponding event object. Previously we'd fail with an
8821 assertion; now we produce a log message. Related to bug 16248.
8823 o Minor features (DoS-resistance, backport from 0.2.7.1-alpha):
8824 - Make it harder for attackers to overload hidden services with
8825 introductions, by blocking multiple introduction requests on the
8826 same circuit. Resolves ticket 15515.
8828 o Minor features (geoip):
8829 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
8832 o Minor bugfixes (compilation, backport from 0.2.7.6):
8833 - Fix a compilation warning with Clang 3.6: Do not check the
8834 presence of an address which can never be NULL. Fixes bug 17781.
8836 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
8837 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
8838 a client authorized hidden service. Fixes bug 15823; bugfix
8842 Changes in version 0.3.0.4-rc - 2017-03-01
8843 Tor 0.3.0.4-rc fixes some remaining bugs, large and small, in the
8844 0.3.0 release series, and introduces a few reliability features to
8845 keep them from coming back.
8847 This is the first release candidate in the Tor 0.3.0 series. If we
8848 find no new bugs or regressions here, the first stable 0.3.0 release
8849 will be nearly identical to it.
8851 o Major bugfixes (bridges):
8852 - When the same bridge is configured multiple times with the same
8853 identity, but at different address:port combinations, treat those
8854 bridge instances as separate guards. This fix restores the ability
8855 of clients to configure the same bridge with multiple pluggable
8856 transports. Fixes bug 21027; bugfix on 0.3.0.1-alpha.
8858 o Major bugfixes (hidden service directory v3):
8859 - Stop crashing on a failed v3 hidden service descriptor lookup
8860 failure. Fixes bug 21471; bugfixes on 0.3.0.1-alpha.
8862 o Major bugfixes (parsing):
8863 - When parsing a malformed content-length field from an HTTP
8864 message, do not read off the end of the buffer. This bug was a
8865 potential remote denial-of-service attack against Tor clients and
8866 relays. A workaround was released in October 2016, to prevent this
8867 bug from crashing Tor. This is a fix for the underlying issue,
8868 which should no longer matter (if you applied the earlier patch).
8869 Fixes bug 20894; bugfix on 0.2.0.16-alpha. Bug found by fuzzing
8870 using AFL (http://lcamtuf.coredump.cx/afl/).
8871 - Fix an integer underflow bug when comparing malformed Tor
8872 versions. This bug could crash Tor when built with
8873 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
8874 0.2.9.8, which were built with -ftrapv by default. In other cases
8875 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
8876 on 0.0.8pre1. Found by OSS-Fuzz.
8878 o Minor feature (protocol versioning):
8879 - Add new protocol version for proposal 224. HSIntro now advertises
8880 version "3-4" and HSDir version "1-2". Fixes ticket 20656.
8882 o Minor features (directory authorities):
8883 - Directory authorities now reject descriptors that claim to be
8884 malformed versions of Tor. Helps prevent exploitation of
8886 - Reject version numbers with components that exceed INT32_MAX.
8887 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
8888 Fixes bug 21450; bugfix on 0.0.8pre1.
8889 - Directory authorities now reject relays running versions
8890 0.2.9.1-alpha through 0.2.9.4-alpha, because those relays
8891 suffer from bug 20499 and don't keep their consensus cache
8892 up-to-date. Resolves ticket 20509.
8894 o Minor features (geoip):
8895 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
8898 o Minor features (reliability, crash):
8899 - Try better to detect problems in buffers where they might grow (or
8900 think they have grown) over 2 GB in size. Diagnostic for
8903 o Minor features (testing):
8904 - During 'make test-network-all', if tor logs any warnings, ask
8905 chutney to output them. Requires a recent version of chutney with
8906 the 21572 patch. Implements 21570.
8908 o Minor bugfixes (certificate expiration time):
8909 - Avoid using link certificates that don't become valid till some
8910 time in the future. Fixes bug 21420; bugfix on 0.2.4.11-alpha
8912 o Minor bugfixes (code correctness):
8913 - Repair a couple of (unreachable or harmless) cases of the risky
8914 comparison-by-subtraction pattern that caused bug 21278.
8915 - Remove a redundant check for the UseEntryGuards option from the
8916 options_transition_affects_guards() function. Fixes bug 21492;
8917 bugfix on 0.3.0.1-alpha.
8919 o Minor bugfixes (directory mirrors):
8920 - Allow relays to use directory mirrors without a DirPort: these
8921 relays need to be contacted over their ORPorts using a begindir
8922 connection. Fixes one case of bug 20711; bugfix on 0.2.8.2-alpha.
8923 - Clarify the message logged when a remote relay is unexpectedly
8924 missing an ORPort or DirPort: users were confusing this with a
8925 local port. Fixes another case of bug 20711; bugfix
8928 o Minor bugfixes (guards):
8929 - Don't warn about a missing guard state on timeout-measurement
8930 circuits: they aren't supposed to be using guards. Fixes an
8931 instance of bug 21007; bugfix on 0.3.0.1-alpha.
8932 - Silence a BUG() warning when attempting to use a guard whose
8933 descriptor we don't know, and make this scenario less likely to
8934 happen. Fixes bug 21415; bugfix on 0.3.0.1-alpha.
8936 o Minor bugfixes (hidden service):
8937 - Pass correct buffer length when encoding legacy ESTABLISH_INTRO
8938 cells. Previously, we were using sizeof() on a pointer, instead of
8939 the real destination buffer. Fortunately, that value was only used
8940 to double-check that there was enough room--which was already
8941 enforced elsewhere. Fixes bug 21553; bugfix on 0.3.0.1-alpha.
8943 o Minor bugfixes (testing):
8944 - Fix Raspbian build issues related to missing socket errno in
8945 test_util.c. Fixes bug 21116; bugfix on 0.2.8.2. Patch
8947 - Rename "make fuzz" to "make test-fuzz-corpora", since it doesn't
8948 actually fuzz anything. Fixes bug 21447; bugfix on 0.3.0.3-alpha.
8949 - Use bash in src/test/test-network.sh. This ensures we reliably
8950 call chutney's newer tools/test-network.sh when available. Fixes
8951 bug 21562; bugfix on 0.2.9.1-alpha.
8954 - Small fixes to the fuzzing documentation. Closes ticket 21472.
8957 Changes in version 0.2.9.10 - 2017-03-01
8958 Tor 0.2.9.10 backports a security fix from later Tor release. It also
8959 includes fixes for some major issues affecting directory authorities,
8960 LibreSSL compatibility, and IPv6 correctness.
8962 The Tor 0.2.9.x release series is now marked as a long-term-support
8963 series. We intend to backport security fixes to 0.2.9.x until at
8964 least January of 2020.
8966 o Major bugfixes (directory authority, 0.3.0.3-alpha):
8967 - During voting, when marking a relay as a probable sybil, do not
8968 clear its BadExit flag: sybils can still be bad in other ways
8969 too. (We still clear the other flags.) Fixes bug 21108; bugfix
8972 o Major bugfixes (IPv6 Exits, backport from 0.3.0.3-alpha):
8973 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
8974 any IPv6 addresses. Instead, only reject a port over IPv6 if the
8975 exit policy rejects that port on more than an IPv6 /16 of
8976 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
8977 which rejected a relay's own IPv6 address by default. Fixes bug
8978 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
8980 o Major bugfixes (parsing, also in 0.3.0.4-rc):
8981 - Fix an integer underflow bug when comparing malformed Tor
8982 versions. This bug could crash Tor when built with
8983 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
8984 0.2.9.8, which were built with -ftrapv by default. In other cases
8985 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
8986 on 0.0.8pre1. Found by OSS-Fuzz.
8988 o Minor features (directory authorities, also in 0.3.0.4-rc):
8989 - Directory authorities now reject descriptors that claim to be
8990 malformed versions of Tor. Helps prevent exploitation of
8992 - Reject version numbers with components that exceed INT32_MAX.
8993 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
8994 Fixes bug 21450; bugfix on 0.0.8pre1.
8996 o Minor features (geoip):
8997 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
9000 o Minor features (portability, compilation, backport from 0.3.0.3-alpha):
9001 - Autoconf now checks to determine if OpenSSL structures are opaque,
9002 instead of explicitly checking for OpenSSL version numbers. Part
9004 - Support building with recent LibreSSL code that uses opaque
9005 structures. Closes ticket 21359.
9007 o Minor bugfixes (code correctness, also in 0.3.0.4-rc):
9008 - Repair a couple of (unreachable or harmless) cases of the risky
9009 comparison-by-subtraction pattern that caused bug 21278.
9011 o Minor bugfixes (tor-resolve, backport from 0.3.0.3-alpha):
9012 - The tor-resolve command line tool now rejects hostnames over 255
9013 characters in length. Previously, it would silently truncate them,
9014 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
9015 Patch by "junglefowl".
9018 Changes in version 0.3.0.3-alpha - 2017-02-03
9019 Tor 0.3.0.3-alpha fixes a few significant bugs introduced over the
9020 0.3.0.x development series, including some that could cause
9021 authorities to behave badly. There is also a fix for a longstanding
9022 bug that could prevent IPv6 exits from working. Tor 0.3.0.3-alpha also
9023 includes some smaller features and bugfixes.
9025 The Tor 0.3.0.x release series is now in patch-freeze: no additional
9026 features will be considered for inclusion in 0.3.0.x. We suspect that
9027 some bugs will probably remain, however, and we encourage people to
9030 o Major bugfixes (directory authority):
9031 - During voting, when marking a relay as a probable sybil, do not
9032 clear its BadExit flag: sybils can still be bad in other ways
9033 too. (We still clear the other flags.) Fixes bug 21108; bugfix
9035 - When deciding whether we have just found a router to be reachable,
9036 do not penalize it for not having performed an Ed25519 link
9037 handshake if it does not claim to support an Ed25519 handshake.
9038 Previously, we would treat such relays as non-running. Fixes bug
9039 21107; bugfix on 0.3.0.1-alpha.
9041 o Major bugfixes (entry guards):
9042 - Stop trying to build circuits through entry guards for which we
9043 have no descriptor. Also, stop crashing in the case that we *do*
9044 accidentally try to build a circuit in such a state. Fixes bug
9045 21242; bugfix on 0.3.0.1-alpha.
9047 o Major bugfixes (IPv6 Exits):
9048 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
9049 any IPv6 addresses. Instead, only reject a port over IPv6 if the
9050 exit policy rejects that port on more than an IPv6 /16 of
9051 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
9052 which rejected a relay's own IPv6 address by default. Fixes bug
9053 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
9055 o Minor feature (client):
9056 - Enable IPv6 traffic on the SocksPort by default. To disable this,
9057 a user will have to specify "NoIPv6Traffic". Closes ticket 21269.
9059 o Minor feature (fallback scripts):
9060 - Add a check_existing mode to updateFallbackDirs.py, which checks
9061 if fallbacks in the hard-coded list are working. Closes ticket
9062 20174. Patch by haxxpop.
9064 o Minor features (ciphersuite selection):
9065 - Clients now advertise a list of ciphersuites closer to the ones
9066 preferred by Firefox. Closes part of ticket 15426.
9067 - Allow relays to accept a wider range of ciphersuites, including
9068 chacha20-poly1305 and AES-CCM. Closes the other part of 15426.
9070 o Minor features (controller, configuration):
9071 - Each of the *Port options, such as SocksPort, ORPort, ControlPort,
9072 and so on, now comes with a __*Port variant that will not be saved
9073 to the torrc file by the controller's SAVECONF command. This
9074 change allows TorBrowser to set up a single-use domain socket for
9075 each time it launches Tor. Closes ticket 20956.
9076 - The GETCONF command can now query options that may only be
9077 meaningful in context-sensitive lists. This allows the controller
9078 to query the mixed SocksPort/__SocksPort style options introduced
9079 in feature 20956. Implements ticket 21300.
9081 o Minor features (portability, compilation):
9082 - Autoconf now checks to determine if OpenSSL structures are opaque,
9083 instead of explicitly checking for OpenSSL version numbers. Part
9085 - Support building with recent LibreSSL code that uses opaque
9086 structures. Closes ticket 21359.
9088 o Minor features (relay):
9089 - We now allow separation of exit and relay traffic to different
9090 source IP addresses, using the OutboundBindAddressExit and
9091 OutboundBindAddressOR options respectively. Closes ticket 17975.
9092 Written by Michael Sonntag.
9094 o Minor bugfix (logging):
9095 - Don't recommend the use of Tor2web in non-anonymous mode.
9096 Recommending Tor2web is a bad idea because the client loses all
9097 anonymity. Tor2web should only be used in specific cases by users
9098 who *know* and understand the issues. Fixes bug 21294; bugfix
9101 o Minor bugfixes (client):
9102 - Always recover from failures in extend_info_from_node(), in an
9103 attempt to prevent any recurrence of bug 21242. Fixes bug 21372;
9104 bugfix on 0.2.3.1-alpha.
9106 o Minor bugfixes (client, entry guards):
9107 - Fix a bug warning (with backtrace) when we fail a channel that
9108 circuits to fallback directories on it. Fixes bug 21128; bugfix
9110 - Fix a spurious bug warning (with backtrace) when removing an
9111 expired entry guard. Fixes bug 21129; bugfix on 0.3.0.1-alpha.
9112 - Fix a bug of the new guard algorithm where tor could stall for up
9113 to 10 minutes before retrying a guard after a long period of no
9114 network. Fixes bug 21052; bugfix on 0.3.0.1-alpha.
9115 - Do not try to build circuits until we have descriptors for our
9116 primary entry guards. Related to fix for bug 21242.
9118 o Minor bugfixes (configure, autoconf):
9119 - Rename the configure option --enable-expensive-hardening to
9120 --enable-fragile-hardening. Expensive hardening makes the tor
9121 daemon abort when some kinds of issues are detected. Thus, it
9122 makes tor more at risk of remote crashes but safer against RCE or
9123 heartbleed bug category. We now try to explain this issue in a
9124 message from the configure script. Fixes bug 21290; bugfix
9127 o Minor bugfixes (controller):
9128 - Restore the (deprecated) DROPGUARDS controller command. Fixes bug
9129 20824; bugfix on 0.3.0.1-alpha.
9131 o Minor bugfixes (hidden service):
9132 - Clean up the code for expiring intro points with no associated
9133 circuits. It was causing, rarely, a service with some expiring
9134 introduction points to not open enough additional introduction
9135 points. Fixes part of bug 21302; bugfix on 0.2.7.2-alpha.
9136 - Stop setting the torrc option HiddenServiceStatistics to "0" just
9137 because we're not a bridge or relay. Instead, we preserve whatever
9138 value the user set (or didn't set). Fixes bug 21150; bugfix
9140 - Resolve two possible underflows which could lead to creating and
9141 closing a lot of introduction point circuits in a non-stop loop.
9142 Fixes bug 21302; bugfix on 0.2.7.2-alpha.
9144 o Minor bugfixes (portability):
9145 - Use "OpenBSD" compiler macro instead of "OPENBSD" or "__OpenBSD__".
9146 It is supported by OpenBSD itself, and also by most OpenBSD
9147 variants (such as Bitrig). Fixes bug 20980; bugfix
9149 - When mapping a file of length greater than SIZE_MAX, do not
9150 silently truncate its contents. This issue could occur on 32 bit
9151 systems with large file support and files which are larger than 4
9152 GB. Fixes bug 21134; bugfix on 0.3.0.1-alpha.
9154 o Minor bugfixes (tor-resolve):
9155 - The tor-resolve command line tool now rejects hostnames over 255
9156 characters in length. Previously, it would silently truncate them,
9157 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
9158 Patch by "junglefowl".
9160 o Minor bugfixes (Windows services):
9161 - Be sure to initialize the monotonic time subsystem before using
9162 it, even when running as an NT service. Fixes bug 21356; bugfix
9166 Changes in version 0.3.0.2-alpha - 2017-01-23
9167 Tor 0.3.0.2-alpha fixes a denial-of-service bug where an attacker could
9168 cause relays and clients to crash, even if they were not built with
9169 the --enable-expensive-hardening option. This bug affects all 0.2.9.x
9170 versions, and also affects 0.3.0.1-alpha: all relays running an affected
9171 version should upgrade.
9173 Tor 0.3.0.2-alpha also improves how exit relays and clients handle DNS
9174 time-to-live values, makes directory authorities enforce the 1-to-1
9175 mapping of relay RSA identity keys to ED25519 identity keys, fixes a
9176 client-side onion service reachability bug, does better at selecting
9177 the set of fallback directories, and more.
9179 o Major bugfixes (security, also in 0.2.9.9):
9180 - Downgrade the "-ftrapv" option from "always on" to "only on when
9181 --enable-expensive-hardening is provided." This hardening option, like
9182 others, can turn survivable bugs into crashes--and having it on by
9183 default made a (relatively harmless) integer overflow bug into a
9184 denial-of-service bug. Fixes bug 21278 (TROVE-2017-001); bugfix on
9187 o Major features (security):
9188 - Change the algorithm used to decide DNS TTLs on client and server
9189 side, to better resist DNS-based correlation attacks like the
9190 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
9191 Feamster. Now relays only return one of two possible DNS TTL
9192 values, and clients are willing to believe DNS TTL values up to 3
9193 hours long. Closes ticket 19769.
9195 o Major features (directory authority, security):
9196 - The default for AuthDirPinKeys is now 1: directory authorities
9197 will reject relays where the RSA identity key matches a previously
9198 seen value, but the Ed25519 key has changed. Closes ticket 18319.
9200 o Major bugfixes (client, guard, crash):
9201 - In circuit_get_global_origin_list(), return the actual list of
9202 origin circuits. The previous version of this code returned the
9203 list of all the circuits, and could have caused strange bugs,
9204 including possible crashes. Fixes bug 21118; bugfix
9207 o Major bugfixes (client, onion service, also in 0.2.9.9):
9208 - Fix a client-side onion service reachability bug, where multiple
9209 socks requests to an onion service (or a single slow request)
9210 could cause us to mistakenly mark some of the service's
9211 introduction points as failed, and we cache that failure so
9212 eventually we run out and can't reach the service. Also resolves a
9213 mysterious "Remote server sent bogus reason code 65021" log
9214 warning. The bug was introduced in ticket 17218, where we tried to
9215 remember the circuit end reason as a uint16_t, which mangled
9216 negative values. Partially fixes bug 21056 and fixes bug 20307;
9217 bugfix on 0.2.8.1-alpha.
9219 o Major bugfixes (DNS):
9220 - Fix a bug that prevented exit nodes from caching DNS records for
9221 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
9223 o Minor features (controller):
9224 - Add "GETINFO sr/current" and "GETINFO sr/previous" keys, to expose
9225 shared-random values to the controller. Closes ticket 19925.
9227 o Minor features (entry guards):
9228 - Add UseEntryGuards to TEST_OPTIONS_DEFAULT_VALUES in order to not
9229 break regression tests.
9230 - Require UseEntryGuards when UseBridges is set, in order to make
9231 sure bridges aren't bypassed. Resolves ticket 20502.
9233 o Minor features (fallback directories):
9234 - Select 200 fallback directories for each release. Closes
9236 - Allow 3 fallback relays per operator, which is safe now that we
9237 are choosing 200 fallback relays. Closes ticket 20912.
9238 - Exclude relays affected by bug 20499 from the fallback list.
9239 Exclude relays from the fallback list if they are running versions
9240 known to be affected by bug 20499, or if in our tests they deliver
9241 a stale consensus (i.e. one that expired more than 24 hours ago).
9242 Closes ticket 20539.
9243 - Reduce the minimum fallback bandwidth to 1 MByte/s. Part of
9245 - Require fallback directories to have the same address and port for
9246 7 days (now that we have enough relays with this stability).
9247 Relays whose OnionOO stability timer is reset on restart by bug
9248 18050 should upgrade to Tor 0.2.8.7 or later, which has a fix for
9249 this issue. Closes ticket 20880; maintains short-term fix
9251 - Require fallbacks to have flags for 90% of the time (weighted
9252 decaying average), rather than 95%. This allows at least 73% of
9253 clients to bootstrap in the first 5 seconds without contacting an
9254 authority. Part of ticket 18828.
9255 - Annotate updateFallbackDirs.py with the bandwidth and consensus
9256 weight for each candidate fallback. Closes ticket 20878.
9257 - Make it easier to change the output sort order of fallbacks.
9258 Closes ticket 20822.
9259 - Display the relay fingerprint when downloading consensuses from
9260 fallbacks. Closes ticket 20908.
9262 o Minor features (geoip, also in 0.2.9.9):
9263 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
9266 o Minor features (next-gen onion service directories):
9267 - Remove the "EnableOnionServicesV3" consensus parameter that we
9268 introduced in 0.3.0.1-alpha: relays are now always willing to act
9269 as v3 onion service directories. Resolves ticket 19899.
9271 o Minor features (linting):
9272 - Enhance the changes file linter to warn on Tor versions that are
9273 prefixed with "tor-". Closes ticket 21096.
9275 o Minor features (logging):
9276 - In several places, describe unset ed25519 keys as "<unset>",
9277 rather than the scary "AAAAAAAA...AAA". Closes ticket 21037.
9279 o Minor bugfix (control protocol):
9280 - The reply to a "GETINFO config/names" request via the control
9281 protocol now spells the type "Dependent" correctly. This is a
9282 breaking change in the control protocol. (The field seems to be
9283 ignored by the most common known controllers.) Fixes bug 18146;
9284 bugfix on 0.1.1.4-alpha.
9286 o Minor bugfixes (bug resilience):
9287 - Fix an unreachable size_t overflow in base64_decode(). Fixes bug
9288 19222; bugfix on 0.2.0.9-alpha. Found by Guido Vranken; fixed by
9289 Hans Jerry Illikainen.
9291 o Minor bugfixes (build):
9292 - Replace obsolete Autoconf macros with their modern equivalent and
9293 prevent similar issues in the future. Fixes bug 20990; bugfix
9296 o Minor bugfixes (client, guards):
9297 - Fix bug where Tor would think that there are circuits waiting for
9298 better guards even though those circuits have been freed. Fixes
9299 bug 21142; bugfix on 0.3.0.1-alpha.
9301 o Minor bugfixes (config):
9302 - Don't assert on startup when trying to get the options list and
9303 LearnCircuitBuildTimeout is set to 0: we are currently parsing the
9304 options so of course they aren't ready yet. Fixes bug 21062;
9305 bugfix on 0.2.9.3-alpha.
9307 o Minor bugfixes (controller):
9308 - Make the GETINFO interface for inquiring about entry guards
9309 support the new guards backend. Fixes bug 20823; bugfix
9312 o Minor bugfixes (dead code):
9313 - Remove a redundant check for PidFile changes at runtime in
9314 options_transition_allowed(): this check is already performed
9315 regardless of whether the sandbox is active. Fixes bug 21123;
9316 bugfix on 0.2.5.4-alpha.
9318 o Minor bugfixes (documentation):
9319 - Update the tor manual page to document every option that can not
9320 be changed while tor is running. Fixes bug 21122.
9322 o Minor bugfixes (fallback directories):
9323 - Stop failing when a relay has no uptime data in
9324 updateFallbackDirs.py. Fixes bug 20945; bugfix on 0.2.8.1-alpha.
9325 - Avoid checking fallback candidates' DirPorts if they are down in
9326 OnionOO. When a relay operator has multiple relays, this
9327 prioritizes relays that are up over relays that are down. Fixes
9328 bug 20926; bugfix on 0.2.8.3-alpha.
9329 - Stop failing when OUTPUT_COMMENTS is True in updateFallbackDirs.py.
9330 Fixes bug 20877; bugfix on 0.2.8.3-alpha.
9332 o Minor bugfixes (guards, bootstrapping):
9333 - When connecting to a directory guard during bootstrap, do not mark
9334 the guard as successful until we receive a good-looking directory
9335 response from it. Fixes bug 20974; bugfix on 0.3.0.1-alpha.
9337 o Minor bugfixes (onion services):
9338 - Fix the config reload pruning of old vs new services so it
9339 actually works when both ephemeral and non-ephemeral services are
9340 configured. Fixes bug 21054; bugfix on 0.3.0.1-alpha.
9341 - Allow the number of introduction points to be as low as 0, rather
9342 than as low as 3. Fixes bug 21033; bugfix on 0.2.7.2-alpha.
9344 o Minor bugfixes (IPv6):
9345 - Make IPv6-using clients try harder to find an IPv6 directory
9346 server. Fixes bug 20999; bugfix on 0.2.8.2-alpha.
9347 - When IPv6 addresses have not been downloaded yet (microdesc
9348 consensus documents don't list relay IPv6 addresses), use hard-
9349 coded addresses for authorities, fallbacks, and configured
9350 bridges. Now IPv6-only clients can use microdescriptors. Fixes bug
9351 20996; bugfix on b167e82 from 19608 in 0.2.8.5-alpha.
9353 o Minor bugfixes (memory leaks):
9354 - Fix a memory leak when configuring hidden services. Fixes bug
9355 20987; bugfix on 0.3.0.1-alpha.
9357 o Minor bugfixes (portability, also in 0.2.9.9):
9358 - Avoid crashing when Tor is built using headers that contain
9359 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
9360 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
9362 - Fix Libevent detection on platforms without Libevent 1 headers
9363 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
9365 o Minor bugfixes (relay):
9366 - Honor DataDirectoryGroupReadable when tor is a relay. Previously,
9367 initializing the keys would reset the DataDirectory to 0700
9368 instead of 0750 even if DataDirectoryGroupReadable was set to 1.
9369 Fixes bug 19953; bugfix on 0.0.2pre16. Patch by "redfish".
9371 o Minor bugfixes (testing):
9372 - Remove undefined behavior from the backtrace generator by removing
9373 its signal handler. Fixes bug 21026; bugfix on 0.2.5.2-alpha.
9375 o Minor bugfixes (unit tests):
9376 - Allow the unit tests to pass even when DNS lookups of bogus
9377 addresses do not fail as expected. Fixes bug 20862 and 20863;
9378 bugfix on unit tests introduced in 0.2.8.1-alpha
9379 through 0.2.9.4-alpha.
9381 o Code simplification and refactoring:
9382 - Refactor code to manipulate global_origin_circuit_list into
9383 separate functions. Closes ticket 20921.
9385 o Documentation (formatting):
9386 - Clean up formatting of tor.1 man page and HTML doc, where <pre>
9387 blocks were incorrectly appearing. Closes ticket 20885.
9389 o Documentation (man page):
9390 - Clarify many options in tor.1 and add some min/max values for
9391 HiddenService options. Closes ticket 21058.
9394 Changes in version 0.2.9.9 - 2017-01-23
9395 Tor 0.2.9.9 fixes a denial-of-service bug where an attacker could
9396 cause relays and clients to crash, even if they were not built with
9397 the --enable-expensive-hardening option. This bug affects all 0.2.9.x
9398 versions, and also affects 0.3.0.1-alpha: all relays running an affected
9399 version should upgrade.
9401 This release also resolves a client-side onion service reachability
9402 bug, and resolves a pair of small portability issues.
9404 o Major bugfixes (security):
9405 - Downgrade the "-ftrapv" option from "always on" to "only on when
9406 --enable-expensive-hardening is provided." This hardening option,
9407 like others, can turn survivable bugs into crashes -- and having
9408 it on by default made a (relatively harmless) integer overflow bug
9409 into a denial-of-service bug. Fixes bug 21278 (TROVE-2017-001);
9410 bugfix on 0.2.9.1-alpha.
9412 o Major bugfixes (client, onion service):
9413 - Fix a client-side onion service reachability bug, where multiple
9414 socks requests to an onion service (or a single slow request)
9415 could cause us to mistakenly mark some of the service's
9416 introduction points as failed, and we cache that failure so
9417 eventually we run out and can't reach the service. Also resolves a
9418 mysterious "Remote server sent bogus reason code 65021" log
9419 warning. The bug was introduced in ticket 17218, where we tried to
9420 remember the circuit end reason as a uint16_t, which mangled
9421 negative values. Partially fixes bug 21056 and fixes bug 20307;
9422 bugfix on 0.2.8.1-alpha.
9424 o Minor features (geoip):
9425 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
9428 o Minor bugfixes (portability):
9429 - Avoid crashing when Tor is built using headers that contain
9430 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
9431 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
9433 - Fix Libevent detection on platforms without Libevent 1 headers
9434 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
9437 Changes in version 0.3.0.1-alpha - 2016-12-19
9438 Tor 0.3.0.1-alpha is the first alpha release in the 0.3.0 development
9439 series. It strengthens Tor's link and circuit handshakes by
9440 identifying relays by their Ed25519 keys, improves the algorithm that
9441 clients use to choose and maintain their list of guards, and includes
9442 additional backend support for the next-generation hidden service
9443 design. It also contains numerous other small features and
9444 improvements to security, correctness, and performance.
9446 Below are the changes since 0.2.9.8.
9448 o Major features (guard selection algorithm):
9449 - Tor's guard selection algorithm has been redesigned from the
9450 ground up, to better support unreliable networks and restrictive
9451 sets of entry nodes, and to better resist guard-capture attacks by
9452 hostile local networks. Implements proposal 271; closes
9455 o Major features (next-generation hidden services):
9456 - Relays can now handle v3 ESTABLISH_INTRO cells as specified by
9457 prop224 aka "Next Generation Hidden Services". Service and clients
9458 don't use this functionality yet. Closes ticket 19043. Based on
9459 initial code by Alec Heifetz.
9460 - Relays now support the HSDir version 3 protocol, so that they can
9461 can store and serve v3 descriptors. This is part of the next-
9462 generation onion service work detailed in proposal 224. Closes
9465 o Major features (protocol, ed25519 identity keys):
9466 - Relays now use Ed25519 to prove their Ed25519 identities and to
9467 one another, and to clients. This algorithm is faster and more
9468 secure than the RSA-based handshake we've been doing until now.
9469 Implements the second big part of proposal 220; Closes
9471 - Clients now support including Ed25519 identity keys in the EXTEND2
9472 cells they generate. By default, this is controlled by a consensus
9473 parameter, currently disabled. You can turn this feature on for
9474 testing by setting ExtendByEd25519ID in your configuration. This
9475 might make your traffic appear different than the traffic
9476 generated by other users, however. Implements part of ticket
9477 15056; part of proposal 220.
9478 - Relays now understand requests to extend to other relays by their
9479 Ed25519 identity keys. When an Ed25519 identity key is included in
9480 an EXTEND2 cell, the relay will only extend the circuit if the
9481 other relay can prove ownership of that identity. Implements part
9482 of ticket 15056; part of proposal 220.
9484 o Major bugfixes (scheduler):
9485 - Actually compare circuit policies in ewma_cmp_cmux(). This bug
9486 caused the channel scheduler to behave more or less randomly,
9487 rather than preferring channels with higher-priority circuits.
9488 Fixes bug 20459; bugfix on 0.2.6.2-alpha.
9490 o Minor features (controller):
9491 - When HSFETCH arguments cannot be parsed, say "Invalid argument"
9492 rather than "unrecognized." Closes ticket 20389; patch from
9495 o Minor features (diagnostic, directory client):
9496 - Warn when we find an unexpected inconsistency in directory
9497 download status objects. Prevents some negative consequences of
9500 o Minor features (directory authority):
9501 - Add a new authority-only AuthDirTestEd25519LinkKeys option (on by
9502 default) to control whether authorities should try to probe relays
9503 by their Ed25519 link keys. This option will go away in a few
9504 releases--unless we encounter major trouble in our ed25519 link
9505 protocol rollout, in which case it will serve as a safety option.
9507 o Minor features (directory cache):
9508 - Relays and bridges will now refuse to serve the consensus they
9509 have if they know it is too old for a client to use. Closes
9512 o Minor features (ed25519 link handshake):
9513 - Advertise support for the ed25519 link handshake using the
9514 subprotocol-versions mechanism, so that clients can tell which
9515 relays can identity themselves by Ed25519 ID. Closes ticket 20552.
9517 o Minor features (fingerprinting resistance, authentication):
9518 - Extend the length of RSA keys used for TLS link authentication to
9519 2048 bits. (These weren't used for forward secrecy; for forward
9520 secrecy, we used P256.) Closes ticket 13752.
9522 o Minor features (infrastructure):
9523 - Implement smartlist_add_strdup() function. Replaces the use of
9524 smartlist_add(sl, tor_strdup(str)). Closes ticket 20048.
9526 o Minor bugfixes (client):
9527 - When clients that use bridges start up with a cached consensus on
9528 disk, they were ignoring it and downloading a new one. Now they
9529 use the cached one. Fixes bug 20269; bugfix on 0.2.3.12-alpha.
9531 o Minor bugfixes (configuration):
9532 - Accept non-space whitespace characters after the severity level in
9533 the `Log` option. Fixes bug 19965; bugfix on 0.2.1.1-alpha.
9534 - Support "TByte" and "TBytes" units in options given in bytes.
9535 "TB", "terabyte(s)", "TBit(s)" and "terabit(s)" were already
9536 supported. Fixes bug 20622; bugfix on 0.2.0.14-alpha.
9538 o Minor bugfixes (consensus weight):
9539 - Add new consensus method that initializes bw weights to 1 instead
9540 of 0. This prevents a zero weight from making it all the way to
9541 the end (happens in small testing networks) and causing an error.
9542 Fixes bug 14881; bugfix on 0.2.2.17-alpha.
9544 o Minor bugfixes (descriptors):
9545 - Correctly recognise downloaded full descriptors as valid, even
9546 when using microdescriptors as circuits. This affects clients with
9547 FetchUselessDescriptors set, and may affect directory authorities.
9548 Fixes bug 20839; bugfix on 0.2.3.2-alpha.
9550 o Minor bugfixes (directory system):
9551 - Download all consensus flavors, descriptors, and authority
9552 certificates when FetchUselessDescriptors is set, regardless of
9553 whether tor is a directory cache or not. Fixes bug 20667; bugfix
9554 on all recent tor versions.
9555 - Bridges and relays now use microdescriptors (like clients do)
9556 rather than old-style router descriptors. Now bridges will blend
9557 in with clients in terms of the circuits they build. Fixes bug
9558 6769; bugfix on 0.2.3.2-alpha.
9560 o Minor bugfixes (ed25519 certificates):
9561 - Correctly interpret ed25519 certificates that would expire some
9562 time after 19 Jan 2038. Fixes bug 20027; bugfix on 0.2.7.2-alpha.
9564 o Minor bugfixes (hidden services):
9565 - Stop ignoring misconfigured hidden services. Instead, refuse to
9566 start tor until the misconfigurations have been corrected. Fixes
9567 bug 20559; bugfix on multiple commits in 0.2.7.1-alpha
9570 o Minor bugfixes (memory leak at exit):
9571 - Fix a small harmless memory leak at exit of the previously unused
9572 RSA->Ed identity cross-certificate. Fixes bug 17779; bugfix
9575 o Minor bugfixes (util):
9576 - When finishing writing a file to disk, if we were about to replace
9577 the file with the temporary file created before and we fail to
9578 replace it, remove the temporary file so it doesn't stay on disk.
9579 Fixes bug 20646; bugfix on 0.2.0.7-alpha. Patch by fk.
9581 o Minor bugfixes (Windows):
9582 - Check for getpagesize before using it to mmap files. This fixes
9583 compilation in some MinGW environments. Fixes bug 20530; bugfix on
9584 0.1.2.1-alpha. Reported by "ice".
9586 o Code simplification and refactoring:
9587 - Abolish all global guard context in entrynodes.c; replace with new
9588 guard_selection_t structure as preparation for proposal 271.
9589 Closes ticket 19858.
9590 - Introduce rend_service_is_ephemeral() that tells if given onion
9591 service is ephemeral. Replace unclear NULL-checkings for service
9592 directory with this function. Closes ticket 20526.
9593 - Extract magic numbers in circuituse.c into defined variables.
9594 - Refactor circuit_is_available_for_use to remove unnecessary check.
9595 - Refactor circuit_predict_and_launch_new for readability and
9596 testability. Closes ticket 18873.
9597 - Refactor large if statement in purpose_needs_anonymity to use
9598 switch statement instead. Closes part of ticket 20077.
9599 - Refactor the hashing API to return negative values for errors, as
9600 is done as throughout the codebase. Closes ticket 20717.
9601 - Remove data structures that were used to index or_connection
9602 objects by their RSA identity digests. These structures are fully
9603 redundant with the similar structures used in the
9604 channel abstraction.
9605 - Remove duplicate code in the channel_write_*cell() functions.
9606 Closes ticket 13827; patch from Pingl.
9607 - Remove redundant behavior of is_sensitive_dir_purpose, refactor to
9608 use only purpose_needs_anonymity. Closes part of ticket 20077.
9609 - The code to generate and parse EXTEND and EXTEND2 cells has been
9610 replaced with code automatically generated by the
9614 - Include the "TBits" unit in Tor's man page. Fixes part of bug
9615 20622; bugfix on 0.2.5.1-alpha.
9616 - Change '1' to 'weight_scale' in consensus bw weights calculation
9617 comments, as that is reality. Closes ticket 20273. Patch
9619 - Correct the value for AuthDirGuardBWGuarantee in the manpage, from
9620 250 KBytes to 2 MBytes. Fixes bug 20435; bugfix
9622 - Stop the man page from incorrectly stating that HiddenServiceDir
9623 must already exist. Fixes 20486.
9624 - Clarify that when ClientRejectInternalAddresses is enabled (which
9625 is the default), multicast DNS hostnames for machines on the local
9626 network (of the form *.local) are also rejected. Closes
9630 - The AuthDirMaxServersPerAuthAddr option no longer exists: The same
9631 limit for relays running on a single IP applies to authority IP
9632 addresses as well as to non-authority IP addresses. Closes
9634 - The UseDirectoryGuards torrc option no longer exists: all users
9635 that use entry guards will also use directory guards. Related to
9636 proposal 271; implements part of ticket 20831.
9639 - New unit tests for tor_htonll(). Closes ticket 19563. Patch
9640 from "overcaffeinated".
9641 - Perform the coding style checks when running the tests and fail
9642 when coding style violations are found. Closes ticket 5500.
9643 - Add tests for networkstatus_compute_bw_weights_v10.
9644 - Add unit tests circuit_predict_and_launch_new.
9645 - Extract dummy_origin_circuit_new so it can be used by other
9649 Changes in version 0.2.8.12 - 2016-12-19
9650 Tor 0.2.8.12 backports a fix for a medium-severity issue (bug 21018
9651 below) where Tor clients could crash when attempting to visit a
9652 hostile hidden service. Clients are recommended to upgrade as packages
9653 become available for their systems.
9655 It also includes an updated list of fallback directories, backported
9658 Now that the Tor 0.2.9 series is stable, only major bugfixes will be
9659 backported to 0.2.8 in the future.
9661 o Major bugfixes (parsing, security, backported from 0.2.9.8):
9662 - Fix a bug in parsing that could cause clients to read a single
9663 byte past the end of an allocated region. This bug could be used
9664 to cause hardened clients (built with --enable-expensive-hardening)
9665 to crash if they tried to visit a hostile hidden service. Non-
9666 hardened clients are only affected depending on the details of
9667 their platform's memory allocator. Fixes bug 21018; bugfix on
9668 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
9669 2016-12-002 and as CVE-2016-1254.
9671 o Minor features (fallback directory list, backported from 0.2.9.8):
9672 - Replace the 81 remaining fallbacks of the 100 originally
9673 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
9674 fallbacks (123 new, 54 existing, 27 removed) generated in December
9675 2016. Resolves ticket 20170.
9677 o Minor features (geoip, backported from 0.2.9.7-rc):
9678 - Update geoip and geoip6 to the December 7 2016 Maxmind GeoLite2
9682 Changes in version 0.2.9.8 - 2016-12-19
9683 Tor 0.2.9.8 is the first stable release of the Tor 0.2.9 series.
9685 The Tor 0.2.9 series makes mandatory a number of security features
9686 that were formerly optional. It includes support for a new shared-
9687 randomness protocol that will form the basis for next generation
9688 hidden services, includes a single-hop hidden service mode for
9689 optimizing .onion services that don't actually want to be hidden,
9690 tries harder not to overload the directory authorities with excessive
9691 downloads, and supports a better protocol versioning scheme for
9692 improved compatibility with other implementations of the Tor protocol.
9694 And of course, there are numerous other bugfixes and improvements.
9696 This release also includes a fix for a medium-severity issue (bug
9697 21018 below) where Tor clients could crash when attempting to visit a
9698 hostile hidden service. Clients are recommended to upgrade as packages
9699 become available for their systems.
9701 Below are the changes since 0.2.9.7-rc. For a list of all changes
9702 since 0.2.8, see the ReleaseNotes file.
9704 o Major bugfixes (parsing, security):
9705 - Fix a bug in parsing that could cause clients to read a single
9706 byte past the end of an allocated region. This bug could be used
9707 to cause hardened clients (built with --enable-expensive-hardening)
9708 to crash if they tried to visit a hostile hidden service. Non-
9709 hardened clients are only affected depending on the details of
9710 their platform's memory allocator. Fixes bug 21018; bugfix on
9711 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
9712 2016-12-002 and as CVE-2016-1254.
9714 o Minor features (fallback directory list):
9715 - Replace the 81 remaining fallbacks of the 100 originally
9716 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
9717 fallbacks (123 new, 54 existing, 27 removed) generated in December
9718 2016. Resolves ticket 20170.
9721 Changes in version 0.2.9.7-rc - 2016-12-12
9722 Tor 0.2.9.7-rc fixes a few small bugs remaining in Tor 0.2.9.6-rc,
9723 including a few that had prevented tests from passing on
9726 o Minor features (geoip):
9727 - Update geoip and geoip6 to the December 7 2016 Maxmind GeoLite2
9730 o Minor bugfix (build):
9731 - The current Git revision when building from a local repository is
9732 now detected correctly when using git worktrees. Fixes bug 20492;
9733 bugfix on 0.2.3.9-alpha.
9735 o Minor bugfixes (directory authority):
9736 - When computing old Tor protocol line version in protover, we were
9737 looking at 0.2.7.5 twice instead of a specific case for
9738 0.2.9.1-alpha. Fixes bug 20810; bugfix on 0.2.9.4-alpha.
9740 o Minor bugfixes (download scheduling):
9741 - Resolve a "bug" warning when considering a download schedule whose
9742 delay had approached INT_MAX. Fixes 20875; bugfix on 0.2.9.5-alpha.
9744 o Minor bugfixes (logging):
9745 - Downgrade a harmless log message about the
9746 pending_entry_connections list from "warn" to "info". Mitigates
9749 o Minor bugfixes (memory leak):
9750 - Fix a small memory leak when receiving AF_UNIX connections on a
9751 SocksPort. Fixes bug 20716; bugfix on 0.2.6.3-alpha.
9752 - When moving a signed descriptor object from a source to an
9753 existing destination, free the allocated memory inside that
9754 destination object. Fixes bug 20715; bugfix on 0.2.8.3-alpha.
9756 o Minor bugfixes (memory leak, use-after-free, linux seccomp2 sandbox):
9757 - Fix a memory leak and use-after-free error when removing entries
9758 from the sandbox's getaddrinfo() cache. Fixes bug 20710; bugfix on
9759 0.2.5.5-alpha. Patch from "cypherpunks".
9761 o Minor bugfixes (portability):
9762 - Use the correct spelling of MAC_OS_X_VERSION_10_12 on configure.ac
9763 Fixes bug 20935; bugfix on 0.2.9.6-rc.
9765 o Minor bugfixes (unit tests):
9766 - Stop expecting NetBSD unit tests to report success for ipfw. Part
9767 of a fix for bug 19960; bugfix on 0.2.9.5-alpha.
9768 - Fix tolerances in unit tests for monotonic time comparisons
9769 between nanoseconds and microseconds. Previously, we accepted a 10
9770 us difference only, which is not realistic on every platform's
9771 clock_gettime(). Fixes bug 19974; bugfix on 0.2.9.1-alpha.
9772 - Remove a double-free in the single onion service unit test. Stop
9773 ignoring a return value. Make future changes less error-prone.
9774 Fixes bug 20864; bugfix on 0.2.9.6-rc.
9777 Changes in version 0.2.8.11 - 2016-12-08
9778 Tor 0.2.8.11 backports fixes for additional portability issues that
9779 could prevent Tor from building correctly on OSX Sierra, or with
9780 OpenSSL 1.1. Affected users should upgrade; others can safely stay
9783 o Minor bugfixes (portability):
9784 - Avoid compilation errors when building on OSX Sierra. Sierra began
9785 to support the getentropy() and clock_gettime() APIs, but created
9786 a few problems in doing so. Tor 0.2.9 has a more thorough set of
9787 workarounds; in 0.2.8, we are just using the /dev/urandom and mach
9788 monotonic time interfaces. Fixes bug 20865. Bugfix
9791 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
9792 - Fix compilation with OpenSSL 1.1 and less commonly-used CPU
9793 architectures. Closes ticket 20588.
9796 Changes in version 0.2.8.10 - 2016-12-02
9797 Tor 0.2.8.10 backports a fix for a bug that would sometimes make clients
9798 unusable after they left standby mode. It also backports fixes for
9799 a few portability issues and a small but problematic memory leak.
9801 o Major bugfixes (client reliability, backport from 0.2.9.5-alpha):
9802 - When Tor leaves standby because of a new application request, open
9803 circuits as needed to serve that request. Previously, we would
9804 potentially wait a very long time. Fixes part of bug 19969; bugfix
9807 o Major bugfixes (client performance, backport from 0.2.9.5-alpha):
9808 - Clients now respond to new application stream requests immediately
9809 when they arrive, rather than waiting up to one second before
9810 starting to handle them. Fixes part of bug 19969; bugfix
9813 o Minor bugfixes (portability, backport from 0.2.9.6-rc):
9814 - Work around a bug in the OSX 10.12 SDK that would prevent us from
9815 successfully targeting earlier versions of OSX. Resolves
9818 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
9819 - Fix implicit conversion warnings under OpenSSL 1.1. Fixes bug
9820 20551; bugfix on 0.2.1.1-alpha.
9822 o Minor bugfixes (relay, backport from 0.2.9.5-alpha):
9823 - Work around a memory leak in OpenSSL 1.1 when encoding public
9824 keys. Fixes bug 20553; bugfix on 0.0.2pre8.
9826 o Minor features (geoip):
9827 - Update geoip and geoip6 to the November 3 2016 Maxmind GeoLite2
9830 Changes in version 0.2.9.6-rc - 2016-12-02
9831 Tor 0.2.9.6-rc fixes a few remaining bugs found in the previous alpha
9832 version. We hope that it will be ready to become stable soon, and we
9833 encourage everyone to test this release. If no showstopper bugs are
9834 found here, the next 0.2.9 release will be stable.
9836 o Major bugfixes (relay, resolver, logging):
9837 - For relays that don't know their own address, avoid attempting a
9838 local hostname resolve for each descriptor we download. This
9839 will cut down on the number of "Success: chose address 'x.x.x.x'"
9840 log lines, and also avoid confusing clock jumps if the resolver
9841 is slow. Fixes bugs 20423 and 20610; bugfix on 0.2.8.1-alpha.
9843 o Minor bugfixes (client, fascistfirewall):
9844 - Avoid spurious warnings when ReachableAddresses or FascistFirewall
9845 is set. Fixes bug 20306; bugfix on 0.2.8.2-alpha.
9847 o Minor bugfixes (hidden services):
9848 - Stop ignoring the anonymity status of saved keys for hidden
9849 services and single onion services when first starting tor.
9850 Instead, refuse to start tor if any hidden service key has been
9851 used in a different hidden service anonymity mode. Fixes bug
9852 20638; bugfix on 17178 in 0.2.9.3-alpha; reported by ahf.
9854 o Minor bugfixes (portability):
9855 - Work around a bug in the OSX 10.12 SDK that would prevent us from
9856 successfully targeting earlier versions of OSX. Resolves
9858 - Run correctly when built on Windows build environments that
9859 require _vcsprintf(). Fixes bug 20560; bugfix on 0.2.2.11-alpha.
9861 o Minor bugfixes (single onion services, Tor2web):
9862 - Stop complaining about long-term one-hop circuits deliberately
9863 created by single onion services and Tor2web. These log messages
9864 are intended to diagnose issue 8387, which relates to circuits
9865 hanging around forever for no reason. Fixes bug 20613; bugfix on
9866 0.2.9.1-alpha. Reported by "pastly".
9868 o Minor bugfixes (unit tests):
9869 - Stop spurious failures in the local interface address discovery
9870 unit tests. Fixes bug 20634; bugfix on 0.2.8.1-alpha; patch by
9874 - Correct the minimum bandwidth value in torrc.sample, and queue a
9875 corresponding change for torrc.minimal. Closes ticket 20085.
9878 Changes in version 0.2.9.5-alpha - 2016-11-08
9879 Tor 0.2.9.5-alpha fixes numerous bugs discovered in the previous alpha
9880 version. We believe one or two probably remain, and we encourage
9881 everyone to test this release.
9883 o Major bugfixes (client performance):
9884 - Clients now respond to new application stream requests immediately
9885 when they arrive, rather than waiting up to one second before
9886 starting to handle them. Fixes part of bug 19969; bugfix
9889 o Major bugfixes (client reliability):
9890 - When Tor leaves standby because of a new application request, open
9891 circuits as needed to serve that request. Previously, we would
9892 potentially wait a very long time. Fixes part of bug 19969; bugfix
9895 o Major bugfixes (download scheduling):
9896 - When using an exponential backoff schedule, do not give up on
9897 downloading just because we have failed a bunch of times. Since
9898 each delay is longer than the last, retrying indefinitely won't
9899 hurt. Fixes bug 20536; bugfix on 0.2.9.1-alpha.
9900 - If a consensus expires while we are waiting for certificates to
9901 download, stop waiting for certificates.
9902 - If we stop waiting for certificates less than a minute after we
9903 started downloading them, do not consider the certificate download
9904 failure a separate failure. Fixes bug 20533; bugfix
9906 - Remove the maximum delay on exponential-backoff scheduling. Since
9907 we now allow an infinite number of failures (see ticket 20536), we
9908 must now allow the time to grow longer on each failure. Fixes part
9909 of bug 20534; bugfix on 0.2.9.1-alpha.
9910 - Make our initial download delays closer to those from 0.2.8. Fixes
9911 another part of bug 20534; bugfix on 0.2.9.1-alpha.
9912 - When determining when to download a directory object, handle times
9913 after 2038 if the operating system supports them. (Someday this
9914 will be important!) Fixes bug 20587; bugfix on 0.2.8.1-alpha.
9915 - When using exponential backoff in test networks, use a lower
9916 exponent, so the delays do not vary as much. This helps test
9917 networks bootstrap consistently. Fixes bug 20597; bugfix on 20499.
9919 o Minor features (geoip):
9920 - Update geoip and geoip6 to the November 3 2016 Maxmind GeoLite2
9923 o Minor bugfixes (client directory scheduling):
9924 - Treat "relay too busy to answer request" as a failed request and a
9925 reason to back off on our retry frequency. This is safe now that
9926 exponential backoffs retry indefinitely, and avoids a bug where we
9927 would reset our download schedule erroneously. Fixes bug 20593;
9928 bugfix on 0.2.9.1-alpha.
9930 o Minor bugfixes (client, logging):
9931 - Remove a BUG warning in circuit_pick_extend_handshake(). Instead,
9932 assume all nodes support EXTEND2. Use ntor whenever a key is
9933 available. Fixes bug 20472; bugfix on 0.2.9.3-alpha.
9934 - On DNSPort, stop logging a BUG warning on a failed hostname
9935 lookup. Fixes bug 19869; bugfix on 0.2.9.1-alpha.
9937 o Minor bugfixes (hidden services):
9938 - When configuring hidden services, check every hidden service
9939 directory's permissions. Previously, we only checked the last
9940 hidden service. Fixes bug 20529; bugfix the work to fix 13942
9943 o Minor bugfixes (portability):
9944 - Fix compilation with OpenSSL 1.1 and less commonly-used CPU
9945 architectures. Closes ticket 20588.
9946 - Use ECDHE ciphers instead of ECDH in tortls tests. LibreSSL has
9947 removed the ECDH ciphers which caused the tests to fail on
9948 platforms which use it. Fixes bug 20460; bugfix on 0.2.8.1-alpha.
9949 - Fix implicit conversion warnings under OpenSSL 1.1. Fixes bug
9950 20551; bugfix on 0.2.1.1-alpha.
9952 o Minor bugfixes (relay bootstrap):
9953 - Ensure relays don't make multiple connections during bootstrap.
9954 Fixes bug 20591; bugfix on 0.2.8.1-alpha.
9956 o Minor bugfixes (relay):
9957 - Work around a memory leak in OpenSSL 1.1 when encoding public
9958 keys. Fixes bug 20553; bugfix on 0.0.2pre8.
9959 - Avoid a small memory leak when informing worker threads about
9960 rotated onion keys. Fixes bug 20401; bugfix on 0.2.6.3-alpha.
9961 - Do not try to parallelize workers more than 16x without the user
9962 explicitly configuring us to do so, even if we do detect more than
9963 16 CPU cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
9965 o Minor bugfixes (single onion services):
9966 - Start correctly when creating a single onion service in a
9967 directory that did not previously exist. Fixes bug 20484; bugfix
9970 o Minor bugfixes (testing):
9971 - Avoid a unit test failure on systems with over 16 detectable CPU
9972 cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
9975 - Clarify that setting HiddenServiceNonAnonymousMode requires you to
9976 also set "SOCKSPort 0". Fixes bug 20487; bugfix on 0.2.9.3-alpha.
9977 - Module-level documentation for several more modules. Closes
9978 tickets 19287 and 19290.
9981 Changes in version 0.2.8.9 - 2016-10-17
9982 Tor 0.2.8.9 backports a fix for a security hole in previous versions
9983 of Tor that would allow a remote attacker to crash a Tor client,
9984 hidden service, relay, or authority. All Tor users should upgrade to
9985 this version, or to 0.2.9.4-alpha. Patches will be released for older
9988 o Major features (security fixes, also in 0.2.9.4-alpha):
9989 - Prevent a class of security bugs caused by treating the contents
9990 of a buffer chunk as if they were a NUL-terminated string. At
9991 least one such bug seems to be present in all currently used
9992 versions of Tor, and would allow an attacker to remotely crash
9993 most Tor instances, especially those compiled with extra compiler
9994 hardening. With this defense in place, such bugs can't crash Tor,
9995 though we should still fix them as they occur. Closes ticket
9996 20384 (TROVE-2016-10-001).
9998 o Minor features (geoip):
9999 - Update geoip and geoip6 to the October 4 2016 Maxmind GeoLite2
10003 Changes in version 0.2.9.4-alpha - 2016-10-17
10004 Tor 0.2.9.4-alpha fixes a security hole in previous versions of Tor
10005 that would allow a remote attacker to crash a Tor client, hidden
10006 service, relay, or authority. All Tor users should upgrade to this
10007 version, or to 0.2.8.9. Patches will be released for older versions
10010 Tor 0.2.9.4-alpha also adds numerous small features and fix-ups to
10011 previous versions of Tor, including the implementation of a feature to
10012 future- proof the Tor ecosystem against protocol changes, some bug
10013 fixes necessary for Tor Browser to use unix domain sockets correctly,
10014 and several portability improvements. We anticipate that this will be
10015 the last alpha in the Tor 0.2.9 series, and that the next release will
10016 be a release candidate.
10018 o Major features (security fixes):
10019 - Prevent a class of security bugs caused by treating the contents
10020 of a buffer chunk as if they were a NUL-terminated string. At
10021 least one such bug seems to be present in all currently used
10022 versions of Tor, and would allow an attacker to remotely crash
10023 most Tor instances, especially those compiled with extra compiler
10024 hardening. With this defense in place, such bugs can't crash Tor,
10025 though we should still fix them as they occur. Closes ticket
10026 20384 (TROVE-2016-10-001).
10028 o Major features (subprotocol versions):
10029 - Tor directory authorities now vote on a set of recommended
10030 subprotocol versions, and on a set of required subprotocol
10031 versions. Clients and relays that lack support for a _required_
10032 subprotocol version will not start; those that lack support for a
10033 _recommended_ subprotocol version will warn the user to upgrade.
10034 Closes ticket 19958; implements part of proposal 264.
10035 - Tor now uses "subprotocol versions" to indicate compatibility.
10036 Previously, versions of Tor looked at the declared Tor version of
10037 a relay to tell whether they could use a given feature. Now, they
10038 should be able to rely on its declared subprotocol versions. This
10039 change allows compatible implementations of the Tor protocol(s) to
10040 exist without pretending to be 100% bug-compatible with particular
10041 releases of Tor itself. Closes ticket 19958; implements part of
10044 o Minor feature (fallback directories):
10045 - Remove broken fallbacks from the hard-coded fallback directory
10046 list. Closes ticket 20190; patch by teor.
10048 o Minor features (client, directory):
10049 - Since authorities now omit all routers that lack the Running and
10050 Valid flags, we assume that any relay listed in the consensus must
10051 have those flags. Closes ticket 20001; implements part of
10054 o Minor features (compilation, portability):
10055 - Compile correctly on MacOS 10.12 (aka "Sierra"). Closes
10058 o Minor features (development tools, etags):
10059 - Teach the "make tags" Makefile target how to correctly find
10060 "MOCK_IMPL" function definitions. Patch from nherring; closes
10063 o Minor features (geoip):
10064 - Update geoip and geoip6 to the October 4 2016 Maxmind GeoLite2
10067 o Minor features (unix domain sockets):
10068 - When configuring a unix domain socket for a SocksPort,
10069 ControlPort, or Hidden service, you can now wrap the address in
10070 quotes, using C-style escapes inside the quotes. This allows unix
10071 domain socket paths to contain spaces.
10073 o Minor features (virtual addresses):
10074 - Increase the maximum number of bits for the IPv6 virtual network
10075 prefix from 16 to 104. In this way, the condition for address
10076 allocation is less restrictive. Closes ticket 20151; feature
10079 o Minor bugfixes (address discovery):
10080 - Stop reordering IP addresses returned by the OS. This makes it
10081 more likely that Tor will guess the same relay IP address every
10082 time. Fixes issue 20163; bugfix on 0.2.7.1-alpha, ticket 17027.
10083 Reported by René Mayrhofer, patch by "cypherpunks".
10085 o Minor bugfixes (client, unix domain sockets):
10086 - Disable IsolateClientAddr when using AF_UNIX backed SocksPorts as
10087 the client address is meaningless. Fixes bug 20261; bugfix
10090 o Minor bugfixes (compilation, OpenBSD):
10091 - Detect Libevent2 functions correctly on systems that provide
10092 libevent2, but where libevent1 is linked with -levent. Fixes bug
10093 19904; bugfix on 0.2.2.24-alpha. Patch from Rubiate.
10095 o Minor bugfixes (configuration):
10096 - When parsing quoted configuration values from the torrc file,
10097 handle windows line endings correctly. Fixes bug 19167; bugfix on
10098 0.2.0.16-alpha. Patch from "Pingl".
10100 o Minor bugfixes (getpass):
10101 - Defensively fix a non-triggerable heap corruption at do_getpass()
10102 to protect ourselves from mistakes in the future. Fixes bug
10103 19223; bugfix on 0.2.7.3-rc. Bug found by Guido Vranken, patch
10106 o Minor bugfixes (hidden service):
10107 - Allow hidden services to run on IPv6 addresses even when the
10108 IPv6Exit option is not set. Fixes bug 18357; bugfix
10112 - Add module-level internal documentation for 36 C files that
10113 previously didn't have a high-level overview. Closes ticket #20385.
10115 o Required libraries:
10116 - When building with OpenSSL, Tor now requires version 1.0.1 or
10117 later. OpenSSL 1.0.0 and earlier are no longer supported by the
10118 OpenSSL team, and should not be used. Closes ticket 20303.
10121 Changes in version 0.2.9.3-alpha - 2016-09-23
10122 Tor 0.2.9.3-alpha adds improved support for entities that want to make
10123 high-performance services available through the Tor .onion mechanism
10124 without themselves receiving anonymity as they host those services. It
10125 also tries harder to ensure that all steps on a circuit are using the
10126 strongest crypto possible, strengthens some TLS properties, and
10127 resolves several bugs -- including a pair of crash bugs from the 0.2.8
10128 series. Anybody running an earlier version of 0.2.9.x should upgrade.
10130 o Major bugfixes (crash, also in 0.2.8.8):
10131 - Fix a complicated crash bug that could affect Tor clients
10132 configured to use bridges when replacing a networkstatus consensus
10133 in which one of their bridges was mentioned. OpenBSD users saw
10134 more crashes here, but all platforms were potentially affected.
10135 Fixes bug 20103; bugfix on 0.2.8.2-alpha.
10137 o Major bugfixes (relay, OOM handler, also in 0.2.8.8):
10138 - Fix a timing-dependent assertion failure that could occur when we
10139 tried to flush from a circuit after having freed its cells because
10140 of an out-of-memory condition. Fixes bug 20203; bugfix on
10141 0.2.8.1-alpha. Thanks to "cypherpunks" for help diagnosing
10144 o Major features (circuit building, security):
10145 - Authorities, relays and clients now require ntor keys in all
10146 descriptors, for all hops (except for rare hidden service protocol
10147 cases), for all circuits, and for all other roles. Part of
10149 - Tor authorities, relays, and clients only use ntor, except for
10150 rare cases in the hidden service protocol. Part of ticket 19163.
10152 o Major features (single-hop "hidden" services):
10153 - Add experimental HiddenServiceSingleHopMode and
10154 HiddenServiceNonAnonymousMode options. When both are set to 1,
10155 every hidden service on a Tor instance becomes a non-anonymous
10156 Single Onion Service. Single Onions make one-hop (direct)
10157 connections to their introduction and renzedvous points. One-hop
10158 circuits make Single Onion servers easily locatable, but clients
10159 remain location-anonymous. This is compatible with the existing
10160 hidden service implementation, and works on the current tor
10161 network without any changes to older relays or clients. Implements
10162 proposal 260, completes ticket 17178. Patch by teor and asn.
10164 o Major features (resource management):
10165 - Tor can now notice it is about to run out of sockets, and
10166 preemptively close connections of lower priority. (This feature is
10167 off by default for now, since the current prioritizing method is
10168 yet not mature enough. You can enable it by setting
10169 "DisableOOSCheck 0", but watch out: it might close some sockets
10170 you would rather have it keep.) Closes ticket 18640.
10172 o Major bugfixes (circuit building):
10173 - Hidden service client-to-intro-point and service-to-rendezvous-
10174 point circuits use the TAP key supplied by the protocol, to avoid
10175 epistemic attacks. Fixes bug 19163; bugfix on 0.2.4.18-rc.
10177 o Major bugfixes (compilation, OpenBSD):
10178 - Fix a Libevent-detection bug in our autoconf script that would
10179 prevent Tor from linking successfully on OpenBSD. Patch from
10180 rubiate. Fixes bug 19902; bugfix on 0.2.9.1-alpha.
10182 o Major bugfixes (hidden services):
10183 - Clients now require hidden services to include the TAP keys for
10184 their intro points in the hidden service descriptor. This prevents
10185 an inadvertent upgrade to ntor, which a malicious hidden service
10186 could use to distinguish clients by consensus version. Fixes bug
10187 20012; bugfix on 0.2.4.8-alpha. Patch by teor.
10189 o Minor features (security, TLS):
10190 - Servers no longer support clients that without AES ciphersuites.
10191 (3DES is no longer considered an acceptable cipher.) We believe
10192 that no such Tor clients currently exist, since Tor has required
10193 OpenSSL 0.9.7 or later since 2009. Closes ticket 19998.
10195 o Minor feature (fallback directories):
10196 - Remove 8 fallbacks that are no longer suitable, leaving 81 of the
10197 100 fallbacks originally introduced in Tor 0.2.8.2-alpha in March
10198 2016. Closes ticket 20190; patch by teor.
10200 o Minor features (geoip, also in 0.2.8.8):
10201 - Update geoip and geoip6 to the September 6 2016 Maxmind GeoLite2
10204 o Minor feature (port flags):
10205 - Add new flags to the *Port options to finer control over which
10206 requests are allowed. The flags are NoDNSRequest, NoOnionTraffic,
10207 and the synthetic flag OnionTrafficOnly, which is equivalent to
10208 NoDNSRequest, NoIPv4Traffic, and NoIPv6Traffic. Closes enhancement
10209 18693; patch by "teor".
10211 o Minor features (directory authority):
10212 - After voting, if the authorities decide that a relay is not
10213 "Valid", they no longer include it in the consensus at all. Closes
10214 ticket 20002; implements part of proposal 272.
10216 o Minor features (testing):
10217 - Disable memory protections on OpenBSD when performing our unit
10218 tests for memwipe(). The test deliberately invokes undefined
10219 behavior, and the OpenBSD protections interfere with this. Patch
10220 from "rubiate". Closes ticket 20066.
10222 o Minor features (testing, ipv6):
10223 - Add the single-onion and single-onion-ipv6 chutney targets to
10224 "make test-network-all". This requires a recent chutney version
10225 with the single onion network flavours (git c72a652 or later).
10226 Closes ticket 20072; patch by teor.
10227 - Add the hs-ipv6 chutney target to make test-network-all's IPv6
10228 tests. Remove bridges+hs, as it's somewhat redundant. This
10229 requires a recent chutney version that supports IPv6 clients,
10230 relays, and authorities. Closes ticket 20069; patch by teor.
10232 o Minor features (Tor2web):
10233 - Make Tor2web clients respect ReachableAddresses. This feature was
10234 inadvertently enabled in 0.2.8.6, then removed by bugfix 19973 on
10235 0.2.8.7. Implements feature 20034. Patch by teor.
10237 o Minor features (unit tests):
10238 - We've done significant work to make the unit tests run faster.
10239 - Our link-handshake unit tests now check that when invalid
10240 handshakes fail, they fail with the error messages we expected.
10241 - Our unit testing code that captures log messages no longer
10242 prevents them from being written out if the user asked for them
10243 (by passing --debug or --info or or --notice --warn to the "test"
10244 binary). This change prevents us from missing unexpected log
10245 messages simply because we were looking for others. Related to
10247 - The unit tests now log all warning messages with the "BUG" flag.
10248 Previously, they only logged errors by default. This change will
10249 help us make our testing code more correct, and make sure that we
10250 only hit this code when we mean to. In the meantime, however,
10251 there will be more warnings in the unit test logs than before.
10252 This is preparatory work for ticket 19999.
10253 - The unit tests now treat any failure of a "tor_assert_nonfatal()"
10254 assertion as a test failure.
10256 o Minor bug fixes (circuits):
10257 - Use the CircuitBuildTimeout option whenever
10258 LearnCircuitBuildTimeout is disabled. Previously, we would respect
10259 the option when a user disabled it, but not when it was disabled
10260 because some other option was set. Fixes bug 20073; bugfix on
10261 0.2.4.12-alpha. Patch by teor.
10263 o Minor bugfixes (allocation):
10264 - Change how we allocate memory for large chunks on buffers, to
10265 avoid a (currently impossible) integer overflow, and to waste less
10266 space when allocating unusually large chunks. Fixes bug 20081;
10267 bugfix on 0.2.0.16-alpha. Issue identified by Guido Vranken.
10268 - Always include orconfig.h before including any other C headers.
10269 Sometimes, it includes macros that affect the behavior of the
10270 standard headers. Fixes bug 19767; bugfix on 0.2.9.1-alpha (the
10271 first version to use AC_USE_SYSTEM_EXTENSIONS).
10272 - Fix a syntax error in the IF_BUG_ONCE__() macro in non-GCC-
10273 compatible compilers. Fixes bug 20141; bugfix on 0.2.9.1-alpha.
10274 Patch from Gisle Vanem.
10275 - Stop trying to build with Clang 4.0's -Wthread-safety warnings.
10276 They apparently require a set of annotations that we aren't
10277 currently using, and they create false positives in our pthreads
10278 wrappers. Fixes bug 20110; bugfix on 0.2.9.1-alpha.
10280 o Minor bugfixes (directory authority):
10281 - Die with a more useful error when the operator forgets to place
10282 the authority_signing_key file into the keys directory. This
10283 avoids an uninformative assert & traceback about having an invalid
10284 key. Fixes bug 20065; bugfix on 0.2.0.1-alpha.
10285 - When allowing private addresses, mark Exits that only exit to
10286 private locations as such. Fixes bug 20064; bugfix
10289 o Minor bugfixes (documentation):
10290 - Document the default PathsNeededToBuildCircuits value that's used
10291 by clients when the directory authorities don't set
10292 min_paths_for_circs_pct. Fixes bug 20117; bugfix on 02c320916e02
10293 in 0.2.4.10-alpha. Patch by teor, reported by Jesse V.
10294 - Fix manual for the User option: it takes a username, not a UID.
10295 Fixes bug 19122; bugfix on 0.0.2pre16 (the first version to have
10298 o Minor bugfixes (hidden services):
10299 - Stop logging intro point details to the client log on certain
10300 error conditions. Fixed as part of bug 20012; bugfix on
10301 0.2.4.8-alpha. Patch by teor.
10303 o Minor bugfixes (IPv6, testing):
10304 - Check for IPv6 correctly on Linux when running test networks.
10305 Fixes bug 19905; bugfix on 0.2.7.3-rc; patch by teor.
10307 o Minor bugfixes (Linux seccomp2 sandbox):
10308 - Add permission to run the sched_yield() and sigaltstack() system
10309 calls, in order to support versions of Tor compiled with asan or
10310 ubsan code that use these calls. Now "sandbox 1" and
10311 "--enable-expensive-hardening" should be compatible on more
10312 systems. Fixes bug 20063; bugfix on 0.2.5.1-alpha.
10314 o Minor bugfixes (logging):
10315 - When logging a message from the BUG() macro, be explicit about
10316 what we were asserting. Previously we were confusing what we were
10317 asserting with what the bug was. Fixes bug 20093; bugfix
10319 - When we are unable to remove the bw_accounting file, do not warn
10320 if the reason we couldn't remove it was that it didn't exist.
10321 Fixes bug 19964; bugfix on 0.2.5.4-alpha. Patch from 'pastly'.
10323 o Minor bugfixes (option parsing):
10324 - Count unix sockets when counting client listeners (SOCKS, Trans,
10325 NATD, and DNS). This has no user-visible behaviour changes: these
10326 options are set once, and never read. Required for correct
10327 behaviour in ticket 17178. Fixes bug 19677; bugfix on
10328 0.2.6.3-alpha. Patch by teor.
10330 o Minor bugfixes (options):
10331 - Check the consistency of UseEntryGuards and EntryNodes more
10332 reliably. Fixes bug 20074; bugfix on 0.2.4.12-alpha. Patch
10334 - Stop changing the configured value of UseEntryGuards on
10335 authorities and Tor2web clients. Fixes bug 20074; bugfix on
10336 commits 51fc6799 in 0.1.1.16-rc and acda1735 in 0.2.4.3-alpha.
10339 o Minor bugfixes (Tor2web):
10340 - Prevent Tor2web clients running hidden services, these services
10341 are not anonymous due to the one-hop client paths. Fixes bug
10342 19678. Patch by teor.
10344 o Minor bugfixes (unit tests):
10345 - Fix a shared-random unit test that was failing on big endian
10346 architectures due to internal representation of a integer copied
10347 to a buffer. The test is changed to take a full 32 bytes of data
10348 and use the output of a python script that make the COMMIT and
10349 REVEAL calculation according to the spec. Fixes bug 19977; bugfix
10351 - The tor_tls_server_info_callback unit test no longer crashes when
10352 debug-level logging is turned on. Fixes bug 20041; bugfix
10356 Changes in version 0.2.8.8 - 2016-09-23
10357 Tor 0.2.8.8 fixes two crash bugs present in previous versions of the
10358 0.2.8.x series. Relays running 0.2.8.x should upgrade, as should users
10359 who select public relays as their bridges.
10361 o Major bugfixes (crash):
10362 - Fix a complicated crash bug that could affect Tor clients
10363 configured to use bridges when replacing a networkstatus consensus
10364 in which one of their bridges was mentioned. OpenBSD users saw
10365 more crashes here, but all platforms were potentially affected.
10366 Fixes bug 20103; bugfix on 0.2.8.2-alpha.
10368 o Major bugfixes (relay, OOM handler):
10369 - Fix a timing-dependent assertion failure that could occur when we
10370 tried to flush from a circuit after having freed its cells because
10371 of an out-of-memory condition. Fixes bug 20203; bugfix on
10372 0.2.8.1-alpha. Thanks to "cypherpunks" for help diagnosing
10375 o Minor feature (fallback directories):
10376 - Remove 8 fallbacks that are no longer suitable, leaving 81 of the
10377 100 fallbacks originally introduced in Tor 0.2.8.2-alpha in March
10378 2016. Closes ticket 20190; patch by teor.
10380 o Minor features (geoip):
10381 - Update geoip and geoip6 to the September 6 2016 Maxmind GeoLite2
10385 Changes in version 0.2.9.2-alpha - 2016-08-24
10386 Tor 0.2.9.2-alpha continues development of the 0.2.9 series with
10387 several new features and bugfixes. It also includes an important
10388 authority update and an important bugfix from 0.2.8.7. Everyone who
10389 sets the ReachableAddresses option, and all bridges, are strongly
10390 encouraged to upgrade to 0.2.8.7, or to 0.2.9.2-alpha.
10392 o Directory authority changes (also in 0.2.8.7):
10393 - The "Tonga" bridge authority has been retired; the new bridge
10394 authority is "Bifroest". Closes tickets 19728 and 19690.
10396 o Major bugfixes (client, security, also in 0.2.8.7):
10397 - Only use the ReachableAddresses option to restrict the first hop
10398 in a path. In earlier versions of 0.2.8.x, it would apply to
10399 every hop in the path, with a possible degradation in anonymity
10400 for anyone using an uncommon ReachableAddress setting. Fixes bug
10401 19973; bugfix on 0.2.8.2-alpha.
10403 o Major features (user interface):
10404 - Tor now supports the ability to declare options deprecated, so
10405 that we can recommend that people stop using them. Previously,
10406 this was done in an ad-hoc way. Closes ticket 19820.
10408 o Major bugfixes (directory downloads):
10409 - Avoid resetting download status for consensuses hourly, since we
10410 already have another, smarter retry mechanism. Fixes bug 8625;
10411 bugfix on 0.2.0.9-alpha.
10413 o Minor features (config):
10414 - Warn users when descriptor and port addresses are inconsistent.
10415 Mitigates bug 13953; patch by teor.
10417 o Minor features (geoip):
10418 - Update geoip and geoip6 to the August 2 2016 Maxmind GeoLite2
10421 o Minor features (user interface):
10422 - There is a new --list-deprecated-options command-line option to
10423 list all of the deprecated options. Implemented as part of
10426 o Minor bugfixes (code style):
10427 - Fix an integer signedness conversion issue in the case conversion
10428 tables. Fixes bug 19168; bugfix on 0.2.1.11-alpha.
10430 o Minor bugfixes (compilation):
10431 - Build correctly on versions of libevent2 without support for
10432 evutil_secure_rng_add_bytes(). Fixes bug 19904; bugfix
10434 - Fix a compilation warning on GCC versions before 4.6. Our
10435 ENABLE_GCC_WARNING macro used the word "warning" as an argument,
10436 when it is also required as an argument to the compiler pragma.
10437 Fixes bug 19901; bugfix on 0.2.9.1-alpha.
10439 o Minor bugfixes (compilation, also in 0.2.8.7):
10440 - Remove an inappropriate "inline" in tortls.c that was causing
10441 warnings on older versions of GCC. Fixes bug 19903; bugfix
10444 o Minor bugfixes (fallback directories, also in 0.2.8.7):
10445 - Avoid logging a NULL string pointer when loading fallback
10446 directory information. Fixes bug 19947; bugfix on 0.2.4.7-alpha
10447 and 0.2.8.1-alpha. Report and patch by "rubiate".
10449 o Minor bugfixes (logging):
10450 - Log a more accurate message when we fail to dump a microdescriptor.
10451 Fixes bug 17758; bugfix on 0.2.2.8-alpha. Patch from Daniel Pinto.
10453 o Minor bugfixes (memory leak):
10454 - Fix a series of slow memory leaks related to parsing torrc files
10455 and options. Fixes bug 19466; bugfix on 0.2.1.6-alpha.
10457 o Deprecated features:
10458 - A number of DNS-cache-related sub-options for client ports are now
10459 deprecated for security reasons, and may be removed in a future
10460 version of Tor. (We believe that client-side DNS caching is a bad
10461 idea for anonymity, and you should not turn it on.) The options
10462 are: CacheDNS, CacheIPv4DNS, CacheIPv6DNS, UseDNSCache,
10463 UseIPv4Cache, and UseIPv6Cache.
10464 - A number of options are deprecated for security reasons, and may
10465 be removed in a future version of Tor. The options are:
10466 AllowDotExit, AllowInvalidNodes, AllowSingleHopCircuits,
10467 AllowSingleHopExits, ClientDNSRejectInternalAddresses,
10468 CloseHSClientCircuitsImmediatelyOnTimeout,
10469 CloseHSServiceRendCircuitsImmediatelyOnTimeout,
10470 ExcludeSingleHopRelays, FastFirstHopPK, TLSECGroup,
10471 UseNTorHandshake, and WarnUnsafeSocks.
10472 - The *ListenAddress options are now deprecated as unnecessary: the
10473 corresponding *Port options should be used instead. These options
10474 may someday be removed. The affected options are:
10475 ControlListenAddress, DNSListenAddress, DirListenAddress,
10476 NATDListenAddress, ORListenAddress, SocksListenAddress,
10477 and TransListenAddress.
10480 - Correct the IPv6 syntax in our documentation for the
10481 VirtualAddrNetworkIPv6 torrc option. Closes ticket 19743.
10484 - We no longer include the (dead, deprecated) bufferevent code in
10485 Tor. Closes ticket 19450. Based on a patch from U+039b.
10488 Changes in version 0.2.8.7 - 2016-08-24
10489 Tor 0.2.8.7 fixes an important bug related to the ReachableAddresses
10490 option in 0.2.8.6, and replaces a retiring bridge authority. Everyone
10491 who sets the ReachableAddresses option, and all bridges, are strongly
10492 encouraged to upgrade.
10494 o Directory authority changes:
10495 - The "Tonga" bridge authority has been retired; the new bridge
10496 authority is "Bifroest". Closes tickets 19728 and 19690.
10498 o Major bugfixes (client, security):
10499 - Only use the ReachableAddresses option to restrict the first hop
10500 in a path. In earlier versions of 0.2.8.x, it would apply to
10501 every hop in the path, with a possible degradation in anonymity
10502 for anyone using an uncommon ReachableAddress setting. Fixes bug
10503 19973; bugfix on 0.2.8.2-alpha.
10505 o Minor features (geoip):
10506 - Update geoip and geoip6 to the August 2 2016 Maxmind GeoLite2
10509 o Minor bugfixes (compilation):
10510 - Remove an inappropriate "inline" in tortls.c that was causing
10511 warnings on older versions of GCC. Fixes bug 19903; bugfix
10514 o Minor bugfixes (fallback directories):
10515 - Avoid logging a NULL string pointer when loading fallback
10516 directory information. Fixes bug 19947; bugfix on 0.2.4.7-alpha
10517 and 0.2.8.1-alpha. Report and patch by "rubiate".
10520 Changes in version 0.2.9.1-alpha - 2016-08-08
10521 Tor 0.2.9.1-alpha is the first alpha release in the 0.2.9 development
10522 series. It improves our support for hardened builds and compiler
10523 warnings, deploys some critical infrastructure for improvements to
10524 hidden services, includes a new timing backend that we hope to use for
10525 better support for traffic padding, makes it easier for programmers to
10526 log unexpected events, and contains other small improvements to
10527 security, correctness, and performance.
10529 Below are the changes since 0.2.8.6.
10531 o New system requirements:
10532 - Tor now requires Libevent version 2.0.10-stable or later. Older
10533 versions of Libevent have less efficient backends for several
10534 platforms, and lack the DNS code that we use for our server-side
10535 DNS support. This implements ticket 19554.
10536 - Tor now requires zlib version 1.2 or later, for security,
10537 efficiency, and (eventually) gzip support. (Back when we started,
10538 zlib 1.1 and zlib 1.0 were still found in the wild. 1.2 was
10539 released in 2003. We recommend the latest version.)
10541 o Major features (build, hardening):
10542 - Tor now builds with -ftrapv by default on compilers that support
10543 it. This option detects signed integer overflow (which C forbids),
10544 and turns it into a hard-failure. We do not apply this option to
10545 code that needs to run in constant time to avoid side-channels;
10546 instead, we use -fwrapv in that code. Closes ticket 17983.
10547 - When --enable-expensive-hardening is selected, stop applying the
10548 clang/gcc sanitizers to code that needs to run in constant time.
10549 Although we are aware of no introduced side-channels, we are not
10550 able to prove that there are none. Related to ticket 17983.
10552 o Major features (compilation):
10553 - Our big list of extra GCC warnings is now enabled by default when
10554 building with GCC (or with anything like Clang that claims to be
10555 GCC-compatible). To make all warnings into fatal compilation
10556 errors, pass --enable-fatal-warnings to configure. Closes
10558 - Use the Autoconf macro AC_USE_SYSTEM_EXTENSIONS to automatically
10559 turn on C and POSIX extensions. (Previously, we attempted to do
10560 this on an ad hoc basis.) Closes ticket 19139.
10562 o Major features (directory authorities, hidden services):
10563 - Directory authorities can now perform the shared randomness
10564 protocol specified by proposal 250. Using this protocol, directory
10565 authorities generate a global fresh random value every day. In the
10566 future, this value will be used by hidden services to select
10567 HSDirs. This release implements the directory authority feature;
10568 the hidden service side will be implemented in the future as part
10569 of proposal 224. Resolves ticket 16943; implements proposal 250.
10571 o Major features (downloading, random exponential backoff):
10572 - When we fail to download an object from a directory service, wait
10573 for an (exponentially increasing) randomized amount of time before
10574 retrying, rather than a fixed interval as we did before. This
10575 prevents a group of Tor instances from becoming too synchronized,
10576 or a single Tor instance from becoming too predictable, in its
10577 download schedule. Closes ticket 15942.
10579 o Major bugfixes (exit policies):
10580 - Avoid disclosing exit outbound bind addresses, configured port
10581 bind addresses, and local interface addresses in relay descriptors
10582 by default under ExitPolicyRejectPrivate. Instead, only reject
10583 these (otherwise unlisted) addresses if
10584 ExitPolicyRejectLocalInterfaces is set. Fixes bug 18456; bugfix on
10585 0.2.7.2-alpha. Patch by teor.
10587 o Major bugfixes (hidden service client):
10588 - Allow Tor clients with appropriate controllers to work with
10589 FetchHidServDescriptors set to 0. Previously, this option also
10590 disabled descriptor cache lookup, thus breaking hidden services
10591 entirely. Fixes bug 18704; bugfix on 0.2.0.20-rc. Patch by "twim".
10593 o Minor features (build, hardening):
10594 - Detect and work around a libclang_rt problem that would prevent
10595 clang from finding __mulodi4() on some 32-bit platforms, and thus
10596 keep -ftrapv from linking on those systems. Closes ticket 19079.
10597 - When building on a system without runtime support for the runtime
10598 hardening options, try to log a useful warning at configuration
10599 time, rather than an incomprehensible warning at link time. If
10600 expensive hardening was requested, this warning becomes an error.
10601 Closes ticket 18895.
10603 o Minor features (code safety):
10604 - In our integer-parsing functions, ensure that maxiumum value we
10605 give is no smaller than the minimum value. Closes ticket 19063;
10608 o Minor features (controller):
10609 - Implement new GETINFO queries for all downloads that use
10610 download_status_t to schedule retries. This allows controllers to
10611 examine the schedule for pending downloads. Closes ticket 19323.
10612 - Allow controllers to configure basic client authorization on
10613 hidden services when they create them with the ADD_ONION control
10614 command. Implements ticket 15588. Patch by "special".
10615 - Fire a STATUS_SERVER controller event whenever the hibernation
10616 status changes between "awake"/"soft"/"hard". Closes ticket 18685.
10618 o Minor features (directory authority):
10619 - Directory authorities now only give the Guard flag to a relay if
10620 they are also giving it the Stable flag. This change allows us to
10621 simplify path selection for clients. It should have minimal effect
10622 in practice, since >99% of Guards already have the Stable flag.
10623 Implements ticket 18624.
10624 - Directory authorities now write their v3-status-votes file out to
10625 disk earlier in the consensus process, so we have a record of the
10626 votes even if we abort the consensus process. Resolves
10629 o Minor features (hidden service):
10630 - Stop being so strict about the payload length of "rendezvous1"
10631 cells. We used to be locked in to the "TAP" handshake length, and
10632 now we can handle better handshakes like "ntor". Resolves
10635 o Minor features (infrastructure, time):
10636 - Tor now uses the operating system's monotonic timers (where
10637 available) for internal fine-grained timing. Previously we would
10638 look at the system clock, and then attempt to compensate for the
10639 clock running backwards. Closes ticket 18908.
10640 - Tor now includes an improved timer backend, so that we can
10641 efficiently support tens or hundreds of thousands of concurrent
10642 timers, as will be needed for some of our planned anti-traffic-
10643 analysis work. This code is based on William Ahern's "timeout.c"
10644 project, which implements a "tickless hierarchical timing wheel".
10645 Closes ticket 18365.
10647 o Minor features (logging):
10648 - Provide a more useful warning message when configured with an
10649 invalid Nickname. Closes ticket 18300; patch from "icanhasaccount".
10650 - When dumping unparseable router descriptors, optionally store them
10651 in separate files, named by digest, up to a configurable size
10652 limit. You can change the size limit by setting the
10653 MaxUnparseableDescSizeToLog option, and disable this feature by
10654 setting that option to 0. Closes ticket 18322.
10655 - Add a set of macros to check nonfatal assertions, for internal
10656 use. Migrating more of our checks to these should help us avoid
10657 needless crash bugs. Closes ticket 18613.
10659 o Minor features (performance):
10660 - Changer the "optimistic data" extension from "off by default" to
10661 "on by default". The default was ordinarily overridden by a
10662 consensus option, but when clients were bootstrapping for the
10663 first time, they would not have a consensus to get the option
10664 from. Changing this default When fetching a consensus for the
10665 first time, use optimistic data. This saves a round-trip during
10666 startup. Closes ticket 18815.
10668 o Minor features (relay, usability):
10669 - When the directory authorities refuse a bad relay's descriptor,
10670 encourage the relay operator to contact us. Many relay operators
10671 won't notice this line in their logs, but it's a win if even a few
10672 learn why we don't like what their relay was doing. Resolves
10675 o Minor features (testing):
10676 - Let backtrace tests work correctly under AddressSanitizer. Fixes
10677 part of bug 18934; bugfix on 0.2.5.2-alpha.
10678 - Move the test-network.sh script to chutney, and modify tor's test-
10679 network.sh to call the (newer) chutney version when available.
10680 Resolves ticket 19116. Patch by teor.
10681 - Use the lcov convention for marking lines as unreachable, so that
10682 we don't count them when we're generating test coverage data.
10683 Update our coverage tools to understand this convention. Closes
10686 o Minor bugfixes (bootstrap):
10687 - Remember the directory we fetched the consensus or previous
10688 certificates from, and use it to fetch future authority
10689 certificates. This change improves bootstrapping performance.
10690 Fixes bug 18963; bugfix on 0.2.8.1-alpha.
10692 o Minor bugfixes (build):
10693 - The test-stem and test-network makefile targets now depend only on
10694 the tor binary that they are testing. Previously, they depended on
10695 "make all". Fixes bug 18240; bugfix on 0.2.8.2-alpha. Based on a
10696 patch from "cypherpunks".
10698 o Minor bugfixes (circuits):
10699 - Make sure extend_info_from_router() is only called on servers.
10700 Fixes bug 19639; bugfix on 0.2.8.1-alpha.
10702 o Minor bugfixes (compilation):
10703 - When building with Clang, use a full set of GCC warnings.
10704 (Previously, we included only a subset, because of the way we
10705 detected them.) Fixes bug 19216; bugfix on 0.2.0.1-alpha.
10707 o Minor bugfixes (directory authority):
10708 - Authorities now sort the "package" lines in their votes, for ease
10709 of debugging. (They are already sorted in consensus documents.)
10710 Fixes bug 18840; bugfix on 0.2.6.3-alpha.
10711 - When parsing a detached signature, make sure we use the length of
10712 the digest algorithm instead of an hardcoded DIGEST256_LEN in
10713 order to avoid comparing bytes out-of-bounds with a smaller digest
10714 length such as SHA1. Fixes bug 19066; bugfix on 0.2.2.6-alpha.
10716 o Minor bugfixes (documentation):
10717 - Document the --passphrase-fd option in the tor manpage. Fixes bug
10718 19504; bugfix on 0.2.7.3-rc.
10719 - Fix the description of the --passphrase-fd option in the
10720 tor-gencert manpage. The option is used to pass the number of a
10721 file descriptor to read the passphrase from, not to read the file
10722 descriptor from. Fixes bug 19505; bugfix on 0.2.0.20-alpha.
10724 o Minor bugfixes (ephemeral hidden service):
10725 - When deleting an ephemeral hidden service, close its intro points
10726 even if they are not completely open. Fixes bug 18604; bugfix
10729 o Minor bugfixes (guard selection):
10730 - Use a single entry guard even if the NumEntryGuards consensus
10731 parameter is not provided. Fixes bug 17688; bugfix
10733 - Don't mark guards as unreachable if connection_connect() fails.
10734 That function fails for local reasons, so it shouldn't reveal
10735 anything about the status of the guard. Fixes bug 14334; bugfix
10738 o Minor bugfixes (hidden service client):
10739 - Increase the minimum number of internal circuits we preemptively
10740 build from 2 to 3, so a circuit is available when a client
10741 connects to another onion service. Fixes bug 13239; bugfix
10744 o Minor bugfixes (logging):
10745 - When logging a directory ownership mismatch, log the owning
10746 username correctly. Fixes bug 19578; bugfix on 0.2.2.29-beta.
10748 o Minor bugfixes (memory leaks):
10749 - Fix a small, uncommon memory leak that could occur when reading a
10750 truncated ed25519 key file. Fixes bug 18956; bugfix
10753 o Minor bugfixes (testing):
10754 - Allow clients to retry HSDirs much faster in test networks. Fixes
10755 bug 19702; bugfix on 0.2.7.1-alpha. Patch by teor.
10756 - Disable ASAN's detection of segmentation faults while running
10757 test_bt.sh, so that we can make sure that our own backtrace
10758 generation code works. Fixes another aspect of bug 18934; bugfix
10759 on 0.2.5.2-alpha. Patch from "cypherpunks".
10760 - Fix the test-network-all target on out-of-tree builds by using the
10761 correct path to the test driver script. Fixes bug 19421; bugfix
10764 o Minor bugfixes (time):
10765 - Improve overflow checks in tv_udiff and tv_mdiff. Fixes bug 19483;
10766 bugfix on all released tor versions.
10767 - When computing the difference between two times in milliseconds,
10768 we now round to the nearest millisecond correctly. Previously, we
10769 could sometimes round in the wrong direction. Fixes bug 19428;
10770 bugfix on 0.2.2.2-alpha.
10772 o Minor bugfixes (user interface):
10773 - Display a more accurate number of suppressed messages in the log
10774 rate-limiter. Previously, there was a potential integer overflow
10775 in the counter. Now, if the number of messages hits a maximum, the
10776 rate-limiter doesn't count any further. Fixes bug 19435; bugfix
10778 - Fix a typo in the passphrase prompt for the ed25519 identity key.
10779 Fixes bug 19503; bugfix on 0.2.7.2-alpha.
10781 o Code simplification and refactoring:
10782 - Remove redundant declarations of the MIN macro. Closes
10784 - Rename tor_dup_addr() to tor_addr_to_str_dup() to avoid confusion.
10785 Closes ticket 18462; patch from "icanhasaccount".
10786 - Split the 600-line directory_handle_command_get function into
10787 separate functions for different URL types. Closes ticket 16698.
10790 - Fix spelling of "--enable-tor2web-mode" in the manpage. Closes
10791 ticket 19153. Patch from "U+039b".
10793 o Removed features:
10794 - Remove support for "GET /tor/bytes.txt" DirPort request, and
10795 "GETINFO dir-usage" controller request, which were only available
10796 via a compile-time option in Tor anyway. Feature was added in
10797 0.2.2.1-alpha. Resolves ticket 19035.
10798 - There is no longer a compile-time option to disable support for
10799 TransPort. (If you don't want TransPort; just don't use it.) Patch
10800 from "U+039b". Closes ticket 19449.
10803 - Run more workqueue tests as part of "make check". These had
10804 previously been implemented, but you needed to know special
10805 command-line options to enable them.
10806 - We now have unit tests for our code to reject zlib "compression
10807 bombs". (Fortunately, the code works fine.)
10810 Changes in version 0.2.8.6 - 2016-08-02
10812 Tor 0.2.8.6 is the first stable version of the Tor 0.2.8 series.
10814 The Tor 0.2.8 series improves client bootstrapping performance,
10815 completes the authority-side implementation of improved identity
10816 keys for relays, and includes numerous bugfixes and performance
10817 improvements throughout the program. This release continues to
10818 improve the coverage of Tor's test suite. For a full list of
10819 changes since Tor 0.2.7, see the ReleaseNotes file.
10821 Changes since 0.2.8.5-rc:
10823 o Minor features (geoip):
10824 - Update geoip and geoip6 to the July 6 2016 Maxmind GeoLite2
10827 o Minor bugfixes (compilation):
10828 - Fix a compilation warning in the unit tests on systems where char
10829 is signed. Fixes bug 19682; bugfix on 0.2.8.1-alpha.
10831 o Minor bugfixes (fallback directories):
10832 - Remove 1 fallback that was on the hardcoded list, then opted-out,
10833 leaving 89 of the 100 fallbacks originally introduced in Tor
10834 0.2.8.2-alpha in March 2016. Closes ticket 19782; patch by teor.
10836 o Minor bugfixes (Linux seccomp2 sandbox):
10837 - Allow more syscalls when running with "Sandbox 1" enabled:
10838 sysinfo, getsockopt(SO_SNDBUF), and setsockopt(SO_SNDBUFFORCE). On
10839 some systems, these are required for Tor to start. Fixes bug
10840 18397; bugfix on 0.2.5.1-alpha. Patch from Daniel Pinto.
10841 - Allow IPPROTO_UDP datagram sockets when running with "Sandbox 1",
10842 so that get_interface_address6_via_udp_socket_hack() can work.
10843 Fixes bug 19660; bugfix on 0.2.5.1-alpha.
10846 Changes in version 0.2.8.5-rc - 2016-07-07
10847 Tor 0.2.8.5-rc is the second release candidate in the Tor 0.2.8
10848 series. If we find no new bugs or regressions here, the first stable
10849 0.2.8 release will be identical to it. It has a few small bugfixes
10850 against previous versions.
10852 o Directory authority changes:
10853 - Urras is no longer a directory authority. Closes ticket 19271.
10855 o Major bugfixes (heartbeat):
10856 - Fix a regression that would crash Tor when the periodic
10857 "heartbeat" log messages were disabled. Fixes bug 19454; bugfix on
10858 0.2.8.1-alpha. Reported by "kubaku".
10860 o Minor features (build):
10861 - Tor now again builds with the recent OpenSSL 1.1 development
10862 branch (tested against 1.1.0-pre6-dev). Closes ticket 19499.
10863 - When building manual pages, set the timezone to "UTC", so that the
10864 output is reproducible. Fixes bug 19558; bugfix on 0.2.2.9-alpha.
10865 Patch from intrigeri.
10867 o Minor bugfixes (fallback directory selection):
10868 - Avoid errors during fallback selection if there are no eligible
10869 fallbacks. Fixes bug 19480; bugfix on 0.2.8.3-alpha. Patch
10872 o Minor bugfixes (IPv6, microdescriptors):
10873 - Don't check node addresses when we only have a routerstatus. This
10874 allows IPv6-only clients to bootstrap by fetching microdescriptors
10875 from fallback directory mirrors. (The microdescriptor consensus
10876 has no IPv6 addresses in it.) Fixes bug 19608; bugfix
10879 o Minor bugfixes (logging):
10880 - Reduce pointlessly verbose log messages when directory servers
10881 can't be found. Fixes bug 18849; bugfix on 0.2.8.3-alpha and
10882 0.2.8.1-alpha. Patch by teor.
10883 - When a fallback directory changes its fingerprint from the hard-
10884 coded fingerprint, log a less severe, more explanatory log
10885 message. Fixes bug 18812; bugfix on 0.2.8.1-alpha. Patch by teor.
10887 o Minor bugfixes (Linux seccomp2 sandboxing):
10888 - Allow statistics to be written to disk when "Sandbox 1" is
10889 enabled. Fixes bugs 19556 and 19957; bugfix on 0.2.5.1-alpha and
10890 0.2.6.1-alpha respectively.
10892 o Minor bugfixes (user interface):
10893 - Remove a warning message "Service [scrubbed] not found after
10894 descriptor upload". This message appears when one uses HSPOST
10895 control command to upload a service descriptor. Since there is
10896 only a descriptor and no service, showing this message is
10897 pointless and confusing. Fixes bug 19464; bugfix on 0.2.7.2-alpha.
10899 o Fallback directory list:
10900 - Add a comment to the generated fallback directory list that
10901 explains how to comment out unsuitable fallbacks in a way that's
10902 compatible with the stem fallback parser.
10903 - Update fallback whitelist and blacklist based on relay operator
10904 emails. Blacklist unsuitable (non-working, over-volatile)
10905 fallbacks. Resolves ticket 19071. Patch by teor.
10906 - Remove 10 unsuitable fallbacks, leaving 90 of the 100 fallbacks
10907 originally introduced in Tor 0.2.8.2-alpha in March 2016. Closes
10908 ticket 19071; patch by teor.
10911 Changes in version 0.2.8.4-rc - 2016-06-15
10912 Tor 0.2.8.4-rc is the first release candidate in the Tor 0.2.8 series.
10913 If we find no new bugs or regressions here, the first stable 0.2.8
10914 release will be identical to it. It has a few small bugfixes against
10917 o Major bugfixes (user interface):
10918 - Correctly give a warning in the cases where a relay is specified
10919 by nickname, and one such relay is found, but it is not officially
10920 Named. Fixes bug 19203; bugfix on 0.2.3.1-alpha.
10922 o Minor features (build):
10923 - Tor now builds once again with the recent OpenSSL 1.1 development
10924 branch (tested against 1.1.0-pre5 and 1.1.0-pre6-dev).
10926 o Minor features (geoip):
10927 - Update geoip and geoip6 to the June 7 2016 Maxmind GeoLite2
10930 o Minor bugfixes (compilation):
10931 - Cause the unit tests to compile correctly on mingw64 versions that
10932 lack sscanf. Fixes bug 19213; bugfix on 0.2.7.1-alpha.
10934 o Minor bugfixes (downloading):
10935 - Predict more correctly whether we'll be downloading over HTTP when
10936 we determine the maximum length of a URL. This should avoid a
10937 "BUG" warning about the Squid HTTP proxy and its URL limits. Fixes
10941 Changes in version 0.2.8.3-alpha - 2016-05-26
10942 Tor 0.2.8.3-alpha resolves several bugs, most of them introduced over
10943 the course of the 0.2.8 development cycle. It improves the behavior of
10944 directory clients, fixes several crash bugs, fixes a gap in compiler
10945 hardening, and allows the full integration test suite to run on
10948 o Major bugfixes (security, client, DNS proxy):
10949 - Stop a crash that could occur when a client running with DNSPort
10950 received a query with multiple address types, and the first
10951 address type was not supported. Found and fixed by Scott Dial.
10952 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
10954 o Major bugfixes (security, compilation):
10955 - Correctly detect compiler flags on systems where _FORTIFY_SOURCE
10956 is predefined. Previously, our use of -D_FORTIFY_SOURCE would
10957 cause a compiler warning, thereby making other checks fail, and
10958 needlessly disabling compiler-hardening support. Fixes one case of
10959 bug 18841; bugfix on 0.2.3.17-beta. Patch from "trudokal".
10961 o Major bugfixes (security, directory authorities):
10962 - Fix a crash and out-of-bounds write during authority voting, when
10963 the list of relays includes duplicate ed25519 identity keys. Fixes
10964 bug 19032; bugfix on 0.2.8.2-alpha.
10966 o Major bugfixes (client, bootstrapping):
10967 - Check if bootstrap consensus downloads are still needed when the
10968 linked connection attaches. This prevents tor making unnecessary
10969 begindir-style connections, which are the only directory
10970 connections tor clients make since the fix for 18483 was merged.
10971 - Fix some edge cases where consensus download connections may not
10972 have been closed, even though they were not needed. Related to fix
10974 - Make relays retry consensus downloads the correct number of times,
10975 rather than the more aggressive client retry count. Fixes part of
10977 - Stop downloading consensuses when we have a consensus, even if we
10978 don't have all the certificates for it yet. Fixes bug 18809;
10979 bugfix on 0.2.8.1-alpha. Patches by arma and teor.
10981 o Major bugfixes (directory mirrors):
10982 - Decide whether to advertise begindir support in the the same way
10983 we decide whether to advertise our DirPort. Allowing these
10984 decisions to become out-of-sync led to surprising behavior like
10985 advertising begindir support when hibernation made us not
10986 advertise a DirPort. Resolves bug 18616; bugfix on 0.2.8.1-alpha.
10989 o Major bugfixes (IPv6 bridges, client):
10990 - Actually use IPv6 addresses when selecting directory addresses for
10991 IPv6 bridges. Fixes bug 18921; bugfix on 0.2.8.1-alpha. Patch
10994 o Major bugfixes (key management):
10995 - If OpenSSL fails to generate an RSA key, do not retain a dangling
10996 pointer to the previous (uninitialized) key value. The impact here
10997 should be limited to a difficult-to-trigger crash, if OpenSSL is
10998 running an engine that makes key generation failures possible, or
10999 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
11000 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
11003 o Major bugfixes (testing):
11004 - Fix a bug that would block 'make test-network-all' on systems where
11005 IPv6 packets were lost. Fixes bug 19008; bugfix on 0.2.7.3-rc.
11006 - Avoid "WSANOTINITIALISED" warnings in the unit tests. Fixes bug 18668;
11007 bugfix on 0.2.8.1-alpha.
11009 o Minor features (clients):
11010 - Make clients, onion services, and bridge relays always use an
11011 encrypted begindir connection for directory requests. Resolves
11012 ticket 18483. Patch by "teor".
11014 o Minor features (fallback directory mirrors):
11015 - Give each fallback the same weight for client selection; restrict
11016 fallbacks to one per operator; report fallback directory detail
11017 changes when rebuilding list; add new fallback directory mirrors
11018 to the whitelist; and many other minor simplifications and fixes.
11019 Closes tasks 17905, 18749, bug 18689, and fixes part of bug 18812 on
11020 0.2.8.1-alpha; patch by "teor".
11021 - Replace the 21 fallbacks generated in January 2016 and included in
11022 Tor 0.2.8.1-alpha, with a list of 100 fallbacks generated in March
11023 2016. Closes task 17158; patch by "teor".
11025 o Minor features (geoip):
11026 - Update geoip and geoip6 to the May 4 2016 Maxmind GeoLite2
11029 o Minor bugfixes (assert, portability):
11030 - Fix an assertion failure in memarea.c on systems where "long" is
11031 shorter than the size of a pointer. Fixes bug 18716; bugfix
11034 o Minor bugfixes (bootstrap):
11035 - Consistently use the consensus download schedule for authority
11036 certificates. Fixes bug 18816; bugfix on 0.2.4.13-alpha.
11038 o Minor bugfixes (build):
11039 - Remove a pair of redundant AM_CONDITIONAL declarations from
11040 configure.ac. Fixes one final case of bug 17744; bugfix
11042 - Resolve warnings when building on systems that are concerned with
11043 signed char. Fixes bug 18728; bugfix on 0.2.7.2-alpha
11045 - When libscrypt.h is found, but no libscrypt library can be linked,
11046 treat libscrypt as absent. Fixes bug 19161; bugfix
11049 o Minor bugfixes (client):
11050 - Turn all TestingClientBootstrap* into non-testing torrc options.
11051 This changes simply renames them by removing "Testing" in front of
11052 them and they do not require TestingTorNetwork to be enabled
11053 anymore. Fixes bug 18481; bugfix on 0.2.8.1-alpha.
11054 - Make directory node selection more reliable, mainly for IPv6-only
11055 clients and clients with few reachable addresses. Fixes bug 18929;
11056 bugfix on 0.2.8.1-alpha. Patch by "teor".
11058 o Minor bugfixes (controller, microdescriptors):
11059 - Make GETINFO dir/status-vote/current/consensus conform to the
11060 control specification by returning "551 Could not open cached
11061 consensus..." when not caching consensuses. Fixes bug 18920;
11062 bugfix on 0.2.2.6-alpha.
11064 o Minor bugfixes (crypto, portability):
11065 - The SHA3 and SHAKE routines now produce the correct output on Big
11066 Endian systems. No code calls either algorithm yet, so this is
11067 primarily a build fix. Fixes bug 18943; bugfix on 0.2.8.1-alpha.
11068 - Tor now builds again with the recent OpenSSL 1.1 development
11069 branch (tested against 1.1.0-pre4 and 1.1.0-pre5-dev). Closes
11072 o Minor bugfixes (directories):
11073 - When fetching extrainfo documents, compare their SHA256 digests
11074 and Ed25519 signing key certificates with the routerinfo that led
11075 us to fetch them, rather than with the most recent routerinfo.
11076 Otherwise we generate many spurious warnings about mismatches.
11077 Fixes bug 17150; bugfix on 0.2.7.2-alpha.
11079 o Minor bugfixes (logging):
11080 - When we can't generate a signing key because OfflineMasterKey is
11081 set, do not imply that we should have been able to load it. Fixes
11082 bug 18133; bugfix on 0.2.7.2-alpha.
11083 - Stop periodic_event_dispatch() from blasting twelve lines per
11084 second at loglevel debug. Fixes bug 18729; fix on 0.2.8.1-alpha.
11085 - When rejecting a misformed INTRODUCE2 cell, only log at
11086 PROTOCOL_WARN severity. Fixes bug 18761; bugfix on 0.2.8.2-alpha.
11088 o Minor bugfixes (pluggable transports):
11089 - Avoid reporting a spurious error when we decide that we don't need
11090 to terminate a pluggable transport because it has already exited.
11091 Fixes bug 18686; bugfix on 0.2.5.5-alpha.
11093 o Minor bugfixes (pointer arithmetic):
11094 - Fix a bug in memarea_alloc() that could have resulted in remote
11095 heap write access, if Tor had ever passed an unchecked size to
11096 memarea_alloc(). Fortunately, all the sizes we pass to
11097 memarea_alloc() are pre-checked to be less than 128 kilobytes.
11098 Fixes bug 19150; bugfix on 0.2.1.1-alpha. Bug found by
11101 o Minor bugfixes (relays):
11102 - Consider more config options when relays decide whether to
11103 regenerate their descriptor. Fixes more of bug 12538; bugfix
11105 - Resolve some edge cases where we might launch an ORPort
11106 reachability check even when DisableNetwork is set. Noticed while
11107 fixing bug 18616; bugfix on 0.2.3.9-alpha.
11109 o Minor bugfixes (statistics):
11110 - We now include consensus downloads via IPv6 in our directory-
11111 request statistics. Fixes bug 18460; bugfix on 0.2.3.14-alpha.
11113 o Minor bugfixes (testing):
11114 - Allow directories in small networks to bootstrap by skipping
11115 DirPort checks when the consensus has no exits. Fixes bug 19003;
11116 bugfix on 0.2.8.1-alpha. Patch by teor.
11117 - Fix a small memory leak that would occur when the
11118 TestingEnableCellStatsEvent option was turned on. Fixes bug 18673;
11119 bugfix on 0.2.5.2-alpha.
11121 o Minor bugfixes (time handling):
11122 - When correcting a corrupt 'struct tm' value, fill in the tm_wday
11123 field. Otherwise, our unit tests crash on Windows. Fixes bug
11124 18977; bugfix on 0.2.2.25-alpha.
11127 - Document the contents of the 'datadir/keys' subdirectory in the
11128 manual page. Closes ticket 17621.
11129 - Stop recommending use of nicknames to identify relays in our
11130 MapAddress documentation. Closes ticket 18312.
11133 Changes in version 0.2.8.2-alpha - 2016-03-28
11134 Tor 0.2.8.2-alpha is the second alpha in its series. It fixes numerous
11135 bugs in earlier versions of Tor, including some that prevented
11136 authorities using Tor 0.2.7.x from running correctly. IPv6 and
11137 directory support should also be much improved.
11139 o New system requirements:
11140 - Tor no longer supports versions of OpenSSL with a broken
11141 implementation of counter mode. (This bug was present in OpenSSL
11142 1.0.0, and was fixed in OpenSSL 1.0.0a.) Tor still detects, but no
11143 longer runs with, these versions.
11144 - Tor no longer attempts to support platforms where the "time_t"
11145 type is unsigned. (To the best of our knowledge, only OpenVMS does
11146 this, and Tor has never actually built on OpenVMS.) Closes
11148 - Tor now uses Autoconf version 2.63 or later, and Automake 1.11 or
11149 later (released in 2008 and 2009 respectively). If you are
11150 building Tor from the git repository instead of from the source
11151 distribution, and your tools are older than this, you will need to
11152 upgrade. Closes ticket 17732.
11154 o Major bugfixes (security, pointers):
11155 - Avoid a difficult-to-trigger heap corruption attack when extending
11156 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
11157 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
11158 Reported by Guido Vranken.
11160 o Major bugfixes (bridges, pluggable transports):
11161 - Modify the check for OR connections to private addresses. Allow
11162 bridges on private addresses, including pluggable transports that
11163 ignore the (potentially private) address in the bridge line. Fixes
11164 bug 18517; bugfix on 0.2.8.1-alpha. Reported by gk, patch by teor.
11166 o Major bugfixes (compilation):
11167 - Repair hardened builds under the clang compiler. Previously, our
11168 use of _FORTIFY_SOURCE would conflict with clang's address
11169 sanitizer. Fixes bug 14821; bugfix on 0.2.5.4-alpha.
11171 o Major bugfixes (crash on shutdown):
11172 - Correctly handle detaching circuits from muxes when shutting down.
11173 Fixes bug 18116; bugfix on 0.2.8.1-alpha.
11174 - Fix an assert-on-exit bug related to counting memory usage in
11175 rephist.c. Fixes bug 18651; bugfix on 0.2.8.1-alpha.
11177 o Major bugfixes (crash on startup):
11178 - Fix a segfault during startup: If a Unix domain socket was
11179 configured as listener (such as a ControlSocket or a SocksPort
11180 "unix:" socket), and tor was started as root but not configured to
11181 switch to another user, tor would segfault while trying to string
11182 compare a NULL value. Fixes bug 18261; bugfix on 0.2.8.1-alpha.
11185 o Major bugfixes (dns proxy mode, crash):
11186 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
11187 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
11189 o Major bugfixes (relays, bridge clients):
11190 - Ensure relays always allow IPv4 OR and Dir connections. Ensure
11191 bridge clients use the address configured in the bridge line.
11192 Fixes bug 18348; bugfix on 0.2.8.1-alpha. Reported by sysrqb,
11195 o Major bugfixes (voting):
11196 - Actually enable support for authorities to match routers by their
11197 Ed25519 identities. Previously, the code had been written, but
11198 some debugging code that had accidentally been left in the
11199 codebase made it stay turned off. Fixes bug 17702; bugfix
11201 - When collating votes by Ed25519 identities, authorities now
11202 include a "NoEdConsensus" flag if the ed25519 value (or lack
11203 thereof) for a server does not reflect the majority consensus.
11204 Related to bug 17668; bugfix on 0.2.7.2-alpha.
11205 - When generating a vote with keypinning disabled, never include two
11206 entries for the same ed25519 identity. This bug was causing
11207 authorities to generate votes that they could not parse when a
11208 router violated key pinning by changing its RSA identity but
11209 keeping its Ed25519 identity. Fixes bug 17668; fixes part of bug
11210 18318. Bugfix on 0.2.7.2-alpha.
11212 o Minor features (security, win32):
11213 - Set SO_EXCLUSIVEADDRUSE on Win32 to avoid a local port-stealing
11214 attack. Fixes bug 18123; bugfix on all tor versions. Patch
11217 o Minor features (bug-resistance):
11218 - Make Tor survive errors involving connections without a
11219 corresponding event object. Previously we'd fail with an
11220 assertion; now we produce a log message. Related to bug 16248.
11222 o Minor features (build):
11223 - Detect systems with FreeBSD-derived kernels (such as GNU/kFreeBSD)
11224 as having possible IPFW support. Closes ticket 18448. Patch from
11225 Steven Chamberlain.
11227 o Minor features (code hardening):
11228 - Use tor_snprintf() and tor_vsnprintf() even in external and low-
11229 level code, to harden against accidental failures to NUL-
11230 terminate. Part of ticket 17852. Patch from jsturgix. Found
11233 o Minor features (crypto):
11234 - Validate the hard-coded Diffie-Hellman parameters and ensure that
11235 p is a safe prime, and g is a suitable generator. Closes
11238 o Minor features (geoip):
11239 - Update geoip and geoip6 to the March 3 2016 Maxmind GeoLite2
11242 o Minor features (hidden service directory):
11243 - Streamline relay-side hsdir handling: when relays consider whether
11244 to accept an uploaded hidden service descriptor, they no longer
11245 check whether they are one of the relays in the network that is
11246 "supposed" to handle that descriptor. Implements ticket 18332.
11248 o Minor features (IPv6):
11249 - Add ClientPreferIPv6DirPort, which is set to 0 by default. If set
11250 to 1, tor prefers IPv6 directory addresses.
11251 - Add ClientUseIPv4, which is set to 1 by default. If set to 0, tor
11252 avoids using IPv4 for client OR and directory connections.
11253 - Try harder to obey the IP version restrictions "ClientUseIPv4 0",
11254 "ClientUseIPv6 0", "ClientPreferIPv6ORPort", and
11255 "ClientPreferIPv6DirPort". Closes ticket 17840; patch by teor.
11257 o Minor features (linux seccomp2 sandbox):
11258 - Reject attempts to change our Address with "Sandbox 1" enabled.
11259 Changing Address with Sandbox turned on would never actually work,
11260 but previously it would fail in strange and confusing ways. Found
11261 while fixing 18548.
11263 o Minor features (robustness):
11264 - Exit immediately with an error message if the code attempts to use
11265 Libevent without having initialized it. This should resolve some
11266 frequently-made mistakes in our unit tests. Closes ticket 18241.
11268 o Minor features (unix domain sockets):
11269 - Add a new per-socket option, RelaxDirModeCheck, to allow creating
11270 Unix domain sockets without checking the permissions on the parent
11271 directory. (Tor checks permissions by default because some
11272 operating systems only check permissions on the parent directory.
11273 However, some operating systems do look at permissions on the
11274 socket, and tor's default check is unneeded.) Closes ticket 18458.
11277 o Minor bugfixes (exit policies, security):
11278 - Refresh an exit relay's exit policy when interface addresses
11279 change. Previously, tor only refreshed the exit policy when the
11280 configured external address changed. Fixes bug 18208; bugfix on
11281 0.2.7.3-rc. Patch by teor.
11283 o Minor bugfixes (security, hidden services):
11284 - Prevent hidden services connecting to client-supplied rendezvous
11285 addresses that are reserved as internal or multicast. Fixes bug
11286 8976; bugfix on 0.2.3.21-rc. Patch by dgoulet and teor.
11288 o Minor bugfixes (build):
11289 - Do not link the unit tests against both the testing and non-
11290 testing versions of the static libraries. Fixes bug 18490; bugfix
11292 - Avoid spurious failures from configure files related to calling
11293 exit(0) in TOR_SEARCH_LIBRARY. Fixes bug 18626; bugfix on
11294 0.2.0.1-alpha. Patch from "cypherpunks".
11295 - Silence spurious clang-scan warnings in the ed25519_donna code by
11296 explicitly initializing some objects. Fixes bug 18384; bugfix on
11297 0.2.7.2-alpha. Patch by teor.
11299 o Minor bugfixes (client, bootstrap):
11300 - Count receipt of new microdescriptors as progress towards
11301 bootstrapping. Previously, with EntryNodes set, Tor might not
11302 successfully repopulate the guard set on bootstrapping. Fixes bug
11303 16825; bugfix on 0.2.3.1-alpha.
11305 o Minor bugfixes (code correctness):
11306 - Update to the latest version of Trunnel, which tries harder to
11307 avoid generating code that can invoke memcpy(p,NULL,0). Bug found
11308 by clang address sanitizer. Fixes bug 18373; bugfix
11311 o Minor bugfixes (configuration):
11312 - Fix a tiny memory leak when parsing a port configuration ending in
11313 ":auto". Fixes bug 18374; bugfix on 0.2.3.3-alpha.
11315 o Minor bugfixes (containers):
11316 - If we somehow attempt to construct a heap with more than
11317 1073741822 elements, avoid an integer overflow when maintaining
11318 the heap property. Fixes bug 18296; bugfix on 0.1.2.1-alpha.
11320 o Minor bugfixes (correctness):
11321 - Fix a bad memory handling bug that would occur if we had queued a
11322 cell on a channel's incoming queue. Fortunately, we can't actually
11323 queue a cell like that as our code is constructed today, but it's
11324 best to avoid this kind of error, even if there isn't any code
11325 that triggers it today. Fixes bug 18570; bugfix on 0.2.4.4-alpha.
11327 o Minor bugfixes (directory):
11328 - When generating a URL for a directory server on an IPv6 address,
11329 wrap the IPv6 address in square brackets. Fixes bug 18051; bugfix
11330 on 0.2.3.9-alpha. Patch from Malek.
11332 o Minor bugfixes (fallback directory mirrors):
11333 - When requesting extrainfo descriptors from a trusted directory
11334 server, check whether it is an authority or a fallback directory
11335 which supports extrainfo descriptors. Fixes bug 18489; bugfix on
11336 0.2.4.7-alpha. Reported by atagar, patch by teor.
11338 o Minor bugfixes (hidden service, client):
11339 - Handle the case where the user makes several fast consecutive
11340 requests to the same .onion address. Previously, the first six
11341 requests would each trigger a descriptor fetch, each picking a
11342 directory (there are 6 overall) and the seventh one would fail
11343 because no directories were left, thereby triggering a close on
11344 all current directory connections asking for the hidden service.
11345 The solution here is to not close the connections if we have
11346 pending directory fetches. Fixes bug 15937; bugfix
11349 o Minor bugfixes (hidden service, control port):
11350 - Add the onion address to the HS_DESC event for the UPLOADED action
11351 both on success or failure. It was previously hardcoded with
11352 UNKNOWN. Fixes bug 16023; bugfix on 0.2.7.2-alpha.
11354 o Minor bugfixes (hidden service, directory):
11355 - Bridges now refuse "rendezvous2" (hidden service descriptor)
11356 publish attempts. Suggested by ticket 18332.
11358 o Minor bugfixes (linux seccomp2 sandbox):
11359 - Allow the setrlimit syscall, and the prlimit and prlimit64
11360 syscalls, which some libc implementations use under the hood.
11361 Fixes bug 15221; bugfix on 0.2.5.1-alpha.
11362 - Avoid a 10-second delay when starting as a client with "Sandbox 1"
11363 enabled and no DNS resolvers configured. This should help TAILS
11364 start up faster. Fixes bug 18548; bugfix on 0.2.5.1-alpha.
11365 - Fix the sandbox's interoperability with unix domain sockets under
11366 setuid. Fixes bug 18253; bugfix on 0.2.8.1-alpha.
11368 o Minor bugfixes (logging):
11369 - When logging information about an unparsable networkstatus vote or
11370 consensus, do not say "vote" when we mean consensus. Fixes bug
11371 18368; bugfix on 0.2.0.8-alpha.
11372 - Scrub service name in "unrecognized service ID" log messages.
11373 Fixes bug 18600; bugfix on 0.2.4.11-alpha.
11374 - Downgrade logs and backtraces about IP versions to info-level.
11375 Only log backtraces once each time tor runs. Assists in diagnosing
11376 bug 18351; bugfix on 0.2.8.1-alpha. Reported by sysrqb and
11377 Christian, patch by teor.
11379 o Minor bugfixes (memory safety):
11380 - Avoid freeing an uninitialized pointer when opening a socket fails
11381 in get_interface_addresses_ioctl(). Fixes bug 18454; bugfix on
11382 0.2.3.11-alpha. Reported by toralf and "cypherpunks", patch
11384 - Correctly duplicate addresses in get_interface_address6_list().
11385 Fixes bug 18454; bugfix on 0.2.8.1-alpha. Reported by toralf,
11386 patch by "cypherpunks".
11387 - Fix a memory leak in tor-gencert. Fixes part of bug 18672; bugfix
11389 - Fix a memory leak in "tor --list-fingerprint". Fixes part of bug
11390 18672; bugfix on 0.2.5.1-alpha.
11392 o Minor bugfixes (private directory):
11393 - Prevent a race condition when creating private directories. Fixes
11394 part of bug 17852; bugfix on 0.0.2pre13. Part of ticket 17852.
11395 Patch from jsturgix. Found with Flawfinder.
11397 o Minor bugfixes (test networks, IPv6):
11398 - Allow internal IPv6 addresses in descriptors in test networks.
11399 Fixes bug 17153; bugfix on 0.2.3.16-alpha. Patch by teor, reported
11402 o Minor bugfixes (testing):
11403 - We no longer disable assertions in the unit tests when coverage is
11404 enabled. Instead, we require you to say --disable-asserts-in-tests
11405 to the configure script if you need assertions disabled in the
11406 unit tests (for example, if you want to perform branch coverage).
11407 Fixes bug 18242; bugfix on 0.2.7.1-alpha.
11409 o Minor bugfixes (time parsing):
11410 - Avoid overflow in tor_timegm when parsing dates in and after 2038
11411 on platforms with 32-bit time_t. Fixes bug 18479; bugfix on
11412 0.0.2pre14. Patch by teor.
11414 o Minor bugfixes (tor-gencert):
11415 - Correctly handle the case where an authority operator enters a
11416 passphrase but sends an EOF before sending a newline. Fixes bug
11417 17443; bugfix on 0.2.0.20-rc. Found by junglefowl.
11419 o Code simplification and refactoring:
11420 - Quote all the string interpolations in configure.ac -- even those
11421 which we are pretty sure can't contain spaces. Closes ticket
11422 17744. Patch from zerosion.
11423 - Remove specialized code for non-inplace AES_CTR. 99% of our AES is
11424 inplace, so there's no need to have a separate implementation for
11425 the non-inplace code. Closes ticket 18258. Patch from Malek.
11426 - Simplify return types for some crypto functions that can't
11427 actually fail. Patch from Hassan Alsibyani. Closes ticket 18259.
11430 - Change build messages to refer to "Fedora" instead of "Fedora
11431 Core", and "dnf" instead of "yum". Closes tickets 18459 and 18426.
11432 Patches from "icanhasaccount" and "cypherpunks".
11434 o Removed features:
11435 - We no longer maintain an internal freelist in memarea.c.
11436 Allocators should be good enough to make this code unnecessary,
11437 and it's doubtful that it ever had any performance benefit.
11440 - Fix several warnings from clang's address sanitizer produced in
11442 - Treat backtrace test failures as expected on FreeBSD until we
11443 solve bug 17808. Closes ticket 18204.
11446 Changes in version 0.2.8.1-alpha - 2016-02-04
11447 Tor 0.2.8.1-alpha is the first alpha release in its series. It
11448 includes numerous small features and bugfixes against previous Tor
11449 versions, and numerous small infrastructure improvements. The most
11450 notable features are a set of improvements to the directory subsystem.
11452 o Major features (security, Linux):
11453 - When Tor starts as root on Linux and is told to switch user ID, it
11454 can now retain the capability to bind to low ports. By default,
11455 Tor will do this only when it's switching user ID and some low
11456 ports have been configured. You can change this behavior with the
11457 new option KeepBindCapabilities. Closes ticket 8195.
11459 o Major features (directory system):
11460 - When bootstrapping multiple consensus downloads at a time, use the
11461 first one that starts downloading, and close the rest. This
11462 reduces failures when authorities or fallback directories are slow
11463 or down. Together with the code for feature 15775, this feature
11464 should reduces failures due to fallback churn. Implements ticket
11465 4483. Patch by "teor". Implements IPv4 portions of proposal 210 by
11466 "mikeperry" and "teor".
11467 - Include a trial list of 21 default fallback directories, generated
11468 in January 2016, based on an opt-in survey of suitable relays.
11469 Doing this should make clients bootstrap more quickly and reliably,
11470 and reduce the load on the directory authorities. Closes ticket
11471 15775. Patch by "teor".
11472 Candidates identified using an OnionOO script by "weasel", "teor",
11473 "gsathya", and "karsten".
11474 - Previously only relays that explicitly opened a directory port
11475 (DirPort) accepted directory requests from clients. Now all
11476 relays, with and without a DirPort, accept and serve tunneled
11477 directory requests that they receive through their ORPort. You can
11478 disable this behavior using the new DirCache option. Closes
11481 o Major key updates:
11482 - Update the V3 identity key for the dannenberg directory authority:
11483 it was changed on 18 November 2015. Closes task 17906. Patch
11486 o Minor features (security, clock):
11487 - Warn when the system clock appears to move back in time (when the
11488 state file was last written in the future). Tor doesn't know that
11489 consensuses have expired if the clock is in the past. Patch by
11490 "teor". Implements ticket 17188.
11492 o Minor features (security, exit policies):
11493 - ExitPolicyRejectPrivate now rejects more private addresses by
11494 default. Specifically, it now rejects the relay's outbound bind
11495 addresses (if configured), and the relay's configured port
11496 addresses (such as ORPort and DirPort). Fixes bug 17027; bugfix on
11497 0.2.0.11-alpha. Patch by "teor".
11499 o Minor features (security, memory erasure):
11500 - Set the unused entries in a smartlist to NULL. This helped catch
11501 a (harmless) bug, and shouldn't affect performance too much.
11502 Implements ticket 17026.
11503 - Use SecureMemoryWipe() function to securely clean memory on
11504 Windows. Previously we'd use OpenSSL's OPENSSL_cleanse() function.
11505 Implements feature 17986.
11506 - Use explicit_bzero or memset_s when present. Previously, we'd use
11507 OpenSSL's OPENSSL_cleanse() function. Closes ticket 7419; patches
11508 from <logan@hackers.mu> and <selven@hackers.mu>.
11509 - Make memwipe() do nothing when passed a NULL pointer or buffer of
11510 zero size. Check size argument to memwipe() for underflow. Fixes
11511 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
11514 o Minor features (security, RNG):
11515 - Adjust Tor's use of OpenSSL's RNG APIs so that they absolutely,
11516 positively are not allowed to fail. Previously we depended on
11517 internal details of OpenSSL's behavior. Closes ticket 17686.
11518 - Never use the system entropy output directly for anything besides
11519 seeding the PRNG. When we want to generate important keys, instead
11520 of using system entropy directly, we now hash it with the PRNG
11521 stream. This may help resist certain attacks based on broken OS
11522 entropy implementations. Closes part of ticket 17694.
11523 - Use modern system calls (like getentropy() or getrandom()) to
11524 generate strong entropy on platforms that have them. Closes
11527 o Minor features (accounting):
11528 - Added two modes to the AccountingRule option: One for limiting
11529 only the number of bytes sent ("AccountingRule out"), and one for
11530 limiting only the number of bytes received ("AccountingRule in").
11531 Closes ticket 15989; patch from "unixninja92".
11533 o Minor features (build):
11534 - Since our build process now uses "make distcheck", we no longer
11535 force "make dist" to depend on "make check". Closes ticket 17893;
11536 patch from "cypherpunks."
11537 - Tor now builds successfully with the recent OpenSSL 1.1
11538 development branch, and with the latest LibreSSL. Closes tickets
11539 17549, 17921, and 17984.
11541 o Minor features (controller):
11542 - Adds the FallbackDir entries to 'GETINFO config/defaults'. Closes
11543 tickets 16774 and 17817. Patch by George Tankersley.
11544 - New 'GETINFO hs/service/desc/id/' command to retrieve a hidden
11545 service descriptor from a service's local hidden service
11546 descriptor cache. Closes ticket 14846.
11547 - Add 'GETINFO exit-policy/reject-private/[default,relay]', so
11548 controllers can examine the the reject rules added by
11549 ExitPolicyRejectPrivate. This makes it easier for stem to display
11552 o Minor features (crypto):
11553 - Add SHA512 support to crypto.c. Closes ticket 17663; patch from
11555 - Add SHA3 and SHAKE support to crypto.c. Closes ticket 17783.
11556 - When allocating a digest state object, allocate no more space than
11557 we actually need. Previously, we would allocate as much space as
11558 the state for the largest algorithm would need. This change saves
11559 up to 672 bytes per circuit. Closes ticket 17796.
11560 - Improve performance when hashing non-multiple of 8 sized buffers,
11561 based on Andrew Moon's public domain SipHash-2-4 implementation.
11562 Fixes bug 17544; bugfix on 0.2.5.3-alpha.
11564 o Minor features (directory downloads):
11565 - Wait for busy authorities and fallback directories to become non-
11566 busy when bootstrapping. (A similar change was made in 6c443e987d
11567 for directory caches chosen from the consensus.) Closes ticket
11568 17864; patch by "teor".
11569 - Add UseDefaultFallbackDirs, which enables any hard-coded fallback
11570 directory mirrors. The default is 1; set it to 0 to disable
11571 fallbacks. Implements ticket 17576. Patch by "teor".
11573 o Minor features (geoip):
11574 - Update geoip and geoip6 to the January 5 2016 Maxmind GeoLite2
11577 o Minor features (IPv6):
11578 - Add an argument 'ipv6=address:orport' to the DirAuthority and
11579 FallbackDir torrc options, to specify an IPv6 address for an
11580 authority or fallback directory. Add hard-coded ipv6 addresses for
11581 directory authorities that have them. Closes ticket 17327; patch
11582 from Nick Mathewson and "teor".
11583 - Add address policy assume_action support for IPv6 addresses.
11584 - Limit IPv6 mask bits to 128.
11585 - Warn when comparing against an AF_UNSPEC address in a policy, it's
11586 almost always a bug. Closes ticket 17863; patch by "teor".
11587 - Allow users to configure directory authorities and fallback
11588 directory servers with IPv6 addresses and ORPorts. Resolves
11590 - routerset_parse now accepts IPv6 literal addresses. Fixes bug
11591 17060; bugfix on 0.2.1.3-alpha. Patch by "teor".
11592 - Make tor_ersatz_socketpair work on IPv6-only systems. Fixes bug
11593 17638; bugfix on 0.0.2pre8. Patch by "teor".
11595 o Minor features (logging):
11596 - When logging to syslog, allow a tag to be added to the syslog
11597 identity (the string prepended to every log message). The tag can
11598 be configured with SyslogIdentityTag and defaults to none. Setting
11599 it to "foo" will cause logs to be tagged as "Tor-foo". Closes
11602 o Minor features (portability):
11603 - Use timingsafe_memcmp() where available. Closes ticket 17944;
11604 patch from <logan@hackers.mu>.
11606 o Minor features (relay, address discovery):
11607 - Add a family argument to get_interface_addresses_raw() and
11608 subfunctions to make network interface address interogation more
11609 efficient. Now Tor can specifically ask for IPv4, IPv6 or both
11610 types of interfaces from the operating system. Resolves
11612 - When get_interface_address6_list(.,AF_UNSPEC,.) is called and
11613 fails to enumerate interface addresses using the platform-specific
11614 API, have it rely on the UDP socket fallback technique to try and
11615 find out what IP addresses (both IPv4 and IPv6) our machine has.
11616 Resolves ticket 17951.
11618 o Minor features (replay cache):
11619 - The replay cache now uses SHA256 instead of SHA1. Implements
11620 feature 8961. Patch by "teor", issue reported by "rransom".
11622 o Minor features (unix file permissions):
11623 - Defer creation of Unix sockets until after setuid. This avoids
11624 needing CAP_CHOWN and CAP_FOWNER when using systemd's
11625 CapabilityBoundingSet, or chown and fowner when using SELinux.
11626 Implements part of ticket 17562. Patch from Jamie Nguyen.
11627 - If any directory created by Tor is marked as group readable, the
11628 filesystem group is allowed to be either the default GID or the
11629 root user. Allowing root to read the DataDirectory prevents the
11630 need for CAP_READ_SEARCH when using systemd's
11631 CapabilityBoundingSet, or dac_read_search when using SELinux.
11632 Implements part of ticket 17562. Patch from Jamie Nguyen.
11633 - Introduce a new DataDirectoryGroupReadable option. If it is set to
11634 1, the DataDirectory will be made readable by the default GID.
11635 Implements part of ticket 17562. Patch from Jamie Nguyen.
11637 o Minor bugfixes (accounting):
11638 - The max bandwidth when using 'AccountRule sum' is now correctly
11639 logged. Fixes bug 18024; bugfix on 0.2.6.1-alpha. Patch
11640 from "unixninja92".
11642 o Minor bugfixes (code correctness):
11643 - When closing an entry connection, generate a warning if we should
11644 have sent an end cell for it but we haven't. Fixes bug 17876;
11645 bugfix on 0.2.3.2-alpha.
11646 - Assert that allocated memory held by the reputation code is freed
11647 according to its internal counters. Fixes bug 17753; bugfix
11649 - Assert when the TLS contexts fail to initialize. Fixes bug 17683;
11652 o Minor bugfixes (compilation):
11653 - Mark all object files that include micro-revision.i as depending
11654 on it, so as to make parallel builds more reliable. Fixes bug
11655 17826; bugfix on 0.2.5.1-alpha.
11656 - Don't try to use the pthread_condattr_setclock() function unless
11657 it actually exists. Fixes compilation on NetBSD-6.x. Fixes bug
11658 17819; bugfix on 0.2.6.3-alpha.
11659 - Fix backtrace compilation on FreeBSD. Fixes bug 17827; bugfix
11661 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
11662 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
11663 - Fix search for libevent libraries on OpenBSD (and other systems
11664 that install libevent 1 and libevent 2 in parallel). Fixes bug
11665 16651; bugfix on 0.1.0.7-rc. Patch from "rubiate".
11666 - Isolate environment variables meant for tests from the rest of the
11667 build system. Fixes bug 17818; bugfix on 0.2.7.3-rc.
11668 - Replace usage of 'INLINE' with 'inline'. Fixes bug 17804; bugfix
11670 - Remove config.log only from make distclean, not from make clean.
11671 Fixes bug 17924; bugfix on 0.2.4.1-alpha.
11673 o Minor bugfixes (crypto):
11674 - Check the return value of HMAC() and assert on failure. Fixes bug
11675 17658; bugfix on 0.2.3.6-alpha. Patch by "teor".
11677 o Minor bugfixes (fallback directories):
11678 - Mark fallbacks as "too busy" when they return a 503 response,
11679 rather than just marking authorities. Fixes bug 17572; bugfix on
11680 0.2.4.7-alpha. Patch by "teor".
11682 o Minor bugfixes (IPv6):
11683 - Update the limits in max_dl_per_request for IPv6 address length.
11684 Fixes bug 17573; bugfix on 0.2.1.5-alpha.
11686 o Minor bugfixes (linux seccomp2 sandbox):
11687 - Fix a crash when using offline master ed25519 keys with the Linux
11688 seccomp2 sandbox enabled. Fixes bug 17675; bugfix on 0.2.7.3-rc.
11690 o Minor bugfixes (logging):
11691 - In log messages that include a function name, use __FUNCTION__
11692 instead of __PRETTY_FUNCTION__. In GCC, these are synonymous, but
11693 with clang __PRETTY_FUNCTION__ has extra information we don't
11694 need. Fixes bug 16563; bugfix on 0.0.2pre8. Fix by Tom van
11696 - Remove needless quotes from a log message about unparseable
11697 addresses. Fixes bug 17843; bugfix on 0.2.3.3-alpha.
11699 o Minor bugfixes (portability):
11700 - Remove an #endif from configure.ac so that we correctly detect the
11701 presence of in6_addr.s6_addr32. Fixes bug 17923; bugfix
11704 o Minor bugfixes (relays):
11705 - Check that both the ORPort and DirPort (if present) are reachable
11706 before publishing a relay descriptor. Otherwise, relays publish a
11707 descriptor with DirPort 0 when the DirPort reachability test takes
11708 longer than the ORPort reachability test. Fixes bug 18050; bugfix
11709 on 0.1.0.1-rc. Reported by "starlight", patch by "teor".
11711 o Minor bugfixes (relays, hidden services):
11712 - Refuse connection requests to private OR addresses unless
11713 ExtendAllowPrivateAddresses is set. Previously, tor would connect,
11714 then refuse to send any cells to a private address. Fixes bugs
11715 17674 and 8976; bugfix on 0.2.3.21-rc. Patch by "teor".
11717 o Minor bugfixes (safe logging):
11718 - When logging a malformed hostname received through socks4, scrub
11719 it if SafeLogging says we should. Fixes bug 17419; bugfix
11722 o Minor bugfixes (statistics code):
11723 - Consistently check for overflow in round_*_to_next_multiple_of
11724 functions, and add unit tests with additional and maximal values.
11725 Fixes part of bug 13192; bugfix on 0.2.2.1-alpha.
11726 - Handle edge cases in the laplace functions: avoid division by
11727 zero, avoid taking the log of zero, and silence clang type
11728 conversion warnings using round and trunc. Add unit tests for edge
11729 cases with maximal values. Fixes part of bug 13192; bugfix
11732 o Minor bugfixes (testing):
11733 - The test for log_heartbeat was incorrectly failing in timezones
11734 with non-integer offsets. Instead of comparing the end of the time
11735 string against a constant, compare it to the output of
11736 format_local_iso_time when given the correct input. Fixes bug
11737 18039; bugfix on 0.2.5.4-alpha.
11738 - Make unit tests pass on IPv6-only systems, and systems without
11739 localhost addresses (like some FreeBSD jails). Fixes bug 17632;
11740 bugfix on 0.2.7.3-rc. Patch by "teor".
11741 - Fix a memory leak in the ntor test. Fixes bug 17778; bugfix
11743 - Check the full results of SHA256 and SHA512 digests in the unit
11744 tests. Bugfix on 0.2.2.4-alpha. Patch by "teor".
11746 o Code simplification and refactoring:
11747 - Move logging of redundant policy entries in
11748 policies_parse_exit_policy_internal into its own function. Closes
11749 ticket 17608; patch from "juce".
11750 - Extract the more complicated parts of circuit_mark_for_close()
11751 into a new function that we run periodically before circuits are
11752 freed. This change removes more than half of the functions
11753 currently in the "blob". Closes ticket 17218.
11754 - Clean up a little duplicated code in
11755 crypto_expand_key_material_TAP(). Closes ticket 17587; patch
11757 - Decouple the list of streams waiting to be attached to circuits
11758 from the overall connection list. This change makes it possible to
11759 attach streams quickly while simplifying Tor's callgraph and
11760 avoiding O(N) scans of the entire connection list. Closes
11762 - When a direct directory request fails immediately on launch,
11763 instead of relaunching that request from inside the code that
11764 launches it, instead mark the connection for teardown. This change
11765 simplifies Tor's callback and prevents the directory-request
11766 launching code from invoking itself recursively. Closes
11768 - Remove code for configuring OpenSSL dynamic locks; OpenSSL doesn't
11769 use them. Closes ticket 17926.
11772 - Add a description of the correct use of the '--keygen' command-
11773 line option. Closes ticket 17583; based on text by 's7r'.
11774 - Document the minimum HeartbeatPeriod value. Closes ticket 15638.
11775 - Explain actual minima for BandwidthRate. Closes ticket 16382.
11776 - Fix a minor formatting typo in the manpage. Closes ticket 17791.
11777 - Mention torspec URL in the manpage and point the reader to it
11778 whenever we mention a document that belongs in torspce. Fixes
11781 o Removed features:
11782 - Remove client-side support for connecting to Tor relays running
11783 versions of Tor before 0.2.3.6-alpha. These relays didn't support
11784 the v3 TLS handshake protocol, and are no longer allowed on the
11785 Tor network. Implements the client side of ticket 11150. Based on
11786 patches by Tom van der Woerdt.
11789 - Add unit tests to check for common RNG failure modes, such as
11790 returning all zeroes, identical values, or incrementing values
11791 (OpenSSL's rand_predictable feature). Patch by "teor".
11792 - Log more information when the backtrace tests fail. Closes ticket
11793 17892. Patch from "cypherpunks."
11794 - Always test both ed25519 backends, so that we can be sure that our
11795 batch-open replacement code works. Part of ticket 16794.
11796 - Cover dns_resolve_impl() in dns.c with unit tests. Implements a
11797 portion of ticket 16831.
11798 - More unit tests for compat_libevent.c, procmon.c, tortls.c,
11799 util_format.c, directory.c, and options_validate.c. Closes tickets
11800 17075, 17082, 17084, 17003, and 17076 respectively. Patches from
11802 - Unit tests for directory_handle_command_get. Closes ticket 17004.
11803 Patch from Reinaldo de Souza Jr.
11806 Changes in version 0.2.7.6 - 2015-12-10
11807 Tor version 0.2.7.6 fixes a major bug in entry guard selection, as
11808 well as a minor bug in hidden service reliability.
11810 o Major bugfixes (guard selection):
11811 - Actually look at the Guard flag when selecting a new directory
11812 guard. When we implemented the directory guard design, we
11813 accidentally started treating all relays as if they have the Guard
11814 flag during guard selection, leading to weaker anonymity and worse
11815 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
11818 o Minor features (geoip):
11819 - Update geoip and geoip6 to the December 1 2015 Maxmind GeoLite2
11822 o Minor bugfixes (compilation):
11823 - When checking for net/pfvar.h, include netinet/in.h if possible.
11824 This fixes transparent proxy detection on OpenBSD. Fixes bug
11825 17551; bugfix on 0.1.2.1-alpha. Patch from "rubiate".
11826 - Fix a compilation warning with Clang 3.6: Do not check the
11827 presence of an address which can never be NULL. Fixes bug 17781.
11829 o Minor bugfixes (correctness):
11830 - When displaying an IPv6 exit policy, include the mask bits
11831 correctly even when the number is greater than 31. Fixes bug
11832 16056; bugfix on 0.2.4.7-alpha. Patch from "gturner".
11833 - The wrong list was used when looking up expired intro points in a
11834 rend service object, causing what we think could be reachability
11835 issues for hidden services, and triggering a BUG log. Fixes bug
11836 16702; bugfix on 0.2.7.2-alpha.
11837 - Fix undefined behavior in the tor_cert_checksig function. Fixes
11838 bug 17722; bugfix on 0.2.7.2-alpha.
11841 Changes in version 0.2.7.5 - 2015-11-20
11842 The Tor 0.2.7 release series is dedicated to the memory of Tor user
11843 and privacy advocate Caspar Bowden (1961-2015). Caspar worked
11844 tirelessly to advocate human rights regardless of national borders,
11845 and oppose the encroachments of mass surveillance. He opposed national
11846 exceptionalism, he brought clarity to legal and policy debates, he
11847 understood and predicted the impact of mass surveillance on the world,
11848 and he laid the groundwork for resisting it. While serving on the Tor
11849 Project's board of directors, he brought us his uncompromising focus
11850 on technical excellence in the service of humankind. Caspar was an
11851 inimitable force for good and a wonderful friend. He was kind,
11852 humorous, generous, gallant, and believed we should protect one
11853 another without exception. We honor him here for his ideals, his
11854 efforts, and his accomplishments. Please honor his memory with works
11855 that would make him proud.
11857 Tor 0.2.7.5 is the first stable release in the Tor 0.2.7 series.
11859 The 0.2.7 series adds a more secure identity key type for relays,
11860 improves cryptography performance, resolves several longstanding
11861 hidden-service performance issues, improves controller support for
11862 hidden services, and includes small bugfixes and performance
11863 improvements throughout the program. This release series also includes
11864 more tests than before, and significant simplifications to which parts
11865 of Tor invoke which others.
11867 (This release contains no code changes since 0.2.7.4-rc.)
11870 Changes in version 0.2.7.4-rc - 2015-10-21
11871 Tor 0.2.7.4-rc is the second release candidate in the 0.2.7 series. It
11872 fixes some important memory leaks, and a scary-looking (but mostly
11873 harmless in practice) invalid-read bug. It also has a few small
11874 bugfixes, notably fixes for compilation and portability on different
11875 platforms. If no further significant bounds are found, the next
11876 release will the the official stable release.
11878 o Major bugfixes (security, correctness):
11879 - Fix an error that could cause us to read 4 bytes before the
11880 beginning of an openssl string. This bug could be used to cause
11881 Tor to crash on systems with unusual malloc implementations, or
11882 systems with unusual hardening installed. Fixes bug 17404; bugfix
11885 o Major bugfixes (correctness):
11886 - Fix a use-after-free bug in validate_intro_point_failure(). Fixes
11887 bug 17401; bugfix on 0.2.7.3-rc.
11889 o Major bugfixes (memory leaks):
11890 - Fix a memory leak in ed25519 batch signature checking. Fixes bug
11891 17398; bugfix on 0.2.6.1-alpha.
11892 - Fix a memory leak in rend_cache_failure_entry_free(). Fixes bug
11893 17402; bugfix on 0.2.7.3-rc.
11894 - Fix a memory leak when reading an expired signing key from disk.
11895 Fixes bug 17403; bugfix on 0.2.7.2-rc.
11897 o Minor features (geoIP):
11898 - Update geoip and geoip6 to the October 9 2015 Maxmind GeoLite2
11901 o Minor bugfixes (compilation):
11902 - Repair compilation with the most recent (unreleased, alpha)
11903 vesions of OpenSSL 1.1. Fixes part of ticket 17237.
11904 - Fix an integer overflow warning in test_crypto_slow.c. Fixes bug
11905 17251; bugfix on 0.2.7.2-alpha.
11906 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
11907 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
11909 o Minor bugfixes (portability):
11910 - Use libexecinfo on FreeBSD to enable backtrace support. Fixes
11911 part of bug 17151; bugfix on 0.2.5.2-alpha. Patch from
11914 o Minor bugfixes (sandbox):
11915 - Add the "hidserv-stats" filename to our sandbox filter for the
11916 HiddenServiceStatistics option to work properly. Fixes bug 17354;
11917 bugfix on 0.2.6.2-alpha. Patch from David Goulet.
11919 o Minor bugfixes (testing):
11920 - Add unit tests for get_interface_address* failure cases. Fixes bug
11921 17173; bugfix on 0.2.7.3-rc. Patch by fk/teor.
11922 - Fix breakage when running 'make check' with BSD make. Fixes bug
11923 17154; bugfix on 0.2.7.3-rc. Patch by Marcin Cieślak.
11924 - Make the get_ifaddrs_* unit tests more tolerant of different
11925 network configurations. (Don't assume every test box has an IPv4
11926 address, and don't assume every test box has a non-localhost
11927 address.) Fixes bug 17255; bugfix on 0.2.7.3-rc. Patch by "teor".
11928 - Skip backtrace tests when backtrace support is not compiled in.
11929 Fixes part of bug 17151; bugfix on 0.2.7.1-alpha. Patch from
11933 - Fix capitalization of SOCKS in sample torrc. Closes ticket 15609.
11934 - Note that HiddenServicePorts can take a unix domain socket. Closes
11938 Changes in version 0.2.7.3-rc - 2015-09-25
11939 Tor 0.2.7.3-rc is the first release candidate in the 0.2.7 series. It
11940 contains numerous usability fixes for Ed25519 keys, safeguards against
11941 several misconfiguration problems, significant simplifications to
11942 Tor's callgraph, and numerous bugfixes and small features.
11944 This is the most tested release of Tor to date. The unit tests cover
11945 39.40% of the code, and the integration tests (accessible with "make
11946 test-full-online", requiring stem and chutney and a network
11947 connection) raise the coverage to 64.49%.
11949 o Major features (security, hidden services):
11950 - Hidden services, if using the EntryNodes option, are required to
11951 use more than one EntryNode, in order to avoid a guard discovery
11952 attack. (This would only affect people who had configured hidden
11953 services and manually specified the EntryNodes option with a
11954 single entry-node. The impact was that it would be easy to
11955 remotely identify the guard node used by such a hidden service.
11956 See ticket for more information.) Fixes ticket 14917.
11958 o Major features (Ed25519 keys, keypinning):
11959 - The key-pinning option on directory authorities is now advisory-
11960 only by default. In a future version, or when the AuthDirPinKeys
11961 option is set, pins are enforced again. Disabling key-pinning
11962 seemed like a good idea so that we can survive the fallout of any
11963 usability problems associated with Ed25519 keys. Closes
11966 o Major features (Ed25519 performance):
11967 - Improve the speed of Ed25519 operations and Curve25519 keypair
11968 generation when built targeting 32 bit x86 platforms with SSE2
11969 available. Implements ticket 16535.
11970 - Improve the runtime speed of Ed25519 signature verification by
11971 using Ed25519-donna's batch verification support. Implements
11974 o Major features (performance testing):
11975 - The test-network.sh script now supports performance testing.
11976 Requires corresponding chutney performance testing changes. Patch
11977 by "teor". Closes ticket 14175.
11979 o Major features (relay, Ed25519):
11980 - Significant usability improvements for Ed25519 key management. Log
11981 messages are better, and the code can recover from far more
11982 failure conditions. Thanks to "s7r" for reporting and diagnosing
11984 - Add a new OfflineMasterKey option to tell Tor never to try loading
11985 or generating a secret Ed25519 identity key. You can use this in
11986 combination with tor --keygen to manage offline and/or encrypted
11987 Ed25519 keys. Implements ticket 16944.
11988 - Add a --newpass option to allow changing or removing the
11989 passphrase of an encrypted key with tor --keygen. Implements part
11991 - On receiving a HUP signal, check to see whether the Ed25519
11992 signing key has changed, and reload it if so. Closes ticket 16790.
11994 o Major bugfixes (relay, Ed25519):
11995 - Avoid crashing on 'tor --keygen'. Fixes bug 16679; bugfix on
11996 0.2.7.2-alpha. Reported by "s7r".
11997 - Improve handling of expired signing keys with offline master keys.
11998 Fixes bug 16685; bugfix on 0.2.7.2-alpha. Reported by "s7r".
12000 o Minor features (client-side privacy):
12001 - New KeepAliveIsolateSOCKSAuth option to indefinitely extend circuit
12002 lifespan when IsolateSOCKSAuth and streams with SOCKS
12003 authentication are attached to the circuit. This allows
12004 applications like TorBrowser to manage circuit lifetime on their
12005 own. Implements feature 15482.
12006 - When logging malformed hostnames from SOCKS5 requests, respect
12007 SafeLogging configuration. Fixes bug 16891; bugfix on 0.1.1.16-rc.
12009 o Minor features (compilation):
12010 - Give a warning as early as possible when trying to build with an
12011 unsupported OpenSSL version. Closes ticket 16901.
12012 - Fail during configure if we're trying to build against an OpenSSL
12013 built without ECC support. Fixes bug 17109, bugfix on 0.2.7.1-alpha
12014 which started requiring ECC.
12016 o Minor features (geoip):
12017 - Update geoip and geoip6 to the September 3 2015 Maxmind GeoLite2
12020 o Minor features (hidden services):
12021 - Relays need to have the Fast flag to get the HSDir flag. As this
12022 is being written, we'll go from 2745 HSDirs down to 2342, a ~14%
12023 drop. This change should make some attacks against the hidden
12024 service directory system harder. Fixes ticket 15963.
12025 - Turn on hidden service statistics collection by setting the torrc
12026 option HiddenServiceStatistics to "1" by default. (This keeps
12027 track only of the fraction of traffic used by hidden services, and
12028 the total number of hidden services in existence.) Closes
12030 - Client now uses an introduction point failure cache to know when
12031 to fetch or keep a descriptor in their cache. Previously, failures
12032 were recorded implicitly, but not explicitly remembered. Closes
12035 o Minor features (testing, authorities, documentation):
12036 - New TestingDirAuthVote{Exit,Guard,HSDir}IsStrict flags to
12037 explicitly manage consensus flags in testing networks. Patch by
12038 "robgjansen", modified by "teor". Implements part of ticket 14882.
12040 o Minor bugfixes (security, exit policies):
12041 - ExitPolicyRejectPrivate now also rejects the relay's published
12042 IPv6 address (if any), and any publicly routable IPv4 or IPv6
12043 addresses on any local interfaces. ticket 17027. Patch by "teor".
12044 Fixes bug 17027; bugfix on 0.2.0.11-alpha.
12046 o Minor bug fixes (torrc exit policies):
12047 - In torrc, "accept6 *" and "reject6 *" ExitPolicy lines now only
12048 produce IPv6 wildcard addresses. Previously they would produce
12049 both IPv4 and IPv6 wildcard addresses. Patch by "teor". Fixes part
12050 of bug 16069; bugfix on 0.2.4.7-alpha.
12051 - When parsing torrc ExitPolicies, we now warn for a number of cases
12052 where the user's intent is likely to differ from Tor's actual
12053 behavior. These include: using an IPv4 address with an accept6 or
12054 reject6 line; using "private" on an accept6 or reject6 line; and
12055 including any ExitPolicy lines after accept *:* or reject *:*.
12056 Related to ticket 16069.
12057 - When parsing torrc ExitPolicies, we now issue an info-level
12058 message when expanding an "accept/reject *" line to include both
12059 IPv4 and IPv6 wildcard addresses. Related to ticket 16069.
12060 - In each instance above, usage advice is provided to avoid the
12061 message. Resolves ticket 16069. Patch by "teor". Fixes part of bug
12062 16069; bugfix on 0.2.4.7-alpha.
12064 o Minor bugfixes (authority):
12065 - Don't assign "HSDir" to a router if it isn't Valid and Running.
12066 Fixes bug 16524; bugfix on 0.2.7.2-alpha.
12067 - Downgrade log messages about Ed25519 key issues if they are in old
12068 cached router descriptors. Fixes part of bug 16286; bugfix
12070 - When we find an Ed25519 key issue in a cached descriptor, stop
12071 saying the descriptor was just "uploaded". Fixes another part of
12072 bug 16286; bugfix on 0.2.7.2-alpha.
12074 o Minor bugfixes (control port):
12075 - Repair a warning and a spurious result when getting the maximum
12076 number of file descriptors from the controller. Fixes bug 16697;
12077 bugfix on 0.2.7.2-alpha.
12079 o Minor bugfixes (correctness):
12080 - When calling channel_free_list(), avoid calling smartlist_remove()
12081 while inside a FOREACH loop. This partially reverts commit
12082 17356fe7fd96af where the correct SMARTLIST_DEL_CURRENT was
12083 incorrectly removed. Fixes bug 16924; bugfix on 0.2.4.4-alpha.
12085 o Minor bugfixes (documentation):
12086 - Advise users on how to configure separate IPv4 and IPv6 exit
12087 policies in the manpage and sample torrcs. Related to ticket 16069.
12088 - Fix the usage message of tor-resolve(1) so that it no longer lists
12089 the removed -F option. Fixes bug 16913; bugfix on 0.2.2.28-beta.
12090 - Fix an error in the manual page and comments for
12091 TestingDirAuthVoteHSDir[IsStrict], which suggested that a HSDir
12092 required "ORPort connectivity". While this is true, it is in no
12093 way unique to the HSDir flag. Of all the flags, only HSDirs need a
12094 DirPort configured in order for the authorities to assign that
12095 particular flag. Patch by "teor". Fixed as part of 14882; bugfix
12098 o Minor bugfixes (Ed25519):
12099 - Fix a memory leak when reading router descriptors with expired
12100 Ed25519 certificates. Fixes bug 16539; bugfix on 0.2.7.2-alpha.
12102 o Minor bugfixes (linux seccomp2 sandbox):
12103 - Allow bridge authorities to run correctly under the seccomp2
12104 sandbox. Fixes bug 16964; bugfix on 0.2.5.1-alpha.
12105 - Allow routers with ed25519 keys to run correctly under the
12106 seccomp2 sandbox. Fixes bug 16965; bugfix on 0.2.7.2-alpha.
12108 o Minor bugfixes (open file limit):
12109 - Fix set_max_file_descriptors() to set by default the max open file
12110 limit to the current limit when setrlimit() fails. Fixes bug
12111 16274; bugfix on 0.2.0.10-alpha. Patch by dgoulet.
12113 o Minor bugfixes (portability):
12114 - Try harder to normalize the exit status of the Tor process to the
12115 standard-provided range. Fixes bug 16975; bugfix on every version
12117 - Check correctly for Windows socket errors in the workqueue
12118 backend. Fixes bug 16741; bugfix on 0.2.6.3-alpha.
12119 - Fix the behavior of crypto_rand_time_range() when told to consider
12120 times before 1970. (These times were possible when running in a
12121 simulated network environment where time()'s output starts at
12122 zero.) Fixes bug 16980; bugfix on 0.2.7.1-alpha.
12123 - Restore correct operation of TLS client-cipher detection on
12124 OpenSSL 1.1. Fixes bug 14047; bugfix on 0.2.7.2-alpha.
12126 o Minor bugfixes (relay):
12127 - Ensure that worker threads actually exit when a fatal error or
12128 shutdown is indicated. This fix doesn't currently affect the
12129 behavior of Tor, because Tor workers never indicates fatal error
12130 or shutdown except in the unit tests. Fixes bug 16868; bugfix
12132 - Unblock threads before releasing the work queue mutex to ensure
12133 predictable scheduling behavior. Fixes bug 16644; bugfix
12136 o Code simplification and refactoring:
12137 - Change the function that's called when we need to retry all
12138 downloads so that it only reschedules the downloads to happen
12139 immediately, rather than launching them all at once itself. This
12140 further simplifies Tor's callgraph.
12141 - Move some format-parsing functions out of crypto.c and
12142 crypto_curve25519.c into crypto_format.c and/or util_format.c.
12143 - Move the client-only parts of init_keys() into a separate
12144 function. Closes ticket 16763.
12145 - Simplify the microdesc_free() implementation so that it no longer
12146 appears (to code analysis tools) to potentially invoke a huge
12147 suite of other microdesc functions.
12148 - Simply the control graph further by deferring the inner body of
12149 directory_all_unreachable() into a callback. Closes ticket 16762.
12150 - Treat the loss of an owning controller as equivalent to a SIGTERM
12151 signal. This removes a tiny amount of duplicated code, and
12152 simplifies our callgraph. Closes ticket 16788.
12153 - When generating an event to send to the controller, we no longer
12154 put the event over the network immediately. Instead, we queue
12155 these events, and use a Libevent callback to deliver them. This
12156 change simplifies Tor's callgraph by reducing the number of
12157 functions from which all other Tor functions are reachable. Closes
12159 - Wrap Windows-only C files inside '#ifdef _WIN32' so that tools
12160 that try to scan or compile every file on Unix won't decide that
12162 - Remove the unused "nulterminate" argument from buf_pullup().
12165 - Recommend a 40 GB example AccountingMax in torrc.sample rather
12166 than a 4 GB max. Closes ticket 16742.
12167 - Include the TUNING document in our source tarball. It is referred
12168 to in the ChangeLog and an error message. Fixes bug 16929; bugfix
12172 - The internal pure-C tor-fw-helper tool is now removed from the Tor
12173 distribution, in favor of the pure-Go clone available from
12174 https://gitweb.torproject.org/tor-fw-helper.git/ . The libraries
12175 used by the C tor-fw-helper are not, in our opinion, very
12176 confidence- inspiring in their secure-programming techniques.
12177 Closes ticket 13338.
12178 - Remove the code that would try to aggressively flush controller
12179 connections while writing to them. This code was introduced in
12180 0.1.2.7-alpha, in order to keep output buffers from exceeding
12181 their limits. But there is no longer a maximum output buffer size,
12182 and flushing data in this way caused some undesirable recursions
12183 in our call graph. Closes ticket 16480.
12186 - Make "bridges+hs" the default test network. This tests almost all
12187 tor functionality during make test-network, while allowing tests
12188 to succeed on non-IPv6 systems. Requires chutney commit 396da92 in
12189 test-network-bridges-hs. Closes tickets 16945 (tor) and 16946
12190 (chutney). Patches by "teor".
12191 - Autodetect CHUTNEY_PATH if the chutney and Tor sources are side-
12192 by-side in the same parent directory. Closes ticket 16903. Patch
12194 - Use environment variables rather than autoconf substitutions to
12195 send variables from the build system to the test scripts. This
12196 change should be easier to maintain, and cause 'make distcheck' to
12197 work better than before. Fixes bug 17148.
12198 - Add a new set of callgraph analysis scripts that use clang to
12199 produce a list of which Tor functions are reachable from which
12200 other Tor functions. We're planning to use these to help simplify
12201 our code structure by identifying illogical dependencies.
12202 - Add new 'test-full' and 'test-full-online' targets to run all
12203 tests, including integration tests with stem and chutney.
12204 - Make the test-workqueue test work on Windows by initializing the
12205 network before we begin.
12206 - New make target (make test-network-all) to run multiple applicable
12207 chutney test cases. Patch from Teor; closes 16953.
12208 - Unit test dns_resolve(), dns_clip_ttl() and dns_get_expiry_ttl()
12209 functions in dns.c. Implements a portion of ticket 16831.
12210 - When building Tor with testing coverage enabled, run Chutney tests
12211 (if any) using the 'tor-cov' coverage binary.
12212 - When running test-network or test-stem, check for the absence of
12213 stem/chutney before doing any build operations.
12216 Changes in version 0.2.7.2-alpha - 2015-07-27
12217 This, the second alpha in the Tor 0.2.7 series, has a number of new
12218 features, including a way to manually pick the number of introduction
12219 points for hidden services, and the much stronger Ed25519 signing key
12220 algorithm for regular Tor relays (including support for encrypted
12221 offline identity keys in the new algorithm).
12223 Support for Ed25519 on relays is currently limited to signing router
12224 descriptors; later alphas in this series will extend Ed25519 key
12225 support to more parts of the Tor protocol.
12227 o Major features (Ed25519 identity keys, Proposal 220):
12228 - All relays now maintain a stronger identity key, using the Ed25519
12229 elliptic curve signature format. This master key is designed so
12230 that it can be kept offline. Relays also generate an online
12231 signing key, and a set of other Ed25519 keys and certificates.
12232 These are all automatically regenerated and rotated as needed.
12233 Implements part of ticket 12498.
12234 - Directory authorities now vote on Ed25519 identity keys along with
12235 RSA1024 keys. Implements part of ticket 12498.
12236 - Directory authorities track which Ed25519 identity keys have been
12237 used with which RSA1024 identity keys, and do not allow them to
12238 vary freely. Implements part of ticket 12498.
12239 - Microdescriptors now include Ed25519 identity keys. Implements
12240 part of ticket 12498.
12241 - Add support for offline encrypted Ed25519 master keys. To use this
12242 feature on your tor relay, run "tor --keygen" to make a new master
12243 key (or to make a new signing key if you already have a master
12244 key). Closes ticket 13642.
12246 o Major features (Hidden services):
12247 - Add the torrc option HiddenServiceNumIntroductionPoints, to
12248 specify a fixed number of introduction points. Its maximum value
12249 is 10 and default is 3. Using this option can increase a hidden
12250 service's reliability under load, at the cost of making it more
12251 visible that the hidden service is facing extra load. Closes
12253 - Remove the adaptive algorithm for choosing the number of
12254 introduction points, which used to change the number of
12255 introduction points (poorly) depending on the number of
12256 connections the HS sees. Closes ticket 4862.
12258 o Major features (onion key cross-certification):
12259 - Relay descriptors now include signatures of their own identity
12260 keys, made using the TAP and ntor onion keys. These signatures
12261 allow relays to prove ownership of their own onion keys. Because
12262 of this change, microdescriptors will no longer need to include
12263 RSA identity keys. Implements proposal 228; closes ticket 12499.
12265 o Major features (performance):
12266 - Improve the runtime speed of Ed25519 operations by using the
12267 public-domain Ed25519-donna by Andrew M. ("floodyberry").
12268 Implements ticket 16467.
12269 - Improve the runtime speed of the ntor handshake by using an
12270 optimized curve25519 basepoint scalarmult implementation from the
12271 public-domain Ed25519-donna by Andrew M. ("floodyberry"), based on
12272 ideas by Adam Langley. Implements ticket 9663.
12274 o Major bugfixes (client-side privacy, also in 0.2.6.9):
12275 - Properly separate out each SOCKSPort when applying stream
12276 isolation. The error occurred because each port's session group
12277 was being overwritten by a default value when the listener
12278 connection was initialized. Fixes bug 16247; bugfix on
12279 0.2.6.3-alpha. Patch by "jojelino".
12281 o Major bugfixes (hidden service clients, stability, also in 0.2.6.10):
12282 - Stop refusing to store updated hidden service descriptors on a
12283 client. This reverts commit 9407040c59218 (which indeed fixed bug
12284 14219, but introduced a major hidden service reachability
12285 regression detailed in bug 16381). This is a temporary fix since
12286 we can live with the minor issue in bug 14219 (it just results in
12287 some load on the network) but the regression of 16381 is too much
12288 of a setback. First-round fix for bug 16381; bugfix
12291 o Major bugfixes (hidden services):
12292 - When cannibalizing a circuit for an introduction point, always
12293 extend to the chosen exit node (creating a 4 hop circuit).
12294 Previously Tor would use the current circuit exit node, which
12295 changed the original choice of introduction point, and could cause
12296 the hidden service to skip excluded introduction points or
12297 reconnect to a skipped introduction point. Fixes bug 16260; bugfix
12300 o Major bugfixes (open file limit):
12301 - The open file limit wasn't checked before calling
12302 tor_accept_socket_nonblocking(), which would make Tor exceed the
12303 limit. Now, before opening a new socket, Tor validates the open
12304 file limit just before, and if the max has been reached, return an
12305 error. Fixes bug 16288; bugfix on 0.1.1.1-alpha.
12307 o Major bugfixes (stability, also in 0.2.6.10):
12308 - Stop crashing with an assertion failure when parsing certain kinds
12309 of malformed or truncated microdescriptors. Fixes bug 16400;
12310 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
12311 by "cypherpunks_backup".
12312 - Stop random client-side assertion failures that could occur when
12313 connecting to a busy hidden service, or connecting to a hidden
12314 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
12317 o Minor features (directory authorities, security, also in 0.2.6.9):
12318 - The HSDir flag given by authorities now requires the Stable flag.
12319 For the current network, this results in going from 2887 to 2806
12320 HSDirs. Also, it makes it harder for an attacker to launch a sybil
12321 attack by raising the effort for a relay to become Stable to
12322 require at the very least 7 days, while maintaining the 96 hours
12323 uptime requirement for HSDir. Implements ticket 8243.
12325 o Minor features (client):
12326 - Relax the validation of hostnames in SOCKS5 requests, allowing the
12327 character '_' to appear, in order to cope with domains observed in
12328 the wild that are serving non-RFC compliant records. Resolves
12330 - Relax the validation done to hostnames in SOCKS5 requests, and
12331 allow a single trailing '.' to cope with clients that pass FQDNs
12332 using that syntax to explicitly indicate that the domain name is
12333 fully-qualified. Fixes bug 16674; bugfix on 0.2.6.2-alpha.
12334 - Add GroupWritable and WorldWritable options to unix-socket based
12335 SocksPort and ControlPort options. These options apply to a single
12336 socket, and override {Control,Socks}SocketsGroupWritable. Closes
12339 o Minor features (control protocol):
12340 - Support network-liveness GETINFO key and NETWORK_LIVENESS event in
12341 the control protocol. Resolves ticket 15358.
12343 o Minor features (directory authorities):
12344 - Directory authorities no longer vote against the "Fast", "Stable",
12345 and "HSDir" flags just because they were going to vote against
12346 "Running": if the consensus turns out to be that the router was
12347 running, then the authority's vote should count. Patch from Peter
12348 Retzlaff; closes issue 8712.
12350 o Minor features (geoip, also in 0.2.6.10):
12351 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
12352 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
12354 o Minor features (hidden services):
12355 - Add the new options "HiddenServiceMaxStreams" and
12356 "HiddenServiceMaxStreamsCloseCircuit" to allow hidden services to
12357 limit the maximum number of simultaneous streams per circuit, and
12358 optionally tear down the circuit when the limit is exceeded. Part
12361 o Minor features (portability):
12362 - Use C99 variadic macros when the compiler is not GCC. This avoids
12363 failing compilations on MSVC, and fixes a log-file-based race
12364 condition in our old workarounds. Original patch from Gisle Vanem.
12366 o Minor bugfixes (compilation, also in 0.2.6.9):
12367 - Build with --enable-systemd correctly when libsystemd is
12368 installed, but systemd is not. Fixes bug 16164; bugfix on
12369 0.2.6.3-alpha. Patch from Peter Palfrader.
12371 o Minor bugfixes (controller):
12372 - Add the descriptor ID in each HS_DESC control event. It was
12373 missing, but specified in control-spec.txt. Fixes bug 15881;
12374 bugfix on 0.2.5.2-alpha.
12376 o Minor bugfixes (crypto error-handling, also in 0.2.6.10):
12377 - Check for failures from crypto_early_init, and refuse to continue.
12378 A previous typo meant that we could keep going with an
12379 uninitialized crypto library, and would have OpenSSL initialize
12380 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
12381 when implementing ticket 4900. Patch by "teor".
12383 o Minor bugfixes (hidden services):
12384 - Fix a crash when reloading configuration while at least one
12385 configured and one ephemeral hidden service exists. Fixes bug
12386 16060; bugfix on 0.2.7.1-alpha.
12387 - Avoid crashing with a double-free bug when we create an ephemeral
12388 hidden service but adding it fails for some reason. Fixes bug
12389 16228; bugfix on 0.2.7.1-alpha.
12391 o Minor bugfixes (Linux seccomp2 sandbox):
12392 - Use the sandbox in tor_open_cloexec whether or not O_CLOEXEC is
12393 defined. Patch by "teor". Fixes bug 16515; bugfix on 0.2.3.1-alpha.
12395 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.10):
12396 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
12397 these when eventfd2() support is missing. Fixes bug 16363; bugfix
12398 on 0.2.6.3-alpha. Patch from "teor".
12400 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.9):
12401 - Fix sandboxing to work when running as a relay, by allowing the
12402 renaming of secret_id_key, and allowing the eventfd2 and futex
12403 syscalls. Fixes bug 16244; bugfix on 0.2.6.1-alpha. Patch by
12405 - Allow systemd connections to work with the Linux seccomp2 sandbox
12406 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
12409 o Minor bugfixes (relay):
12410 - Fix a rarely-encountered memory leak when failing to initialize
12411 the thread pool. Fixes bug 16631; bugfix on 0.2.6.3-alpha. Patch
12412 from "cypherpunks".
12414 o Minor bugfixes (systemd):
12415 - Fix an accidental formatting error that broke the systemd
12416 configuration file. Fixes bug 16152; bugfix on 0.2.7.1-alpha.
12417 - Tor's systemd unit file no longer contains extraneous spaces.
12418 These spaces would sometimes confuse tools like deb-systemd-
12419 helper. Fixes bug 16162; bugfix on 0.2.5.5-alpha.
12421 o Minor bugfixes (tests):
12422 - Use the configured Python executable when running test-stem-full.
12423 Fixes bug 16470; bugfix on 0.2.7.1-alpha.
12425 o Minor bugfixes (tests, also in 0.2.6.9):
12426 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
12427 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
12429 o Minor bugfixes (threads, comments):
12430 - Always initialize return value in compute_desc_id in rendcommon.c
12431 Patch by "teor". Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
12432 - Check for NULL values in getinfo_helper_onions(). Patch by "teor".
12433 Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
12434 - Remove undefined directive-in-macro in test_util_writepid clang
12435 3.7 complains that using a preprocessor directive inside a macro
12436 invocation in test_util_writepid in test_util.c is undefined.
12437 Patch by "teor". Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
12439 o Code simplification and refactoring:
12440 - Define WINVER and _WIN32_WINNT centrally, in orconfig.h, in order
12441 to ensure they remain consistent and visible everywhere.
12442 - Remove some vestigial workarounds for the MSVC6 compiler. We
12443 haven't supported that in ages.
12444 - The link authentication code has been refactored for better
12445 testability and reliability. It now uses code generated with the
12446 "trunnel" binary encoding generator, to reduce the risk of bugs
12447 due to programmer error. Done as part of ticket 12498.
12450 - Include a specific and (hopefully) accurate documentation of the
12451 torrc file's meta-format in doc/torrc_format.txt. This is mainly
12452 of interest to people writing programs to parse or generate torrc
12453 files. This document is not a commitment to long-term
12454 compatibility; some aspects of the current format are a bit
12455 ridiculous. Closes ticket 2325.
12457 o Removed features:
12458 - Tor no longer supports copies of OpenSSL that are missing support
12459 for Elliptic Curve Cryptography. (We began using ECC when
12460 available in 0.2.4.8-alpha, for more safe and efficient key
12461 negotiation.) In particular, support for at least one of P256 or
12462 P224 is now required, with manual configuration needed if only
12463 P224 is available. Resolves ticket 16140.
12464 - Tor no longer supports versions of OpenSSL before 1.0. (If you are
12465 on an operating system that has not upgraded to OpenSSL 1.0 or
12466 later, and you compile Tor from source, you will need to install a
12467 more recent OpenSSL to link Tor against.) These versions of
12468 OpenSSL are still supported by the OpenSSL, but the numerous
12469 cryptographic improvements in later OpenSSL releases makes them a
12470 clear choice. Resolves ticket 16034.
12471 - Remove the HidServDirectoryV2 option. Now all relays offer to
12472 store hidden service descriptors. Related to 16543.
12473 - Remove the VoteOnHidServDirectoriesV2 option, since all
12474 authorities have long set it to 1. Closes ticket 16543.
12477 - Document use of coverity, clang static analyzer, and clang dynamic
12478 undefined behavior and address sanitizers in doc/HACKING. Include
12479 detailed usage instructions in the blacklist. Patch by "teor".
12480 Closes ticket 15817.
12481 - The link authentication protocol code now has extensive tests.
12482 - The relay descriptor signature testing code now has
12484 - The test_workqueue program now runs faster, and is enabled by
12485 default as a part of "make check".
12486 - Now that OpenSSL has its own scrypt implementation, add an unit
12487 test that checks for interoperability between libscrypt_scrypt()
12488 and OpenSSL's EVP_PBE_scrypt() so that we could not use libscrypt
12489 and rely on EVP_PBE_scrypt() whenever possible. Resolves
12493 Changes in version 0.2.6.10 - 2015-07-12
12494 Tor version 0.2.6.10 fixes some significant stability and hidden
12495 service client bugs, bulletproofs the cryptography init process, and
12496 fixes a bug when using the sandbox code with some older versions of
12497 Linux. Everyone running an older version, especially an older version
12498 of 0.2.6, should upgrade.
12500 o Major bugfixes (hidden service clients, stability):
12501 - Stop refusing to store updated hidden service descriptors on a
12502 client. This reverts commit 9407040c59218 (which indeed fixed bug
12503 14219, but introduced a major hidden service reachability
12504 regression detailed in bug 16381). This is a temporary fix since
12505 we can live with the minor issue in bug 14219 (it just results in
12506 some load on the network) but the regression of 16381 is too much
12507 of a setback. First-round fix for bug 16381; bugfix
12510 o Major bugfixes (stability):
12511 - Stop crashing with an assertion failure when parsing certain kinds
12512 of malformed or truncated microdescriptors. Fixes bug 16400;
12513 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
12514 by "cypherpunks_backup".
12515 - Stop random client-side assertion failures that could occur when
12516 connecting to a busy hidden service, or connecting to a hidden
12517 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
12520 o Minor features (geoip):
12521 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
12522 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
12524 o Minor bugfixes (crypto error-handling):
12525 - Check for failures from crypto_early_init, and refuse to continue.
12526 A previous typo meant that we could keep going with an
12527 uninitialized crypto library, and would have OpenSSL initialize
12528 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
12529 when implementing ticket 4900. Patch by "teor".
12531 o Minor bugfixes (Linux seccomp2 sandbox):
12532 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
12533 these when eventfd2() support is missing. Fixes bug 16363; bugfix
12534 on 0.2.6.3-alpha. Patch from "teor".
12537 Changes in version 0.2.6.9 - 2015-06-11
12538 Tor 0.2.6.9 fixes a regression in the circuit isolation code, increases the
12539 requirements for receiving an HSDir flag, and addresses some other small
12540 bugs in the systemd and sandbox code. Clients using circuit isolation
12541 should upgrade; all directory authorities should upgrade.
12543 o Major bugfixes (client-side privacy):
12544 - Properly separate out each SOCKSPort when applying stream
12545 isolation. The error occurred because each port's session group was
12546 being overwritten by a default value when the listener connection
12547 was initialized. Fixes bug 16247; bugfix on 0.2.6.3-alpha. Patch
12550 o Minor feature (directory authorities, security):
12551 - The HSDir flag given by authorities now requires the Stable flag.
12552 For the current network, this results in going from 2887 to 2806
12553 HSDirs. Also, it makes it harder for an attacker to launch a sybil
12554 attack by raising the effort for a relay to become Stable which
12555 takes at the very least 7 days to do so and by keeping the 96
12556 hours uptime requirement for HSDir. Implements ticket 8243.
12558 o Minor bugfixes (compilation):
12559 - Build with --enable-systemd correctly when libsystemd is
12560 installed, but systemd is not. Fixes bug 16164; bugfix on
12561 0.2.6.3-alpha. Patch from Peter Palfrader.
12563 o Minor bugfixes (Linux seccomp2 sandbox):
12564 - Fix sandboxing to work when running as a relaymby renaming of
12565 secret_id_key, and allowing the eventfd2 and futex syscalls. Fixes
12566 bug 16244; bugfix on 0.2.6.1-alpha. Patch by Peter Palfrader.
12567 - Allow systemd connections to work with the Linux seccomp2 sandbox
12568 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
12571 o Minor bugfixes (tests):
12572 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
12573 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
12576 Changes in version 0.2.6.8 - 2015-05-21
12577 Tor 0.2.6.8 fixes a bit of dodgy code in parsing INTRODUCE2 cells, and
12578 fixes an authority-side bug in assigning the HSDir flag. All directory
12579 authorities should upgrade.
12581 o Major bugfixes (hidden services, backport from 0.2.7.1-alpha):
12582 - Revert commit that made directory authorities assign the HSDir
12583 flag to relays without a DirPort; this was bad because such relays
12584 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
12587 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
12588 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
12589 a client authorized hidden service. Fixes bug 15823; bugfix
12592 o Minor features (geoip):
12593 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
12594 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
12598 Changes in version 0.2.7.1-alpha - 2015-05-12
12599 Tor 0.2.7.1-alpha is the first alpha release in its series. It
12600 includes numerous small features and bugfixes against previous Tor
12601 versions, and numerous small infrastructure improvements. The most
12602 notable features are several new ways for controllers to interact with
12603 the hidden services subsystem.
12605 o New system requirements:
12606 - Tor no longer includes workarounds to support Libevent versions
12607 before 1.3e. Libevent 2.0 or later is recommended. Closes
12610 o Major features (controller):
12611 - Add the ADD_ONION and DEL_ONION commands that allow the creation
12612 and management of hidden services via the controller. Closes
12614 - New "GETINFO onions/current" and "GETINFO onions/detached"
12615 commands to get information about hidden services created via the
12616 controller. Part of ticket 6411.
12617 - New HSFETCH command to launch a request for a hidden service
12618 descriptor. Closes ticket 14847.
12619 - New HSPOST command to upload a hidden service descriptor. Closes
12620 ticket 3523. Patch by "DonnchaC".
12622 o Major bugfixes (hidden services):
12623 - Revert commit that made directory authorities assign the HSDir
12624 flag to relays without a DirPort; this was bad because such relays
12625 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
12628 o Minor features (clock-jump tolerance):
12629 - Recover better when our clock jumps back many hours, like might
12630 happen for Tails or Whonix users who start with a very wrong
12631 hardware clock, use Tor to discover a more accurate time, and then
12632 fix their clock. Resolves part of ticket 8766.
12634 o Minor features (command-line interface):
12635 - Make --hash-password imply --hush to prevent unnecessary noise.
12636 Closes ticket 15542. Patch from "cypherpunks".
12637 - Print a warning whenever we find a relative file path being used
12638 as torrc option. Resolves issue 14018.
12640 o Minor features (controller):
12641 - Add DirAuthority lines for default directory authorities to the
12642 output of the "GETINFO config/defaults" command if not already
12643 present. Implements ticket 14840.
12644 - Controllers can now use "GETINFO hs/client/desc/id/..." to
12645 retrieve items from the client's hidden service descriptor cache.
12646 Closes ticket 14845.
12647 - Implement a new controller command "GETINFO status/fresh-relay-
12648 descs" to fetch a descriptor/extrainfo pair that was generated on
12649 demand just for the controller's use. Implements ticket 14784.
12651 o Minor features (DoS-resistance):
12652 - Make it harder for attackers to overload hidden services with
12653 introductions, by blocking multiple introduction requests on the
12654 same circuit. Resolves ticket 15515.
12656 o Minor features (geoip):
12657 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
12658 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
12661 o Minor features (HS popularity countermeasure):
12662 - To avoid leaking HS popularity, don't cycle the introduction point
12663 when we've handled a fixed number of INTRODUCE2 cells but instead
12664 cycle it when a random number of introductions is reached, thus
12665 making it more difficult for an attacker to find out the amount of
12666 clients that have used the introduction point for a specific HS.
12667 Closes ticket 15745.
12669 o Minor features (logging):
12670 - Include the Tor version in all LD_BUG log messages, since people
12671 tend to cut and paste those into the bugtracker. Implements
12674 o Minor features (pluggable transports):
12675 - When launching managed pluggable transports on Linux systems,
12676 attempt to have the kernel deliver a SIGTERM on tor exit if the
12677 pluggable transport process is still running. Resolves
12679 - When launching managed pluggable transports, setup a valid open
12680 stdin in the child process that can be used to detect if tor has
12681 terminated. The "TOR_PT_EXIT_ON_STDIN_CLOSE" environment variable
12682 can be used by implementations to detect this new behavior.
12683 Resolves ticket 15435.
12685 o Minor features (testing):
12686 - Add a test to verify that the compiler does not eliminate our
12687 memwipe() implementation. Closes ticket 15377.
12688 - Add make rule `check-changes` to verify the format of changes
12689 files. Closes ticket 15180.
12690 - Add unit tests for control_event_is_interesting(). Add a compile-
12691 time check that the number of events doesn't exceed the capacity
12692 of control_event_t.event_mask. Closes ticket 15431, checks for
12693 bugs similar to 13085. Patch by "teor".
12694 - Command-line argument tests moved to Stem. Resolves ticket 14806.
12695 - Integrate the ntor, backtrace, and zero-length keys tests into the
12696 automake test suite. Closes ticket 15344.
12697 - Remove assertions during builds to determine Tor's test coverage.
12698 We don't want to trigger these even in assertions, so including
12699 them artificially makes our branch coverage look worse than it is.
12700 This patch provides the new test-stem-full and coverage-html-full
12701 configure options. Implements ticket 15400.
12703 o Minor bugfixes (build):
12704 - Improve out-of-tree builds by making non-standard rules work and
12705 clean up additional files and directories. Fixes bug 15053; bugfix
12708 o Minor bugfixes (command-line interface):
12709 - When "--quiet" is provided along with "--validate-config", do not
12710 write anything to stdout on success. Fixes bug 14994; bugfix
12712 - When complaining about bad arguments to "--dump-config", use
12713 stderr, not stdout.
12715 o Minor bugfixes (configuration, unit tests):
12716 - Only add the default fallback directories when the DirAuthorities,
12717 AlternateDirAuthority, and FallbackDir directory config options
12718 are set to their defaults. The default fallback directory list is
12719 currently empty, this fix will only change tor's behavior when it
12720 has default fallback directories. Includes unit tests for
12721 consider_adding_dir_servers(). Fixes bug 15642; bugfix on
12722 90f6071d8dc0 in 0.2.4.7-alpha. Patch by "teor".
12724 o Minor bugfixes (correctness):
12725 - For correctness, avoid modifying a constant string in
12726 handle_control_postdescriptor. Fixes bug 15546; bugfix
12728 - Remove side-effects from tor_assert() calls. This was harmless,
12729 because we never disable assertions, but it is bad style and
12730 unnecessary. Fixes bug 15211; bugfix on 0.2.5.5, 0.2.2.36,
12733 o Minor bugfixes (hidden service):
12734 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
12735 a client authorized hidden service. Fixes bug 15823; bugfix
12737 - Remove an extraneous newline character from the end of hidden
12738 service descriptors. Fixes bug 15296; bugfix on 0.2.0.10-alpha.
12740 o Minor bugfixes (interface):
12741 - Print usage information for --dump-config when it is used without
12742 an argument. Also, fix the error message to use different wording
12743 and add newline at the end. Fixes bug 15541; bugfix
12746 o Minor bugfixes (logs):
12747 - When building Tor under Clang, do not include an extra set of
12748 parentheses in log messages that include function names. Fixes bug
12749 15269; bugfix on every released version of Tor when compiled with
12750 recent enough Clang.
12752 o Minor bugfixes (network):
12753 - When attempting to use fallback technique for network interface
12754 lookup, disregard loopback and multicast addresses since they are
12755 unsuitable for public communications.
12757 o Minor bugfixes (statistics):
12758 - Disregard the ConnDirectionStatistics torrc options when Tor is
12759 not a relay since in that mode of operation no sensible data is
12760 being collected and because Tor might run into measurement hiccups
12761 when running as a client for some time, then becoming a relay.
12762 Fixes bug 15604; bugfix on 0.2.2.35.
12764 o Minor bugfixes (test networks):
12765 - When self-testing reachability, use ExtendAllowPrivateAddresses to
12766 determine if local/private addresses imply reachability. The
12767 previous fix used TestingTorNetwork, which implies
12768 ExtendAllowPrivateAddresses, but this excluded rare configurations
12769 where ExtendAllowPrivateAddresses is set but TestingTorNetwork is
12770 not. Fixes bug 15771; bugfix on 0.2.6.1-alpha. Patch by "teor",
12771 issue discovered by CJ Ess.
12773 o Minor bugfixes (testing):
12774 - Check for matching value in server response in ntor_ref.py. Fixes
12775 bug 15591; bugfix on 0.2.4.8-alpha. Reported and fixed
12777 - Set the severity correctly when testing
12778 get_interface_addresses_ifaddrs() and
12779 get_interface_addresses_win32(), so that the tests fail gracefully
12780 instead of triggering an assertion. Fixes bug 15759; bugfix on
12781 0.2.6.3-alpha. Reported by Nicolas Derive.
12783 o Code simplification and refactoring:
12784 - Move the hacky fallback code out of get_interface_address6() into
12785 separate function and get it covered with unit-tests. Resolves
12787 - Refactor hidden service client-side cache lookup to intelligently
12788 report its various failure cases, and disentangle failure cases
12789 involving a lack of introduction points. Closes ticket 14391.
12790 - Use our own Base64 encoder instead of OpenSSL's, to allow more
12791 control over the output. Part of ticket 15652.
12794 - Improve the descriptions of statistics-related torrc options in
12795 the manpage to describe rationale and possible uses cases. Fixes
12797 - Improve the layout and formatting of ./configure --help messages.
12798 Closes ticket 15024. Patch from "cypherpunks".
12799 - Standardize on the term "server descriptor" in the manual page.
12800 Previously, we had used "router descriptor", "server descriptor",
12801 and "relay descriptor" interchangeably. Part of ticket 14987.
12804 - Remove `USE_OPENSSL_BASE64` and the corresponding fallback code
12805 and always use the internal Base64 decoder. The internal decoder
12806 has been part of tor since 0.2.0.10-alpha, and no one should
12807 be using the OpenSSL one. Part of ticket 15652.
12808 - Remove the 'tor_strclear()' function; use memwipe() instead.
12809 Closes ticket 14922.
12811 o Removed features:
12812 - Remove the (seldom-used) DynamicDHGroups feature. For anti-
12813 fingerprinting we now recommend pluggable transports; for forward-
12814 secrecy in TLS, we now use the P-256 group. Closes ticket 13736.
12815 - Remove the undocumented "--digests" command-line option. It
12816 complicated our build process, caused subtle build issues on
12817 multiple platforms, and is now redundant since we started
12818 including git version identifiers. Closes ticket 14742.
12819 - Tor no longer contains checks for ancient directory cache versions
12820 that didn't know about microdescriptors.
12821 - Tor no longer contains workarounds for stat files generated by
12822 super-old versions of Tor that didn't choose guards sensibly.
12825 Changes in version 0.2.4.27 - 2015-04-06
12826 Tor 0.2.4.27 backports two fixes from 0.2.6.7 for security issues that
12827 could be used by an attacker to crash hidden services, or crash clients
12828 visiting hidden services. Hidden services should upgrade as soon as
12829 possible; clients should upgrade whenever packages become available.
12831 This release also backports a simple improvement to make hidden
12832 services a bit less vulnerable to denial-of-service attacks.
12834 o Major bugfixes (security, hidden service):
12835 - Fix an issue that would allow a malicious client to trigger an
12836 assertion failure and halt a hidden service. Fixes bug 15600;
12837 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
12838 - Fix a bug that could cause a client to crash with an assertion
12839 failure when parsing a malformed hidden service descriptor. Fixes
12840 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
12842 o Minor features (DoS-resistance, hidden service):
12843 - Introduction points no longer allow multiple INTRODUCE1 cells to
12844 arrive on the same circuit. This should make it more expensive for
12845 attackers to overwhelm hidden services with introductions.
12846 Resolves ticket 15515.
12849 Changes in version 0.2.5.12 - 2015-04-06
12850 Tor 0.2.5.12 backports two fixes from 0.2.6.7 for security issues that
12851 could be used by an attacker to crash hidden services, or crash clients
12852 visiting hidden services. Hidden services should upgrade as soon as
12853 possible; clients should upgrade whenever packages become available.
12855 This release also backports a simple improvement to make hidden
12856 services a bit less vulnerable to denial-of-service attacks.
12858 o Major bugfixes (security, hidden service):
12859 - Fix an issue that would allow a malicious client to trigger an
12860 assertion failure and halt a hidden service. Fixes bug 15600;
12861 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
12862 - Fix a bug that could cause a client to crash with an assertion
12863 failure when parsing a malformed hidden service descriptor. Fixes
12864 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
12866 o Minor features (DoS-resistance, hidden service):
12867 - Introduction points no longer allow multiple INTRODUCE1 cells to
12868 arrive on the same circuit. This should make it more expensive for
12869 attackers to overwhelm hidden services with introductions.
12870 Resolves ticket 15515.
12873 Changes in version 0.2.6.7 - 2015-04-06
12874 Tor 0.2.6.7 fixes two security issues that could be used by an
12875 attacker to crash hidden services, or crash clients visiting hidden
12876 services. Hidden services should upgrade as soon as possible; clients
12877 should upgrade whenever packages become available.
12879 This release also contains two simple improvements to make hidden
12880 services a bit less vulnerable to denial-of-service attacks.
12882 o Major bugfixes (security, hidden service):
12883 - Fix an issue that would allow a malicious client to trigger an
12884 assertion failure and halt a hidden service. Fixes bug 15600;
12885 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
12886 - Fix a bug that could cause a client to crash with an assertion
12887 failure when parsing a malformed hidden service descriptor. Fixes
12888 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
12890 o Minor features (DoS-resistance, hidden service):
12891 - Introduction points no longer allow multiple INTRODUCE1 cells to
12892 arrive on the same circuit. This should make it more expensive for
12893 attackers to overwhelm hidden services with introductions.
12894 Resolves ticket 15515.
12895 - Decrease the amount of reattempts that a hidden service performs
12896 when its rendezvous circuits fail. This reduces the computational
12897 cost for running a hidden service under heavy load. Resolves
12901 Changes in version 0.2.6.6 - 2015-03-24
12902 Tor 0.2.6.6 is the first stable release in the 0.2.6 series.
12904 It adds numerous safety, security, correctness, and performance
12905 improvements. Client programs can be configured to use more kinds of
12906 sockets, AutomapHosts works better, the multithreading backend is
12907 improved, cell transmission is refactored, test coverage is much
12908 higher, more denial-of-service attacks are handled, guard selection is
12909 improved to handle long-term guards better, pluggable transports
12910 should work a bit better, and some annoying hidden service performance
12911 bugs should be addressed.
12913 o Minor bugfixes (portability):
12914 - Use the correct datatype in the SipHash-2-4 function to prevent
12915 compilers from assuming any sort of alignment. Fixes bug 15436;
12916 bugfix on 0.2.5.3-alpha.
12918 Changes in version 0.2.6.5-rc - 2015-03-18
12919 Tor 0.2.6.5-rc is the second and (hopefully) last release candidate in
12920 the 0.2.6. It fixes a small number of bugs found in 0.2.6.4-rc.
12922 o Major bugfixes (client):
12923 - Avoid crashing when making certain configuration option changes on
12924 clients. Fixes bug 15245; bugfix on 0.2.6.3-alpha. Reported
12927 o Major bugfixes (pluggable transports):
12928 - Initialize the extended OR Port authentication cookie before
12929 launching pluggable transports. This prevents a race condition
12930 that occurred when server-side pluggable transports would cache the
12931 authentication cookie before it has been (re)generated. Fixes bug
12932 15240; bugfix on 0.2.5.1-alpha.
12934 o Major bugfixes (portability):
12935 - Do not crash on startup when running on Solaris. Fixes a bug
12936 related to our fix for 9495; bugfix on 0.2.6.1-alpha. Reported
12939 o Minor features (heartbeat):
12940 - On relays, report how many connections we negotiated using each
12941 version of the Tor link protocols. This information will let us
12942 know if removing support for very old versions of the Tor
12943 protocols is harming the network. Closes ticket 15212.
12945 o Code simplification and refactoring:
12946 - Refactor main loop to extract the 'loop' part. This makes it
12947 easier to run Tor under Shadow. Closes ticket 15176.
12950 Changes in version 0.2.5.11 - 2015-03-17
12951 Tor 0.2.5.11 is the second stable release in the 0.2.5 series.
12953 It backports several bugfixes from the 0.2.6 branch, including a
12954 couple of medium-level security fixes for relays and exit nodes.
12955 It also updates the list of directory authorities.
12957 o Directory authority changes:
12958 - Remove turtles as a directory authority.
12959 - Add longclaw as a new (v3) directory authority. This implements
12960 ticket 13296. This keeps the directory authority count at 9.
12961 - The directory authority Faravahar has a new IP address. This
12962 closes ticket 14487.
12964 o Major bugfixes (crash, OSX, security):
12965 - Fix a remote denial-of-service opportunity caused by a bug in
12966 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
12969 o Major bugfixes (relay, stability, possible security):
12970 - Fix a bug that could lead to a relay crashing with an assertion
12971 failure if a buffer of exactly the wrong layout was passed to
12972 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
12973 0.2.0.10-alpha. Patch from 'cypherpunks'.
12974 - Do not assert if the 'data' pointer on a buffer is advanced to the
12975 very end of the buffer; log a BUG message instead. Only assert if
12976 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
12978 o Major bugfixes (exit node stability):
12979 - Fix an assertion failure that could occur under high DNS load.
12980 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
12981 diagnosed and fixed by "cypherpunks".
12983 o Major bugfixes (Linux seccomp2 sandbox):
12984 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
12985 crash during attempts to call wait4. Fixes bug 15088; bugfix on
12986 0.2.5.1-alpha. Patch from "sanic".
12988 o Minor features (controller):
12989 - New "GETINFO bw-event-cache" to get information about recent
12990 bandwidth events. Closes ticket 14128. Useful for controllers to
12991 get recent bandwidth history after the fix for ticket 13988.
12993 o Minor features (geoip):
12994 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
12995 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
12998 o Minor bugfixes (client, automapping):
12999 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
13000 no value follows the option. Fixes bug 14142; bugfix on
13001 0.2.4.7-alpha. Patch by "teor".
13002 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
13003 14195; bugfix on 0.1.0.1-rc.
13005 o Minor bugfixes (compilation):
13006 - Build without warnings with the stock OpenSSL srtp.h header, which
13007 has a duplicate declaration of SSL_get_selected_srtp_profile().
13008 Fixes bug 14220; this is OpenSSL's bug, not ours.
13010 o Minor bugfixes (directory authority):
13011 - Allow directory authorities to fetch more data from one another if
13012 they find themselves missing lots of votes. Previously, they had
13013 been bumping against the 10 MB queued data limit. Fixes bug 14261;
13014 bugfix on 0.1.2.5-alpha.
13015 - Enlarge the buffer to read bwauth generated files to avoid an
13016 issue when parsing the file in dirserv_read_measured_bandwidths().
13017 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
13019 o Minor bugfixes (statistics):
13020 - Increase period over which bandwidth observations are aggregated
13021 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
13023 o Minor bugfixes (preventative security, C safety):
13024 - When reading a hexadecimal, base-32, or base-64 encoded value from
13025 a string, always overwrite the whole output buffer. This prevents
13026 some bugs where we would look at (but fortunately, not reveal)
13027 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
13031 Changes in version 0.2.4.26 - 2015-03-17
13032 Tor 0.2.4.26 includes an updated list of directory authorities. It
13033 also backports a couple of stability and security bugfixes from 0.2.5
13036 o Directory authority changes:
13037 - Remove turtles as a directory authority.
13038 - Add longclaw as a new (v3) directory authority. This implements
13039 ticket 13296. This keeps the directory authority count at 9.
13040 - The directory authority Faravahar has a new IP address. This
13041 closes ticket 14487.
13043 o Major bugfixes (exit node stability, also in 0.2.6.3-alpha):
13044 - Fix an assertion failure that could occur under high DNS load.
13045 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
13046 diagnosed and fixed by "cypherpunks".
13048 o Major bugfixes (relay, stability, possible security, also in 0.2.6.4-rc):
13049 - Fix a bug that could lead to a relay crashing with an assertion
13050 failure if a buffer of exactly the wrong layout was passed to
13051 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
13052 0.2.0.10-alpha. Patch from 'cypherpunks'.
13053 - Do not assert if the 'data' pointer on a buffer is advanced to the
13054 very end of the buffer; log a BUG message instead. Only assert if
13055 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
13057 o Minor features (geoip):
13058 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
13059 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
13062 Changes in version 0.2.6.4-rc - 2015-03-09
13063 Tor 0.2.6.4-alpha fixes an issue in the directory code that an
13064 attacker might be able to use in order to crash certain Tor
13065 directories. It also resolves some minor issues left over from, or
13066 introduced in, Tor 0.2.6.3-alpha or earlier.
13068 o Major bugfixes (crash, OSX, security):
13069 - Fix a remote denial-of-service opportunity caused by a bug in
13070 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
13073 o Major bugfixes (relay, stability, possible security):
13074 - Fix a bug that could lead to a relay crashing with an assertion
13075 failure if a buffer of exactly the wrong layout is passed to
13076 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
13077 0.2.0.10-alpha. Patch from "cypherpunks".
13078 - Do not assert if the 'data' pointer on a buffer is advanced to the
13079 very end of the buffer; log a BUG message instead. Only assert if
13080 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
13082 o Major bugfixes (FreeBSD IPFW transparent proxy):
13083 - Fix address detection with FreeBSD transparent proxies, when
13084 "TransProxyType ipfw" is in use. Fixes bug 15064; bugfix
13087 o Major bugfixes (Linux seccomp2 sandbox):
13088 - Pass IPPROTO_TCP rather than 0 to socket(), so that the Linux
13089 seccomp2 sandbox doesn't fail. Fixes bug 14989; bugfix
13091 - Allow AF_UNIX hidden services to be used with the seccomp2
13092 sandbox. Fixes bug 15003; bugfix on 0.2.6.3-alpha.
13093 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
13094 crash during attempts to call wait4. Fixes bug 15088; bugfix on
13095 0.2.5.1-alpha. Patch from "sanic".
13097 o Minor features (controller):
13098 - Messages about problems in the bootstrap process now include
13099 information about the server we were trying to connect to when we
13100 noticed the problem. Closes ticket 15006.
13102 o Minor features (geoip):
13103 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
13104 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
13107 o Minor features (logs):
13108 - Quiet some log messages in the heartbeat and at startup. Closes
13111 o Minor bugfixes (certificate handling):
13112 - If an authority operator accidentally makes a signing certificate
13113 with a future publication time, do not discard its real signing
13114 certificates. Fixes bug 11457; bugfix on 0.2.0.3-alpha.
13115 - Remove any old authority certificates that have been superseded
13116 for at least two days. Previously, we would keep superseded
13117 certificates until they expired, if they were published close in
13118 time to the certificate that superseded them. Fixes bug 11454;
13119 bugfix on 0.2.1.8-alpha.
13121 o Minor bugfixes (compilation):
13122 - Fix a compilation warning on s390. Fixes bug 14988; bugfix
13124 - Fix a compilation warning on FreeBSD. Fixes bug 15151; bugfix
13127 o Minor bugfixes (testing):
13128 - Fix endianness issues in unit test for resolve_my_address() to
13129 have it pass on big endian systems. Fixes bug 14980; bugfix on
13131 - Avoid a side-effect in a tor_assert() in the unit tests. Fixes bug
13132 15188; bugfix on 0.1.2.3-alpha. Patch from Tom van der Woerdt.
13133 - When running the new 'make test-stem' target, use the configured
13134 python binary. Fixes bug 15037; bugfix on 0.2.6.3-alpha. Patch
13135 from "cypherpunks".
13136 - When running the zero-length-keys tests, do not use the default
13137 torrc file. Fixes bug 15033; bugfix on 0.2.6.3-alpha. Reported
13140 o Directory authority IP change:
13141 - The directory authority Faravahar has a new IP address. This
13142 closes ticket 14487.
13145 - Remove some lingering dead code that once supported mempools.
13146 Mempools were disabled by default in 0.2.5, and removed entirely
13147 in 0.2.6.3-alpha. Closes more of ticket 14848; patch
13151 Changes in version 0.2.6.3-alpha - 2015-02-19
13152 Tor 0.2.6.3-alpha is the third (and hopefully final) alpha release in
13153 the 0.2.6.x series. It introduces support for more kinds of sockets,
13154 makes it harder to accidentally run an exit, improves our
13155 multithreading backend, incorporates several fixes for the
13156 AutomapHostsOnResolve option, and fixes numerous other bugs besides.
13158 If no major regressions or security holes are found in this version,
13159 the next version will be a release candidate.
13161 o Deprecated versions:
13162 - Tor relays older than 0.2.4.18-rc are no longer allowed to
13163 advertise themselves on the network. Closes ticket 13555.
13165 o Major features (security, unix domain sockets):
13166 - Allow SocksPort to be an AF_UNIX Unix Domain Socket. Now high risk
13167 applications can reach Tor without having to create AF_INET or
13168 AF_INET6 sockets, meaning they can completely disable their
13169 ability to make non-Tor network connections. To create a socket of
13170 this type, use "SocksPort unix:/path/to/socket". Implements
13172 - Support mapping hidden service virtual ports to AF_UNIX sockets.
13173 The syntax is "HiddenServicePort 80 unix:/path/to/socket".
13174 Implements ticket 11485.
13176 o Major features (changed defaults):
13177 - Prevent relay operators from unintentionally running exits: When a
13178 relay is configured as an exit node, we now warn the user unless
13179 the "ExitRelay" option is set to 1. We warn even more loudly if
13180 the relay is configured with the default exit policy, since this
13181 can indicate accidental misconfiguration. Setting "ExitRelay 0"
13182 stops Tor from running as an exit relay. Closes ticket 10067.
13184 o Major features (directory system):
13185 - When downloading server- or microdescriptors from a directory
13186 server, we no longer launch multiple simultaneous requests to the
13187 same server. This reduces load on the directory servers,
13188 especially when directory guards are in use. Closes ticket 9969.
13189 - When downloading server- or microdescriptors over a tunneled
13190 connection, do not limit the length of our requests to what the
13191 Squid proxy is willing to handle. Part of ticket 9969.
13192 - Authorities can now vote on the correct digests and latest
13193 versions for different software packages. This allows packages
13194 that include Tor to use the Tor authority system as a way to get
13195 notified of updates and their correct digests. Implements proposal
13196 227. Closes ticket 10395.
13198 o Major features (guards):
13199 - Introduce the Guardfraction feature to improves load balancing on
13200 guard nodes. Specifically, it aims to reduce the traffic gap that
13201 guard nodes experience when they first get the Guard flag. This is
13202 a required step if we want to increase the guard lifetime to 9
13203 months or greater. Closes ticket 9321.
13205 o Major features (performance):
13206 - Make the CPU worker implementation more efficient by avoiding the
13207 kernel and lengthening pipelines. The original implementation used
13208 sockets to transfer data from the main thread to the workers, and
13209 didn't allow any thread to be assigned more than a single piece of
13210 work at once. The new implementation avoids communications
13211 overhead by making requests in shared memory, avoiding kernel IO
13212 where possible, and keeping more requests in flight at once.
13213 Implements ticket 9682.
13215 o Major features (relay):
13216 - Raise the minimum acceptable configured bandwidth rate for bridges
13217 to 50 KiB/sec and for relays to 75 KiB/sec. (The old values were
13218 20 KiB/sec.) Closes ticket 13822.
13220 o Major bugfixes (exit node stability):
13221 - Fix an assertion failure that could occur under high DNS load.
13222 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
13223 diagnosed and fixed by "cypherpunks".
13225 o Major bugfixes (mixed relay-client operation):
13226 - When running as a relay and client at the same time (not
13227 recommended), if we decide not to use a new guard because we want
13228 to retry older guards, only close the locally-originating circuits
13229 passing through that guard. Previously we would close all the
13230 circuits through that guard. Fixes bug 9819; bugfix on
13231 0.2.1.1-alpha. Reported by "skruffy".
13233 o Minor features (build):
13234 - New --disable-system-torrc compile-time option to prevent Tor from
13235 looking for the system-wide torrc or torrc-defaults files.
13236 Resolves ticket 13037.
13238 o Minor features (controller):
13239 - Include SOCKS_USERNAME and SOCKS_PASSWORD values in controller
13240 events so controllers can observe circuit isolation inputs. Closes
13242 - ControlPort now supports the unix:/path/to/socket syntax as an
13243 alternative to the ControlSocket option, for consistency with
13244 SocksPort and HiddenServicePort. Closes ticket 14451.
13245 - New "GETINFO bw-event-cache" to get information about recent
13246 bandwidth events. Closes ticket 14128. Useful for controllers to
13247 get recent bandwidth history after the fix for ticket 13988.
13249 o Minor features (Denial of service resistance):
13250 - Count the total number of bytes used storing hidden service
13251 descriptors against the value of MaxMemInQueues. If we're low on
13252 memory, and more than 20% of our memory is used holding hidden
13253 service descriptors, free them until no more than 10% of our
13254 memory holds hidden service descriptors. Free the least recently
13255 fetched descriptors first. Resolves ticket 13806.
13256 - When we have recently been under memory pressure (over 3/4 of
13257 MaxMemInQueues is allocated), then allocate smaller zlib objects
13258 for small requests. Closes ticket 11791.
13260 o Minor features (geoip):
13261 - Update geoip and geoip6 files to the January 7 2015 Maxmind
13262 GeoLite2 Country database.
13264 o Minor features (guard nodes):
13265 - Reduce the time delay before saving guard status to disk from 10
13266 minutes to 30 seconds (or from one hour to 10 minutes if
13267 AvoidDiskWrites is set). Closes ticket 12485.
13269 o Minor features (hidden service):
13270 - Make Sybil attacks against hidden services harder by changing the
13271 minimum time required to get the HSDir flag from 25 hours up to 96
13272 hours. Addresses ticket 14149.
13273 - New option "HiddenServiceAllowUnknownPorts" to allow hidden
13274 services to disable the anti-scanning feature introduced in
13275 0.2.6.2-alpha. With this option not set, a connection to an
13276 unlisted port closes the circuit. With this option set, only a
13277 RELAY_DONE cell is sent. Closes ticket 14084.
13279 o Minor features (interface):
13280 - Implement "-f -" command-line option to read torrc configuration
13281 from standard input, if you don't want to store the torrc file in
13282 the file system. Implements feature 13865.
13284 o Minor features (logging):
13285 - Add a count of unique clients to the bridge heartbeat message.
13286 Resolves ticket 6852.
13287 - Suppress "router info incompatible with extra info" message when
13288 reading extrainfo documents from cache. (This message got loud
13289 around when we closed bug 9812 in 0.2.6.2-alpha.) Closes
13291 - Elevate hidden service authorized-client message from DEBUG to
13292 INFO. Closes ticket 14015.
13294 o Minor features (stability):
13295 - Add assertions in our hash-table iteration code to check for
13296 corrupted values that could cause infinite loops. Closes
13299 o Minor features (systemd):
13300 - Various improvements and modernizations in systemd hardening
13301 support. Closes ticket 13805. Patch from Craig Andrews.
13303 o Minor features (testing networks):
13304 - Drop the minimum RendPostPeriod on a testing network to 5 seconds,
13305 and the default on a testing network to 2 minutes. Drop the
13306 MIN_REND_INITIAL_POST_DELAY on a testing network to 5 seconds, but
13307 keep the default on a testing network at 30 seconds. This reduces
13308 HS bootstrap time to around 25 seconds. Also, change the default
13309 time in test-network.sh to match. Closes ticket 13401. Patch
13311 - Create TestingDirAuthVoteHSDir to correspond to
13312 TestingDirAuthVoteExit/Guard. Ensures that authorities vote the
13313 HSDir flag for the listed relays regardless of uptime or ORPort
13314 connectivity. Respects the value of VoteOnHidServDirectoriesV2.
13315 Partial implementation for ticket 14067. Patch by "teor".
13317 o Minor features (tor2web mode):
13318 - Introduce the config option Tor2webRendezvousPoints, which allows
13319 clients in Tor2webMode to select a specific Rendezvous Point to be
13320 used in HS circuits. This might allow better performance for
13321 Tor2Web nodes. Implements ticket 12844.
13323 o Minor bugfixes (client DNS):
13324 - Report the correct cached DNS expiration times on SOCKS port or in
13325 DNS replies. Previously, we would report everything as "never
13326 expires." Fixes bug 14193; bugfix on 0.2.3.17-beta.
13327 - Avoid a small memory leak when we find a cached answer for a
13328 reverse DNS lookup in a client-side DNS cache. (Remember, client-
13329 side DNS caching is off by default, and is not recommended.) Fixes
13330 bug 14259; bugfix on 0.2.0.1-alpha.
13332 o Minor bugfixes (client, automapping):
13333 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
13334 no value follows the option. Fixes bug 14142; bugfix on
13335 0.2.4.7-alpha. Patch by "teor".
13336 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
13337 14195; bugfix on 0.1.0.1-rc.
13338 - Prevent changes to other options from removing the wildcard value
13339 "." from "AutomapHostsSuffixes". Fixes bug 12509; bugfix
13341 - Allow MapAddress and AutomapHostsOnResolve to work together when
13342 an address is mapped into another address type (like .onion) that
13343 must be automapped at resolve time. Fixes bug 7555; bugfix
13346 o Minor bugfixes (client, bridges):
13347 - When we are using bridges and we had a network connectivity
13348 problem, only retry connecting to our currently configured
13349 bridges, not all bridges we know about and remember using. Fixes
13350 bug 14216; bugfix on 0.2.2.17-alpha.
13352 o Minor bugfixes (client, IPv6):
13353 - Reject socks requests to literal IPv6 addresses when IPv6Traffic
13354 flag is not set; and not because the NoIPv4Traffic flag was set.
13355 Previously we'd looked at the NoIPv4Traffic flag for both types of
13356 literal addresses. Fixes bug 14280; bugfix on 0.2.4.7-alpha.
13358 o Minor bugfixes (compilation):
13359 - The address of an array in the middle of a structure will always
13360 be non-NULL. clang recognises this and complains. Disable the
13361 tautologous and redundant check to silence this warning. Fixes bug
13362 14001; bugfix on 0.2.1.2-alpha.
13363 - Avoid warnings when building with systemd 209 or later. Fixes bug
13364 14072; bugfix on 0.2.6.2-alpha. Patch from "h.venev".
13365 - Compile correctly with (unreleased) OpenSSL 1.1.0 headers.
13366 Addresses ticket 14188.
13367 - Build without warnings with the stock OpenSSL srtp.h header, which
13368 has a duplicate declaration of SSL_get_selected_srtp_profile().
13369 Fixes bug 14220; this is OpenSSL's bug, not ours.
13370 - Do not compile any code related to Tor2Web mode when Tor2Web mode
13371 is not enabled at compile time. Previously, this code was included
13372 in a disabled state. See discussion on ticket 12844.
13373 - Remove the --disable-threads configure option again. It was
13374 accidentally partially reintroduced in 29ac883606d6d. Fixes bug
13375 14819; bugfix on 0.2.6.2-alpha.
13377 o Minor bugfixes (controller):
13378 - Report "down" in response to the "GETINFO entry-guards" command
13379 when relays are down with an unreachable_since value. Previously,
13380 we would report "up". Fixes bug 14184; bugfix on 0.1.2.2-alpha.
13381 - Avoid crashing on a malformed EXTENDCIRCUIT command. Fixes bug
13382 14116; bugfix on 0.2.2.9-alpha.
13383 - Add a code for the END_CIRC_REASON_IP_NOW_REDUNDANT circuit close
13384 reason. Fixes bug 14207; bugfix on 0.2.6.2-alpha.
13386 o Minor bugfixes (directory authority):
13387 - Allow directory authorities to fetch more data from one another if
13388 they find themselves missing lots of votes. Previously, they had
13389 been bumping against the 10 MB queued data limit. Fixes bug 14261;
13390 bugfix on 0.1.2.5-alpha.
13391 - Do not attempt to download extrainfo documents which we will be
13392 unable to validate with a matching server descriptor. Fixes bug
13393 13762; bugfix on 0.2.0.1-alpha.
13394 - Fix a bug that was truncating AUTHDIR_NEWDESC events sent to the
13395 control port. Fixes bug 14953; bugfix on 0.2.0.1-alpha.
13396 - Enlarge the buffer to read bwauth generated files to avoid an
13397 issue when parsing the file in dirserv_read_measured_bandwidths().
13398 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
13400 o Minor bugfixes (file handling):
13401 - Stop failing when key files are zero-length. Instead, generate new
13402 keys, and overwrite the empty key files. Fixes bug 13111; bugfix
13403 on all versions of Tor. Patch by "teor".
13404 - Stop generating a fresh .old RSA onion key file when the .old file
13405 is missing. Fixes part of 13111; bugfix on 0.0.6rc1.
13406 - Avoid overwriting .old key files with empty key files.
13407 - Skip loading zero-length extrainfo store, router store, stats,
13408 state, and key files.
13409 - Avoid crashing when trying to reload a torrc specified as a
13410 relative path with RunAsDaemon turned on. Fixes bug 13397; bugfix
13413 o Minor bugfixes (hidden services):
13414 - Close the introduction circuit when we have no more usable intro
13415 points, instead of waiting for it to time out. This also ensures
13416 that no follow-up HS descriptor fetch is triggered when the
13417 circuit eventually times out. Fixes bug 14224; bugfix on 0.0.6.
13418 - When fetching a hidden service descriptor for a down service that
13419 was recently up, do not keep refetching until we try the same
13420 replica twice in a row. Fixes bug 14219; bugfix on 0.2.0.10-alpha.
13421 - Successfully launch Tor with a nonexistent hidden service
13422 directory. Our fix for bug 13942 didn't catch this case. Fixes bug
13423 14106; bugfix on 0.2.6.2-alpha.
13425 o Minor bugfixes (logging):
13426 - Avoid crashing when there are more log domains than entries in
13427 domain_list. Bugfix on 0.2.3.1-alpha.
13428 - Add a string representation for LD_SCHED. Fixes bug 14740; bugfix
13430 - Don't log messages to stdout twice when starting up. Fixes bug
13431 13993; bugfix on 0.2.6.1-alpha.
13433 o Minor bugfixes (parsing):
13434 - Stop accepting milliseconds (or other junk) at the end of
13435 descriptor publication times. Fixes bug 9286; bugfix on 0.0.2pre25.
13436 - Support two-number and three-number version numbers correctly, in
13437 case we change the Tor versioning system in the future. Fixes bug
13438 13661; bugfix on 0.0.8pre1.
13440 o Minor bugfixes (path counting):
13441 - When deciding whether the consensus lists any exit nodes, count
13442 the number listed in the consensus, not the number we have
13443 descriptors for. Fixes part of bug 14918; bugfix on 0.2.6.2-alpha.
13444 - When deciding whether we have any exit nodes, only examine
13445 ExitNodes when the ExitNodes option is actually set. Fixes part of
13446 bug 14918; bugfix on 0.2.6.2-alpha.
13447 - Get rid of redundant and possibly scary warnings that we are
13448 missing directory information while we bootstrap. Fixes part of
13449 bug 14918; bugfix on 0.2.6.2-alpha.
13451 o Minor bugfixes (portability):
13452 - Fix the ioctl()-based network interface lookup code so that it
13453 will work on systems that have variable-length struct ifreq, for
13455 - Fix scheduler compilation on targets where char is unsigned. Fixes
13456 bug 14764; bugfix on 0.2.6.2-alpha. Reported by Christian Kujau.
13458 o Minor bugfixes (sandbox):
13459 - Allow glibc fatal errors to be sent to stderr before Tor exits.
13460 Previously, glibc would try to write them to /dev/tty, and the
13461 sandbox would trap the call and make Tor exit prematurely. Fixes
13462 bug 14759; bugfix on 0.2.5.1-alpha.
13464 o Minor bugfixes (shutdown):
13465 - When shutting down, always call event_del() on lingering read or
13466 write events before freeing them. Otherwise, we risk double-frees
13467 or read-after-frees in event_base_free(). Fixes bug 12985; bugfix
13470 o Minor bugfixes (small memory leaks):
13471 - Avoid leaking memory when using IPv6 virtual address mappings.
13472 Fixes bug 14123; bugfix on 0.2.4.7-alpha. Patch by Tom van
13475 o Minor bugfixes (statistics):
13476 - Increase period over which bandwidth observations are aggregated
13477 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
13479 o Minor bugfixes (systemd support):
13480 - Fix detection and operation of systemd watchdog. Fixes part of bug
13481 14141; bugfix on 0.2.6.2-alpha. Patch from Tomasz Torcz.
13482 - Run correctly under systemd with the RunAsDaemon option set. Fixes
13483 part of bug 14141; bugfix on 0.2.5.7-rc. Patch from Tomasz Torcz.
13484 - Inform the systemd supervisor about more changes in the Tor
13485 process status. Implements part of ticket 14141. Patch from
13487 - Cause the "--disable-systemd" option to actually disable systemd
13488 support. Fixes bug 14350; bugfix on 0.2.6.2-alpha. Patch
13491 o Minor bugfixes (TLS):
13492 - Check more thoroughly throughout the TLS code for possible
13493 unlogged TLS errors. Possible diagnostic or fix for bug 13319.
13495 o Minor bugfixes (transparent proxy):
13496 - Use getsockname, not getsockopt, to retrieve the address for a
13497 TPROXY-redirected connection. Fixes bug 13796; bugfix
13500 o Code simplification and refactoring:
13501 - Move fields related to isolating and configuring client ports into
13502 a shared structure. Previously, they were duplicated across
13503 port_cfg_t, listener_connection_t, and edge_connection_t. Failure
13504 to copy them correctly had been the cause of at least one bug in
13505 the past. Closes ticket 8546.
13506 - Refactor the get_interface_addresses_raw() doom-function into
13507 multiple smaller and simpler subfunctions. Cover the resulting
13508 subfunctions with unit-tests. Fixes a significant portion of
13510 - Remove workaround in dirserv_thinks_router_is_hs_dir() that was
13511 only for version <= 0.2.2.24 which is now deprecated. Closes
13513 - Remove a test for a long-defunct broken version-one
13517 - Adding section on OpenBSD to our TUNING document. Thanks to mmcc
13518 for writing the OpenBSD-specific tips. Resolves ticket 13702.
13519 - Make the tor-resolve documentation match its help string and its
13520 options. Resolves part of ticket 14325.
13521 - Log a more useful error message from tor-resolve when failing to
13522 look up a hidden service address. Resolves part of ticket 14325.
13524 o Downgraded warnings:
13525 - Don't warn when we've attempted to contact a relay using the wrong
13526 ntor onion key. Closes ticket 9635.
13528 o Removed features:
13529 - To avoid confusion with the "ExitRelay" option, "ExitNode" is no
13530 longer silently accepted as an alias for "ExitNodes".
13531 - The --enable-mempool and --enable-buf-freelists options, which
13532 were originally created to work around bad malloc implementations,
13533 no longer exist. They were off-by-default in 0.2.5. Closes
13537 - Make the checkdir/perms test complete successfully even if the
13538 global umask is not 022. Fixes bug 14215; bugfix on 0.2.6.2-alpha.
13539 - Test that tor does not fail when key files are zero-length. Check
13540 that tor generates new keys, and overwrites the empty key files.
13541 - Test that tor generates new keys when keys are missing
13542 (existing behavior).
13543 - Test that tor does not overwrite key files that already contain
13544 data (existing behavior). Tests bug 13111. Patch by "teor".
13545 - New "make test-stem" target to run stem integration tests.
13546 Requires that the "STEM_SOURCE_DIR" environment variable be set.
13547 Closes ticket 14107.
13548 - Make the test_cmdline_args.py script work correctly on Windows.
13549 Patch from Gisle Vanem.
13550 - Move the slower unit tests into a new "./src/test/test-slow"
13551 binary that can be run independently of the other tests. Closes
13553 - Avoid undefined behavior when sampling huge values from the
13554 Laplace distribution. This made unittests fail on Raspberry Pi.
13555 Bug found by Device. Fixes bug 14090; bugfix on 0.2.6.2-alpha.
13558 Changes in version 0.2.6.2-alpha - 2014-12-31
13559 Tor 0.2.6.2-alpha is the second alpha release in the 0.2.6.x series.
13560 It introduces a major new backend for deciding when to send cells on
13561 channels, which should lead down the road to big performance
13562 increases. It contains security and statistics features for better
13563 work on hidden services, and numerous bugfixes.
13565 This release contains many new unit tests, along with major
13566 performance improvements for running testing networks using Chutney.
13567 Thanks to a series of patches contributed by "teor", testing networks
13568 should now bootstrap in seconds, rather than minutes.
13570 o Major features (relay, infrastructure):
13571 - Complete revision of the code that relays use to decide which cell
13572 to send next. Formerly, we selected the best circuit to write on
13573 each channel, but we didn't select among channels in any
13574 sophisticated way. Now, we choose the best circuits globally from
13575 among those whose channels are ready to deliver traffic.
13577 This patch implements a new inter-cmux comparison API, a global
13578 high/low watermark mechanism and a global scheduler loop for
13579 transmission prioritization across all channels as well as among
13580 circuits on one channel. This schedule is currently tuned to
13581 (tolerantly) avoid making changes in network performance, but it
13582 should form the basis for major circuit performance increases in
13583 the future. Code by Andrea; tuning by Rob Jansen; implements
13586 o Major features (hidden services):
13587 - Make HS port scanning more difficult by immediately closing the
13588 circuit when a user attempts to connect to a nonexistent port.
13589 Closes ticket 13667.
13590 - Add a HiddenServiceStatistics option that allows Tor relays to
13591 gather and publish statistics about the overall size and volume of
13592 hidden service usage. Specifically, when this option is turned on,
13593 an HSDir will publish an approximate number of hidden services
13594 that have published descriptors to it the past 24 hours. Also, if
13595 a relay has acted as a hidden service rendezvous point, it will
13596 publish the approximate amount of rendezvous cells it has relayed
13597 the past 24 hours. The statistics themselves are obfuscated so
13598 that the exact values cannot be derived. For more details see
13599 proposal 238, "Better hidden service stats from Tor relays". This
13600 feature is currently disabled by default. Implements feature 13192.
13602 o Major bugfixes (client, automap):
13603 - Repair automapping with IPv6 addresses. This automapping should
13604 have worked previously, but one piece of debugging code that we
13605 inserted to detect a regression actually caused the regression to
13606 manifest itself again. Fixes bug 13811 and bug 12831; bugfix on
13607 0.2.4.7-alpha. Diagnosed and fixed by Francisco Blas
13610 o Major bugfixes (hidden services):
13611 - When closing an introduction circuit that was opened in parallel
13612 with others, don't mark the introduction point as unreachable.
13613 Previously, the first successful connection to an introduction
13614 point would make the other introduction points get marked as
13615 having timed out. Fixes bug 13698; bugfix on 0.0.6rc2.
13617 o Directory authority changes:
13618 - Remove turtles as a directory authority.
13619 - Add longclaw as a new (v3) directory authority. This implements
13620 ticket 13296. This keeps the directory authority count at 9.
13622 o Major removed features:
13623 - Tor clients no longer support connecting to hidden services
13624 running on Tor 0.2.2.x and earlier; the Support022HiddenServices
13625 option has been removed. (There shouldn't be any hidden services
13626 running these versions on the network.) Closes ticket 7803.
13628 o Minor features (client):
13629 - Validate hostnames in SOCKS5 requests more strictly. If SafeSocks
13630 is enabled, reject requests with IP addresses as hostnames.
13631 Resolves ticket 13315.
13633 o Minor features (controller):
13634 - Add a "SIGNAL HEARTBEAT" controller command that tells Tor to
13635 write an unscheduled heartbeat message to the log. Implements
13638 o Minor features (geoip):
13639 - Update geoip and geoip6 to the November 15 2014 Maxmind GeoLite2
13642 o Minor features (hidden services):
13643 - When re-enabling the network, don't try to build introduction
13644 circuits until we have successfully built a circuit. This makes
13645 hidden services come up faster when the network is re-enabled.
13646 Patch from "akwizgran". Closes ticket 13447.
13647 - When we fail to retrieve a hidden service descriptor, send the
13648 controller an "HS_DESC FAILED" controller event. Implements
13650 - New HiddenServiceDirGroupReadable option to cause hidden service
13651 directories and hostname files to be created group-readable. Patch
13652 from "anon", David Stainton, and "meejah". Closes ticket 11291.
13654 o Minor features (systemd):
13655 - Where supported, when running with systemd, report successful
13656 startup to systemd. Part of ticket 11016. Patch by Michael Scherer.
13657 - When running with systemd, support systemd watchdog messages. Part
13658 of ticket 11016. Patch by Michael Scherer.
13660 o Minor features (transparent proxy):
13661 - Update the transparent proxy option checks to allow for both ipfw
13662 and pf on OS X. Closes ticket 14002.
13663 - Use the correct option when using IPv6 with transparent proxy
13664 support on Linux. Resolves 13808. Patch by Francisco Blas
13667 o Minor bugfixes (preventative security, C safety):
13668 - When reading a hexadecimal, base-32, or base-64 encoded value from
13669 a string, always overwrite the whole output buffer. This prevents
13670 some bugs where we would look at (but fortunately, not reveal)
13671 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
13673 - Clear all memory targeted by tor_addr_{to,from}_sockaddr(), not
13674 just the part that's used. This makes it harder for data leak bugs
13675 to occur in the event of other programming failures. Resolves
13678 o Minor bugfixes (client, microdescriptors):
13679 - Use a full 256 bits of the SHA256 digest of a microdescriptor when
13680 computing which microdescriptors to download. This keeps us from
13681 erroneous download behavior if two microdescriptor digests ever
13682 have the same first 160 bits. Fixes part of bug 13399; bugfix
13684 - Reset a router's status if its microdescriptor digest changes,
13685 even if the first 160 bits remain the same. Fixes part of bug
13686 13399; bugfix on 0.2.3.1-alpha.
13688 o Minor bugfixes (compilation):
13689 - Silence clang warnings under --enable-expensive-hardening,
13690 including implicit truncation of 64 bit values to 32 bit, const
13691 char assignment to self, tautological compare, and additional
13692 parentheses around equality tests. Fixes bug 13577; bugfix
13694 - Fix a clang warning about checking whether an address in the
13695 middle of a structure is NULL. Fixes bug 14001; bugfix
13698 o Minor bugfixes (hidden services):
13699 - Correctly send a controller event when we find that a rendezvous
13700 circuit has finished. Fixes bug 13936; bugfix on 0.1.1.5-alpha.
13701 - Pre-check directory permissions for new hidden-services to avoid
13702 at least one case of "Bug: Acting on config options left us in a
13703 broken state. Dying." Fixes bug 13942; bugfix on 0.0.6pre1.
13704 - When adding a new hidden service (for example, via SETCONF), Tor
13705 no longer congratulates the user for running a relay. Fixes bug
13706 13941; bugfix on 0.2.6.1-alpha.
13707 - When fetching hidden service descriptors, we now check not only
13708 for whether we got the hidden service we had in mind, but also
13709 whether we got the particular descriptors we wanted. This prevents
13710 a class of inefficient but annoying DoS attacks by hidden service
13711 directories. Fixes bug 13214; bugfix on 0.2.1.6-alpha. Reported
13714 o Minor bugfixes (Linux seccomp2 sandbox):
13715 - Make transparent proxy support work along with the seccomp2
13716 sandbox. Fixes part of bug 13808; bugfix on 0.2.5.1-alpha. Patch
13717 by Francisco Blas Izquierdo Riera.
13718 - Fix a memory leak in tor-resolve when running with the sandbox
13719 enabled. Fixes bug 14050; bugfix on 0.2.5.9-rc.
13721 o Minor bugfixes (logging):
13722 - Downgrade warnings about RSA signature failures to info log level.
13723 Emit a warning when an extra info document is found incompatible
13724 with a corresponding router descriptor. Fixes bug 9812; bugfix
13726 - Make connection_ap_handshake_attach_circuit() log the circuit ID
13727 correctly. Fixes bug 13701; bugfix on 0.0.6.
13729 o Minor bugfixes (misc):
13730 - Stop allowing invalid address patterns like "*/24" that contain
13731 both a wildcard address and a bit prefix length. This affects all
13732 our address-range parsing code. Fixes bug 7484; bugfix
13735 o Minor bugfixes (testing networks, fast startup):
13736 - Allow Tor to build circuits using a consensus with no exits. If
13737 the consensus has no exits (typical of a bootstrapping test
13738 network), allow Tor to build circuits once enough descriptors have
13739 been downloaded. This assists in bootstrapping a testing Tor
13740 network. Fixes bug 13718; bugfix on 0.2.4.10-alpha. Patch
13742 - When V3AuthVotingInterval is low, give a lower If-Modified-Since
13743 header to directory servers. This allows us to obtain consensuses
13744 promptly when the consensus interval is very short. This assists
13745 in bootstrapping a testing Tor network. Fixes parts of bugs 13718
13746 and 13963; bugfix on 0.2.0.3-alpha. Patch by "teor".
13747 - Stop assuming that private addresses are local when checking
13748 reachability in a TestingTorNetwork. Instead, when testing, assume
13749 all OR connections are remote. (This is necessary due to many test
13750 scenarios running all relays on localhost.) This assists in
13751 bootstrapping a testing Tor network. Fixes bug 13924; bugfix on
13752 0.1.0.1-rc. Patch by "teor".
13753 - Avoid building exit circuits from a consensus with no exits. Now
13754 thanks to our fix for 13718, we accept a no-exit network as not
13755 wholly lost, but we need to remember not to try to build exit
13756 circuits on it. Closes ticket 13814; patch by "teor".
13757 - Stop requiring exits to have non-zero bandwithcapacity in a
13758 TestingTorNetwork. Instead, when TestingMinExitFlagThreshold is 0,
13759 ignore exit bandwidthcapacity. This assists in bootstrapping a
13760 testing Tor network. Fixes parts of bugs 13718 and 13839; bugfix
13761 on 0.2.0.3-alpha. Patch by "teor".
13762 - Add "internal" to some bootstrap statuses when no exits are
13763 available. If the consensus does not contain Exits, Tor will only
13764 build internal circuits. In this case, relevant statuses will
13765 contain the word "internal" as indicated in the Tor control-
13766 spec.txt. When bootstrap completes, Tor will be ready to build
13767 internal circuits. If a future consensus contains Exits, exit
13768 circuits may become available. Fixes part of bug 13718; bugfix on
13769 0.2.4.10-alpha. Patch by "teor".
13770 - Decrease minimum consensus interval to 10 seconds when
13771 TestingTorNetwork is set, or 5 seconds for the first consensus.
13772 Fix assumptions throughout the code that assume larger intervals.
13773 Fixes bugs 13718 and 13823; bugfix on 0.2.0.3-alpha. Patch
13775 - Avoid excluding guards from path building in minimal test
13776 networks, when we're in a test network and excluding guards would
13777 exclude all relays. This typically occurs in incredibly small tor
13778 networks, and those using "TestingAuthVoteGuard *". Fixes part of
13779 bug 13718; bugfix on 0.1.1.11-alpha. Patch by "teor".
13781 o Code simplification and refactoring:
13782 - Stop using can_complete_circuits as a global variable; access it
13783 with a function instead.
13784 - Avoid using operators directly as macro arguments: this lets us
13785 apply coccinelle transformations to our codebase more directly.
13786 Closes ticket 13172.
13787 - Combine the functions used to parse ClientTransportPlugin and
13788 ServerTransportPlugin into a single function. Closes ticket 6456.
13789 - Add inline functions and convenience macros for inspecting channel
13790 state. Refactor the code to use convenience macros instead of
13791 checking channel state directly. Fixes issue 7356.
13792 - Document all members of was_router_added_t and rename
13793 ROUTER_WAS_NOT_NEW to ROUTER_IS_ALREADY_KNOWN to make it less
13794 confusable with ROUTER_WAS_TOO_OLD. Fixes issue 13644.
13795 - In connection_exit_begin_conn(), use END_CIRC_REASON_TORPROTOCOL
13796 constant instead of hardcoded value. Fixes issue 13840.
13797 - Refactor our generic strmap and digestmap types into a single
13798 implementation, so that we can add a new digest256map
13802 - Document the bridge-authority-only 'networkstatus-bridges' file.
13803 Closes ticket 13713; patch from "tom".
13804 - Fix typo in PredictedPortsRelevanceTime option description in
13805 manpage. Resolves issue 13707.
13806 - Stop suggesting that users specify relays by nickname: it isn't a
13807 good idea. Also, properly cross-reference how to specify relays in
13808 all parts of manual documenting options that take a list of
13809 relays. Closes ticket 13381.
13810 - Clarify the HiddenServiceDir option description in manpage to make
13811 it clear that relative paths are taken with respect to the current
13812 working directory. Also clarify that this behavior is not
13813 guaranteed to remain indefinitely. Fixes issue 13913.
13816 - New tests for many parts of channel, relay, and circuitmux
13817 functionality. Code by Andrea; part of 9262.
13818 - New tests for parse_transport_line(). Part of ticket 6456.
13819 - In the unit tests, use chgrp() to change the group of the unit
13820 test temporary directory to the current user, so that the sticky
13821 bit doesn't interfere with tests that check directory groups.
13823 - Add unit tests for resolve_my_addr(). Part of ticket 12376; patch
13827 Changes in version 0.2.6.1-alpha - 2014-10-30
13828 Tor 0.2.6.1-alpha is the first release in the Tor 0.2.6.x series. It
13829 includes numerous code cleanups and new tests, and fixes a large
13830 number of annoying bugs. Out-of-memory conditions are handled better
13831 than in 0.2.5, pluggable transports have improved proxy support, and
13832 clients now use optimistic data for contacting hidden services. Also,
13833 we are now more robust to changes in what we consider a parseable
13834 directory object, so that tightening restrictions does not have a risk
13835 of introducing infinite download loops.
13837 This is the first alpha release in a new series, so expect there to be
13838 bugs. Users who would rather test out a more stable branch should stay
13839 with 0.2.5.x for now.
13841 o New compiler and system requirements:
13842 - Tor 0.2.6.x requires that your compiler support more of the C99
13843 language standard than before. The 'configure' script now detects
13844 whether your compiler supports C99 mid-block declarations and
13845 designated initializers. If it does not, Tor will not compile.
13847 We may revisit this requirement if it turns out that a significant
13848 number of people need to build Tor with compilers that don't
13849 bother implementing a 15-year-old standard. Closes ticket 13233.
13850 - Tor no longer supports systems without threading support. When we
13851 began working on Tor, there were several systems that didn't have
13852 threads, or where the thread support wasn't able to run the
13853 threads of a single process on multiple CPUs. That no longer
13854 holds: every system where Tor needs to run well now has threading
13855 support. Resolves ticket 12439.
13857 o Removed platform support:
13858 - We no longer include special code to build on Windows CE; as far
13859 as we know, nobody has used Tor on Windows CE in a very long time.
13860 Closes ticket 11446.
13862 o Major features (bridges):
13863 - Expose the outgoing upstream HTTP/SOCKS proxy to pluggable
13864 transports if they are configured via the "TOR_PT_PROXY"
13865 environment variable. Implements proposal 232. Resolves
13868 o Major features (client performance, hidden services):
13869 - Allow clients to use optimistic data when connecting to a hidden
13870 service, which should remove a round-trip from hidden service
13871 initialization. See proposal 181 for details. Implements
13874 o Major features (directory system):
13875 - Upon receiving an unparseable directory object, if its digest
13876 matches what we expected, then don't try to download it again.
13877 Previously, when we got a descriptor we didn't like, we would keep
13878 trying to download it over and over. Closes ticket 11243.
13880 o Major features (sample torrc):
13881 - Add a new, infrequently-changed "torrc.minimal". This file is
13882 similar to torrc.sample, but it will change as infrequently as
13883 possible, for the benefit of users whose systems prompt them for
13884 intervention whenever a default configuration file is changed.
13885 Making this change allows us to update torrc.sample to be a more
13886 generally useful "sample torrc".
13888 o Major bugfixes (directory authorities):
13889 - Do not assign the HSDir flag to relays if they are not Valid, or
13890 currently hibernating. Fixes 12573; bugfix on 0.2.0.10-alpha.
13892 o Major bugfixes (directory bandwidth performance):
13893 - Don't flush the zlib buffer aggressively when compressing
13894 directory information for clients. This should save about 7% of
13895 the bandwidth currently used for compressed descriptors and
13896 microdescriptors. Fixes bug 11787; bugfix on 0.1.1.23.
13898 o Minor features (security, memory wiping):
13899 - Ensure we securely wipe keys from memory after
13900 crypto_digest_get_digest and init_curve25519_keypair_from_file
13901 have finished using them. Resolves ticket 13477.
13903 o Minor features (security, out-of-memory handling):
13904 - When handling an out-of-memory condition, allocate less memory for
13905 temporary data structures. Fixes issue 10115.
13906 - When handling an out-of-memory condition, consider more types of
13907 buffers, including those on directory connections, and zlib
13908 buffers. Resolves ticket 11792.
13911 - When identity keypair is generated for first time, log a
13912 congratulatory message that links to the new relay lifecycle
13913 document. Implements feature 10427.
13915 o Minor features (client):
13916 - Clients are now willing to send optimistic data (before they
13917 receive a 'connected' cell) to relays of any version. (Relays
13918 without support for optimistic data are no longer supported on the
13919 Tor network.) Resolves ticket 13153.
13921 o Minor features (directory authorities):
13922 - Don't list relays with a bandwidth estimate of 0 in the consensus.
13923 Implements a feature proposed during discussion of bug 13000.
13924 - In tor-gencert, report an error if the user provides the same
13925 argument more than once.
13926 - If a directory authority can't find a best consensus method in the
13927 votes that it holds, it now falls back to its favorite consensus
13928 method. Previously, it fell back to method 1. Neither of these is
13929 likely to get enough signatures, but "fall back to favorite"
13930 doesn't require us to maintain support an obsolete consensus
13931 method. Implements part of proposal 215.
13933 o Minor features (logging):
13934 - On Unix-like systems, you can now use named pipes as the target of
13935 the Log option, and other options that try to append to files.
13936 Closes ticket 12061. Patch from "carlo von lynX".
13937 - When opening a log file at startup, send it every log message that
13938 we generated between startup and opening it. Previously, log
13939 messages that were generated before opening the log file were only
13940 logged to stdout. Closes ticket 6938.
13941 - Add a TruncateLogFile option to overwrite logs instead of
13942 appending to them. Closes ticket 5583.
13944 o Minor features (portability, Solaris):
13945 - Threads are no longer disabled by default on Solaris; we believe
13946 that the versions of Solaris with broken threading support are all
13947 obsolete by now. Resolves ticket 9495.
13949 o Minor features (relay):
13950 - Re-check our address after we detect a changed IP address from
13951 getsockname(). This ensures that the controller command "GETINFO
13952 address" will report the correct value. Resolves ticket 11582.
13954 - A new AccountingRule option lets Relays set whether they'd like
13955 AccountingMax to be applied separately to inbound and outbound
13956 traffic, or applied to the sum of inbound and outbound traffic.
13957 Resolves ticket 961. Patch by "chobe".
13959 o Minor features (testing networks):
13960 - Add the TestingDirAuthVoteExit option, which lists nodes to assign
13961 the "Exit" flag regardless of their uptime, bandwidth, or exit
13962 policy. TestingTorNetwork must be set for this option to have any
13963 effect. Previously, authorities would take up to 35 minutes to
13964 give nodes the Exit flag in a test network. Partially implements
13967 o Minor features (validation):
13968 - Check all date/time values passed to tor_timegm and
13969 parse_rfc1123_time for validity, taking leap years into account.
13970 Improves HTTP header validation. Implemented with bug 13476.
13971 - In correct_tm(), limit the range of values returned by system
13972 localtime(_r) and gmtime(_r) to be between the years 1 and 8099.
13973 This means we don't have to deal with negative or too large dates,
13974 even if a clock is wrong. Otherwise we might fail to read a file
13975 written by us which includes such a date. Fixes bug 13476.
13977 o Minor bugfixes (bridge clients):
13978 - When configured to use a bridge without an identity digest (not
13979 recommended), avoid launching an extra channel to it when
13980 bootstrapping. Fixes bug 7733; bugfix on 0.2.4.4-alpha.
13982 o Minor bugfixes (bridges):
13983 - When DisableNetwork is set, do not launch pluggable transport
13984 plugins, and if any are running, terminate them. Fixes bug 13213;
13985 bugfix on 0.2.3.6-alpha.
13987 o Minor bugfixes (C correctness):
13988 - Fix several instances of possible integer overflow/underflow/NaN.
13989 Fixes bug 13104; bugfix on 0.2.3.1-alpha and later. Patches
13991 - In circuit_build_times_calculate_timeout() in circuitstats.c,
13992 avoid dividing by zero in the pareto calculations. This traps
13993 under clang's "undefined-trap" sanitizer. Fixes bug 13290; bugfix
13995 - Fix an integer overflow in format_time_interval(). Fixes bug
13996 13393; bugfix on 0.2.0.10-alpha.
13997 - Set the correct day of year value when the system's localtime(_r)
13998 or gmtime(_r) functions fail to set struct tm. Not externally
13999 visible. Fixes bug 13476; bugfix on 0.0.2pre14.
14000 - Avoid unlikely signed integer overflow in tor_timegm on systems
14001 with 32-bit time_t. Fixes bug 13476; bugfix on 0.0.2pre14.
14003 o Minor bugfixes (client):
14004 - Fix smartlist_choose_node_by_bandwidth() so that relays with the
14005 BadExit flag are not considered worthy candidates. Fixes bug
14006 13066; bugfix on 0.1.2.3-alpha.
14007 - Use the consensus schedule for downloading consensuses, and not
14008 the generic schedule. Fixes bug 11679; bugfix on 0.2.2.6-alpha.
14009 - Handle unsupported or malformed SOCKS5 requests properly by
14010 responding with the appropriate error message before closing the
14011 connection. Fixes bugs 12971 and 13314; bugfix on 0.0.2pre13.
14013 o Minor bugfixes (client, torrc):
14014 - Stop modifying the value of our DirReqStatistics torrc option just
14015 because we're not a bridge or relay. This bug was causing Tor
14016 Browser users to write "DirReqStatistics 0" in their torrc files
14017 as if they had chosen to change the config. Fixes bug 4244; bugfix
14019 - When GeoIPExcludeUnknown is enabled, do not incorrectly decide
14020 that our options have changed every time we SIGHUP. Fixes bug
14021 9801; bugfix on 0.2.4.10-alpha. Patch from "qwerty1".
14023 o Minor bugfixes (controller):
14024 - Return an error when the second or later arguments of the
14025 "setevents" controller command are invalid events. Previously we
14026 would return success while silently skipping invalid events. Fixes
14027 bug 13205; bugfix on 0.2.3.2-alpha. Reported by "fpxnns".
14029 o Minor bugfixes (directory system):
14030 - Always believe that v3 directory authorities serve extra-info
14031 documents, whether they advertise "caches-extra-info" or not.
14032 Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
14033 - When running as a v3 directory authority, advertise that you serve
14034 extra-info documents so that clients who want them can find them
14035 from you too. Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
14036 - Check the BRIDGE_DIRINFO flag bitwise rather than using equality.
14037 Previously, directories offering BRIDGE_DIRINFO and some other
14038 flag (i.e. microdescriptors or extrainfo) would be ignored when
14039 looking for bridges. Partially fixes bug 13163; bugfix
14042 o Minor bugfixes (networking):
14043 - Check for orconns and use connection_or_close_for_error() rather
14044 than connection_mark_for_close() directly in the getsockopt()
14045 failure case of connection_handle_write_impl(). Fixes bug 11302;
14046 bugfix on 0.2.4.4-alpha.
14048 o Minor bugfixes (relay):
14049 - When generating our family list, remove spaces from around the
14050 entries. Fixes bug 12728; bugfix on 0.2.1.7-alpha.
14051 - If our previous bandwidth estimate was 0 bytes, allow publishing a
14052 new relay descriptor immediately. Fixes bug 13000; bugfix
14055 o Minor bugfixes (testing networks):
14056 - Fix TestingDirAuthVoteGuard to properly give out Guard flags in a
14057 testing network. Fixes bug 13064; bugfix on 0.2.5.2-alpha.
14058 - Stop using the default authorities in networks which provide both
14059 AlternateDirAuthority and AlternateBridgeAuthority. Partially
14060 fixes bug 13163; bugfix on 0.2.0.13-alpha.
14062 o Minor bugfixes (testing):
14063 - Stop spawn test failures due to a race condition between the
14064 SIGCHLD handler updating the process status, and the test reading
14065 it. Fixes bug 13291; bugfix on 0.2.3.3-alpha.
14067 o Minor bugfixes (testing, Windows):
14068 - Avoid passing an extra backslash when creating a temporary
14069 directory for running the unit tests on Windows. Fixes bug 12392;
14070 bugfix on 0.2.2.25-alpha. Patch from Gisle Vanem.
14072 o Minor bugfixes (windows):
14073 - Remove code to special-case handling of NTE_BAD_KEYSET when
14074 acquiring windows CryptoAPI context. This error can't actually
14075 occur for the parameters we're providing. Fixes bug 10816; bugfix
14078 o Minor bugfixes (zlib):
14079 - Avoid truncating a zlib stream when trying to finalize it with an
14080 empty output buffer. Fixes bug 11824; bugfix on 0.1.1.23.
14083 - Allow our configure script to build correctly with autoconf 2.62
14084 again. Fixes bug 12693; bugfix on 0.2.5.2-alpha.
14085 - Improve the error message from ./configure to make it clear that
14086 when asciidoc has not been found, the user will have to either add
14087 --disable-asciidoc argument or install asciidoc. Resolves
14090 o Code simplification and refactoring:
14091 - Change the entry_is_live() function to take named bitfield
14092 elements instead of an unnamed list of booleans. Closes
14094 - Refactor and unit-test entry_is_time_to_retry() in entrynodes.c.
14095 Resolves ticket 12205.
14096 - Use calloc and reallocarray functions instead of multiply-
14097 then-malloc. This makes it less likely for us to fall victim to an
14098 integer overflow attack when allocating. Resolves ticket 12855.
14099 - Use the standard macro name SIZE_MAX, instead of our
14101 - Document usage of the NO_DIRINFO and ALL_DIRINFO flags clearly in
14102 functions which take them as arguments. Replace 0 with NO_DIRINFO
14103 in a function call for clarity. Seeks to prevent future issues
14105 - Avoid 4 null pointer errors under clang static analysis by using
14106 tor_assert() to prove that the pointers aren't null. Fixes
14108 - Rework the API of policies_parse_exit_policy() to use a bitmask to
14109 represent parsing options, instead of a confusing mess of
14110 booleans. Resolves ticket 8197.
14111 - Introduce a helper function to parse ExitPolicy in
14112 or_options_t structure.
14115 - Add a doc/TUNING document with tips for handling large numbers of
14116 TCP connections when running busy Tor relay. Update the warning
14117 message to point to this file when running out of sockets
14118 operating system is allowing to use simultaneously. Resolves
14121 o Removed features:
14122 - We no longer remind the user about configuration options that have
14123 been obsolete since 0.2.3.x or earlier. Patch by Adrien Bak.
14124 - Remove our old, non-weighted bandwidth-based node selection code.
14125 Previously, we used it as a fallback when we couldn't perform
14126 weighted bandwidth-based node selection. But that would only
14127 happen in the cases where we had no consensus, or when we had a
14128 consensus generated by buggy or ancient directory authorities. In
14129 either case, it's better to use the more modern, better maintained
14130 algorithm, with reasonable defaults for the weights. Closes
14132 - Remove the --disable-curve25519 configure option. Relays and
14133 clients now are required to support curve25519 and the
14135 - The old "StrictEntryNodes" and "StrictExitNodes" options, which
14136 used to be deprecated synonyms for "StrictNodes", are now marked
14137 obsolete. Resolves ticket 12226.
14138 - Clients don't understand the BadDirectory flag in the consensus
14139 anymore, and ignore it.
14142 - Refactor the function that chooses guard nodes so that it can more
14143 easily be tested; write some tests for it.
14144 - Fix and re-enable the fgets_eagain unit test. Fixes bug 12503;
14145 bugfix on 0.2.3.1-alpha. Patch from "cypherpunks."
14146 - Create unit tests for format_time_interval(). With bug 13393.
14147 - Add unit tests for tor_timegm signed overflow, tor_timegm and
14148 parse_rfc1123_time validity checks, correct_tm year clamping. Unit
14149 tests (visible) fixes in bug 13476.
14150 - Add a "coverage-html" make target to generate HTML-visualized
14151 coverage results when building with --enable-coverage. (Requires
14152 lcov.) Patch from Kevin Murray.
14153 - Enable the backtrace handler (where supported) when running the
14155 - Revise all unit tests that used the legacy test_* macros to
14156 instead use the recommended tt_* macros. This patch was generated
14157 with coccinelle, to avoid manual errors. Closes ticket 13119.
14159 o Distribution (systemd):
14160 - systemd unit file: only allow tor to write to /var/lib/tor and
14161 /var/log/tor. The rest of the filesystem is accessible for reading
14162 only. Patch by intrigeri; resolves ticket 12751.
14163 - systemd unit file: ensure that the process and all its children
14164 can never gain new privileges. Patch by intrigeri; resolves
14166 - systemd unit file: set up /var/run/tor as writable for the Tor
14167 service. Patch by intrigeri; resolves ticket 13196.
14169 o Removed features (directory authorities):
14170 - Remove code that prevented authorities from listing Tor relays
14171 affected by CVE-2011-2769 as guards. These relays are already
14172 rejected altogether due to the minimum version requirement of
14173 0.2.3.16-alpha. Closes ticket 13152.
14174 - The "AuthDirRejectUnlisted" option no longer has any effect, as
14175 the fingerprints file (approved-routers) has been deprecated.
14176 - Directory authorities do not support being Naming dirauths anymore.
14177 The "NamingAuthoritativeDir" config option is now obsolete.
14178 - Directory authorities do not support giving out the BadDirectory
14180 - Directory authorities no longer advertise or support consensus
14181 methods 1 through 12 inclusive. These consensus methods were
14182 obsolete and/or insecure: maintaining the ability to support them
14183 served no good purpose. Implements part of proposal 215; closes
14186 o Testing (test-network.sh):
14187 - Stop using "echo -n", as some shells' built-in echo doesn't
14188 support "-n". Instead, use "/bin/echo -n". Partially fixes
14190 - Stop an apparent test-network hang when used with make -j2. Fixes
14192 - Add a --delay option to test-network.sh, which configures the
14193 delay before the chutney network tests for data transmission.
14194 Partially implements ticket 13161.
14197 Changes in version 0.2.5.10 - 2014-10-24
14198 Tor 0.2.5.10 is the first stable release in the 0.2.5 series.
14200 It adds several new security features, including improved
14201 denial-of-service resistance for relays, new compiler hardening
14202 options, and a system-call sandbox for hardened installations on Linux
14203 (requires seccomp2). The controller protocol has several new features,
14204 resolving IPv6 addresses should work better than before, and relays
14205 should be a little more CPU-efficient. We've added support for more
14206 OpenBSD and FreeBSD transparent proxy types. We've improved the build
14207 system and testing infrastructure to allow unit testing of more parts
14208 of the Tor codebase. Finally, we've addressed several nagging pluggable
14209 transport usability issues, and included numerous other small bugfixes
14210 and features mentioned below.
14212 This release marks end-of-life for Tor 0.2.3.x; those Tor versions
14213 have accumulated many known flaws; everyone should upgrade.
14215 o Deprecated versions:
14216 - Tor 0.2.3.x has reached end-of-life; it has received no patches or
14217 attention for some while.
14220 Changes in version 0.2.5.9-rc - 2014-10-20
14221 Tor 0.2.5.9-rc is the third release candidate for the Tor 0.2.5.x
14222 series. It disables SSL3 in response to the recent "POODLE" attack
14223 (even though POODLE does not affect Tor). It also works around a crash
14224 bug caused by some operating systems' response to the "POODLE" attack
14225 (which does affect Tor). It also contains a few miscellaneous fixes.
14227 o Major security fixes:
14228 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
14229 today support TLS 1.0 or later, so we can safely turn off support
14230 for this old (and insecure) protocol. Fixes bug 13426.
14232 o Major bugfixes (openssl bug workaround):
14233 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
14234 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
14235 13471. This is a workaround for an OpenSSL bug.
14238 - Disable the sandbox name resolver cache when running tor-resolve:
14239 tor-resolve doesn't use the sandbox code, and turning it on was
14240 breaking attempts to do tor-resolve on a non-default server on
14241 Linux. Fixes bug 13295; bugfix on 0.2.5.3-alpha.
14243 o Compilation fixes:
14244 - Build and run correctly on systems like OpenBSD-current that have
14245 patched OpenSSL to remove get_cipher_by_char and/or its
14246 implementations. Fixes issue 13325.
14248 o Downgraded warnings:
14249 - Downgrade the severity of the 'unexpected sendme cell from client'
14250 from 'warn' to 'protocol warning'. Closes ticket 8093.
14253 Changes in version 0.2.4.25 - 2014-10-20
14254 Tor 0.2.4.25 disables SSL3 in response to the recent "POODLE" attack
14255 (even though POODLE does not affect Tor). It also works around a crash
14256 bug caused by some operating systems' response to the "POODLE" attack
14257 (which does affect Tor).
14259 o Major security fixes (also in 0.2.5.9-rc):
14260 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
14261 today support TLS 1.0 or later, so we can safely turn off support
14262 for this old (and insecure) protocol. Fixes bug 13426.
14264 o Major bugfixes (openssl bug workaround, also in 0.2.5.9-rc):
14265 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
14266 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
14267 13471. This is a workaround for an OpenSSL bug.
14270 Changes in version 0.2.5.8-rc - 2014-09-22
14271 Tor 0.2.5.8-rc is the second release candidate for the Tor 0.2.5.x
14272 series. It fixes a bug that affects consistency and speed when
14273 connecting to hidden services, and it updates the location of one of
14274 the directory authorities.
14277 - Clients now send the correct address for their chosen rendezvous
14278 point when trying to access a hidden service. They used to send
14279 the wrong address, which would still work some of the time because
14280 they also sent the identity digest of the rendezvous point, and if
14281 the hidden service happened to try connecting to the rendezvous
14282 point from a relay that already had a connection open to it,
14283 the relay would reuse that connection. Now connections to hidden
14284 services should be more robust and faster. Also, this bug meant
14285 that clients were leaking to the hidden service whether they were
14286 on a little-endian (common) or big-endian (rare) system, which for
14287 some users might have reduced their anonymity. Fixes bug 13151;
14288 bugfix on 0.2.1.5-alpha.
14290 o Directory authority changes:
14291 - Change IP address for gabelmoo (v3 directory authority).
14294 Changes in version 0.2.4.24 - 2014-09-22
14295 Tor 0.2.4.24 fixes a bug that affects consistency and speed when
14296 connecting to hidden services, and it updates the location of one of
14297 the directory authorities.
14300 - Clients now send the correct address for their chosen rendezvous
14301 point when trying to access a hidden service. They used to send
14302 the wrong address, which would still work some of the time because
14303 they also sent the identity digest of the rendezvous point, and if
14304 the hidden service happened to try connecting to the rendezvous
14305 point from a relay that already had a connection open to it,
14306 the relay would reuse that connection. Now connections to hidden
14307 services should be more robust and faster. Also, this bug meant
14308 that clients were leaking to the hidden service whether they were
14309 on a little-endian (common) or big-endian (rare) system, which for
14310 some users might have reduced their anonymity. Fixes bug 13151;
14311 bugfix on 0.2.1.5-alpha.
14313 o Directory authority changes:
14314 - Change IP address for gabelmoo (v3 directory authority).
14316 o Minor features (geoip):
14317 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
14321 Changes in version 0.2.5.7-rc - 2014-09-11
14322 Tor 0.2.5.7-rc fixes several regressions from earlier in the 0.2.5.x
14323 release series, and some long-standing bugs related to ORPort reachability
14324 testing and failure to send CREATE cells. It is the first release
14325 candidate for the Tor 0.2.5.x series.
14327 o Major bugfixes (client, startup):
14328 - Start making circuits as soon as DisabledNetwork is turned off.
14329 When Tor started with DisabledNetwork set, it would correctly
14330 conclude that it shouldn't build circuits, but it would mistakenly
14331 cache this conclusion, and continue believing it even when
14332 DisableNetwork is set to 0. Fixes the bug introduced by the fix
14333 for bug 11200; bugfix on 0.2.5.4-alpha.
14334 - Resume expanding abbreviations for command-line options. The fix
14335 for bug 4647 accidentally removed our hack from bug 586 that
14336 rewrote HashedControlPassword to __HashedControlSessionPassword
14337 when it appears on the commandline (which allowed the user to set
14338 her own HashedControlPassword in the torrc file while the
14339 controller generates a fresh session password for each run). Fixes
14340 bug 12948; bugfix on 0.2.5.1-alpha.
14341 - Warn about attempts to run hidden services and relays in the same
14342 process: that's probably not a good idea. Closes ticket 12908.
14344 o Major bugfixes (relay):
14345 - Avoid queuing or sending destroy cells for circuit ID zero when we
14346 fail to send a CREATE cell. Fixes bug 12848; bugfix on 0.0.8pre1.
14347 Found and fixed by "cypherpunks".
14348 - Fix ORPort reachability detection on relays running behind a
14349 proxy, by correctly updating the "local" mark on the controlling
14350 channel when changing the address of an or_connection_t after the
14351 handshake. Fixes bug 12160; bugfix on 0.2.4.4-alpha.
14353 o Minor features (bridge):
14354 - Add an ExtORPortCookieAuthFileGroupReadable option to make the
14355 cookie file for the ExtORPort g+r by default.
14357 o Minor features (geoip):
14358 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
14361 o Minor bugfixes (logging):
14362 - Reduce the log severity of the "Pluggable transport proxy does not
14363 provide any needed transports and will not be launched." message,
14364 since Tor Browser includes several ClientTransportPlugin lines in
14365 its torrc-defaults file, leading every Tor Browser user who looks
14366 at her logs to see these notices and wonder if they're dangerous.
14367 Resolves bug 13124; bugfix on 0.2.5.3-alpha.
14368 - Downgrade "Unexpected onionskin length after decryption" warning
14369 to a protocol-warn, since there's nothing relay operators can do
14370 about a client that sends them a malformed create cell. Resolves
14371 bug 12996; bugfix on 0.0.6rc1.
14372 - Log more specific warnings when we get an ESTABLISH_RENDEZVOUS
14373 cell on a cannibalized or non-OR circuit. Resolves ticket 12997.
14374 - When logging information about an EXTEND2 or EXTENDED2 cell, log
14375 their names correctly. Fixes part of bug 12700; bugfix
14377 - When logging information about a relay cell whose command we don't
14378 recognize, log its command as an integer. Fixes part of bug 12700;
14379 bugfix on 0.2.1.10-alpha.
14380 - Escape all strings from the directory connection before logging
14381 them. Fixes bug 13071; bugfix on 0.1.1.15. Patch from "teor".
14383 o Minor bugfixes (controller):
14384 - Restore the functionality of CookieAuthFileGroupReadable. Fixes
14385 bug 12864; bugfix on 0.2.5.1-alpha.
14386 - Actually send TRANSPORT_LAUNCHED and HS_DESC events to
14387 controllers. Fixes bug 13085; bugfix on 0.2.5.1-alpha. Patch
14390 o Minor bugfixes (compilation):
14391 - Fix compilation of test.h with MSVC. Patch from Gisle Vanem;
14392 bugfix on 0.2.5.5-alpha.
14393 - Make the nmake make files work again. Fixes bug 13081. Bugfix on
14394 0.2.5.1-alpha. Patch from "NewEraCracker".
14395 - In routerlist_assert_ok(), don't take the address of a
14396 routerinfo's cache_info member unless that routerinfo is non-NULL.
14397 Fixes bug 13096; bugfix on 0.1.1.9-alpha. Patch by "teor".
14398 - Fix a large number of false positive warnings from the clang
14399 analyzer static analysis tool. This should make real warnings
14400 easier for clang analyzer to find. Patch from "teor". Closes
14403 o Distribution (systemd):
14404 - Verify configuration file via ExecStartPre in the systemd unit
14405 file. Patch from intrigeri; resolves ticket 12730.
14406 - Explicitly disable RunAsDaemon in the systemd unit file. Our
14407 current systemd unit uses "Type = simple", so systemd does not
14408 expect tor to fork. If the user has "RunAsDaemon 1" in their
14409 torrc, then things won't work as expected. This is e.g. the case
14410 on Debian (and derivatives), since there we pass "--defaults-torrc
14411 /usr/share/tor/tor-service-defaults-torrc" (that contains
14412 "RunAsDaemon 1") by default. Patch by intrigeri; resolves
14416 - Adjust the URLs in the README to refer to the new locations of
14417 several documents on the website. Fixes bug 12830. Patch from
14419 - Document 'reject6' and 'accept6' ExitPolicy entries. Resolves
14423 Changes in version 0.2.5.6-alpha - 2014-07-28
14424 Tor 0.2.5.6-alpha brings us a big step closer to slowing down the
14425 risk from guard rotation, and fixes a variety of other issues to get
14426 us closer to a release candidate.
14428 o Major features (also in 0.2.4.23):
14429 - Make the number of entry guards configurable via a new
14430 NumEntryGuards consensus parameter, and the number of directory
14431 guards configurable via a new NumDirectoryGuards consensus
14432 parameter. Implements ticket 12688.
14434 o Major bugfixes (also in 0.2.4.23):
14435 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
14436 implementation that caused incorrect results on 32-bit
14437 implementations when certain malformed inputs were used along with
14438 a small class of private ntor keys. This bug does not currently
14439 appear to allow an attacker to learn private keys or impersonate a
14440 Tor server, but it could provide a means to distinguish 32-bit Tor
14441 implementations from 64-bit Tor implementations. Fixes bug 12694;
14442 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
14446 - Perform circuit cleanup operations even when circuit
14447 construction operations are disabled (because the network is
14448 disabled, or because there isn't enough directory information).
14449 Previously, when we were not building predictive circuits, we
14450 were not closing expired circuits either. Fixes bug 8387; bugfix on
14451 0.1.1.11-alpha. This bug became visible in 0.2.4.10-alpha when we
14452 became more strict about when we have "enough directory information
14453 to build circuits".
14456 - Authorities now assign the Guard flag to the fastest 25% of the
14457 network (it used to be the fastest 50%). Also raise the consensus
14458 weight that guarantees the Guard flag from 250 to 2000. For the
14459 current network, this results in about 1100 guards, down from 2500.
14460 This step paves the way for moving the number of entry guards
14461 down to 1 (proposal 236) while still providing reasonable expected
14462 performance for most users. Implements ticket 12690.
14463 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
14465 - Slightly enhance the diagnostic message for bug 12184.
14467 o Minor bugfixes (also in 0.2.4.23):
14468 - Warn and drop the circuit if we receive an inbound 'relay early'
14469 cell. Those used to be normal to receive on hidden service circuits
14470 due to bug 1038, but the buggy Tor versions are long gone from
14471 the network so we can afford to resume watching for them. Resolves
14472 the rest of bug 1038; bugfix on 0.2.1.19.
14473 - Correct a confusing error message when trying to extend a circuit
14474 via the control protocol but we don't know a descriptor or
14475 microdescriptor for one of the specified relays. Fixes bug 12718;
14476 bugfix on 0.2.3.1-alpha.
14479 - Fix compilation when building with bufferevents enabled. (This
14480 configuration is still not expected to work, however.)
14481 Fixes bugs 12438, 12474, 11578; bugfixes on 0.2.5.1-alpha and
14482 0.2.5.3-alpha. Patches from Anthony G. Basile and Sathyanarayanan
14484 - Compile correctly with builds and forks of OpenSSL (such as
14485 LibreSSL) that disable compression. Fixes bug 12602; bugfix on
14486 0.2.1.1-alpha. Patch from "dhill".
14489 Changes in version 0.2.4.23 - 2014-07-28
14490 Tor 0.2.4.23 brings us a big step closer to slowing down the risk from
14491 guard rotation, and also backports several important fixes from the
14492 Tor 0.2.5 alpha release series.
14495 - Clients now look at the "usecreatefast" consensus parameter to
14496 decide whether to use CREATE_FAST or CREATE cells for the first hop
14497 of their circuit. This approach can improve security on connections
14498 where Tor's circuit handshake is stronger than the available TLS
14499 connection security levels, but the tradeoff is more computational
14500 load on guard relays. Implements proposal 221. Resolves ticket 9386.
14501 - Make the number of entry guards configurable via a new
14502 NumEntryGuards consensus parameter, and the number of directory
14503 guards configurable via a new NumDirectoryGuards consensus
14504 parameter. Implements ticket 12688.
14507 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
14508 implementation that caused incorrect results on 32-bit
14509 implementations when certain malformed inputs were used along with
14510 a small class of private ntor keys. This bug does not currently
14511 appear to allow an attacker to learn private keys or impersonate a
14512 Tor server, but it could provide a means to distinguish 32-bit Tor
14513 implementations from 64-bit Tor implementations. Fixes bug 12694;
14514 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
14518 - Warn and drop the circuit if we receive an inbound 'relay early'
14519 cell. Those used to be normal to receive on hidden service circuits
14520 due to bug 1038, but the buggy Tor versions are long gone from
14521 the network so we can afford to resume watching for them. Resolves
14522 the rest of bug 1038; bugfix on 0.2.1.19.
14523 - Correct a confusing error message when trying to extend a circuit
14524 via the control protocol but we don't know a descriptor or
14525 microdescriptor for one of the specified relays. Fixes bug 12718;
14526 bugfix on 0.2.3.1-alpha.
14527 - Avoid an illegal read from stack when initializing the TLS
14528 module using a version of OpenSSL without all of the ciphers
14529 used by the v2 link handshake. Fixes bug 12227; bugfix on
14530 0.2.4.8-alpha. Found by "starlight".
14533 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
14537 Changes in version 0.2.5.5-alpha - 2014-06-18
14538 Tor 0.2.5.5-alpha fixes a wide variety of remaining issues in the Tor
14539 0.2.5.x release series, including a couple of DoS issues, some
14540 performance regressions, a large number of bugs affecting the Linux
14541 seccomp2 sandbox code, and various other bugfixes. It also adds
14542 diagnostic bugfixes for a few tricky issues that we're trying to
14545 o Major features (security, traffic analysis resistance):
14546 - Several major improvements to the algorithm used to decide when to
14547 close TLS connections. Previous versions of Tor closed connections
14548 at a fixed interval after the last time a non-padding cell was
14549 sent over the connection, regardless of the target of the
14550 connection. Now, we randomize the intervals by adding up to 50% of
14551 their base value, we measure the length of time since connection
14552 last had at least one circuit, and we allow connections to known
14553 ORs to remain open a little longer (15 minutes instead of 3
14554 minutes minimum). These changes should improve Tor's resistance
14555 against some kinds of traffic analysis, and lower some overhead
14556 from needlessly closed connections. Fixes ticket 6799.
14557 Incidentally fixes ticket 12023; bugfix on 0.2.5.1-alpha.
14559 o Major bugfixes (security, OOM, new since 0.2.5.4-alpha, also in 0.2.4.22):
14560 - Fix a memory leak that could occur if a microdescriptor parse
14561 fails during the tokenizing step. This bug could enable a memory
14562 exhaustion attack by directory servers. Fixes bug 11649; bugfix
14565 o Major bugfixes (security, directory authorities):
14566 - Directory authorities now include a digest of each relay's
14567 identity key as a part of its microdescriptor.
14569 This is a workaround for bug 11743 (reported by "cypherpunks"),
14570 where Tor clients do not support receiving multiple
14571 microdescriptors with the same SHA256 digest in the same
14572 consensus. When clients receive a consensus like this, they only
14573 use one of the relays. Without this fix, a hostile relay could
14574 selectively disable some client use of target relays by
14575 constructing a router descriptor with a different identity and the
14576 same microdescriptor parameters and getting the authorities to
14577 list it in a microdescriptor consensus. This fix prevents an
14578 attacker from causing a microdescriptor collision, because the
14579 router's identity is not forgeable.
14581 o Major bugfixes (relay):
14582 - Use a direct dirport connection when uploading non-anonymous
14583 descriptors to the directory authorities. Previously, relays would
14584 incorrectly use tunnel connections under a fairly wide variety of
14585 circumstances. Fixes bug 11469; bugfix on 0.2.4.3-alpha.
14586 - When a circuit accidentally has the same circuit ID for its
14587 forward and reverse direction, correctly detect the direction of
14588 cells using that circuit. Previously, this bug made roughly one
14589 circuit in a million non-functional. Fixes bug 12195; this is a
14590 bugfix on every version of Tor.
14592 o Major bugfixes (client, pluggable transports):
14593 - When managing pluggable transports, use OS notification facilities
14594 to learn if they have crashed, and don't attempt to kill any
14595 process that has already exited. Fixes bug 8746; bugfix
14598 o Minor features (diagnostic):
14599 - When logging a warning because of bug 7164, additionally check the
14600 hash table for consistency (as proposed on ticket 11737). This may
14601 help diagnose bug 7164.
14602 - When we log a heartbeat, log how many one-hop circuits we have
14603 that are at least 30 minutes old, and log status information about
14604 a few of them. This is an attempt to track down bug 8387.
14605 - When encountering an unexpected CR while writing text to a file on
14606 Windows, log the name of the file. Should help diagnosing
14608 - Give more specific warnings when a client notices that an onion
14609 handshake has failed. Fixes ticket 9635.
14610 - Add significant new logging code to attempt to diagnose bug 12184,
14611 where relays seem to run out of available circuit IDs.
14612 - Improve the diagnostic log message for bug 8387 even further to
14613 try to improve our odds of figuring out why one-hop directory
14614 circuits sometimes do not get closed.
14616 o Minor features (security, memory management):
14617 - Memory allocation tricks (mempools and buffer freelists) are now
14618 disabled by default. You can turn them back on with
14619 --enable-mempools and --enable-buf-freelists respectively. We're
14620 disabling these features because malloc performance is good enough
14621 on most platforms, and a similar feature in OpenSSL exacerbated
14622 exploitation of the Heartbleed attack. Resolves ticket 11476.
14624 o Minor features (security):
14625 - Apply the secure SipHash-2-4 function to the hash table mapping
14626 circuit IDs and channels to circuits. We missed this one when we
14627 were converting all the other hash functions to use SipHash back
14628 in 0.2.5.3-alpha. Resolves ticket 11750.
14630 o Minor features (build):
14631 - The configure script has a --disable-seccomp option to turn off
14632 support for libseccomp on systems that have it, in case it (or
14633 Tor's use of it) is broken. Resolves ticket 11628.
14635 o Minor features (other):
14636 - Update geoip and geoip6 to the June 4 2014 Maxmind GeoLite2
14639 o Minor bugfixes (security, new since 0.2.5.4-alpha, also in 0.2.4.22):
14640 - When running a hidden service, do not allow TunneledDirConns 0;
14641 this will keep the hidden service from running, and also
14642 make it publish its descriptors directly over HTTP. Fixes bug 10849;
14643 bugfix on 0.2.1.1-alpha.
14645 o Minor bugfixes (performance):
14646 - Avoid a bug where every successful connection made us recompute
14647 the flag telling us whether we have sufficient information to
14648 build circuits. Previously, we would forget our cached value
14649 whenever we successfully opened a channel (or marked a router as
14650 running or not running for any other reason), regardless of
14651 whether we had previously believed the router to be running. This
14652 forced us to run an expensive update operation far too often.
14653 Fixes bug 12170; bugfix on 0.1.2.1-alpha.
14654 - Avoid using tor_memeq() for checking relay cell integrity. This
14655 removes a possible performance bottleneck. Fixes part of bug
14656 12169; bugfix on 0.2.1.31.
14658 o Minor bugfixes (compilation):
14659 - Fix compilation of test_status.c when building with MVSC. Bugfix
14660 on 0.2.5.4-alpha. Patch from Gisle Vanem.
14661 - Resolve GCC complaints on OpenBSD about discarding constness in
14662 TO_{ORIGIN,OR}_CIRCUIT functions. Fixes part of bug 11633; bugfix
14663 on 0.1.1.23. Patch from Dana Koch.
14664 - Resolve clang complaints on OpenBSD with -Wshorten-64-to-32 due to
14665 treatment of long and time_t as comparable types. Fixes part of
14666 bug 11633. Patch from Dana Koch.
14667 - Make Tor compile correctly with --disable-buf-freelists. Fixes bug
14668 11623; bugfix on 0.2.5.3-alpha.
14669 - When deciding whether to build the 64-bit curve25519
14670 implementation, detect platforms where we can compile 128-bit
14671 arithmetic but cannot link it. Fixes bug 11729; bugfix on
14672 0.2.4.8-alpha. Patch from "conradev".
14673 - Fix compilation when DNS_CACHE_DEBUG is enabled. Fixes bug 11761;
14674 bugfix on 0.2.3.13-alpha. Found by "cypherpunks".
14675 - Fix compilation with dmalloc. Fixes bug 11605; bugfix
14678 o Minor bugfixes (Directory server):
14679 - When sending a compressed set of descriptors or microdescriptors,
14680 make sure to finalize the zlib stream. Previously, we would write
14681 all the compressed data, but if the last descriptor we wanted to
14682 send was missing or too old, we would not mark the stream as
14683 finished. This caused problems for decompression tools. Fixes bug
14684 11648; bugfix on 0.1.1.23.
14686 o Minor bugfixes (Linux seccomp sandbox):
14687 - Make the seccomp sandbox code compile under ARM Linux. Fixes bug
14688 11622; bugfix on 0.2.5.1-alpha.
14689 - Avoid crashing when re-opening listener ports with the seccomp
14690 sandbox active. Fixes bug 12115; bugfix on 0.2.5.1-alpha.
14691 - Avoid crashing with the seccomp sandbox enabled along with
14692 ConstrainedSockets. Fixes bug 12139; bugfix on 0.2.5.1-alpha.
14693 - When we receive a SIGHUP with the sandbox enabled, correctly
14694 support rotating our log files. Fixes bug 12032; bugfix
14696 - Avoid crash when running with sandboxing enabled and
14697 DirReqStatistics not disabled. Fixes bug 12035; bugfix
14699 - Fix a "BUG" warning when trying to write bridge-stats files with
14700 the Linux syscall sandbox filter enabled. Fixes bug 12041; bugfix
14702 - Prevent the sandbox from crashing on startup when run with the
14703 --enable-expensive-hardening configuration option. Fixes bug
14704 11477; bugfix on 0.2.5.4-alpha.
14705 - When running with DirPortFrontPage and sandboxing both enabled,
14706 reload the DirPortFrontPage correctly when restarting. Fixes bug
14707 12028; bugfix on 0.2.5.1-alpha.
14708 - Don't try to enable the sandbox when using the Tor binary to check
14709 its configuration, hash a passphrase, or so on. Doing so was
14710 crashing on startup for some users. Fixes bug 11609; bugfix
14712 - Avoid warnings when running with sandboxing and node statistics
14713 enabled at the same time. Fixes part of 12064; bugfix on
14714 0.2.5.1-alpha. Patch from Michael Wolf.
14715 - Avoid warnings when running with sandboxing enabled at the same
14716 time as cookie authentication, hidden services, or directory
14717 authority voting. Fixes part of 12064; bugfix on 0.2.5.1-alpha.
14718 - Do not allow options that require calls to exec to be enabled
14719 alongside the seccomp2 sandbox: they will inevitably crash. Fixes
14720 bug 12043; bugfix on 0.2.5.1-alpha.
14721 - Handle failures in getpwnam()/getpwuid() when running with the
14722 User option set and the Linux syscall sandbox enabled. Fixes bug
14723 11946; bugfix on 0.2.5.1-alpha.
14724 - Refactor the getaddrinfo workaround that the seccomp sandbox uses
14725 to avoid calling getaddrinfo() after installing the sandbox
14726 filters. Previously, it preloaded a cache with the IPv4 address
14727 for our hostname, and nothing else. Now, it loads the cache with
14728 every address that it used to initialize the Tor process. Fixes
14729 bug 11970; bugfix on 0.2.5.1-alpha.
14731 o Minor bugfixes (pluggable transports):
14732 - Enable the ExtORPortCookieAuthFile option, to allow changing the
14733 default location of the authentication token for the extended OR
14734 Port as used by sever-side pluggable transports. We had
14735 implemented this option before, but the code to make it settable
14736 had been omitted. Fixes bug 11635; bugfix on 0.2.5.1-alpha.
14737 - Avoid another 60-second delay when starting Tor in a pluggable-
14738 transport-using configuration when we already have cached
14739 descriptors for our bridges. Fixes bug 11965; bugfix
14742 o Minor bugfixes (client):
14743 - Avoid "Tried to open a socket with DisableNetwork set" warnings
14744 when starting a client with bridges configured and DisableNetwork
14745 set. (Tor launcher starts Tor with DisableNetwork set the first
14746 time it runs.) Fixes bug 10405; bugfix on 0.2.3.9-alpha.
14748 o Minor bugfixes (testing):
14749 - The Python parts of the test scripts now work on Python 3 as well
14750 as Python 2, so systems where '/usr/bin/python' is Python 3 will
14751 no longer have the tests break. Fixes bug 11608; bugfix
14753 - When looking for versions of python that we could run the tests
14754 with, check for "python2.7" and "python3.3"; previously we were
14755 only looking for "python", "python2", and "python3". Patch from
14756 Dana Koch. Fixes bug 11632; bugfix on 0.2.5.2-alpha.
14757 - Fix all valgrind warnings produced by the unit tests. There were
14758 over a thousand memory leak warnings previously, mostly produced
14759 by forgetting to free things in the unit test code. Fixes bug
14760 11618, bugfixes on many versions of Tor.
14762 o Minor bugfixes (tor-fw-helper):
14763 - Give a correct log message when tor-fw-helper fails to launch.
14764 (Previously, we would say something like "tor-fw-helper sent us a
14765 string we could not parse".) Fixes bug 9781; bugfix
14768 o Minor bugfixes (relay, threading):
14769 - Check return code on spawn_func() in cpuworker code, so that we
14770 don't think we've spawned a nonworking cpuworker and write junk to
14771 it forever. Fix related to bug 4345; bugfix on all released Tor
14772 versions. Found by "skruffy".
14773 - Use a pthread_attr to make sure that spawn_func() cannot return an
14774 error while at the same time launching a thread. Fix related to
14775 bug 4345; bugfix on all released Tor versions. Reported
14778 o Minor bugfixes (relay, oom prevention):
14779 - Correctly detect the total available system memory. We tried to do
14780 this in 0.2.5.4-alpha, but the code was set up to always return an
14781 error value, even on success. Fixes bug 11805; bugfix
14784 o Minor bugfixes (relay, other):
14785 - We now drop CREATE cells for already-existent circuit IDs and for
14786 zero-valued circuit IDs, regardless of other factors that might
14787 otherwise have called for DESTROY cells. Fixes bug 12191; bugfix
14789 - Avoid an illegal read from stack when initializing the TLS module
14790 using a version of OpenSSL without all of the ciphers used by the
14791 v2 link handshake. Fixes bug 12227; bugfix on 0.2.4.8-alpha. Found
14793 - When rejecting DATA cells for stream_id zero, still count them
14794 against the circuit's deliver window so that we don't fail to send
14795 a SENDME. Fixes bug 11246; bugfix on 0.2.4.10-alpha.
14797 o Minor bugfixes (logging):
14798 - Fix a misformatted log message about delayed directory fetches.
14799 Fixes bug 11654; bugfix on 0.2.5.3-alpha.
14800 - Squelch a spurious LD_BUG message "No origin circuit for
14801 successful SOCKS stream" in certain hidden service failure cases;
14805 - Include a tor.service file in contrib/dist for use with systemd.
14806 Some distributions will be able to use this file unmodified;
14807 others will need to tweak it, or write their own. Patch from Jamie
14808 Nguyen; resolves ticket 8368.
14811 - Clean up several option names in the manpage to match their real
14812 names, add the missing documentation for a couple of testing and
14813 directory authority options, remove the documentation for a
14814 V2-directory fetching option that no longer exists. Resolves
14816 - Correct the documentation so that it lists the correct directory
14817 for the stats files. (They are in a subdirectory called "stats",
14819 - In the manpage, move more authority-only options into the
14820 directory authority section so that operators of regular directory
14821 caches don't get confused.
14824 - The contrib directory has been sorted and tidied. Before, it was
14825 an unsorted dumping ground for useful and not-so-useful things.
14826 Now, it is divided based on functionality, and the items which
14827 seemed to be nonfunctional or useless have been removed. Resolves
14828 ticket 8966; based on patches from "rl1987".
14831 - Remove /tor/dbg-stability.txt URL that was meant to help debug WFU
14832 and MTBF calculations, but that nobody was using. Fixes ticket 11742.
14833 - The TunnelDirConns and PreferTunnelledDirConns options no longer
14834 exist; tunneled directory connections have been available since
14835 0.1.2.5-alpha, and turning them off is not a good idea. This is a
14836 brute-force fix for 10849, where "TunnelDirConns 0" would break
14840 Changes in version 0.2.4.22 - 2014-05-16
14841 Tor 0.2.4.22 backports numerous high-priority fixes from the Tor 0.2.5
14842 alpha release series. These include blocking all authority signing
14843 keys that may have been affected by the OpenSSL "heartbleed" bug,
14844 choosing a far more secure set of TLS ciphersuites by default, closing
14845 a couple of memory leaks that could be used to run a target relay out
14846 of RAM, and several others.
14848 o Major features (security, backport from 0.2.5.4-alpha):
14849 - Block authority signing keys that were used on authorities
14850 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
14851 don't have any evidence that these keys _were_ compromised; we're
14852 doing this to be prudent.) Resolves ticket 11464.
14854 o Major bugfixes (security, OOM):
14855 - Fix a memory leak that could occur if a microdescriptor parse
14856 fails during the tokenizing step. This bug could enable a memory
14857 exhaustion attack by directory servers. Fixes bug 11649; bugfix
14860 o Major bugfixes (TLS cipher selection, backport from 0.2.5.4-alpha):
14861 - The relay ciphersuite list is now generated automatically based on
14862 uniform criteria, and includes all OpenSSL ciphersuites with
14863 acceptable strength and forward secrecy. Previously, we had left
14864 some perfectly fine ciphersuites unsupported due to omission or
14865 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
14866 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
14867 - Relays now trust themselves to have a better view than clients of
14868 which TLS ciphersuites are better than others. (Thanks to bug
14869 11513, the relay list is now well-considered, whereas the client
14870 list has been chosen mainly for anti-fingerprinting purposes.)
14871 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
14872 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
14873 AES128. Resolves ticket 11528.
14874 - Clients now try to advertise the same list of ciphersuites as
14875 Firefox 28. This change enables selection of (fast) GCM
14876 ciphersuites, disables some strange old ciphers, and stops
14877 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
14878 Resolves ticket 11438.
14880 o Minor bugfixes (configuration, security):
14881 - When running a hidden service, do not allow TunneledDirConns 0:
14882 trying to set that option together with a hidden service would
14883 otherwise prevent the hidden service from running, and also make
14884 it publish its descriptors directly over HTTP. Fixes bug 10849;
14885 bugfix on 0.2.1.1-alpha.
14887 o Minor bugfixes (controller, backport from 0.2.5.4-alpha):
14888 - Avoid sending a garbage value to the controller when a circuit is
14889 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
14891 o Minor bugfixes (exit relay, backport from 0.2.5.4-alpha):
14892 - Stop leaking memory when we successfully resolve a PTR record.
14893 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
14895 o Minor bugfixes (bridge client, backport from 0.2.5.4-alpha):
14896 - Avoid 60-second delays in the bootstrapping process when Tor is
14897 launching for a second time while using bridges. Fixes bug 9229;
14898 bugfix on 0.2.0.3-alpha.
14900 o Minor bugfixes (relays and bridges, backport from 0.2.5.4-alpha):
14901 - Give the correct URL in the warning message when trying to run a
14902 relay on an ancient version of Windows. Fixes bug 9393.
14904 o Minor bugfixes (compilation):
14905 - Fix a compilation error when compiling with --disable-curve25519.
14906 Fixes bug 9700; bugfix on 0.2.4.17-rc.
14909 - Downgrade the warning severity for the the "md was still
14910 referenced 1 node(s)" warning. Tor 0.2.5.4-alpha has better code
14911 for trying to diagnose this bug, and the current warning in
14912 earlier versions of tor achieves nothing useful. Addresses warning
14915 o Minor features (log verbosity, backport from 0.2.5.4-alpha):
14916 - When we run out of usable circuit IDs on a channel, log only one
14917 warning for the whole channel, and describe how many circuits
14918 there were on the channel. Fixes part of ticket 11553.
14920 o Minor features (security, backport from 0.2.5.4-alpha):
14921 - Decrease the lower limit of MaxMemInCellQueues to 256 MBytes (but
14922 leave the default at 8GBytes), to better support Raspberry Pi
14923 users. Fixes bug 9686; bugfix on 0.2.4.14-alpha.
14925 o Documentation (backport from 0.2.5.4-alpha):
14926 - Correctly document that we search for a system torrc file before
14927 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
14931 Changes in version 0.2.5.4-alpha - 2014-04-25
14932 Tor 0.2.5.4-alpha includes several security and performance
14933 improvements for clients and relays, including blacklisting authority
14934 signing keys that were used while susceptible to the OpenSSL
14935 "heartbleed" bug, fixing two expensive functions on busy relays,
14936 improved TLS ciphersuite preference lists, support for run-time
14937 hardening on compilers that support AddressSanitizer, and more work on
14938 the Linux sandbox code.
14940 There are also several usability fixes for clients (especially clients
14941 that use bridges), two new TransPort protocols supported (one on
14942 OpenBSD, one on FreeBSD), and various other bugfixes.
14944 This release marks end-of-life for Tor 0.2.2.x; those Tor versions
14945 have accumulated many known flaws; everyone should upgrade.
14947 o Major features (security):
14948 - If you don't specify MaxMemInQueues yourself, Tor now tries to
14949 pick a good value based on your total system memory. Previously,
14950 the default was always 8 GB. You can still override the default by
14951 setting MaxMemInQueues yourself. Resolves ticket 11396.
14952 - Block authority signing keys that were used on authorities
14953 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
14954 don't have any evidence that these keys _were_ compromised; we're
14955 doing this to be prudent.) Resolves ticket 11464.
14957 o Major features (relay performance):
14958 - Speed up server-side lookups of rendezvous and introduction point
14959 circuits by using hashtables instead of linear searches. These
14960 functions previously accounted between 3 and 7% of CPU usage on
14961 some busy relays. Resolves ticket 9841.
14962 - Avoid wasting CPU when extending a circuit over a channel that is
14963 nearly out of circuit IDs. Previously, we would do a linear scan
14964 over possible circuit IDs before finding one or deciding that we
14965 had exhausted our possibilities. Now, we try at most 64 random
14966 circuit IDs before deciding that we probably won't succeed. Fixes
14967 a possible root cause of ticket 11553.
14969 o Major features (seccomp2 sandbox, Linux only):
14970 - The seccomp2 sandbox can now run a test network for multiple hours
14971 without crashing. The sandbox is still experimental, and more bugs
14972 will probably turn up. To try it, enable "Sandbox 1" on a Linux
14973 host. Resolves ticket 11351.
14974 - Strengthen sandbox code: the sandbox can now test the arguments
14975 for rename(), and blocks _sysctl() entirely. Resolves another part
14977 - When the sandbox blocks a system call, it now tries to log a stack
14978 trace before exiting. Resolves ticket 11465.
14980 o Major bugfixes (TLS cipher selection):
14981 - The relay ciphersuite list is now generated automatically based on
14982 uniform criteria, and includes all OpenSSL ciphersuites with
14983 acceptable strength and forward secrecy. Previously, we had left
14984 some perfectly fine ciphersuites unsupported due to omission or
14985 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
14986 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
14987 - Relays now trust themselves to have a better view than clients of
14988 which TLS ciphersuites are better than others. (Thanks to bug
14989 11513, the relay list is now well-considered, whereas the client
14990 list has been chosen mainly for anti-fingerprinting purposes.)
14991 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
14992 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
14993 AES128. Resolves ticket 11528.
14994 - Clients now try to advertise the same list of ciphersuites as
14995 Firefox 28. This change enables selection of (fast) GCM
14996 ciphersuites, disables some strange old ciphers, and stops
14997 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
14998 Resolves ticket 11438.
15000 o Major bugfixes (bridge client):
15001 - Avoid 60-second delays in the bootstrapping process when Tor is
15002 launching for a second time while using bridges. Fixes bug 9229;
15003 bugfix on 0.2.0.3-alpha.
15005 o Minor features (transparent proxy, *BSD):
15006 - Support FreeBSD's ipfw firewall interface for TransPort ports on
15007 FreeBSD. To enable it, set "TransProxyType ipfw". Resolves ticket
15008 10267; patch from "yurivict".
15009 - Support OpenBSD's divert-to rules with the pf firewall for
15010 transparent proxy ports. To enable it, set "TransProxyType
15011 pf-divert". This allows Tor to run a TransPort transparent proxy
15012 port on OpenBSD 4.4 or later without root privileges. See the
15013 pf.conf(5) manual page for information on configuring pf to use
15014 divert-to rules. Closes ticket 10896; patch from Dana Koch.
15016 o Minor features (security):
15017 - New --enable-expensive-hardening option to enable security
15018 hardening options that consume nontrivial amounts of CPU and
15019 memory. Right now, this includes AddressSanitizer and UbSan, which
15020 are supported in newer versions of GCC and Clang. Closes ticket
15023 o Minor features (log verbosity):
15024 - Demote the message that we give when a flushing connection times
15025 out for too long from NOTICE to INFO. It was usually meaningless.
15026 Resolves ticket 5286.
15027 - Don't log so many notice-level bootstrapping messages at startup
15028 about downloading descriptors. Previously, we'd log a notice
15029 whenever we learned about more routers. Now, we only log a notice
15030 at every 5% of progress. Fixes bug 9963.
15031 - Warn less verbosely when receiving a malformed
15032 ESTABLISH_RENDEZVOUS cell. Fixes ticket 11279.
15033 - When we run out of usable circuit IDs on a channel, log only one
15034 warning for the whole channel, and describe how many circuits
15035 there were on the channel. Fixes part of ticket 11553.
15037 o Minor features (relay):
15038 - If a circuit timed out for at least 3 minutes, check if we have a
15039 new external IP address, and publish a new descriptor with the new
15040 IP address if it changed. Resolves ticket 2454.
15042 o Minor features (controller):
15043 - Make the entire exit policy available from the control port via
15044 GETINFO exit-policy/*. Implements enhancement 7952. Patch from
15046 - Because of the fix for ticket 11396, the real limit for memory
15047 usage may no longer match the configured MaxMemInQueues value. The
15048 real limit is now exposed via GETINFO limits/max-mem-in-queues.
15050 o Minor features (bridge client):
15051 - Report a more useful failure message when we can't connect to a
15052 bridge because we don't have the right pluggable transport
15053 configured. Resolves ticket 9665. Patch from Fábio J. Bertinatto.
15055 o Minor features (diagnostic):
15056 - Add more log messages to diagnose bug 7164, which causes
15057 intermittent "microdesc_free() called but md was still referenced"
15058 warnings. We now include more information, to figure out why we
15059 might be cleaning a microdescriptor for being too old if it's
15060 still referenced by a live node_t object.
15062 o Minor bugfixes (client, DNSPort):
15063 - When using DNSPort, try to respond to AAAA requests with AAAA
15064 answers. Previously, we hadn't looked at the request type when
15065 deciding which answer type to prefer. Fixes bug 10468; bugfix on
15067 - When receiving a DNS query for an unsupported record type, reply
15068 with no answer rather than with a NOTIMPL error. This behavior
15069 isn't correct either, but it will break fewer client programs, we
15070 hope. Fixes bug 10268; bugfix on 0.2.0.1-alpha. Original patch
15073 o Minor bugfixes (exit relay):
15074 - Stop leaking memory when we successfully resolve a PTR record.
15075 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
15077 o Minor bugfixes (bridge client):
15078 - Stop accepting bridge lines containing hostnames. Doing so would
15079 cause clients to perform DNS requests on the hostnames, which was
15080 not sensible behavior. Fixes bug 10801; bugfix on 0.2.0.1-alpha.
15081 - Avoid a 60-second delay in the bootstrapping process when a Tor
15082 client with pluggable transports re-reads its configuration at
15083 just the wrong time. Re-fixes bug 11156; bugfix on 0.2.5.3-alpha.
15085 o Minor bugfixes (client, logging during bootstrap):
15086 - Warn only once if we start logging in an unsafe way. Previously,
15087 we complain as many times as we had problems. Fixes bug 9870;
15088 bugfix on 0.2.5.1-alpha.
15089 - Only report the first fatal bootstrap error on a given OR
15090 connection. This stops us from telling the controller bogus error
15091 messages like "DONE". Fixes bug 10431; bugfix on 0.2.1.1-alpha.
15092 - Be more helpful when trying to run sandboxed on Linux without
15093 libseccomp. Instead of saying "Sandbox is not implemented on this
15094 platform", we now explain that we need to be built with
15095 libseccomp. Fixes bug 11543; bugfix on 0.2.5.1-alpha.
15096 - Avoid generating spurious warnings when starting with
15097 DisableNetwork enabled. Fixes bug 11200 and bug 10405; bugfix on
15100 o Minor bugfixes (closing OR connections):
15101 - If write_to_buf() in connection_write_to_buf_impl_() ever fails,
15102 check if it's an or_connection_t and correctly call
15103 connection_or_close_for_error() rather than
15104 connection_mark_for_close() directly. Fixes bug 11304; bugfix on
15106 - When closing all connections on setting DisableNetwork to 1, use
15107 connection_or_close_normally() rather than closing OR connections
15108 out from under the channel layer. Fixes bug 11306; bugfix on
15111 o Minor bugfixes (controller):
15112 - Avoid sending a garbage value to the controller when a circuit is
15113 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
15115 o Minor bugfixes (tor-fw-helper):
15116 - Allow tor-fw-helper to build again by adding src/ext to its
15117 CPPFLAGS. Fixes bug 11296; bugfix on 0.2.5.3-alpha.
15119 o Minor bugfixes (bridges):
15120 - Avoid potential crashes or bad behavior when launching a
15121 server-side managed proxy with ORPort or ExtORPort temporarily
15122 disabled. Fixes bug 9650; bugfix on 0.2.3.16-alpha.
15124 o Minor bugfixes (platform-specific):
15125 - Fix compilation on Solaris, which does not have <endian.h>. Fixes
15126 bug 11426; bugfix on 0.2.5.3-alpha.
15127 - When dumping a malformed directory object to disk, save it in
15128 binary mode on Windows, not text mode. Fixes bug 11342; bugfix on
15130 - Don't report failures from make_socket_reuseable() on incoming
15131 sockets on OSX: this can happen when incoming connections close
15132 early. Fixes bug 10081.
15134 o Minor bugfixes (trivial memory leaks):
15135 - Fix a small memory leak when signing a directory object. Fixes bug
15136 11275; bugfix on 0.2.4.13-alpha.
15137 - Free placeholder entries in our circuit table at exit; fixes a
15138 harmless memory leak. Fixes bug 11278; bugfix on 0.2.5.1-alpha.
15139 - Don't re-initialize a second set of OpenSSL mutexes when starting
15140 up. Previously, we'd make one set of mutexes, and then immediately
15141 replace them with another. Fixes bug 11726; bugfix on
15143 - Resolve some memory leaks found by coverity in the unit tests, on
15144 exit in tor-gencert, and on a failure to compute digests for our
15145 own keys when generating a v3 networkstatus vote. These leaks
15146 should never have affected anyone in practice.
15148 o Minor bugfixes (hidden service):
15149 - Only retry attempts to connect to a chosen rendezvous point 8
15150 times, not 30. Fixes bug 4241; bugfix on 0.1.0.1-rc.
15152 o Minor bugfixes (misc code correctness):
15153 - Fix various instances of undefined behavior in channeltls.c,
15154 tor_memmem(), and eventdns.c that would cause us to construct
15155 pointers to memory outside an allocated object. (These invalid
15156 pointers were not accessed, but C does not even allow them to
15157 exist.) Fixes bug 10363; bugfixes on 0.1.1.1-alpha, 0.1.2.1-alpha,
15158 0.2.0.10-alpha, and 0.2.3.6-alpha. Reported by "bobnomnom".
15159 - Use the AddressSanitizer and Ubsan sanitizers (in clang-3.4) to
15160 fix some miscellaneous errors in our tests and codebase. Fixes bug
15161 11232. Bugfixes on versions back as far as 0.2.1.11-alpha.
15162 - Always check return values for unlink, munmap, UnmapViewOfFile;
15163 check strftime return values more often. In some cases all we can
15164 do is report a warning, but this may help prevent deeper bugs from
15165 going unnoticed. Closes ticket 8787; bugfixes on many, many tor
15167 - Fix numerous warnings from the clang "scan-build" static analyzer.
15168 Some of these are programming style issues; some of them are false
15169 positives that indicated awkward code; some are undefined behavior
15170 cases related to constructing (but not using) invalid pointers;
15171 some are assumptions about API behavior; some are (harmlessly)
15172 logging sizeof(ptr) bytes from a token when sizeof(*ptr) would be
15173 correct; and one or two are genuine bugs that weren't reachable
15174 from the rest of the program. Fixes bug 8793; bugfixes on many,
15178 - Build the torify.1 manpage again. Previously, we were only trying
15179 to build it when also building tor-fw-helper. That's why we didn't
15180 notice that we'd broken the ability to build it. Fixes bug 11321;
15181 bugfix on 0.2.5.1-alpha.
15182 - Fix the layout of the SOCKSPort flags in the manpage. Fixes bug
15183 11061; bugfix on 0.2.4.7-alpha.
15184 - Correctly document that we search for a system torrc file before
15185 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
15187 - Resolve warnings from Doxygen.
15189 o Code simplifications and refactoring:
15190 - Remove is_internal_IP() function. Resolves ticket 4645.
15191 - Remove unused function circuit_dump_by_chan from circuitlist.c.
15192 Closes issue 9107; patch from "marek".
15193 - Change our use of the ENUM_BF macro to avoid declarations that
15196 o Deprecated versions:
15197 - Tor 0.2.2.x has reached end-of-life; it has received no patches or
15198 attention for some while. Directory authorities no longer accept
15199 descriptors from relays running any version of Tor prior to Tor
15200 0.2.3.16-alpha. Resolves ticket 11149.
15203 - New macros in test.h to simplify writing mock-functions for unit
15204 tests. Part of ticket 11507. Patch from Dana Koch.
15205 - Complete tests for the status.c module. Resolves ticket 11507.
15206 Patch from Dana Koch.
15209 - Remove all code for the long unused v1 directory protocol.
15210 Resolves ticket 11070.
15213 Changes in version 0.2.5.3-alpha - 2014-03-22
15214 Tor 0.2.5.3-alpha includes all the fixes from 0.2.4.21. It contains
15215 two new anti-DoS features for Tor relays, resolves a bug that kept
15216 SOCKS5 support for IPv6 from working, fixes several annoying usability
15217 issues for bridge users, and removes more old code for unused
15220 The Tor 0.2.5.x release series is now in patch-freeze: no feature
15221 patches not already written will be considered for inclusion in 0.2.5.x.
15223 o Major features (relay security, DoS-resistance):
15224 - When deciding whether we have run out of memory and we need to
15225 close circuits, also consider memory allocated in buffers for
15226 streams attached to each circuit.
15228 This change, which extends an anti-DoS feature introduced in
15229 0.2.4.13-alpha and improved in 0.2.4.14-alpha, lets Tor exit relays
15230 better resist more memory-based DoS attacks than before. Since the
15231 MaxMemInCellQueues option now applies to all queues, it is renamed
15232 to MaxMemInQueues. This feature fixes bug 10169.
15233 - Avoid hash-flooding denial-of-service attacks by using the secure
15234 SipHash-2-4 hash function for our hashtables. Without this
15235 feature, an attacker could degrade performance of a targeted
15236 client or server by flooding their data structures with a large
15237 number of entries to be stored at the same hash table position,
15238 thereby slowing down the Tor instance. With this feature, hash
15239 table positions are derived from a randomized cryptographic key,
15240 and an attacker cannot predict which entries will collide. Closes
15242 - Decrease the lower limit of MaxMemInQueues to 256 MBytes (but leave
15243 the default at 8GBytes), to better support Raspberry Pi users. Fixes
15244 bug 9686; bugfix on 0.2.4.14-alpha.
15246 o Minor features (bridges, pluggable transports):
15247 - Bridges now write the SHA1 digest of their identity key
15248 fingerprint (that is, a hash of a hash of their public key) to
15249 notice-level logs, and to a new hashed-fingerprint file. This
15250 information will help bridge operators look up their bridge in
15251 Globe and similar tools. Resolves ticket 10884.
15252 - Improve the message that Tor displays when running as a bridge
15253 using pluggable transports without an Extended ORPort listener.
15254 Also, log the message in the log file too. Resolves ticket 11043.
15256 o Minor features (other):
15257 - Add a new option, PredictedPortsRelevanceTime, to control how long
15258 after having received a request to connect to a given port Tor
15259 will try to keep circuits ready in anticipation of future requests
15260 for that port. Patch from "unixninja92"; implements ticket 9176.
15261 - Generate a warning if any ports are listed in the SocksPolicy,
15262 DirPolicy, AuthDirReject, AuthDirInvalid, AuthDirBadDir, or
15263 AuthDirBadExit options. (These options only support address
15264 ranges.) Fixes part of ticket 11108.
15265 - Update geoip and geoip6 to the February 7 2014 Maxmind GeoLite2
15268 o Minor bugfixes (new since 0.2.5.2-alpha, also in 0.2.4.21):
15269 - Build without warnings under clang 3.4. (We have some macros that
15270 define static functions only some of which will get used later in
15271 the module. Starting with clang 3.4, these give a warning unless the
15272 unused attribute is set on them.) Resolves ticket 10904.
15273 - Fix build warnings about missing "a2x" comment when building the
15274 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
15275 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
15277 o Minor bugfixes (client):
15278 - Improve the log message when we can't connect to a hidden service
15279 because all of the hidden service directory nodes hosting its
15280 descriptor are excluded. Improves on our fix for bug 10722, which
15281 was a bugfix on 0.2.0.10-alpha.
15282 - Raise a control port warning when we fail to connect to all of
15283 our bridges. Previously, we didn't inform the controller, and
15284 the bootstrap process would stall. Fixes bug 11069; bugfix on
15286 - Exit immediately when a process-owning controller exits.
15287 Previously, tor relays would wait for a little while after their
15288 controller exited, as if they had gotten an INT signal -- but this
15289 was problematic, since there was no feedback for the user. To do a
15290 clean shutdown, controllers should send an INT signal and give Tor
15291 a chance to clean up. Fixes bug 10449; bugfix on 0.2.2.28-beta.
15292 - Stop attempting to connect to bridges before our pluggable
15293 transports are configured (harmless but resulted in some erroneous
15294 log messages). Fixes bug 11156; bugfix on 0.2.3.2-alpha.
15295 - Fix connections to IPv6 addresses over SOCKS5. Previously, we were
15296 generating incorrect SOCKS5 responses, and confusing client
15297 applications. Fixes bug 10987; bugfix on 0.2.4.7-alpha.
15299 o Minor bugfixes (relays and bridges):
15300 - Avoid crashing on a malformed resolv.conf file when running a
15301 relay using Libevent 1. Fixes bug 8788; bugfix on 0.1.1.23.
15302 - Non-exit relays no longer launch mock DNS requests to check for
15303 DNS hijacking. This has been unnecessary since 0.2.1.7-alpha, when
15304 non-exit relays stopped servicing DNS requests. Fixes bug 965;
15305 bugfix on 0.2.1.7-alpha. Patch from Matt Pagan.
15306 - Bridges now report complete directory request statistics. Related
15307 to bug 5824; bugfix on 0.2.2.1-alpha.
15308 - Bridges now never collect statistics that were designed for
15309 relays. Fixes bug 5824; bugfix on 0.2.3.8-alpha.
15310 - Stop giving annoying warning messages when we decide not to launch
15311 a pluggable transport proxy that we don't need (because there are
15312 no bridges configured to use it). Resolves ticket 5018; bugfix
15314 - Give the correct URL in the warning message when trying to run a
15315 relay on an ancient version of Windows. Fixes bug 9393.
15317 o Minor bugfixes (backtrace support):
15318 - Support automatic backtraces on more platforms by using the
15319 "-fasynchronous-unwind-tables" compiler option. This option is
15320 needed for platforms like 32-bit Intel where "-fomit-frame-pointer"
15321 is on by default and table generation is not. This doesn't yet
15322 add Windows support; only Linux, OSX, and some BSDs are affected.
15323 Reported by 'cypherpunks'; fixes bug 11047; bugfix on 0.2.5.2-alpha.
15324 - Avoid strange behavior if two threads hit failed assertions at the
15325 same time and both try to log backtraces at once. (Previously, if
15326 this had happened, both threads would have stored their intermediate
15327 results in the same buffer, and generated junk outputs.) Reported by
15328 "cypherpunks". Fixes bug 11048; bugfix on 0.2.5.2-alpha.
15329 - Fix a compiler warning in format_number_sigsafe(). Bugfix on
15330 0.2.5.2-alpha; patch from Nick Hopper.
15332 o Minor bugfixes (unit tests):
15333 - Fix a small bug in the unit tests that might have made the tests
15334 call 'chmod' with an uninitialized bitmask. Fixes bug 10928;
15335 bugfix on 0.2.5.1-alpha. Patch from Dana Koch.
15338 - Remove all remaining code related to version-0 hidden service
15339 descriptors: they have not been in use since 0.2.2.1-alpha. Fixes
15340 the rest of bug 10841.
15343 - Document in the manpage that "KBytes" may also be written as
15344 "kilobytes" or "KB", that "Kbits" may also be written as
15345 "kilobits", and so forth. Closes ticket 9222.
15346 - Document that the ClientOnly config option overrides ORPort.
15347 Our old explanation made ClientOnly sound as though it did
15348 nothing at all. Resolves bug 9059.
15349 - Explain that SocksPolicy, DirPolicy, and similar options don't
15350 take port arguments. Fixes the other part of ticket 11108.
15351 - Fix a comment about the rend_server_descriptor_t.protocols field
15352 to more accurately describe its range. Also, make that field
15353 unsigned, to more accurately reflect its usage. Fixes bug 9099;
15354 bugfix on 0.2.1.5-alpha.
15355 - Fix the manpage's description of HiddenServiceAuthorizeClient:
15356 the maximum client name length is 16, not 19. Fixes bug 11118;
15357 bugfix on 0.2.1.6-alpha.
15359 o Code simplifications and refactoring:
15360 - Get rid of router->address, since in all cases it was just the
15361 string representation of router->addr. Resolves ticket 5528.
15363 o Test infrastructure:
15364 - Update to the latest version of tinytest.
15365 - Improve the tinytest implementation of string operation tests so
15366 that comparisons with NULL strings no longer crash the tests; they
15367 now just fail, normally. Fixes bug 9004; bugfix on 0.2.2.4-alpha.
15370 Changes in version 0.2.4.21 - 2014-02-28
15371 Tor 0.2.4.21 further improves security against potential adversaries who
15372 find breaking 1024-bit crypto doable, and backports several stability
15373 and robustness patches from the 0.2.5 branch.
15375 o Major features (client security):
15376 - When we choose a path for a 3-hop circuit, make sure it contains
15377 at least one relay that supports the NTor circuit extension
15378 handshake. Otherwise, there is a chance that we're building
15379 a circuit that's worth attacking by an adversary who finds
15380 breaking 1024-bit crypto doable, and that chance changes the game
15381 theory. Implements ticket 9777.
15384 - Do not treat streams that fail with reason
15385 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
15386 since it could also indicate an ENETUNREACH connection error. Fixes
15387 part of bug 10777; bugfix on 0.2.4.8-alpha.
15389 o Code simplification and refactoring:
15390 - Remove data structures which were introduced to implement the
15391 CellStatistics option: they are now redundant with the new timestamp
15392 field in the regular packed_cell_t data structure, which we did
15393 in 0.2.4.18-rc in order to resolve bug 9093. Resolves ticket 10870.
15396 - Always clear OpenSSL bignums before freeing them -- even bignums
15397 that don't contain secrets. Resolves ticket 10793. Patch by
15399 - Build without warnings under clang 3.4. (We have some macros that
15400 define static functions only some of which will get used later in
15401 the module. Starting with clang 3.4, these give a warning unless the
15402 unused attribute is set on them.) Resolves ticket 10904.
15403 - Update geoip and geoip6 files to the February 7 2014 Maxmind
15404 GeoLite2 Country database.
15407 - Set the listen() backlog limit to the largest actually supported
15408 on the system, not to the value in a header file. Fixes bug 9716;
15409 bugfix on every released Tor.
15410 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
15411 exit node as a NOROUTE error, not an INTERNAL error, since they
15412 can apparently happen when trying to connect to the wrong sort
15413 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
15414 - Fix build warnings about missing "a2x" comment when building the
15415 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
15416 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
15417 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
15418 not entirely remove it from the connection lists. Fixes bug 9602;
15419 bugfix on 0.2.4.4-alpha.
15420 - Fix a segmentation fault in our benchmark code when running with
15421 Fedora's OpenSSL package, or any other OpenSSL that provides
15422 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
15423 - Turn "circuit handshake stats since last time" log messages into a
15424 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
15426 o Documentation fixes:
15427 - Document that all but one DirPort entry must have the NoAdvertise
15428 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
15431 Changes in version 0.2.5.2-alpha - 2014-02-13
15432 Tor 0.2.5.2-alpha includes all the fixes from 0.2.4.18-rc and 0.2.4.20,
15433 like the "poor random number generation" fix and the "building too many
15434 circuits" fix. It also further improves security against potential
15435 adversaries who find breaking 1024-bit crypto doable, and launches
15436 pluggable transports on demand (which gets us closer to integrating
15437 pluggable transport support by default -- not to be confused with Tor
15438 bundles enabling pluggable transports and bridges by default).
15440 o Major features (client security):
15441 - When we choose a path for a 3-hop circuit, make sure it contains
15442 at least one relay that supports the NTor circuit extension
15443 handshake. Otherwise, there is a chance that we're building
15444 a circuit that's worth attacking by an adversary who finds
15445 breaking 1024-bit crypto doable, and that chance changes the game
15446 theory. Implements ticket 9777.
15447 - Clients now look at the "usecreatefast" consensus parameter to
15448 decide whether to use CREATE_FAST or CREATE cells for the first hop
15449 of their circuit. This approach can improve security on connections
15450 where Tor's circuit handshake is stronger than the available TLS
15451 connection security levels, but the tradeoff is more computational
15452 load on guard relays. Implements proposal 221. Resolves ticket 9386.
15454 o Major features (bridges):
15455 - Don't launch pluggable transport proxies if we don't have any
15456 bridges configured that would use them. Now we can list many
15457 pluggable transports, and Tor will dynamically start one when it
15458 hears a bridge address that needs it. Resolves ticket 5018.
15459 - The bridge directory authority now assigns status flags (Stable,
15460 Guard, etc) to bridges based on thresholds calculated over all
15461 Running bridges. Now bridgedb can finally make use of its features
15462 to e.g. include at least one Stable bridge in its answers. Fixes
15465 o Major features (other):
15466 - Extend ORCONN controller event to include an "ID" parameter,
15467 and add four new controller event types CONN_BW, CIRC_BW,
15468 CELL_STATS, and TB_EMPTY that show connection and circuit usage.
15469 The new events are emitted in private Tor networks only, with the
15470 goal of being able to better track performance and load during
15471 full-network simulations. Implements proposal 218 and ticket 7359.
15472 - On some platforms (currently: recent OSX versions, glibc-based
15473 platforms that support the ELF format, and a few other
15474 Unix-like operating systems), Tor can now dump stack traces
15475 when a crash occurs or an assertion fails. By default, traces
15476 are dumped to stderr (if possible) and to any logs that are
15477 reporting errors. Implements ticket 9299.
15480 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
15481 not entirely remove it from the connection lists. Fixes bug 9602;
15482 bugfix on 0.2.4.4-alpha.
15483 - Do not treat streams that fail with reason
15484 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
15485 since it could also indicate an ENETUNREACH connection error. Fixes
15486 part of bug 10777; bugfix on 0.2.4.8-alpha.
15488 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
15489 - Do not allow OpenSSL engines to replace the PRNG, even when
15490 HardwareAccel is set. The only default builtin PRNG engine uses
15491 the Intel RDRAND instruction to replace the entire PRNG, and
15492 ignores all attempts to seed it with more entropy. That's
15493 cryptographically stupid: the right response to a new alleged
15494 entropy source is never to discard all previously used entropy
15495 sources. Fixes bug 10402; works around behavior introduced in
15496 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
15498 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
15499 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
15500 - Avoid launching spurious extra circuits when a stream is pending.
15501 This fixes a bug where any circuit that _wasn't_ unusable for new
15502 streams would be treated as if it were, causing extra circuits to
15503 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
15505 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
15506 - No longer stop reading or writing on cpuworker connections when
15507 our rate limiting buckets go empty. Now we should handle circuit
15508 handshake requests more promptly. Resolves bug 9731.
15509 - Stop trying to bootstrap all our directory information from
15510 only our first guard. Discovered while fixing bug 9946; bugfix
15513 o Minor features (bridges, pluggable transports):
15514 - Add threshold cutoffs to the networkstatus document created by
15515 the Bridge Authority. Fixes bug 1117.
15516 - On Windows, spawn background processes using the CREATE_NO_WINDOW
15517 flag. Now Tor Browser Bundle 3.5 with pluggable transports enabled
15518 doesn't pop up a blank console window. (In Tor Browser Bundle 2.x,
15519 Vidalia set this option for us.) Implements ticket 10297.
15521 o Minor features (security):
15522 - Always clear OpenSSL bignums before freeing them -- even bignums
15523 that don't contain secrets. Resolves ticket 10793. Patch by
15526 o Minor features (config options and command line):
15527 - Add an --allow-missing-torrc commandline option that tells Tor to
15528 run even if the configuration file specified by -f is not available.
15529 Implements ticket 10060.
15530 - Add support for the TPROXY transparent proxying facility on Linux.
15531 See documentation for the new TransProxyType option for more
15532 details. Implementation by "thomo". Closes ticket 10582.
15534 o Minor features (controller):
15535 - Add a new "HS_DESC" controller event that reports activities
15536 related to hidden service descriptors. Resolves ticket 8510.
15537 - New "DROPGUARDS" controller command to forget all current entry
15538 guards. Not recommended for ordinary use, since replacing guards
15539 too frequently makes several attacks easier. Resolves ticket 9934;
15542 o Minor features (build):
15543 - Assume that a user using ./configure --host wants to cross-compile,
15544 and give an error if we cannot find a properly named
15545 tool-chain. Add a --disable-tool-name-check option to proceed
15546 nevertheless. Addresses ticket 9869. Patch by Benedikt Gollatz.
15547 - If we run ./configure and the compiler recognizes -fstack-protector
15548 but the linker rejects it, warn the user about a potentially missing
15549 libssp package. Addresses ticket 9948. Patch from Benedikt Gollatz.
15551 o Minor features (testing):
15552 - If Python is installed, "make check" now runs extra tests beyond
15553 the unit test scripts.
15554 - When bootstrapping a test network, sometimes very few relays get
15555 the Guard flag. Now a new option "TestingDirAuthVoteGuard" can
15556 specify a set of relays which should be voted Guard regardless of
15557 their uptime or bandwidth. Addresses ticket 9206.
15559 o Minor features (log messages):
15560 - When ServerTransportPlugin is set on a bridge, Tor can write more
15561 useful statistics about bridge use in its extrainfo descriptors,
15562 but only if the Extended ORPort ("ExtORPort") is set too. Add a
15563 log message to inform the user in this case. Resolves ticket 9651.
15564 - When receiving a new controller connection, log the origin address.
15565 Resolves ticket 9698; patch from "sigpipe".
15566 - When logging OpenSSL engine status at startup, log the status of
15567 more engines. Fixes ticket 10043; patch from Joshua Datko.
15568 - Turn "circuit handshake stats since last time" log messages into a
15569 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
15571 o Minor features (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
15572 - Improve the circuit queue out-of-memory handler. Previously, when
15573 we ran low on memory, we'd close whichever circuits had the most
15574 queued cells. Now, we close those that have the *oldest* queued
15575 cells, on the theory that those are most responsible for us
15576 running low on memory. Based on analysis from a forthcoming paper
15577 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
15578 - Generate bootstrapping status update events correctly when fetching
15579 microdescriptors. Fixes bug 9927.
15580 - Update to the October 2 2013 Maxmind GeoLite Country database.
15582 o Minor bugfixes (clients):
15583 - When closing a channel that has already been open, do not close
15584 pending circuits that were waiting to connect to the same relay.
15585 Fixes bug 9880; bugfix on 0.2.5.1-alpha. Thanks to skruffy for
15588 o Minor bugfixes (relays):
15589 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
15590 exit node as a NOROUTE error, not an INTERNAL error, since they
15591 can apparently happen when trying to connect to the wrong sort
15592 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
15594 o Minor bugfixes (bridges):
15595 - Fix a bug where the first connection works to a bridge that uses a
15596 pluggable transport with client-side parameters, but we don't send
15597 the client-side parameters on subsequent connections. (We don't
15598 use any pluggable transports with client-side parameters yet,
15599 but ScrambleSuit will soon become the first one.) Fixes bug 9162;
15600 bugfix on 0.2.0.3-alpha. Based on a patch from "rl1987".
15602 o Minor bugfixes (node selection):
15603 - If ExcludeNodes is set, consider non-excluded hidden service
15604 directory servers before excluded ones. Do not consider excluded
15605 hidden service directory servers at all if StrictNodes is
15606 set. (Previously, we would sometimes decide to connect to those
15607 servers, and then realize before we initiated a connection that
15608 we had excluded them.) Fixes bug 10722; bugfix on 0.2.0.10-alpha.
15609 Reported by "mr-4".
15610 - If we set the ExitNodes option but it doesn't include any nodes
15611 that have the Exit flag, we would choose not to bootstrap. Now we
15612 bootstrap so long as ExitNodes includes nodes which can exit to
15613 some port. Fixes bug 10543; bugfix on 0.2.4.10-alpha.
15615 o Minor bugfixes (controller and command-line):
15616 - If changing a config option via "setconf" fails in a recoverable
15617 way, we used to nonetheless write our new control ports to the
15618 file described by the "ControlPortWriteToFile" option. Now we only
15619 write out that file if we successfully switch to the new config
15620 option. Fixes bug 5605; bugfix on 0.2.2.26-beta. Patch from "Ryman".
15621 - When a command-line option such as --version or --help that
15622 ordinarily implies --hush appears on the command line along with
15623 --quiet, then actually obey --quiet. Previously, we obeyed --quiet
15624 only if it appeared later on the command line. Fixes bug 9578;
15625 bugfix on 0.2.5.1-alpha.
15627 o Minor bugfixes (code correctness):
15628 - Previously we used two temporary files when writing descriptors to
15629 disk; now we only use one. Fixes bug 1376.
15630 - Remove an erroneous (but impossible and thus harmless) pointer
15631 comparison that would have allowed compilers to skip a bounds
15632 check in channeltls.c. Fixes bugs 10313 and 9980; bugfix on
15633 0.2.0.10-alpha. Noticed by Jared L Wong and David Fifield.
15634 - Fix an always-true assertion in pluggable transports code so it
15635 actually checks what it was trying to check. Fixes bug 10046;
15636 bugfix on 0.2.3.9-alpha. Found by "dcb".
15638 o Minor bugfixes (protocol correctness):
15639 - When receiving a VERSIONS cell with an odd number of bytes, close
15640 the connection immediately since the cell is malformed. Fixes bug
15641 10365; bugfix on 0.2.0.10-alpha. Spotted by "bobnomnom"; fix by
15644 o Minor bugfixes (build):
15645 - Restore the ability to compile Tor with V2_HANDSHAKE_SERVER
15646 turned off (that is, without support for v2 link handshakes). Fixes
15647 bug 4677; bugfix on 0.2.3.2-alpha. Patch from "piet".
15648 - Fix compilation warnings and startup issues when running with
15649 "Sandbox 1" and libseccomp-2.1.0. Fixes bug 10563; bugfix on
15651 - Fix compilation on Solaris 9, which didn't like us having an
15652 identifier named "sun". Fixes bug 10565; bugfix in 0.2.5.1-alpha.
15654 o Minor bugfixes (testing):
15655 - Fix a segmentation fault in our benchmark code when running with
15656 Fedora's OpenSSL package, or any other OpenSSL that provides
15657 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
15659 o Minor bugfixes (log messages):
15660 - Fix a bug where clients using bridges would report themselves
15661 as 50% bootstrapped even without a live consensus document.
15662 Fixes bug 9922; bugfix on 0.2.1.1-alpha.
15663 - Suppress a warning where, if there's only one directory authority
15664 in the network, we would complain that votes and signatures cannot
15665 be uploaded to other directory authorities. Fixes bug 10842;
15666 bugfix on 0.2.2.26-beta.
15667 - Report bootstrapping progress correctly when we're downloading
15668 microdescriptors. We had updated our "do we have enough microdescs
15669 to begin building circuits?" logic most recently in 0.2.4.10-alpha
15670 (see bug 5956), but we left the bootstrap status event logic at
15671 "how far through getting 1/4 of them are we?" Fixes bug 9958;
15672 bugfix on 0.2.2.36, which is where they diverged (see bug 5343).
15674 o Minor bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
15675 - Avoid a crash bug when starting with a corrupted microdescriptor
15676 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
15677 - If we fail to dump a previously cached microdescriptor to disk, avoid
15678 freeing duplicate data later on. Fixes bug 10423; bugfix on
15679 0.2.4.13-alpha. Spotted by "bobnomnom".
15681 o Minor bugfixes on 0.2.4.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
15682 - Correctly log long IPv6 exit policies, instead of truncating them
15683 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
15684 - Our default TLS ecdhe groups were backwards: we meant to be using
15685 P224 for relays (for performance win) and P256 for bridges (since
15686 it is more common in the wild). Instead we had it backwards. After
15687 reconsideration, we decided that the default should be P256 on all
15688 hosts, since its security is probably better, and since P224 is
15689 reportedly used quite little in the wild. Found by "skruffy" on
15690 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
15691 - Free directory authority certificate download statuses on exit
15692 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
15694 o Minor bugfixes on 0.2.3.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
15695 - If the guard we choose first doesn't answer, we would try the
15696 second guard, but once we connected to the second guard we would
15697 abandon it and retry the first one, slowing down bootstrapping.
15698 The fix is to treat all our initially chosen guards as acceptable
15699 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
15700 - Fix an assertion failure that would occur when disabling the
15701 ORPort setting on a running Tor process while accounting was
15702 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
15703 - When examining the list of network interfaces to find our address,
15704 do not consider non-running or disabled network interfaces. Fixes
15705 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
15706 - Avoid an off-by-one error when checking buffer boundaries when
15707 formatting the exit status of a pluggable transport helper.
15708 This is probably not an exploitable bug, but better safe than
15709 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
15712 o Removed code and features:
15713 - Clients now reject any directory authority certificates lacking
15714 a dir-key-crosscert element. These have been included since
15715 0.2.1.9-alpha, so there's no real reason for them to be optional
15716 any longer. Completes proposal 157. Resolves ticket 10162.
15717 - Remove all code that existed to support the v2 directory system,
15718 since there are no longer any v2 directory authorities. Resolves
15720 - Remove the HSAuthoritativeDir and AlternateHSAuthority torrc
15721 options, which were used for designating authorities as "Hidden
15722 service authorities". There has been no use of hidden service
15723 authorities since 0.2.2.1-alpha, when we stopped uploading or
15724 downloading v0 hidden service descriptors. Fixes bug 10881; also
15725 part of a fix for bug 10841.
15727 o Code simplification and refactoring:
15728 - Remove some old fallback code designed to keep Tor clients working
15729 in a network with only two working relays. Elsewhere in the code we
15730 have long since stopped supporting such networks, so there wasn't
15731 much point in keeping it around. Addresses ticket 9926.
15732 - Reject 0-length EXTEND2 cells more explicitly. Fixes bug 10536;
15733 bugfix on 0.2.4.8-alpha. Reported by "cypherpunks".
15734 - Remove data structures which were introduced to implement the
15735 CellStatistics option: they are now redundant with the addition
15736 of a timestamp to the regular packed_cell_t data structure, which
15737 we did in 0.2.4.18-rc in order to resolve ticket 9093. Implements
15740 o Documentation (man page) fixes:
15741 - Update manpage to describe some of the files you can expect to
15742 find in Tor's DataDirectory. Addresses ticket 9839.
15743 - Document that all but one DirPort entry must have the NoAdvertise
15744 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
15746 o Documentation fixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
15747 - Clarify the usage and risks of setting the ContactInfo torrc line
15748 for your relay or bridge. Resolves ticket 9854.
15749 - Add anchors to the manpage so we can link to the html version of
15750 the documentation for specific options. Resolves ticket 9866.
15751 - Replace remaining references to DirServer in man page and
15752 log entries. Resolves ticket 10124.
15755 - Make the "tor-gencert" tool used by directory authority operators
15756 create 2048-bit signing keys by default (rather than 1024-bit, since
15757 1024-bit is uncomfortably small these days). Addresses ticket 10324.
15760 Changes in version 0.2.4.20 - 2013-12-22
15761 Tor 0.2.4.20 fixes potentially poor random number generation for users
15762 who 1) use OpenSSL 1.0.0 or later, 2) set "HardwareAccel 1" in their
15763 torrc file, 3) have "Sandy Bridge" or "Ivy Bridge" Intel processors,
15764 and 4) have no state file in their DataDirectory (as would happen on
15765 first start). Users who generated relay or hidden service identity
15766 keys in such a situation should discard them and generate new ones.
15768 This release also fixes a logic error that caused Tor clients to build
15769 many more preemptive circuits than they actually need.
15772 - Do not allow OpenSSL engines to replace the PRNG, even when
15773 HardwareAccel is set. The only default builtin PRNG engine uses
15774 the Intel RDRAND instruction to replace the entire PRNG, and
15775 ignores all attempts to seed it with more entropy. That's
15776 cryptographically stupid: the right response to a new alleged
15777 entropy source is never to discard all previously used entropy
15778 sources. Fixes bug 10402; works around behavior introduced in
15779 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
15781 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
15782 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
15783 - Avoid launching spurious extra circuits when a stream is pending.
15784 This fixes a bug where any circuit that _wasn't_ unusable for new
15785 streams would be treated as if it were, causing extra circuits to
15786 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
15789 - Avoid a crash bug when starting with a corrupted microdescriptor
15790 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
15791 - If we fail to dump a previously cached microdescriptor to disk, avoid
15792 freeing duplicate data later on. Fixes bug 10423; bugfix on
15793 0.2.4.13-alpha. Spotted by "bobnomnom".
15796 Changes in version 0.2.4.19 - 2013-12-11
15797 The Tor 0.2.4 release series is dedicated to the memory of Aaron Swartz
15798 (1986-2013). Aaron worked on diverse projects including helping to guide
15799 Creative Commons, playing a key role in stopping SOPA/PIPA, bringing
15800 transparency to the U.S government's PACER documents, and contributing
15801 design and development for Tor and Tor2Web. Aaron was one of the latest
15802 martyrs in our collective fight for civil liberties and human rights,
15803 and his death is all the more painful because he was one of us.
15805 Tor 0.2.4.19, the first stable release in the 0.2.4 branch, features
15806 a new circuit handshake and link encryption that use ECC to provide
15807 better security and efficiency; makes relays better manage circuit
15808 creation requests; uses "directory guards" to reduce client enumeration
15809 risks; makes bridges collect and report statistics about the pluggable
15810 transports they support; cleans up and improves our geoip database;
15811 gets much closer to IPv6 support for clients, bridges, and relays; makes
15812 directory authorities use measured bandwidths rather than advertised
15813 ones when computing flags and thresholds; disables client-side DNS
15814 caching to reduce tracking risks; and fixes a big bug in bridge
15815 reachability testing. This release introduces two new design
15816 abstractions in the code: a new "channel" abstraction between circuits
15817 and or_connections to allow for implementing alternate relay-to-relay
15818 transports, and a new "circuitmux" abstraction storing the queue of
15819 circuits for a channel. The release also includes many stability,
15820 security, and privacy fixes.
15823 Changes in version 0.2.4.18-rc - 2013-11-16
15824 Tor 0.2.4.18-rc is the fourth release candidate for the Tor 0.2.4.x
15825 series. It takes a variety of fixes from the 0.2.5.x branch to improve
15826 stability, performance, and better handling of edge cases.
15829 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
15830 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
15831 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
15832 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
15833 them to solve bug 6033.)
15836 - No longer stop reading or writing on cpuworker connections when
15837 our rate limiting buckets go empty. Now we should handle circuit
15838 handshake requests more promptly. Resolves bug 9731.
15839 - If we are unable to save a microdescriptor to the journal, do not
15840 drop it from memory and then reattempt downloading it. Fixes bug
15841 9645; bugfix on 0.2.2.6-alpha.
15842 - Stop trying to bootstrap all our directory information from
15843 only our first guard. Discovered while fixing bug 9946; bugfix
15845 - The new channel code sometimes lost track of in-progress circuits,
15846 causing long-running clients to stop building new circuits. The
15847 fix is to always call circuit_n_chan_done(chan, 0) from
15848 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
15850 o Minor bugfixes (on 0.2.4.x):
15851 - Correctly log long IPv6 exit policies, instead of truncating them
15852 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
15853 - Our default TLS ecdhe groups were backwards: we meant to be using
15854 P224 for relays (for performance win) and P256 for bridges (since
15855 it is more common in the wild). Instead we had it backwards. After
15856 reconsideration, we decided that the default should be P256 on all
15857 hosts, since its security is probably better, and since P224 is
15858 reportedly used quite little in the wild. Found by "skruffy" on
15859 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
15860 - Free directory authority certificate download statuses on exit
15861 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
15863 o Minor bugfixes (on 0.2.3.x and earlier):
15864 - If the guard we choose first doesn't answer, we would try the
15865 second guard, but once we connected to the second guard we would
15866 abandon it and retry the first one, slowing down bootstrapping.
15867 The fix is to treat all our initially chosen guards as acceptable
15868 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
15869 - Fix an assertion failure that would occur when disabling the
15870 ORPort setting on a running Tor process while accounting was
15871 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
15872 - When examining the list of network interfaces to find our address,
15873 do not consider non-running or disabled network interfaces. Fixes
15874 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
15875 - Avoid an off-by-one error when checking buffer boundaries when
15876 formatting the exit status of a pluggable transport helper.
15877 This is probably not an exploitable bug, but better safe than
15878 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
15881 o Minor features (protecting client timestamps):
15882 - Clients no longer send timestamps in their NETINFO cells. These were
15883 not used for anything, and they provided one small way for clients
15884 to be distinguished from each other as they moved from network to
15885 network or behind NAT. Implements part of proposal 222.
15886 - Clients now round timestamps in INTRODUCE cells down to the nearest
15887 10 minutes. If a new Support022HiddenServices option is set to 0, or
15888 if it's set to "auto" and the feature is disabled in the consensus,
15889 the timestamp is sent as 0 instead. Implements part of proposal 222.
15890 - Stop sending timestamps in AUTHENTICATE cells. This is not such
15891 a big deal from a security point of view, but it achieves no actual
15892 good purpose, and isn't needed. Implements part of proposal 222.
15893 - Reduce down accuracy of timestamps in hidden service descriptors.
15894 Implements part of proposal 222.
15896 o Minor features (other):
15897 - Improve the circuit queue out-of-memory handler. Previously, when
15898 we ran low on memory, we'd close whichever circuits had the most
15899 queued cells. Now, we close those that have the *oldest* queued
15900 cells, on the theory that those are most responsible for us
15901 running low on memory. Based on analysis from a forthcoming paper
15902 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
15903 - Generate bootstrapping status update events correctly when fetching
15904 microdescriptors. Fixes bug 9927.
15905 - Update to the October 2 2013 Maxmind GeoLite Country database.
15907 o Documentation fixes:
15908 - Clarify the usage and risks of setting the ContactInfo torrc line
15909 for your relay or bridge. Resolves ticket 9854.
15910 - Add anchors to the manpage so we can link to the html version of
15911 the documentation for specific options. Resolves ticket 9866.
15912 - Replace remaining references to DirServer in man page and
15913 log entries. Resolves ticket 10124.
15916 Changes in version 0.2.5.1-alpha - 2013-10-02
15917 Tor 0.2.5.1-alpha introduces experimental support for syscall sandboxing
15918 on Linux, allows bridges that offer pluggable transports to report usage
15919 statistics, fixes many issues to make testing easier, and provides
15920 a pile of minor features and bugfixes that have been waiting for a
15921 release of the new branch.
15923 This is the first alpha release in a new series, so expect there to
15924 be bugs. Users who would rather test out a more stable branch should
15925 stay with 0.2.4.x for now.
15927 o Major features (security):
15928 - Use the seccomp2 syscall filtering facility on Linux to limit
15929 which system calls Tor can invoke. This is an experimental,
15930 Linux-only feature to provide defense-in-depth against unknown
15931 attacks. To try turning it on, set "Sandbox 1" in your torrc
15932 file. Please be ready to report bugs. We hope to add support
15933 for better sandboxing in the future, including more fine-grained
15934 filters, better division of responsibility, and support for more
15935 platforms. This work has been done by Cristian-Matei Toader for
15936 Google Summer of Code.
15937 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
15938 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
15939 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
15940 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
15941 them to solve bug 6033.)
15943 o Major features (other):
15944 - Add support for passing arguments to managed pluggable transport
15945 proxies. Implements ticket 3594.
15946 - Bridges now track GeoIP information and the number of their users
15947 even when pluggable transports are in use, and report usage
15948 statistics in their extra-info descriptors. Resolves tickets 4773
15950 - Make testing Tor networks bootstrap better: lower directory fetch
15951 retry schedules and maximum interval without directory requests,
15952 and raise maximum download tries. Implements ticket 6752.
15953 - Add make target 'test-network' to run tests on a Chutney network.
15954 Implements ticket 8530.
15955 - The ntor handshake is now on-by-default, no matter what the
15956 directory authorities recommend. Implements ticket 8561.
15959 - Instead of writing destroy cells directly to outgoing connection
15960 buffers, queue them and intersperse them with other outgoing cells.
15961 This can prevent a set of resource starvation conditions where too
15962 many pending destroy cells prevent data cells from actually getting
15963 delivered. Reported by "oftc_must_be_destroyed". Fixes bug 7912;
15964 bugfix on 0.2.0.1-alpha.
15965 - If we are unable to save a microdescriptor to the journal, do not
15966 drop it from memory and then reattempt downloading it. Fixes bug
15967 9645; bugfix on 0.2.2.6-alpha.
15968 - The new channel code sometimes lost track of in-progress circuits,
15969 causing long-running clients to stop building new circuits. The
15970 fix is to always call circuit_n_chan_done(chan, 0) from
15971 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
15974 - Tor now builds each source file in two modes: a mode that avoids
15975 exposing identifiers needlessly, and another mode that exposes
15976 more identifiers for testing. This lets the compiler do better at
15977 optimizing the production code, while enabling us to take more
15978 radical measures to let the unit tests test things.
15979 - The production builds no longer include functions used only in
15980 the unit tests; all functions exposed from a module only for
15981 unit-testing are now static in production builds.
15982 - Add an --enable-coverage configuration option to make the unit
15983 tests (and a new src/or/tor-cov target) to build with gcov test
15987 - We now have rudimentary function mocking support that our unit
15988 tests can use to test functions in isolation. Function mocking
15989 lets the tests temporarily replace a function's dependencies with
15990 stub functions, so that the tests can check the function without
15991 invoking the other functions it calls.
15992 - Add more unit tests for the <circid,channel>->circuit map, and
15993 the destroy-cell-tracking code to fix bug 7912.
15994 - Unit tests for failing cases of the TAP onion handshake.
15995 - More unit tests for address-manipulation functions.
15997 o Minor features (protecting client timestamps):
15998 - Clients no longer send timestamps in their NETINFO cells. These were
15999 not used for anything, and they provided one small way for clients
16000 to be distinguished from each other as they moved from network to
16001 network or behind NAT. Implements part of proposal 222.
16002 - Clients now round timestamps in INTRODUCE cells down to the nearest
16003 10 minutes. If a new Support022HiddenServices option is set to 0, or
16004 if it's set to "auto" and the feature is disabled in the consensus,
16005 the timestamp is sent as 0 instead. Implements part of proposal 222.
16006 - Stop sending timestamps in AUTHENTICATE cells. This is not such
16007 a big deal from a security point of view, but it achieves no actual
16008 good purpose, and isn't needed. Implements part of proposal 222.
16009 - Reduce down accuracy of timestamps in hidden service descriptors.
16010 Implements part of proposal 222.
16012 o Minor features (config options):
16013 - Config (torrc) lines now handle fingerprints which are missing
16014 their initial '$'. Resolves ticket 4341; improvement over 0.0.9pre5.
16015 - Support a --dump-config option to print some or all of the
16016 configured options. Mainly useful for debugging the command-line
16017 option parsing code. Helps resolve ticket 4647.
16018 - Raise awareness of safer logging: notify user of potentially
16019 unsafe config options, like logging more verbosely than severity
16020 "notice" or setting SafeLogging to 0. Resolves ticket 5584.
16021 - Add a new configuration option TestingV3AuthVotingStartOffset
16022 that bootstraps a network faster by changing the timing for
16023 consensus votes. Addresses ticket 8532.
16024 - Add a new torrc option "ServerTransportOptions" that allows
16025 bridge operators to pass configuration parameters to their
16026 pluggable transports. Resolves ticket 8929.
16027 - The config (torrc) file now accepts bandwidth and space limits in
16028 bits as well as bytes. (Anywhere that you can say "2 Kilobytes",
16029 you can now say "16 kilobits", and so on.) Resolves ticket 9214.
16032 o Minor features (build):
16033 - Add support for `--library-versions` flag. Implements ticket 6384.
16034 - Return the "unexpected sendme" warnings to a warn severity, but make
16035 them rate limited, to help diagnose ticket 8093.
16036 - Detect a missing asciidoc, and warn the user about it, during
16037 configure rather than at build time. Fixes issue 6506. Patch from
16040 o Minor features (other):
16041 - Use the SOCK_NONBLOCK socket type, if supported, to open nonblocking
16042 sockets in a single system call. Implements ticket 5129.
16043 - Log current accounting state (bytes sent and received + remaining
16044 time for the current accounting period) in the relay's heartbeat
16045 message. Implements ticket 5526; patch from Peter Retzlaff.
16046 - Implement the TRANSPORT_LAUNCHED control port event that
16047 notifies controllers about new launched pluggable
16048 transports. Resolves ticket 5609.
16049 - If we're using the pure-C 32-bit curve25519_donna implementation
16050 of curve25519, build it with the -fomit-frame-pointer option to
16051 make it go faster on register-starved hosts. This improves our
16052 handshake performance by about 6% on i386 hosts without nacl.
16053 Closes ticket 8109.
16054 - Update to the September 4 2013 Maxmind GeoLite Country database.
16057 - Set the listen() backlog limit to the largest actually supported
16058 on the system, not to the value in a header file. Fixes bug 9716;
16059 bugfix on every released Tor.
16060 - No longer accept malformed http headers when parsing urls from
16061 headers. Now we reply with Bad Request ("400"). Fixes bug 2767;
16062 bugfix on 0.0.6pre1.
16063 - In munge_extrainfo_into_routerinfo(), check the return value of
16064 memchr(). This would have been a serious issue if we ever passed
16065 it a non-extrainfo. Fixes bug 8791; bugfix on 0.2.0.6-alpha. Patch
16067 - On the chance that somebody manages to build Tor on a
16068 platform where time_t is unsigned, correct the way that
16069 microdesc_add_to_cache() handles negative time arguments.
16070 Fixes bug 8042; bugfix on 0.2.3.1-alpha.
16071 - Reject relative control socket paths and emit a warning. Previously,
16072 single-component control socket paths would be rejected, but Tor
16073 would not log why it could not validate the config. Fixes bug 9258;
16074 bugfix on 0.2.3.16-alpha.
16076 o Minor bugfixes (command line):
16077 - Use a single command-line parser for parsing torrc options on the
16078 command line and for finding special command-line options to avoid
16079 inconsistent behavior for torrc option arguments that have the same
16080 names as command-line options. Fixes bugs 4647 and 9578; bugfix on
16082 - No longer allow 'tor --hash-password' with no arguments. Fixes bug
16083 9573; bugfix on 0.0.9pre5.
16085 o Minor fixes (build, auxiliary programs):
16086 - Stop preprocessing the "torify" script with autoconf, since
16087 it no longer refers to LOCALSTATEDIR. Fixes bug 5505; patch
16089 - The tor-fw-helper program now follows the standard convention and
16090 exits with status code "0" on success. Fixes bug 9030; bugfix on
16091 0.2.3.1-alpha. Patch by Arlo Breault.
16092 - Corrected ./configure advice for what openssl dev package you should
16093 install on Debian. Fixes bug 9207; bugfix on 0.2.0.1-alpha.
16095 o Minor code improvements:
16096 - Remove constants and tests for PKCS1 padding; it's insecure and
16097 shouldn't be used for anything new. Fixes bug 8792; patch
16099 - Remove instances of strcpy() from the unit tests. They weren't
16100 hurting anything, since they were only in the unit tests, but it's
16101 embarrassing to have strcpy() in the code at all, and some analysis
16102 tools don't like it. Fixes bug 8790; bugfix on 0.2.3.6-alpha and
16103 0.2.3.8-alpha. Patch from Arlo Breault.
16105 o Removed features:
16106 - Remove migration code from when we renamed the "cached-routers"
16107 file to "cached-descriptors" back in 0.2.0.8-alpha. This
16108 incidentally resolves ticket 6502 by cleaning up the related code
16109 a bit. Patch from Akshay Hebbar.
16111 o Code simplification and refactoring:
16112 - Extract the common duplicated code for creating a subdirectory
16113 of the data directory and writing to a file in it. Fixes ticket
16114 4282; patch from Peter Retzlaff.
16115 - Since OpenSSL 0.9.7, the i2d_*() functions support allocating output
16116 buffer. Avoid calling twice: i2d_RSAPublicKey(), i2d_DHparams(),
16117 i2d_X509(), and i2d_PublicKey(). Resolves ticket 5170.
16118 - Add a set of accessor functions for the circuit timeout data
16119 structure. Fixes ticket 6153; patch from "piet".
16120 - Clean up exit paths from connection_listener_new(). Closes ticket
16121 8789. Patch from Arlo Breault.
16122 - Since we rely on OpenSSL 0.9.8 now, we can use EVP_PKEY_cmp()
16123 and drop our own custom pkey_eq() implementation. Fixes bug 9043.
16124 - Use a doubly-linked list to implement the global circuit list.
16125 Resolves ticket 9108. Patch from Marek Majkowski.
16126 - Remove contrib/id_to_fp.c since it wasn't used anywhere.
16129 Changes in version 0.2.4.17-rc - 2013-09-05
16130 Tor 0.2.4.17-rc is the third release candidate for the Tor 0.2.4.x
16131 series. It adds an emergency step to help us tolerate the massive
16132 influx of users: 0.2.4 clients using the new (faster and safer) "NTor"
16133 circuit-level handshakes now effectively jump the queue compared to
16134 the 0.2.3 clients using "TAP" handshakes. This release also fixes a
16135 big bug hindering bridge reachability tests.
16138 - Relays now process the new "NTor" circuit-level handshake requests
16139 with higher priority than the old "TAP" circuit-level handshake
16140 requests. We still process some TAP requests to not totally starve
16141 0.2.3 clients when NTor becomes popular. A new consensus parameter
16142 "NumNTorsPerTAP" lets us tune the balance later if we need to.
16143 Implements ticket 9574.
16146 - If the circuit build timeout logic is disabled (via the consensus,
16147 or because we are an authority), then don't build testing circuits.
16148 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
16149 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
16150 previously they did not, which prevented them from receiving
16151 successful connections from relays for self-test or bandwidth
16152 testing. Also, when a relay is extending a circuit to a bridge,
16153 it needs to send a NETINFO cell, even when the bridge hasn't sent
16154 an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
16155 - If the time to download the next old-style networkstatus is in
16156 the future, do not decline to consider whether to download the
16157 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
16161 - Avoid double-closing the listener socket in our socketpair()
16162 replacement (used on Windows) in the case where the addresses on
16163 our opened sockets don't match what we expected. Fixes bug 9400;
16164 bugfix on 0.0.2pre7. Found by Coverity.
16166 o Minor fixes (config options):
16167 - Avoid overflows when the user sets MaxCircuitDirtiness to a
16168 ridiculously high value, by imposing a (ridiculously high) 30-day
16169 maximum on MaxCircuitDirtiness.
16170 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
16171 message is logged at notice, not at info.
16172 - Warn and fail if a server is configured not to advertise any
16173 ORPorts at all. (We need *something* to put in our descriptor,
16174 or we just won't work.)
16177 - Track how many "TAP" and "NTor" circuit handshake requests we get,
16178 and how many we complete, and log it every hour to help relay
16179 operators follow trends in network load. Addresses ticket 9658.
16180 - Update to the August 7 2013 Maxmind GeoLite Country database.
16183 Changes in version 0.2.4.16-rc - 2013-08-10
16184 Tor 0.2.4.16-rc is the second release candidate for the Tor 0.2.4.x
16185 series. It fixes several crash bugs in the 0.2.4 branch.
16188 - Fix a bug in the voting algorithm that could yield incorrect results
16189 when a non-naming authority declared too many flags. Fixes bug 9200;
16190 bugfix on 0.2.0.3-alpha.
16191 - Fix an uninitialized read that could in some cases lead to a remote
16192 crash while parsing INTRODUCE2 cells. Bugfix on 0.2.4.1-alpha.
16193 Anybody running a hidden service on the experimental 0.2.4.x
16194 branch should upgrade. (This is, so far as we know, unrelated to
16196 - Avoid an assertion failure when processing DNS replies without the
16197 answer types we expected. Fixes bug 9337; bugfix on 0.2.4.7-alpha.
16198 - Avoid a crash when using --hash-password. Fixes bug 9295; bugfix on
16199 0.2.4.15-rc. Found by stem integration tests.
16202 - Fix an invalid memory read that occurred when a pluggable
16203 transport proxy failed its configuration protocol.
16204 Fixes bug 9288; bugfix on 0.2.4.1-alpha.
16205 - When evaluating whether to use a connection that we haven't
16206 decided is canonical using a recent link protocol version,
16207 decide that it's canonical only if it used address _does_
16208 match the desired address. Fixes bug 9309; bugfix on
16209 0.2.4.4-alpha. Reported by skruffy.
16210 - Make the default behavior of NumDirectoryGuards be to track
16211 NumEntryGuards. Now a user who changes only NumEntryGuards will get
16212 the behavior she expects. Fixes bug 9354; bugfix on 0.2.4.8-alpha.
16213 - Fix a spurious compilation warning with some older versions of
16214 GCC on FreeBSD. Fixes bug 9254; bugfix on 0.2.4.14-alpha.
16217 - Update to the July 3 2013 Maxmind GeoLite Country database.
16220 Changes in version 0.2.4.15-rc - 2013-07-01
16221 Tor 0.2.4.15-rc is the first release candidate for the Tor 0.2.4.x
16222 series. It fixes a few smaller bugs, but generally appears stable.
16223 Please test it and let us know whether it is!
16226 - When receiving a new configuration file via the control port's
16227 LOADCONF command, do not treat the defaults file as absent.
16228 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
16231 - Issue a warning when running with the bufferevents backend enabled.
16232 It's still not stable, and people should know that they're likely
16233 to hit unexpected problems. Closes ticket 9147.
16236 Changes in version 0.2.4.14-alpha - 2013-06-18
16237 Tor 0.2.4.14-alpha fixes a pair of client guard enumeration problems
16238 present in 0.2.4.13-alpha.
16241 - When we have too much memory queued in circuits (according to a new
16242 MaxMemInCellQueues option), close the circuits consuming the most
16243 memory. This prevents us from running out of memory as a relay if
16244 circuits fill up faster than they can be drained. Fixes bug 9063;
16245 bugfix on the 54th commit of Tor. This bug is a further fix beyond
16246 bug 6252, whose fix was merged into 0.2.3.21-rc.
16248 This change also fixes an earlier approach taken in 0.2.4.13-alpha,
16249 where we tried to solve this issue simply by imposing an upper limit
16250 on the number of queued cells for a single circuit. That approach
16251 proved to be problematic, since there are ways to provoke clients to
16252 send a number of cells in excess of any such reasonable limit. Fixes
16253 bug 9072; bugfix on 0.2.4.13-alpha.
16255 - Limit hidden service descriptors to at most ten introduction
16256 points, to slow one kind of guard enumeration. Fixes bug 9002;
16257 bugfix on 0.1.1.11-alpha.
16260 Changes in version 0.2.4.13-alpha - 2013-06-14
16261 Tor 0.2.4.13-alpha fixes a variety of potential remote crash
16262 vulnerabilities, makes socks5 username/password circuit isolation
16263 actually actually work (this time for sure!), and cleans up a bunch
16264 of other issues in preparation for a release candidate.
16266 o Major bugfixes (robustness):
16267 - Close any circuit that has too many cells queued on it. Fixes
16268 bug 9063; bugfix on the 54th commit of Tor. This bug is a further
16269 fix beyond bug 6252, whose fix was merged into 0.2.3.21-rc.
16270 - Prevent the get_freelists() function from running off the end of
16271 the list of freelists if it somehow gets an unrecognized
16272 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
16274 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
16275 when an exit connection with optimistic data succeeds immediately
16276 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
16278 - Fix a directory authority crash bug when building a consensus
16279 using an older consensus as its basis. Fixes bug 8833. Bugfix
16283 - Avoid a memory leak where we would leak a consensus body when we
16284 find that a consensus which we couldn't previously verify due to
16285 missing certificates is now verifiable. Fixes bug 8719; bugfix
16287 - We used to always request authority certificates by identity digest,
16288 meaning we'd get the newest one even when we wanted one with a
16289 different signing key. Then we would complain about being given
16290 a certificate we already had, and never get the one we really
16291 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
16292 resource to request the one we want. Fixes bug 5595; bugfix on
16294 - Follow the socks5 protocol when offering username/password
16295 authentication. The fix for bug 8117 exposed this bug, and it
16296 turns out real-world applications like Pidgin do care. Bugfix on
16297 0.2.3.2-alpha; fixes bug 8879.
16298 - Prevent failures on Windows Vista and later when rebuilding the
16299 microdescriptor cache. Diagnosed by Robert Ransom. Fixes bug 8822;
16300 bugfix on 0.2.4.12-alpha.
16303 - Fix an impossible buffer overrun in the AES unit tests. Fixes
16304 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
16305 - If for some reason we fail to write a microdescriptor while
16306 rebuilding the cache, do not let the annotations from that
16307 microdescriptor linger in the cache file, and do not let the
16308 microdescriptor stay recorded as present in its old location.
16309 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
16310 - Fix a memory leak that would occur whenever a configuration
16311 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
16312 - Paste the description for PathBias parameters from the man
16313 page into or.h, so the code documents them too. Fixes bug 7982;
16314 bugfix on 0.2.3.17-beta and 0.2.4.8-alpha.
16315 - Relays now treat a changed IPv6 ORPort as sufficient reason to
16316 publish an updated descriptor. Fixes bug 6026; bugfix on
16318 - When launching a resolve request on behalf of an AF_UNIX control
16319 socket, omit the address field of the new entry connection, used in
16320 subsequent controller events, rather than letting tor_dup_addr()
16321 set it to "<unknown address type>". Fixes bug 8639; bugfix on
16324 o Minor bugfixes (log messages):
16325 - Fix a scaling issue in the path bias accounting code that
16326 resulted in "Bug:" log messages from either
16327 pathbias_scale_close_rates() or pathbias_count_build_success().
16328 This represents a bugfix on a previous bugfix: the original fix
16329 attempted in 0.2.4.10-alpha was incomplete. Fixes bug 8235; bugfix
16331 - Give a less useless error message when the user asks for an IPv4
16332 address on an IPv6-only port, or vice versa. Fixes bug 8846; bugfix
16336 - Downgrade "unexpected SENDME" warnings to protocol-warn for 0.2.4.x,
16337 to tolerate bug 8093 for now.
16338 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
16339 in directory authority votes to describe whether they have enough
16340 measured bandwidths to ignore advertised (relay descriptor)
16341 bandwidth claims. Resolves ticket 8711.
16342 - Update to the June 5 2013 Maxmind GeoLite Country database.
16344 o Removed documentation:
16345 - Remove some of the older contents of doc/ as obsolete; move others
16346 to torspec.git. Fixes bug 8965.
16348 o Code simplification and refactoring:
16349 - Avoid using character buffers when constructing most directory
16350 objects: this approach was unwieldy and error-prone. Instead,
16351 build smartlists of strings, and concatenate them when done.
16354 Changes in version 0.2.4.12-alpha - 2013-04-18
16355 Tor 0.2.4.12-alpha moves Tor forward on several fronts: it starts the
16356 process for lengthening the guard rotation period, makes directory
16357 authority opinions in the consensus a bit less gameable, makes socks5
16358 username/password circuit isolation actually work, and fixes a wide
16359 variety of other issues.
16362 - Raise the default time that a client keeps an entry guard from
16363 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
16364 2012 paper. (We would make it even longer, but we need better client
16365 load balancing first.) Also, make the guard lifetime controllable
16366 via a new GuardLifetime torrc option and a GuardLifetime consensus
16367 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
16368 - Directory authorities now prefer using measured bandwidths to
16369 advertised ones when computing flags and thresholds. Resolves
16371 - Directory authorities that have more than a threshold number
16372 of relays with measured bandwidths now treat relays with unmeasured
16373 bandwidths as having bandwidth 0. Resolves ticket 8435.
16375 o Major bugfixes (assert / resource use):
16376 - Avoid a bug where our response to TLS renegotiation under certain
16377 network conditions could lead to a busy-loop, with 100% CPU
16378 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
16379 - Avoid an assertion when we discover that we'd like to write a cell
16380 onto a closing connection: just discard the cell. Fixes another
16381 case of bug 7350; bugfix on 0.2.4.4-alpha.
16383 o Major bugfixes (client-side privacy):
16384 - When we mark a circuit as unusable for new circuits, have it
16385 continue to be unusable for new circuits even if MaxCircuitDirtiness
16386 is increased too much at the wrong time, or the system clock jumps
16387 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
16388 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
16389 which have resolved to internal addresses") is set, apply that
16390 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
16391 - When an exit relay rejects a stream with reason "exit policy", but
16392 we only know an exit policy summary (e.g. from the microdesc
16393 consensus) for it, do not mark the relay as useless for all exiting.
16394 Instead, mark just the circuit as unsuitable for that particular
16395 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
16396 - Allow applications to get proper stream isolation with
16397 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
16398 username/password authentication also offer "no authentication". Tor
16399 had previously preferred "no authentication", so the applications
16400 never actually sent Tor their auth details. Now Tor selects
16401 username/password authentication if it's offered. You can disable
16402 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
16403 bug 8117; bugfix on 0.2.3.3-alpha.
16405 o Major bugfixes (other):
16406 - When unable to find any working directory nodes to use as a
16407 directory guard, give up rather than adding the same non-working
16408 nodes to the directory guard list over and over. Fixes bug 8231;
16409 bugfix on 0.2.4.8-alpha.
16412 - Reject as invalid most directory objects containing a NUL.
16413 Belt-and-suspender fix for bug 8037.
16414 - In our testsuite, create temporary directories with a bit more
16415 entropy in their name to make name collisions less likely. Fixes
16417 - Add CACHED keyword to ADDRMAP events in the control protocol
16418 to indicate whether a DNS result will be cached or not. Resolves
16420 - Update to the April 3 2013 Maxmind GeoLite Country database.
16422 o Minor features (build):
16423 - Detect and reject attempts to build Tor with threading support
16424 when OpenSSL has been compiled without threading support.
16426 - Clarify that when autoconf is checking for nacl, it is checking
16427 specifically for nacl with a fast curve25519 implementation.
16429 - Warn if building on a platform with an unsigned time_t: there
16430 are too many places where Tor currently assumes that time_t can
16431 hold negative values. We'd like to fix them all, but probably
16434 o Minor bugfixes (build):
16435 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
16436 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
16437 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
16438 - Add the old src/or/micro-revision.i filename to CLEANFILES.
16439 On the off chance that somebody has one, it will go away as soon
16440 as they run "make clean". Fix for bug 7143; bugfix on 0.2.4.1-alpha.
16441 - Build Tor correctly on 32-bit platforms where the compiler can build
16442 but not run code using the "uint128_t" construction. Fixes bug 8587;
16443 bugfix on 0.2.4.8-alpha.
16444 - Fix compilation warning with some versions of clang that would
16445 prefer the -Wswitch-enum compiler flag to warn about switch
16446 statements with missing enum values, even if those switch
16447 statements have a "default:" statement. Fixes bug 8598; bugfix
16450 o Minor bugfixes (protocol):
16451 - Fix the handling of a TRUNCATE cell when it arrives while the
16452 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
16453 - Fix a misframing issue when reading the version numbers in a
16454 VERSIONS cell. Previously we would recognize [00 01 00 02] as
16455 'version 1, version 2, and version 0x100', when it should have
16456 only included versions 1 and 2. Fixes bug 8059; bugfix on
16457 0.2.0.10-alpha. Reported pseudonymously.
16458 - Make the format and order of STREAM events for DNS lookups
16459 consistent among the various ways to launch DNS lookups. Fixes
16460 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy".
16461 - Correct our check for which versions of Tor support the EXTEND2
16462 cell. We had been willing to send it to Tor 0.2.4.7-alpha and
16463 later, when support was really added in version 0.2.4.8-alpha.
16464 Fixes bug 8464; bugfix on 0.2.4.8-alpha.
16466 o Minor bugfixes (other):
16467 - Correctly store microdescriptors and extrainfo descriptors with
16468 an internal NUL byte. Fixes bug 8037; bugfix on 0.2.0.1-alpha.
16469 Bug reported by "cypherpunks".
16470 - Increase the width of the field used to remember a connection's
16471 link protocol version to two bytes. Harmless for now, since the
16472 only currently recognized versions are one byte long. Reported
16473 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
16474 - If the state file's path bias counts are invalid (presumably from a
16475 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
16476 additional checks and log messages to the scaling of Path Bias
16477 counts, in case there still are remaining issues with scaling.
16478 Should help resolve bug 8235.
16479 - Eliminate several instances where we use "Nickname=ID" to refer to
16480 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
16481 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
16482 on 0.2.3.21-rc, 0.2.4.5-alpha, 0.2.4.8-alpha, and 0.2.4.10-alpha.
16484 o Minor bugfixes (syscalls):
16485 - Always check the return values of functions fcntl() and
16486 setsockopt(). We don't believe these are ever actually failing in
16487 practice, but better safe than sorry. Also, checking these return
16488 values should please analysis tools like Coverity. Patch from
16489 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
16490 - Use direct writes rather than stdio when building microdescriptor
16491 caches, in an attempt to mitigate bug 8031, or at least make it
16494 o Minor bugfixes (config):
16495 - When rejecting a configuration because we were unable to parse a
16496 quoted string, log an actual error message. Fixes bug 7950; bugfix
16498 - Behave correctly when the user disables LearnCircuitBuildTimeout
16499 but doesn't tell us what they would like the timeout to be. Fixes
16500 bug 6304; bugfix on 0.2.2.14-alpha.
16501 - When autodetecting the number of CPUs, use the number of available
16502 CPUs in preference to the number of configured CPUs. Inform the
16503 user if this reduces the number of available CPUs. Fixes bug 8002;
16504 bugfix on 0.2.3.1-alpha.
16505 - Make it an error when you set EntryNodes but disable UseGuardNodes,
16506 since it will (surprisingly to some users) ignore EntryNodes. Fixes
16507 bug 8180; bugfix on 0.2.3.11-alpha.
16508 - Allow TestingTorNetworks to override the 4096-byte minimum for
16509 the Fast threshold. Otherwise they can't bootstrap until they've
16510 observed more traffic. Fixes bug 8508; bugfix on 0.2.4.10-alpha.
16511 - Fix some logic errors when the user manually overrides the
16512 PathsNeededToBuildCircuits option in torrc. Fixes bug 8599; bugfix
16515 o Minor bugfixes (log messages to help diagnose bugs):
16516 - If we fail to free a microdescriptor because of bug 7164, log
16517 the filename and line number from which we tried to free it.
16518 - Add another diagnostic to the heartbeat message: track and log
16519 overhead that TLS is adding to the data we write. If this is
16520 high, we are sending too little data to SSL_write at a time.
16521 Diagnostic for bug 7707.
16522 - Add more detail to a log message about relaxed timeouts, to help
16524 - Warn more aggressively when flushing microdescriptors to a
16525 microdescriptor cache fails, in an attempt to mitigate bug 8031,
16526 or at least make it more diagnosable.
16527 - Improve debugging output to help track down bug 8185 ("Bug:
16528 outgoing relay cell has n_chan==NULL. Dropping.")
16529 - Log the purpose of a path-bias testing circuit correctly.
16530 Improves a log message from bug 8477; bugfix on 0.2.4.8-alpha.
16532 o Minor bugfixes (0.2.4.x log messages that were too noisy):
16533 - Don't attempt to relax the timeout of already opened 1-hop circuits.
16534 They might never timeout. This should eliminate some/all cases of
16535 the relaxed timeout log message.
16536 - Use circuit creation time for network liveness evaluation. This
16537 should eliminate warning log messages about liveness caused
16538 by changes in timeout evaluation. Fixes bug 6572; bugfix on
16540 - Reduce a path bias length check from notice to info. The message
16541 is triggered when creating controller circuits. Fixes bug 8196;
16542 bugfix on 0.2.4.8-alpha.
16543 - Fix a path state issue that triggered a notice during relay startup.
16544 Fixes bug 8320; bugfix on 0.2.4.10-alpha.
16545 - Reduce occurrences of warns about circuit purpose in
16546 connection_ap_expire_building(). Fixes bug 8477; bugfix on
16549 o Minor bugfixes (pre-0.2.4.x log messages that were too noisy):
16550 - If we encounter a write failure on a SOCKS connection before we
16551 finish our SOCKS handshake, don't warn that we closed the
16552 connection before we could send a SOCKS reply. Fixes bug 8427;
16553 bugfix on 0.1.0.1-rc.
16554 - Correctly recognize that [::1] is a loopback address. Fixes
16555 bug 8377; bugfix on 0.2.1.3-alpha.
16556 - Fix a directory authority warn caused when we have a large amount
16557 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
16558 - Don't log inappropriate heartbeat messages when hibernating: a
16559 hibernating node is _expected_ to drop out of the consensus,
16560 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
16561 bugfix on 0.2.3.1-alpha.
16562 - Don't complain about bootstrapping problems while hibernating.
16563 These complaints reflect a general code problem, but not one
16564 with any problematic effects (no connections are actually
16565 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
16567 o Documentation fixes:
16568 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
16569 names match. Fixes bug 7768.
16570 - Make the torify manpage no longer refer to tsocks; torify hasn't
16571 supported tsocks since 0.2.3.14-alpha.
16572 - Make the tor manpage no longer reference tsocks.
16573 - Fix the GeoIPExcludeUnknown documentation to refer to
16574 ExcludeExitNodes rather than the currently nonexistent
16575 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
16578 - The tor-tsocks.conf is no longer distributed or installed. We
16579 recommend that tsocks users use torsocks instead. Resolves
16583 Changes in version 0.2.4.11-alpha - 2013-03-11
16584 Tor 0.2.4.11-alpha makes relay measurement by directory authorities
16585 more robust, makes hidden service authentication work again, and
16586 resolves a DPI fingerprint for Tor's SSL transport.
16588 o Major features (directory authorities):
16589 - Directory authorities now support a new consensus method (17)
16590 where they cap the published bandwidth of servers for which
16591 insufficient bandwidth measurements exist. Fixes part of bug 2286.
16592 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
16593 serve any v2 directory information. Now we can test disabling the
16594 old deprecated v2 directory format, and see whether doing so has
16595 any effect on network load. Begins to fix bug 6783.
16596 - Directory authorities now include inside each vote a statement of
16597 the performance thresholds they used when assigning flags.
16598 Implements ticket 8151.
16600 o Major bugfixes (directory authorities):
16601 - Stop marking every relay as having been down for one hour every
16602 time we restart a directory authority. These artificial downtimes
16603 were messing with our Stable and Guard flag calculations. Fixes
16604 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
16606 o Major bugfixes (hidden services):
16607 - Allow hidden service authentication to succeed again. When we
16608 refactored the hidden service introduction code back
16609 in 0.2.4.1-alpha, we didn't update the code that checks
16610 whether authentication information is present, causing all
16611 authentication checks to return "false". Fix for bug 8207; bugfix
16612 on 0.2.4.1-alpha. Found by Coverity; this is CID 718615.
16614 o Minor features (relays, bridges):
16615 - Make bridge relays check once a minute for whether their IP
16616 address has changed, rather than only every 15 minutes. Resolves
16617 bugs 1913 and 1992.
16618 - Refactor resolve_my_address() so it returns the method by which we
16619 decided our public IP address (explicitly configured, resolved from
16620 explicit hostname, guessed from interfaces, learned by gethostname).
16621 Now we can provide more helpful log messages when a relay guesses
16622 its IP address incorrectly (e.g. due to unexpected lines in
16623 /etc/hosts). Resolves ticket 2267.
16624 - Teach bridge-using clients to avoid 0.2.2 bridges when making
16625 microdescriptor-related dir requests, and only fall back to normal
16626 descriptors if none of their bridges can handle microdescriptors
16627 (as opposed to the fix in ticket 4013, which caused them to fall
16628 back to normal descriptors if *any* of their bridges preferred
16629 them). Resolves ticket 4994.
16630 - Randomize the lifetime of our SSL link certificate, so censors can't
16631 use the static value for filtering Tor flows. Resolves ticket 8443;
16632 related to ticket 4014 which was included in 0.2.2.33.
16633 - Support a new version of the link protocol that allows 4-byte circuit
16634 IDs. Previously, circuit IDs were limited to 2 bytes, which presented
16635 a possible resource exhaustion issue. Closes ticket 7351; implements
16638 o Minor features (portability):
16639 - Tweak the curve25519-donna*.c implementations to tolerate systems
16640 that lack stdint.h. Fixes bug 3894; bugfix on 0.2.4.8-alpha.
16641 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
16642 the signs of types during autoconf. This is better than our old
16643 approach, which didn't work when cross-compiling.
16644 - Detect the sign of enum values, rather than assuming that MSC is the
16645 only compiler where enum types are all signed. Fixes bug 7727;
16646 bugfix on 0.2.4.10-alpha.
16648 o Minor features (other):
16649 - Say "KBytes" rather than "KB" in the man page (for various values
16650 of K), to further reduce confusion about whether Tor counts in
16651 units of memory or fractions of units of memory. Resolves ticket 7054.
16652 - Clear the high bit on curve25519 public keys before passing them to
16653 our backend, in case we ever wind up using a backend that doesn't do
16654 so itself. If we used such a backend, and *didn't* clear the high bit,
16655 we could wind up in a situation where users with such backends would
16656 be distinguishable from users without. Fixes bug 8121; bugfix on
16658 - Update to the March 6 2013 Maxmind GeoLite Country database.
16660 o Minor bugfixes (clients):
16661 - When we receive a RELAY_END cell with the reason DONE, or with no
16662 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
16663 status as "connection refused". Previously we reported these cases
16664 as success but then immediately closed the connection. Fixes bug
16665 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
16666 - Downgrade an assertion in connection_ap_expire_beginning to an
16667 LD_BUG message. The fix for bug 8024 should prevent this message
16668 from displaying, but just in case, a warn that we can diagnose
16669 is better than more assert crashes. Fixes bug 8065; bugfix on
16671 - Lower path use bias thresholds to .80 for notice and .60 for warn.
16672 Also make the rate limiting flags for the path use bias log messages
16673 independent from the original path bias flags. Fixes bug 8161;
16674 bugfix on 0.2.4.10-alpha.
16676 o Minor bugfixes (relays):
16677 - Stop trying to resolve our hostname so often (e.g. every time we
16678 think about doing a directory fetch). Now we reuse the cached
16679 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
16680 and 2410 (bugfix on 0.1.2.2-alpha).
16681 - Stop sending a stray "(null)" in some cases for the server status
16682 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
16684 - When choosing which stream on a formerly stalled circuit to wake
16685 first, make better use of the platform's weak RNG. Previously,
16686 we had been using the % ("modulo") operator to try to generate a
16687 1/N chance of picking each stream, but this behaves badly with
16688 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
16690 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
16691 Irix's random() only return 15 bits; Solaris's random() returns more
16692 bits but its RAND_MAX says it only returns 15, and so on. Motivated
16693 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
16695 o Minor bugfixes (directory authorities):
16696 - Directory authorities now use less space when formatting identical
16697 microdescriptor lines in directory votes. Fixes bug 8158; bugfix
16700 o Minor bugfixes (memory leaks spotted by Coverity -- bug 7816):
16701 - Avoid leaking memory if we fail to compute a consensus signature
16702 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
16703 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
16705 - Fix a memory leak during safe-cookie controller authentication.
16706 Bugfix on 0.2.3.13-alpha.
16707 - Avoid memory leak of IPv6 policy content if we fail to format it into
16708 a router descriptor. Bugfix on 0.2.4.7-alpha.
16710 o Minor bugfixes (other code correctness issues):
16711 - Avoid a crash if we fail to generate an extrainfo descriptor.
16712 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
16713 this is CID 718634.
16714 - When detecting the largest possible file descriptor (in order to
16715 close all file descriptors when launching a new program), actually
16716 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
16717 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
16719 - Fix a copy-and-paste error when adding a missing A1 to a routerset
16720 because of GeoIPExcludeUnknown. Fix for Coverity CID 980650.
16721 Bugfix on 0.2.4.10-alpha.
16722 - Fix an impossible-to-trigger integer overflow when estimating how
16723 long our onionskin queue would take. (This overflow would require us
16724 to accept 4 million onionskins before processing 100 of them.) Fixes
16725 bug 8210; bugfix on 0.2.4.10-alpha.
16727 o Code simplification and refactoring:
16728 - Add a wrapper function for the common "log a message with a
16732 Changes in version 0.2.4.10-alpha - 2013-02-04
16733 Tor 0.2.4.10-alpha adds defenses at the directory authority level from
16734 certain attacks that flood the network with relays; changes the queue
16735 for circuit create requests from a sized-based limit to a time-based
16736 limit; resumes building with MSVC on Windows; and fixes a wide variety
16739 o Major bugfixes (directory authority):
16740 - When computing directory thresholds, ignore any rejected-as-sybil
16741 nodes during the computation so that they can't influence Fast,
16742 Guard, etc. (We should have done this for proposal 109.) Fixes
16744 - When marking a node as a likely sybil, reset its uptime metrics
16745 to zero, so that it cannot time towards getting marked as Guard,
16746 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
16750 - When a TLS write is partially successful but incomplete, remember
16751 that the flushed part has been flushed, and notice that bytes were
16752 actually written. Reported and fixed pseudonymously. Fixes bug
16753 7708; bugfix on Tor 0.1.0.5-rc.
16754 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
16755 ID: these could be used to create unexpected streams and circuits
16756 which would count as "present" to some parts of Tor but "absent"
16757 to others, leading to zombie circuits and streams or to a bandwidth
16758 denial-of-service. Fixes bug 7889; bugfix on every released version
16759 of Tor. Reported by "oftc_must_be_destroyed".
16760 - Rename all macros in our local copy of queue.h to begin with "TOR_".
16761 This change seems the only good way to permanently prevent conflicts
16762 with queue.h on various operating systems. Fixes bug 8107; bugfix
16765 o Major features (relay):
16766 - Instead of limiting the number of queued onionskins (aka circuit
16767 create requests) to a fixed, hard-to-configure number, we limit
16768 the size of the queue based on how many we expect to be able to
16769 process in a given amount of time. We estimate the time it will
16770 take to process an onionskin based on average processing time
16771 of previous onionskins. Closes ticket 7291. You'll never have to
16772 configure MaxOnionsPending again.
16774 o Major features (portability):
16775 - Resume building correctly with MSVC and Makefile.nmake. This patch
16776 resolves numerous bugs and fixes reported by ultramage, including
16777 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
16778 - Make the ntor and curve25519 code build correctly with MSVC.
16779 Fix on 0.2.4.8-alpha.
16782 - When directory authorities are computing thresholds for flags,
16783 never let the threshold for the Fast flag fall below 4096
16784 bytes. Also, do not consider nodes with extremely low bandwidths
16785 when deciding thresholds for various directory flags. This change
16786 should raise our threshold for Fast relays, possibly in turn
16787 improving overall network performance; see ticket 1854. Resolves
16789 - The Tor client now ignores sub-domain components of a .onion
16790 address. This change makes HTTP "virtual" hosting
16791 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
16792 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
16793 hosted on the same hidden service. Implements proposal 204.
16794 - We compute the overhead from passing onionskins back and forth to
16795 cpuworkers, and report it when dumping statistics in response to
16796 SIGUSR1. Supports ticket 7291.
16798 o Minor features (path selection):
16799 - When deciding whether we have enough descriptors to build circuits,
16800 instead of looking at raw relay counts, look at which fraction
16801 of (bandwidth-weighted) paths we're able to build. This approach
16802 keeps clients from building circuits if their paths are likely to
16803 stand out statistically. The default fraction of paths needed is
16804 taken from the consensus directory; you can override it with the
16805 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
16806 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
16807 and we have GeoIP information, also exclude all nodes with unknown
16808 countries "??" and "A1". This behavior is controlled by the
16809 new GeoIPExcludeUnknown option: you can make such nodes always
16810 excluded with "GeoIPExcludeUnknown 1", and disable the feature
16811 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
16812 gets you the default behavior. Implements feature 7706.
16813 - Path Use Bias: Perform separate accounting for successful circuit
16814 use. Keep separate statistics on stream attempt rates versus stream
16815 success rates for each guard. Provide configurable thresholds to
16816 determine when to emit log messages or disable use of guards that
16817 fail too many stream attempts. Resolves ticket 7802.
16819 o Minor features (log messages):
16820 - When learning a fingerprint for a bridge, log its corresponding
16821 transport type. Implements ticket 7896.
16822 - Improve the log message when "Bug/attack: unexpected sendme cell
16823 from client" occurs, to help us track bug 8093.
16826 - Remove a couple of extraneous semicolons that were upsetting the
16827 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
16828 bugfix on 0.2.2.1-alpha.
16829 - Remove a source of rounding error during path bias count scaling;
16830 don't count cannibalized circuits as used for path bias until we
16831 actually try to use them; and fix a circuit_package_relay_cell()
16832 warning message about n_chan==NULL. Fixes bug 7802.
16833 - Detect nacl when its headers are in a nacl/ subdirectory. Also,
16834 actually link against nacl when we're configured to use it. Fixes
16835 bug 7972; bugfix on 0.2.4.8-alpha.
16836 - Compile correctly with the --disable-curve25519 option. Fixes
16837 bug 8153; bugfix on 0.2.4.8-alpha.
16839 o Build improvements:
16840 - Do not report status verbosely from autogen.sh unless the -v flag
16841 is specified. Fixes issue 4664. Patch from Onizuka.
16842 - Replace all calls to snprintf() outside of src/ext with
16843 tor_snprintf(). Also remove the #define to replace snprintf with
16844 _snprintf on Windows; they have different semantics, and all of
16845 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
16846 - Try to detect if we are ever building on a platform where
16847 memset(...,0,...) does not set the value of a double to 0.0. Such
16848 platforms are permitted by the C standard, though in practice
16849 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
16850 currently support them, but it's better to detect them and fail
16851 than to perform erroneously.
16853 o Removed features:
16854 - Stop exporting estimates of v2 and v3 directory traffic shares
16855 in extrainfo documents. They were unneeded and sometimes inaccurate.
16856 Also stop exporting any v2 directory request statistics. Resolves
16858 - Drop support for detecting and warning about versions of Libevent
16859 before 1.3e. Nothing reasonable ships with them any longer;
16860 warning the user about them shouldn't be needed. Resolves ticket
16863 o Code simplifications and refactoring:
16864 - Rename "isin" functions to "contains", for grammar. Resolves
16866 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
16867 with the natural logarithm function from the system libm. Resolves
16871 Changes in version 0.2.4.9-alpha - 2013-01-15
16872 Tor 0.2.4.9-alpha provides a quick fix to make the new ntor handshake
16873 work more robustly.
16876 - Fix backward compatibility logic when receiving an embedded ntor
16877 handshake tunneled in a CREATE cell. This clears up the "Bug:
16878 couldn't format CREATED cell" warning. Fixes bug 7959; bugfix
16882 Changes in version 0.2.4.8-alpha - 2013-01-14
16883 Tor 0.2.4.8-alpha introduces directory guards to reduce user enumeration
16884 risks, adds a new stronger and faster circuit handshake, and offers
16885 stronger and faster link encryption when both sides support it.
16888 - Preliminary support for directory guards (proposal 207): when
16889 possible, clients now use their entry guards for non-anonymous
16890 directory requests. This can help prevent client enumeration. Note
16891 that this behavior only works when we have a usable consensus
16892 directory, and when options about what to download are more or less
16893 standard. In the future we should re-bootstrap from our guards,
16894 rather than re-bootstrapping from the preconfigured list of
16895 directory sources that ships with Tor. Resolves ticket 6526.
16896 - Tor relays and clients now support a better CREATE/EXTEND cell
16897 format, allowing the sender to specify multiple address, identity,
16898 and handshake types. Implements Robert Ransom's proposal 200;
16899 closes ticket 7199.
16901 o Major features (new circuit handshake):
16902 - Tor now supports a new circuit extension handshake designed by Ian
16903 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
16904 circuit extension handshake, later called "TAP", was a bit slow
16905 (especially on the relay side), had a fragile security proof, and
16906 used weaker keys than we'd now prefer. The new circuit handshake
16907 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
16908 function, making it significantly more secure than the older
16909 handshake, and significantly faster. Tor can use one of two built-in
16910 pure-C curve25519-donna implementations by Adam Langley, or it
16911 can link against the "nacl" library for a tuned version if present.
16913 The built-in version is very fast for 64-bit systems when building
16914 with GCC. The built-in 32-bit version is still faster than the
16915 old TAP protocol, but using libnacl is better on most such hosts.
16917 Clients don't currently use this protocol by default, since
16918 comparatively few clients support it so far. To try it, set
16919 UseNTorHandshake to 1.
16921 Implements proposal 216; closes ticket 7202.
16923 o Major features (better link encryption):
16924 - Relays can now enable the ECDHE TLS ciphersuites when available
16925 and appropriate. These ciphersuites let us negotiate forward-secure
16926 TLS secret keys more safely and more efficiently than with our
16927 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
16928 public relays prefer the (faster) P224 group, and bridges prefer
16929 the (more common) P256 group; you can override this with the
16932 Enabling these ciphers was a little tricky, since for a long time,
16933 clients had been claiming to support them without actually doing
16934 so, in order to foil fingerprinting. But with the client-side
16935 implementation of proposal 198 in 0.2.3.17-beta, clients can now
16936 match the ciphers from recent Firefox versions *and* list the
16937 ciphers they actually mean, so relays can believe such clients
16938 when they advertise ECDHE support in their TLS ClientHello messages.
16940 This feature requires clients running 0.2.3.17-beta or later,
16941 and requires both sides to be running OpenSSL 1.0.0 or later
16942 with ECC support. OpenSSL 1.0.1, with the compile-time option
16943 "enable-ec_nistp_64_gcc_128", is highly recommended.
16945 Implements the relay side of proposal 198; closes ticket 7200.
16948 - Avoid crashing when, as a relay without IPv6-exit support, a
16949 client insists on getting an IPv6 address or nothing. Fixes bug
16950 7814; bugfix on 0.2.4.7-alpha.
16953 - Improve circuit build timeout handling for hidden services.
16954 In particular: adjust build timeouts more accurately depending
16955 upon the number of hop-RTTs that a particular circuit type
16956 undergoes. Additionally, launch intro circuits in parallel
16957 if they timeout, and take the first one to reply as valid.
16958 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
16959 separate error codes; or at least, don't break for that reason.
16960 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
16961 - Update to the January 2 2013 Maxmind GeoLite Country database.
16963 o Minor features (testing):
16964 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
16965 (P-256) Diffie-Hellman handshakes to src/or/bench.
16966 - Add benchmark functions to test onion handshake performance.
16968 o Minor features (path bias detection):
16969 - Alter the Path Bias log messages to be more descriptive in terms
16970 of reporting timeouts and other statistics.
16971 - Create three levels of Path Bias log messages, as opposed to just
16972 two. These are configurable via consensus as well as via the torrc
16973 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
16974 The default values are 0.70, 0.50, and 0.30 respectively.
16975 - Separate the log message levels from the decision to drop guards,
16976 which also is available via torrc option PathBiasDropGuards.
16977 PathBiasDropGuards still defaults to 0 (off).
16978 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
16979 in combination with PathBiasExtremeRate.
16980 - Increase the default values for PathBiasScaleThreshold and
16981 PathBiasCircThreshold from (200, 20) to (300, 150).
16982 - Add in circuit usage accounting to path bias. If we try to use a
16983 built circuit but fail for any reason, it counts as path bias.
16984 Certain classes of circuits where the adversary gets to pick your
16985 destination node are exempt from this accounting. Usage accounting
16986 can be specifically disabled via consensus parameter or torrc.
16987 - Convert all internal path bias state to double-precision floating
16988 point, to avoid roundoff error and other issues.
16989 - Only record path bias information for circuits that have completed
16990 *two* hops. Assuming end-to-end tagging is the attack vector, this
16991 makes us more resilient to ambient circuit failure without any
16992 detection capability loss.
16994 o Minor bugfixes (log messages):
16995 - Rate-limit the "No circuits are opened. Relaxed timeout for a
16996 circuit with channel state open..." message to once per hour to
16997 keep it from filling the notice logs. Mitigates bug 7799 but does
16998 not fix the underlying cause. Bugfix on 0.2.4.7-alpha.
16999 - Avoid spurious warnings when configuring multiple client ports of
17000 which only some are nonlocal. Previously, we had claimed that some
17001 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
17004 o Code simplifications and refactoring:
17005 - Get rid of a couple of harmless clang warnings, where we compared
17006 enums to ints. These warnings are newly introduced in clang 3.2.
17007 - Split the onion.c file into separate modules for the onion queue
17008 and the different handshakes it supports.
17009 - Remove the marshalling/unmarshalling code for sending requests to
17010 cpuworkers over a socket, and instead just send structs. The
17011 recipient will always be the same Tor binary as the sender, so
17012 any encoding is overkill.
17015 Changes in version 0.2.4.7-alpha - 2012-12-24
17016 Tor 0.2.4.7-alpha introduces a new approach to providing fallback
17017 directory mirrors for more robust bootstrapping; fixes more issues where
17018 clients with changing network conditions refuse to make any circuits;
17019 adds initial support for exiting to IPv6 addresses; resumes being able
17020 to update our GeoIP database, and includes the geoip6 file this time;
17021 turns off the client-side DNS cache by default due to privacy risks;
17022 and fixes a variety of other issues.
17024 o Major features (client resilience):
17025 - Add a new "FallbackDir" torrc option to use when we can't use
17026 a directory mirror from the consensus (either because we lack a
17027 consensus, or because they're all down). Currently, all authorities
17028 are fallbacks by default, and there are no other default fallbacks,
17029 but that will change. This option will allow us to give clients a
17030 longer list of servers to try to get a consensus from when first
17031 connecting to the Tor network, and thereby reduce load on the
17032 directory authorities. Implements proposal 206, "Preconfigured
17033 directory sources for bootstrapping". We also removed the old
17034 "FallbackNetworkstatus" option, since we never got it working well
17035 enough to use it. Closes bug 572.
17036 - If we have no circuits open, use a relaxed timeout (the
17037 95-percentile cutoff) until a circuit succeeds. This heuristic
17038 should allow Tor to succeed at building circuits even when the
17039 network connection drastically changes. Should help with bug 3443.
17041 o Major features (IPv6):
17042 - Relays can now exit to IPv6 addresses: make sure that you have IPv6
17043 connectivity, then set the IPv6Exit flag to 1. Also make sure your
17044 exit policy reads as you would like: the address * applies to all
17045 address families, whereas *4 is IPv4 address only, and *6 is IPv6
17046 addresses only. On the client side, you'll need to wait until the
17047 authorities have upgraded, wait for enough exits to support IPv6,
17048 apply the "IPv6Traffic" flag to a SocksPort, and use Socks5. Closes
17049 ticket 5547, implements proposal 117 as revised in proposal 208.
17051 We DO NOT recommend that clients with actual anonymity needs start
17052 using IPv6 over Tor yet, since not enough exits support it yet.
17054 o Major features (geoip database):
17055 - Maxmind began labelling Tor relays as being in country "A1",
17056 which breaks by-country node selection inside Tor. Now we use a
17057 script to replace "A1" ("Anonymous Proxy") entries in our geoip
17058 file with real country codes. This script fixes about 90% of "A1"
17059 entries automatically and uses manual country code assignments to
17060 fix the remaining 10%. See src/config/README.geoip for details.
17061 Fixes bug 6266. Also update to the December 5 2012 Maxmind GeoLite
17062 Country database, as modified above.
17064 o Major bugfixes (client-side DNS):
17065 - Turn off the client-side DNS cache by default. Updating and using
17066 the DNS cache is now configurable on a per-client-port
17067 level. SOCKSPort, DNSPort, etc lines may now contain
17068 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
17069 cache these types of DNS answers when we receive them from an
17070 exit node in response to an application request on this port, and
17071 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
17072 cached DNS answers of these types, we shouldn't use them. It's
17073 potentially risky to use cached DNS answers at the client, since
17074 doing so can indicate to one exit what answers we've gotten
17075 for DNS lookups in the past. With IPv6, this becomes especially
17076 problematic. Using cached DNS answers for requests on the same
17077 circuit would present less linkability risk, since all traffic
17078 on a circuit is already linkable, but it would also provide
17079 little performance benefit: the exit node caches DNS replies
17080 too. Implements a simplified version of Proposal 205. Implements
17083 o Major bugfixes (other):
17084 - Alter circuit build timeout measurement to start at the point
17085 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
17086 initialization). This should make our timeout measurements more
17087 uniform. Previously, we were sometimes including ORconn setup time
17088 in our circuit build time measurements. Should resolve bug 3443.
17089 - Fix an assertion that could trigger in hibernate_go_dormant() when
17090 closing an or_connection_t: call channel_mark_for_close() rather
17091 than connection_mark_for_close(). Fixes bug 7267. Bugfix on
17093 - Include the geoip6 IPv6 GeoIP database in the tarball. Fixes bug
17094 7655; bugfix on 0.2.4.6-alpha.
17097 - Add a new torrc option "ServerTransportListenAddr" to let bridge
17098 operators select the address where their pluggable transports will
17099 listen for connections. Resolves ticket 7013.
17100 - Allow an optional $ before the node identity digest in the
17101 controller command GETINFO ns/id/<identity>, for consistency with
17102 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
17103 - Log packaged cell fullness as part of the heartbeat message.
17104 Diagnosis to try to determine the extent of bug 7743.
17106 o Minor features (IPv6):
17107 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
17108 prefer to hand out virtual IPv6 addresses, since there are more of
17109 them and we can't run out. To override this behavior and make IPv4
17110 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
17111 or DNSPort you're using for resolving. Implements ticket 7571.
17112 - AutomapHostsOnResolve responses are now randomized, to avoid
17113 annoying situations where Tor is restarted and applications
17114 connect to the wrong addresses.
17115 - Never try more than 1000 times to pick a new virtual address when
17116 AutomapHostsOnResolve is set. That's good enough so long as we
17117 aren't close to handing out our entire virtual address space;
17118 if you're getting there, it's best to switch to IPv6 virtual
17122 - The ADDRMAP command can no longer generate an ill-formed error
17123 code on a failed MAPADDRESS. It now says "internal" rather than
17124 an English sentence fragment with spaces in the middle. Bugfix on
17125 Tor 0.2.0.19-alpha.
17126 - Fix log messages and comments to avoid saying "GMT" when we mean
17127 "UTC". Fixes bug 6113.
17128 - Compile on win64 using mingw64. Fixes bug 7260; patches from
17130 - Fix a crash when debugging unit tests on Windows: deallocate a
17131 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
17132 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
17135 - The DirServer option is now DirAuthority, for consistency with
17136 current naming patterns. You can still use the old DirServer form.
17138 o Code simplification and refactoring:
17139 - Move the client-side address-map/virtual-address/DNS-cache code
17140 out of connection_edge.c into a new addressmap.c module.
17141 - Remove unused code for parsing v1 directories and "running routers"
17142 documents. Fixes bug 6887.
17145 Changes in version 0.2.3.25 - 2012-11-19
17146 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
17147 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
17148 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
17149 programmer, and friend. Unstinting in his dedication to the cause of
17150 freedom, he inspired and helped many of us as we began our work on
17151 anonymity, and inspires us still. Please honor his memory by writing
17152 software to protect people's freedoms, and by helping others to do so.
17154 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
17155 significantly reduced directory overhead (via microdescriptors),
17156 enormous crypto performance improvements for fast relays on new
17157 enough hardware, a new v3 TLS handshake protocol that can better
17158 resist fingerprinting, support for protocol obfuscation plugins (aka
17159 pluggable transports), better scalability for hidden services, IPv6
17160 support for bridges, performance improvements like allowing clients
17161 to skip the first round-trip on the circuit ("optimistic data") and
17162 refilling token buckets more often, a new "stream isolation" design
17163 to isolate different applications on different circuits, and many
17164 stability, security, and privacy fixes.
17167 - Tor tries to wipe potentially sensitive data after using it, so
17168 that if some subsequent security failure exposes Tor's memory,
17169 the damage will be limited. But we had a bug where the compiler
17170 was eliminating these wipe operations when it decided that the
17171 memory was no longer visible to a (correctly running) program,
17172 hence defeating our attempt at defense in depth. We fix that
17173 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
17174 is unlikely to optimize away. Future versions of Tor may use
17175 a less ridiculously heavy approach for this. Fixes bug 7352.
17176 Reported in an article by Andrey Karpov.
17179 - Fix a harmless bug when opting against publishing a relay descriptor
17180 because DisableNetwork is set. Fixes bug 7464; bugfix on
17184 Changes in version 0.2.4.6-alpha - 2012-11-13
17185 Tor 0.2.4.6-alpha fixes an assert bug that has been plaguing relays,
17186 makes our defense-in-depth memory wiping more reliable, and begins to
17187 count IPv6 addresses in bridge statistics,
17190 - Fix an assertion failure that could occur when closing a connection
17191 with a spliced rendezvous circuit. Fix for bug 7212; bugfix on
17193 - Tor tries to wipe potentially sensitive data after using it, so
17194 that if some subsequent security failure exposes Tor's memory,
17195 the damage will be limited. But we had a bug where the compiler
17196 was eliminating these wipe operations when it decided that the
17197 memory was no longer visible to a (correctly running) program,
17198 hence defeating our attempt at defense in depth. We fix that
17199 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
17200 is unlikely to optimize away. Future versions of Tor may use
17201 a less ridiculously heavy approach for this. Fixes bug 7352.
17202 Reported in an article by Andrey Karpov.
17205 - Add GeoIP database for IPv6 addresses. The new config option
17207 - Bridge statistics now count bridge clients connecting over IPv6:
17208 bridge statistics files now list "bridge-ip-versions" and
17209 extra-info documents list "geoip6-db-digest". The control protocol
17210 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
17211 implementation by "shkoo", addressing ticket 5055.
17214 - Warn when we are binding low ports when hibernation is enabled;
17215 previously we had warned when we were _advertising_ low ports with
17216 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
17217 - Fix a harmless bug when opting against publishing a relay descriptor
17218 because DisableNetwork is set. Fixes bug 7464; bugfix on
17220 - Add warning message when a managed proxy dies during configuration.
17221 Fixes bug 7195; bugfix on 0.2.4.2-alpha.
17222 - Fix a linking error when building tor-fw-helper without miniupnp.
17223 Fixes bug 7235; bugfix on 0.2.4.2-alpha. Fix by Anthony G. Basile.
17224 - Check for closing an or_connection_t without going through correct
17225 channel functions; emit a warning and then call
17226 connection_or_close_for_error() so we don't assert as in bugs 7212
17228 - Compile correctly on compilers without C99 designated initializer
17229 support. Fixes bug 7286; bugfix on 0.2.4.4-alpha.
17230 - Avoid a possible assert that can occur when channel_send_destroy() is
17231 called on a channel in CHANNEL_STATE_CLOSING, CHANNEL_STATE_CLOSED,
17232 or CHANNEL_STATE_ERROR when the Tor process is resumed after being
17233 blocked for a long interval. Fixes bug 7350; bugfix on 0.2.4.4-alpha.
17234 - Fix a memory leak on failing cases of channel_tls_process_certs_cell.
17235 Fixes bug 7422; bugfix on 0.2.4.4-alpha.
17237 o Code simplification and refactoring:
17238 - Start using OpenBSD's implementation of queue.h, so that we don't
17239 need to hand-roll our own pointer and list structures whenever we
17240 need them. (We can't rely on a sys/queue.h, since some operating
17241 systems don't have them, and the ones that do have them don't all
17242 present the same extensions.)
17245 Changes in version 0.2.4.5-alpha - 2012-10-25
17246 Tor 0.2.4.5-alpha comes hard at the heels of 0.2.4.4-alpha, to fix
17247 two important security vulnerabilities that could lead to remotely
17248 triggerable relay crashes, fix a major bug that was preventing clients
17249 from choosing suitable exit nodes, and refactor some of our code.
17251 o Major bugfixes (security, also in 0.2.3.24-rc):
17252 - Fix a group of remotely triggerable assertion failures related to
17253 incorrect link protocol negotiation. Found, diagnosed, and fixed
17254 by "some guy from France". Fix for CVE-2012-2250; bugfix on
17256 - Fix a denial of service attack by which any directory authority
17257 could crash all the others, or by which a single v2 directory
17258 authority could crash everybody downloading v2 directory
17259 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
17261 o Major bugfixes (also in 0.2.3.24-rc):
17262 - When parsing exit policy summaries from microdescriptors, we had
17263 previously been ignoring the last character in each one, so that
17264 "accept 80,443,8080" would be treated by clients as indicating
17265 a node that allows access to ports 80, 443, and 808. That would
17266 lead to clients attempting connections that could never work,
17267 and ignoring exit nodes that would support their connections. Now
17268 clients parse these exit policy summaries correctly. Fixes bug 7192;
17269 bugfix on 0.2.3.1-alpha.
17271 o Minor bugfixes (also in 0.2.3.24-rc):
17272 - Clients now consider the ClientRejectInternalAddresses config option
17273 when using a microdescriptor consensus stanza to decide whether
17274 an exit relay would allow exiting to an internal address. Fixes
17275 bug 7190; bugfix on 0.2.3.1-alpha.
17278 - Only disable TLS session ticket support when running as a TLS
17279 server. Now clients will blend better with regular Firefox
17280 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
17282 o Code simplification and refactoring:
17283 - Start using OpenBSD's implementation of queue.h (originally by
17285 - Move the entry node code from circuitbuild.c to its own file.
17286 - Move the circuit build timeout tracking code from circuitbuild.c
17290 Changes in version 0.2.3.24-rc - 2012-10-25
17291 Tor 0.2.3.24-rc fixes two important security vulnerabilities that
17292 could lead to remotely triggerable relay crashes, and fixes
17293 a major bug that was preventing clients from choosing suitable exit
17296 o Major bugfixes (security):
17297 - Fix a group of remotely triggerable assertion failures related to
17298 incorrect link protocol negotiation. Found, diagnosed, and fixed
17299 by "some guy from France". Fix for CVE-2012-2250; bugfix on
17301 - Fix a denial of service attack by which any directory authority
17302 could crash all the others, or by which a single v2 directory
17303 authority could crash everybody downloading v2 directory
17304 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
17307 - When parsing exit policy summaries from microdescriptors, we had
17308 previously been ignoring the last character in each one, so that
17309 "accept 80,443,8080" would be treated by clients as indicating
17310 a node that allows access to ports 80, 443, and 808. That would
17311 lead to clients attempting connections that could never work,
17312 and ignoring exit nodes that would support their connections. Now
17313 clients parse these exit policy summaries correctly. Fixes bug 7192;
17314 bugfix on 0.2.3.1-alpha.
17317 - Clients now consider the ClientRejectInternalAddresses config option
17318 when using a microdescriptor consensus stanza to decide whether
17319 an exit relay would allow exiting to an internal address. Fixes
17320 bug 7190; bugfix on 0.2.3.1-alpha.
17323 Changes in version 0.2.4.4-alpha - 2012-10-20
17324 Tor 0.2.4.4-alpha adds a new v3 directory authority, fixes a privacy
17325 vulnerability introduced by a change in OpenSSL, fixes a remotely
17326 triggerable assert, and adds new channel_t and circuitmux_t abstractions
17327 that will make it easier to test new connection transport and cell
17328 scheduling algorithms.
17330 o New directory authorities (also in 0.2.3.23-rc):
17331 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
17332 authority. Closes ticket 5749.
17334 o Major bugfixes (security/privacy, also in 0.2.3.23-rc):
17335 - Disable TLS session tickets. OpenSSL's implementation was giving
17336 our TLS session keys the lifetime of our TLS context objects, when
17337 perfect forward secrecy would want us to discard anything that
17338 could decrypt a link connection as soon as the link connection
17339 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
17340 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
17341 - Discard extraneous renegotiation attempts once the V3 link
17342 protocol has been initiated. Failure to do so left us open to
17343 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
17344 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
17346 o Internal abstraction features:
17347 - Introduce new channel_t abstraction between circuits and
17348 or_connection_t to allow for implementing alternate OR-to-OR
17349 transports. A channel_t is an abstract object which can either be a
17350 cell-bearing channel, which is responsible for authenticating and
17351 handshaking with the remote OR and transmitting cells to and from
17352 it, or a listening channel, which spawns new cell-bearing channels
17353 at the request of remote ORs. Implements part of ticket 6465.
17354 - Also new is the channel_tls_t subclass of channel_t, adapting it
17355 to the existing or_connection_t code. The V2/V3 protocol handshaking
17356 code which formerly resided in command.c has been moved below the
17357 channel_t abstraction layer and may be found in channeltls.c now.
17358 Implements the rest of ticket 6465.
17359 - Introduce new circuitmux_t storing the queue of circuits for
17360 a channel; this encapsulates and abstracts the queue logic and
17361 circuit selection policy, and allows the latter to be overridden
17362 easily by switching out a policy object. The existing EWMA behavior
17363 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
17365 o Required libraries:
17366 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
17367 strongly recommended.
17370 - Warn users who run hidden services on a Tor client with
17371 UseEntryGuards disabled that their hidden services will be
17372 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
17373 attack which motivated Tor to support entry guards in the first
17374 place). Resolves ticket 6889.
17375 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
17376 dhill. Resolves ticket 6982.
17377 - Option OutboundBindAddress can be specified multiple times and
17378 accepts IPv6 addresses. Resolves ticket 6876.
17380 o Minor bugfixes (also in 0.2.3.23-rc):
17381 - Don't serve or accept v2 hidden service descriptors over a
17382 relay's DirPort. It's never correct to do so, and disabling it
17383 might make it more annoying to exploit any bugs that turn up in the
17384 descriptor-parsing code. Fixes bug 7149.
17385 - Fix two cases in src/or/transports.c where we were calling
17386 fmt_addr() twice in a parameter list. Bug found by David
17387 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
17388 - Fix memory leaks whenever we logged any message about the "path
17389 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
17390 - When relays refuse a "create" cell because their queue of pending
17391 create cells is too big (typically because their cpu can't keep up
17392 with the arrival rate), send back reason "resource limit" rather
17393 than reason "internal", so network measurement scripts can get a
17394 more accurate picture. Fixes bug 7037; bugfix on 0.1.1.11-alpha.
17397 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
17398 - Free some more still-in-use memory at exit, to make hunting for
17399 memory leaks easier. Resolves bug 7029.
17400 - When a Tor client gets a "truncated" relay cell, the first byte of
17401 its payload specifies why the circuit was truncated. We were
17402 ignoring this 'reason' byte when tearing down the circuit, resulting
17403 in the controller not being told why the circuit closed. Now we
17404 pass the reason from the truncated cell to the controller. Bugfix
17405 on 0.1.2.3-alpha; fixes bug 7039.
17406 - Downgrade "Failed to hand off onionskin" messages to "debug"
17407 severity, since they're typically redundant with the "Your computer
17408 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
17409 - Make clients running with IPv6 bridges connect over IPv6 again,
17410 even without setting new config options ClientUseIPv6 and
17411 ClientPreferIPv6ORPort. Fixes bug 6757; bugfix on 0.2.4.1-alpha.
17412 - Use square brackets around IPv6 addresses in numerous places
17413 that needed them, including log messages, HTTPS CONNECT proxy
17414 requests, TransportProxy statefile entries, and pluggable transport
17415 extra-info lines. Fixes bug 7011; patch by David Fifield.
17417 o Code refactoring and cleanup:
17418 - Source files taken from other packages now reside in src/ext;
17419 previously they were scattered around the rest of Tor.
17420 - Avoid use of reserved identifiers in our C code. The C standard
17421 doesn't like us declaring anything that starts with an
17422 underscore, so let's knock it off before we get in trouble. Fix
17423 for bug 1031; bugfix on the first Tor commit.
17426 Changes in version 0.2.3.23-rc - 2012-10-20
17427 Tor 0.2.3.23-rc adds a new v3 directory authority, fixes a privacy
17428 vulnerability introduced by a change in OpenSSL, and fixes a variety
17429 of smaller bugs in preparation for the release.
17431 o New directory authorities:
17432 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
17433 authority. Closes ticket 5749.
17435 o Major bugfixes (security/privacy):
17436 - Disable TLS session tickets. OpenSSL's implementation was giving
17437 our TLS session keys the lifetime of our TLS context objects, when
17438 perfect forward secrecy would want us to discard anything that
17439 could decrypt a link connection as soon as the link connection
17440 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
17441 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
17442 - Discard extraneous renegotiation attempts once the V3 link
17443 protocol has been initiated. Failure to do so left us open to
17444 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
17445 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
17448 - Fix a possible crash bug when checking for deactivated circuits
17449 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
17450 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
17452 o Minor bugfixes (on 0.2.3.x):
17453 - Fix two cases in src/or/transports.c where we were calling
17454 fmt_addr() twice in a parameter list. Bug found by David
17455 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
17456 - Convert an assert in the pathbias code to a log message. The assert
17457 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
17458 bugfix on 0.2.3.17-beta.
17459 - Fix memory leaks whenever we logged any message about the "path
17460 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
17462 o Minor bugfixes (on 0.2.2.x and earlier):
17463 - Don't serve or accept v2 hidden service descriptors over a relay's
17464 DirPort. It's never correct to do so, and disabling it might
17465 make it more annoying to exploit any bugs that turn up in the
17466 descriptor-parsing code. Fixes bug 7149.
17467 - When relays refuse a "create" cell because their queue of pending
17468 create cells is too big (typically because their cpu can't keep up
17469 with the arrival rate), send back reason "resource limit" rather
17470 than reason "internal", so network measurement scripts can get a
17471 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
17472 - Correct file sizes when reading binary files on Cygwin, to avoid
17473 a bug where Tor would fail to read its state file. Fixes bug 6844;
17474 bugfix on 0.1.2.7-alpha.
17475 - Avoid undefined behavior when parsing the list of supported
17476 rendezvous/introduction protocols in a hidden service descriptor.
17477 Previously, Tor would have confused (as-yet-unused) protocol version
17478 numbers greater than 32 with lower ones on many platforms. Fixes
17479 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
17481 o Documentation fixes:
17482 - Clarify that hidden services are TCP only. Fixes bug 6024.
17485 Changes in version 0.2.4.3-alpha - 2012-09-22
17486 Tor 0.2.4.3-alpha fixes another opportunity for a remotely triggerable
17487 assertion, resumes letting relays test reachability of their DirPort,
17488 and cleans up a bunch of smaller bugs.
17491 - Fix an assertion failure in tor_timegm() that could be triggered
17492 by a badly formatted directory object. Bug found by fuzzing with
17493 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
17496 - Fix a possible crash bug when checking for deactivated circuits
17497 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
17498 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
17499 - Allow routers to detect that their own DirPorts are running. When
17500 we removed support for versions_supports_begindir, we also
17501 accidentally removed the mechanism we used to self-test our
17502 DirPort. Diagnosed with help from kargig. Fixes bugs 6814 and 6815;
17503 bugfix on 0.2.4.2-alpha.
17505 o Security features:
17506 - Switch to a completely time-invariant approach for picking nodes
17507 weighted by bandwidth. Our old approach would run through the
17508 part of the loop after it had made its choice slightly slower
17509 than it ran through the part of the loop before it had made its
17510 choice. Addresses ticket 6538.
17511 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
17512 by tor2web clients allows hidden services to identify tor2web
17513 clients through their repeated selection of the same rendezvous
17514 and introduction point circuit endpoints (their guards). Resolves
17518 - Enable Tor to read configuration, state, and key information from
17519 a FIFO. Previously Tor would only read from files with a positive
17520 stat.st_size. Code from meejah; fixes bug 6044.
17523 - Correct file sizes when reading binary files on Cygwin, to avoid
17524 a bug where Tor would fail to read its state file. Fixes bug 6844;
17525 bugfix on 0.1.2.7-alpha.
17526 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
17527 bugfix on 0.2.0.3-alpha.
17528 - When complaining about a client port on a public address, log
17529 which address we're complaining about. Fixes bug 4020; bugfix on
17530 0.2.3.3-alpha. Patch by Tom Fitzhenry.
17531 - Convert an assert in the pathbias code to a log message. The assert
17532 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
17533 bugfix on 0.2.3.17-beta.
17534 - Our new buildsystem was overzealous about rebuilding manpages: it
17535 would rebuild them all whenever any one of them changed. Now our
17536 dependency checking should be correct. Fixes bug 6843; bugfix on
17538 - Don't do reachability testing over IPv6 unless AuthDirPublishIPv6
17539 is set. Fixes bug 6880. Bugfix on 0.2.4.1-alpha.
17540 - Correct log printout about which address family is preferred
17541 when connecting to a bridge with both an IPv4 and IPv6 OR port.
17542 Fixes bug 6884; bugfix on 0.2.4.1-alpha.
17544 o Minor bugfixes (code cleanliness):
17545 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
17546 with large values. This situation was untriggered, but nevertheless
17547 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
17548 - Reject consensus votes with more than 64 known-flags. We aren't even
17549 close to that limit yet, and our code doesn't handle it correctly.
17550 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
17551 - Avoid undefined behavior when parsing the list of supported
17552 rendezvous/introduction protocols in a hidden service descriptor.
17553 Previously, Tor would have confused (as-yet-unused) protocol version
17554 numbers greater than 32 with lower ones on many platforms. Fixes
17555 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
17556 - Fix handling of rendezvous client authorization types over 8.
17557 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
17558 - Fix building with older versions of GCC (2.95, for one) that don't
17559 like preprocessor directives inside macro arguments. Found by
17560 grarpamp. Fixes bug 6842; bugfix on 0.2.4.2-alpha.
17561 - Switch weighted node selection rule from using a list of doubles
17562 to using a list of int64_t. This change should make the process
17563 slightly easier to debug and maintain. Needed to finish ticket 6538.
17565 o Code simplification and refactoring:
17566 - Move the generic "config" code into a new file, and have "config.c"
17567 hold only torrc- and state-related code. Resolves ticket 6823.
17568 - Move the core of our "choose a weighted element at random" logic
17569 into its own function, and give it unit tests. Now the logic is
17570 testable, and a little less fragile too.
17571 - Removed the testing_since field of node_t, which hasn't been used
17572 for anything since 0.2.0.9-alpha.
17574 o Documentation fixes:
17575 - Clarify that hidden services are TCP only. Fixes bug 6024.
17576 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
17580 Changes in version 0.2.3.22-rc - 2012-09-11
17581 Tor 0.2.3.22-rc fixes another opportunity for a remotely triggerable
17585 - Fix an assertion failure in tor_timegm() that could be triggered
17586 by a badly formatted directory object. Bug found by fuzzing with
17587 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
17590 - Avoid segfault when starting up having run with an extremely old
17591 version of Tor and parsing its state file. Fixes bug 6801; bugfix
17595 Changes in version 0.2.2.39 - 2012-09-11
17596 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
17600 - Fix an assertion failure in tor_timegm() that could be triggered
17601 by a badly formatted directory object. Bug found by fuzzing with
17602 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
17603 - Do not crash when comparing an address with port value 0 to an
17604 address policy. This bug could have been used to cause a remote
17605 assertion failure by or against directory authorities, or to
17606 allow some applications to crash clients. Fixes bug 6690; bugfix
17610 Changes in version 0.2.4.2-alpha - 2012-09-10
17611 Tor 0.2.4.2-alpha enables port forwarding for pluggable transports,
17612 raises the default rate limiting even more, and makes the bootstrapping
17613 log messages less noisy.
17616 - Automatically forward the TCP ports of pluggable transport
17617 proxies using tor-fw-helper if PortForwarding is enabled. Implements
17621 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
17622 to 1GB/1GB. The previous defaults were intended to be "basically
17623 infinite", but it turns out they're now limiting our 100mbit+
17624 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
17625 last time we raised it).
17628 - Detect when we're running with a version of OpenSSL other than the
17629 one we compiled with. This has occasionally given people hard-to-
17631 - Log fewer lines at level "notice" about our OpenSSL and Libevent
17632 versions and capabilities when everything is going right. Resolves
17633 part of ticket 6736.
17634 - Directory authorities no long accept descriptors for any version of
17635 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
17636 These versions are insecure, unsupported, or both. Implements
17640 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
17641 to start with a triple-underscore so the controller won't touch it.
17642 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
17643 - Avoid segfault when starting up having run with an extremely old
17644 version of Tor and parsing its state file. Fixes bug 6801; bugfix
17646 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
17647 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
17648 - Don't follow the NULL pointer if microdescriptor generation fails.
17649 (This does not appear to be triggerable, but it's best to be safe.)
17650 Found by "f. tp.". Fixes bug 6797; bugfix on 0.2.4.1-alpha.
17651 - Fix mis-declared dependencies on src/common/crypto.c and
17652 src/or/tor_main.c that could break out-of-tree builds under some
17653 circumstances. Fixes bug 6778; bugfix on 0.2.4.1-alpha.
17654 - Avoid a warning when building common_sha1.i out of tree. Fixes bug
17655 6778; bugfix on 0.2.4.1-alpha.
17656 - Fix a harmless (in this case) build warning for implicitly
17657 converting a strlen() to an int. Bugfix on 0.2.4.1-alpha.
17659 o Removed features:
17660 - Now that all versions before 0.2.2.x are disallowed, we no longer
17661 need to work around their missing features. Thus we can remove a
17662 bunch of compatibility code.
17664 o Code refactoring:
17665 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
17666 TCP ports to forward. In the past it only accepted two ports:
17667 the ORPort and the DirPort.
17670 Changes in version 0.2.4.1-alpha - 2012-09-05
17671 Tor 0.2.4.1-alpha lets bridges publish their pluggable transports to
17672 bridgedb; lets relays use IPv6 addresses and directory authorities
17673 advertise them; and switches to a cleaner build interface.
17675 This is the first alpha release in a new series, so expect there to
17676 be bugs. Users who would rather test out a more stable branch should
17677 stay with 0.2.3.x for now.
17679 o Major features (bridges):
17680 - Bridges now report the pluggable transports they support to the
17681 bridge authority, so it can pass the supported transports on to
17682 bridgedb and/or eventually do reachability testing. Implements
17685 o Major features (IPv6):
17686 - Bridge authorities now accept IPv6 bridge addresses and include
17687 them in network status documents. Implements ticket 5534.
17688 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
17689 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
17690 to happen. Implements ticket 5535.
17691 - All kind of relays, not just bridges, can now advertise an IPv6
17692 OR port. Implements ticket 6362.
17693 - Directory authorities vote on IPv6 OR ports using the new consensus
17694 method 14. Implements ticket 6363.
17696 o Major features (build):
17697 - Switch to a nonrecursive Makefile structure. Now instead of each
17698 Makefile.am invoking other Makefile.am's, there is a master
17699 Makefile.am that includes the others. This change makes our build
17700 process slightly more maintainable, and improves parallelism for
17701 building with make -j. Original patch by Stewart Smith; various
17702 fixes by Jim Meyering.
17703 - Where available, we now use automake's "silent" make rules by
17704 default, so that warnings are easier to spot. You can get the old
17705 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
17707 o Minor features (code security and spec conformance):
17708 - Clear keys and key-derived material left on the stack in
17709 rendservice.c and rendclient.c. Check return value of
17710 crypto_pk_write_private_key_to_string() in rend_service_load_keys().
17711 These fixes should make us more forward-secure against cold-boot
17712 attacks and the like. Fixes bug 2385.
17713 - Reject EXTEND cells sent to nonexistent streams. According to the
17714 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
17715 we were only checking for stream IDs that were currently in use.
17716 Found while hunting for more instances of bug 6271. Bugfix on
17717 0.0.2pre8, which introduced incremental circuit construction.
17719 o Minor features (streamlining);
17720 - No longer include the "opt" prefix when generating routerinfos
17721 or v2 directories: it has been needless since Tor 0.1.2. Closes
17723 - Remove some now-needless code that tried to aggressively flush
17724 OR connections as data was added to them. Since 0.2.0.1-alpha, our
17725 cell queue logic has saved us from the failure mode that this code
17726 was supposed to prevent. Removing this code will limit the number
17727 of baroque control flow paths through Tor's network logic. Reported
17728 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
17730 o Minor features (controller):
17731 - Add a "GETINFO signal/names" control port command. Implements
17733 - Provide default values for all options via "GETINFO config/defaults".
17734 Implements ticket 4971.
17736 o Minor features (IPv6):
17737 - New config option "AuthDirHasIPv6Connectivity 1" that directory
17738 authorities should set if they have IPv6 connectivity and want to
17739 do reachability tests for IPv6 relays. Implements feature 5974.
17740 - A relay with an IPv6 OR port now sends that address in NETINFO
17741 cells (in addition to its other address). Implements ticket 6364.
17743 o Minor features (log messages):
17744 - Omit the first heartbeat log message, because it never has anything
17745 useful to say, and it clutters up the bootstrapping messages.
17746 Resolves ticket 6758.
17747 - Don't log about reloading the microdescriptor cache at startup. Our
17748 bootstrap warnings are supposed to tell the user when there's a
17749 problem, and our bootstrap notices say when there isn't. Resolves
17750 ticket 6759; bugfix on 0.2.2.6-alpha.
17751 - Don't log "I learned some more directory information" when we're
17752 reading cached directory information. Reserve it for when new
17753 directory information arrives in response to a fetch. Resolves
17755 - Prevent rounding error in path bias counts when scaling
17756 them down, and use the correct scale factor default. Also demote
17757 some path bias related log messages down a level and make others
17758 less scary sounding. Fixes bug 6647. Bugfix against 0.2.3.17-beta.
17759 - We no longer warn so much when generating manpages from their
17762 o Code simplifications and refactoring:
17763 - Enhance our internal sscanf replacement so that we can eliminate
17764 the last remaining uses of the system sscanf. (Though those uses
17765 of sscanf were safe, sscanf itself is generally error prone, so
17766 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
17768 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
17769 - Move last_reachable and testing_since from routerinfo_t to node_t.
17770 Implements ticket 5529.
17771 - Add replaycache_t structure, functions and unit tests, then refactor
17772 rend_service_introduce() to be more clear to read, improve, debug,
17773 and test. Resolves bug 6177.
17774 - Finally remove support for malloc_good_size and malloc_usable_size.
17775 We had hoped that these functions would let us eke a little more
17776 memory out of our malloc implementation. Unfortunately, the only
17777 implementations that provided these functions are also ones that
17778 are already efficient about not overallocation: they never got us
17779 more than 7 or so bytes per allocation. Removing them saves us a
17780 little code complexity and a nontrivial amount of build complexity.
17782 o New requirements:
17783 - Tor maintainers now require Automake version 1.9 or later to build
17784 Tor from the Git repository. (Automake is not required when building
17785 from a source distribution.)
17788 Changes in version 0.2.3.21-rc - 2012-09-05
17789 Tor 0.2.3.21-rc is the fourth release candidate for the Tor 0.2.3.x
17790 series. It fixes a trio of potential security bugs, fixes a bug where
17791 we were leaving some of the fast relays out of the microdescriptor
17792 consensus, resumes interpreting "ORPort 0" and "DirPort 0" correctly,
17793 and cleans up other smaller issues.
17795 o Major bugfixes (security):
17796 - Tear down the circuit if we get an unexpected SENDME cell. Clients
17797 could use this trick to make their circuits receive cells faster
17798 than our flow control would have allowed, or to gum up the network,
17799 or possibly to do targeted memory denial-of-service attacks on
17800 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
17801 from July 2002, before the release of Tor 0.0.0. We had committed
17802 this patch previously, but we had to revert it because of bug 6271.
17803 Now that 6271 is fixed, this patch appears to work.
17804 - Reject any attempt to extend to an internal address. Without
17805 this fix, a router could be used to probe addresses on an internal
17806 network to see whether they were accepting connections. Fixes bug
17807 6710; bugfix on 0.0.8pre1.
17808 - Do not crash when comparing an address with port value 0 to an
17809 address policy. This bug could have been used to cause a remote
17810 assertion failure by or against directory authorities, or to
17811 allow some applications to crash clients. Fixes bug 6690; bugfix
17815 - Remove the upper bound on microdescriptor length. We were hitting
17816 the limit for routers with complex exit policies or family
17817 declarations, causing clients to not use them. Fixes the first
17818 piece of bug 6404; fix on 0.2.2.6-alpha.
17819 - Detect "ORPort 0" as meaning, uniformly, that we're not running
17820 as a relay. Previously, some of our code would treat the presence
17821 of any ORPort line as meaning that we should act like a relay,
17822 even though our new listener code would correctly not open any
17823 ORPorts for ORPort 0. Similar bugs in other Port options are also
17824 fixed. Fixes the first half of bug 6507; bugfix on 0.2.3.3-alpha.
17827 - Avoid a pair of double-free and use-after-mark bugs that can
17828 occur with certain timings in canceled and re-received DNS
17829 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
17830 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
17831 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
17832 - Allow one-hop directory fetching circuits the full "circuit build
17833 timeout" period, rather than just half of it, before failing them
17834 and marking the relay down. This fix should help reduce cases where
17835 clients declare relays (or worse, bridges) unreachable because
17836 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
17837 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
17839 - Authorities no longer include any router in their microdescriptor
17840 consensuses for which they couldn't generate or agree on a
17841 microdescriptor. Fixes the second piece of bug 6404; fix on
17843 - Detect and reject attempts to specify both "FooPort" and
17844 "FooPort 0" in the same configuration domain. (It's still okay
17845 to have a FooPort in your configuration file, and use "FooPort 0"
17846 on the command line to disable it.) Fixes the second half of bug
17847 6507; bugfix on 0.2.3.3-alpha.
17848 - Make wildcarded addresses (that is, ones beginning with "*.") work
17849 when provided via the controller's MapAddress command. Previously,
17850 they were accepted, but we never actually noticed that they were
17851 wildcards. Fixes bug 6244; bugfix on 0.2.3.9-alpha.
17852 - Avoid crashing on a malformed state file where EntryGuardPathBias
17853 precedes EntryGuard. Fix for bug 6774; bugfix on 0.2.3.17-beta.
17854 - Add a (probably redundant) memory clear between iterations of
17855 the router status voting loop, to prevent future coding errors
17856 where data might leak between iterations of the loop. Resolves
17859 o Minor bugfixes (log messages):
17860 - Downgrade "set buildtimeout to low value" messages to "info"
17861 severity; they were never an actual problem, there was never
17862 anything reasonable to do about them, and they tended to spam logs
17863 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
17864 - Downgrade path-bias warning messages to "info". We'll try to get
17865 them working better in 0.2.4. Add internal circuit construction
17866 state to protect against the noisy warn message "Unexpectedly high
17867 circuit_successes". Also add some additional rate-limited notice
17868 messages to help determine the root cause of the warn. Fixes bug
17869 6475. Bugfix against 0.2.3.17-beta.
17870 - Move log message when unable to find a microdesc in a routerstatus
17871 entry to parse time. Previously we'd spam this warning every time
17872 we tried to figure out which microdescriptors to download. Fixes
17873 the third piece of bug 6404; fix on 0.2.3.18-rc.
17876 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
17877 change when the authority is deciding whether to accept a newly
17878 uploaded descriptor. Implements ticket 6423.
17879 - Add missing documentation for consensus and microdesc files.
17880 Resolves ticket 6732.
17883 Changes in version 0.2.2.38 - 2012-08-12
17884 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
17885 attack that could in theory leak path information.
17888 - Avoid an uninitialized memory read when reading a vote or consensus
17889 document that has an unrecognized flavor name. This read could
17890 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
17891 - Try to leak less information about what relays a client is
17892 choosing to a side-channel attacker. Previously, a Tor client would
17893 stop iterating through the list of available relays as soon as it
17894 had chosen one, thus finishing a little earlier when it picked
17895 a router earlier in the list. If an attacker can recover this
17896 timing information (nontrivial but not proven to be impossible),
17897 they could learn some coarse-grained information about which relays
17898 a client was picking (middle nodes in particular are likelier to
17899 be affected than exits). The timing attack might be mitigated by
17900 other factors (see bug 6537 for some discussion), but it's best
17901 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
17904 Changes in version 0.2.3.20-rc - 2012-08-05
17905 Tor 0.2.3.20-rc is the third release candidate for the Tor 0.2.3.x
17906 series. It fixes a pair of code security bugs and a potential anonymity
17907 issue, updates our RPM spec files, and cleans up other smaller issues.
17910 - Avoid read-from-freed-memory and double-free bugs that could occur
17911 when a DNS request fails while launching it. Fixes bug 6480;
17912 bugfix on 0.2.0.1-alpha.
17913 - Avoid an uninitialized memory read when reading a vote or consensus
17914 document that has an unrecognized flavor name. This read could
17915 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
17916 - Try to leak less information about what relays a client is
17917 choosing to a side-channel attacker. Previously, a Tor client would
17918 stop iterating through the list of available relays as soon as it
17919 had chosen one, thus finishing a little earlier when it picked
17920 a router earlier in the list. If an attacker can recover this
17921 timing information (nontrivial but not proven to be impossible),
17922 they could learn some coarse-grained information about which relays
17923 a client was picking (middle nodes in particular are likelier to
17924 be affected than exits). The timing attack might be mitigated by
17925 other factors (see bug 6537 for some discussion), but it's best
17926 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
17929 - Try to make the warning when giving an obsolete SOCKSListenAddress
17930 a little more useful.
17931 - Terminate active server managed proxies if Tor stops being a
17932 relay. Addresses parts of bug 6274; bugfix on 0.2.3.6-alpha.
17933 - Provide a better error message about possible OSX Asciidoc failure
17934 reasons. Fixes bug 6436.
17935 - Warn when Tor is configured to use accounting in a way that can
17936 link a hidden service to some other hidden service or public
17937 address. Resolves ticket 6490.
17940 - Check return value of fputs() when writing authority certificate
17941 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
17942 - Ignore ServerTransportPlugin lines when Tor is not configured as
17943 a relay. Fixes bug 6274; bugfix on 0.2.3.6-alpha.
17944 - When disabling guards for having too high a proportion of failed
17945 circuits, make sure to look at each guard. Fixes bug 6397; bugfix
17949 - Update our default RPM spec files to work with mock and rpmbuild
17950 on RHEL/Fedora. They have an updated set of dependencies and
17951 conflicts, a fix for an ancient typo when creating the "_tor"
17952 user, and better instructions. Thanks to Ondrej Mikle for the
17953 patch series. Fixes bug 6043.
17956 - Make it possible to set the TestingTorNetwork configuration
17957 option using AlternateDirAuthority and AlternateBridgeAuthority
17958 as an alternative to setting DirServer. Addresses ticket 6377.
17961 - Clarify the documentation for the Alternate*Authority options.
17963 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
17965 o Code simplification and refactoring:
17966 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
17967 10 lines. Also, don't nest them. Doing so in the past has
17968 led to hard-to-debug code. The new style is to use the
17969 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
17972 Changes in version 0.2.3.19-rc - 2012-07-06
17973 Tor 0.2.3.19-rc is the second release candidate for the Tor 0.2.3.x
17974 series. It fixes the compile on Windows, reverts to a GeoIP database
17975 that isn't as broken, and fixes a flow control bug that has been around
17976 since the beginning of Tor.
17979 - Fix a bug handling SENDME cells on nonexistent streams that could
17980 result in bizarre window values. Report and patch contributed
17981 pseudonymously. Fixes part of bug 6271. This bug was introduced
17982 before the first Tor release, in svn commit r152.
17983 - Revert to the May 1 2012 Maxmind GeoLite Country database. In the
17984 June 2012 database, Maxmind marked many Tor relays as country "A1",
17985 which will cause risky behavior for clients that set EntryNodes
17986 or ExitNodes. Addresses bug 6334; bugfix on 0.2.3.17-beta.
17987 - Instead of ENOBUFS on Windows, say WSAENOBUFS. Fixes compilation
17988 on Windows. Fixes bug 6296; bugfix on 0.2.3.18-rc.
17991 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
17992 bugfix on 0.2.1.10-alpha.
17995 Changes in version 0.2.3.18-rc - 2012-06-28
17996 Tor 0.2.3.18-rc is the first release candidate for the Tor 0.2.3.x
17997 series. It fixes a few smaller bugs, but generally appears stable.
17998 Please test it and let us know whether it is!
18001 - Allow wildcarded mapaddress targets to be specified on the
18002 controlport. Partially fixes bug 6244; bugfix on 0.2.3.9-alpha.
18003 - Make our linker option detection code more robust against linkers
18004 such as on FreeBSD 8, where a bad combination of options completes
18005 successfully but makes an unrunnable binary. Fixes bug 6173;
18006 bugfix on 0.2.3.17-beta.
18008 o Minor bugfixes (on 0.2.2.x and earlier):
18009 - Avoid a false positive in the util/threads unit test by increasing
18010 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
18011 - Replace "Sending publish request" log messages with "Launching
18012 upload", so that they no longer confusingly imply that we're
18013 sending something to a directory we might not even be connected
18014 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
18015 - Make sure to set *socket_error in all error cases in
18016 connection_connect(), so it can't produce a warning about
18017 errno being zero from errno_to_orconn_end_reason(). Bugfix on
18018 0.2.1.1-alpha; resolves ticket 6028.
18019 - Downgrade "Got a certificate, but we already have it" log messages
18020 from warning to info, except when we're a dirauth. Fixes bug 5238;
18021 bugfix on 0.2.1.7-alpha.
18022 - When checking for requested signatures on the latest consensus
18023 before serving it to a client, make sure to check the right
18024 consensus flavor. Bugfix on 0.2.2.6-alpha.
18025 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
18026 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
18028 o Minor bugfixes (on 0.2.3.x):
18029 - Make format_helper_exit_status() avoid unnecessary space padding
18030 and stop confusing log_from_pipe(). Fixes ticket 5557; bugfix
18032 - Downgrade a message about cleaning the microdescriptor cache to
18033 "info" from "notice". Fixes bug 6238; bugfix on 0.2.3.1-alpha.
18034 - Log a BUG message at severity INFO if we have a networkstatus with
18035 a missing entry for some microdescriptor. Continues on a patch
18037 - Improve the log message when a managed proxy fails to launch. Fixes
18038 bug 5099; bugfix on 0.2.3.6-alpha.
18039 - Don't do DNS lookups when parsing corrupted managed proxy protocol
18040 messages. Fixes bug 6226; bugfix on 0.2.3.6-alpha.
18041 - When formatting wildcarded address mappings for the controller,
18042 be sure to include "*." as appropriate. Partially fixes bug 6244;
18043 bugfix on 0.2.3.9-alpha.
18044 - Avoid a warning caused by using strcspn() from glibc with clang 3.0.
18045 Bugfix on 0.2.3.13-alpha.
18046 - Stop logging messages about running with circuit timeout learning
18047 enabled at severity LD_BUG. Fixes bug 6169; bugfix on 0.2.3.17-beta.
18048 - Disable a spurious warning about reading on a marked and flushing
18049 connection. We shouldn't be doing that, but apparently we
18050 sometimes do. Fixes bug 6203; bugfix on 0.2.3.17-beta.
18051 - Fix a bug that stopped AllowDotExit from working on addresses
18052 that had an entry in the DNS cache. Fixes bug 6211; bugfix on
18055 o Code simplification, refactoring, unit tests:
18056 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
18057 Libevent's notion of cached time when possible.
18058 - Remove duplicate code for invoking getrlimit() from control.c.
18059 - Add a unit test for the environment_variable_names_equal function.
18062 - Document the --defaults-torrc option, and the new (in 0.2.3)
18063 semantics for overriding, extending, and clearing lists of
18064 options. Closes bug 4748.
18067 Changes in version 0.2.3.17-beta - 2012-06-15
18068 Tor 0.2.3.17-beta enables compiler and linker hardening by default,
18069 gets our TLS handshake back on track for being able to blend in with
18070 Firefox, fixes a big bug in 0.2.3.16-alpha that broke Tor's interaction
18071 with Vidalia, and otherwise continues to get us closer to a release
18075 - Enable gcc and ld hardening by default. Resolves ticket 5210.
18076 - Update TLS cipher list to match Firefox 8 and later. Resolves
18078 - Implement the client side of proposal 198: remove support for
18079 clients falsely claiming to support standard ciphersuites that
18080 they can actually provide. As of modern OpenSSL versions, it's not
18081 necessary to fake any standard ciphersuite, and doing so prevents
18082 us from using better ciphersuites in the future, since servers
18083 can't know whether an advertised ciphersuite is really supported or
18084 not. Some hosts -- notably, ones with very old versions of OpenSSL
18085 or where OpenSSL has been built with ECC disabled -- will stand
18086 out because of this change; TBB users should not be affected.
18089 - Change the default value for DynamicDHGroups (introduced in
18090 0.2.3.9-alpha) to 0. This feature can make Tor relays less
18091 identifiable by their use of the mod_ssl DH group, but at
18092 the cost of some usability (#4721) and bridge tracing (#6087)
18093 regressions. Resolves ticket 5598.
18094 - Send a CRLF at the end of each STATUS_* control protocol event. This
18095 bug tickled a bug in Vidalia which would make it freeze. Fixes
18096 bug 6094; bugfix on 0.2.3.16-alpha.
18099 - Disable writing on marked-for-close connections when they are
18100 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
18101 bug 5263; bugfix on 0.0.2pre13, where we first added a special
18102 case for flushing marked connections.
18103 - Detect SSL handshake even when the initial attempt to write the
18104 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
18105 - Change the AllowDotExit rules so they should actually work.
18106 We now enforce AllowDotExit only immediately after receiving an
18107 address via SOCKS or DNSPort: other sources are free to provide
18108 .exit addresses after the resolution occurs. Fixes bug 3940;
18109 bugfix on 0.2.2.1-alpha.
18110 - Fix a (harmless) integer overflow in cell statistics reported by
18111 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
18112 - Make sure circuitbuild.c checks LearnCircuitBuildTimeout in all the
18113 right places and never depends on the consensus parameters or
18114 computes adaptive timeouts when it is disabled. Fixes bug 5049;
18115 bugfix on 0.2.2.14-alpha.
18116 - When building Tor on Windows with -DUNICODE (not default), ensure
18117 that error messages, filenames, and DNS server names are always
18118 NUL-terminated when we convert them to a single-byte encoding.
18119 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
18120 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
18121 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
18122 - Fix an edge case where TestingTorNetwork is set but the authorities
18123 and relays all have an uptime of zero, where the private Tor network
18124 could briefly lack support for hidden services. Fixes bug 3886;
18125 bugfix on 0.2.2.18-alpha.
18126 - Correct the manpage's descriptions for the default values of
18127 DirReqStatistics and ExtraInfoStatistics. Fixes bug 2865; bugfix
18129 - Fix the documentation for the --hush and --quiet command line
18130 options, which changed their behavior back in 0.2.3.3-alpha.
18131 - Fix compilation warning with clang 3.1. Fixes bug 6141; bugfix on
18135 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
18136 more information to it, so that we can track it down in case it
18137 returns again. Mitigates bug 5235.
18138 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
18139 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
18140 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
18141 - Warn the user when HTTPProxy, but no other proxy type, is
18142 configured. This can cause surprising behavior: it doesn't send
18143 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
18144 directory traffic only. Resolves ticket 4663.
18145 - Issue a notice if a guard completes less than 40% of your circuits.
18146 Threshold is configurable by torrc option PathBiasNoticeRate and
18147 consensus parameter pb_noticepct. There is additional, off-by-
18148 default code to disable guards which fail too many circuits.
18149 Addresses ticket 5458.
18150 - Update to the June 6 2012 Maxmind GeoLite Country database.
18152 o Code simplifications and refactoring:
18153 - Remove validate_pluggable_transports_config(): its warning
18154 message is now handled by connection_or_connect().
18157 Changes in version 0.2.2.37 - 2012-06-06
18158 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
18159 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
18163 - Work around a bug in OpenSSL that broke renegotiation with TLS
18164 1.1 and TLS 1.2. Without this workaround, all attempts to speak
18165 the v2 Tor connection protocol when both sides were using OpenSSL
18166 1.0.1 would fail. Resolves ticket 6033.
18167 - When waiting for a client to renegotiate, don't allow it to add
18168 any bytes to the input buffer. This fixes a potential DoS issue.
18169 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
18170 - Fix an edge case where if we fetch or publish a hidden service
18171 descriptor, we might build a 4-hop circuit and then use that circuit
18172 for exiting afterwards -- even if the new last hop doesn't obey our
18173 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
18176 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
18177 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
18180 - Tell GCC and Clang to check for any errors in format strings passed
18181 to the tor_v*(print|scan)f functions.
18184 Changes in version 0.2.3.16-alpha - 2012-06-05
18185 Tor 0.2.3.16-alpha introduces a workaround for a critical renegotiation
18186 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
18187 currently). It also fixes a variety of smaller bugs and other cleanups
18188 that get us closer to a release candidate.
18190 o Major bugfixes (general):
18191 - Work around a bug in OpenSSL that broke renegotiation with TLS
18192 1.1 and TLS 1.2. Without this workaround, all attempts to speak
18193 the v2 Tor connection protocol when both sides were using OpenSSL
18194 1.0.1 would fail. Resolves ticket 6033.
18195 - When waiting for a client to renegotiate, don't allow it to add
18196 any bytes to the input buffer. This fixes a potential DoS issue.
18197 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
18198 - Pass correct OR address to managed proxies (like obfsproxy),
18199 even when ORListenAddress is used. Fixes bug 4865; bugfix on
18201 - The advertised platform of a router now includes only its operating
18202 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not its
18203 service pack level (for Windows) or its CPU architecture (for Unix).
18204 We also no longer include the "git-XYZ" tag in the version. Resolves
18207 o Major bugfixes (clients):
18208 - If we are unable to find any exit that supports our predicted ports,
18209 stop calling them predicted, so that we don't loop and build
18210 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
18211 which introduced predicted ports.
18212 - Fix an edge case where if we fetch or publish a hidden service
18213 descriptor, we might build a 4-hop circuit and then use that circuit
18214 for exiting afterwards -- even if the new last hop doesn't obey our
18215 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
18216 - Check at each new consensus whether our entry guards were picked
18217 long enough ago that we should rotate them. Previously, we only
18218 did this check at startup, which could lead to us holding a guard
18219 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
18220 - When fetching a bridge descriptor from a bridge authority,
18221 always do so anonymously, whether we have been able to open
18222 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
18223 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
18224 but we'll need to wait for bug 6010 before it's actually usable.
18226 o Major bugfixes (directory authorities):
18227 - When computing weight parameters, behave more robustly in the
18228 presence of a bad bwweightscale value. Previously, the authorities
18229 would crash if they agreed on a sufficiently broken weight_scale
18230 value: now, they use a reasonable default and carry on. Partial
18231 fix for 5786; bugfix on 0.2.2.17-alpha.
18232 - Check more thoroughly to prevent a rogue authority from
18233 double-voting on any consensus directory parameter. Previously,
18234 authorities would crash in this case if the total number of
18235 votes for any parameter exceeded the number of active voters,
18236 but would let it pass otherwise. Partial fix for bug 5786; bugfix
18240 - Rate-limit log messages when asked to connect anonymously to
18241 a private address. When these hit, they tended to hit fast and
18242 often. Also, don't bother trying to connect to addresses that we
18243 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
18244 reply makes us think we have been lied to, even when the address the
18245 client tried to connect to was "localhost." Resolves ticket 2822.
18246 - Allow packagers to insert an extra string in server descriptor
18247 platform lines by setting the preprocessor variable TOR_BUILD_TAG.
18248 Resolves the rest of ticket 2988.
18249 - Raise the threshold of server descriptors needed (75%) and exit
18250 server descriptors needed (50%) before we will declare ourselves
18251 bootstrapped. This will make clients start building circuits a
18252 little later, but makes the initially constructed circuits less
18253 skewed and less in conflict with further directory fetches. Fixes
18255 - Close any connection that sends unrecognized junk before the
18256 handshake. Solves an issue noted in bug 4369.
18257 - Improve log messages about managed transports. Resolves ticket 5070.
18258 - Tag a bridge's descriptor as "never to be sent unencrypted".
18259 This shouldn't matter, since bridges don't open non-anonymous
18260 connections to the bridge authority and don't allow unencrypted
18261 directory connections from clients, but we might as well make
18262 sure. Closes bug 5139.
18263 - Expose our view of whether we have gone dormant to the controller,
18264 via a new "GETINFO dormant" value. Torbutton and other controllers
18265 can use this to avoid doing periodic requests through Tor while
18266 it's dormant (bug 4718). Fixes bug 5954.
18267 - Tell GCC and Clang to check for any errors in format strings passed
18268 to the tor_v*(print|scan)f functions.
18269 - Update to the May 1 2012 Maxmind GeoLite Country database.
18271 o Minor bugfixes (already included in 0.2.2.36):
18272 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
18273 Fixes bug 5346; bugfix on 0.0.8pre3.
18274 - Correct parsing of certain date types in parse_http_time().
18275 Without this patch, If-Modified-Since would behave
18276 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
18277 Esteban Manchado Velázques.
18278 - Make our number-parsing functions always treat too-large values
18279 as an error, even when those values exceed the width of the
18280 underlying type. Previously, if the caller provided these
18281 functions with minima or maxima set to the extreme values of the
18282 underlying integer type, these functions would return those
18283 values on overflow rather than treating overflow as an error.
18284 Fixes part of bug 5786; bugfix on 0.0.9.
18285 - If we hit the error case where routerlist_insert() replaces an
18286 existing (old) server descriptor, make sure to remove that
18287 server descriptor from the old_routers list. Fix related to bug
18288 1776. Bugfix on 0.2.2.18-alpha.
18289 - Clarify the behavior of MaxCircuitDirtiness with hidden service
18290 circuits. Fixes issue 5259.
18292 o Minor bugfixes (coding cleanup, on 0.2.2.x and earlier):
18293 - Prevent a null-pointer dereference when receiving a data cell
18294 for a nonexistent stream when the circuit in question has an
18295 empty deliver window. We don't believe this is triggerable,
18296 since we don't currently allow deliver windows to become empty,
18297 but the logic is tricky enough that it's better to make the code
18298 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
18299 - Fix a memory leak when trying to launch a DNS request when the
18300 network is disabled or the nameservers are unconfigurable. Fixes
18301 bug 5916; bugfix on Tor 0.1.2.1-alpha (for the unconfigurable
18302 nameserver case) and on 0.2.3.9-alpha (for the DisableNetwork case).
18303 - Don't hold a Windows file handle open for every file mapping;
18304 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
18306 - Avoid O(n^2) performance characteristics when parsing a large
18307 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
18308 - Format more doubles with %f, not %lf. Patch from grarpamp to make
18309 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
18311 - Make our replacement implementation of strtok_r() compatible with
18312 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
18313 bugfix on 0.2.2.1-alpha.
18314 - Fix a NULL-pointer dereference on a badly formed
18315 SETCIRCUITPURPOSE command. Found by mikeyc. Fixes bug 5796;
18316 bugfix on 0.2.2.9-alpha.
18317 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
18318 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
18319 - Defensively refactor rend_mid_rendezvous() so that protocol
18320 violations and length checks happen in the beginning. Fixes
18322 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
18323 that IPv6 stuff will compile on MSVC, and compilation issues
18324 will be easier to track down. Fixes bug 5861.
18326 o Minor bugfixes (correctness, on 0.2.2.x and earlier):
18327 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
18328 resource exhaustion, so that clients can adjust their load to
18329 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
18330 started using END_STREAM_REASON_RESOURCELIMIT.
18331 - Don't check for whether the address we're using for outbound
18332 connections has changed until after the outbound connection has
18333 completed. On Windows, getsockname() doesn't succeed until the
18334 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
18335 - If the configuration tries to set MyFamily on a bridge, refuse to
18336 do so, and warn about the security implications. Fixes bug 4657;
18337 bugfix on 0.2.0.3-alpha.
18338 - If the client fails to set a reasonable set of ciphersuites
18339 during its v2 handshake renegotiation, allow the renegotiation to
18340 continue nevertheless (i.e. send all the required certificates).
18341 Fixes bug 4591; bugfix on 0.2.0.20-rc.
18342 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
18343 option is set to 0 (which Vidalia version 0.2.16 now does when
18344 a SAVECONF attempt fails), perform other actions that SIGHUP
18345 usually causes (like reopening the logs). Fixes bug 5095; bugfix
18347 - If we fail to write a microdescriptor to the disk cache, do not
18348 continue replacing the old microdescriptor file. Fixes bug 2954;
18349 bugfix on 0.2.2.6-alpha.
18350 - Exit nodes don't need to fetch certificates for authorities that
18351 they don't recognize; only directory authorities, bridges,
18352 and caches need to do that. Fixes part of bug 2297; bugfix on
18354 - Correctly handle checking the permissions on the parent
18355 directory of a control socket in the root directory. Bug found
18356 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
18358 - When told to add a bridge with the same digest as a preexisting
18359 bridge but a different addr:port, change the addr:port as
18360 requested. Previously we would not notice the change. Fixes half
18361 of bug 5603; fix on 0.2.2.26-beta.
18362 - End AUTHCHALLENGE error messages (in the control protocol) with
18363 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36 and 0.2.3.13-alpha.
18365 o Minor bugfixes (on 0.2.3.x):
18366 - Turn an assertion (that the number of handshakes received as a
18367 server is not < 1) into a warning. Fixes bug 4873; bugfix on
18369 - Format IPv4 addresses correctly in ADDRMAP events. (Previously,
18370 we had reversed them when the answer was cached.) Fixes bug
18371 5723; bugfix on 0.2.3.1-alpha.
18372 - Work correctly on Linux systems with accept4 support advertised in
18373 their headers, but without accept4 support in the kernel. Fix
18374 by murb. Fixes bug 5762; bugfix on 0.2.3.1-alpha.
18375 - When told to add a bridge with the same addr:port as a preexisting
18376 bridge but a different transport, change the transport as
18377 requested. Previously we would not notice the change. Fixes half
18378 of bug 5603; fix on 0.2.3.2-alpha.
18379 - Avoid a "double-reply" warning when replying to a SOCKS request
18380 with a parse error. Patch from Fabian Keil. Fixes bug 4108;
18381 bugfix on 0.2.3.4-alpha.
18382 - Fix a bug where a bridge authority crashes if it has seen no
18383 directory requests when it's time to write statistics to disk.
18384 Fixes bug 5891; bugfix on 0.2.3.6-alpha. Also fixes bug 5508 in
18386 - Don't try to open non-control listeners when DisableNetwork is set.
18387 Previously, we'd open all listeners, then immediately close them.
18388 Fixes bug 5604; bugfix on 0.2.3.9-alpha.
18389 - Don't abort the managed proxy protocol if the managed proxy
18390 sends us an unrecognized line; ignore it instead. Fixes bug
18391 5910; bugfix on 0.2.3.9-alpha.
18392 - Fix a compile warning in crypto.c when compiling with clang 3.1.
18393 Fixes bug 5969, bugfix on 0.2.3.9-alpha.
18394 - Fix a compilation issue on GNU Hurd, which doesn't have PATH_MAX.
18395 Fixes bug 5355; bugfix on 0.2.3.11-alpha.
18396 - Remove bogus definition of "_WIN32" from src/win32/orconfig.h, to
18397 unbreak the MSVC build. Fixes bug 5858; bugfix on 0.2.3.12-alpha.
18398 - Resolve numerous small warnings and build issues with MSVC. Resolves
18401 o Documentation fixes:
18402 - Improve the manual's documentation for the NT Service command-line
18403 options. Addresses ticket 3964.
18404 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
18405 - Document the changes to the ORPort and DirPort options, and the
18406 fact that {OR/Dir}ListenAddress is now unnecessary (and
18407 therefore deprecated). Resolves ticket 5597.
18410 - Remove the torrc.bridge file: we don't use it for anything, and
18411 it had become badly desynchronized from torrc.sample. Resolves
18415 Changes in version 0.2.2.36 - 2012-05-24
18416 Tor 0.2.2.36 updates the addresses for two of the eight directory
18417 authorities, fixes some potential anonymity and security issues,
18418 and fixes several crash bugs.
18420 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
18421 known flaws, and nobody should be using them. You should upgrade. If
18422 you're using a Linux or BSD and its packages are obsolete, stop using
18423 those packages and upgrade anyway.
18425 o Directory authority changes:
18426 - Change IP address for maatuska (v3 directory authority).
18427 - Change IP address for ides (v3 directory authority), and rename
18431 - When building or running with any version of OpenSSL earlier
18432 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
18433 versions have a bug (CVE-2011-4576) in which their block cipher
18434 padding includes uninitialized data, potentially leaking sensitive
18435 information to any peer with whom they make a SSLv3 connection. Tor
18436 does not use SSL v3 by default, but a hostile client or server
18437 could force an SSLv3 connection in order to gain information that
18438 they shouldn't have been able to get. The best solution here is to
18439 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
18440 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
18441 to make sure that the bug can't happen.
18442 - Never use a bridge or a controller-supplied node as an exit, even
18443 if its exit policy allows it. Found by wanoskarnet. Fixes bug
18444 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
18445 and 0.2.0.3-alpha (for bridge-purpose descriptors).
18446 - Only build circuits if we have a sufficient threshold of the total
18447 descriptors that are marked in the consensus with the "Exit"
18448 flag. This mitigates an attack proposed by wanoskarnet, in which
18449 all of a client's bridges collude to restrict the exit nodes that
18450 the client knows about. Fixes bug 5343.
18451 - Provide controllers with a safer way to implement the cookie
18452 authentication mechanism. With the old method, if another locally
18453 running program could convince a controller that it was the Tor
18454 process, then that program could trick the controller into telling
18455 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
18456 authentication method uses a challenge-response approach to prevent
18457 this attack. Fixes bug 5185; implements proposal 193.
18460 - Avoid logging uninitialized data when unable to decode a hidden
18461 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
18462 - Avoid a client-side assertion failure when receiving an INTRODUCE2
18463 cell on a general purpose circuit. Fixes bug 5644; bugfix on
18465 - Fix builds when the path to sed, openssl, or sha1sum contains
18466 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
18468 - Correct our replacements for the timeradd() and timersub() functions
18469 on platforms that lack them (for example, Windows). The timersub()
18470 function is used when expiring circuits, while timeradd() is
18471 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
18472 bugfix on 0.2.2.24-alpha.
18473 - Fix the SOCKET_OK test that we use to tell when socket
18474 creation fails so that it works on Win64. Fixes part of bug 4533;
18475 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
18478 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
18479 Fixes bug 5346; bugfix on 0.0.8pre3.
18480 - Make our number-parsing functions always treat too-large values
18481 as an error, even when those values exceed the width of the
18482 underlying type. Previously, if the caller provided these
18483 functions with minima or maxima set to the extreme values of the
18484 underlying integer type, these functions would return those
18485 values on overflow rather than treating overflow as an error.
18486 Fixes part of bug 5786; bugfix on 0.0.9.
18487 - Older Linux kernels erroneously respond to strange nmap behavior
18488 by having accept() return successfully with a zero-length
18489 socket. When this happens, just close the connection. Previously,
18490 we would try harder to learn the remote address: but there was
18491 no such remote address to learn, and our method for trying to
18492 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
18493 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
18494 - Correct parsing of certain date types in parse_http_time().
18495 Without this patch, If-Modified-Since would behave
18496 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
18497 Esteban Manchado Velázques.
18498 - Change the BridgePassword feature (part of the "bridge community"
18499 design, which is not yet implemented) to use a time-independent
18500 comparison. The old behavior might have allowed an adversary
18501 to use timing to guess the BridgePassword value. Fixes bug 5543;
18502 bugfix on 0.2.0.14-alpha.
18503 - Detect and reject certain misformed escape sequences in
18504 configuration values. Previously, these values would cause us
18505 to crash if received in a torrc file or over an authenticated
18506 control port. Bug found by Esteban Manchado Velázquez, and
18507 independently by Robert Connolly from Matta Consulting who further
18508 noted that it allows a post-authentication heap overflow. Patch
18509 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
18510 bugfix on 0.2.0.16-alpha.
18511 - Fix a compile warning when using the --enable-openbsd-malloc
18512 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
18513 - During configure, detect when we're building with clang version
18514 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
18515 CFLAGS. clang doesn't support them yet.
18516 - When sending an HTTP/1.1 proxy request, include a Host header.
18517 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
18518 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
18519 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
18520 - If we hit the error case where routerlist_insert() replaces an
18521 existing (old) server descriptor, make sure to remove that
18522 server descriptor from the old_routers list. Fix related to bug
18523 1776. Bugfix on 0.2.2.18-alpha.
18525 o Minor bugfixes (documentation and log messages):
18526 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
18527 Fixes bug 4856; bugfix on Tor 0.0.6.
18528 - Update "ClientOnly" man page entry to explain that there isn't
18529 really any point to messing with it. Resolves ticket 5005.
18530 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
18531 directory authority option (introduced in Tor 0.2.2.34).
18532 - Downgrade the "We're missing a certificate" message from notice
18533 to info: people kept mistaking it for a real problem, whereas it
18534 is seldom the problem even when we are failing to bootstrap. Fixes
18535 bug 5067; bugfix on 0.2.0.10-alpha.
18536 - Correctly spell "connect" in a log message on failure to create a
18537 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
18538 - Clarify the behavior of MaxCircuitDirtiness with hidden service
18539 circuits. Fixes issue 5259.
18542 - Directory authorities now reject versions of Tor older than
18543 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
18544 inclusive. These versions accounted for only a small fraction of
18545 the Tor network, and have numerous known security issues. Resolves
18547 - Update to the May 1 2012 Maxmind GeoLite Country database.
18550 - When sending or relaying a RELAY_EARLY cell, we used to convert
18551 it to a RELAY cell if the connection was using the v1 link
18552 protocol. This was a workaround for older versions of Tor, which
18553 didn't handle RELAY_EARLY cells properly. Now that all supported
18554 versions can handle RELAY_EARLY cells, and now that we're enforcing
18555 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
18556 remove this workaround. Addresses bug 4786.
18559 Changes in version 0.2.3.15-alpha - 2012-04-30
18560 Tor 0.2.3.15-alpha fixes a variety of smaller bugs, including making
18561 the development branch build on Windows again.
18563 o Minor bugfixes (on 0.2.2.x and earlier):
18564 - Make sure that there are no unhandled pending TLS errors before
18565 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
18566 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
18567 Bugfix on 0.1.0.5-rc; fixes bug 4528.
18568 - Fix an assert that directory authorities could trigger on sighup
18569 during some configuration state transitions. We now don't treat
18570 it as a fatal error when the new descriptor we just generated in
18571 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
18572 - After we pick a directory mirror, we would refuse to use it if
18573 it's in our ExcludeExitNodes list, resulting in mysterious failures
18574 to bootstrap for people who just wanted to avoid exiting from
18575 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
18576 - When building with --enable-static-tor on OpenBSD, do not
18577 erroneously attempt to link -lrt. Fixes bug 5103.
18579 o Minor bugfixes (on 0.2.3.x):
18580 - When Tor is built with kernel headers from a recent (last few
18581 years) Linux kernel, do not fail to run on older (pre-2.6.28
18582 Linux kernels). Fixes bug 5112; bugfix on 0.2.3.1-alpha.
18583 - Fix cross-compilation issues with mingw. Bugfixes on 0.2.3.6-alpha
18584 and 0.2.3.12-alpha.
18585 - Fix compilation with miniupnpc version 1.6; patch from
18586 Anthony G. Basile. Fixes bug 5434; bugfix on 0.2.3.12-alpha.
18587 - Fix compilation with MSVC, which had defined MS_WINDOWS. Bugfix
18588 on 0.2.3.13-alpha; found and fixed by Gisle Vanem.
18589 - Fix compilation on platforms without unistd.h, or where environ
18590 is defined in stdlib.h. Fixes bug 5704; bugfix on 0.2.3.13-alpha.
18593 - Directory authorities are now a little more lenient at accepting
18594 older router descriptors, or newer router descriptors that don't
18595 make big changes. This should help ameliorate past and future
18596 issues where routers think they have uploaded valid descriptors,
18597 but the authorities don't think so. Fix for ticket 2479.
18598 - Make the code that clients use to detect an address change be
18599 IPv6-aware, so that it won't fill clients' logs with error
18600 messages when trying to get the IPv4 address of an IPv6
18601 connection. Implements ticket 5537.
18603 o Removed features:
18604 - Remove the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays option;
18605 authorities needed to use it for a while to keep the network working
18606 as people upgraded to 0.2.1.31, 0.2.2.34, or 0.2.3.6-alpha, but
18607 that was six months ago. As of now, it should no longer be needed
18611 Changes in version 0.2.3.14-alpha - 2012-04-23
18612 Tor 0.2.3.14-alpha fixes yet more bugs to get us closer to a release
18613 candidate. It also dramatically speeds up AES: fast relays should
18614 consider switching to the newer OpenSSL library.
18616 o Directory authority changes:
18617 - Change IP address for ides (v3 directory authority), and rename
18621 - Avoid logging uninitialized data when unable to decode a hidden
18622 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
18623 - Avoid a client-side assertion failure when receiving an INTRODUCE2
18624 cell on a general purpose circuit. Fixes bug 5644; bugfix on
18626 - If authorities are unable to get a v2 consensus document from other
18627 directory authorities, they no longer fall back to fetching
18628 them from regular directory caches. Fixes bug 5635; bugfix on
18629 0.2.2.26-beta, where routers stopped downloading v2 consensus
18630 documents entirely.
18631 - When we start a Tor client with a normal consensus already cached,
18632 be willing to download a microdescriptor consensus. Fixes bug 4011;
18633 fix on 0.2.3.1-alpha.
18635 o Major features (performance):
18636 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
18637 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
18638 vectorized AES implementations as appropriate. These can be much,
18639 much faster than other AES implementations.
18641 o Minor bugfixes (0.2.2.x and earlier):
18642 - Don't launch more than 10 service-side introduction-point circuits
18643 for a hidden service in five minutes. Previously, we would consider
18644 launching more introduction-point circuits if at least one second
18645 had passed without any introduction-point circuits failing. Fixes
18646 bug 4607; bugfix on 0.0.7pre1.
18647 - Change the BridgePassword feature (part of the "bridge community"
18648 design, which is not yet implemented) to use a time-independent
18649 comparison. The old behavior might have allowed an adversary
18650 to use timing to guess the BridgePassword value. Fixes bug 5543;
18651 bugfix on 0.2.0.14-alpha.
18652 - Enforce correct return behavior of tor_vsscanf() when the '%%'
18653 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
18654 - When sending an HTTP/1.1 proxy request, include a Host header.
18655 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
18656 - Don't log that we have "decided to publish new relay descriptor"
18657 unless we are actually publishing a descriptor. Fixes bug 3942;
18658 bugfix on 0.2.2.28-beta.
18660 o Minor bugfixes (0.2.3.x):
18661 - Fix a bug where a bridge authority crashes (on a failed assert)
18662 if it has seen no directory requests when it's time to write
18663 statistics to disk. Fixes bug 5508. Bugfix on 0.2.3.6-alpha.
18664 - Fix bug stomping on ORPort option NoListen and ignoring option
18665 NoAdvertise. Fixes bug 5151; bugfix on 0.2.3.9-alpha.
18666 - In the testsuite, provide a large enough buffer in the tor_sscanf
18667 unit test. Otherwise we'd overrun that buffer and crash during
18668 the unit tests. Found by weasel. Fixes bug 5449; bugfix on
18670 - Make sure we create the keys directory if it doesn't exist and we're
18671 about to store the dynamic Diffie-Hellman parameters. Fixes bug
18672 5572; bugfix on 0.2.3.13-alpha.
18673 - Fix a small memory leak when trying to decode incorrect base16
18674 authenticator during SAFECOOKIE authentication. Found by
18675 Coverity Scan. Fixes CID 507. Bugfix on 0.2.3.13-alpha.
18678 - Add more information to a log statement that might help track down
18679 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
18680 non-IP address" messages (or any Bug messages, for that matter!),
18681 please let us know about it.
18682 - Relays now understand an IPv6 address when they get one from a
18683 directory server. Resolves ticket 4875.
18684 - Resolve IPv6 addresses in bridge and entry statistics to country
18685 code "??" which means we at least count them. Resolves ticket 5053;
18686 improves on 0.2.3.9-alpha.
18687 - Update to the April 3 2012 Maxmind GeoLite Country database.
18688 - Begin a doc/state-contents.txt file to explain the contents of
18689 the Tor state file. Fixes bug 2987.
18691 o Default torrc changes:
18692 - Stop listing "socksport 9050" in torrc.sample. We open a socks
18693 port on 9050 by default anyway, so this should not change anything
18695 - Stop mentioning the deprecated *ListenAddress options in
18696 torrc.sample. Fixes bug 5438.
18697 - Document unit of bandwidth related options in sample torrc.
18700 o Removed features:
18701 - The "torify" script no longer supports the "tsocks" socksifier
18702 tool, since tsocks doesn't support DNS and UDP right for Tor.
18703 Everyone should be using torsocks instead. Fixes bugs 3530 and
18704 5180. Based on a patch by "ugh".
18706 o Code refactoring:
18707 - Change the symmetric cipher interface so that creating and
18708 initializing a stream cipher are no longer separate functions.
18709 - Remove all internal support for unpadded RSA. We never used it, and
18710 it would be a bad idea to start.
18713 Changes in version 0.2.3.13-alpha - 2012-03-26
18714 Tor 0.2.3.13-alpha fixes a variety of stability and correctness bugs
18715 in managed pluggable transports, as well as providing other cleanups
18716 that get us closer to a release candidate.
18718 o Directory authority changes:
18719 - Change IP address for maatuska (v3 directory authority).
18722 - Provide controllers with a safer way to implement the cookie
18723 authentication mechanism. With the old method, if another locally
18724 running program could convince a controller that it was the Tor
18725 process, then that program could trick the controller into telling
18726 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
18727 authentication method uses a challenge-response approach to prevent
18728 this attack. Fixes bug 5185, implements proposal 193.
18729 - Never use a bridge or a controller-supplied node as an exit, even
18730 if its exit policy allows it. Found by wanoskarnet. Fixes bug
18731 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
18732 and 0.2.0.3-alpha (for bridge-purpose descriptors).
18733 - Only build circuits if we have a sufficient threshold of the total
18734 descriptors that are marked in the consensus with the "Exit"
18735 flag. This mitigates an attack proposed by wanoskarnet, in which
18736 all of a client's bridges collude to restrict the exit nodes that
18737 the client knows about. Fixes bug 5343.
18739 o Major bugfixes (on Tor 0.2.3.x):
18740 - Avoid an assert when managed proxies like obfsproxy are configured,
18741 and we receive HUP signals or setconf attempts too rapidly. This
18742 situation happens most commonly when Vidalia tries to attach to
18743 Tor or tries to configure the Tor it's attached to. Fixes bug 5084;
18744 bugfix on 0.2.3.6-alpha.
18745 - Fix a relay-side pluggable transports bug where managed proxies were
18746 unreachable from the Internet, because Tor asked them to bind on
18747 localhost. Fixes bug 4725; bugfix on 0.2.3.9-alpha.
18748 - Stop discarding command-line arguments when TestingTorNetwork
18749 is set. Discovered by Kevin Bauer. Fixes bug 5373; bugfix on
18750 0.2.3.9-alpha, where task 4552 added support for two layers of
18752 - Resume allowing the unit tests to run in gdb. This was accidentally
18753 made impossible when the DisableDebuggerAttachment option was
18754 introduced. Fixes bug 5448; bugfix on 0.2.3.9-alpha.
18755 - Resume building with nat-pmp support. Fixes bug 4955; bugfix on
18756 0.2.3.11-alpha. Reported by Anthony G. Basile.
18758 o Minor bugfixes (on 0.2.2.x and earlier):
18759 - Ensure we don't cannibalize circuits that are longer than three hops
18760 already, so we don't end up making circuits with 5 or more
18761 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
18762 0.1.0.1-rc which introduced cannibalization.
18763 - Detect and reject certain misformed escape sequences in
18764 configuration values. Previously, these values would cause us
18765 to crash if received in a torrc file or over an authenticated
18766 control port. Bug found by Esteban Manchado Velázquez, and
18767 independently by Robert Connolly from Matta Consulting who further
18768 noted that it allows a post-authentication heap overflow. Patch
18769 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
18770 bugfix on 0.2.0.16-alpha.
18771 - Fix a compile warning when using the --enable-openbsd-malloc
18772 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
18773 - Directory caches no longer refuse to clean out descriptors because
18774 of missing v2 networkstatus documents, unless they're configured
18775 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
18776 0.2.2.26-beta. Patch by Daniel Bryg.
18777 - Update to the latest version of the tinytest unit testing framework.
18778 This includes a couple of bugfixes that can be relevant for
18779 running forked unit tests on Windows, and removes all reserved
18782 o Minor bugfixes (on 0.2.3.x):
18783 - On a failed pipe() call, don't leak file descriptors. Fixes bug
18784 4296; bugfix on 0.2.3.1-alpha.
18785 - Spec conformance: on a v3 handshake, do not send a NETINFO cell
18786 until after we have received a CERTS cell. Fixes bug 4361; bugfix
18787 on 0.2.3.6-alpha. Patch by "frosty".
18788 - When binding to an IPv6 address, set the IPV6_V6ONLY socket
18789 option, so that the IP stack doesn't decide to use it for IPv4
18790 too. Fixes bug 4760; bugfix on 0.2.3.9-alpha.
18791 - Ensure that variables set in Tor's environment cannot override
18792 environment variables that Tor passes to a managed
18793 pluggable-transport proxy. Previously, Tor would pass every
18794 variable in its environment to managed proxies along with the new
18795 ones, in such a way that on many operating systems, the inherited
18796 environment variables would override those which Tor tried to
18797 explicitly set. Bugfix on 0.2.3.12-alpha for most Unixoid systems;
18798 bugfix on 0.2.3.9-alpha for Windows.
18801 - A wide variety of new unit tests by Esteban Manchado Velázquez.
18802 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
18803 - Update to the March 6 2012 Maxmind GeoLite Country database.
18806 Changes in version 0.2.3.12-alpha - 2012-02-13
18807 Tor 0.2.3.12-alpha lets fast exit relays scale better, allows clients
18808 to use bridges that run Tor 0.2.2.x, and resolves several big bugs
18809 when Tor is configured to use a pluggable transport like obfsproxy.
18812 - Fix builds when the path to sed, openssl, or sha1sum contains
18813 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
18815 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
18816 connections. This change should allow busy exit relays to stop
18817 running out of available sockets as quickly. Fixes bug 4950;
18818 bugfix on 0.2.2.26-beta.
18819 - Allow 0.2.3.x clients to use 0.2.2.x bridges. Previously the client
18820 would ask the bridge for microdescriptors, which are only supported
18821 in 0.2.3.x, and then fail to bootstrap when it didn't get the
18822 answers it wanted. Fixes bug 4013; bugfix on 0.2.3.2-alpha.
18823 - Properly set up obfsproxy's environment when in managed mode. The
18824 Tor Browser Bundle needs LD_LIBRARY_PATH to be passed to obfsproxy,
18825 and when you run your Tor as a daemon, there's no HOME. Fixes bugs
18826 5076 and 5082; bugfix on 0.2.3.6-alpha.
18829 - Use the dead_strip option when building Tor on OS X. This reduces
18830 binary size by almost 19% when linking openssl and libevent
18831 statically, which we do for Tor Browser Bundle.
18832 - Fix broken URLs in the sample torrc file, and tell readers about
18833 the OutboundBindAddress, ExitPolicyRejectPrivate, and
18834 PublishServerDescriptor options. Addresses bug 4652.
18835 - Update to the February 7 2012 Maxmind GeoLite Country database.
18838 - Downgrade the "We're missing a certificate" message from notice
18839 to info: people kept mistaking it for a real problem, whereas it
18840 is seldom the problem even when we are failing to bootstrap. Fixes
18841 bug 5067; bugfix on 0.2.0.10-alpha.
18842 - Don't put "TOR_PT_EXTENDED_SERVER_PORT=127.0.0.1:4200" in a
18843 managed pluggable transport server proxy's environment.
18844 Previously, we would put it there, even though Tor doesn't
18845 implement an 'extended server port' yet, and even though Tor
18846 almost certainly isn't listening at that address. For now, we set
18847 it to an empty string to avoid crashing older obfsproxies. Bugfix
18849 - Log the heartbeat message every HeartbeatPeriod seconds, not every
18850 HeartbeatPeriod + 1 seconds. Fixes bug 4942; bugfix on
18851 0.2.3.1-alpha. Bug reported by Scott Bennett.
18852 - Calculate absolute paths correctly on Windows. Fixes bug 4973;
18853 bugfix on 0.2.3.11-alpha.
18854 - Update "ClientOnly" man page entry to explain that there isn't
18855 really any point to messing with it. Resolves ticket 5005.
18856 - Use the correct CVE number for CVE-2011-4576 in our comments and
18857 log messages. Found by "fermenthor". Resolves bug 5066; bugfix on
18860 o Code simplifications and refactoring:
18861 - Use the _WIN32 macro throughout our code to detect Windows.
18862 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
18866 Changes in version 0.2.3.11-alpha - 2012-01-22
18867 Tor 0.2.3.11-alpha marks feature-freeze for the 0.2.3 tree. It deploys
18868 the last step of the plan to limit maximum circuit length, includes
18869 a wide variety of hidden service performance and correctness fixes,
18870 works around an OpenSSL security flaw if your distro is too stubborn
18871 to upgrade, and fixes a bunch of smaller issues.
18874 - Now that Tor 0.2.0.x is completely deprecated, enable the final
18875 part of "Proposal 110: Avoiding infinite length circuits" by
18876 refusing all circuit-extend requests that do not use a relay_early
18877 cell. This change helps Tor resist a class of denial-of-service
18878 attacks by limiting the maximum circuit length.
18879 - Adjust the number of introduction points that a hidden service
18880 will try to maintain based on how long its introduction points
18881 remain in use and how many introductions they handle. Fixes
18883 - Try to use system facilities for enumerating local interface
18884 addresses, before falling back to our old approach (which was
18885 binding a UDP socket, and calling getsockname() on it). That
18886 approach was scaring OS X users whose draconian firewall
18887 software warned about binding to UDP sockets, regardless of
18888 whether packets were sent. Now we try to use getifaddrs(),
18889 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
18890 system supports. Resolves ticket 1827.
18892 o Major security workaround:
18893 - When building or running with any version of OpenSSL earlier
18894 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
18895 versions have a bug (CVE-2011-4576) in which their block cipher
18896 padding includes uninitialized data, potentially leaking sensitive
18897 information to any peer with whom they make a SSLv3 connection. Tor
18898 does not use SSL v3 by default, but a hostile client or server
18899 could force an SSLv3 connection in order to gain information that
18900 they shouldn't have been able to get. The best solution here is to
18901 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
18902 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
18903 to make sure that the bug can't happen.
18906 - Fix the SOCKET_OK test that we use to tell when socket
18907 creation fails so that it works on Win64. Fixes part of bug 4533;
18908 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
18909 - Correct our replacements for the timeradd() and timersub() functions
18910 on platforms that lack them (for example, Windows). The timersub()
18911 function is used when expiring circuits, while timeradd() is
18912 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
18913 bugfix on 0.2.2.24-alpha and 0.2.3.1-alpha.
18914 - Do not use OpenSSL 1.0.0's counter mode: it has a critical bug
18915 that was fixed in OpenSSL 1.0.0a. We test for the counter mode
18916 bug at runtime, not compile time, because some distributions hack
18917 their OpenSSL to mis-report its version. Fixes bug 4779; bugfix
18918 on 0.2.3.9-alpha. Found by Pascal.
18920 o Minor features (controller):
18921 - Use absolute path names when reporting the torrc filename in the
18922 control protocol, so a controller can more easily find the torrc
18923 file. Resolves bug 1101.
18924 - Extend the control protocol to report flags that control a circuit's
18925 path selection in CIRC events and in replies to 'GETINFO
18926 circuit-status'. Implements part of ticket 2411.
18927 - Extend the control protocol to report the hidden service address
18928 and current state of a hidden-service-related circuit in CIRC
18929 events and in replies to 'GETINFO circuit-status'. Implements part
18931 - When reporting the path to the cookie file to the controller,
18932 give an absolute path. Resolves ticket 4881.
18933 - Allow controllers to request an event notification whenever a
18934 circuit is cannibalized or its purpose is changed. Implements
18935 part of ticket 3457.
18936 - Include the creation time of a circuit in CIRC and CIRC2
18937 control-port events and the list produced by the 'GETINFO
18938 circuit-status' control-port command.
18940 o Minor features (directory authorities):
18941 - Directory authorities now reject versions of Tor older than
18942 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
18943 inclusive. These versions accounted for only a small fraction of
18944 the Tor network, and have numerous known security issues. Resolves
18946 - Authority operators can now vote for all relays in a given
18947 set of countries to be BadDir/BadExit/Invalid/Rejected.
18948 - Provide two consensus parameters (FastFlagMinThreshold and
18949 FastFlagMaxThreshold) to control the range of allowable bandwidths
18950 for the Fast directory flag. These allow authorities to run
18951 experiments on appropriate requirements for being a "Fast" node.
18952 The AuthDirFastGuarantee config value still applies. Implements
18954 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
18955 directory authority option (introduced in Tor 0.2.2.34).
18957 o Minor features (other):
18958 - Don't disable the DirPort when we cannot exceed our AccountingMax
18959 limit during this interval because the effective bandwidthrate is
18960 low enough. This is useful in a situation where AccountMax is only
18961 used as an additional safeguard or to provide statistics.
18962 - Prepend an informative header to generated dynamic_dh_params files.
18963 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
18964 EntryNodes will have no effect. Resolves issue 2571.
18965 - Log more useful messages when we fail to disable debugger
18967 - Log which authority we're missing votes from when we go to fetch
18968 them from the other auths.
18969 - Log (at debug level) whenever a circuit's purpose is changed.
18970 - Add missing documentation for the MaxClientCircuitsPending,
18971 UseMicrodescriptors, UserspaceIOCPBuffers, and
18972 _UseFilteringSSLBufferevents options, all introduced during
18973 the 0.2.3.x series.
18974 - Update to the January 3 2012 Maxmind GeoLite Country database.
18976 o Minor bugfixes (hidden services):
18977 - Don't close hidden service client circuits which have almost
18978 finished connecting to their destination when they reach
18979 the normal circuit-build timeout. Previously, we would close
18980 introduction circuits which are waiting for an acknowledgement
18981 from the introduction point, and rendezvous circuits which have
18982 been specified in an INTRODUCE1 cell sent to a hidden service,
18983 after the normal CBT. Now, we mark them as 'timed out', and launch
18984 another rendezvous attempt in parallel. This behavior change can
18985 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
18986 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
18987 - Don't close hidden-service-side rendezvous circuits when they
18988 reach the normal circuit-build timeout. This behavior change can
18989 be disabled using the new
18990 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
18991 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
18992 - Make sure we never mark the wrong rendezvous circuit as having
18993 had its introduction cell acknowledged by the introduction-point
18994 relay. Previously, when we received an INTRODUCE_ACK cell on a
18995 client-side hidden-service introduction circuit, we might have
18996 marked a rendezvous circuit other than the one we specified in
18997 the INTRODUCE1 cell as INTRO_ACKED, which would have produced
18998 a warning message and interfered with the hidden service
18999 connection-establishment process. Fixes bug 4759; bugfix on
19000 0.2.3.3-alpha, when we added the stream-isolation feature which
19001 might cause Tor to open multiple rendezvous circuits for the same
19003 - Don't trigger an assertion failure when we mark a new client-side
19004 hidden-service introduction circuit for close during the process
19005 of creating it. Fixes bug 4796; bugfix on 0.2.3.6-alpha. Reported
19008 o Minor bugfixes (log messages):
19009 - Correctly spell "connect" in a log message on failure to create a
19010 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta and
19012 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
19013 Fixes bug 4856; bugfix on Tor 0.0.6.
19014 - Fix the log message describing how we work around discovering
19015 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
19016 4837; bugfix on 0.2.2.9-alpha.
19017 - When logging about a disallowed .exit name, do not also call it
19018 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
19020 o Minor bugfixes (build fixes):
19021 - During configure, detect when we're building with clang version
19022 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
19023 CFLAGS. clang doesn't support them yet.
19024 - During configure, search for library containing cos function as
19025 libm lives in libcore on some platforms (BeOS/Haiku). Linking
19026 against libm was hard-coded before. Fixes the first part of bug
19027 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
19029 - Detect attempts to build Tor on (as yet hypothetical) versions
19030 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
19031 fix for bug 4533. Bugfix on 0.2.2.28-beta.
19032 - Preprocessor directives should not be put inside the arguments
19033 of a macro. This would break compilation with GCC releases prior
19034 to version 3.3. We would never recommend such an old GCC version,
19035 but it is apparently required for binary compatibility on some
19036 platforms (namely, certain builds of Haiku). Fixes the other part
19037 of bug 4727; bugfix on 0.2.3.3-alpha. Patch and analysis by Martin
19040 o Minor bugfixes (other):
19041 - Older Linux kernels erroneously respond to strange nmap behavior
19042 by having accept() return successfully with a zero-length
19043 socket. When this happens, just close the connection. Previously,
19044 we would try harder to learn the remote address: but there was
19045 no such remote address to learn, and our method for trying to
19046 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
19047 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
19048 - Fix null-pointer access that could occur if TLS allocation failed.
19049 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un". This was
19050 erroneously listed as fixed in 0.2.3.9-alpha, but the fix had
19051 accidentally been reverted.
19052 - Fix our implementation of crypto_random_hostname() so it can't
19053 overflow on ridiculously large inputs. (No Tor version has ever
19054 provided this kind of bad inputs, but let's be correct in depth.)
19055 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
19056 - Find more places in the code that should have been testing for
19057 invalid sockets using the SOCKET_OK macro. Required for a fix
19058 for bug 4533. Bugfix on 0.2.2.28-beta.
19059 - Fix an assertion failure when, while running with bufferevents, a
19060 connection finishes connecting after it is marked for close, but
19061 before it is closed. Fixes bug 4697; bugfix on 0.2.3.1-alpha.
19062 - test_util_spawn_background_ok() hardcoded the expected value
19063 for ENOENT to 2. This isn't portable as error numbers are
19064 platform specific, and particularly the hurd has ENOENT at
19065 0x40000002. Construct expected string at runtime, using the correct
19066 value for ENOENT. Fixes bug 4733; bugfix on 0.2.3.1-alpha.
19067 - Reject attempts to disable DisableDebuggerAttachment while Tor is
19068 running. Fixes bug 4650; bugfix on 0.2.3.9-alpha.
19069 - Use an appropriate-width type for sockets in tor-fw-helper on
19070 win64. Fixes bug 1983 at last. Bugfix on 0.2.3.9-alpha.
19073 - When sending or relaying a RELAY_EARLY cell, we used to convert
19074 it to a RELAY cell if the connection was using the v1 link
19075 protocol. This was a workaround for older versions of Tor, which
19076 didn't handle RELAY_EARLY cells properly. Now that all supported
19077 versions can handle RELAY_EARLY cells, and now that we're enforcing
19078 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
19079 remove this workaround. Addresses bug 4786.
19081 o Code simplifications and refactoring:
19082 - Use OpenSSL's built-in SSL_state_string_long() instead of our
19083 own homebrewed ssl_state_to_string() replacement. Patch from
19084 Emile Snyder. Fixes bug 4653.
19085 - Use macros to indicate OpenSSL versions, so we don't need to worry
19086 about accidental hexadecimal bit shifts.
19087 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
19089 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
19090 - Use the smartlist_add_asprintf() alias more consistently.
19091 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
19092 invalid value, rather than just -1.
19093 - Rename a handful of old identifiers, mostly related to crypto
19094 structures and crypto functions. By convention, our "create an
19095 object" functions are called "type_new()", our "free an object"
19096 functions are called "type_free()", and our types indicate that
19097 they are types only with a final "_t". But a handful of older
19098 types and functions broke these rules, with function names like
19099 "type_create" or "subsystem_op_type", or with type names like
19103 Changes in version 0.2.3.10-alpha - 2011-12-16
19104 Tor 0.2.3.10-alpha fixes a critical heap-overflow security issue in
19105 Tor's buffers code. Absolutely everybody should upgrade.
19107 The bug relied on an incorrect calculation when making data continuous
19108 in one of our IO buffers, if the first chunk of the buffer was
19109 misaligned by just the wrong amount. The miscalculation would allow an
19110 attacker to overflow a piece of heap-allocated memory. To mount this
19111 attack, the attacker would need to either open a SOCKS connection to
19112 Tor's SocksPort (usually restricted to localhost), or target a Tor
19113 instance configured to make its connections through a SOCKS proxy
19114 (which Tor does not do by default).
19116 Good security practice requires that all heap-overflow bugs should be
19117 presumed to be exploitable until proven otherwise, so we are treating
19118 this as a potential code execution attack. Please upgrade immediately!
19119 This bug does not affect bufferevents-based builds of Tor. Special
19120 thanks to "Vektor" for reporting this issue to us!
19122 This release also contains a few minor bugfixes for issues discovered
19126 - Fix a heap overflow bug that could occur when trying to pull
19127 data into the first chunk of a buffer, when that chunk had
19128 already had some data drained from it. Fixes CVE-2011-2778;
19129 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
19132 - If we can't attach streams to a rendezvous circuit when we
19133 finish connecting to a hidden service, clear the rendezvous
19134 circuit's stream-isolation state and try to attach streams
19135 again. Previously, we cleared rendezvous circuits' isolation
19136 state either too early (if they were freshly built) or not at all
19137 (if they had been built earlier and were cannibalized). Bugfix on
19138 0.2.3.3-alpha; fixes bug 4655.
19139 - Fix compilation of the libnatpmp helper on non-Windows. Bugfix on
19140 0.2.3.9-alpha; fixes bug 4691. Reported by Anthony G. Basile.
19141 - Fix an assertion failure when a relay with accounting enabled
19142 starts up while dormant. Fixes bug 4702; bugfix on 0.2.3.9-alpha.
19145 - Update to the December 6 2011 Maxmind GeoLite Country database.
19148 Changes in version 0.2.2.35 - 2011-12-16
19149 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
19150 buffers code. Absolutely everybody should upgrade.
19152 The bug relied on an incorrect calculation when making data continuous
19153 in one of our IO buffers, if the first chunk of the buffer was
19154 misaligned by just the wrong amount. The miscalculation would allow an
19155 attacker to overflow a piece of heap-allocated memory. To mount this
19156 attack, the attacker would need to either open a SOCKS connection to
19157 Tor's SocksPort (usually restricted to localhost), or target a Tor
19158 instance configured to make its connections through a SOCKS proxy
19159 (which Tor does not do by default).
19161 Good security practice requires that all heap-overflow bugs should be
19162 presumed to be exploitable until proven otherwise, so we are treating
19163 this as a potential code execution attack. Please upgrade immediately!
19164 This bug does not affect bufferevents-based builds of Tor. Special
19165 thanks to "Vektor" for reporting this issue to us!
19167 Tor 0.2.2.35 also fixes several bugs in previous versions, including
19168 crash bugs for unusual configurations, and a long-term bug that
19169 would prevent Tor from starting on Windows machines with draconian
19172 With this release, we remind everyone that 0.2.0.x has reached its
19173 formal end-of-life. Those Tor versions have many known flaws, and
19174 nobody should be using them. You should upgrade -- ideally to the
19175 0.2.2.x series. If you're using a Linux or BSD and its packages are
19176 obsolete, stop using those packages and upgrade anyway.
19178 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
19179 longer receive support after some time in early 2012.
19182 - Fix a heap overflow bug that could occur when trying to pull
19183 data into the first chunk of a buffer, when that chunk had
19184 already had some data drained from it. Fixes CVE-2011-2778;
19185 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
19186 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
19187 that it doesn't attempt to allocate a socketpair. This could cause
19188 some problems on Windows systems with overzealous firewalls. Fix for
19189 bug 4457; workaround for Libevent versions 2.0.1-alpha through
19191 - If we mark an OR connection for close based on a cell we process,
19192 don't process any further cells on it. We already avoid further
19193 reads on marked-for-close connections, but now we also discard the
19194 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
19195 which was the first version where we might mark a connection for
19196 close based on processing a cell on it.
19197 - Correctly sanity-check that we don't underflow on a memory
19198 allocation (and then assert) for hidden service introduction
19199 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
19200 bugfix on 0.2.1.5-alpha.
19201 - Fix a memory leak when we check whether a hidden service
19202 descriptor has any usable introduction points left. Fixes bug
19203 4424. Bugfix on 0.2.2.25-alpha.
19204 - Don't crash when we're running as a relay and don't have a GeoIP
19205 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
19206 we've had in the 0.2.3.x branch already.
19207 - When running as a client, do not print a misleading (and plain
19208 wrong) log message that we're collecting "directory request"
19209 statistics: clients don't collect statistics. Also don't create a
19210 useless (because empty) stats file in the stats/ directory. Fixes
19211 bug 4353; bugfix on 0.2.2.34.
19214 - Detect failure to initialize Libevent. This fix provides better
19215 detection for future instances of bug 4457.
19216 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
19217 function. This was eating up hideously large amounts of time on some
19218 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
19219 - Resolve an integer overflow bug in smartlist_ensure_capacity().
19220 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
19222 - Don't warn about unused log_mutex in log.c when building with
19223 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
19224 0.1.0.6-rc which introduced --disable-threads.
19225 - When configuring, starting, or stopping an NT service, stop
19226 immediately after the service configuration attempt has succeeded
19227 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
19228 - When sending a NETINFO cell, include the original address
19229 received for the other side, not its canonical address. Found
19230 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
19231 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
19232 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
19233 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
19234 occurred when a client tried to fetch a descriptor for a bridge
19235 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
19236 - Backport fixes for a pair of compilation warnings on Windows.
19237 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
19238 - If we had ever tried to call tor_addr_to_str on an address of
19239 unknown type, we would have done a strdup on an uninitialized
19240 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
19241 Reported by "troll_un".
19242 - Correctly detect and handle transient lookup failures from
19243 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
19244 Reported by "troll_un".
19245 - Fix null-pointer access that could occur if TLS allocation failed.
19246 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
19247 - Use tor_socket_t type for listener argument to accept(). Fixes bug
19248 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
19251 - Add two new config options for directory authorities:
19252 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
19253 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
19254 that is always sufficient to satisfy the bandwidth requirement for
19255 the Guard flag. Now it will be easier for researchers to simulate
19256 Tor networks with different values. Resolves ticket 4484.
19257 - When Tor ignores a hidden service specified in its configuration,
19258 include the hidden service's directory in the warning message.
19259 Previously, we would only tell the user that some hidden service
19260 was ignored. Bugfix on 0.0.6; fixes bug 4426.
19261 - Update to the December 6 2011 Maxmind GeoLite Country database.
19263 o Packaging changes:
19264 - Make it easier to automate expert package builds on Windows,
19265 by removing an absolute path from makensis.exe command.
19268 Changes in version 0.2.1.32 - 2011-12-16
19269 Tor 0.2.1.32 backports important security and privacy fixes for
19270 oldstable. This release is intended only for package maintainers and
19271 others who cannot use the 0.2.2 stable series. All others should be
19272 using Tor 0.2.2.x or newer.
19274 The Tor 0.2.1.x series will reach formal end-of-life some time in
19275 early 2012; we will stop releasing patches for it then.
19277 o Major bugfixes (also included in 0.2.2.x):
19278 - Correctly sanity-check that we don't underflow on a memory
19279 allocation (and then assert) for hidden service introduction
19280 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
19281 bugfix on 0.2.1.5-alpha.
19282 - Fix a heap overflow bug that could occur when trying to pull
19283 data into the first chunk of a buffer, when that chunk had
19284 already had some data drained from it. Fixes CVE-2011-2778;
19285 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
19288 - Update to the December 6 2011 Maxmind GeoLite Country database.
19291 Changes in version 0.2.3.9-alpha - 2011-12-08
19292 Tor 0.2.3.9-alpha introduces initial IPv6 support for bridges, adds
19293 a "DisableNetwork" security feature that bundles can use to avoid
19294 touching the network until bridges are configured, moves forward on
19295 the pluggable transport design, fixes a flaw in the hidden service
19296 design that unnecessarily prevented clients with wrong clocks from
19297 reaching hidden services, and fixes a wide variety of other issues.
19300 - Clients can now connect to private bridges over IPv6. Bridges
19301 still need at least one IPv4 address in order to connect to
19302 other relays. Note that we don't yet handle the case where the
19303 user has two bridge lines for the same bridge (one IPv4, one
19304 IPv6). Implements parts of proposal 186.
19305 - New "DisableNetwork" config option to prevent Tor from launching any
19306 connections or accepting any connections except on a control port.
19307 Bundles and controllers can set this option before letting Tor talk
19308 to the rest of the network, for example to prevent any connections
19309 to a non-bridge address. Packages like Orbot can also use this
19310 option to instruct Tor to save power when the network is off.
19311 - Clients and bridges can now be configured to use a separate
19312 "transport" proxy. This approach makes the censorship arms race
19313 easier by allowing bridges to use protocol obfuscation plugins. It
19314 implements the "managed proxy" part of proposal 180 (ticket 3472).
19315 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
19316 implementation. It makes AES_CTR about 7% faster than our old one
19317 (which was about 10% faster than the one OpenSSL used to provide).
19318 Resolves ticket 4526.
19319 - Add a "tor2web mode" for clients that want to connect to hidden
19320 services non-anonymously (and possibly more quickly). As a safety
19321 measure to try to keep users from turning this on without knowing
19322 what they are doing, tor2web mode must be explicitly enabled at
19323 compile time, and a copy of Tor compiled to run in tor2web mode
19324 cannot be used as a normal Tor client. Implements feature 2553.
19325 - Add experimental support for running on Windows with IOCP and no
19326 kernel-space socket buffers. This feature is controlled by a new
19327 "UserspaceIOCPBuffers" config option (off by default), which has
19328 no effect unless Tor has been built with support for bufferevents,
19329 is running on Windows, and has enabled IOCP. This may, in the long
19330 run, help solve or mitigate bug 98.
19331 - Use a more secure consensus parameter voting algorithm. Now at
19332 least three directory authorities or a majority of them must
19333 vote on a given parameter before it will be included in the
19334 consensus. Implements proposal 178.
19337 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
19338 They used to check that the timestamp was within 30 minutes
19339 of their system clock, so they could cap the size of their
19340 replay-detection cache, but that approach unnecessarily refused
19341 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
19342 the v3 intro-point protocol (the first one which sent a timestamp
19343 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
19344 - Only use the EVP interface when AES acceleration is enabled,
19345 to avoid a 5-7% performance regression. Resolves issue 4525;
19346 bugfix on 0.2.3.8-alpha.
19348 o Privacy/anonymity features (bridge detection):
19349 - Make bridge SSL certificates a bit more stealthy by using random
19350 serial numbers, in the same fashion as OpenSSL when generating
19351 self-signed certificates. Implements ticket 4584.
19352 - Introduce a new config option "DynamicDHGroups", enabled by
19353 default, which provides each bridge with a unique prime DH modulus
19354 to be used during SSL handshakes. This option attempts to help
19355 against censors who might use the Apache DH modulus as a static
19356 identifier for bridges. Addresses ticket 4548.
19358 o Minor features (new/different config options):
19359 - New configuration option "DisableDebuggerAttachment" (on by default)
19360 to prevent basic debugging attachment attempts by other processes.
19361 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
19362 - Allow MapAddress directives to specify matches against super-domains,
19363 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
19364 Implements issue 933.
19365 - Slightly change behavior of "list" options (that is, config
19366 options that can appear more than once) when they appear both in
19367 torrc and on the command line. Previously, the command-line options
19368 would be appended to the ones from torrc. Now, the command-line
19369 options override the torrc options entirely. This new behavior
19370 allows the user to override list options (like exit policies and
19371 ports to listen on) from the command line, rather than simply
19372 appending to the list.
19373 - You can get the old (appending) command-line behavior for "list"
19374 options by prefixing the option name with a "+".
19375 - You can remove all the values for a "list" option from the command
19376 line without adding any new ones by prefixing the option name
19378 - Add experimental support for a "defaults" torrc file to be parsed
19379 before the regular torrc. Torrc options override the defaults file's
19380 options in the same way that the command line overrides the torrc.
19381 The SAVECONF controller command saves only those options which
19382 differ between the current configuration and the defaults file. HUP
19383 reloads both files. (Note: This is an experimental feature; its
19384 behavior will probably be refined in future 0.2.3.x-alpha versions
19385 to better meet packagers' needs.) Implements task 4552.
19388 - Try to make the introductory warning message that Tor prints on
19389 startup more useful for actually finding help and information.
19390 Resolves ticket 2474.
19391 - Running "make version" now displays the version of Tor that
19392 we're about to build. Idea from katmagic; resolves issue 4400.
19393 - Expire old or over-used hidden service introduction points.
19394 Required by fix for bug 3460.
19395 - Move the replay-detection cache for the RSA-encrypted parts of
19396 INTRODUCE2 cells to the introduction point data structures.
19397 Previously, we would use one replay-detection cache per hidden
19398 service. Required by fix for bug 3460.
19399 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
19400 public key replay-detection cache from 60 minutes to 5 minutes. This
19401 replay-detection cache is now used only to detect multiple
19402 INTRODUCE2 cells specifying the same rendezvous point, so we can
19403 avoid launching multiple simultaneous attempts to connect to it.
19405 o Minor bugfixes (on Tor 0.2.2.x and earlier):
19406 - Resolve an integer overflow bug in smartlist_ensure_capacity().
19407 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
19409 - Fix a minor formatting issue in one of tor-gencert's error messages.
19411 - Prevent a false positive from the check-spaces script, by disabling
19412 the "whitespace between function name and (" check for functions
19414 - Fix a log message suggesting that people contact a non-existent
19415 email address. Fixes bug 3448.
19416 - Fix null-pointer access that could occur if TLS allocation failed.
19417 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
19418 - Report a real bootstrap problem to the controller on router
19419 identity mismatch. Previously we just said "foo", which probably
19420 made a lot of sense at the time. Fixes bug 4169; bugfix on
19422 - If we had ever tried to call tor_addr_to_str() on an address of
19423 unknown type, we would have done a strdup() on an uninitialized
19424 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
19425 Reported by "troll_un".
19426 - Correctly detect and handle transient lookup failures from
19427 tor_addr_lookup(). Fixes bug 4530; bugfix on 0.2.1.5-alpha.
19428 Reported by "troll_un".
19429 - Use tor_socket_t type for listener argument to accept(). Fixes bug
19430 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
19431 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
19432 bug 4532; found by "troll_un".
19434 o Minor bugfixes (on Tor 0.2.3.x):
19435 - Fix a compile warning in tor_inet_pton(). Bugfix on 0.2.3.8-alpha;
19437 - Don't send two ESTABLISH_RENDEZVOUS cells when opening a new
19438 circuit for use as a hidden service client's rendezvous point.
19439 Fixes bugs 4641 and 4171; bugfix on 0.2.3.3-alpha. Diagnosed
19440 with help from wanoskarnet.
19441 - Restore behavior of overriding SocksPort, ORPort, and similar
19442 options from the command line. Bugfix on 0.2.3.3-alpha.
19445 - Properly handle the case where the build-tree is not the same
19446 as the source tree when generating src/common/common_sha1.i,
19447 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
19448 bugfix on 0.2.0.1-alpha.
19450 o Code simplifications, cleanups, and refactorings:
19451 - Remove the pure attribute from all functions that used it
19452 previously. In many cases we assigned it incorrectly, because the
19453 functions might assert or call impure functions, and we don't have
19454 evidence that keeping the pure attribute is worthwhile. Implements
19455 changes suggested in ticket 4421.
19456 - Remove some dead code spotted by coverity. Fixes cid 432.
19457 Bugfix on 0.2.3.1-alpha, closes bug 4637.
19460 Changes in version 0.2.3.8-alpha - 2011-11-22
19461 Tor 0.2.3.8-alpha fixes some crash and assert bugs, including a
19462 socketpair-related bug that has been bothering Windows users. It adds
19463 support to serve microdescriptors to controllers, so Vidalia's network
19464 map can resume listing relays (once Vidalia implements its side),
19465 and adds better support for hardware AES acceleration. Finally, it
19466 starts the process of adjusting the bandwidth cutoff for getting the
19467 "Fast" flag from 20KB to (currently) 32KB -- preliminary results show
19468 that tiny relays harm performance more than they help network capacity.
19471 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
19472 that it doesn't attempt to allocate a socketpair. This could cause
19473 some problems on Windows systems with overzealous firewalls. Fix for
19474 bug 4457; workaround for Libevent versions 2.0.1-alpha through
19476 - Correctly sanity-check that we don't underflow on a memory
19477 allocation (and then assert) for hidden service introduction
19478 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
19479 bugfix on 0.2.1.5-alpha.
19480 - Remove the artificially low cutoff of 20KB to guarantee the Fast
19481 flag. In the past few years the average relay speed has picked
19482 up, and while the "top 7/8 of the network get the Fast flag" and
19483 "all relays with 20KB or more of capacity get the Fast flag" rules
19484 used to have the same result, now the top 7/8 of the network has
19485 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
19486 - Fix a rare assertion failure when checking whether a v0 hidden
19487 service descriptor has any usable introduction points left, and
19488 we don't have enough information to build a circuit to the first
19489 intro point named in the descriptor. The HS client code in
19490 0.2.3.x no longer uses v0 HS descriptors, but this assertion can
19491 trigger on (and crash) v0 HS authorities. Fixes bug 4411.
19492 Bugfix on 0.2.3.1-alpha; diagnosed by frosty_un.
19493 - Make bridge authorities not crash when they are asked for their own
19494 descriptor. Bugfix on 0.2.3.7-alpha, reported by Lucky Green.
19495 - When running as a client, do not print a misleading (and plain
19496 wrong) log message that we're collecting "directory request"
19497 statistics: clients don't collect statistics. Also don't create a
19498 useless (because empty) stats file in the stats/ directory. Fixes
19499 bug 4353; bugfix on 0.2.2.34 and 0.2.3.7-alpha.
19502 - Allow Tor controllers like Vidalia to obtain the microdescriptor
19503 for a relay by identity digest or nickname. Previously,
19504 microdescriptors were only available by their own digests, so a
19505 controller would have to ask for and parse the whole microdescriptor
19506 consensus in order to look up a single relay's microdesc. Fixes
19507 bug 3832; bugfix on 0.2.3.1-alpha.
19508 - Use OpenSSL's EVP interface for AES encryption, so that all AES
19509 operations can use hardware acceleration (if present). Resolves
19512 o Minor bugfixes (on 0.2.2.x and earlier):
19513 - Detect failure to initialize Libevent. This fix provides better
19514 detection for future instances of bug 4457.
19515 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
19516 function. This was eating up hideously large amounts of time on some
19517 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
19518 - Don't warn about unused log_mutex in log.c when building with
19519 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
19520 0.1.0.6-rc which introduced --disable-threads.
19521 - Allow manual 'authenticate' commands to the controller interface
19522 from netcat (nc) as well as telnet. We were rejecting them because
19523 they didn't come with the expected whitespace at the end of the
19524 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
19525 - Fix some (not actually triggerable) buffer size checks in usage of
19526 tor_inet_ntop. Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
19528 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
19529 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
19530 - When configuring, starting, or stopping an NT service, stop
19531 immediately after the service configuration attempt has succeeded
19532 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
19533 - When sending a NETINFO cell, include the original address
19534 received for the other side, not its canonical address. Found
19535 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
19536 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
19537 can pick them up when the tests aren't disabled. Bugfix on
19538 0.2.2.4-alpha which introduced tinytest.
19539 - Fix a memory leak when we check whether a hidden service
19540 descriptor has any usable introduction points left. Fixes bug
19541 4424. Bugfix on 0.2.2.25-alpha.
19542 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
19543 occurred when a client tried to fetch a descriptor for a bridge
19544 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
19546 o Minor bugfixes (on 0.2.3.x):
19547 - Make util unit tests build correctly with MSVC. Bugfix on
19548 0.2.3.3-alpha. Patch by Gisle Vanem.
19549 - Successfully detect AUTH_CHALLENGE cells with no recognized
19550 authentication type listed. Fixes bug 4367; bugfix on 0.2.3.6-alpha.
19551 Found by frosty_un.
19552 - If a relay receives an AUTH_CHALLENGE cell it can't answer,
19553 it should still send a NETINFO cell to allow the connection to
19554 become open. Fixes bug 4368; fix on 0.2.3.6-alpha; bug found by
19556 - Log less loudly when we get an invalid authentication certificate
19557 from a source other than a directory authority: it's not unusual
19558 to see invalid certs because of clock skew. Fixes bug 4370; bugfix
19560 - Tolerate servers with more clock skew in their authentication
19561 certificates than previously. Fixes bug 4371; bugfix on
19563 - Fix a couple of compile warnings on Windows. Fixes bug 4469; bugfix
19564 on 0.2.3.4-alpha and 0.2.3.6-alpha.
19567 - Add two new config options for directory authorities:
19568 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
19569 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
19570 that is always sufficient to satisfy the bandwidth requirement for
19571 the Guard flag. Now it will be easier for researchers to simulate
19572 Tor networks with different values. Resolves ticket 4484.
19573 - When Tor ignores a hidden service specified in its configuration,
19574 include the hidden service's directory in the warning message.
19575 Previously, we would only tell the user that some hidden service
19576 was ignored. Bugfix on 0.0.6; fixes bug 4426.
19577 - When we fail to initialize Libevent, retry with IOCP disabled so we
19578 don't need to turn on multi-threading support in Libevent, which in
19579 turn requires a working socketpair(). This is a workaround for bug
19580 4457, which affects Libevent versions from 2.0.1-alpha through
19582 - Detect when we try to build on a platform that doesn't define
19583 AF_UNSPEC to 0. We don't work there, so refuse to compile.
19584 - Update to the November 1 2011 Maxmind GeoLite Country database.
19586 o Packaging changes:
19587 - Make it easier to automate expert package builds on Windows,
19588 by removing an absolute path from makensis.exe command.
19590 o Code simplifications and refactoring:
19591 - Remove some redundant #include directives throughout the code.
19592 Patch from Andrea Gelmini.
19593 - Unconditionally use OpenSSL's AES implementation instead of our
19594 old built-in one. OpenSSL's AES has been better for a while, and
19595 relatively few servers should still be on any version of OpenSSL
19596 that doesn't have good optimized assembly AES.
19597 - Use the name "CERTS" consistently to refer to the new cell type;
19598 we were calling it CERT in some places and CERTS in others.
19601 - Numerous new unit tests for functions in util.c and address.c by
19603 - The long-disabled benchmark tests are now split into their own
19604 ./src/test/bench binary.
19605 - The benchmark tests can now use more accurate timers than
19606 gettimeofday() when such timers are available.
19609 Changes in version 0.2.3.7-alpha - 2011-10-30
19610 Tor 0.2.3.7-alpha fixes a crash bug in 0.2.3.6-alpha introduced by
19611 the new v3 handshake. It also resolves yet another bridge address
19615 - If we mark an OR connection for close based on a cell we process,
19616 don't process any further cells on it. We already avoid further
19617 reads on marked-for-close connections, but now we also discard the
19618 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
19619 which was the first version where we might mark a connection for
19620 close based on processing a cell on it.
19621 - Fix a double-free bug that would occur when we received an invalid
19622 certificate in a CERT cell in the new v3 handshake. Fixes bug 4343;
19623 bugfix on 0.2.3.6-alpha.
19624 - Bridges no longer include their address in NETINFO cells on outgoing
19625 OR connections, to allow them to blend in better with clients.
19626 Removes another avenue for enumerating bridges. Reported by
19627 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
19628 cells were introduced.
19631 - Fixed a typo in a hibernation-related log message. Fixes bug 4331;
19632 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
19635 Changes in version 0.2.3.6-alpha - 2011-10-26
19636 Tor 0.2.3.6-alpha includes the fix from 0.2.2.34 for a critical
19637 anonymity vulnerability where an attacker can deanonymize Tor
19638 users. Everybody should upgrade.
19640 This release also features support for a new v3 connection handshake
19641 protocol, and fixes to make hidden service connections more robust.
19644 - Implement a new handshake protocol (v3) for authenticating Tors to
19645 each other over TLS. It should be more resistant to fingerprinting
19646 than previous protocols, and should require less TLS hacking for
19647 future Tor implementations. Implements proposal 176.
19648 - Allow variable-length padding cells to disguise the length of
19649 Tor's TLS records. Implements part of proposal 184.
19651 o Privacy/anonymity fixes (clients):
19652 - Clients and bridges no longer send TLS certificate chains on
19653 outgoing OR connections. Previously, each client or bridge would
19654 use the same cert chain for all outgoing OR connections until
19655 its IP address changes, which allowed any relay that the client
19656 or bridge contacted to determine which entry guards it is using.
19657 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
19658 - If a relay receives a CREATE_FAST cell on a TLS connection, it
19659 no longer considers that connection as suitable for satisfying a
19660 circuit EXTEND request. Now relays can protect clients from the
19661 CVE-2011-2768 issue even if the clients haven't upgraded yet.
19662 - Directory authorities no longer assign the Guard flag to relays
19663 that haven't upgraded to the above "refuse EXTEND requests
19664 to client connections" fix. Now directory authorities can
19665 protect clients from the CVE-2011-2768 issue even if neither
19666 the clients nor the relays have upgraded yet. There's a new
19667 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
19668 to let us transition smoothly, else tomorrow there would be no
19671 o Major bugfixes (hidden services):
19672 - Improve hidden service robustness: when an attempt to connect to
19673 a hidden service ends, be willing to refetch its hidden service
19674 descriptors from each of the HSDir relays responsible for them
19675 immediately. Previously, we would not consider refetching the
19676 service's descriptors from each HSDir for 15 minutes after the last
19677 fetch, which was inconvenient if the hidden service was not running
19678 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
19679 - When one of a hidden service's introduction points appears to be
19680 unreachable, stop trying it. Previously, we would keep trying
19681 to build circuits to the introduction point until we lost the
19682 descriptor, usually because the user gave up and restarted Tor.
19683 Partly fixes bug 3825.
19684 - Don't launch a useless circuit after failing to use one of a
19685 hidden service's introduction points. Previously, we would
19686 launch a new introduction circuit, but not set the hidden service
19687 which that circuit was intended to connect to, so it would never
19688 actually be used. A different piece of code would then create a
19689 new introduction circuit correctly. Bug reported by katmagic and
19690 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
19692 o Major bugfixes (other):
19693 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
19694 that they initiated. Relays could distinguish incoming bridge
19695 connections from client connections, creating another avenue for
19696 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
19697 Found by "frosty_un".
19698 - Don't update the AccountingSoftLimitHitAt state file entry whenever
19699 tor gets started. This prevents a wrong average bandwidth
19700 estimate, which would cause relays to always start a new accounting
19701 interval at the earliest possible moment. Fixes bug 2003; bugfix
19702 on 0.2.2.7-alpha. Reported by BryonEldridge, who also helped
19703 immensely in tracking this bug down.
19704 - Fix a crash bug when changing node restrictions while a DNS lookup
19705 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
19708 o Minor bugfixes (on 0.2.2.x and earlier):
19709 - When a hidden service turns an extra service-side introduction
19710 circuit into a general-purpose circuit, free the rend_data and
19711 intro_key fields first, so we won't leak memory if the circuit
19712 is cannibalized for use as another service-side introduction
19713 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
19714 - Rephrase the log message emitted if the TestSocks check is
19715 successful. Patch from Fabian Keil; fixes bug 4094.
19716 - Bridges now skip DNS self-tests, to act a little more stealthily.
19717 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
19718 bridges. Patch by "warms0x".
19719 - Remove a confusing dollar sign from the example fingerprint in the
19720 man page, and also make the example fingerprint a valid one. Fixes
19721 bug 4309; bugfix on 0.2.1.3-alpha.
19722 - Fix internal bug-checking logic that was supposed to catch
19723 failures in digest generation so that it will fail more robustly
19724 if we ask for a nonexistent algorithm. Found by Coverity Scan.
19725 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
19726 - Report any failure in init_keys() calls launched because our
19727 IP address has changed. Spotted by Coverity Scan. Bugfix on
19728 0.1.1.4-alpha; fixes CID 484.
19730 o Minor bugfixes (on 0.2.3.x):
19731 - Fix a bug in configure.in that kept it from building a configure
19732 script with autoconf versions earlier than 2.61. Fixes bug 2430;
19733 bugfix on 0.2.3.1-alpha.
19734 - Don't warn users that they are exposing a client port to the
19735 Internet if they have specified an RFC1918 address. Previously,
19736 we would warn if the user had specified any non-loopback
19737 address. Bugfix on 0.2.3.3-alpha. Fixes bug 4018; reported by Tas.
19738 - Fix memory leaks in the failing cases of the new SocksPort and
19739 ControlPort code. Found by Coverity Scan. Bugfix on 0.2.3.3-alpha;
19740 fixes coverity CIDs 485, 486, and 487.
19743 - When a hidden service's introduction point times out, consider
19744 trying it again during the next attempt to connect to the
19745 HS. Previously, we would not try it again unless a newly fetched
19746 descriptor contained it. Required by fixes for bugs 1297 and 3825.
19747 - The next version of Windows will be called Windows 8, and it has
19748 a major version of 6, minor version of 2. Correctly identify that
19749 version instead of calling it "Very recent version". Resolves
19750 ticket 4153; reported by funkstar.
19751 - The Bridge Authority now writes statistics on how many bridge
19752 descriptors it gave out in total, and how many unique descriptors
19753 it gave out. It also lists how often the most and least commonly
19754 fetched descriptors were given out, as well as the median and
19755 25th/75th percentile. Implements tickets 4200 and 4294.
19756 - Update to the October 4 2011 Maxmind GeoLite Country database.
19758 o Code simplifications and refactoring:
19759 - Remove some old code to remember statistics about which descriptors
19760 we've served as a directory mirror. The feature wasn't used and
19761 is outdated now that microdescriptors are around.
19762 - Rename Tor functions that turn strings into addresses, so that
19763 "parse" indicates that no hostname resolution occurs, and
19764 "lookup" indicates that hostname resolution may occur. This
19765 should help prevent mistakes in the future. Fixes bug 3512.
19768 Changes in version 0.2.2.34 - 2011-10-26
19769 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
19770 can deanonymize Tor users. Everybody should upgrade.
19772 The attack relies on four components: 1) Clients reuse their TLS cert
19773 when talking to different relays, so relays can recognize a user by
19774 the identity key in her cert. 2) An attacker who knows the client's
19775 identity key can probe each guard relay to see if that identity key
19776 is connected to that guard relay right now. 3) A variety of active
19777 attacks in the literature (starting from "Low-Cost Traffic Analysis
19778 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
19779 discover the guard relays that a Tor user visiting the website is using.
19780 4) Clients typically pick three guards at random, so the set of guards
19781 for a given user could well be a unique fingerprint for her. This
19782 release fixes components #1 and #2, which is enough to block the attack;
19783 the other two remain as open research problems. Special thanks to
19784 "frosty_un" for reporting the issue to us!
19786 Clients should upgrade so they are no longer recognizable by the TLS
19787 certs they present. Relays should upgrade so they no longer allow a
19788 remote attacker to probe them to test whether unpatched clients are
19789 currently connected to them.
19791 This release also fixes several vulnerabilities that allow an attacker
19792 to enumerate bridge relays. Some bridge enumeration attacks still
19793 remain; see for example proposal 188.
19795 o Privacy/anonymity fixes (clients):
19796 - Clients and bridges no longer send TLS certificate chains on
19797 outgoing OR connections. Previously, each client or bridge would
19798 use the same cert chain for all outgoing OR connections until
19799 its IP address changes, which allowed any relay that the client
19800 or bridge contacted to determine which entry guards it is using.
19801 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
19802 - If a relay receives a CREATE_FAST cell on a TLS connection, it
19803 no longer considers that connection as suitable for satisfying a
19804 circuit EXTEND request. Now relays can protect clients from the
19805 CVE-2011-2768 issue even if the clients haven't upgraded yet.
19806 - Directory authorities no longer assign the Guard flag to relays
19807 that haven't upgraded to the above "refuse EXTEND requests
19808 to client connections" fix. Now directory authorities can
19809 protect clients from the CVE-2011-2768 issue even if neither
19810 the clients nor the relays have upgraded yet. There's a new
19811 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
19812 to let us transition smoothly, else tomorrow there would be no
19815 o Privacy/anonymity fixes (bridge enumeration):
19816 - Bridge relays now do their directory fetches inside Tor TLS
19817 connections, like all the other clients do, rather than connecting
19818 directly to the DirPort like public relays do. Removes another
19819 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
19820 - Bridges relays now build circuits for themselves in a more similar
19821 way to how clients build them. Removes another avenue for
19822 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
19823 when bridges were introduced.
19824 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
19825 that they initiated. Relays could distinguish incoming bridge
19826 connections from client connections, creating another avenue for
19827 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
19828 Found by "frosty_un".
19831 - Fix a crash bug when changing node restrictions while a DNS lookup
19832 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
19834 - Don't launch a useless circuit after failing to use one of a
19835 hidden service's introduction points. Previously, we would
19836 launch a new introduction circuit, but not set the hidden service
19837 which that circuit was intended to connect to, so it would never
19838 actually be used. A different piece of code would then create a
19839 new introduction circuit correctly. Bug reported by katmagic and
19840 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
19843 - Change an integer overflow check in the OpenBSD_Malloc code so
19844 that GCC is less likely to eliminate it as impossible. Patch
19845 from Mansour Moufid. Fixes bug 4059.
19846 - When a hidden service turns an extra service-side introduction
19847 circuit into a general-purpose circuit, free the rend_data and
19848 intro_key fields first, so we won't leak memory if the circuit
19849 is cannibalized for use as another service-side introduction
19850 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
19851 - Bridges now skip DNS self-tests, to act a little more stealthily.
19852 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
19853 bridges. Patch by "warms0x".
19854 - Fix internal bug-checking logic that was supposed to catch
19855 failures in digest generation so that it will fail more robustly
19856 if we ask for a nonexistent algorithm. Found by Coverity Scan.
19857 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
19858 - Report any failure in init_keys() calls launched because our
19859 IP address has changed. Spotted by Coverity Scan. Bugfix on
19860 0.1.1.4-alpha; fixes CID 484.
19862 o Minor bugfixes (log messages and documentation):
19863 - Remove a confusing dollar sign from the example fingerprint in the
19864 man page, and also make the example fingerprint a valid one. Fixes
19865 bug 4309; bugfix on 0.2.1.3-alpha.
19866 - The next version of Windows will be called Windows 8, and it has
19867 a major version of 6, minor version of 2. Correctly identify that
19868 version instead of calling it "Very recent version". Resolves
19869 ticket 4153; reported by funkstar.
19870 - Downgrade log messages about circuit timeout calibration from
19871 "notice" to "info": they don't require or suggest any human
19872 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
19873 bugfix on 0.2.2.14-alpha.
19876 - Turn on directory request statistics by default and include them in
19877 extra-info descriptors. Don't break if we have no GeoIP database.
19878 Backported from 0.2.3.1-alpha; implements ticket 3951.
19879 - Update to the October 4 2011 Maxmind GeoLite Country database.
19882 Changes in version 0.2.1.31 - 2011-10-26
19883 Tor 0.2.1.31 backports important security and privacy fixes for
19884 oldstable. This release is intended only for package maintainers and
19885 others who cannot use the 0.2.2 stable series. All others should be
19886 using Tor 0.2.2.x or newer.
19888 o Security fixes (also included in 0.2.2.x):
19889 - Replace all potentially sensitive memory comparison operations
19890 with versions whose runtime does not depend on the data being
19891 compared. This will help resist a class of attacks where an
19892 adversary can use variations in timing information to learn
19893 sensitive data. Fix for one case of bug 3122. (Safe memcmp
19894 implementation by Robert Ransom based partially on code by DJB.)
19895 - Fix an assert in parsing router descriptors containing IPv6
19896 addresses. This one took down the directory authorities when
19897 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
19899 o Privacy/anonymity fixes (also included in 0.2.2.x):
19900 - Clients and bridges no longer send TLS certificate chains on
19901 outgoing OR connections. Previously, each client or bridge would
19902 use the same cert chain for all outgoing OR connections until
19903 its IP address changes, which allowed any relay that the client
19904 or bridge contacted to determine which entry guards it is using.
19905 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
19906 - If a relay receives a CREATE_FAST cell on a TLS connection, it
19907 no longer considers that connection as suitable for satisfying a
19908 circuit EXTEND request. Now relays can protect clients from the
19909 CVE-2011-2768 issue even if the clients haven't upgraded yet.
19910 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
19911 that they initiated. Relays could distinguish incoming bridge
19912 connections from client connections, creating another avenue for
19913 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
19914 Found by "frosty_un".
19915 - When receiving a hidden service descriptor, check that it is for
19916 the hidden service we wanted. Previously, Tor would store any
19917 hidden service descriptors that a directory gave it, whether it
19918 wanted them or not. This wouldn't have let an attacker impersonate
19919 a hidden service, but it did let directories pre-seed a client
19920 with descriptors that it didn't want. Bugfix on 0.0.6.
19921 - Avoid linkability based on cached hidden service descriptors: forget
19922 all hidden service descriptors cached as a client when processing a
19923 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
19924 - Make the bridge directory authority refuse to answer directory
19925 requests for "all" descriptors. It used to include bridge
19926 descriptors in its answer, which was a major information leak.
19927 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
19928 - Don't attach new streams to old rendezvous circuits after SIGNAL
19929 NEWNYM. Previously, we would keep using an existing rendezvous
19930 circuit if it remained open (i.e. if it were kept open by a
19931 long-lived stream, or if a new stream were attached to it before
19932 Tor could notice that it was old and no longer in use). Bugfix on
19933 0.1.1.15-rc; fixes bug 3375.
19935 o Minor bugfixes (also included in 0.2.2.x):
19936 - When we restart our relay, we might get a successful connection
19937 from the outside before we've started our reachability tests,
19938 triggering a warning: "ORPort found reachable, but I have no
19939 routerinfo yet. Failing to inform controller of success." This
19940 bug was harmless unless Tor is running under a controller
19941 like Vidalia, in which case the controller would never get a
19942 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
19944 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
19945 enabled. Fixes bug 1526.
19946 - Remove undocumented option "-F" from tor-resolve: it hasn't done
19947 anything since 0.2.1.16-rc.
19948 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
19949 None of the cases where we did this before were wrong, but by making
19950 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
19951 - Fix a rare crash bug that could occur when a client was configured
19952 with a large number of bridges. Fixes bug 2629; bugfix on
19953 0.2.1.2-alpha. Bugfix by trac user "shitlei".
19954 - Correct the warning displayed when a rendezvous descriptor exceeds
19955 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
19957 - Fix an uncommon assertion failure when running with DNSPort under
19958 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
19959 - When warning about missing zlib development packages during compile,
19960 give the correct package names. Bugfix on 0.2.0.1-alpha.
19961 - Require that introduction point keys and onion keys have public
19962 exponent 65537. Bugfix on 0.2.0.10-alpha.
19963 - Do not crash when our configuration file becomes unreadable, for
19964 example due to a permissions change, between when we start up
19965 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
19967 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
19969 - Always NUL-terminate the sun_path field of a sockaddr_un before
19970 passing it to the kernel. (Not a security issue: kernels are
19971 smart enough to reject bad sockaddr_uns.) Found by Coverity;
19972 CID #428. Bugfix on Tor 0.2.0.3-alpha.
19973 - Don't stack-allocate the list of supplementary GIDs when we're
19974 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
19975 could take up to 256K, which is way too much stack. Found by
19976 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
19978 o Minor bugfixes (only in 0.2.1.x):
19979 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
19980 rely on them. Bugfix on 0.2.1.30.
19981 - Use git revisions instead of svn revisions when generating our
19982 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
19984 o Minor features (also included in 0.2.2.x):
19985 - Adjust the expiration time on our SSL session certificates to
19986 better match SSL certs seen in the wild. Resolves ticket 4014.
19987 - Allow nameservers with IPv6 address. Resolves bug 2574.
19988 - Update to the October 4 2011 Maxmind GeoLite Country database.
19991 Changes in version 0.2.3.5-alpha - 2011-09-28
19992 Tor 0.2.3.5-alpha fixes two bugs that make it possible to enumerate
19993 bridge relays; fixes an assertion error that many users started hitting
19994 today; and adds the ability to refill token buckets more often than
19995 once per second, allowing significant performance improvements.
19998 - Bridge relays now do their directory fetches inside Tor TLS
19999 connections, like all the other clients do, rather than connecting
20000 directly to the DirPort like public relays do. Removes another
20001 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
20002 - Bridges relays now build circuits for themselves in a more similar
20003 way to how clients build them. Removes another avenue for
20004 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
20005 when bridges were introduced.
20008 - Fix an "Assertion md->held_by_node == 1 failed" error that could
20009 occur when the same microdescriptor was referenced by two node_t
20010 objects at once. Fix for bug 4118; bugfix on Tor 0.2.3.1-alpha.
20012 o Major features (networking):
20013 - Add a new TokenBucketRefillInterval option to refill token buckets
20014 more frequently than once per second. This should improve network
20015 performance, alleviate queueing problems, and make traffic less
20016 bursty. Implements proposal 183; closes ticket 3630. Design by
20017 Florian Tschorsch and Björn Scheuermann; implementation by
20021 - Change an integer overflow check in the OpenBSD_Malloc code so
20022 that GCC is less likely to eliminate it as impossible. Patch
20023 from Mansour Moufid. Fixes bug 4059.
20025 o Minor bugfixes (usability):
20026 - Downgrade log messages about circuit timeout calibration from
20027 "notice" to "info": they don't require or suggest any human
20028 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
20029 bugfix on 0.2.2.14-alpha.
20031 o Minor features (diagnostics):
20032 - When the system call to create a listener socket fails, log the
20033 error message explaining why. This may help diagnose bug 4027.
20036 Changes in version 0.2.3.4-alpha - 2011-09-13
20037 Tor 0.2.3.4-alpha includes the fixes from 0.2.2.33, including a slight
20038 tweak to Tor's TLS handshake that makes relays and bridges that run
20039 this new version reachable from Iran again. It also fixes a few new
20040 bugs in 0.2.3.x, and teaches relays to recognize when they're not
20041 listed in the network consensus and republish.
20043 o Major bugfixes (also part of 0.2.2.33):
20044 - Avoid an assertion failure when reloading a configuration with
20045 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
20046 3923; bugfix on 0.2.2.25-alpha.
20048 o Minor features (security, also part of 0.2.2.33):
20049 - Check for replays of the public-key encrypted portion of an
20050 INTRODUCE1 cell, in addition to the current check for replays of
20051 the g^x value. This prevents a possible class of active attacks
20052 by an attacker who controls both an introduction point and a
20053 rendezvous point, and who uses the malleability of AES-CTR to
20054 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
20055 that these attacks are infeasible (requiring the attacker to send
20056 on the order of zettabytes of altered cells in a short interval),
20057 but we'd rather block them off in case there are any classes of
20058 this attack that we missed. Reported by Willem Pinckaers.
20060 o Minor features (also part of 0.2.2.33):
20061 - Adjust the expiration time on our SSL session certificates to
20062 better match SSL certs seen in the wild. Resolves ticket 4014.
20063 - Change the default required uptime for a relay to be accepted as
20064 a HSDir (hidden service directory) from 24 hours to 25 hours.
20065 Improves on 0.2.0.10-alpha; resolves ticket 2649.
20066 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
20067 authorities to abstain from voting on assignment of the HSDir
20068 consensus flag. Related to bug 2649.
20069 - Update to the September 6 2011 Maxmind GeoLite Country database.
20071 o Minor bugfixes (also part of 0.2.2.33):
20072 - Demote the 'replay detected' log message emitted when a hidden
20073 service receives the same Diffie-Hellman public key in two different
20074 INTRODUCE2 cells to info level. A normal Tor client can cause that
20075 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
20076 fixes part of bug 2442.
20077 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
20078 level. There is nothing that a hidden service's operator can do
20079 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
20081 - Clarify a log message specifying the characters permitted in
20082 HiddenServiceAuthorizeClient client names. Previously, the log
20083 message said that "[A-Za-z0-9+-_]" were permitted; that could have
20084 given the impression that every ASCII character between "+" and "_"
20085 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
20087 o Build fixes (also part of 0.2.2.33):
20088 - Clean up some code issues that prevented Tor from building on older
20089 BSDs. Fixes bug 3894; reported by "grarpamp".
20090 - Search for a platform-specific version of "ar" when cross-compiling.
20091 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
20094 - Fix a bug where the SocksPort option (for example) would get
20095 ignored and replaced by the default if a SocksListenAddress
20096 option was set. Bugfix on 0.2.3.3-alpha; fixes bug 3936. Fix by
20100 - Relays now try regenerating and uploading their descriptor more
20101 frequently if they are not listed in the consensus, or if the
20102 version of their descriptor listed in the consensus is too
20103 old. This fix should prevent situations where a server declines
20104 to re-publish itself because it has done so too recently, even
20105 though the authorities decided not to list its recent-enough
20106 descriptor. Fix for bug 3327.
20109 - Relays now include a reason for regenerating their descriptors
20110 in an HTTP header when uploading to the authorities. This will
20111 make it easier to debug descriptor-upload issues in the future.
20112 - When starting as root and then changing our UID via the User
20113 control option, and we have a ControlSocket configured, make sure
20114 that the ControlSocket is owned by the same account that Tor will
20115 run under. Implements ticket 3421; fix by Jérémy Bobbio.
20118 - Abort if tor_vasprintf fails in connection_printf_to_buf (a
20119 utility function used in the control-port code). This shouldn't
20120 ever happen unless Tor is completely out of memory, but if it did
20121 happen and Tor somehow recovered from it, Tor could have sent a log
20122 message to a control port in the middle of a reply to a controller
20123 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
20124 - Make 'FetchUselessDescriptors' cause all descriptor types and
20125 all consensus types (including microdescriptors) to get fetched.
20126 Fixes bug 3851; bugfix on 0.2.3.1-alpha.
20128 o Code refactoring:
20129 - Make a new "entry connection" struct as an internal subtype of "edge
20130 connection", to simplify the code and make exit connections smaller.
20133 Changes in version 0.2.2.33 - 2011-09-13
20134 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
20135 TLS handshake that makes relays and bridges that run this new version
20136 reachable from Iran again.
20139 - Avoid an assertion failure when reloading a configuration with
20140 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
20141 3923; bugfix on 0.2.2.25-alpha.
20143 o Minor features (security):
20144 - Check for replays of the public-key encrypted portion of an
20145 INTRODUCE1 cell, in addition to the current check for replays of
20146 the g^x value. This prevents a possible class of active attacks
20147 by an attacker who controls both an introduction point and a
20148 rendezvous point, and who uses the malleability of AES-CTR to
20149 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
20150 that these attacks are infeasible (requiring the attacker to send
20151 on the order of zettabytes of altered cells in a short interval),
20152 but we'd rather block them off in case there are any classes of
20153 this attack that we missed. Reported by Willem Pinckaers.
20156 - Adjust the expiration time on our SSL session certificates to
20157 better match SSL certs seen in the wild. Resolves ticket 4014.
20158 - Change the default required uptime for a relay to be accepted as
20159 a HSDir (hidden service directory) from 24 hours to 25 hours.
20160 Improves on 0.2.0.10-alpha; resolves ticket 2649.
20161 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
20162 authorities to abstain from voting on assignment of the HSDir
20163 consensus flag. Related to bug 2649.
20164 - Update to the September 6 2011 Maxmind GeoLite Country database.
20166 o Minor bugfixes (documentation and log messages):
20167 - Correct the man page to explain that HashedControlPassword and
20168 CookieAuthentication can both be set, in which case either method
20169 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
20170 when we decided to allow these config options to both be set. Issue
20171 raised by bug 3898.
20172 - Demote the 'replay detected' log message emitted when a hidden
20173 service receives the same Diffie-Hellman public key in two different
20174 INTRODUCE2 cells to info level. A normal Tor client can cause that
20175 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
20176 fixes part of bug 2442.
20177 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
20178 level. There is nothing that a hidden service's operator can do
20179 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
20181 - Clarify a log message specifying the characters permitted in
20182 HiddenServiceAuthorizeClient client names. Previously, the log
20183 message said that "[A-Za-z0-9+-_]" were permitted; that could have
20184 given the impression that every ASCII character between "+" and "_"
20185 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
20188 - Provide a substitute implementation of lround() for MSVC, which
20189 apparently lacks it. Patch from Gisle Vanem.
20190 - Clean up some code issues that prevented Tor from building on older
20191 BSDs. Fixes bug 3894; reported by "grarpamp".
20192 - Search for a platform-specific version of "ar" when cross-compiling.
20193 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
20196 Changes in version 0.2.3.3-alpha - 2011-09-01
20197 Tor 0.2.3.3-alpha adds a new "stream isolation" feature to improve Tor's
20198 security, and provides client-side support for the microdescriptor
20199 and optimistic data features introduced earlier in the 0.2.3.x
20200 series. It also includes numerous critical bugfixes in the (optional)
20201 bufferevent-based networking backend.
20203 o Major features (stream isolation):
20204 - You can now configure Tor so that streams from different
20205 applications are isolated on different circuits, to prevent an
20206 attacker who sees your streams as they leave an exit node from
20207 linking your sessions to one another. To do this, choose some way
20208 to distinguish the applications: have them connect to different
20209 SocksPorts, or have one of them use SOCKS4 while the other uses
20210 SOCKS5, or have them pass different authentication strings to the
20211 SOCKS proxy. Then, use the new SocksPort syntax to configure the
20212 degree of isolation you need. This implements Proposal 171.
20213 - There's a new syntax for specifying multiple client ports (such as
20214 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
20215 multiple *Port entries with full addr:port syntax on each.
20216 The old *ListenAddress format is still supported, but you can't
20217 mix it with the new *Port syntax.
20219 o Major features (other):
20220 - Enable microdescriptor fetching by default for clients. This allows
20221 clients to download a much smaller amount of directory information.
20222 To disable it (and go back to the old-style consensus and
20223 descriptors), set "UseMicrodescriptors 0" in your torrc file.
20224 - Tor's firewall-helper feature, introduced in 0.2.3.1-alpha (see the
20225 "PortForwarding" config option), now supports Windows.
20226 - When using an exit relay running 0.2.3.x, clients can now
20227 "optimistically" send data before the exit relay reports that
20228 the stream has opened. This saves a round trip when starting
20229 connections where the client speaks first (such as web browsing).
20230 This behavior is controlled by a consensus parameter (currently
20231 disabled). To turn it on or off manually, use the "OptimisticData"
20232 torrc option. Implements proposal 181; code by Ian Goldberg.
20234 o Major bugfixes (bufferevents, fixes on 0.2.3.1-alpha):
20235 - When using IOCP on Windows, we need to enable Libevent windows
20237 - The IOCP backend now works even when the user has not specified
20238 the (internal, debugging-only) _UseFilteringSSLBufferevents option.
20239 Fixes part of bug 3752.
20240 - Correctly record the bytes we've read and written when using
20241 bufferevents, so that we can include them in our bandwidth history
20242 and advertised bandwidth. Fixes bug 3803.
20243 - Apply rate-limiting only at the bottom of a chain of filtering
20244 bufferevents. This prevents us from filling up internal read
20245 buffers and violating rate-limits when filtering bufferevents
20246 are enabled. Fixes part of bug 3804.
20247 - Add high-watermarks to the output buffers for filtered
20248 bufferevents. This prevents us from filling up internal write
20249 buffers and wasting CPU cycles when filtering bufferevents are
20250 enabled. Fixes part of bug 3804.
20251 - Correctly notice when data has been written from a bufferevent
20252 without flushing it completely. Fixes bug 3805.
20253 - Fix a bug where server-side tunneled bufferevent-based directory
20254 streams would get closed prematurely. Fixes bug 3814.
20255 - Fix a use-after-free error with per-connection rate-limiting
20256 buckets. Fixes bug 3888.
20258 o Major bugfixes (also part of 0.2.2.31-rc):
20259 - If we're configured to write our ControlPorts to disk, only write
20260 them after switching UID and creating the data directory. This way,
20261 we don't fail when starting up with a nonexistent DataDirectory
20262 and a ControlPortWriteToFile setting based on that directory. Fixes
20263 bug 3747; bugfix on Tor 0.2.2.26-beta.
20266 - Added a new CONF_CHANGED event so that controllers can be notified
20267 of any configuration changes made by other controllers, or by the
20268 user. Implements ticket 1692.
20269 - Use evbuffer_copyout() in inspect_evbuffer(). This fixes a memory
20270 leak when using bufferevents, and lets Libevent worry about how to
20271 best copy data out of a buffer.
20272 - Replace files in stats/ rather than appending to them. Now that we
20273 include statistics in extra-info descriptors, it makes no sense to
20274 keep old statistics forever. Implements ticket 2930.
20276 o Minor features (build compatibility):
20277 - Limited, experimental support for building with nmake and MSVC.
20278 - Provide a substitute implementation of lround() for MSVC, which
20279 apparently lacks it. Patch from Gisle Vanem.
20281 o Minor features (also part of 0.2.2.31-rc):
20282 - Update to the August 2 2011 Maxmind GeoLite Country database.
20284 o Minor bugfixes (on 0.2.3.x-alpha):
20285 - Fix a spurious warning when parsing SOCKS requests with
20286 bufferevents enabled. Fixes bug 3615; bugfix on 0.2.3.2-alpha.
20287 - Get rid of a harmless warning that could happen on relays running
20288 with bufferevents. The warning was caused by someone doing an http
20289 request to a relay's orport. Also don't warn for a few related
20290 non-errors. Fixes bug 3700; bugfix on 0.2.3.1-alpha.
20292 o Minor bugfixes (on 2.2.x and earlier):
20293 - Correct the man page to explain that HashedControlPassword and
20294 CookieAuthentication can both be set, in which case either method
20295 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
20296 when we decided to allow these config options to both be set. Issue
20297 raised by bug 3898.
20298 - The "--quiet" and "--hush" options now apply not only to Tor's
20299 behavior before logs are configured, but also to Tor's behavior in
20300 the absence of configured logs. Fixes bug 3550; bugfix on
20303 o Minor bugfixes (also part of 0.2.2.31-rc):
20304 - Write several files in text mode, on OSes that distinguish text
20305 mode from binary mode (namely, Windows). These files are:
20306 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
20307 that collect those statistics; 'client_keys' and 'hostname' for
20308 hidden services that use authentication; and (in the tor-gencert
20309 utility) newly generated identity and signing keys. Previously,
20310 we wouldn't specify text mode or binary mode, leading to an
20311 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
20312 the DirRecordUsageByCountry option which would have triggered
20313 the assertion failure was added), although this assertion failure
20314 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
20315 - Selectively disable deprecation warnings on OS X because Lion
20316 started deprecating the shipped copy of openssl. Fixes bug 3643.
20317 - Remove an extra pair of quotation marks around the error
20318 message in control-port STATUS_GENERAL BUG events. Bugfix on
20319 0.1.2.6-alpha; fixes bug 3732.
20320 - When unable to format an address as a string, report its value
20321 as "???" rather than reusing the last formatted address. Bugfix
20324 o Code simplifications and refactoring:
20325 - Rewrite the listener-selection logic so that parsing which ports
20326 we want to listen on is now separate from binding to the ports
20330 - Building Tor with bufferevent support now requires Libevent
20331 2.0.13-stable or later. Previous versions of Libevent had bugs in
20332 SSL-related bufferevents and related issues that would make Tor
20333 work badly with bufferevents. Requiring 2.0.13-stable also allows
20334 Tor with bufferevents to take advantage of Libevent APIs
20335 introduced after 2.0.8-rc.
20338 Changes in version 0.2.2.32 - 2011-08-27
20339 The Tor 0.2.2 release series is dedicated to the memory of Andreas
20340 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
20341 a founder of the PETS community, a leader in our field, a mentor,
20342 and a friend. He left us with these words: "I had the possibility
20343 to contribute to this world that is not as it should be. I hope I
20344 could help in some areas to make the world a better place, and that
20345 I could also encourage other people to be engaged in improving the
20346 world. Please, stay engaged. This world needs you, your love, your
20347 initiative -- now I cannot be part of that anymore."
20349 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
20350 ready. More than two years in the making, this release features improved
20351 client performance and hidden service reliability, better compatibility
20352 for Android, correct behavior for bridges that listen on more than
20353 one address, more extensible and flexible directory object handling,
20354 better reporting of network statistics, improved code security, and
20355 many many other features and bugfixes.
20358 Changes in version 0.2.2.31-rc - 2011-08-17
20359 Tor 0.2.2.31-rc is the second and hopefully final release candidate
20360 for the Tor 0.2.2.x series.
20363 - Remove an extra pair of quotation marks around the error
20364 message in control-port STATUS_GENERAL BUG events. Bugfix on
20365 0.1.2.6-alpha; fixes bug 3732.
20366 - If we're configured to write our ControlPorts to disk, only write
20367 them after switching UID and creating the data directory. This way,
20368 we don't fail when starting up with a nonexistent DataDirectory
20369 and a ControlPortWriteToFile setting based on that directory. Fixes
20370 bug 3747; bugfix on Tor 0.2.2.26-beta.
20373 - Update to the August 2 2011 Maxmind GeoLite Country database.
20376 - Allow GETINFO fingerprint to return a fingerprint even when
20377 we have not yet built a router descriptor. Fixes bug 3577;
20378 bugfix on 0.2.0.1-alpha.
20379 - Write several files in text mode, on OSes that distinguish text
20380 mode from binary mode (namely, Windows). These files are:
20381 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
20382 that collect those statistics; 'client_keys' and 'hostname' for
20383 hidden services that use authentication; and (in the tor-gencert
20384 utility) newly generated identity and signing keys. Previously,
20385 we wouldn't specify text mode or binary mode, leading to an
20386 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
20387 the DirRecordUsageByCountry option which would have triggered
20388 the assertion failure was added), although this assertion failure
20389 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
20390 - Selectively disable deprecation warnings on OS X because Lion
20391 started deprecating the shipped copy of openssl. Fixes bug 3643.
20392 - When unable to format an address as a string, report its value
20393 as "???" rather than reusing the last formatted address. Bugfix
20397 Changes in version 0.2.3.2-alpha - 2011-07-18
20398 Tor 0.2.3.2-alpha introduces two new experimental features:
20399 microdescriptors and pluggable transports. It also continues cleaning
20400 up a variety of recently introduced features.
20403 - Clients can now use microdescriptors instead of regular descriptors
20404 to build circuits. Microdescriptors are authority-generated
20405 summaries of regular descriptors' contents, designed to change
20406 very rarely (see proposal 158 for details). This feature is
20407 designed to save bandwidth, especially for clients on slow internet
20408 connections. It's off by default for now, since nearly no caches
20409 support it, but it will be on-by-default for clients in a future
20410 version. You can use the UseMicrodescriptors option to turn it on.
20411 - Tor clients using bridges can now be configured to use a separate
20412 'transport' proxy for each bridge. This approach helps to resist
20413 censorship by allowing bridges to use protocol obfuscation
20414 plugins. It implements part of proposal 180. Implements ticket 2841.
20415 - While we're trying to bootstrap, record how many TLS connections
20416 fail in each state, and report which states saw the most failures
20417 in response to any bootstrap failures. This feature may speed up
20418 diagnosis of censorship events. Implements ticket 3116.
20420 o Major bugfixes (on 0.2.3.1-alpha):
20421 - When configuring a large set of nodes in EntryNodes (as with
20422 'EntryNodes {cc}' or 'EntryNodes 1.1.1.1/16'), choose only a
20423 random subset to be guards, and choose them in random
20424 order. Fixes bug 2798.
20425 - Tor could crash when remembering a consensus in a non-used consensus
20426 flavor without having a current consensus set. Fixes bug 3361.
20427 - Comparing an unknown address to a microdescriptor's shortened exit
20428 policy would always give a "rejected" result. Fixes bug 3599.
20429 - Using microdescriptors as a client no longer prevents Tor from
20430 uploading and downloading hidden service descriptors. Fixes
20434 - Allow nameservers with IPv6 address. Resolves bug 2574.
20435 - Accept attempts to include a password authenticator in the
20436 handshake, as supported by SOCKS5. This handles SOCKS clients that
20437 don't know how to omit a password when authenticating. Resolves
20439 - When configuring a large set of nodes in EntryNodes, and there are
20440 enough of them listed as Guard so that we don't need to consider
20441 the non-guard entries, prefer the ones listed with the Guard flag.
20442 - Check for and recover from inconsistency in the microdescriptor
20443 cache. This will make it harder for us to accidentally free a
20444 microdescriptor without removing it from the appropriate data
20445 structures. Fixes issue 3135; issue noted by "wanoskarnet".
20446 - Log SSL state transitions at log level DEBUG, log domain
20447 HANDSHAKE. This can be useful for debugging censorship events.
20448 Implements ticket 3264.
20449 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
20450 implements ticket 3439.
20452 o Minor bugfixes (on 0.2.3.1-alpha):
20453 - Do not free all general-purpose regular descriptors just
20454 because microdescriptor use is enabled. Fixes bug 3113.
20455 - Correctly link libevent_openssl when --enable-static-libevent
20456 is passed to configure. Fixes bug 3118.
20457 - Bridges should not complain during their heartbeat log messages that
20458 they are unlisted in the consensus: that's more or less the point
20459 of being a bridge. Fixes bug 3183.
20460 - Report a SIGNAL event to controllers when acting on a delayed
20461 SIGNAL NEWNYM command. Previously, we would report a SIGNAL
20462 event to the controller if we acted on a SIGNAL NEWNYM command
20463 immediately, and otherwise not report a SIGNAL event for the
20464 command at all. Fixes bug 3349.
20465 - Fix a crash when handling the SIGNAL controller command or
20466 reporting ERR-level status events with bufferevents enabled. Found
20467 by Robert Ransom. Fixes bug 3367.
20468 - Always ship the tor-fw-helper manpage in our release tarballs.
20469 Fixes bug 3389. Reported by Stephen Walker.
20470 - Fix a class of double-mark-for-close bugs when bufferevents
20471 are enabled. Fixes bug 3403.
20472 - Update tor-fw-helper to support libnatpmp-20110618. Fixes bug 3434.
20473 - Add SIGNAL to the list returned by the 'GETINFO events/names'
20474 control-port command. Fixes part of bug 3465.
20475 - Prevent using negative indices during unit test runs when read_all()
20476 fails. Spotted by coverity.
20477 - Fix a rare memory leak when checking the nodelist without it being
20478 present. Found by coverity.
20479 - Only try to download a microdescriptor-flavored consensus from
20480 a directory cache that provides them.
20482 o Minor bugfixes (on 0.2.2.x and earlier):
20483 - Assert that hidden-service-related operations are not performed
20484 using single-hop circuits. Previously, Tor would assert that
20485 client-side streams are not attached to single-hop circuits,
20486 but not that other sensitive operations on the client and service
20487 side are not performed using single-hop circuits. Fixes bug 3332;
20489 - Don't publish a new relay descriptor when we reload our onion key,
20490 unless the onion key has actually changed. Fixes bug 3263 and
20491 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
20492 - Allow GETINFO fingerprint to return a fingerprint even when
20493 we have not yet built a router descriptor. Fixes bug 3577;
20494 bugfix on 0.2.0.1-alpha.
20495 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
20496 on 0.2.2.4-alpha; fixes bug 3427.
20498 o Code simplification and refactoring:
20499 - Use tor_sscanf() in place of scanf() in more places through the
20500 code. This makes us a little more locale-independent, and
20501 should help shut up code-analysis tools that can't tell
20502 a safe sscanf string from a dangerous one.
20503 - Use tt_assert(), not tor_assert(), for checking for test failures.
20504 This makes the unit tests more able to go on in the event that
20506 - Split connection_about_to_close() into separate functions for each
20510 - On Windows, we now define the _WIN32_WINNT macros only if they
20511 are not already defined. This lets the person building Tor decide,
20512 if they want, to require a later version of Windows.
20515 Changes in version 0.2.2.30-rc - 2011-07-07
20516 Tor 0.2.2.30-rc is the first release candidate for the Tor 0.2.2.x
20517 series. It fixes a few smaller bugs, but generally appears stable.
20518 Please test it and let us know whether it is!
20521 - Send a SUCCEEDED stream event to the controller when a reverse
20522 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
20523 discovered by katmagic.
20524 - Always NUL-terminate the sun_path field of a sockaddr_un before
20525 passing it to the kernel. (Not a security issue: kernels are
20526 smart enough to reject bad sockaddr_uns.) Found by Coverity;
20527 CID #428. Bugfix on Tor 0.2.0.3-alpha.
20528 - Don't stack-allocate the list of supplementary GIDs when we're
20529 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
20530 could take up to 256K, which is way too much stack. Found by
20531 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
20532 - Add BUILDTIMEOUT_SET to the list returned by the 'GETINFO
20533 events/names' control-port command. Bugfix on 0.2.2.9-alpha;
20534 fixes part of bug 3465.
20535 - Fix a memory leak when receiving a descriptor for a hidden
20536 service we didn't ask for. Found by Coverity; CID #30. Bugfix
20540 - Update to the July 1 2011 Maxmind GeoLite Country database.
20543 Changes in version 0.2.2.29-beta - 2011-06-20
20544 Tor 0.2.2.29-beta reverts an accidental behavior change for users who
20545 have bridge lines in their torrc but don't want to use them; gets
20546 us closer to having the control socket feature working on Debian;
20547 and fixes a variety of smaller bugs.
20550 - Revert the UseBridges option to its behavior before 0.2.2.28-beta.
20551 When we changed the default behavior to "use bridges if any
20552 are listed in the torrc", we surprised users who had bridges
20553 in their torrc files but who didn't actually want to use them.
20554 Partial resolution for bug 3354.
20557 - Don't attach new streams to old rendezvous circuits after SIGNAL
20558 NEWNYM. Previously, we would keep using an existing rendezvous
20559 circuit if it remained open (i.e. if it were kept open by a
20560 long-lived stream, or if a new stream were attached to it before
20561 Tor could notice that it was old and no longer in use). Bugfix on
20562 0.1.1.15-rc; fixes bug 3375.
20565 - Fix a bug when using ControlSocketsGroupWritable with User. The
20566 directory's group would be checked against the current group, not
20567 the configured group. Patch by Jérémy Bobbio. Fixes bug 3393;
20568 bugfix on 0.2.2.26-beta.
20569 - Make connection_printf_to_buf()'s behavior sane. Its callers
20570 expect it to emit a CRLF iff the format string ends with CRLF;
20571 it actually emitted a CRLF iff (a) the format string ended with
20572 CRLF or (b) the resulting string was over 1023 characters long or
20573 (c) the format string did not end with CRLF *and* the resulting
20574 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
20575 fixes part of bug 3407.
20576 - Make send_control_event_impl()'s behavior sane. Its callers
20577 expect it to always emit a CRLF at the end of the string; it
20578 might have emitted extra control characters as well. Bugfix on
20579 0.1.1.9-alpha; fixes another part of bug 3407.
20580 - Make crypto_rand_int() check the value of its input correctly.
20581 Previously, it accepted values up to UINT_MAX, but could return a
20582 negative number if given a value above INT_MAX+1. Found by George
20583 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
20584 - Avoid a segfault when reading a malformed circuit build state
20585 with more than INT_MAX entries. Found by wanoskarnet. Bugfix on
20587 - When asked about a DNS record type we don't support via a
20588 client DNSPort, reply with NOTIMPL rather than an empty
20589 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
20590 - Fix a rare memory leak during stats writing. Found by coverity.
20593 - Update to the June 1 2011 Maxmind GeoLite Country database.
20595 o Code simplifications and refactoring:
20596 - Remove some dead code as indicated by coverity.
20597 - Remove a few dead assignments during router parsing. Found by
20599 - Add some forgotten return value checks during unit tests. Found
20601 - Don't use 1-bit wide signed bit fields. Found by coverity.
20604 Changes in version 0.2.2.28-beta - 2011-06-04
20605 Tor 0.2.2.28-beta makes great progress towards a new stable release: we
20606 fixed a big bug in whether relays stay in the consensus consistently,
20607 we moved closer to handling bridges and hidden services correctly,
20608 and we started the process of better handling the dreaded "my Vidalia
20609 died, and now my Tor demands a password when I try to reconnect to it"
20613 - Don't decide to make a new descriptor when receiving a HUP signal.
20614 This bug has caused a lot of 0.2.2.x relays to disappear from the
20615 consensus periodically. Fixes the most common case of triggering
20616 bug 1810; bugfix on 0.2.2.7-alpha.
20617 - Actually allow nameservers with IPv6 addresses. Fixes bug 2574.
20618 - Don't try to build descriptors if "ORPort auto" is set and we
20619 don't know our actual ORPort yet. Fix for bug 3216; bugfix on
20621 - Resolve a crash that occurred when setting BridgeRelay to 1 with
20622 accounting enabled. Fixes bug 3228; bugfix on 0.2.2.18-alpha.
20623 - Apply circuit timeouts to opened hidden-service-related circuits
20624 based on the correct start time. Previously, we would apply the
20625 circuit build timeout based on time since the circuit's creation;
20626 it was supposed to be applied based on time since the circuit
20627 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
20628 - Use the same circuit timeout for client-side introduction
20629 circuits as for other four-hop circuits, rather than the timeout
20630 for single-hop directory-fetch circuits; the shorter timeout may
20631 have been appropriate with the static circuit build timeout in
20632 0.2.1.x and earlier, but caused many hidden service access attempts
20633 to fail with the adaptive CBT introduced in 0.2.2.2-alpha. Bugfix
20634 on 0.2.2.2-alpha; fixes another part of bug 1297.
20635 - In ticket 2511 we fixed a case where you could use an unconfigured
20636 bridge if you had configured it as a bridge the last time you ran
20637 Tor. Now fix another edge case: if you had configured it as a bridge
20638 but then switched to a different bridge via the controller, you
20639 would still be willing to use the old one. Bugfix on 0.2.0.1-alpha;
20643 - Add an __OwningControllerProcess configuration option and a
20644 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
20645 that when it exits, Tor will shut down. Implements feature 3049.
20646 - If "UseBridges 1" is set and no bridges are configured, Tor will
20647 now refuse to build any circuits until some bridges are set.
20648 If "UseBridges auto" is set, Tor will use bridges if they are
20649 configured and we are not running as a server, but otherwise will
20650 make circuits as usual. The new default is "auto". Patch by anonym,
20651 so the Tails LiveCD can stop automatically revealing you as a Tor
20655 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
20656 - Remove a trailing asterisk from "exit-policy/default" in the
20657 output of the control port command "GETINFO info/names". Bugfix
20659 - Use a wide type to hold sockets when built for 64-bit Windows builds.
20661 - Warn when the user configures two HiddenServiceDir lines that point
20662 to the same directory. Bugfix on 0.0.6 (the version introducing
20663 HiddenServiceDir); fixes bug 3289.
20664 - Remove dead code from rend_cache_lookup_v2_desc_as_dir. Fixes
20665 part of bug 2748; bugfix on 0.2.0.10-alpha.
20666 - Log malformed requests for rendezvous descriptors as protocol
20667 warnings, not warnings. Also, use a more informative log message
20668 in case someone sees it at log level warning without prior
20669 info-level messages. Fixes the other part of bug 2748; bugfix
20671 - Clear the table recording the time of the last request for each
20672 hidden service descriptor from each HS directory on SIGNAL NEWNYM.
20673 Previously, we would clear our HS descriptor cache on SIGNAL
20674 NEWNYM, but if we had previously retrieved a descriptor (or tried
20675 to) from every directory responsible for it, we would refuse to
20676 fetch it again for up to 15 minutes. Bugfix on 0.2.2.25-alpha;
20678 - Fix a log message that said "bits" while displaying a value in
20679 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
20681 - When checking for 1024-bit keys, check for 1024 bits, not 128
20682 bytes. This allows Tor to correctly discard keys of length 1017
20683 through 1023. Bugfix on 0.0.9pre5.
20686 - Relays now log the reason for publishing a new relay descriptor,
20687 so we have a better chance of hunting down instances of bug 1810.
20688 Resolves ticket 3252.
20689 - Revise most log messages that refer to nodes by nickname to
20690 instead use the "$key=nickname at address" format. This should be
20691 more useful, especially since nicknames are less and less likely
20692 to be unique. Resolves ticket 3045.
20693 - Log (at info level) when purging pieces of hidden-service-client
20694 state because of SIGNAL NEWNYM.
20697 - Remove undocumented option "-F" from tor-resolve: it hasn't done
20698 anything since 0.2.1.16-rc.
20701 Changes in version 0.2.2.27-beta - 2011-05-18
20702 Tor 0.2.2.27-beta fixes a bridge-related stability bug in the previous
20703 release, and also adds a few more general bugfixes.
20706 - Fix a crash bug when changing bridges in a running Tor process.
20707 Fixes bug 3213; bugfix on 0.2.2.26-beta.
20708 - When the controller configures a new bridge, don't wait 10 to 60
20709 seconds before trying to fetch its descriptor. Bugfix on
20710 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
20713 - Require that onion keys have exponent 65537 in microdescriptors too.
20714 Fixes more of bug 3207; bugfix on 0.2.2.26-beta.
20715 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
20716 Changed the limit to 512 characters by removing base64 newlines.
20717 Fixes bug 2752. Fix by Michael Yakubovich.
20718 - When a client starts or stops using bridges, never use a circuit
20719 that was built before the configuration change. This behavior could
20720 put at risk a user who uses bridges to ensure that her traffic
20721 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
20725 Changes in version 0.2.2.26-beta - 2011-05-17
20726 Tor 0.2.2.26-beta fixes a variety of potential privacy problems. It
20727 also introduces a new "socksport auto" approach that should make it
20728 easier to run multiple Tors on the same system, and does a lot of
20729 cleanup to get us closer to a release candidate.
20731 o Security/privacy fixes:
20732 - Replace all potentially sensitive memory comparison operations
20733 with versions whose runtime does not depend on the data being
20734 compared. This will help resist a class of attacks where an
20735 adversary can use variations in timing information to learn
20736 sensitive data. Fix for one case of bug 3122. (Safe memcmp
20737 implementation by Robert Ransom based partially on code by DJB.)
20738 - When receiving a hidden service descriptor, check that it is for
20739 the hidden service we wanted. Previously, Tor would store any
20740 hidden service descriptors that a directory gave it, whether it
20741 wanted them or not. This wouldn't have let an attacker impersonate
20742 a hidden service, but it did let directories pre-seed a client
20743 with descriptors that it didn't want. Bugfix on 0.0.6.
20744 - On SIGHUP, do not clear out all TrackHostExits mappings, client
20745 DNS cache entries, and virtual address mappings: that's what
20746 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
20749 - The options SocksPort, ControlPort, and so on now all accept a
20750 value "auto" that opens a socket on an OS-selected port. A
20751 new ControlPortWriteToFile option tells Tor to write its
20752 actual control port or ports to a chosen file. If the option
20753 ControlPortFileGroupReadable is set, the file is created as
20754 group-readable. Now users can run two Tor clients on the same
20755 system without needing to manually mess with parameters. Resolves
20756 part of ticket 3076.
20757 - Set SO_REUSEADDR on all sockets, not just listeners. This should
20758 help busy exit nodes avoid running out of useable ports just
20759 because all the ports have been used in the near past. Resolves
20763 - New "GETINFO net/listeners/(type)" controller command to return
20764 a list of addresses and ports that are bound for listeners for a
20765 given connection type. This is useful when the user has configured
20766 "SocksPort auto" and the controller needs to know which port got
20767 chosen. Resolves another part of ticket 3076.
20768 - Add a new ControlSocketsGroupWritable configuration option: when
20769 it is turned on, ControlSockets are group-writeable by the default
20770 group of the current user. Patch by Jérémy Bobbio; implements
20772 - Tor now refuses to create a ControlSocket in a directory that is
20773 world-readable (or group-readable if ControlSocketsGroupWritable
20774 is 0). This is necessary because some operating systems do not
20775 enforce permissions on an AF_UNIX sockets. Permissions on the
20776 directory holding the socket, however, seems to work everywhere.
20777 - Rate-limit a warning about failures to download v2 networkstatus
20778 documents. Resolves part of bug 1352.
20779 - Backport code from 0.2.3.x that allows directory authorities to
20780 clean their microdescriptor caches. Needed to resolve bug 2230.
20781 - When an HTTPS proxy reports "403 Forbidden", we now explain
20782 what it means rather than calling it an unexpected status code.
20783 Closes bug 2503. Patch from Michael Yakubovich.
20784 - Update to the May 1 2011 Maxmind GeoLite Country database.
20787 - Authorities now clean their microdesc cache periodically and when
20788 reading from disk initially, not only when adding new descriptors.
20789 This prevents a bug where we could lose microdescriptors. Bugfix
20790 on 0.2.2.6-alpha. Fixes bug 2230.
20791 - Do not crash when our configuration file becomes unreadable, for
20792 example due to a permissions change, between when we start up
20793 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
20795 - Avoid a bug that would keep us from replacing a microdescriptor
20796 cache on Windows. (We would try to replace the file while still
20797 holding it open. That's fine on Unix, but Windows doesn't let us
20798 do that.) Bugfix on 0.2.2.6-alpha; bug found by wanoskarnet.
20799 - Add missing explanations for the authority-related torrc options
20800 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey in the
20801 man page. Resolves issue 2379.
20802 - As an authority, do not upload our own vote or signature set to
20803 ourself. It would tell us nothing new, and as of 0.2.2.24-alpha,
20804 it would get flagged as a duplicate. Resolves bug 3026.
20805 - Accept hidden service descriptors if we think we might be a hidden
20806 service directory, regardless of what our consensus says. This
20807 helps robustness, since clients and hidden services can sometimes
20808 have a more up-to-date view of the network consensus than we do,
20809 and if they think that the directory authorities list us a HSDir,
20810 we might actually be one. Related to bug 2732; bugfix on
20812 - When a controller changes TrackHostExits, remove mappings for
20813 hosts that should no longer have their exits tracked. Bugfix on
20815 - When a controller changes VirtualAddrNetwork, remove any mappings
20816 for hosts that were automapped to the old network. Bugfix on
20818 - When a controller changes one of the AutomapHosts* options, remove
20819 any mappings for hosts that should no longer be automapped. Bugfix
20821 - Do not reset the bridge descriptor download status every time we
20822 re-parse our configuration or get a configuration change. Fixes
20823 bug 3019; bugfix on 0.2.0.3-alpha.
20825 o Minor bugfixes (code cleanup):
20826 - When loading the microdesc journal, remember its current size.
20827 In 0.2.2, this helps prevent the microdesc journal from growing
20828 without limit on authorities (who are the only ones to use it in
20829 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
20830 Fix posted by "cypherpunks."
20831 - The microdesc journal is supposed to get rebuilt only if it is
20832 at least _half_ the length of the store, not _twice_ the length
20833 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
20834 - Fix a potential null-pointer dereference while computing a
20835 consensus. Bugfix on 0.2.0.3-alpha, found with the help of
20837 - Avoid a possible null-pointer dereference when rebuilding the mdesc
20838 cache without actually having any descriptors to cache. Bugfix on
20839 0.2.2.6-alpha. Issue discovered using clang's static analyzer.
20840 - If we fail to compute the identity digest of a v3 legacy keypair,
20841 warn, and don't use a buffer-full of junk instead. Bugfix on
20842 0.2.1.1-alpha; fixes bug 3106.
20843 - Resolve an untriggerable issue in smartlist_string_num_isin(),
20844 where if the function had ever in the future been used to check
20845 for the presence of a too-large number, it would have given an
20846 incorrect result. (Fortunately, we only used it for 16-bit
20847 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
20848 - Require that introduction point keys and onion handshake keys
20849 have a public exponent of 65537. Starts to fix bug 3207; bugfix
20852 o Removed features:
20853 - Caches no longer download and serve v2 networkstatus documents
20854 unless FetchV2Networkstatus flag is set: these documents haven't
20855 haven't been used by clients or relays since 0.2.0.x. Resolves
20859 Changes in version 0.2.3.1-alpha - 2011-05-05
20860 Tor 0.2.3.1-alpha adds some new experimental features, including support
20861 for an improved network IO backend, IOCP networking on Windows,
20862 microdescriptor caching, "fast-start" support for streams, and automatic
20863 home router configuration. There are also numerous internal improvements
20864 to try to make the code easier for developers to work with.
20866 This is the first alpha release in a new series, so expect there to be
20867 bugs. Users who would rather test out a more stable branch should
20868 stay with 0.2.2.x for now.
20871 - Tor can now optionally build with the "bufferevents" buffered IO
20872 backend provided by Libevent 2. To use this feature, make sure you
20873 have the latest possible version of Libevent, and pass the
20874 --enable-bufferevents flag to configure when building Tor from
20875 source. This feature will make our networking code more flexible,
20876 let us stack layers on each other, and let us use more efficient
20877 zero-copy transports where available.
20878 - As an experimental feature, Tor can use IOCP for networking on Windows.
20879 Once this code is tuned and optimized, it promises much better
20880 performance than the select-based backend we've used in the past. To
20881 try this feature, you must build Tor with Libevent 2, configure Tor
20882 with the "bufferevents" buffered IO backend, and add "DisableIOCP 0" to
20883 your torrc. There are known bugs here: only try this if you can help
20884 debug it as it breaks.
20885 - The EntryNodes option can now include country codes like {de} or IP
20886 addresses or network masks. Previously we had disallowed these options
20887 because we didn't have an efficient way to keep the list up to
20888 date. Fixes bug 1982, but see bug 2798 for an unresolved issue here.
20889 - Exit nodes now accept and queue data on not-yet-connected streams.
20890 Previously, the client wasn't allowed to send data until the stream was
20891 connected, which slowed down all connections. This change will enable
20892 clients to perform a "fast-start" on streams and send data without
20893 having to wait for a confirmation that the stream has opened. (Patch
20894 from Ian Goldberg; implements the server side of Proposal 174.)
20895 - Tor now has initial support for automatic port mapping on the many
20896 home routers that support NAT-PMP or UPnP. (Not yet supported on
20897 Windows). To build the support code, you'll need to have libnatpnp
20898 library and/or the libminiupnpc library, and you'll need to enable the
20899 feature specifically by passing "--enable-upnp" and/or
20900 "--enable-natpnp" to configure. To turn it on, use the new
20901 PortForwarding option.
20902 - Caches now download, cache, and serve multiple "flavors" of the
20903 consensus, including a flavor that describes microdescriptors.
20904 - Caches now download, cache, and serve microdescriptors -- small
20905 summaries of router descriptors that are authenticated by all of the
20906 directory authorities. Once enough caches are running this code,
20907 clients will be able to save significant amounts of directory bandwidth
20908 by downloading microdescriptors instead of router descriptors.
20911 - Make logging resolution configurable with a new LogTimeGranularity
20912 option, and change the default from 1 millisecond to 1 second.
20913 Implements enhancement 1668.
20914 - We log which torrc file we're using on startup. Implements ticket
20916 - Ordinarily, Tor does not count traffic from private addresses (like
20917 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
20918 There is now a new option, CountPrivateBandwidth, to disable this
20919 behavior. Patch from Daniel Cagara.
20920 - New --enable-static-tor configure option for building Tor as
20921 statically as possible. Idea, general hackery and thoughts from
20922 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
20924 - If you set the NumCPUs option to 0, Tor will now try to detect how
20925 many CPUs you have. This is the new default behavior.
20926 - Turn on directory request statistics by default and include them in
20927 extra-info descriptors. Don't break if we have no GeoIP database.
20928 - Relays that set "ConnDirectionStatistics 1" write statistics on the
20929 bidirectional use of connections to disk every 24 hours.
20930 - Add a GeoIP file digest to the extra-info descriptor. Implements
20932 - The NodeFamily option -- which let you declare that you want to
20933 consider nodes to be part of a family whether they list themselves
20934 that way or not -- now allows IP address ranges and country codes.
20935 - Add a new 'Heartbeat' log message type to periodically log a message
20936 describing Tor's status at level Notice. This feature is meant for
20937 operators who log at notice, and want to make sure that their Tor
20938 server is still working. Implementation by George Kadianakis.
20940 o Minor bugfixes (on 0.2.2.25-alpha):
20941 - When loading the microdesc journal, remember its current size.
20942 In 0.2.2, this helps prevent the microdesc journal from growing
20943 without limit on authorities (who are the only ones to use it in
20944 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
20945 Fix posted by "cypherpunks."
20946 - The microdesc journal is supposed to get rebuilt only if it is
20947 at least _half_ the length of the store, not _twice_ the length
20948 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
20949 - If as an authority we fail to compute the identity digest of a v3
20950 legacy keypair, warn, and don't use a buffer-full of junk instead.
20951 Bugfix on 0.2.1.1-alpha; fixes bug 3106.
20952 - Authorities now clean their microdesc cache periodically and when
20953 reading from disk initially, not only when adding new descriptors.
20954 This prevents a bug where we could lose microdescriptors. Bugfix
20957 o Minor features (controller):
20958 - Add a new SIGNAL event to the controller interface so that
20959 controllers can be notified when Tor handles a signal. Resolves
20960 issue 1955. Patch by John Brooks.
20961 - Add a new GETINFO option to get total bytes read and written. Patch
20962 from pipe, revised by atagar. Resolves ticket 2345.
20963 - Implement some GETINFO controller fields to provide information about
20964 the Tor process's pid, euid, username, and resource limits.
20967 - Our build system requires automake 1.6 or later to create the
20968 Makefile.in files. Previously, you could have used 1.4.
20969 This only affects developers and people building Tor from git;
20970 people who build Tor from the source distribution without changing
20971 the Makefile.am files should be fine.
20972 - Our autogen.sh script uses autoreconf to launch autoconf, automake, and
20973 so on. This is more robust against some of the failure modes
20974 associated with running the autotools pieces on their own.
20976 o Minor packaging issues:
20977 - On OpenSUSE, create the /var/run/tor directory on startup if it is not
20978 already created. Patch from Andreas Stieger. Fixes bug 2573.
20980 o Code simplifications and refactoring:
20981 - A major revision to our internal node-selecting and listing logic.
20982 Tor already had at least two major ways to look at the question of
20983 "which Tor servers do we know about": a list of router descriptors,
20984 and a list of entries in the current consensus. With
20985 microdescriptors, we're adding a third. Having so many systems
20986 without an abstraction layer over them was hurting the codebase.
20987 Now, we have a new "node_t" abstraction that presents a consistent
20988 interface to a client's view of a Tor node, and holds (nearly) all
20989 of the mutable state formerly in routerinfo_t and routerstatus_t.
20990 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
20991 no longer link against Libevent: they never used it, but
20992 our library structure used to force them to link it.
20994 o Removed features:
20995 - Remove some old code to work around even older versions of Tor that
20996 used forked processes to handle DNS requests. Such versions of Tor
20997 are no longer in use as servers.
20999 o Documentation fixes:
21000 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
21001 - Add missing documentation for the authority-related torrc options
21002 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey. Resolves
21006 Changes in version 0.2.2.25-alpha - 2011-04-29
21007 Tor 0.2.2.25-alpha fixes many bugs: hidden service clients are more
21008 robust, routers no longer overreport their bandwidth, Win7 should crash
21009 a little less, and NEWNYM (as used by Vidalia's "new identity" button)
21010 now prevents hidden service-related activity from being linkable. It
21011 provides more information to Vidalia so you can see if your bridge is
21012 working. Also, 0.2.2.25-alpha revamps the Entry/Exit/ExcludeNodes and
21013 StrictNodes configuration options to make them more reliable, more
21014 understandable, and more regularly applied. If you use those options,
21015 please see the revised documentation for them in the manual page.
21018 - Relays were publishing grossly inflated bandwidth values because
21019 they were writing their state files wrong--now they write the
21020 correct value. Also, resume reading bandwidth history from the
21021 state file correctly. Fixes bug 2704; bugfix on 0.2.2.23-alpha.
21022 - Improve hidden service robustness: When we find that we have
21023 extended a hidden service's introduction circuit to a relay not
21024 listed as an introduction point in the HS descriptor we currently
21025 have, retry with an introduction point from the current
21026 descriptor. Previously we would just give up. Fixes bugs 1024 and
21027 1930; bugfix on 0.2.0.10-alpha.
21028 - Clients now stop trying to use an exit node associated with a given
21029 destination by TrackHostExits if they fail to reach that exit node.
21030 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
21031 - Fix crash bug on platforms where gmtime and localtime can return
21032 NULL. Windows 7 users were running into this one. Fixes part of bug
21033 2077. Bugfix on all versions of Tor. Found by boboper.
21035 o Security and stability fixes:
21036 - Don't double-free a parsable, but invalid, microdescriptor, even if
21037 it is followed in the blob we're parsing by an unparsable
21038 microdescriptor. Fixes an issue reported in a comment on bug 2954.
21039 Bugfix on 0.2.2.6-alpha; fix by "cypherpunks".
21040 - If the Nickname configuration option isn't given, Tor would pick a
21041 nickname based on the local hostname as the nickname for a relay.
21042 Because nicknames are not very important in today's Tor and the
21043 "Unnamed" nickname has been implemented, this is now problematic
21044 behavior: It leaks information about the hostname without being
21045 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
21046 introduced the Unnamed nickname. Reported by tagnaq.
21047 - Fix an uncommon assertion failure when running with DNSPort under
21048 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
21049 - Avoid linkability based on cached hidden service descriptors: forget
21050 all hidden service descriptors cached as a client when processing a
21051 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
21054 - Export GeoIP information on bridge usage to controllers even if we
21055 have not yet been running for 24 hours. Now Vidalia bridge operators
21056 can get more accurate and immediate feedback about their
21057 contributions to the network.
21059 o Major features and bugfixes (node selection):
21060 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
21061 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and StrictNodes
21062 options. Previously, we had been ambiguous in describing what
21063 counted as an "exit" node, and what operations exactly "StrictNodes
21064 0" would permit. This created confusion when people saw nodes built
21065 through unexpected circuits, and made it hard to tell real bugs from
21066 surprises. Now the intended behavior is:
21067 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
21068 a node that delivers user traffic outside the Tor network.
21069 . "Entry", in the context of EntryNodes, means a node used as the
21070 first hop of a multihop circuit. It doesn't include direct
21071 connections to directory servers.
21072 . "ExcludeNodes" applies to all nodes.
21073 . "StrictNodes" changes the behavior of ExcludeNodes only. When
21074 StrictNodes is set, Tor should avoid all nodes listed in
21075 ExcludeNodes, even when it will make user requests fail. When
21076 StrictNodes is *not* set, then Tor should follow ExcludeNodes
21077 whenever it can, except when it must use an excluded node to
21078 perform self-tests, connect to a hidden service, provide a
21079 hidden service, fulfill a .exit request, upload directory
21080 information, or fetch directory information.
21081 Collectively, the changes to implement the behavior fix bug 1090.
21082 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
21083 a node is listed in both, it's treated as excluded.
21084 - ExcludeNodes now applies to directory nodes -- as a preference if
21085 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
21086 Don't exclude all the directory authorities and set StrictNodes to 1
21087 unless you really want your Tor to break.
21088 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
21089 - ExcludeExitNodes now overrides .exit requests.
21090 - We don't use bridges listed in ExcludeNodes.
21091 - When StrictNodes is 1:
21092 . We now apply ExcludeNodes to hidden service introduction points
21093 and to rendezvous points selected by hidden service users. This
21094 can make your hidden service less reliable: use it with caution!
21095 . If we have used ExcludeNodes on ourself, do not try relay
21096 reachability self-tests.
21097 . If we have excluded all the directory authorities, we will not
21098 even try to upload our descriptor if we're a relay.
21099 . Do not honor .exit requests to an excluded node.
21100 - Remove a misfeature that caused us to ignore the Fast/Stable flags
21101 when ExitNodes is set. Bugfix on 0.2.2.7-alpha.
21102 - When the set of permitted nodes changes, we now remove any mappings
21103 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
21105 - We never cannibalize a circuit that had excluded nodes on it, even
21106 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
21107 - Revert a change where we would be laxer about attaching streams to
21108 circuits than when building the circuits. This was meant to prevent
21109 a set of bugs where streams were never attachable, but our improved
21110 code here should make this unnecessary. Bugfix on 0.2.2.7-alpha.
21111 - Keep track of how many times we launch a new circuit to handle a
21112 given stream. Too many launches could indicate an inconsistency
21113 between our "launch a circuit to handle this stream" logic and our
21114 "attach this stream to one of the available circuits" logic.
21115 - Improve log messages related to excluded nodes.
21118 - Fix a spurious warning when moving from a short month to a long
21119 month on relays with month-based BandwidthAccounting. Bugfix on
21120 0.2.2.17-alpha; fixes bug 3020.
21121 - When a client finds that an origin circuit has run out of 16-bit
21122 stream IDs, we now mark it as unusable for new streams. Previously,
21123 we would try to close the entire circuit. Bugfix on 0.0.6.
21124 - Add a forgotten cast that caused a compile warning on OS X 10.6.
21125 Bugfix on 0.2.2.24-alpha.
21126 - Be more careful about reporting the correct error from a failed
21127 connect() system call. Under some circumstances, it was possible to
21128 look at an incorrect value for errno when sending the end reason.
21129 Bugfix on 0.1.0.1-rc.
21130 - Correctly handle an "impossible" overflow cases in connection byte
21131 counting, where we write or read more than 4GB on an edge connection
21132 in a single second. Bugfix on 0.1.2.8-beta.
21133 - Correct the warning displayed when a rendezvous descriptor exceeds
21134 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
21136 - Clients and hidden services now use HSDir-flagged relays for hidden
21137 service descriptor downloads and uploads even if the relays have no
21138 DirPort set and the client has disabled TunnelDirConns. This will
21139 eventually allow us to give the HSDir flag to relays with no
21140 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
21141 - Downgrade "no current certificates known for authority" message from
21142 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
21143 - Make the SIGNAL DUMP control-port command work on FreeBSD. Fixes bug
21144 2917. Bugfix on 0.1.1.1-alpha.
21145 - Only limit the lengths of single HS descriptors, even when multiple
21146 HS descriptors are published to an HSDir relay in a single POST
21147 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
21148 - Write the current time into the LastWritten line in our state file,
21149 rather than the time from the previous write attempt. Also, stop
21150 trying to use a time of -1 in our log statements. Fixes bug 3039;
21151 bugfix on 0.2.2.14-alpha.
21152 - Be more consistent in our treatment of file system paths. "~" should
21153 get expanded to the user's home directory in the Log config option.
21154 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
21155 feature for the -f and --DataDirectory options.
21158 - Make sure every relay writes a state file at least every 12 hours.
21159 Previously, a relay could go for weeks without writing its state
21160 file, and on a crash could lose its bandwidth history, capacity
21161 estimates, client country statistics, and so on. Addresses bug 3012.
21162 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
21163 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
21164 clients are already deprecated because of security bugs.
21165 - Don't allow v0 hidden service authorities to act as clients.
21166 Required by fix for bug 3000.
21167 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
21168 by fix for bug 3000.
21169 - Ensure that no empty [dirreq-](read|write)-history lines are added
21170 to an extrainfo document. Implements ticket 2497.
21172 o Code simplification and refactoring:
21173 - Remove workaround code to handle directory responses from servers
21174 that had bug 539 (they would send HTTP status 503 responses _and_
21175 send a body too). Since only server versions before
21176 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
21177 keep the workaround in place.
21178 - Remove the old 'fuzzy time' logic. It was supposed to be used for
21179 handling calculations where we have a known amount of clock skew and
21180 an allowed amount of unknown skew. But we only used it in three
21181 places, and we never adjusted the known/unknown skew values. This is
21182 still something we might want to do someday, but if we do, we'll
21183 want to do it differently.
21184 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
21185 None of the cases where we did this before were wrong, but by making
21186 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
21187 - Use GetTempDir to find the proper temporary directory location on
21188 Windows when generating temporary files for the unit tests. Patch by
21192 Changes in version 0.2.2.24-alpha - 2011-04-08
21193 Tor 0.2.2.24-alpha fixes a variety of bugs, including a big bug that
21194 prevented Tor clients from effectively using "multihomed" bridges,
21195 that is, bridges that listen on multiple ports or IP addresses so users
21196 can continue to use some of their addresses even if others get blocked.
21199 - Fix a bug where bridge users who configure the non-canonical
21200 address of a bridge automatically switch to its canonical
21201 address. If a bridge listens at more than one address, it should be
21202 able to advertise those addresses independently and any non-blocked
21203 addresses should continue to work. Bugfix on Tor 0.2.0.x. Fixes
21205 - If you configured Tor to use bridge A, and then quit and
21206 configured Tor to use bridge B instead, it would happily continue
21207 to use bridge A if it's still reachable. While this behavior is
21208 a feature if your goal is connectivity, in some scenarios it's a
21209 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
21210 - Directory authorities now use data collected from their own
21211 uptime observations when choosing whether to assign the HSDir flag
21212 to relays, instead of trusting the uptime value the relay reports in
21213 its descriptor. This change helps prevent an attack where a small
21214 set of nodes with frequently-changing identity keys can blackhole
21215 a hidden service. (Only authorities need upgrade; others will be
21216 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
21219 - When we restart our relay, we might get a successful connection
21220 from the outside before we've started our reachability tests,
21221 triggering a warning: "ORPort found reachable, but I have no
21222 routerinfo yet. Failing to inform controller of success." This
21223 bug was harmless unless Tor is running under a controller
21224 like Vidalia, in which case the controller would never get a
21225 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
21227 - Make directory authorities more accurate at recording when
21228 relays that have failed several reachability tests became
21229 unreachable, so we can provide more accuracy at assigning Stable,
21230 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
21231 - Fix an issue that prevented static linking of libevent on
21232 some platforms (notably Linux). Fixes bug 2698; bugfix on
21233 versions 0.2.1.23/0.2.2.8-alpha (the versions introducing
21234 the --with-static-libevent configure option).
21235 - We now ask the other side of a stream (the client or the exit)
21236 for more data on that stream when the amount of queued data on
21237 that stream dips low enough. Previously, we wouldn't ask the
21238 other side for more data until either it sent us more data (which
21239 it wasn't supposed to do if it had exhausted its window!) or we
21240 had completely flushed all our queued data. This flow control fix
21241 should improve throughput. Fixes bug 2756; bugfix on the earliest
21242 released versions of Tor (svn commit r152).
21243 - Avoid a double-mark-for-free warning when failing to attach a
21244 transparent proxy connection. (We thought we had fixed this in
21245 0.2.2.23-alpha, but it turns out our fix was checking the wrong
21246 connection.) Fixes bug 2757; bugfix on 0.1.2.1-alpha (the original
21247 bug) and 0.2.2.23-alpha (the incorrect fix).
21248 - When warning about missing zlib development packages during compile,
21249 give the correct package names. Bugfix on 0.2.0.1-alpha.
21252 - Directory authorities now log the source of a rejected POSTed v3
21253 networkstatus vote.
21254 - Make compilation with clang possible when using
21255 --enable-gcc-warnings by removing two warning options that clang
21256 hasn't implemented yet and by fixing a few warnings. Implements
21258 - When expiring circuits, use microsecond timers rather than
21259 one-second timers. This can avoid an unpleasant situation where a
21260 circuit is launched near the end of one second and expired right
21261 near the beginning of the next, and prevent fluctuations in circuit
21263 - Use computed circuit-build timeouts to decide when to launch
21264 parallel introduction circuits for hidden services. (Previously,
21265 we would retry after 15 seconds.)
21266 - Update to the April 1 2011 Maxmind GeoLite Country database.
21269 - Create the /var/run/tor directory on startup on OpenSUSE if it is
21270 not already created. Patch from Andreas Stieger. Fixes bug 2573.
21272 o Documentation changes:
21273 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
21274 - Resolve all doxygen warnings except those for missing documentation.
21276 - Add doxygen documentation for more functions, fields, and types.
21279 Changes in version 0.2.2.23-alpha - 2011-03-08
21280 Tor 0.2.2.23-alpha lets relays record their bandwidth history so when
21281 they restart they don't lose their bandwidth capacity estimate. This
21282 release also fixes a diverse set of user-facing bugs, ranging from
21283 relays overrunning their rate limiting to clients falsely warning about
21284 clock skew to bridge descriptor leaks by our bridge directory authority.
21287 - Stop sending a CLOCK_SKEW controller status event whenever
21288 we fetch directory information from a relay that has a wrong clock.
21289 Instead, only inform the controller when it's a trusted authority
21290 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
21291 the rest of bug 1074.
21292 - Fix an assert in parsing router descriptors containing IPv6
21293 addresses. This one took down the directory authorities when
21294 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
21295 - Make the bridge directory authority refuse to answer directory
21296 requests for "all" descriptors. It used to include bridge
21297 descriptors in its answer, which was a major information leak.
21298 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
21299 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
21300 Tor would ignore their RelayBandwidthBurst setting,
21301 potentially using more bandwidth than expected. Bugfix on
21302 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
21303 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
21304 hidserv" in her torrc. The 'hidserv' argument never controlled
21305 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
21308 - Relays now save observed peak bandwidth throughput rates to their
21309 state file (along with total usage, which was already saved)
21310 so that they can determine their correct estimated bandwidth on
21311 restart. Resolves bug 1863, where Tor relays would reset their
21312 estimated bandwidth to 0 after restarting.
21313 - Directory authorities now take changes in router IP address and
21314 ORPort into account when determining router stability. Previously,
21315 if a router changed its IP or ORPort, the authorities would not
21316 treat it as having any downtime for the purposes of stability
21317 calculation, whereas clients would experience downtime since the
21318 change could take a while to propagate to them. Resolves issue 1035.
21319 - Enable Address Space Layout Randomization (ASLR) and Data Execution
21320 Prevention (DEP) by default on Windows to make it harder for
21321 attackers to exploit vulnerabilities. Patch from John Brooks.
21323 o Minor bugfixes (on 0.2.1.x and earlier):
21324 - Fix a rare crash bug that could occur when a client was configured
21325 with a large number of bridges. Fixes bug 2629; bugfix on
21326 0.2.1.2-alpha. Bugfix by trac user "shitlei".
21327 - Avoid a double mark-for-free warning when failing to attach a
21328 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
21330 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
21331 found by "cypherpunks". This bug was introduced before the first
21332 Tor release, in svn commit r110.
21333 - Country codes aren't supported in EntryNodes until 0.2.3.x, so
21334 don't mention them in the manpage. Fixes bug 2450; issue
21335 spotted by keb and G-Lo.
21336 - Fix a bug in bandwidth history state parsing that could have been
21337 triggered if a future version of Tor ever changed the timing
21338 granularity at which bandwidth history is measured. Bugfix on
21339 Tor 0.1.1.11-alpha.
21340 - When a relay decides that its DNS is too broken for it to serve
21341 as an exit server, it advertised itself as a non-exit, but
21342 continued to act as an exit. This could create accidental
21343 partitioning opportunities for users. Instead, if a relay is
21344 going to advertise reject *:* as its exit policy, it should
21345 really act with exit policy "reject *:*". Fixes bug 2366.
21346 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
21347 - In the special case where you configure a public exit relay as your
21348 bridge, Tor would be willing to use that exit relay as the last
21349 hop in your circuit as well. Now we fail that circuit instead.
21350 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
21351 - Fix a bug with our locking implementation on Windows that couldn't
21352 correctly detect when a file was already locked. Fixes bug 2504,
21353 bugfix on 0.2.1.6-alpha.
21354 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
21355 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
21357 - Set target port in get_interface_address6() correctly. Bugfix
21358 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
21359 - Directory authorities are now more robust to hops back in time
21360 when calculating router stability. Previously, if a run of uptime
21361 or downtime appeared to be negative, the calculation could give
21362 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
21364 - Fix an assert that got triggered when using the TestingTorNetwork
21365 configuration option and then issuing a GETINFO config-text control
21366 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
21368 o Minor bugfixes (on 0.2.2.x):
21369 - Clients should not weight BadExit nodes as Exits in their node
21370 selection. Similarly, directory authorities should not count BadExit
21371 bandwidth as Exit bandwidth when computing bandwidth-weights.
21372 Bugfix on 0.2.2.10-alpha; fixes bug 2203.
21373 - Correctly clear our dir_read/dir_write history when there is an
21374 error parsing any bw history value from the state file. Bugfix on
21375 Tor 0.2.2.15-alpha.
21376 - Resolve a bug in verifying signatures of directory objects
21377 with digests longer than SHA1. Bugfix on 0.2.2.20-alpha.
21378 Fixes bug 2409. Found by "piebeer".
21379 - Bridge authorities no longer crash on SIGHUP when they try to
21380 publish their relay descriptor to themselves. Fixes bug 2572. Bugfix
21384 - Log less aggressively about circuit timeout changes, and improve
21385 some other circuit timeout messages. Resolves bug 2004.
21386 - Log a little more clearly about the times at which we're no longer
21387 accepting new connections. Resolves bug 2181.
21388 - Reject attempts at the client side to open connections to private
21389 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
21390 a randomly chosen exit node. Attempts to do so are always
21391 ill-defined, generally prevented by exit policies, and usually
21392 in error. This will also help to detect loops in transparent
21393 proxy configurations. You can disable this feature by setting
21394 "ClientRejectInternalAddresses 0" in your torrc.
21395 - Always treat failure to allocate an RSA key as an unrecoverable
21397 - Update to the March 1 2011 Maxmind GeoLite Country database.
21399 o Minor features (log subsystem):
21400 - Add documentation for configuring logging at different severities in
21401 different log domains. We've had this feature since 0.2.1.1-alpha,
21402 but for some reason it never made it into the manpage. Fixes
21404 - Make it simpler to specify "All log domains except for A and B".
21405 Previously you needed to say "[*,~A,~B]". Now you can just say
21407 - Add a "LogMessageDomains 1" option to include the domains of log
21408 messages along with the messages. Without this, there's no way
21409 to use log domains without reading the source or doing a lot
21412 o Packaging changes:
21413 - Stop shipping the Tor specs files and development proposal documents
21414 in the tarball. They are now in a separate git repository at
21415 git://git.torproject.org/torspec.git
21418 Changes in version 0.2.1.30 - 2011-02-23
21419 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
21420 change is a slight tweak to Tor's TLS handshake that makes relays
21421 and bridges that run this new version reachable from Iran again.
21422 We don't expect this tweak will win the arms race long-term, but it
21423 buys us time until we roll out a better solution.
21426 - Stop sending a CLOCK_SKEW controller status event whenever
21427 we fetch directory information from a relay that has a wrong clock.
21428 Instead, only inform the controller when it's a trusted authority
21429 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
21430 the rest of bug 1074.
21431 - Fix a bounds-checking error that could allow an attacker to
21432 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
21433 Found by "piebeer".
21434 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
21435 Tor would ignore their RelayBandwidthBurst setting,
21436 potentially using more bandwidth than expected. Bugfix on
21437 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
21438 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
21439 hidserv" in her torrc. The 'hidserv' argument never controlled
21440 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
21443 - Adjust our TLS Diffie-Hellman parameters to match those used by
21445 - Update to the February 1 2011 Maxmind GeoLite Country database.
21448 - Check for and reject overly long directory certificates and
21449 directory tokens before they have a chance to hit any assertions.
21450 Bugfix on 0.2.1.28. Found by "doorss".
21451 - Bring the logic that gathers routerinfos and assesses the
21452 acceptability of circuits into line. This prevents a Tor OP from
21453 getting locked in a cycle of choosing its local OR as an exit for a
21454 path (due to a .exit request) and then rejecting the circuit because
21455 its OR is not listed yet. It also prevents Tor clients from using an
21456 OR running in the same instance as an exit (due to a .exit request)
21457 if the OR does not meet the same requirements expected of an OR
21458 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
21460 o Packaging changes:
21461 - Stop shipping the Tor specs files and development proposal documents
21462 in the tarball. They are now in a separate git repository at
21463 git://git.torproject.org/torspec.git
21464 - Do not include Git version tags as though they are SVN tags when
21465 generating a tarball from inside a repository that has switched
21466 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
21469 Changes in version 0.2.2.22-alpha - 2011-01-25
21470 Tor 0.2.2.22-alpha fixes a few more less-critical security issues. The
21471 main other change is a slight tweak to Tor's TLS handshake that makes
21472 relays and bridges that run this new version reachable from Iran again.
21473 We don't expect this tweak will win the arms race long-term, but it
21474 will buy us a bit more time until we roll out a better solution.
21477 - Fix a bounds-checking error that could allow an attacker to
21478 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
21479 Found by "piebeer".
21480 - Don't assert when changing from bridge to relay or vice versa
21481 via the controller. The assert happened because we didn't properly
21482 initialize our keys in this case. Bugfix on 0.2.2.18-alpha; fixes
21483 bug 2433. Reported by bastik.
21486 - Adjust our TLS Diffie-Hellman parameters to match those used by
21488 - Provide a log message stating which geoip file we're parsing
21489 instead of just stating that we're parsing the geoip file.
21490 Implements ticket 2432.
21493 - Check for and reject overly long directory certificates and
21494 directory tokens before they have a chance to hit any assertions.
21495 Bugfix on 0.2.1.28 / 0.2.2.20-alpha. Found by "doorss".
21498 Changes in version 0.2.2.21-alpha - 2011-01-15
21499 Tor 0.2.2.21-alpha includes all the patches from Tor 0.2.1.29, which
21500 continues our recent code security audit work. The main fix resolves
21501 a remote heap overflow vulnerability that can allow remote code
21502 execution (CVE-2011-0427). Other fixes address a variety of assert
21503 and crash bugs, most of which we think are hard to exploit remotely.
21505 o Major bugfixes (security), also included in 0.2.1.29:
21506 - Fix a heap overflow bug where an adversary could cause heap
21507 corruption. This bug probably allows remote code execution
21508 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
21510 - Prevent a denial-of-service attack by disallowing any
21511 zlib-compressed data whose compression factor is implausibly
21512 high. Fixes part of bug 2324; reported by "doorss".
21513 - Zero out a few more keys in memory before freeing them. Fixes
21514 bug 2384 and part of bug 2385. These key instances found by
21515 "cypherpunks", based on Andrew Case's report about being able
21516 to find sensitive data in Tor's memory space if you have enough
21517 permissions. Bugfix on 0.0.2pre9.
21519 o Major bugfixes (crashes), also included in 0.2.1.29:
21520 - Prevent calls to Libevent from inside Libevent log handlers.
21521 This had potential to cause a nasty set of crashes, especially
21522 if running Libevent with debug logging enabled, and running
21523 Tor with a controller watching for low-severity log messages.
21524 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
21525 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
21526 underflow errors there too. Fixes the other part of bug 2324.
21527 - Fix a bug where we would assert if we ever had a
21528 cached-descriptors.new file (or another file read directly into
21529 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
21530 on 0.2.1.25. Found by doorss.
21531 - Fix some potential asserts and parsing issues with grossly
21532 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
21535 o Minor bugfixes (other), also included in 0.2.1.29:
21536 - Fix a bug with handling misformed replies to reverse DNS lookup
21537 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
21538 bug reported by doorss.
21539 - Fix compilation on mingw when a pthreads compatibility library
21540 has been installed. (We don't want to use it, so we shouldn't
21541 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
21542 - Fix a bug where we would declare that we had run out of virtual
21543 addresses when the address space was only half-exhausted. Bugfix
21545 - Correctly handle the case where AutomapHostsOnResolve is set but
21546 no virtual addresses are available. Fixes bug 2328; bugfix on
21547 0.1.2.1-alpha. Bug found by doorss.
21548 - Correctly handle wrapping around when we run out of virtual
21549 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
21551 o Minor features, also included in 0.2.1.29:
21552 - Update to the January 1 2011 Maxmind GeoLite Country database.
21553 - Introduce output size checks on all of our decryption functions.
21555 o Build changes, also included in 0.2.1.29:
21556 - Tor does not build packages correctly with Automake 1.6 and earlier;
21557 added a check to Makefile.am to make sure that we're building with
21558 Automake 1.7 or later.
21559 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
21560 because we built it with a too-old version of automake. Thus that
21561 release broke ./configure --enable-openbsd-malloc, which is popular
21562 among really fast exit relays on Linux.
21564 o Major bugfixes, new in 0.2.2.21-alpha:
21565 - Prevent crash/heap corruption when the cbtnummodes consensus
21566 parameter is set to 0 or large values. Fixes bug 2317; bugfix
21569 o Major features, new in 0.2.2.21-alpha:
21570 - Introduce minimum/maximum values that clients will believe
21571 from the consensus. Now we'll have a better chance to avoid crashes
21572 or worse when a consensus param has a weird value.
21574 o Minor features, new in 0.2.2.21-alpha:
21575 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
21576 used on bridges, and it makes bridge scanning somewhat easier.
21577 - If writing the state file to disk fails, wait up to an hour before
21578 retrying again, rather than trying again each second. Fixes bug
21579 2346; bugfix on Tor 0.1.1.3-alpha.
21580 - Make Libevent log messages get delivered to controllers later,
21581 and not from inside the Libevent log handler. This prevents unsafe
21582 reentrant Libevent calls while still letting the log messages
21584 - Detect platforms that brokenly use a signed size_t, and refuse to
21585 build there. Found and analyzed by doorss and rransom.
21586 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
21589 o Minor bugfixes, new in 0.2.2.21-alpha:
21590 - Handle SOCKS messages longer than 128 bytes long correctly, rather
21591 than waiting forever for them to finish. Fixes bug 2330; bugfix
21592 on 0.2.0.16-alpha. Found by doorss.
21593 - Add assertions to check for overflow in arguments to
21594 base32_encode() and base32_decode(); fix a signed-unsigned
21595 comparison there too. These bugs are not actually reachable in Tor,
21596 but it's good to prevent future errors too. Found by doorss.
21597 - Correctly detect failures to create DNS requests when using Libevent
21598 versions before v2. (Before Libevent 2, we used our own evdns
21599 implementation. Its return values for Libevent's evdns_resolve_*()
21600 functions are not consistent with those from Libevent.) Fixes bug
21601 2363; bugfix on 0.2.2.6-alpha. Found by "lodger".
21603 o Documentation, new in 0.2.2.21-alpha:
21604 - Document the default socks host and port (127.0.0.1:9050) for
21608 Changes in version 0.2.1.29 - 2011-01-15
21609 Tor 0.2.1.29 continues our recent code security audit work. The main
21610 fix resolves a remote heap overflow vulnerability that can allow remote
21611 code execution. Other fixes address a variety of assert and crash bugs,
21612 most of which we think are hard to exploit remotely.
21614 o Major bugfixes (security):
21615 - Fix a heap overflow bug where an adversary could cause heap
21616 corruption. This bug probably allows remote code execution
21617 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
21619 - Prevent a denial-of-service attack by disallowing any
21620 zlib-compressed data whose compression factor is implausibly
21621 high. Fixes part of bug 2324; reported by "doorss".
21622 - Zero out a few more keys in memory before freeing them. Fixes
21623 bug 2384 and part of bug 2385. These key instances found by
21624 "cypherpunks", based on Andrew Case's report about being able
21625 to find sensitive data in Tor's memory space if you have enough
21626 permissions. Bugfix on 0.0.2pre9.
21628 o Major bugfixes (crashes):
21629 - Prevent calls to Libevent from inside Libevent log handlers.
21630 This had potential to cause a nasty set of crashes, especially
21631 if running Libevent with debug logging enabled, and running
21632 Tor with a controller watching for low-severity log messages.
21633 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
21634 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
21635 underflow errors there too. Fixes the other part of bug 2324.
21636 - Fix a bug where we would assert if we ever had a
21637 cached-descriptors.new file (or another file read directly into
21638 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
21639 on 0.2.1.25. Found by doorss.
21640 - Fix some potential asserts and parsing issues with grossly
21641 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
21644 o Minor bugfixes (other):
21645 - Fix a bug with handling misformed replies to reverse DNS lookup
21646 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
21647 bug reported by doorss.
21648 - Fix compilation on mingw when a pthreads compatibility library
21649 has been installed. (We don't want to use it, so we shouldn't
21650 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
21651 - Fix a bug where we would declare that we had run out of virtual
21652 addresses when the address space was only half-exhausted. Bugfix
21654 - Correctly handle the case where AutomapHostsOnResolve is set but
21655 no virtual addresses are available. Fixes bug 2328; bugfix on
21656 0.1.2.1-alpha. Bug found by doorss.
21657 - Correctly handle wrapping around to when we run out of virtual
21658 address space. Found by cypherpunks, bugfix on 0.2.0.5-alpha.
21659 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
21660 because we built it with a too-old version of automake. Thus that
21661 release broke ./configure --enable-openbsd-malloc, which is popular
21662 among really fast exit relays on Linux.
21665 - Update to the January 1 2011 Maxmind GeoLite Country database.
21666 - Introduce output size checks on all of our decryption functions.
21669 - Tor does not build packages correctly with Automake 1.6 and earlier;
21670 added a check to Makefile.am to make sure that we're building with
21671 Automake 1.7 or later.
21674 Changes in version 0.2.2.20-alpha - 2010-12-17
21675 Tor 0.2.2.20-alpha does some code cleanup to reduce the risk of remotely
21676 exploitable bugs. We also fix a variety of other significant bugs,
21677 change the IP address for one of our directory authorities, and update
21678 the minimum version that Tor relays must run to join the network.
21681 - Fix a remotely exploitable bug that could be used to crash instances
21682 of Tor remotely by overflowing on the heap. Remote-code execution
21683 hasn't been confirmed, but can't be ruled out. Everyone should
21684 upgrade. Bugfix on the 0.1.1 series and later.
21685 - Fix a bug that could break accounting on 64-bit systems with large
21686 time_t values, making them hibernate for impossibly long intervals.
21687 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
21688 - Fix a logic error in directory_fetches_from_authorities() that
21689 would cause all _non_-exits refusing single-hop-like circuits
21690 to fetch from authorities, when we wanted to have _exits_ fetch
21691 from authorities. Fixes more of 2097. Bugfix on 0.2.2.16-alpha;
21693 - Fix a stream fairness bug that would cause newer streams on a given
21694 circuit to get preference when reading bytes from the origin or
21695 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
21696 introduced before the first Tor release, in svn revision r152.
21698 o Directory authority changes:
21699 - Change IP address and ports for gabelmoo (v3 directory authority).
21702 - Avoid crashes when AccountingMax is set on clients. Fixes bug 2235.
21703 Bugfix on 0.2.2.18-alpha. Diagnosed by boboper.
21704 - Fix an off-by-one error in calculating some controller command
21705 argument lengths. Fortunately, this mistake is harmless since
21706 the controller code does redundant NUL termination too. Found by
21707 boboper. Bugfix on 0.1.1.1-alpha.
21708 - Do not dereference NULL if a bridge fails to build its
21709 extra-info descriptor. Found by an anonymous commenter on
21710 Trac. Bugfix on 0.2.2.19-alpha.
21713 - Update to the December 1 2010 Maxmind GeoLite Country database.
21714 - Directory authorities now reject relays running any versions of
21715 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
21716 known bugs that keep RELAY_EARLY cells from working on rendezvous
21717 circuits. Followup to fix for bug 2081.
21718 - Directory authorities now reject relays running any version of Tor
21719 older than 0.2.0.26-rc. That version is the earliest that fetches
21720 current directory information correctly. Fixes bug 2156.
21721 - Report only the top 10 ports in exit-port stats in order not to
21722 exceed the maximum extra-info descriptor length of 50 KB. Implements
21726 Changes in version 0.2.1.28 - 2010-12-17
21727 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
21728 exploitable bugs. We also took this opportunity to change the IP address
21729 for one of our directory authorities, and to update the geoip database
21733 - Fix a remotely exploitable bug that could be used to crash instances
21734 of Tor remotely by overflowing on the heap. Remote-code execution
21735 hasn't been confirmed, but can't be ruled out. Everyone should
21736 upgrade. Bugfix on the 0.1.1 series and later.
21738 o Directory authority changes:
21739 - Change IP address and ports for gabelmoo (v3 directory authority).
21742 - Update to the December 1 2010 Maxmind GeoLite Country database.
21745 Changes in version 0.2.1.27 - 2010-11-23
21746 Yet another OpenSSL security patch broke its compatibility with Tor:
21747 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
21748 also took this opportunity to fix several crash bugs, integrate a new
21749 directory authority, and update the bundled GeoIP database.
21752 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
21753 No longer set the tlsext_host_name extension on server SSL objects;
21754 but continue to set it on client SSL objects. Our goal in setting
21755 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
21756 bugfix on 0.2.1.1-alpha.
21757 - Do not log messages to the controller while shrinking buffer
21758 freelists. Doing so would sometimes make the controller connection
21759 try to allocate a buffer chunk, which would mess up the internals
21760 of the freelist and cause an assertion failure. Fixes bug 1125;
21761 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
21762 - Learn our external IP address when we're a relay or bridge, even if
21763 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
21764 where we introduced bridge relays that don't need to publish to
21765 be useful. Fixes bug 2050.
21766 - Do even more to reject (and not just ignore) annotations on
21767 router descriptors received anywhere but from the cache. Previously
21768 we would ignore such annotations at first, but cache them to disk
21769 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
21770 - When you're using bridges and your network goes away and your
21771 bridges get marked as down, recover when you attempt a new socks
21772 connection (if the network is back), rather than waiting up to an
21773 hour to try fetching new descriptors for your bridges. Bugfix on
21774 0.2.0.3-alpha; fixes bug 1981.
21777 - Move to the November 2010 Maxmind GeoLite country db (rather
21778 than the June 2009 ip-to-country GeoIP db) for our statistics that
21779 count how many users relays are seeing from each country. Now we'll
21780 have more accurate data, especially for many African countries.
21782 o New directory authorities:
21783 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
21787 - Fix an assertion failure that could occur in directory caches or
21788 bridge users when using a very short voting interval on a testing
21789 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
21791 - Enforce multiplicity rules when parsing annotations. Bugfix on
21792 0.2.0.8-alpha. Found by piebeer.
21793 - Allow handshaking OR connections to take a full KeepalivePeriod
21794 seconds to handshake. Previously, we would close them after
21795 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
21796 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
21798 - When building with --enable-gcc-warnings on OpenBSD, disable
21799 warnings in system headers. This makes --enable-gcc-warnings
21800 pass on OpenBSD 4.8.
21803 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
21804 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
21805 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
21806 Servers can start sending this code when enough clients recognize
21807 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
21808 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
21809 Patch from mingw-san.
21812 - Remove the old debian/ directory from the main Tor distribution.
21813 The official Tor-for-debian git repository lives at the URL
21814 https://git.torproject.org/debian/tor.git
21815 - Stop shipping the old doc/website/ directory in the tarball. We
21816 changed the website format in late 2010, and what we shipped in
21817 0.2.1.26 really wasn't that useful anyway.
21820 Changes in version 0.2.2.19-alpha - 2010-11-22
21821 Yet another OpenSSL security patch broke its compatibility with Tor:
21822 Tor 0.2.2.19-alpha makes relays work with OpenSSL 0.9.8p and 1.0.0.b.
21825 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
21826 No longer set the tlsext_host_name extension on server SSL objects;
21827 but continue to set it on client SSL objects. Our goal in setting
21828 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
21829 bugfix on 0.2.1.1-alpha.
21832 - Try harder not to exceed the maximum length of 50 KB when writing
21833 statistics to extra-info descriptors. This bug was triggered by very
21834 fast relays reporting exit-port, entry, and dirreq statistics.
21835 Reported by Olaf Selke. Bugfix on 0.2.2.1-alpha. Fixes bug 2183.
21836 - Publish a router descriptor even if generating an extra-info
21837 descriptor fails. Previously we would not publish a router
21838 descriptor without an extra-info descriptor; this can cause fast
21839 exit relays collecting exit-port statistics to drop from the
21840 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
21843 Changes in version 0.2.2.18-alpha - 2010-11-16
21844 Tor 0.2.2.18-alpha fixes several crash bugs that have been nagging
21845 us lately, makes unpublished bridge relays able to detect their IP
21846 address, and fixes a wide variety of other bugs to get us much closer
21847 to a stable release.
21850 - Do even more to reject (and not just ignore) annotations on
21851 router descriptors received anywhere but from the cache. Previously
21852 we would ignore such annotations at first, but cache them to disk
21853 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
21854 - Do not log messages to the controller while shrinking buffer
21855 freelists. Doing so would sometimes make the controller connection
21856 try to allocate a buffer chunk, which would mess up the internals
21857 of the freelist and cause an assertion failure. Fixes bug 1125;
21858 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
21859 - Learn our external IP address when we're a relay or bridge, even if
21860 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
21861 where we introduced bridge relays that don't need to publish to
21862 be useful. Fixes bug 2050.
21863 - Maintain separate TLS contexts and certificates for incoming and
21864 outgoing connections in bridge relays. Previously we would use the
21865 same TLS contexts and certs for incoming and outgoing connections.
21866 Bugfix on 0.2.0.3-alpha; addresses bug 988.
21867 - Maintain separate identity keys for incoming and outgoing TLS
21868 contexts in bridge relays. Previously we would use the same
21869 identity keys for incoming and outgoing TLS contexts. Bugfix on
21870 0.2.0.3-alpha; addresses the other half of bug 988.
21871 - Avoid an assertion failure when we as an authority receive a
21872 duplicate upload of a router descriptor that we already have,
21873 but which we previously considered an obsolete descriptor.
21874 Fixes another case of bug 1776. Bugfix on 0.2.2.16-alpha.
21875 - Avoid a crash bug triggered by looking at a dangling pointer while
21876 setting the network status consensus. Found by Robert Ransom.
21877 Bugfix on 0.2.2.17-alpha. Fixes bug 2097.
21878 - Fix a logic error where servers that _didn't_ act as exits would
21879 try to keep their server lists more aggressively up to date than
21880 exits, when it was supposed to be the other way around. Bugfix
21883 o Minor bugfixes (on Tor 0.2.1.x and earlier):
21884 - When we're trying to guess whether we know our IP address as
21885 a relay, we would log various ways that we failed to guess
21886 our address, but never log that we ended up guessing it
21887 successfully. Now add a log line to help confused and anxious
21888 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
21889 - Bring the logic that gathers routerinfos and assesses the
21890 acceptability of circuits into line. This prevents a Tor OP from
21891 getting locked in a cycle of choosing its local OR as an exit for a
21892 path (due to a .exit request) and then rejecting the circuit because
21893 its OR is not listed yet. It also prevents Tor clients from using an
21894 OR running in the same instance as an exit (due to a .exit request)
21895 if the OR does not meet the same requirements expected of an OR
21896 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
21897 - Correctly describe errors that occur when generating a TLS object.
21898 Previously we would attribute them to a failure while generating a
21899 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
21901 - Enforce multiplicity rules when parsing annotations. Bugfix on
21902 0.2.0.8-alpha. Found by piebeer.
21903 - Fix warnings that newer versions of autoconf produced during
21904 ./autogen.sh. These warnings appear to be harmless in our case,
21905 but they were extremely verbose. Fixes bug 2020.
21907 o Minor bugfixes (on Tor 0.2.2.x):
21908 - Enable protection of small arrays whenever we build with gcc
21909 hardening features, not only when also building with warnings
21910 enabled. Fixes bug 2031; bugfix on 0.2.2.14-alpha. Reported by keb.
21913 - Make hidden services work better in private Tor networks by not
21914 requiring any uptime to join the hidden service descriptor
21915 DHT. Implements ticket 2088.
21916 - Rate-limit the "your application is giving Tor only an IP address"
21917 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
21918 - When AllowSingleHopExits is set, print a warning to explain to the
21919 relay operator why most clients are avoiding her relay.
21920 - Update to the November 1 2010 Maxmind GeoLite Country database.
21922 o Code simplifications and refactoring:
21923 - When we fixed bug 1038 we had to put in a restriction not to send
21924 RELAY_EARLY cells on rend circuits. This was necessary as long
21925 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
21926 active. Now remove this obsolete check. Resolves bug 2081.
21927 - Some options used different conventions for uppercasing of acronyms
21928 when comparing manpage and source. Fix those in favor of the
21929 manpage, as it makes sense to capitalize acronyms.
21930 - Remove the torrc.complete file. It hasn't been kept up to date
21931 and users will have better luck checking out the manpage.
21932 - Remove the obsolete "NoPublish" option; it has been flagged
21933 as obsolete and has produced a warning since 0.1.1.18-rc.
21934 - Remove everything related to building the expert bundle for OS X.
21935 It has confused many users, doesn't work right on OS X 10.6,
21936 and is hard to get rid of once installed. Resolves bug 1274.
21939 Changes in version 0.2.2.17-alpha - 2010-09-30
21940 Tor 0.2.2.17-alpha introduces a feature to make it harder for clients
21941 to use one-hop circuits (which can put the exit relays at higher risk,
21942 plus unbalance the network); fixes a big bug in bandwidth accounting
21943 for relays that want to limit their monthly bandwidth use; fixes a
21944 big pile of bugs in how clients tolerate temporary network failure;
21945 and makes our adaptive circuit build timeout feature (which improves
21946 client performance if your network is fast while not breaking things
21947 if your network is slow) better handle bad networks.
21950 - Exit relays now try harder to block exit attempts from unknown
21951 relays, to make it harder for people to use them as one-hop proxies
21952 a la tortunnel. Controlled by the refuseunknownexits consensus
21953 parameter (currently enabled), or you can override it on your
21954 relay with the RefuseUnknownExits torrc option. Resolves bug 1751.
21956 o Major bugfixes (0.2.1.x and earlier):
21957 - Fix a bug in bandwidth accounting that could make us use twice
21958 the intended bandwidth when our interval start changes due to
21959 daylight saving time. Now we tolerate skew in stored vs computed
21960 interval starts: if the start of the period changes by no more than
21961 50% of the period's duration, we remember bytes that we transferred
21962 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
21963 - Always search the Windows system directory for system DLLs, and
21964 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
21965 - When you're using bridges and your network goes away and your
21966 bridges get marked as down, recover when you attempt a new socks
21967 connection (if the network is back), rather than waiting up to an
21968 hour to try fetching new descriptors for your bridges. Bugfix on
21969 0.2.0.3-alpha; fixes bug 1981.
21971 o Major bugfixes (on 0.2.2.x):
21972 - Fix compilation on Windows. Bugfix on 0.2.2.16-alpha; related to
21974 - Fix a segfault that could happen when operating a bridge relay with
21975 no GeoIP database set. Fixes bug 1964; bugfix on 0.2.2.15-alpha.
21976 - The consensus bandwidth-weights (used by clients to choose fast
21977 relays) entered an unexpected edge case in September where
21978 Exits were much scarcer than Guards, resulting in bad weight
21979 recommendations. Now we compute them using new constraints that
21980 should succeed in all cases. Also alter directory authorities to
21981 not include the bandwidth-weights line if they fail to produce
21982 valid values. Fixes bug 1952; bugfix on 0.2.2.10-alpha.
21983 - When weighting bridges during path selection, we used to trust
21984 the bandwidths they provided in their descriptor, only capping them
21985 at 10MB/s. This turned out to be problematic for two reasons:
21986 Bridges could claim to handle a lot more traffic then they
21987 actually would, thus making more clients pick them and have a
21988 pretty effective DoS attack. The other issue is that new bridges
21989 that might not have a good estimate for their bw capacity yet
21990 would not get used at all unless no other bridges are available
21991 to a client. Fixes bug 1912; bugfix on 0.2.2.7-alpha.
21993 o Major bugfixes (on the circuit build timeout feature, 0.2.2.x):
21994 - Ignore cannibalized circuits when recording circuit build times.
21995 This should provide for a minor performance improvement for hidden
21996 service users using 0.2.2.14-alpha, and should remove two spurious
21997 notice log messages. Bugfix on 0.2.2.14-alpha; fixes bug 1740.
21998 - Simplify the logic that causes us to decide if the network is
21999 unavailable for purposes of recording circuit build times. If we
22000 receive no cells whatsoever for the entire duration of a circuit's
22001 full measured lifetime, the network is probably down. Also ignore
22002 one-hop directory fetching circuit timeouts when calculating our
22003 circuit build times. These changes should hopefully reduce the
22004 cases where we see ridiculous circuit build timeouts for people
22005 with spotty wireless connections. Fixes part of bug 1772; bugfix
22007 - Prevent the circuit build timeout from becoming larger than
22008 the maximum build time we have ever seen. Also, prevent the time
22009 period for measurement circuits from becoming larger than twice that
22010 value. Fixes the other part of bug 1772; bugfix on 0.2.2.2-alpha.
22013 - When we run out of directory information such that we can't build
22014 circuits, but then get enough that we can build circuits, log when
22015 we actually construct a circuit, so the user has a better chance of
22016 knowing what's going on. Fixes bug 1362.
22017 - Be more generous with how much bandwidth we'd use up (with
22018 accounting enabled) before entering "soft hibernation". Previously,
22019 we'd refuse new connections and circuits once we'd used up 95% of
22020 our allotment. Now, we use up 95% of our allotment, AND make sure
22021 that we have no more than 500MB (or 3 hours of expected traffic,
22022 whichever is lower) remaining before we enter soft hibernation.
22023 - If we've configured EntryNodes and our network goes away and/or all
22024 our entrynodes get marked down, optimistically retry them all when
22025 a new socks application request appears. Fixes bug 1882.
22026 - Add some more defensive programming for architectures that can't
22027 handle unaligned integer accesses. We don't know of any actual bugs
22028 right now, but that's the best time to fix them. Fixes bug 1943.
22029 - Support line continuations in the torrc config file. If a line
22030 ends with a single backslash character, the newline is ignored, and
22031 the configuration value is treated as continuing on the next line.
22034 o Minor bugfixes (on 0.2.1.x and earlier):
22035 - For bandwidth accounting, calculate our expected bandwidth rate
22036 based on the time during which we were active and not in
22037 soft-hibernation during the last interval. Previously, we were
22038 also considering the time spent in soft-hibernation. If this
22039 was a long time, we would wind up underestimating our bandwidth
22040 by a lot, and skewing our wakeup time towards the start of the
22041 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
22043 o Minor bugfixes (on 0.2.2.x):
22044 - Resume generating CIRC FAILED REASON=TIMEOUT control port messages,
22045 which were disabled by the circuit build timeout changes in
22046 0.2.2.14-alpha. Bugfix on 0.2.2.14-alpha; fixes bug 1739.
22047 - Make sure we don't warn about missing bandwidth weights when
22048 choosing bridges or other relays not in the consensus. Bugfix on
22049 0.2.2.10-alpha; fixes bug 1805.
22050 - In our logs, do not double-report signatures from unrecognized
22051 authorities both as "from unknown authority" and "not
22052 present". Fixes bug 1956, bugfix on 0.2.2.16-alpha.
22055 Changes in version 0.2.2.16-alpha - 2010-09-17
22056 Tor 0.2.2.16-alpha fixes a variety of old stream fairness bugs (most
22057 evident at exit relays), and also continues to resolve all the little
22058 bugs that have been filling up trac lately.
22060 o Major bugfixes (stream-level fairness):
22061 - When receiving a circuit-level SENDME for a blocked circuit, try
22062 to package cells fairly from all the streams that had previously
22063 been blocked on that circuit. Previously, we had started with the
22064 oldest stream, and allowed each stream to potentially exhaust
22065 the circuit's package window. This gave older streams on any
22066 given circuit priority over newer ones. Fixes bug 1937. Detected
22067 originally by Camilo Viecco. This bug was introduced before the
22068 first Tor release, in svn commit r152: it is the new winner of
22069 the longest-lived bug prize.
22070 - When the exit relay got a circuit-level sendme cell, it started
22071 reading on the exit streams, even if had 500 cells queued in the
22072 circuit queue already, so the circuit queue just grew and grew in
22073 some cases. We fix this by not re-enabling reading on receipt of a
22074 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
22075 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
22077 - Newly created streams were allowed to read cells onto circuits,
22078 even if the circuit's cell queue was blocked and waiting to drain.
22079 This created potential unfairness, as older streams would be
22080 blocked, but newer streams would gladly fill the queue completely.
22081 We add code to detect this situation and prevent any stream from
22082 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
22086 - Update to the September 1 2010 Maxmind GeoLite Country database.
22087 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
22088 not. This would lead to a cookie that is still not group readable.
22089 Closes bug 1843. Suggested by katmagic.
22090 - When logging a rate-limited warning, we now mention how many messages
22091 got suppressed since the last warning.
22092 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
22093 do individual connection-level rate limiting of clients. The torrc
22094 config options with the same names trump the consensus params, if
22095 both are present. Replaces the old "bwconnrate" and "bwconnburst"
22096 consensus params which were broken from 0.2.2.7-alpha through
22097 0.2.2.14-alpha. Closes bug 1947.
22098 - When a router changes IP address or port, authorities now launch
22099 a new reachability test for it. Implements ticket 1899.
22100 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
22101 2 no signature, 4 required" messages about consensus signatures
22102 easier to read, and make sure they get logged at the same severity
22103 as the messages explaining which keys are which. Fixes bug 1290.
22104 - Don't warn when we have a consensus that we can't verify because
22105 of missing certificates, unless those certificates are ones
22106 that we have been trying and failing to download. Fixes bug 1145.
22107 - If you configure your bridge with a known identity fingerprint,
22108 and the bridge authority is unreachable (as it is in at least
22109 one country now), fall back to directly requesting the descriptor
22110 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
22112 - When building with --enable-gcc-warnings on OpenBSD, disable
22113 warnings in system headers. This makes --enable-gcc-warnings
22114 pass on OpenBSD 4.8.
22116 o Minor bugfixes (on 0.2.1.x and earlier):
22117 - Authorities will now attempt to download consensuses if their
22118 own efforts to make a live consensus have failed. This change
22119 means authorities that restart will fetch a valid consensus, and
22120 it means authorities that didn't agree with the current consensus
22121 will still fetch and serve it if it has enough signatures. Bugfix
22122 on 0.2.0.9-alpha; fixes bug 1300.
22123 - Ensure DNS requests launched by "RESOLVE" commands from the
22124 controller respect the __LeaveStreamsUnattached setconf options. The
22125 same goes for requests launched via DNSPort or transparent
22126 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
22127 - Allow handshaking OR connections to take a full KeepalivePeriod
22128 seconds to handshake. Previously, we would close them after
22129 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
22130 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
22132 - Rate-limit "Failed to hand off onionskin" warnings.
22133 - Never relay a cell for a circuit we have already destroyed.
22134 Between marking a circuit as closeable and finally closing it,
22135 it may have been possible for a few queued cells to get relayed,
22136 even though they would have been immediately dropped by the next
22137 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
22138 - Never queue a cell for a circuit that's already been marked
22140 - Never vote for a server as "Running" if we have a descriptor for
22141 it claiming to be hibernating, and that descriptor was published
22142 more recently than our last contact with the server. Bugfix on
22143 0.2.0.3-alpha; fixes bug 911.
22144 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
22147 o Minor bugfixes (on 0.2.2.x):
22148 - Fix a regression introduced in 0.2.2.7-alpha that marked relays
22149 down if a directory fetch fails and you've configured either
22150 bridges or EntryNodes. The intent was to mark the relay as down
22151 _unless_ you're using bridges or EntryNodes, since if you are
22152 then you could quickly run out of entry points.
22153 - Fix the Windows directory-listing code. A bug introduced in
22154 0.2.2.14-alpha could make Windows directory servers forget to load
22155 some of their cached v2 networkstatus files.
22156 - Really allow clients to use relays as bridges. Fixes bug 1776;
22157 bugfix on 0.2.2.15-alpha.
22158 - Demote a warn to info that happens when the CellStatistics option
22159 was just enabled. Bugfix on 0.2.2.15-alpha; fixes bug 1921.
22160 Reported by Moritz Bartl.
22161 - On Windows, build correctly either with or without Unicode support.
22162 This is necessary so that Tor can support fringe platforms like
22163 Windows 98 (which has no Unicode), or Windows CE (which has no
22164 non-Unicode). Bugfix on 0.2.2.14-alpha; fixes bug 1797.
22167 - Add a unit test for cross-platform directory-listing code.
22170 Changes in version 0.2.2.15-alpha - 2010-08-18
22171 Tor 0.2.2.15-alpha fixes a big bug in hidden service availability,
22172 fixes a variety of other bugs that were preventing performance
22173 experiments from moving forward, fixes several bothersome memory leaks,
22174 and generally closes a lot of smaller bugs that have been filling up
22178 - Stop assigning the HSDir flag to relays that disable their
22179 DirPort (and thus will refuse to answer directory requests). This
22180 fix should dramatically improve the reachability of hidden services:
22181 hidden services and hidden service clients pick six HSDir relays
22182 to store and retrieve the hidden service descriptor, and currently
22183 about half of the HSDir relays will refuse to work. Bugfix on
22184 0.2.0.10-alpha; fixes part of bug 1693.
22185 - The PerConnBWRate and Burst config options, along with the
22186 bwconnrate and bwconnburst consensus params, initialized each conn's
22187 token bucket values only when the connection is established. Now we
22188 update them if the config options change, and update them every time
22189 we get a new consensus. Otherwise we can encounter an ugly edge
22190 case where we initialize an OR conn to client-level bandwidth,
22191 but then later the relay joins the consensus and we leave it
22192 throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
22193 - Fix a regression that caused Tor to rebind its ports if it receives
22194 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
22197 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
22198 should give us approximately 40-50% more Guard-flagged nodes,
22199 improving the anonymity the Tor network can provide and also
22200 decreasing the dropoff in throughput that relays experience when
22201 they first get the Guard flag.
22202 - Allow enabling or disabling the *Statistics config options while
22206 - Update to the August 1 2010 Maxmind GeoLite Country database.
22207 - Have the controller interface give a more useful message than
22208 "Internal Error" in response to failed GETINFO requests.
22209 - Warn when the same option is provided more than once in a torrc
22210 file, on the command line, or in a single SETCONF statement, and
22211 the option is one that only accepts a single line. Closes bug 1384.
22212 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
22213 Patch from mingw-san.
22214 - Add support for the country code "{??}" in torrc options like
22215 ExcludeNodes, to indicate all routers of unknown country. Closes
22217 - Relays report the number of bytes spent on answering directory
22218 requests in extra-info descriptors similar to {read,write}-history.
22219 Implements enhancement 1790.
22221 o Minor bugfixes (on 0.2.1.x and earlier):
22222 - Complain if PublishServerDescriptor is given multiple arguments that
22223 include 0 or 1. This configuration will be rejected in the future.
22224 Bugfix on 0.2.0.1-alpha; closes bug 1107.
22225 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
22226 Bugfix on 0.2.0.13-alpha; closes bug 928.
22227 - Change "Application request when we're believed to be offline."
22228 notice to "Application request when we haven't used client
22229 functionality lately.", to clarify that it's not an error. Bugfix
22230 on 0.0.9.3; fixes bug 1222.
22231 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
22232 would return "551 Internal error" rather than "552 Unrecognized key
22233 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
22234 - Users can't configure a regular relay to be their bridge. It didn't
22235 work because when Tor fetched the bridge descriptor, it found
22236 that it already had it, and didn't realize that the purpose of the
22237 descriptor had changed. Now we replace routers with a purpose other
22238 than bridge with bridge descriptors when fetching them. Bugfix on
22239 0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
22240 refetch the descriptor with router purpose 'general', disabling
22242 - Fix a rare bug in rend_fn unit tests: we would fail a test when
22243 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
22244 on 0.2.0.10-alpha; fixes bug 1808.
22245 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
22246 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
22247 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
22248 Servers can start sending this code when enough clients recognize
22249 it. Also update the spec to reflect this new reason. Bugfix on
22250 0.1.0.1-rc; fixes part of bug 1793.
22251 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
22252 when we switch from being a public relay to a bridge. Otherwise
22253 there will still be clients that see the relay in their consensus,
22254 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
22256 - Instead of giving an assertion failure on an internal mismatch
22257 on estimated freelist size, just log a BUG warning and try later.
22258 Mitigates but does not fix bug 1125.
22259 - Fix an assertion failure that could occur in caches or bridge users
22260 when using a very short voting interval on a testing network.
22261 Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.
22263 o Minor bugfixes (on 0.2.2.x):
22264 - Alter directory authorities to always consider Exit-flagged nodes
22265 as potential Guard nodes in their votes. The actual decision to
22266 use Exits as Guards is done in the consensus bandwidth weights.
22267 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
22268 - When the controller is reporting the purpose of circuits that
22269 didn't finish building before the circuit build timeout, it was
22270 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
22271 - Our libevent version parsing code couldn't handle versions like
22272 1.4.14b-stable and incorrectly warned the user about using an
22273 old and broken version of libevent. Treat 1.4.14b-stable like
22274 1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
22276 - Don't use substitution references like $(VAR:MOD) when
22277 $(asciidoc_files) is empty -- make(1) on NetBSD transforms
22278 '$(:x)' to 'x' rather than the empty string. This bites us in
22279 doc/ when configured with --disable-asciidoc. Bugfix on
22280 0.2.2.9-alpha; fixes bug 1773.
22281 - Remove a spurious hidden service server-side log notice about
22282 "Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
22284 - Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
22286 - Correctly report written bytes on linked connections. Found while
22287 implementing 1790. Bugfix on 0.2.2.4-alpha.
22288 - Fix three memory leaks: one in circuit_build_times_parse_state(),
22289 one in dirvote_add_signatures_to_pending_consensus(), and one every
22290 time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
22291 0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.
22293 o Code simplifications and refactoring:
22294 - Take a first step towards making or.h smaller by splitting out
22295 function definitions for all source files in src/or/. Leave
22296 structures and defines in or.h for now.
22297 - Remove a bunch of unused function declarations as well as a block of
22298 #if 0'd code from the unit tests. Closes bug 1824.
22299 - New unit tests for exit-port history statistics; refactored exit
22300 statistics code to be more easily tested.
22301 - Remove the old debian/ directory from the main Tor distribution.
22302 The official Tor-for-debian git repository lives at the URL
22303 https://git.torproject.org/debian/tor.git
22306 Changes in version 0.2.2.14-alpha - 2010-07-12
22307 Tor 0.2.2.14-alpha greatly improves client-side handling of
22308 circuit build timeouts, which are used to estimate speed and improve
22309 performance. We also move to a much better GeoIP database, port Tor to
22310 Windows CE, introduce new compile flags that improve code security,
22311 add an eighth v3 directory authority, and address a lot of more
22315 - Tor directory authorities no longer crash when started with a
22316 cached-microdesc-consensus file in their data directory. Bugfix
22317 on 0.2.2.6-alpha; fixes bug 1532.
22318 - Treat an unset $HOME like an empty $HOME rather than triggering an
22319 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
22320 - Ignore negative and large circuit build timeout values that can
22321 happen during a suspend or hibernate. These values caused various
22322 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
22323 - Alter calculation of Pareto distribution parameter 'Xm' for
22324 Circuit Build Timeout learning to use the weighted average of the
22325 top N=3 modes (because we have three entry guards). Considering
22326 multiple modes should improve the timeout calculation in some cases,
22327 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
22329 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
22330 right censored distribution model. This approach improves over the
22331 synthetic timeout generation approach that was producing insanely
22332 high timeout values. Now we calculate build timeouts using truncated
22333 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
22334 - Do not close circuits that are under construction when they reach
22335 the circuit build timeout. Instead, leave them building (but do not
22336 use them) for up until the time corresponding to the 95th percentile
22337 on the Pareto CDF or 60 seconds, whichever is greater. This is done
22338 to provide better data for the new Pareto model. This percentile
22339 can be controlled by the consensus.
22342 - Move to the June 2010 Maxmind GeoLite country db (rather than the
22343 June 2009 ip-to-country GeoIP db) for our statistics that count
22344 how many users relays are seeing from each country. Now we have
22345 more accurate data for many African countries.
22346 - Port Tor to build and run correctly on Windows CE systems, using
22347 the wcecompat library. Contributed by Valerio Lupi.
22348 - New "--enable-gcc-hardening" ./configure flag (off by default)
22349 to turn on gcc compile time hardening options. It ensures
22350 that signed ints have defined behavior (-fwrapv), enables
22351 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
22352 with canaries (-fstack-protector-all), turns on ASLR protection if
22353 supported by the kernel (-fPIE, -pie), and adds additional security
22354 related warnings. Verified to work on Mac OS X and Debian Lenny.
22355 - New "--enable-linker-hardening" ./configure flag (off by default)
22356 to turn on ELF specific hardening features (relro, now). This does
22357 not work with Mac OS X or any other non-ELF binary format.
22359 o New directory authorities:
22360 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
22364 - New config option "WarnUnsafeSocks 0" disables the warning that
22365 occurs whenever Tor receives a socks handshake using a version of
22366 the socks protocol that can only provide an IP address (rather
22367 than a hostname). Setups that do DNS locally over Tor are fine,
22368 and we shouldn't spam the logs in that case.
22369 - Convert the HACKING file to asciidoc, and add a few new sections
22370 to it, explaining how we use Git, how we make changelogs, and
22371 what should go in a patch.
22372 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
22373 event, to give information on the current rate of circuit timeouts
22374 over our stored history.
22375 - Add ability to disable circuit build time learning via consensus
22376 parameter and via a LearnCircuitBuildTimeout config option. Also
22377 automatically disable circuit build time calculation if we are
22378 either a AuthoritativeDirectory, or if we fail to write our state
22379 file. Fixes bug 1296.
22380 - More gracefully handle corrupt state files, removing asserts
22381 in favor of saving a backup and resetting state.
22382 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
22386 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
22388 - When a2x fails, mention that the user could disable manpages instead
22389 of trying to fix their asciidoc installation.
22390 - Where available, use Libevent 2.0's periodic timers so that our
22391 once-per-second cleanup code gets called even more closely to
22392 once per second than it would otherwise. Fixes bug 943.
22393 - If you run a bridge that listens on multiple IP addresses, and
22394 some user configures a bridge address that uses a different IP
22395 address than your bridge writes in its router descriptor, and the
22396 user doesn't specify an identity key, their Tor would discard the
22397 descriptor because "it isn't one of our configured bridges", and
22398 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
22399 Bugfix on 0.2.0.3-alpha.
22400 - If OpenSSL fails to make a duplicate of a private or public key, log
22401 an error message and try to exit cleanly. May help with debugging
22402 if bug 1209 ever remanifests.
22403 - Save a couple bytes in memory allocation every time we escape
22404 certain characters in a string. Patch from Florian Zumbiehl.
22405 - Make it explicit that we don't cannibalize one-hop circuits. This
22406 happens in the wild, but doesn't turn out to be a problem because
22407 we fortunately don't use those circuits. Many thanks to outofwords
22408 for the initial analysis and to swissknife who confirmed that
22409 two-hop circuits are actually created.
22410 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
22411 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
22412 - Eliminate a case where a circuit build time warning was displayed
22413 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
22416 Changes in version 0.2.1.26 - 2010-05-02
22417 Tor 0.2.1.26 addresses the recent connection and memory overload
22418 problems we've been seeing on relays, especially relays with their
22419 DirPort open. If your relay has been crashing, or you turned it off
22420 because it used too many resources, give this release a try.
22422 This release also fixes yet another instance of broken OpenSSL libraries
22423 that was causing some relays to drop out of the consensus.
22426 - Teach relays to defend themselves from connection overload. Relays
22427 now close idle circuits early if it looks like they were intended
22428 for directory fetches. Relays are also more aggressive about closing
22429 TLS connections that have no circuits on them. Such circuits are
22430 unlikely to be re-used, and tens of thousands of them were piling
22431 up at the fast relays, causing the relays to run out of sockets
22432 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
22433 their directory fetches over TLS).
22434 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
22435 that claim to be earlier than 0.9.8m, but which have in reality
22436 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
22437 behavior. Possible fix for some cases of bug 1346.
22438 - Directory mirrors were fetching relay descriptors only from v2
22439 directory authorities, rather than v3 authorities like they should.
22440 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
22441 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
22444 - Finally get rid of the deprecated and now harmful notion of "clique
22445 mode", where directory authorities maintain TLS connections to
22449 - In the util/threads test, no longer free the test_mutex before all
22450 worker threads have finished. Bugfix on 0.2.1.6-alpha.
22451 - The master thread could starve the worker threads quite badly on
22452 certain systems, causing them to run only partially in the allowed
22453 window. This resulted in test failures. Now the master thread sleeps
22454 occasionally for a few microseconds while the two worker-threads
22455 compete for the mutex. Bugfix on 0.2.0.1-alpha.
22458 Changes in version 0.2.2.13-alpha - 2010-04-24
22459 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
22460 problems we've been seeing on relays, especially relays with their
22461 DirPort open. If your relay has been crashing, or you turned it off
22462 because it used too many resources, give this release a try.
22465 - Teach relays to defend themselves from connection overload. Relays
22466 now close idle circuits early if it looks like they were intended
22467 for directory fetches. Relays are also more aggressive about closing
22468 TLS connections that have no circuits on them. Such circuits are
22469 unlikely to be re-used, and tens of thousands of them were piling
22470 up at the fast relays, causing the relays to run out of sockets
22471 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
22472 their directory fetches over TLS).
22475 - Finally get rid of the deprecated and now harmful notion of "clique
22476 mode", where directory authorities maintain TLS connections to
22478 - Directory authorities now do an immediate reachability check as soon
22479 as they hear about a new relay. This change should slightly reduce
22480 the time between setting up a relay and getting listed as running
22481 in the consensus. It should also improve the time between setting
22482 up a bridge and seeing use by bridge users.
22483 - Directory authorities no longer launch a TLS connection to every
22484 relay as they startup. Now that we have 2k+ descriptors cached,
22485 the resulting network hiccup is becoming a burden. Besides,
22486 authorities already avoid voting about Running for the first half
22487 hour of their uptime.
22490 Changes in version 0.2.2.12-alpha - 2010-04-20
22491 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
22492 handle and vote on descriptors. It was causing relays to drop out of
22496 - Many relays have been falling out of the consensus lately because
22497 not enough authorities know about their descriptor for them to get
22498 a majority of votes. When we deprecated the v2 directory protocol,
22499 we got rid of the only way that v3 authorities can hear from each
22500 other about other descriptors. Now authorities examine every v3
22501 vote for new descriptors, and fetch them from that authority. Bugfix
22503 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
22504 and a warning in or.h related to bandwidth_weight_rule_t that
22505 prevented clean compile on OS X. Fixes bug 1363; bugfix on
22507 - Fix a segfault on relays when DirReqStatistics is enabled
22508 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
22512 - Demote a confusing TLS warning that relay operators might get when
22513 someone tries to talk to their OrPort. It is neither the operator's
22514 fault nor can they do anything about it. Fixes bug 1364; bugfix
22518 Changes in version 0.2.2.11-alpha - 2010-04-15
22519 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
22520 libraries that was causing some relays to drop out of the consensus.
22523 - Directory mirrors were fetching relay descriptors only from v2
22524 directory authorities, rather than v3 authorities like they should.
22525 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
22526 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
22527 - Fix a parsing error that made every possible value of
22528 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
22529 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
22530 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
22531 about the option without breaking older ones.
22532 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
22533 that claim to be earlier than 0.9.8m, but which have in reality
22534 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
22535 behavior. Possible fix for some cases of bug 1346.
22538 - Experiment with a more aggressive approach to preventing clients
22539 from making one-hop exit streams. Exit relays who want to try it
22540 out can set "RefuseUnknownExits 1" in their torrc, and then look
22541 for "Attempt by %s to open a stream" log messages. Let us know
22543 - Add support for statically linking zlib by specifying
22544 --enable-static-zlib, to go with our support for statically linking
22545 openssl and libevent. Resolves bug 1358.
22548 - Fix a segfault that happens whenever a Tor client that is using
22549 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
22551 - When we cleaned up the contrib/tor-exit-notice.html file, we left
22552 out the first line. Fixes bug 1295.
22553 - When building the manpage from a tarball, we required asciidoc, but
22554 the asciidoc -> roff/html conversion was already done for the
22555 tarball. Make 'make' complain only when we need asciidoc (either
22556 because we're compiling directly from git, or because we altered
22557 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
22558 - When none of the directory authorities vote on any params, Tor
22559 segfaulted when trying to make the consensus from the votes. We
22560 didn't trigger the bug in practice, because authorities do include
22561 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
22564 - In the util/threads test, no longer free the test_mutex before all
22565 worker threads have finished. Bugfix on 0.2.1.6-alpha.
22566 - The master thread could starve the worker threads quite badly on
22567 certain systems, causing them to run only partially in the allowed
22568 window. This resulted in test failures. Now the master thread sleeps
22569 occasionally for a few microseconds while the two worker-threads
22570 compete for the mutex. Bugfix on 0.2.0.1-alpha.
22573 Changes in version 0.2.2.10-alpha - 2010-03-07
22574 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
22575 could prevent relays from guessing their IP address correctly. It also
22576 starts the groundwork for another client-side performance boost, since
22577 currently we're not making efficient use of relays that have both the
22578 Guard flag and the Exit flag.
22581 - Fix a regression from our patch for bug 1244 that caused relays
22582 to guess their IP address incorrectly if they didn't set Address
22583 in their torrc and/or their address fails to resolve. Bugfix on
22584 0.2.2.9-alpha; fixes bug 1269.
22586 o Major features (performance):
22587 - Directory authorities now compute consensus weightings that instruct
22588 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
22589 and no flag. Clients that use these weightings will distribute
22590 network load more evenly across these different relay types. The
22591 weightings are in the consensus so we can change them globally in
22592 the future. Extra thanks to "outofwords" for finding some nasty
22593 security bugs in the first implementation of this feature.
22595 o Minor features (performance):
22596 - Always perform router selections using weighted relay bandwidth,
22597 even if we don't need a high capacity circuit at the time. Non-fast
22598 circuits now only differ from fast ones in that they can use relays
22599 not marked with the Fast flag. This "feature" could turn out to
22600 be a horrible bug; we should investigate more before it goes into
22604 - Allow disabling building of the manpages. Skipping the manpage
22605 speeds up the build considerably.
22607 o Minor bugfixes (on 0.2.2.x):
22608 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
22609 Bugfix on 0.2.2.9-alpha.
22610 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
22611 config option. Bugfix on 0.2.2.7-alpha.
22612 - Ship the asciidoc-helper file in the tarball, so that people can
22613 build from source if they want to, and touching the .1.txt files
22614 doesn't break the build. Bugfix on 0.2.2.9-alpha.
22616 o Minor bugfixes (on 0.2.1.x or earlier):
22617 - Fix a dereference-then-NULL-check sequence when publishing
22618 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
22620 - Fix another dereference-then-NULL-check sequence. Bugfix on
22621 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
22622 - Make sure we treat potentially not NUL-terminated strings correctly.
22623 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
22625 o Code simplifications and refactoring:
22626 - Fix some urls in the exit notice file and make it XHTML1.1 strict
22627 compliant. Based on a patch from Christian Kujau.
22628 - Don't use sed in asciidoc-helper anymore.
22629 - Make the build process fail if asciidoc cannot be found and
22630 building with asciidoc isn't disabled.
22633 Changes in version 0.2.2.9-alpha - 2010-02-22
22634 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
22635 location of a directory authority, and cleans up a bunch of small bugs.
22637 o Directory authority changes:
22638 - Change IP address for dannenberg (v3 directory authority), and
22639 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
22640 service directory authority) from the list.
22643 - Make Tor work again on the latest OS X: when deciding whether to
22644 use strange flags to turn TLS renegotiation on, detect the OpenSSL
22645 version at run-time, not compile time. We need to do this because
22646 Apple doesn't update its dev-tools headers when it updates its
22647 libraries in a security patch.
22648 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
22649 that could happen on 32-bit platforms with 64-bit time_t. Also fix
22650 a memory leak when requesting a hidden service descriptor we've
22651 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
22653 - Authorities could be tricked into giving out the Exit flag to relays
22654 that didn't allow exiting to any ports. This bug could screw
22655 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
22656 1238. Bug discovered by Martin Kowalczyk.
22657 - When freeing a session key, zero it out completely. We only zeroed
22658 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
22659 patched by ekir. Fixes bug 1254.
22662 - Fix static compilation by listing the openssl libraries in the right
22663 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
22664 - Resume handling .exit hostnames in a special way: originally we
22665 stripped the .exit part and used the requested exit relay. In
22666 0.2.2.1-alpha we stopped treating them in any special way, meaning
22667 if you use a .exit address then Tor will pass it on to the exit
22668 relay. Now we reject the .exit stream outright, since that behavior
22669 might be more expected by the user. Found and diagnosed by Scott
22670 Bennett and Downie on or-talk.
22671 - Don't spam the controller with events when we have no file
22672 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
22673 for log messages was already solved from bug 748.)
22674 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
22676 - Make the DNSPort option work with libevent 2.x. Don't alter the
22677 behavior for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
22678 - Emit a GUARD DROPPED controller event for a case we missed.
22679 - Make more fields in the controller protocol case-insensitive, since
22680 control-spec.txt said they were.
22681 - Refactor resolve_my_address() to not use gethostbyname() anymore.
22682 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
22683 - Fix a spec conformance issue: the network-status-version token
22684 must be the first token in a v3 consensus or vote. Discovered by
22685 parakeep. Bugfix on 0.2.0.3-alpha.
22687 o Code simplifications and refactoring:
22688 - Generate our manpage and HTML documentation using Asciidoc. This
22689 change should make it easier to maintain the documentation, and
22690 produce nicer HTML.
22691 - Remove the --enable-iphone option. According to reports from Marco
22692 Bonetti, Tor builds fine without any special tweaking on recent
22693 iPhone SDK versions.
22694 - Removed some unnecessary files from the source distribution. The
22695 AUTHORS file has now been merged into the people page on the
22696 website. The roadmaps and design doc can now be found in the
22697 projects directory in svn.
22698 - Enabled various circuit build timeout constants to be controlled
22699 by consensus parameters. Also set better defaults for these
22700 parameters based on experimentation on broadband and simulated
22701 high latency links.
22704 - The 'EXTENDCIRCUIT' control port command can now be used with
22705 a circ id of 0 and no path. This feature will cause Tor to build
22706 a new 'fast' general purpose circuit using its own path selection
22708 - Added a BUILDTIMEOUT_SET controller event to describe changes
22709 to the circuit build timeout.
22710 - Future-proof the controller protocol a bit by ignoring keyword
22711 arguments we do not recognize.
22712 - Expand homedirs passed to tor-checkkey. This should silence a
22713 coverity complaint about passing a user-supplied string into
22714 open() without checking it.
22717 Changes in version 0.2.1.25 - 2010-03-16
22718 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
22719 prevent relays from guessing their IP address correctly. It also fixes
22720 several minor potential security bugs.
22723 - Fix a regression from our patch for bug 1244 that caused relays
22724 to guess their IP address incorrectly if they didn't set Address
22725 in their torrc and/or their address fails to resolve. Bugfix on
22726 0.2.1.23; fixes bug 1269.
22727 - When freeing a session key, zero it out completely. We only zeroed
22728 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
22729 patched by ekir. Fixes bug 1254.
22732 - Fix a dereference-then-NULL-check sequence when publishing
22733 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
22735 - Fix another dereference-then-NULL-check sequence. Bugfix on
22736 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
22737 - Make sure we treat potentially not NUL-terminated strings correctly.
22738 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
22742 Changes in version 0.2.1.24 - 2010-02-21
22743 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
22747 - Work correctly out-of-the-box with even more vendor-patched versions
22748 of OpenSSL. In particular, make it so Debian and OS X don't need
22749 customized patches to run/build.
22752 Changes in version 0.2.1.23 - 2010-02-13
22753 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
22754 again on the latest OS X, and updates the location of a directory
22757 o Major bugfixes (performance):
22758 - We were selecting our guards uniformly at random, and then weighting
22759 which of our guards we'd use uniformly at random. This imbalance
22760 meant that Tor clients were severely limited on throughput (and
22761 probably latency too) by the first hop in their circuit. Now we
22762 select guards weighted by currently advertised bandwidth. We also
22763 automatically discard guards picked using the old algorithm. Fixes
22764 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
22767 - Make Tor work again on the latest OS X: when deciding whether to
22768 use strange flags to turn TLS renegotiation on, detect the OpenSSL
22769 version at run-time, not compile time. We need to do this because
22770 Apple doesn't update its dev-tools headers when it updates its
22771 libraries in a security patch.
22772 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
22773 that could happen on 32-bit platforms with 64-bit time_t. Also fix
22774 a memory leak when requesting a hidden service descriptor we've
22775 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
22778 o Directory authority changes:
22779 - Change IP address for dannenberg (v3 directory authority), and
22780 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
22781 service directory authority) from the list.
22784 - Refactor resolve_my_address() to not use gethostbyname() anymore.
22785 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
22788 - Avoid a mad rush at the beginning of each month when each client
22789 rotates half of its guards. Instead we spread the rotation out
22790 throughout the month, but we still avoid leaving a precise timestamp
22791 in the state file about when we first picked the guard. Improves
22792 over the behavior introduced in 0.1.2.17.
22795 Changes in version 0.2.2.8-alpha - 2010-01-26
22796 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
22797 causing bridge relays to disappear. If you're running a bridge,
22801 - Fix a memory corruption bug on bridges that occurred during the
22802 inclusion of stats data in extra-info descriptors. Also fix the
22803 interface for geoip_get_bridge_stats* to prevent similar bugs in
22804 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
22805 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
22808 - Ignore OutboundBindAddress when connecting to localhost.
22809 Connections to localhost need to come _from_ localhost, or else
22810 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
22814 Changes in version 0.2.2.7-alpha - 2010-01-19
22815 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
22816 as laying the groundwork for further relay-side performance fixes. It
22817 also starts cleaning up client behavior with respect to the EntryNodes,
22818 ExitNodes, and StrictNodes config options.
22820 This release also rotates two directory authority keys, due to a
22821 security breach of some of the Torproject servers.
22823 o Directory authority changes:
22824 - Rotate keys (both v3 identity and relay identity) for moria1
22827 o Major features (performance):
22828 - We were selecting our guards uniformly at random, and then weighting
22829 which of our guards we'd use uniformly at random. This imbalance
22830 meant that Tor clients were severely limited on throughput (and
22831 probably latency too) by the first hop in their circuit. Now we
22832 select guards weighted by currently advertised bandwidth. We also
22833 automatically discard guards picked using the old algorithm. Fixes
22834 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
22835 - When choosing which cells to relay first, relays can now favor
22836 circuits that have been quiet recently, to provide lower latency
22837 for low-volume circuits. By default, relays enable or disable this
22838 feature based on a setting in the consensus. You can override
22839 this default by using the new "CircuitPriorityHalflife" config
22840 option. Design and code by Ian Goldberg, Can Tang, and Chris
22842 - Add separate per-conn write limiting to go with the per-conn read
22843 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
22844 but never per-conn write limits.
22845 - New consensus params "bwconnrate" and "bwconnburst" to let us
22846 rate-limit client connections as they enter the network. It's
22847 controlled in the consensus so we can turn it on and off for
22848 experiments. It's starting out off. Based on proposal 163.
22850 o Major features (relay selection options):
22851 - Switch to a StrictNodes config option, rather than the previous
22852 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
22853 "StrictExcludeNodes" option.
22854 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
22855 change during a config reload, mark and discard all our origin
22856 circuits. This fix should address edge cases where we change the
22857 config options and but then choose a circuit that we created before
22859 - If EntryNodes or ExitNodes are set, be more willing to use an
22860 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
22862 - Make EntryNodes config option much more aggressive even when
22863 StrictNodes is not set. Before it would prepend your requested
22864 entrynodes to your list of guard nodes, but feel free to use others
22865 after that. Now it chooses only from your EntryNodes if any of
22866 those are available, and only falls back to others if a) they're
22867 all down and b) StrictNodes is not set.
22868 - Now we refresh your entry guards from EntryNodes at each consensus
22869 fetch -- rather than just at startup and then they slowly rot as
22870 the network changes.
22873 - Stop bridge directory authorities from answering dbg-stability.txt
22874 directory queries, which would let people fetch a list of all
22875 bridge identities they track. Bugfix on 0.2.1.6-alpha.
22878 - Log a notice when we get a new control connection. Now it's easier
22879 for security-conscious users to recognize when a local application
22880 is knocking on their controller door. Suggested by bug 1196.
22881 - New config option "CircuitStreamTimeout" to override our internal
22882 timeout schedule for how many seconds until we detach a stream from
22883 a circuit and try a new circuit. If your network is particularly
22884 slow, you might want to set this to a number like 60.
22885 - New controller command "getinfo config-text". It returns the
22886 contents that Tor would write if you send it a SAVECONF command,
22887 so the controller can write the file to disk itself.
22888 - New options for SafeLogging to allow scrubbing only log messages
22889 generated while acting as a relay.
22890 - Ship the bridges spec file in the tarball too.
22891 - Avoid a mad rush at the beginning of each month when each client
22892 rotates half of its guards. Instead we spread the rotation out
22893 throughout the month, but we still avoid leaving a precise timestamp
22894 in the state file about when we first picked the guard. Improves
22895 over the behavior introduced in 0.1.2.17.
22897 o Minor bugfixes (compiling):
22898 - Fix compilation on OS X 10.3, which has a stub mlockall() but
22899 hides it. Bugfix on 0.2.2.6-alpha.
22900 - Fix compilation on Solaris by removing support for the
22901 DisableAllSwap config option. Solaris doesn't have an rlimit for
22902 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
22905 o Minor bugfixes (crashes):
22906 - Do not segfault when writing buffer stats when we haven't observed
22907 a single circuit to report about. Found by Fabian Lanze. Bugfix on
22909 - If we're in the pathological case where there's no exit bandwidth
22910 but there is non-exit bandwidth, or no guard bandwidth but there
22911 is non-guard bandwidth, don't crash during path selection. Bugfix
22913 - Fix an impossible-to-actually-trigger buffer overflow in relay
22914 descriptor generation. Bugfix on 0.1.0.15.
22916 o Minor bugfixes (privacy):
22917 - Fix an instance where a Tor directory mirror might accidentally
22918 log the IP address of a misbehaving Tor client. Bugfix on
22920 - Don't list Windows capabilities in relay descriptors. We never made
22921 use of them, and maybe it's a bad idea to publish them. Bugfix
22924 o Minor bugfixes (other):
22925 - Resolve an edge case in path weighting that could make us misweight
22926 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
22927 - Fix statistics on client numbers by country as seen by bridges that
22928 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
22929 intervals instead of variable 12-to-48-hour intervals.
22930 - After we free an internal connection structure, overwrite it
22931 with a different memory value than we use for overwriting a freed
22932 internal circuit structure. Should help with debugging. Suggested
22934 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
22937 o Removed features:
22938 - Remove the HSAuthorityRecordStats option that version 0 hidden
22939 service authorities could have used to track statistics of overall
22940 hidden service usage.
22943 Changes in version 0.2.1.22 - 2010-01-19
22944 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
22945 authorities -- it would tell you its whole history of bridge descriptors
22946 if you make the right directory request. This stable update also
22947 rotates two of the seven v3 directory authority keys and locations.
22949 o Directory authority changes:
22950 - Rotate keys (both v3 identity and relay identity) for moria1
22954 - Stop bridge directory authorities from answering dbg-stability.txt
22955 directory queries, which would let people fetch a list of all
22956 bridge identities they track. Bugfix on 0.2.1.6-alpha.
22959 Changes in version 0.2.1.21 - 2009-12-21
22960 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
22961 library. If you use Tor on Linux / Unix and you're getting SSL
22962 renegotiation errors, upgrading should help. We also recommend an
22963 upgrade if you're an exit relay.
22966 - Work around a security feature in OpenSSL 0.9.8l that prevents our
22967 handshake from working unless we explicitly tell OpenSSL that we
22968 are using SSL renegotiation safely. We are, of course, but OpenSSL
22969 0.9.8l won't work unless we say we are.
22970 - Avoid crashing if the client is trying to upload many bytes and the
22971 circuit gets torn down at the same time, or if the flip side
22972 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
22975 - Do not refuse to learn about authority certs and v2 networkstatus
22976 documents that are older than the latest consensus. This bug might
22977 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
22978 Spotted and fixed by xmux.
22979 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
22980 trigger platform-specific option misparsing case found by Coverity
22982 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
22983 trigger assert. Fixes bug 1173.
22986 Changes in version 0.2.2.6-alpha - 2009-11-19
22987 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
22988 support for the new lower-footprint "microdescriptor" directory design,
22989 future-proofing our consensus format against new hash functions or
22990 other changes, and an Android port. It also makes Tor compatible with
22991 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
22994 - Directory authorities can now create, vote on, and serve multiple
22995 parallel formats of directory data as part of their voting process.
22996 Partially implements Proposal 162: "Publish the consensus in
22998 - Directory authorities can now agree on and publish small summaries
22999 of router information that clients can use in place of regular
23000 server descriptors. This transition will eventually allow clients
23001 to use far less bandwidth for downloading information about the
23002 network. Begins the implementation of Proposal 158: "Clients
23003 download consensus + microdescriptors".
23004 - The directory voting system is now extensible to use multiple hash
23005 algorithms for signatures and resource selection. Newer formats
23006 are signed with SHA256, with a possibility for moving to a better
23007 hash algorithm in the future.
23008 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
23009 current and future memory pages via mlockall(). On supported
23010 platforms (modern Linux and probably BSD but not Windows or OS X),
23011 this should effectively disable any and all attempts to page out
23012 memory. This option requires that you start your Tor as root --
23013 if you use DisableAllSwap, please consider using the User option
23014 to properly reduce the privileges of your Tor.
23015 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
23016 to help Tor build correctly for Android phones.
23019 - Work around a security feature in OpenSSL 0.9.8l that prevents our
23020 handshake from working unless we explicitly tell OpenSSL that we
23021 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
23022 won't work unless we say we are.
23025 - Fix a crash bug when trying to initialize the evdns module in
23026 Libevent 2. Bugfix on 0.2.1.16-rc.
23027 - Stop logging at severity 'warn' when some other Tor client tries
23028 to establish a circuit with us using weak DH keys. It's a protocol
23029 violation, but that doesn't mean ordinary users need to hear about
23030 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
23031 - Do not refuse to learn about authority certs and v2 networkstatus
23032 documents that are older than the latest consensus. This bug might
23033 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
23034 Spotted and fixed by xmux.
23035 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
23036 - If all authorities restart at once right before a consensus vote,
23037 nobody will vote about "Running", and clients will get a consensus
23038 with no usable relays. Instead, authorities refuse to build a
23039 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
23040 - If your relay can't keep up with the number of incoming create
23041 cells, it would log one warning per failure into your logs. Limit
23042 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
23043 - Bridges now use "reject *:*" as their default exit policy. Bugfix
23044 on 0.2.0.3-alpha; fixes bug 1113.
23045 - Fix a memory leak on directory authorities during voting that was
23046 introduced in 0.2.2.1-alpha. Found via valgrind.
23049 Changes in version 0.2.1.20 - 2009-10-15
23050 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
23051 services at once, prepares for more performance improvements, and
23052 fixes a bunch of smaller bugs.
23054 The Windows and OS X bundles also include a more recent Vidalia,
23055 and switch from Privoxy to Polipo.
23057 The OS X installers are now drag and drop. It's best to un-install
23058 Tor/Vidalia and then install this new bundle, rather than upgrade. If
23059 you want to upgrade, you'll need to update the paths for Tor and Polipo
23060 in the Vidalia Settings window.
23063 - Send circuit or stream sendme cells when our window has decreased
23064 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
23065 by Karsten when testing the "reduce circuit window" performance
23066 patch. Bugfix on the 54th commit on Tor -- from July 2002,
23067 before the release of Tor 0.0.0. This is the new winner of the
23069 - Fix a remotely triggerable memory leak when a consensus document
23070 contains more than one signature from the same voter. Bugfix on
23072 - Avoid segfault in rare cases when finishing an introduction circuit
23073 as a client and finding out that we don't have an introduction key
23074 for it. Fixes bug 1073. Reported by Aaron Swartz.
23077 - Tor now reads the "circwindow" parameter out of the consensus,
23078 and uses that value for its circuit package window rather than the
23079 default of 1000 cells. Begins the implementation of proposal 168.
23081 o New directory authorities:
23082 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
23084 - Move moria1 and tonga to alternate IP addresses.
23087 - Fix a signed/unsigned compile warning in 0.2.1.19.
23088 - Fix possible segmentation fault on directory authorities. Bugfix on
23090 - Fix an extremely rare infinite recursion bug that could occur if
23091 we tried to log a message after shutting down the log subsystem.
23092 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
23093 - Fix an obscure bug where hidden services on 64-bit big-endian
23094 systems might mis-read the timestamp in v3 introduce cells, and
23095 refuse to connect back to the client. Discovered by "rotor".
23096 Bugfix on 0.2.1.6-alpha.
23097 - We were triggering a CLOCK_SKEW controller status event whenever
23098 we connect via the v2 connection protocol to any relay that has
23099 a wrong clock. Instead, we should only inform the controller when
23100 it's a trusted authority that claims our clock is wrong. Bugfix
23101 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
23102 - We were telling the controller about CHECKING_REACHABILITY and
23103 REACHABILITY_FAILED status events whenever we launch a testing
23104 circuit or notice that one has failed. Instead, only tell the
23105 controller when we want to inform the user of overall success or
23106 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
23108 - Don't warn when we're using a circuit that ends with a node
23109 excluded in ExcludeExitNodes, but the circuit is not used to access
23110 the outside world. This should help fix bug 1090. Bugfix on
23112 - Work around a small memory leak in some versions of OpenSSL that
23113 stopped the memory used by the hostname TLS extension from being
23117 - Add a "getinfo status/accepted-server-descriptor" controller
23118 command, which is the recommended way for controllers to learn
23119 whether our server descriptor has been successfully received by at
23120 least on directory authority. Un-recommend good-server-descriptor
23121 getinfo and status events until we have a better design for them.
23124 Changes in version 0.2.2.5-alpha - 2009-10-11
23125 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
23128 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
23130 o Directory authorities:
23131 - Temporarily (just for this release) move dizum to an alternate
23135 Changes in version 0.2.2.4-alpha - 2009-10-10
23136 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
23137 introduces a new unit test framework, shifts directry authority
23138 addresses around to reduce the impact from recent blocking events,
23139 and fixes a few smaller bugs.
23142 - Fix several more asserts in the circuit_build_times code, for
23143 example one that causes Tor to fail to start once we have
23144 accumulated 5000 build times in the state file. Bugfixes on
23145 0.2.2.2-alpha; fixes bug 1108.
23147 o New directory authorities:
23148 - Move moria1 and Tonga to alternate IP addresses.
23151 - Log SSL state transitions at debug level during handshake, and
23152 include SSL states in error messages. This may help debug future
23153 SSL handshake issues.
23154 - Add a new "Handshake" log domain for activities that happen
23155 during the TLS handshake.
23156 - Revert to the "June 3 2009" ip-to-country file. The September one
23157 seems to have removed most US IP addresses.
23158 - Directory authorities now reject Tor relays with versions less than
23159 0.1.2.14. This step cuts out four relays from the current network,
23160 none of which are very big.
23163 - Fix a couple of smaller issues with gathering statistics. Bugfixes
23165 - Fix two memory leaks in the error case of
23166 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
23167 - Don't count one-hop circuits when we're estimating how long it
23168 takes circuits to build on average. Otherwise we'll set our circuit
23169 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
23170 - Directory authorities no longer change their opinion of, or vote on,
23171 whether a router is Running, unless they have themselves been
23172 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
23175 o Code simplifications and refactoring:
23176 - Revise our unit tests to use the "tinytest" framework, so we
23177 can run tests in their own processes, have smarter setup/teardown
23178 code, and so on. The unit test code has moved to its own
23179 subdirectory, and has been split into multiple modules.
23182 Changes in version 0.2.2.3-alpha - 2009-09-23
23183 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
23186 - Fix an overzealous assert in our new circuit build timeout code.
23187 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
23190 - If the networkstatus consensus tells us that we should use a
23191 negative circuit package window, ignore it. Otherwise we'll
23192 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
23195 Changes in version 0.2.2.2-alpha - 2009-09-21
23196 Tor 0.2.2.2-alpha introduces our latest performance improvement for
23197 clients: Tor tracks the average time it takes to build a circuit, and
23198 avoids using circuits that take too long to build. For fast connections,
23199 this feature can cut your expected latency in half. For slow or flaky
23200 connections, it could ruin your Tor experience. Let us know if it does!
23203 - Tor now tracks how long it takes to build client-side circuits
23204 over time, and adapts its timeout to local network performance.
23205 Since a circuit that takes a long time to build will also provide
23206 bad performance, we get significant latency improvements by
23207 discarding the slowest 20% of circuits. Specifically, Tor creates
23208 circuits more aggressively than usual until it has enough data
23209 points for a good timeout estimate. Implements proposal 151.
23210 We are especially looking for reports (good and bad) from users with
23211 both EDGE and broadband connections that can move from broadband
23212 to EDGE and find out if the build-time data in the .tor/state gets
23213 reset without loss of Tor usability. You should also see a notice
23214 log message telling you that Tor has reset its timeout.
23215 - Directory authorities can now vote on arbitrary integer values as
23216 part of the consensus process. This is designed to help set
23217 network-wide parameters. Implements proposal 167.
23218 - Tor now reads the "circwindow" parameter out of the consensus,
23219 and uses that value for its circuit package window rather than the
23220 default of 1000 cells. Begins the implementation of proposal 168.
23223 - Fix a remotely triggerable memory leak when a consensus document
23224 contains more than one signature from the same voter. Bugfix on
23228 - Fix an extremely rare infinite recursion bug that could occur if
23229 we tried to log a message after shutting down the log subsystem.
23230 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
23231 - Fix parsing for memory or time units given without a space between
23232 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
23233 - A networkstatus vote must contain exactly one signature. Spec
23234 conformance issue. Bugfix on 0.2.0.3-alpha.
23235 - Fix an obscure bug where hidden services on 64-bit big-endian
23236 systems might mis-read the timestamp in v3 introduce cells, and
23237 refuse to connect back to the client. Discovered by "rotor".
23238 Bugfix on 0.2.1.6-alpha.
23239 - We were triggering a CLOCK_SKEW controller status event whenever
23240 we connect via the v2 connection protocol to any relay that has
23241 a wrong clock. Instead, we should only inform the controller when
23242 it's a trusted authority that claims our clock is wrong. Bugfix
23243 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
23244 - We were telling the controller about CHECKING_REACHABILITY and
23245 REACHABILITY_FAILED status events whenever we launch a testing
23246 circuit or notice that one has failed. Instead, only tell the
23247 controller when we want to inform the user of overall success or
23248 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
23250 - Don't warn when we're using a circuit that ends with a node
23251 excluded in ExcludeExitNodes, but the circuit is not used to access
23252 the outside world. This should help fix bug 1090, but more problems
23253 remain. Bugfix on 0.2.1.6-alpha.
23254 - Work around a small memory leak in some versions of OpenSSL that
23255 stopped the memory used by the hostname TLS extension from being
23257 - Make our 'torify' script more portable; if we have only one of
23258 'torsocks' or 'tsocks' installed, don't complain to the user;
23259 and explain our warning about tsocks better.
23262 - Add a "getinfo status/accepted-server-descriptor" controller
23263 command, which is the recommended way for controllers to learn
23264 whether our server descriptor has been successfully received by at
23265 least on directory authority. Un-recommend good-server-descriptor
23266 getinfo and status events until we have a better design for them.
23267 - Update to the "September 4 2009" ip-to-country file.
23270 Changes in version 0.2.2.1-alpha - 2009-08-26
23271 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
23272 Tor clients to bootstrap on networks where only port 80 is reachable,
23273 makes it more straightforward to support hardware crypto accelerators,
23274 and starts the groundwork for gathering stats safely at relays.
23277 - Start the process of disabling ".exit" address notation, since it
23278 can be used for a variety of esoteric application-level attacks
23279 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
23282 o New directory authorities:
23283 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
23287 - New AccelName and AccelDir options add support for dynamic OpenSSL
23288 hardware crypto acceleration engines.
23289 - Tor now supports tunneling all of its outgoing connections over
23290 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
23291 configuration options. Code by Christopher Davis.
23294 - Send circuit or stream sendme cells when our window has decreased
23295 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
23296 by Karsten when testing the "reduce circuit window" performance
23297 patch. Bugfix on the 54th commit on Tor -- from July 2002,
23298 before the release of Tor 0.0.0. This is the new winner of the
23301 o New options for gathering stats safely:
23302 - Directory mirrors that set "DirReqStatistics 1" write statistics
23303 about directory requests to disk every 24 hours. As compared to the
23304 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
23305 1) stats are written to disk exactly every 24 hours; 2) estimated
23306 shares of v2 and v3 requests are determined as mean values, not at
23307 the end of a measurement period; 3) unresolved requests are listed
23308 with country code '??'; 4) directories also measure download times.
23309 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
23310 number of exit streams and transferred bytes per port to disk every
23312 - Relays that set "CellStatistics 1" write statistics on how long
23313 cells spend in their circuit queues to disk every 24 hours.
23314 - Entry nodes that set "EntryStatistics 1" write statistics on the
23315 rough number and origins of connecting clients to disk every 24
23317 - Relays that write any of the above statistics to disk and set
23318 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
23319 their extra-info documents.
23322 - New --digests command-line switch to output the digests of the
23323 source files Tor was built with.
23324 - The "torify" script now uses torsocks where available.
23325 - The memarea code now uses a sentinel value at the end of each area
23326 to make sure nothing writes beyond the end of an area. This might
23327 help debug some conceivable causes of bug 930.
23328 - Time and memory units in the configuration file can now be set to
23329 fractional units. For example, "2.5 GB" is now a valid value for
23331 - Certain Tor clients (such as those behind check.torproject.org) may
23332 want to fetch the consensus in an extra early manner. To enable this
23333 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
23334 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
23335 as only certain clients who must have this information sooner should
23337 - Instead of adding the svn revision to the Tor version string, report
23338 the git commit (when we're building from a git checkout).
23341 - If any of the v3 certs we download are unparseable, we should
23342 actually notice the failure so we don't retry indefinitely. Bugfix
23343 on 0.2.0.x; reported by "rotator".
23344 - If the cached cert file is unparseable, warn but don't exit.
23345 - Fix possible segmentation fault on directory authorities. Bugfix on
23347 - When Tor fails to parse a descriptor of any kind, dump it to disk.
23348 Might help diagnosing bug 1051.
23350 o Deprecated and removed features:
23351 - The controller no longer accepts the old obsolete "addr-mappings/"
23352 or "unregistered-servers-" GETINFO values.
23353 - Hidden services no longer publish version 0 descriptors, and clients
23354 do not request or use version 0 descriptors. However, the old hidden
23355 service authorities still accept and serve version 0 descriptors
23356 when contacted by older hidden services/clients.
23357 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
23358 always on; using them is necessary for correct forward-compatible
23360 - Remove support for .noconnect style addresses. Nobody was using
23361 them, and they provided another avenue for detecting Tor users
23362 via application-level web tricks.
23364 o Packaging changes:
23365 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
23366 installer bundles. See
23367 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
23368 for details of what's new in Vidalia 0.2.3.
23369 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
23370 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
23371 configuration file, rather than the old Privoxy.
23372 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
23373 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
23374 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
23375 better compatibility with OS X 10.6, aka Snow Leopard.
23376 - OS X Vidalia Bundle: The multi-package installer is now replaced
23377 by a simple drag and drop to the /Applications folder. This change
23378 occurred with the upgrade to Vidalia 0.2.3.
23381 Changes in version 0.2.1.19 - 2009-07-28
23382 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
23383 services on Tor 0.2.1.3-alpha through 0.2.1.18.
23386 - Make accessing hidden services on 0.2.1.x work right again.
23387 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
23388 part of patch provided by "optimist".
23391 - When a relay/bridge is writing out its identity key fingerprint to
23392 the "fingerprint" file and to its logs, write it without spaces. Now
23393 it will look like the fingerprints in our bridges documentation,
23394 and confuse fewer users.
23397 - Relays no longer publish a new server descriptor if they change
23398 their MaxAdvertisedBandwidth config option but it doesn't end up
23399 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
23400 fixes bug 1026. Patch from Sebastian.
23401 - Avoid leaking memory every time we get a create cell but we have
23402 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
23403 fixes bug 1034. Reported by BarkerJr.
23406 Changes in version 0.2.1.18 - 2009-07-24
23407 Tor 0.2.1.18 lays the foundations for performance improvements,
23408 adds status events to help users diagnose bootstrap problems, adds
23409 optional authentication/authorization for hidden services, fixes a
23410 variety of potential anonymity problems, and includes a huge pile of
23411 other features and bug fixes.
23414 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
23417 Changes in version 0.2.1.17-rc - 2009-07-07
23418 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
23419 candidate for the 0.2.1.x series. It lays the groundwork for further
23420 client performance improvements, and also fixes a big bug with directory
23421 authorities that were causing them to assign Guard and Stable flags
23424 The Windows bundles also finally include the geoip database that we
23425 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
23426 should actually install Torbutton rather than giving you a cryptic
23427 failure message (oops).
23430 - Clients now use the bandwidth values in the consensus, rather than
23431 the bandwidth values in each relay descriptor. This approach opens
23432 the door to more accurate bandwidth estimates once the directory
23433 authorities start doing active measurements. Implements more of
23437 - When Tor clients restart after 1-5 days, they discard all their
23438 cached descriptors as too old, but they still use the cached
23439 consensus document. This approach is good for robustness, but
23440 bad for performance: since they don't know any bandwidths, they
23441 end up choosing at random rather than weighting their choice by
23442 speed. Fixed by the above feature of putting bandwidths in the
23443 consensus. Bugfix on 0.2.0.x.
23444 - Directory authorities were neglecting to mark relays down in their
23445 internal histories if the relays fall off the routerlist without
23446 ever being found unreachable. So there were relays in the histories
23447 that haven't been seen for eight months, and are listed as being
23448 up for eight months. This wreaked havoc on the "median wfu"
23449 and "median mtbf" calculations, in turn making Guard and Stable
23450 flags very wrong, hurting network performance. Fixes bugs 696 and
23451 969. Bugfix on 0.2.0.6-alpha.
23454 - Serve the DirPortFrontPage page even when we have been approaching
23455 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
23456 - The control port would close the connection before flushing long
23457 replies, such as the network consensus, if a QUIT command was issued
23458 before the reply had completed. Now, the control port flushes all
23459 pending replies before closing the connection. Also fixed a spurious
23460 warning when a QUIT command is issued after a malformed or rejected
23461 AUTHENTICATE command, but before the connection was closed. Patch
23462 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
23463 - When we can't find an intro key for a v2 hidden service descriptor,
23464 fall back to the v0 hidden service descriptor and log a bug message.
23465 Workaround for bug 1024.
23466 - Fix a log message that did not respect the SafeLogging option.
23470 - If we're a relay and we change our IP address, be more verbose
23471 about the reason that made us change. Should help track down
23472 further bugs for relays on dynamic IP addresses.
23475 Changes in version 0.2.0.35 - 2009-06-24
23477 - Avoid crashing in the presence of certain malformed descriptors.
23478 Found by lark, and by automated fuzzing.
23479 - Fix an edge case where a malicious exit relay could convince a
23480 controller that the client's DNS question resolves to an internal IP
23481 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
23484 - Finally fix the bug where dynamic-IP relays disappear when their
23485 IP address changes: directory mirrors were mistakenly telling
23486 them their old address if they asked via begin_dir, so they
23487 never got an accurate answer about their new address, so they
23488 just vanished after a day. For belt-and-suspenders, relays that
23489 don't set Address in their config now avoid using begin_dir for
23490 all direct connections. Should fix bugs 827, 883, and 900.
23491 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
23492 that would occur on some exit nodes when DNS failures and timeouts
23493 occurred in certain patterns. Fix for bug 957.
23496 - When starting with a cache over a few days old, do not leak
23497 memory for the obsolete router descriptors in it. Bugfix on
23498 0.2.0.33; fixes bug 672.
23499 - Hidden service clients didn't use a cached service descriptor that
23500 was older than 15 minutes, but wouldn't fetch a new one either,
23501 because there was already one in the cache. Now, fetch a v2
23502 descriptor unless the same descriptor was added to the cache within
23503 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
23506 Changes in version 0.2.1.16-rc - 2009-06-20
23507 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
23508 a bunch of minor bugs.
23511 - Fix an edge case where a malicious exit relay could convince a
23512 controller that the client's DNS question resolves to an internal IP
23513 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
23515 o Major performance improvements (on 0.2.0.x):
23516 - Disable and refactor some debugging checks that forced a linear scan
23517 over the whole server-side DNS cache. These accounted for over 50%
23518 of CPU time on a relatively busy exit node's gprof profile. Found
23520 - Disable some debugging checks that appeared in exit node profile
23524 - Update to the "June 3 2009" ip-to-country file.
23525 - Do not have tor-resolve automatically refuse all .onion addresses;
23526 if AutomapHostsOnResolve is set in your torrc, this will work fine.
23528 o Minor bugfixes (on 0.2.0.x):
23529 - Log correct error messages for DNS-related network errors on
23531 - Fix a race condition that could cause crashes or memory corruption
23532 when running as a server with a controller listening for log
23534 - Avoid crashing when we have a policy specified in a DirPolicy or
23535 SocksPolicy or ReachableAddresses option with ports set on it,
23536 and we re-load the policy. May fix bug 996.
23537 - Hidden service clients didn't use a cached service descriptor that
23538 was older than 15 minutes, but wouldn't fetch a new one either,
23539 because there was already one in the cache. Now, fetch a v2
23540 descriptor unless the same descriptor was added to the cache within
23541 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
23543 o Minor bugfixes (on 0.2.1.x):
23544 - Don't warn users about low port and hibernation mix when they
23545 provide a *ListenAddress directive to fix that. Bugfix on
23547 - When switching back and forth between bridge mode, do not start
23548 gathering GeoIP data until two hours have passed.
23549 - Do not complain that the user has requested an excluded node as
23550 an exit when the node is not really an exit. This could happen
23551 because the circuit was for testing, or an introduction point.
23555 Changes in version 0.2.1.15-rc - 2009-05-25
23556 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
23557 series. It fixes a major bug on fast exit relays, as well as a variety
23558 of more minor bugs.
23560 o Major bugfixes (on 0.2.0.x):
23561 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
23562 that would occur on some exit nodes when DNS failures and timeouts
23563 occurred in certain patterns. Fix for bug 957.
23565 o Minor bugfixes (on 0.2.0.x):
23566 - Actually return -1 in the error case for read_bandwidth_usage().
23567 Harmless bug, since we currently don't care about the return value
23568 anywhere. Bugfix on 0.2.0.9-alpha.
23569 - Provide a more useful log message if bug 977 (related to buffer
23570 freelists) ever reappears, and do not crash right away.
23571 - Fix an assertion failure on 64-bit platforms when we allocated
23572 memory right up to the end of a memarea, then realigned the memory
23573 one step beyond the end. Fixes a possible cause of bug 930.
23574 - Protect the count of open sockets with a mutex, so we can't
23575 corrupt it when two threads are closing or opening sockets at once.
23576 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
23577 - Don't allow a bridge to publish its router descriptor to a
23578 non-bridge directory authority. Fixes part of bug 932.
23579 - When we change to or from being a bridge, reset our counts of
23580 client usage by country. Fixes bug 932.
23581 - Fix a bug that made stream bandwidth get misreported to the
23583 - Stop using malloc_usable_size() to use more area than we had
23584 actually allocated: it was safe, but made valgrind really unhappy.
23585 - Fix a memory leak when v3 directory authorities load their keys
23586 and cert from disk. Bugfix on 0.2.0.1-alpha.
23588 o Minor bugfixes (on 0.2.1.x):
23589 - Fix use of freed memory when deciding to mark a non-addable
23590 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
23593 Changes in version 0.2.1.14-rc - 2009-04-12
23594 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
23595 series. It begins fixing some major performance problems, and also
23596 finally addresses the bug that was causing relays on dynamic IP
23597 addresses to fall out of the directory.
23600 - Clients replace entry guards that were chosen more than a few months
23601 ago. This change should significantly improve client performance,
23602 especially once more people upgrade, since relays that have been
23603 a guard for a long time are currently overloaded.
23605 o Major bugfixes (on 0.2.0):
23606 - Finally fix the bug where dynamic-IP relays disappear when their
23607 IP address changes: directory mirrors were mistakenly telling
23608 them their old address if they asked via begin_dir, so they
23609 never got an accurate answer about their new address, so they
23610 just vanished after a day. For belt-and-suspenders, relays that
23611 don't set Address in their config now avoid using begin_dir for
23612 all direct connections. Should fix bugs 827, 883, and 900.
23613 - Relays were falling out of the networkstatus consensus for
23614 part of a day if they changed their local config but the
23615 authorities discarded their new descriptor as "not sufficiently
23616 different". Now directory authorities accept a descriptor as changed
23617 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
23618 patch by Sebastian.
23619 - Avoid crashing in the presence of certain malformed descriptors.
23620 Found by lark, and by automated fuzzing.
23623 - When generating circuit events with verbose nicknames for
23624 controllers, try harder to look up nicknames for routers on a
23625 circuit. (Previously, we would look in the router descriptors we had
23626 for nicknames, but not in the consensus.) Partial fix for bug 941.
23627 - If the bridge config line doesn't specify a port, assume 443.
23628 This makes bridge lines a bit smaller and easier for users to
23630 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
23631 bytes (aka 20KB/s), to match our documentation. Also update
23632 directory authorities so they always assign the Fast flag to relays
23633 with 20KB/s of capacity. Now people running relays won't suddenly
23634 find themselves not seeing any use, if the network gets faster
23636 - Update to the "April 3 2009" ip-to-country file.
23639 - Avoid trying to print raw memory to the logs when we decide to
23640 give up on downloading a given relay descriptor. Bugfix on
23642 - In tor-resolve, when the Tor client to use is specified by
23643 <hostname>:<port>, actually use the specified port rather than
23644 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
23645 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
23646 - When starting with a cache over a few days old, do not leak
23647 memory for the obsolete router descriptors in it. Bugfix on
23649 - Avoid double-free on list of successfully uploaded hidden
23650 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
23651 - Change memarea_strndup() implementation to work even when
23652 duplicating a string at the end of a page. This bug was
23653 harmless for now, but could have meant crashes later. Fix by
23654 lark. Bugfix on 0.2.1.1-alpha.
23655 - Limit uploaded directory documents to be 16M rather than 500K.
23656 The directory authorities were refusing v3 consensus votes from
23657 other authorities, since the votes are now 504K. Fixes bug 959;
23658 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
23659 - Directory authorities should never send a 503 "busy" response to
23660 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
23664 Changes in version 0.2.1.13-alpha - 2009-03-09
23665 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
23666 cleanups. We're finally getting close to a release candidate.
23669 - Correctly update the list of which countries we exclude as
23670 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
23671 lark. Bugfix on 0.2.1.6-alpha.
23673 o Minor bugfixes (on 0.2.0.x and earlier):
23674 - Automatically detect MacOSX versions earlier than 10.4.0, and
23675 disable kqueue from inside Tor when running with these versions.
23676 We previously did this from the startup script, but that was no
23677 help to people who didn't use the startup script. Resolves bug 863.
23678 - When we had picked an exit node for a connection, but marked it as
23679 "optional", and it turned out we had no onion key for the exit,
23680 stop wanting that exit and try again. This situation may not
23681 be possible now, but will probably become feasible with proposal
23682 158. Spotted by rovv. Fixes another case of bug 752.
23683 - Clients no longer cache certificates for authorities they do not
23684 recognize. Bugfix on 0.2.0.9-alpha.
23685 - When we can't transmit a DNS request due to a network error, retry
23686 it after a while, and eventually transmit a failing response to
23687 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
23688 - If the controller claimed responsibility for a stream, but that
23689 stream never finished making its connection, it would live
23690 forever in circuit_wait state. Now we close it after SocksTimeout
23691 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
23692 - Drop begin cells to a hidden service if they come from the middle
23693 of a circuit. Patch from lark.
23694 - When we erroneously receive two EXTEND cells for the same circuit
23695 ID on the same connection, drop the second. Patch from lark.
23696 - Fix a crash that occurs on exit nodes when a nameserver request
23697 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
23698 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
23700 - Do not assume that a stack-allocated character array will be
23701 64-bit aligned on platforms that demand that uint64_t access is
23702 aligned. Possible fix for bug 604.
23703 - Parse dates and IPv4 addresses in a locale- and libc-independent
23704 manner, to avoid platform-dependent behavior on malformed input.
23705 - Build correctly when configured to build outside the main source
23706 path. Patch from Michael Gold.
23707 - We were already rejecting relay begin cells with destination port
23708 of 0. Now also reject extend cells with destination port or address
23709 of 0. Suggested by lark.
23711 o Minor bugfixes (on 0.2.1.x):
23712 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
23713 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
23714 - If we're an exit node, scrub the IP address to which we are exiting
23715 in the logs. Bugfix on 0.2.1.8-alpha.
23718 - On Linux, use the prctl call to re-enable core dumps when the user
23720 - New controller event NEWCONSENSUS that lists the networkstatus
23721 lines for every recommended relay. Now controllers like Torflow
23722 can keep up-to-date on which relays they should be using.
23723 - Update to the "February 26 2009" ip-to-country file.
23726 Changes in version 0.2.0.34 - 2009-02-08
23727 Tor 0.2.0.34 features several more security-related fixes. You should
23728 upgrade, especially if you run an exit relay (remote crash) or a
23729 directory authority (remote infinite loop), or you're on an older
23730 (pre-XP) or not-recently-patched Windows (remote exploit).
23732 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
23733 have many known flaws, and nobody should be using them. You should
23734 upgrade. If you're using a Linux or BSD and its packages are obsolete,
23735 stop using those packages and upgrade anyway.
23738 - Fix an infinite-loop bug on handling corrupt votes under certain
23739 circumstances. Bugfix on 0.2.0.8-alpha.
23740 - Fix a temporary DoS vulnerability that could be performed by
23741 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
23742 - Avoid a potential crash on exit nodes when processing malformed
23743 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
23744 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
23745 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
23748 - Fix compilation on systems where time_t is a 64-bit integer.
23749 Patch from Matthias Drochner.
23750 - Don't consider expiring already-closed client connections. Fixes
23751 bug 893. Bugfix on 0.0.2pre20.
23754 Changes in version 0.2.1.12-alpha - 2009-02-08
23755 Tor 0.2.1.12-alpha features several more security-related fixes. You
23756 should upgrade, especially if you run an exit relay (remote crash) or
23757 a directory authority (remote infinite loop), or you're on an older
23758 (pre-XP) or not-recently-patched Windows (remote exploit). It also
23759 includes a big pile of minor bugfixes and cleanups.
23762 - Fix an infinite-loop bug on handling corrupt votes under certain
23763 circumstances. Bugfix on 0.2.0.8-alpha.
23764 - Fix a temporary DoS vulnerability that could be performed by
23765 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
23766 - Avoid a potential crash on exit nodes when processing malformed
23767 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
23770 - Let controllers actually ask for the "clients_seen" event for
23771 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
23772 reported by Matt Edman.
23773 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
23775 - Fix a bug in address parsing that was preventing bridges or hidden
23776 service targets from being at IPv6 addresses.
23777 - Solve a bug that kept hardware crypto acceleration from getting
23778 enabled when accounting was turned on. Fixes bug 907. Bugfix on
23780 - Remove a bash-ism from configure.in to build properly on non-Linux
23781 platforms. Bugfix on 0.2.1.1-alpha.
23782 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
23783 headers. Bugfix on 0.2.0.10-alpha.
23784 - Don't consider expiring already-closed client connections. Fixes
23785 bug 893. Bugfix on 0.0.2pre20.
23786 - Fix another interesting corner-case of bug 891 spotted by rovv:
23787 Previously, if two hosts had different amounts of clock drift, and
23788 one of them created a new connection with just the wrong timing,
23789 the other might decide to deprecate the new connection erroneously.
23790 Bugfix on 0.1.1.13-alpha.
23791 - Resolve a very rare crash bug that could occur when the user forced
23792 a nameserver reconfiguration during the middle of a nameserver
23793 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
23794 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
23795 Bugfix on 0.2.1.7-alpha.
23796 - If we're using bridges and our network goes away, be more willing
23797 to forgive our bridges and try again when we get an application
23798 request. Bugfix on 0.2.0.x.
23801 - Support platforms where time_t is 64 bits long. (Congratulations,
23802 NetBSD!) Patch from Matthias Drochner.
23803 - Add a 'getinfo status/clients-seen' controller command, in case
23804 controllers want to hear clients_seen events but connect late.
23807 - Disable GCC's strict alias optimization by default, to avoid the
23808 likelihood of its introducing subtle bugs whenever our code violates
23809 the letter of C99's alias rules.
23812 Changes in version 0.2.0.33 - 2009-01-21
23813 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
23814 useful to users. It also finally fixes a bug where a relay or client
23815 that's been off for many days would take a long time to bootstrap.
23817 This update also fixes an important security-related bug reported by
23818 Ilja van Sprundel. You should upgrade. (We'll send out more details
23819 about the bug once people have had some time to upgrade.)
23822 - Fix a heap-corruption bug that may be remotely triggerable on
23823 some platforms. Reported by Ilja van Sprundel.
23826 - When a stream at an exit relay is in state "resolving" or
23827 "connecting" and it receives an "end" relay cell, the exit relay
23828 would silently ignore the end cell and not close the stream. If
23829 the client never closes the circuit, then the exit relay never
23830 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
23831 reported by "wood".
23832 - When sending CREATED cells back for a given circuit, use a 64-bit
23833 connection ID to find the right connection, rather than an addr:port
23834 combination. Now that we can have multiple OR connections between
23835 the same ORs, it is no longer possible to use addr:port to uniquely
23836 identify a connection.
23837 - Bridge relays that had DirPort set to 0 would stop fetching
23838 descriptors shortly after startup, and then briefly resume
23839 after a new bandwidth test and/or after publishing a new bridge
23840 descriptor. Bridge users that try to bootstrap from them would
23841 get a recent networkstatus but would get descriptors from up to
23842 18 hours earlier, meaning most of the descriptors were obsolete
23843 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
23844 - Prevent bridge relays from serving their 'extrainfo' document
23845 to anybody who asks, now that extrainfo docs include potentially
23846 sensitive aggregated client geoip summaries. Bugfix on
23848 - If the cached networkstatus consensus is more than five days old,
23849 discard it rather than trying to use it. In theory it could be
23850 useful because it lists alternate directory mirrors, but in practice
23851 it just means we spend many minutes trying directory mirrors that
23852 are long gone from the network. Also discard router descriptors as
23853 we load them if they are more than five days old, since the onion
23854 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
23857 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
23858 could make gcc generate non-functional binary search code. Bugfix
23860 - Build correctly on platforms without socklen_t.
23861 - Compile without warnings on solaris.
23862 - Avoid potential crash on internal error during signature collection.
23863 Fixes bug 864. Patch from rovv.
23864 - Correct handling of possible malformed authority signing key
23865 certificates with internal signature types. Fixes bug 880.
23866 Bugfix on 0.2.0.3-alpha.
23867 - Fix a hard-to-trigger resource leak when logging credential status.
23869 - When we can't initialize DNS because the network is down, do not
23870 automatically stop Tor from starting. Instead, we retry failed
23871 dns_init() every 10 minutes, and change the exit policy to reject
23872 *:* until one succeeds. Fixes bug 691.
23873 - Use 64 bits instead of 32 bits for connection identifiers used with
23874 the controller protocol, to greatly reduce risk of identifier reuse.
23875 - When we're choosing an exit node for a circuit, and we have
23876 no pending streams, choose a good general exit rather than one that
23877 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
23878 - Fix another case of assuming, when a specific exit is requested,
23879 that we know more than the user about what hosts it allows.
23880 Fixes one case of bug 752. Patch from rovv.
23881 - Clip the MaxCircuitDirtiness config option to a minimum of 10
23882 seconds. Warn the user if lower values are given in the
23883 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
23884 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
23885 user if lower values are given in the configuration. Bugfix on
23886 0.1.1.17-rc. Patch by Sebastian.
23887 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
23888 the cache because we already had a v0 descriptor with the same ID.
23889 Bugfix on 0.2.0.18-alpha.
23890 - Fix a race condition when freeing keys shared between main thread
23891 and CPU workers that could result in a memory leak. Bugfix on
23892 0.1.0.1-rc. Fixes bug 889.
23893 - Send a valid END cell back when a client tries to connect to a
23894 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
23895 840. Patch from rovv.
23896 - Check which hops rendezvous stream cells are associated with to
23897 prevent possible guess-the-streamid injection attacks from
23898 intermediate hops. Fixes another case of bug 446. Based on patch
23900 - If a broken client asks a non-exit router to connect somewhere,
23901 do not even do the DNS lookup before rejecting the connection.
23902 Fixes another case of bug 619. Patch from rovv.
23903 - When a relay gets a create cell it can't decrypt (e.g. because it's
23904 using the wrong onion key), we were dropping it and letting the
23905 client time out. Now actually answer with a destroy cell. Fixes
23906 bug 904. Bugfix on 0.0.2pre8.
23908 o Minor bugfixes (hidden services):
23909 - Do not throw away existing introduction points on SIGHUP. Bugfix on
23910 0.0.6pre1. Patch by Karsten. Fixes bug 874.
23913 - Report the case where all signatures in a detached set are rejected
23914 differently than the case where there is an error handling the
23916 - When we realize that another process has modified our cached
23917 descriptors, print out a more useful error message rather than
23918 triggering an assertion. Fixes bug 885. Patch from Karsten.
23919 - Implement the 0x20 hack to better resist DNS poisoning: set the
23920 case on outgoing DNS requests randomly, and reject responses that do
23921 not match the case correctly. This logic can be disabled with the
23922 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
23923 of servers that do not reliably preserve case in replies. See
23924 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
23926 - Check DNS replies for more matching fields to better resist DNS
23928 - Never use OpenSSL compression: it wastes RAM and CPU trying to
23929 compress cells, which are basically all encrypted, compressed, or
23933 Changes in version 0.2.1.11-alpha - 2009-01-20
23934 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
23935 week it will take a long time to bootstrap again" bug. It also fixes
23936 an important security-related bug reported by Ilja van Sprundel. You
23937 should upgrade. (We'll send out more details about the bug once people
23938 have had some time to upgrade.)
23941 - Fix a heap-corruption bug that may be remotely triggerable on
23942 some platforms. Reported by Ilja van Sprundel.
23945 - Discard router descriptors as we load them if they are more than
23946 five days old. Otherwise if Tor is off for a long time and then
23947 starts with cached descriptors, it will try to use the onion
23948 keys in those obsolete descriptors when building circuits. Bugfix
23949 on 0.2.0.x. Fixes bug 887.
23952 - Try to make sure that the version of Libevent we're running with
23953 is binary-compatible with the one we built with. May address bug
23955 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
23956 for bug 905. Bugfix on 0.2.1.7-alpha.
23957 - Add a new --enable-local-appdata configuration switch to change
23958 the default location of the datadir on win32 from APPDATA to
23959 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
23960 entirely. Patch from coderman.
23963 - Make outbound DNS packets respect the OutboundBindAddress setting.
23964 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
23965 - When our circuit fails at the first hop (e.g. we get a destroy
23966 cell back), avoid using that OR connection anymore, and also
23967 tell all the one-hop directory requests waiting for it that they
23968 should fail. Bugfix on 0.2.1.3-alpha.
23969 - In the torify(1) manpage, mention that tsocks will leak your
23973 Changes in version 0.2.1.10-alpha - 2009-01-06
23974 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
23975 would make the bridge relay not so useful if it had DirPort set to 0,
23976 and one that could let an attacker learn a little bit of information
23977 about the bridge's users), and a bug that would cause your Tor relay
23978 to ignore a circuit create request it can't decrypt (rather than reply
23979 with an error). It also fixes a wide variety of other bugs.
23982 - If the cached networkstatus consensus is more than five days old,
23983 discard it rather than trying to use it. In theory it could
23984 be useful because it lists alternate directory mirrors, but in
23985 practice it just means we spend many minutes trying directory
23986 mirrors that are long gone from the network. Helps bug 887 a bit;
23988 - Bridge relays that had DirPort set to 0 would stop fetching
23989 descriptors shortly after startup, and then briefly resume
23990 after a new bandwidth test and/or after publishing a new bridge
23991 descriptor. Bridge users that try to bootstrap from them would
23992 get a recent networkstatus but would get descriptors from up to
23993 18 hours earlier, meaning most of the descriptors were obsolete
23994 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
23995 - Prevent bridge relays from serving their 'extrainfo' document
23996 to anybody who asks, now that extrainfo docs include potentially
23997 sensitive aggregated client geoip summaries. Bugfix on
24001 - New controller event "clients_seen" to report a geoip-based summary
24002 of which countries we've seen clients from recently. Now controllers
24003 like Vidalia can show bridge operators that they're actually making
24005 - Build correctly against versions of OpenSSL 0.9.8 or later built
24006 without support for deprecated functions.
24007 - Update to the "December 19 2008" ip-to-country file.
24009 o Minor bugfixes (on 0.2.0.x):
24010 - Authorities now vote for the Stable flag for any router whose
24011 weighted MTBF is at least 5 days, regardless of the mean MTBF.
24012 - Do not remove routers as too old if we do not have any consensus
24013 document. Bugfix on 0.2.0.7-alpha.
24014 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
24015 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
24016 - When an exit relay resolves a stream address to a local IP address,
24017 do not just keep retrying that same exit relay over and
24018 over. Instead, just close the stream. Addresses bug 872. Bugfix
24019 on 0.2.0.32. Patch from rovv.
24020 - If a hidden service sends us an END cell, do not consider
24021 retrying the connection; just close it. Patch from rovv.
24022 - When we made bridge authorities stop serving bridge descriptors over
24023 unencrypted links, we also broke DirPort reachability testing for
24024 bridges. So bridges with a non-zero DirPort were printing spurious
24025 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
24026 - When a relay gets a create cell it can't decrypt (e.g. because it's
24027 using the wrong onion key), we were dropping it and letting the
24028 client time out. Now actually answer with a destroy cell. Fixes
24029 bug 904. Bugfix on 0.0.2pre8.
24030 - Squeeze 2-5% out of client performance (according to oprofile) by
24031 improving the implementation of some policy-manipulation functions.
24033 o Minor bugfixes (on 0.2.1.x):
24034 - Make get_interface_address() function work properly again; stop
24035 guessing the wrong parts of our address as our address.
24036 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
24037 send on that circuit. Otherwise we might violate the proposal-110
24038 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
24040 - When we're sending non-EXTEND cells to the first hop in a circuit,
24041 for example to use an encrypted directory connection, we don't need
24042 to use RELAY_EARLY cells: the first hop knows what kind of cell
24043 it is, and nobody else can even see the cell type. Conserving
24044 RELAY_EARLY cells makes it easier to cannibalize circuits like
24046 - Stop logging nameserver addresses in reverse order.
24047 - If we are retrying a directory download slowly over and over, do
24048 not automatically give up after the 254th failure. Bugfix on
24050 - Resume reporting accurate "stream end" reasons to the local control
24051 port. They were lost in the changes for Proposal 148. Bugfix on
24054 o Deprecated and removed features:
24055 - The old "tor --version --version" command, which would print out
24056 the subversion "Id" of most of the source files, is now removed. It
24057 turned out to be less useful than we'd expected, and harder to
24060 o Code simplifications and refactoring:
24061 - Change our header file guard macros to be less likely to conflict
24062 with system headers. Adam Langley noticed that we were conflicting
24063 with log.h on Android.
24064 - Tool-assisted documentation cleanup. Nearly every function or
24065 static variable in Tor should have its own documentation now.
24068 Changes in version 0.2.1.9-alpha - 2008-12-25
24069 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
24071 o New directory authorities:
24072 - gabelmoo (the authority run by Karsten Loesing) now has a new
24076 - Never use a connection with a mismatched address to extend a
24077 circuit, unless that connection is canonical. A canonical
24078 connection is one whose address is authenticated by the router's
24079 identity key, either in a NETINFO cell or in a router descriptor.
24080 - Avoid a possible memory corruption bug when receiving hidden service
24081 descriptors. Bugfix on 0.2.1.6-alpha.
24084 - Fix a logic error that would automatically reject all but the first
24085 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
24086 part of bug 813/868. Bug spotted by coderman.
24087 - When a stream at an exit relay is in state "resolving" or
24088 "connecting" and it receives an "end" relay cell, the exit relay
24089 would silently ignore the end cell and not close the stream. If
24090 the client never closes the circuit, then the exit relay never
24091 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
24092 reported by "wood".
24093 - When we can't initialize DNS because the network is down, do not
24094 automatically stop Tor from starting. Instead, retry failed
24095 dns_init() every 10 minutes, and change the exit policy to reject
24096 *:* until one succeeds. Fixes bug 691.
24099 - Give a better error message when an overzealous init script says
24100 "sudo -u username tor --user username". Makes Bug 882 easier for
24102 - When a directory authority gives us a new guess for our IP address,
24103 log which authority we used. Hopefully this will help us debug
24104 the recent complaints about bad IP address guesses.
24105 - Detect svn revision properly when we're using git-svn.
24106 - Try not to open more than one descriptor-downloading connection
24107 to an authority at once. This should reduce load on directory
24108 authorities. Fixes bug 366.
24109 - Add cross-certification to newly generated certificates, so that
24110 a signing key is enough information to look up a certificate.
24111 Partial implementation of proposal 157.
24112 - Start serving certificates by <identity digest, signing key digest>
24113 pairs. Partial implementation of proposal 157.
24114 - Clients now never report any stream end reason except 'MISC'.
24115 Implements proposal 148.
24116 - On platforms with a maximum syslog string length, truncate syslog
24117 messages to that length ourselves, rather than relying on the
24118 system to do it for us.
24119 - Optimize out calls to time(NULL) that occur for every IO operation,
24120 or for every cell. On systems where time() is a slow syscall,
24121 this fix will be slightly helpful.
24122 - Exit servers can now answer resolve requests for ip6.arpa addresses.
24123 - When we download a descriptor that we then immediately (as
24124 a directory authority) reject, do not retry downloading it right
24125 away. Should save some bandwidth on authorities. Fix for bug
24126 888. Patch by Sebastian Hahn.
24127 - When a download gets us zero good descriptors, do not notify
24128 Tor that new directory information has arrived.
24129 - Avoid some nasty corner cases in the logic for marking connections
24130 as too old or obsolete or noncanonical for circuits. Partial
24133 o Minor features (controller):
24134 - New CONSENSUS_ARRIVED event to note when a new consensus has
24135 been fetched and validated.
24136 - When we realize that another process has modified our cached
24137 descriptors file, print out a more useful error message rather
24138 than triggering an assertion. Fixes bug 885. Patch from Karsten.
24139 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
24140 controllers to prevent SIGHUP from reloading the
24141 configuration. Fixes bug 856.
24144 - Resume using the correct "REASON=" stream when telling the
24145 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
24146 - When a canonical connection appears later in our internal list
24147 than a noncanonical one for a given OR ID, always use the
24148 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
24150 - Clip the MaxCircuitDirtiness config option to a minimum of 10
24151 seconds. Warn the user if lower values are given in the
24152 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
24153 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
24154 user if lower values are given in the configuration. Bugfix on
24155 0.1.1.17-rc. Patch by Sebastian.
24156 - Fix a race condition when freeing keys shared between main thread
24157 and CPU workers that could result in a memory leak. Bugfix on
24158 0.1.0.1-rc. Fixes bug 889.
24160 o Minor bugfixes (hidden services):
24161 - Do not throw away existing introduction points on SIGHUP (bugfix on
24162 0.0.6pre1); also, do not stall hidden services because we're
24163 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
24164 by John Brooks. Patch by Karsten. Fixes bug 874.
24165 - Fix a memory leak when we decline to add a v2 rendezvous
24166 descriptor to the cache because we already had a v0 descriptor
24167 with the same ID. Bugfix on 0.2.0.18-alpha.
24169 o Deprecated and removed features:
24170 - RedirectExits has been removed. It was deprecated since
24172 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
24173 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
24174 - Cell pools are now always enabled; --disable-cell-pools is ignored.
24176 o Code simplifications and refactoring:
24177 - Rename the confusing or_is_obsolete field to the more appropriate
24178 is_bad_for_new_circs, and move it to or_connection_t where it
24180 - Move edge-only flags from connection_t to edge_connection_t: not
24181 only is this better coding, but on machines of plausible alignment,
24182 it should save 4-8 bytes per connection_t. "Every little bit helps."
24183 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
24184 for consistency; keep old option working for backward compatibility.
24185 - Simplify the code for finding connections to use for a circuit.
24188 Changes in version 0.2.1.8-alpha - 2008-12-08
24189 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
24190 builds better on unusual platforms like Solaris and old OS X, and
24191 fixes a variety of other issues.
24194 - New DirPortFrontPage option that takes an html file and publishes
24195 it as "/" on the DirPort. Now relay operators can provide a
24196 disclaimer without needing to set up a separate webserver. There's
24197 a sample disclaimer in contrib/tor-exit-notice.html.
24200 - When the client is choosing entry guards, now it selects at most
24201 one guard from a given relay family. Otherwise we could end up with
24202 all of our entry points into the network run by the same operator.
24203 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
24206 - Fix a DOS opportunity during the voting signature collection process
24207 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
24208 - Fix a possible segfault when establishing an exit connection. Bugfix
24212 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
24214 - Made Tor a little less aggressive about deleting expired
24215 certificates. Partial fix for bug 854.
24216 - Stop doing unaligned memory access that generated bus errors on
24217 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
24218 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
24219 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
24220 - Make USR2 log-level switch take effect immediately. Bugfix on
24222 - If one win32 nameserver fails to get added, continue adding the
24223 rest, and don't automatically fail.
24224 - Use fcntl() for locking when flock() is not available. Should fix
24225 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
24226 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
24227 could make gcc generate non-functional binary search code. Bugfix
24229 - Build correctly on platforms without socklen_t.
24230 - Avoid potential crash on internal error during signature collection.
24231 Fixes bug 864. Patch from rovv.
24232 - Do not use C's stdio library for writing to log files. This will
24233 improve logging performance by a minute amount, and will stop
24234 leaking fds when our disk is full. Fixes bug 861.
24235 - Stop erroneous use of O_APPEND in cases where we did not in fact
24236 want to re-seek to the end of a file before every last write().
24237 - Correct handling of possible malformed authority signing key
24238 certificates with internal signature types. Fixes bug 880. Bugfix
24240 - Fix a hard-to-trigger resource leak when logging credential status.
24244 - Directory mirrors no longer fetch the v1 directory or
24245 running-routers files. They are obsolete, and nobody asks for them
24246 anymore. This is the first step to making v1 authorities obsolete.
24248 o Minor features (controller):
24249 - Return circuit purposes in response to GETINFO circuit-status. Fixes
24253 Changes in version 0.2.0.32 - 2008-11-20
24254 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
24255 packages (and maybe other packages) noticed by Theo de Raadt, fixes
24256 a smaller security flaw that might allow an attacker to access local
24257 services, further improves hidden service performance, and fixes a
24258 variety of other issues.
24261 - The "User" and "Group" config options did not clear the
24262 supplementary group entries for the Tor process. The "User" option
24263 is now more robust, and we now set the groups to the specified
24264 user's primary group. The "Group" option is now ignored. For more
24265 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
24266 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
24267 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
24268 - The "ClientDNSRejectInternalAddresses" config option wasn't being
24269 consistently obeyed: if an exit relay refuses a stream because its
24270 exit policy doesn't allow it, we would remember what IP address
24271 the relay said the destination address resolves to, even if it's
24272 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
24275 - Fix a DOS opportunity during the voting signature collection process
24276 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
24278 o Major bugfixes (hidden services):
24279 - When fetching v0 and v2 rendezvous service descriptors in parallel,
24280 we were failing the whole hidden service request when the v0
24281 descriptor fetch fails, even if the v2 fetch is still pending and
24282 might succeed. Similarly, if the last v2 fetch fails, we were
24283 failing the whole hidden service request even if a v0 fetch is
24284 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
24285 - When extending a circuit to a hidden service directory to upload a
24286 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
24287 requests failed, because the router descriptor has not been
24288 downloaded yet. In these cases, do not attempt to upload the
24289 rendezvous descriptor, but wait until the router descriptor is
24290 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
24291 descriptor from a hidden service directory for which the router
24292 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
24296 - Fix several infrequent memory leaks spotted by Coverity.
24297 - When testing for libevent functions, set the LDFLAGS variable
24298 correctly. Found by Riastradh.
24299 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
24300 bootstrapping with tunneled directory connections. Bugfix on
24301 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
24302 - When asked to connect to A.B.exit:80, if we don't know the IP for A
24303 and we know that server B rejects most-but-not all connections to
24304 port 80, we would previously reject the connection. Now, we assume
24305 the user knows what they were asking for. Fixes bug 752. Bugfix
24306 on 0.0.9rc5. Diagnosed by BarkerJr.
24307 - If we overrun our per-second write limits a little, count this as
24308 having used up our write allocation for the second, and choke
24309 outgoing directory writes. Previously, we had only counted this when
24310 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
24311 Bugfix on 0.2.0.x (??).
24312 - Remove the old v2 directory authority 'lefkada' from the default
24313 list. It has been gone for many months.
24314 - Stop doing unaligned memory access that generated bus errors on
24315 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
24316 - Make USR2 log-level switch take effect immediately. Bugfix on
24319 o Minor bugfixes (controller):
24320 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
24321 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
24324 Changes in version 0.2.1.7-alpha - 2008-11-08
24325 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
24326 packages (and maybe other packages) noticed by Theo de Raadt, fixes
24327 a smaller security flaw that might allow an attacker to access local
24328 services, adds better defense against DNS poisoning attacks on exit
24329 relays, further improves hidden service performance, and fixes a
24330 variety of other issues.
24333 - The "ClientDNSRejectInternalAddresses" config option wasn't being
24334 consistently obeyed: if an exit relay refuses a stream because its
24335 exit policy doesn't allow it, we would remember what IP address
24336 the relay said the destination address resolves to, even if it's
24337 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
24338 - The "User" and "Group" config options did not clear the
24339 supplementary group entries for the Tor process. The "User" option
24340 is now more robust, and we now set the groups to the specified
24341 user's primary group. The "Group" option is now ignored. For more
24342 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
24343 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
24344 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
24345 - Do not use or believe expired v3 authority certificates. Patch
24346 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
24349 - Now NodeFamily and MyFamily config options allow spaces in
24350 identity fingerprints, so it's easier to paste them in.
24351 Suggested by Lucky Green.
24352 - Implement the 0x20 hack to better resist DNS poisoning: set the
24353 case on outgoing DNS requests randomly, and reject responses that do
24354 not match the case correctly. This logic can be disabled with the
24355 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
24356 of servers that do not reliably preserve case in replies. See
24357 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
24359 - Preserve case in replies to DNSPort requests in order to support
24360 the 0x20 hack for resisting DNS poisoning attacks.
24362 o Hidden service performance improvements:
24363 - When the client launches an introduction circuit, retry with a
24364 new circuit after 30 seconds rather than 60 seconds.
24365 - Launch a second client-side introduction circuit in parallel
24366 after a delay of 15 seconds (based on work by Christian Wilms).
24367 - Hidden services start out building five intro circuits rather
24368 than three, and when the first three finish they publish a service
24369 descriptor using those. Now we publish our service descriptor much
24370 faster after restart.
24373 - Minor fix in the warning messages when you're having problems
24374 bootstrapping; also, be more forgiving of bootstrap problems when
24375 we're still making incremental progress on a given bootstrap phase.
24376 - When we're choosing an exit node for a circuit, and we have
24377 no pending streams, choose a good general exit rather than one that
24378 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
24379 - Send a valid END cell back when a client tries to connect to a
24380 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
24381 840. Patch from rovv.
24382 - If a broken client asks a non-exit router to connect somewhere,
24383 do not even do the DNS lookup before rejecting the connection.
24384 Fixes another case of bug 619. Patch from rovv.
24385 - Fix another case of assuming, when a specific exit is requested,
24386 that we know more than the user about what hosts it allows.
24387 Fixes another case of bug 752. Patch from rovv.
24388 - Check which hops rendezvous stream cells are associated with to
24389 prevent possible guess-the-streamid injection attacks from
24390 intermediate hops. Fixes another case of bug 446. Based on patch
24392 - Avoid using a negative right-shift when comparing 32-bit
24393 addresses. Possible fix for bug 845 and bug 811.
24394 - Make the assert_circuit_ok() function work correctly on circuits that
24395 have already been marked for close.
24396 - Fix read-off-the-end-of-string error in unit tests when decoding
24397 introduction points.
24398 - Fix uninitialized size field for memory area allocation: may improve
24399 memory performance during directory parsing.
24400 - Treat duplicate certificate fetches as failures, so that we do
24401 not try to re-fetch an expired certificate over and over and over.
24402 - Do not say we're fetching a certificate when we'll in fact skip it
24403 because of a pending download.
24406 Changes in version 0.2.1.6-alpha - 2008-09-30
24407 Tor 0.2.1.6-alpha further improves performance and robustness of
24408 hidden services, starts work on supporting per-country relay selection,
24409 and fixes a variety of smaller issues.
24412 - Implement proposal 121: make it possible to build hidden services
24413 that only certain clients are allowed to connect to. This is
24414 enforced at several points, so that unauthorized clients are unable
24415 to send INTRODUCE cells to the service, or even (depending on the
24416 type of authentication) to learn introduction points. This feature
24417 raises the bar for certain kinds of active attacks against hidden
24418 services. Code by Karsten Loesing.
24419 - Relays now store and serve v2 hidden service descriptors by default,
24420 i.e., the new default value for HidServDirectoryV2 is 1. This is
24421 the last step in proposal 114, which aims to make hidden service
24422 lookups more reliable.
24423 - Start work to allow node restrictions to include country codes. The
24424 syntax to exclude nodes in a country with country code XX is
24425 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
24426 refinement to decide what config options should take priority if
24427 you ask to both use a particular node and exclude it.
24428 - Allow ExitNodes list to include IP ranges and country codes, just
24429 like the Exclude*Nodes lists. Patch from Robert Hogan.
24432 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
24433 Tor to fail to start if you had it configured to use a bridge
24434 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
24435 - When extending a circuit to a hidden service directory to upload a
24436 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
24437 requests failed, because the router descriptor had not been
24438 downloaded yet. In these cases, we now wait until the router
24439 descriptor is downloaded, and then retry. Likewise, clients
24440 now skip over a hidden service directory if they don't yet have
24441 its router descriptor, rather than futilely requesting it and
24442 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
24444 - When fetching v0 and v2 rendezvous service descriptors in parallel,
24445 we were failing the whole hidden service request when the v0
24446 descriptor fetch fails, even if the v2 fetch is still pending and
24447 might succeed. Similarly, if the last v2 fetch fails, we were
24448 failing the whole hidden service request even if a v0 fetch is
24449 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
24450 - DNS replies need to have names matching their requests, but
24451 these names should be in the questions section, not necessarily
24452 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
24455 - Update to the "September 1 2008" ip-to-country file.
24456 - Allow ports 465 and 587 in the default exit policy again. We had
24457 rejected them in 0.1.0.15, because back in 2005 they were commonly
24458 misconfigured and ended up as spam targets. We hear they are better
24459 locked down these days.
24460 - Use a lockfile to make sure that two Tor processes are not
24461 simultaneously running with the same datadir.
24462 - Serve the latest v3 networkstatus consensus via the control
24463 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
24464 - Better logging about stability/reliability calculations on directory
24466 - Drop the requirement to have an open dir port for storing and
24467 serving v2 hidden service descriptors.
24468 - Directory authorities now serve a /tor/dbg-stability.txt URL to
24469 help debug WFU and MTBF calculations.
24470 - Implement most of Proposal 152: allow specialized servers to permit
24471 single-hop circuits, and clients to use those servers to build
24472 single-hop circuits when using a specialized controller. Patch
24473 from Josh Albrecht. Resolves feature request 768.
24474 - Add a -p option to tor-resolve for specifying the SOCKS port: some
24475 people find host:port too confusing.
24476 - Make TrackHostExit mappings expire a while after their last use, not
24477 after their creation. Patch from Robert Hogan.
24478 - Provide circuit purposes along with circuit events to the controller.
24481 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
24483 - Fixed some memory leaks -- some quite frequent, some almost
24484 impossible to trigger -- based on results from Coverity.
24485 - When testing for libevent functions, set the LDFLAGS variable
24486 correctly. Found by Riastradh.
24487 - Fix an assertion bug in parsing policy-related options; possible fix
24489 - Catch and report a few more bootstrapping failure cases when Tor
24490 fails to establish a TCP connection. Cleanup on 0.2.1.x.
24491 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
24492 bootstrapping with tunneled directory connections. Bugfix on
24493 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
24494 - When asked to connect to A.B.exit:80, if we don't know the IP for A
24495 and we know that server B rejects most-but-not all connections to
24496 port 80, we would previously reject the connection. Now, we assume
24497 the user knows what they were asking for. Fixes bug 752. Bugfix
24498 on 0.0.9rc5. Diagnosed by BarkerJr.
24499 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
24500 service directories if they have no advertised dir port. Bugfix
24502 - If we overrun our per-second write limits a little, count this as
24503 having used up our write allocation for the second, and choke
24504 outgoing directory writes. Previously, we had only counted this when
24505 we had met our limits precisely. Fixes bug 824. Patch by rovv.
24506 Bugfix on 0.2.0.x (??).
24507 - Avoid a "0 divided by 0" calculation when calculating router uptime
24508 at directory authorities. Bugfix on 0.2.0.8-alpha.
24509 - Make DNS resolved controller events into "CLOSED", not
24510 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
24512 - Fix a bug where an unreachable relay would establish enough
24513 reachability testing circuits to do a bandwidth test -- if
24514 we already have a connection to the middle hop of the testing
24515 circuit, then it could establish the last hop by using the existing
24516 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
24517 circuits no longer use entry guards in 0.2.1.3-alpha.
24518 - If we have correct permissions on $datadir, we complain to stdout
24519 and fail to start. But dangerous permissions on
24520 $datadir/cached-status/ would cause us to open a log and complain
24521 there. Now complain to stdout and fail to start in both cases. Fixes
24522 bug 820, reported by seeess.
24523 - Remove the old v2 directory authority 'lefkada' from the default
24524 list. It has been gone for many months.
24526 o Code simplifications and refactoring:
24527 - Revise the connection_new functions so that a more typesafe variant
24528 exists. This will work better with Coverity, and let us find any
24529 actual mistakes we're making here.
24530 - Refactor unit testing logic so that dmalloc can be used sensibly
24531 with unit tests to check for memory leaks.
24532 - Move all hidden-service related fields from connection and circuit
24533 structure to substructures: this way they won't eat so much memory.
24536 Changes in version 0.2.0.31 - 2008-09-03
24537 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
24538 a big bug we're seeing where in rare cases traffic from one Tor stream
24539 gets mixed into another stream, and fixes a variety of smaller issues.
24542 - Make sure that two circuits can never exist on the same connection
24543 with the same circuit ID, even if one is marked for close. This
24544 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
24545 - Relays now reject risky extend cells: if the extend cell includes
24546 a digest of all zeroes, or asks to extend back to the relay that
24547 sent the extend cell, tear down the circuit. Ideas suggested
24549 - If not enough of our entry guards are available so we add a new
24550 one, we might use the new one even if it overlapped with the
24551 current circuit's exit relay (or its family). Anonymity bugfix
24552 pointed out by rovv.
24555 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
24556 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
24557 - Correctly detect the presence of the linux/netfilter_ipv4.h header
24558 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
24559 - Pick size of default geoip filename string correctly on windows.
24560 Fixes bug 806. Bugfix on 0.2.0.30.
24561 - Make the autoconf script accept the obsolete --with-ssl-dir
24562 option as an alias for the actually-working --with-openssl-dir
24563 option. Fix the help documentation to recommend --with-openssl-dir.
24564 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
24565 - When using the TransPort option on OpenBSD, and using the User
24566 option to change UID and drop privileges, make sure to open
24567 /dev/pf before dropping privileges. Fixes bug 782. Patch from
24568 Christopher Davis. Bugfix on 0.1.2.1-alpha.
24569 - Try to attach connections immediately upon receiving a RENDEZVOUS2
24570 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
24571 on the client side when connecting to a hidden service. Bugfix
24572 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
24573 - When closing an application-side connection because its circuit is
24574 getting torn down, generate the stream event correctly. Bugfix on
24575 0.1.2.x. Anonymous patch.
24578 Changes in version 0.2.1.5-alpha - 2008-08-31
24579 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
24580 in a lot of the infrastructure for adding authorization to hidden
24581 services, lays the groundwork for having clients read their load
24582 balancing information out of the networkstatus consensus rather than
24583 the individual router descriptors, addresses two potential anonymity
24584 issues, and fixes a variety of smaller issues.
24587 - Convert many internal address representations to optionally hold
24589 - Generate and accept IPv6 addresses in many protocol elements.
24590 - Make resolver code handle nameservers located at ipv6 addresses.
24591 - Begin implementation of proposal 121 ("Client authorization for
24592 hidden services"): configure hidden services with client
24593 authorization, publish descriptors for them, and configure
24594 authorization data for hidden services at clients. The next
24595 step is to actually access hidden services that perform client
24597 - More progress toward proposal 141: Network status consensus
24598 documents and votes now contain bandwidth information for each
24599 router and a summary of that router's exit policy. Eventually this
24600 will be used by clients so that they do not have to download every
24601 known descriptor before building circuits.
24603 o Major bugfixes (on 0.2.0.x and before):
24604 - When sending CREATED cells back for a given circuit, use a 64-bit
24605 connection ID to find the right connection, rather than an addr:port
24606 combination. Now that we can have multiple OR connections between
24607 the same ORs, it is no longer possible to use addr:port to uniquely
24608 identify a connection.
24609 - Relays now reject risky extend cells: if the extend cell includes
24610 a digest of all zeroes, or asks to extend back to the relay that
24611 sent the extend cell, tear down the circuit. Ideas suggested
24613 - If not enough of our entry guards are available so we add a new
24614 one, we might use the new one even if it overlapped with the
24615 current circuit's exit relay (or its family). Anonymity bugfix
24616 pointed out by rovv.
24619 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
24620 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
24621 - When using the TransPort option on OpenBSD, and using the User
24622 option to change UID and drop privileges, make sure to open /dev/pf
24623 before dropping privileges. Fixes bug 782. Patch from Christopher
24624 Davis. Bugfix on 0.1.2.1-alpha.
24625 - Correctly detect the presence of the linux/netfilter_ipv4.h header
24626 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
24627 - Add a missing safe_str() call for a debug log message.
24628 - Use 64 bits instead of 32 bits for connection identifiers used with
24629 the controller protocol, to greatly reduce risk of identifier reuse.
24630 - Make the autoconf script accept the obsolete --with-ssl-dir
24631 option as an alias for the actually-working --with-openssl-dir
24632 option. Fix the help documentation to recommend --with-openssl-dir.
24633 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
24636 - Rate-limit too-many-sockets messages: when they happen, they happen
24637 a lot. Resolves bug 748.
24638 - Resist DNS poisoning a little better by making sure that names in
24639 answer sections match.
24640 - Print the SOCKS5 error message string as well as the error code
24641 when a tor-resolve request fails. Patch from Jacob.
24644 Changes in version 0.2.1.4-alpha - 2008-08-04
24645 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
24648 - The address part of exit policies was not correctly written
24649 to router descriptors. This generated router descriptors that failed
24650 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
24652 - Tor triggered a false assert when extending a circuit to a relay
24653 but we already have a connection open to that relay. Noticed by
24654 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
24657 - Fix a hidden service logging bug: in some edge cases, the router
24658 descriptor of a previously picked introduction point becomes
24659 obsolete and we need to give up on it rather than continually
24660 complaining that it has become obsolete. Observed by xiando. Bugfix
24663 o Removed features:
24664 - Take out the TestVia config option, since it was a workaround for
24665 a bug that was fixed in Tor 0.1.1.21.
24668 Changes in version 0.2.1.3-alpha - 2008-08-03
24669 Tor 0.2.1.3-alpha implements most of the pieces to prevent
24670 infinite-length circuit attacks (see proposal 110); fixes a bug that
24671 might cause exit relays to corrupt streams they send back; allows
24672 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
24673 ExcludeExitNodes config options; and fixes a big pile of bugs.
24675 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
24676 - Send a bootstrap problem "warn" event on the first problem if the
24677 reason is NO_ROUTE (that is, our network is down).
24680 - Implement most of proposal 110: The first K cells to be sent
24681 along a circuit are marked as special "early" cells; only K "early"
24682 cells will be allowed. Once this code is universal, we can block
24683 certain kinds of DOS attack by requiring that EXTEND commands must
24684 be sent using an "early" cell.
24687 - Try to attach connections immediately upon receiving a RENDEZVOUS2
24688 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
24689 on the client side when connecting to a hidden service. Bugfix
24690 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
24691 - Ensure that two circuits can never exist on the same connection
24692 with the same circuit ID, even if one is marked for close. This
24693 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
24696 - When relays do their initial bandwidth measurement, don't limit
24697 to just our entry guards for the test circuits. Otherwise we tend
24698 to have multiple test circuits going through a single entry guard,
24699 which makes our bandwidth test less accurate. Fixes part of bug 654;
24700 patch contributed by Josh Albrecht.
24701 - Add an ExcludeExitNodes option so users can list a set of nodes
24702 that should be be excluded from the exit node position, but
24703 allowed elsewhere. Implements proposal 151.
24704 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
24705 ExcludeNodes and ExcludeExitNodes lists.
24706 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
24707 be more efficient. Formerly it was quadratic in the number of
24708 servers; now it should be linear. Fixes bug 509.
24709 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
24710 and n_conn_id_digest fields into a separate structure that's
24711 only needed when the circuit has not yet attached to an n_conn.
24714 - Change the contrib/tor.logrotate script so it makes the new
24715 logs as "_tor:_tor" rather than the default, which is generally
24716 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
24717 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
24718 warnings (occasionally), but it can also cause the compiler to
24719 eliminate error-checking code. Suggested by Peter Gutmann.
24720 - When a hidden service is giving up on an introduction point candidate
24721 that was not included in the last published rendezvous descriptor,
24722 don't reschedule publication of the next descriptor. Fixes bug 763.
24724 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
24725 HiddenServiceExcludeNodes as obsolete: they never worked properly,
24726 and nobody claims to be using them. Fixes bug 754. Bugfix on
24727 0.1.0.1-rc. Patch from Christian Wilms.
24728 - Fix a small alignment and memory-wasting bug on buffer chunks.
24731 o Minor bugfixes (controller):
24732 - When closing an application-side connection because its circuit
24733 is getting torn down, generate the stream event correctly.
24734 Bugfix on 0.1.2.x. Anonymous patch.
24736 o Removed features:
24737 - Remove all backward-compatibility code to support relays running
24738 versions of Tor so old that they no longer work at all on the
24742 Changes in version 0.2.0.30 - 2008-07-15
24744 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
24745 warnings (occasionally), but it can also cause the compiler to
24746 eliminate error-checking code. Suggested by Peter Gutmann.
24749 Changes in version 0.2.0.29-rc - 2008-07-08
24750 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
24751 hidden-service performance bugs, and fixes a bunch of smaller bugs.
24754 - If you have more than one bridge but don't know their keys,
24755 you would only launch a request for the descriptor of the first one
24756 on your list. (Tor considered launching requests for the others, but
24757 found that it already had a connection on the way for $0000...0000
24758 so it didn't open another.) Bugfix on 0.2.0.x.
24759 - If you have more than one bridge but don't know their keys, and the
24760 connection to one of the bridges failed, you would cancel all
24761 pending bridge connections. (After all, they all have the same
24762 digest.) Bugfix on 0.2.0.x.
24763 - When a hidden service was trying to establish an introduction point,
24764 and Tor had built circuits preemptively for such purposes, we
24765 were ignoring all the preemptive circuits and launching a new one
24766 instead. Bugfix on 0.2.0.14-alpha.
24767 - When a hidden service was trying to establish an introduction point,
24768 and Tor *did* manage to reuse one of the preemptively built
24769 circuits, it didn't correctly remember which one it used,
24770 so it asked for another one soon after, until there were no
24771 more preemptive circuits, at which point it launched one from
24772 scratch. Bugfix on 0.0.9.x.
24773 - Make directory servers include the X-Your-Address-Is: http header in
24774 their responses even for begin_dir conns. Now clients who only
24775 ever use begin_dir connections still have a way to learn their IP
24776 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
24779 - Fix a macro/CPP interaction that was confusing some compilers:
24780 some GCCs don't like #if/#endif pairs inside macro arguments.
24782 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
24783 Fixes bug 704; fix from Steven Murdoch.
24784 - When opening /dev/null in finish_daemonize(), do not pass the
24785 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
24786 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
24787 - Correctly detect transparent proxy support on Linux hosts that
24788 require in.h to be included before netfilter_ipv4.h. Patch
24790 - Disallow session resumption attempts during the renegotiation
24791 stage of the v2 handshake protocol. Clients should never be trying
24792 session resumption at this point, but apparently some did, in
24793 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
24794 found by Geoff Goodell.
24797 Changes in version 0.2.1.2-alpha - 2008-06-20
24798 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
24799 make it easier to set up your own private Tor network; fixes several
24800 big bugs with using more than one bridge relay; fixes a big bug with
24801 offering hidden services quickly after Tor starts; and uses a better
24802 API for reporting potential bootstrapping problems to the controller.
24805 - New TestingTorNetwork config option to allow adjustment of
24806 previously constant values that, while reasonable, could slow
24807 bootstrapping. Implements proposal 135. Patch from Karsten.
24810 - If you have more than one bridge but don't know their digests,
24811 you would only learn a request for the descriptor of the first one
24812 on your list. (Tor considered launching requests for the others, but
24813 found that it already had a connection on the way for $0000...0000
24814 so it didn't open another.) Bugfix on 0.2.0.x.
24815 - If you have more than one bridge but don't know their digests,
24816 and the connection to one of the bridges failed, you would cancel
24817 all pending bridge connections. (After all, they all have the
24818 same digest.) Bugfix on 0.2.0.x.
24819 - When establishing a hidden service, introduction points that
24820 originate from cannibalized circuits are completely ignored and not
24821 included in rendezvous service descriptors. This might be another
24822 reason for delay in making a hidden service available. Bugfix
24823 from long ago (0.0.9.x?)
24826 - Allow OpenSSL to use dynamic locks if it wants.
24827 - When building a consensus, do not include routers that are down.
24828 This will cut down 30% to 40% on consensus size. Implements
24830 - In directory authorities' approved-routers files, allow
24831 fingerprints with or without space.
24832 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
24833 controller can query our current bootstrap state in case it attaches
24834 partway through and wants to catch up.
24835 - Send an initial "Starting" bootstrap status event, so we have a
24836 state to start out in.
24839 - Asking for a conditional consensus at .../consensus/<fingerprints>
24840 would crash a dirserver if it did not already have a
24841 consensus. Bugfix on 0.2.1.1-alpha.
24842 - Clean up some macro/CPP interactions: some GCC versions don't like
24843 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
24846 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
24847 - Directory authorities shouldn't complain about bootstrapping
24848 problems just because they do a lot of reachability testing and
24849 some of the connection attempts fail.
24850 - Start sending "count" and "recommendation" key/value pairs in
24851 bootstrap problem status events, so the controller can hear about
24852 problems even before Tor decides they're worth reporting for sure.
24853 - If you're using bridges, generate "bootstrap problem" warnings
24854 as soon as you run out of working bridges, rather than waiting
24855 for ten failures -- which will never happen if you have less than
24857 - If we close our OR connection because there's been a circuit
24858 pending on it for too long, we were telling our bootstrap status
24859 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
24862 Changes in version 0.2.1.1-alpha - 2008-06-13
24863 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
24864 were making the Tor process bloat especially on Linux; makes our TLS
24865 handshake blend in better; sends "bootstrap phase" status events to
24866 the controller, so it can keep the user informed of progress (and
24867 problems) fetching directory information and establishing circuits;
24868 and adds a variety of smaller features.
24871 - More work on making our TLS handshake blend in: modify the list
24872 of ciphers advertised by OpenSSL in client mode to even more
24873 closely resemble a common web browser. We cheat a little so that
24874 we can advertise ciphers that the locally installed OpenSSL doesn't
24876 - Start sending "bootstrap phase" status events to the controller,
24877 so it can keep the user informed of progress fetching directory
24878 information and establishing circuits. Also inform the controller
24879 if we think we're stuck at a particular bootstrap phase. Implements
24881 - Resume using OpenSSL's RAND_poll() for better (and more portable)
24882 cross-platform entropy collection again. We used to use it, then
24883 stopped using it because of a bug that could crash systems that
24884 called RAND_poll when they had a lot of fds open. It looks like the
24885 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
24886 at startup, and to call RAND_poll() when we reseed later only if
24887 we have a non-buggy OpenSSL version.
24890 - When we choose to abandon a new entry guard because we think our
24891 older ones might be better, close any circuits pending on that
24892 new entry guard connection. This fix should make us recover much
24893 faster when our network is down and then comes back. Bugfix on
24894 0.1.2.8-beta; found by lodger.
24896 o Memory fixes and improvements:
24897 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
24898 to avoid unused RAM in buffer chunks and memory pools.
24899 - Speed up parsing and cut down on memory fragmentation by using
24900 stack-style allocations for parsing directory objects. Previously,
24901 this accounted for over 40% of allocations from within Tor's code
24902 on a typical directory cache.
24903 - Use a Bloom filter rather than a digest-based set to track which
24904 descriptors we need to keep around when we're cleaning out old
24905 router descriptors. This speeds up the computation significantly,
24906 and may reduce fragmentation.
24907 - Reduce the default smartlist size from 32 to 16; it turns out that
24908 most smartlists hold around 8-12 elements tops.
24909 - Make dumpstats() log the fullness and size of openssl-internal
24911 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
24912 patch to their OpenSSL, turn it on to save memory on servers. This
24913 patch will (with any luck) get included in a mainline distribution
24915 - Never use OpenSSL compression: it wastes RAM and CPU trying to
24916 compress cells, which are basically all encrypted, compressed,
24920 - Stop reloading the router list from disk for no reason when we
24921 run out of reachable directory mirrors. Once upon a time reloading
24922 it would set the 'is_running' flag back to 1 for them. It hasn't
24923 done that for a long time.
24924 - In very rare situations new hidden service descriptors were
24925 published earlier than 30 seconds after the last change to the
24926 service. (We currently think that a hidden service descriptor
24927 that's been stable for 30 seconds is worth publishing.)
24930 - Allow separate log levels to be configured for different logging
24931 domains. For example, this allows one to log all notices, warnings,
24932 or errors, plus all memory management messages of level debug or
24933 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
24934 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
24935 and stop using a warning that had become unfixably verbose under
24937 - New --hush command-line option similar to --quiet. While --quiet
24938 disables all logging to the console on startup, --hush limits the
24939 output to messages of warning and error severity.
24940 - Servers support a new URL scheme for consensus downloads that
24941 allows the client to specify which authorities are trusted.
24942 The server then only sends the consensus if the client will trust
24943 it. Otherwise a 404 error is sent back. Clients use this
24944 new scheme when the server supports it (meaning it's running
24945 0.2.1.1-alpha or later). Implements proposal 134.
24946 - New configure/torrc options (--enable-geoip-stats,
24947 DirRecordUsageByCountry) to record how many IPs we've served
24948 directory info to in each country code, how many status documents
24949 total we've sent to each country code, and what share of the total
24950 directory requests we should expect to see.
24951 - Use the TLS1 hostname extension to more closely resemble browser
24953 - Lots of new unit tests.
24954 - Add a macro to implement the common pattern of iterating through
24955 two parallel lists in lockstep.
24958 Changes in version 0.2.0.28-rc - 2008-06-13
24959 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
24960 performance bug, and fixes a bunch of smaller bugs.
24963 - Fix a bug where, when we were choosing the 'end stream reason' to
24964 put in our relay end cell that we send to the exit relay, Tor
24965 clients on Windows were sometimes sending the wrong 'reason'. The
24966 anonymity problem is that exit relays may be able to guess whether
24967 the client is running Windows, thus helping partition the anonymity
24968 set. Down the road we should stop sending reasons to exit relays,
24969 or otherwise prevent future versions of this bug.
24972 - While setting up a hidden service, some valid introduction circuits
24973 were overlooked and abandoned. This might be the reason for
24974 the long delay in making a hidden service available. Bugfix on
24978 - Update to the "June 9 2008" ip-to-country file.
24979 - Run 'make test' as part of 'make dist', so we stop releasing so
24980 many development snapshots that fail their unit tests.
24983 - When we're checking if we have enough dir info for each relay
24984 to begin establishing circuits, make sure that we actually have
24985 the descriptor listed in the consensus, not just any descriptor.
24987 - Bridge relays no longer print "xx=0" in their extrainfo document
24988 for every single country code in the geoip db. Bugfix on
24990 - Only warn when we fail to load the geoip file if we were planning to
24991 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
24992 - If we change our MaxAdvertisedBandwidth and then reload torrc,
24993 Tor won't realize it should publish a new relay descriptor. Fixes
24994 bug 688, reported by mfr. Bugfix on 0.1.2.x.
24995 - When we haven't had any application requests lately, don't bother
24996 logging that we have expired a bunch of descriptors. Bugfix
24998 - Make relay cells written on a connection count as non-padding when
24999 tracking how long a connection has been in use. Bugfix on
25000 0.2.0.1-alpha. Spotted by lodger.
25001 - Fix unit tests in 0.2.0.27-rc.
25002 - Fix compile on Windows.
25005 Changes in version 0.2.0.27-rc - 2008-06-03
25006 Tor 0.2.0.27-rc adds a few features we left out of the earlier
25007 release candidates. In particular, we now include an IP-to-country
25008 GeoIP database, so controllers can easily look up what country a
25009 given relay is in, and so bridge relays can give us some sanitized
25010 summaries about which countries are making use of bridges. (See proposal
25011 126-geoip-fetching.txt for details.)
25014 - Include an IP-to-country GeoIP file in the tarball, so bridge
25015 relays can report sanitized summaries of the usage they're seeing.
25018 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
25019 Robert Hogan. Fixes the first part of bug 681.
25020 - Make bridge authorities never serve extrainfo docs.
25021 - Add support to detect Libevent versions in the 1.4.x series
25023 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
25024 - Include a new contrib/tor-exit-notice.html file that exit relay
25025 operators can put on their website to help reduce abuse queries.
25028 - When tunneling an encrypted directory connection, and its first
25029 circuit fails, do not leave it unattached and ask the controller
25030 to deal. Fixes the second part of bug 681.
25031 - Make bridge authorities correctly expire old extrainfo documents
25035 Changes in version 0.2.0.26-rc - 2008-05-13
25036 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
25037 in Debian's OpenSSL packages. All users running any 0.2.0.x version
25038 should upgrade, whether they're running Debian or not.
25040 o Major security fixes:
25041 - Use new V3 directory authority keys on the tor26, gabelmoo, and
25042 moria1 V3 directory authorities. The old keys were generated with
25043 a vulnerable version of Debian's OpenSSL package, and must be
25044 considered compromised. Other authorities' keys were not generated
25045 with an affected version of OpenSSL.
25048 - List authority signatures as "unrecognized" based on DirServer
25049 lines, not on cert cache. Bugfix on 0.2.0.x.
25052 - Add a new V3AuthUseLegacyKey option to make it easier for
25053 authorities to change their identity keys if they have to.
25056 Changes in version 0.2.0.25-rc - 2008-04-23
25057 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
25060 - Remember to initialize threading before initializing logging.
25061 Otherwise, many BSD-family implementations will crash hard on
25062 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
25065 - Authorities correctly free policies on bad servers on
25066 exit. Fixes bug 672. Bugfix on 0.2.0.x.
25069 Changes in version 0.2.0.24-rc - 2008-04-22
25070 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
25071 v3 directory authority, makes relays with dynamic IP addresses and no
25072 DirPort notice more quickly when their IP address changes, fixes a few
25073 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
25075 o New directory authorities:
25076 - Take lefkada out of the list of v3 directory authorities, since
25077 it has been down for months.
25078 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
25082 - Detect address changes more quickly on non-directory mirror
25083 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
25085 o Minor features (security):
25086 - Reject requests for reverse-dns lookup of names that are in
25087 a private address space. Patch from lodger.
25088 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
25091 o Minor bugfixes (crashes):
25092 - Avoid a rare assert that can trigger when Tor doesn't have much
25093 directory information yet and it tries to fetch a v2 hidden
25094 service descriptor. Fixes bug 651, reported by nwf.
25095 - Initialize log mutex before initializing dmalloc. Otherwise,
25096 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
25097 - Use recursive pthread mutexes in order to avoid deadlock when
25098 logging debug-level messages to a controller. Bug spotted by nwf,
25099 bugfix on 0.2.0.16-alpha.
25101 o Minor bugfixes (resource management):
25102 - Keep address policies from leaking memory: start their refcount
25103 at 1, not 2. Bugfix on 0.2.0.16-alpha.
25104 - Free authority certificates on exit, so they don't look like memory
25105 leaks. Bugfix on 0.2.0.19-alpha.
25106 - Free static hashtables for policy maps and for TLS connections on
25107 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
25108 - Avoid allocating extra space when computing consensuses on 64-bit
25109 platforms. Bug spotted by aakova.
25111 o Minor bugfixes (misc):
25112 - Do not read the configuration file when we've only been told to
25113 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
25114 based on patch from Sebastian Hahn.
25115 - Exit relays that are used as a client can now reach themselves
25116 using the .exit notation, rather than just launching an infinite
25117 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
25118 - When attempting to open a logfile fails, tell us why.
25119 - Fix a dumb bug that was preventing us from knowing that we should
25120 preemptively build circuits to handle expected directory requests.
25121 Fixes bug 660. Bugfix on 0.1.2.x.
25122 - Warn less verbosely about clock skew from netinfo cells from
25123 untrusted sources. Fixes bug 663.
25124 - Make controller stream events for DNS requests more consistent,
25125 by adding "new stream" events for DNS requests, and removing
25126 spurious "stream closed" events" for cached reverse resolves.
25127 Patch from mwenge. Fixes bug 646.
25128 - Correctly notify one-hop connections when a circuit build has
25129 failed. Possible fix for bug 669. Found by lodger.
25132 Changes in version 0.2.0.23-rc - 2008-03-24
25133 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
25134 makes bootstrapping faster if the first directory mirror you contact
25135 is down. The bundles also include the new Vidalia 0.1.2 release.
25138 - When a tunneled directory request is made to a directory server
25139 that's down, notice after 30 seconds rather than 120 seconds. Also,
25140 fail any begindir streams that are pending on it, so they can
25141 retry elsewhere. This was causing multi-minute delays on bootstrap.
25144 Changes in version 0.2.0.22-rc - 2008-03-18
25145 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
25146 enables encrypted directory connections by default for non-relays, fixes
25147 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
25148 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
25151 - Enable encrypted directory connections by default for non-relays,
25152 so censor tools that block Tor directory connections based on their
25153 plaintext patterns will no longer work. This means Tor works in
25154 certain censored countries by default again.
25157 - Make sure servers always request certificates from clients during
25158 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
25159 - Do not enter a CPU-eating loop when a connection is closed in
25160 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
25161 diagnosed by lodger; bugfix on 0.2.0.20-rc.
25162 - Fix assertion failure that could occur when a blocked circuit
25163 became unblocked, and it had pending client DNS requests. Bugfix
25164 on 0.2.0.1-alpha. Fixes bug 632.
25166 o Minor bugfixes (on 0.1.2.x):
25167 - Generate "STATUS_SERVER" events rather than misspelled
25168 "STATUS_SEVER" events. Caught by mwenge.
25169 - When counting the number of bytes written on a TLS connection,
25170 look at the BIO actually used for writing to the network, not
25171 at the BIO used (sometimes) to buffer data for the network.
25172 Looking at different BIOs could result in write counts on the
25173 order of ULONG_MAX. Fixes bug 614.
25174 - On Windows, correctly detect errors when listing the contents of
25175 a directory. Fix from lodger.
25177 o Minor bugfixes (on 0.2.0.x):
25178 - Downgrade "sslv3 alert handshake failure" message to INFO.
25179 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
25180 left BandwidthRate and BandwidthBurst at the default, we would be
25181 silently limited by those defaults. Now raise them to match the
25182 RelayBandwidth* values.
25183 - Fix the SVK version detection logic to work correctly on a branch.
25184 - Make --enable-openbsd-malloc work correctly on Linux with alpha
25185 CPUs. Fixes bug 625.
25186 - Logging functions now check that the passed severity is sane.
25187 - Use proper log levels in the testsuite call of
25188 get_interface_address6().
25189 - When using a nonstandard malloc, do not use the platform values for
25190 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
25191 - Make the openbsd malloc code use 8k pages on alpha CPUs and
25193 - Detect mismatched page sizes when using --enable-openbsd-malloc.
25194 - Avoid double-marked-for-close warning when certain kinds of invalid
25195 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
25196 for bug 617. Bugfix on 0.2.0.1-alpha.
25197 - Make sure that the "NULL-means-reject *:*" convention is followed by
25198 all the policy manipulation functions, avoiding some possible crash
25199 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
25200 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
25201 actually works, and doesn't warn about every single reverse lookup.
25202 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
25205 - Only log guard node status when guard node status has changed.
25206 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
25207 make "INFO" 75% less verbose.
25210 Changes in version 0.2.0.21-rc - 2008-03-02
25211 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
25212 makes Tor work well with Vidalia again, fixes a rare assert bug,
25213 and fixes a pair of more minor bugs. The bundles also include Vidalia
25214 0.1.0 and Torbutton 1.1.16.
25217 - The control port should declare that it requires password auth
25218 when HashedControlSessionPassword is set too. Patch from Matt Edman;
25219 bugfix on 0.2.0.20-rc. Fixes bug 615.
25220 - Downgrade assert in connection_buckets_decrement() to a log message.
25221 This may help us solve bug 614, and in any case will make its
25222 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
25223 - We were sometimes miscounting the number of bytes read from the
25224 network, causing our rate limiting to not be followed exactly.
25225 Bugfix on 0.2.0.16-alpha. Reported by lodger.
25228 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
25229 OpenSSL versions should have been working fine. Diagnosis and patch
25230 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
25231 Bugfix on 0.2.0.20-rc.
25234 Changes in version 0.2.0.20-rc - 2008-02-24
25235 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
25236 makes more progress towards normalizing Tor's TLS handshake, makes
25237 hidden services work better again, helps relays bootstrap if they don't
25238 know their IP address, adds optional support for linking in openbsd's
25239 allocator or tcmalloc, allows really fast relays to scale past 15000
25240 sockets, and fixes a bunch of minor bugs reported by Veracode.
25243 - Enable the revised TLS handshake based on the one designed by
25244 Steven Murdoch in proposal 124, as revised in proposal 130. It
25245 includes version negotiation for OR connections as described in
25246 proposal 105. The new handshake is meant to be harder for censors
25247 to fingerprint, and it adds the ability to detect certain kinds of
25248 man-in-the-middle traffic analysis attacks. The version negotiation
25249 feature will allow us to improve Tor's link protocol more safely
25251 - Choose which bridge to use proportional to its advertised bandwidth,
25252 rather than uniformly at random. This should speed up Tor for
25253 bridge users. Also do this for people who set StrictEntryNodes.
25254 - When a TrackHostExits-chosen exit fails too many times in a row,
25255 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
25258 - Resolved problems with (re-)fetching hidden service descriptors.
25259 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
25260 and 0.2.0.19-alpha.
25261 - If we only ever used Tor for hidden service lookups or posts, we
25262 would stop building circuits and start refusing connections after
25263 24 hours, since we falsely believed that Tor was dormant. Reported
25264 by nwf; bugfix on 0.1.2.x.
25265 - Servers that don't know their own IP address should go to the
25266 authorities for their first directory fetch, even if their DirPort
25267 is off or if they don't know they're reachable yet. This will help
25268 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
25269 - When counting the number of open sockets, count not only the number
25270 of sockets we have received from the socket() call, but also
25271 the number we've gotten from accept() and socketpair(). This bug
25272 made us fail to count all sockets that we were using for incoming
25273 connections. Bugfix on 0.2.0.x.
25274 - Fix code used to find strings within buffers, when those strings
25275 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
25276 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
25277 - Add a new __HashedControlSessionPassword option for controllers
25278 to use for one-off session password hashes that shouldn't get
25279 saved to disk by SAVECONF --- Vidalia users were accumulating a
25280 pile of HashedControlPassword lines in their torrc files, one for
25281 each time they had restarted Tor and then clicked Save. Make Tor
25282 automatically convert "HashedControlPassword" to this new option but
25283 only when it's given on the command line. Partial fix for bug 586.
25285 o Minor features (performance):
25286 - Tune parameters for cell pool allocation to minimize amount of
25288 - Add OpenBSD malloc code from phk as an optional malloc
25289 replacement on Linux: some glibc libraries do very poorly
25290 with Tor's memory allocation patterns. Pass
25291 --enable-openbsd-malloc to get the replacement malloc code.
25292 - Add a --with-tcmalloc option to the configure script to link
25293 against tcmalloc (if present). Does not yet search for
25294 non-system include paths.
25295 - Stop imposing an arbitrary maximum on the number of file descriptors
25296 used for busy servers. Bug reported by Olaf Selke; patch from
25299 o Minor features (other):
25300 - When SafeLogging is disabled, log addresses along with all TLS
25302 - When building with --enable-gcc-warnings, check for whether Apple's
25303 warning "-Wshorten-64-to-32" is available.
25304 - Add a --passphrase-fd argument to the tor-gencert command for
25307 o Minor bugfixes (memory leaks and code problems):
25308 - We were leaking a file descriptor if Tor started with a zero-length
25309 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
25310 - Detect size overflow in zlib code. Reported by Justin Ferguson and
25312 - We were comparing the raw BridgePassword entry with a base64'ed
25313 version of it, when handling a "/tor/networkstatus-bridges"
25314 directory request. Now compare correctly. Noticed by Veracode.
25315 - Recover from bad tracked-since value in MTBF-history file.
25316 Should fix bug 537.
25317 - Alter the code that tries to recover from unhandled write
25318 errors, to not try to flush onto a socket that's given us
25319 unhandled errors. Bugfix on 0.1.2.x.
25320 - Make Unix controlsockets work correctly on OpenBSD. Patch from
25321 tup. Bugfix on 0.2.0.3-alpha.
25323 o Minor bugfixes (other):
25324 - If we have an extra-info document for our server, always make
25325 it available on the control port, even if we haven't gotten
25326 a copy of it from an authority yet. Patch from mwenge.
25327 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
25328 - Directory mirrors no longer include a guess at the client's IP
25329 address if the connection appears to be coming from the same /24
25330 network; it was producing too many wrong guesses.
25331 - Make the new hidden service code respect the SafeLogging setting.
25332 Bugfix on 0.2.0.x. Patch from Karsten.
25333 - When starting as an authority, do not overwrite all certificates
25334 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
25335 - If we're trying to flush the last bytes on a connection (for
25336 example, when answering a directory request), reset the
25337 time-to-give-up timeout every time we manage to write something
25338 on the socket. Bugfix on 0.1.2.x.
25339 - Change the behavior of "getinfo status/good-server-descriptor"
25340 so it doesn't return failure when any authority disappears.
25341 - Even though the man page said that "TrackHostExits ." should
25342 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
25343 - Report TLS "zero return" case as a "clean close" and "IO error"
25344 as a "close". Stop calling closes "unexpected closes": existing
25345 Tors don't use SSL_close(), so having a connection close without
25346 the TLS shutdown handshake is hardly unexpected.
25347 - Send NAMESERVER_STATUS messages for a single failed nameserver
25350 o Code simplifications and refactoring:
25351 - Remove the tor_strpartition function: its logic was confused,
25352 and it was only used for one thing that could be implemented far
25356 Changes in version 0.2.0.19-alpha - 2008-02-09
25357 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
25358 handshake, makes path selection for relays more secure and IP address
25359 guessing more robust, and generally fixes a lot of bugs in preparation
25360 for calling the 0.2.0 branch stable.
25363 - Do not include recognizeable strings in the commonname part of
25364 Tor's x509 certificates.
25367 - If we're a relay, avoid picking ourselves as an introduction point,
25368 a rendezvous point, or as the final hop for internal circuits. Bug
25369 reported by taranis and lodger. Bugfix on 0.1.2.x.
25370 - Patch from "Andrew S. Lists" to catch when we contact a directory
25371 mirror at IP address X and he says we look like we're coming from
25372 IP address X. Bugfix on 0.1.2.x.
25374 o Minor features (security):
25375 - Be more paranoid about overwriting sensitive memory on free(),
25376 as a defensive programming tactic to ensure forward secrecy.
25378 o Minor features (directory authority):
25379 - Actually validate the options passed to AuthDirReject,
25380 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
25381 - Reject router descriptors with out-of-range bandwidthcapacity or
25382 bandwidthburst values.
25384 o Minor features (controller):
25385 - Reject controller commands over 1MB in length. This keeps rogue
25386 processes from running us out of memory.
25388 o Minor features (misc):
25389 - Give more descriptive well-formedness errors for out-of-range
25390 hidden service descriptor/protocol versions.
25391 - Make memory debugging information describe more about history
25392 of cell allocation, so we can help reduce our memory use.
25394 o Deprecated features (controller):
25395 - The status/version/num-versioning and status/version/num-concurring
25396 GETINFO options are no longer useful in the v3 directory protocol:
25397 treat them as deprecated, and warn when they're used.
25400 - When our consensus networkstatus has been expired for a while, stop
25401 being willing to build circuits using it. Fixes bug 401. Bugfix
25403 - Directory caches now fetch certificates from all authorities
25404 listed in a networkstatus consensus, even when they do not
25405 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
25406 - When connecting to a bridge without specifying its key, insert
25407 the connection into the identity-to-connection map as soon as
25408 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
25409 - Detect versions of OS X where malloc_good_size() is present in the
25410 library but never actually declared. Resolves bug 587. Bugfix
25412 - Stop incorrectly truncating zlib responses to directory authority
25413 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
25414 - Stop recommending that every server operator send mail to tor-ops.
25415 Resolves bug 597. Bugfix on 0.1.2.x.
25416 - Don't trigger an assert if we start a directory authority with a
25417 private IP address (like 127.0.0.1).
25418 - Avoid possible failures when generating a directory with routers
25419 with over-long versions strings, or too many flags set. Bugfix
25421 - If an attempt to launch a DNS resolve request over the control
25422 port fails because we have overrun the limit on the number of
25423 connections, tell the controller that the request has failed.
25424 - Avoid using too little bandwidth when our clock skips a few
25425 seconds. Bugfix on 0.1.2.x.
25426 - Fix shell error when warning about missing packages in configure
25427 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
25428 - Do not become confused when receiving a spurious VERSIONS-like
25429 cell from a confused v1 client. Bugfix on 0.2.0.x.
25430 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
25431 introduction points for a hidden service have failed. Patch from
25432 Karsten Loesing. Bugfix on 0.2.0.x.
25434 o Code simplifications and refactoring:
25435 - Remove some needless generality from cpuworker code, for improved
25437 - Stop overloading the circuit_t.onionskin field for both "onionskin
25438 from a CREATE cell that we are waiting for a cpuworker to be
25439 assigned" and "onionskin from an EXTEND cell that we are going to
25440 send to an OR as soon as we are connected". Might help with bug 600.
25441 - Add an in-place version of aes_crypt() so that we can avoid doing a
25442 needless memcpy() call on each cell payload.
25445 Changes in version 0.2.0.18-alpha - 2008-01-25
25446 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
25447 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
25448 that can warn or reject connections to ports generally associated with
25449 vulnerable-plaintext protocols.
25451 o New directory authorities:
25452 - Set up dannenberg (run by CCC) as the sixth v3 directory
25456 - Fix a major memory leak when attempting to use the v2 TLS
25457 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
25458 - We accidentally enabled the under-development v2 TLS handshake
25459 code, which was causing log entries like "TLS error while
25460 renegotiating handshake". Disable it again. Resolves bug 590.
25461 - We were computing the wrong Content-Length: header for directory
25462 responses that need to be compressed on the fly, causing clients
25463 asking for those items to always fail. Bugfix on 0.2.0.x; partially
25467 - Avoid going directly to the directory authorities even if you're a
25468 relay, if you haven't found yourself reachable yet or if you've
25469 decided not to advertise your dirport yet. Addresses bug 556.
25470 - If we've gone 12 hours since our last bandwidth check, and we
25471 estimate we have less than 50KB bandwidth capacity but we could
25472 handle more, do another bandwidth test.
25473 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
25474 Tor can warn and/or refuse connections to ports commonly used with
25475 vulnerable-plaintext protocols. Currently we warn on ports 23,
25476 109, 110, and 143, but we don't reject any.
25479 - When we setconf ClientOnly to 1, close any current OR and Dir
25480 listeners. Reported by mwenge.
25481 - When we get a consensus that's been signed by more people than
25482 we expect, don't log about it; it's not a big deal. Reported
25486 - Don't answer "/tor/networkstatus-bridges" directory requests if
25487 the request isn't encrypted.
25488 - Make "ClientOnly 1" config option disable directory ports too.
25489 - Patches from Karsten Loesing to make v2 hidden services more
25490 robust: work even when there aren't enough HSDir relays available;
25491 retry when a v2 rend desc fetch fails; but don't retry if we
25492 already have a usable v0 rend desc.
25495 Changes in version 0.2.0.17-alpha - 2008-01-17
25496 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
25499 - Make the tor-gencert man page get included correctly in the tarball.
25502 Changes in version 0.2.0.16-alpha - 2008-01-17
25503 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
25504 Loesing, and generally cleans up a lot of features and minor bugs.
25506 o New directory authorities:
25507 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
25510 o Major performance improvements:
25511 - Switch our old ring buffer implementation for one more like that
25512 used by free Unix kernels. The wasted space in a buffer with 1mb
25513 of data will now be more like 8k than 1mb. The new implementation
25514 also avoids realloc();realloc(); patterns that can contribute to
25515 memory fragmentation.
25518 - Configuration files now accept C-style strings as values. This
25519 helps encode characters not allowed in the current configuration
25520 file format, such as newline or #. Addresses bug 557.
25521 - Although we fixed bug 539 (where servers would send HTTP status 503
25522 responses _and_ send a body too), there are still servers out
25523 there that haven't upgraded. Therefore, make clients parse such
25524 bodies when they receive them.
25525 - When we're not serving v2 directory information, there is no reason
25526 to actually keep any around. Remove the obsolete files and directory
25527 on startup if they are very old and we aren't going to serve them.
25529 o Minor performance improvements:
25530 - Reference-count and share copies of address policy entries; only 5%
25531 of them were actually distinct.
25532 - Never walk through the list of logs if we know that no log is
25533 interested in a given message.
25536 - When an authority has not signed a consensus, do not try to
25537 download a nonexistent "certificate with key 00000000". Bugfix
25538 on 0.2.0.x. Fixes bug 569.
25539 - Fix a rare assert error when we're closing one of our threads:
25540 use a mutex to protect the list of logs, so we never write to the
25541 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
25542 bug 575, which is kind of the revenge of bug 222.
25543 - Patch from Karsten Loesing to complain less at both the client
25544 and the relay when a relay used to have the HSDir flag but doesn't
25545 anymore, and we try to upload a hidden service descriptor.
25546 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
25548 - Do not try to download missing certificates until we have tried
25549 to check our fallback consensus. Fixes bug 583.
25550 - Make bridges round reported GeoIP stats info up to the nearest
25551 estimate, not down. Now we can distinguish between "0 people from
25552 this country" and "1 person from this country".
25553 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
25554 - Avoid possible segfault if key generation fails in
25555 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
25556 - Avoid segfault in the case where a badly behaved v2 versioning
25557 directory sends a signed networkstatus with missing client-versions.
25559 - Avoid segfaults on certain complex invocations of
25560 router_get_by_hexdigest(). Bugfix on 0.1.2.
25561 - Correct bad index on array access in parse_http_time(). Bugfix
25563 - Fix possible bug in vote generation when server versions are present
25564 but client versions are not.
25565 - Fix rare bug on REDIRECTSTREAM control command when called with no
25566 port set: it could erroneously report an error when none had
25568 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
25569 compressing large objects and find ourselves with more than 4k
25570 left over. Bugfix on 0.2.0.
25571 - Fix a small memory leak when setting up a hidden service.
25572 - Fix a few memory leaks that could in theory happen under bizarre
25574 - Fix an assert if we post a general-purpose descriptor via the
25575 control port but that descriptor isn't mentioned in our current
25576 network consensus. Bug reported by Jon McLachlan; bugfix on
25579 o Minor features (controller):
25580 - Get NS events working again. Patch from tup.
25581 - The GETCONF command now escapes and quotes configuration values
25582 that don't otherwise fit into the torrc file.
25583 - The SETCONF command now handles quoted values correctly.
25585 o Minor features (directory authorities):
25586 - New configuration options to override default maximum number of
25587 servers allowed on a single IP address. This is important for
25588 running a test network on a single host.
25589 - Actually implement the -s option to tor-gencert.
25590 - Add a manual page for tor-gencert.
25592 o Minor features (bridges):
25593 - Bridge authorities no longer serve bridge descriptors over
25594 unencrypted connections.
25596 o Minor features (other):
25597 - Add hidden services and DNSPorts to the list of things that make
25598 Tor accept that it has running ports. Change starting Tor with no
25599 ports from a fatal error to a warning; we might change it back if
25600 this turns out to confuse anybody. Fixes bug 579.
25603 Changes in version 0.1.2.19 - 2008-01-17
25604 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
25605 exit policy a little bit more conservative so it's safer to run an
25606 exit relay on a home system, and fixes a variety of smaller issues.
25609 - Exit policies now reject connections that are addressed to a
25610 relay's public (external) IP address too, unless
25611 ExitPolicyRejectPrivate is turned off. We do this because too
25612 many relays are running nearby to services that trust them based
25613 on network address.
25616 - When the clock jumps forward a lot, do not allow the bandwidth
25617 buckets to become negative. Fixes bug 544.
25618 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
25619 on every successful resolve. Reported by Mike Perry.
25620 - Purge old entries from the "rephist" database and the hidden
25621 service descriptor database even when DirPort is zero.
25622 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
25623 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
25624 crashing or mis-answering these requests.
25625 - When we decide to send a 503 response to a request for servers, do
25626 not then also send the server descriptors: this defeats the whole
25627 purpose. Fixes bug 539.
25630 - Changing the ExitPolicyRejectPrivate setting should cause us to
25631 rebuild our server descriptor.
25632 - Fix handling of hex nicknames when answering controller requests for
25633 networkstatus by name, or when deciding whether to warn about
25634 unknown routers in a config option. (Patch from mwenge.)
25635 - Fix a couple of hard-to-trigger autoconf problems that could result
25636 in really weird results on platforms whose sys/types.h files define
25637 nonstandard integer types.
25638 - Don't try to create the datadir when running --verify-config or
25639 --hash-password. Resolves bug 540.
25640 - If we were having problems getting a particular descriptor from the
25641 directory caches, and then we learned about a new descriptor for
25642 that router, we weren't resetting our failure count. Reported
25644 - Although we fixed bug 539 (where servers would send HTTP status 503
25645 responses _and_ send a body too), there are still servers out there
25646 that haven't upgraded. Therefore, make clients parse such bodies
25647 when they receive them.
25648 - Run correctly on systems where rlim_t is larger than unsigned long.
25649 This includes some 64-bit systems.
25650 - Run correctly on platforms (like some versions of OS X 10.5) where
25651 the real limit for number of open files is OPEN_FILES, not rlim_max
25652 from getrlimit(RLIMIT_NOFILES).
25653 - Avoid a spurious free on base64 failure.
25654 - Avoid segfaults on certain complex invocations of
25655 router_get_by_hexdigest().
25656 - Fix rare bug on REDIRECTSTREAM control command when called with no
25657 port set: it could erroneously report an error when none had
25661 Changes in version 0.2.0.15-alpha - 2007-12-25
25662 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
25663 features added in 0.2.0.13-alpha.
25666 - Fix several remotely triggerable asserts based on DirPort requests
25667 for a v2 or v3 networkstatus object before we were prepared. This
25668 was particularly bad for 0.2.0.13 and later bridge relays, who
25669 would never have a v2 networkstatus and would thus always crash
25670 when used. Bugfixes on 0.2.0.x.
25671 - Estimate the v3 networkstatus size more accurately, rather than
25672 estimating it at zero bytes and giving it artificially high priority
25673 compared to other directory requests. Bugfix on 0.2.0.x.
25676 - Fix configure.in logic for cross-compilation.
25677 - When we load a bridge descriptor from the cache, and it was
25678 previously unreachable, mark it as retriable so we won't just
25679 ignore it. Also, try fetching a new copy immediately. Bugfixes
25681 - The bridge GeoIP stats were counting other relays, for example
25682 self-reachability and authority-reachability tests.
25685 - Support compilation to target iPhone; patch from cjacker huang.
25686 To build for iPhone, pass the --enable-iphone option to configure.
25689 Changes in version 0.2.0.14-alpha - 2007-12-23
25691 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
25692 without a datadirectory from a previous Tor install. Reported
25694 - Fix a crash when we fetch a descriptor that turns out to be
25695 unexpected (it used to be in our networkstatus when we started
25696 fetching it, but it isn't in our current networkstatus), and we
25697 aren't using bridges. Bugfix on 0.2.0.x.
25698 - Fix a crash when accessing hidden services: it would work the first
25699 time you use a given introduction point for your service, but
25700 on subsequent requests we'd be using garbage memory. Fixed by
25701 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
25702 - Fix a crash when we load a bridge descriptor from disk but we don't
25703 currently have a Bridge line for it in our torrc. Bugfix on
25707 - If bridge authorities set BridgePassword, they will serve a
25708 snapshot of known bridge routerstatuses from their DirPort to
25709 anybody who knows that password. Unset by default.
25712 - Make the unit tests build again.
25713 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
25714 - Make PublishServerDescriptor default to 1, so the default doesn't
25715 have to change as we invent new directory protocol versions.
25716 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
25717 be included unless sys/time.h is already included. Fixes
25718 bug 553. Bugfix on 0.2.0.x.
25719 - If we receive a general-purpose descriptor and then receive an
25720 identical bridge-purpose descriptor soon after, don't discard
25721 the next one as a duplicate.
25724 - If BridgeRelay is set to 1, then the default for
25725 PublishServerDescriptor is now "bridge" rather than "v2,v3".
25726 - If the user sets RelayBandwidthRate but doesn't set
25727 RelayBandwidthBurst, then make them equal rather than erroring out.
25730 Changes in version 0.2.0.13-alpha - 2007-12-21
25731 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
25732 Goodell, fixes many more bugs, and adds a lot of infrastructure for
25735 o New directory authorities:
25736 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
25740 - Only update guard status (usable / not usable) once we have
25741 enough directory information. This was causing us to always pick
25742 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
25743 causing us to discard all our guards on startup if we hadn't been
25744 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
25745 - Purge old entries from the "rephist" database and the hidden
25746 service descriptor databases even when DirPort is zero. Bugfix
25748 - We were ignoring our RelayBandwidthRate for the first 30 seconds
25749 after opening a circuit -- even a relayed circuit. Bugfix on
25751 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
25752 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
25753 crashing or mis-answering these types of requests.
25754 - Relays were publishing their server descriptor to v1 and v2
25755 directory authorities, but they didn't try publishing to v3-only
25756 authorities. Fix this; and also stop publishing to v1 authorities.
25758 - When we were reading router descriptors from cache, we were ignoring
25759 the annotations -- so for example we were reading in bridge-purpose
25760 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
25761 - When we decided to send a 503 response to a request for servers, we
25762 were then also sending the server descriptors: this defeats the
25763 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
25766 - Bridge relays now behave like clients with respect to time
25767 intervals for downloading new consensus documents -- otherwise they
25768 stand out. Bridge users now wait until the end of the interval,
25769 so their bridge relay will be sure to have a new consensus document.
25770 - Three new config options (AlternateDirAuthority,
25771 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
25772 user selectively replace the default directory authorities by type,
25773 rather than the all-or-nothing replacement that DirServer offers.
25774 - Tor can now be configured to read a GeoIP file from disk in one
25775 of two formats. This can be used by controllers to map IP addresses
25776 to countries. Eventually, it may support exit-by-country.
25777 - When possible, bridge relays remember which countries users
25778 are coming from, and report aggregate information in their
25779 extra-info documents, so that the bridge authorities can learn
25780 where Tor is blocked.
25781 - Bridge directory authorities now do reachability testing on the
25782 bridges they know. They provide router status summaries to the
25783 controller via "getinfo ns/purpose/bridge", and also dump summaries
25784 to a file periodically.
25785 - Stop fetching directory info so aggressively if your DirPort is
25786 on but your ORPort is off; stop fetching v2 dir info entirely.
25787 You can override these choices with the new FetchDirInfoEarly
25791 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
25792 consensus documents when there are too many relays at a single
25793 IP address. Now clear it in v2 network status documents too, and
25794 also clear it in routerinfo_t when the relay is no longer listed
25795 in the relevant networkstatus document.
25796 - Don't crash if we get an unexpected value for the
25797 PublishServerDescriptor config option. Reported by Matt Edman;
25798 bugfix on 0.2.0.9-alpha.
25799 - Our new v2 hidden service descriptor format allows descriptors
25800 that have no introduction points. But Tor crashed when we tried
25801 to build a descriptor with no intro points (and it would have
25802 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
25803 by Karsten Loesing.
25804 - Fix building with dmalloc 5.5.2 with glibc.
25805 - Reject uploaded descriptors and extrainfo documents if they're
25806 huge. Otherwise we'll cache them all over the network and it'll
25807 clog everything up. Reported by Aljosha Judmayer.
25808 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
25809 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
25810 - When the DANGEROUS_VERSION controller status event told us we're
25811 running an obsolete version, it used the string "OLD" to describe
25812 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
25813 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
25814 - If we can't expand our list of entry guards (e.g. because we're
25815 using bridges or we have StrictEntryNodes set), don't mark relays
25816 down when they fail a directory request. Otherwise we're too quick
25817 to mark all our entry points down. Bugfix on 0.1.2.x.
25818 - Fix handling of hex nicknames when answering controller requests for
25819 networkstatus by name, or when deciding whether to warn about unknown
25820 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
25821 - Fix a couple of hard-to-trigger autoconf problems that could result
25822 in really weird results on platforms whose sys/types.h files define
25823 nonstandard integer types. Bugfix on 0.1.2.x.
25824 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
25825 - Don't crash on name lookup when we have no current consensus. Fixes
25826 bug 538; bugfix on 0.2.0.x.
25827 - Only Tors that want to mirror the v2 directory info should
25828 create the "cached-status" directory in their datadir. (All Tors
25829 used to create it.) Bugfix on 0.2.0.9-alpha.
25830 - Directory authorities should only automatically download Extra Info
25831 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
25834 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
25835 consumers. (We already do this on HUP.)
25836 - Authorities and caches fetch the v2 networkstatus documents
25837 less often, now that v3 is encouraged.
25838 - Add a new config option BridgeRelay that specifies you want to
25839 be a bridge relay. Right now the only difference is that it makes
25840 you answer begin_dir requests, and it makes you cache dir info,
25841 even if your DirPort isn't on.
25842 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
25843 ask about source, timestamp of arrival, purpose, etc. We need
25844 something like this to help Vidalia not do GeoIP lookups on bridge
25846 - Allow multiple HashedControlPassword config lines, to support
25847 multiple controller passwords.
25848 - Authorities now decide whether they're authoritative for a given
25849 router based on the router's purpose.
25850 - New config options AuthDirBadDir and AuthDirListBadDirs for
25851 authorities to mark certain relays as "bad directories" in the
25852 networkstatus documents. Also supports the "!baddir" directive in
25853 the approved-routers file.
25856 Changes in version 0.2.0.12-alpha - 2007-11-16
25857 This twelfth development snapshot fixes some more build problems as
25858 well as a few minor bugs.
25861 - Make it build on OpenBSD again. Patch from tup.
25862 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
25863 package-building for Red Hat, OS X, etc.
25865 o Minor bugfixes (on 0.1.2.x):
25866 - Changing the ExitPolicyRejectPrivate setting should cause us to
25867 rebuild our server descriptor.
25869 o Minor bugfixes (on 0.2.0.x):
25870 - When we're lacking a consensus, don't try to perform rendezvous
25871 operations. Reported by Karsten Loesing.
25872 - Fix a small memory leak whenever we decide against using a
25873 newly picked entry guard. Reported by Mike Perry.
25874 - When authorities detected more than two relays running on the same
25875 IP address, they were clearing all the status flags but forgetting
25876 to clear the "hsdir" flag. So clients were being told that a
25877 given relay was the right choice for a v2 hsdir lookup, yet they
25878 never had its descriptor because it was marked as 'not running'
25880 - If we're trying to fetch a bridge descriptor and there's no way
25881 the bridge authority could help us (for example, we don't know
25882 a digest, or there is no bridge authority), don't be so eager to
25883 fall back to asking the bridge authority.
25884 - If we're using bridges or have strictentrynodes set, and our
25885 chosen exit is in the same family as all our bridges/entry guards,
25886 then be flexible about families.
25889 - When we negotiate a v2 link-layer connection (not yet implemented),
25890 accept RELAY_EARLY cells and turn them into RELAY cells if we've
25891 negotiated a v1 connection for their next step. Initial code for
25895 Changes in version 0.2.0.11-alpha - 2007-11-12
25896 This eleventh development snapshot fixes some build problems with
25897 the previous snapshot. It also includes a more secure-by-default exit
25898 policy for relays, fixes an enormous memory leak for exit relays, and
25899 fixes another bug where servers were falling out of the directory list.
25902 - Exit policies now reject connections that are addressed to a
25903 relay's public (external) IP address too, unless
25904 ExitPolicyRejectPrivate is turned off. We do this because too
25905 many relays are running nearby to services that trust them based
25906 on network address. Bugfix on 0.1.2.x.
25909 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
25910 on every successful resolve. Reported by Mike Perry; bugfix
25912 - On authorities, never downgrade to old router descriptors simply
25913 because they're listed in the consensus. This created a catch-22
25914 where we wouldn't list a new descriptor because there was an
25915 old one in the consensus, and we couldn't get the new one in the
25916 consensus because we wouldn't list it. Possible fix for bug 548.
25917 Also, this might cause bug 543 to appear on authorities; if so,
25918 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
25920 o Packaging fixes on 0.2.0.10-alpha:
25921 - We were including instructions about what to do with the
25922 src/config/fallback-consensus file, but we weren't actually
25923 including it in the tarball. Disable all of that for now.
25926 - Allow people to say PreferTunnelledDirConns rather than
25927 PreferTunneledDirConns, for those alternate-spellers out there.
25930 - Don't reevaluate all the information from our consensus document
25931 just because we've downloaded a v2 networkstatus that we intend
25932 to cache. Fixes bug 545; bugfix on 0.2.0.x.
25935 Changes in version 0.2.0.10-alpha - 2007-11-10
25936 This tenth development snapshot adds a third v3 directory authority
25937 run by Mike Perry, adds most of Karsten Loesing's new hidden service
25938 descriptor format, fixes a bad crash bug and new bridge bugs introduced
25939 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
25940 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
25941 addresses many more minor issues.
25943 o New directory authorities:
25944 - Set up ides (run by Mike Perry) as the third v3 directory authority.
25947 - Allow tunnelled directory connections to ask for an encrypted
25948 "begin_dir" connection or an anonymized "uses a full Tor circuit"
25949 connection independently. Now we can make anonymized begin_dir
25950 connections for (e.g.) more secure hidden service posting and
25952 - More progress on proposal 114: code from Karsten Loesing to
25953 implement new hidden service descriptor format.
25954 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
25955 accommodate the growing number of servers that use the default
25956 and are reaching it.
25957 - Directory authorities use a new formula for selecting which nodes
25958 to advertise as Guards: they must be in the top 7/8 in terms of
25959 how long we have known about them, and above the median of those
25960 nodes in terms of weighted fractional uptime.
25961 - Make "not enough dir info yet" warnings describe *why* Tor feels
25962 it doesn't have enough directory info yet.
25965 - Stop servers from crashing if they set a Family option (or
25966 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
25968 - Make bridge users work again -- the move to v3 directories in
25969 0.2.0.9-alpha had introduced a number of bugs that made bridges
25970 no longer work for clients.
25971 - When the clock jumps forward a lot, do not allow the bandwidth
25972 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
25974 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
25975 - When the consensus lists a router descriptor that we previously were
25976 mirroring, but that we considered non-canonical, reload the
25977 descriptor as canonical. This fixes bug 543 where Tor servers
25978 would start complaining after a few days that they don't have
25979 enough directory information to build a circuit.
25980 - Consider replacing the current consensus when certificates arrive
25981 that make the pending consensus valid. Previously, we were only
25982 considering replacement when the new certs _didn't_ help.
25983 - Fix an assert error on startup if we didn't already have the
25984 consensus and certs cached in our datadirectory: we were caching
25985 the consensus in consensus_waiting_for_certs but then free'ing it
25987 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
25988 Request) if we need more v3 certs but we've already got pending
25989 requests for all of them.
25990 - Correctly back off from failing certificate downloads. Fixes
25992 - Authorities don't vote on the Running flag if they have been running
25993 for less than 30 minutes themselves. Fixes bug 547, where a newly
25994 started authority would vote that everyone was down.
25996 o New requirements:
25997 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
25998 it, it had no AES, and it hasn't seen any security patches since
26002 - Clients now hold circuitless TLS connections open for 1.5 times
26003 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
26004 rebuild a new circuit over them within that timeframe. Previously,
26005 they held them open only for KeepalivePeriod (5 minutes).
26006 - Use "If-Modified-Since" to avoid retrieving consensus
26007 networkstatuses that we already have.
26008 - When we have no consensus, check FallbackNetworkstatusFile (defaults
26009 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
26010 we start knowing some directory caches.
26011 - When we receive a consensus from the future, warn about skew.
26012 - Improve skew reporting: try to give the user a better log message
26013 about how skewed they are, and how much this matters.
26014 - When we have a certificate for an authority, believe that
26015 certificate's claims about the authority's IP address.
26016 - New --quiet command-line option to suppress the default console log.
26017 Good in combination with --hash-password.
26018 - Authorities send back an X-Descriptor-Not-New header in response to
26019 an accepted-but-discarded descriptor upload. Partially implements
26021 - Make the log message for "tls error. breaking." more useful.
26022 - Better log messages about certificate downloads, to attempt to
26023 track down the second incarnation of bug 546.
26025 o Minor features (bridges):
26026 - If bridge users set UpdateBridgesFromAuthority, but the digest
26027 they ask for is a 404 from the bridge authority, they now fall
26028 back to trying the bridge directly.
26029 - Bridges now use begin_dir to publish their server descriptor to
26030 the bridge authority, even when they haven't set TunnelDirConns.
26032 o Minor features (controller):
26033 - When reporting clock skew, and we know that the clock is _at least
26034 as skewed_ as some value, but we don't know the actual value,
26035 report the value as a "minimum skew."
26038 - Update linux-tor-prio.sh script to allow QoS based on the uid of
26039 the Tor process. Patch from Marco Bonetti with tweaks from Mike
26043 - Refuse to start if both ORPort and UseBridges are set. Bugfix
26044 on 0.2.0.x, suggested by Matt Edman.
26045 - Don't stop fetching descriptors when FetchUselessDescriptors is
26046 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
26047 reported by tup and ioerror.
26048 - Better log message on vote from unknown authority.
26049 - Don't log "Launching 0 request for 0 router" message.
26051 o Minor bugfixes (memory leaks):
26052 - Stop leaking memory every time we parse a v3 certificate. Bugfix
26054 - Stop leaking memory every time we load a v3 certificate. Bugfix
26055 on 0.2.0.1-alpha. Fixes bug 536.
26056 - Stop leaking a cached networkstatus on exit. Bugfix on
26058 - Stop leaking voter information every time we free a consensus.
26059 Bugfix on 0.2.0.3-alpha.
26060 - Stop leaking signed data every time we check a voter signature.
26061 Bugfix on 0.2.0.3-alpha.
26062 - Stop leaking a signature every time we fail to parse a consensus or
26063 a vote. Bugfix on 0.2.0.3-alpha.
26064 - Stop leaking v2_download_status_map on shutdown. Bugfix on
26066 - Stop leaking conn->nickname every time we make a connection to a
26067 Tor relay without knowing its expected identity digest (e.g. when
26068 using bridges). Bugfix on 0.2.0.3-alpha.
26070 - Minor bugfixes (portability):
26071 - Run correctly on platforms where rlim_t is larger than unsigned
26072 long, and/or where the real limit for number of open files is
26073 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
26074 particular, these may be needed for OS X 10.5.
26077 Changes in version 0.1.2.18 - 2007-10-28
26078 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
26079 hidden service introduction that were causing huge delays, and a big
26080 bug that was causing some servers to disappear from the network status
26081 lists for a few hours each day.
26083 o Major bugfixes (crashes):
26084 - If a connection is shut down abruptly because of something that
26085 happened inside connection_flushed_some(), do not call
26086 connection_finished_flushing(). Should fix bug 451:
26087 "connection_stop_writing: Assertion conn->write_event failed"
26088 Bugfix on 0.1.2.7-alpha.
26089 - Fix possible segfaults in functions called from
26090 rend_process_relay_cell().
26092 o Major bugfixes (hidden services):
26093 - Hidden services were choosing introduction points uniquely by
26094 hexdigest, but when constructing the hidden service descriptor
26095 they merely wrote the (potentially ambiguous) nickname.
26096 - Clients now use the v2 intro format for hidden service
26097 connections: they specify their chosen rendezvous point by identity
26098 digest rather than by (potentially ambiguous) nickname. These
26099 changes could speed up hidden service connections dramatically.
26101 o Major bugfixes (other):
26102 - Stop publishing a new server descriptor just because we get a
26103 HUP signal. This led (in a roundabout way) to some servers getting
26104 dropped from the networkstatus lists for a few hours each day.
26105 - When looking for a circuit to cannibalize, consider family as well
26106 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
26107 circuit cannibalization).
26108 - When a router wasn't listed in a new networkstatus, we were leaving
26109 the flags for that router alone -- meaning it remained Named,
26110 Running, etc -- even though absence from the networkstatus means
26111 that it shouldn't be considered to exist at all anymore. Now we
26112 clear all the flags for routers that fall out of the networkstatus
26113 consensus. Fixes bug 529.
26116 - Don't try to access (or alter) the state file when running
26117 --list-fingerprint or --verify-config or --hash-password. Resolves
26119 - When generating information telling us how to extend to a given
26120 router, do not try to include the nickname if it is
26121 absent. Resolves bug 467.
26122 - Fix a user-triggerable segfault in expand_filename(). (There isn't
26123 a way to trigger this remotely.)
26124 - When sending a status event to the controller telling it that an
26125 OR address is reachable, set the port correctly. (Previously we
26126 were reporting the dir port.)
26127 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
26128 command. Bugfix on 0.1.2.17.
26129 - When loading bandwidth history, do not believe any information in
26130 the future. Fixes bug 434.
26131 - When loading entry guard information, do not believe any information
26133 - When we have our clock set far in the future and generate an
26134 onion key, then re-set our clock to be correct, we should not stop
26135 the onion key from getting rotated.
26136 - On some platforms, accept() can return a broken address. Detect
26137 this more quietly, and deal accordingly. Fixes bug 483.
26138 - It's not actually an error to find a non-pending entry in the DNS
26139 cache when canceling a pending resolve. Don't log unless stuff
26140 is fishy. Resolves bug 463.
26141 - Don't reset trusted dir server list when we set a configuration
26142 option. Patch from Robert Hogan.
26143 - Don't try to create the datadir when running --verify-config or
26144 --hash-password. Resolves bug 540.
26147 Changes in version 0.2.0.9-alpha - 2007-10-24
26148 This ninth development snapshot switches clients to the new v3 directory
26149 system; allows servers to be listed in the network status even when they
26150 have the same nickname as a registered server; and fixes many other
26151 bugs including a big one that was causing some servers to disappear
26152 from the network status lists for a few hours each day.
26154 o Major features (directory system):
26155 - Clients now download v3 consensus networkstatus documents instead
26156 of v2 networkstatus documents. Clients and caches now base their
26157 opinions about routers on these consensus documents. Clients only
26158 download router descriptors listed in the consensus.
26159 - Authorities now list servers who have the same nickname as
26160 a different named server, but list them with a new flag,
26161 "Unnamed". Now we can list servers that happen to pick the same
26162 nickname as a server that registered two years ago and then
26163 disappeared. Partially implements proposal 122.
26164 - If the consensus lists a router as "Unnamed", the name is assigned
26165 to a different router: do not identify the router by that name.
26166 Partially implements proposal 122.
26167 - Authorities can now come to a consensus on which method to use to
26168 compute the consensus. This gives us forward compatibility.
26171 - Stop publishing a new server descriptor just because we HUP or
26172 when we find our DirPort to be reachable but won't actually publish
26173 it. New descriptors without any real changes are dropped by the
26174 authorities, and can screw up our "publish every 18 hours" schedule.
26176 - When a router wasn't listed in a new networkstatus, we were leaving
26177 the flags for that router alone -- meaning it remained Named,
26178 Running, etc -- even though absence from the networkstatus means
26179 that it shouldn't be considered to exist at all anymore. Now we
26180 clear all the flags for routers that fall out of the networkstatus
26181 consensus. Fixes bug 529; bugfix on 0.1.2.x.
26182 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
26183 extrainfo documents and then discard them immediately for not
26184 matching the latest router. Bugfix on 0.2.0.1-alpha.
26186 o Minor features (v3 directory protocol):
26187 - Allow tor-gencert to generate a new certificate without replacing
26189 - Allow certificates to include an address.
26190 - When we change our directory-cache settings, reschedule all voting
26191 and download operations.
26192 - Reattempt certificate downloads immediately on failure, as long as
26193 we haven't failed a threshold number of times yet.
26194 - Delay retrying consensus downloads while we're downloading
26195 certificates to verify the one we just got. Also, count getting a
26196 consensus that we already have (or one that isn't valid) as a failure,
26197 and count failing to get the certificates after 20 minutes as a
26199 - Build circuits and download descriptors even if our consensus is a
26200 little expired. (This feature will go away once authorities are
26203 o Minor features (router descriptor cache):
26204 - If we find a cached-routers file that's been sitting around for more
26205 than 28 days unmodified, then most likely it's a leftover from
26206 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
26208 - When we (as a cache) download a descriptor because it was listed
26209 in a consensus, remember when the consensus was supposed to expire,
26210 and don't expire the descriptor until then.
26212 o Minor features (performance):
26213 - Call routerlist_remove_old_routers() much less often. This should
26214 speed startup, especially on directory caches.
26215 - Don't try to launch new descriptor downloads quite so often when we
26216 already have enough directory information to build circuits.
26217 - Base64 decoding was actually showing up on our profile when parsing
26218 the initial descriptor file; switch to an in-process all-at-once
26219 implementation that's about 3.5x times faster than calling out to
26222 o Minor features (compilation):
26223 - Detect non-ASCII platforms (if any still exist) and refuse to
26224 build there: some of our code assumes that 'A' is 65 and so on.
26226 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
26227 - Make the "next period" votes into "current period" votes immediately
26228 after publishing the consensus; avoid a heisenbug that made them
26229 stick around indefinitely.
26230 - When we discard a vote as a duplicate, do not report this as
26232 - Treat missing v3 keys or certificates as an error when running as a
26233 v3 directory authority.
26234 - When we're configured to be a v3 authority, but we're only listed
26235 as a non-v3 authority in our DirServer line for ourself, correct
26237 - If an authority doesn't have a qualified hostname, just put
26238 its address in the vote. This fixes the problem where we referred to
26239 "moria on moria:9031."
26240 - Distinguish between detached signatures for the wrong period, and
26241 detached signatures for a divergent vote.
26242 - Fix a small memory leak when computing a consensus.
26243 - When there's no consensus, we were forming a vote every 30
26244 minutes, but writing the "valid-after" line in our vote based
26245 on our configured V3AuthVotingInterval: so unless the intervals
26246 matched up, we immediately rejected our own vote because it didn't
26247 start at the voting interval that caused us to construct a vote.
26249 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
26250 - Delete unverified-consensus when the real consensus is set.
26251 - Consider retrying a consensus networkstatus fetch immediately
26252 after one fails: don't wait 60 seconds to notice.
26253 - When fetching a consensus as a cache, wait until a newer consensus
26254 should exist before trying to replace the current one.
26255 - Use a more forgiving schedule for retrying failed consensus
26256 downloads than for other types.
26258 o Minor bugfixes (other directory issues):
26259 - Correct the implementation of "download votes by digest." Bugfix on
26261 - Authorities no longer send back "400 you're unreachable please fix
26262 it" errors to Tor servers that aren't online all the time. We're
26263 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
26265 o Minor bugfixes (controller):
26266 - Don't reset trusted dir server list when we set a configuration
26267 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
26268 - Respond to INT and TERM SIGNAL commands before we execute the
26269 signal, in case the signal shuts us down. We had a patch in
26270 0.1.2.1-alpha that tried to do this by queueing the response on
26271 the connection's buffer before shutting down, but that really
26272 isn't the same thing at all. Bug located by Matt Edman.
26274 o Minor bugfixes (misc):
26275 - Correctly check for bad options to the "PublishServerDescriptor"
26276 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
26277 - Stop leaking memory on failing case of base32_decode, and make
26278 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
26279 - Don't try to download extrainfo documents when we're trying to
26280 fetch enough directory info to build a circuit: having enough
26281 info should get priority. Bugfix on 0.2.0.x.
26282 - Don't complain that "your server has not managed to confirm that its
26283 ports are reachable" if we haven't been able to build any circuits
26284 yet. Bug found by spending four hours without a v3 consensus. Bugfix
26286 - Detect the reason for failing to mmap a descriptor file we just
26287 wrote, and give a more useful log message. Fixes bug 533. Bugfix
26290 o Code simplifications and refactoring:
26291 - Remove support for the old bw_accounting file: we've been storing
26292 bandwidth accounting information in the state file since
26293 0.1.2.5-alpha. This may result in bandwidth accounting errors
26294 if you try to upgrade from 0.1.1.x or earlier, or if you try to
26295 downgrade to 0.1.1.x or earlier.
26296 - New convenience code to locate a file within the DataDirectory.
26297 - Move non-authority functionality out of dirvote.c.
26298 - Refactor the arguments for router_pick_{directory_|trusteddir}server
26299 so that they all take the same named flags.
26302 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
26303 Unix users an easy way to script their Tor process (e.g. by
26304 adjusting bandwidth based on the time of the day).
26307 Changes in version 0.2.0.8-alpha - 2007-10-12
26308 This eighth development snapshot fixes a crash bug that's been bothering
26309 us since February 2007, lets bridge authorities store a list of bridge
26310 descriptors they've seen, gets v3 directory voting closer to working,
26311 starts caching v3 directory consensus documents on directory mirrors,
26312 and fixes a variety of smaller issues including some minor memory leaks.
26314 o Major features (router descriptor cache):
26315 - Store routers in a file called cached-descriptors instead of in
26316 cached-routers. Initialize cached-descriptors from cached-routers
26317 if the old format is around. The new format allows us to store
26318 annotations along with descriptors.
26319 - Use annotations to record the time we received each descriptor, its
26320 source, and its purpose.
26321 - Disable the SETROUTERPURPOSE controller command: it is now
26323 - Controllers should now specify cache=no or cache=yes when using
26324 the +POSTDESCRIPTOR command.
26325 - Bridge authorities now write bridge descriptors to disk, meaning
26326 we can export them to other programs and begin distributing them
26329 o Major features (directory authorities):
26330 - When a v3 authority is missing votes or signatures, it now tries
26332 - Directory authorities track weighted fractional uptime as well as
26333 weighted mean-time-between failures. WFU is suitable for deciding
26334 whether a node is "usually up", while MTBF is suitable for deciding
26335 whether a node is "likely to stay up." We need both, because
26336 "usually up" is a good requirement for guards, while "likely to
26337 stay up" is a good requirement for long-lived connections.
26339 o Major features (v3 directory system):
26340 - Caches now download v3 network status documents as needed,
26341 and download the descriptors listed in them.
26342 - All hosts now attempt to download and keep fresh v3 authority
26343 certificates, and re-attempt after failures.
26344 - More internal-consistency checks for vote parsing.
26346 o Major bugfixes (crashes):
26347 - If a connection is shut down abruptly because of something that
26348 happened inside connection_flushed_some(), do not call
26349 connection_finished_flushing(). Should fix bug 451. Bugfix on
26352 o Major bugfixes (performance):
26353 - Fix really bad O(n^2) performance when parsing a long list of
26354 routers: Instead of searching the entire list for an "extra-info "
26355 string which usually wasn't there, once for every routerinfo
26356 we read, just scan lines forward until we find one we like.
26358 - When we add data to a write buffer in response to the data on that
26359 write buffer getting low because of a flush, do not consider the
26360 newly added data as a candidate for immediate flushing, but rather
26361 make it wait until the next round of writing. Otherwise, we flush
26362 and refill recursively, and a single greedy TLS connection can
26363 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
26365 o Minor features (v3 authority system):
26366 - Add more ways for tools to download the votes that lead to the
26368 - Send a 503 when low on bandwidth and a vote, consensus, or
26369 certificate is requested.
26370 - If-modified-since is now implemented properly for all kinds of
26371 certificate requests.
26373 o Minor bugfixes (network statuses):
26374 - Tweak the implementation of proposal 109 slightly: allow at most
26375 two Tor servers on the same IP address, except if it's the location
26376 of a directory authority, in which case allow five. Bugfix on
26379 o Minor bugfixes (controller):
26380 - When sending a status event to the controller telling it that an
26381 OR address is reachable, set the port correctly. (Previously we
26382 were reporting the dir port.) Bugfix on 0.1.2.x.
26384 o Minor bugfixes (v3 directory system):
26385 - Fix logic to look up a cert by its signing key digest. Bugfix on
26387 - Only change the reply to a vote to "OK" if it's not already
26388 set. This gets rid of annoying "400 OK" log messages, which may
26389 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
26390 - When we get a valid consensus, recompute the voting schedule.
26391 - Base the valid-after time of a vote on the consensus voting
26392 schedule, not on our preferred schedule.
26393 - Make the return values and messages from signature uploads and
26394 downloads more sensible.
26395 - Fix a memory leak when serving votes and consensus documents, and
26396 another when serving certificates.
26398 o Minor bugfixes (performance):
26399 - Use a slightly simpler string hashing algorithm (copying Python's
26400 instead of Java's) and optimize our digest hashing algorithm to take
26401 advantage of 64-bit platforms and to remove some possibly-costly
26403 - Fix a minor memory leak whenever we parse guards from our state
26404 file. Bugfix on 0.2.0.7-alpha.
26405 - Fix a minor memory leak whenever we write out a file. Bugfix on
26407 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
26408 command. Bugfix on 0.2.0.5-alpha.
26410 o Minor bugfixes (portability):
26411 - On some platforms, accept() can return a broken address. Detect
26412 this more quietly, and deal accordingly. Fixes bug 483.
26413 - Stop calling tor_strlower() on uninitialized memory in some cases.
26414 Bugfix in 0.2.0.7-alpha.
26416 o Minor bugfixes (usability):
26417 - Treat some 403 responses from directory servers as INFO rather than
26418 WARN-severity events.
26419 - It's not actually an error to find a non-pending entry in the DNS
26420 cache when canceling a pending resolve. Don't log unless stuff is
26421 fishy. Resolves bug 463.
26423 o Minor bugfixes (anonymity):
26424 - Never report that we've used more bandwidth than we're willing to
26425 relay: it leaks how much non-relay traffic we're using. Resolves
26427 - When looking for a circuit to cannibalize, consider family as well
26428 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
26429 circuit cannibalization).
26431 o Code simplifications and refactoring:
26432 - Make a bunch of functions static. Remove some dead code.
26433 - Pull out about a third of the really big routerlist.c; put it in a
26434 new module, networkstatus.c.
26435 - Merge the extra fields in local_routerstatus_t back into
26436 routerstatus_t: we used to need one routerstatus_t for each
26437 authority's opinion, plus a local_routerstatus_t for the locally
26438 computed consensus opinion. To save space, we put the locally
26439 modified fields into local_routerstatus_t, and only the common
26440 stuff into routerstatus_t. But once v3 directories are in use,
26441 clients and caches will no longer need to hold authority opinions;
26442 thus, the rationale for keeping the types separate is now gone.
26443 - Make the code used to reschedule and reattempt downloads more
26445 - Turn all 'Are we a directory server/mirror?' logic into a call to
26447 - Remove the code to generate the oldest (v1) directory format.
26448 The code has been disabled since 0.2.0.5-alpha.
26451 Changes in version 0.2.0.7-alpha - 2007-09-21
26452 This seventh development snapshot makes bridges work again, makes bridge
26453 authorities work for the first time, fixes two huge performance flaws
26454 in hidden services, and fixes a variety of minor issues.
26456 o New directory authorities:
26457 - Set up moria1 and tor26 as the first v3 directory authorities. See
26458 doc/spec/dir-spec.txt for details on the new directory design.
26460 o Major bugfixes (crashes):
26461 - Fix possible segfaults in functions called from
26462 rend_process_relay_cell(). Bugfix on 0.1.2.x.
26464 o Major bugfixes (bridges):
26465 - Fix a bug that made servers send a "404 Not found" in response to
26466 attempts to fetch their server descriptor. This caused Tor servers
26467 to take many minutes to establish reachability for their DirPort,
26468 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
26469 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
26470 users configure that and specify a bridge with an identity
26471 fingerprint, now they will lookup the bridge descriptor at the
26472 default bridge authority via a one-hop tunnel, but once circuits
26473 are established they will switch to a three-hop tunnel for later
26474 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
26476 o Major bugfixes (hidden services):
26477 - Hidden services were choosing introduction points uniquely by
26478 hexdigest, but when constructing the hidden service descriptor
26479 they merely wrote the (potentially ambiguous) nickname.
26480 - Clients now use the v2 intro format for hidden service
26481 connections: they specify their chosen rendezvous point by identity
26482 digest rather than by (potentially ambiguous) nickname. Both
26483 are bugfixes on 0.1.2.x, and they could speed up hidden service
26484 connections dramatically. Thanks to Karsten Loesing.
26486 o Minor features (security):
26487 - As a client, do not believe any server that tells us that an
26488 address maps to an internal address space.
26489 - Make it possible to enable HashedControlPassword and
26490 CookieAuthentication at the same time.
26492 o Minor features (guard nodes):
26493 - Tag every guard node in our state file with the version that
26494 we believe added it, or with our own version if we add it. This way,
26495 if a user temporarily runs an old version of Tor and then switches
26496 back to a new one, she doesn't automatically lose her guards.
26498 o Minor features (speed):
26499 - When implementing AES counter mode, update only the portions of the
26500 counter buffer that need to change, and don't keep separate
26501 network-order and host-order counters when they are the same (i.e.,
26502 on big-endian hosts.)
26504 o Minor features (controller):
26505 - Accept LF instead of CRLF on controller, since some software has a
26506 hard time generating real Internet newlines.
26507 - Add GETINFO values for the server status events
26508 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
26511 o Removed features:
26512 - Routers no longer include bandwidth-history lines in their
26513 descriptors; this information is already available in extra-info
26514 documents, and including it in router descriptors took up 60%
26515 (!) of compressed router descriptor downloads. Completes
26516 implementation of proposal 104.
26517 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
26518 and TorControl.py, as they use the old v0 controller protocol,
26519 and are obsoleted by TorFlow anyway.
26520 - Drop support for v1 rendezvous descriptors, since we never used
26521 them anyway, and the code has probably rotted by now. Based on
26522 patch from Karsten Loesing.
26523 - On OSX, stop warning the user that kqueue support in libevent is
26524 "experimental", since it seems to have worked fine for ages.
26527 - When generating information telling us how to extend to a given
26528 router, do not try to include the nickname if it is absent. Fixes
26529 bug 467. Bugfix on 0.2.0.3-alpha.
26530 - Fix a user-triggerable (but not remotely-triggerable) segfault
26531 in expand_filename(). Bugfix on 0.1.2.x.
26532 - Fix a memory leak when freeing incomplete requests from DNSPort.
26533 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
26534 - Don't try to access (or alter) the state file when running
26535 --list-fingerprint or --verify-config or --hash-password. (Resolves
26536 bug 499.) Bugfix on 0.1.2.x.
26537 - Servers used to decline to publish their DirPort if their
26538 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
26539 were below a threshold. Now they only look at BandwidthRate and
26540 RelayBandwidthRate. Bugfix on 0.1.2.x.
26541 - Remove an optimization in the AES counter-mode code that assumed
26542 that the counter never exceeded 2^68. When the counter can be set
26543 arbitrarily as an IV (as it is by Karsten's new hidden services
26544 code), this assumption no longer holds. Bugfix on 0.1.2.x.
26545 - Resume listing "AUTHORITY" flag for authorities in network status.
26546 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
26548 o Code simplifications and refactoring:
26549 - Revamp file-writing logic so we don't need to have the entire
26550 contents of a file in memory at once before we write to disk. Tor,
26552 - Turn "descriptor store" into a full-fledged type.
26553 - Move all NT services code into a separate source file.
26554 - Unify all code that computes medians, percentile elements, etc.
26555 - Get rid of a needless malloc when parsing address policies.
26558 Changes in version 0.1.2.17 - 2007-08-30
26559 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
26560 X bundles. Vidalia 0.0.14 makes authentication required for the
26561 ControlPort in the default configuration, which addresses important
26562 security risks. Everybody who uses Vidalia (or another controller)
26565 In addition, this Tor update fixes major load balancing problems with
26566 path selection, which should speed things up a lot once many people
26569 o Major bugfixes (security):
26570 - We removed support for the old (v0) control protocol. It has been
26571 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
26572 become more of a headache than it's worth.
26574 o Major bugfixes (load balancing):
26575 - When choosing nodes for non-guard positions, weight guards
26576 proportionally less, since they already have enough load. Patch
26578 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
26579 will allow fast Tor servers to get more attention.
26580 - When we're upgrading from an old Tor version, forget our current
26581 guards and pick new ones according to the new weightings. These
26582 three load balancing patches could raise effective network capacity
26583 by a factor of four. Thanks to Mike Perry for measurements.
26585 o Major bugfixes (stream expiration):
26586 - Expire not-yet-successful application streams in all cases if
26587 they've been around longer than SocksTimeout. Right now there are
26588 some cases where the stream will live forever, demanding a new
26589 circuit every 15 seconds. Fixes bug 454; reported by lodger.
26591 o Minor features (controller):
26592 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
26593 is valid before any authentication has been received. It tells
26594 a controller what kind of authentication is expected, and what
26595 protocol is spoken. Implements proposal 119.
26597 o Minor bugfixes (performance):
26598 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
26599 greatly speeding up loading cached-routers from disk on startup.
26600 - Disable sentinel-based debugging for buffer code: we squashed all
26601 the bugs that this was supposed to detect a long time ago, and now
26602 its only effect is to change our buffer sizes from nice powers of
26603 two (which platform mallocs tend to like) to values slightly over
26604 powers of two (which make some platform mallocs sad).
26606 o Minor bugfixes (misc):
26607 - If exit bandwidth ever exceeds one third of total bandwidth, then
26608 use the correct formula to weight exit nodes when choosing paths.
26609 Based on patch from Mike Perry.
26610 - Choose perfectly fairly among routers when choosing by bandwidth and
26611 weighting by fraction of bandwidth provided by exits. Previously, we
26612 would choose with only approximate fairness, and correct ourselves
26613 if we ran off the end of the list.
26614 - If we require CookieAuthentication but we fail to write the
26615 cookie file, we would warn but not exit, and end up in a state
26616 where no controller could authenticate. Now we exit.
26617 - If we require CookieAuthentication, stop generating a new cookie
26618 every time we change any piece of our config.
26619 - Refuse to start with certain directory authority keys, and
26620 encourage people using them to stop.
26621 - Terminate multi-line control events properly. Original patch
26623 - Fix a minor memory leak when we fail to find enough suitable
26624 servers to choose a circuit.
26625 - Stop leaking part of the descriptor when we run into a particularly
26626 unparseable piece of it.
26629 Changes in version 0.2.0.6-alpha - 2007-08-26
26630 This sixth development snapshot features a new Vidalia version in the
26631 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
26632 the ControlPort in the default configuration, which addresses important
26635 In addition, this snapshot fixes major load balancing problems
26636 with path selection, which should speed things up a lot once many
26637 people have upgraded. The directory authorities also use a new
26638 mean-time-between-failure approach to tracking which servers are stable,
26639 rather than just looking at the most recent uptime.
26641 o New directory authorities:
26642 - Set up Tonga as the default bridge directory authority.
26645 - Directory authorities now track servers by weighted
26646 mean-times-between-failures. When we have 4 or more days of data,
26647 use measured MTBF rather than declared uptime to decide whether
26648 to call a router Stable. Implements proposal 108.
26650 o Major bugfixes (load balancing):
26651 - When choosing nodes for non-guard positions, weight guards
26652 proportionally less, since they already have enough load. Patch
26654 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
26655 will allow fast Tor servers to get more attention.
26656 - When we're upgrading from an old Tor version, forget our current
26657 guards and pick new ones according to the new weightings. These
26658 three load balancing patches could raise effective network capacity
26659 by a factor of four. Thanks to Mike Perry for measurements.
26661 o Major bugfixes (descriptor parsing):
26662 - Handle unexpected whitespace better in malformed descriptors. Bug
26663 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
26666 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
26667 GETINFO for Torstat to use until it can switch to using extrainfos.
26668 - Optionally (if built with -DEXPORTMALLINFO) export the output
26669 of mallinfo via http, as tor/mallinfo.txt. Only accessible
26673 - Do not intermix bridge routers with controller-added
26674 routers. (Bugfix on 0.2.0.x)
26675 - Do not fail with an assert when accept() returns an unexpected
26676 address family. Addresses but does not wholly fix bug 483. (Bugfix
26678 - Let directory authorities startup even when they can't generate
26679 a descriptor immediately, e.g. because they don't know their
26681 - Stop putting the authentication cookie in a file called "0"
26682 in your working directory if you don't specify anything for the
26683 new CookieAuthFile option. Reported by Matt Edman.
26684 - Make it possible to read the PROTOCOLINFO response in a way that
26685 conforms to our control-spec. Reported by Matt Edman.
26686 - Fix a minor memory leak when we fail to find enough suitable
26687 servers to choose a circuit. Bugfix on 0.1.2.x.
26688 - Stop leaking part of the descriptor when we run into a particularly
26689 unparseable piece of it. Bugfix on 0.1.2.x.
26690 - Unmap the extrainfo cache file on exit.
26693 Changes in version 0.2.0.5-alpha - 2007-08-19
26694 This fifth development snapshot fixes compilation on Windows again;
26695 fixes an obnoxious client-side bug that slowed things down and put
26696 extra load on the network; gets us closer to using the v3 directory
26697 voting scheme; makes it easier for Tor controllers to use cookie-based
26698 authentication; and fixes a variety of other bugs.
26700 o Removed features:
26701 - Version 1 directories are no longer generated in full. Instead,
26702 authorities generate and serve "stub" v1 directories that list
26703 no servers. This will stop Tor versions 0.1.0.x and earlier from
26704 working, but (for security reasons) nobody should be running those
26707 o Major bugfixes (compilation, 0.2.0.x):
26708 - Try to fix Win32 compilation again: improve checking for IPv6 types.
26709 - Try to fix MSVC compilation: build correctly on platforms that do
26710 not define s6_addr16 or s6_addr32.
26711 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
26714 o Major bugfixes (stream expiration):
26715 - Expire not-yet-successful application streams in all cases if
26716 they've been around longer than SocksTimeout. Right now there are
26717 some cases where the stream will live forever, demanding a new
26718 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
26719 reported by lodger.
26721 o Minor features (directory servers):
26722 - When somebody requests a list of statuses or servers, and we have
26723 none of those, return a 404 rather than an empty 200.
26725 o Minor features (directory voting):
26726 - Store v3 consensus status consensuses on disk, and reload them
26729 o Minor features (security):
26730 - Warn about unsafe ControlPort configurations.
26731 - Refuse to start with certain directory authority keys, and
26732 encourage people using them to stop.
26734 o Minor features (controller):
26735 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
26736 is valid before any authentication has been received. It tells
26737 a controller what kind of authentication is expected, and what
26738 protocol is spoken. Implements proposal 119.
26739 - New config option CookieAuthFile to choose a new location for the
26740 cookie authentication file, and config option
26741 CookieAuthFileGroupReadable to make it group-readable.
26743 o Minor features (unit testing):
26744 - Add command-line arguments to unit-test executable so that we can
26745 invoke any chosen test from the command line rather than having
26746 to run the whole test suite at once; and so that we can turn on
26747 logging for the unit tests.
26749 o Minor bugfixes (on 0.1.2.x):
26750 - If we require CookieAuthentication but we fail to write the
26751 cookie file, we would warn but not exit, and end up in a state
26752 where no controller could authenticate. Now we exit.
26753 - If we require CookieAuthentication, stop generating a new cookie
26754 every time we change any piece of our config.
26755 - When loading bandwidth history, do not believe any information in
26756 the future. Fixes bug 434.
26757 - When loading entry guard information, do not believe any information
26759 - When we have our clock set far in the future and generate an
26760 onion key, then re-set our clock to be correct, we should not stop
26761 the onion key from getting rotated.
26762 - Clean up torrc sample config file.
26763 - Do not automatically run configure from autogen.sh. This
26764 non-standard behavior tended to annoy people who have built other
26767 o Minor bugfixes (on 0.2.0.x):
26768 - Fix a bug with AutomapHostsOnResolve that would always cause
26769 the second request to fail. Bug reported by Kate. Bugfix on
26771 - Fix a bug in ADDRMAP controller replies that would sometimes
26772 try to print a NULL. Patch from tup.
26773 - Read v3 directory authority keys from the right location.
26774 - Numerous bugfixes to directory voting code.
26777 Changes in version 0.1.2.16 - 2007-08-01
26778 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
26779 remote attacker in certain situations to rewrite the user's torrc
26780 configuration file. This can completely compromise anonymity of users
26781 in most configurations, including those running the Vidalia bundles,
26782 TorK, etc. Or worse.
26784 o Major security fixes:
26785 - Close immediately after missing authentication on control port;
26786 do not allow multiple authentication attempts.
26789 Changes in version 0.2.0.4-alpha - 2007-08-01
26790 This fourth development snapshot fixes a critical security vulnerability
26791 for most users, specifically those running Vidalia, TorK, etc. Everybody
26792 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
26794 o Major security fixes:
26795 - Close immediately after missing authentication on control port;
26796 do not allow multiple authentication attempts.
26798 o Major bugfixes (compilation):
26799 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
26802 o Minor features (performance):
26803 - Be even more aggressive about releasing RAM from small
26804 empty buffers. Thanks to our free-list code, this shouldn't be too
26805 performance-intensive.
26806 - Disable sentinel-based debugging for buffer code: we squashed all
26807 the bugs that this was supposed to detect a long time ago, and
26808 now its only effect is to change our buffer sizes from nice
26809 powers of two (which platform mallocs tend to like) to values
26810 slightly over powers of two (which make some platform mallocs sad).
26811 - Log malloc statistics from mallinfo() on platforms where it
26815 Changes in version 0.2.0.3-alpha - 2007-07-29
26816 This third development snapshot introduces new experimental
26817 blocking-resistance features and a preliminary version of the v3
26818 directory voting design, and includes many other smaller features
26822 - The first pieces of our "bridge" design for blocking-resistance
26823 are implemented. People can run bridge directory authorities;
26824 people can run bridges; and people can configure their Tor clients
26825 with a set of bridges to use as the first hop into the Tor network.
26826 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
26828 - Create listener connections before we setuid to the configured
26829 User and Group. Now non-Windows users can choose port values
26830 under 1024, start Tor as root, and have Tor bind those ports
26831 before it changes to another UID. (Windows users could already
26833 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
26834 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
26835 on "vserver" accounts. (Patch from coderman.)
26836 - Be even more aggressive about separating local traffic from relayed
26837 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
26839 o Major features (experimental):
26840 - First cut of code for "v3 dir voting": directory authorities will
26841 vote on a common network status document rather than each publishing
26842 their own opinion. This code needs more testing and more corner-case
26843 handling before it's ready for use.
26846 - Directory authorities now call routers Fast if their bandwidth is
26847 at least 100KB/s, and consider their bandwidth adequate to be a
26848 Guard if it is at least 250KB/s, no matter the medians. This fix
26849 complements proposal 107. [Bugfix on 0.1.2.x]
26850 - Directory authorities now never mark more than 3 servers per IP as
26851 Valid and Running. (Implements proposal 109, by Kevin Bauer and
26853 - Minor change to organizationName and commonName generation
26854 procedures in TLS certificates during Tor handshakes, to invalidate
26855 some earlier censorware approaches. This is not a long-term
26856 solution, but applying it will give us a bit of time to look into
26857 the epidemiology of countermeasures as they spread.
26859 o Major bugfixes (directory):
26860 - Rewrite directory tokenization code to never run off the end of
26861 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
26863 o Minor features (controller):
26864 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
26865 match requests to applications. (Patch from Robert Hogan.)
26866 - Report address and port correctly on connections to DNSPort. (Patch
26867 from Robert Hogan.)
26868 - Add a RESOLVE command to launch hostname lookups. (Original patch
26869 from Robert Hogan.)
26870 - Add GETINFO status/enough-dir-info to let controllers tell whether
26871 Tor has downloaded sufficient directory information. (Patch
26873 - You can now use the ControlSocket option to tell Tor to listen for
26874 controller connections on Unix domain sockets on systems that
26875 support them. (Patch from Peter Palfrader.)
26876 - STREAM NEW events are generated for DNSPort requests and for
26877 tunneled directory connections. (Patch from Robert Hogan.)
26878 - New "GETINFO address-mappings/*" command to get address mappings
26879 with expiry information. "addr-mappings/*" is now deprecated.
26882 o Minor features (misc):
26883 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
26885 - The tor-gencert tool for v3 directory authorities now creates all
26886 files as readable to the file creator only, and write-protects
26887 the authority identity key.
26888 - When dumping memory usage, list bytes used in buffer memory
26890 - When running with dmalloc, dump more stats on hup and on exit.
26891 - Directory authorities now fail quickly and (relatively) harmlessly
26892 if they generate a network status document that is somehow
26895 o Traffic load balancing improvements:
26896 - If exit bandwidth ever exceeds one third of total bandwidth, then
26897 use the correct formula to weight exit nodes when choosing paths.
26898 (Based on patch from Mike Perry.)
26899 - Choose perfectly fairly among routers when choosing by bandwidth and
26900 weighting by fraction of bandwidth provided by exits. Previously, we
26901 would choose with only approximate fairness, and correct ourselves
26902 if we ran off the end of the list. [Bugfix on 0.1.2.x]
26904 o Performance improvements:
26905 - Be more aggressive with freeing buffer RAM or putting it on the
26907 - Use Critical Sections rather than Mutexes for synchronizing threads
26908 on win32; Mutexes are heavier-weight, and designed for synchronizing
26911 o Deprecated and removed features:
26912 - RedirectExits is now deprecated.
26913 - Stop allowing address masks that do not correspond to bit prefixes.
26914 We have warned about these for a really long time; now it's time
26915 to reject them. (Patch from croup.)
26917 o Minor bugfixes (directory):
26918 - Fix another crash bug related to extra-info caching. (Bug found by
26919 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
26920 - Directories no longer return a "304 not modified" when they don't
26921 have the networkstatus the client asked for. Also fix a memory
26922 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
26923 - We had accidentally labelled 0.1.2.x directory servers as not
26924 suitable for begin_dir requests, and had labelled no directory
26925 servers as suitable for uploading extra-info documents. [Bugfix
26928 o Minor bugfixes (dns):
26929 - Fix a crash when DNSPort is set more than once. (Patch from Robert
26930 Hogan.) [Bugfix on 0.2.0.2-alpha]
26931 - Add DNSPort connections to the global connection list, so that we
26932 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
26934 - Fix a dangling reference that could lead to a crash when DNSPort is
26935 changed or closed (Patch from Robert Hogan.) [Bugfix on
26938 o Minor bugfixes (controller):
26939 - Provide DNS expiry times in GMT, not in local time. For backward
26940 compatibility, ADDRMAP events only provide GMT expiry in an extended
26941 field. "GETINFO address-mappings" always does the right thing.
26942 - Use CRLF line endings properly in NS events.
26943 - Terminate multi-line control events properly. (Original patch
26944 from tup.) [Bugfix on 0.1.2.x-alpha]
26945 - Do not include spaces in SOURCE_ADDR fields in STREAM
26946 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
26949 Changes in version 0.1.2.15 - 2007-07-17
26950 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
26951 problems, fixes compilation on BSD, and fixes a variety of other
26952 bugs. Everybody should upgrade.
26954 o Major bugfixes (compilation):
26955 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
26957 o Major bugfixes (crashes):
26958 - Try even harder not to dereference the first character after
26959 an mmap(). Reported by lodger.
26960 - Fix a crash bug in directory authorities when we re-number the
26961 routerlist while inserting a new router.
26962 - When the cached-routers file is an even multiple of the page size,
26963 don't run off the end and crash. (Fixes bug 455; based on idea
26965 - Fix eventdns.c behavior on Solaris: It is critical to include
26966 orconfig.h _before_ sys/types.h, so that we can get the expected
26967 definition of _FILE_OFFSET_BITS.
26969 o Major bugfixes (security):
26970 - Fix a possible buffer overrun when using BSD natd support. Bug
26972 - When sending destroy cells from a circuit's origin, don't include
26973 the reason for tearing down the circuit. The spec says we didn't,
26974 and now we actually don't. Reported by lodger.
26975 - Keep streamids from different exits on a circuit separate. This
26976 bug may have allowed other routers on a given circuit to inject
26977 cells into streams. Reported by lodger; fixes bug 446.
26978 - If there's a never-before-connected-to guard node in our list,
26979 never choose any guards past it. This way we don't expand our
26980 guard list unless we need to.
26982 o Minor bugfixes (guard nodes):
26983 - Weight guard selection by bandwidth, so that low-bandwidth nodes
26984 don't get overused as guards.
26986 o Minor bugfixes (directory):
26987 - Correctly count the number of authorities that recommend each
26988 version. Previously, we were under-counting by 1.
26989 - Fix a potential crash bug when we load many server descriptors at
26990 once and some of them make others of them obsolete. Fixes bug 458.
26992 o Minor bugfixes (hidden services):
26993 - Stop tearing down the whole circuit when the user asks for a
26994 connection to a port that the hidden service didn't configure.
26997 o Minor bugfixes (misc):
26998 - On Windows, we were preventing other processes from reading
26999 cached-routers while Tor was running. Reported by janbar.
27000 - Fix a possible (but very unlikely) bug in picking routers by
27001 bandwidth. Add a log message to confirm that it is in fact
27002 unlikely. Patch from lodger.
27003 - Backport a couple of memory leak fixes.
27004 - Backport miscellaneous cosmetic bugfixes.
27007 Changes in version 0.2.0.2-alpha - 2007-06-02
27008 o Major bugfixes on 0.2.0.1-alpha:
27009 - Fix an assertion failure related to servers without extra-info digests.
27010 Resolves bugs 441 and 442.
27012 o Minor features (directory):
27013 - Support "If-Modified-Since" when answering HTTP requests for
27014 directories, running-routers documents, and network-status documents.
27015 (There's no need to support it for router descriptors, since those
27016 are downloaded by descriptor digest.)
27018 o Minor build issues:
27019 - Clear up some MIPSPro compiler warnings.
27020 - When building from a tarball on a machine that happens to have SVK
27021 installed, report the micro-revision as whatever version existed
27022 in the tarball, not as "x".
27025 Changes in version 0.2.0.1-alpha - 2007-06-01
27026 This early development snapshot provides new features for people running
27027 Tor as both a client and a server (check out the new RelayBandwidth
27028 config options); lets Tor run as a DNS proxy; and generally moves us
27029 forward on a lot of fronts.
27031 o Major features, server usability:
27032 - New config options RelayBandwidthRate and RelayBandwidthBurst:
27033 a separate set of token buckets for relayed traffic. Right now
27034 relayed traffic is defined as answers to directory requests, and
27035 OR connections that don't have any local circuits on them.
27037 o Major features, client usability:
27038 - A client-side DNS proxy feature to replace the need for
27039 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
27040 for DNS requests on port 9999, use the Tor network to resolve them
27041 anonymously, and send the reply back like a regular DNS server.
27042 The code still only implements a subset of DNS.
27043 - Make PreferTunneledDirConns and TunnelDirConns work even when
27044 we have no cached directory info. This means Tor clients can now
27045 do all of their connections protected by TLS.
27047 o Major features, performance and efficiency:
27048 - Directory authorities accept and serve "extra info" documents for
27049 routers. These documents contain fields from router descriptors
27050 that aren't usually needed, and that use a lot of excess
27051 bandwidth. Once these fields are removed from router descriptors,
27052 the bandwidth savings should be about 60%. [Partially implements
27054 - Servers upload extra-info documents to any authority that accepts
27055 them. Authorities (and caches that have been configured to download
27056 extra-info documents) download them as needed. [Partially implements
27058 - Change the way that Tor buffers data that it is waiting to write.
27059 Instead of queueing data cells in an enormous ring buffer for each
27060 client->OR or OR->OR connection, we now queue cells on a separate
27061 queue for each circuit. This lets us use less slack memory, and
27062 will eventually let us be smarter about prioritizing different kinds
27064 - Use memory pools to allocate cells with better speed and memory
27065 efficiency, especially on platforms where malloc() is inefficient.
27066 - Stop reading on edge connections when their corresponding circuit
27067 buffers are full; start again as the circuits empty out.
27069 o Major features, other:
27070 - Add an HSAuthorityRecordStats option that hidden service authorities
27071 can use to track statistics of overall hidden service usage without
27072 logging information that would be very useful to an attacker.
27073 - Start work implementing multi-level keys for directory authorities:
27074 Add a standalone tool to generate key certificates. (Proposal 103.)
27077 - Directory authorities now call routers Stable if they have an
27078 uptime of at least 30 days, even if that's not the median uptime
27079 in the network. Implements proposal 107, suggested by Kevin Bauer
27082 o Minor fixes (resource management):
27083 - Count the number of open sockets separately from the number
27084 of active connection_t objects. This will let us avoid underusing
27085 our allocated connection limit.
27086 - We no longer use socket pairs to link an edge connection to an
27087 anonymous directory connection or a DirPort test connection.
27088 Instead, we track the link internally and transfer the data
27089 in-process. This saves two sockets per "linked" connection (at the
27090 client and at the server), and avoids the nasty Windows socketpair()
27092 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
27093 for every single inactive connection_t. Free items from the
27094 4k/16k-buffer free lists when they haven't been used for a while.
27096 o Minor features (build):
27097 - Make autoconf search for libevent, openssl, and zlib consistently.
27098 - Update deprecated macros in configure.in.
27099 - When warning about missing headers, tell the user to let us
27100 know if the compile succeeds anyway, so we can downgrade the
27102 - Include the current subversion revision as part of the version
27103 string: either fetch it directly if we're in an SVN checkout, do
27104 some magic to guess it if we're in an SVK checkout, or use
27105 the last-detected version if we're building from a .tar.gz.
27106 Use this version consistently in log messages.
27108 o Minor features (logging):
27109 - Always prepend "Bug: " to any log message about a bug.
27110 - Put a platform string (e.g. "Linux i686") in the startup log
27111 message, so when people paste just their logs, we know if it's
27112 OpenBSD or Windows or what.
27113 - When logging memory usage, break down memory used in buffers by
27116 o Minor features (directory system):
27117 - New config option V2AuthoritativeDirectory that all directory
27118 authorities should set. This will let future authorities choose
27119 not to serve V2 directory information.
27120 - Directory authorities allow multiple router descriptors and/or extra
27121 info documents to be uploaded in a single go. This will make
27122 implementing proposal 104 simpler.
27124 o Minor features (controller):
27125 - Add a new config option __DisablePredictedCircuits designed for
27126 use by the controller, when we don't want Tor to build any circuits
27128 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
27129 so we can exit from the middle of the circuit.
27130 - Implement "getinfo status/circuit-established".
27131 - Implement "getinfo status/version/..." so a controller can tell
27132 whether the current version is recommended, and whether any versions
27133 are good, and how many authorities agree. (Patch from shibz.)
27135 o Minor features (hidden services):
27136 - Allow multiple HiddenServicePort directives with the same virtual
27137 port; when they occur, the user is sent round-robin to one
27138 of the target ports chosen at random. Partially fixes bug 393 by
27139 adding limited ad-hoc round-robining.
27141 o Minor features (other):
27143 - Add a new AutomapHostsOnResolve option: when it is enabled, any
27144 resolve request for hosts matching a given pattern causes Tor to
27145 generate an internal virtual address mapping for that host. This
27146 allows DNSPort to work sensibly with hidden service users. By
27147 default, .exit and .onion addresses are remapped; the list of
27148 patterns can be reconfigured with AutomapHostsSuffixes.
27149 - Add an "-F" option to tor-resolve to force a resolve for a .onion
27150 address. Thanks to the AutomapHostsOnResolve option, this is no
27151 longer a completely silly thing to do.
27152 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
27153 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
27154 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
27155 minus 1 byte: the actual maximum declared bandwidth.
27157 o Removed features:
27158 - Removed support for the old binary "version 0" controller protocol.
27159 This has been deprecated since 0.1.1, and warnings have been issued
27160 since 0.1.2. When we encounter a v0 control message, we now send
27161 back an error and close the connection.
27162 - Remove the old "dns worker" server DNS code: it hasn't been default
27163 since 0.1.2.2-alpha, and all the servers seem to be using the new
27166 o Minor bugfixes (portability):
27167 - Even though Windows is equally happy with / and \ as path separators,
27168 try to use \ consistently on Windows and / consistently on Unix: it
27169 makes the log messages nicer.
27170 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
27171 - Read resolv.conf files correctly on platforms where read() returns
27172 partial results on small file reads.
27174 o Minor bugfixes (directory):
27175 - Correctly enforce that elements of directory objects do not appear
27176 more often than they are allowed to appear.
27177 - When we are reporting the DirServer line we just parsed, we were
27178 logging the second stanza of the key fingerprint, not the first.
27180 o Minor bugfixes (logging):
27181 - When we hit an EOF on a log (probably because we're shutting down),
27182 don't try to remove the log from the list: just mark it as
27183 unusable. (Bulletproofs against bug 222.)
27185 o Minor bugfixes (other):
27186 - In the exitlist script, only consider the most recently published
27187 server descriptor for each server. Also, when the user requests
27188 a list of servers that _reject_ connections to a given address,
27189 explicitly exclude the IPs that also have servers that accept
27190 connections to that address. (Resolves bug 405.)
27191 - Stop allowing hibernating servers to be "stable" or "fast".
27192 - On Windows, we were preventing other processes from reading
27193 cached-routers while Tor was running. (Reported by janbar)
27194 - Make the NodeFamilies config option work. (Reported by
27195 lodger -- it has never actually worked, even though we added it
27197 - Check return values from pthread_mutex functions.
27198 - Don't save non-general-purpose router descriptors to the disk cache,
27199 because we have no way of remembering what their purpose was when
27201 - Add even more asserts to hunt down bug 417.
27202 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
27203 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
27204 Add a log message to confirm that it is in fact unlikely.
27206 o Minor bugfixes (controller):
27207 - Make 'getinfo fingerprint' return a 551 error if we're not a
27208 server, so we match what the control spec claims we do. Reported
27210 - Fix a typo in an error message when extendcircuit fails that
27211 caused us to not follow the \r\n-based delimiter protocol. Reported
27214 o Code simplifications and refactoring:
27215 - Stop passing around circuit_t and crypt_path_t pointers that are
27216 implicit in other procedure arguments.
27217 - Drop the old code to choke directory connections when the
27218 corresponding OR connections got full: thanks to the cell queue
27219 feature, OR conns don't get full any more.
27220 - Make dns_resolve() handle attaching connections to circuits
27221 properly, so the caller doesn't have to.
27222 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
27223 - Keep the connection array as a dynamic smartlist_t, rather than as
27224 a fixed-sized array. This is important, as the number of connections
27225 is becoming increasingly decoupled from the number of sockets.
27228 Changes in version 0.1.2.14 - 2007-05-25
27229 Tor 0.1.2.14 changes the addresses of two directory authorities (this
27230 change especially affects those who serve or use hidden services),
27231 and fixes several other crash- and security-related bugs.
27233 o Directory authority changes:
27234 - Two directory authorities (moria1 and moria2) just moved to new
27235 IP addresses. This change will particularly affect those who serve
27236 or use hidden services.
27238 o Major bugfixes (crashes):
27239 - If a directory server runs out of space in the connection table
27240 as it's processing a begin_dir request, it will free the exit stream
27241 but leave it attached to the circuit, leading to unpredictable
27242 behavior. (Reported by seeess, fixes bug 425.)
27243 - Fix a bug in dirserv_remove_invalid() that would cause authorities
27244 to corrupt memory under some really unlikely scenarios.
27245 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
27246 - Avoid segfaults when reading from mmaped descriptor file. (Reported
27249 o Major bugfixes (security):
27250 - When choosing an entry guard for a circuit, avoid using guards
27251 that are in the same family as the chosen exit -- not just guards
27252 that are exactly the chosen exit. (Reported by lodger.)
27254 o Major bugfixes (resource management):
27255 - If a directory authority is down, skip it when deciding where to get
27256 networkstatus objects or descriptors. Otherwise we keep asking
27257 every 10 seconds forever. Fixes bug 384.
27258 - Count it as a failure if we fetch a valid network-status but we
27259 don't want to keep it. Otherwise we'll keep fetching it and keep
27260 not wanting to keep it. Fixes part of bug 422.
27261 - If all of our dirservers have given us bad or no networkstatuses
27262 lately, then stop hammering them once per minute even when we
27263 think they're failed. Fixes another part of bug 422.
27266 - Actually set the purpose correctly for descriptors inserted with
27267 purpose=controller.
27268 - When we have k non-v2 authorities in our DirServer config,
27269 we ignored the last k authorities in the list when updating our
27271 - Correctly back-off from requesting router descriptors that we are
27272 having a hard time downloading.
27273 - Read resolv.conf files correctly on platforms where read() returns
27274 partial results on small file reads.
27275 - Don't rebuild the entire router store every time we get 32K of
27276 routers: rebuild it when the journal gets very large, or when
27277 the gaps in the store get very large.
27280 - When routers publish SVN revisions in their router descriptors,
27281 authorities now include those versions correctly in networkstatus
27283 - Warn when using a version of libevent before 1.3b to run a server on
27284 OSX or BSD: these versions interact badly with userspace threads.
27287 Changes in version 0.1.2.13 - 2007-04-24
27288 This release features some major anonymity fixes, such as safer path
27289 selection; better client performance; faster bootstrapping, better
27290 address detection, and better DNS support for servers; write limiting as
27291 well as read limiting to make servers easier to run; and a huge pile of
27292 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
27294 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
27295 of the Freenode IRC network, remembering his patience and vision for
27296 free speech on the Internet.
27299 - Fix a memory leak when we ask for "all" networkstatuses and we
27300 get one we don't recognize.
27301 - Add more asserts to hunt down bug 417.
27302 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
27305 Changes in version 0.1.2.12-rc - 2007-03-16
27307 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
27308 directory information requested inside Tor connections (i.e. via
27309 begin_dir cells). It only triggered when the same connection was
27310 serving other data at the same time. Reported by seeess.
27313 - When creating a circuit via the controller, send a 'launched'
27314 event when we're done, so we follow the spec better.
27317 Changes in version 0.1.2.11-rc - 2007-03-15
27318 o Minor bugfixes (controller), reported by daejees:
27319 - Correct the control spec to match how the code actually responds
27320 to 'getinfo addr-mappings/*'.
27321 - The control spec described a GUARDS event, but the code
27322 implemented a GUARD event. Standardize on GUARD, but let people
27323 ask for GUARDS too.
27326 Changes in version 0.1.2.10-rc - 2007-03-07
27327 o Major bugfixes (Windows):
27328 - Do not load the NT services library functions (which may not exist)
27329 just to detect if we're a service trying to shut down. Now we run
27330 on Win98 and friends again.
27332 o Minor bugfixes (other):
27333 - Clarify a couple of log messages.
27334 - Fix a misleading socks5 error number.
27337 Changes in version 0.1.2.9-rc - 2007-03-02
27338 o Major bugfixes (Windows):
27339 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
27340 of the usual GCC "%llu". This prevents a bug when saving 64-bit
27341 int configuration values: the high-order 32 bits would get
27342 truncated. In particular, we were being bitten by the default
27343 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
27344 and maybe also bug 397.)
27346 o Minor bugfixes (performance):
27347 - Use OpenSSL's AES implementation on platforms where it's faster.
27348 This could save us as much as 10% CPU usage.
27350 o Minor bugfixes (server):
27351 - Do not rotate onion key immediately after setting it for the first
27354 o Minor bugfixes (directory authorities):
27355 - Stop calling servers that have been hibernating for a long time
27356 "stable". Also, stop letting hibernating or obsolete servers affect
27357 uptime and bandwidth cutoffs.
27358 - Stop listing hibernating servers in the v1 directory.
27360 o Minor bugfixes (hidden services):
27361 - Upload hidden service descriptors slightly less often, to reduce
27362 load on authorities.
27364 o Minor bugfixes (other):
27365 - Fix an assert that could trigger if a controller quickly set then
27366 cleared EntryNodes. Bug found by Udo van den Heuvel.
27367 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
27369 - Fix a potential race condition in the rpm installer. Found by
27371 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
27372 of 2 as indicating that the server is completely bad; it sometimes
27373 means that the server is just bad for the request in question. (may fix
27374 the last of bug 326.)
27375 - Disable encrypted directory connections when we don't have a server
27376 descriptor for the destination. We'll get this working again in
27380 Changes in version 0.1.2.8-beta - 2007-02-26
27381 o Major bugfixes (crashes):
27382 - Stop crashing when the controller asks us to resetconf more than
27383 one config option at once. (Vidalia 0.0.11 does this.)
27384 - Fix a crash that happened on Win98 when we're given command-line
27385 arguments: don't try to load NT service functions from advapi32.dll
27386 except when we need them. (Bug introduced in 0.1.2.7-alpha;
27388 - Fix a longstanding obscure crash bug that could occur when
27389 we run out of DNS worker processes. (Resolves bug 390.)
27391 o Major bugfixes (hidden services):
27392 - Correctly detect whether hidden service descriptor downloads are
27393 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
27395 o Major bugfixes (accounting):
27396 - When we start during an accounting interval before it's time to wake
27397 up, remember to wake up at the correct time. (May fix bug 342.)
27399 o Minor bugfixes (controller):
27400 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
27401 clear the corresponding on_circuit variable, and remember later
27402 that we don't need to send a redundant CLOSED event. Resolves part
27404 - Report events where a resolve succeeded or where we got a socks
27405 protocol error correctly, rather than calling both of them
27407 - Change reported stream target addresses to IP consistently when
27408 we finally get the IP from an exit node.
27409 - Send log messages to the controller even if they happen to be very
27412 o Minor bugfixes (other):
27413 - Display correct results when reporting which versions are
27414 recommended, and how recommended they are. (Resolves bug 383.)
27415 - Improve our estimates for directory bandwidth to be less random:
27416 guess that an unrecognized directory will have the average bandwidth
27417 from all known directories, not that it will have the average
27418 bandwidth from those directories earlier than it on the list.
27419 - If we start a server with ClientOnly 1, then set ClientOnly to 0
27420 and hup, stop triggering an assert based on an empty onion_key.
27421 - On platforms with no working mmap() equivalent, don't warn the
27422 user when cached-routers doesn't exist.
27423 - Warn the user when mmap() [or its equivalent] fails for some reason
27424 other than file-not-found.
27425 - Don't warn the user when cached-routers.new doesn't exist: that's
27426 perfectly fine when starting up for the first time.
27427 - When EntryNodes are configured, rebuild the guard list to contain,
27428 in order: the EntryNodes that were guards before; the rest of the
27429 EntryNodes; the nodes that were guards before.
27430 - Mask out all signals in sub-threads; only the libevent signal
27431 handler should be processing them. This should prevent some crashes
27432 on some machines using pthreads. (Patch from coderman.)
27433 - Fix switched arguments on memset in the implementation of
27434 tor_munmap() for systems with no mmap() call.
27435 - When Tor receives a router descriptor that it asked for, but
27436 no longer wants (because it has received fresh networkstatuses
27437 in the meantime), do not warn the user. Cache the descriptor if
27438 we're a cache; drop it if we aren't.
27439 - Make earlier entry guards _really_ get retried when the network
27441 - On a malformed DNS reply, always give an error to the corresponding
27443 - Build with recent libevents on platforms that do not define the
27444 nonstandard types "u_int8_t" and friends.
27446 o Minor features (controller):
27447 - Warn the user when an application uses the obsolete binary v0
27448 control protocol. We're planning to remove support for it during
27449 the next development series, so it's good to give people some
27451 - Add STREAM_BW events to report per-entry-stream bandwidth
27452 use. (Patch from Robert Hogan.)
27453 - Rate-limit SIGNEWNYM signals in response to controllers that
27454 impolitely generate them for every single stream. (Patch from
27455 mwenge; closes bug 394.)
27456 - Make REMAP stream events have a SOURCE (cache or exit), and
27457 make them generated in every case where we get a successful
27458 connected or resolved cell.
27460 o Minor bugfixes (performance):
27461 - Call router_have_min_dir_info half as often. (This is showing up in
27462 some profiles, but not others.)
27463 - When using GCC, make log_debug never get called at all, and its
27464 arguments never get evaluated, when no debug logs are configured.
27465 (This is showing up in some profiles, but not others.)
27468 - Remove some never-implemented options. Mark PathlenCoinWeight as
27470 - Implement proposal 106: Stop requiring clients to have well-formed
27471 certificates; stop checking nicknames in certificates. (Clients
27472 have certificates so that they can look like Tor servers, but in
27473 the future we might want to allow them to look like regular TLS
27474 clients instead. Nicknames in certificates serve no purpose other
27475 than making our protocol easier to recognize on the wire.)
27476 - Revise messages on handshake failure again to be even more clear about
27477 which are incoming connections and which are outgoing.
27478 - Discard any v1 directory info that's over 1 month old (for
27479 directories) or over 1 week old (for running-routers lists).
27480 - Do not warn when individual nodes in the configuration's EntryNodes,
27481 ExitNodes, etc are down: warn only when all possible nodes
27482 are down. (Fixes bug 348.)
27483 - Always remove expired routers and networkstatus docs before checking
27484 whether we have enough information to build circuits. (Fixes
27486 - Put a lower-bound on MaxAdvertisedBandwidth.
27489 Changes in version 0.1.2.7-alpha - 2007-02-06
27490 o Major bugfixes (rate limiting):
27491 - Servers decline directory requests much more aggressively when
27492 they're low on bandwidth. Otherwise they end up queueing more and
27493 more directory responses, which can't be good for latency.
27494 - But never refuse directory requests from local addresses.
27495 - Fix a memory leak when sending a 503 response for a networkstatus
27497 - Be willing to read or write on local connections (e.g. controller
27498 connections) even when the global rate limiting buckets are empty.
27499 - If our system clock jumps back in time, don't publish a negative
27500 uptime in the descriptor. Also, don't let the global rate limiting
27501 buckets go absurdly negative.
27502 - Flush local controller connection buffers periodically as we're
27503 writing to them, so we avoid queueing 4+ megabytes of data before
27506 o Major bugfixes (NT services):
27507 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
27508 command-line flag so that admins can override the default by saying
27509 "tor --service install --user "SomeUser"". This will not affect
27510 existing installed services. Also, warn the user that the service
27511 will look for its configuration file in the service user's
27512 %appdata% directory. (We can't do the 'hardwire the user's appdata
27513 directory' trick any more, since we may not have read access to that
27516 o Major bugfixes (other):
27517 - Previously, we would cache up to 16 old networkstatus documents
27518 indefinitely, if they came from nontrusted authorities. Now we
27519 discard them if they are more than 10 days old.
27520 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
27522 - Detect and reject malformed DNS responses containing circular
27524 - If exits are rare enough that we're not marking exits as guards,
27525 ignore exit bandwidth when we're deciding the required bandwidth
27527 - When we're handling a directory connection tunneled over Tor,
27528 don't fill up internal memory buffers with all the data we want
27529 to tunnel; instead, only add it if the OR connection that will
27530 eventually receive it has some room for it. (This can lead to
27531 slowdowns in tunneled dir connections; a better solution will have
27532 to wait for 0.2.0.)
27534 o Minor bugfixes (dns):
27535 - Add some defensive programming to eventdns.c in an attempt to catch
27536 possible memory-stomping bugs.
27537 - Detect and reject DNS replies containing IPv4 or IPv6 records with
27538 an incorrect number of bytes. (Previously, we would ignore the
27540 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
27541 in the correct order, and doesn't crash.
27542 - Free memory held in recently-completed DNS lookup attempts on exit.
27543 This was not a memory leak, but may have been hiding memory leaks.
27544 - Handle TTL values correctly on reverse DNS lookups.
27545 - Treat failure to parse resolv.conf as an error.
27547 o Minor bugfixes (other):
27548 - Fix crash with "tor --list-fingerprint" (reported by seeess).
27549 - When computing clock skew from directory HTTP headers, consider what
27550 time it was when we finished asking for the directory, not what
27552 - Expire socks connections if they spend too long waiting for the
27553 handshake to finish. Previously we would let them sit around for
27554 days, if the connecting application didn't close them either.
27555 - And if the socks handshake hasn't started, don't send a
27556 "DNS resolve socks failed" handshake reply; just close it.
27557 - Stop using C functions that OpenBSD's linker doesn't like.
27558 - Don't launch requests for descriptors unless we have networkstatuses
27559 from at least half of the authorities. This delays the first
27560 download slightly under pathological circumstances, but can prevent
27561 us from downloading a bunch of descriptors we don't need.
27562 - Do not log IPs with TLS failures for incoming TLS
27563 connections. (Fixes bug 382.)
27564 - If the user asks to use invalid exit nodes, be willing to use
27566 - Stop using the reserved ac_cv namespace in our configure script.
27567 - Call stat() slightly less often; use fstat() when possible.
27568 - Refactor the way we handle pending circuits when an OR connection
27569 completes or fails, in an attempt to fix a rare crash bug.
27570 - Only rewrite a conn's address based on X-Forwarded-For: headers
27571 if it's a parseable public IP address; and stop adding extra quotes
27572 to the resulting address.
27575 - Weight directory requests by advertised bandwidth. Now we can
27576 let servers enable write limiting but still allow most clients to
27577 succeed at their directory requests. (We still ignore weights when
27578 choosing a directory authority; I hope this is a feature.)
27581 - Create a new file ReleaseNotes which was the old ChangeLog. The
27582 new ChangeLog file now includes the summaries for all development
27584 - Check for addresses with invalid characters at the exit as well
27585 as at the client, and warn less verbosely when they fail. You can
27586 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
27587 - Adapt a patch from goodell to let the contrib/exitlist script
27588 take arguments rather than require direct editing.
27589 - Inform the server operator when we decide not to advertise a
27590 DirPort due to AccountingMax enabled or a low BandwidthRate. It
27591 was confusing Zax, so now we're hopefully more helpful.
27592 - Bring us one step closer to being able to establish an encrypted
27593 directory tunnel without knowing a descriptor first. Still not
27594 ready yet. As part of the change, now assume we can use a
27595 create_fast cell if we don't know anything about a router.
27596 - Allow exit nodes to use nameservers running on ports other than 53.
27597 - Servers now cache reverse DNS replies.
27598 - Add an --ignore-missing-torrc command-line option so that we can
27599 get the "use sensible defaults if the configuration file doesn't
27600 exist" behavior even when specifying a torrc location on the command
27603 o Minor features (controller):
27604 - Track reasons for OR connection failure; make these reasons
27605 available via the controller interface. (Patch from Mike Perry.)
27606 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
27607 can learn when clients are sending malformed hostnames to Tor.
27608 - Clean up documentation for controller status events.
27609 - Add a REMAP status to stream events to note that a stream's
27610 address has changed because of a cached address or a MapAddress
27614 Changes in version 0.1.2.6-alpha - 2007-01-09
27616 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
27617 connection handles more than 4 gigs in either direction, we crash.
27618 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
27619 advertised exit node, somebody might try to exit from us when
27620 we're bootstrapping and before we've built our descriptor yet.
27621 Refuse the connection rather than crashing.
27624 - Warn if we (as a server) find that we've resolved an address that we
27625 weren't planning to resolve.
27626 - Warn that using select() on any libevent version before 1.1 will be
27627 unnecessarily slow (even for select()).
27628 - Flush ERR-level controller status events just like we currently
27629 flush ERR-level log events, so that a Tor shutdown doesn't prevent
27630 the controller from learning about current events.
27632 o Minor features (more controller status events):
27633 - Implement EXTERNAL_ADDRESS server status event so controllers can
27634 learn when our address changes.
27635 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
27636 can learn when directories reject our descriptor.
27637 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
27638 can learn when a client application is speaking a non-socks protocol
27640 - Implement DANGEROUS_SOCKS client status event so controllers
27641 can learn when a client application is leaking DNS addresses.
27642 - Implement BUG general status event so controllers can learn when
27643 Tor is unhappy about its internal invariants.
27644 - Implement CLOCK_SKEW general status event so controllers can learn
27645 when Tor thinks the system clock is set incorrectly.
27646 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
27647 server status events so controllers can learn when their descriptors
27648 are accepted by a directory.
27649 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
27650 server status events so controllers can learn about Tor's progress in
27651 deciding whether it's reachable from the outside.
27652 - Implement BAD_LIBEVENT general status event so controllers can learn
27653 when we have a version/method combination in libevent that needs to
27655 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
27656 and DNS_USELESS server status events so controllers can learn
27657 about changes to DNS server status.
27659 o Minor features (directory):
27660 - Authorities no longer recommend exits as guards if this would shift
27661 too much load to the exit nodes.
27664 Changes in version 0.1.2.5-alpha - 2007-01-06
27666 - Enable write limiting as well as read limiting. Now we sacrifice
27667 capacity if we're pushing out lots of directory traffic, rather
27668 than overrunning the user's intended bandwidth limits.
27669 - Include TLS overhead when counting bandwidth usage; previously, we
27670 would count only the bytes sent over TLS, but not the bytes used
27672 - Support running the Tor service with a torrc not in the same
27673 directory as tor.exe and default to using the torrc located in
27674 the %appdata%\Tor\ of the user who installed the service. Patch
27676 - Servers now check for the case when common DNS requests are going to
27677 wildcarded addresses (i.e. all getting the same answer), and change
27678 their exit policy to reject *:* if it's happening.
27679 - Implement BEGIN_DIR cells, so we can connect to the directory
27680 server via TLS to do encrypted directory requests rather than
27681 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
27682 config options if you like.
27684 o Minor features (config and docs):
27685 - Start using the state file to store bandwidth accounting data:
27686 the bw_accounting file is now obsolete. We'll keep generating it
27687 for a while for people who are still using 0.1.2.4-alpha.
27688 - Try to batch changes to the state file so that we do as few
27689 disk writes as possible while still storing important things in
27691 - The state file and the bw_accounting file get saved less often when
27692 the AvoidDiskWrites config option is set.
27693 - Make PIDFile work on Windows (untested).
27694 - Add internal descriptions for a bunch of configuration options:
27695 accessible via controller interface and in comments in saved
27697 - Reject *:563 (NNTPS) in the default exit policy. We already reject
27698 NNTP by default, so this seems like a sensible addition.
27699 - Clients now reject hostnames with invalid characters. This should
27700 avoid some inadvertent info leaks. Add an option
27701 AllowNonRFC953Hostnames to disable this behavior, in case somebody
27702 is running a private network with hosts called @, !, and #.
27703 - Add a maintainer script to tell us which options are missing
27704 documentation: "make check-docs".
27705 - Add a new address-spec.txt document to describe our special-case
27706 addresses: .exit, .onion, and .noconnnect.
27708 o Minor features (DNS):
27709 - Ongoing work on eventdns infrastructure: now it has dns server
27710 and ipv6 support. One day Tor will make use of it.
27711 - Add client-side caching for reverse DNS lookups.
27712 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
27713 - When we change nameservers or IP addresses, reset and re-launch
27714 our tests for DNS hijacking.
27716 o Minor features (directory):
27717 - Authorities now specify server versions in networkstatus. This adds
27718 about 2% to the size of compressed networkstatus docs, and allows
27719 clients to tell which servers support BEGIN_DIR and which don't.
27720 The implementation is forward-compatible with a proposed future
27721 protocol version scheme not tied to Tor versions.
27722 - DirServer configuration lines now have an orport= option so
27723 clients can open encrypted tunnels to the authorities without
27724 having downloaded their descriptors yet. Enabled for moria1,
27725 moria2, tor26, and lefkada now in the default configuration.
27726 - Directory servers are more willing to send a 503 "busy" if they
27727 are near their write limit, especially for v1 directory requests.
27728 Now they can use their limited bandwidth for actual Tor traffic.
27729 - Clients track responses with status 503 from dirservers. After a
27730 dirserver has given us a 503, we try not to use it until an hour has
27731 gone by, or until we have no dirservers that haven't given us a 503.
27732 - When we get a 503 from a directory, and we're not a server, we don't
27733 count the failure against the total number of failures allowed
27734 for the thing we're trying to download.
27735 - Report X-Your-Address-Is correctly from tunneled directory
27736 connections; don't report X-Your-Address-Is when it's an internal
27737 address; and never believe reported remote addresses when they're
27739 - Protect against an unlikely DoS attack on directory servers.
27740 - Add a BadDirectory flag to network status docs so that authorities
27741 can (eventually) tell clients about caches they believe to be
27744 o Minor features (controller):
27745 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
27746 - Reimplement GETINFO so that info/names stays in sync with the
27748 - Implement "GETINFO fingerprint".
27749 - Implement "SETEVENTS GUARD" so controllers can get updates on
27750 entry guard status as it changes.
27752 o Minor features (clean up obsolete pieces):
27753 - Remove some options that have been deprecated since at least
27754 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
27755 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
27756 to set log options.
27757 - We no longer look for identity and onion keys in "identity.key" and
27758 "onion.key" -- these were replaced by secret_id_key and
27759 secret_onion_key in 0.0.8pre1.
27760 - We no longer require unrecognized directory entries to be
27763 o Major bugfixes (security):
27764 - Stop sending the HttpProxyAuthenticator string to directory
27765 servers when directory connections are tunnelled through Tor.
27766 - Clients no longer store bandwidth history in the state file.
27767 - Do not log introduction points for hidden services if SafeLogging
27769 - When generating bandwidth history, round down to the nearest
27770 1k. When storing accounting data, round up to the nearest 1k.
27771 - When we're running as a server, remember when we last rotated onion
27772 keys, so that we will rotate keys once they're a week old even if
27773 we never stay up for a week ourselves.
27775 o Major bugfixes (other):
27776 - Fix a longstanding bug in eventdns that prevented the count of
27777 timed-out resolves from ever being reset. This bug caused us to
27778 give up on a nameserver the third time it timed out, and try it
27779 10 seconds later... and to give up on it every time it timed out
27781 - Take out the '5 second' timeout from the connection retry
27782 schedule. Now the first connect attempt will wait a full 10
27783 seconds before switching to a new circuit. Perhaps this will help
27784 a lot. Based on observations from Mike Perry.
27785 - Fix a bug on the Windows implementation of tor_mmap_file() that
27786 would prevent the cached-routers file from ever loading. Reported
27790 - Fix an assert failure when a directory authority sets
27791 AuthDirRejectUnlisted and then receives a descriptor from an
27792 unlisted router. Reported by seeess.
27793 - Avoid a double-free when parsing malformed DirServer lines.
27794 - Fix a bug when a BSD-style PF socket is first used. Patch from
27796 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
27797 to resolve an address at a given exit node even when they ask for
27799 - Servers no longer ever list themselves in their "family" line,
27800 even if configured to do so. This makes it easier to configure
27801 family lists conveniently.
27802 - When running as a server, don't fall back to 127.0.0.1 when no
27803 nameservers are configured in /etc/resolv.conf; instead, make the
27804 user fix resolv.conf or specify nameservers explicitly. (Resolves
27806 - Stop accepting certain malformed ports in configured exit policies.
27807 - Don't re-write the fingerprint file every restart, unless it has
27809 - Stop warning when a single nameserver fails: only warn when _all_ of
27810 our nameservers have failed. Also, when we only have one nameserver,
27811 raise the threshold for deciding that the nameserver is dead.
27812 - Directory authorities now only decide that routers are reachable
27813 if their identity keys are as expected.
27814 - When the user uses bad syntax in the Log config line, stop
27815 suggesting other bad syntax as a replacement.
27816 - Correctly detect ipv6 DNS capability on OpenBSD.
27818 o Minor bugfixes (controller):
27819 - Report the circuit number correctly in STREAM CLOSED events. Bug
27820 reported by Mike Perry.
27821 - Do not report bizarre values for results of accounting GETINFOs
27822 when the last second's write or read exceeds the allotted bandwidth.
27823 - Report "unrecognized key" rather than an empty string when the
27824 controller tries to fetch a networkstatus that doesn't exist.
27827 Changes in version 0.1.1.26 - 2006-12-14
27828 o Security bugfixes:
27829 - Stop sending the HttpProxyAuthenticator string to directory
27830 servers when directory connections are tunnelled through Tor.
27831 - Clients no longer store bandwidth history in the state file.
27832 - Do not log introduction points for hidden services if SafeLogging
27836 - Fix an assert failure when a directory authority sets
27837 AuthDirRejectUnlisted and then receives a descriptor from an
27838 unlisted router (reported by seeess).
27841 Changes in version 0.1.2.4-alpha - 2006-12-03
27843 - Add support for using natd; this allows FreeBSDs earlier than
27844 5.1.2 to have ipfw send connections through Tor without using
27845 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
27848 - Make all connections to addresses of the form ".noconnect"
27849 immediately get closed. This lets application/controller combos
27850 successfully test whether they're talking to the same Tor by
27851 watching for STREAM events.
27852 - Make cross.sh cross-compilation script work even when autogen.sh
27853 hasn't been run. (Patch from Michael Mohr.)
27854 - Statistics dumped by -USR2 now include a breakdown of public key
27855 operations, for profiling.
27858 - Fix a major leak when directory authorities parse their
27859 approved-routers list, a minor memory leak when we fail to pick
27860 an exit node, and a few rare leaks on errors.
27861 - Handle TransPort connections even when the server sends data before
27862 the client sends data. Previously, the connection would just hang
27863 until the client sent data. (Patch from tup based on patch from
27865 - Avoid assert failure when our cached-routers file is empty on
27869 - Don't log spurious warnings when we see a circuit close reason we
27870 don't recognize; it's probably just from a newer version of Tor.
27871 - Have directory authorities allow larger amounts of drift in uptime
27872 without replacing the server descriptor: previously, a server that
27873 restarted every 30 minutes could have 48 "interesting" descriptors
27875 - Start linking to the Tor specification and Tor reference manual
27876 correctly in the Windows installer.
27877 - Add Vidalia to the OS X uninstaller script, so when we uninstall
27878 Tor/Privoxy we also uninstall Vidalia.
27879 - Resume building on Irix64, and fix a lot of warnings from its
27880 MIPSpro C compiler.
27881 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
27882 when we're running as a client.
27885 Changes in version 0.1.1.25 - 2006-11-04
27887 - When a client asks us to resolve (rather than connect to)
27888 an address, and we have a cached answer, give them the cached
27889 answer. Previously, we would give them no answer at all.
27890 - We were building exactly the wrong circuits when we predict
27891 hidden service requirements, meaning Tor would have to build all
27892 its circuits on demand.
27893 - If none of our live entry guards have a high uptime, but we
27894 require a guard with a high uptime, try adding a new guard before
27895 we give up on the requirement. This patch should make long-lived
27896 connections more stable on average.
27897 - When testing reachability of our DirPort, don't launch new
27898 tests when there's already one in progress -- unreachable
27899 servers were stacking up dozens of testing streams.
27901 o Security bugfixes:
27902 - When the user sends a NEWNYM signal, clear the client-side DNS
27903 cache too. Otherwise we continue to act on previous information.
27906 - Avoid a memory corruption bug when creating a hash table for
27908 - Avoid possibility of controller-triggered crash when misusing
27909 certain commands from a v0 controller on platforms that do not
27910 handle printf("%s",NULL) gracefully.
27911 - Avoid infinite loop on unexpected controller input.
27912 - Don't log spurious warnings when we see a circuit close reason we
27913 don't recognize; it's probably just from a newer version of Tor.
27914 - Add Vidalia to the OS X uninstaller script, so when we uninstall
27915 Tor/Privoxy we also uninstall Vidalia.
27918 Changes in version 0.1.2.3-alpha - 2006-10-29
27920 - Prepare for servers to publish descriptors less often: never
27921 discard a descriptor simply for being too old until either it is
27922 recommended by no authorities, or until we get a better one for
27923 the same router. Make caches consider retaining old recommended
27924 routers for even longer.
27925 - If most authorities set a BadExit flag for a server, clients
27926 don't think of it as a general-purpose exit. Clients only consider
27927 authorities that advertise themselves as listing bad exits.
27928 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
27929 headers for content, so that we can work better in the presence of
27930 caching HTTP proxies.
27931 - Allow authorities to list nodes as bad exits by fingerprint or by
27934 o Minor features, controller:
27935 - Add a REASON field to CIRC events; for backward compatibility, this
27936 field is sent only to controllers that have enabled the extended
27937 event format. Also, add additional reason codes to explain why
27938 a given circuit has been destroyed or truncated. (Patches from
27940 - Add a REMOTE_REASON field to extended CIRC events to tell the
27941 controller about why a remote OR told us to close a circuit.
27942 - Stream events also now have REASON and REMOTE_REASON fields,
27943 working much like those for circuit events.
27944 - There's now a GETINFO ns/... field so that controllers can ask Tor
27945 about the current status of a router.
27946 - A new event type "NS" to inform a controller when our opinion of
27947 a router's status has changed.
27948 - Add a GETINFO events/names and GETINFO features/names so controllers
27949 can tell which events and features are supported.
27950 - A new CLEARDNSCACHE signal to allow controllers to clear the
27951 client-side DNS cache without expiring circuits.
27953 o Security bugfixes:
27954 - When the user sends a NEWNYM signal, clear the client-side DNS
27955 cache too. Otherwise we continue to act on previous information.
27958 - Avoid sending junk to controllers or segfaulting when a controller
27959 uses EVENT_NEW_DESC with verbose nicknames.
27960 - Stop triggering asserts if the controller tries to extend hidden
27961 service circuits (reported by mwenge).
27962 - Avoid infinite loop on unexpected controller input.
27963 - When the controller does a "GETINFO network-status", tell it
27964 about even those routers whose descriptors are very old, and use
27965 long nicknames where appropriate.
27966 - Change NT service functions to be loaded on demand. This lets us
27967 build with MinGW without breaking Tor for Windows 98 users.
27968 - Do DirPort reachability tests less often, since a single test
27969 chews through many circuits before giving up.
27970 - In the hidden service example in torrc.sample, stop recommending
27971 esoteric and discouraged hidden service options.
27972 - When stopping an NT service, wait up to 10 sec for it to actually
27973 stop. Patch from Matt Edman; resolves bug 295.
27974 - Fix handling of verbose nicknames with ORCONN controller events:
27975 make them show up exactly when requested, rather than exactly when
27977 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
27978 printing a duplicate "$" in the keys we send (reported by mwenge).
27979 - Correctly set maximum connection limit on Cygwin. (This time
27981 - Try to detect Windows correctly when cross-compiling.
27982 - Detect the size of the routers file correctly even if it is
27983 corrupted (on systems without mmap) or not page-aligned (on systems
27984 with mmap). This bug was harmless.
27985 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
27986 to open a stream fails; now we do in more cases. This should
27987 make clients able to find a good exit faster in some cases, since
27988 unhandleable requests will now get an error rather than timing out.
27989 - Resolve two memory leaks when rebuilding the on-disk router cache
27990 (reported by fookoowa).
27991 - Clean up minor code warnings suggested by the MIPSpro C compiler,
27992 and reported by some Centos users.
27993 - Controller signals now work on non-Unix platforms that don't define
27994 SIGUSR1 and SIGUSR2 the way we expect.
27995 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
27996 values before failing, and always enables eventdns.
27997 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
27998 Try to fix this in configure.in by checking for most functions
27999 before we check for libevent.
28002 Changes in version 0.1.2.2-alpha - 2006-10-07
28004 - Make our async eventdns library on-by-default for Tor servers,
28005 and plan to deprecate the separate dnsworker threads.
28006 - Add server-side support for "reverse" DNS lookups (using PTR
28007 records so clients can determine the canonical hostname for a given
28008 IPv4 address). Only supported by servers using eventdns; servers
28009 now announce in their descriptors whether they support eventdns.
28010 - Specify and implement client-side SOCKS5 interface for reverse DNS
28011 lookups (see doc/socks-extensions.txt).
28012 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
28013 connect to directory servers through Tor. Previously, clients needed
28014 to find Tor exits to make private connections to directory servers.
28015 - Avoid choosing Exit nodes for entry or middle hops when the
28016 total bandwidth available from non-Exit nodes is much higher than
28017 the total bandwidth available from Exit nodes.
28018 - Workaround for name servers (like Earthlink's) that hijack failing
28019 DNS requests and replace the no-such-server answer with a "helpful"
28020 redirect to an advertising-driven search portal. Also work around
28021 DNS hijackers who "helpfully" decline to hijack known-invalid
28022 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
28023 lets you turn it off.
28024 - Send out a burst of long-range padding cells once we've established
28025 that we're reachable. Spread them over 4 circuits, so hopefully
28026 a few will be fast. This exercises our bandwidth and bootstraps
28027 us into the directory more quickly.
28029 o New/improved config options:
28030 - Add new config option "ResolvConf" to let the server operator
28031 choose an alternate resolve.conf file when using eventdns.
28032 - Add an "EnforceDistinctSubnets" option to control our "exclude
28033 servers on the same /16" behavior. It's still on by default; this
28034 is mostly for people who want to operate private test networks with
28035 all the machines on the same subnet.
28036 - If one of our entry guards is on the ExcludeNodes list, or the
28037 directory authorities don't think it's a good guard, treat it as
28038 if it were unlisted: stop using it as a guard, and throw it off
28039 the guards list if it stays that way for a long time.
28040 - Allow directory authorities to be marked separately as authorities
28041 for the v1 directory protocol, the v2 directory protocol, and
28042 as hidden service directories, to make it easier to retire old
28043 authorities. V1 authorities should set "HSAuthoritativeDir 1"
28044 to continue being hidden service authorities too.
28045 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
28047 o Minor features, controller:
28048 - Fix CIRC controller events so that controllers can learn the
28049 identity digests of non-Named servers used in circuit paths.
28050 - Let controllers ask for more useful identifiers for servers. Instead
28051 of learning identity digests for un-Named servers and nicknames
28052 for Named servers, the new identifiers include digest, nickname,
28053 and indication of Named status. Off by default; see control-spec.txt
28054 for more information.
28055 - Add a "getinfo address" controller command so it can display Tor's
28056 best guess to the user.
28057 - New controller event to alert the controller when our server
28058 descriptor has changed.
28059 - Give more meaningful errors on controller authentication failure.
28061 o Minor features, other:
28062 - When asked to resolve a hostname, don't use non-exit servers unless
28063 requested to do so. This allows servers with broken DNS to be
28064 useful to the network.
28065 - Divide eventdns log messages into warn and info messages.
28066 - Reserve the nickname "Unnamed" for routers that can't pick
28067 a hostname: any router can call itself Unnamed; directory
28068 authorities will never allocate Unnamed to any particular router;
28069 clients won't believe that any router is the canonical Unnamed.
28070 - Only include function names in log messages for info/debug messages.
28071 For notice/warn/err, the content of the message should be clear on
28072 its own, and printing the function name only confuses users.
28073 - Avoid some false positives during reachability testing: don't try
28074 to test via a server that's on the same /24 as us.
28075 - If we fail to build a circuit to an intended enclave, and it's
28076 not mandatory that we use that enclave, stop wanting it.
28077 - When eventdns is enabled, allow multithreaded builds on NetBSD and
28078 OpenBSD. (We had previously disabled threads on these platforms
28079 because they didn't have working thread-safe resolver functions.)
28081 o Major bugfixes, anonymity/security:
28082 - If a client asked for a server by name, and there's a named server
28083 in our network-status but we don't have its descriptor yet, we
28084 could return an unnamed server instead.
28085 - Fix NetBSD bug that could allow someone to force uninitialized RAM
28086 to be sent to a server's DNS resolver. This only affects NetBSD
28087 and other platforms that do not bounds-check tolower().
28088 - Reject (most) attempts to use Tor circuits with length one. (If
28089 many people start using Tor as a one-hop proxy, exit nodes become
28090 a more attractive target for compromise.)
28091 - Just because your DirPort is open doesn't mean people should be
28092 able to remotely teach you about hidden service descriptors. Now
28093 only accept rendezvous posts if you've got HSAuthoritativeDir set.
28095 o Major bugfixes, other:
28096 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
28097 - When a client asks the server to resolve (not connect to)
28098 an address, and it has a cached answer, give them the cached answer.
28099 Previously, the server would give them no answer at all.
28100 - Allow really slow clients to not hang up five minutes into their
28101 directory downloads (suggested by Adam J. Richter).
28102 - We were building exactly the wrong circuits when we anticipated
28103 hidden service requirements, meaning Tor would have to build all
28104 its circuits on demand.
28105 - Avoid crashing when we mmap a router cache file of size 0.
28106 - When testing reachability of our DirPort, don't launch new
28107 tests when there's already one in progress -- unreachable
28108 servers were stacking up dozens of testing streams.
28110 o Minor bugfixes, correctness:
28111 - If we're a directory mirror and we ask for "all" network status
28112 documents, we would discard status documents from authorities
28113 we don't recognize.
28114 - Avoid a memory corruption bug when creating a hash table for
28116 - Avoid controller-triggered crash when misusing certain commands
28117 from a v0 controller on platforms that do not handle
28118 printf("%s",NULL) gracefully.
28119 - Don't crash when a controller sends a third argument to an
28120 "extendcircuit" request.
28121 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
28122 response; fix error code when "getinfo dir/status/" fails.
28123 - Avoid crash when telling controller stream-status and a stream
28125 - Patch from Adam Langley to fix assert() in eventdns.c.
28126 - Fix a debug log message in eventdns to say "X resolved to Y"
28127 instead of "X resolved to X".
28128 - Make eventdns give strings for DNS errors, not just error numbers.
28129 - Track unreachable entry guards correctly: don't conflate
28130 'unreachable by us right now' with 'listed as down by the directory
28131 authorities'. With the old code, if a guard was unreachable by
28132 us but listed as running, it would clog our guard list forever.
28133 - Behave correctly in case we ever have a network with more than
28134 2GB/s total advertised capacity.
28135 - Make TrackExitHosts case-insensitive, and fix the behavior of
28136 ".suffix" TrackExitHosts items to avoid matching in the middle of
28138 - Finally fix the openssl warnings from newer gccs that believe that
28139 ignoring a return value is okay, but casting a return value and
28140 then ignoring it is a sign of madness.
28141 - Prevent the contrib/exitlist script from printing the same
28142 result more than once.
28143 - Patch from Steve Hildrey: Generate network status correctly on
28144 non-versioning dirservers.
28145 - Don't listen to the X-Your-Address-Is hint if you did the lookup
28146 via Tor; otherwise you'll think you're the exit node's IP address.
28148 o Minor bugfixes, performance:
28149 - Two small performance improvements on parsing descriptors.
28150 - Major performance improvement on inserting descriptors: change
28151 algorithm from O(n^2) to O(n).
28152 - Make the common memory allocation path faster on machines where
28153 malloc(0) returns a pointer.
28154 - Start remembering X-Your-Address-Is directory hints even if you're
28155 a client, so you can become a server more smoothly.
28156 - Avoid duplicate entries on MyFamily line in server descriptor.
28158 o Packaging, features:
28159 - Remove architecture from OS X builds. The official builds are
28160 now universal binaries.
28161 - The Debian package now uses --verify-config when (re)starting,
28162 to distinguish configuration errors from other errors.
28163 - Update RPMs to require libevent 1.1b.
28165 o Packaging, bugfixes:
28166 - Patches so Tor builds with MinGW on Windows.
28167 - Patches so Tor might run on Cygwin again.
28168 - Resume building on non-gcc compilers and ancient gcc. Resume
28169 building with the -O0 compile flag. Resume building cleanly on
28171 - Run correctly on OS X platforms with case-sensitive filesystems.
28172 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
28173 - Add autoconf checks so Tor can build on Solaris x86 again.
28176 - Documented (and renamed) ServerDNSSearchDomains and
28177 ServerDNSResolvConfFile options.
28178 - Be clearer that the *ListenAddress directives can be repeated
28182 Changes in version 0.1.1.24 - 2006-09-29
28184 - Allow really slow clients to not hang up five minutes into their
28185 directory downloads (suggested by Adam J. Richter).
28186 - Fix major performance regression from 0.1.0.x: instead of checking
28187 whether we have enough directory information every time we want to
28188 do something, only check when the directory information has changed.
28189 This should improve client CPU usage by 25-50%.
28190 - Don't crash if, after a server has been running for a while,
28191 it can't resolve its hostname.
28194 - Allow Tor to start when RunAsDaemon is set but no logs are set.
28195 - Don't crash when the controller receives a third argument to an
28196 "extendcircuit" request.
28197 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
28198 response; fix error code when "getinfo dir/status/" fails.
28199 - Fix configure.in to not produce broken configure files with
28200 more recent versions of autoconf. Thanks to Clint for his auto*
28202 - Fix security bug on NetBSD that could allow someone to force
28203 uninitialized RAM to be sent to a server's DNS resolver. This
28204 only affects NetBSD and other platforms that do not bounds-check
28206 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
28207 methods: these are known to be buggy.
28208 - If we're a directory mirror and we ask for "all" network status
28209 documents, we would discard status documents from authorities
28210 we don't recognize.
28213 Changes in version 0.1.2.1-alpha - 2006-08-27
28215 - Add "eventdns" async dns library from Adam Langley, tweaked to
28216 build on OSX and Windows. Only enabled if you pass the
28217 --enable-eventdns argument to configure.
28218 - Allow servers with no hostname or IP address to learn their
28219 IP address by asking the directory authorities. This code only
28220 kicks in when you would normally have exited with a "no address"
28221 error. Nothing's authenticated, so use with care.
28222 - Rather than waiting a fixed amount of time between retrying
28223 application connections, we wait only 5 seconds for the first,
28224 10 seconds for the second, and 15 seconds for each retry after
28225 that. Hopefully this will improve the expected user experience.
28226 - Patch from Tup to add support for transparent AP connections:
28227 this basically bundles the functionality of trans-proxy-tor
28228 into the Tor mainline. Now hosts with compliant pf/netfilter
28229 implementations can redirect TCP connections straight to Tor
28230 without diverting through SOCKS. Needs docs.
28231 - Busy directory servers save lots of memory by spooling server
28232 descriptors, v1 directories, and v2 networkstatus docs to buffers
28233 as needed rather than en masse. Also mmap the cached-routers
28234 files, so we don't need to keep the whole thing in memory too.
28235 - Automatically avoid picking more than one node from the same
28236 /16 network when constructing a circuit.
28237 - Revise and clean up the torrc.sample that we ship with; add
28238 a section for BandwidthRate and BandwidthBurst.
28241 - Split circuit_t into origin_circuit_t and or_circuit_t, and
28242 split connection_t into edge, or, dir, control, and base structs.
28243 These will save quite a bit of memory on busy servers, and they'll
28244 also help us track down bugs in the code and bugs in the spec.
28245 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
28246 or later. Log when we are doing this, so we can diagnose it when
28247 it fails. (Also, recommend libevent 1.1b for kqueue and
28248 win32 methods; deprecate libevent 1.0b harder; make libevent
28249 recommendation system saner.)
28250 - Start being able to build universal binaries on OS X (thanks
28252 - Export the default exit policy via the control port, so controllers
28253 don't need to guess what it is / will be later.
28254 - Add a man page entry for ProtocolWarnings.
28255 - Add TestVia config option to the man page.
28256 - Remove even more protocol-related warnings from Tor server logs,
28257 such as bad TLS handshakes and malformed begin cells.
28258 - Stop fetching descriptors if you're not a dir mirror and you
28259 haven't tried to establish any circuits lately. [This currently
28260 causes some dangerous behavior, because when you start up again
28261 you'll use your ancient server descriptors.]
28262 - New DirPort behavior: if you have your dirport set, you download
28263 descriptors aggressively like a directory mirror, whether or not
28264 your ORPort is set.
28265 - Get rid of the router_retry_connections notion. Now routers
28266 no longer try to rebuild long-term connections to directory
28267 authorities, and directory authorities no longer try to rebuild
28268 long-term connections to all servers. We still don't hang up
28269 connections in these two cases though -- we need to look at it
28270 more carefully to avoid flapping, and we likely need to wait til
28271 0.1.1.x is obsolete.
28272 - Drop compatibility with obsolete Tors that permit create cells
28273 to have the wrong circ_id_type.
28274 - Re-enable per-connection rate limiting. Get rid of the "OP
28275 bandwidth" concept. Lay groundwork for "bandwidth classes" --
28276 separate global buckets that apply depending on what sort of conn
28278 - Start publishing one minute or so after we find our ORPort
28279 to be reachable. This will help reduce the number of descriptors
28280 we have for ourselves floating around, since it's quite likely
28281 other things (e.g. DirPort) will change during that minute too.
28282 - Fork the v1 directory protocol into its own spec document,
28283 and mark dir-spec.txt as the currently correct (v2) spec.
28286 - When we find our DirPort to be reachable, publish a new descriptor
28287 so we'll tell the world (reported by pnx).
28288 - Publish a new descriptor after we hup/reload. This is important
28289 if our config has changed such that we'll want to start advertising
28290 our DirPort now, etc.
28291 - Allow Tor to start when RunAsDaemon is set but no logs are set.
28292 - When we have a state file we cannot parse, tell the user and
28293 move it aside. Now we avoid situations where the user starts
28294 Tor in 1904, Tor writes a state file with that timestamp in it,
28295 the user fixes her clock, and Tor refuses to start.
28296 - Fix configure.in to not produce broken configure files with
28297 more recent versions of autoconf. Thanks to Clint for his auto*
28299 - "tor --verify-config" now exits with -1(255) or 0 depending on
28300 whether the config options are bad or good.
28301 - Resolve bug 321 when using dnsworkers: append a period to every
28302 address we resolve at the exit node, so that we do not accidentally
28303 pick up local addresses, and so that failing searches are retried
28304 in the resolver search domains. (This is already solved for
28305 eventdns.) (This breaks Blossom servers for now.)
28306 - If we are using an exit enclave and we can't connect, e.g. because
28307 its webserver is misconfigured to not listen on localhost, then
28308 back off and try connecting from somewhere else before we fail.
28311 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
28312 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
28313 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
28314 when the IP address is mapped through MapAddress to a hostname.
28315 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
28316 useless IPv6 DNS resolves.
28317 - Patch suggested by Karsten Loesing: respond to SIGNAL command
28318 before we execute the signal, in case the signal shuts us down.
28319 - Clean up AllowInvalidNodes man page entry.
28320 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
28321 - Add more asserts to track down an assert error on a windows Tor
28322 server with connection_add being called with socket == -1.
28323 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
28324 - Fix misleading log messages: an entry guard that is "unlisted",
28325 as well as not known to be "down" (because we've never heard
28326 of it), is not therefore "up".
28327 - Remove code to special-case "-cvs" ending, since it has not
28328 actually mattered since 0.0.9.
28329 - Make our socks5 handling more robust to broken socks clients:
28330 throw out everything waiting on the buffer in between socks
28331 handshake phases, since they can't possibly (so the theory
28332 goes) have predicted what we plan to respond to them.
28335 Changes in version 0.1.1.23 - 2006-07-30
28337 - Fast Tor servers, especially exit nodes, were triggering asserts
28338 due to a bug in handling the list of pending DNS resolves. Some
28339 bugs still remain here; we're hunting them.
28340 - Entry guards could crash clients by sending unexpected input.
28341 - More fixes on reachability testing: if you find yourself reachable,
28342 then don't ever make any client requests (so you stop predicting
28343 circuits), then hup or have your clock jump, then later your IP
28344 changes, you won't think circuits are working, so you won't try to
28345 test reachability, so you won't publish.
28348 - Avoid a crash if the controller does a resetconf firewallports
28349 and then a setconf fascistfirewall=1.
28350 - Avoid an integer underflow when the dir authority decides whether
28351 a router is stable: we might wrongly label it stable, and compute
28352 a slightly wrong median stability, when a descriptor is published
28354 - Fix a place where we might trigger an assert if we can't build our
28355 own server descriptor yet.
28358 Changes in version 0.1.1.22 - 2006-07-05
28360 - Fix a big bug that was causing servers to not find themselves
28361 reachable if they changed IP addresses. Since only 0.1.1.22+
28362 servers can do reachability testing correctly, now we automatically
28363 make sure to test via one of these.
28364 - Fix to allow clients and mirrors to learn directory info from
28365 descriptor downloads that get cut off partway through.
28366 - Directory authorities had a bug in deciding if a newly published
28367 descriptor was novel enough to make everybody want a copy -- a few
28368 servers seem to be publishing new descriptors many times a minute.
28370 - Fix a rare bug that was causing some servers to complain about
28371 "closing wedged cpuworkers" and skip some circuit create requests.
28372 - Make the Exit flag in directory status documents actually work.
28375 Changes in version 0.1.1.21 - 2006-06-10
28376 o Crash and assert fixes from 0.1.1.20:
28377 - Fix a rare crash on Tor servers that have enabled hibernation.
28378 - Fix a seg fault on startup for Tor networks that use only one
28379 directory authority.
28380 - Fix an assert from a race condition that occurs on Tor servers
28381 while exiting, where various threads are trying to log that they're
28382 exiting, and delete the logs, at the same time.
28383 - Make our unit tests pass again on certain obscure platforms.
28386 - Add support for building SUSE RPM packages.
28387 - Speed up initial bootstrapping for clients: if we are making our
28388 first ever connection to any entry guard, then don't mark it down
28390 - When only one Tor server in the network is labelled as a guard,
28391 and we've already picked him, we would cycle endlessly picking him
28392 again, being unhappy about it, etc. Now we specifically exclude
28393 current guards when picking a new guard.
28394 - Servers send create cells more reliably after the TLS connection
28395 is established: we were sometimes forgetting to send half of them
28396 when we had more than one pending.
28397 - If we get a create cell that asks us to extend somewhere, but the
28398 Tor server there doesn't match the expected digest, we now send
28399 a destroy cell back, rather than silently doing nothing.
28400 - Make options->RedirectExit work again.
28401 - Make cookie authentication for the controller work again.
28402 - Stop being picky about unusual characters in the arguments to
28403 mapaddress. It's none of our business.
28404 - Add a new config option "TestVia" that lets you specify preferred
28405 middle hops to use for test circuits. Perhaps this will let me
28406 debug the reachability problems better.
28408 o Log / documentation fixes:
28409 - If we're a server and some peer has a broken TLS certificate, don't
28410 log about it unless ProtocolWarnings is set, i.e., we want to hear
28411 about protocol violations by others.
28412 - Fix spelling of VirtualAddrNetwork in man page.
28413 - Add a better explanation at the top of the autogenerated torrc file
28414 about what happened to our old torrc.
28417 Changes in version 0.1.1.20 - 2006-05-23
28419 - Downgrade a log severity where servers complain that they're
28421 - Avoid a compile warning on FreeBSD.
28422 - Remove string size limit on NEWDESC messages; solve bug 291.
28423 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
28424 more thoroughly when we're running on windows.
28427 Changes in version 0.1.1.19-rc - 2006-05-03
28429 - Regenerate our local descriptor if it's dirty and we try to use
28430 it locally (e.g. if it changes during reachability detection).
28431 - If we setconf our ORPort to 0, we continued to listen on the
28432 old ORPort and receive connections.
28433 - Avoid a second warning about machine/limits.h on Debian
28435 - Be willing to add our own routerinfo into the routerlist.
28436 Now authorities will include themselves in their directories
28437 and network-statuses.
28438 - Stop trying to upload rendezvous descriptors to every
28439 directory authority: only try the v1 authorities.
28440 - Servers no longer complain when they think they're not
28441 registered with the directory authorities. There were too many
28443 - Backport dist-rpm changes so rpms can be built without errors.
28446 - Implement an option, VirtualAddrMask, to set which addresses
28447 get handed out in response to mapaddress requests. This works
28448 around a bug in tsocks where 127.0.0.0/8 is never socksified.
28451 Changes in version 0.1.1.18-rc - 2006-04-10
28453 - Work harder to download live network-statuses from all the
28454 directory authorities we know about. Improve the threshold
28455 decision logic so we're more robust to edge cases.
28456 - When fetching rendezvous descriptors, we were willing to ask
28457 v2 authorities too, which would always return 404.
28460 - Stop listing down or invalid nodes in the v1 directory. This will
28461 reduce its bulk by about 1/3, and reduce load on directory
28463 - When deciding whether a router is Fast or Guard-worthy, consider
28464 his advertised BandwidthRate and not just the BandwidthCapacity.
28465 - No longer ship INSTALL and README files -- they are useless now.
28466 - Force rpmbuild to behave and honor target_cpu.
28467 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
28468 - Start to include translated versions of the tor-doc-*.html
28469 files, along with the screenshots. Still needs more work.
28470 - Start sending back 512 and 451 errors if mapaddress fails,
28471 rather than not sending anything back at all.
28472 - When we fail to bind or listen on an incoming or outgoing
28473 socket, we should close it before failing. otherwise we just
28474 leak it. (thanks to weasel for finding.)
28475 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
28476 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
28477 - Make NoPublish (even though deprecated) work again.
28478 - Fix a minor security flaw where a versioning auth dirserver
28479 could list a recommended version many times in a row to make
28480 clients more convinced that it's recommended.
28481 - Fix crash bug if there are two unregistered servers running
28482 with the same nickname, one of them is down, and you ask for
28483 them by nickname in your EntryNodes or ExitNodes. Also, try
28484 to pick the one that's running rather than an arbitrary one.
28485 - Fix an infinite loop we could hit if we go offline for too long.
28486 - Complain when we hit WSAENOBUFS on recv() or write() too.
28487 Perhaps this will help us hunt the bug.
28488 - If you're not a versioning dirserver, don't put the string
28489 "client-versions \nserver-versions \n" in your network-status.
28490 - Lower the minimum required number of file descriptors to 1000,
28491 so we can have some overhead for Valgrind on Linux, where the
28492 default ulimit -n is 1024.
28495 - Add tor.dizum.com as the fifth authoritative directory server.
28496 - Add a new config option FetchUselessDescriptors, off by default,
28497 for when you plan to run "exitlist" on your client and you want
28498 to know about even the non-running descriptors.
28501 Changes in version 0.1.1.17-rc - 2006-03-28
28503 - Clients and servers since 0.1.1.10-alpha have been expiring
28504 connections whenever they are idle for 5 minutes and they *do*
28505 have circuits on them. Oops. With this new version, clients will
28506 discard their previous entry guard choices and avoid choosing
28507 entry guards running these flawed versions.
28508 - Fix memory leak when uncompressing concatenated zlib streams. This
28509 was causing substantial leaks over time on Tor servers.
28510 - The v1 directory was including servers as much as 48 hours old,
28511 because that's how the new routerlist->routers works. Now only
28512 include them if they're 20 hours old or less.
28515 - Resume building on irix64, netbsd 2.0, etc.
28516 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
28518 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
28519 and it is confusing some users.
28520 - Mirrors stop caching the v1 directory so often.
28521 - Make the max number of old descriptors that a cache will hold
28522 rise with the number of directory authorities, so we can scale.
28523 - Change our win32 uname() hack to be more forgiving about what
28524 win32 versions it thinks it's found.
28527 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
28529 - When the controller's *setconf commands fail, collect an error
28530 message in a string and hand it back to the controller.
28531 - Make the v2 dir's "Fast" flag based on relative capacity, just
28532 like "Stable" is based on median uptime. Name everything in the
28533 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
28534 - Log server fingerprint on startup, so new server operators don't
28535 have to go hunting around their filesystem for it.
28536 - Return a robots.txt on our dirport to discourage google indexing.
28537 - Let the controller ask for GETINFO dir/status/foo so it can ask
28538 directly rather than connecting to the dir port. Only works when
28539 dirport is set for now.
28541 o New config options rather than constants in the code:
28542 - SocksTimeout: How long do we let a socks connection wait
28543 unattached before we fail it?
28544 - CircuitBuildTimeout: Cull non-open circuits that were born
28545 at least this many seconds ago.
28546 - CircuitIdleTimeout: Cull open clean circuits that were born
28547 at least this many seconds ago.
28550 Changes in version 0.1.1.16-rc - 2006-03-18
28551 o Bugfixes on 0.1.1.15-rc:
28552 - Fix assert when the controller asks to attachstream a connect-wait
28553 or resolve-wait stream.
28554 - Now do address rewriting when the controller asks us to attach
28555 to a particular circuit too. This will let Blossom specify
28556 "moria2.exit" without having to learn what moria2's IP address is.
28557 - Make the "tor --verify-config" command-line work again, so people
28558 can automatically check if their torrc will parse.
28559 - Authoritative dirservers no longer require an open connection from
28560 a server to consider him "reachable". We need this change because
28561 when we add new auth dirservers, old servers won't know not to
28563 - Let Tor build on Sun CC again.
28564 - Fix an off-by-one buffer size in dirserv.c that magically never
28565 hit our three authorities but broke sjmurdoch's own tor network.
28566 - If we as a directory mirror don't know of any v1 directory
28567 authorities, then don't try to cache any v1 directories.
28568 - Stop warning about unknown servers in our family when they are
28569 given as hex digests.
28570 - Stop complaining as quickly to the server operator that he
28571 hasn't registered his nickname/key binding.
28572 - Various cleanups so we can add new V2 Auth Dirservers.
28573 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
28574 reflect the updated flags in our v2 dir protocol.
28575 - Resume allowing non-printable characters for exit streams (both
28576 for connecting and for resolving). Now we tolerate applications
28577 that don't follow the RFCs. But continue to block malformed names
28580 o Bugfixes on 0.1.0.x:
28581 - Fix assert bug in close_logs(): when we close and delete logs,
28582 remove them all from the global "logfiles" list.
28583 - Fix minor integer overflow in calculating when we expect to use up
28584 our bandwidth allocation before hibernating.
28585 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
28586 there are multiple SSLs installed with different versions.
28587 - When we try to be a server and Address is not explicitly set and
28588 our hostname resolves to a private IP address, try to use an
28589 interface address if it has a public address. Now Windows machines
28590 that think of themselves as localhost can work by default.
28593 - Let the controller ask for GETINFO dir/server/foo so it can ask
28594 directly rather than connecting to the dir port.
28595 - Let the controller tell us about certain router descriptors
28596 that it doesn't want Tor to use in circuits. Implement
28597 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
28598 - New config option SafeSocks to reject all application connections
28599 using unsafe socks protocols. Defaults to off.
28602 Changes in version 0.1.1.15-rc - 2006-03-11
28603 o Bugfixes and cleanups:
28604 - When we're printing strings from the network, don't try to print
28605 non-printable characters. This protects us against shell escape
28606 sequence exploits, and also against attacks to fool humans into
28607 misreading their logs.
28608 - Fix a bug where Tor would fail to establish any connections if you
28609 left it off for 24 hours and then started it: we were happy with
28610 the obsolete network statuses, but they all referred to router
28611 descriptors that were too old to fetch, so we ended up with no
28612 valid router descriptors.
28613 - Fix a seg fault in the controller's "getinfo orconn-status"
28614 command while listing status on incoming handshaking connections.
28615 Introduce a status name "NEW" for these connections.
28616 - If we get a linelist or linelist_s config option from the torrc
28617 (e.g. ExitPolicy) and it has no value, warn and skip rather than
28618 silently resetting it to its default.
28619 - Don't abandon entry guards until they've been down or gone for
28621 - Cleaner and quieter log messages.
28624 - New controller signal NEWNYM that makes new application requests
28625 use clean circuits.
28626 - Add a new circuit purpose 'controller' to let the controller ask
28627 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
28628 controller command to let you specify the purpose if you're
28629 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
28630 command to let you change a circuit's purpose after it's been
28632 - Accept "private:*" in routerdesc exit policies; not generated yet
28633 because older Tors do not understand it.
28634 - Add BSD-style contributed startup script "rc.subr" from Peter
28638 Changes in version 0.1.1.14-alpha - 2006-02-20
28639 o Bugfixes on 0.1.1.x:
28640 - Don't die if we ask for a stdout or stderr log (even implicitly)
28641 and we're set to RunAsDaemon -- just warn.
28642 - We still had a few bugs in the OR connection rotation code that
28643 caused directory servers to slowly aggregate connections to other
28644 fast Tor servers. This time for sure!
28645 - Make log entries on Win32 include the name of the function again.
28646 - We were treating a pair of exit policies if they were equal even
28647 if one said accept and the other said reject -- causing us to
28648 not always publish a new descriptor since we thought nothing
28650 - Retry pending server downloads as well as pending networkstatus
28651 downloads when we unexpectedly get a socks request.
28652 - We were ignoring the IS_FAST flag in the directory status,
28653 meaning we were willing to pick trivial-bandwidth nodes for "fast"
28655 - If the controller's SAVECONF command fails (e.g. due to file
28656 permissions), let the controller know that it failed.
28659 - If we're trying to be a Tor server and running Windows 95/98/ME
28660 as a server, explain that we'll likely crash.
28661 - When we're a server, a client asks for an old-style directory,
28662 and our write bucket is empty, don't give it to him. This way
28663 small servers can continue to serve the directory *sometimes*,
28664 without getting overloaded.
28665 - Compress exit policies even more -- look for duplicate lines
28667 - Clients now honor the "guard" flag in the router status when
28668 picking entry guards, rather than looking at is_fast or is_stable.
28669 - Retain unrecognized lines in $DATADIR/state file, so that we can
28670 be forward-compatible.
28671 - Generate 18.0.0.0/8 address policy format in descs when we can;
28672 warn when the mask is not reducible to a bit-prefix.
28673 - Let the user set ControlListenAddress in the torrc. This can be
28674 dangerous, but there are some cases (like a secured LAN) where it
28676 - Split ReachableAddresses into ReachableDirAddresses and
28677 ReachableORAddresses, so we can restrict Dir conns to port 80
28678 and OR conns to port 443.
28679 - Now we can target arch and OS in rpm builds (contributed by
28680 Phobos). Also make the resulting dist-rpm filename match the
28682 - New config options to help controllers: FetchServerDescriptors
28683 and FetchHidServDescriptors for whether to fetch server
28684 info and hidserv info or let the controller do it, and
28685 PublishServerDescriptor and PublishHidServDescriptors.
28686 - Also let the controller set the __AllDirActionsPrivate config
28687 option if you want all directory fetches/publishes to happen via
28688 Tor (it assumes your controller bootstraps your circuits).
28691 Changes in version 0.1.0.17 - 2006-02-17
28692 o Crash bugfixes on 0.1.0.x:
28693 - When servers with a non-zero DirPort came out of hibernation,
28694 sometimes they would trigger an assert.
28696 o Other important bugfixes:
28697 - On platforms that don't have getrlimit (like Windows), we were
28698 artificially constraining ourselves to a max of 1024
28699 connections. Now just assume that we can handle as many as 15000
28700 connections. Hopefully this won't cause other problems.
28702 o Backported features:
28703 - When we're a server, a client asks for an old-style directory,
28704 and our write bucket is empty, don't give it to him. This way
28705 small servers can continue to serve the directory *sometimes*,
28706 without getting overloaded.
28707 - Whenever you get a 503 in response to a directory fetch, try
28708 once more. This will become important once servers start sending
28709 503's whenever they feel busy.
28710 - Fetch a new directory every 120 minutes, not every 40 minutes.
28711 Now that we have hundreds of thousands of users running the old
28712 directory algorithm, it's starting to hurt a lot.
28713 - Bump up the period for forcing a hidden service descriptor upload
28714 from 20 minutes to 1 hour.
28717 Changes in version 0.1.1.13-alpha - 2006-02-09
28718 o Crashes in 0.1.1.x:
28719 - When you tried to setconf ORPort via the controller, Tor would
28720 crash. So people using TorCP to become a server were sad.
28721 - Solve (I hope) the stack-smashing bug that we were seeing on fast
28722 servers. The problem appears to be something do with OpenSSL's
28723 random number generation, or how we call it, or something. Let me
28724 know if the crashes continue.
28725 - Turn crypto hardware acceleration off by default, until we find
28726 somebody smart who can test it for us. (It appears to produce
28727 seg faults in at least some cases.)
28728 - Fix a rare assert error when we've tried all intro points for
28729 a hidden service and we try fetching the service descriptor again:
28730 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
28733 - Fix a major load balance bug: we were round-robining in 16 KB
28734 chunks, and servers with bandwidthrate of 20 KB, while downloading
28735 a 600 KB directory, would starve their other connections. Now we
28736 try to be a bit more fair.
28737 - Dir authorities and mirrors were never expiring the newest
28738 descriptor for each server, causing memory and directory bloat.
28739 - Fix memory-bloating and connection-bloating bug on servers: We
28740 were never closing any connection that had ever had a circuit on
28741 it, because we were checking conn->n_circuits == 0, yet we had a
28742 bug that let it go negative.
28743 - Make Tor work using squid as your http proxy again -- squid
28744 returns an error if you ask for a URL that's too long, and it uses
28745 a really generic error message. Plus, many people are behind a
28746 transparent squid so they don't even realize it.
28747 - On platforms that don't have getrlimit (like Windows), we were
28748 artificially constraining ourselves to a max of 1024
28749 connections. Now just assume that we can handle as many as 15000
28750 connections. Hopefully this won't cause other problems.
28751 - Add a new config option ExitPolicyRejectPrivate which defaults to
28752 1. This means all exit policies will begin with rejecting private
28753 addresses, unless the server operator explicitly turns it off.
28756 - Clients no longer download descriptors for non-running
28758 - Before we add new directory authorities, we should make it
28759 clear that only v1 authorities should receive/publish hidden
28760 service descriptors.
28763 - As soon as we've fetched some more directory info, immediately
28764 try to download more server descriptors. This way we don't have
28765 a 10 second pause during initial bootstrapping.
28766 - Remove even more loud log messages that the server operator can't
28768 - When we're running an obsolete or un-recommended version, make
28769 the log message more clear about what the problem is and what
28770 versions *are* still recommended.
28771 - Provide a more useful warn message when our onion queue gets full:
28772 the CPU is too slow or the exit policy is too liberal.
28773 - Don't warn when we receive a 503 from a dirserver/cache -- this
28774 will pave the way for them being able to refuse if they're busy.
28775 - When we fail to bind a listener, try to provide a more useful
28776 log message: e.g., "Is Tor already running?"
28777 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
28778 Goldberg can prove things about our handshake protocol more
28780 - MaxConn has been obsolete for a while now. Document the ConnLimit
28781 config option, which is a *minimum* number of file descriptors
28782 that must be available else Tor refuses to start.
28783 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
28784 if you log to syslog and want something other than LOG_DAEMON.
28785 - Make dirservers generate a separate "guard" flag to mean,
28786 "would make a good entry guard". Make clients parse it and vote
28787 on it. Not used by clients yet.
28788 - Implement --with-libevent-dir option to ./configure. Also, improve
28789 search techniques to find libevent, and use those for openssl too.
28790 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
28791 - Only start testing reachability once we've established a
28792 circuit. This will make startup on dirservers less noisy.
28793 - Don't try to upload hidden service descriptors until we have
28794 established a circuit.
28795 - Fix the controller's "attachstream 0" command to treat conn like
28796 it just connected, doing address remapping, handling .exit and
28797 .onion idioms, and so on. Now we're more uniform in making sure
28798 that the controller hears about new and closing connections.
28801 Changes in version 0.1.1.12-alpha - 2006-01-11
28802 o Bugfixes on 0.1.1.x:
28803 - The fix to close duplicate server connections was closing all
28804 Tor client connections if they didn't establish a circuit
28805 quickly enough. Oops.
28806 - Fix minor memory issue (double-free) that happened on exit.
28808 o Bugfixes on 0.1.0.x:
28809 - Tor didn't warn when it failed to open a log file.
28812 Changes in version 0.1.1.11-alpha - 2006-01-10
28813 o Crashes in 0.1.1.x:
28814 - Include all the assert/crash fixes from 0.1.0.16.
28815 - If you start Tor and then quit very quickly, there were some
28816 races that tried to free things that weren't allocated yet.
28817 - Fix a rare memory stomp if you're running hidden services.
28818 - Fix segfault when specifying DirServer in config without nickname.
28819 - Fix a seg fault when you finish connecting to a server but at
28820 that moment you dump his server descriptor.
28821 - Extendcircuit and Attachstream controller commands would
28822 assert/crash if you don't give them enough arguments.
28823 - Fix an assert error when we're out of space in the connection_list
28824 and we try to post a hidden service descriptor (reported by weasel).
28825 - If you specify a relative torrc path and you set RunAsDaemon in
28826 your torrc, then it chdir()'s to the new directory. If you HUP,
28827 it tries to load the new torrc location, fails, and exits.
28828 The fix: no longer allow a relative path to torrc using -f.
28831 - Implement "entry guards": automatically choose a handful of entry
28832 nodes and stick with them for all circuits. Only pick new guards
28833 when the ones you have are unsuitable, and if the old guards
28834 become suitable again, switch back. This will increase security
28835 dramatically against certain end-point attacks. The EntryNodes
28836 config option now provides some hints about which entry guards you
28837 want to use most; and StrictEntryNodes means to only use those.
28838 - New directory logic: download by descriptor digest, not by
28839 fingerprint. Caches try to download all listed digests from
28840 authorities; clients try to download "best" digests from caches.
28841 This avoids partitioning and isolating attacks better.
28842 - Make the "stable" router flag in network-status be the median of
28843 the uptimes of running valid servers, and make clients pay
28844 attention to the network-status flags. Thus the cutoff adapts
28845 to the stability of the network as a whole, making IRC, IM, etc
28846 connections more reliable.
28849 - Tor servers with dynamic IP addresses were needing to wait 18
28850 hours before they could start doing reachability testing using
28851 the new IP address and ports. This is because they were using
28852 the internal descriptor to learn what to test, yet they were only
28853 rebuilding the descriptor once they decided they were reachable.
28854 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
28855 to download certain server descriptors, throw them away, and then
28856 fetch them again after 30 minutes. Now mirrors throw away these
28857 server descriptors so clients can't get them.
28858 - We were leaving duplicate connections to other ORs open for a week,
28859 rather than closing them once we detect a duplicate. This only
28860 really affected authdirservers, but it affected them a lot.
28861 - Spread the authdirservers' reachability testing over the entire
28862 testing interval, so we don't try to do 500 TLS's at once every
28866 - If the network is down, and we try to connect to a conn because
28867 we have a circuit in mind, and we timeout (30 seconds) because the
28868 network never answers, we were expiring the circuit, but we weren't
28869 obsoleting the connection or telling the entry_guards functions.
28870 - Some Tor servers process billions of cells per day. These statistics
28871 need to be uint64_t's.
28872 - Check for integer overflows in more places, when adding elements
28873 to smartlists. This could possibly prevent a buffer overflow
28874 on malicious huge inputs. I don't see any, but I haven't looked
28876 - ReachableAddresses kept growing new "reject *:*" lines on every
28878 - When you "setconf log" via the controller, it should remove all
28879 logs. We were automatically adding back in a "log notice stdout".
28880 - Newly bootstrapped Tor networks couldn't establish hidden service
28881 circuits until they had nodes with high uptime. Be more tolerant.
28882 - We were marking servers down when they could not answer every piece
28883 of the directory request we sent them. This was far too harsh.
28884 - Fix the torify (tsocks) config file to not use Tor for localhost
28886 - Directory authorities now go to the proper authority when asking for
28887 a networkstatus, even when they want a compressed one.
28888 - Fix a harmless bug that was causing Tor servers to log
28889 "Got an end because of misc error, but we're not an AP. Closing."
28890 - Authorities were treating their own descriptor changes as cosmetic,
28891 meaning the descriptor available in the network-status and the
28892 descriptor that clients downloaded were different.
28893 - The OS X installer was adding a symlink for tor_resolve but
28894 the binary was called tor-resolve (reported by Thomas Hardly).
28895 - Workaround a problem with some http proxies where they refuse GET
28896 requests that specify "Content-Length: 0" (reported by Adrian).
28897 - Fix wrong log message when you add a "HiddenServiceNodes" config
28898 line without any HiddenServiceDir line (reported by Chris Thomas).
28901 - Write the TorVersion into the state file so we have a prayer of
28902 keeping forward and backward compatibility.
28903 - Revive the FascistFirewall config option rather than eliminating it:
28904 now it's a synonym for ReachableAddresses *:80,*:443.
28905 - Clients choose directory servers from the network status lists,
28906 not from their internal list of router descriptors. Now they can
28907 go to caches directly rather than needing to go to authorities
28909 - Directory authorities ignore router descriptors that have only
28910 cosmetic differences: do this for 0.1.0.x servers now too.
28911 - Add a new flag to network-status indicating whether the server
28912 can answer v2 directory requests too.
28913 - Authdirs now stop whining so loudly about bad descriptors that
28914 they fetch from other dirservers. So when there's a log complaint,
28915 it's for sure from a freshly uploaded descriptor.
28916 - Reduce memory requirements in our structs by changing the order
28918 - There used to be two ways to specify your listening ports in a
28919 server descriptor: on the "router" line and with a separate "ports"
28920 line. Remove support for the "ports" line.
28921 - New config option "AuthDirRejectUnlisted" for auth dirservers as
28922 a panic button: if we get flooded with unusable servers we can
28923 revert to only listing servers in the approved-routers file.
28924 - Auth dir servers can now mark a fingerprint as "!reject" or
28925 "!invalid" in the approved-routers file (as its nickname), to
28926 refuse descriptors outright or include them but marked as invalid.
28927 - Servers store bandwidth history across restarts/crashes.
28928 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
28929 get a better idea of why their circuits failed. Not used yet.
28930 - Directory mirrors now cache up to 16 unrecognized network-status
28931 docs. Now we can add new authdirservers and they'll be cached too.
28932 - When picking a random directory, prefer non-authorities if any
28934 - New controller option "getinfo desc/all-recent" to fetch the
28935 latest server descriptor for every router that Tor knows about.
28938 Changes in version 0.1.0.16 - 2006-01-02
28939 o Crash bugfixes on 0.1.0.x:
28940 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
28941 corrupting the heap, losing FDs, or crashing when we need to resize
28942 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
28943 - It turns out sparc64 platforms crash on unaligned memory access
28944 too -- so detect and avoid this.
28945 - Handle truncated compressed data correctly (by detecting it and
28947 - Fix possible-but-unlikely free(NULL) in control.c.
28948 - When we were closing connections, there was a rare case that
28949 stomped on memory, triggering seg faults and asserts.
28950 - Avoid potential infinite recursion when building a descriptor. (We
28951 don't know that it ever happened, but better to fix it anyway.)
28952 - We were neglecting to unlink marked circuits from soon-to-close OR
28953 connections, which caused some rare scribbling on freed memory.
28954 - Fix a memory stomping race bug when closing the joining point of two
28955 rendezvous circuits.
28956 - Fix an assert in time parsing found by Steven Murdoch.
28958 o Other bugfixes on 0.1.0.x:
28959 - When we're doing reachability testing, provide more useful log
28960 messages so the operator knows what to expect.
28961 - Do not check whether DirPort is reachable when we are suppressing
28962 advertising it because of hibernation.
28963 - When building with -static or on Solaris, we sometimes needed -ldl.
28964 - When we're deciding whether a stream has enough circuits around
28965 that can handle it, count the freshly dirty ones and not the ones
28966 that are so dirty they won't be able to handle it.
28967 - When we're expiring old circuits, we had a logic error that caused
28968 us to close new rendezvous circuits rather than old ones.
28969 - Give a more helpful log message when you try to change ORPort via
28970 the controller: you should upgrade Tor if you want that to work.
28971 - We were failing to parse Tor versions that start with "Tor ".
28972 - Tolerate faulty streams better: when a stream fails for reason
28973 exitpolicy, stop assuming that the router is lying about his exit
28974 policy. When a stream fails for reason misc, allow it to retry just
28975 as if it was resolvefailed. When a stream has failed three times,
28976 reset its failure count so we can try again and get all three tries.
28979 Changes in version 0.1.1.10-alpha - 2005-12-11
28980 o Correctness bugfixes on 0.1.0.x:
28981 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
28982 corrupting the heap, losing FDs, or crashing when we need to resize
28983 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
28984 - Stop doing the complex voodoo overkill checking for insecure
28985 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
28986 - When we were closing connections, there was a rare case that
28987 stomped on memory, triggering seg faults and asserts.
28988 - We were neglecting to unlink marked circuits from soon-to-close OR
28989 connections, which caused some rare scribbling on freed memory.
28990 - When we're deciding whether a stream has enough circuits around
28991 that can handle it, count the freshly dirty ones and not the ones
28992 that are so dirty they won't be able to handle it.
28993 - Recover better from TCP connections to Tor servers that are
28994 broken but don't tell you (it happens!); and rotate TLS
28995 connections once a week.
28996 - When we're expiring old circuits, we had a logic error that caused
28997 us to close new rendezvous circuits rather than old ones.
28998 - Fix a scary-looking but apparently harmless bug where circuits
28999 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
29000 servers, and never switch to state CIRCUIT_STATE_OPEN.
29001 - When building with -static or on Solaris, we sometimes needed to
29003 - Give a useful message when people run Tor as the wrong user,
29004 rather than telling them to start chowning random directories.
29005 - We were failing to inform the controller about new .onion streams.
29007 o Security bugfixes on 0.1.0.x:
29008 - Refuse server descriptors if the fingerprint line doesn't match
29009 the included identity key. Tor doesn't care, but other apps (and
29010 humans) might actually be trusting the fingerprint line.
29011 - We used to kill the circuit when we receive a relay command we
29012 don't recognize. Now we just drop it.
29013 - Start obeying our firewall options more rigorously:
29014 . If we can't get to a dirserver directly, try going via Tor.
29015 . Don't ever try to connect (as a client) to a place our
29016 firewall options forbid.
29017 . If we specify a proxy and also firewall options, obey the
29018 firewall options even when we're using the proxy: some proxies
29019 can only proxy to certain destinations.
29020 - Fix a bug found by Lasse Overlier: when we were making internal
29021 circuits (intended to be cannibalized later for rendezvous and
29022 introduction circuits), we were picking them so that they had
29023 useful exit nodes. There was no need for this, and it actually
29024 aids some statistical attacks.
29025 - Start treating internal circuits and exit circuits separately.
29026 It's important to keep them separate because internal circuits
29027 have their last hops picked like middle hops, rather than like
29028 exit hops. So exiting on them will break the user's expectations.
29030 o Bugfixes on 0.1.1.x:
29031 - Take out the mis-feature where we tried to detect IP address
29032 flapping for people with DynDNS, and chose not to upload a new
29033 server descriptor sometimes.
29034 - Try to be compatible with OpenSSL 0.9.6 again.
29035 - Log fix: when the controller is logging about .onion addresses,
29036 sometimes it didn't include the ".onion" part of the address.
29037 - Don't try to modify options->DirServers internally -- if the
29038 user didn't specify any, just add the default ones directly to
29039 the trusted dirserver list. This fixes a bug where people running
29040 controllers would use SETCONF on some totally unrelated config
29041 option, and Tor would start yelling at them about changing their
29043 - Let the controller's redirectstream command specify a port, in
29044 case the controller wants to change that too.
29045 - When we requested a pile of server descriptors, we sometimes
29046 accidentally launched a duplicate request for the first one.
29047 - Bugfix for trackhostexits: write down the fingerprint of the
29048 chosen exit, not its nickname, because the chosen exit might not
29050 - When parsing foo.exit, if foo is unknown, and we are leaving
29051 circuits unattached, set the chosen_exit field and leave the
29052 address empty. This matters because controllers got confused
29054 - Directory authorities no longer try to download server
29055 descriptors that they know they will reject.
29057 o Features and updates:
29058 - Replace balanced trees with hash tables: this should make stuff
29059 significantly faster.
29060 - Resume using the AES counter-mode implementation that we ship,
29061 rather than OpenSSL's. Ours is significantly faster.
29062 - Many other CPU and memory improvements.
29063 - Add a new config option FastFirstHopPK (on by default) so clients
29064 do a trivial crypto handshake for their first hop, since TLS has
29065 already taken care of confidentiality and authentication.
29066 - Add a new config option TestSocks so people can see if their
29067 applications are using socks4, socks4a, socks5-with-ip, or
29068 socks5-with-hostname. This way they don't have to keep mucking
29069 with tcpdump and wondering if something got cached somewhere.
29070 - Warn when listening on a public address for socks. I suspect a
29071 lot of people are setting themselves up as open socks proxies,
29072 and they have no idea that jerks on the Internet are using them,
29073 since they simply proxy the traffic into the Tor network.
29074 - Add "private:*" as an alias in configuration for policies. Now
29075 you can simplify your exit policy rather than needing to list
29076 every single internal or nonroutable network space.
29077 - Add a new controller event type that allows controllers to get
29078 all server descriptors that were uploaded to a router in its role
29079 as authoritative dirserver.
29080 - Start shipping socks-extensions.txt, tor-doc-unix.html,
29081 tor-doc-server.html, and stylesheet.css in the tarball.
29082 - Stop shipping tor-doc.html in the tarball.
29085 Changes in version 0.1.1.9-alpha - 2005-11-15
29086 o Usability improvements:
29087 - Start calling it FooListenAddress rather than FooBindAddress,
29088 since few of our users know what it means to bind an address
29090 - Reduce clutter in server logs. We're going to try to make
29091 them actually usable now. New config option ProtocolWarnings that
29092 lets you hear about how _other Tors_ are breaking the protocol. Off
29094 - Divide log messages into logging domains. Once we put some sort
29095 of interface on this, it will let people looking at more verbose
29096 log levels specify the topics they want to hear more about.
29097 - Make directory servers return better http 404 error messages
29098 instead of a generic "Servers unavailable".
29099 - Check for even more Windows version flags when writing the platform
29100 string in server descriptors, and note any we don't recognize.
29101 - Clean up more of the OpenSSL memory when exiting, so we can detect
29102 memory leaks better.
29103 - Make directory authorities be non-versioning, non-naming by
29104 default. Now we can add new directory servers without requiring
29105 their operators to pay close attention.
29106 - When logging via syslog, include the pid whenever we provide
29107 a log entry. Suggested by Todd Fries.
29109 o Performance improvements:
29110 - Directory servers now silently throw away new descriptors that
29111 haven't changed much if the timestamps are similar. We do this to
29112 tolerate older Tor servers that upload a new descriptor every 15
29113 minutes. (It seemed like a good idea at the time.)
29114 - Inline bottleneck smartlist functions; use fast versions by default.
29115 - Add a "Map from digest to void*" abstraction digestmap_t so we
29116 can do less hex encoding/decoding. Use it in router_get_by_digest()
29117 to resolve a performance bottleneck.
29118 - Allow tor_gzip_uncompress to extract as much as possible from
29119 truncated compressed data. Try to extract as many
29120 descriptors as possible from truncated http responses (when
29121 DIR_PURPOSE_FETCH_ROUTERDESC).
29122 - Make circ->onionskin a pointer, not a static array. moria2 was using
29123 125000 circuit_t's after it had been up for a few weeks, which
29124 translates to 20+ megs of wasted space.
29125 - The private half of our EDH handshake keys are now chosen out
29126 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
29128 o Security improvements:
29129 - Start making directory caches retain old routerinfos, so soon
29130 clients can start asking by digest of descriptor rather than by
29131 fingerprint of server.
29132 - Add half our entropy from RAND_poll in OpenSSL. This knows how
29133 to use egd (if present), openbsd weirdness (if present), vms/os2
29134 weirdness (if we ever port there), and more in the future.
29136 o Bugfixes on 0.1.0.x:
29137 - Do round-robin writes of at most 16 kB per write. This might be
29138 more fair on loaded Tor servers, and it might resolve our Windows
29139 crash bug. It might also slow things down.
29140 - Our TLS handshakes were generating a single public/private
29141 keypair for the TLS context, rather than making a new one for
29142 each new connections. Oops. (But we were still rotating them
29143 periodically, so it's not so bad.)
29144 - When we were cannibalizing a circuit with a particular exit
29145 node in mind, we weren't checking to see if that exit node was
29146 already present earlier in the circuit. Oops.
29147 - When a Tor server's IP changes (e.g. from a dyndns address),
29148 upload a new descriptor so clients will learn too.
29149 - Really busy servers were keeping enough circuits open on stable
29150 connections that they were wrapping around the circuit_id
29151 space. (It's only two bytes.) This exposed a bug where we would
29152 feel free to reuse a circuit_id even if it still exists but has
29153 been marked for close. Try to fix this bug. Some bug remains.
29154 - If we would close a stream early (e.g. it asks for a .exit that
29155 we know would refuse it) but the LeaveStreamsUnattached config
29156 option is set by the controller, then don't close it.
29158 o Bugfixes on 0.1.1.8-alpha:
29159 - Fix a big pile of memory leaks, some of them serious.
29160 - Do not try to download a routerdesc if we would immediately reject
29162 - Resume inserting a newline between all router descriptors when
29163 generating (old style) signed directories, since our spec says
29165 - When providing content-type application/octet-stream for
29166 server descriptors using .z, we were leaving out the
29167 content-encoding header. Oops. (Everything tolerated this just
29168 fine, but that doesn't mean we need to be part of the problem.)
29169 - Fix a potential seg fault in getconf and getinfo using version 1
29170 of the controller protocol.
29171 - Avoid crash: do not check whether DirPort is reachable when we
29172 are suppressing it because of hibernation.
29173 - Make --hash-password not crash on exit.
29176 Changes in version 0.1.1.8-alpha - 2005-10-07
29177 o New features (major):
29178 - Clients don't download or use the directory anymore. Now they
29179 download and use network-statuses from the trusted dirservers,
29180 and fetch individual server descriptors as needed from mirrors.
29181 See dir-spec.txt for all the gory details.
29182 - Be more conservative about whether to advertise our DirPort.
29183 The main change is to not advertise if we're running at capacity
29184 and either a) we could hibernate or b) our capacity is low and
29185 we're using a default DirPort.
29186 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
29188 o New features (minor):
29189 - Try to be smart about when to retry network-status and
29190 server-descriptor fetches. Still needs some tuning.
29191 - Stop parsing, storing, or using running-routers output (but
29192 mirrors still cache and serve it).
29193 - Consider a threshold of versioning dirservers (dirservers who have
29194 an opinion about which Tor versions are still recommended) before
29195 deciding whether to warn the user that he's obsolete.
29196 - Dirservers can now reject/invalidate by key and IP, with the
29197 config options "AuthDirInvalid" and "AuthDirReject". This is
29198 useful since currently we automatically list servers as running
29199 and usable even if we know they're jerks.
29200 - Provide dire warnings to any users who set DirServer; move it out
29201 of torrc.sample and into torrc.complete.
29202 - Add MyFamily to torrc.sample in the server section.
29203 - Add nicknames to the DirServer line, so we can refer to them
29204 without requiring all our users to memorize their IP addresses.
29205 - When we get an EOF or a timeout on a directory connection, note
29206 how many bytes of serverdesc we are dropping. This will help
29207 us determine whether it is smart to parse incomplete serverdesc
29209 - Add a new function to "change pseudonyms" -- that is, to stop
29210 using any currently-dirty circuits for new streams, so we don't
29211 link new actions to old actions. Currently it's only called on
29212 HUP (or SIGNAL RELOAD).
29213 - On sighup, if UseHelperNodes changed to 1, use new circuits.
29214 - Start using RAND_bytes rather than RAND_pseudo_bytes from
29215 OpenSSL. Also, reseed our entropy every hour, not just at
29216 startup. And entropy in 512-bit chunks, not 160-bit chunks.
29218 o Fixes on 0.1.1.7-alpha:
29219 - Nobody ever implemented EVENT_ADDRMAP for control protocol
29220 version 0, so don't let version 0 controllers ask for it.
29221 - If you requested something with too many newlines via the
29222 v1 controller protocol, you could crash tor.
29223 - Fix a number of memory leaks, including some pretty serious ones.
29224 - Re-enable DirPort testing again, so Tor servers will be willing
29225 to advertise their DirPort if it's reachable.
29226 - On TLS handshake, only check the other router's nickname against
29227 its expected nickname if is_named is set.
29229 o Fixes forward-ported from 0.1.0.15:
29230 - Don't crash when we don't have any spare file descriptors and we
29231 try to spawn a dns or cpu worker.
29232 - Make the numbers in read-history and write-history into uint64s,
29233 so they don't overflow and publish negatives in the descriptor.
29235 o Fixes on 0.1.0.x:
29236 - For the OS X package's modified privoxy config file, comment
29237 out the "logfile" line so we don't log everything passed
29239 - We were whining about using socks4 or socks5-with-local-lookup
29240 even when it's an IP in the "virtual" range we designed exactly
29242 - We were leaking some memory every time the client changes IPs.
29243 - Never call free() on tor_malloc()d memory. This will help us
29244 use dmalloc to detect memory leaks.
29245 - Check for named servers when looking them up by nickname;
29246 warn when we'recalling a non-named server by its nickname;
29247 don't warn twice about the same name.
29248 - Try to list MyFamily elements by key, not by nickname, and warn
29249 if we've not heard of the server.
29250 - Make windows platform detection (uname equivalent) smarter.
29251 - It turns out sparc64 doesn't like unaligned access either.
29254 Changes in version 0.1.0.15 - 2005-09-23
29255 o Bugfixes on 0.1.0.x:
29256 - Reject ports 465 and 587 (spam targets) in default exit policy.
29257 - Don't crash when we don't have any spare file descriptors and we
29258 try to spawn a dns or cpu worker.
29259 - Get rid of IgnoreVersion undocumented config option, and make us
29260 only warn, never exit, when we're running an obsolete version.
29261 - Don't try to print a null string when your server finds itself to
29262 be unreachable and the Address config option is empty.
29263 - Make the numbers in read-history and write-history into uint64s,
29264 so they don't overflow and publish negatives in the descriptor.
29265 - Fix a minor memory leak in smartlist_string_remove().
29266 - We were only allowing ourselves to upload a server descriptor at
29267 most every 20 minutes, even if it changed earlier than that.
29268 - Clean up log entries that pointed to old URLs.
29271 Changes in version 0.1.1.7-alpha - 2005-09-14
29272 o Fixes on 0.1.1.6-alpha:
29273 - Exit servers were crashing when people asked them to make a
29274 connection to an address not in their exit policy.
29275 - Looking up a non-existent stream for a v1 control connection would
29277 - Fix a seg fault if we ask a dirserver for a descriptor by
29278 fingerprint but he doesn't know about him.
29279 - SETCONF was appending items to linelists, not clearing them.
29280 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
29281 out and refuse the setconf if it would fail.
29282 - Downgrade the dirserver log messages when whining about
29286 - Add Peter Palfrader's check-tor script to tor/contrib/
29287 It lets you easily check whether a given server (referenced by
29288 nickname) is reachable by you.
29289 - Numerous changes to move towards client-side v2 directories. Not
29292 o Fixes on 0.1.0.x:
29293 - If the user gave tor an odd number of command-line arguments,
29294 we were silently ignoring the last one. Now we complain and fail.
29295 [This wins the oldest-bug prize -- this bug has been present since
29296 November 2002, as released in Tor 0.0.0.]
29297 - Do not use unaligned memory access on alpha, mips, or mipsel.
29298 It *works*, but is very slow, so we treat them as if it doesn't.
29299 - Retry directory requests if we fail to get an answer we like
29300 from a given dirserver (we were retrying before, but only if
29301 we fail to connect).
29302 - When writing the RecommendedVersions line, sort them first.
29303 - When the client asked for a rendezvous port that the hidden
29304 service didn't want to provide, we were sending an IP address
29305 back along with the end cell. Fortunately, it was zero. But stop
29307 - Correct "your server is reachable" log entries to indicate that
29308 it was self-testing that told us so.
29311 Changes in version 0.1.1.6-alpha - 2005-09-09
29312 o Fixes on 0.1.1.5-alpha:
29313 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
29314 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
29315 - Fix bug with tor_memmem finding a match at the end of the string.
29316 - Make unit tests run without segfaulting.
29317 - Resolve some solaris x86 compile warnings.
29318 - Handle duplicate lines in approved-routers files without warning.
29319 - Fix bug where as soon as a server refused any requests due to his
29320 exit policy (e.g. when we ask for localhost and he tells us that's
29321 127.0.0.1 and he won't do it), we decided he wasn't obeying his
29322 exit policy using him for any exits.
29323 - Only do openssl hardware accelerator stuff if openssl version is
29326 o New controller features/fixes:
29327 - Add a "RESETCONF" command so you can set config options like
29328 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
29329 a config option in the torrc with no value, then it clears it
29330 entirely (rather than setting it to its default).
29331 - Add a "GETINFO config-file" to tell us where torrc is.
29332 - Avoid sending blank lines when GETINFO replies should be empty.
29333 - Add a QUIT command for the controller (for using it manually).
29334 - Fix a bug in SAVECONF that was adding default dirservers and
29335 other redundant entries to the torrc file.
29337 o Start on the new directory design:
29338 - Generate, publish, cache, serve new network-status format.
29339 - Publish individual descriptors (by fingerprint, by "all", and by
29341 - Publish client and server recommended versions separately.
29342 - Allow tor_gzip_uncompress() to handle multiple concatenated
29343 compressed strings. Serve compressed groups of router
29344 descriptors. The compression logic here could be more
29346 - Distinguish v1 authorities (all currently trusted directories)
29347 from v2 authorities (all trusted directories).
29348 - Change DirServers config line to note which dirs are v1 authorities.
29349 - Add configuration option "V1AuthoritativeDirectory 1" which
29350 moria1, moria2, and tor26 should set.
29351 - Remove option when getting directory cache to see whether they
29352 support running-routers; they all do now. Replace it with one
29353 to see whether caches support v2 stuff.
29356 - Dirservers now do their own external reachability testing of each
29357 Tor server, and only list them as running if they've been found to
29358 be reachable. We also send back warnings to the server's logs if
29359 it uploads a descriptor that we already believe is unreachable.
29360 - Implement exit enclaves: if we know an IP address for the
29361 destination, and there's a running Tor server at that address
29362 which allows exit to the destination, then extend the circuit to
29363 that exit first. This provides end-to-end encryption and end-to-end
29364 authentication. Also, if the user wants a .exit address or enclave,
29365 use 4 hops rather than 3, and cannibalize a general circ for it
29367 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
29368 controller. Also, rotate dns and cpu workers if the controller
29369 changes options that will affect them; and initialize the dns
29370 worker cache tree whether or not we start out as a server.
29371 - Only upload a new server descriptor when options change, 18
29372 hours have passed, uptime is reset, or bandwidth changes a lot.
29373 - Check [X-]Forwarded-For headers in HTTP requests when generating
29374 log messages. This lets people run dirservers (and caches) behind
29375 Apache but still know which IP addresses are causing warnings.
29377 o Config option changes:
29378 - Replace (Fascist)Firewall* config options with a new
29379 ReachableAddresses option that understands address policies.
29380 For example, "ReachableAddresses *:80,*:443"
29381 - Get rid of IgnoreVersion undocumented config option, and make us
29382 only warn, never exit, when we're running an obsolete version.
29383 - Make MonthlyAccountingStart config option truly obsolete now.
29385 o Fixes on 0.1.0.x:
29386 - Reject ports 465 and 587 in the default exit policy, since
29387 people have started using them for spam too.
29388 - It turns out we couldn't bootstrap a network since we added
29389 reachability detection in 0.1.0.1-rc. Good thing the Tor network
29390 has never gone down. Add an AssumeReachable config option to let
29391 servers and dirservers bootstrap. When we're trying to build a
29392 high-uptime or high-bandwidth circuit but there aren't enough
29393 suitable servers, try being less picky rather than simply failing.
29394 - Our logic to decide if the OR we connected to was the right guy
29395 was brittle and maybe open to a mitm for unverified routers.
29396 - We weren't cannibalizing circuits correctly for
29397 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
29398 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
29399 build those from scratch. This should make hidden services faster.
29400 - Predict required circuits better, with an eye toward making hidden
29401 services faster on the service end.
29402 - Retry streams if the exit node sends back a 'misc' failure. This
29403 should result in fewer random failures. Also, after failing
29404 from resolve failed or misc, reset the num failures, so we give
29405 it a fair shake next time we try.
29406 - Clean up the rendezvous warn log msgs, and downgrade some to info.
29407 - Reduce severity on logs about dns worker spawning and culling.
29408 - When we're shutting down and we do something like try to post a
29409 server descriptor or rendezvous descriptor, don't complain that
29410 we seem to be unreachable. Of course we are, we're shutting down.
29411 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
29412 We don't use them yet, but maybe one day our DNS resolver will be
29413 able to discover them.
29414 - Make ContactInfo mandatory for authoritative directory servers.
29415 - Require server descriptors to list IPv4 addresses -- hostnames
29416 are no longer allowed. This also fixes some potential security
29417 problems with people providing hostnames as their address and then
29418 preferentially resolving them to partition users.
29419 - Change log line for unreachability to explicitly suggest /etc/hosts
29420 as the culprit. Also make it clearer what IP address and ports we're
29421 testing for reachability.
29422 - Put quotes around user-supplied strings when logging so users are
29423 more likely to realize if they add bad characters (like quotes)
29425 - Let auth dir servers start without specifying an Address config
29427 - Make unit tests (and other invocations that aren't the real Tor)
29428 run without launching listeners, creating subdirectories, and so on.
29431 Changes in version 0.1.1.5-alpha - 2005-08-08
29432 o Bugfixes included in 0.1.0.14.
29434 o Bugfixes on 0.1.0.x:
29435 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
29436 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
29437 it would silently using ignore the 6668.
29440 Changes in version 0.1.0.14 - 2005-08-08
29441 o Bugfixes on 0.1.0.x:
29442 - Fix the other half of the bug with crypto handshakes
29444 - Fix an assert trigger if you send a 'signal term' via the
29445 controller when it's listening for 'event info' messages.
29448 Changes in version 0.1.1.4-alpha - 2005-08-04
29449 o Bugfixes included in 0.1.0.13.
29452 - Improve tor_gettimeofday() granularity on windows.
29453 - Make clients regenerate their keys when their IP address changes.
29454 - Implement some more GETINFO goodness: expose helper nodes, config
29455 options, getinfo keys.
29458 Changes in version 0.1.0.13 - 2005-08-04
29459 o Bugfixes on 0.1.0.x:
29460 - Fix a critical bug in the security of our crypto handshakes.
29461 - Fix a size_t underflow in smartlist_join_strings2() that made
29462 it do bad things when you hand it an empty smartlist.
29463 - Fix Windows installer to ship Tor license (thanks to Aphex for
29464 pointing out this oversight) and put a link to the doc directory
29466 - Explicitly set no-unaligned-access for sparc: it turns out the
29467 new gcc's let you compile broken code, but that doesn't make it
29471 Changes in version 0.1.1.3-alpha - 2005-07-23
29472 o Bugfixes on 0.1.1.2-alpha:
29473 - Fix a bug in handling the controller's "post descriptor"
29475 - Fix several bugs in handling the controller's "extend circuit"
29477 - Fix a bug in handling the controller's "stream status" event.
29478 - Fix an assert failure if we have a controller listening for
29479 circuit events and we go offline.
29480 - Re-allow hidden service descriptors to publish 0 intro points.
29481 - Fix a crash when generating your hidden service descriptor if
29482 you don't have enough intro points already.
29484 o New features on 0.1.1.2-alpha:
29485 - New controller function "getinfo accounting", to ask how
29486 many bytes we've used in this time period.
29487 - Experimental support for helper nodes: a lot of the risk from
29488 a small static adversary comes because users pick new random
29489 nodes every time they rebuild a circuit. Now users will try to
29490 stick to the same small set of entry nodes if they can. Not
29491 enabled by default yet.
29493 o Bugfixes on 0.1.0.12:
29494 - If you're an auth dir server, always publish your dirport,
29495 even if you haven't yet found yourself to be reachable.
29496 - Fix a size_t underflow in smartlist_join_strings2() that made
29497 it do bad things when you hand it an empty smartlist.
29500 Changes in version 0.1.0.12 - 2005-07-18
29501 o New directory servers:
29502 - tor26 has changed IP address.
29504 o Bugfixes on 0.1.0.x:
29505 - Fix a possible double-free in tor_gzip_uncompress().
29506 - When --disable-threads is set, do not search for or link against
29507 pthreads libraries.
29508 - Don't trigger an assert if an authoritative directory server
29509 claims its dirport is 0.
29510 - Fix bug with removing Tor as an NT service: some people were
29511 getting "The service did not return an error." Thanks to Matt
29515 Changes in version 0.1.1.2-alpha - 2005-07-15
29516 o New directory servers:
29517 - tor26 has changed IP address.
29519 o Bugfixes on 0.1.0.x, crashes/leaks:
29520 - Port the servers-not-obeying-their-exit-policies fix from
29522 - Fix an fd leak in start_daemon().
29523 - On Windows, you can't always reopen a port right after you've
29524 closed it. So change retry_listeners() to only close and re-open
29525 ports that have changed.
29526 - Fix a possible double-free in tor_gzip_uncompress().
29528 o Bugfixes on 0.1.0.x, usability:
29529 - When tor_socketpair() fails in Windows, give a reasonable
29530 Windows-style errno back.
29531 - Let people type "tor --install" as well as "tor -install" when
29533 want to make it an NT service.
29534 - NT service patch from Matt Edman to improve error messages.
29535 - When the controller asks for a config option with an abbreviated
29536 name, give the full name in our response.
29537 - Correct the man page entry on TrackHostExitsExpire.
29538 - Looks like we were never delivering deflated (i.e. compressed)
29539 running-routers lists, even when asked. Oops.
29540 - When --disable-threads is set, do not search for or link against
29541 pthreads libraries.
29543 o Bugfixes on 0.1.1.x:
29544 - Fix a seg fault with autodetecting which controller version is
29548 - New hidden service descriptor format: put a version in it, and
29549 let people specify introduction/rendezvous points that aren't
29550 in "the directory" (which is subjective anyway).
29551 - Allow the DEBUG controller event to work again. Mark certain log
29552 entries as "don't tell this to controllers", so we avoid cycles.
29555 Changes in version 0.1.0.11 - 2005-06-30
29556 o Bugfixes on 0.1.0.x:
29557 - Fix major security bug: servers were disregarding their
29558 exit policies if clients behaved unexpectedly.
29559 - Make OS X init script check for missing argument, so we don't
29560 confuse users who invoke it incorrectly.
29561 - Fix a seg fault in "tor --hash-password foo".
29562 - The MAPADDRESS control command was broken.
29565 Changes in version 0.1.1.1-alpha - 2005-06-29
29567 - Make OS X init script check for missing argument, so we don't
29568 confuse users who invoke it incorrectly.
29569 - Fix a seg fault in "tor --hash-password foo".
29570 - Fix a possible way to DoS dirservers.
29571 - When we complain that your exit policy implicitly allows local or
29572 private address spaces, name them explicitly so operators can
29574 - Make the log message less scary when all the dirservers are
29575 temporarily unreachable.
29576 - We were printing the number of idle dns workers incorrectly when
29580 - Revised controller protocol (version 1) that uses ascii rather
29581 than binary. Add supporting libraries in python and java so you
29582 can use the controller from your applications without caring how
29583 our protocol works.
29584 - Spiffy new support for crypto hardware accelerators. Can somebody
29588 Changes in version 0.0.9.10 - 2005-06-16
29589 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
29590 - Refuse relay cells that claim to have a length larger than the
29591 maximum allowed. This prevents a potential attack that could read
29592 arbitrary memory (e.g. keys) from an exit server's process
29596 Changes in version 0.1.0.10 - 2005-06-14
29597 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
29598 libevent before 1.1a.
29601 Changes in version 0.1.0.9-rc - 2005-06-09
29603 - Reset buf->highwater every time buf_shrink() is called, not just on
29604 a successful shrink. This was causing significant memory bloat.
29605 - Fix buffer overflow when checking hashed passwords.
29606 - Security fix: if seeding the RNG on Win32 fails, quit.
29607 - Allow seeding the RNG on Win32 even when you're not running as
29609 - Disable threading on Solaris too. Something is wonky with it,
29610 cpuworkers, and reentrant libs.
29611 - Reenable the part of the code that tries to flush as soon as an
29612 OR outbuf has a full TLS record available. Perhaps this will make
29613 OR outbufs not grow as huge except in rare cases, thus saving lots
29614 of CPU time plus memory.
29615 - Reject malformed .onion addresses rather then passing them on as
29616 normal web requests.
29617 - Adapt patch from Adam Langley: fix possible memory leak in
29618 tor_lookup_hostname().
29619 - Initialize libevent later in the startup process, so the logs are
29620 already established by the time we start logging libevent warns.
29621 - Use correct errno on win32 if libevent fails.
29622 - Check and warn about known-bad/slow libevent versions.
29623 - Pay more attention to the ClientOnly config option.
29624 - Have torctl.in/tor.sh.in check for location of su binary (needed
29626 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
29627 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
29628 HttpProxyAuthenticator
29629 - Stop warning about sigpipes in the logs. We're going to
29630 pretend that getting these occasionally is normal and fine.
29631 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
29633 installer screens; and don't put stuff into StartupItems unless
29634 the user asks you to.
29635 - Require servers that use the default dirservers to have public IP
29636 addresses. We have too many servers that are configured with private
29637 IPs and their admins never notice the log entries complaining that
29638 their descriptors are being rejected.
29639 - Add OSX uninstall instructions. An actual uninstall script will
29643 Changes in version 0.1.0.8-rc - 2005-05-23
29645 - It turns out that kqueue on OS X 10.3.9 was causing kernel
29646 panics. Disable kqueue on all OS X Tors.
29647 - Fix RPM: remove duplicate line accidentally added to the rpm
29649 - Disable threads on openbsd too, since its gethostaddr is not
29651 - Tolerate libevent 0.8 since it still works, even though it's
29653 - Enable building on Red Hat 9.0 again.
29654 - Allow the middle hop of the testing circuit to be running any
29655 version, now that most of them have the bugfix to let them connect
29656 to unknown servers. This will allow reachability testing to work
29657 even when 0.0.9.7-0.0.9.9 become obsolete.
29658 - Handle relay cells with rh.length too large. This prevents
29659 a potential attack that could read arbitrary memory (maybe even
29660 keys) from the exit server's process.
29661 - We screwed up the dirport reachability testing when we don't yet
29662 have a cached version of the directory. Hopefully now fixed.
29663 - Clean up router_load_single_router() (used by the controller),
29664 so it doesn't seg fault on error.
29665 - Fix a minor memory leak when somebody establishes an introduction
29666 point at your Tor server.
29667 - If a socks connection ends because read fails, don't warn that
29668 you're not sending a socks reply back.
29671 - Add HttpProxyAuthenticator config option too, that works like
29672 the HttpsProxyAuthenticator config option.
29673 - Encode hashed controller passwords in hex instead of base64,
29674 to make it easier to write controllers.
29677 Changes in version 0.1.0.7-rc - 2005-05-17
29679 - Fix a bug in the OS X package installer that prevented it from
29680 installing on Tiger.
29681 - Fix a script bug in the OS X package installer that made it
29682 complain during installation.
29683 - Find libevent even if it's hiding in /usr/local/ and your
29684 CFLAGS and LDFLAGS don't tell you to look there.
29685 - Be able to link with libevent as a shared library (the default
29686 after 1.0d), even if it's hiding in /usr/local/lib and even
29687 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
29688 assuming you're running gcc. Otherwise fail and give a useful
29690 - Fix a bug in the RPM packager: set home directory for _tor to
29691 something more reasonable when first installing.
29692 - Free a minor amount of memory that is still reachable on exit.
29695 Changes in version 0.1.0.6-rc - 2005-05-14
29697 - Implement --disable-threads configure option. Disable threads on
29698 netbsd by default, because it appears to have no reentrant resolver
29700 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
29701 release (1.1) detects and disables kqueue if it's broken.
29702 - Append default exit policy before checking for implicit internal
29703 addresses. Now we don't log a bunch of complaints on startup
29704 when using the default exit policy.
29705 - Some people were putting "Address " in their torrc, and they had
29706 a buggy resolver that resolved " " to 0.0.0.0. Oops.
29707 - If DataDir is ~/.tor, and that expands to /.tor, then default to
29708 LOCALSTATEDIR/tor instead.
29709 - Fix fragmented-message bug in TorControl.py.
29710 - Resolve a minor bug which would prevent unreachable dirports
29711 from getting suppressed in the published descriptor.
29712 - When the controller gave us a new descriptor, we weren't resolving
29713 it immediately, so Tor would think its address was 0.0.0.0 until
29714 we fetched a new directory.
29715 - Fix an uppercase/lowercase case error in suppressing a bogus
29716 libevent warning on some Linuxes.
29719 - Begin scrubbing sensitive strings from logs by default. Turn off
29720 the config option SafeLogging if you need to do debugging.
29721 - Switch to a new buffer management algorithm, which tries to avoid
29722 reallocing and copying quite as much. In first tests it looks like
29723 it uses *more* memory on average, but less cpu.
29724 - First cut at support for "create-fast" cells. Clients can use
29725 these when extending to their first hop, since the TLS already
29726 provides forward secrecy and authentication. Not enabled on
29728 - When dirservers refuse a router descriptor, we now log its
29729 contactinfo, platform, and the poster's IP address.
29730 - Call tor_free_all instead of connections_free_all after forking, to
29731 save memory on systems that need to fork.
29732 - Whine at you if you're a server and you don't set your contactinfo.
29733 - Implement --verify-config command-line option to check if your torrc
29734 is valid without actually launching Tor.
29735 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
29736 rather than just rejecting it.
29739 Changes in version 0.1.0.5-rc - 2005-04-27
29741 - Stop trying to print a null pointer if an OR conn fails because
29742 we didn't like its cert.
29744 - Switch our internal buffers implementation to use a ring buffer,
29745 to hopefully improve performance for fast servers a lot.
29746 - Add HttpsProxyAuthenticator support (basic auth only), based
29747 on patch from Adam Langley.
29748 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
29749 the fast servers that have been joining lately.
29750 - Give hidden service accesses extra time on the first attempt,
29751 since 60 seconds is often only barely enough. This might improve
29753 - Improve performance for dirservers: stop re-parsing the whole
29754 directory every time you regenerate it.
29755 - Add more debugging info to help us find the weird dns freebsd
29756 pthreads bug; cleaner debug messages to help track future issues.
29759 Changes in version 0.0.9.9 - 2005-04-23
29760 o Bugfixes on 0.0.9.x:
29761 - If unofficial Tor clients connect and send weird TLS certs, our
29762 Tor server triggers an assert. This release contains a minimal
29763 backport from the broader fix that we put into 0.1.0.4-rc.
29766 Changes in version 0.1.0.4-rc - 2005-04-23
29768 - If unofficial Tor clients connect and send weird TLS certs, our
29769 Tor server triggers an assert. Stop asserting, and start handling
29770 TLS errors better in other situations too.
29771 - When the controller asks us to tell it about all the debug-level
29772 logs, it turns out we were generating debug-level logs while
29773 telling it about them, which turns into a bad loop. Now keep
29774 track of whether you're sending a debug log to the controller,
29775 and don't log when you are.
29776 - Fix the "postdescriptor" feature of the controller interface: on
29777 non-complete success, only say "done" once.
29779 - Clients are now willing to load balance over up to 2mB, not 1mB,
29780 of advertised bandwidth capacity.
29781 - Add a NoPublish config option, so you can be a server (e.g. for
29782 testing running Tor servers in other Tor networks) without
29783 publishing your descriptor to the primary dirservers.
29786 Changes in version 0.1.0.3-rc - 2005-04-08
29787 o Improvements on 0.1.0.2-rc:
29788 - Client now retries when streams end early for 'hibernating' or
29789 'resource limit' reasons, rather than failing them.
29790 - More automated handling for dirserver operators:
29791 - Automatically approve nodes running 0.1.0.2-rc or later,
29792 now that the the reachability detection stuff is working.
29793 - Now we allow two unverified servers with the same nickname
29794 but different keys. But if a nickname is verified, only that
29795 nickname+key are allowed.
29796 - If you're an authdirserver connecting to an address:port,
29797 and it's not the OR you were expecting, forget about that
29798 descriptor. If he *was* the one you were expecting, then forget
29799 about all other descriptors for that address:port.
29800 - Allow servers to publish descriptors from 12 hours in the future.
29801 Corollary: only whine about clock skew from the dirserver if
29802 he's a trusted dirserver (since now even verified servers could
29803 have quite wrong clocks).
29804 - Adjust maximum skew and age for rendezvous descriptors: let skew
29805 be 48 hours rather than 90 minutes.
29806 - Efficiency improvements:
29807 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
29808 it much faster to look up a circuit for each relay cell.
29809 - Remove most calls to assert_all_pending_dns_resolves_ok(),
29810 since they're eating our cpu on exit nodes.
29811 - Stop wasting time doing a case insensitive comparison for every
29812 dns name every time we do any lookup. Canonicalize the names to
29813 lowercase and be done with it.
29814 - Start sending 'truncated' cells back rather than destroy cells,
29815 if the circuit closes in front of you. This means we won't have
29816 to abandon partially built circuits.
29817 - Only warn once per nickname from add_nickname_list_to_smartlist
29818 per failure, so an entrynode or exitnode choice that's down won't
29820 - Put a note in the torrc about abuse potential with the default
29822 - Revise control spec and implementation to allow all log messages to
29823 be sent to controller with their severities intact (suggested by
29824 Matt Edman). Update TorControl to handle new log event types.
29825 - Provide better explanation messages when controller's POSTDESCRIPTOR
29827 - Stop putting nodename in the Platform string in server descriptors.
29828 It doesn't actually help, and it is confusing/upsetting some people.
29830 o Bugfixes on 0.1.0.2-rc:
29831 - We were printing the host mask wrong in exit policies in server
29832 descriptors. This isn't a critical bug though, since we were still
29833 obeying the exit policy internally.
29834 - Fix Tor when compiled with libevent but without pthreads: move
29835 connection_unregister() from _connection_free() to
29837 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
29838 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
29839 when we look through the connection array, we'll find any of the
29840 cpu/dnsworkers. This is no good.
29842 o Bugfixes on 0.0.9.8:
29843 - Fix possible bug on threading platforms (e.g. win32) which was
29844 leaking a file descriptor whenever a cpuworker or dnsworker died.
29845 - When using preferred entry or exit nodes, ignore whether the
29846 circuit wants uptime or capacity. They asked for the nodes, they
29848 - chdir() to your datadirectory at the *end* of the daemonize process,
29849 not the beginning. This was a problem because the first time you
29850 run tor, if your datadir isn't there, and you have runasdaemon set
29851 to 1, it will try to chdir to it before it tries to create it. Oops.
29852 - Handle changed router status correctly when dirserver reloads
29853 fingerprint file. We used to be dropping all unverified descriptors
29854 right then. The bug was hidden because we would immediately
29855 fetch a directory from another dirserver, which would include the
29856 descriptors we just dropped.
29857 - When we're connecting to an OR and he's got a different nickname/key
29858 than we were expecting, only complain loudly if we're an OP or a
29859 dirserver. Complaining loudly to the OR admins just confuses them.
29860 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
29861 artificially capped at 500kB.
29864 Changes in version 0.0.9.8 - 2005-04-07
29865 o Bugfixes on 0.0.9.x:
29866 - We have a bug that I haven't found yet. Sometimes, very rarely,
29867 cpuworkers get stuck in the 'busy' state, even though the cpuworker
29868 thinks of itself as idle. This meant that no new circuits ever got
29869 established. Here's a workaround to kill any cpuworker that's been
29870 busy for more than 100 seconds.
29873 Changes in version 0.1.0.2-rc - 2005-04-01
29874 o Bugfixes on 0.1.0.1-rc:
29875 - Fixes on reachability detection:
29876 - Don't check for reachability while hibernating.
29877 - If ORPort is reachable but DirPort isn't, still publish the
29878 descriptor, but zero out DirPort until it's found reachable.
29879 - When building testing circs for ORPort testing, use only
29880 high-bandwidth nodes, so fewer circuits fail.
29881 - Complain about unreachable ORPort separately from unreachable
29882 DirPort, so the user knows what's going on.
29883 - Make sure we only conclude ORPort reachability if we didn't
29884 initiate the conn. Otherwise we could falsely conclude that
29885 we're reachable just because we connected to the guy earlier
29886 and he used that same pipe to extend to us.
29887 - Authdirservers shouldn't do ORPort reachability detection,
29888 since they're in clique mode, so it will be rare to find a
29889 server not already connected to them.
29890 - When building testing circuits, always pick middle hops running
29891 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
29892 bug. (This is a kludge; it will go away when 0.0.9.x becomes
29894 - When we decide we're reachable, actually publish our descriptor
29896 - Fix bug in redirectstream in the controller.
29897 - Fix the state descriptor strings so logs don't claim edge streams
29898 are in a different state than they actually are.
29899 - Use recent libevent features when possible (this only really affects
29900 win32 and osx right now, because the new libevent with these
29901 features hasn't been released yet). Add code to suppress spurious
29903 - Prevent possible segfault in connection_close_unattached_ap().
29904 - Fix newlines on torrc in win32.
29905 - Improve error msgs when tor-resolve fails.
29907 o Improvements on 0.0.9.x:
29908 - New experimental script tor/contrib/ExerciseServer.py (needs more
29909 work) that uses the controller interface to build circuits and
29910 fetch pages over them. This will help us bootstrap servers that
29911 have lots of capacity but haven't noticed it yet.
29912 - New experimental script tor/contrib/PathDemo.py (needs more work)
29913 that uses the controller interface to let you choose whole paths
29915 "<hostname>.<path,separated by dots>.<length of path>.path"
29916 - When we've connected to an OR and handshaked but didn't like
29917 the result, we were closing the conn without sending destroy
29918 cells back for pending circuits. Now send those destroys.
29921 Changes in version 0.0.9.7 - 2005-04-01
29922 o Bugfixes on 0.0.9.x:
29923 - Fix another race crash bug (thanks to Glenn Fink for reporting).
29924 - Compare identity to identity, not to nickname, when extending to
29925 a router not already in the directory. This was preventing us from
29926 extending to unknown routers. Oops.
29927 - Make sure to create OS X Tor user in <500 range, so we aren't
29928 creating actual system users.
29929 - Note where connection-that-hasn't-sent-end was marked, and fix
29930 a few really loud instances of this harmless bug (it's fixed more
29934 Changes in version 0.1.0.1-rc - 2005-03-28
29936 - Add reachability testing. Your Tor server will automatically try
29937 to see if its ORPort and DirPort are reachable from the outside,
29938 and it won't upload its descriptor until it decides they are.
29939 - Handle unavailable hidden services better. Handle slow or busy
29940 hidden services better.
29941 - Add support for CONNECTing through https proxies, with "HttpsProxy"
29943 - New exit policy: accept most low-numbered ports, rather than
29944 rejecting most low-numbered ports.
29945 - More Tor controller support (still experimental). See
29946 http://tor.eff.org/doc/control-spec.txt for all the new features,
29947 including signals to emulate unix signals from any platform;
29948 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
29949 closestream; closecircuit; etc.
29950 - Make nt services work and start on startup on win32 (based on
29951 patch by Matt Edman).
29952 - Add a new AddressMap config directive to rewrite incoming socks
29953 addresses. This lets you, for example, declare an implicit
29954 required exit node for certain sites.
29955 - Add a new TrackHostExits config directive to trigger addressmaps
29956 for certain incoming socks addresses -- for sites that break when
29957 your exit keeps changing (based on patch by Mike Perry).
29958 - Redo the client-side dns cache so it's just an addressmap too.
29959 - Notice when our IP changes, and reset stats/uptime/reachability.
29960 - When an application is using socks5, give him the whole variety of
29961 potential socks5 responses (connect refused, host unreachable, etc),
29962 rather than just "success" or "failure".
29963 - A more sane version numbering system. See
29964 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
29965 - New contributed script "exitlist": a simple python script to
29966 parse directories and find Tor nodes that exit to listed
29968 - New contributed script "privoxy-tor-toggle" to toggle whether
29969 Privoxy uses Tor. Seems to be configured for Debian by default.
29970 - Report HTTP reasons to client when getting a response from directory
29971 servers -- so you can actually know what went wrong.
29972 - New config option MaxAdvertisedBandwidth which lets you advertise
29973 a low bandwidthrate (to not attract as many circuits) while still
29974 allowing a higher bandwidthrate in reality.
29976 o Robustness/stability fixes:
29977 - Make Tor use Niels Provos's libevent instead of its current
29978 poll-but-sometimes-select mess. This will let us use faster async
29979 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
29981 - pthread support now too. This was forced because when we forked,
29982 we ended up wasting a lot of duplicate ram over time. Also switch
29983 to foo_r versions of some library calls to allow reentry and
29985 - Better handling for heterogeneous / unreliable nodes:
29986 - Annotate circuits w/ whether they aim to contain high uptime nodes
29987 and/or high capacity nodes. When building circuits, choose
29989 - This means that every single node in an intro rend circuit,
29990 not just the last one, will have a minimum uptime.
29991 - New config option LongLivedPorts to indicate application streams
29992 that will want high uptime circuits.
29993 - Servers reset uptime when a dir fetch entirely fails. This
29994 hopefully reflects stability of the server's network connectivity.
29995 - If somebody starts his tor server in Jan 2004 and then fixes his
29996 clock, don't make his published uptime be a year.
29997 - Reset published uptime when you wake up from hibernation.
29998 - Introduce a notion of 'internal' circs, which are chosen without
29999 regard to the exit policy of the last hop. Intro and rendezvous
30000 circs must be internal circs, to avoid leaking information. Resolve
30001 and connect streams can use internal circs if they want.
30002 - New circuit pooling algorithm: make sure to have enough circs around
30003 to satisfy any predicted ports, and also make sure to have 2 internal
30004 circs around if we've required internal circs lately (and with high
30005 uptime if we've seen that lately too).
30006 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
30007 which describes how often we retry making new circuits if current
30008 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
30009 how long we're willing to make use of an already-dirty circuit.
30010 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
30011 circ as necessary, if there are any completed ones lying around
30012 when we try to launch one.
30013 - Make hidden services try to establish a rendezvous for 30 seconds,
30014 rather than for n (where n=3) attempts to build a circuit.
30015 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
30016 "ShutdownWaitLength".
30017 - Try to be more zealous about calling connection_edge_end when
30018 things go bad with edge conns in connection.c.
30019 - Revise tor-spec to add more/better stream end reasons.
30020 - Revise all calls to connection_edge_end to avoid sending "misc",
30021 and to take errno into account where possible.
30024 - Fix a race condition that can trigger an assert, when we have a
30025 pending create cell and an OR connection fails right then.
30026 - Fix several double-mark-for-close bugs, e.g. where we were finding
30027 a conn for a cell even if that conn is already marked for close.
30028 - Make sequence of log messages when starting on win32 with no config
30029 file more reasonable.
30030 - When choosing an exit node for a new non-internal circ, don't take
30031 into account whether it'll be useful for any pending x.onion
30032 addresses -- it won't.
30033 - Turn addr_policy_compare from a tristate to a quadstate; this should
30034 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
30035 for google.com" problem.
30036 - Make "platform" string in descriptor more accurate for Win32 servers,
30037 so it's not just "unknown platform".
30038 - Fix an edge case in parsing config options (thanks weasel).
30039 If they say "--" on the commandline, it's not an option.
30040 - Reject odd-looking addresses at the client (e.g. addresses that
30041 contain a colon), rather than having the server drop them because
30043 - tor-resolve requests were ignoring .exit if there was a working circuit
30044 they could use instead.
30045 - REUSEADDR on normal platforms means you can rebind to the port
30046 right after somebody else has let it go. But REUSEADDR on win32
30047 means to let you bind to the port _even when somebody else
30048 already has it bound_! So, don't do that on Win32.
30049 - Change version parsing logic: a version is "obsolete" if it is not
30050 recommended and (1) there is a newer recommended version in the
30051 same series, or (2) there are no recommended versions in the same
30052 series, but there are some recommended versions in a newer series.
30053 A version is "new" if it is newer than any recommended version in
30055 - Stop most cases of hanging up on a socks connection without sending
30059 - Require BandwidthRate to be at least 20kB/s for servers.
30060 - When a dirserver causes you to give a warn, mention which dirserver
30062 - New config option DirAllowPrivateAddresses for authdirservers.
30063 Now by default they refuse router descriptors that have non-IP or
30064 private-IP addresses.
30065 - Stop publishing socksport in the directory, since it's not
30066 actually meant to be public. For compatibility, publish a 0 there
30068 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
30069 smart" value, that is low for servers and high for clients.
30070 - If our clock jumps forward by 100 seconds or more, assume something
30071 has gone wrong with our network and abandon all not-yet-used circs.
30072 - Warn when exit policy implicitly allows local addresses.
30073 - If we get an incredibly skewed timestamp from a dirserver mirror
30074 that isn't a verified OR, don't warn -- it's probably him that's
30076 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
30077 cookies to disk and doesn't log each web request to disk. (Thanks
30078 to Brett Carrington for pointing this out.)
30079 - When a client asks us for a dir mirror and we don't have one,
30080 launch an attempt to get a fresh one.
30081 - If we're hibernating and we get a SIGINT, exit immediately.
30082 - Add --with-dmalloc ./configure option, to track memory leaks.
30083 - And try to free all memory on closing, so we can detect what
30085 - Cache local dns resolves correctly even when they're .exit
30087 - Give a better warning when some other server advertises an
30088 ORPort that is actually an apache running ssl.
30089 - Add "opt hibernating 1" to server descriptor to make it clearer
30090 whether the server is hibernating.
30093 Changes in version 0.0.9.6 - 2005-03-24
30094 o Bugfixes on 0.0.9.x (crashes and asserts):
30095 - Add new end stream reasons to maintenance branch. Fix bug where
30096 reason (8) could trigger an assert. Prevent bug from recurring.
30097 - Apparently win32 stat wants paths to not end with a slash.
30098 - Fix assert triggers in assert_cpath_layer_ok(), where we were
30099 blowing away the circuit that conn->cpath_layer points to, then
30100 checking to see if the circ is well-formed. Backport check to make
30101 sure we dont use the cpath on a closed connection.
30102 - Prevent circuit_resume_edge_reading_helper() from trying to package
30103 inbufs for marked-for-close streams.
30104 - Don't crash on hup if your options->address has become unresolvable.
30105 - Some systems (like OS X) sometimes accept() a connection and tell
30106 you the remote host is 0.0.0.0:0. If this happens, due to some
30107 other mis-features, we get confused; so refuse the conn for now.
30109 o Bugfixes on 0.0.9.x (other):
30110 - Fix harmless but scary "Unrecognized content encoding" warn message.
30111 - Add new stream error reason: TORPROTOCOL reason means "you are not
30112 speaking a version of Tor I understand; say bye-bye to your stream."
30113 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
30114 into the future, now that we are more tolerant of skew. This
30115 resolves a bug where a Tor server would refuse to cache a directory
30116 because all the directories it gets are too far in the future;
30117 yet the Tor server never logs any complaints about clock skew.
30118 - Mac packaging magic: make man pages useable, and do not overwrite
30119 existing torrc files.
30120 - Make OS X log happily to /var/log/tor/tor.log
30123 Changes in version 0.0.9.5 - 2005-02-22
30124 o Bugfixes on 0.0.9.x:
30125 - Fix an assert race at exit nodes when resolve requests fail.
30126 - Stop picking unverified dir mirrors--it only leads to misery.
30127 - Patch from Matt Edman to make NT services work better. Service
30128 support is still not compiled into the executable by default.
30129 - Patch from Dmitri Bely so the Tor service runs better under
30130 the win32 SYSTEM account.
30131 - Make tor-resolve actually work (?) on Win32.
30132 - Fix a sign bug when getrlimit claims to have 4+ billion
30133 file descriptors available.
30134 - Stop refusing to start when bandwidthburst == bandwidthrate.
30135 - When create cells have been on the onion queue more than five
30136 seconds, just send back a destroy and take them off the list.
30139 Changes in version 0.0.9.4 - 2005-02-03
30140 o Bugfixes on 0.0.9:
30141 - Fix an assert bug that took down most of our servers: when
30142 a server claims to have 1 GB of bandwidthburst, don't
30144 - Don't crash as badly if we have spawned the max allowed number
30145 of dnsworkers, or we're out of file descriptors.
30146 - Block more file-sharing ports in the default exit policy.
30147 - MaxConn is now automatically set to the hard limit of max
30148 file descriptors we're allowed (ulimit -n), minus a few for
30150 - Give a clearer message when servers need to raise their
30151 ulimit -n when they start running out of file descriptors.
30152 - SGI Compatibility patches from Jan Schaumann.
30153 - Tolerate a corrupt cached directory better.
30154 - When a dirserver hasn't approved your server, list which one.
30155 - Go into soft hibernation after 95% of the bandwidth is used,
30156 not 99%. This is especially important for daily hibernators who
30157 have a small accounting max. Hopefully it will result in fewer
30158 cut connections when the hard hibernation starts.
30159 - Load-balance better when using servers that claim more than
30160 800kB/s of capacity.
30161 - Make NT services work (experimental, only used if compiled in).
30164 Changes in version 0.0.9.3 - 2005-01-21
30165 o Bugfixes on 0.0.9:
30166 - Backport the cpu use fixes from main branch, so busy servers won't
30167 need as much processor time.
30168 - Work better when we go offline and then come back, or when we
30169 run Tor at boot before the network is up. We do this by
30170 optimistically trying to fetch a new directory whenever an
30171 application request comes in and we think we're offline -- the
30172 human is hopefully a good measure of when the network is back.
30173 - Backport some minimal hidserv bugfixes: keep rend circuits open as
30174 long as you keep using them; actually publish hidserv descriptors
30175 shortly after they change, rather than waiting 20-40 minutes.
30176 - Enable Mac startup script by default.
30177 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
30178 - When you update AllowUnverifiedNodes or FirewallPorts via the
30179 controller's setconf feature, we were always appending, never
30181 - When you update HiddenServiceDir via setconf, it was screwing up
30182 the order of reading the lines, making it fail.
30183 - Do not rewrite a cached directory back to the cache; otherwise we
30184 will think it is recent and not fetch a newer one on startup.
30185 - Workaround for webservers that lie about Content-Encoding: Tor
30186 now tries to autodetect compressed directories and compression
30187 itself. This lets us Proxypass dir fetches through apache.
30190 Changes in version 0.0.9.2 - 2005-01-04
30191 o Bugfixes on 0.0.9 (crashes and asserts):
30192 - Fix an assert on startup when the disk is full and you're logging
30194 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
30195 style address, then we'd crash.
30196 - Fix an assert trigger when the running-routers string we get from
30197 a dirserver is broken.
30198 - Make worker threads start and run on win32. Now win32 servers
30200 - Bandaid (not actually fix, but now it doesn't crash) an assert
30201 where the dns worker dies mysteriously and the main Tor process
30202 doesn't remember anything about the address it was resolving.
30204 o Bugfixes on 0.0.9 (Win32):
30205 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
30206 name out of the warning/assert messages.
30207 - Fix a superficial "unhandled error on read" bug on win32.
30208 - The win32 installer no longer requires a click-through for our
30209 license, since our Free Software license grants rights but does not
30211 - Win32: When connecting to a dirserver fails, try another one
30212 immediately. (This was already working for non-win32 Tors.)
30213 - Stop trying to parse $HOME on win32 when hunting for default
30215 - Make tor-resolve.c work on win32 by calling network_init().
30217 o Bugfixes on 0.0.9 (other):
30218 - Make 0.0.9.x build on Solaris again.
30219 - Due to a fencepost error, we were blowing away the \n when reporting
30220 confvalue items in the controller. So asking for multiple config
30221 values at once couldn't work.
30222 - When listing circuits that are pending on an opening OR connection,
30223 if we're an OR we were listing circuits that *end* at us as
30224 being pending on every listener, dns/cpu worker, etc. Stop that.
30225 - Dirservers were failing to create 'running-routers' or 'directory'
30226 strings if we had more than some threshold of routers. Fix them so
30227 they can handle any number of routers.
30228 - Fix a superficial "Duplicate mark for close" bug.
30229 - Stop checking for clock skew for OR connections, even for servers.
30230 - Fix a fencepost error that was chopping off the last letter of any
30231 nickname that is the maximum allowed nickname length.
30232 - Update URLs in log messages so they point to the new website.
30233 - Fix a potential problem in mangling server private keys while
30234 writing to disk (not triggered yet, as far as we know).
30235 - Include the licenses for other free software we include in Tor,
30236 now that we're shipping binary distributions more regularly.
30239 Changes in version 0.0.9.1 - 2004-12-15
30240 o Bugfixes on 0.0.9:
30241 - Make hibernation actually work.
30242 - Make HashedControlPassword config option work.
30243 - When we're reporting event circuit status to a controller,
30244 don't use the stream status code.
30247 Changes in version 0.0.9 - 2004-12-12
30249 - Clean up manpage and torrc.sample file.
30250 - Clean up severities and text of log warnings.
30252 - Make servers trigger an assert when they enter hibernation.
30255 Changes in version 0.0.9rc7 - 2004-12-08
30256 o Bugfixes on 0.0.9rc:
30257 - Fix a stack-trashing crash when an exit node begins hibernating.
30258 - Avoid looking at unallocated memory while considering which
30259 ports we need to build circuits to cover.
30260 - Stop a sigpipe: when an 'end' cell races with eof from the app,
30261 we shouldn't hold-open-until-flush if the eof arrived first.
30262 - Fix a bug with init_cookie_authentication() in the controller.
30263 - When recommending new-format log lines, if the upper bound is
30264 LOG_ERR, leave it implicit.
30266 o Bugfixes on 0.0.8.1:
30267 - Fix a whole slew of memory leaks.
30268 - Fix isspace() and friends so they still make Solaris happy
30269 but also so they don't trigger asserts on win32.
30270 - Fix parse_iso_time on platforms without strptime (eg win32).
30271 - win32: tolerate extra "readable" events better.
30272 - win32: when being multithreaded, leave parent fdarray open.
30273 - Make unit tests work on win32.
30276 Changes in version 0.0.9rc6 - 2004-12-06
30277 o Bugfixes on 0.0.9pre:
30278 - Clean up some more integer underflow opportunities (not exploitable
30280 - While hibernating, hup should not regrow our listeners.
30281 - Send an end to the streams we close when we hibernate, rather
30282 than just chopping them off.
30283 - React to eof immediately on non-open edge connections.
30285 o Bugfixes on 0.0.8.1:
30286 - Calculate timeout for waiting for a connected cell from the time
30287 we sent the begin cell, not from the time the stream started. If
30288 it took a long time to establish the circuit, we would time out
30289 right after sending the begin cell.
30290 - Fix router_compare_addr_to_addr_policy: it was not treating a port
30291 of * as always matching, so we were picking reject *:* nodes as
30292 exit nodes too. Oops.
30295 - New circuit building strategy: keep a list of ports that we've
30296 used in the past 6 hours, and always try to have 2 circuits open
30297 or on the way that will handle each such port. Seed us with port
30298 80 so web users won't complain that Tor is "slow to start up".
30299 - Make kill -USR1 dump more useful stats about circuits.
30300 - When warning about retrying or giving up, print the address, so
30301 the user knows which one it's talking about.
30302 - If you haven't used a clean circuit in an hour, throw it away,
30303 just to be on the safe side. (This means after 6 hours a totally
30304 unused Tor client will have no circuits open.)
30307 Changes in version 0.0.9rc5 - 2004-12-01
30308 o Bugfixes on 0.0.8.1:
30309 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
30310 - Let resolve conns retry/expire also, rather than sticking around
30312 - If we are using select, make sure we stay within FD_SETSIZE.
30314 o Bugfixes on 0.0.9pre:
30315 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
30316 but doesn't seem to be currently; thanks to Ilja van Sprundel for
30318 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
30319 instead. Impose minima and maxima for all *Period options; impose
30320 even tighter maxima for fetching if we are a caching dirserver.
30321 Clip rather than rejecting.
30322 - Fetch cached running-routers from servers that serve it (that is,
30323 authdirservers and servers running 0.0.9rc5-cvs or later.)
30326 - Accept *:706 (silc) in default exit policy.
30327 - Implement new versioning format for post 0.1.
30328 - Support "foo.nickname.exit" addresses, to let Alice request the
30329 address "foo" as viewed by exit node "nickname". Based on a patch
30331 - Make tor --version --version dump the cvs Id of every file.
30334 Changes in version 0.0.9rc4 - 2004-11-28
30335 o Bugfixes on 0.0.8.1:
30336 - Make windows sockets actually non-blocking (oops), and handle
30337 win32 socket errors better.
30339 o Bugfixes on 0.0.9rc1:
30340 - Actually catch the -USR2 signal.
30343 Changes in version 0.0.9rc3 - 2004-11-25
30344 o Bugfixes on 0.0.8.1:
30345 - Flush the log file descriptor after we print "Tor opening log file",
30346 so we don't see those messages days later.
30348 o Bugfixes on 0.0.9rc1:
30349 - Make tor-resolve work again.
30350 - Avoid infinite loop in tor-resolve if tor hangs up on it.
30351 - Fix an assert trigger for clients/servers handling resolves.
30354 Changes in version 0.0.9rc2 - 2004-11-24
30355 o Bugfixes on 0.0.9rc1:
30356 - I broke socks5 support while fixing the eof bug.
30357 - Allow unitless bandwidths and intervals; they default to bytes
30359 - New servers don't start out hibernating; they are active until
30360 they run out of bytes, so they have a better estimate of how
30361 long it takes, and so their operators can know they're working.
30364 Changes in version 0.0.9rc1 - 2004-11-23
30365 o Bugfixes on 0.0.8.1:
30366 - Finally fix a bug that's been plaguing us for a year:
30367 With high load, circuit package window was reaching 0. Whenever
30368 we got a circuit-level sendme, we were reading a lot on each
30369 socket, but only writing out a bit. So we would eventually reach
30370 eof. This would be noticed and acted on even when there were still
30371 bytes sitting in the inbuf.
30372 - When poll() is interrupted, we shouldn't believe the revents values.
30374 o Bugfixes on 0.0.9pre6:
30375 - Fix hibernate bug that caused pre6 to be broken.
30376 - Don't keep rephist info for routers that haven't had activity for
30377 24 hours. (This matters now that clients have keys, since we track
30379 - Never call close_temp_logs while validating log options.
30380 - Fix backslash-escaping on tor.sh.in and torctl.in.
30383 - Implement weekly/monthly/daily accounting: now you specify your
30384 hibernation properties by
30385 AccountingMax N bytes|KB|MB|GB|TB
30386 AccountingStart day|week|month [day] HH:MM
30387 Defaults to "month 1 0:00".
30388 - Let bandwidth and interval config options be specified as 5 bytes,
30389 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
30390 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
30391 get back to normal.)
30392 - If your requested entry or exit node has advertised bandwidth 0,
30394 - Be more greedy about filling up relay cells -- we try reading again
30395 once we've processed the stuff we read, in case enough has arrived
30396 to fill the last cell completely.
30397 - Apply NT service patch from Osamu Fujino. Still needs more work.
30400 Changes in version 0.0.9pre6 - 2004-11-15
30401 o Bugfixes on 0.0.8.1:
30402 - Fix assert failure on malformed socks4a requests.
30403 - Use identity comparison, not nickname comparison, to choose which
30404 half of circuit-ID-space each side gets to use. This is needed
30405 because sometimes we think of a router as a nickname, and sometimes
30406 as a hex ID, and we can't predict what the other side will do.
30407 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
30408 write() call will fail and we handle it there.
30409 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
30410 and smartlist_len, which are two major profiling offenders.
30412 o Bugfixes on 0.0.9pre5:
30413 - Fix a bug in read_all that was corrupting config files on windows.
30414 - When we're raising the max number of open file descriptors to
30415 'unlimited', don't log that we just raised it to '-1'.
30416 - Include event code with events, as required by control-spec.txt.
30417 - Don't give a fingerprint when clients do --list-fingerprint:
30418 it's misleading, because it will never be the same again.
30419 - Stop using strlcpy in tor_strndup, since it was slowing us
30421 - Remove warn on startup about missing cached-directory file.
30422 - Make kill -USR1 work again.
30423 - Hibernate if we start tor during the "wait for wakeup-time" phase
30424 of an accounting interval. Log our hibernation plans better.
30425 - Authoritative dirservers now also cache their directory, so they
30426 have it on start-up.
30429 - Fetch running-routers; cache running-routers; compress
30430 running-routers; serve compressed running-routers.z
30431 - Add NSI installer script contributed by J Doe.
30432 - Commit VC6 and VC7 workspace/project files.
30433 - Commit a tor.spec for making RPM files, with help from jbash.
30434 - Add contrib/torctl.in contributed by Glenn Fink.
30435 - Implement the control-spec's SAVECONF command, to write your
30436 configuration to torrc.
30437 - Get cookie authentication for the controller closer to working.
30438 - Include control-spec.txt in the tarball.
30439 - When set_conf changes our server descriptor, upload a new copy.
30440 But don't upload it too often if there are frequent changes.
30441 - Document authentication config in man page, and document signals
30443 - Clean up confusing parts of man page and torrc.sample.
30444 - Make expand_filename handle ~ and ~username.
30445 - Use autoconf to enable largefile support where necessary. Use
30446 ftello where available, since ftell can fail at 2GB.
30447 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
30448 log more informatively.
30449 - Give a slightly more useful output for "tor -h".
30450 - Refuse application socks connections to port 0.
30451 - Check clock skew for verified servers, but allow unverified
30452 servers and clients to have any clock skew.
30453 - Break DirFetchPostPeriod into:
30454 - DirFetchPeriod for fetching full directory,
30455 - StatusFetchPeriod for fetching running-routers,
30456 - DirPostPeriod for posting server descriptor,
30457 - RendPostPeriod for posting hidden service descriptors.
30458 - Make sure the hidden service descriptors are at a random offset
30459 from each other, to hinder linkability.
30462 Changes in version 0.0.9pre5 - 2004-11-09
30463 o Bugfixes on 0.0.9pre4:
30464 - Fix a seg fault in unit tests (doesn't affect main program).
30465 - Fix an assert bug where a hidden service provider would fail if
30466 the first hop of his rendezvous circuit was down.
30467 - Hidden service operators now correctly handle version 1 style
30468 INTRODUCE1 cells (nobody generates them still, so not a critical
30470 - If do_hup fails, actually notice.
30471 - Handle more errnos from accept() without closing the listener.
30472 Some OpenBSD machines were closing their listeners because
30473 they ran out of file descriptors.
30474 - Send resolve cells to exit routers that are running a new
30475 enough version of the resolve code to work right.
30476 - Better handling of winsock includes on non-MSV win32 compilers.
30477 - Some people had wrapped their tor client/server in a script
30478 that would restart it whenever it died. This did not play well
30479 with our "shut down if your version is obsolete" code. Now people
30480 don't fetch a new directory if their local cached version is
30482 - Make our autogen.sh work on ksh as well as bash.
30485 - Hibernation: New config option "AccountingMaxKB" lets you
30486 set how many KBytes per month you want to allow your server to
30487 consume. Rather than spreading those bytes out evenly over the
30488 month, we instead hibernate for some of the month and pop up
30489 at a deterministic time, work until the bytes are consumed, then
30490 hibernate again. Config option "MonthlyAccountingStart" lets you
30491 specify which day of the month your billing cycle starts on.
30492 - Control interface: a separate program can now talk to your
30493 client/server over a socket, and get/set config options, receive
30494 notifications of circuits and streams starting/finishing/dying,
30495 bandwidth used, etc. The next step is to get some GUIs working.
30496 Let us know if you want to help out. See doc/control-spec.txt .
30497 - Ship a contrib/tor-control.py as an example script to interact
30498 with the control port.
30499 - "tor --hash-password zzyxz" will output a salted password for
30500 use in authenticating to the control interface.
30501 - New log format in config:
30502 "Log minsev[-maxsev] stdout|stderr|syslog" or
30503 "Log minsev[-maxsev] file /var/foo"
30506 - DirPolicy config option, to let people reject incoming addresses
30507 from their dirserver.
30508 - "tor --list-fingerprint" will list your identity key fingerprint
30510 - Add "pass" target for RedirectExit, to make it easier to break
30511 out of a sequence of RedirectExit rules.
30512 - Clients now generate a TLS cert too, in preparation for having
30513 them act more like real nodes.
30514 - Ship src/win32/ in the tarball, so people can use it to build.
30515 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
30517 - New "router-status" line in directory, to better bind each verified
30518 nickname to its identity key.
30519 - Deprecate unofficial config option abbreviations, and abbreviations
30520 not on the command line.
30521 - Add a pure-C tor-resolve implementation.
30522 - Use getrlimit and friends to ensure we can reach MaxConn (currently
30523 1024) file descriptors.
30525 o Code security improvements, inspired by Ilja:
30526 - Replace sprintf with snprintf. (I think they were all safe, but
30528 - Replace strcpy/strncpy with strlcpy in more places.
30529 - Avoid strcat; use snprintf or strlcat instead.
30530 - snprintf wrapper with consistent (though not C99) overflow behavior.
30533 Changes in version 0.0.9pre4 - 2004-10-17
30534 o Bugfixes on 0.0.9pre3:
30535 - If the server doesn't specify an exit policy, use the real default
30536 exit policy, not reject *:*.
30537 - Ignore fascistfirewall when uploading/downloading hidden service
30538 descriptors, since we go through Tor for those; and when using
30539 an HttpProxy, since we assume it can reach them all.
30540 - When looking for an authoritative dirserver, use only the ones
30541 configured at boot. Don't bother looking in the directory.
30542 - The rest of the fix for get_default_conf_file() on older win32.
30543 - Make 'Routerfile' config option obsolete.
30546 - New 'MyFamily nick1,...' config option for a server to
30547 specify other servers that shouldn't be used in the same circuit
30548 with it. Only believed if nick1 also specifies us.
30549 - New 'NodeFamily nick1,nick2,...' config option for a client to
30550 specify nodes that it doesn't want to use in the same circuit.
30551 - New 'Redirectexit pattern address:port' config option for a
30552 server to redirect exit connections, e.g. to a local squid.
30555 Changes in version 0.0.9pre3 - 2004-10-13
30556 o Bugfixes on 0.0.8.1:
30557 - Better torrc example lines for dirbindaddress and orbindaddress.
30558 - Improved bounds checking on parsed ints (e.g. config options and
30559 the ones we find in directories.)
30560 - Better handling of size_t vs int, so we're more robust on 64
30562 - Fix the rest of the bug where a newly started OR would appear
30563 as unverified even after we've added his fingerprint and hupped
30565 - Fix a bug from 0.0.7: when read() failed on a stream, we would
30566 close it without sending back an end. So 'connection refused'
30567 would simply be ignored and the user would get no response.
30569 o Bugfixes on 0.0.9pre2:
30570 - Serving the cached-on-disk directory to people is bad. We now
30571 provide no directory until we've fetched a fresh one.
30572 - Workaround for bug on windows where cached-directories get crlf
30574 - Make get_default_conf_file() work on older windows too.
30575 - If we write a *:* exit policy line in the descriptor, don't write
30576 any more exit policy lines.
30579 - Use only 0.0.9pre1 and later servers for resolve cells.
30580 - Make the dirservers file obsolete.
30581 - Include a dir-signing-key token in directories to tell the
30582 parsing entity which key is being used to sign.
30583 - Remove the built-in bulky default dirservers string.
30584 - New config option "Dirserver %s:%d [fingerprint]", which can be
30585 repeated as many times as needed. If no dirservers specified,
30586 default to moria1,moria2,tor26.
30587 - Make moria2 advertise a dirport of 80, so people behind firewalls
30588 will be able to get a directory.
30589 - Http proxy support
30590 - Dirservers translate requests for http://%s:%d/x to /x
30591 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
30592 be routed through this host.
30593 - Clients ask for /tor/x rather than /x for new enough dirservers.
30594 This way we can one day coexist peacefully with apache.
30595 - Clients specify a "Host: %s%d" http header, to be compatible
30596 with more proxies, and so running squid on an exit node can work.
30599 Changes in version 0.0.8.1 - 2004-10-13
30601 - Fix a seg fault that can be triggered remotely for Tor
30602 clients/servers with an open dirport.
30603 - Fix a rare assert trigger, where routerinfos for entries in
30604 our cpath would expire while we're building the path.
30605 - Fix a bug in OutboundBindAddress so it (hopefully) works.
30606 - Fix a rare seg fault for people running hidden services on
30607 intermittent connections.
30608 - Fix a bug in parsing opt keywords with objects.
30609 - Fix a stale pointer assert bug when a stream detaches and
30611 - Fix a string format vulnerability (probably not exploitable)
30612 in reporting stats locally.
30613 - Fix an assert trigger: sometimes launching circuits can fail
30614 immediately, e.g. because too many circuits have failed recently.
30615 - Fix a compile warning on 64 bit platforms.
30618 Changes in version 0.0.9pre2 - 2004-10-03
30620 - Make fetching a cached directory work for 64-bit platforms too.
30621 - Make zlib.h a required header, not an optional header.
30624 Changes in version 0.0.9pre1 - 2004-10-01
30626 - Stop using separate defaults for no-config-file and
30627 empty-config-file. Now you have to explicitly turn off SocksPort,
30628 if you don't want it open.
30629 - Fix a bug in OutboundBindAddress so it (hopefully) works.
30630 - Improve man page to mention more of the 0.0.8 features.
30631 - Fix a rare seg fault for people running hidden services on
30632 intermittent connections.
30633 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
30635 - Fix more dns related bugs: send back resolve_failed and end cells
30636 more reliably when the resolve fails, rather than closing the
30637 circuit and then trying to send the cell. Also attach dummy resolve
30638 connections to a circuit *before* calling dns_resolve(), to fix
30639 a bug where cached answers would never be sent in RESOLVED cells.
30640 - When we run out of disk space, or other log writing error, don't
30641 crash. Just stop logging to that log and continue.
30642 - We were starting to daemonize before we opened our logs, so if
30643 there were any problems opening logs, we would complain to stderr,
30644 which wouldn't work, and then mysteriously exit.
30645 - Fix a rare bug where sometimes a verified OR would connect to us
30646 before he'd uploaded his descriptor, which would cause us to
30647 assign conn->nickname as though he's unverified. Now we look through
30648 the fingerprint list to see if he's there.
30649 - Fix a rare assert trigger, where routerinfos for entries in
30650 our cpath would expire while we're building the path.
30653 - Clients can ask dirservers for /dir.z to get a compressed version
30654 of the directory. Only works for servers running 0.0.9, of course.
30655 - Make clients cache directories and use them to seed their router
30656 lists at startup. This means clients have a datadir again.
30657 - Configuration infrastructure support for warning on obsolete
30659 - Respond to content-encoding headers by trying to uncompress as
30661 - Reply with a deflated directory when a client asks for "dir.z".
30662 We could use allow-encodings instead, but allow-encodings isn't
30663 specified in HTTP 1.0.
30664 - Raise the max dns workers from 50 to 100.
30665 - Discourage people from setting their dirfetchpostperiod more often
30666 than once per minute.
30667 - Protect dirservers from overzealous descriptor uploading -- wait
30668 10 seconds after directory gets dirty, before regenerating.
30671 Changes in version 0.0.8 - 2004-08-25
30672 o Port it to SunOS 5.9 / Athena
30675 Changes in version 0.0.8rc2 - 2004-08-20
30676 o Make it compile on cygwin again.
30677 o When picking unverified routers, skip those with low uptime and/or
30678 low bandwidth, depending on what properties you care about.
30681 Changes in version 0.0.8rc1 - 2004-08-18
30682 o Changes from 0.0.7.3:
30684 - Fix assert triggers: if the other side returns an address 0.0.0.0,
30685 don't put it into the client dns cache.
30686 - If a begin failed due to exit policy, but we believe the IP address
30687 should have been allowed, switch that router to exitpolicy reject *:*
30688 until we get our next directory.
30690 - Clients choose nodes proportional to advertised bandwidth.
30691 - Avoid using nodes with low uptime as introduction points.
30692 - Handle servers with dynamic IP addresses: don't replace
30693 options->Address with the resolved one at startup, and
30694 detect our address right before we make a routerinfo each time.
30695 - 'FascistFirewall' option to pick dirservers and ORs on specific
30696 ports; plus 'FirewallPorts' config option to tell FascistFirewall
30697 which ports are open. (Defaults to 80,443)
30698 - Be more aggressive about trying to make circuits when the network
30699 has changed (e.g. when you unsuspend your laptop).
30700 - Check for time skew on http headers; report date in response to
30702 - If the entrynode config line has only one node, don't pick it as
30704 - Add strict{entry|exit}nodes config options. If set to 1, then
30705 we refuse to build circuits that don't include the specified entry
30707 - OutboundBindAddress config option, to bind to a specific
30708 IP address for outgoing connect()s.
30709 - End truncated log entries (e.g. directories) with "[truncated]".
30711 o Patches to 0.0.8preX:
30713 - Patches to compile and run on win32 again (maybe)?
30714 - Fix crash when looking for ~/.torrc with no $HOME set.
30715 - Fix a race bug in the unit tests.
30716 - Handle verified/unverified name collisions better when new
30717 routerinfo's arrive in a directory.
30718 - Sometimes routers were getting entered into the stats before
30719 we'd assigned their identity_digest. Oops.
30720 - Only pick and establish intro points after we've gotten a
30723 - AllowUnverifiedNodes config option to let circuits choose no-name
30724 routers in entry,middle,exit,introduction,rendezvous positions.
30725 Allow middle and rendezvous positions by default.
30726 - Add a man page for tor-resolve.
30729 Changes in version 0.0.7.3 - 2004-08-12
30730 o Stop dnsworkers from triggering an assert failure when you
30731 ask them to resolve the host "".
30734 Changes in version 0.0.8pre3 - 2004-08-09
30735 o Changes from 0.0.7.2:
30736 - Allow multiple ORs with same nickname in routerlist -- now when
30737 people give us one identity key for a nickname, then later
30738 another, we don't constantly complain until the first expires.
30739 - Remember used bandwidth (both in and out), and publish 15-minute
30740 snapshots for the past day into our descriptor.
30741 - You can now fetch $DIRURL/running-routers to get just the
30742 running-routers line, not the whole descriptor list. (But
30743 clients don't use this yet.)
30744 - When people mistakenly use Tor as an http proxy, point them
30745 at the tor-doc.html rather than the INSTALL.
30746 - Remove our mostly unused -- and broken -- hex_encode()
30747 function. Use base16_encode() instead. (Thanks to Timo Lindfors
30748 for pointing out this bug.)
30749 - Rotate onion keys every 12 hours, not every 2 hours, so we have
30750 fewer problems with people using the wrong key.
30751 - Change the default exit policy to reject the default edonkey,
30752 kazaa, gnutella ports.
30753 - Add replace_file() to util.[ch] to handle win32's rename().
30755 o Changes from 0.0.8preX:
30756 - Fix two bugs in saving onion keys to disk when rotating, so
30757 hopefully we'll get fewer people using old onion keys.
30758 - Fix an assert error that was making SocksPolicy not work.
30759 - Be willing to expire routers that have an open dirport -- it's
30760 just the authoritative dirservers we want to not forget.
30761 - Reject tor-resolve requests for .onion addresses early, so we
30762 don't build a whole rendezvous circuit and then fail.
30763 - When you're warning a server that he's unverified, don't cry
30764 wolf unpredictably.
30765 - Fix a race condition: don't try to extend onto a connection
30766 that's still handshaking.
30767 - For servers in clique mode, require the conn to be open before
30768 you'll choose it for your path.
30769 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
30770 end relay cell, etc.
30771 - Measure bandwidth capacity over the last 24 hours, not just 12
30772 - Bugfix: authoritative dirservers were making and signing a new
30773 directory for each client, rather than reusing the cached one.
30776 Changes in version 0.0.8pre2 - 2004-08-04
30777 o Changes from 0.0.7.2:
30779 - Check directory signature _before_ you decide whether you're
30780 you're running an obsolete version and should exit.
30781 - Check directory signature _before_ you parse the running-routers
30782 list to decide who's running or verified.
30783 - Bugfixes and features:
30784 - Check return value of fclose while writing to disk, so we don't
30785 end up with broken files when servers run out of disk space.
30786 - Log a warning if the user uses an unsafe socks variant, so people
30787 are more likely to learn about privoxy or socat.
30788 - Dirservers now include RFC1123-style dates in the HTTP headers,
30789 which one day we will use to better detect clock skew.
30791 o Changes from 0.0.8pre1:
30792 - Make it compile without warnings again on win32.
30793 - Log a warning if you're running an unverified server, to let you
30794 know you might want to get it verified.
30795 - Only pick a default nickname if you plan to be a server.
30798 Changes in version 0.0.8pre1 - 2004-07-23
30800 - Made our unit tests compile again on OpenBSD 3.5, and tor
30801 itself compile again on OpenBSD on a sparc64.
30802 - We were neglecting milliseconds when logging on win32, so
30803 everything appeared to happen at the beginning of each second.
30805 o Protocol changes:
30806 - 'Extend' relay cell payloads now include the digest of the
30807 intended next hop's identity key. Now we can verify that we're
30808 extending to the right router, and also extend to routers we
30809 hadn't heard of before.
30812 - Tor nodes can now act as relays (with an advertised ORPort)
30813 without being manually verified by the dirserver operators.
30814 - Uploaded descriptors of unverified routers are now accepted
30815 by the dirservers, and included in the directory.
30816 - Verified routers are listed by nickname in the running-routers
30817 list; unverified routers are listed as "$<fingerprint>".
30818 - We now use hash-of-identity-key in most places rather than
30819 nickname or addr:port, for improved security/flexibility.
30820 - To avoid Sybil attacks, paths still use only verified servers.
30821 But now we have a chance to play around with hybrid approaches.
30822 - Nodes track bandwidth usage to estimate capacity (not used yet).
30823 - ClientOnly option for nodes that never want to become servers.
30824 - Directory caching.
30825 - "AuthoritativeDir 1" option for the official dirservers.
30826 - Now other nodes (clients and servers) will cache the latest
30827 directory they've pulled down.
30828 - They can enable their DirPort to serve it to others.
30829 - Clients will pull down a directory from any node with an open
30830 DirPort, and check the signature/timestamp correctly.
30831 - Authoritative dirservers now fetch directories from other
30832 authdirservers, to stay better synced.
30833 - Running-routers list tells who's down also, along with noting
30834 if they're verified (listed by nickname) or unverified (listed
30836 - Allow dirservers to serve running-router list separately.
30837 This isn't used yet.
30838 - ORs connect-on-demand to other ORs
30839 - If you get an extend cell to an OR you're not connected to,
30840 connect, handshake, and forward the create cell.
30841 - The authoritative dirservers stay connected to everybody,
30842 and everybody stays connected to 0.0.7 servers, but otherwise
30843 clients/servers expire unused connections after 5 minutes.
30844 - When servers get a sigint, they delay 30 seconds (refusing new
30845 connections) then exit. A second sigint causes immediate exit.
30846 - File and name management:
30847 - Look for .torrc if no CONFDIR "torrc" is found.
30848 - If no datadir is defined, then choose, make, and secure ~/.tor
30850 - If torrc not found, exitpolicy reject *:*.
30851 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
30852 - If no nickname is defined, derive default from hostname.
30853 - Rename secret key files, e.g. identity.key -> secret_id_key,
30854 to discourage people from mailing their identity key to tor-ops.
30855 - Refuse to build a circuit before the directory has arrived --
30856 it won't work anyway, since you won't know the right onion keys
30858 - Try other dirservers immediately if the one you try is down. This
30859 should tolerate down dirservers better now.
30860 - Parse tor version numbers so we can do an is-newer-than check
30861 rather than an is-in-the-list check.
30862 - New socks command 'resolve', to let us shim gethostbyname()
30864 - A 'tor_resolve' script to access the socks resolve functionality.
30865 - A new socks-extensions.txt doc file to describe our
30866 interpretation and extensions to the socks protocols.
30867 - Add a ContactInfo option, which gets published in descriptor.
30868 - Publish OR uptime in descriptor (and thus in directory) too.
30869 - Write tor version at the top of each log file
30870 - New docs in the tarball:
30872 - Document that you should proxy your SSL traffic too.
30875 Changes in version 0.0.7.2 - 2004-07-07
30876 o A better fix for the 0.0.0.0 problem, that will hopefully
30877 eliminate the remaining related assertion failures.
30880 Changes in version 0.0.7.1 - 2004-07-04
30881 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
30882 since internally we use 0.0.0.0 to signify "not yet resolved".
30885 Changes in version 0.0.7 - 2004-06-07
30886 o Updated the man page to reflect the new features.
30889 Changes in version 0.0.7rc2 - 2004-06-06
30890 o Changes from 0.0.7rc1:
30891 - Make it build on Win32 again.
30892 o Changes from 0.0.6.2:
30893 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
30897 Changes in version 0.0.7rc1 - 2004-06-02
30899 - On sighup, we were adding another log without removing the first
30900 one. So log messages would get duplicated n times for n sighups.
30901 - Several cases of using a connection after we'd freed it. The
30902 problem was that connections that are pending resolve are in both
30903 the pending_resolve tree, and also the circuit's resolving_streams
30904 list. When you want to remove one, you must remove it from both.
30905 - Fix a double-mark-for-close where an end cell arrived for a
30906 resolving stream, and then the resolve failed.
30907 - Check directory signatures based on name of signer, not on whom
30908 we got the directory from. This will let us cache directories more
30911 - Crank up some of our constants to handle more users.
30914 Changes in version 0.0.7pre1 - 2004-06-02
30915 o Fixes for crashes and other obnoxious bugs:
30916 - Fix an epipe bug: sometimes when directory connections failed
30917 to connect, we would give them a chance to flush before closing
30919 - When we detached from a circuit because of resolvefailed, we
30920 would immediately try the same circuit twice more, and then
30921 give up on the resolve thinking we'd tried three different
30923 - Limit the number of intro circuits we'll attempt to build for a
30924 hidden service per 15-minute period.
30925 - Check recommended-software string *early*, before actually parsing
30926 the directory. Thus we can detect an obsolete version and exit,
30927 even if the new directory format doesn't parse.
30928 o Fixes for security bugs:
30929 - Remember which nodes are dirservers when you startup, and if a
30930 random OR enables his dirport, don't automatically assume he's
30931 a trusted dirserver.
30933 - Directory connections were asking the wrong poll socket to
30934 start writing, and not asking themselves to start writing.
30935 - When we detached from a circuit because we sent a begin but
30936 didn't get a connected, we would use it again the first time;
30937 but after that we would correctly switch to a different one.
30938 - Stop warning when the first onion decrypt attempt fails; they
30939 will sometimes legitimately fail now that we rotate keys.
30940 - Override unaligned-access-ok check when $host_cpu is ia64 or
30941 arm. Apparently they allow it but the kernel whines.
30942 - Dirservers try to reconnect periodically too, in case connections
30944 - Fix some memory leaks in directory servers.
30945 - Allow backslash in Win32 filenames.
30946 - Made Tor build complain-free on FreeBSD, hopefully without
30947 breaking other BSD builds. We'll see.
30949 - Doxygen markup on all functions and global variables.
30950 - Make directory functions update routerlist, not replace it. So
30951 now directory disagreements are not so critical a problem.
30952 - Remove the upper limit on number of descriptors in a dirserver's
30953 directory (not that we were anywhere close).
30954 - Allow multiple logfiles at different severity ranges.
30955 - Allow *BindAddress to specify ":port" rather than setting *Port
30956 separately. Allow multiple instances of each BindAddress config
30957 option, so you can bind to multiple interfaces if you want.
30958 - Allow multiple exit policy lines, which are processed in order.
30959 Now we don't need that huge line with all the commas in it.
30960 - Enable accept/reject policies on SOCKS connections, so you can bind
30961 to 0.0.0.0 but still control who can use your OP.
30964 Changes in version 0.0.6.2 - 2004-05-16
30965 o Our integrity-checking digest was checking only the most recent cell,
30966 not the previous cells like we'd thought.
30967 Thanks to Stefan Mark for finding the flaw!
30970 Changes in version 0.0.6.1 - 2004-05-06
30971 o Fix two bugs in our AES counter-mode implementation (this affected
30972 onion-level stream encryption, but not TLS-level). It turns
30973 out we were doing something much more akin to a 16-character
30974 polyalphabetic cipher. Oops.
30975 Thanks to Stefan Mark for finding the flaw!
30976 o Retire moria3 as a directory server, and add tor26 as a directory
30980 Changes in version 0.0.6 - 2004-05-02
30981 [version bump only]
30984 Changes in version 0.0.6rc4 - 2004-05-01
30985 o Update the built-in dirservers list to use the new directory format
30986 o Fix a rare seg fault: if a node offering a hidden service attempts
30987 to build a circuit to Alice's rendezvous point and fails before it
30988 reaches the last hop, it retries with a different circuit, but
30990 o Handle windows socket errors correctly.
30993 Changes in version 0.0.6rc3 - 2004-04-28
30994 o Don't expire non-general excess circuits (if we had enough
30995 circuits open, we were expiring rendezvous circuits -- even
30996 when they had a stream attached. oops.)
30997 o Fetch randomness from /dev/urandom better (not via fopen/fread)
30998 o Better debugging for tls errors
30999 o Some versions of openssl have an SSL_pending function that erroneously
31000 returns bytes when there is a non-application record pending.
31001 o Set Content-Type on the directory and hidserv descriptor.
31002 o Remove IVs from cipher code, since AES-ctr has none.
31003 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
31004 o We were using an array of length zero in a few places.
31005 o win32's gethostbyname can't resolve an IP to an IP.
31006 o win32's close can't close a socket.
31009 Changes in version 0.0.6rc2 - 2004-04-26
31010 o Fix a bug where we were closing tls connections intermittently.
31011 It turns out openssl keeps its errors around -- so if an error
31012 happens, and you don't ask about it, and then another openssl
31013 operation happens and succeeds, and you ask if there was an error,
31014 it tells you about the first error. Fun fun.
31015 o Fix a bug that's been lurking since 27 may 03 (!)
31016 When passing back a destroy cell, we would use the wrong circ id.
31017 'Mostly harmless', but still worth fixing.
31018 o Since we don't support truncateds much, don't bother sending them;
31019 just close the circ.
31020 o check for <machine/limits.h> so we build on NetBSD again (I hope).
31021 o don't crash if a conn that sent a begin has suddenly lost its circuit
31022 (this was quite rare).
31025 Changes in version 0.0.6rc1 - 2004-04-25
31026 o We now rotate link (tls context) keys and onion keys.
31027 o CREATE cells now include oaep padding, so you can tell
31028 if you decrypted them correctly.
31029 o Add bandwidthburst to server descriptor.
31030 o Directories now say which dirserver signed them.
31031 o Use a tor_assert macro that logs failed assertions too.
31034 Changes in version 0.0.6pre5 - 2004-04-18
31035 o changes from 0.0.6pre4:
31036 - make tor build on broken freebsd 5.2 installs
31037 - fix a failed assert when you try an intro point, get a nack, and try
31038 a second one and it works.
31039 - when alice uses a port that the hidden service doesn't accept,
31040 it now sends back an end cell (denied by exit policy). otherwise
31041 alice would just have to wait to time out.
31042 - fix another rare bug: when we had tried all the intro
31043 points for a hidden service, we fetched the descriptor
31044 again, but we left our introcirc thinking it had already
31045 sent an intro, so it kept waiting for a response...
31046 - bugfix: when you sleep your hidden-service laptop, as soon
31047 as it wakes up it tries to upload a service descriptor, but
31048 socketpair fails for some reason (localhost not up yet?).
31049 now we simply give up on that upload, and we'll try again later.
31050 i'd still like to find the bug though.
31051 - if an intro circ waiting for an ack dies before getting one, then
31053 - we were reusing stale service descriptors and refetching usable
31057 Changes in version 0.0.6pre4 - 2004-04-14
31058 o changes from 0.0.6pre3:
31059 - when bob fails to connect to the rendezvous point, and his
31060 circ didn't fail because of the rendezvous point itself, then
31061 he retries a couple of times
31062 - we expire introduction and rendezvous circs more thoroughly
31063 (sometimes they were hanging around forever)
31064 - we expire unattached rendezvous streams that have been around
31065 too long (they were sticking around forever).
31066 - fix a measly fencepost error that was crashing everybody with
31070 Changes in version 0.0.6pre3 - 2004-04-14
31071 o changes from 0.0.6pre2:
31072 - make hup work again
31073 - fix some memory leaks for dirservers
31074 - allow more skew in rendezvous descriptor timestamps, to help
31075 handle people like blanu who don't know what time it is
31076 - normal circs are 3 hops, but some rend/intro circs are 4, if
31077 the initiator doesn't get to choose the last hop
31078 - send acks for introductions, so alice can know whether to try
31080 - bob publishes intro points more correctly
31081 o changes from 0.0.5:
31082 - fix an assert trigger that's been plaguing us since the days
31083 of 0.0.2prexx (thanks weasel!)
31084 - retry stream correctly when we fail to connect because of
31085 exit-policy-reject (should try another) or can't-resolve-address
31086 (also should try another, because dns on random internet servers
31088 - when we hup a dirserver and we've *removed* a server from the
31089 approved-routers list, now we remove that server from the
31090 in-memory directories too
31093 Changes in version 0.0.6pre2 - 2004-04-08
31094 o We fixed our base32 implementation. Now it works on all architectures.
31097 Changes in version 0.0.6pre1 - 2004-04-08
31099 - Hidden services and rendezvous points are implemented. Go to
31100 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
31101 hidden services. (This only works via a socks4a proxy such as
31102 Privoxy, and currently it's quite slow.)
31105 Changes in version 0.0.5 - 2004-03-30
31106 [version bump only]
31109 Changes in version 0.0.5rc3 - 2004-03-29
31110 o Install torrc as torrc.sample -- we no longer clobber your
31112 o Re-enable recommendedversion checking (we broke it in rc2, oops)
31113 o Add in a 'notice' log level for things the operator should hear
31114 but that aren't warnings
31117 Changes in version 0.0.5rc2 - 2004-03-29
31118 o Hold socks connection open until reply is flushed (if possible)
31119 o Make exit nodes resolve IPs to IPs immediately, rather than asking
31120 the dns farm to do it.
31121 o Fix c99 aliasing warnings in rephist.c
31122 o Don't include server descriptors that are older than 24 hours in the
31124 o Give socks 'reject' replies their whole 15s to attempt to flush,
31125 rather than seeing the 60s timeout and assuming the flush had failed.
31126 o Clean automake droppings from the cvs repository
31129 Changes in version 0.0.5rc1 - 2004-03-28
31130 o Fix mangled-state bug in directory fetching (was causing sigpipes).
31131 o Only build circuits after we've fetched the directory: clients were
31132 using only the directory servers before they'd fetched a directory.
31133 This also means longer startup time; so it goes.
31134 o Fix an assert trigger where an OP would fail to handshake, and we'd
31135 expect it to have a nickname.
31136 o Work around a tsocks bug: do a socks reject when AP connection dies
31137 early, else tsocks goes into an infinite loop.
31140 Changes in version 0.0.4 - 2004-03-26
31141 o When connecting to a dirserver or OR and the network is down,
31145 Changes in version 0.0.3 - 2004-03-26
31146 o Warn and fail if server chose a nickname with illegal characters
31147 o Port to Solaris and Sparc:
31148 - include missing header fcntl.h
31149 - have autoconf find -lsocket -lnsl automatically
31150 - deal with hardware word alignment
31151 - make uname() work (solaris has a different return convention)
31152 - switch from using signal() to sigaction()
31153 o Preliminary work on reputation system:
31154 - Keep statistics on success/fail of connect attempts; they're published
31155 by kill -USR1 currently.
31156 - Add a RunTesting option to try to learn link state by creating test
31157 circuits, even when SocksPort is off.
31158 - Remove unused open circuits when there are too many.
31161 Changes in version 0.0.2 - 2004-03-19
31162 - Include strlcpy and strlcat for safer string ops
31163 - define INADDR_NONE so we compile (but still not run) on solaris
31166 Changes in version 0.0.2pre27 - 2004-03-14
31168 - Allow internal tor networks (we were rejecting internal IPs,
31169 now we allow them if they're set explicitly).
31170 - And fix a few endian issues.
31173 Changes in version 0.0.2pre26 - 2004-03-14
31175 - If a stream times out after 15s without a connected cell, don't
31176 try that circuit again: try a new one.
31177 - Retry streams at most 4 times. Then give up.
31178 - When a dirserver gets a descriptor from an unknown router, it
31179 logs its fingerprint (so the dirserver operator can choose to
31180 accept it even without mail from the server operator).
31181 - Inform unapproved servers when we reject their descriptors.
31182 - Make tor build on Windows again. It works as a client, who knows
31184 - Clearer instructions in the torrc for how to set up a server.
31185 - Be more efficient about reading fd's when our global token bucket
31186 (used for rate limiting) becomes empty.
31188 - Stop asserting that computers always go forward in time. It's
31190 - When we sent a cell (e.g. destroy) and then marked an OR connection
31191 expired, we might close it before finishing a flush if the other
31192 side isn't reading right then.
31193 - Don't allow dirservers to start if they haven't defined
31194 RecommendedVersions
31195 - We were caching transient dns failures. Oops.
31196 - Prevent servers from publishing an internal IP as their address.
31197 - Address a strcat vulnerability in circuit.c
31200 Changes in version 0.0.2pre25 - 2004-03-04
31202 - Put the OR's IP in its router descriptor, not its fqdn. That way
31203 we'll stop being stalled by gethostbyname for nodes with flaky dns,
31206 - If the user typed in an address that didn't resolve, the server
31210 Changes in version 0.0.2pre24 - 2004-03-03
31212 - Fix an assertion failure in dns.c, where we were trying to dequeue
31213 a pending dns resolve even if it wasn't pending
31214 - Fix a spurious socks5 warning about still trying to write after the
31215 connection is finished.
31216 - Hold certain marked_for_close connections open until they're finished
31217 flushing, rather than losing bytes by closing them too early.
31218 - Correctly report the reason for ending a stream
31219 - Remove some duplicate calls to connection_mark_for_close
31220 - Put switch_id and start_daemon earlier in the boot sequence, so it
31221 will actually try to chdir() to options.DataDirectory
31222 - Make 'make test' exit(1) if a test fails; fix some unit tests
31223 - Make tor fail when you use a config option it doesn't know about,
31224 rather than warn and continue.
31225 - Make --version work
31226 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
31229 Changes in version 0.0.2pre23 - 2004-02-29
31231 - Print a statement when the first circ is finished, so the user
31232 knows it's working.
31233 - If a relay cell is unrecognized at the end of the circuit,
31234 send back a destroy. (So attacks to mutate cells are more
31236 - New config option 'excludenodes' to avoid certain nodes for circuits.
31237 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
31238 so you can collect coredumps there.
31240 - Fix a bug in tls flushing where sometimes data got wedged and
31241 didn't flush until more data got sent. Hopefully this bug was
31242 a big factor in the random delays we were seeing.
31243 - Make 'connected' cells include the resolved IP, so the client
31244 dns cache actually gets populated.
31245 - Disallow changing from ORPort=0 to ORPort>0 on hup.
31246 - When we time-out on a stream and detach from the circuit, send an
31247 end cell down it first.
31248 - Only warn about an unknown router (in exitnodes, entrynodes,
31249 excludenodes) after we've fetched a directory.
31252 Changes in version 0.0.2pre22 - 2004-02-26
31254 - Servers publish less revealing uname information in descriptors.
31255 - More memory tracking and assertions, to crash more usefully when
31257 - If the default torrc isn't there, just use some default defaults.
31258 Plus provide an internal dirservers file if they don't have one.
31259 - When the user tries to use Tor as an http proxy, give them an http
31260 501 failure explaining that we're a socks proxy.
31261 - Dump a new router.desc on hup, to help confused people who change
31262 their exit policies and then wonder why router.desc doesn't reflect
31264 - Clean up the generic tor.sh init script that we ship with.
31266 - If the exit stream is pending on the resolve, and a destroy arrives,
31267 then the stream wasn't getting removed from the pending list. I
31268 think this was the one causing recent server crashes.
31269 - Use a more robust poll on OSX 10.3, since their poll is flaky.
31270 - When it couldn't resolve any dirservers, it was useless from then on.
31271 Now it reloads the RouterFile (or default dirservers) if it has no
31273 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
31274 many users don't even *have* a /usr/local/sbin/.
31277 Changes in version 0.0.2pre21 - 2004-02-18
31279 - There's a ChangeLog file that actually reflects the changelog.
31280 - There's a 'torify' wrapper script, with an accompanying
31281 tor-tsocks.conf, that simplifies the process of using tsocks for
31282 tor. It even has a man page.
31283 - The tor binary gets installed to sbin rather than bin now.
31284 - Retry streams where the connected cell hasn't arrived in 15 seconds
31285 - Clean up exit policy handling -- get the default out of the torrc,
31286 so we can update it without forcing each server operator to fix
31288 - Allow imaps and pop3s in default exit policy
31290 - Prevent picking middleman nodes as the last node in the circuit
31293 Changes in version 0.0.2pre20 - 2004-01-30
31295 - We now have a deb package, and it's in debian unstable. Go to
31296 it, apt-getters. :)
31297 - I've split the TotalBandwidth option into BandwidthRate (how many
31298 bytes per second you want to allow, long-term) and
31299 BandwidthBurst (how many bytes you will allow at once before the cap
31300 kicks in). This better token bucket approach lets you, say, set
31301 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
31302 performance while not exceeding your monthly bandwidth quota.
31303 - Push out a tls record's worth of data once you've got it, rather
31304 than waiting until you've read everything waiting to be read. This
31305 may improve performance by pipelining better. We'll see.
31306 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
31307 from failed circuits (if they haven't been connected yet) and attach
31309 - Expire old streams that haven't managed to connect. Some day we'll
31310 have them reattach to new circuits instead.
31313 - Fix several memory leaks that were causing servers to become bloated
31315 - Fix a few very rare assert triggers. A few more remain.
31316 - Setuid to User _before_ complaining about running as root.
31319 Changes in version 0.0.2pre19 - 2004-01-07
31321 - Fix deadlock condition in dns farm. We were telling a child to die by
31322 closing the parent's file descriptor to him. But newer children were
31323 inheriting the open file descriptor from the parent, and since they
31324 weren't closing it, the socket never closed, so the child never read
31325 eof, so he never knew to exit. Similarly, dns workers were holding
31326 open other sockets, leading to all sorts of chaos.
31327 - New cleaner daemon() code for forking and backgrounding.
31328 - If you log to a file, it now prints an entry at the top of the
31329 logfile so you know it's working.
31330 - The onionskin challenge length was 30 bytes longer than necessary.
31331 - Started to patch up the spec so it's not quite so out of date.
31334 Changes in version 0.0.2pre18 - 2004-01-02
31336 - Fix endian issues with the 'integrity' field in the relay header.
31337 - Fix a potential bug where connections in state
31338 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
31341 Changes in version 0.0.2pre17 - 2003-12-30
31343 - Made --debuglogfile (or any second log file, actually) work.
31344 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
31345 adversary could force us into an infinite loop.
31348 - Each onionskin handshake now includes a hash of the computed key,
31349 to prove the server's identity and help perfect forward secrecy.
31350 - Changed cell size from 256 to 512 bytes (working toward compatibility
31352 - Changed cell length to 2 bytes, and moved it to the relay header.
31353 - Implemented end-to-end integrity checking for the payloads of
31355 - Separated streamid from 'recognized' (otherwise circuits will get
31356 messed up when we try to have streams exit from the middle). We
31357 use the integrity-checking to confirm that a cell is addressed to
31359 - Randomize the initial circid and streamid values, so an adversary who
31360 breaks into a node can't learn how many circuits or streams have
31364 Changes in version 0.0.2pre16 - 2003-12-14
31366 - Fixed a bug that made HUP trigger an assert
31367 - Fixed a bug where a circuit that immediately failed wasn't being
31368 counted as a failed circuit in counting retries.
31371 - Now we close the circuit when we get a truncated cell: otherwise we're
31372 open to an anonymity attack where a bad node in the path truncates
31373 the circuit and then we open streams at him.
31374 - Add port ranges to exit policies
31375 - Add a conservative default exit policy
31376 - Warn if you're running tor as root
31377 - on HUP, retry OR connections and close/rebind listeners
31378 - options.EntryNodes: try these nodes first when picking the first node
31379 - options.ExitNodes: if your best choices happen to include any of
31380 your preferred exit nodes, you choose among just those preferred
31382 - options.ExcludedNodes: nodes that are never picked in path building
31385 Changes in version 0.0.2pre15 - 2003-12-03
31386 o Robustness and bugfixes:
31387 - Sometimes clients would cache incorrect DNS resolves, which would
31388 really screw things up.
31389 - An OP that goes offline would slowly leak all its sockets and stop
31391 - A wide variety of bugfixes in exit node selection, exit policy
31392 handling, and processing pending streams when a new circuit is
31394 - Pick nodes for a path only from those the directory says are up
31395 - Choose randomly from all running dirservers, not always the first one
31396 - Increase allowed http header size for directory fetch.
31397 - Stop writing to stderr (if we're daemonized it will be closed).
31398 - Enable -g always, so cores will be more useful to me.
31399 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
31402 - Wrote a man page. It lists commonly used options.
31405 - Change default loglevel to warn.
31406 - Make PidFile default to null rather than littering in your CWD.
31407 - OnionRouter config option is now obsolete. Instead it just checks
31409 - Moved to a single unified torrc file for both clients and servers.
31412 Changes in version 0.0.2pre14 - 2003-11-29
31413 o Robustness and bugfixes:
31414 - Force the admin to make the DataDirectory himself
31415 - to get ownership/permissions right
31416 - so clients no longer make a DataDirectory and then never use it
31417 - fix bug where a client who was offline for 45 minutes would never
31418 pull down a directory again
31419 - fix (or at least hide really well) the dns assert bug that was
31420 causing server crashes
31421 - warnings and improved robustness wrt clockskew for certs
31422 - use the native daemon(3) to daemonize, when available
31423 - exit if bind() fails
31424 - exit if neither socksport nor orport is defined
31425 - include our own tor_timegm (Win32 doesn't have its own)
31426 - bugfix for win32 with lots of connections
31427 - fix minor bias in PRNG
31428 - make dirserver more robust to corrupt cached directory
31431 - Wrote the design document (woo)
31433 o Circuit building and exit policies:
31434 - Circuits no longer try to use nodes that the directory has told them
31436 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
31437 bitcounts (18.0.0.0/8).
31438 - Make AP connections standby for a circuit if no suitable circuit
31439 exists, rather than failing
31440 - Circuits choose exit node based on addr/port, exit policies, and
31441 which AP connections are standing by
31442 - Bump min pathlen from 2 to 3
31443 - Relay end cells have a payload to describe why the stream ended.
31444 - If the stream failed because of exit policy, try again with a new
31446 - Clients have a dns cache to remember resolved addresses.
31447 - Notice more quickly when we have no working circuits
31450 - APPort is now called SocksPort
31451 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
31453 - RecommendedVersions is now a config variable rather than
31454 hardcoded (for dirservers)
31455 - Reloads config on HUP
31456 - Usage info on -h or --help
31457 - If you set User and Group config vars, it'll setu/gid to them.
31460 Changes in version 0.0.2pre13 - 2003-10-19
31461 o General stability:
31462 - SSL_write no longer fails when it returns WANTWRITE and the number
31463 of bytes in the buf has changed by the next SSL_write call.
31464 - Fix segfault fetching directory when network is down
31465 - Fix a variety of minor memory leaks
31466 - Dirservers reload the fingerprints file on HUP, so I don't have
31467 to take down the network when I approve a new router
31468 - Default server config file has explicit Address line to specify fqdn
31471 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
31472 - Make listener connections not ever alloc bufs
31474 o Autoconf improvements:
31475 - don't clobber an external CFLAGS in ./configure
31476 - Make install now works
31477 - create var/lib/tor on make install
31478 - autocreate a tor.sh initscript to help distribs
31479 - autocreate the torrc and sample-server-torrc with correct paths
31481 o Log files and Daemonizing now work:
31482 - If --DebugLogFile is specified, log to it at -l debug
31483 - If --LogFile is specified, use it instead of commandline
31484 - If --RunAsDaemon is set, tor forks and backgrounds on startup