1 Changes in version 0.4.0.4-rc - 2019-04-11
2 Tor 0.4.0.4-rc is the first release candidate in its series; it fixes
3 several bugs from earlier versions, including some that had affected
4 stability, and one that prevented relays from working with NSS.
6 o Major bugfixes (NSS, relay):
7 - When running with NSS, disable TLS 1.2 ciphersuites that use
8 SHA384 for their PRF. Due to an NSS bug, the TLS key exporters for
9 these ciphersuites don't work -- which caused relays to fail to
10 handshake with one another when these ciphersuites were enabled.
11 Fixes bug 29241; bugfix on 0.3.5.1-alpha.
13 o Minor features (bandwidth authority):
14 - Make bandwidth authorities ignore relays that are reported in the
15 bandwidth file with the flag "vote=0". This change allows us to
16 report unmeasured relays for diagnostic reasons without including
17 their bandwidth in the bandwidth authorities' vote. Closes
19 - When a directory authority is using a bandwidth file to obtain the
20 bandwidth values that will be included in the next vote, serve
21 this bandwidth file at /tor/status-vote/next/bandwidth. Closes
24 o Minor features (circuit padding):
25 - Stop warning about undefined behavior in the probability
26 distribution tests. Float division by zero may technically be
27 undefined behavior in C, but it's well defined in IEEE 754.
28 Partial backport of 29298. Closes ticket 29527; bugfix
31 o Minor features (continuous integration):
32 - On Travis Rust builds, cleanup Rust registry and refrain from
33 caching the "target/" directory to speed up builds. Resolves
36 o Minor features (dormant mode):
37 - Add a DormantCanceledByStartup option to tell Tor that it should
38 treat a startup event as cancelling any previous dormant state.
39 Integrators should use this option with caution: it should only be
40 used if Tor is being started because of something that the user
41 did, and not if Tor is being automatically started in the
42 background. Closes ticket 29357.
44 o Minor features (geoip):
45 - Update geoip and geoip6 to the April 2 2019 Maxmind GeoLite2
46 Country database. Closes ticket 29992.
48 o Minor features (NSS, diagnostic):
49 - Try to log an error from NSS (if there is any) and a more useful
50 description of our situation if we are using NSS and a call to
51 SSL_ExportKeyingMaterial() fails. Diagnostic for ticket 29241.
53 o Minor bugfixes (security):
54 - Fix a potential double free bug when reading huge bandwidth files.
55 The issue is not exploitable in the current Tor network because
56 the vulnerable code is only reached when directory authorities
57 read bandwidth files, but bandwidth files come from a trusted
58 source (usually the authorities themselves). Furthermore, the
59 issue is only exploitable in rare (non-POSIX) 32-bit architectures,
60 which are not used by any of the current authorities. Fixes bug
61 30040; bugfix on 0.3.5.1-alpha. Bug found and fixed by
63 - Verify in more places that we are not about to create a buffer
64 with more than INT_MAX bytes, to avoid possible OOB access in the
65 event of bugs. Fixes bug 30041; bugfix on 0.2.0.16. Found and
66 fixed by Tobias Stoeckmann.
68 o Minor bugfix (continuous integration):
69 - Reset coverage state on disk after Travis CI has finished. This
70 should prevent future coverage merge errors from causing the test
71 suite for the "process" subsystem to fail. The process subsystem
72 was introduced in 0.4.0.1-alpha. Fixes bug 29036; bugfix
74 - Terminate test-stem if it takes more than 9.5 minutes to run.
75 (Travis terminates the job after 10 minutes of no output.)
76 Diagnostic for 29437. Fixes bug 30011; bugfix on 0.3.5.4-alpha.
78 o Minor bugfixes (bootstrap reporting):
79 - During bootstrap reporting, correctly distinguish pluggable
80 transports from plain proxies. Fixes bug 28925; bugfix
83 o Minor bugfixes (C correctness):
84 - Fix an unlikely memory leak in consensus_diff_apply(). Fixes bug
85 29824; bugfix on 0.3.1.1-alpha. This is Coverity warning
88 o Minor bugfixes (circuitpadding testing):
89 - Minor tweaks to avoid rare test failures related to timers and
90 monotonic time. Fixes bug 29500; bugfix on 0.4.0.1-alpha.
92 o Minor bugfixes (directory authorities):
93 - Actually include the bandwidth-file-digest line in directory
94 authority votes. Fixes bug 29959; bugfix on 0.4.0.2-alpha.
96 o Minor bugfixes (logging):
97 - On Windows, when errors cause us to reload a consensus from disk,
98 tell the user that we are retrying at log level "notice".
99 Previously we only logged this information at "info", which was
100 confusing because the errors themselves were logged at "warning".
101 Improves previous fix for 28614. Fixes bug 30004; bugfix
104 o Minor bugfixes (pluggable transports):
105 - Restore old behavior when it comes to discovering the path of a
106 given Pluggable Transport executable file. A change in
107 0.4.0.1-alpha had broken this behavior on paths containing a
108 space. Fixes bug 29874; bugfix on 0.4.0.1-alpha.
110 o Minor bugfixes (testing):
111 - Backport the 0.3.4 src/test/test-network.sh to 0.2.9. We need a
112 recent test-network.sh to use new chutney features in CI. Fixes
113 bug 29703; bugfix on 0.2.9.1-alpha.
114 - Fix a test failure on Windows caused by an unexpected "BUG"
115 warning in our tests for tor_gmtime_r(-1). Fixes bug 29922; bugfix
118 o Minor bugfixes (TLS protocol):
119 - When classifying a client's selection of TLS ciphers, if the
120 client ciphers are not yet available, do not cache the result.
121 Previously, we had cached the unavailability of the cipher list
122 and never looked again, which in turn led us to assume that the
123 client only supported the ancient V1 link protocol. This, in turn,
124 was causing Stem integration tests to stall in some cases. Fixes
125 bug 30021; bugfix on 0.2.4.8-alpha.
127 o Code simplification and refactoring:
128 - Introduce a connection_dir_buf_add() helper function that detects
129 whether compression is in use, and adds a string accordingly.
130 Resolves issue 28816.
131 - Refactor handle_get_next_bandwidth() to use
132 connection_dir_buf_add(). Implements ticket 29897.
135 - Clarify that Tor performs stream isolation among *Port listeners
136 by default. Resolves issue 29121.
139 Changes in version 0.4.0.3-alpha - 2019-03-22
140 Tor 0.4.0.3-alpha is the third in its series; it fixes several small
141 bugs from earlier versions.
143 o Minor features (address selection):
144 - Treat the subnet 100.64.0.0/10 as public for some purposes;
145 private for others. This subnet is the RFC 6598 (Carrier Grade
146 NAT) IP range, and is deployed by many ISPs as an alternative to
147 RFC 1918 that does not break existing internal networks. Tor now
148 blocks SOCKS and control ports on these addresses and warns users
149 if client ports or ExtORPorts are listening on a RFC 6598 address.
150 Closes ticket 28525. Patch by Neel Chauhan.
152 o Minor features (geoip):
153 - Update geoip and geoip6 to the March 4 2019 Maxmind GeoLite2
154 Country database. Closes ticket 29666.
156 o Minor bugfixes (circuitpadding):
157 - Inspect the circuit-level cell queue before sending padding, to
158 avoid sending padding when too much data is queued. Fixes bug
159 29204; bugfix on 0.4.0.1-alpha.
161 o Minor bugfixes (logging):
162 - Correct a misleading error message when IPv4Only or IPv6Only is
163 used but the resolved address can not be interpreted as an address
164 of the specified IP version. Fixes bug 13221; bugfix on
165 0.2.3.9-alpha. Patch from Kris Katterjohn.
166 - Log the correct port number for listening sockets when "auto" is
167 used to let Tor pick the port number. Previously, port 0 was
168 logged instead of the actual port number. Fixes bug 29144; bugfix
169 on 0.3.5.1-alpha. Patch from Kris Katterjohn.
170 - Stop logging a BUG() warning when Tor is waiting for exit
171 descriptors. Fixes bug 28656; bugfix on 0.3.5.1-alpha.
173 o Minor bugfixes (memory management):
174 - Refactor the shared random state's memory management so that it
175 actually takes ownership of the shared random value pointers.
176 Fixes bug 29706; bugfix on 0.2.9.1-alpha.
178 o Minor bugfixes (memory management, testing):
179 - Stop leaking parts of the shared random state in the shared-random
180 unit tests. Fixes bug 29599; bugfix on 0.2.9.1-alpha.
182 o Minor bugfixes (pluggable transports):
183 - Fix an assertion failure crash bug when a pluggable transport is
184 terminated during the bootstrap phase. Fixes bug 29562; bugfix
187 o Minor bugfixes (Rust, protover):
188 - Add a missing "Padding" value to the Rust implementation of
189 protover. Fixes bug 29631; bugfix on 0.4.0.1-alpha.
191 o Minor bugfixes (single onion services):
192 - Allow connections to single onion services to remain idle without
193 being disconnected. Previously, relays acting as rendezvous points
194 for single onion services were mistakenly closing idle rendezvous
195 circuits after 60 seconds, thinking that they were unused
196 directory-fetching circuits that had served their purpose. Fixes
197 bug 29665; bugfix on 0.2.1.26.
199 o Minor bugfixes (stats):
200 - When ExtraInfoStatistics is 0, stop including PaddingStatistics in
201 relay and bridge extra-info documents. Fixes bug 29017; bugfix
204 o Minor bugfixes (testing):
205 - Downgrade some LOG_ERR messages in the address/* tests to
206 warnings. The LOG_ERR messages were occurring when we had no
207 configured network. We were failing the unit tests, because we
208 backported 28668 to 0.3.5.8, but did not backport 29530. Fixes bug
209 29530; bugfix on 0.3.5.8.
210 - Fix our gcov wrapper script to look for object files at the
211 correct locations. Fixes bug 29435; bugfix on 0.3.5.1-alpha.
212 - Decrease the false positive rate of stochastic probability
213 distribution tests. Fixes bug 29693; bugfix on 0.4.0.1-alpha.
215 o Minor bugfixes (Windows, CI):
216 - Skip the Appveyor 32-bit Windows Server 2016 job, and 64-bit
217 Windows Server 2012 R2 job. The remaining 2 jobs still provide
218 coverage of 64/32-bit, and Windows Server 2016/2012 R2. Also set
219 fast_finish, so failed jobs terminate the build immediately. Fixes
220 bug 29601; bugfix on 0.3.5.4-alpha.
223 Changes in version 0.3.5.8 - 2019-02-21
224 Tor 0.3.5.8 backports serveral fixes from later releases, including fixes
225 for an annoying SOCKS-parsing bug that affected users in earlier 0.3.5.x
228 It also includes a fix for a medium-severity security bug affecting Tor
229 0.3.2.1-alpha and later. All Tor instances running an affected release
230 should upgrade to 0.3.3.12, 0.3.4.11, 0.3.5.8, or 0.4.0.2-alpha.
232 o Major bugfixes (cell scheduler, KIST, security):
233 - Make KIST consider the outbuf length when computing what it can
234 put in the outbuf. Previously, KIST acted as though the outbuf
235 were empty, which could lead to the outbuf becoming too full. It
236 is possible that an attacker could exploit this bug to cause a Tor
237 client or relay to run out of memory and crash. Fixes bug 29168;
238 bugfix on 0.3.2.1-alpha. This issue is also being tracked as
239 TROVE-2019-001 and CVE-2019-8955.
241 o Major bugfixes (networking, backport from 0.4.0.2-alpha):
242 - Gracefully handle empty username/password fields in SOCKS5
243 username/password auth messsage and allow SOCKS5 handshake to
244 continue. Previously, we had rejected these handshakes, breaking
245 certain applications. Fixes bug 29175; bugfix on 0.3.5.1-alpha.
247 o Minor features (compilation, backport from 0.4.0.2-alpha):
248 - Compile correctly when OpenSSL is built with engine support
249 disabled, or with deprecated APIs disabled. Closes ticket 29026.
250 Patches from "Mangix".
252 o Minor features (geoip):
253 - Update geoip and geoip6 to the February 5 2019 Maxmind GeoLite2
254 Country database. Closes ticket 29478.
256 o Minor features (testing, backport from 0.4.0.2-alpha):
257 - Treat all unexpected ERR and BUG messages as test failures. Closes
260 o Minor bugfixes (onion service v3, client, backport from 0.4.0.1-alpha):
261 - Stop logging a "BUG()" warning and stacktrace when we find a SOCKS
262 connection waiting for a descriptor that we actually have in the
263 cache. It turns out that this can actually happen, though it is
264 rare. Now, tor will recover and retry the descriptor. Fixes bug
265 28669; bugfix on 0.3.2.4-alpha.
267 o Minor bugfixes (IPv6, backport from 0.4.0.1-alpha):
268 - Fix tor_ersatz_socketpair on IPv6-only systems. Previously, the
269 IPv6 socket was bound using an address family of AF_INET instead
270 of AF_INET6. Fixes bug 28995; bugfix on 0.3.5.1-alpha. Patch from
273 o Minor bugfixes (build, compatibility, rust, backport from 0.4.0.2-alpha):
274 - Update Cargo.lock file to match the version made by the latest
275 version of Rust, so that "make distcheck" will pass again. Fixes
276 bug 29244; bugfix on 0.3.3.4-alpha.
278 o Minor bugfixes (client, clock skew, backport from 0.4.0.1-alpha):
279 - Select guards even if the consensus has expired, as long as the
280 consensus is still reasonably live. Fixes bug 24661; bugfix
283 o Minor bugfixes (compilation, backport from 0.4.0.1-alpha):
284 - Compile correctly on OpenBSD; previously, we were missing some
285 headers required in order to detect it properly. Fixes bug 28938;
286 bugfix on 0.3.5.1-alpha. Patch from Kris Katterjohn.
288 o Minor bugfixes (documentation, backport from 0.4.0.2-alpha):
289 - Describe the contents of the v3 onion service client authorization
290 files correctly: They hold public keys, not private keys. Fixes
291 bug 28979; bugfix on 0.3.5.1-alpha. Spotted by "Felixix".
293 o Minor bugfixes (logging, backport from 0.4.0.1-alpha):
294 - Rework rep_hist_log_link_protocol_counts() to iterate through all
295 link protocol versions when logging incoming/outgoing connection
296 counts. Tor no longer skips version 5, and we won't have to
297 remember to update this function when new link protocol version is
298 developed. Fixes bug 28920; bugfix on 0.2.6.10.
300 o Minor bugfixes (logging, backport from 0.4.0.2-alpha):
301 - Log more information at "warning" level when unable to read a
302 private key; log more information at "info" level when unable to
303 read a public key. We had warnings here before, but they were lost
304 during our NSS work. Fixes bug 29042; bugfix on 0.3.5.1-alpha.
306 o Minor bugfixes (misc, backport from 0.4.0.2-alpha):
307 - The amount of total available physical memory is now determined
308 using the sysctl identifier HW_PHYSMEM (rather than HW_USERMEM)
309 when it is defined and a 64-bit variant is not available. Fixes
310 bug 28981; bugfix on 0.2.5.4-alpha. Patch from Kris Katterjohn.
312 o Minor bugfixes (onion services, backport from 0.4.0.2-alpha):
313 - Avoid crashing if ClientOnionAuthDir (incorrectly) contains more
314 than one private key for a hidden service. Fixes bug 29040; bugfix
316 - In hs_cache_store_as_client() log an HSDesc we failed to parse at
317 "debug" level. Tor used to log it as a warning, which caused very
318 long log lines to appear for some users. Fixes bug 29135; bugfix
320 - Stop logging "Tried to establish rendezvous on non-OR circuit..."
321 as a warning. Instead, log it as a protocol warning, because there
322 is nothing that relay operators can do to fix it. Fixes bug 29029;
323 bugfix on 0.2.5.7-rc.
325 o Minor bugfixes (tests, directory clients, backport from 0.4.0.1-alpha):
326 - Mark outdated dirservers when Tor only has a reasonably live
327 consensus. Fixes bug 28569; bugfix on 0.3.2.5-alpha.
329 o Minor bugfixes (tests, backport from 0.4.0.2-alpha):
330 - Detect and suppress "bug" warnings from the util/time test on
331 Windows. Fixes bug 29161; bugfix on 0.2.9.3-alpha.
332 - Do not log an error-level message if we fail to find an IPv6
333 network interface from the unit tests. Fixes bug 29160; bugfix
336 o Minor bugfixes (usability, backport from 0.4.0.1-alpha):
337 - Stop saying "Your Guard ..." in pathbias_measure_{use,close}_rate().
338 Some users took this phrasing to mean that the mentioned guard was
339 under their control or responsibility, which it is not. Fixes bug
340 28895; bugfix on Tor 0.3.0.1-alpha.
343 Changes in version 0.3.4.11 - 2019-02-21
344 Tor 0.3.4.11 is the third stable release in its series. It includes
345 a fix for a medium-severity security bug affecting Tor 0.3.2.1-alpha and
346 later. All Tor instances running an affected release should upgrade to
347 0.3.3.12, 0.3.4.11, 0.3.5.8, or 0.4.0.2-alpha.
349 o Major bugfixes (cell scheduler, KIST, security):
350 - Make KIST consider the outbuf length when computing what it can
351 put in the outbuf. Previously, KIST acted as though the outbuf
352 were empty, which could lead to the outbuf becoming too full. It
353 is possible that an attacker could exploit this bug to cause a Tor
354 client or relay to run out of memory and crash. Fixes bug 29168;
355 bugfix on 0.3.2.1-alpha. This issue is also being tracked as
356 TROVE-2019-001 and CVE-2019-8955.
358 o Minor features (geoip):
359 - Update geoip and geoip6 to the February 5 2019 Maxmind GeoLite2
360 Country database. Closes ticket 29478.
362 o Minor bugfixes (build, compatibility, rust, backport from 0.4.0.2-alpha):
363 - Update Cargo.lock file to match the version made by the latest
364 version of Rust, so that "make distcheck" will pass again. Fixes
365 bug 29244; bugfix on 0.3.3.4-alpha.
367 o Minor bugfixes (onion services, backport from 0.4.0.2-alpha):
368 - Stop logging "Tried to establish rendezvous on non-OR circuit..."
369 as a warning. Instead, log it as a protocol warning, because there
370 is nothing that relay operators can do to fix it. Fixes bug 29029;
371 bugfix on 0.2.5.7-rc.
374 Changes in version 0.3.3.12 - 2019-02-21
375 Tor 0.3.3.12 fixes a medium-severity security bug affecting Tor
376 0.3.2.1-alpha and later. All Tor instances running an affected release
377 should upgrade to 0.3.3.12, 0.3.4.11, 0.3.5.8, or 0.4.0.2-alpha.
379 This release marks the end of support for the Tor 0.3.3.x series. We
380 recommend that users switch to either the Tor 0.3.4 series (supported
381 until at least 10 June 2019), or the Tor 0.3.5 series, which will
382 receive long-term support until at least 1 Feb 2022.
384 o Major bugfixes (cell scheduler, KIST, security):
385 - Make KIST consider the outbuf length when computing what it can
386 put in the outbuf. Previously, KIST acted as though the outbuf
387 were empty, which could lead to the outbuf becoming too full. It
388 is possible that an attacker could exploit this bug to cause a Tor
389 client or relay to run out of memory and crash. Fixes bug 29168;
390 bugfix on 0.3.2.1-alpha. This issue is also being tracked as
391 TROVE-2019-001 and CVE-2019-8955.
393 o Minor features (geoip):
394 - Update geoip and geoip6 to the February 5 2019 Maxmind GeoLite2
395 Country database. Closes ticket 29478.
397 o Minor bugfixes (build, compatibility, rust, backport from 0.4.0.2-alpha):
398 - Update Cargo.lock file to match the version made by the latest
399 version of Rust, so that "make distcheck" will pass again. Fixes
400 bug 29244; bugfix on 0.3.3.4-alpha.
402 o Minor bugfixes (onion services, backport from 0.4.0.2-alpha):
403 - Stop logging "Tried to establish rendezvous on non-OR circuit..."
404 as a warning. Instead, log it as a protocol warning, because there
405 is nothing that relay operators can do to fix it. Fixes bug 29029;
406 bugfix on 0.2.5.7-rc.
409 Changes in version 0.4.0.2-alpha - 2019-02-21
410 Tor 0.4.0.2-alpha is the second alpha in its series; it fixes several
411 bugs from earlier versions, including several that had broken
412 backward compatibility.
414 It also includes a fix for a medium-severity security bug affecting Tor
415 0.3.2.1-alpha and later. All Tor instances running an affected release
416 should upgrade to 0.3.3.12, 0.3.4.11, 0.3.5.8, or 0.4.0.2-alpha.
418 o Major bugfixes (cell scheduler, KIST, security):
419 - Make KIST consider the outbuf length when computing what it can
420 put in the outbuf. Previously, KIST acted as though the outbuf
421 were empty, which could lead to the outbuf becoming too full. It
422 is possible that an attacker could exploit this bug to cause a Tor
423 client or relay to run out of memory and crash. Fixes bug 29168;
424 bugfix on 0.3.2.1-alpha. This issue is also being tracked as
425 TROVE-2019-001 and CVE-2019-8955.
427 o Major bugfixes (networking):
428 - Gracefully handle empty username/password fields in SOCKS5
429 username/password auth messsage and allow SOCKS5 handshake to
430 continue. Previously, we had rejected these handshakes, breaking
431 certain applications. Fixes bug 29175; bugfix on 0.3.5.1-alpha.
433 o Major bugfixes (windows, startup):
434 - When reading a consensus file from disk, detect whether it was
435 written in text mode, and re-read it in text mode if so. Always
436 write consensus files in binary mode so that we can map them into
437 memory later. Previously, we had written in text mode, which
438 confused us when we tried to map the file on windows. Fixes bug
439 28614; bugfix on 0.4.0.1-alpha.
441 o Minor features (compilation):
442 - Compile correctly when OpenSSL is built with engine support
443 disabled, or with deprecated APIs disabled. Closes ticket 29026.
444 Patches from "Mangix".
446 o Minor features (developer tooling):
447 - Check that bugfix versions in changes files look like Tor versions
448 from the versions spec. Warn when bugfixes claim to be on a future
449 release. Closes ticket 27761.
450 - Provide a git pre-commit hook that disallows commiting if we have
451 any failures in our code and changelog formatting checks. It is
452 now available in scripts/maint/pre-commit.git-hook. Implements
455 o Minor features (directory authority):
456 - When a directory authority is using a bandwidth file to obtain
457 bandwidth values, include the digest of that file in the vote.
460 o Minor features (geoip):
461 - Update geoip and geoip6 to the February 5 2019 Maxmind GeoLite2
462 Country database. Closes ticket 29478.
464 o Minor features (testing):
465 - Treat all unexpected ERR and BUG messages as test failures. Closes
468 o Minor bugfixes (build, compatibility, rust):
469 - Update Cargo.lock file to match the version made by the latest
470 version of Rust, so that "make distcheck" will pass again. Fixes
471 bug 29244; bugfix on 0.3.3.4-alpha.
473 o Minor bugfixes (compilation):
474 - Fix compilation warnings in test_circuitpadding.c. Fixes bug
475 29169; bugfix on 0.4.0.1-alpha.
476 - Silence a compiler warning in test-memwipe.c on OpenBSD. Fixes bug
477 29145; bugfix on 0.2.9.3-alpha. Patch from Kris Katterjohn.
479 o Minor bugfixes (documentation):
480 - Describe the contents of the v3 onion service client authorization
481 files correctly: They hold public keys, not private keys. Fixes
482 bug 28979; bugfix on 0.3.5.1-alpha. Spotted by "Felixix".
484 o Minor bugfixes (linux seccomp sandbox):
485 - Fix startup crash when experimental sandbox support is enabled.
486 Fixes bug 29150; bugfix on 0.4.0.1-alpha. Patch by Peter Gerber.
488 o Minor bugfixes (logging):
489 - Avoid logging that we are relaxing a circuit timeout when that
490 timeout is fixed. Fixes bug 28698; bugfix on 0.2.4.7-alpha.
491 - Log more information at "warning" level when unable to read a
492 private key; log more information at "info" level when unable to
493 read a public key. We had warnings here before, but they were lost
494 during our NSS work. Fixes bug 29042; bugfix on 0.3.5.1-alpha.
496 o Minor bugfixes (misc):
497 - The amount of total available physical memory is now determined
498 using the sysctl identifier HW_PHYSMEM (rather than HW_USERMEM)
499 when it is defined and a 64-bit variant is not available. Fixes
500 bug 28981; bugfix on 0.2.5.4-alpha. Patch from Kris Katterjohn.
502 o Minor bugfixes (onion services):
503 - Avoid crashing if ClientOnionAuthDir (incorrectly) contains more
504 than one private key for a hidden service. Fixes bug 29040; bugfix
506 - In hs_cache_store_as_client() log an HSDesc we failed to parse at
507 "debug" level. Tor used to log it as a warning, which caused very
508 long log lines to appear for some users. Fixes bug 29135; bugfix
510 - Stop logging "Tried to establish rendezvous on non-OR circuit..."
511 as a warning. Instead, log it as a protocol warning, because there
512 is nothing that relay operators can do to fix it. Fixes bug 29029;
513 bugfix on 0.2.5.7-rc.
515 o Minor bugfixes (scheduler):
516 - When re-adding channels to the pending list, check the correct
517 channel's sched_heap_idx. This issue has had no effect in mainline
518 Tor, but could have led to bugs down the road in improved versions
519 of our circuit scheduling code. Fixes bug 29508; bugfix
522 o Minor bugfixes (tests):
523 - Fix intermittent failures on an adaptive padding test. Fixes one
524 case of bug 29122; bugfix on 0.4.0.1-alpha.
525 - Disable an unstable circuit-padding test that was failing
526 intermittently because of an ill-defined small histogram. Such
527 histograms will be allowed again after 29298 is implemented. Fixes
528 a second case of bug 29122; bugfix on 0.4.0.1-alpha.
529 - Detect and suppress "bug" warnings from the util/time test on
530 Windows. Fixes bug 29161; bugfix on 0.2.9.3-alpha.
531 - Do not log an error-level message if we fail to find an IPv6
532 network interface from the unit tests. Fixes bug 29160; bugfix
536 - In the manpage entry describing MapAddress torrc setting, use
537 example IP addresses from ranges specified for use in documentation
538 by RFC 5737. Resolves issue 28623.
541 - Remove the old check-tor script. Resolves issue 29072.
544 Changes in version 0.4.0.1-alpha - 2019-01-18
545 Tor 0.4.0.1-alpha is the first release in the new 0.4.0.x series. It
546 introduces improved features for power and bandwidth conservation,
547 more accurate reporting of bootstrap progress for user interfaces, and
548 an experimental backend for an exciting new adaptive padding feature.
549 There is also the usual assortment of bugfixes and minor features, all
552 o Major features (battery management, client, dormant mode):
553 - When Tor is running as a client, and it is unused for a long time,
554 it can now enter a "dormant" state. When Tor is dormant, it avoids
555 network and CPU activity until it is reawoken either by a user
556 request or by a controller command. For more information, see the
557 configuration options starting with "Dormant". Implements tickets
559 - The client's memory of whether it is "dormant", and how long it
560 has spent idle, persists across invocations. Implements
562 - There is a DormantOnFirstStartup option that integrators can use
563 if they expect that in many cases, Tor will be installed but
566 o Major features (bootstrap reporting):
567 - When reporting bootstrap progress, report the first connection
568 uniformly, regardless of whether it's a connection for building
569 application circuits. This allows finer-grained reporting of early
570 progress than previously possible, with the improvements of ticket
571 27169. Closes tickets 27167 and 27103. Addresses ticket 27308.
572 - When reporting bootstrap progress, treat connecting to a proxy or
573 pluggable transport as separate from having successfully used that
574 proxy or pluggable transport to connect to a relay. Closes tickets
577 o Major features (circuit padding):
578 - Implement preliminary support for the circuit padding portion of
579 Proposal 254. The implementation supports Adaptive Padding (aka
580 WTF-PAD) state machines for use between experimental clients and
581 relays. Support is also provided for APE-style state machines that
582 use probability distributions instead of histograms to specify
583 inter-packet delay. At the moment, Tor does not provide any
584 padding state machines that are used in normal operation: for now,
585 this feature exists solely for experimentation. Closes
588 o Major features (refactoring):
589 - Tor now uses an explicit list of its own subsystems when
590 initializing and shutting down. Previously, these systems were
591 managed implicitly in various places throughout the codebase.
592 (There may still be some subsystems using the old system.) Closes
595 o Minor features (bootstrap reporting):
596 - When reporting bootstrap progress, stop distinguishing between
597 situations where only internal paths are available and situations
598 where external paths are available. Previously, Tor would often
599 erroneously report that it had only internal paths. Closes
602 o Minor features (continuous integration):
603 - Log Python version during each Travis CI job. Resolves
606 o Minor features (controller):
607 - Add a DROPOWNERSHIP command to undo the effects of TAKEOWNERSHIP.
608 Implements ticket 28843.
610 o Minor features (developer tooling):
611 - Provide a git hook script to prevent "fixup!" and "squash!"
612 commits from ending up in the master branch, as scripts/main/pre-
613 push.git-hook. Closes ticket 27993.
615 o Minor features (directory authority):
616 - Directory authorities support a new consensus algorithm, under
617 which the family lines in microdescriptors are encoded in a
618 canonical form. This change makes family lines more compressible
619 in transit, and on the client. Closes ticket 28266; implements
622 o Minor features (directory authority, relay):
623 - Authorities now vote on a "StaleDesc" flag to indicate that a
624 relay's descriptor is so old that the relay should upload again
625 soon. Relays treat this flag as a signal to upload a new
626 descriptor. This flag will eventually let us remove the
627 'published' date from routerstatus entries, and make our consensus
628 diffs much smaller. Closes ticket 26770; implements proposal 293.
630 o Minor features (fallback directory mirrors):
631 - Update the fallback whitelist based on operator opt-ins and opt-
632 outs. Closes ticket 24805, patch by Phoul.
634 o Minor features (FreeBSD):
635 - On FreeBSD-based systems, warn relay operators if the
636 "net.inet.ip.random_id" sysctl (IP ID randomization) is disabled.
639 o Minor features (HTTP standards compliance):
640 - Stop sending the header "Content-type: application/octet-stream"
641 along with transparently compressed documents: this confused
642 browsers. Closes ticket 28100.
644 o Minor features (IPv6):
645 - We add an option ClientAutoIPv6ORPort, to make clients randomly
646 prefer a node's IPv4 or IPv6 ORPort. The random preference is set
647 every time a node is loaded from a new consensus or bridge config.
648 We expect that this option will enable clients to bootstrap more
649 quickly without having to determine whether they support IPv4,
650 IPv6, or both. Closes ticket 27490. Patch by Neel Chauhan.
651 - When using addrs_in_same_network_family(), avoid choosing circuit
652 paths that pass through the same IPv6 subnet more than once.
653 Previously, we only checked IPv4 subnets. Closes ticket 24393.
654 Patch by Neel Chauhan.
656 o Minor features (log messages):
657 - Improve log message in v3 onion services that could print out
658 negative revision counters. Closes ticket 27707. Patch
661 o Minor features (memory usage):
662 - Save memory by storing microdescriptor family lists with a more
663 compact representation. Closes ticket 27359.
664 - Tor clients now use mmap() to read consensus files from disk, so
665 that they no longer need keep the full text of a consensus in
666 memory when parsing it or applying a diff. Closes ticket 27244.
668 o Minor features (parsing):
669 - Directory authorities now validate that router descriptors and
670 ExtraInfo documents are in a valid subset of UTF-8, and reject
671 them if they are not. Closes ticket 27367.
673 o Minor features (performance):
674 - Cache the results of summarize_protocol_flags(), so that we don't
675 have to parse the same protocol-versions string over and over.
676 This should save us a huge number of malloc calls on startup, and
677 may reduce memory fragmentation with some allocators. Closes
679 - Remove a needless memset() call from get_token_arguments, thereby
680 speeding up the tokenization of directory objects by about 20%.
682 - Replace parse_short_policy() with a faster implementation, to
683 improve microdescriptor parsing time. Closes ticket 28853.
684 - Speed up directory parsing a little by avoiding use of the non-
685 inlined strcmp_len() function. Closes ticket 28856.
686 - Speed up microdescriptor parsing by about 30%, to help improve
687 startup time. Closes ticket 28839.
689 o Minor features (pluggable transports):
690 - Add support for emitting STATUS updates to Tor's control port from
691 a pluggable transport process. Closes ticket 28846.
692 - Add support for logging to Tor's logging subsystem from a
693 pluggable transport process. Closes ticket 28180.
695 o Minor features (process management):
696 - Add a new process API for handling child processes. This new API
697 allows Tor to have bi-directional communication with child
698 processes on both Unix and Windows. Closes ticket 28179.
699 - Use the subsystem manager to initialize and shut down the process
700 module. Closes ticket 28847.
702 o Minor features (relay):
703 - When listing relay families, list them in canonical form including
704 the relay's own identity, and try to give a more useful set of
705 warnings. Part of ticket 28266 and proposal 298.
707 o Minor features (required protocols):
708 - Before exiting because of a missing required protocol, Tor will
709 now check the publication time of the consensus, and not exit
710 unless the consensus is newer than the Tor program's own release
711 date. Previously, Tor would not check the consensus publication
712 time, and so might exit because of a missing protocol that might
713 no longer be required in a current consensus. Implements proposal
714 297; closes ticket 27735.
716 o Minor features (testing):
717 - Allow a HeartbeatPeriod of less than 30 minutes in testing Tor
718 networks. Closes ticket 28840. Patch by Rob Jansen.
720 o Minor bugfixes (client, clock skew):
721 - Bootstrap successfully even when Tor's clock is behind the clocks
722 on the authorities. Fixes bug 28591; bugfix on 0.2.0.9-alpha.
723 - Select guards even if the consensus has expired, as long as the
724 consensus is still reasonably live. Fixes bug 24661; bugfix
727 o Minor bugfixes (compilation):
728 - Compile correctly on OpenBSD; previously, we were missing some
729 headers required in order to detect it properly. Fixes bug 28938;
730 bugfix on 0.3.5.1-alpha. Patch from Kris Katterjohn.
732 o Minor bugfixes (directory clients):
733 - Mark outdated dirservers when Tor only has a reasonably live
734 consensus. Fixes bug 28569; bugfix on 0.3.2.5-alpha.
736 o Minor bugfixes (directory mirrors):
737 - Even when a directory mirror's clock is behind the clocks on the
738 authorities, we now allow the mirror to serve "future"
739 consensuses. Fixes bug 28654; bugfix on 0.3.0.1-alpha.
741 o Minor bugfixes (DNS):
742 - Gracefully handle an empty or absent resolve.conf file by falling
743 back to using "localhost" as a DNS server (and hoping it works).
744 Previously, we would just stop running as an exit. Fixes bug
745 21900; bugfix on 0.2.1.10-alpha.
747 o Minor bugfixes (guards):
748 - In count_acceptable_nodes(), the minimum number is now one bridge
749 or guard node, and two non-guard nodes for a circuit. Previously,
750 we had added up the sum of all nodes with a descriptor, but that
751 could cause us to build failing circuits when we had either too
752 many bridges or not enough guard nodes. Fixes bug 25885; bugfix on
753 0.3.6.1-alpha. Patch by Neel Chauhan.
755 o Minor bugfixes (IPv6):
756 - Fix tor_ersatz_socketpair on IPv6-only systems. Previously, the
757 IPv6 socket was bound using an address family of AF_INET instead
758 of AF_INET6. Fixes bug 28995; bugfix on 0.3.5.1-alpha. Patch from
761 o Minor bugfixes (logging):
762 - Rework rep_hist_log_link_protocol_counts() to iterate through all
763 link protocol versions when logging incoming/outgoing connection
764 counts. Tor no longer skips version 5, and we won't have to
765 remember to update this function when new link protocol version is
766 developed. Fixes bug 28920; bugfix on 0.2.6.10.
768 o Minor bugfixes (networking):
769 - Introduce additional checks into tor_addr_parse() to reject
770 certain incorrect inputs that previously were not detected. Fixes
771 bug 23082; bugfix on 0.2.0.10-alpha.
773 o Minor bugfixes (onion service v3, client):
774 - Stop logging a "BUG()" warning and stacktrace when we find a SOCKS
775 connection waiting for a descriptor that we actually have in the
776 cache. It turns out that this can actually happen, though it is
777 rare. Now, tor will recover and retry the descriptor. Fixes bug
778 28669; bugfix on 0.3.2.4-alpha.
780 o Minor bugfixes (periodic events):
781 - Refrain from calling routerlist_remove_old_routers() from
782 check_descriptor_callback(). Instead, create a new hourly periodic
783 event. Fixes bug 27929; bugfix on 0.2.8.1-alpha.
785 o Minor bugfixes (pluggable transports):
786 - Make sure that data is continously read from standard output and
787 standard error pipes of a pluggable transport child-process, to
788 avoid deadlocking when a pipe's buffer is full. Fixes bug 26360;
789 bugfix on 0.2.3.6-alpha.
791 o Minor bugfixes (unit tests):
792 - Instead of relying on hs_free_all() to clean up all onion service
793 objects in test_build_descriptors(), we now deallocate them one by
794 one. This lets Coverity know that we are not leaking memory there
795 and fixes CID 1442277. Fixes bug 28989; bugfix on 0.3.5.1-alpha.
797 o Minor bugfixes (usability):
798 - Stop saying "Your Guard ..." in pathbias_measure_{use,close}_rate().
799 Some users took this phrasing to mean that the mentioned guard was
800 under their control or responsibility, which it is not. Fixes bug
801 28895; bugfix on Tor 0.3.0.1-alpha.
803 o Code simplification and refactoring:
804 - Reimplement NETINFO cell parsing and generation to rely on
805 trunnel-generated wire format handling code. Closes ticket 27325.
806 - Remove unnecessary unsafe code from the Rust macro "cstr!". Closes
808 - Rework SOCKS wire format handling to rely on trunnel-generated
809 parsing/generation code. Resolves ticket 27620.
810 - Split out bootstrap progress reporting from control.c into a
811 separate file. Part of ticket 27402.
812 - The .may_include files that we use to describe our directory-by-
813 directory dependency structure now describe a noncircular
814 dependency graph over the directories that they cover. Our
815 checkIncludes.py tool now enforces this noncircularity. Closes
819 - Mention that you cannot add a new onion service if Tor is already
820 running with Sandbox enabled. Closes ticket 28560.
821 - Improve ControlPort documentation. Mention that it accepts
822 address:port pairs, and can be used multiple times. Closes
824 - Document the exact output of "tor --version". Closes ticket 28889.
827 - Stop responding to the 'GETINFO status/version/num-concurring' and
828 'GETINFO status/version/num-versioning' control port commands, as
829 those were deprecated back in 0.2.0.30. Also stop listing them in
830 output of 'GETINFO info/names'. Resolves ticket 28757.
831 - The scripts used to generate and maintain the list of fallback
832 directories have been extracted into a new "fallback-scripts"
833 repository. Closes ticket 27914.
836 - Run shellcheck for scripts in the in scripts/ directory. Closes
838 - Add unit tests for tokenize_string() and get_next_token()
839 functions. Resolves ticket 27625.
841 o Code simplification and refactoring (onion service v3):
842 - Consolidate the authorized client descriptor cookie computation
843 code from client and service into one function. Closes
846 o Code simplification and refactoring (shell scripts):
847 - Cleanup scan-build.sh to silence shellcheck warnings. Closes
849 - Fix issues that shellcheck found in chutney-git-bisect.sh.
850 Resolves ticket 28006.
851 - Fix issues that shellcheck found in updateRustDependencies.sh.
852 Resolves ticket 28012.
853 - Fix shellcheck warnings in cov-diff script. Resolves issue 28009.
854 - Fix shellcheck warnings in run_calltool.sh. Resolves ticket 28011.
855 - Fix shellcheck warnings in run_trunnel.sh. Resolves issue 28010.
856 - Fix shellcheck warnings in scripts/test/coverage. Resolves
860 Changes in version 0.3.3.11 - 2019-01-07
861 Tor 0.3.3.11 backports numerous fixes from later versions of Tor.
862 numerous fixes, including an important fix for anyone using OpenSSL
863 1.1.1. Anyone running an earlier version of Tor 0.3.3 should upgrade
864 to this version, or to a later series.
866 As a reminder, support the Tor 0.3.3 series will end on 22 Feb 2019.
867 We anticipate that this will be the last release of Tor 0.3.3, unless
868 some major bug is before then. Some time between now and then, users
869 should switch to either the Tor 0.3.4 series (supported until at least
870 10 June 2019), or the Tor 0.3.5 series, which will receive long-term
871 support until at least 1 Feb 2022.
873 o Major bugfixes (OpenSSL, portability, backport from 0.3.5.5-alpha):
874 - Fix our usage of named groups when running as a TLS 1.3 client in
875 OpenSSL 1.1.1. Previously, we only initialized EC groups when
876 running as a relay, which caused clients to fail to negotiate TLS
877 1.3 with relays. Fixes bug 28245; bugfix on 0.2.9.15 (when TLS 1.3
880 o Major bugfixes (restart-in-process, backport from 0.3.5.1-alpha):
881 - Fix a use-after-free error that could be caused by passing Tor an
882 impossible set of options that would fail during options_act().
883 Fixes bug 27708; bugfix on 0.3.3.1-alpha.
885 o Minor features (continuous integration, backport from 0.3.5.1-alpha):
886 - Only run one online rust build in Travis, to reduce network
887 errors. Skip offline rust builds on Travis for Linux gcc, because
888 they're redundant. Implements ticket 27252.
889 - Skip gcc on OSX in Travis CI, because it's rarely used. Skip a
890 duplicate hardening-off build in Travis on Tor 0.2.9. Skip gcc on
891 Linux with default settings, because all the non-default builds
892 use gcc on Linux. Implements ticket 27252.
894 o Minor features (continuous integration, backport from 0.3.5.3-alpha):
895 - Use the Travis Homebrew addon to install packages on macOS during
896 Travis CI. The package list is the same, but the Homebrew addon
897 does not do a `brew update` by default. Implements ticket 27738.
899 o Minor features (fallback directory list, backport from 0.3.5.6-rc):
900 - Replace the 150 fallbacks originally introduced in Tor
901 0.3.3.1-alpha in January 2018 (of which ~115 were still
902 functional), with a list of 157 fallbacks (92 new, 65 existing, 85
903 removed) generated in December 2018. Closes ticket 24803.
905 o Minor features (geoip):
906 - Update geoip and geoip6 to the January 3 2019 Maxmind GeoLite2
907 Country database. Closes ticket 29012.
909 o Minor features (OpenSSL bug workaround, backport from 0.3.5.7):
910 - Work around a bug in OpenSSL 1.1.1a, which prevented the TLS 1.3
911 key export function from handling long labels. When this bug is
912 detected, Tor will disable TLS 1.3. We recommend upgrading to a
913 version of OpenSSL without this bug when it becomes available.
916 o Minor bugfixes (relay statistics, backport from 0.3.5.7):
917 - Update relay descriptor on bandwidth changes only when the uptime
918 is smaller than 24h, in order to reduce the efficiency of guard
919 discovery attacks. Fixes bug 24104; bugfix on 0.1.1.6-alpha.
921 o Minor bugfixes (C correctness, backport from 0.3.5.4-alpha):
922 - Avoid undefined behavior in an end-of-string check when parsing
923 the BEGIN line in a directory object. Fixes bug 28202; bugfix
926 o Minor bugfixes (code safety, backport from 0.3.5.3-alpha):
927 - Rewrite our assertion macros so that they no longer suppress the
928 compiler's -Wparentheses warnings. Fixes bug 27709; bugfix
930 o Minor bugfixes (compilation, backport from 0.3.5.5-alpha):
931 - Initialize a variable unconditionally in aes_new_cipher(), since
932 some compilers cannot tell that we always initialize it before
933 use. Fixes bug 28413; bugfix on 0.2.9.3-alpha.
935 o Minor bugfixes (directory authority, backport from 0.3.5.4-alpha):
936 - Log additional info when we get a relay that shares an ed25519 ID
937 with a different relay, instead making a BUG() warning. Fixes bug
938 27800; bugfix on 0.3.2.1-alpha.
940 o Minor bugfixes (directory permissions, backport form 0.3.5.3-alpha):
941 - When a user requests a group-readable DataDirectory, give it to
942 them. Previously, when the DataDirectory and the CacheDirectory
943 were the same, the default setting (0) for
944 CacheDirectoryGroupReadable would override the setting for
945 DataDirectoryGroupReadable. Fixes bug 26913; bugfix
948 o Minor bugfixes (onion service v3, backport from 0.3.5.1-alpha):
949 - When the onion service directory can't be created or has the wrong
950 permissions, do not log a stack trace. Fixes bug 27335; bugfix
953 o Minor bugfixes (onion service v3, backport from 0.3.5.2-alpha):
954 - Close all SOCKS request (for the same .onion) if the newly fetched
955 descriptor is unusable. Before that, we would close only the first
956 one leaving the other hanging and let to time out by themselves.
957 Fixes bug 27410; bugfix on 0.3.2.1-alpha.
959 o Minor bugfixes (onion service v3, backport from 0.3.5.3-alpha):
960 - Don't warn so loudly when Tor is unable to decode an onion
961 descriptor. This can now happen as a normal use case if a client
962 gets a descriptor with client authorization but the client is not
963 authorized. Fixes bug 27550; bugfix on 0.3.5.1-alpha.
965 o Minor bugfixes (onion service v3, backport from 0.3.5.6-rc):
966 - When deleting an ephemeral onion service (DEL_ONION), do not close
967 any rendezvous circuits in order to let the existing client
968 connections finish by themselves or closed by the application. The
969 HS v2 is doing that already so now we have the same behavior for
970 all versions. Fixes bug 28619; bugfix on 0.3.3.1-alpha.
972 o Minor bugfixes (HTTP tunnel):
973 - Fix a bug warning when closing an HTTP tunnel connection due to
974 an HTTP request we couldn't handle. Fixes bug 26470; bugfix on
977 o Minor bugfixes (memory leaks, backport from 0.3.5.5-alpha):
978 - Fix a harmless memory leak in libtorrunner.a. Fixes bug 28419;
979 bugfix on 0.3.3.1-alpha. Patch from Martin Kepplinger.
981 o Minor bugfixes (netflow padding, backport from 0.3.5.1-alpha):
982 - Ensure circuitmux queues are empty before scheduling or sending
983 padding. Fixes bug 25505; bugfix on 0.3.1.1-alpha.
985 o Minor bugfixes (protover, backport from 0.3.5.3-alpha):
986 - Reject protocol names containing bytes other than alphanumeric
987 characters and hyphens ([A-Za-z0-9-]). Fixes bug 27316; bugfix
990 o Minor bugfixes (rust, backport from 0.3.5.1-alpha):
991 - Compute protover votes correctly in the rust version of the
992 protover code. Previously, the protover rewrite in 24031 allowed
993 repeated votes from the same voter for the same protocol version
994 to be counted multiple times in protover_compute_vote(). Fixes bug
995 27649; bugfix on 0.3.3.5-rc.
996 - Reject protover names that contain invalid characters. Fixes bug
997 27687; bugfix on 0.3.3.1-alpha.
999 o Minor bugfixes (rust, backport from 0.3.5.2-alpha):
1000 - protover_all_supported() would attempt to allocate up to 16GB on
1001 some inputs, leading to a potential memory DoS. Fixes bug 27206;
1002 bugfix on 0.3.3.5-rc.
1004 o Minor bugfixes (rust, backport from 0.3.5.4-alpha):
1005 - Fix a potential null dereference in protover_all_supported(). Add
1006 a test for it. Fixes bug 27804; bugfix on 0.3.3.1-alpha.
1007 - Return a string that can be safely freed by C code, not one
1008 created by the rust allocator, in protover_all_supported(). Fixes
1009 bug 27740; bugfix on 0.3.3.1-alpha.
1010 - Fix an API mismatch in the rust implementation of
1011 protover_compute_vote(). This bug could have caused crashes on any
1012 directory authorities running Tor with Rust (which we do not yet
1013 recommend). Fixes bug 27741; bugfix on 0.3.3.6.
1015 o Minor bugfixes (testing, backport from 0.3.5.1-alpha):
1016 - If a unit test running in a subprocess exits abnormally or with a
1017 nonzero status code, treat the test as having failed, even if the
1018 test reported success. Without this fix, memory leaks don't cause
1019 the tests to fail, even with LeakSanitizer. Fixes bug 27658;
1020 bugfix on 0.2.2.4-alpha.
1022 o Minor bugfixes (testing, backport from 0.3.5.4-alpha):
1023 - Treat backtrace test failures as expected on BSD-derived systems
1024 (NetBSD, OpenBSD, and macOS/Darwin) until we solve bug 17808.
1025 (FreeBSD failures have been treated as expected since 18204 in
1026 0.2.8.) Fixes bug 27948; bugfix on 0.2.5.2-alpha.
1028 o Minor bugfixes (unit tests, guard selection, backport from 0.3.5.6-rc):
1029 - Stop leaking memory in an entry guard unit test. Fixes bug 28554;
1030 bugfix on 0.3.0.1-alpha.
1033 Changes in version 0.3.4.10 - 2019-01-07
1034 Tor 0.3.4.9 is the second stable release in its series; it backports
1035 numerous fixes, including an important fix for relays, and for anyone
1036 using OpenSSL 1.1.1. Anyone running an earlier version of Tor 0.3.4
1039 As a reminder, the Tor 0.3.4 series will be supported until 10 June
1040 2019. Some time between now and then, users should switch to the Tor
1041 0.3.5 series, which will receive long-term support until at least 1
1044 o Major bugfixes (OpenSSL, portability, backport from 0.3.5.5-alpha):
1045 - Fix our usage of named groups when running as a TLS 1.3 client in
1046 OpenSSL 1.1.1. Previously, we only initialized EC groups when
1047 running as a relay, which caused clients to fail to negotiate TLS
1048 1.3 with relays. Fixes bug 28245; bugfix on 0.2.9.15 (when TLS 1.3
1051 o Major bugfixes (relay, directory, backport from 0.3.5.7):
1052 - Always reactivate linked connections in the main loop so long as
1053 any linked connection has been active. Previously, connections
1054 serving directory information wouldn't get reactivated after the
1055 first chunk of data was sent (usually 32KB), which would prevent
1056 clients from bootstrapping. Fixes bug 28912; bugfix on
1057 0.3.4.1-alpha. Patch by "cypherpunks3".
1059 o Minor features (continuous integration, Windows, backport from 0.3.5.6-rc):
1060 - Always show the configure and test logs, and upload them as build
1061 artifacts, when building for Windows using Appveyor CI.
1064 o Minor features (controller, backport from 0.3.5.1-alpha):
1065 - For purposes of CIRC_BW-based dropped cell detection, track half-
1066 closed stream ids, and allow their ENDs, SENDMEs, DATA and path
1067 bias check cells to arrive without counting it as dropped until
1068 either the END arrives, or the windows are empty. Closes
1071 o Minor features (fallback directory list, backport from 0.3.5.6-rc):
1072 - Replace the 150 fallbacks originally introduced in Tor
1073 0.3.3.1-alpha in January 2018 (of which ~115 were still
1074 functional), with a list of 157 fallbacks (92 new, 65 existing, 85
1075 removed) generated in December 2018. Closes ticket 24803.
1077 o Minor features (geoip):
1078 - Update geoip and geoip6 to the November 6 2018 Maxmind GeoLite2
1079 Country database. Closes ticket 28395.
1081 o Minor features (OpenSSL bug workaround, backport from 0.3.5.7):
1082 - Work around a bug in OpenSSL 1.1.1a, which prevented the TLS 1.3
1083 key export function from handling long labels. When this bug is
1084 detected, Tor will disable TLS 1.3. We recommend upgrading to a
1085 version of OpenSSL without this bug when it becomes available.
1086 Closes ticket 28973.
1088 o Minor bugfixes (compilation, backport from 0.3.5.5-alpha):
1089 - Initialize a variable unconditionally in aes_new_cipher(), since
1090 some compilers cannot tell that we always initialize it before
1091 use. Fixes bug 28413; bugfix on 0.2.9.3-alpha.
1093 o Minor bugfixes (connection, relay, backport from 0.3.5.5-alpha):
1094 - Avoid a logging a BUG() stacktrace when closing connection held
1095 open because the write side is rate limited but not the read side.
1096 Now, the connection read side is simply shut down until Tor is
1097 able to flush the connection and close it. Fixes bug 27750; bugfix
1100 o Minor bugfixes (continuous integration, Windows, backport from 0.3.5.5-alpha):
1101 - Manually configure the zstd compiler options, when building using
1102 mingw on Appveyor Windows CI. The MSYS2 mingw zstd package does
1103 not come with a pkg-config file. Fixes bug 28454; bugfix
1105 - Stop using an external OpenSSL install, and stop installing MSYS2
1106 packages, when building using mingw on Appveyor Windows CI. Fixes
1107 bug 28399; bugfix on 0.3.4.1-alpha.
1109 o Minor bugfixes (continuous integration, Windows, backport from 0.3.5.6-rc):
1110 - Explicitly specify the path to the OpenSSL library and do not
1111 download OpenSSL from Pacman, but instead use the library that is
1112 already provided by AppVeyor. Fixes bug 28574; bugfix on master.
1114 o Minor bugfixes (directory permissions, backport form 0.3.5.3-alpha):
1115 - When a user requests a group-readable DataDirectory, give it to
1116 them. Previously, when the DataDirectory and the CacheDirectory
1117 were the same, the default setting (0) for
1118 CacheDirectoryGroupReadable would override the setting for
1119 DataDirectoryGroupReadable. Fixes bug 26913; bugfix
1122 o Minor bugfixes (memory leaks, backport from 0.3.5.5-alpha):
1123 - Fix a harmless memory leak in libtorrunner.a. Fixes bug 28419;
1124 bugfix on 0.3.3.1-alpha. Patch from Martin Kepplinger.
1126 o Minor bugfixes (onion service v3, backport from 0.3.5.3-alpha):
1127 - Don't warn so loudly when Tor is unable to decode an onion
1128 descriptor. This can now happen as a normal use case if a client
1129 gets a descriptor with client authorization but the client is not
1130 authorized. Fixes bug 27550; bugfix on 0.3.5.1-alpha.
1132 o Minor bugfixes (onion service v3, backport from 0.3.5.6-rc):
1133 - When deleting an ephemeral onion service (DEL_ONION), do not close
1134 any rendezvous circuits in order to let the existing client
1135 connections finish by themselves or closed by the application. The
1136 HS v2 is doing that already so now we have the same behavior for
1137 all versions. Fixes bug 28619; bugfix on 0.3.3.1-alpha.
1139 o Minor bugfixes (relay statistics, backport from 0.3.5.7):
1140 - Update relay descriptor on bandwidth changes only when the uptime
1141 is smaller than 24h, in order to reduce the efficiency of guard
1142 discovery attacks. Fixes bug 24104; bugfix on 0.1.1.6-alpha.
1144 o Minor bugfixes (unit tests, guard selection, backport from 0.3.5.6-rc):
1145 - Stop leaking memory in an entry guard unit test. Fixes bug 28554;
1146 bugfix on 0.3.0.1-alpha.
1149 Changes in version 0.3.5.7 - 2019-01-07
1150 Tor 0.3.5.7 is the first stable release in its series; it includes
1151 compilation and portability fixes, and a fix for a severe problem
1152 affecting directory caches.
1154 The Tor 0.3.5 series includes several new features and performance
1155 improvements, including client authorization for v3 onion services,
1156 cleanups to bootstrap reporting, support for improved bandwidth-
1157 measurement tools, experimental support for NSS in place of OpenSSL,
1158 and much more. It also begins a full reorganization of Tor's code
1159 layout, for improved modularity and maintainability in the future.
1160 Finally, there is the usual set of performance improvements and
1161 bugfixes that we try to do in every release series.
1163 There are a couple of changes in the 0.3.5 that may affect
1164 compatibility. First, the default version for newly created onion
1165 services is now v3. Use the HiddenServiceVersion option if you want to
1166 override this. Second, some log messages related to bootstrapping have
1167 changed; if you use stem, you may need to update to the latest version
1168 so it will recognize them.
1170 We have designated 0.3.5 as a "long-term support" (LTS) series: we
1171 will continue to patch major bugs in typical configurations of 0.3.5
1172 until at least 1 Feb 2022. (We do not plan to provide long-term
1173 support for embedding, Rust support, NSS support, running a directory
1174 authority, or unsupported platforms. For these, you will need to stick
1175 with the latest stable release.)
1177 Below are the changes since 0.3.5.6-rc. For a complete list of changes
1178 since 0.3.4.9, see the ReleaseNotes file.
1180 o Major bugfixes (relay, directory):
1181 - Always reactivate linked connections in the main loop so long as
1182 any linked connection has been active. Previously, connections
1183 serving directory information wouldn't get reactivated after the
1184 first chunk of data was sent (usually 32KB), which would prevent
1185 clients from bootstrapping. Fixes bug 28912; bugfix on
1186 0.3.4.1-alpha. Patch by "cypherpunks3".
1188 o Minor features (compilation):
1189 - When possible, place our warning flags in a separate file, to
1190 avoid flooding verbose build logs. Closes ticket 28924.
1192 o Minor features (geoip):
1193 - Update geoip and geoip6 to the January 3 2019 Maxmind GeoLite2
1194 Country database. Closes ticket 29012.
1196 o Minor features (OpenSSL bug workaround):
1197 - Work around a bug in OpenSSL 1.1.1a, which prevented the TLS 1.3
1198 key export function from handling long labels. When this bug is
1199 detected, Tor will disable TLS 1.3. We recommend upgrading to a
1200 version of OpenSSL without this bug when it becomes available.
1201 Closes ticket 28973.
1203 o Minor features (performance):
1204 - Remove about 96% of the work from the function that we run at
1205 startup to test our curve25519_basepoint implementation. Since
1206 this function has yet to find an actual failure, we now only run
1207 it for 8 iterations instead of 200. Based on our profile
1208 information, this change should save around 8% of our startup time
1209 on typical desktops, and may have a similar effect on other
1210 platforms. Closes ticket 28838.
1211 - Stop re-validating our hardcoded Diffie-Hellman parameters on
1212 every startup. Doing this wasted time and cycles, especially on
1213 low-powered devices. Closes ticket 28851.
1215 o Minor bugfixes (compilation):
1216 - Fix compilation for Android by adding a missing header to
1217 freespace.c. Fixes bug 28974; bugfix on 0.3.5.1-alpha.
1219 o Minor bugfixes (correctness):
1220 - Fix an unreached code path where we checked the value of
1221 "hostname" inside send_resolved_hostname_cell(). Previously, we
1222 used it before checking it; now we check it first. Fixes bug
1223 28879; bugfix on 0.1.2.7-alpha.
1225 o Minor bugfixes (testing):
1226 - Make sure that test_rebind.py actually obeys its timeout, even
1227 when it receives a large number of log messages. Fixes bug 28883;
1228 bugfix on 0.3.5.4-alpha.
1229 - Stop running stem's unit tests as part of "make test-stem", but
1230 continue to run stem's unit and online tests during "make test-
1231 stem-full". Fixes bug 28568; bugfix on 0.2.6.3-alpha.
1233 o Minor bugfixes (windows services):
1234 - Make Tor start correctly as an NT service again: previously it was
1235 broken by refactoring. Fixes bug 28612; bugfix on 0.3.5.3-alpha.
1237 o Code simplification and refactoring:
1238 - When parsing a port configuration, make it more obvious to static
1239 analyzer tools that we always initialize the address. Closes
1243 Changes in version 0.3.5.6-rc - 2018-12-18
1244 Tor 0.3.5.6-rc fixes numerous small bugs in earlier versions of Tor.
1245 It is the first release candidate in the 0.3.5.x series; if no further
1246 huge bugs are found, our next release may be the stable 0.3.5.x.
1248 o Minor features (continuous integration, Windows):
1249 - Always show the configure and test logs, and upload them as build
1250 artifacts, when building for Windows using Appveyor CI.
1253 o Minor features (fallback directory list):
1254 - Replace the 150 fallbacks originally introduced in Tor
1255 0.3.3.1-alpha in January 2018 (of which ~115 were still
1256 functional), with a list of 157 fallbacks (92 new, 65 existing, 85
1257 removed) generated in December 2018. Closes ticket 24803.
1259 o Minor features (geoip):
1260 - Update geoip and geoip6 to the December 5 2018 Maxmind GeoLite2
1261 Country database. Closes ticket 28744.
1263 o Minor bugfixes (compilation):
1264 - Add missing dependency on libgdi32.dll for tor-print-ed-signing-
1265 cert.exe on Windows. Fixes bug 28485; bugfix on 0.3.5.1-alpha.
1267 o Minor bugfixes (continuous integration, Windows):
1268 - Explicitly specify the path to the OpenSSL library and do not
1269 download OpenSSL from Pacman, but instead use the library that is
1270 already provided by AppVeyor. Fixes bug 28574; bugfix on master.
1272 o Minor bugfixes (onion service v3):
1273 - When deleting an ephemeral onion service (DEL_ONION), do not close
1274 any rendezvous circuits in order to let the existing client
1275 connections finish by themselves or closed by the application. The
1276 HS v2 is doing that already so now we have the same behavior for
1277 all versions. Fixes bug 28619; bugfix on 0.3.3.1-alpha.
1279 o Minor bugfixes (restart-in-process, boostrap):
1280 - Add missing resets of bootstrap tracking state when shutting down
1281 (regression caused by ticket 27169). Fixes bug 28524; bugfix
1284 o Minor bugfixes (testing):
1285 - Use a separate DataDirectory for the test_rebind script.
1286 Previously, this script would run using the default DataDirectory,
1287 and sometimes fail. Fixes bug 28562; bugfix on 0.3.5.1-alpha.
1288 Patch from Taylor R Campbell.
1289 - Stop leaking memory in an entry guard unit test. Fixes bug 28554;
1290 bugfix on 0.3.0.1-alpha.
1292 o Minor bugfixes (Windows):
1293 - Correctly identify Windows 8.1, Windows 10, and Windows Server
1294 2008 and later from their NT versions. Fixes bug 28096; bugfix on
1295 0.2.2.34; reported by Keifer Bly.
1296 - On recent Windows versions, the GetVersionEx() function may report
1297 an earlier Windows version than the running OS. To avoid user
1298 confusion, add "[or later]" to Tor's version string on affected
1299 versions of Windows. Fixes bug 28096; bugfix on 0.2.2.34; reported
1301 - Remove Windows versions that were never supported by the
1302 GetVersionEx() function. Stop duplicating the latest Windows
1303 version in get_uname(). Fixes bug 28096; bugfix on 0.2.2.34;
1304 reported by Keifer Bly.
1307 - Increase logging and tag all log entries with timestamps in
1308 test_rebind.py. Provides diagnostics for issue 28229.
1310 o Code simplification and refactoring (shared random, dirauth):
1311 - Change many tor_assert() to use BUG() instead. The idea is to not
1312 crash a dirauth but rather scream loudly with a stacktrace and let
1313 it continue run. The shared random subsystem is very resilient and
1314 if anything wrong happens with it, at worst a non coherent value
1315 will be put in the vote and discarded by the other authorities.
1316 Closes ticket 19566.
1318 o Documentation (onion services):
1319 - Document in the man page that changing ClientOnionAuthDir value or
1320 adding a new file in the directory will not work at runtime upon
1321 sending a HUP if Sandbox 1. Closes ticket 28128.
1322 - Note in the man page that the only real way to fully revoke an
1323 onion service v3 client authorization is by restarting the tor
1324 process. Closes ticket 28275.
1327 Changes in version 0.3.5.5-alpha - 2018-11-16
1328 Tor 0.3.5.5-alpha includes numerous bugfixes on earlier releases,
1329 including several that we hope to backport to older release series in
1332 o Major bugfixes (OpenSSL, portability):
1333 - Fix our usage of named groups when running as a TLS 1.3 client in
1334 OpenSSL 1.1.1. Previously, we only initialized EC groups when
1335 running as a relay, which caused clients to fail to negotiate TLS
1336 1.3 with relays. Fixes bug 28245; bugfix on 0.2.9.15 (when TLS 1.3
1339 o Minor features (geoip):
1340 - Update geoip and geoip6 to the November 6 2018 Maxmind GeoLite2
1341 Country database. Closes ticket 28395.
1343 o Minor bugfixes (compilation):
1344 - Initialize a variable unconditionally in aes_new_cipher(), since
1345 some compilers cannot tell that we always initialize it before
1346 use. Fixes bug 28413; bugfix on 0.2.9.3-alpha.
1348 o Minor bugfixes (connection, relay):
1349 - Avoid a logging a BUG() stacktrace when closing connection held
1350 open because the write side is rate limited but not the read side.
1351 Now, the connection read side is simply shut down until Tor is
1352 able to flush the connection and close it. Fixes bug 27750; bugfix
1355 o Minor bugfixes (continuous integration, Windows):
1356 - Manually configure the zstd compiler options, when building using
1357 mingw on Appveyor Windows CI. The MSYS2 mingw zstd package does
1358 not come with a pkg-config file. Fixes bug 28454; bugfix
1360 - Stop using an external OpenSSL install, and stop installing MSYS2
1361 packages, when building using mingw on Appveyor Windows CI. Fixes
1362 bug 28399; bugfix on 0.3.4.1-alpha.
1364 o Minor bugfixes (documentation):
1365 - Make Doxygen work again after the code movement in the 0.3.5
1366 source tree. Fixes bug 28435; bugfix on 0.3.5.1-alpha.
1368 o Minor bugfixes (Linux seccomp2 sandbox):
1369 - Permit the "shutdown()" system call, which is apparently used by
1370 OpenSSL under some circumstances. Fixes bug 28183; bugfix
1373 o Minor bugfixes (logging):
1374 - Stop talking about the Named flag in log messages. Clients have
1375 ignored the Named flag since 0.3.2. Fixes bug 28441; bugfix
1378 o Minor bugfixes (memory leaks):
1379 - Fix a harmless memory leak in libtorrunner.a. Fixes bug 28419;
1380 bugfix on 0.3.3.1-alpha. Patch from Martin Kepplinger.
1382 o Minor bugfixes (onion services):
1383 - On an intro point for a version 3 onion service, stop closing
1384 introduction circuits on an NACK. This lets the client decide
1385 whether to reuse the circuit or discard it. Previously, we closed
1386 intro circuits when sending NACKs. Fixes bug 27841; bugfix on
1387 0.3.2.1-alpha. Patch by Neel Chaunan.
1388 - When replacing a descriptor in the client cache, make sure to
1389 close all client introduction circuits for the old descriptor, so
1390 we don't end up with unusable leftover circuits. Fixes bug 27471;
1391 bugfix on 0.3.2.1-alpha.
1394 Changes in version 0.3.5.4-alpha - 2018-11-08
1395 Tor 0.3.5.4-alpha includes numerous bugfixes on earlier versions and
1396 improves our continuous integration support. It continues our attempts
1397 to stabilize this alpha branch and build it into a foundation for an
1398 acceptable long-term-support release.
1400 o Major bugfixes (compilation, rust):
1401 - Rust tests can now build and run successfully with the
1402 --enable-fragile-hardening option enabled. Doing this currently
1403 requires the rust beta channel; it will be possible with stable
1404 rust once Rust version 1.31 is released. Patch from Alex Crichton.
1405 Fixes bugs 27272, 27273, and 27274. Bugfix on 0.3.1.1-alpha.
1407 o Major bugfixes (embedding, main loop):
1408 - When DisableNetwork becomes set, actually disable periodic events
1409 that are already enabled. (Previously, we would refrain from
1410 enabling new ones, but we would leave the old ones turned on.)
1411 Fixes bug 28348; bugfix on 0.3.4.1-alpha.
1413 o Minor features (continuous integration):
1414 - Add a Travis CI build for --enable-nss on Linux gcc. Closes
1416 - Add new CI job to Travis configuration to run stem-based
1417 integration tests. Closes ticket 27913.
1419 o Minor features (Windows, continuous integration):
1420 - Build tor on Windows Server 2012 R2 and Windows Server 2016 using
1421 Appveyor's CI. Closes ticket 28318.
1423 o Minor bugfixes (C correctness, also in 0.3.4.9):
1424 - Avoid undefined behavior in an end-of-string check when parsing
1425 the BEGIN line in a directory object. Fixes bug 28202; bugfix
1428 o Minor bugfixes (compilation):
1429 - Fix a pair of missing headers on OpenBSD. Fixes bug 28303; bugfix
1430 on 0.3.5.1-alpha. Patch from Kris Katterjohn.
1432 o Minor bugfixes (compilation, OpenSolaris):
1433 - Fix compilation on OpenSolaris and its descendants by adding a
1434 missing include to compat_pthreads.c. Fixes bug 27963; bugfix
1437 o Minor bugfixes (configuration):
1438 - Refuse to start with relative file paths and RunAsDaemon set
1439 (regression from the fix for bug 22731). Fixes bug 28298; bugfix
1442 o Minor bugfixes (directory authority, also in 0.3.4.9):
1443 - Log additional info when we get a relay that shares an ed25519 ID
1444 with a different relay, instead of a BUG() warning with a
1445 backtrace. Fixes bug 27800; bugfix on 0.3.2.1-alpha.
1447 o Minor bugfixes (onion service v3):
1448 - Build the service descriptor's signing key certificate before
1449 uploading, so we always have a fresh one: leaving no chances for
1450 it to expire service side. Fixes bug 27838; bugfix
1453 o Minor bugfixes (onion service v3, client authorization):
1454 - Fix an assert() when adding a client authorization for the first
1455 time and then sending a HUP signal to the service. Before that,
1456 Tor would stop abruptly. Fixes bug 27995; bugfix on 0.3.5.1-alpha.
1458 o Minor bugfixes (onion services):
1459 - Unless we have explicitly set HiddenServiceVersion, detect the
1460 onion service version and then look for invalid options.
1461 Previously, we did the reverse, but that broke existing configs
1462 which were pointed to a v2 service and had options like
1463 HiddenServiceAuthorizeClient set. Fixes bug 28127; bugfix on
1464 0.3.5.1-alpha. Patch by Neel Chauhan.
1466 o Minor bugfixes (portability):
1467 - Make the OPE code (which is used for v3 onion services) run
1468 correctly on big-endian platforms. Fixes bug 28115; bugfix
1471 o Minor bugfixes (protover, rust):
1472 - Reject extra commas in version strings. Fixes bug 27197; bugfix
1475 o Minor bugfixes (relay shutdown, systemd):
1476 - Notify systemd of ShutdownWaitLength so it can be set to longer
1477 than systemd's TimeoutStopSec. In Tor's systemd service file, set
1478 TimeoutSec to 60 seconds to allow Tor some time to shut down.
1479 Fixes bug 28113; bugfix on 0.2.6.2-alpha.
1481 o Minor bugfixes (rust, also in 0.3.4.9):
1482 - Fix a potential null dereference in protover_all_supported(). Add
1483 a test for it. Fixes bug 27804; bugfix on 0.3.3.1-alpha.
1484 - Return a string that can be safely freed by C code, not one
1485 created by the rust allocator, in protover_all_supported(). Fixes
1486 bug 27740; bugfix on 0.3.3.1-alpha.
1488 o Minor bugfixes (rust, directory authority, also in 0.3.4.9):
1489 - Fix an API mismatch in the rust implementation of
1490 protover_compute_vote(). This bug could have caused crashes on any
1491 directory authorities running Tor with Rust (which we do not yet
1492 recommend). Fixes bug 27741; bugfix on 0.3.3.6.
1494 o Minor bugfixes (testing):
1495 - Avoid hangs and race conditions in test_rebind.py. Fixes bug
1496 27968; bugfix on 0.3.5.1-alpha.
1498 o Minor bugfixes (testing, also in 0.3.4.9):
1499 - Treat backtrace test failures as expected on BSD-derived systems
1500 (NetBSD, OpenBSD, and macOS/Darwin) until we solve bug 17808.
1501 (FreeBSD failures have been treated as expected since 18204 in
1502 0.2.8.) Fixes bug 27948; bugfix on 0.2.5.2-alpha.
1504 o Documentation (onion service manpage):
1505 - Improve HSv3 client authorization by making some options more
1506 explicit and detailed. Closes ticket 28026. Patch by Mike Tigas.
1509 Changes in version 0.3.4.9 - 2018-11-02
1510 Tor 0.3.4.9 is the second stable release in its series; it backports
1511 numerous fixes, including a fix for a bandwidth management bug that
1512 was causing memory exhaustion on relays. Anyone running an earlier
1513 version of Tor 0.3.4.9 should upgrade.
1515 o Major bugfixes (compilation, backport from 0.3.5.3-alpha):
1516 - Fix compilation on ARM (and other less-used CPUs) when compiling
1517 with OpenSSL before 1.1. Fixes bug 27781; bugfix on 0.3.4.1-alpha.
1519 o Major bugfixes (mainloop, bootstrap, backport from 0.3.5.3-alpha):
1520 - Make sure Tor bootstraps and works properly if only the
1521 ControlPort is set. Prior to this fix, Tor would only bootstrap
1522 when a client port was set (Socks, Trans, NATD, DNS or HTTPTunnel
1523 port). Fixes bug 27849; bugfix on 0.3.4.1-alpha.
1525 o Major bugfixes (relay, backport from 0.3.5.3-alpha):
1526 - When our write bandwidth limit is exhausted, stop writing on the
1527 connection. Previously, we had a typo in the code that would make
1528 us stop reading instead, leading to relay connections being stuck
1529 indefinitely and consuming kernel RAM. Fixes bug 28089; bugfix
1532 o Major bugfixes (restart-in-process, backport from 0.3.5.1-alpha):
1533 - Fix a use-after-free error that could be caused by passing Tor an
1534 impossible set of options that would fail during options_act().
1535 Fixes bug 27708; bugfix on 0.3.3.1-alpha.
1537 o Minor features (continuous integration, backport from 0.3.5.1-alpha):
1538 - Don't do a distcheck with --disable-module-dirauth in Travis.
1539 Implements ticket 27252.
1540 - Only run one online rust build in Travis, to reduce network
1541 errors. Skip offline rust builds on Travis for Linux gcc, because
1542 they're redundant. Implements ticket 27252.
1543 - Skip gcc on OSX in Travis CI, because it's rarely used. Skip a
1544 duplicate hardening-off build in Travis on Tor 0.2.9. Skip gcc on
1545 Linux with default settings, because all the non-default builds
1546 use gcc on Linux. Implements ticket 27252.
1548 o Minor features (continuous integration, backport from 0.3.5.3-alpha):
1549 - Use the Travis Homebrew addon to install packages on macOS during
1550 Travis CI. The package list is the same, but the Homebrew addon
1551 does not do a `brew update` by default. Implements ticket 27738.
1553 o Minor features (geoip):
1554 - Update geoip and geoip6 to the October 9 2018 Maxmind GeoLite2
1555 Country database. Closes ticket 27991.
1557 o Minor bugfixes (32-bit OSX and iOS, timing, backport from 0.3.5.2-alpha):
1558 - Fix an integer overflow bug in our optimized 32-bit millisecond-
1559 difference algorithm for 32-bit Apple platforms. Previously, it
1560 would overflow when calculating the difference between two times
1561 more than 47 days apart. Fixes part of bug 27139; bugfix
1563 - Improve the precision of our 32-bit millisecond difference
1564 algorithm for 32-bit Apple platforms. Fixes part of bug 27139;
1565 bugfix on 0.3.4.1-alpha.
1566 - Relax the tolerance on the mainloop/update_time_jumps test when
1567 running on 32-bit Apple platforms. Fixes part of bug 27139; bugfix
1570 o Minor bugfixes (C correctness, to appear in 0.3.5.4-alpha):
1571 - Avoid undefined behavior in an end-of-string check when parsing
1572 the BEGIN line in a directory object. Fixes bug 28202; bugfix
1575 o Minor bugfixes (CI, appveyor, to appear in 0.3.5.4-alpha):
1576 - Only install the necessary mingw packages during our appveyor
1577 builds. This change makes the build a little faster, and prevents
1578 a conflict with a preinstalled mingw openssl that appveyor now
1579 ships. Fixes bugs 27943 and 27765; bugfix on 0.3.4.2-alpha.
1581 o Minor bugfixes (code safety, backport from 0.3.5.3-alpha):
1582 - Rewrite our assertion macros so that they no longer suppress the
1583 compiler's -Wparentheses warnings. Fixes bug 27709; bugfix
1585 o Minor bugfixes (continuous integration, backport from 0.3.5.1-alpha):
1586 - Stop reinstalling identical packages in our Windows CI. Fixes bug
1587 27464; bugfix on 0.3.4.1-alpha.
1589 o Minor bugfixes (directory authority, to appear in 0.3.5.4-alpha):
1590 - Log additional info when we get a relay that shares an ed25519 ID
1591 with a different relay, instead making a BUG() warning. Fixes bug
1592 27800; bugfix on 0.3.2.1-alpha.
1594 o Minor bugfixes (directory connection shutdown, backport from 0.3.5.1-alpha):
1595 - Avoid a double-close when shutting down a stalled directory
1596 connection. Fixes bug 26896; bugfix on 0.3.4.1-alpha.
1598 o Minor bugfixes (HTTP tunnel, backport from 0.3.5.1-alpha):
1599 - Fix a bug warning when closing an HTTP tunnel connection due to an
1600 HTTP request we couldn't handle. Fixes bug 26470; bugfix
1603 o Minor bugfixes (netflow padding, backport from 0.3.5.1-alpha):
1604 - Ensure circuitmux queues are empty before scheduling or sending
1605 padding. Fixes bug 25505; bugfix on 0.3.1.1-alpha.
1607 o Minor bugfixes (onion service v3, backport from 0.3.5.1-alpha):
1608 - When the onion service directory can't be created or has the wrong
1609 permissions, do not log a stack trace. Fixes bug 27335; bugfix
1612 o Minor bugfixes (onion service v3, backport from 0.3.5.2-alpha):
1613 - Close all SOCKS request (for the same .onion) if the newly fetched
1614 descriptor is unusable. Before that, we would close only the first
1615 one leaving the other hanging and let to time out by themselves.
1616 Fixes bug 27410; bugfix on 0.3.2.1-alpha.
1618 o Minor bugfixes (onion service v3, backport from 0.3.5.3-alpha):
1619 - When selecting a v3 rendezvous point, don't only look at the
1620 protover, but also check whether the curve25519 onion key is
1621 present. This way we avoid picking a relay that supports the v3
1622 rendezvous but for which we don't have the microdescriptor. Fixes
1623 bug 27797; bugfix on 0.3.2.1-alpha.
1625 o Minor bugfixes (protover, backport from 0.3.5.3-alpha):
1626 - Reject protocol names containing bytes other than alphanumeric
1627 characters and hyphens ([A-Za-z0-9-]). Fixes bug 27316; bugfix
1630 o Minor bugfixes (rust, backport from 0.3.5.1-alpha):
1631 - Compute protover votes correctly in the rust version of the
1632 protover code. Previously, the protover rewrite in 24031 allowed
1633 repeated votes from the same voter for the same protocol version
1634 to be counted multiple times in protover_compute_vote(). Fixes bug
1635 27649; bugfix on 0.3.3.5-rc.
1636 - Reject protover names that contain invalid characters. Fixes bug
1637 27687; bugfix on 0.3.3.1-alpha.
1639 o Minor bugfixes (rust, backport from 0.3.5.2-alpha):
1640 - protover_all_supported() would attempt to allocate up to 16GB on
1641 some inputs, leading to a potential memory DoS. Fixes bug 27206;
1642 bugfix on 0.3.3.5-rc.
1644 o Minor bugfixes (rust, directory authority, to appear in 0.3.5.4-alpha):
1645 - Fix an API mismatch in the rust implementation of
1646 protover_compute_vote(). This bug could have caused crashes on any
1647 directory authorities running Tor with Rust (which we do not yet
1648 recommend). Fixes bug 27741; bugfix on 0.3.3.6.
1650 o Minor bugfixes (rust, to appear in 0.3.5.4-alpha):
1651 - Fix a potential null dereference in protover_all_supported(). Add
1652 a test for it. Fixes bug 27804; bugfix on 0.3.3.1-alpha.
1653 - Return a string that can be safely freed by C code, not one
1654 created by the rust allocator, in protover_all_supported(). Fixes
1655 bug 27740; bugfix on 0.3.3.1-alpha.
1657 o Minor bugfixes (testing, backport from 0.3.5.1-alpha):
1658 - If a unit test running in a subprocess exits abnormally or with a
1659 nonzero status code, treat the test as having failed, even if the
1660 test reported success. Without this fix, memory leaks don't cause
1661 the tests to fail, even with LeakSanitizer. Fixes bug 27658;
1662 bugfix on 0.2.2.4-alpha.
1664 o Minor bugfixes (testing, backport from 0.3.5.3-alpha):
1665 - Make the hs_service tests use the same time source when creating
1666 the introduction point and when testing it. Now tests work better
1667 on very slow systems like ARM or Travis. Fixes bug 27810; bugfix
1670 o Minor bugfixes (testing, to appear in 0.3.5.4-alpha):
1671 - Treat backtrace test failures as expected on BSD-derived systems
1672 (NetBSD, OpenBSD, and macOS/Darwin) until we solve bug 17808.
1673 (FreeBSD failures have been treated as expected since 18204 in
1674 0.2.8.) Fixes bug 27948; bugfix on 0.2.5.2-alpha.
1677 Changes in version 0.3.5.3-alpha - 2018-10-17
1678 Tor 0.3.5.3-alpha fixes several bugs, mostly from previous 0.3.5.x
1679 versions. One important fix for relays addresses a problem with rate-
1680 limiting code from back in 0.3.4.x: If the fix works out, we'll be
1681 backporting it soon. This release is still an alpha, but we hope it's
1682 getting closer and closer to stability.
1684 o Major features (onion services):
1685 - Version 3 onion services can now use the per-service
1686 HiddenServiceExportCircuitID option to differentiate client
1687 circuits. It communicates with the service by using the HAProxy
1688 protocol to assign virtual IP addresses to inbound client
1689 circuits. Closes ticket 4700. Patch by Mahrud Sayrafi.
1691 o Major bugfixes (compilation):
1692 - Fix compilation on ARM (and other less-used CPUs) when compiling
1693 with OpenSSL before 1.1. Fixes bug 27781; bugfix on 0.3.4.1-alpha.
1695 o Major bugfixes (initialization, crash):
1696 - Fix an assertion crash that would stop Tor from starting up if it
1697 tried to activate a periodic event too early. Fixes bug 27861;
1698 bugfix on 0.3.5.1-alpha.
1700 o Major bugfixes (mainloop, bootstrap):
1701 - Make sure Tor bootstraps and works properly if only the
1702 ControlPort is set. Prior to this fix, Tor would only bootstrap
1703 when a client port was set (Socks, Trans, NATD, DNS or HTTPTunnel
1704 port). Fixes bug 27849; bugfix on 0.3.4.1-alpha.
1706 o Major bugfixes (relay):
1707 - When our write bandwidth limit is exhausted, stop writing on the
1708 connection. Previously, we had a typo in the code that would make
1709 us stop reading instead, leading to relay connections being stuck
1710 indefinitely and consuming kernel RAM. Fixes bug 28089; bugfix
1713 o Minor features (continuous integration):
1714 - Use the Travis Homebrew addon to install packages on macOS during
1715 Travis CI. The package list is the same, but the Homebrew addon
1716 does not do a `brew update` by default. Implements ticket 27738.
1717 - Report what program produced the mysterious core file that we
1718 occasionally see on Travis CI during make distcheck. Closes
1721 o Minor features (geoip):
1722 - Update geoip and geoip6 to the October 9 2018 Maxmind GeoLite2
1723 Country database. Closes ticket 27991.
1725 o Minor bugfixes (code safety):
1726 - Rewrite our assertion macros so that they no longer suppress the
1727 compiler's -Wparentheses warnings. Fixes bug 27709; bugfix
1730 o Minor bugfixes (compilation):
1731 - Compile the ed25519-donna code with a correct declaration of
1732 crypto_strongest_rand(). Previously, we built it with one type,
1733 but linked it against another in the unit tests, which caused
1734 compilation failures with LTO enabled. This could have caused
1735 other undefined behavior in the tests. Fixes bug 27728; bugfix
1738 o Minor bugfixes (compilation, netbsd):
1739 - Add a missing include back into procmon.c. Fixes bug 27990; bugfix
1742 o Minor bugfixes (continuous integration, appveyor):
1743 - Install only the necessary mingw packages during our appveyor
1744 builds. This change makes the build a little faster, and prevents
1745 a conflict with a preinstalled mingw openssl that appveyor now
1746 ships. Fixes bugs 27765 and 27943; bugfix on 0.3.4.2-alpha.
1748 o Minor bugfixes (directory permissions):
1749 - When a user requests a group-readable DataDirectory, give it to
1750 them. Previously, when the DataDirectory and the CacheDirectory
1751 were the same, the default setting (0) for
1752 CacheDirectoryGroupReadable would override the setting for
1753 DataDirectoryGroupReadable. Fixes bug 26913; bugfix
1756 o Minor bugfixes (memory leaks):
1757 - Fix a small memory leak when calling Tor with --dump-config. Fixes
1758 bug 27893; bugfix on 0.3.2.1-alpha.
1760 o Minor bugfixes (networking):
1761 - In retry_listeners_ports(), make sure that we're removing a member
1762 of old_conns smartlist at most once. Fixes bug 27808; bugfix
1764 - Refrain from attempting socket rebinding when old and new
1765 listeners are in different address families. Fixes bug 27928;
1766 bugfix on 0.3.5.1-alpha.
1768 o Minor bugfixes (onion service v3):
1769 - Stop dumping a stack trace when trying to connect to an intro
1770 point without having a descriptor for it. Fixes bug 27774; bugfix
1772 - Don't warn so loudly when Tor is unable to decode an onion
1773 descriptor. This can now happen as a normal use case if a client
1774 gets a descriptor with client authorization but the client is not
1775 authorized. Fixes bug 27550; bugfix on 0.3.5.1-alpha.
1776 - When selecting a v3 rendezvous point, don't only look at the
1777 protover, but also check whether the curve25519 onion key is
1778 present. This way we avoid picking a relay that supports the v3
1779 rendezvous but for which we don't have the microdescriptor. Fixes
1780 bug 27797; bugfix on 0.3.2.1-alpha.
1782 o Minor bugfixes (protover):
1783 - Reject protocol names containing bytes other than alphanumeric
1784 characters and hyphens ([A-Za-z0-9-]). Fixes bug 27316; bugfix
1787 o Minor bugfixes (testing):
1788 - Make the hs_service tests use the same time source when creating
1789 the introduction point and when testing it. Now tests work better
1790 on very slow systems like ARM or Travis. Fixes bug 27810; bugfix
1792 - In test_rebind.py, check if the Python version is in the supported
1793 range. Fixes bug 27675; bugfix on 0.3.5.1-alpha.
1795 o Code simplification and refactoring:
1796 - Divide more large Tor source files -- especially ones that span
1797 multiple areas of functionality -- into smaller parts, including
1798 onion.c and main.c. Closes ticket 26747.
1799 - Divide the "routerparse.c" module into separate modules for each
1800 group of parsed objects. Closes ticket 27924.
1801 - Move protover_rust.c to the same place protover.c was moved to.
1802 Closes ticket 27814.
1803 - Split directory.c into separate pieces for client, server, and
1804 common functionality. Closes ticket 26744.
1805 - Split the non-statistics-related parts from the rephist.c and
1806 geoip.c modules. Closes ticket 27892.
1807 - Split the router.c file into relay-only and shared components, to
1808 help with future modularization. Closes ticket 27864.
1811 - In the tor-resolve(1) manpage, fix the reference to socks-
1812 extensions.txt by adding a web URL. Resolves ticket 27853.
1813 - Mention that we require Python to be 2.7 or newer for some
1814 integration tests that we ship with Tor. Resolves ticket 27677.
1817 Changes in version 0.3.5.2-alpha - 2018-09-21
1818 Tor 0.3.5.2-alpha fixes several bugs in 0.3.5.1-alpha, including one
1819 that made Tor think it had run out of sockets. Anybody running a relay
1820 or an onion service on 0.3.5.1-alpha should upgrade.
1822 o Major bugfixes (relay bandwidth statistics):
1823 - When we close relayed circuits, report the data in the circuit
1824 queues as being written in our relay bandwidth stats. This
1825 mitigates guard discovery and other attacks that close circuits
1826 for the explicit purpose of noticing this discrepancy in
1827 statistics. Fixes bug 23512; bugfix on 0.0.8pre3.
1829 o Major bugfixes (socket accounting):
1830 - In our socket accounting code, count a socket as closed even when
1831 it is closed indirectly by the TLS layer. Previously, we would
1832 count these sockets as still in use, and incorrectly believe that
1833 we had run out of sockets. Fixes bug 27795; bugfix
1836 o Minor bugfixes (32-bit OSX and iOS, timing):
1837 - Fix an integer overflow bug in our optimized 32-bit millisecond-
1838 difference algorithm for 32-bit Apple platforms. Previously, it
1839 would overflow when calculating the difference between two times
1840 more than 47 days apart. Fixes part of bug 27139; bugfix
1842 - Improve the precision of our 32-bit millisecond difference
1843 algorithm for 32-bit Apple platforms. Fixes part of bug 27139;
1844 bugfix on 0.3.4.1-alpha.
1845 - Relax the tolerance on the mainloop/update_time_jumps test when
1846 running on 32-bit Apple platforms. Fixes part of bug 27139; bugfix
1849 o Minor bugfixes (onion service v3):
1850 - Close all SOCKS request (for the same .onion) if the newly fetched
1851 descriptor is unusable. Before that, we would close only the first
1852 one leaving the other hanging and let to time out by themselves.
1853 Fixes bug 27410; bugfix on 0.3.2.1-alpha.
1855 o Minor bugfixes (memory leak):
1856 - Fix an unlikely memory leak when trying to read a private key from
1857 a ridiculously large file. Fixes bug 27764; bugfix on
1858 0.3.5.1-alpha. This is CID 1439488.
1860 o Minor bugfixes (NSS):
1861 - Correctly detect failure to open a dummy TCP socket when stealing
1862 ownership of an fd from the NSS layer. Fixes bug 27782; bugfix
1865 o Minor bugfixes (rust):
1866 - protover_all_supported() would attempt to allocate up to 16GB on
1867 some inputs, leading to a potential memory DoS. Fixes bug 27206;
1868 bugfix on 0.3.3.5-rc.
1870 o Minor bugfixes (testing):
1871 - Revise the "conditionvar_timeout" test so that it succeeds even on
1872 heavily loaded systems where the test threads are not scheduled
1873 within 200 msec. Fixes bug 27073; bugfix on 0.2.6.3-alpha.
1875 o Code simplification and refactoring:
1876 - Divide the routerlist.c and dirserv.c modules into smaller parts.
1877 Closes ticket 27799.
1880 Changes in version 0.3.5.1-alpha - 2018-09-18
1881 Tor 0.3.5.1-alpha is the first release of the 0.3.5.x series. It adds
1882 client authorization for modern (v3) onion services, improves
1883 bootstrap reporting, begins reorganizing Tor's codebase, adds optional
1884 support for NSS in place of OpenSSL, and much more.
1886 o Major features (onion services, UI change):
1887 - For a newly created onion service, the default version is now 3.
1888 Tor still supports existing version 2 services, but the operator
1889 now needs to set "HiddenServiceVersion 2" in order to create a new
1890 version 2 service. For existing services, Tor now learns the
1891 version by reading the key file. Closes ticket 27215.
1893 o Major features (relay, UI change):
1894 - Relays no longer run as exits by default. If the "ExitRelay"
1895 option is auto (or unset), and no exit policy is specified with
1896 ExitPolicy or ReducedExitPolicy, we now treat ExitRelay as 0.
1897 Previously in this case, we allowed exit traffic and logged a
1898 warning message. Closes ticket 21530. Patch by Neel Chauhan.
1899 - Tor now validates that the ContactInfo config option is valid UTF-
1900 8 when parsing torrc. Closes ticket 27428.
1902 o Major features (bootstrap):
1903 - Don't report directory progress until after a connection to a
1904 relay or bridge has succeeded. Previously, we'd report 80%
1905 progress based on cached directory information when we couldn't
1906 even connect to the network. Closes ticket 27169.
1908 o Major features (new code layout):
1909 - Nearly all of Tor's source code has been moved around into more
1910 logical places. The "common" directory is now divided into a set
1911 of libraries in "lib", and files in the "or" directory have been
1912 split into "core" (logic absolutely needed for onion routing),
1913 "feature" (independent modules in Tor), and "app" (to configure
1914 and invoke the rest of Tor). See doc/HACKING/CodeStructure.md for
1915 more information. Closes ticket 26481.
1917 This refactoring is not complete: although the libraries have been
1918 refactored to be acyclic, the main body of Tor is still too
1919 interconnected. We will attempt to improve this in the future.
1921 o Major features (onion services v3):
1922 - Implement onion service client authorization at the descriptor
1923 level: only authorized clients can decrypt a service's descriptor
1924 to find out how to contact it. A new torrc option was added to
1925 control this client side: ClientOnionAuthDir <path>. On the
1926 service side, if the "authorized_clients/" directory exists in the
1927 onion service directory path, client configurations are read from
1928 the files within. See the manpage for more details. Closes ticket
1929 27547. Patch done by Suphanat Chunhapanya (haxxpop).
1930 - Improve revision counter generation in next-gen onion services.
1931 Onion services can now scale by hosting multiple instances on
1932 different hosts without synchronization between them, which was
1933 previously impossible because descriptors would get rejected by
1934 HSDirs. Addresses ticket 25552.
1936 o Major features (portability, cryptography, experimental, TLS):
1937 - Tor now has the option to compile with the NSS library instead of
1938 OpenSSL. This feature is experimental, and we expect that bugs may
1939 remain. It is mainly intended for environments where Tor's
1940 performance is not CPU-bound, and where NSS is already known to be
1941 installed. To try it out, configure Tor with the --enable-nss
1942 flag. Closes tickets 26631, 26815, and 26816.
1944 If you are experimenting with this option and using an old cached
1945 consensus, Tor may fail to start. To solve this, delete your
1946 "cached-consensus" and "cached-microdesc-consensus" files,
1947 (if present), and restart Tor.
1949 o Major bugfixes (directory authority):
1950 - Actually check that the address we get from DirAuthority
1951 configuration line is valid IPv4. Explicitly disallow DirAuthority
1952 address to be a DNS hostname. Fixes bug 26488; bugfix
1955 o Major bugfixes (restart-in-process):
1956 - Fix a use-after-free error that could be caused by passing Tor an
1957 impossible set of options that would fail during options_act().
1958 Fixes bug 27708; bugfix on 0.3.3.1-alpha.
1960 o Minor features (admin tools):
1961 - Add a new --key-expiration option to print the expiration date of
1962 the signing cert in an ed25519_signing_cert file. Resolves
1965 o Minor features (build):
1966 - If you pass the "--enable-pic" option to configure, Tor will try
1967 to tell the compiler to build position-independent code suitable
1968 to link into a dynamic library. (The default remains -fPIE, for
1969 code suitable for a relocatable executable.) Closes ticket 23846.
1971 o Minor features (code correctness, testing):
1972 - Tor's build process now includes a "check-includes" make target to
1973 verify that no module of Tor relies on any headers from a higher-
1974 level module. We hope to use this feature over time to help
1975 refactor our codebase. Closes ticket 26447.
1977 o Minor features (code layout):
1978 - We have a new "lowest-level" error-handling API for use by code
1979 invoked from within the logging module. With this interface, the
1980 logging code is no longer at risk of calling into itself if a
1981 failure occurs while it is trying to log something. Closes
1984 o Minor features (compilation):
1985 - Tor's configure script now supports a --with-malloc= option to
1986 select your malloc implementation. Supported options are
1987 "tcmalloc", "jemalloc", "openbsd" (deprecated), and "system" (the
1988 default). Addresses part of ticket 20424. Based on a patch from
1991 o Minor features (config):
1992 - The "auto" keyword in torrc is now case-insensitive. Closes
1995 o Minor features (continuous integration):
1996 - Don't do a distcheck with --disable-module-dirauth in Travis.
1997 Implements ticket 27252.
1998 - Install libcap-dev and libseccomp2-dev so these optional
1999 dependencies get tested on Travis CI. Closes ticket 26560.
2000 - Only run one online rust build in Travis, to reduce network
2001 errors. Skip offline rust builds on Travis for Linux gcc, because
2002 they're redundant. Implements ticket 27252.
2003 - Skip gcc on OSX in Travis CI, because it's rarely used. Skip a
2004 duplicate hardening-off build in Travis on Tor 0.2.9. Skip gcc on
2005 Linux with default settings, because all the non-default builds
2006 use gcc on Linux. Implements ticket 27252.
2008 o Minor features (controller):
2009 - Emit CIRC_BW events as soon as we detect that we processed an
2010 invalid or otherwise dropped cell on a circuit. This allows
2011 vanguards and other controllers to react more quickly to dropped
2012 cells. Closes ticket 27678.
2013 - For purposes of CIRC_BW-based dropped cell detection, track half-
2014 closed stream ids, and allow their ENDs, SENDMEs, DATA and path
2015 bias check cells to arrive without counting it as dropped until
2016 either the END arrives, or the windows are empty. Closes
2018 - Implement a 'GETINFO md/all' controller command to enable getting
2019 all known microdescriptors. Closes ticket 8323.
2020 - The GETINFO command now support an "uptime" argument, to return
2021 Tor's uptime in seconds. Closes ticket 25132.
2023 o Minor features (denial-of-service avoidance):
2024 - Make our OOM handler aware of the DNS cache so that it doesn't
2025 fill up the memory. This check is important for our DoS mitigation
2026 subsystem. Closes ticket 18642. Patch by Neel Chauhan.
2028 o Minor features (development):
2029 - Tor's makefile now supports running the "clippy" Rust style tool
2030 on our Rust code. Closes ticket 22156.
2032 o Minor features (directory authority):
2033 - There is no longer an artificial upper limit on the length of
2034 bandwidth lines. Closes ticket 26223.
2035 - When a bandwidth file is used to obtain the bandwidth measurements,
2036 include this bandwidth file headers in the votes. Closes
2038 - Improved support for networks with only a single authority or a
2039 single fallback directory. Patch from Gabriel Somlo. Closes
2042 o Minor features (embedding API):
2043 - The Tor controller API now supports a function to launch Tor with
2044 a preconstructed owning controller FD, so that embedding
2045 applications don't need to manage controller ports and
2046 authentication. Closes ticket 24204.
2047 - The Tor controller API now has a function that returns the name
2048 and version of the backend implementing the API. Closes
2051 o Minor features (geoip):
2052 - Update geoip and geoip6 to the September 6 2018 Maxmind GeoLite2
2053 Country database. Closes ticket 27631.
2055 o Minor features (memory management):
2056 - Get Libevent to use the same memory allocator as Tor, by calling
2057 event_set_mem_functions() during initialization. Resolves
2060 o Minor features (memory usage):
2061 - When not using them, store legacy TAP public onion keys in DER-
2062 encoded format, rather than as expanded public keys. This should
2063 save several megabytes on typical clients. Closes ticket 27246.
2065 o Minor features (OpenSSL):
2066 - When possible, use RFC5869 HKDF implementation from OpenSSL rather
2067 than our own. Resolves ticket 19979.
2069 o Minor features (Rust, code quality):
2070 - Improve rust code quality in the rust protover implementation by
2071 making it more idiomatic. Includes changing an internal API to
2072 take &str instead of &String. Closes ticket 26492.
2074 o Minor features (testing):
2075 - Add scripts/test/chutney-git-bisect.sh, for bisecting using
2076 chutney. Implements ticket 27211.
2078 o Minor features (tor-resolve):
2079 - The tor-resolve utility can now be used with IPv6 SOCKS proxies.
2080 Side-effect of the refactoring for ticket 26526.
2082 o Minor features (UI):
2083 - Log each included configuration file or directory as we read it,
2084 to provide more visibility about where Tor is reading from. Patch
2085 from Unto Sten; closes ticket 27186.
2086 - Lower log level of "Scheduler type KIST has been enabled" to INFO.
2087 Closes ticket 26703.
2089 o Minor bugfixes (bootstrap):
2090 - Try harder to get descriptors in non-exit test networks, by using
2091 the mid weight for the third hop when there are no exits. Fixes
2092 bug 27237; bugfix on 0.2.6.2-alpha.
2094 o Minor bugfixes (C correctness):
2095 - Avoid casting smartlist index to int implicitly, as it may trigger
2096 a warning (-Wshorten-64-to-32). Fixes bug 26282; bugfix on
2097 0.2.3.13-alpha, 0.2.7.1-alpha and 0.2.1.1-alpha.
2098 - Use time_t for all values in
2099 predicted_ports_prediction_time_remaining(). Rework the code that
2100 computes difference between durations/timestamps. Fixes bug 27165;
2101 bugfix on 0.3.1.1-alpha.
2103 o Minor bugfixes (client, memory usage):
2104 - When not running as a directory cache, there is no need to store
2105 the text of the current consensus networkstatus in RAM.
2106 Previously, however, clients would store it anyway, at a cost of
2107 over 5 MB. Now, they do not. Fixes bug 27247; bugfix
2110 o Minor bugfixes (client, reachableaddresses):
2111 - Instead of adding a "reject *:*" line to ReachableAddresses when
2112 loading the configuration, add one to the policy after parsing it
2113 in parse_reachable_addresses(). This prevents extra "reject *.*"
2114 lines from accumulating on reloads. Fixes bug 20874; bugfix on
2115 0.1.1.5-alpha. Patch by Neel Chauhan.
2117 o Minor bugfixes (code quality):
2118 - Rename sandbox_getaddrinfo() and other functions to no longer
2119 misleadingly suggest that they are sandbox-only. Fixes bug 26525;
2120 bugfix on 0.2.7.1-alpha.
2122 o Minor bugfixes (configuration, Onion Services):
2123 - In rend_service_parse_port_config(), disallow any input to remain
2124 after address-port pair was parsed. This will catch address and
2125 port being whitespace-separated by mistake of the user. Fixes bug
2126 27044; bugfix on 0.2.9.10.
2128 o Minor bugfixes (continuous integration):
2129 - Stop reinstalling identical packages in our Windows CI. Fixes bug
2130 27464; bugfix on 0.3.4.1-alpha.
2132 o Minor bugfixes (controller):
2133 - Consider all routerinfo errors other than "not a server" to be
2134 transient for the purpose of "GETINFO exit-policy/*" controller
2135 request. Print stacktrace in the unlikely case of failing to
2136 recompute routerinfo digest. Fixes bug 27034; bugfix
2139 o Minor bugfixes (directory connection shutdown):
2140 - Avoid a double-close when shutting down a stalled directory
2141 connection. Fixes bug 26896; bugfix on 0.3.4.1-alpha.
2143 o Minor bugfixes (HTTP tunnel):
2144 - Fix a bug warning when closing an HTTP tunnel connection due to an
2145 HTTP request we couldn't handle. Fixes bug 26470; bugfix
2148 o Minor bugfixes (ipv6):
2149 - In addrs_in_same_network_family(), we choose the subnet size based
2150 on the IP version (IPv4 or IPv6). Previously, we chose a fixed
2151 subnet size of /16 for both IPv4 and IPv6 addresses. Fixes bug
2152 15518; bugfix on 0.2.3.1-alpha. Patch by Neel Chauhan.
2154 o Minor bugfixes (logging):
2155 - As a precaution, do an early return from log_addr_has_changed() if
2156 Tor is running as client. Also, log a stack trace for debugging as
2157 this function should only be called when Tor runs as server. Fixes
2158 bug 26892; bugfix on 0.1.1.9-alpha.
2159 - Refrain from mentioning bug 21018 in the logs, as it is already
2160 fixed. Fixes bug 25477; bugfix on 0.2.9.8.
2162 o Minor bugfixes (logging, documentation):
2163 - When SafeLogging is enabled, scrub IP address in
2164 channel_tls_process_netinfo_cell(). Also, add a note to manpage
2165 that scrubbing is not guaranteed on loglevels below Notice. Fixes
2166 bug 26882; bugfix on 0.2.4.10-alpha.
2168 o Minor bugfixes (netflow padding):
2169 - Ensure circuitmux queues are empty before scheduling or sending
2170 padding. Fixes bug 25505; bugfix on 0.3.1.1-alpha.
2172 o Minor bugfixes (onion service v2):
2173 - Log at level "info", not "warning", in the case that we do not
2174 have a consensus when a .onion request comes in. This can happen
2175 normally while bootstrapping. Fixes bug 27040; bugfix
2178 o Minor bugfixes (onion service v3):
2179 - When the onion service directory can't be created or has the wrong
2180 permissions, do not log a stack trace. Fixes bug 27335; bugfix
2183 o Minor bugfixes (OS compatibility):
2184 - Properly handle configuration changes that move a listener to/from
2185 wildcard IP address. If the first attempt to bind a socket fails,
2186 close the old listener and try binding the socket again. Fixes bug
2187 17873; bugfix on 0.0.8pre-1.
2189 o Minor bugfixes (performance)::
2190 - Rework node_is_a_configured_bridge() to no longer call
2191 node_get_all_orports(), which was performing too many memory
2192 allocations. Fixes bug 27224; bugfix on 0.2.3.9.
2194 o Minor bugfixes (relay statistics):
2195 - Update relay descriptor on bandwidth changes only when the uptime
2196 is smaller than 24h, in order to reduce the efficiency of guard
2197 discovery attacks. Fixes bug 24104; bugfix on 0.1.1.6-alpha.
2199 o Minor bugfixes (relays):
2200 - Consider the fact that we'll be making direct connections to our
2201 entry and guard nodes when computing the fraction of nodes that
2202 have their descriptors. Also, if we are using bridges and there is
2203 at least one bridge with a full descriptor, treat the fraction of
2204 guards available as 100%. Fixes bug 25886; bugfix on 0.2.4.10-alpha.
2205 Patch by Neel Chauhan.
2206 - Update the message logged on relays when DirCache is disabled.
2207 Since 0.3.3.5-rc, authorities require DirCache (V2Dir) for the
2208 Guard flag. Fixes bug 24312; bugfix on 0.3.3.5-rc.
2210 o Minor bugfixes (rust, protover):
2211 - Compute protover votes correctly in the rust version of the
2212 protover code. Previously, the protover rewrite in 24031 allowed
2213 repeated votes from the same voter for the same protocol version
2214 to be counted multiple times in protover_compute_vote(). Fixes bug
2215 27649; bugfix on 0.3.3.5-rc.
2216 - Reject protover names that contain invalid characters. Fixes bug
2217 27687; bugfix on 0.3.3.1-alpha.
2219 o Minor bugfixes (testing):
2220 - Fix two unit tests to work when HOME environment variable is not
2221 set. Fixes bug 27096; bugfix on 0.2.8.1-alpha.
2222 - If a unit test running in a subprocess exits abnormally or with a
2223 nonzero status code, treat the test as having failed, even if the
2224 test reported success. Without this fix, memory leaks don't cause
2225 the tests to fail, even with LeakSanitizer. Fixes bug 27658;
2226 bugfix on 0.2.2.4-alpha.
2227 - When logging a version mismatch in our openssl_version tests,
2228 report the actual offending version strings. Fixes bug 26152;
2229 bugfix on 0.2.9.1-alpha.
2230 - Fix forking tests on Windows when there is a space somewhere in
2231 the path. Fixes bug 26437; bugfix on 0.2.2.4-alpha.
2233 o Code simplification and refactoring:
2234 - 'updateFallbackDirs.py' now ignores the blacklist file, as it's not
2235 longer needed. Closes ticket 26502.
2236 - Include paths to header files within Tor are now qualified by
2237 directory within the top-level src directory.
2238 - Many structures have been removed from the centralized "or.h"
2239 header, and moved into their own headers. This will allow us to
2240 reduce the number of places in the code that rely on each
2241 structure's contents and layout. Closes ticket 26383.
2242 - Remove ATTR_NONNULL macro from codebase. Resolves ticket 26527.
2243 - Remove GetAdaptersAddresses_fn_t. The code that used it was
2244 removed as part of the 26481 refactor. Closes ticket 27467.
2245 - Rework Tor SOCKS server code to use Trunnel and benefit from
2246 autogenerated functions for parsing and generating SOCKS wire
2247 format. New implementation is cleaner, more maintainable and
2248 should be less prone to heartbleed-style vulnerabilities.
2249 Implements a significant fraction of ticket 3569.
2250 - Split sampled_guards_update_from_consensus() and
2251 select_entry_guard_for_circuit() into subfunctions. In
2252 entry_guards_update_primary() unite three smartlist enumerations
2253 into one and move smartlist comparison code out of the function.
2254 Closes ticket 21349.
2255 - Tor now assumes that you have standards-conformant stdint.h and
2256 inttypes.h headers when compiling. Closes ticket 26626.
2257 - Unify our bloom filter logic. Previously we had two copies of this
2258 code: one for routerlist filtering, and one for address set
2259 calculations. Closes ticket 26510.
2260 - Use the simpler strcmpstart() helper in
2261 rend_parse_v2_service_descriptor instead of strncmp(). Closes
2263 - Utility functions that can perform a DNS lookup are now wholly
2264 separated from those that can't, in separate headers and C
2265 modules. Closes ticket 26526.
2268 - Copy paragraph and URL to Tor's code of conduct document from
2269 CONTRIBUTING to new CODE_OF_CONDUCT file. Resolves ticket 26638.
2270 - Remove old instructions from INSTALL document. Closes ticket 26588.
2271 - Warn users that they should not include MyFamily line(s) in their
2272 torrc when running Tor bridge. Closes ticket 26908.
2275 - Tor no longer supports building with the dmalloc library. For
2276 debugging memory issues, we suggest using gperftools or msan
2277 instead. Closes ticket 26426.
2278 - Tor no longer attempts to run on Windows environments without the
2279 GetAdaptersAddresses() function. This function has existed since
2280 Windows XP, which is itself already older than we support.
2281 - Remove Tor2web functionality for version 2 onion services. The
2282 Tor2webMode and Tor2webRendezvousPoints options are now obsolete.
2283 (This feature was never shipped in vanilla Tor and it was only
2284 possible to use this feature by building the support at compile
2285 time. Tor2webMode is not implemented for version 3 onion services.)
2286 Closes ticket 26367.
2289 Changes in version 0.2.9.17 - 2018-09-10
2290 Tor 0.2.9.17 backports numerous bugfixes from later versions of Tor.
2292 o Minor features (compatibility, backport from 0.3.4.8):
2293 - Tell OpenSSL to maintain backward compatibility with previous
2294 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
2295 ciphers are disabled by default. Closes ticket 27344.
2297 o Minor features (continuous integration, backport from 0.3.4.7-rc):
2298 - Enable macOS builds in our Travis CI configuration. Closes
2300 - Install libcap-dev and libseccomp2-dev so these optional
2301 dependencies get tested on Travis CI. Closes ticket 26560.
2302 - Run asciidoc during Travis CI. Implements ticket 27087.
2303 - Use ccache in our Travis CI configuration. Closes ticket 26952.
2305 o Minor features (geoip):
2306 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
2307 Country database. Closes ticket 27089.
2309 o Minor bugfixes (compilation, backport from 0.3.4.6-rc):
2310 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
2311 tell the compiler not to include the system malloc implementation.
2312 Fixes bug 20424; bugfix on 0.2.0.20-rc.
2314 o Minor bugfixes (compilation, backport from 0.3.4.7-rc):
2315 - Silence a spurious compiler warning on the GetAdaptersAddresses
2316 function pointer cast. This issue is already fixed by 26481 in
2317 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
2318 bugfix on 0.2.3.11-alpha.
2319 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
2320 supported, and always fails. Some compilers warn about the
2321 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
2324 o Minor bugfixes (compilation, windows, backport from 0.3.4.7-rc):
2325 - Don't link or search for pthreads when building for Windows, even
2326 if we are using build environment (like mingw) that provides a
2327 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
2329 o Minor bugfixes (continuous integration, backport from 0.3.4.6-rc):
2330 - Skip a pair of unreliable key generation tests on Windows, until
2331 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
2332 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
2334 o Minor bugfixes (continuous integration, backport from 0.3.4.7-rc):
2335 - Pass the module flags to distcheck configure, and log the flags
2336 before running configure. (Backported to 0.2.9 and later as a
2337 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
2339 o Minor bugfixes (continuous integration, backport from 0.3.4.8):
2340 - When a Travis build fails, and showing a log fails, keep trying to
2341 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
2342 - When we use echo in Travis, don't pass a --flag as the first
2343 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
2345 o Minor bugfixes (directory authority, backport from 0.3.4.6-rc):
2346 - When voting for recommended versions, make sure that all of the
2347 versions are well-formed and parsable. Fixes bug 26485; bugfix
2350 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.4.7-rc):
2351 - Fix a bug in out sandboxing rules for the openat() syscall.
2352 Previously, no openat() call would be permitted, which would break
2353 filesystem operations on recent glibc versions. Fixes bug 25440;
2354 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
2356 o Minor bugfixes (onion services, backport from 0.3.4.8):
2357 - Silence a spurious compiler warning in
2358 rend_client_send_introduction(). Fixes bug 27463; bugfix
2361 o Minor bugfixes (single onion services, Tor2web, backport from 0.3.4.6-rc):
2362 - Log a protocol warning when single onion services or Tor2web clients
2363 fail to authenticate direct connections to relays.
2364 Fixes bug 26924; bugfix on 0.2.9.1-alpha.
2366 o Minor bugfixes (testing, backport from 0.3.4.6-rc):
2367 - Disable core dumps in test_bt.sh, to avoid failures in "make
2368 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
2370 o Minor bugfixes (testing, chutney, backport from 0.3.4.8):
2371 - Before running make test-network-all, delete old logs and test
2372 result files, to avoid spurious failures. Fixes bug 27295; bugfix
2375 o Minor bugfixes (testing, openssl compatibility, backport from 0.3.4.7-rc):
2376 - Our "tortls/cert_matches_key" unit test no longer relies on
2377 OpenSSL internals. Previously, it relied on unsupported OpenSSL
2378 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
2379 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
2381 o Minor bugfixes (Windows, compilation, backport from 0.3.4.7-rc):
2382 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
2383 27185; bugfix on 0.2.2.2-alpha.
2386 Changes in version 0.3.2.12 - 2018-09-10
2387 Tor 0.3.2.12 backport numerous fixes from later versions of Tor.
2389 o Minor features (compatibility, backport from 0.3.4.8):
2390 - Tell OpenSSL to maintain backward compatibility with previous
2391 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
2392 ciphers are disabled by default. Closes ticket 27344.
2394 o Minor features (continuous integration, backport from 0.3.4.7-rc):
2395 - Enable macOS builds in our Travis CI configuration. Closes
2397 - Install libcap-dev and libseccomp2-dev so these optional
2398 dependencies get tested on Travis CI. Closes ticket 26560.
2399 - Run asciidoc during Travis CI. Implements ticket 27087.
2400 - Use ccache in our Travis CI configuration. Closes ticket 26952.
2402 o Minor features (continuous integration, rust, backport from 0.3.4.7-rc):
2403 - Use cargo cache in our Travis CI configuration. Closes
2406 o Minor features (controller, backport from 0.3.4.6-rc):
2407 - The control port now exposes the list of HTTPTunnelPorts and
2408 ExtOrPorts via GETINFO net/listeners/httptunnel and
2409 net/listeners/extor respectively. Closes ticket 26647.
2411 o Minor features (directory authorities, backport from 0.3.4.7-rc):
2412 - Authorities no longer vote to make the subprotocol version
2413 "LinkAuth=1" a requirement: it is unsupportable with NSS, and
2414 hasn't been needed since Tor 0.3.0.1-alpha. Closes ticket 27286.
2416 o Minor features (geoip):
2417 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
2418 Country database. Closes ticket 27089.
2420 o Minor bugfixes (compilation, backport from 0.3.4.6-rc):
2421 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
2422 tell the compiler not to include the system malloc implementation.
2423 Fixes bug 20424; bugfix on 0.2.0.20-rc.
2424 - Don't try to use a pragma to temporarily disable the
2425 -Wunused-const-variable warning if the compiler doesn't support
2426 it. Fixes bug 26785; bugfix on 0.3.2.11.
2428 o Minor bugfixes (compilation, backport from 0.3.4.7-rc):
2429 - Silence a spurious compiler warning on the GetAdaptersAddresses
2430 function pointer cast. This issue is already fixed by 26481 in
2431 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
2432 bugfix on 0.2.3.11-alpha.
2433 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
2434 supported, and always fails. Some compilers warn about the
2435 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
2438 o Minor bugfixes (compilation, windows, backport from 0.3.4.7-rc):
2439 - Don't link or search for pthreads when building for Windows, even
2440 if we are using build environment (like mingw) that provides a
2441 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
2443 o Minor bugfixes (continuous integration, backport from 0.3.4.6-rc):
2444 - Skip a pair of unreliable key generation tests on Windows, until
2445 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
2446 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
2448 o Minor bugfixes (continuous integration, backport from 0.3.4.7-rc):
2449 - Build with zstd on macOS. Fixes bug 27090; bugfix on 0.3.1.5-alpha.
2450 - Pass the module flags to distcheck configure, and log the flags
2451 before running configure. (Backported to 0.2.9 and later as a
2452 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
2454 o Minor bugfixes (continuous integration, backport from 0.3.4.8):
2455 - When a Travis build fails, and showing a log fails, keep trying to
2456 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
2457 - When we use echo in Travis, don't pass a --flag as the first
2458 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
2460 o Minor bugfixes (directory authority, backport from 0.3.4.6-rc):
2461 - When voting for recommended versions, make sure that all of the
2462 versions are well-formed and parsable. Fixes bug 26485; bugfix
2465 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.4.7-rc):
2466 - Fix a bug in out sandboxing rules for the openat() syscall.
2467 Previously, no openat() call would be permitted, which would break
2468 filesystem operations on recent glibc versions. Fixes bug 25440;
2469 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
2471 o Minor bugfixes (logging, backport from 0.3.4.6-rc):
2472 - Improve the log message when connection initiators fail to
2473 authenticate direct connections to relays. Fixes bug 26927; bugfix
2476 o Minor bugfixes (onion services, backport from 0.3.4.7-rc):
2477 - Fix bug that causes services to not ever rotate their descriptors
2478 if they were getting SIGHUPed often. Fixes bug 26932; bugfix
2481 o Minor bugfixes (onion services, backport from 0.3.4.8):
2482 - Silence a spurious compiler warning in
2483 rend_client_send_introduction(). Fixes bug 27463; bugfix
2486 o Minor bugfixes (rust, backport from 0.3.4.7-rc):
2487 - Backport test_rust.sh from master. Fixes bug 26497; bugfix
2489 - Consistently use ../../.. as a fallback for $abs_top_srcdir in
2490 test_rust.sh. Fixes bug 27093; bugfix on 0.3.4.3-alpha.
2491 - Stop setting $CARGO_HOME. cargo will use the user's $CARGO_HOME, or
2492 $HOME/.cargo by default. Fixes bug 26497; bugfix on 0.3.1.5-alpha.
2494 o Minor bugfixes (single onion services, Tor2web, backport from 0.3.4.6-rc):
2495 - Log a protocol warning when single onion services or Tor2web clients
2496 fail to authenticate direct connections to relays.
2497 Fixes bug 26924; bugfix on 0.2.9.1-alpha.
2499 o Minor bugfixes (testing, backport from 0.3.4.6-rc):
2500 - Disable core dumps in test_bt.sh, to avoid failures in "make
2501 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
2503 o Minor bugfixes (testing, chutney, backport from 0.3.4.8):
2504 - When running make test-network-all, use the mixed+hs-v2 network.
2505 (A previous fix to chutney removed v3 onion services from the
2506 mixed+hs-v23 network, so seeing "mixed+hs-v23" in tests is
2507 confusing.) Fixes bug 27345; bugfix on 0.3.2.1-alpha.
2508 - Before running make test-network-all, delete old logs and test
2509 result files, to avoid spurious failures. Fixes bug 27295; bugfix
2512 o Minor bugfixes (testing, openssl compatibility):
2513 - Our "tortls/cert_matches_key" unit test no longer relies on OpenSSL
2514 internals. Previously, it relied on unsupported OpenSSL behavior in
2515 a way that caused it to crash with OpenSSL 1.0.2p. Fixes bug 27226;
2516 bugfix on 0.2.5.1-alpha.
2518 o Minor bugfixes (testing, openssl compatibility, backport from 0.3.4.7-rc):
2519 - Our "tortls/cert_matches_key" unit test no longer relies on
2520 OpenSSL internals. Previously, it relied on unsupported OpenSSL
2521 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
2522 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
2524 o Minor bugfixes (Windows, compilation, backport from 0.3.4.7-rc):
2525 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
2526 27185; bugfix on 0.2.2.2-alpha.
2529 Changes in version 0.3.3.10 - 2018-09-10
2530 Tor 0.3.3.10 backports numerous fixes from later versions of Tor.
2532 o Minor features (bug workaround, backport from 0.3.4.7-rc):
2533 - Compile correctly on systems that provide the C11 stdatomic.h
2534 header, but where C11 atomic functions don't actually compile.
2535 Closes ticket 26779; workaround for Debian issue 903709.
2537 o Minor features (compatibility, backport from 0.3.4.8):
2538 - Tell OpenSSL to maintain backward compatibility with previous
2539 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
2540 ciphers are disabled by default. Closes ticket 27344.
2542 o Minor features (continuous integration, backport from 0.3.4.7-rc):
2543 - Backport Travis rust distcheck to 0.3.3. Closes ticket 24629.
2544 - Enable macOS builds in our Travis CI configuration. Closes
2546 - Install libcap-dev and libseccomp2-dev so these optional
2547 dependencies get tested on Travis CI. Closes ticket 26560.
2548 - Run asciidoc during Travis CI. Implements ticket 27087.
2549 - Use ccache in our Travis CI configuration. Closes ticket 26952.
2551 o Minor features (continuous integration, rust, backport from 0.3.4.7-rc):
2552 - Use cargo cache in our Travis CI configuration. Closes
2555 o Minor features (controller, backport from 0.3.4.6-rc):
2556 - The control port now exposes the list of HTTPTunnelPorts and
2557 ExtOrPorts via GETINFO net/listeners/httptunnel and
2558 net/listeners/extor respectively. Closes ticket 26647.
2560 o Minor features (directory authorities, backport from 0.3.4.7-rc):
2561 - Authorities no longer vote to make the subprotocol version
2562 "LinkAuth=1" a requirement: it is unsupportable with NSS, and
2563 hasn't been needed since Tor 0.3.0.1-alpha. Closes ticket 27286.
2565 o Minor features (geoip):
2566 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
2567 Country database. Closes ticket 27089.
2569 o Minor bugfixes (compilation, backport from 0.3.4.6-rc):
2570 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
2571 tell the compiler not to include the system malloc implementation.
2572 Fixes bug 20424; bugfix on 0.2.0.20-rc.
2573 - Don't try to use a pragma to temporarily disable the
2574 -Wunused-const-variable warning if the compiler doesn't support
2575 it. Fixes bug 26785; bugfix on 0.3.2.11.
2577 o Minor bugfixes (compilation, backport from 0.3.4.7-rc):
2578 - Silence a spurious compiler warning on the GetAdaptersAddresses
2579 function pointer cast. This issue is already fixed by 26481 in
2580 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
2581 bugfix on 0.2.3.11-alpha.
2582 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
2583 supported, and always fails. Some compilers warn about the
2584 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
2587 o Minor bugfixes (compilation, windows, backport from 0.3.4.7-rc):
2588 - Don't link or search for pthreads when building for Windows, even
2589 if we are using build environment (like mingw) that provides a
2590 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
2592 o Minor bugfixes (continuous integration, backport from 0.3.4.6-rc):
2593 - Skip a pair of unreliable key generation tests on Windows, until
2594 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
2595 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
2597 o Minor bugfixes (continuous integration, backport from 0.3.4.7-rc):
2598 - Build with zstd on macOS. Fixes bug 27090; bugfix on 0.3.1.5-alpha.
2599 - Pass the module flags to distcheck configure, and log the flags
2600 before running configure. (Backported to 0.2.9 and later as a
2601 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
2603 o Minor bugfixes (continuous integration, backport from 0.3.4.8):
2604 - When a Travis build fails, and showing a log fails, keep trying to
2605 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
2606 - When we use echo in Travis, don't pass a --flag as the first
2607 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
2609 o Minor bugfixes (directory authority, backport from 0.3.4.6-rc):
2610 - When voting for recommended versions, make sure that all of the
2611 versions are well-formed and parsable. Fixes bug 26485; bugfix
2614 o Minor bugfixes (in-process restart, backport from 0.3.4.7-rc):
2615 - Always call tor_free_all() when leaving tor_run_main(). When we
2616 did not, restarting tor in-process would cause an assertion
2617 failure. Fixes bug 26948; bugfix on 0.3.3.1-alpha.
2619 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.4.7-rc):
2620 - Fix a bug in our sandboxing rules for the openat() syscall.
2621 Previously, no openat() call would be permitted, which would break
2622 filesystem operations on recent glibc versions. Fixes bug 25440;
2623 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
2625 o Minor bugfixes (logging, backport from 0.3.4.6-rc):
2626 - Improve the log message when connection initiators fail to
2627 authenticate direct connections to relays. Fixes bug 26927; bugfix
2630 o Minor bugfixes (onion services, backport from 0.3.4.7-rc):
2631 - Fix bug that causes services to not ever rotate their descriptors
2632 if they were getting SIGHUPed often. Fixes bug 26932; bugfix
2635 o Minor bugfixes (onion services, backport from 0.3.4.8):
2636 - Silence a spurious compiler warning in
2637 rend_client_send_introduction(). Fixes bug 27463; bugfix
2640 o Minor bugfixes (portability, backport from 0.3.4.6-rc):
2641 - Work around two different bugs in the OS X 10.10 and later SDKs
2642 that would prevent us from successfully targeting earlier versions
2643 of OS X. Fixes bug 26876; bugfix on 0.3.3.1-alpha.
2645 o Minor bugfixes (portability, backport from 0.3.4.7-rc):
2646 - Fix compilation of the unit tests on GNU/Hurd, which does not
2647 define PATH_MAX. Fixes bug 26873; bugfix on 0.3.3.1-alpha. Patch
2650 o Minor bugfixes (rust, backport from 0.3.4.7-rc):
2651 - Backport test_rust.sh from master. Fixes bug 26497; bugfix
2653 - Consistently use ../../.. as a fallback for $abs_top_srcdir in
2654 test_rust.sh. Fixes bug 27093; bugfix on 0.3.4.3-alpha.
2655 - Protover parsing was accepting the presence of whitespace in
2656 version strings, which the C implementation would choke on, e.g.
2657 "Desc=1\t,2". Fixes bug 27177; bugfix on 0.3.3.5-rc.
2658 - Protover parsing was ignoring a 2nd hyphen and everything after
2659 it, accepting entries like "Link=1-5-foo". Fixes bug 27164; bugfix
2661 - Stop setting $CARGO_HOME. cargo will use the user's $CARGO_HOME, or
2662 $HOME/.cargo by default. Fixes bug 26497; bugfix on 0.3.1.5-alpha.
2663 - cd to ${abs_top_builddir}/src/rust before running cargo in
2664 src/test/test_rust.sh. This makes the working directory consistent
2665 between builds and tests. Fixes bug 26497; bugfix on 0.3.3.2-alpha.
2667 o Minor bugfixes (single onion services, Tor2web, backport from 0.3.4.6-rc):
2668 - Log a protocol warning when single onion services or Tor2web clients
2669 fail to authenticate direct connections to relays.
2670 Fixes bug 26924; bugfix on 0.2.9.1-alpha.
2672 o Minor bugfixes (testing, backport from 0.3.4.6-rc):
2673 - Disable core dumps in test_bt.sh, to avoid failures in "make
2674 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
2676 o Minor bugfixes (testing, chutney, backport from 0.3.4.8):
2677 - When running make test-network-all, use the mixed+hs-v2 network.
2678 (A previous fix to chutney removed v3 onion services from the
2679 mixed+hs-v23 network, so seeing "mixed+hs-v23" in tests is
2680 confusing.) Fixes bug 27345; bugfix on 0.3.2.1-alpha.
2681 - Before running make test-network-all, delete old logs and test
2682 result files, to avoid spurious failures. Fixes bug 27295; bugfix
2685 o Minor bugfixes (testing, openssl compatibility, backport from 0.3.4.7-rc):
2686 - Our "tortls/cert_matches_key" unit test no longer relies on
2687 OpenSSL internals. Previously, it relied on unsupported OpenSSL
2688 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
2689 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
2691 o Minor bugfixes (v3 onion services, backport from 0.3.4.6-rc):
2692 - Stop sending ed25519 link specifiers in v3 onion service introduce
2693 cells and descriptors, when the rendezvous or introduction point
2694 doesn't support ed25519 link authentication. Fixes bug 26627;
2695 bugfix on 0.3.2.4-alpha.
2697 o Minor bugfixes (Windows, compilation, backport from 0.3.4.7-rc):
2698 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
2699 27185; bugfix on 0.2.2.2-alpha.
2702 Changes in version 0.3.4.8 - 2018-09-10
2703 Tor 0.3.4.8 is the first stable release in its series; it includes
2704 compilation and portability fixes.
2706 The Tor 0.3.4 series includes improvements for running Tor in
2707 low-power and embedded environments, which should help performance in
2708 general. We've begun work on better modularity, and included preliminary
2709 changes on the directory authority side to accommodate a new bandwidth
2710 measurement system. We've also integrated more continuous-integration
2711 systems into our development process, and made corresponding changes to
2712 Tor's testing infrastructure. Finally, we've continued to refine
2713 our anti-denial-of-service code.
2715 Below are the changes since 0.3.4.7-rc. For a complete list of changes
2716 since 0.3.3.9, see the ReleaseNotes file.
2718 o Minor features (compatibility):
2719 - Tell OpenSSL to maintain backward compatibility with previous
2720 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
2721 ciphers are disabled by default. Closes ticket 27344.
2723 o Minor features (continuous integration):
2724 - Log the compiler path and version during Appveyor builds.
2725 Implements ticket 27449.
2726 - Show config.log and test-suite.log after failed Appveyor builds.
2727 Also upload the zipped full logs as a build artifact. Implements
2730 o Minor bugfixes (compilation):
2731 - Silence a spurious compiler warning on the GetAdaptersAddresses
2732 function pointer cast. This issue is already fixed by 26481 in
2733 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
2734 bugfix on 0.2.3.11-alpha.
2735 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
2736 supported, and always fails. Some compilers warn about the
2737 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
2740 o Minor bugfixes (continuous integration):
2741 - Disable gcc hardening in Appveyor Windows 64-bit builds. As of
2742 August 29 2018, Appveyor images come with gcc 8.2.0 by default.
2743 Executables compiled for 64-bit Windows with this version of gcc
2744 crash when Tor's --enable-gcc-hardening flag is set. Fixes bug
2745 27460; bugfix on 0.3.4.1-alpha.
2746 - When a Travis build fails, and showing a log fails, keep trying to
2747 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
2748 - When we use echo in Travis, don't pass a --flag as the first
2749 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
2751 o Minor bugfixes (onion services):
2752 - Silence a spurious compiler warning in
2753 rend_client_send_introduction(). Fixes bug 27463; bugfix
2756 o Minor bugfixes (testing, chutney):
2757 - When running make test-network-all, use the mixed+hs-v2 network.
2758 (A previous fix to chutney removed v3 onion services from the
2759 mixed+hs-v23 network, so seeing "mixed+hs-v23" in tests is
2760 confusing.) Fixes bug 27345; bugfix on 0.3.2.1-alpha.
2761 - Before running make test-network-all, delete old logs and test
2762 result files, to avoid spurious failures. Fixes bug 27295; bugfix
2765 Changes in version 0.3.4.7-rc - 2018-08-24
2766 Tor 0.3.4.7-rc fixes several small compilation, portability, and
2767 correctness issues in previous versions of Tor. This version is a
2768 release candidate: if no serious bugs are found, we expect that the
2769 stable 0.3.4 release will be (almost) the same as this release.
2771 o Minor features (bug workaround):
2772 - Compile correctly on systems that provide the C11 stdatomic.h
2773 header, but where C11 atomic functions don't actually compile.
2774 Closes ticket 26779; workaround for Debian issue 903709.
2776 o Minor features (continuous integration):
2777 - Backport Travis rust distcheck to 0.3.3. Closes ticket 24629.
2778 - Enable macOS builds in our Travis CI configuration. Closes
2780 - Install libcap-dev and libseccomp2-dev so these optional
2781 dependencies get tested on Travis CI. Closes ticket 26560.
2782 - Only post Appveyor IRC notifications when the build fails.
2783 Implements ticket 27275.
2784 - Run asciidoc during Travis CI. Implements ticket 27087.
2785 - Use ccache in our Travis CI configuration. Closes ticket 26952.
2787 o Minor features (continuous integration, rust):
2788 - Use cargo cache in our Travis CI configuration. Closes
2791 o Minor features (directory authorities):
2792 - Authorities no longer vote to make the subprotocol version
2793 "LinkAuth=1" a requirement: it is unsupportable with NSS, and
2794 hasn't been needed since Tor 0.3.0.1-alpha. Closes ticket 27286.
2796 o Minor features (geoip):
2797 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
2798 Country database. Closes ticket 27089.
2800 o Minor bugfixes (compilation, windows):
2801 - Don't link or search for pthreads when building for Windows, even
2802 if we are using build environment (like mingw) that provides a
2803 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
2805 o Minor bugfixes (continuous integration):
2806 - Improve Appveyor CI IRC logging. Generate correct branches and
2807 URLs for pull requests and tags. Use unambiguous short commits.
2808 Fixes bug 26979; bugfix on master.
2809 - Build with zstd on macOS. Fixes bug 27090; bugfix on 0.3.1.5-alpha.
2810 - Pass the module flags to distcheck configure, and log the flags
2811 before running configure. (Backported to 0.2.9 and later as a
2812 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
2814 o Minor bugfixes (in-process restart):
2815 - Always call tor_free_all() when leaving tor_run_main(). When we
2816 did not, restarting tor in-process would cause an assertion
2817 failure. Fixes bug 26948; bugfix on 0.3.3.1-alpha.
2819 o Minor bugfixes (linux seccomp2 sandbox):
2820 - Fix a bug in out sandboxing rules for the openat() syscall.
2821 Previously, no openat() call would be permitted, which would break
2822 filesystem operations on recent glibc versions. Fixes bug 25440;
2823 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
2825 o Minor bugfixes (onion services):
2826 - Fix bug that causes services to not ever rotate their descriptors
2827 if they were getting SIGHUPed often. Fixes bug 26932; bugfix
2830 o Minor bugfixes (portability):
2831 - Fix compilation of the unit tests on GNU/Hurd, which does not
2832 define PATH_MAX. Fixes bug 26873; bugfix on 0.3.3.1-alpha. Patch
2835 o Minor bugfixes (rust):
2836 - Backport test_rust.sh from master. Fixes bug 26497; bugfix
2838 - Consistently use ../../.. as a fallback for $abs_top_srcdir in
2839 test_rust.sh. Fixes bug 27093; bugfix on 0.3.4.3-alpha.
2840 - Protover parsing was accepting the presence of whitespace in
2841 version strings, which the C implementation would choke on, e.g.
2842 "Desc=1\t,2". Fixes bug 27177; bugfix on 0.3.3.5-rc.
2843 - Protover parsing was ignoring a 2nd hyphen and everything after
2844 it, accepting entries like "Link=1-5-foo". Fixes bug 27164; bugfix
2846 - Stop setting $CARGO_HOME. cargo will use the user's $CARGO_HOME, or
2847 $HOME/.cargo by default. Fixes bug 26497; bugfix on 0.3.1.5-alpha.
2848 - cd to ${abs_top_builddir}/src/rust before running cargo in
2849 src/test/test_rust.sh. This makes the working directory consistent
2850 between builds and tests. Fixes bug 26497; bugfix on 0.3.3.2-alpha.
2852 o Minor bugfixes (testing, bootstrap):
2853 - When calculating bootstrap progress, check exit policies and the
2854 exit flag. Previously, Tor would only check the exit flag, which
2855 caused race conditions in small and fast networks like chutney.
2856 Fixes bug 27236; bugfix on 0.2.6.3-alpha.
2858 o Minor bugfixes (testing, openssl compatibility):
2859 - Our "tortls/cert_matches_key" unit test no longer relies on
2860 OpenSSL internals. Previously, it relied on unsupported OpenSSL
2861 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
2862 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
2864 o Minor bugfixes (Windows, compilation):
2865 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
2866 27185; bugfix on 0.2.2.2-alpha.
2869 Changes in version 0.3.4.6-rc - 2018-08-06
2870 Tor 0.3.4.6-rc fixes several small compilation, portability, and
2871 correctness issues in previous versions of Tor. This version is a
2872 release candidate: if no serious bugs are found, we expect that the
2873 stable 0.3.4 release will be (almost) the same as this release.
2875 o Major bugfixes (event scheduler):
2876 - When we enable a periodic event, schedule it in the event loop
2877 rather than running it immediately. Previously, we would re-run
2878 periodic events immediately in the middle of (for example)
2879 changing our options, with unpredictable effects. Fixes bug 27003;
2880 bugfix on 0.3.4.1-alpha.
2882 o Minor features (compilation):
2883 - When building Tor, prefer to use Python 3 over Python 2, and more
2884 recent (contemplated) versions over older ones. Closes
2886 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
2887 tell the compiler not to include the system malloc implementation.
2888 Fixes bug 20424; bugfix on 0.2.0.20-rc.
2889 - Don't try to use a pragma to temporarily disable the
2890 -Wunused-const-variable warning if the compiler doesn't support
2891 it. Fixes bug 26785; bugfix on 0.3.2.11.
2893 o Minor bugfixes (continuous integration):
2894 - Skip a pair of unreliable key generation tests on Windows, until
2895 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
2896 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
2898 o Minor features (controller):
2899 - The control port now exposes the list of HTTPTunnelPorts and
2900 ExtOrPorts via GETINFO net/listeners/httptunnel and
2901 net/listeners/extor respectively. Closes ticket 26647.
2903 o Minor bugfixes (directory authority):
2904 - When voting for recommended versions, make sure that all of the
2905 versions are well-formed and parsable. Fixes bug 26485; bugfix
2908 o Minor features (geoip):
2909 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
2910 Country database. Closes ticket 26674.
2912 o Minor features (Rust, portability):
2913 - Rust cross-compilation is now supported. Closes ticket 25895.
2915 o Minor bugfixes (compilation):
2916 - Update build system so that tor builds again with --disable-unittests
2917 after recent refactoring. Fixes bug 26789; bugfix on 0.3.4.3-alpha.
2918 - Fix a compilation warning on some versions of GCC when building
2919 code that calls routerinfo_get_my_routerinfo() twice, assuming
2920 that the second call will succeed if the first one did. Fixes bug
2921 26269; bugfix on 0.2.8.2-alpha.
2923 o Minor bugfixes (controller):
2924 - Report the port correctly when a port is configured to bind to
2925 "auto". Fixes bug 26568; bugfix on 0.3.4.1-alpha.
2926 - Parse the "HSADDRESS=" parameter in HSPOST commands properly.
2927 Previously, it was misparsed and ignored. Fixes bug 26523; bugfix
2928 on 0.3.3.1-alpha. Patch by "akwizgran".
2930 o Minor bugfixes (correctness, flow control):
2931 - Upon receiving a stream-level SENDME cell, verify that our window
2932 has not grown too large. Fixes bug 26214; bugfix on svn
2935 o Minor bugfixes (memory, correctness):
2936 - Fix a number of small memory leaks identified by coverity. Fixes
2937 bug 26467; bugfix on numerous Tor versions.
2939 o Minor bugfixes (logging):
2940 - Improve the log message when connection initiators fail to
2941 authenticate direct connections to relays. Fixes bug 26927; bugfix
2944 o Minor bugfixes (portability):
2945 - Avoid a compilation error in test_bwmgt.c on Solaris 10. Fixes bug
2946 26994; bugfix on 0.3.4.1-alpha.
2947 - Work around two different bugs in the OS X 10.10 and later SDKs
2948 that would prevent us from successfully targeting earlier versions
2949 of OS X. Fixes bug 26876; bugfix on 0.3.3.1-alpha.
2951 o Minor bugfixes (single onion services, Tor2web):
2952 - Log a protocol warning when single onion services or Tor2web
2953 clients fail to authenticate direct connections to relays. Fixes
2954 bug 26924; bugfix on 0.2.9.1-alpha.
2956 o Minor bugfixes (testing):
2957 - Disable core dumps in test_bt.sh, to avoid failures in "make
2958 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
2960 o Minor bugfixes (testing, compatibility):
2961 - When running the ntor_ref.py and hs_ntor_ref.py tests, make sure
2962 only to pass strings (rather than "bytes" objects) to the Python
2963 subprocess module. Python 3 on Windows seems to require this.
2964 Fixes bug 26535; bugfix on 0.2.5.5-alpha (for ntor_ref.py) and
2965 0.3.1.1-alpha (for hs_ntor_ref.py).
2967 o Minor bugfixes (v3 onion services):
2968 - Stop sending ed25519 link specifiers in v3 onion service introduce
2969 cells and descriptors, when the rendezvous or introduction point
2970 doesn't support ed25519 link authentication. Fixes bug 26627;
2971 bugfix on 0.3.2.4-alpha.
2974 Changes in version 0.3.4.5-rc - 2018-07-13
2975 Tor 0.3.4.5-rc moves to a new bridge authority, meaning people running
2976 bridge relays should upgrade.
2978 o Directory authority changes:
2979 - The "Bifroest" bridge authority has been retired; the new bridge
2980 authority is "Serge", and it is operated by George from the
2981 TorBSD project. Closes ticket 26771.
2984 Changes in version 0.3.3.9 - 2018-07-13
2985 Tor 0.3.3.9 moves to a new bridge authority, meaning people running
2986 bridge relays should upgrade.
2988 o Directory authority changes:
2989 - The "Bifroest" bridge authority has been retired; the new bridge
2990 authority is "Serge", and it is operated by George from the
2991 TorBSD project. Closes ticket 26771.
2994 Changes in version 0.3.2.11 - 2018-07-13
2995 Tor 0.3.2.11 moves to a new bridge authority, meaning people running
2996 bridge relays should upgrade. We also take this opportunity to backport
2999 o Directory authority changes:
3000 - The "Bifroest" bridge authority has been retired; the new bridge
3001 authority is "Serge", and it is operated by George from the
3002 TorBSD project. Closes ticket 26771.
3004 o Directory authority changes (backport from 0.3.3.7):
3005 - Add an IPv6 address for the "dannenberg" directory authority.
3006 Closes ticket 26343.
3008 o Major bugfixes (directory authorities, backport from 0.3.4.1-alpha):
3009 - When directory authorities read a zero-byte bandwidth file, they
3010 would previously log a warning with the contents of an
3011 uninitialised buffer. They now log a warning about the empty file
3012 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
3014 o Major bugfixes (onion service, backport from 0.3.4.1-alpha):
3015 - Correctly detect when onion services get disabled after HUP. Fixes
3016 bug 25761; bugfix on 0.3.2.1.
3018 o Minor features (sandbox, backport from 0.3.3.4-alpha):
3019 - Explicitly permit the poll() system call when the Linux
3020 seccomp2-based sandbox is enabled: apparently, some versions of
3021 libc use poll() when calling getpwnam(). Closes ticket 25313.
3023 o Minor feature (continuous integration, backport from 0.3.3.5-rc):
3024 - Update the Travis CI configuration to use the stable Rust channel,
3025 now that we have decided to require that. Closes ticket 25714.
3027 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
3028 - Our .travis.yml configuration now includes support for testing the
3029 results of "make distcheck". (It's not uncommon for "make check"
3030 to pass but "make distcheck" to fail.) Closes ticket 25814.
3031 - Our Travis CI configuration now integrates with the Coveralls
3032 coverage analysis tool. Closes ticket 25818.
3034 o Minor features (relay, diagnostic, backport from 0.3.4.3-alpha):
3035 - Add several checks to detect whether Tor relays are uploading
3036 their descriptors without specifying why they regenerated them.
3037 Diagnostic for ticket 25686.
3039 o Minor features (compilation, backport from 0.3.4.4-rc):
3040 - When building Tor, prefer to use Python 3 over Python 2, and more
3041 recent (contemplated) versions over older ones. Closes
3044 o Minor features (geoip):
3045 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
3046 Country database. Closes ticket 26674.
3048 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
3049 - Upon receiving a malformed connected cell, stop processing the
3050 cell immediately. Previously we would mark the connection for
3051 close, but continue processing the cell as if the connection were
3052 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
3054 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
3055 - Allow the nanosleep() system call, which glibc uses to implement
3056 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
3058 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
3059 - When running the hs_ntor_ref.py test, make sure only to pass
3060 strings (rather than "bytes" objects) to the Python subprocess
3061 module. Python 3 on Windows seems to require this. Fixes bug
3062 26535; bugfix on 0.3.1.1-alpha.
3063 - When running the ntor_ref.py test, make sure only to pass strings
3064 (rather than "bytes" objects) to the Python subprocess module.
3065 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
3068 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
3069 - Work around a change in OpenSSL 1.1.1 where return values that
3070 would previously indicate "no password" now indicate an empty
3071 password. Without this workaround, Tor instances running with
3072 OpenSSL 1.1.1 would accept descriptors that other Tor instances
3073 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
3075 o Minor bugfixes (documentation, backport from 0.3.3.5-rc):
3076 - Document that the PerConnBW{Rate,Burst} options will fall back to
3077 their corresponding consensus parameters only if those parameters
3078 are set. Previously we had claimed that these values would always
3079 be set in the consensus. Fixes bug 25296; bugfix on 0.2.2.7-alpha.
3081 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
3082 - Fix a compilation warning on some versions of GCC when building
3083 code that calls routerinfo_get_my_routerinfo() twice, assuming
3084 that the second call will succeed if the first one did. Fixes bug
3085 26269; bugfix on 0.2.8.2-alpha.
3087 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
3088 - Don't consider Tor running as a client if the ControlPort is open,
3089 but no actual client ports are open. Fixes bug 26062; bugfix
3092 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
3093 - Prevent a possible out-of-bounds smartlist read in
3094 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
3096 o Minor bugfixes (C correctness, backport from 0.3.3.4-alpha):
3097 - Fix a very unlikely (impossible, we believe) null pointer
3098 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
3099 Coverity; this is CID 1430932.
3101 o Minor bugfixes (onion service, backport from 0.3.4.1-alpha):
3102 - Fix a memory leak when a v3 onion service is configured and gets a
3103 SIGHUP signal. Fixes bug 25901; bugfix on 0.3.2.1-alpha.
3104 - When parsing the descriptor signature, look for the token plus an
3105 extra white-space at the end. This is more correct but also will
3106 allow us to support new fields that might start with "signature".
3107 Fixes bug 26069; bugfix on 0.3.0.1-alpha.
3109 o Minor bugfixes (relay, backport from 0.3.4.3-alpha):
3110 - Relays now correctly block attempts to re-extend to the previous
3111 relay by Ed25519 identity. Previously they would warn in this
3112 case, but not actually reject the attempt. Fixes bug 26158; bugfix
3115 o Minor bugfixes (relay, crash, backport from 0.3.4.1-alpha):
3116 - Avoid a crash when running with DirPort set but ORPort turned off.
3117 Fixes a case of bug 23693; bugfix on 0.3.1.1-alpha.
3119 o Minor bugfixes (compilation, backport from 0.3.4.2-alpha):
3120 - Silence unused-const-variable warnings in zstd.h with some GCC
3121 versions. Fixes bug 26272; bugfix on 0.3.1.1-alpha.
3123 o Minor bugfixes (testing, backport from 0.3.3.4-alpha):
3124 - Avoid intermittent test failures due to a test that had relied on
3125 onion service introduction point creation finishing within 5
3126 seconds of real clock time. Fixes bug 25450; bugfix
3129 o Minor bugfixes (compilation, backport from 0.3.3.4-alpha):
3130 - Fix a C99 compliance issue in our configuration script that caused
3131 compilation issues when compiling Tor with certain versions of
3132 xtools. Fixes bug 25474; bugfix on 0.3.2.5-alpha.
3134 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
3135 - Fix a number of small memory leaks identified by coverity. Fixes
3136 bug 26467; bugfix on numerous Tor versions.
3138 o Code simplification and refactoring (backport from 0.3.3.5-rc):
3139 - Move the list of default directory authorities to its own file.
3140 Closes ticket 24854. Patch by "beastr0".
3143 Changes in version 0.2.9.16 - 2018-07-13
3144 Tor 0.2.9.16 moves to a new bridge authority, meaning people running
3145 bridge relays should upgrade. We also take this opportunity to backport
3148 o Directory authority changes:
3149 - The "Bifroest" bridge authority has been retired; the new bridge
3150 authority is "Serge", and it is operated by George from the
3151 TorBSD project. Closes ticket 26771.
3153 o Directory authority changes (backport from 0.3.3.7):
3154 - Add an IPv6 address for the "dannenberg" directory authority.
3155 Closes ticket 26343.
3157 o Major bugfixes (directory authorities, backport from 0.3.4.1-alpha):
3158 - When directory authorities read a zero-byte bandwidth file, they
3159 would previously log a warning with the contents of an
3160 uninitialised buffer. They now log a warning about the empty file
3161 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
3163 o Minor features (sandbox, backport from 0.3.3.4-alpha):
3164 - Explicitly permit the poll() system call when the Linux
3165 seccomp2-based sandbox is enabled: apparently, some versions of
3166 libc use poll() when calling getpwnam(). Closes ticket 25313.
3168 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
3169 - Our .travis.yml configuration now includes support for testing the
3170 results of "make distcheck". (It's not uncommon for "make check"
3171 to pass but "make distcheck" to fail.) Closes ticket 25814.
3172 - Our Travis CI configuration now integrates with the Coveralls
3173 coverage analysis tool. Closes ticket 25818.
3175 o Minor features (compilation, backport from 0.3.4.4-rc):
3176 - When building Tor, prefer to use Python 3 over Python 2, and more
3177 recent (contemplated) versions over older ones. Closes
3180 o Minor features (geoip):
3181 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
3182 Country database. Closes ticket 26674.
3184 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
3185 - Upon receiving a malformed connected cell, stop processing the
3186 cell immediately. Previously we would mark the connection for
3187 close, but continue processing the cell as if the connection were
3188 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
3190 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
3191 - Allow the nanosleep() system call, which glibc uses to implement
3192 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
3194 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
3195 - When running the ntor_ref.py test, make sure only to pass strings
3196 (rather than "bytes" objects) to the Python subprocess module.
3197 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
3200 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
3201 - Work around a change in OpenSSL 1.1.1 where return values that
3202 would previously indicate "no password" now indicate an empty
3203 password. Without this workaround, Tor instances running with
3204 OpenSSL 1.1.1 would accept descriptors that other Tor instances
3205 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
3207 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
3208 - Fix a compilation warning on some versions of GCC when building
3209 code that calls routerinfo_get_my_routerinfo() twice, assuming
3210 that the second call will succeed if the first one did. Fixes bug
3211 26269; bugfix on 0.2.8.2-alpha.
3213 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
3214 - Don't consider Tor running as a client if the ControlPort is open,
3215 but no actual client ports are open. Fixes bug 26062; bugfix
3218 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
3219 - Prevent a possible out-of-bounds smartlist read in
3220 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
3222 o Minor bugfixes (C correctness, backport from 0.3.3.4-alpha):
3223 - Fix a very unlikely (impossible, we believe) null pointer
3224 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
3225 Coverity; this is CID 1430932.
3227 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
3228 - Fix a number of small memory leaks identified by coverity. Fixes
3229 bug 26467; bugfix on numerous Tor versions.
3231 o Code simplification and refactoring (backport from 0.3.3.5-rc):
3232 - Move the list of default directory authorities to its own file.
3233 Closes ticket 24854. Patch by "beastr0".
3236 Changes in version 0.3.4.4-rc - 2018-07-09
3237 Tor 0.3.4.4-rc fixes several small compilation, portability, and
3238 correctness issues in previous versions of Tor. This version is a
3239 release candidate: if no serious bugs are found, we expect that the
3240 stable 0.3.4 release will be (almost) the same as this release.
3242 o Minor features (compilation):
3243 - When building Tor, prefer to use Python 3 over Python 2, and more
3244 recent (contemplated) versions over older ones. Closes
3247 o Minor features (geoip):
3248 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
3249 Country database. Closes ticket 26674.
3251 o Minor features (Rust, portability):
3252 - Rust cross-compilation is now supported. Closes ticket 25895.
3254 o Minor bugfixes (compilation):
3255 - Fix a compilation warning on some versions of GCC when building
3256 code that calls routerinfo_get_my_routerinfo() twice, assuming
3257 that the second call will succeed if the first one did. Fixes bug
3258 26269; bugfix on 0.2.8.2-alpha.
3260 o Minor bugfixes (control port):
3261 - Report the port correctly when a port is configured to bind to
3262 "auto". Fixes bug 26568; bugfix on 0.3.4.1-alpha.
3263 - Handle the HSADDRESS= argument to the HSPOST command properly.
3264 (Previously, this argument was misparsed and thus ignored.) Fixes
3265 bug 26523; bugfix on 0.3.3.1-alpha. Patch by "akwizgran".
3267 o Minor bugfixes (correctness, flow control):
3268 - Upon receiving a stream-level SENDME cell, verify that our window
3269 has not grown too large. Fixes bug 26214; bugfix on svn
3272 o Minor bugfixes (memory, correctness):
3273 - Fix a number of small memory leaks identified by coverity. Fixes
3274 bug 26467; bugfix on numerous Tor versions.
3276 o Minor bugfixes (testing, compatibility):
3277 - When running the hs_ntor_ref.py test, make sure only to pass
3278 strings (rather than "bytes" objects) to the Python subprocess
3279 module. Python 3 on Windows seems to require this. Fixes bug
3280 26535; bugfix on 0.3.1.1-alpha.
3281 - When running the ntor_ref.py test, make sure only to pass strings
3282 (rather than "bytes" objects) to the Python subprocess module.
3283 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
3287 Changes in version 0.3.3.8 - 2018-07-09
3288 Tor 0.3.3.8 backports several changes from the 0.3.4.x series, including
3289 fixes for a memory leak affecting directory authorities.
3291 o Major bugfixes (directory authority, backport from 0.3.4.3-alpha):
3292 - Stop leaking memory on directory authorities when planning to
3293 vote. This bug was crashing authorities by exhausting their
3294 memory. Fixes bug 26435; bugfix on 0.3.3.6.
3296 o Major bugfixes (rust, testing, backport from 0.3.4.3-alpha):
3297 - Make sure that failing tests in Rust will actually cause the build
3298 to fail: previously, they were ignored. Fixes bug 26258; bugfix
3301 o Minor features (compilation, backport from 0.3.4.4-rc):
3302 - When building Tor, prefer to use Python 3 over Python 2, and more
3303 recent (contemplated) versions over older ones. Closes
3306 o Minor features (geoip):
3307 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
3308 Country database. Closes ticket 26674.
3310 o Minor features (relay, diagnostic, backport from 0.3.4.3-alpha):
3311 - Add several checks to detect whether Tor relays are uploading
3312 their descriptors without specifying why they regenerated them.
3313 Diagnostic for ticket 25686.
3315 o Minor bugfixes (circuit path selection, backport from 0.3.4.1-alpha):
3316 - Don't count path selection failures as circuit build failures.
3317 This change should eliminate cases where Tor blames its guard or
3318 the network for situations like insufficient microdescriptors
3319 and/or overly restrictive torrc settings. Fixes bug 25705; bugfix
3322 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
3323 - Fix a compilation warning on some versions of GCC when building
3324 code that calls routerinfo_get_my_routerinfo() twice, assuming
3325 that the second call will succeed if the first one did. Fixes bug
3326 26269; bugfix on 0.2.8.2-alpha.
3328 o Minor bugfixes (control port, backport from 0.3.4.4-rc):
3329 - Handle the HSADDRESS= argument to the HSPOST command properly.
3330 (Previously, this argument was misparsed and thus ignored.) Fixes
3331 bug 26523; bugfix on 0.3.3.1-alpha. Patch by "akwizgran".
3333 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
3334 - Fix a number of small memory leaks identified by coverity. Fixes
3335 bug 26467; bugfix on numerous Tor versions.
3337 o Minor bugfixes (relay, backport from 0.3.4.3-alpha):
3338 - Relays now correctly block attempts to re-extend to the previous
3339 relay by Ed25519 identity. Previously they would warn in this
3340 case, but not actually reject the attempt. Fixes bug 26158; bugfix
3343 o Minor bugfixes (restart-in-process, backport from 0.3.4.1-alpha):
3344 - When shutting down, Tor now clears all the flags in the control.c
3345 module. This should prevent a bug where authentication cookies are
3346 not generated on restart. Fixes bug 25512; bugfix on 0.3.3.1-alpha.
3348 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
3349 - When running the hs_ntor_ref.py test, make sure only to pass
3350 strings (rather than "bytes" objects) to the Python subprocess
3351 module. Python 3 on Windows seems to require this. Fixes bug
3352 26535; bugfix on 0.3.1.1-alpha.
3353 - When running the ntor_ref.py test, make sure only to pass strings
3354 (rather than "bytes" objects) to the Python subprocess module.
3355 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
3359 Changes in version 0.3.4.3-alpha - 2018-06-26
3360 Tor 0.3.4.3-alpha fixes several bugs in earlier versions, including
3361 one that was causing stability issues on directory authorities.
3363 o Major bugfixes (directory authority):
3364 - Stop leaking memory on directory authorities when planning to
3365 vote. This bug was crashing authorities by exhausting their
3366 memory. Fixes bug 26435; bugfix on 0.3.3.6.
3368 o Major bugfixes (rust, testing):
3369 - Make sure that failing tests in Rust will actually cause the build
3370 to fail: previously, they were ignored. Fixes bug 26258; bugfix
3373 o Minor feature (directory authorities):
3374 - Stop warning about incomplete bw lines before the first complete
3375 bw line has been found, so that additional header lines can be
3376 ignored. Fixes bug 25960; bugfix on 0.2.2.1-alpha
3378 o Minor features (relay, diagnostic):
3379 - Add several checks to detect whether Tor relays are uploading
3380 their descriptors without specifying why they regenerated them.
3381 Diagnostic for ticket 25686.
3383 o Minor features (unit tests):
3384 - Test complete bandwidth measurements files, and test that
3385 incomplete bandwidth lines only give warnings when the end of the
3386 header has not been detected. Fixes bug 25947; bugfix
3389 o Minor bugfixes (compilation):
3390 - Refrain from compiling unit testing related object files when
3391 --disable-unittests is set to configure script. Fixes bug 24891;
3392 bugfix on 0.2.5.1-alpha.
3393 - When linking the libtor_testing.a library, only include the
3394 dirauth object files once. Previously, they were getting added
3395 twice. Fixes bug 26402; bugfix on 0.3.4.1-alpha.
3396 - The --enable-fatal-warnings flag now affects Rust code as well.
3397 Closes ticket 26245.
3399 o Minor bugfixes (onion services):
3400 - Recompute some consensus information after detecting a clock jump,
3401 or after transitioning from a non-live consensus to a live
3402 consensus. We do this to avoid having an outdated state, and
3403 miscalculating the index for next-generation onion services. Fixes
3404 bug 24977; bugfix on 0.3.2.1-alpha.
3406 o Minor bugfixes (relay):
3407 - Relays now correctly block attempts to re-extend to the previous
3408 relay by Ed25519 identity. Previously they would warn in this
3409 case, but not actually reject the attempt. Fixes bug 26158; bugfix
3412 o Minor bugfixes (testing):
3413 - Fix compilation of the doctests in the Rust crypto crate. Fixes
3414 bug 26415; bugfix on 0.3.4.1-alpha.
3415 - Instead of trying to read the geoip configuration files from
3416 within the unit tests, instead create our own ersatz files with
3417 just enough geoip data in the format we expect. Trying to read
3418 from the source directory created problems on Windows with mingw,
3419 where the build system's paths are not the same as the platform's
3420 paths. Fixes bug 25787; bugfix on 0.3.4.1-alpha.
3421 - Refrain from trying to get an item from an empty smartlist in
3422 test_bridges_clear_bridge_list. Set DEBUG_SMARTLIST in unit tests
3423 to catch improper smartlist usage. Furthermore, enable
3424 DEBUG_SMARTLIST globally when build is configured with fragile
3425 hardening. Fixes bug 26196; bugfix on 0.3.4.1-alpha.
3428 Changes in version 0.3.3.7 - 2018-06-12
3429 Tor 0.3.3.7 backports several changes from the 0.3.4.x series, including
3430 fixes for bugs affecting compatibility and stability.
3432 o Directory authority changes:
3433 - Add an IPv6 address for the "dannenberg" directory authority.
3434 Closes ticket 26343.
3436 o Minor features (geoip):
3437 - Update geoip and geoip6 to the June 7 2018 Maxmind GeoLite2
3438 Country database. Closes ticket 26351.
3440 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
3441 - Work around a change in OpenSSL 1.1.1 where return values that
3442 would previously indicate "no password" now indicate an empty
3443 password. Without this workaround, Tor instances running with
3444 OpenSSL 1.1.1 would accept descriptors that other Tor instances
3445 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
3447 o Minor bugfixes (compilation, backport from 0.3.4.2-alpha):
3448 - Silence unused-const-variable warnings in zstd.h with some GCC
3449 versions. Fixes bug 26272; bugfix on 0.3.1.1-alpha.
3451 o Minor bugfixes (controller, backport from 0.3.4.2-alpha):
3452 - Improve accuracy of the BUILDTIMEOUT_SET control port event's
3453 TIMEOUT_RATE and CLOSE_RATE fields. (We were previously
3454 miscounting the total number of circuits for these field values.)
3455 Fixes bug 26121; bugfix on 0.3.3.1-alpha.
3457 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
3458 - Prevent a possible out-of-bounds smartlist read in
3459 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
3461 o Minor bugfixes (path selection, backport from 0.3.4.1-alpha):
3462 - Only select relays when they have the descriptors we prefer to use
3463 for them. This change fixes a bug where we could select a relay
3464 because it had _some_ descriptor, but reject it later with a
3465 nonfatal assertion error because it didn't have the exact one we
3466 wanted. Fixes bugs 25691 and 25692; bugfix on 0.3.3.4-alpha.
3469 Changes in version 0.3.4.2-alpha - 2018-06-12
3470 Tor 0.3.4.2-alpha fixes several minor bugs in the previous alpha
3471 release, and forward-ports an authority-only security fix from 0.3.3.6.
3473 o Directory authority changes:
3474 - Add an IPv6 address for the "dannenberg" directory authority.
3475 Closes ticket 26343.
3477 o Major bugfixes (security, directory authority, denial-of-service, also in 0.3.3.6):
3478 - Fix a bug that could have allowed an attacker to force a directory
3479 authority to use up all its RAM by passing it a maliciously
3480 crafted protocol versions string. Fixes bug 25517; bugfix on
3481 0.2.9.4-alpha. This issue is also tracked as TROVE-2018-005.
3483 o Minor features (continuous integration):
3484 - Add the necessary configuration files for continuous integration
3485 testing on Windows, via the Appveyor platform. Closes ticket
3486 25549. Patches from Marcin Cieślak and Isis Lovecruft.
3488 o Minor features (geoip):
3489 - Update geoip and geoip6 to the June 7 2018 Maxmind GeoLite2
3490 Country database. Closes ticket 26351.
3492 o Minor bugfixes (compatibility, openssl):
3493 - Work around a change in OpenSSL 1.1.1 where return values that
3494 would previously indicate "no password" now indicate an empty
3495 password. Without this workaround, Tor instances running with
3496 OpenSSL 1.1.1 would accept descriptors that other Tor instances
3497 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
3499 o Minor bugfixes (compilation):
3500 - Silence unused-const-variable warnings in zstd.h with some GCC
3501 versions. Fixes bug 26272; bugfix on 0.3.1.1-alpha.
3502 - Fix compilation when using OpenSSL 1.1.0 with the "no-deprecated"
3503 flag enabled. Fixes bug 26156; bugfix on 0.3.4.1-alpha.
3504 - Avoid a compiler warning when casting the return value of
3505 smartlist_len() to double with DEBUG_SMARTLIST enabled. Fixes bug
3506 26283; bugfix on 0.2.4.10-alpha.
3508 o Minor bugfixes (control port):
3509 - Do not count 0-length RELAY_COMMAND_DATA cells as valid data in
3510 CIRC_BW events. Previously, such cells were counted entirely in
3511 the OVERHEAD field. Now they are not. Fixes bug 26259; bugfix
3514 o Minor bugfixes (controller):
3515 - Improve accuracy of the BUILDTIMEOUT_SET control port event's
3516 TIMEOUT_RATE and CLOSE_RATE fields. (We were previously
3517 miscounting the total number of circuits for these field values.)
3518 Fixes bug 26121; bugfix on 0.3.3.1-alpha.
3520 o Minor bugfixes (hardening):
3521 - Prevent a possible out-of-bounds smartlist read in
3522 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
3524 o Minor bugfixes (onion services):
3525 - Fix a bug that blocked the creation of ephemeral v3 onion
3526 services. Fixes bug 25939; bugfix on 0.3.4.1-alpha.
3528 o Minor bugfixes (test coverage tools):
3529 - Update our "cov-diff" script to handle output from the latest
3530 version of gcov, and to remove extraneous timestamp information
3531 from its output. Fixes bugs 26101 and 26102; bugfix
3535 Changes in version 0.3.3.6 - 2018-05-22
3536 Tor 0.3.3.6 is the first stable release in the 0.3.3 series. It
3537 backports several important fixes from the 0.3.4.1-alpha.
3539 The Tor 0.3.3 series includes controller support and other
3540 improvements for v3 onion services, official support for embedding Tor
3541 within other applications, and our first non-trivial module written in
3542 the Rust programming language. (Rust is still not enabled by default
3543 when building Tor.) And as usual, there are numerous other smaller
3544 bugfixes, features, and improvements.
3546 Below are the changes since 0.3.3.5-rc. For a list of all changes
3547 since 0.3.2.10, see the ReleaseNotes file.
3549 o Major bugfixes (directory authorities, security, backport from 0.3.4.1-alpha):
3550 - When directory authorities read a zero-byte bandwidth file, they
3551 would previously log a warning with the contents of an
3552 uninitialised buffer. They now log a warning about the empty file
3553 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
3555 o Major bugfixes (security, directory authority, denial-of-service):
3556 - Fix a bug that could have allowed an attacker to force a directory
3557 authority to use up all its RAM by passing it a maliciously
3558 crafted protocol versions string. Fixes bug 25517; bugfix on
3559 0.2.9.4-alpha. This issue is also tracked as TROVE-2018-005.
3561 o Major bugfixes (crash, backport from 0.3.4.1-alpha):
3562 - Avoid a rare assertion failure in the circuit build timeout code
3563 if we fail to allow any circuits to actually complete. Fixes bug
3564 25733; bugfix on 0.2.2.2-alpha.
3566 o Major bugfixes (directory authorities, backport from 0.3.4.1-alpha):
3567 - Avoid a crash when testing router reachability on a router that
3568 could have an ed25519 ID, but which does not. Fixes bug 25415;
3569 bugfix on 0.3.3.2-alpha.
3571 o Major bugfixes (onion service, backport from 0.3.4.1-alpha):
3572 - Correctly detect when onion services get disabled after HUP. Fixes
3573 bug 25761; bugfix on 0.3.2.1.
3575 o Major bugfixes (relay, denial of service, backport from 0.3.4.1-alpha):
3576 - Impose a limit on circuit cell queue size. The limit can be
3577 controlled by a consensus parameter. Fixes bug 25226; bugfix
3580 o Minor features (compatibility, backport from 0.3.4.1-alpha):
3581 - Avoid some compilation warnings with recent versions of LibreSSL.
3582 Closes ticket 26006.
3584 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
3585 - Our .travis.yml configuration now includes support for testing the
3586 results of "make distcheck". (It's not uncommon for "make check"
3587 to pass but "make distcheck" to fail.) Closes ticket 25814.
3588 - Our Travis CI configuration now integrates with the Coveralls
3589 coverage analysis tool. Closes ticket 25818.
3591 o Minor features (geoip):
3592 - Update geoip and geoip6 to the May 1 2018 Maxmind GeoLite2 Country
3593 database. Closes ticket 26104.
3595 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
3596 - Don't consider Tor running as a client if the ControlPort is open,
3597 but no actual client ports are open. Fixes bug 26062; bugfix
3600 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
3601 - Upon receiving a malformed connected cell, stop processing the
3602 cell immediately. Previously we would mark the connection for
3603 close, but continue processing the cell as if the connection were
3604 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
3606 o Minor bugfixes (documentation, backport from 0.3.4.1-alpha):
3607 - Stop saying in the manual that clients cache ipv4 dns answers from
3608 exit relays. We haven't used them since 0.2.6.3-alpha, and in
3609 ticket 24050 we stopped even caching them as of 0.3.2.6-alpha, but
3610 we forgot to say so in the man page. Fixes bug 26052; bugfix
3613 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
3614 - Allow the nanosleep() system call, which glibc uses to implement
3615 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
3617 o Minor bugfixes (onion service, backport from 0.3.4.1-alpha):
3618 - Fix a memory leak when a v3 onion service is configured and gets a
3619 SIGHUP signal. Fixes bug 25901; bugfix on 0.3.2.1-alpha.
3620 - When parsing the descriptor signature, look for the token plus an
3621 extra white-space at the end. This is more correct but also will
3622 allow us to support new fields that might start with "signature".
3623 Fixes bug 26069; bugfix on 0.3.0.1-alpha.
3625 o Minor bugfixes (relay, crash, backport from 0.3.4.1-alpha):
3626 - Avoid a crash when running with DirPort set but ORPort turned off.
3627 Fixes a case of bug 23693; bugfix on 0.3.1.1-alpha.
3629 o Documentation (backport from 0.3.4.1-alpha):
3630 - Correct an IPv6 error in the documentation for ExitPolicy. Closes
3631 ticket 25857. Patch from "CTassisF".
3634 Changes in version 0.3.4.1-alpha - 2018-05-17
3635 Tor 0.3.4.1-alpha is the first release in the 0.3.4.x series. It
3636 includes refactoring to begin reducing Tor's binary size and idle CPU
3637 usage on mobile, along with prep work for new bandwidth scanners,
3638 improvements to the experimental "vanguards" feature, and numerous
3639 other small features and bugfixes.
3641 o New system requirements:
3642 - Tor no longer tries to support old operating systems without
3643 mmap() or some local equivalent. Apparently, compilation on such
3644 systems has been broken for some time, without anybody noticing or
3645 complaining. Closes ticket 25398.
3647 o Major feature (directory authority, modularization):
3648 - The directory authority subsystem has been modularized. The code
3649 is now located in src/or/dirauth/, and is compiled in by default.
3650 To disable the module, the configure option
3651 --disable-module-dirauth has been added. This module may be
3652 disabled by default in some future release. Closes ticket 25610.
3654 o Major features (main loop, CPU usage):
3655 - When Tor is disabled (via DisableNetwork or via hibernation), it
3656 no longer needs to run any per-second events. This change should
3657 make it easier for mobile applications to disable Tor while the
3658 device is sleeping, or Tor is not running. Closes ticket 26063.
3659 - Tor no longer enables all of its periodic events by default.
3660 Previously, Tor would enable all possible main loop events,
3661 regardless of whether it needed them. Furthermore, many of these
3662 events are now disabled with Tor is hibernating or DisableNetwork
3663 is set. This is a big step towards reducing client CPU usage by
3664 reducing the amount of wake-ups the daemon does. Closes ticket
3666 - The bandwidth-limitation logic has been refactored so that
3667 bandwidth calculations are performed on-demand, rather than every
3668 TokenBucketRefillInterval milliseconds. This change should improve
3669 the granularity of our bandwidth calculations, and limit the
3670 number of times that the Tor process needs to wake up when it is
3671 idle. Closes ticket 25373.
3672 - Move responsibility for many operations from a once-per-second
3673 callback to a callback that is only scheduled as needed. Moving
3674 this functionality has allowed us to disable the callback when
3675 Tor's network is disabled. Once enough items are removed from our
3676 once-per-second callback, we can eliminate it entirely to conserve
3677 CPU when idle. The functionality removed includes: closing
3678 connections, circuits, and channels (ticket 25932); consensus
3679 voting (25937); flushing log callbacks (25951); honoring delayed
3680 SIGNEWNYM requests (25949); rescanning the consensus cache
3681 (25931); saving the state file to disk (25948); warning relay
3682 operators about unreachable ports (25952); and keeping track of
3683 Tor's uptime (26009).
3685 o Major bugfixes (directory authorities, security):
3686 - When directory authorities read a zero-byte bandwidth file, they
3687 would previously log a warning with the contents of an
3688 uninitialised buffer. They now log a warning about the empty file
3689 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
3691 o Major bugfixes (crash):
3692 - Avoid a rare assertion failure in the circuit build timeout code
3693 if we fail to allow any circuits to actually complete. Fixes bug
3694 25733; bugfix on 0.2.2.2-alpha.
3696 o Major bugfixes (directory authority):
3697 - Avoid a crash when testing router reachability on a router that
3698 could have an ed25519 ID, but which does not. Fixes bug 25415;
3699 bugfix on 0.3.3.2-alpha.
3701 o Major bugfixes (onion service):
3702 - Correctly detect when onion services get disabled after HUP. Fixes
3703 bug 25761; bugfix on 0.3.2.1.
3705 o Major bugfixes (protover, voting):
3706 - Revise Rust implementation of protover to use a more memory-
3707 efficient voting algorithm and corresponding data structures, thus
3708 avoiding a potential (but small impact) DoS attack where specially
3709 crafted protocol strings would expand to several potential
3710 megabytes in memory. In the process, several portions of code were
3711 revised to be methods on new, custom types, rather than functions
3712 taking interchangeable types, thus increasing type safety of the
3713 module. Custom error types and handling were added as well, in
3714 order to facilitate better error dismissal/handling in outside
3715 crates and avoid mistakenly passing an internal error string to C
3716 over the FFI boundary. Many tests were added, and some previous
3717 differences between the C and Rust implementations have been
3718 remedied. Fixes bug 24031; bugfix on 0.3.3.1-alpha.
3720 o Major bugfixes (relay, denial of service):
3721 - Impose a limit on circuit cell queue size. The limit can be
3722 controlled by a consensus parameter. Fixes bug 25226; bugfix
3725 o Minor features (accounting):
3726 - When Tor becomes dormant, it now uses a scheduled event to wake up
3727 at the right time. Previously, we would use the per-second timer
3728 to check whether to wake up, but we no longer have any per-second
3729 timers enabled when the network is disabled. Closes ticket 26064.
3731 o Minor features (code quality):
3732 - Add optional spell-checking for the Tor codebase, using the
3733 "misspell" program. To use this feature, run "make check-typos".
3734 Closes ticket 25024.
3736 o Minor features (compatibility):
3737 - Tor now detects versions of OpenSSL 1.1.0 and later compiled with
3738 the no-deprecated option, and builds correctly with them. Closes
3739 tickets 19429, 19981, and 25353.
3740 - Avoid some compilation warnings with recent versions of LibreSSL.
3741 Closes ticket 26006.
3743 o Minor features (compression, zstd):
3744 - When running with zstd, Tor now considers using advanced functions
3745 that the zstd maintainers have labeled as potentially unstable. To
3746 prevent breakage, Tor will only use this functionality when the
3747 runtime version of the zstd library matches the version with which
3748 Tor was compiled. Closes ticket 25162.
3750 o Minor features (configuration):
3751 - The "DownloadSchedule" options have been renamed to end with
3752 "DownloadInitialDelay". The old names are still allowed, but will
3753 produce a warning. Comma-separated lists are still permitted for
3754 these options, but all values after the first are ignored (as they
3755 have been since 0.2.9). Closes ticket 23354.
3757 o Minor features (continuous integration):
3758 - Our .travis.yml configuration now includes support for testing the
3759 results of "make distcheck". (It's not uncommon for "make check"
3760 to pass but "make distcheck" to fail.) Closes ticket 25814.
3761 - Our Travis CI configuration now integrates with the Coveralls
3762 coverage analysis tool. Closes ticket 25818.
3764 o Minor features (control port):
3765 - Introduce GETINFO "current-time/{local,utc}" to return the local
3766 and UTC times respectively in ISO format. This helps a controller
3767 like Tor Browser detect a time-related error. Closes ticket 25511.
3768 Patch by Neel Chauhan.
3769 - Introduce new fields to the CIRC_BW event. There are two new
3770 fields in each of the read and written directions. The DELIVERED
3771 fields report the total valid data on the circuit, as measured by
3772 the payload sizes of verified and error-checked relay command
3773 cells. The OVERHEAD fields report the total unused bytes in each
3774 of these cells. Closes ticket 25903.
3776 o Minor features (directory authority):
3777 - Directory authorities now open their key-pinning files as O_SYNC,
3778 to limit their chances of accidentally writing partial lines.
3779 Closes ticket 23909.
3781 o Minor features (directory authority, forward compatibility):
3782 - Make the lines of the measured bandwidth file able to contain
3783 their entries in any order. Previously, the node_id entry needed
3784 to come first. Closes ticket 26004.
3786 o Minor features (entry guards):
3787 - Introduce a new torrc option NumPrimaryGuards for controlling the
3788 number of primary guards. Closes ticket 25843.
3790 o Minor features (geoip):
3791 - Update geoip and geoip6 to the May 1 2018 Maxmind GeoLite2 Country
3792 database. Closes ticket 26104.
3794 o Minor features (performance):
3795 - Avoid a needless call to malloc() when processing an incoming
3796 relay cell. Closes ticket 24914.
3797 - Make our timing-wheel code run a tiny bit faster on 32-bit
3798 platforms, by preferring 32-bit math to 64-bit. Closes
3800 - Avoid a needless malloc()/free() pair every time we handle an ntor
3801 handshake. Closes ticket 25150.
3803 o Minor features (testing):
3804 - Add a unit test for voting_schedule_get_start_of_next_interval().
3805 Closes ticket 26014, and helps make unit test coverage
3807 - A new unittests module specifically for testing the functions in
3808 the (new-ish) bridges.c module has been created with new
3809 unittests, raising the code coverage percentages. Closes 25425.
3810 - We now have improved testing for addressmap_get_virtual_address()
3811 function. This should improve our test coverage, and make our test
3812 coverage more deterministic. Closes ticket 25993.
3814 o Minor features (timekeeping, circuit scheduling):
3815 - When keeping track of how busy each circuit have been recently on
3816 a given connection, use coarse-grained monotonic timers rather
3817 than gettimeofday(). This change should marginally increase
3818 accuracy and performance. Implements part of ticket 25927.
3820 o Minor bugfixes (bandwidth management):
3821 - Consider ourselves "low on write bandwidth" if we have exhausted
3822 our write bandwidth some time in the last second. This was the
3823 documented behavior before, but the actual behavior was to change
3824 this value every TokenBucketRefillInterval. Fixes bug 25828;
3825 bugfix on 0.2.3.5-alpha.
3827 o Minor bugfixes (C correctness):
3828 - Add a missing lock acquisition in the shutdown code of the control
3829 subsystem. Fixes bug 25675; bugfix on 0.2.7.3-rc. Found by
3830 Coverity; this is CID 1433643.
3832 o Minor bugfixes (circuit path selection):
3833 - Don't count path selection failures as circuit build failures.
3834 This change should eliminate cases where Tor blames its guard or
3835 the network for situations like insufficient microdescriptors
3836 and/or overly restrictive torrc settings. Fixes bug 25705; bugfix
3839 o Minor bugfixes (client):
3840 - Don't consider Tor running as a client if the ControlPort is open,
3841 but no actual client ports are open. Fixes bug 26062; bugfix
3844 o Minor bugfixes (code style):
3845 - Fixed multiple includes of transports.h in src/or/connection.c
3846 Fixes bug 25261; bugfix on 0.2.5.1-alpha.
3847 - Remove the unused variable n_possible from the function
3848 channel_get_for_extend(). Fixes bug 25645; bugfix on 0.2.4.4-alpha
3850 o Minor bugfixes (control interface):
3851 - Respond with more human-readable error messages to GETINFO exit-
3852 policy/* requests. Also, let controller know if an error is
3853 transient (response code 551) or not (response code 552). Fixes
3854 bug 25852; bugfix on 0.2.8.1-alpha.
3856 o Minor bugfixes (controller):
3857 - Make CIRC_BW event reflect the total of all data sent on a
3858 circuit, including padding and dropped cells. Also fix a mis-
3859 counting bug when STREAM_BW events were enabled. Fixes bug 25400;
3860 bugfix on 0.2.5.2-alpha.
3862 o Minor bugfixes (correctness, client):
3863 - Upon receiving a malformed connected cell, stop processing the cell
3864 immediately. Previously we would mark the connection for close, but
3865 continue processing the cell as if the connection were open. Fixes bug
3866 26072; bugfix on 0.2.4.7-alpha.
3868 o Minor bugfixes (directory client):
3869 - When unverified-consensus is verified, rename it to cached-
3870 consenus. Fixes bug 4187; bugfix on 0.2.0.3-alpha.
3871 - Fixed launching a certificate fetch always during the scheduled
3872 periodic consensus fetch by fetching only in those cases when
3873 consensus are waiting for certs. Fixes bug 24740; bugfix
3876 o Minor bugfixes (documentation):
3877 - Stop saying in the manual that clients cache ipv4 dns answers from
3878 exit relays. We haven't used them since 0.2.6.3-alpha, and in
3879 ticket 24050 we stopped even caching them as of 0.3.2.6-alpha, but
3880 we forgot to say so in the man page. Fixes bug 26052; bugfix
3883 o Minor bugfixes (error reporting):
3884 - Improve tolerance for directory authorities with skewed clocks.
3885 Previously, an authority with a clock more than 60 seconds ahead
3886 could cause a client with a correct clock to warn that the
3887 client's clock was behind. Now the clocks of a majority of
3888 directory authorities have to be ahead of the client before this
3889 warning will occur. Fixes bug 25756; bugfix on 0.2.2.25-alpha.
3891 o Minor bugfixes (Linux seccomp2 sandbox):
3892 - Allow the nanosleep() system call, which glibc uses to implement
3893 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
3895 o Minor bugfixes (onion service):
3896 - Fix a memory leak when a v3 onion service is configured and gets a
3897 SIGHUP signal. Fixes bug 25901; bugfix on 0.3.2.1-alpha.
3898 - When parsing the descriptor signature, look for the token plus an
3899 extra white-space at the end. This is more correct but also will
3900 allow us to support new fields that might start with "signature".
3901 Fixes bug 26069; bugfix on 0.3.0.1-alpha.
3903 o Minor bugfixes (path selection):
3904 - Only select relays when they have the descriptors we prefer to use
3905 for them. This change fixes a bug where we could select a relay
3906 because it had _some_ descriptor, but reject it later with a
3907 nonfatal assertion error because it didn't have the exact one we
3908 wanted. Fixes bugs 25691 and 25692; bugfix on 0.3.3.4-alpha.
3910 o Minor bugfixes (portability):
3911 - Do not align mmap length, as it is not required by POSIX, and the
3912 getpagesize function is deprecated. Fixes bug 25399; bugfix
3915 o Minor bugfixes (portability, FreeBSD):
3916 - In have_enough_mem_for_dircache(), the variable DIRCACHE_MIN_MEM_MB
3917 does not stringify on FreeBSD, so we switch to tor_asprintf().
3918 Fixes bug 20887; bugfix on 0.2.8.1-alpha. Patch by Neel Chauhan.
3920 o Minor bugfixes (relay statistics):
3921 - When a relay is collecting internal statistics about how many
3922 create cell requests it has seen of each type, accurately count
3923 the requests from relays that temporarily fall out of the
3924 consensus. (To be extra conservative, we were already ignoring
3925 requests from clients in our counts, and we continue ignoring them
3926 here.) Fixes bug 24910; bugfix on 0.2.4.17-rc.
3928 o Minor bugfixes (relay, crash):
3929 - Avoid a crash when running with DirPort set but ORPort turned off.
3930 Fixes a case of bug 23693; bugfix on 0.3.1.1-alpha.
3932 o Minor bugfixes (restart-in-process):
3933 - When shutting down, Tor now clears all the flags in the control.c
3934 module. This should prevent a bug where authentication cookies are
3935 not generated on restart. Fixes bug 25512; bugfix on 0.3.3.1-alpha.
3937 o Minor bugfixes (testing):
3938 - When testing workqueue event-cancellation, make sure that we
3939 actually cancel an event, and that cancel each event with equal
3940 probability. (It was previously possible, though extremely
3941 unlikely, for our event-canceling test not to cancel any events.)
3942 Fixes bug 26008; bugfix on 0.2.6.3-alpha.
3943 - Repeat part of the test in test_client_pick_intro() a number of
3944 times, to give it consistent coverage. Fixes bug 25996; bugfix
3946 - Remove randomness from the hs_common/responsible_hsdirs test, so
3947 that it always takes the same path through the function it tests.
3948 Fixes bug 25997; bugfix on 0.3.2.1-alpha.
3949 - Change the behavior of the "channel/outbound" test so that it
3950 never causes a 10-second rollover for the EWMA circuitmux code.
3951 Previously, this behavior would happen randomly, and result in
3952 fluctuating test coverage. Fixes bug 25994; bugfix
3954 - Use X509_new() to allocate certificates that will be freed later
3955 with X509_free(). Previously, some parts of the unit tests had
3956 used tor_malloc_zero(), which is incorrect, and which caused test
3957 failures on Windows when they were built with extra hardening.
3958 Fixes bugs 25943 and 25944; bugfix on 0.2.8.1-alpha. Patch by
3960 - While running the circuit_timeout test, fix the PRNG to a
3961 deterministic AES stream, so that the test coverage from this test
3962 will itself be deterministic. Fixes bug 25995; bugfix
3965 o Minor bugfixes (vanguards):
3966 - Allow the last hop in a vanguard circuit to be the same as our
3967 first, to prevent the adversary from influencing guard node choice
3968 by choice of last hop. Also prevent the creation of A - B - A
3969 paths, or A - A paths, which are forbidden by relays. Fixes bug
3970 25870; bugfix on 0.3.3.1-alpha.
3972 o Code simplification and refactoring:
3973 - Remove duplicate code in parse_{c,s}method_line and bootstrap
3974 their functionalities into a single function. Fixes bug 6236;
3975 bugfix on 0.2.3.6-alpha.
3976 - We remove the PortForwsrding and PortForwardingHelper options,
3977 related functions, and the port_forwarding tests. These options
3978 were used by the now-deprecated Vidalia to help ordinary users
3979 become Tor relays or bridges. Closes ticket 25409. Patch by
3981 - In order to make the OR and dir checking function in router.c less
3982 confusing we renamed some functions and
3983 consider_testing_reachability() has been split into
3984 router_should_check_reachability() and
3985 router_do_reachability_checks(). Also we improved the documentation
3986 in some functions. Closes ticket 18918.
3987 - Initial work to isolate Libevent usage to a handful of modules in
3988 our codebase, to simplify our call structure, and so that we can
3989 more easily change event loops in the future if needed. Closes
3991 - Introduce a function to call getsockname() and return tor_addr_t,
3992 to save a little complexity throughout the codebase. Closes
3994 - Make hsdir_index in node_t a hsdir_index_t rather than a pointer
3995 as hsdir_index is always present. Also, we move hsdir_index_t into
3996 or.h. Closes ticket 23094. Patch by Neel Chauhan.
3997 - Merge functions used for describing nodes and suppress the
3998 functions that do not allocate memory for the output buffer
3999 string. NODE_DESC_BUF_LEN constant and format_node_description()
4000 function cannot be used externally from router.c module anymore.
4001 Closes ticket 25432. Patch by valentecaio.
4002 - Our main loop has been simplified so that all important operations
4003 happen inside events. Previously, some operations had to happen
4004 outside the event loop, to prevent infinite sequences of event
4005 activations. Closes ticket 25374.
4006 - Put a SHA1 public key digest in hs_service_intro_point_t, and use
4007 it in register_intro_circ() and service_intro_point_new(). This
4008 prevents the digest from being re-calculated each time. Closes
4009 ticket 23107. Patch by Neel Chauhan.
4010 - Refactor token-bucket implementations to use a common backend.
4011 Closes ticket 25766.
4012 - Remove extern declaration of stats_n_seconds_working variable from
4013 main, protecting its accesses with get_uptime() and reset_uptime()
4014 functions. Closes ticket 25081, patch by “valentecaio”.
4015 - Remove our previous logic for "cached gettimeofday()" -- our
4016 coarse monotonic timers are fast enough for this purpose, and far
4017 less error-prone. Implements part of ticket 25927.
4018 - Remove the return value for fascist_firewall_choose_address_base(),
4019 and sister functions such as fascist_firewall_choose_address_node()
4020 and fascist_firewall_choose_address_rs(). Also, while we're here,
4021 initialize the ap argument as leaving it uninitialized can pose a
4022 security hazard. Closes ticket 24734. Patch by Neel Chauhan.
4023 - Rename two fields of connection_t struct. timestamp_lastwritten is
4024 renamed to timestamp_last_write_allowed and timestamp_lastread is
4025 renamed to timestamp_last_read_allowed. Closes ticket 24714, patch
4027 - Since Tor requires C99, remove our old workaround code for libc
4028 implementations where free(NULL) doesn't work. Closes ticket 24484.
4029 - Use our standard rate-limiting code to deal with excessive
4030 libevent failures, rather than the hand-rolled logic we had
4031 before. Closes ticket 26016.
4032 - We remove the return value of node_get_prim_orport() and
4033 node_get_prim_dirport(), and introduce node_get_prim_orport() in
4034 node_ipv6_or_preferred() and node_ipv6_dir_preferred() in order to
4035 check for a null address. Closes ticket 23873. Patch by
4037 - We switch to should_record_bridge_info() in
4038 geoip_note_client_seen() and options_need_geoip_info() instead of
4039 accessing the configuration values directly. Fixes bug 25290;
4040 bugfix on 0.2.1.6-alpha. Patch by Neel Chauhan.
4042 o Deprecated features:
4043 - As we are not recommending 0.2.5 anymore, we require relays that
4044 once had an ed25519 key associated with their RSA key to always
4045 have that key, instead of allowing them to drop back to a version
4046 that didn't support ed25519. This means they need to use a new RSA
4047 key if they want to downgrade to an older version of tor without
4048 ed25519. Closes ticket 20522.
4051 - Correct an IPv6 error in the documentation for ExitPolicy. Closes
4052 ticket 25857. Patch from "CTassisF".
4055 - Directory authorities will no longer support voting according to
4056 any consensus method before consensus method 25. This keeps
4057 authorities compatible with all authorities running 0.2.9.8 and
4058 later, and does not break any clients or relays. Implements ticket
4059 24378 and proposal 290.
4060 - The PortForwarding and PortForwardingHelper features have been
4061 removed. The reasoning is, given that implementations of NAT
4062 traversal protocols within common consumer grade routers are
4063 frequently buggy, and that the target audience for a NAT punching
4064 feature is a perhaps less-technically-inclined relay operator,
4065 when the helper fails to setup traversal the problems are usually
4066 deep, ugly, and very router specific, making them horrendously
4067 impossible for technical support to reliable assist with, and thus
4068 resulting in frustration all around. Unfortunately, relay
4069 operators who would like to run relays behind NATs will need to
4070 become more familiar with the port forwarding configurations on
4071 their local router. Closes 25409.
4072 - The TestingEnableTbEmptyEvent option has been removed. It was used
4073 in testing simulations to measure how often connection buckets
4074 were emptied, in order to improve our scheduling, but it has not
4075 been actively used in years. Closes ticket 25760.
4076 - The old "round-robin" circuit multiplexer (circuitmux)
4077 implementation has been removed, along with a fairly large set of
4078 code that existed to support it. It has not been the default
4079 circuitmux since we introduced the "EWMA" circuitmux in 0.2.4.x,
4080 but it still required an unreasonable amount of memory and CPU.
4081 Closes ticket 25268.
4084 Changes in version 0.3.3.5-rc - 2018-04-15
4085 Tor 0.3.3.5-rc fixes various bugs in earlier versions of Tor,
4086 including some that could affect reliability or correctness.
4088 This is the first release candidate in the 0.3.3 series. If we find no
4089 new bugs or regression here, then the first stable 0.3.3 release will
4090 be nearly identical to this one.
4092 o Major bugfixes (security, protover, voting):
4093 - Revise Rust implementation of protover to use a more memory-
4094 efficient voting algorithm and corresponding data structures, thus
4095 avoiding a potential memory-based DoS attack where specially
4096 crafted protocol strings would expand to fill available memory.
4097 Fixes bug 24031; bugfix on 0.3.3.1-alpha.
4099 o Major bugfixes (performance, load balancing):
4100 - Directory authorities no longer vote in favor of the Guard flag
4101 for relays without directory support. Starting in Tor
4102 0.3.0.1-alpha, clients have been avoiding using such relays in the
4103 Guard position, leading to increasingly broken load balancing for
4104 the 5%-or-so of Guards that don't advertise directory support.
4105 Fixes bug 22310; bugfix on 0.3.0.6.
4107 o Minor feature (continuous integration):
4108 - Update the Travis CI configuration to use the stable Rust channel,
4109 now that we have decided to require that. Closes ticket 25714.
4111 o Minor features (config options):
4112 - Change the way the default value for MaxMemInQueues is calculated.
4113 We now use 40% of the hardware RAM if the system has 8 GB RAM or
4114 more. Otherwise we use the former value of 75%. Closes
4117 o Minor features (geoip):
4118 - Update geoip and geoip6 to the April 3 2018 Maxmind GeoLite2
4119 Country database. Closes ticket 25718.
4121 o Minor bugfixes (client):
4122 - When using a listed relay as a bridge, and also using
4123 microdescriptors, and considering that relay as a non-bridge in a
4124 circuit, treat its microdescriptor as a valid source of
4125 information about that relay. This change should prevent a non-
4126 fatal assertion error. Fixes bug 25691; bugfix on 0.3.3.4-alpha.
4128 o Minor bugfixes (controller):
4129 - Restore the correct operation of the RESOLVE command, which had
4130 been broken since we added the ability to enable/disable DNS on
4131 specific listener ports. Fixes bug 25617; bugfix on 0.2.9.3-alpha.
4133 o Minor bugfixes (distribution, compilation, rust):
4134 - Build correctly when the rust dependencies submodule is loaded,
4135 but the TOR_RUST_DEPENDENCIES environment variable is not set.
4136 Fixes bug 25679; bugfix on 0.3.3.1-alpha.
4137 - Actually include all of our Rust source in our source
4138 distributions. (Previously, a few of the files were accidentally
4139 omitted.) Fixes bug 25732; bugfix on 0.3.3.2-alpha.
4141 o Minor bugfixes (documentation):
4142 - Document that the PerConnBW{Rate,Burst} options will fall back to
4143 their corresponding consensus parameters only if those parameters
4144 are set. Previously we had claimed that these values would always
4145 be set in the consensus. Fixes bug 25296; bugfix on 0.2.2.7-alpha.
4146 - Revert a misformatting issue in the ExitPolicy documentation.
4147 Fixes bug 25582; bugfix on 0.3.3.1-alpha.
4149 o Minor bugfixes (exit relay DNS retries):
4150 - Re-attempt timed-out DNS queries 3 times before failure, since our
4151 timeout is 5 seconds for them, but clients wait 10-15. Also allow
4152 slightly more timeouts per resolver when an exit has multiple
4153 resolvers configured. Fixes bug 21394; bugfix on 0.3.1.9.
4155 o Minor bugfixes (onion services):
4156 - Re-instate counting the client HSDir fetch circuits against the
4157 MaxClientCircuitsPending rate limit. Fixes bug 24989; bugfix
4159 - Remove underscores from the _HSLayer{2,3}Nodes options. This
4160 expert-user configuration can now be enabled as HSLayer{2,3}Nodes.
4161 Fixes bug 25581; bugfix on 0.3.3.1-alpha
4163 o Code simplification and refactoring:
4164 - Move the list of default directory authorities to its own file.
4165 Closes ticket 24854. Patch by "beastr0".
4167 o Documentation (manpage, denial of service):
4168 - Provide more detail about the denial-of-service options, by
4169 listing each mitigation and explaining how they relate. Closes
4173 Changes in version 0.3.3.4-alpha - 2018-03-29
4174 Tor 0.3.3.4-alpha includes various bugfixes for issues found during
4175 the alpha testing of earlier releases in its series. We are
4176 approaching a stable 0.3.3.4-alpha release: more testing is welcome!
4178 o New system requirements:
4179 - When built with Rust, Tor now depends on version 0.2.39 of the
4180 libc crate. Closes tickets 25310 and 25664.
4182 o Major bugfixes (relay, connection):
4183 - If we have failed to connect to a relay and received a connection
4184 refused, timeout, or similar error (at the TCP level), do not try
4185 that same address/port again for 60 seconds after the failure has
4186 occurred. Fixes bug 24767; bugfix on 0.0.6.
4188 o Minor features (geoip):
4189 - Update geoip and geoip6 to the March 8 2018 Maxmind GeoLite2
4190 Country database. Closes ticket 25469.
4192 o Minor features (log messages):
4193 - Improve log message in the out-of-memory handler to include
4194 information about memory usage from the different compression
4195 backends. Closes ticket 25372.
4197 o Minor features (sandbox):
4198 - Explicitly permit the poll() system call when the Linux
4199 seccomp2-based sandbox is enabled: apparently, some versions of
4200 libc use poll() when calling getpwnam(). Closes ticket 25313.
4202 o Minor bugfixes (C correctness):
4203 - Fix a very unlikely (impossible, we believe) null pointer
4204 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
4205 Coverity; this is CID 1430932.
4207 o Minor bugfixes (channel, client):
4208 - Better identify client connection when reporting to the geoip
4209 client cache. Fixes bug 24904; bugfix on 0.3.1.7.
4211 o Minor bugfixes (compilation):
4212 - Fix a C99 compliance issue in our configuration script that caused
4213 compilation issues when compiling Tor with certain versions of
4214 xtools. Fixes bug 25474; bugfix on 0.3.2.5-alpha.
4216 o Minor bugfixes (controller, reliability):
4217 - Avoid a (nonfatal) assertion failure when extending a one-hop
4218 circuit from the controller to become a multihop circuit. Fixes
4219 bug 24903; bugfix on 0.2.5.2-alpha.
4221 o Major bugfixes (networking):
4222 - Tor will no longer reject IPv6 address strings from Tor Browser
4223 when they are passed as hostnames in SOCKS5 requests. Fixes bug
4224 25036, bugfix on Tor 0.3.1.2.
4226 o Minor bugfixes (networking):
4227 - string_is_valid_hostname() will not consider IP strings to be
4228 valid hostnames. Fixes bug 25055; bugfix on Tor 0.2.5.5.
4230 o Minor bugfixes (onion service v3):
4231 - Avoid an assertion failure when the next onion service
4232 descriptor rotation type is out of sync with the consensus's
4233 valid-after time. Instead, log a warning message with extra
4234 information, so we can better hunt down the cause of this
4235 assertion. Fixes bug 25306; bugfix on 0.3.2.1-alpha.
4237 o Minor bugfixes (testing):
4238 - Avoid intermittent test failures due to a test that had relied on
4239 onion service introduction point creation finishing within 5
4240 seconds of real clock time. Fixes bug 25450; bugfix
4242 - Rust crates are now automatically detected and tested. Previously,
4243 some crates were not tested by `make test-rust` due to a static
4244 string in the `src/test/test_rust.sh` script specifying which
4245 crates to test. Fixes bug 25560; bugfix on 0.3.3.3-alpha.
4247 o Minor bugfixes (testing, benchmarks):
4248 - Fix a crash when running benchmark tests on win32 systems. The
4249 crash was due to a mutex that wasn't initialized before logging
4250 and options were initialized. Fixes bug 25479; bugfix
4253 o Minor bugfixes (warnings, ipv6):
4254 - Avoid a bug warning that could occur when trying to connect to a
4255 relay over IPv6. This warning would occur on a Tor instance that
4256 downloads router descriptors, but prefers to use microdescriptors.
4257 Fixes bug 25213; bugfix on 0.3.3.1-alpha.
4259 o Code simplification and refactoring:
4260 - Remove the old (deterministic) directory retry logic entirely:
4261 We've used exponential backoff exclusively for some time. Closes
4265 - Improved the documentation of AccountingStart parameter. Closes
4267 - Update the documentation for "Log" to include the current list of
4268 logging domains. Closes ticket 25378.
4271 Changes in version 0.3.1.10 - 2018-03-03
4272 Tor 0.3.1.10 backports a number of bugfixes, including important fixes for
4275 It includes an important security fix for a remote crash attack
4276 against directory authorities, tracked as TROVE-2018-001.
4278 This release also backports our new system for improved resistance to
4279 denial-of-service attacks against relays.
4281 This release also fixes several minor bugs and annoyances from
4284 All directory authorities should upgrade to one of the versions
4285 released today. Relays running 0.3.1.x may wish to update to one of
4286 the versions released today, for the DoS mitigations.
4288 Please note: according to our release calendar, Tor 0.3.1 will no
4289 longer be supported after 1 July 2018. If you will be running Tor
4290 after that date, you should make sure to plan to upgrade to the latest
4291 stable version, or downgrade to 0.2.9 (which will receive long-term
4294 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
4295 - Fix a protocol-list handling bug that could be used to remotely crash
4296 directory authorities with a null-pointer exception. Fixes bug 25074;
4297 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
4300 o Major features (denial-of-service mitigation, backport from 0.3.3.2-alpha):
4301 - Give relays some defenses against the recent network overload. We
4302 start with three defenses (default parameters in parentheses).
4303 First: if a single client address makes too many concurrent
4304 connections (>100), hang up on further connections. Second: if a
4305 single client address makes circuits too quickly (more than 3 per
4306 second, with an allowed burst of 90) while also having too many
4307 connections open (3), refuse new create cells for the next while
4308 (1-2 hours). Third: if a client asks to establish a rendezvous
4309 point to you directly, ignore the request. These defenses can be
4310 manually controlled by new torrc options, but relays will also
4311 take guidance from consensus parameters, so there's no need to
4312 configure anything manually. Implements ticket 24902.
4314 o Minor features (linux seccomp2 sandbox, backport from 0.3.2.5-alpha):
4315 - Update the sandbox rules so that they should now work correctly
4316 with Glibc 2.26. Closes ticket 24315.
4318 o Major bugfixes (onion services, retry behavior, backport from 0.3.3.1-alpha):
4319 - Fix an "off by 2" error in counting rendezvous failures on the
4320 onion service side. While we thought we would stop the rendezvous
4321 attempt after one failed circuit, we were actually making three
4322 circuit attempts before giving up. Now switch to a default of 2,
4323 and allow the consensus parameter "hs_service_max_rdv_failures" to
4324 override. Fixes bug 24895; bugfix on 0.0.6.
4326 o Major bugfixes (protocol versions, backport from 0.3.3.2-alpha):
4327 - Add Link protocol version 5 to the supported protocols list. Fixes
4328 bug 25070; bugfix on 0.3.1.1-alpha.
4330 o Major bugfixes (relay, backport from 0.3.3.1-alpha):
4331 - Fix a set of false positives where relays would consider
4332 connections to other relays as being client-only connections (and
4333 thus e.g. deserving different link padding schemes) if those
4334 relays fell out of the consensus briefly. Now we look only at the
4335 initial handshake and whether the connection authenticated as a
4336 relay. Fixes bug 24898; bugfix on 0.3.1.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 feature (relay statistics, backport from 0.3.2.6-alpha):
4344 - Change relay bandwidth reporting stats interval from 4 hours to 24
4345 hours in order to reduce the efficiency of guard discovery
4346 attacks. Fixes ticket 23856.
4348 o Minor features (compatibility, OpenSSL, backport from 0.3.3.3-alpha):
4349 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
4350 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
4351 since they neither disabled TLS 1.3 nor enabled any of the
4352 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
4353 Closes ticket 24978.
4355 o Minor features (fallback directory mirrors, backport from 0.3.2.9):
4356 - The fallback directory list has been re-generated based on the
4357 current status of the network. Tor uses fallback directories to
4358 bootstrap when it doesn't yet have up-to-date directory
4359 information. Closes ticket 24801.
4360 - Make the default DirAuthorityFallbackRate 0.1, so that clients
4361 prefer to bootstrap from fallback directory mirrors. This is a
4362 follow-up to 24679, which removed weights from the default
4363 fallbacks. Implements ticket 24681.
4365 o Minor features (geoip):
4366 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
4369 o Minor bugfix (channel connection, backport from 0.3.3.2-alpha):
4370 - Use the actual observed address of an incoming relay connection,
4371 not the canonical address of the relay from its descriptor, when
4372 making decisions about how to handle the incoming connection.
4373 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
4375 o Minor bugfix (directory authority, backport from 0.3.3.2-alpha):
4376 - Directory authorities, when refusing a descriptor from a rejected
4377 relay, now explicitly tell the relay (in its logs) to set a valid
4378 ContactInfo address and contact the bad-relays@ mailing list.
4379 Fixes bug 25170; bugfix on 0.2.9.1.
4381 o Minor bugfixes (address selection, backport from 0.3.2.9):
4382 - When the fascist_firewall_choose_address_ functions don't find a
4383 reachable address, set the returned address to the null address
4384 and port. This is a precautionary measure, because some callers do
4385 not check the return value. Fixes bug 24736; bugfix
4388 o Major bugfixes (bootstrapping, backport from 0.3.2.5-alpha):
4389 - Fetch descriptors aggressively whenever we lack enough to build
4390 circuits, regardless of how many descriptors we are missing.
4391 Previously, we would delay launching the fetch when we had fewer
4392 than 15 missing descriptors, even if some of those descriptors
4393 were blocking circuits from building. Fixes bug 23985; bugfix on
4394 0.1.1.11-alpha. The effects of this bug became worse in
4395 0.3.0.3-alpha, when we began treating missing descriptors from our
4396 primary guards as a reason to delay circuits.
4397 - Don't try fetching microdescriptors from relays that have failed
4398 to deliver them in the past. Fixes bug 23817; bugfix
4401 o Minor bugfixes (compilation, backport from 0.3.2.7-rc):
4402 - Fix a signed/unsigned comparison warning introduced by our fix to
4403 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
4405 o Minor bugfixes (control port, linux seccomp2 sandbox, backport from 0.3.2.5-alpha):
4406 - Avoid a crash when attempting to use the seccomp2 sandbox together
4407 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
4410 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
4411 - Fix a possible crash on malformed consensus. If a consensus had
4412 contained an unparseable protocol line, it could have made clients
4413 and relays crash with a null-pointer exception. To exploit this
4414 issue, however, an attacker would need to be able to subvert the
4415 directory authority system. Fixes bug 25251; bugfix on
4416 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
4418 o Minor bugfixes (directory cache, backport from 0.3.2.5-alpha):
4419 - Recover better from empty or corrupt files in the consensus cache
4420 directory. Fixes bug 24099; bugfix on 0.3.1.1-alpha.
4421 - When a consensus diff calculation is only partially successful,
4422 only record the successful parts as having succeeded. Partial
4423 success can happen if (for example) one compression method fails
4424 but the others succeed. Previously we misrecorded all the
4425 calculations as having succeeded, which would later cause a
4426 nonfatal assertion failure. Fixes bug 24086; bugfix
4429 o Minor bugfixes (entry guards, backport from 0.3.2.3-alpha):
4430 - Tor now updates its guard state when it reads a consensus
4431 regardless of whether it's missing descriptors. That makes tor use
4432 its primary guards to fetch descriptors in some edge cases where
4433 it would previously have used fallback directories. Fixes bug
4434 23862; bugfix on 0.3.0.1-alpha.
4436 o Minor bugfixes (logging, backport from 0.3.3.2-alpha):
4437 - Don't treat inability to store a cached consensus object as a bug:
4438 it can happen normally when we are out of disk space. Fixes bug
4439 24859; bugfix on 0.3.1.1-alpha.
4441 o Minor bugfixes (memory usage, backport from 0.3.2.8-rc):
4442 - When queuing DESTROY cells on a channel, only queue the circuit-id
4443 and reason fields: not the entire 514-byte cell. This fix should
4444 help mitigate any bugs or attacks that fill up these queues, and
4445 free more RAM for other uses. Fixes bug 24666; bugfix
4448 o Minor bugfixes (network layer, backport from 0.3.2.5-alpha):
4449 - When closing a connection via close_connection_immediately(), we
4450 mark it as "not blocked on bandwidth", to prevent later calls from
4451 trying to unblock it, and give it permission to read. This fixes a
4452 backtrace warning that can happen on relays under various
4453 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
4455 o Minor bugfixes (path selection, backport from 0.3.2.4-alpha):
4456 - When selecting relays by bandwidth, avoid a rounding error that
4457 could sometimes cause load to be imbalanced incorrectly.
4458 Previously, we would always round upwards; now, we round towards
4459 the nearest integer. This had the biggest effect when a relay's
4460 weight adjustments should have given it weight 0, but it got
4461 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
4462 - When calculating the fraction of nodes that have descriptors, and
4463 all nodes in the network have zero bandwidths, count the number of
4464 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
4465 - Actually log the total bandwidth in compute_weighted_bandwidths().
4466 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
4468 o Minor bugfixes (performance, fragile-hardening, backport from 0.3.3.1-alpha):
4469 - Improve the performance of our consensus-diff application code
4470 when Tor is built with the --enable-fragile-hardening option set.
4471 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
4473 o Minor bugfixes (OSX, backport from 0.3.3.1-alpha):
4474 - Don't exit the Tor process if setrlimit() fails to change the file
4475 limit (which can happen sometimes on some versions of OSX). Fixes
4476 bug 21074; bugfix on 0.0.9pre5.
4478 o Minor bugfixes (portability, msvc, backport from 0.3.2.9):
4479 - Fix a bug in the bit-counting parts of our timing-wheel code on
4480 MSVC. (Note that MSVC is still not a supported build platform, due
4481 to cyptographic timing channel risks.) Fixes bug 24633; bugfix
4484 o Minor bugfixes (relay, partial backport):
4485 - Make the internal channel_is_client() function look at what sort
4486 of connection handshake the other side used, rather than whether
4487 the other side ever sent a create_fast cell to us. Backports part
4488 of the fixes from bugs 22805 and 24898.
4490 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
4491 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
4493 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
4494 bugfix on 0.2.9.4-alpha.
4496 o Code simplification and refactoring (backport from 0.3.3.3-alpha):
4497 - Update the "rust dependencies" submodule to be a project-level
4498 repository, rather than a user repository. Closes ticket 25323.
4501 Changes in version 0.2.9.15 - 2018-03-03
4502 Tor 0.2.9.15 backports important security and stability bugfixes from
4505 It includes an important security fix for a remote crash attack
4506 against directory authorities, tracked as TROVE-2018-001.
4508 This release also backports our new system for improved resistance to
4509 denial-of-service attacks against relays.
4511 This release also fixes several minor bugs and annoyances from
4514 All directory authorities should upgrade to one of the versions
4515 released today. Relays running 0.2.9.x may wish to update to one of
4516 the versions released today, for the DoS mitigations.
4518 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
4519 - Fix a protocol-list handling bug that could be used to remotely crash
4520 directory authorities with a null-pointer exception. Fixes bug 25074;
4521 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
4524 o Major features (denial-of-service mitigation):
4525 - Give relays some defenses against the recent network overload. We
4526 start with three defenses (default parameters in parentheses).
4527 First: if a single client address makes too many concurrent
4528 connections (>100), hang up on further connections. Second: if a
4529 single client address makes circuits too quickly (more than 3 per
4530 second, with an allowed burst of 90) while also having too many
4531 connections open (3), refuse new create cells for the next while
4532 (1-2 hours). Third: if a client asks to establish a rendezvous
4533 point to you directly, ignore the request. These defenses can be
4534 manually controlled by new torrc options, but relays will also
4535 take guidance from consensus parameters, so there's no need to
4536 configure anything manually. Implements ticket 24902.
4538 o Major bugfixes (bootstrapping):
4539 - Fetch descriptors aggressively whenever we lack enough to build
4540 circuits, regardless of how many descriptors we are missing.
4541 Previously, we would delay launching the fetch when we had fewer
4542 than 15 missing descriptors, even if some of those descriptors
4543 were blocking circuits from building. Fixes bug 23985; bugfix on
4544 0.1.1.11-alpha. The effects of this bug became worse in
4545 0.3.0.3-alpha, when we began treating missing descriptors from our
4546 primary guards as a reason to delay circuits.
4548 o Major bugfixes (onion services, retry behavior):
4549 - Fix an "off by 2" error in counting rendezvous failures on the
4550 onion service side. While we thought we would stop the rendezvous
4551 attempt after one failed circuit, we were actually making three
4552 circuit attempts before giving up. Now switch to a default of 2,
4553 and allow the consensus parameter "hs_service_max_rdv_failures" to
4554 override. Fixes bug 24895; bugfix on 0.0.6.
4556 o Minor feature (relay statistics):
4557 - Change relay bandwidth reporting stats interval from 4 hours to 24
4558 hours in order to reduce the efficiency of guard discovery
4559 attacks. Fixes ticket 23856.
4561 o Minor features (compatibility, OpenSSL):
4562 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
4563 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
4564 since they neither disabled TLS 1.3 nor enabled any of the
4565 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
4566 Closes ticket 24978.
4568 o Minor features (denial-of-service avoidance):
4569 - Make our OOM handler aware of the geoip client history cache so it
4570 doesn't fill up the memory. This check is important for IPv6 and
4571 our DoS mitigation subsystem. Closes ticket 25122.
4573 o Minor features (fallback directory mirrors):
4574 - The fallback directory list has been re-generated based on the
4575 current status of the network. Tor uses fallback directories to
4576 bootstrap when it doesn't yet have up-to-date directory
4577 information. Closes ticket 24801.
4578 - Make the default DirAuthorityFallbackRate 0.1, so that clients
4579 prefer to bootstrap from fallback directory mirrors. This is a
4580 follow-up to 24679, which removed weights from the default
4581 fallbacks. Implements ticket 24681.
4583 o Minor features (geoip):
4584 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
4587 o Minor features (linux seccomp2 sandbox):
4588 - Update the sandbox rules so that they should now work correctly
4589 with Glibc 2.26. Closes ticket 24315.
4591 o Minor bugfix (channel connection):
4592 - Use the actual observed address of an incoming relay connection,
4593 not the canonical address of the relay from its descriptor, when
4594 making decisions about how to handle the incoming connection.
4595 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
4597 o Minor bugfix (directory authority):
4598 - Directory authorities, when refusing a descriptor from a rejected
4599 relay, now explicitly tell the relay (in its logs) to set a valid
4600 ContactInfo address and contact the bad-relays@ mailing list.
4601 Fixes bug 25170; bugfix on 0.2.9.1.
4603 o Minor bugfixes (address selection):
4604 - When the fascist_firewall_choose_address_ functions don't find a
4605 reachable address, set the returned address to the null address
4606 and port. This is a precautionary measure, because some callers do
4607 not check the return value. Fixes bug 24736; bugfix
4610 o Minor bugfixes (compilation):
4611 - Fix a signed/unsigned comparison warning introduced by our fix to
4612 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
4614 o Minor bugfixes (control port, linux seccomp2 sandbox):
4615 - Avoid a crash when attempting to use the seccomp2 sandbox together
4616 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
4619 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
4620 - Fix a possible crash on malformed consensus. If a consensus had
4621 contained an unparseable protocol line, it could have made clients
4622 and relays crash with a null-pointer exception. To exploit this
4623 issue, however, an attacker would need to be able to subvert the
4624 directory authority system. Fixes bug 25251; bugfix on
4625 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
4627 o Minor bugfixes (memory usage):
4628 - When queuing DESTROY cells on a channel, only queue the circuit-id
4629 and reason fields: not the entire 514-byte cell. This fix should
4630 help mitigate any bugs or attacks that fill up these queues, and
4631 free more RAM for other uses. Fixes bug 24666; bugfix
4634 o Minor bugfixes (network layer):
4635 - When closing a connection via close_connection_immediately(), we
4636 mark it as "not blocked on bandwidth", to prevent later calls from
4637 trying to unblock it, and give it permission to read. This fixes a
4638 backtrace warning that can happen on relays under various
4639 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
4641 o Minor bugfixes (OSX):
4642 - Don't exit the Tor process if setrlimit() fails to change the file
4643 limit (which can happen sometimes on some versions of OSX). Fixes
4644 bug 21074; bugfix on 0.0.9pre5.
4646 o Minor bugfixes (path selection):
4647 - When selecting relays by bandwidth, avoid a rounding error that
4648 could sometimes cause load to be imbalanced incorrectly.
4649 Previously, we would always round upwards; now, we round towards
4650 the nearest integer. This had the biggest effect when a relay's
4651 weight adjustments should have given it weight 0, but it got
4652 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
4653 - When calculating the fraction of nodes that have descriptors, and
4654 all nodes in the network have zero bandwidths, count the number of
4655 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
4656 - Actually log the total bandwidth in compute_weighted_bandwidths().
4657 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
4659 o Minor bugfixes (portability, msvc):
4660 - Fix a bug in the bit-counting parts of our timing-wheel code on
4661 MSVC. (Note that MSVC is still not a supported build platform, due
4662 to cryptographic timing channel risks.) Fixes bug 24633; bugfix
4665 o Minor bugfixes (relay):
4666 - Make the internal channel_is_client() function look at what sort
4667 of connection handshake the other side used, rather than whether
4668 the other side ever sent a create_fast cell to us. Backports part
4669 of the fixes from bugs 22805 and 24898.
4671 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
4672 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
4674 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
4675 bugfix on 0.2.9.4-alpha.
4678 Changes in version 0.3.2.10 - 2018-03-03
4679 Tor 0.3.2.10 is the second stable release in the 0.3.2 series. It
4680 backports a number of bugfixes, including important fixes for security
4683 It includes an important security fix for a remote crash attack
4684 against directory authorities, tracked as TROVE-2018-001.
4686 Additionally, it backports a fix for a bug whose severity we have
4687 upgraded: Bug 24700, which was fixed in 0.3.3.2-alpha, can be remotely
4688 triggered in order to crash relays with a use-after-free pattern. As
4689 such, we are now tracking that bug as TROVE-2018-002 and
4690 CVE-2018-0491, and backporting it to earlier releases. This bug
4691 affected versions 0.3.2.1-alpha through 0.3.2.9, as well as version
4694 This release also backports our new system for improved resistance to
4695 denial-of-service attacks against relays.
4697 This release also fixes several minor bugs and annoyances from
4700 Relays running 0.3.2.x SHOULD upgrade to one of the versions released
4701 today, for the fix to TROVE-2018-002. Directory authorities should
4702 also upgrade. (Relays on earlier versions might want to update too for
4703 the DoS mitigations.)
4705 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
4706 - Fix a protocol-list handling bug that could be used to remotely crash
4707 directory authorities with a null-pointer exception. Fixes bug 25074;
4708 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
4711 o Major bugfixes (scheduler, KIST, denial-of-service, backport from 0.3.3.2-alpha):
4712 - Avoid adding the same channel twice in the KIST scheduler pending
4713 list, which could lead to remote denial-of-service use-after-free
4714 attacks against relays. Fixes bug 24700; bugfix on 0.3.2.1-alpha.
4716 o Major features (denial-of-service mitigation, backport from 0.3.3.2-alpha):
4717 - Give relays some defenses against the recent network overload. We
4718 start with three defenses (default parameters in parentheses).
4719 First: if a single client address makes too many concurrent
4720 connections (>100), hang up on further connections. Second: if a
4721 single client address makes circuits too quickly (more than 3 per
4722 second, with an allowed burst of 90) while also having too many
4723 connections open (3), refuse new create cells for the next while
4724 (1-2 hours). Third: if a client asks to establish a rendezvous
4725 point to you directly, ignore the request. These defenses can be
4726 manually controlled by new torrc options, but relays will also
4727 take guidance from consensus parameters, so there's no need to
4728 configure anything manually. Implements ticket 24902.
4730 o Major bugfixes (onion services, retry behavior, backport from 0.3.3.1-alpha):
4731 - Fix an "off by 2" error in counting rendezvous failures on the
4732 onion service side. While we thought we would stop the rendezvous
4733 attempt after one failed circuit, we were actually making three
4734 circuit attempts before giving up. Now switch to a default of 2,
4735 and allow the consensus parameter "hs_service_max_rdv_failures" to
4736 override. Fixes bug 24895; bugfix on 0.0.6.
4737 - New-style (v3) onion services now obey the "max rendezvous circuit
4738 attempts" logic. Previously they would make as many rendezvous
4739 circuit attempts as they could fit in the MAX_REND_TIMEOUT second
4740 window before giving up. Fixes bug 24894; bugfix on 0.3.2.1-alpha.
4742 o Major bugfixes (protocol versions, backport from 0.3.3.2-alpha):
4743 - Add Link protocol version 5 to the supported protocols list. Fixes
4744 bug 25070; bugfix on 0.3.1.1-alpha.
4746 o Major bugfixes (relay, backport from 0.3.3.1-alpha):
4747 - Fix a set of false positives where relays would consider
4748 connections to other relays as being client-only connections (and
4749 thus e.g. deserving different link padding schemes) if those
4750 relays fell out of the consensus briefly. Now we look only at the
4751 initial handshake and whether the connection authenticated as a
4752 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
4754 o Major bugfixes (scheduler, consensus, backport from 0.3.3.2-alpha):
4755 - The scheduler subsystem was failing to promptly notice changes in
4756 consensus parameters, making it harder to switch schedulers
4757 network-wide. Fixes bug 24975; bugfix on 0.3.2.1-alpha.
4759 o Minor features (denial-of-service avoidance, backport from 0.3.3.2-alpha):
4760 - Make our OOM handler aware of the geoip client history cache so it
4761 doesn't fill up the memory. This check is important for IPv6 and
4762 our DoS mitigation subsystem. Closes ticket 25122.
4764 o Minor features (compatibility, OpenSSL, backport from 0.3.3.3-alpha):
4765 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
4766 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
4767 since they neither disabled TLS 1.3 nor enabled any of the
4768 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
4769 Closes ticket 24978.
4771 o Minor features (geoip):
4772 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
4775 o Minor features (logging, diagnostic, backport from 0.3.3.2-alpha):
4776 - When logging a failure to create an onion service's descriptor,
4777 also log what the problem with the descriptor was. Diagnostic
4780 o Minor bugfix (channel connection, backport from 0.3.3.2-alpha):
4781 - Use the actual observed address of an incoming relay connection,
4782 not the canonical address of the relay from its descriptor, when
4783 making decisions about how to handle the incoming connection.
4784 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
4786 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
4787 - Fix a possible crash on malformed consensus. If a consensus had
4788 contained an unparseable protocol line, it could have made clients
4789 and relays crash with a null-pointer exception. To exploit this
4790 issue, however, an attacker would need to be able to subvert the
4791 directory authority system. Fixes bug 25251; bugfix on
4792 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
4794 o Minor bugfix (directory authority, backport from 0.3.3.2-alpha):
4795 - Directory authorities, when refusing a descriptor from a rejected
4796 relay, now explicitly tell the relay (in its logs) to set a valid
4797 ContactInfo address and contact the bad-relays@ mailing list.
4798 Fixes bug 25170; bugfix on 0.2.9.1.
4800 o Minor bugfixes (build, rust, backport from 0.3.3.1-alpha):
4801 - When building with Rust on OSX, link against libresolv, to work
4802 around the issue at https://github.com/rust-lang/rust/issues/46797.
4803 Fixes bug 24652; bugfix on 0.3.1.1-alpha.
4805 o Minor bugfixes (onion services, backport from 0.3.3.2-alpha):
4806 - Remove a BUG() statement when a client fetches an onion descriptor
4807 that has a lower revision counter than the one in its cache. This
4808 can happen in normal circumstances due to HSDir desync. Fixes bug
4809 24976; bugfix on 0.3.2.1-alpha.
4811 o Minor bugfixes (logging, backport from 0.3.3.2-alpha):
4812 - Don't treat inability to store a cached consensus object as a bug:
4813 it can happen normally when we are out of disk space. Fixes bug
4814 24859; bugfix on 0.3.1.1-alpha.
4816 o Minor bugfixes (performance, fragile-hardening, backport from 0.3.3.1-alpha):
4817 - Improve the performance of our consensus-diff application code
4818 when Tor is built with the --enable-fragile-hardening option set.
4819 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
4821 o Minor bugfixes (OSX, backport from 0.3.3.1-alpha):
4822 - Don't exit the Tor process if setrlimit() fails to change the file
4823 limit (which can happen sometimes on some versions of OSX). Fixes
4824 bug 21074; bugfix on 0.0.9pre5.
4826 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
4827 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
4829 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
4830 bugfix on 0.2.9.4-alpha.
4832 o Minor bugfixes (testing, backport from 0.3.3.1-alpha):
4833 - Fix a memory leak in the scheduler/loop_kist unit test. Fixes bug
4834 25005; bugfix on 0.3.2.7-rc.
4836 o Minor bugfixes (v3 onion services, backport from 0.3.3.2-alpha):
4837 - Look at the "HSRend" protocol version, not the "HSDir" protocol
4838 version, when deciding whether a consensus entry can support the
4839 v3 onion service protocol as a rendezvous point. Fixes bug 25105;
4840 bugfix on 0.3.2.1-alpha.
4842 o Code simplification and refactoring (backport from 0.3.3.3-alpha):
4843 - Update the "rust dependencies" submodule to be a project-level
4844 repository, rather than a user repository. Closes ticket 25323.
4846 o Documentation (backport from 0.3.3.1-alpha)
4847 - Document that operators who run more than one relay or bridge are
4848 expected to set MyFamily and ContactInfo correctly. Closes
4852 Changes in version 0.3.3.3-alpha - 2018-03-03
4853 Tor 0.3.3.3-alpha is the third alpha release for the 0.3.3.x series.
4854 It includes an important security fix for a remote crash attack
4855 against directory authorities tracked as TROVE-2018-001.
4857 Additionally, with this release, we are upgrading the severity of a
4858 bug fixed in 0.3.3.2-alpha. Bug 24700, which was fixed in
4859 0.3.3.2-alpha, can be remotely triggered in order to crash relays with
4860 a use-after-free pattern. As such, we are now tracking that bug as
4861 TROVE-2018-002 and CVE-2018-0491. This bug affected versions
4862 0.3.2.1-alpha through 0.3.2.9, as well as 0.3.3.1-alpha.
4864 This release also fixes several minor bugs and annoyances from
4867 Relays running 0.3.2.x should upgrade to one of the versions released
4868 today, for the fix to TROVE-2018-002. Directory authorities should
4869 also upgrade. (Relays on earlier versions might want to update too for
4870 the DoS mitigations.)
4872 o Major bugfixes (denial-of-service, directory authority):
4873 - Fix a protocol-list handling bug that could be used to remotely crash
4874 directory authorities with a null-pointer exception. Fixes bug 25074;
4875 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
4878 o Minor features (compatibility, OpenSSL):
4879 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
4880 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
4881 since they neither disabled TLS 1.3 nor enabled any of the
4882 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
4883 Closes ticket 24978.
4885 o Minor features (logging):
4886 - Clarify the log messages produced when getrandom() or a related
4887 entropy-generation mechanism gives an error. Closes ticket 25120.
4889 o Minor features (testing):
4890 - Add a "make test-rust" target to run the rust tests only. Closes
4893 o Minor bugfixes (denial-of-service):
4894 - Fix a possible crash on malformed consensus. If a consensus had
4895 contained an unparseable protocol line, it could have made clients
4896 and relays crash with a null-pointer exception. To exploit this
4897 issue, however, an attacker would need to be able to subvert the
4898 directory authority system. Fixes bug 25251; bugfix on
4899 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
4901 o Minor bugfixes (DoS mitigation):
4902 - Add extra safety checks when refilling the circuit creation bucket
4903 to ensure we never set a value above the allowed maximum burst.
4904 Fixes bug 25202; bugfix on 0.3.3.2-alpha.
4905 - When a new consensus arrives, don't update our DoS-mitigation
4906 parameters if we aren't a public relay. Fixes bug 25223; bugfix
4909 o Minor bugfixes (man page, SocksPort):
4910 - Remove dead code from the old "SocksSocket" option, and rename
4911 SocksSocketsGroupWritable to UnixSocksGroupWritable. The old option
4912 still works, but is deprecated. Fixes bug 24343; bugfix on 0.2.6.3.
4914 o Minor bugfixes (performance):
4915 - Reduce the number of circuits that will be opened at once during
4916 the circuit build timeout phase. This is done by increasing the
4917 idle timeout to 3 minutes, and lowering the maximum number of
4918 concurrent learning circuits to 10. Fixes bug 24769; bugfix
4921 o Minor bugfixes (spec conformance):
4922 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
4924 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
4925 bugfix on 0.2.9.4-alpha.
4927 o Minor bugfixes (spec conformance, rust):
4928 - Resolve a denial-of-service issue caused by an infinite loop in
4929 the rust protover code. Fixes bug 25250, bugfix on 0.3.3.1-alpha.
4930 Also tracked as TROVE-2018-003.
4932 o Code simplification and refactoring:
4933 - Update the "rust dependencies" submodule to be a project-level
4934 repository, rather than a user repository. Closes ticket 25323.
4937 Changes in version 0.3.3.2-alpha - 2018-02-10
4938 Tor 0.3.3.2-alpha is the second alpha in the 0.3.3.x series. It
4939 introduces a mechanism to handle the high loads that many relay
4940 operators have been reporting recently. It also fixes several bugs in
4941 older releases. If this new code proves reliable, we plan to backport
4942 it to older supported release series.
4944 o Major features (denial-of-service mitigation):
4945 - Give relays some defenses against the recent network overload. We
4946 start with three defenses (default parameters in parentheses).
4947 First: if a single client address makes too many concurrent
4948 connections (>100), hang up on further connections. Second: if a
4949 single client address makes circuits too quickly (more than 3 per
4950 second, with an allowed burst of 90) while also having too many
4951 connections open (3), refuse new create cells for the next while
4952 (1-2 hours). Third: if a client asks to establish a rendezvous
4953 point to you directly, ignore the request. These defenses can be
4954 manually controlled by new torrc options, but relays will also
4955 take guidance from consensus parameters, so there's no need to
4956 configure anything manually. Implements ticket 24902.
4958 o Major bugfixes (netflow padding):
4959 - Stop adding unneeded channel padding right after we finish
4960 flushing to a connection that has been trying to flush for many
4961 seconds. Instead, treat all partial or complete flushes as
4962 activity on the channel, which will defer the time until we need
4963 to add padding. This fix should resolve confusing and scary log
4964 messages like "Channel padding timeout scheduled 221453ms in the
4965 past." Fixes bug 22212; bugfix on 0.3.1.1-alpha.
4967 o Major bugfixes (protocol versions):
4968 - Add Link protocol version 5 to the supported protocols list. Fixes
4969 bug 25070; bugfix on 0.3.1.1-alpha.
4971 o Major bugfixes (scheduler, consensus):
4972 - The scheduler subsystem was failing to promptly notice changes in
4973 consensus parameters, making it harder to switch schedulers
4974 network-wide. Fixes bug 24975; bugfix on 0.3.2.1-alpha.
4976 o Minor features (denial-of-service avoidance):
4977 - Make our OOM handler aware of the geoip client history cache so it
4978 doesn't fill up the memory. This check is important for IPv6 and
4979 our DoS mitigation subsystem. Closes ticket 25122.
4981 o Minor features (directory authority):
4982 - When directory authorities are unable to add signatures to a
4983 pending consensus, log the reason why. Closes ticket 24849.
4985 o Minor features (geoip):
4986 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
4989 o Minor features (logging, diagnostic):
4990 - When logging a failure to create an onion service's descriptor,
4991 also log what the problem with the descriptor was. Diagnostic for
4994 o Minor bugfix (channel connection):
4995 - Use the actual observed address of an incoming relay connection,
4996 not the canonical address of the relay from its descriptor, when
4997 making decisions about how to handle the incoming connection.
4998 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
5000 o Minor bugfix (directory authority):
5001 - Directory authorities, when refusing a descriptor from a rejected
5002 relay, now explicitly tell the relay (in its logs) to set a valid
5003 ContactInfo address and contact the bad-relays@ mailing list.
5004 Fixes bug 25170; bugfix on 0.2.9.1.
5006 o Minor bugfixes (all versions of Tor):
5007 - Use the "misspell" tool to detect and fix typos throughout the
5008 source code. Fixes bug 23650; bugfix on various versions of Tor.
5009 Patch from Deepesh Pathak.
5011 o Minor bugfixes (circuit, cannibalization):
5012 - Don't cannibalize preemptively-built circuits if we no longer
5013 recognize their first hop. This situation can happen if our Guard
5014 relay went off the consensus after the circuit was created. Fixes
5015 bug 24469; bugfix on 0.0.6.
5017 o Minor bugfixes (correctness):
5018 - Remove a nonworking, unnecessary check to see whether a circuit
5019 hop's identity digest was set when the circuit failed. Fixes bug
5020 24927; bugfix on 0.2.4.4-alpha.
5022 o Minor bugfixes (logging):
5023 - Don't treat inability to store a cached consensus object as a bug:
5024 it can happen normally when we are out of disk space. Fixes bug
5025 24859; bugfix on 0.3.1.1-alpha.
5026 - Fix a (mostly harmless) race condition when invoking
5027 LOG_PROTOCOL_WARN message from a subthread while the torrc options
5028 are changing. Fixes bug 23954; bugfix on 0.1.1.9-alpha.
5030 o Minor bugfixes (onion services):
5031 - Remove a BUG() statement when a client fetches an onion descriptor
5032 that has a lower revision counter than the one in its cache. This
5033 can happen in normal circumstances due to HSDir desync. Fixes bug
5034 24976; bugfix on 0.3.2.1-alpha.
5035 - If we are configured to offer a single onion service, don't log
5036 long-term established one hop rendezvous points in the heartbeat.
5037 Fixes bug 25116; bugfix on 0.2.9.6-rc.
5039 o Minor bugfixes (performance):
5040 - Avoid calling protocol_list_supports_protocol() from inside tight
5041 loops when running with cached routerinfo_t objects. Instead,
5042 summarize the relevant protocols as flags in the routerinfo_t, as
5043 we do for routerstatus_t objects. This change simplifies our code
5044 a little, and saves a large amount of short-term memory allocation
5045 operations. Fixes bug 25008; bugfix on 0.2.9.4-alpha.
5047 o Minor bugfixes (Rust FFI):
5048 - Fix a minor memory leak which would happen whenever the C code
5049 would call the Rust implementation of
5050 protover_get_supported_protocols(). This was due to the C version
5051 returning a static string, whereas the Rust version newly allocated
5052 a CString to pass across the FFI boundary. Consequently, the C
5053 code was not expecting to need to free() what it was given. Fixes
5054 bug 25127; bugfix on 0.3.2.1-alpha.
5056 o Minor bugfixes (scheduler, KIST):
5057 - Avoid adding the same channel twice in the KIST scheduler pending
5058 list, which would waste CPU cycles. Fixes bug 24700; bugfix
5061 o Minor bugfixes (unit test, monotonic time):
5062 - Increase a constant (1msec to 10msec) in the monotonic time test
5063 that makes sure the nsec/usec/msec times read are synchronized.
5064 This change was needed to accommodate slow systems like armel or
5065 when the clock_gettime() is not a VDSO on the running kernel.
5066 Fixes bug 25113; bugfix on 0.2.9.1.
5068 o Minor bugfixes (v3 onion services):
5069 - Look at the "HSRend" protocol version, not the "HSDir" protocol
5070 version, when deciding whether a consensus entry can support the
5071 v3 onion service protocol as a rendezvous point. Fixes bug 25105;
5072 bugfix on 0.3.2.1-alpha.
5074 o Code simplification and refactoring:
5075 - Remove the unused nodelist_recompute_all_hsdir_indices(). Closes
5077 - Remove a series of counters used to track circuit extend attempts
5078 and connection status but that in reality we aren't using for
5079 anything other than stats logged by a SIGUSR1 signal. Closes
5082 o Documentation (man page):
5083 - The HiddenServiceVersion torrc option accepts only one number:
5084 either version 2 or 3. Closes ticket 25026; bugfix
5088 Changes in version 0.3.3.1-alpha - 2018-01-25
5089 Tor 0.3.3.1-alpha is the first release in the 0.3.3.x series. It adds
5090 several new features to Tor, including several improvements to
5091 bootstrapping, and support for an experimental "vanguards" feature to
5092 resist guard discovery attacks. This series also includes better
5093 support for applications that need to embed Tor or manage v3
5096 o Major features (embedding):
5097 - There is now a documented stable API for programs that need to
5098 embed Tor. See tor_api.h for full documentation and known bugs.
5099 Closes ticket 23684.
5100 - Tor now has support for restarting in the same process.
5101 Controllers that run Tor using the "tor_api.h" interface can now
5102 restart Tor after Tor has exited. This support is incomplete,
5103 however: we fixed crash bugs that prevented it from working at
5104 all, but many bugs probably remain, including a possibility of
5105 security issues. Implements ticket 24581.
5107 o Major features (IPv6, directory documents):
5108 - Add consensus method 27, which adds IPv6 ORPorts to the microdesc
5109 consensus. This information makes it easier for IPv6 clients to
5110 bootstrap and choose reachable entry guards. Implements ticket 23826.
5111 - Add consensus method 28, which removes IPv6 ORPorts from
5112 microdescriptors. Now that the consensus contains IPv6 ORPorts, they
5113 are redundant in microdescs. This change will be used by Tor clients
5114 on 0.2.8.x and later. (That is to say, with all Tor clients that
5115 have IPv6 bootstrap and guard support.) Implements ticket 23828.
5116 - Expand the documentation for AuthDirHasIPv6Connectivity when it is
5117 set by different numbers of authorities. Fixes 23870
5120 o Major features (onion service v3, control port):
5121 - The control port now supports commands and events for v3 onion
5122 services. It is now possible to create ephemeral v3 services using
5123 ADD_ONION. Additionally, several events (HS_DESC, HS_DESC_CONTENT,
5124 CIRC and CIRC_MINOR) and commands (GETINFO, HSPOST, ADD_ONION and
5125 DEL_ONION) have been extended to support v3 onion services. Closes
5126 ticket 20699; implements proposal 284.
5128 o Major features (onion services):
5129 - Provide torrc options to pin the second and third hops of onion
5130 service circuits to a list of nodes. The option HSLayer2Guards
5131 pins the second hop, and the option HSLayer3Guards pins the third
5132 hop. These options are for use in conjunction with experiments
5133 with "vanguards" for preventing guard enumeration attacks. Closes
5136 o Major features (rust, portability, experimental):
5137 - Tor now ships with an optional implementation of one of its
5138 smaller modules (protover.c) in the Rust programming language. To
5139 try it out, install a Rust build environment, and configure Tor
5140 with "--enable-rust --enable-cargo-online-mode". This should not
5141 cause any user-visible changes, but should help us gain more
5142 experience with Rust, and plan future Rust integration work.
5143 Implementation by Chelsea Komlo. Closes ticket 22840.
5145 o Minor features (storage, configuration):
5146 - Users can store cached directory documents somewhere other than
5147 the DataDirectory by using the CacheDirectory option. Similarly,
5148 the storage location for relay's keys can be overridden with the
5149 KeyDirectory option. Closes ticket 22703.
5151 o Major features (v3 onion services, ipv6):
5152 - When v3 onion service clients send introduce cells, they now
5153 include the IPv6 address of the rendezvous point, if it has one.
5154 Current v3 onion services running 0.3.2 ignore IPv6 addresses, but
5155 in future Tor versions, IPv6-only v3 single onion services will be
5156 able to use IPv6 addresses to connect directly to the rendezvous
5157 point. Closes ticket 23577. Patch by Neel Chauhan.
5159 o Major bugfixes (onion services, retry behavior):
5160 - Fix an "off by 2" error in counting rendezvous failures on the
5161 onion service side. While we thought we would stop the rendezvous
5162 attempt after one failed circuit, we were actually making three
5163 circuit attempts before giving up. Now switch to a default of 2,
5164 and allow the consensus parameter "hs_service_max_rdv_failures" to
5165 override. Fixes bug 24895; bugfix on 0.0.6.
5166 - New-style (v3) onion services now obey the "max rendezvous circuit
5167 attempts" logic. Previously they would make as many rendezvous
5168 circuit attempts as they could fit in the MAX_REND_TIMEOUT second
5169 window before giving up. Fixes bug 24894; bugfix on 0.3.2.1-alpha.
5171 o Major bugfixes (relays):
5172 - Fix a set of false positives where relays would consider
5173 connections to other relays as being client-only connections (and
5174 thus e.g. deserving different link padding schemes) if those
5175 relays fell out of the consensus briefly. Now we look only at the
5176 initial handshake and whether the connection authenticated as a
5177 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
5179 o Minor feature (IPv6):
5180 - Make IPv6-only clients wait for microdescs for relays, even if we
5181 were previously using descriptors (or were using them as a bridge)
5182 and have a cached descriptor for them. Implements ticket 23827.
5183 - When a consensus has IPv6 ORPorts, make IPv6-only clients use
5184 them, rather than waiting to download microdescriptors.
5185 Implements ticket 23827.
5187 o Minor features (cleanup):
5188 - Tor now deletes the CookieAuthFile and ExtORPortCookieAuthFile
5189 when it stops. Closes ticket 23271.
5191 o Minor features (defensive programming):
5192 - Most of the functions in Tor that free objects have been replaced
5193 with macros that free the objects and set the corresponding
5194 pointers to NULL. This change should help prevent a large class of
5195 dangling pointer bugs. Closes ticket 24337.
5196 - Where possible, the tor_free() macro now only evaluates its input
5197 once. Part of ticket 24337.
5198 - Check that microdesc ed25519 ids are non-zero in
5199 node_get_ed25519_id() before returning them. Implements ticket
5200 24001, patch by "aruna1234".
5202 o Minor features (embedding):
5203 - Tor can now start with a preauthenticated control connection
5204 created by the process that launched it. This feature is meant for
5205 use by programs that want to launch and manage a Tor process
5206 without allowing other programs to manage it as well. For more
5207 information, see the __OwningControllerFD option documented in
5208 control-spec.txt. Closes ticket 23900.
5209 - On most errors that would cause Tor to exit, it now tries to
5210 return from the tor_main() function, rather than calling the
5211 system exit() function. Most users won't notice a difference here,
5212 but it should be significant for programs that run Tor inside
5213 a separate thread: they should now be able to survive Tor's exit
5214 conditions rather than having Tor shut down the entire process.
5215 Closes ticket 23848.
5216 - Applications that want to embed Tor can now tell Tor not to
5217 register any of its own POSIX signal handlers, using the
5218 __DisableSignalHandlers option. Closes ticket 24588.
5220 o Minor features (fallback directory list):
5221 - Avoid selecting fallbacks that change their IP addresses too
5222 often. Select more fallbacks by ignoring the Guard flag, and
5223 allowing lower cutoffs for the Running and V2Dir flags. Also allow
5224 a lower bandwidth, and a higher number of fallbacks per operator
5225 (5% of the list). Implements ticket 24785.
5226 - Update the fallback whitelist and blacklist based on opt-ins and
5227 relay changes. Closes tickets 22321, 24678, 22527, 24135,
5230 o Minor features (fallback directory mirror configuration):
5231 - Add a nickname to each fallback in a C comment. This makes it
5232 easier for operators to find their relays, and allows stem to use
5233 nicknames to identify fallbacks. Implements ticket 24600.
5234 - Add a type and version header to the fallback directory mirror
5235 file. Also add a delimiter to the end of each fallback entry. This
5236 helps external parsers like stem and Relay Search. Implements
5238 - Add an extrainfo cache flag for each fallback in a C comment. This
5239 allows stem to use fallbacks to fetch extra-info documents, rather
5240 than using authorities. Implements ticket 22759.
5241 - Add the generateFallbackDirLine.py script for automatically
5242 generating fallback directory mirror lines from relay fingerprints.
5243 No more typos! Add the lookupFallbackDirContact.py script for
5244 automatically looking up operator contact info from relay
5245 fingerprints. Implements ticket 24706, patch by teor and atagar.
5246 - Reject any fallback directory mirror that serves an expired
5247 consensus. Implements ticket 20942, patch by "minik".
5248 - Remove commas and equals signs from external string inputs to the
5249 fallback list. This avoids format confusion attacks. Implements
5251 - Remove the "weight=10" line from fallback directory mirror
5252 entries. Ticket 24681 will maintain the current fallback weights
5253 by changing Tor's default fallback weight to 10. Implements
5255 - Stop logging excessive information about fallback netblocks.
5256 Implements ticket 24791.
5258 o Minor features (forward-compatibility):
5259 - If a relay supports some link authentication protocol that we do
5260 not recognize, then include that relay's ed25519 key when telling
5261 other relays to extend to it. Previously, we treated future
5262 versions as if they were too old to support ed25519 link
5263 authentication. Closes ticket 20895.
5265 o Minor features (heartbeat):
5266 - Add onion service information to our heartbeat logs, displaying
5267 stats about the activity of configured onion services. Closes
5270 o Minor features (instrumentation, development):
5271 - Add the MainloopStats option to allow developers to get
5272 instrumentation information from the main event loop via the
5273 heartbeat messages. We hope to use this to improve Tor's behavior
5274 when it's trying to sleep. Closes ticket 24605.
5276 o Minor features (log messages):
5277 - Improve a warning message that happens when we fail to re-parse an
5278 old router because of an expired certificate. Closes ticket 20020.
5279 - Make the log more quantitative when we hit MaxMemInQueues
5280 threshold exposing some values. Closes ticket 24501.
5282 o Minor features (logging, android):
5283 - Added support for the Android logging subsystem. Closes
5286 o Minor features (performance):
5287 - Support predictive circuit building for onion service circuits
5288 with multiple layers of guards. Closes ticket 23101.
5289 - Use stdatomic.h where available, rather than mutexes, to implement
5290 atomic_counter_t. Closes ticket 23953.
5292 o Minor features (performance, 32-bit):
5293 - Improve performance on 32-bit systems by avoiding 64-bit division
5294 when calculating the timestamp in milliseconds for channel padding
5295 computations. Implements ticket 24613.
5296 - Improve performance on 32-bit systems by avoiding 64-bit division
5297 when timestamping cells and buffer chunks for OOM calculations.
5298 Implements ticket 24374.
5300 o Minor features (performance, OSX, iOS):
5301 - Use the mach_approximate_time() function (when available) to
5302 implement coarse monotonic time. Having a coarse time function
5303 should avoid a large number of system calls, and improve
5304 performance slightly, especially under load. Closes ticket 24427.
5306 o Minor features (performance, windows):
5307 - Improve performance on Windows Vista and Windows 7 by adjusting
5308 TCP send window size according to the recommendation from
5309 SIO_IDEAL_SEND_BACKLOG_QUERY. Closes ticket 22798. Patch
5312 o Major features (relay):
5313 - Implement an option, ReducedExitPolicy, to allow an Tor exit relay
5314 operator to use a more reasonable ("reduced") exit policy, rather
5315 than the default one. If you want to run an exit node without
5316 thinking too hard about which ports to allow, this one is for you.
5317 Closes ticket 13605. Patch from Neel Chauhan.
5319 o Minor features (testing, debugging, embedding):
5320 - For development purposes, Tor now has a mode in which it runs for
5321 a few seconds, then stops, and starts again without exiting the
5322 process. This mode is meant to help us debug various issues with
5323 ticket 23847. To use this feature, compile with
5324 --enable-restart-debugging, and set the TOR_DEBUG_RESTART
5325 environment variable. This is expected to crash a lot, and is
5326 really meant for developers only. It will likely be removed in a
5327 future release. Implements ticket 24583.
5329 o Minor bugfix (network IPv6 test):
5330 - Tor's test scripts now check if "ping -6 ::1" works when the user
5331 runs "make test-network-all". Fixes bug 24677; bugfix on
5332 0.2.9.3-alpha. Patch by "ffmancera".
5334 o Minor bugfixes (build, rust):
5335 - Fix output of autoconf checks to display success messages for Rust
5336 dependencies and a suitable rustc compiler version. Fixes bug
5337 24612; bugfix on 0.3.1.3-alpha.
5338 - When building with Rust on OSX, link against libresolv, to work
5339 around the issue at https://github.com/rust-lang/rust/issues/46797.
5340 Fixes bug 24652; bugfix on 0.3.1.1-alpha.
5341 - Don't pass the --quiet option to cargo: it seems to suppress some
5342 errors, which is not what we want to do when building. Fixes bug
5343 24518; bugfix on 0.3.1.7.
5344 - Build correctly when building from outside Tor's source tree with
5345 the TOR_RUST_DEPENDENCIES option set. Fixes bug 22768; bugfix
5348 o Minor bugfixes (directory authorities, IPv6):
5349 - When creating a routerstatus (vote) from a routerinfo (descriptor),
5350 set the IPv6 address to the unspecified IPv6 address, and
5351 explicitly initialize the port to zero. Fixes bug 24488; bugfix
5354 o Minor bugfixes (fallback directory mirrors):
5355 - Make updateFallbackDirs.py search harder for python. (Some OSs
5356 don't put it in /usr/bin.) Fixes bug 24708; bugfix
5359 o Minor bugfixes (hibernation, bandwidth accounting, shutdown):
5360 - When hibernating, close connections normally and allow them to
5361 flush. Fixes bug 23571; bugfix on 0.2.4.7-alpha. Also fixes
5363 - Do not attempt to launch self-reachability tests when entering
5364 hibernation. Fixes a case of bug 12062; bugfix on 0.0.9pre5.
5365 - Resolve several bugs related to descriptor fetching on bridge
5366 clients with bandwidth accounting enabled. (This combination is
5367 not recommended!) Fixes a case of bug 12062; bugfix
5369 - When hibernating, do not attempt to launch DNS checks. Fixes a
5370 case of bug 12062; bugfix on 0.1.2.2-alpha.
5371 - When hibernating, do not try to upload or download descriptors.
5372 Fixes a case of bug 12062; bugfix on 0.0.9pre5.
5374 o Minor bugfixes (IPv6, bridges):
5375 - Tor now always sets IPv6 preferences for bridges. Fixes bug 24573;
5376 bugfix on 0.2.8.2-alpha.
5377 - Tor now sets IPv6 address in the routerstatus as well as in the
5378 router descriptors when updating addresses for a bridge. Closes
5379 ticket 24572; bugfix on 0.2.4.5-alpha. Patch by "ffmancera".
5381 o Minor bugfixes (linux seccomp2 sandbox):
5382 - When running with the sandbox enabled, reload configuration files
5383 correctly even when %include was used. Previously we would crash.
5384 Fixes bug 22605; bugfix on 0.3.1. Patch from Daniel Pinto.
5386 o Minor bugfixes (memory leaks):
5387 - Avoid possible at-exit memory leaks related to use of Libevent's
5388 event_base_once() function. (This function tends to leak memory if
5389 the event_base is closed before the event fires.) Fixes bug 24584;
5390 bugfix on 0.2.8.1-alpha.
5391 - Fix a harmless memory leak in tor-resolve. Fixes bug 24582; bugfix
5394 o Minor bugfixes (OSX):
5395 - Don't exit the Tor process if setrlimit() fails to change the file
5396 limit (which can happen sometimes on some versions of OSX). Fixes
5397 bug 21074; bugfix on 0.0.9pre5.
5399 o Minor bugfixes (performance, fragile-hardening):
5400 - Improve the performance of our consensus-diff application code
5401 when Tor is built with the --enable-fragile-hardening option set.
5402 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
5404 o Minor bugfixes (performance, timeouts):
5405 - Consider circuits for timeout as soon as they complete a hop. This
5406 is more accurate than applying the timeout in
5407 circuit_expire_building() because that function is only called
5408 once per second, which is now too slow for typical timeouts on the
5409 current network. Fixes bug 23114; bugfix on 0.2.2.2-alpha.
5410 - Use onion service circuits (and other circuits longer than 3 hops)
5411 to calculate a circuit build timeout. Previously, Tor only
5412 calculated its build timeout based on circuits that planned to be
5413 exactly 3 hops long. With this change, we include measurements
5414 from all circuits at the point where they complete their third
5415 hop. Fixes bug 23100; bugfix on 0.2.2.2-alpha.
5417 o Minor bugfixes (testing):
5418 - Give out Exit flags in bootstrapping networks. Fixes bug 24137;
5419 bugfix on 0.2.3.1-alpha.
5420 - Fix a memory leak in the scheduler/loop_kist unit test. Fixes bug
5421 25005; bugfix on 0.3.2.7-rc.
5423 o Code simplification and refactoring:
5424 - Remove /usr/athena from search path in configure.ac. Closes
5426 - Remove duplicate code in node_has_curve25519_onion_key() and
5427 node_get_curve25519_onion_key(), and add a check for a zero
5428 microdesc curve25519 onion key. Closes ticket 23966, patch by
5429 "aruna1234" and teor.
5430 - Rewrite channel_rsa_id_group_set_badness to reduce temporary
5431 memory allocations with large numbers of OR connections (e.g.
5432 relays). Closes ticket 24119.
5433 - Separate the function that deletes ephemeral files when Tor
5435 - Small changes to Tor's buf_t API to make it suitable for use as a
5436 general-purpose safe string constructor. Closes ticket 22342.
5437 - Switch -Wnormalized=id to -Wnormalized=nfkc in configure.ac to
5438 avoid source code identifier confusion. Closes ticket 24467.
5439 - The tor_git_revision[] constant no longer needs to be redeclared
5440 by everything that links against the rest of Tor. Done as part of
5441 ticket 23845, to simplify our external API.
5442 - We make extend_info_from_node() use node_get_curve25519_onion_key()
5443 introduced in ticket 23577 to access the curve25519 public keys
5444 rather than accessing it directly. Closes ticket 23760. Patch by
5446 - Add a function to log channels' scheduler state changes to aid
5447 debugging efforts. Closes ticket 24531.
5450 - Add documentation on how to build tor with Rust dependencies
5451 without having to be online. Closes ticket 22907; bugfix
5453 - Clarify the behavior of RelayBandwidth{Rate,Burst} with client
5454 traffic. Closes ticket 24318.
5455 - Document that OutboundBindAddress doesn't apply to DNS requests.
5456 Closes ticket 22145. Patch from Aruna Maurya.
5457 - Document that operators who run more than one relay or bridge are
5458 expected to set MyFamily and ContactInfo correctly. Closes
5461 o Code simplification and refactoring (channels):
5462 - Remove the incoming and outgoing channel queues. These were never
5463 used, but still took up a step in our fast path.
5464 - The majority of the channel unit tests have been rewritten and the
5465 code coverage has now been raised to 83.6% for channel.c. Closes
5467 - Remove other dead code from the channel subsystem: All together,
5468 this cleanup has removed more than 1500 lines of code overall and
5469 adding very little except for unit test.
5471 o Code simplification and refactoring (circuit rendezvous):
5472 - Split the client-side rendezvous circuit lookup into two
5473 functions: one that returns only established circuits and another
5474 that returns all kinds of circuits. Closes ticket 23459.
5476 o Code simplification and refactoring (controller):
5477 - Make most of the variables in networkstatus_getinfo_by_purpose()
5478 const. Implements ticket 24489.
5481 Changes in version 0.3.2.9 - 2018-01-09
5482 Tor 0.3.2.9 is the first stable release in the 0.3.2 series.
5484 The 0.3.2 series includes our long-anticipated new onion service
5485 design, with numerous security features. (For more information, see
5486 our blog post at https://blog.torproject.org/fall-harvest.) We also
5487 have a new circuit scheduler algorithm for improved performance on
5488 relays everywhere (see https://blog.torproject.org/kist-and-tell),
5489 along with many smaller features and bugfixes.
5491 Per our stable release policy, we plan to support each stable release
5492 series for at least the next nine months, or for three months after
5493 the first stable release of the next series: whichever is longer. If
5494 you need a release with long-term support, we recommend that you stay
5495 with the 0.2.9 series.
5497 Below is a list of the changes since 0.3.2.8-rc. For a list of all
5498 changes since 0.3.1, see the ReleaseNotes file.
5500 o Minor features (fallback directory mirrors):
5501 - The fallback directory list has been re-generated based on the
5502 current status of the network. Tor uses fallback directories to
5503 bootstrap when it doesn't yet have up-to-date directory
5504 information. Closes ticket 24801.
5505 - Make the default DirAuthorityFallbackRate 0.1, so that clients
5506 prefer to bootstrap from fallback directory mirrors. This is a
5507 follow-up to 24679, which removed weights from the default
5508 fallbacks. Implements ticket 24681.
5510 o Minor features (geoip):
5511 - Update geoip and geoip6 to the January 5 2018 Maxmind GeoLite2
5514 o Minor bugfixes (address selection):
5515 - When the fascist_firewall_choose_address_ functions don't find a
5516 reachable address, set the returned address to the null address
5517 and port. This is a precautionary measure, because some callers do
5518 not check the return value. Fixes bug 24736; bugfix
5521 o Minor bugfixes (compilation):
5522 - Resolve a few shadowed-variable warnings in the onion service
5523 code. Fixes bug 24634; bugfix on 0.3.2.1-alpha.
5525 o Minor bugfixes (portability, msvc):
5526 - Fix a bug in the bit-counting parts of our timing-wheel code on
5527 MSVC. (Note that MSVC is still not a supported build platform, due
5528 to cryptographic timing channel risks.) Fixes bug 24633; bugfix
5532 Changes in version 0.3.2.8-rc - 2017-12-21
5533 Tor 0.3.2.8-rc fixes a pair of bugs in the KIST and KISTLite
5534 schedulers that had led servers under heavy load to overload their
5535 outgoing connections. All relay operators running earlier 0.3.2.x
5536 versions should upgrade. This version also includes a mitigation for
5537 over-full DESTROY queues leading to out-of-memory conditions: if it
5538 works, we will soon backport it to earlier release series.
5540 This is the second release candidate in the 0.3.2 series. If we find
5541 no new bugs or regression here, then the first stable 0.3.2 release
5542 will be nearly identical to this.
5544 o Major bugfixes (KIST, scheduler):
5545 - The KIST scheduler did not correctly account for data already
5546 enqueued in each connection's send socket buffer, particularly in
5547 cases when the TCP/IP congestion window was reduced between
5548 scheduler calls. This situation lead to excessive per-connection
5549 buffering in the kernel, and a potential memory DoS. Fixes bug
5550 24665; bugfix on 0.3.2.1-alpha.
5552 o Minor features (geoip):
5553 - Update geoip and geoip6 to the December 6 2017 Maxmind GeoLite2
5556 o Minor bugfixes (hidden service v3):
5557 - Bump hsdir_spread_store parameter from 3 to 4 in order to increase
5558 the probability of reaching a service for a client missing
5559 microdescriptors. Fixes bug 24425; bugfix on 0.3.2.1-alpha.
5561 o Minor bugfixes (memory usage):
5562 - When queuing DESTROY cells on a channel, only queue the circuit-id
5563 and reason fields: not the entire 514-byte cell. This fix should
5564 help mitigate any bugs or attacks that fill up these queues, and
5565 free more RAM for other uses. Fixes bug 24666; bugfix
5568 o Minor bugfixes (scheduler, KIST):
5569 - Use a sane write limit for KISTLite when writing onto a connection
5570 buffer instead of using INT_MAX and shoving as much as it can.
5571 Because the OOM handler cleans up circuit queues, we are better
5572 off at keeping them in that queue instead of the connection's
5573 buffer. Fixes bug 24671; bugfix on 0.3.2.1-alpha.
5576 Changes in version 0.3.2.7-rc - 2017-12-14
5577 Tor 0.3.2.7-rc fixes various bugs in earlier versions of Tor,
5578 including some that could affect reliability or correctness.
5580 This is the first release candidate in the 0.3.2 series. If we find no
5581 new bugs or regression here, then the first stable 0.3.2. release will
5582 be nearly identical to this.
5584 o Major bugfixes (circuit prediction):
5585 - Fix circuit prediction logic so that a client doesn't treat a port
5586 as being "handled" by a circuit if that circuit already has
5587 isolation settings on it. This change should make Tor clients more
5588 responsive by improving their chances of having a pre-created
5589 circuit ready for use when a request arrives. Fixes bug 18859;
5590 bugfix on 0.2.3.3-alpha.
5592 o Minor features (logging):
5593 - Provide better warnings when the getrandom() syscall fails. Closes
5596 o Minor features (portability):
5597 - Tor now compiles correctly on arm64 with libseccomp-dev installed.
5598 (It doesn't yet work with the sandbox enabled.) Closes
5601 o Minor bugfixes (bridge clients, bootstrap):
5602 - Retry directory downloads when we get our first bridge descriptor
5603 during bootstrap or while reconnecting to the network. Keep
5604 retrying every time we get a bridge descriptor, until we have a
5605 reachable bridge. Fixes part of bug 24367; bugfix on 0.2.0.3-alpha.
5606 - Stop delaying bridge descriptor fetches when we have cached bridge
5607 descriptors. Instead, only delay bridge descriptor fetches when we
5608 have at least one reachable bridge. Fixes part of bug 24367;
5609 bugfix on 0.2.0.3-alpha.
5610 - Stop delaying directory fetches when we have cached bridge
5611 descriptors. Instead, only delay bridge descriptor fetches when
5612 all our bridges are definitely unreachable. Fixes part of bug
5613 24367; bugfix on 0.2.0.3-alpha.
5615 o Minor bugfixes (compilation):
5616 - Fix a signed/unsigned comparison warning introduced by our fix to
5617 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
5619 o Minor bugfixes (correctness):
5620 - Fix several places in our codebase where a C compiler would be
5621 likely to eliminate a check, based on assuming that undefined
5622 behavior had not happened elsewhere in the code. These cases are
5623 usually a sign of redundant checking or dubious arithmetic. Found
5624 by Georg Koppen using the "STACK" tool from Wang, Zeldovich,
5625 Kaashoek, and Solar-Lezama. Fixes bug 24423; bugfix on various
5628 o Minor bugfixes (onion service v3):
5629 - Fix a race where an onion service would launch a new intro circuit
5630 after closing an old one, but fail to register it before freeing
5631 the previously closed circuit. This bug was making the service
5632 unable to find the established intro circuit and thus not upload
5633 its descriptor, thus making a service unavailable for up to 24
5634 hours. Fixes bug 23603; bugfix on 0.3.2.1-alpha.
5636 o Minor bugfixes (scheduler, KIST):
5637 - Properly set the scheduler state of an unopened channel in the
5638 KIST scheduler main loop. This prevents a harmless but annoying
5639 log warning. Fixes bug 24502; bugfix on 0.3.2.4-alpha.
5640 - Avoid a possible integer overflow when computing the available
5641 space on the TCP buffer of a channel. This had no security
5642 implications; but could make KIST allow too many cells on a
5643 saturated connection. Fixes bug 24590; bugfix on 0.3.2.1-alpha.
5644 - Downgrade to "info" a harmless warning about the monotonic time
5645 moving backwards: This can happen on platform not supporting
5646 monotonic time. Fixes bug 23696; bugfix on 0.3.2.1-alpha.
5649 Changes in version 0.3.2.6-alpha - 2017-12-01
5650 This version of Tor is the latest in the 0.3.2 alpha series. It
5651 includes fixes for several important security issues. All Tor users
5652 should upgrade to this release, or to one of the other releases coming
5655 o Major bugfixes (security):
5656 - Fix a denial of service bug where an attacker could use a
5657 malformed directory object to cause a Tor instance to pause while
5658 OpenSSL would try to read a passphrase from the terminal. (Tor
5659 instances run without a terminal, which is the case for most Tor
5660 packages, are not impacted.) Fixes bug 24246; bugfix on every
5661 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
5662 Found by OSS-Fuzz as testcase 6360145429790720.
5663 - Fix a denial of service issue where an attacker could crash a
5664 directory authority using a malformed router descriptor. Fixes bug
5665 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
5667 - When checking for replays in the INTRODUCE1 cell data for a
5668 (legacy) onion service, correctly detect replays in the RSA-
5669 encrypted part of the cell. We were previously checking for
5670 replays on the entire cell, but those can be circumvented due to
5671 the malleability of Tor's legacy hybrid encryption. This fix helps
5672 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
5673 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
5676 o Major bugfixes (security, onion service v2):
5677 - Fix a use-after-free error that could crash v2 Tor onion services
5678 when they failed to open circuits while expiring introduction
5679 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
5680 also tracked as TROVE-2017-013 and CVE-2017-8823.
5682 o Major bugfixes (security, relay):
5683 - When running as a relay, make sure that we never build a path
5684 through ourselves, even in the case where we have somehow lost the
5685 version of our descriptor appearing in the consensus. Fixes part
5686 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
5687 as TROVE-2017-012 and CVE-2017-8822.
5688 - When running as a relay, make sure that we never choose ourselves
5689 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
5690 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
5692 o Minor feature (relay statistics):
5693 - Change relay bandwidth reporting stats interval from 4 hours to 24
5694 hours in order to reduce the efficiency of guard discovery
5695 attacks. Fixes ticket 23856.
5697 o Minor features (directory authority):
5698 - Add an IPv6 address for the "bastet" directory authority. Closes
5701 o Minor bugfixes (client):
5702 - By default, do not enable storage of client-side DNS values. These
5703 values were unused by default previously, but they should not have
5704 been cached at all. Fixes bug 24050; bugfix on 0.2.6.3-alpha.
5707 Changes in version 0.3.1.9 - 2017-12-01:
5708 Tor 0.3.1.9 backports important security and stability fixes from the
5709 0.3.2 development series. All Tor users should upgrade to this
5710 release, or to another of the releases coming out today.
5712 o Major bugfixes (security, backport from 0.3.2.6-alpha):
5713 - Fix a denial of service bug where an attacker could use a
5714 malformed directory object to cause a Tor instance to pause while
5715 OpenSSL would try to read a passphrase from the terminal. (Tor
5716 instances run without a terminal, which is the case for most Tor
5717 packages, are not impacted.) Fixes bug 24246; bugfix on every
5718 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
5719 Found by OSS-Fuzz as testcase 6360145429790720.
5720 - Fix a denial of service issue where an attacker could crash a
5721 directory authority using a malformed router descriptor. Fixes bug
5722 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
5724 - When checking for replays in the INTRODUCE1 cell data for a
5725 (legacy) onion service, correctly detect replays in the RSA-
5726 encrypted part of the cell. We were previously checking for
5727 replays on the entire cell, but those can be circumvented due to
5728 the malleability of Tor's legacy hybrid encryption. This fix helps
5729 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
5730 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
5733 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
5734 - Fix a use-after-free error that could crash v2 Tor onion services
5735 when they failed to open circuits while expiring introduction
5736 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
5737 also tracked as TROVE-2017-013 and CVE-2017-8823.
5739 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
5740 - When running as a relay, make sure that we never build a path
5741 through ourselves, even in the case where we have somehow lost the
5742 version of our descriptor appearing in the consensus. Fixes part
5743 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
5744 as TROVE-2017-012 and CVE-2017-8822.
5745 - When running as a relay, make sure that we never choose ourselves
5746 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
5747 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
5749 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
5750 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
5751 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
5752 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
5753 identifying and finding a workaround to this bug and to Moritz,
5754 Arthur Edelstein, and Roger for helping to track it down and
5757 o Minor features (bridge):
5758 - Bridges now include notice in their descriptors that they are
5759 bridges, and notice of their distribution status, based on their
5760 publication settings. Implements ticket 18329. For more fine-
5761 grained control of how a bridge is distributed, upgrade to 0.3.2.x
5764 o Minor features (directory authority, backport from 0.3.2.6-alpha):
5765 - Add an IPv6 address for the "bastet" directory authority. Closes
5768 o Minor features (geoip):
5769 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
5772 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
5773 - Avoid unnecessary calls to directory_fetches_from_authorities() on
5774 relays, to prevent spurious address resolutions and descriptor
5775 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
5776 bugfix on in 0.2.8.1-alpha.
5778 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
5779 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
5780 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
5782 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
5783 - When a circuit is marked for close, do not attempt to package any
5784 cells for channels on that circuit. Previously, we would detect
5785 this condition lower in the call stack, when we noticed that the
5786 circuit had no attached channel, and log an annoying message.
5787 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
5789 o Minor bugfixes (onion service, backport from 0.3.2.5-alpha):
5790 - Rename the consensus parameter "hsdir-interval" to "hsdir_interval"
5791 so it matches dir-spec.txt. Fixes bug 24262; bugfix
5794 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
5795 - Avoid a crash when transitioning from client mode to bridge mode.
5796 Previously, we would launch the worker threads whenever our
5797 "public server" mode changed, but not when our "server" mode
5798 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
5801 Changes in version 0.3.0.13 - 2017-12-01
5802 Tor 0.3.0.13 backports important security and stability bugfixes from
5803 later Tor releases. All Tor users should upgrade to this release, or
5804 to another of the releases coming out today.
5806 Note: the Tor 0.3.0 series will no longer be supported after 26 Jan
5807 2018. If you need a release with long-term support, please stick with
5808 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
5810 o Major bugfixes (security, backport from 0.3.2.6-alpha):
5811 - Fix a denial of service bug where an attacker could use a
5812 malformed directory object to cause a Tor instance to pause while
5813 OpenSSL would try to read a passphrase from the terminal. (Tor
5814 instances run without a terminal, which is the case for most Tor
5815 packages, are not impacted.) Fixes bug 24246; bugfix on every
5816 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
5817 Found by OSS-Fuzz as testcase 6360145429790720.
5818 - Fix a denial of service issue where an attacker could crash a
5819 directory authority using a malformed router descriptor. Fixes bug
5820 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
5822 - When checking for replays in the INTRODUCE1 cell data for a
5823 (legacy) onion service, correctly detect replays in the RSA-
5824 encrypted part of the cell. We were previously checking for
5825 replays on the entire cell, but those can be circumvented due to
5826 the malleability of Tor's legacy hybrid encryption. This fix helps
5827 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
5828 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
5831 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
5832 - Fix a use-after-free error that could crash v2 Tor onion services
5833 when they failed to open circuits while expiring introduction
5834 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
5835 also tracked as TROVE-2017-013 and CVE-2017-8823.
5837 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
5838 - When running as a relay, make sure that we never build a path
5839 through ourselves, even in the case where we have somehow lost the
5840 version of our descriptor appearing in the consensus. Fixes part
5841 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
5842 as TROVE-2017-012 and CVE-2017-8822.
5843 - When running as a relay, make sure that we never choose ourselves
5844 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
5845 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
5847 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
5848 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
5849 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
5850 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
5851 identifying and finding a workaround to this bug and to Moritz,
5852 Arthur Edelstein, and Roger for helping to track it down and
5855 o Minor features (security, windows, backport from 0.3.1.1-alpha):
5856 - Enable a couple of pieces of Windows hardening: one
5857 (HeapEnableTerminationOnCorruption) that has been on-by-default
5858 since Windows 8, and unavailable before Windows 7; and one
5859 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
5860 affect us, but shouldn't do any harm. Closes ticket 21953.
5862 o Minor features (bridge, backport from 0.3.1.9):
5863 - Bridges now include notice in their descriptors that they are
5864 bridges, and notice of their distribution status, based on their
5865 publication settings. Implements ticket 18329. For more fine-
5866 grained control of how a bridge is distributed, upgrade to 0.3.2.x
5869 o Minor features (directory authority, backport from 0.3.2.6-alpha):
5870 - Add an IPv6 address for the "bastet" directory authority. Closes
5873 o Minor features (geoip):
5874 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
5877 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
5878 - Avoid unnecessary calls to directory_fetches_from_authorities() on
5879 relays, to prevent spurious address resolutions and descriptor
5880 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
5881 bugfix on in 0.2.8.1-alpha.
5883 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
5884 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
5885 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
5887 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
5888 - When a circuit is marked for close, do not attempt to package any
5889 cells for channels on that circuit. Previously, we would detect
5890 this condition lower in the call stack, when we noticed that the
5891 circuit had no attached channel, and log an annoying message.
5892 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
5894 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
5895 - Avoid a crash when transitioning from client mode to bridge mode.
5896 Previously, we would launch the worker threads whenever our
5897 "public server" mode changed, but not when our "server" mode
5898 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
5900 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
5901 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
5902 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
5905 Changes in version 0.2.9.14 - 2017-12-01
5906 Tor 0.3.0.13 backports important security and stability bugfixes from
5907 later Tor releases. All Tor users should upgrade to this release, or
5908 to another of the releases coming out today.
5910 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
5911 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
5912 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
5913 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
5914 identifying and finding a workaround to this bug and to Moritz,
5915 Arthur Edelstein, and Roger for helping to track it down and
5918 o Major bugfixes (security, backport from 0.3.2.6-alpha):
5919 - Fix a denial of service bug where an attacker could use a
5920 malformed directory object to cause a Tor instance to pause while
5921 OpenSSL would try to read a passphrase from the terminal. (Tor
5922 instances run without a terminal, which is the case for most Tor
5923 packages, are not impacted.) Fixes bug 24246; bugfix on every
5924 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
5925 Found by OSS-Fuzz as testcase 6360145429790720.
5926 - Fix a denial of service issue where an attacker could crash a
5927 directory authority using a malformed router descriptor. Fixes bug
5928 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
5930 - When checking for replays in the INTRODUCE1 cell data for a
5931 (legacy) onion service, correctly detect replays in the RSA-
5932 encrypted part of the cell. We were previously checking for
5933 replays on the entire cell, but those can be circumvented due to
5934 the malleability of Tor's legacy hybrid encryption. This fix helps
5935 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
5936 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
5939 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
5940 - Fix a use-after-free error that could crash v2 Tor onion services
5941 when they failed to open circuits while expiring introduction
5942 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
5943 also tracked as TROVE-2017-013 and CVE-2017-8823.
5945 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
5946 - When running as a relay, make sure that we never build a path
5947 through ourselves, even in the case where we have somehow lost the
5948 version of our descriptor appearing in the consensus. Fixes part
5949 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
5950 as TROVE-2017-012 and CVE-2017-8822.
5952 o Minor features (bridge, backport from 0.3.1.9):
5953 - Bridges now include notice in their descriptors that they are
5954 bridges, and notice of their distribution status, based on their
5955 publication settings. Implements ticket 18329. For more fine-
5956 grained control of how a bridge is distributed, upgrade to 0.3.2.x
5959 o Minor features (directory authority, backport from 0.3.2.6-alpha):
5960 - Add an IPv6 address for the "bastet" directory authority. Closes
5963 o Minor features (geoip):
5964 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
5967 o Minor features (security, windows, backport from 0.3.1.1-alpha):
5968 - Enable a couple of pieces of Windows hardening: one
5969 (HeapEnableTerminationOnCorruption) that has been on-by-default
5970 since Windows 8, and unavailable before Windows 7; and one
5971 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
5972 affect us, but shouldn't do any harm. Closes ticket 21953.
5974 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
5975 - Avoid unnecessary calls to directory_fetches_from_authorities() on
5976 relays, to prevent spurious address resolutions and descriptor
5977 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
5978 bugfix on in 0.2.8.1-alpha.
5980 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
5981 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
5982 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
5984 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
5985 - When a circuit is marked for close, do not attempt to package any
5986 cells for channels on that circuit. Previously, we would detect
5987 this condition lower in the call stack, when we noticed that the
5988 circuit had no attached channel, and log an annoying message.
5989 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
5991 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
5992 - Avoid a crash when transitioning from client mode to bridge mode.
5993 Previously, we would launch the worker threads whenever our
5994 "public server" mode changed, but not when our "server" mode
5995 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
5997 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
5998 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
5999 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
6002 Changes in version 0.2.8.17 - 2017-12-01
6003 Tor 0.2.8.17 backports important security and stability bugfixes from
6004 later Tor releases. All Tor users should upgrade to this release, or
6005 to another of the releases coming out today.
6007 Note: the Tor 0.2.8 series will no longer be supported after 1 Jan
6008 2018. If you need a release with long-term support, please upgrade with
6009 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
6011 o Major bugfixes (security, backport from 0.3.2.6-alpha):
6012 - Fix a denial of service bug where an attacker could use a
6013 malformed directory object to cause a Tor instance to pause while
6014 OpenSSL would try to read a passphrase from the terminal. (Tor
6015 instances run without a terminal, which is the case for most Tor
6016 packages, are not impacted.) Fixes bug 24246; bugfix on every
6017 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
6018 Found by OSS-Fuzz as testcase 6360145429790720.
6019 - When checking for replays in the INTRODUCE1 cell data for a
6020 (legacy) onion service, correctly detect replays in the RSA-
6021 encrypted part of the cell. We were previously checking for
6022 replays on the entire cell, but those can be circumvented due to
6023 the malleability of Tor's legacy hybrid encryption. This fix helps
6024 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
6025 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
6028 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
6029 - Fix a use-after-free error that could crash v2 Tor onion services
6030 when they failed to open circuits while expiring introduction
6031 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
6032 also tracked as TROVE-2017-013 and CVE-2017-8823.
6034 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
6035 - When running as a relay, make sure that we never build a path through
6036 ourselves, even in the case where we have somehow lost the version of
6037 our descriptor appearing in the consensus. Fixes part of bug 21534;
6038 bugfix on 0.2.0.1-alpha. This issue is also tracked as TROVE-2017-012
6041 o Minor features (bridge, backport from 0.3.1.9):
6042 - Bridges now include notice in their descriptors that they are
6043 bridges, and notice of their distribution status, based on their
6044 publication settings. Implements ticket 18329. For more fine-
6045 grained control of how a bridge is distributed, upgrade to 0.3.2.x
6048 o Minor features (directory authority, backport from 0.3.2.6-alpha):
6049 - Add an IPv6 address for the "bastet" directory authority. Closes
6052 o Minor features (geoip):
6053 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
6056 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
6057 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
6058 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
6061 Changes in version 0.2.5.16 - 2017-12-01
6062 Tor 0.2.5.13 backports important security and stability bugfixes from
6063 later Tor releases. All Tor users should upgrade to this release, or
6064 to another of the releases coming out today.
6066 Note: the Tor 0.2.5 series will no longer be supported after 1 May
6067 2018. If you need a release with long-term support, please upgrade to
6068 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
6070 o Major bugfixes (security, backport from 0.3.2.6-alpha):
6071 - Fix a denial of service bug where an attacker could use a
6072 malformed directory object to cause a Tor instance to pause while
6073 OpenSSL would try to read a passphrase from the terminal. (Tor
6074 instances run without a terminal, which is the case for most Tor
6075 packages, are not impacted.) Fixes bug 24246; bugfix on every
6076 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
6077 Found by OSS-Fuzz as testcase 6360145429790720.
6078 - When checking for replays in the INTRODUCE1 cell data for a
6079 (legacy) onion service, correctly detect replays in the RSA-
6080 encrypted part of the cell. We were previously checking for
6081 replays on the entire cell, but those can be circumvented due to
6082 the malleability of Tor's legacy hybrid encryption. This fix helps
6083 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
6084 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
6087 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
6088 - When running as a relay, make sure that we never build a path
6089 through ourselves, even in the case where we have somehow lost the
6090 version of our descriptor appearing in the consensus. Fixes part
6091 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
6092 as TROVE-2017-012 and CVE-2017-8822.
6094 o Minor features (bridge, backport from 0.3.1.9):
6095 - Bridges now include notice in their descriptors that they are
6096 bridges, and notice of their distribution status, based on their
6097 publication settings. Implements ticket 18329. For more fine-
6098 grained control of how a bridge is distributed, upgrade to 0.3.2.x
6101 o Minor features (geoip):
6102 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
6106 Changes in version 0.3.2.5-alpha - 2017-11-22
6107 Tor 0.3.2.5-alpha is the fifth alpha release in the 0.3.2.x series. It
6108 fixes several stability and reliability bugs, including a fix for
6109 intermittent bootstrapping failures that some people have been seeing
6110 since the 0.3.0.x series.
6112 Please test this alpha out -- many of these fixes will soon be
6113 backported to stable Tor versions if no additional bugs are found
6116 o Major bugfixes (bootstrapping):
6117 - Fetch descriptors aggressively whenever we lack enough to build
6118 circuits, regardless of how many descriptors we are missing.
6119 Previously, we would delay launching the fetch when we had fewer
6120 than 15 missing descriptors, even if some of those descriptors
6121 were blocking circuits from building. Fixes bug 23985; bugfix on
6122 0.1.1.11-alpha. The effects of this bug became worse in
6123 0.3.0.3-alpha, when we began treating missing descriptors from our
6124 primary guards as a reason to delay circuits.
6125 - Don't try fetching microdescriptors from relays that have failed
6126 to deliver them in the past. Fixes bug 23817; bugfix
6129 o Minor features (directory authority):
6130 - Make the "Exit" flag assignment only depend on whether the exit
6131 policy allows connections to ports 80 and 443. Previously relays
6132 would get the Exit flag if they allowed connections to one of
6133 these ports and also port 6667. Resolves ticket 23637.
6135 o Minor features (geoip):
6136 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
6139 o Minor features (linux seccomp2 sandbox):
6140 - Update the sandbox rules so that they should now work correctly
6141 with Glibc 2.26. Closes ticket 24315.
6143 o Minor features (logging):
6144 - Downgrade a pair of log messages that could occur when an exit's
6145 resolver gave us an unusual (but not forbidden) response. Closes
6147 - Improve the message we log when re-enabling circuit build timeouts
6148 after having received a consensus. Closes ticket 20963.
6150 o Minor bugfixes (compilation):
6151 - Fix a memory leak warning in one of the libevent-related
6152 configuration tests that could occur when manually specifying
6153 -fsanitize=address. Fixes bug 24279; bugfix on 0.3.0.2-alpha.
6154 Found and patched by Alex Xu.
6155 - When detecting OpenSSL on Windows from our configure script, make
6156 sure to try linking with the ws2_32 library. Fixes bug 23783;
6157 bugfix on 0.3.2.2-alpha.
6159 o Minor bugfixes (control port, linux seccomp2 sandbox):
6160 - Avoid a crash when attempting to use the seccomp2 sandbox together
6161 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
6164 o Minor bugfixes (control port, onion services):
6165 - Report "FAILED" instead of "UPLOAD_FAILED" "FAILED" for the
6166 HS_DESC event when a service is not able to upload a descriptor.
6167 Fixes bug 24230; bugfix on 0.2.7.1-alpha.
6169 o Minor bugfixes (directory cache):
6170 - Recover better from empty or corrupt files in the consensus cache
6171 directory. Fixes bug 24099; bugfix on 0.3.1.1-alpha.
6172 - When a consensus diff calculation is only partially successful,
6173 only record the successful parts as having succeeded. Partial
6174 success can happen if (for example) one compression method fails
6175 but the others succeed. Previously we misrecorded all the
6176 calculations as having succeeded, which would later cause a
6177 nonfatal assertion failure. Fixes bug 24086; bugfix
6180 o Minor bugfixes (logging):
6181 - Only log once if we notice that KIST support is gone. Fixes bug
6182 24158; bugfix on 0.3.2.1-alpha.
6183 - Suppress a log notice when relay descriptors arrive. We already
6184 have a bootstrap progress for this so no need to log notice
6185 everytime tor receives relay descriptors. Microdescriptors behave
6186 the same. Fixes bug 23861; bugfix on 0.2.8.2-alpha.
6188 o Minor bugfixes (network layer):
6189 - When closing a connection via close_connection_immediately(), we
6190 mark it as "not blocked on bandwidth", to prevent later calls from
6191 trying to unblock it, and give it permission to read. This fixes a
6192 backtrace warning that can happen on relays under various
6193 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
6195 o Minor bugfixes (onion services):
6196 - The introduction circuit was being timed out too quickly while
6197 waiting for the rendezvous circuit to complete. Keep the intro
6198 circuit around longer instead of timing out and reopening new ones
6199 constantly. Fixes bug 23681; bugfix on 0.2.4.8-alpha.
6200 - Rename the consensus parameter "hsdir-interval" to "hsdir_interval"
6201 so it matches dir-spec.txt. Fixes bug 24262; bugfix
6203 - Silence a warning about failed v3 onion descriptor uploads that
6204 can happen naturally under certain edge cases. Fixes part of bug
6205 23662; bugfix on 0.3.2.1-alpha.
6207 o Minor bugfixes (tests):
6208 - Fix a memory leak in one of the bridge-distribution test cases.
6209 Fixes bug 24345; bugfix on 0.3.2.3-alpha.
6210 - Fix a bug in our fuzzing mock replacement for crypto_pk_checksig(),
6211 to correctly handle cases where a caller gives it an RSA key of
6212 under 160 bits. (This is not actually a bug in Tor itself, but
6213 rather in our fuzzing code.) Fixes bug 24247; bugfix on
6214 0.3.0.3-alpha. Found by OSS-Fuzz as issue 4177.
6217 - Add notes in man page regarding OS support for the various
6218 scheduler types. Attempt to use less jargon in the scheduler
6219 section. Closes ticket 24254.
6222 Changes in version 0.3.2.4-alpha - 2017-11-08
6223 Tor 0.3.2.4-alpha is the fourth alpha release in the 0.3.2.x series.
6224 It fixes several stability and reliability bugs, especially including
6225 a major reliability issue that has been plaguing fast exit relays in
6228 o Major bugfixes (exit relays, DNS):
6229 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
6230 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
6231 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
6232 identifying and finding a workaround to this bug and to Moritz,
6233 Arthur Edelstein, and Roger for helping to track it down and
6236 o Major bugfixes (scheduler, channel):
6237 - Stop processing scheduled channels if they closed while flushing
6238 cells. This can happen if the write on the connection fails
6239 leading to the channel being closed while in the scheduler loop.
6240 Fixes bug 23751; bugfix on 0.3.2.1-alpha.
6242 o Minor features (logging, scheduler):
6243 - Introduce a SCHED_BUG() function to log extra information about
6244 the scheduler state if we ever catch a bug in the scheduler.
6245 Closes ticket 23753.
6247 o Minor features (removed deprecations):
6248 - The ClientDNSRejectInternalAddresses flag can once again be set in
6249 non-testing Tor networks, so long as they do not use the default
6250 directory authorities. This change also removes the deprecation of
6251 this flag from 0.2.9.2-alpha. Closes ticket 21031.
6253 o Minor features (testing):
6254 - Our fuzzing tests now test the encrypted portions of v3 onion
6255 service descriptors. Implements more of 21509.
6257 o Minor bugfixes (directory client):
6258 - On failure to download directory information, delay retry attempts
6259 by a random amount based on the "decorrelated jitter" algorithm.
6260 Our previous delay algorithm tended to produce extra-long delays
6261 too easily. Fixes bug 23816; bugfix on 0.2.9.1-alpha.
6263 o Minor bugfixes (IPv6, v3 single onion services):
6264 - Remove buggy code for IPv6-only v3 single onion services, and
6265 reject attempts to configure them. This release supports IPv4,
6266 dual-stack, and IPv6-only v3 onion services; and IPv4 and dual-
6267 stack v3 single onion services. Fixes bug 23820; bugfix
6270 o Minor bugfixes (logging, relay):
6271 - Give only a protocol warning when the ed25519 key is not
6272 consistent between the descriptor and microdescriptor of a relay.
6273 This can happen, for instance, if the relay has been flagged
6274 NoEdConsensus. Fixes bug 24025; bugfix on 0.3.2.1-alpha.
6276 o Minor bugfixes (manpage, onion service):
6277 - Document that the HiddenServiceNumIntroductionPoints option is
6278 0-10 for v2 services and 0-20 for v3 services. Fixes bug 24115;
6279 bugfix on 0.3.2.1-alpha.
6281 o Minor bugfixes (memory leaks):
6282 - Fix a minor memory leak at exit in the KIST scheduler. This bug
6283 should have no user-visible impact. Fixes bug 23774; bugfix
6285 - Fix a memory leak when decrypting a badly formatted v3 onion
6286 service descriptor. Fixes bug 24150; bugfix on 0.3.2.1-alpha.
6287 Found by OSS-Fuzz; this is OSS-Fuzz issue 3994.
6289 o Minor bugfixes (onion services):
6290 - Cache some needed onion service client information instead of
6291 constantly computing it over and over again. Fixes bug 23623;
6292 bugfix on 0.3.2.1-alpha.
6293 - Properly retry HSv3 descriptor fetches when missing required
6294 directory information. Fixes bug 23762; bugfix on 0.3.2.1-alpha.
6296 o Minor bugfixes (path selection):
6297 - When selecting relays by bandwidth, avoid a rounding error that
6298 could sometimes cause load to be imbalanced incorrectly.
6299 Previously, we would always round upwards; now, we round towards
6300 the nearest integer. This had the biggest effect when a relay's
6301 weight adjustments should have given it weight 0, but it got
6302 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
6303 - When calculating the fraction of nodes that have descriptors, and
6304 all nodes in the network have zero bandwidths, count the number of
6305 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
6306 - Actually log the total bandwidth in compute_weighted_bandwidths().
6307 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
6309 o Minor bugfixes (relay, crash):
6310 - Avoid a crash when transitioning from client mode to bridge mode.
6311 Previously, we would launch the worker threads whenever our
6312 "public server" mode changed, but not when our "server" mode
6313 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
6315 o Minor bugfixes (testing):
6316 - Fix a spurious fuzzing-only use of an uninitialized value. Found
6317 by Brian Carpenter. Fixes bug 24082; bugfix on 0.3.0.3-alpha.
6318 - Test that IPv6-only clients can use microdescriptors when running
6319 "make test-network-all". Requires chutney master 61c28b9 or later.
6320 Closes ticket 24109.
6323 Changes in version 0.3.2.3-alpha - 2017-10-27
6324 Tor 0.3.2.3-alpha is the third release in the 0.3.2 series. It fixes
6325 numerous small bugs in earlier versions of 0.3.2.x, and adds a new
6326 directory authority, Bastet.
6328 o Directory authority changes:
6329 - Add "Bastet" as a ninth directory authority to the default list.
6330 Closes ticket 23910.
6331 - The directory authority "Longclaw" has changed its IP address.
6332 Closes ticket 23592.
6334 o Minor features (bridge):
6335 - Bridge relays can now set the BridgeDistribution config option to
6336 add a "bridge-distribution-request" line to their bridge
6337 descriptor, which tells BridgeDB how they'd like their bridge
6338 address to be given out. (Note that as of Oct 2017, BridgeDB does
6339 not yet implement this feature.) As a side benefit, this feature
6340 provides a way to distinguish bridge descriptors from non-bridge
6341 descriptors. Implements tickets 18329.
6343 o Minor features (client, entry guards):
6344 - Improve log messages when missing descriptors for primary guards.
6345 Resolves ticket 23670.
6347 o Minor features (geoip):
6348 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
6351 o Minor bugfixes (bridge):
6352 - Overwrite the bridge address earlier in the process of retrieving
6353 its descriptor, to make sure we reach it on the configured
6354 address. Fixes bug 20532; bugfix on 0.2.0.10-alpha.
6356 o Minor bugfixes (documentation):
6357 - Document better how to read gcov, and what our gcov postprocessing
6358 scripts do. Fixes bug 23739; bugfix on 0.2.9.1-alpha.
6360 o Minor bugfixes (entry guards):
6361 - Tor now updates its guard state when it reads a consensus
6362 regardless of whether it's missing descriptors. That makes tor use
6363 its primary guards to fetch descriptors in some edge cases where
6364 it would previously have used fallback directories. Fixes bug
6365 23862; bugfix on 0.3.0.1-alpha.
6367 o Minor bugfixes (hidden service client):
6368 - When handling multiple SOCKS request for the same .onion address,
6369 only fetch the service descriptor once.
6370 - When a descriptor fetch fails with a non-recoverable error, close
6371 all pending SOCKS requests for that .onion. Fixes bug 23653;
6372 bugfix on 0.3.2.1-alpha.
6374 o Minor bugfixes (hidden service):
6375 - Always regenerate missing hidden service public key files. Prior
6376 to this, if the public key was deleted from disk, it wouldn't get
6377 recreated. Fixes bug 23748; bugfix on 0.3.2.2-alpha. Patch
6379 - Make sure that we have a usable ed25519 key when the intro point
6380 relay supports ed25519 link authentication. Fixes bug 24002;
6381 bugfix on 0.3.2.1-alpha.
6383 o Minor bugfixes (hidden service, v2):
6384 - When reloading configured hidden services, copy all information
6385 from the old service object. Previously, some data was omitted,
6386 causing delays in descriptor upload, and other bugs. Fixes bug
6387 23790; bugfix on 0.2.1.9-alpha.
6389 o Minor bugfixes (memory safety, defensive programming):
6390 - Clear the target address when node_get_prim_orport() returns
6391 early. Fixes bug 23874; bugfix on 0.2.8.2-alpha.
6393 o Minor bugfixes (relay):
6394 - Avoid a BUG warning when receiving a dubious CREATE cell while an
6395 option transition is in progress. Fixes bug 23952; bugfix
6398 o Minor bugfixes (testing):
6399 - Adjust the GitLab CI configuration to more closely match that of
6400 Travis CI. Fixes bug 23757; bugfix on 0.3.2.2-alpha.
6401 - Prevent scripts/test/coverage from attempting to move gcov output
6402 to the root directory. Fixes bug 23741; bugfix on 0.2.5.1-alpha.
6403 - When running unit tests as root, skip a test that would fail
6404 because it expects a permissions error. This affects some
6405 continuous integration setups. Fixes bug 23758; bugfix
6407 - Stop unconditionally mirroring the tor repository in GitLab CI.
6408 This prevented developers from enabling GitLab CI on master. Fixes
6409 bug 23755; bugfix on 0.3.2.2-alpha.
6410 - Fix the hidden service v3 descriptor decoding fuzzing to use the
6411 latest decoding API correctly. Fixes bug 21509; bugfix
6414 o Minor bugfixes (warnings):
6415 - When we get an HTTP request on a SOCKS port, tell the user about
6416 the new HTTPTunnelPort option. Previously, we would give a "Tor is
6417 not an HTTP Proxy" message, which stopped being true when
6418 HTTPTunnelPort was introduced. Fixes bug 23678; bugfix
6422 Changes in version 0.2.5.15 - 2017-10-25
6423 Tor 0.2.5.15 backports a collection of bugfixes from later Tor release
6424 series. It also adds a new directory authority, Bastet.
6426 Note: the Tor 0.2.5 series will no longer be supported after 1 May
6427 2018. If you need a release with long-term support, please upgrade to
6428 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
6430 o Directory authority changes:
6431 - Add "Bastet" as a ninth directory authority to the default list.
6432 Closes ticket 23910.
6433 - The directory authority "Longclaw" has changed its IP address.
6434 Closes ticket 23592.
6436 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
6437 - Avoid an assertion failure bug affecting our implementation of
6438 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
6439 handling of "0xx" differs from what we had expected. Fixes bug
6440 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
6442 o Minor features (geoip):
6443 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
6446 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
6447 - Fix a memset() off the end of an array when packing cells. This
6448 bug should be harmless in practice, since the corrupted bytes are
6449 still in the same structure, and are always padding bytes,
6450 ignored, or immediately overwritten, depending on compiler
6451 behavior. Nevertheless, because the memset()'s purpose is to make
6452 sure that any other cell-handling bugs can't expose bytes to the
6453 network, we need to fix it. Fixes bug 22737; bugfix on
6454 0.2.4.11-alpha. Fixes CID 1401591.
6456 o Build features (backport from 0.3.1.5-alpha):
6457 - Tor's repository now includes a Travis Continuous Integration (CI)
6458 configuration file (.travis.yml). This is meant to help new
6459 developers and contributors who fork Tor to a Github repository be
6460 better able to test their changes, and understand what we expect
6461 to pass. To use this new build feature, you must fork Tor to your
6462 Github account, then go into the "Integrations" menu in the
6463 repository settings for your fork and enable Travis, then push
6464 your changes. Closes ticket 22636.
6467 Changes in version 0.2.8.16 - 2017-10-25
6468 Tor 0.2.8.16 backports a collection of bugfixes from later Tor release
6469 series, including a bugfix for a crash issue that had affected relays
6470 under memory pressure. It also adds a new directory authority, Bastet.
6472 Note: the Tor 0.2.8 series will no longer be supported after 1 Jan
6473 2018. If you need a release with long-term support, please stick with
6474 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
6476 o Directory authority changes:
6477 - Add "Bastet" as a ninth directory authority to the default list.
6478 Closes ticket 23910.
6479 - The directory authority "Longclaw" has changed its IP address.
6480 Closes ticket 23592.
6482 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
6483 - Fix a timing-based assertion failure that could occur when the
6484 circuit out-of-memory handler freed a connection's output buffer.
6485 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
6487 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
6488 - Remove longclaw's IPv6 address, as it will soon change. Authority
6489 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
6490 3/8 directory authorities with IPv6 addresses, but there are also
6491 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
6493 o Minor features (geoip):
6494 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
6498 Changes in version 0.2.9.13 - 2017-10-25
6499 Tor 0.2.9.13 backports a collection of bugfixes from later Tor release
6500 series, including a bugfix for a crash issue that had affected relays
6501 under memory pressure. It also adds a new directory authority, Bastet.
6503 o Directory authority changes:
6504 - Add "Bastet" as a ninth directory authority to the default list.
6505 Closes ticket 23910.
6506 - The directory authority "Longclaw" has changed its IP address.
6507 Closes ticket 23592.
6509 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
6510 - Fix a timing-based assertion failure that could occur when the
6511 circuit out-of-memory handler freed a connection's output buffer.
6512 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
6514 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
6515 - Remove longclaw's IPv6 address, as it will soon change. Authority
6516 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
6517 3/8 directory authorities with IPv6 addresses, but there are also
6518 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
6520 o Minor features (geoip):
6521 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
6524 o Minor bugfixes (directory authority, backport from 0.3.1.5-alpha):
6525 - When a directory authority rejects a descriptor or extrainfo with
6526 a given digest, mark that digest as undownloadable, so that we do
6527 not attempt to download it again over and over. We previously
6528 tried to avoid downloading such descriptors by other means, but we
6529 didn't notice if we accidentally downloaded one anyway. This
6530 behavior became problematic in 0.2.7.2-alpha, when authorities
6531 began pinning Ed25519 keys. Fixes bug 22349; bugfix
6534 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
6535 - Clear the address when node_get_prim_orport() returns early.
6536 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
6538 o Minor bugfixes (Windows service, backport from 0.3.1.6-rc):
6539 - When running as a Windows service, set the ID of the main thread
6540 correctly. Failure to do so made us fail to send log messages to
6541 the controller in 0.2.1.16-rc, slowed down controller event
6542 delivery in 0.2.7.3-rc and later, and crash with an assertion
6543 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
6544 Patch and diagnosis from "Vort".
6547 Changes in version 0.3.0.12 - 2017-10-25
6548 Tor 0.3.0.12 backports a collection of bugfixes from later Tor release
6549 series, including a bugfix for a crash issue that had affected relays
6550 under memory pressure. It also adds a new directory authority, Bastet.
6552 Note: the Tor 0.3.0 series will no longer be supported after 26 Jan
6553 2018. If you need a release with long-term support, please stick with
6554 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
6556 o Directory authority changes:
6557 - Add "Bastet" as a ninth directory authority to the default list.
6558 Closes ticket 23910.
6559 - The directory authority "Longclaw" has changed its IP address.
6560 Closes ticket 23592.
6562 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
6563 - Fix a timing-based assertion failure that could occur when the
6564 circuit out-of-memory handler freed a connection's output buffer.
6565 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
6567 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
6568 - Remove longclaw's IPv6 address, as it will soon change. Authority
6569 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
6570 3/8 directory authorities with IPv6 addresses, but there are also
6571 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
6573 o Minor features (geoip):
6574 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
6577 o Minor bugfixes (directory authority, backport from 0.3.1.5-alpha):
6578 - When a directory authority rejects a descriptor or extrainfo with
6579 a given digest, mark that digest as undownloadable, so that we do
6580 not attempt to download it again over and over. We previously
6581 tried to avoid downloading such descriptors by other means, but we
6582 didn't notice if we accidentally downloaded one anyway. This
6583 behavior became problematic in 0.2.7.2-alpha, when authorities
6584 began pinning Ed25519 keys. Fixes bug 22349; bugfix
6587 o Minor bugfixes (hidden service, relay, backport from 0.3.2.2-alpha):
6588 - Avoid a possible double close of a circuit by the intro point on
6589 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
6590 bugfix on 0.3.0.1-alpha.
6592 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
6593 - Clear the address when node_get_prim_orport() returns early.
6594 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
6596 o Minor bugfixes (Windows service, backport from 0.3.1.6-rc):
6597 - When running as a Windows service, set the ID of the main thread
6598 correctly. Failure to do so made us fail to send log messages to
6599 the controller in 0.2.1.16-rc, slowed down controller event
6600 delivery in 0.2.7.3-rc and later, and crash with an assertion
6601 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
6602 Patch and diagnosis from "Vort".
6605 Changes in version 0.3.1.8 - 2017-10-25
6606 Tor 0.3.1.8 is the second stable release in the 0.3.1 series.
6607 It includes several bugfixes, including a bugfix for a crash issue
6608 that had affected relays under memory pressure. It also adds
6609 a new directory authority, Bastet.
6611 o Directory authority changes:
6612 - Add "Bastet" as a ninth directory authority to the default list.
6613 Closes ticket 23910.
6614 - The directory authority "Longclaw" has changed its IP address.
6615 Closes ticket 23592.
6617 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
6618 - Fix a timing-based assertion failure that could occur when the
6619 circuit out-of-memory handler freed a connection's output buffer.
6620 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
6622 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
6623 - Remove longclaw's IPv6 address, as it will soon change. Authority
6624 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
6625 3/8 directory authorities with IPv6 addresses, but there are also
6626 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
6628 o Minor features (geoip):
6629 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
6632 o Minor bugfixes (compilation, backport from 0.3.2.2-alpha):
6633 - Fix a compilation warning when building with zstd support on
6634 32-bit platforms. Fixes bug 23568; bugfix on 0.3.1.1-alpha. Found
6635 and fixed by Andreas Stieger.
6637 o Minor bugfixes (compression, backport from 0.3.2.2-alpha):
6638 - Handle a pathological case when decompressing Zstandard data when
6639 the output buffer size is zero. Fixes bug 23551; bugfix
6642 o Minor bugfixes (directory authority, backport from 0.3.2.1-alpha):
6643 - Remove the length limit on HTTP status lines that authorities can
6644 send in their replies. Fixes bug 23499; bugfix on 0.3.1.6-rc.
6646 o Minor bugfixes (hidden service, relay, backport from 0.3.2.2-alpha):
6647 - Avoid a possible double close of a circuit by the intro point on
6648 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
6649 bugfix on 0.3.0.1-alpha.
6651 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
6652 - Clear the address when node_get_prim_orport() returns early.
6653 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
6655 o Minor bugfixes (unit tests, backport from 0.3.2.2-alpha):
6656 - Fix additional channelpadding unit test failures by using mocked
6657 time instead of actual time for all tests. Fixes bug 23608; bugfix
6661 Changes in version 0.3.2.2-alpha - 2017-09-29
6662 Tor 0.3.2.2-alpha is the second release in the 0.3.2 series. This
6663 release fixes several minor bugs in the new scheduler and next-
6664 generation onion services; both features were newly added in the 0.3.2
6665 series. Other fixes in this alpha include several fixes for non-fatal
6666 tracebacks which would appear in logs.
6668 With the aim to stabilise the 0.3.2 series by 15 December 2017, this
6669 alpha does not contain any substantial new features. Minor features
6670 include better testing and logging.
6672 The following comprises the complete list of changes included
6675 o Major bugfixes (relay, crash, assertion failure):
6676 - Fix a timing-based assertion failure that could occur when the
6677 circuit out-of-memory handler freed a connection's output buffer.
6678 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
6680 o Major bugfixes (scheduler):
6681 - If a channel is put into the scheduler's pending list, then it
6682 starts closing, and then if the scheduler runs before it finishes
6683 closing, the scheduler will get stuck trying to flush its cells
6684 while the lower layers refuse to cooperate. Fix that race
6685 condition by giving the scheduler an escape method. Fixes bug
6686 23676; bugfix on 0.3.2.1-alpha.
6688 o Minor features (build, compilation):
6689 - The "check-changes" feature is now part of the "make check" tests;
6690 we'll use it to try to prevent misformed changes files from
6691 accumulating. Closes ticket 23564.
6692 - Tor builds should now fail if there are any mismatches between the
6693 C type representing a configuration variable and the C type the
6694 data-driven parser uses to store a value there. Previously, we
6695 needed to check these by hand, which sometimes led to mistakes.
6696 Closes ticket 23643.
6698 o Minor features (directory authorities):
6699 - Remove longclaw's IPv6 address, as it will soon change. Authority
6700 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
6701 3/8 directory authorities with IPv6 addresses, but there are also
6702 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
6704 o Minor features (hidden service, circuit, logging):
6705 - Improve logging of many callsite in the circuit subsystem to print
6706 the circuit identifier(s).
6707 - Log when we cleanup an intro point from a service so we know when
6708 and for what reason it happened. Closes ticket 23604.
6710 o Minor features (logging):
6711 - Log more circuit information whenever we are about to try to
6712 package a relay cell on a circuit with a nonexistent n_chan.
6713 Attempt to diagnose ticket 8185.
6714 - Improve info-level log identification of particular circuits, to
6715 help with debugging. Closes ticket 23645.
6717 o Minor features (relay):
6718 - When choosing which circuits can be expired as unused, consider
6719 circuits from clients even if those clients used regular CREATE
6720 cells to make them; and do not consider circuits from relays even
6721 if they were made with CREATE_FAST. Part of ticket 22805.
6723 o Minor features (robustness):
6724 - Change several fatal assertions when flushing buffers into non-
6725 fatal assertions, to prevent any recurrence of 23690.
6727 o Minor features (spec conformance, bridge, diagnostic):
6728 - When handling the USERADDR command on an ExtOrPort, warn when the
6729 transports provides a USERADDR with no port. In a future version,
6730 USERADDR commands of this format may be rejected. Detects problems
6731 related to ticket 23080.
6733 o Minor features (testing):
6734 - Add a unit test to make sure that our own generated platform
6735 string will be accepted by directory authorities. Closes
6738 o Minor bugfixes (bootstrapping):
6739 - When warning about state file clock skew, report the correct
6740 direction for the detected skew. Fixes bug 23606; bugfix
6742 - Avoid an assertion failure when logging a state file clock skew
6743 very early in bootstrapping. Fixes bug 23607; bugfix
6746 o Minor bugfixes (build, compilation):
6747 - Fix a compilation warning when building with zstd support on
6748 32-bit platforms. Fixes bug 23568; bugfix on 0.3.1.1-alpha. Found
6749 and fixed by Andreas Stieger.
6750 - When searching for OpenSSL, don't accept any OpenSSL library that
6751 lacks TLSv1_1_method(): Tor doesn't build with those versions.
6752 Additionally, look in /usr/local/opt/openssl, if it's present.
6753 These changes together repair the default build on OSX systems
6754 with Homebrew installed. Fixes bug 23602; bugfix on 0.2.7.2-alpha.
6756 o Minor bugfixes (compression):
6757 - Handle a pathological case when decompressing Zstandard data when
6758 the output buffer size is zero. Fixes bug 23551; bugfix
6761 o Minor bugfixes (documentation):
6762 - Fix manpage to not refer to the obsolete (and misspelled)
6763 UseEntryGuardsAsDirectoryGuards parameter in the description of
6764 NumDirectoryGuards. Fixes bug 23611; bugfix on 0.2.4.8-alpha.
6766 o Minor bugfixes (hidden service v3):
6767 - Don't log an assertion failure when we can't find the right
6768 information to extend to an introduction point. In rare cases,
6769 this could happen, causing a warning, even though tor would
6770 recover gracefully. Fixes bug 23159; bugfix on 0.3.2.1-alpha.
6771 - Pad RENDEZVOUS cell up to the size of the legacy cell which is
6772 much bigger so the rendezvous point can't distinguish which hidden
6773 service protocol is being used. Fixes bug 23420; bugfix
6776 o Minor bugfixes (hidden service, relay):
6777 - Avoid a possible double close of a circuit by the intro point on
6778 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
6779 bugfix on 0.3.0.1-alpha.
6781 o Minor bugfixes (logging, relay shutdown, annoyance):
6782 - When a circuit is marked for close, do not attempt to package any
6783 cells for channels on that circuit. Previously, we would detect
6784 this condition lower in the call stack, when we noticed that the
6785 circuit had no attached channel, and log an annoying message.
6786 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
6788 o Minor bugfixes (scheduler):
6789 - When switching schedulers due to a consensus change, we didn't
6790 give the new scheduler a chance to react to the consensus. Fix
6791 that. Fixes bug 23537; bugfix on 0.3.2.1-alpha.
6792 - Make the KISTSchedRunInterval option a non negative value. With
6793 this, the way to disable KIST through the consensus is to set it
6794 to 0. Fixes bug 23539; bugfix on 0.3.2.1-alpha.
6795 - Only notice log the selected scheduler when we switch scheduler
6796 types. Fixes bug 23552; bugfix on 0.3.2.1-alpha.
6797 - Avoid a compilation warning on macOS in scheduler_ev_add() caused
6798 by a different tv_usec data type. Fixes bug 23575; bugfix
6800 - Make a hard exit if tor is unable to pick a scheduler which can
6801 happen if the user specifies a scheduler type that is not
6802 supported and not other types in Schedulers. Fixes bug 23581;
6803 bugfix on 0.3.2.1-alpha.
6804 - Properly initialize the scheduler last run time counter so it is
6805 not 0 at the first tick. Fixes bug 23696; bugfix on 0.3.2.1-alpha.
6807 o Minor bugfixes (testing):
6808 - Capture and detect several "Result does not fit" warnings in unit
6809 tests on platforms with 32-bit time_t. Fixes bug 21800; bugfix
6811 - Fix additional channelpadding unit test failures by using mocked
6812 time instead of actual time for all tests. Fixes bug 23608; bugfix
6814 - The removal of some old scheduler options caused some tests to
6815 fail on BSD systems. Assume current behavior is correct and make
6816 the tests pass again. Fixes bug 23566; bugfix on 0.3.2.1-alpha.
6818 o Code simplification and refactoring:
6819 - Remove various ways of testing circuits and connections for
6820 "clientness"; instead, favor channel_is_client(). Part of
6823 o Deprecated features:
6824 - The ReachableDirAddresses and ClientPreferIPv6DirPort options are
6825 now deprecated; they do not apply to relays, and they have had no
6826 effect on clients since 0.2.8.x. Closes ticket 19704.
6829 - HiddenServiceVersion man page entry wasn't mentioning the now
6830 supported version 3. Fixes ticket 23580; bugfix on 0.3.2.1-alpha.
6831 - Clarify that the Address option is entirely about setting an
6832 advertised IPv4 address. Closes ticket 18891.
6833 - Clarify the manpage's use of the term "address" to clarify what
6834 kind of address is intended. Closes ticket 21405.
6835 - Document that onion service subdomains are allowed, and ignored.
6836 Closes ticket 18736.
6839 Changes in version 0.3.2.1-alpha - 2017-09-18
6840 Tor 0.3.2.1-alpha is the first release in the 0.3.2.x series. It
6841 includes support for our next-generation ("v3") onion service
6842 protocol, and adds a new circuit scheduler for more responsive
6843 forwarding decisions from relays. There are also numerous other small
6844 features and bugfixes here.
6846 Below are the changes since Tor 0.3.1.7.
6848 o Major feature (scheduler, channel):
6849 - Tor now uses new schedulers to decide which circuits should
6850 deliver cells first, in order to improve congestion at relays. The
6851 first type is called "KIST" ("Kernel Informed Socket Transport"),
6852 and is only available on Linux-like systems: it uses feedback from
6853 the kernel to prevent the kernel's TCP buffers from growing too
6854 full. The second new scheduler type is called "KISTLite": it
6855 behaves the same as KIST, but runs on systems without kernel
6856 support for inspecting TCP implementation details. The old
6857 scheduler is still available, under the name "Vanilla". To change
6858 the default scheduler preference order, use the new "Schedulers"
6859 option. (The default preference order is "KIST,KISTLite,Vanilla".)
6861 Matt Traudt implemented KIST, based on research by Rob Jansen,
6862 John Geddes, Christ Wacek, Micah Sherr, and Paul Syverson. For
6863 more information, see the design paper at
6864 http://www.robgjansen.com/publications/kist-sec2014.pdf and the
6865 followup implementation paper at https://arxiv.org/abs/1709.01044.
6866 Closes ticket 12541.
6868 o Major features (next-generation onion services):
6869 - Tor now supports the next-generation onion services protocol for
6870 clients and services! As part of this release, the core of
6871 proposal 224 has been implemented and is available for
6872 experimentation and testing by our users. This newer version of
6873 onion services ("v3") features many improvements over the legacy
6876 a) Better crypto (replaced SHA1/DH/RSA1024
6877 with SHA3/ed25519/curve25519)
6879 b) Improved directory protocol, leaking much less information to
6882 c) Improved directory protocol, with smaller surface for
6885 d) Better onion address security against impersonation.
6887 e) More extensible introduction/rendezvous protocol.
6889 f) A cleaner and more modular codebase.
6891 You can identify a next-generation onion address by its length:
6892 they are 56 characters long, as in
6893 "4acth47i6kxnvkewtm6q7ib2s3ufpo5sqbsnzjpbi7utijcltosqemad.onion".
6895 In the future, we will release more options and features for v3
6896 onion services, but we first need a testing period, so that the
6897 current codebase matures and becomes more robust. Planned features
6898 include: offline keys, advanced client authorization, improved
6899 guard algorithms, and statistics. For full details, see
6902 Legacy ("v2") onion services will still work for the foreseeable
6903 future, and will remain the default until this new codebase gets
6904 tested and hardened. Service operators who want to experiment with
6905 the new system can use the 'HiddenServiceVersion 3' torrc
6906 directive along with the regular onion service configuration
6907 options. We will publish a blog post about this new feature
6910 o Major bugfixes (usability, control port):
6911 - Report trusted clock skew indications as bootstrap errors, so
6912 controllers can more easily alert users when their clocks are
6913 wrong. Fixes bug 23506; bugfix on 0.1.2.6-alpha.
6915 o Minor features (bug detection):
6916 - Log a warning message with a stack trace for any attempt to call
6917 get_options() during option validation. This pattern has caused
6918 subtle bugs in the past. Closes ticket 22281.
6920 o Minor features (client):
6921 - You can now use Tor as a tunneled HTTP proxy: use the new
6922 HTTPTunnelPort option to open a port that accepts HTTP CONNECT
6923 requests. Closes ticket 22407.
6924 - Add an extra check to make sure that we always use the newer guard
6925 selection code for picking our guards. Closes ticket 22779.
6926 - When downloading (micro)descriptors, don't split the list into
6927 multiple requests unless we want at least 32 descriptors.
6928 Previously, we split at 4, not 32, which led to significant
6929 overhead in HTTP request size and degradation in compression
6930 performance. Closes ticket 23220.
6932 o Minor features (command line):
6933 - Add a new commandline option, --key-expiration, which prints when
6934 the current signing key is going to expire. Implements ticket
6935 17639; patch by Isis Lovecruft.
6937 o Minor features (control port):
6938 - If an application tries to use the control port as an HTTP proxy,
6939 respond with a meaningful "This is the Tor control port" message,
6940 and log the event. Closes ticket 1667. Patch from Ravi
6942 - Provide better error message for GETINFO desc/(id|name) when not
6943 fetching router descriptors. Closes ticket 5847. Patch by
6945 - Add GETINFO "{desc,md}/download-enabled", to inform the controller
6946 whether Tor will try to download router descriptors and
6947 microdescriptors respectively. Closes ticket 22684.
6948 - Added new GETINFO targets "ip-to-country/{ipv4,ipv6}-available",
6949 so controllers can tell whether the geoip databases are loaded.
6950 Closes ticket 23237.
6951 - Adds a timestamp field to the CIRC_BW and STREAM_BW bandwidth
6952 events. Closes ticket 19254. Patch by "DonnchaC".
6954 o Minor features (development support):
6955 - Developers can now generate a call-graph for Tor using the
6956 "calltool" python program, which post-processes object dumps. It
6957 should work okay on many Linux and OSX platforms, and might work
6958 elsewhere too. To run it, install calltool from
6959 https://gitweb.torproject.org/user/nickm/calltool.git and run
6960 "make callgraph". Closes ticket 19307.
6962 o Minor features (ed25519):
6963 - Add validation function to checks for torsion components in
6964 ed25519 public keys, used by prop224 client-side code. Closes
6965 ticket 22006. Math help by Ian Goldberg.
6967 o Minor features (exit relay, DNS):
6968 - Improve the clarity and safety of the log message from evdns when
6969 receiving an apparently spoofed DNS reply. Closes ticket 3056.
6971 o Minor features (integration, hardening):
6972 - Add a new NoExec option to prevent Tor from running other
6973 programs. When this option is set to 1, Tor will never try to run
6974 another program, regardless of the settings of
6975 PortForwardingHelper, ClientTransportPlugin, or
6976 ServerTransportPlugin. Once NoExec is set, it cannot be disabled
6977 without restarting Tor. Closes ticket 22976.
6979 o Minor features (logging):
6980 - Improve the warning message for specifying a relay by nickname.
6981 The previous message implied that nickname registration was still
6982 part of the Tor network design, which it isn't. Closes
6984 - If the sandbox filter fails to load, suggest to the user that
6985 their kernel might not support seccomp2. Closes ticket 23090.
6987 o Minor features (portability):
6988 - Check at configure time whether uint8_t is the same type as
6989 unsigned char. Lots of existing code already makes this
6990 assumption, and there could be strict aliasing issues if the
6991 assumption is violated. Closes ticket 22410.
6993 o Minor features (relay, configuration):
6994 - Reject attempts to use relative file paths when RunAsDaemon is
6995 set. Previously, Tor would accept these, but the directory-
6996 changing step of RunAsDaemon would give strange and/or confusing
6997 results. Closes ticket 22731.
6999 o Minor features (startup, safety):
7000 - When configured to write a PID file, Tor now exits if it is unable
7001 to do so. Previously, it would warn and continue. Closes
7004 o Minor features (static analysis):
7005 - The BUG() macro has been changed slightly so that Coverity no
7006 longer complains about dead code if the bug is impossible. Closes
7009 o Minor features (testing):
7010 - The default chutney network tests now include tests for the v3
7011 hidden service design. Make sure you have the latest version of
7012 chutney if you want to run these. Closes ticket 22437.
7013 - Add a unit test to verify that we can parse a hardcoded v2 hidden
7014 service descriptor. Closes ticket 15554.
7016 o Minor bugfixes (certificate handling):
7017 - Fix a time handling bug in Tor certificates set to expire after
7018 the year 2106. Fixes bug 23055; bugfix on 0.3.0.1-alpha. Found by
7019 Coverity as CID 1415728.
7021 o Minor bugfixes (client, usability):
7022 - Refrain from needlessly rejecting SOCKS5-with-hostnames and
7023 SOCKS4a requests that contain IP address strings, even when
7024 SafeSocks in enabled, as this prevents user from connecting to
7025 known IP addresses without relying on DNS for resolving. SafeSocks
7026 still rejects SOCKS connections that connect to IP addresses when
7027 those addresses are _not_ encoded as hostnames. Fixes bug 22461;
7028 bugfix on Tor 0.2.6.2-alpha.
7030 o Minor bugfixes (code correctness):
7031 - Call htons() in extend_cell_format() for encoding a 16-bit value.
7032 Previously we used ntohs(), which happens to behave the same on
7033 all the platforms we support, but which isn't really correct.
7034 Fixes bug 23106; bugfix on 0.2.4.8-alpha.
7035 - For defense-in-depth, make the controller's write_escaped_data()
7036 function robust to extremely long inputs. Fixes bug 19281; bugfix
7037 on 0.1.1.1-alpha. Reported by Guido Vranken.
7039 o Minor bugfixes (compilation):
7040 - Fix unused-variable warnings in donna's Curve25519 SSE2 code.
7041 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
7043 o Minor bugfixes (consensus expiry):
7044 - Check for adequate directory information correctly. Previously, Tor
7045 would reconsider whether it had sufficient directory information
7046 every 2 minutes. Fixes bug 23091; bugfix on 0.2.0.19-alpha.
7048 o Minor bugfixes (directory protocol):
7049 - Directory servers now include a "Date:" http header for response
7050 codes other than 200. Clients starting with a skewed clock and a
7051 recent consensus were getting "304 Not modified" responses from
7052 directory authorities, so without the Date header, the client
7053 would never hear about a wrong clock. Fixes bug 23499; bugfix
7055 - Make clients wait for 6 seconds before trying to download a
7056 consensus from an authority. Fixes bug 17750; bugfix
7059 o Minor bugfixes (DoS-resistance):
7060 - If future code asks if there are any running bridges, without
7061 checking if bridges are enabled, log a BUG warning rather than
7062 crashing. Fixes bug 23524; bugfix on 0.3.0.1-alpha.
7064 o Minor bugfixes (format strictness):
7065 - Restrict several data formats to decimal. Previously, the
7066 BuildTimeHistogram entries in the state file, the "bw=" entries in
7067 the bandwidth authority file, and the process IDs passed to the
7068 __OwningControllerProcess option could all be specified in hex or
7069 octal as well as in decimal. This was not an intentional feature.
7070 Fixes bug 22802; bugfixes on 0.2.2.1-alpha, 0.2.2.2-alpha,
7073 o Minor bugfixes (heartbeat):
7074 - If we fail to write a heartbeat message, schedule a retry for the
7075 minimum heartbeat interval number of seconds in the future. Fixes
7076 bug 19476; bugfix on 0.2.3.1-alpha.
7078 o Minor bugfixes (linux seccomp2 sandbox, logging):
7079 - Fix some messages on unexpected errors from the seccomp2 library.
7080 Fixes bug 22750; bugfix on 0.2.5.1-alpha. Patch from "cypherpunks".
7082 o Minor bugfixes (logging):
7083 - Remove duplicate log messages regarding opening non-local
7084 SocksPorts upon parsing config and opening listeners at startup.
7085 Fixes bug 4019; bugfix on 0.2.3.3-alpha.
7086 - Use a more comprehensible log message when telling the user
7087 they've excluded every running exit node. Fixes bug 7890; bugfix
7089 - When logging the number of descriptors we intend to download per
7090 directory request, do not log a number higher than then the number
7091 of descriptors we're fetching in total. Fixes bug 19648; bugfix
7093 - When warning about a directory owned by the wrong user, log the
7094 actual name of the user owning the directory. Previously, we'd log
7095 the name of the process owner twice. Fixes bug 23487; bugfix
7097 - The tor specification says hop counts are 1-based, so fix two log
7098 messages that mistakenly logged 0-based hop counts. Fixes bug
7099 18982; bugfix on 0.2.6.2-alpha and 0.2.4.5-alpha. Patch by teor.
7100 Credit to Xiaofan Li for reporting this issue.
7102 o Minor bugfixes (portability):
7103 - Stop using the PATH_MAX variable, which is not defined on GNU
7104 Hurd. Fixes bug 23098; bugfix on 0.3.1.1-alpha.
7106 o Minor bugfixes (relay):
7107 - When uploading our descriptor for the first time after startup,
7108 report the reason for uploading as "Tor just started" rather than
7109 leaving it blank. Fixes bug 22885; bugfix on 0.2.3.4-alpha.
7110 - Avoid unnecessary calls to directory_fetches_from_authorities() on
7111 relays, to prevent spurious address resolutions and descriptor
7112 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
7113 bugfix on in 0.2.8.1-alpha.
7115 o Minor bugfixes (tests):
7116 - Fix a broken unit test for the OutboundAddress option: the parsing
7117 function was never returning an error on failure. Fixes bug 23366;
7118 bugfix on 0.3.0.3-alpha.
7119 - Fix a signed-integer overflow in the unit tests for
7120 dir/download_status_random_backoff, which was untriggered until we
7121 fixed bug 17750. Fixes bug 22924; bugfix on 0.2.9.1-alpha.
7123 o Minor bugfixes (usability, control port):
7124 - Stop making an unnecessary routerlist check in NETINFO clock skew
7125 detection; this was preventing clients from reporting NETINFO clock
7126 skew to controllers. Fixes bug 23532; bugfix on 0.2.4.4-alpha.
7128 o Code simplification and refactoring:
7129 - Extract the code for handling newly-open channels into a separate
7130 function from the general code to handle channel state
7131 transitions. This change simplifies our callgraph, reducing the
7132 size of the largest strongly connected component by roughly a
7133 factor of two. Closes ticket 22608.
7134 - Remove dead code for largely unused statistics on the number of
7135 times we've attempted various public key operations. Fixes bug
7136 19871; bugfix on 0.1.2.4-alpha. Fix by Isis Lovecruft.
7137 - Remove several now-obsolete functions for asking about old
7138 variants directory authority status. Closes ticket 22311; patch
7140 - Remove some of the code that once supported "Named" and "Unnamed"
7141 routers. Authorities no longer vote for these flags. Closes
7143 - Rename the obsolete malleable hybrid_encrypt functions used in TAP
7144 and old hidden services, to indicate that they aren't suitable for
7145 new protocols or formats. Closes ticket 23026.
7146 - Replace our STRUCT_OFFSET() macro with offsetof(). Closes ticket
7147 22521. Patch from Neel Chauhan.
7148 - Split the enormous circuit_send_next_onion_skin() function into
7149 multiple subfunctions. Closes ticket 22804.
7150 - Split the portions of the buffer.c module that handle particular
7151 protocols into separate modules. Part of ticket 23149.
7152 - Use our test macros more consistently, to produce more useful
7153 error messages when our unit tests fail. Add coccinelle patches to
7154 allow us to re-check for test macro uses. Closes ticket 22497.
7156 o Deprecated features:
7157 - Deprecate HTTPProxy/HTTPProxyAuthenticator config options. They
7158 only applies to direct unencrypted HTTP connections to your
7159 directory server, which your Tor probably isn't using. Closes
7163 - Clarify in the manual that "Sandbox 1" is only supported on Linux
7164 kernels. Closes ticket 22677.
7165 - Document all values of PublishServerDescriptor in the manpage.
7166 Closes ticket 15645.
7167 - Improve the documentation for the directory port part of the
7168 DirAuthority line. Closes ticket 20152.
7169 - Restore documentation for the authorities' "approved-routers"
7170 file. Closes ticket 21148.
7173 - The AllowDotExit option has been removed as unsafe. It has been
7174 deprecated since 0.2.9.2-alpha. Closes ticket 23426.
7175 - The ClientDNSRejectInternalAddresses flag can no longer be set on
7176 non-testing networks. It has been deprecated since 0.2.9.2-alpha.
7177 Closes ticket 21031.
7178 - The controller API no longer includes an AUTHDIR_NEWDESCS event:
7179 nobody was using it any longer. Closes ticket 22377.
7182 Changes in version 0.2.8.15 - 2017-09-18
7183 Tor 0.2.8.15 backports a collection of bugfixes from later
7186 Most significantly, it includes a fix for TROVE-2017-008, a
7187 security bug that affects hidden services running with the
7188 SafeLogging option disabled. For more information, see
7189 https://trac.torproject.org/projects/tor/ticket/23490
7191 Note that Tor 0.2.8.x will no longer be supported after 1 Jan
7192 2018. We suggest that you upgrade to the latest stable release if
7193 possible. If you can't, we recommend that you upgrade at least to
7194 0.2.9, which will be supported until 2020.
7196 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
7197 - Avoid an assertion failure bug affecting our implementation of
7198 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
7199 handling of "0xx" differs from what we had expected. Fixes bug
7200 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
7203 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
7206 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
7207 - Backport a fix for an "unused variable" warning that appeared
7208 in some versions of mingw. Fixes bug 22838; bugfix on
7211 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
7212 - Fix a memset() off the end of an array when packing cells. This
7213 bug should be harmless in practice, since the corrupted bytes are
7214 still in the same structure, and are always padding bytes,
7215 ignored, or immediately overwritten, depending on compiler
7216 behavior. Nevertheless, because the memset()'s purpose is to make
7217 sure that any other cell-handling bugs can't expose bytes to the
7218 network, we need to fix it. Fixes bug 22737; bugfix on
7219 0.2.4.11-alpha. Fixes CID 1401591.
7221 o Build features (backport from 0.3.1.5-alpha):
7222 - Tor's repository now includes a Travis Continuous Integration (CI)
7223 configuration file (.travis.yml). This is meant to help new
7224 developers and contributors who fork Tor to a Github repository be
7225 better able to test their changes, and understand what we expect
7226 to pass. To use this new build feature, you must fork Tor to your
7227 Github account, then go into the "Integrations" menu in the
7228 repository settings for your fork and enable Travis, then push
7229 your changes. Closes ticket 22636.
7232 Changes in version 0.2.9.12 - 2017-09-18
7233 Tor 0.2.9.12 backports a collection of bugfixes from later
7236 Most significantly, it includes a fix for TROVE-2017-008, a
7237 security bug that affects hidden services running with the
7238 SafeLogging option disabled. For more information, see
7239 https://trac.torproject.org/projects/tor/ticket/23490
7241 o Major features (security, backport from 0.3.0.2-alpha):
7242 - Change the algorithm used to decide DNS TTLs on client and server
7243 side, to better resist DNS-based correlation attacks like the
7244 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
7245 Feamster. Now relays only return one of two possible DNS TTL
7246 values, and clients are willing to believe DNS TTL values up to 3
7247 hours long. Closes ticket 19769.
7249 o Major bugfixes (crash, directory connections, backport from 0.3.0.5-rc):
7250 - Fix a rare crash when sending a begin cell on a circuit whose
7251 linked directory connection had already been closed. Fixes bug
7252 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
7254 o Major bugfixes (DNS, backport from 0.3.0.2-alpha):
7255 - Fix a bug that prevented exit nodes from caching DNS records for
7256 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
7258 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
7259 - Fix a typo that had prevented TPROXY-based transparent proxying
7260 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
7261 Patch from "d4fq0fQAgoJ".
7263 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
7264 - Avoid an assertion failure bug affecting our implementation of
7265 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
7266 handling of "0xx" differs from what we had expected. Fixes bug
7267 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
7269 o Minor features (code style, backport from 0.3.1.3-alpha):
7270 - Add "Falls through" comments to our codebase, in order to silence
7271 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
7272 Stieger. Closes ticket 22446.
7274 o Minor features (geoip):
7275 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
7278 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.1-alpha):
7279 - Roll over monthly accounting at the configured hour and minute,
7280 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
7281 Found by Andrey Karpov with PVS-Studio.
7283 o Minor bugfixes (compilation, backport from 0.3.1.5-alpha):
7284 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
7285 bugfix on 0.2.8.1-alpha.
7286 - Fix warnings when building with libscrypt and openssl scrypt support
7287 on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
7288 - When building with certain versions the mingw C header files, avoid
7289 float-conversion warnings when calling the C functions isfinite(),
7290 isnan(), and signbit(). Fixes bug 22801; bugfix on 0.2.8.1-alpha.
7292 o Minor bugfixes (compilation, backport from 0.3.1.7):
7293 - Avoid compiler warnings in the unit tests for running tor_sscanf()
7294 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
7296 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
7297 - Backport a fix for an "unused variable" warning that appeared
7298 in some versions of mingw. Fixes bug 22838; bugfix on
7301 o Minor bugfixes (controller, backport from 0.3.1.7):
7302 - Do not crash when receiving a HSPOST command with an empty body.
7303 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
7304 - Do not crash when receiving a POSTDESCRIPTOR command with an
7305 empty body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
7307 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
7308 - Avoid Coverity build warnings related to our BUG() macro. By
7309 default, Coverity treats BUG() as the Linux kernel does: an
7310 instant abort(). We need to override that so our BUG() macro
7311 doesn't prevent Coverity from analyzing functions that use it.
7312 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
7314 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
7315 - Fix a memset() off the end of an array when packing cells. This
7316 bug should be harmless in practice, since the corrupted bytes are
7317 still in the same structure, and are always padding bytes,
7318 ignored, or immediately overwritten, depending on compiler
7319 behavior. Nevertheless, because the memset()'s purpose is to make
7320 sure that any other cell-handling bugs can't expose bytes to the
7321 network, we need to fix it. Fixes bug 22737; bugfix on
7322 0.2.4.11-alpha. Fixes CID 1401591.
7324 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
7325 - When setting the maximum number of connections allowed by the OS,
7326 always allow some extra file descriptors for other files. Fixes
7327 bug 22797; bugfix on 0.2.0.10-alpha.
7329 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
7330 - Avoid a sandbox failure when trying to re-bind to a socket and
7331 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
7333 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
7334 - Permit the fchmod system call, to avoid crashing on startup when
7335 starting with the seccomp2 sandbox and an unexpected set of
7336 permissions on the data directory or its contents. Fixes bug
7337 22516; bugfix on 0.2.5.4-alpha.
7339 o Minor bugfixes (relay, backport from 0.3.0.5-rc):
7340 - Avoid a double-marked-circuit warning that could happen when we
7341 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
7344 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
7345 - Reject version numbers with non-numeric prefixes (such as +, -, or
7346 whitespace). Disallowing whitespace prevents differential version
7347 parsing between POSIX-based and Windows platforms. Fixes bug 21507
7348 and part of 21508; bugfix on 0.0.8pre1.
7350 o Build features (backport from 0.3.1.5-alpha):
7351 - Tor's repository now includes a Travis Continuous Integration (CI)
7352 configuration file (.travis.yml). This is meant to help new
7353 developers and contributors who fork Tor to a Github repository be
7354 better able to test their changes, and understand what we expect
7355 to pass. To use this new build feature, you must fork Tor to your
7356 Github account, then go into the "Integrations" menu in the
7357 repository settings for your fork and enable Travis, then push
7358 your changes. Closes ticket 22636.
7361 Changes in version 0.3.0.11 - 2017-09-18
7362 Tor 0.3.0.11 backports a collection of bugfixes from Tor the 0.3.1
7365 Most significantly, it includes a fix for TROVE-2017-008, a
7366 security bug that affects hidden services running with the
7367 SafeLogging option disabled. For more information, see
7368 https://trac.torproject.org/projects/tor/ticket/23490
7370 o Minor features (code style, backport from 0.3.1.7):
7371 - Add "Falls through" comments to our codebase, in order to silence
7372 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
7373 Stieger. Closes ticket 22446.
7376 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
7379 o Minor bugfixes (compilation, backport from 0.3.1.7):
7380 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
7381 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
7383 o Minor bugfixes (controller, backport from 0.3.1.7):
7384 - Do not crash when receiving a HSPOST command with an empty body.
7385 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
7386 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
7387 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
7389 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
7390 - When setting the maximum number of connections allowed by the OS,
7391 always allow some extra file descriptors for other files. Fixes
7392 bug 22797; bugfix on 0.2.0.10-alpha.
7394 o Minor bugfixes (logging, relay, backport from 0.3.1.6-rc):
7395 - Remove a forgotten debugging message when an introduction point
7396 successfully establishes a hidden service prop224 circuit with
7398 - Change three other log_warn() for an introduction point to
7399 protocol warnings, because they can be failure from the network
7400 and are not relevant to the operator. Fixes bug 23078; bugfix on
7401 0.3.0.1-alpha and 0.3.0.2-alpha.
7404 Changes in version 0.3.1.7 - 2017-09-18
7405 Tor 0.3.1.7 is the first stable release in the 0.3.1 series.
7407 With the 0.3.1 series, Tor now serves and downloads directory
7408 information in more compact formats, to save on bandwidth overhead. It
7409 also contains a new padding system to resist netflow-based traffic
7410 analysis, and experimental support for building parts of Tor in Rust
7411 (though no parts of Tor are in Rust yet). There are also numerous
7412 small features, bugfixes on earlier release series, and groundwork for
7413 the hidden services revamp of 0.3.2.
7415 This release also includes a fix for TROVE-2017-008, a security bug
7416 that affects hidden services running with the SafeLogging option
7417 disabled. For more information, see
7418 https://trac.torproject.org/projects/tor/ticket/23490
7420 Per our stable release policy, we plan to support each stable release
7421 series for at least the next nine months, or for three months after
7422 the first stable release of the next series: whichever is longer. If
7423 you need a release with long-term support, we recommend that you stay
7424 with the 0.2.9 series.
7426 Below is a list of the changes since 0.3.1.6-rc. For a list of all
7427 changes since 0.3.0, see the ReleaseNotes file.
7429 o Major bugfixes (security, hidden services, loggging):
7430 - Fix a bug where we could log uninitialized stack when a certain
7431 hidden service error occurred while SafeLogging was disabled.
7432 Fixes bug #23490; bugfix on 0.2.7.2-alpha. This is also tracked as
7433 TROVE-2017-008 and CVE-2017-0380.
7435 o Minor features (defensive programming):
7436 - Create a pair of consensus parameters, nf_pad_tor2web and
7437 nf_pad_single_onion, to disable netflow padding in the consensus
7438 for non-anonymous connections in case the overhead is high. Closes
7441 o Minor features (diagnostic):
7442 - Add a stack trace to the bug warnings that can be logged when
7443 trying to send an outgoing relay cell with n_chan == 0. Diagnostic
7444 attempt for bug 23105.
7446 o Minor features (geoip):
7447 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
7450 o Minor bugfixes (compilation):
7451 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
7452 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
7454 o Minor bugfixes (controller):
7455 - Do not crash when receiving a HSPOST command with an empty body.
7456 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
7457 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
7458 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
7460 o Minor bugfixes (relay):
7461 - Inform the geoip and rephist modules about all requests, even on
7462 relays that are only fetching microdescriptors. Fixes a bug
7463 related to 21585; bugfix on 0.3.0.1-alpha.
7465 o Minor bugfixes (unit tests):
7466 - Fix a channelpadding unit test failure on slow systems by using
7467 mocked time instead of actual time. Fixes bug 23077; bugfix
7471 Changes in version 0.3.1.6-rc - 2017-09-05
7472 Tor 0.3.1.6-rc fixes a few small bugs and annoyances in the 0.3.1
7473 release series, including a bug that produced weird behavior on
7474 Windows directory caches.
7476 This is the first release candidate in the Tor 0.3.1 series. If we
7477 find no new bugs or regressions here, the first stable 0.3.1 release
7478 will be nearly identical to it.
7480 o Major bugfixes (windows, directory cache):
7481 - On Windows, do not try to delete cached consensus documents and
7482 diffs before they are unmapped from memory--Windows won't allow
7483 that. Instead, allow the consensus cache directory to grow larger,
7484 to hold files that might need to stay around longer. Fixes bug
7485 22752; bugfix on 0.3.1.1-alpha.
7487 o Minor features (directory authority):
7488 - Improve the message that authorities report to relays that present
7489 RSA/Ed25519 keypairs that conflict with previously pinned keys.
7490 Closes ticket 22348.
7492 o Minor features (geoip):
7493 - Update geoip and geoip6 to the August 3 2017 Maxmind GeoLite2
7496 o Minor features (testing):
7497 - Add more tests for compression backend initialization. Closes
7500 o Minor bugfixes (directory cache):
7501 - Fix a memory leak when recovering space in the consensus cache.
7502 Fixes bug 23139; bugfix on 0.3.1.1-alpha.
7504 o Minor bugfixes (hidden service):
7505 - Increase the number of circuits that a service is allowed to
7506 open over a specific period of time. The value was lower than it
7507 should be (8 vs 12) in the normal case of 3 introduction points.
7508 Fixes bug 22159; bugfix on 0.3.0.5-rc.
7509 - Fix a BUG warning during HSv3 descriptor decoding that could be
7510 cause by a specially crafted descriptor. Fixes bug 23233; bugfix
7511 on 0.3.0.1-alpha. Bug found by "haxxpop".
7512 - Rate-limit the log messages if we exceed the maximum number of
7513 allowed intro circuits. Fixes bug 22159; bugfix on 0.3.1.1-alpha.
7515 o Minor bugfixes (logging, relay):
7516 - Remove a forgotten debugging message when an introduction point
7517 successfully establishes a hidden service prop224 circuit with
7519 - Change three other log_warn() for an introduction point to
7520 protocol warnings, because they can be failure from the network
7521 and are not relevant to the operator. Fixes bug 23078; bugfix on
7522 0.3.0.1-alpha and 0.3.0.2-alpha.
7524 o Minor bugfixes (relay):
7525 - When a relay is not running as a directory cache, it will no
7526 longer generate compressed consensuses and consensus diff
7527 information. Previously, this was a waste of disk and CPU. Fixes
7528 bug 23275; bugfix on 0.3.1.1-alpha.
7530 o Minor bugfixes (robustness, error handling):
7531 - Improve our handling of the cases where OpenSSL encounters a
7532 memory error while encoding keys and certificates. We haven't
7533 observed these errors in the wild, but if they do happen, we now
7534 detect and respond better. Fixes bug 19418; bugfix on all versions
7535 of Tor. Reported by Guido Vranken.
7537 o Minor bugfixes (stability):
7538 - Avoid crashing on a double-free when unable to load or process an
7539 included file. Fixes bug 23155; bugfix on 0.3.1.1-alpha. Found
7540 with the clang static analyzer.
7542 o Minor bugfixes (testing):
7543 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
7544 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
7545 - Port the hs_ntor handshake test to work correctly with recent
7546 versions of the pysha3 module. Fixes bug 23071; bugfix
7549 o Minor bugfixes (Windows service):
7550 - When running as a Windows service, set the ID of the main thread
7551 correctly. Failure to do so made us fail to send log messages to
7552 the controller in 0.2.1.16-rc, slowed down controller event
7553 delivery in 0.2.7.3-rc and later, and crash with an assertion
7554 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
7555 Patch and diagnosis from "Vort".
7558 Changes in version 0.3.0.10 - 2017-08-02
7559 Tor 0.3.0.10 backports a collection of small-to-medium bugfixes
7560 from the current Tor alpha series. OpenBSD users and TPROXY users
7561 should upgrade; others are probably okay sticking with 0.3.0.9.
7563 o Major features (build system, continuous integration, backport from 0.3.1.5-alpha):
7564 - Tor's repository now includes a Travis Continuous Integration (CI)
7565 configuration file (.travis.yml). This is meant to help new
7566 developers and contributors who fork Tor to a Github repository be
7567 better able to test their changes, and understand what we expect
7568 to pass. To use this new build feature, you must fork Tor to your
7569 Github account, then go into the "Integrations" menu in the
7570 repository settings for your fork and enable Travis, then push
7571 your changes. Closes ticket 22636.
7573 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
7574 - Fix a typo that had prevented TPROXY-based transparent proxying
7575 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
7576 Patch from "d4fq0fQAgoJ".
7578 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
7579 - Avoid an assertion failure bug affecting our implementation of
7580 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
7581 handling of "0xbar" differs from what we had expected. Fixes bug
7582 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
7584 o Minor features (backport from 0.3.1.5-alpha):
7585 - Update geoip and geoip6 to the July 4 2017 Maxmind GeoLite2
7588 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.2-alpha):
7589 - Roll over monthly accounting at the configured hour and minute,
7590 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
7591 Found by Andrey Karpov with PVS-Studio.
7593 o Minor bugfixes (compilation warnings, backport from 0.3.1.5-alpha):
7594 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
7595 bugfix on 0.2.8.1-alpha.
7596 - Fix warnings when building with libscrypt and openssl scrypt
7597 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
7598 - When building with certain versions of the mingw C header files,
7599 avoid float-conversion warnings when calling the C functions
7600 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
7603 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
7604 - Backport a fix for an "unused variable" warning that appeared
7605 in some versions of mingw. Fixes bug 22838; bugfix on
7608 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
7609 - Avoid Coverity build warnings related to our BUG() macro. By
7610 default, Coverity treats BUG() as the Linux kernel does: an
7611 instant abort(). We need to override that so our BUG() macro
7612 doesn't prevent Coverity from analyzing functions that use it.
7613 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
7615 o Minor bugfixes (directory authority, backport from 0.3.1.1-alpha):
7616 - When rejecting a router descriptor for running an obsolete version
7617 of Tor without ntor support, warn about the obsolete tor version,
7618 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
7620 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
7621 - Avoid a sandbox failure when trying to re-bind to a socket and
7622 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
7624 o Minor bugfixes (unit tests, backport from 0.3.1.5-alpha)
7625 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
7626 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
7629 Changes in version 0.3.1.5-alpha - 2017-08-01
7630 Tor 0.3.1.5-alpha improves the performance of consensus diff
7631 calculation, fixes a crash bug on older versions of OpenBSD, and fixes
7632 several other bugs. If no serious bugs are found in this version, the
7633 next version will be a release candidate.
7635 This release also marks the end of support for the Tor 0.2.4.x,
7636 0.2.6.x, and 0.2.7.x release series. Those releases will receive no
7637 further bug or security fixes. Anyone still running or distributing
7638 one of those versions should upgrade.
7640 o Major features (build system, continuous integration):
7641 - Tor's repository now includes a Travis Continuous Integration (CI)
7642 configuration file (.travis.yml). This is meant to help new
7643 developers and contributors who fork Tor to a Github repository be
7644 better able to test their changes, and understand what we expect
7645 to pass. To use this new build feature, you must fork Tor to your
7646 Github account, then go into the "Integrations" menu in the
7647 repository settings for your fork and enable Travis, then push
7648 your changes. Closes ticket 22636.
7650 o Major bugfixes (openbsd, denial-of-service):
7651 - Avoid an assertion failure bug affecting our implementation of
7652 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
7653 handling of "0xbar" differs from what we had expected. Fixes bug
7654 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
7656 o Major bugfixes (relay, performance):
7657 - Perform circuit handshake operations at a higher priority than we
7658 use for consensus diff creation and compression. This should
7659 prevent circuits from starving when a relay or bridge receives a
7660 new consensus, especially on lower-powered machines. Fixes bug
7661 22883; bugfix on 0.3.1.1-alpha.
7663 o Minor features (bridge authority):
7664 - Add "fingerprint" lines to the networkstatus-bridges file produced
7665 by bridge authorities. Closes ticket 22207.
7667 o Minor features (directory cache, consensus diff):
7668 - Add a new MaxConsensusAgeForDiffs option to allow directory cache
7669 operators with low-resource environments to adjust the number of
7670 consensuses they'll store and generate diffs from. Most cache
7671 operators should leave it unchanged. Helps to work around
7674 o Minor features (geoip):
7675 - Update geoip and geoip6 to the July 4 2017 Maxmind GeoLite2
7678 o Minor features (relay, performance):
7679 - Always start relays with at least two worker threads, to prevent
7680 priority inversion on slow tasks. Part of the fix for bug 22883.
7681 - Allow background work to be queued with different priorities, so
7682 that a big pile of slow low-priority jobs will not starve out
7683 higher priority jobs. This lays the groundwork for a fix for
7686 o Minor bugfixes (build system, rust):
7687 - Fix a problem where Rust toolchains were not being found when
7688 building without --enable-cargo-online-mode, due to setting the
7689 $HOME environment variable instead of $CARGO_HOME. Fixes bug
7690 22830; bugfix on 0.3.1.1-alpha. Fix by Chelsea Komlo.
7692 o Minor bugfixes (compatibility, zstd):
7693 - Write zstd epilogues correctly when the epilogue requires
7694 reallocation of the output buffer, even with zstd 1.3.0.
7695 (Previously, we worked on 1.2.0 and failed with 1.3.0). Fixes bug
7696 22927; bugfix on 0.3.1.1-alpha.
7698 o Minor bugfixes (compilation warnings):
7699 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug
7700 22915; bugfix on 0.2.8.1-alpha.
7701 - Fix warnings when building with libscrypt and openssl scrypt
7702 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
7703 - Compile correctly when both openssl 1.1.0 and libscrypt are
7704 detected. Previously this would cause an error. Fixes bug 22892;
7705 bugfix on 0.3.1.1-alpha.
7706 - When building with certain versions of the mingw C header files,
7707 avoid float-conversion warnings when calling the C functions
7708 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
7711 o Minor bugfixes (coverity build support):
7712 - Avoid Coverity build warnings related to our BUG() macro. By
7713 default, Coverity treats BUG() as the Linux kernel does: an
7714 instant abort(). We need to override that so our BUG() macro
7715 doesn't prevent Coverity from analyzing functions that use it.
7716 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
7718 o Minor bugfixes (directory authority):
7719 - When a directory authority rejects a descriptor or extrainfo with
7720 a given digest, mark that digest as undownloadable, so that we do
7721 not attempt to download it again over and over. We previously
7722 tried to avoid downloading such descriptors by other means, but we
7723 didn't notice if we accidentally downloaded one anyway. This
7724 behavior became problematic in 0.2.7.2-alpha, when authorities
7725 began pinning Ed25519 keys. Fixes bug 22349; bugfix
7728 o Minor bugfixes (error reporting, windows):
7729 - When formatting Windows error messages, use the English format to
7730 avoid codepage issues. Fixes bug 22520; bugfix on 0.1.2.8-alpha.
7733 o Minor bugfixes (file limits, osx):
7734 - When setting the maximum number of connections allowed by the OS,
7735 always allow some extra file descriptors for other files. Fixes
7736 bug 22797; bugfix on 0.2.0.10-alpha.
7738 o Minor bugfixes (linux seccomp2 sandbox):
7739 - Avoid a sandbox failure when trying to re-bind to a socket and
7740 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
7742 o Minor bugfixes (memory leaks):
7743 - Fix a small memory leak when validating a configuration that uses
7744 two or more AF_UNIX sockets for the same port type. Fixes bug
7745 23053; bugfix on 0.2.6.3-alpha. This is CID 1415725.
7747 o Minor bugfixes (unit tests):
7748 - test_consdiff_base64cmp would fail on OS X because while OS X
7749 follows the standard of (less than zero/zero/greater than zero),
7750 it doesn't follow the convention of (-1/0/+1). Make the test
7751 comply with the standard. Fixes bug 22870; bugfix on 0.3.1.1-alpha.
7752 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
7753 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
7756 Changes in version 0.3.1.4-alpha - 2017-06-29
7757 Tor 0.3.1.4-alpha fixes a path selection bug that would allow a client
7758 to use a guard that was in the same network family as a chosen exit
7759 relay. This is a security regression; all clients running earlier
7760 versions of 0.3.0.x or 0.3.1.x should upgrade to 0.3.0.9
7763 This release also fixes several other bugs introduced in 0.3.0.x
7764 and 0.3.1.x, including others that can affect bandwidth usage
7768 - To build with zstd and lzma support, Tor now requires the
7769 pkg-config tool at build time. (This requirement was new in
7770 0.3.1.1-alpha, but was not noted at the time. Noting it here to
7771 close ticket 22623.)
7773 o Major bugfixes (path selection, security):
7774 - When choosing which guard to use for a circuit, avoid the exit's
7775 family along with the exit itself. Previously, the new guard
7776 selection logic avoided the exit, but did not consider its family.
7777 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
7778 006 and CVE-2017-0377.
7780 o Major bugfixes (compression, zstd):
7781 - Correctly detect a full buffer when decompressing a large zstd-
7782 compressed input. Previously, we would sometimes treat a full
7783 buffer as an error. Fixes bug 22628; bugfix on 0.3.1.1-alpha.
7785 o Major bugfixes (directory protocol):
7786 - Ensure that we send "304 Not modified" as HTTP status code when a
7787 client is attempting to fetch a consensus or consensus diff, and
7788 the best one we can send them is one they already have. Fixes bug
7789 22702; bugfix on 0.3.1.1-alpha.
7791 o Major bugfixes (entry guards):
7792 - When starting with an old consensus, do not add new entry guards
7793 unless the consensus is "reasonably live" (under 1 day old). Fixes
7794 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
7796 o Minor features (bug mitigation, diagnostics, logging):
7797 - Avoid an assertion failure, and log a better error message, when
7798 unable to remove a file from the consensus cache on Windows.
7799 Attempts to mitigate and diagnose bug 22752.
7801 o Minor features (geoip):
7802 - Update geoip and geoip6 to the June 8 2017 Maxmind GeoLite2
7805 o Minor bugfixes (compression):
7806 - When compressing or decompressing a buffer, check for a failure to
7807 create a compression object. Fixes bug 22626; bugfix
7809 - When decompressing a buffer, check for extra data after the end of
7810 the compressed data. Fixes bug 22629; bugfix on 0.3.1.1-alpha.
7811 - When decompressing an object received over an anonymous directory
7812 connection, if we have already decompressed it using an acceptable
7813 compression method, do not reject it for looking like an
7814 unacceptable compression method. Fixes part of bug 22670; bugfix
7816 - When serving directory votes compressed with zlib, do not claim to
7817 have compressed them with zstd. Fixes bug 22669; bugfix
7819 - When spooling compressed data to an output buffer, don't try to
7820 spool more data when there is no more data to spool and we are not
7821 trying to flush the input. Previously, we would sometimes launch
7822 compression requests with nothing to do, which interferes with our
7823 22672 checks. Fixes bug 22719; bugfix on 0.2.0.16-alpha.
7825 o Minor bugfixes (defensive programming):
7826 - Detect and break out of infinite loops in our compression code. We
7827 don't think that any such loops exist now, but it's best to be
7828 safe. Closes ticket 22672.
7829 - Fix a memset() off the end of an array when packing cells. This
7830 bug should be harmless in practice, since the corrupted bytes are
7831 still in the same structure, and are always padding bytes,
7832 ignored, or immediately overwritten, depending on compiler
7833 behavior. Nevertheless, because the memset()'s purpose is to make
7834 sure that any other cell-handling bugs can't expose bytes to the
7835 network, we need to fix it. Fixes bug 22737; bugfix on
7836 0.2.4.11-alpha. Fixes CID 1401591.
7838 o Minor bugfixes (linux seccomp2 sandbox):
7839 - Permit the fchmod system call, to avoid crashing on startup when
7840 starting with the seccomp2 sandbox and an unexpected set of
7841 permissions on the data directory or its contents. Fixes bug
7842 22516; bugfix on 0.2.5.4-alpha.
7843 - Fix a crash in the LZMA module, when the sandbox was enabled, and
7844 liblzma would allocate more than 16 MB of memory. We solve this by
7845 bumping the mprotect() limit in the sandbox module from 16 MB to
7846 20 MB. Fixes bug 22751; bugfix on 0.3.1.1-alpha.
7848 o Minor bugfixes (logging):
7849 - When decompressing, do not warn if we fail to decompress using a
7850 compression method that we merely guessed. Fixes part of bug
7851 22670; bugfix on 0.1.1.14-alpha.
7852 - When decompressing, treat mismatch between content-encoding and
7853 actual compression type as a protocol warning. Fixes part of bug
7854 22670; bugfix on 0.1.1.9-alpha.
7855 - Downgrade "assigned_to_cpuworker failed" message to info-level
7856 severity. In every case that can reach it, either a better warning
7857 has already been logged, or no warning is warranted. Fixes bug
7858 22356; bugfix on 0.2.6.3-alpha.
7859 - Demote a warn that was caused by libevent delays to info if
7860 netflow padding is less than 4.5 seconds late, or to notice
7861 if it is more (4.5 seconds is the amount of time that a netflow
7862 record might be emitted after, if we chose the maximum timeout).
7863 Fixes bug 22212; bugfix on 0.3.1.1-alpha.
7865 o Minor bugfixes (process behavior):
7866 - When exiting because of an error, always exit with a nonzero exit
7867 status. Previously, we would fail to report an error in our exit
7868 status in cases related to __OwningControllerProcess failure,
7869 lockfile contention, and Ed25519 key initialization. Fixes bug
7870 22720; bugfix on versions 0.2.1.6-alpha, 0.2.2.28-beta, and
7871 0.2.7.2-alpha respectively. Reported by "f55jwk4f"; patch
7875 - Add a manpage description for the key-pinning-journal file. Closes
7877 - Correctly note that bandwidth accounting values are stored in the
7878 state file, and the bw_accounting file is now obsolete. Closes
7880 - Document more of the files in the Tor data directory, including
7881 cached-extrainfo, secret_onion_key{,_ntor}.old, hidserv-stats,
7882 approved-routers, sr-random, and diff-cache. Found while fixing
7886 Changes in version 0.3.0.9 - 2017-06-29
7887 Tor 0.3.0.9 fixes a path selection bug that would allow a client
7888 to use a guard that was in the same network family as a chosen exit
7889 relay. This is a security regression; all clients running earlier
7890 versions of 0.3.0.x or 0.3.1.x should upgrade to 0.3.0.9 or
7893 This release also backports several other bugfixes from the 0.3.1.x
7896 o Major bugfixes (path selection, security, backport from 0.3.1.4-alpha):
7897 - When choosing which guard to use for a circuit, avoid the exit's
7898 family along with the exit itself. Previously, the new guard
7899 selection logic avoided the exit, but did not consider its family.
7900 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
7901 006 and CVE-2017-0377.
7903 o Major bugfixes (entry guards, backport from 0.3.1.1-alpha):
7904 - Don't block bootstrapping when a primary bridge is offline and we
7905 can't get its descriptor. Fixes bug 22325; fixes one case of bug
7906 21969; bugfix on 0.3.0.3-alpha.
7908 o Major bugfixes (entry guards, backport from 0.3.1.4-alpha):
7909 - When starting with an old consensus, do not add new entry guards
7910 unless the consensus is "reasonably live" (under 1 day old). Fixes
7911 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
7913 o Minor features (geoip):
7914 - Update geoip and geoip6 to the June 8 2017 Maxmind GeoLite2
7917 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
7918 - Reject version numbers with non-numeric prefixes (such as +, -, or
7919 whitespace). Disallowing whitespace prevents differential version
7920 parsing between POSIX-based and Windows platforms. Fixes bug 21507
7921 and part of 21508; bugfix on 0.0.8pre1.
7923 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
7924 - Permit the fchmod system call, to avoid crashing on startup when
7925 starting with the seccomp2 sandbox and an unexpected set of
7926 permissions on the data directory or its contents. Fixes bug
7927 22516; bugfix on 0.2.5.4-alpha.
7929 o Minor bugfixes (defensive programming, backport from 0.3.1.4-alpha):
7930 - Fix a memset() off the end of an array when packing cells. This
7931 bug should be harmless in practice, since the corrupted bytes are
7932 still in the same structure, and are always padding bytes,
7933 ignored, or immediately overwritten, depending on compiler
7934 behavior. Nevertheless, because the memset()'s purpose is to make
7935 sure that any other cell-handling bugs can't expose bytes to the
7936 network, we need to fix it. Fixes bug 22737; bugfix on
7937 0.2.4.11-alpha. Fixes CID 1401591.
7940 Changes in version 0.3.1.3-alpha - 2017-06-08
7941 Tor 0.3.1.3-alpha fixes a pair of bugs that would allow an attacker to
7942 remotely crash a hidden service with an assertion failure. Anyone
7943 running a hidden service should upgrade to this version, or to some
7944 other version with fixes for TROVE-2017-004 and TROVE-2017-005.
7946 Tor 0.3.1.3-alpha also includes fixes for several key management bugs
7947 that sometimes made relays unreliable, as well as several other
7948 bugfixes described below.
7950 o Major bugfixes (hidden service, relay, security):
7951 - Fix a remotely triggerable assertion failure when a hidden service
7952 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
7953 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
7954 - Fix a remotely triggerable assertion failure caused by receiving a
7955 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
7956 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
7959 o Major bugfixes (relay, link handshake):
7960 - When performing the v3 link handshake on a TLS connection, report
7961 that we have the x509 certificate that we actually used on that
7962 connection, even if we have changed certificates since that
7963 connection was first opened. Previously, we would claim to have
7964 used our most recent x509 link certificate, which would sometimes
7965 make the link handshake fail. Fixes one case of bug 22460; bugfix
7968 o Major bugfixes (relays, key management):
7969 - Regenerate link and authentication certificates whenever the key
7970 that signs them changes; also, regenerate link certificates
7971 whenever the signed key changes. Previously, these processes were
7972 only weakly coupled, and we relays could (for minutes to hours)
7973 wind up with an inconsistent set of keys and certificates, which
7974 other relays would not accept. Fixes two cases of bug 22460;
7975 bugfix on 0.3.0.1-alpha.
7976 - When sending an Ed25519 signing->link certificate in a CERTS cell,
7977 send the certificate that matches the x509 certificate that we
7978 used on the TLS connection. Previously, there was a race condition
7979 if the TLS context rotated after we began the TLS handshake but
7980 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
7983 o Major bugfixes (torrc, crash):
7984 - Fix a crash bug when using %include in torrc. Fixes bug 22417;
7985 bugfix on 0.3.1.1-alpha. Patch by Daniel Pinto.
7987 o Minor features (code style):
7988 - Add "Falls through" comments to our codebase, in order to silence
7989 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
7990 Stieger. Closes ticket 22446.
7992 o Minor features (diagnostic):
7993 - Add logging messages to try to diagnose a rare bug that seems to
7994 generate RSA->Ed25519 cross-certificates dated in the 1970s. We
7995 think this is happening because of incorrect system clocks, but
7996 we'd like to know for certain. Diagnostic for bug 22466.
7998 o Minor bugfixes (correctness):
7999 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
8000 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
8002 o Minor bugfixes (directory protocol):
8003 - Check for libzstd >= 1.1, because older versions lack the
8004 necessary streaming API. Fixes bug 22413; bugfix on 0.3.1.1-alpha.
8006 o Minor bugfixes (link handshake):
8007 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
8008 months, and regenerate it when it is within one month of expiring.
8009 Previously, we had generated this certificate at startup with a
8010 ten-year lifetime, but that could lead to weird behavior when Tor
8011 was started with a grossly inaccurate clock. Mitigates bug 22466;
8012 mitigation on 0.3.0.1-alpha.
8014 o Minor bugfixes (storage directories):
8015 - Always check for underflows in the cached storage directory usage.
8016 If the usage does underflow, re-calculate it. Also, avoid a
8017 separate underflow when the usage is not known. Fixes bug 22424;
8018 bugfix on 0.3.1.1-alpha.
8020 o Minor bugfixes (unit tests):
8021 - The unit tests now pass on systems where localhost is misconfigured
8022 to some IPv4 address other than 127.0.0.1. Fixes bug 6298; bugfix
8026 - Clarify the manpage for the (deprecated) torify script. Closes
8029 Changes in version 0.3.0.8 - 2017-06-08
8030 Tor 0.3.0.8 fixes a pair of bugs that would allow an attacker to
8031 remotely crash a hidden service with an assertion failure. Anyone
8032 running a hidden service should upgrade to this version, or to some
8033 other version with fixes for TROVE-2017-004 and TROVE-2017-005.
8035 Tor 0.3.0.8 also includes fixes for several key management bugs
8036 that sometimes made relays unreliable, as well as several other
8037 bugfixes described below.
8039 o Major bugfixes (hidden service, relay, security, backport
8040 from 0.3.1.3-alpha):
8041 - Fix a remotely triggerable assertion failure when a hidden service
8042 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
8043 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
8044 - Fix a remotely triggerable assertion failure caused by receiving a
8045 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
8046 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
8049 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
8050 - When performing the v3 link handshake on a TLS connection, report
8051 that we have the x509 certificate that we actually used on that
8052 connection, even if we have changed certificates since that
8053 connection was first opened. Previously, we would claim to have
8054 used our most recent x509 link certificate, which would sometimes
8055 make the link handshake fail. Fixes one case of bug 22460; bugfix
8058 o Major bugfixes (relays, key management, backport from 0.3.1.3-alpha):
8059 - Regenerate link and authentication certificates whenever the key
8060 that signs them changes; also, regenerate link certificates
8061 whenever the signed key changes. Previously, these processes were
8062 only weakly coupled, and we relays could (for minutes to hours)
8063 wind up with an inconsistent set of keys and certificates, which
8064 other relays would not accept. Fixes two cases of bug 22460;
8065 bugfix on 0.3.0.1-alpha.
8066 - When sending an Ed25519 signing->link certificate in a CERTS cell,
8067 send the certificate that matches the x509 certificate that we
8068 used on the TLS connection. Previously, there was a race condition
8069 if the TLS context rotated after we began the TLS handshake but
8070 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
8073 o Major bugfixes (hidden service v3, backport from 0.3.1.1-alpha):
8074 - Stop rejecting v3 hidden service descriptors because their size
8075 did not match an old padding rule. Fixes bug 22447; bugfix on
8078 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
8079 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
8080 December 2016 (of which ~126 were still functional) with a list of
8081 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
8082 2017. Resolves ticket 21564.
8084 o Minor bugfixes (configuration, backport from 0.3.1.1-alpha):
8085 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
8086 bug 22252; bugfix on 0.2.9.3-alpha.
8088 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
8089 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
8090 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
8092 o Minor bugfixes (link handshake, backport from 0.3.1.3-alpha):
8093 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
8094 months, and regenerate it when it is within one month of expiring.
8095 Previously, we had generated this certificate at startup with a
8096 ten-year lifetime, but that could lead to weird behavior when Tor
8097 was started with a grossly inaccurate clock. Mitigates bug 22466;
8098 mitigation on 0.3.0.1-alpha.
8100 o Minor bugfixes (memory leak, directory authority, backport from
8102 - When directory authorities reject a router descriptor due to
8103 keypinning, free the router descriptor rather than leaking the
8104 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
8107 Changes in version 0.2.9.11 - 2017-06-08
8108 Tor 0.2.9.11 backports a fix for a bug that would allow an attacker to
8109 remotely crash a hidden service with an assertion failure. Anyone
8110 running a hidden service should upgrade to this version, or to some
8111 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
8112 are not affected by TROVE-2017-004.)
8114 Tor 0.2.9.11 also backports fixes for several key management bugs
8115 that sometimes made relays unreliable, as well as several other
8116 bugfixes described below.
8118 o Major bugfixes (hidden service, relay, security, backport
8119 from 0.3.1.3-alpha):
8120 - Fix a remotely triggerable assertion failure caused by receiving a
8121 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
8122 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
8125 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
8126 - When performing the v3 link handshake on a TLS connection, report
8127 that we have the x509 certificate that we actually used on that
8128 connection, even if we have changed certificates since that
8129 connection was first opened. Previously, we would claim to have
8130 used our most recent x509 link certificate, which would sometimes
8131 make the link handshake fail. Fixes one case of bug 22460; bugfix
8134 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
8135 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
8136 December 2016 (of which ~126 were still functional) with a list of
8137 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
8138 2017. Resolves ticket 21564.
8140 o Minor features (future-proofing, backport from 0.3.0.7):
8141 - Tor no longer refuses to download microdescriptors or descriptors if
8142 they are listed as "published in the future". This change will
8143 eventually allow us to stop listing meaningful "published" dates
8144 in microdescriptor consensuses, and thereby allow us to reduce the
8145 resources required to download consensus diffs by over 50%.
8146 Implements part of ticket 21642; implements part of proposal 275.
8148 o Minor features (directory authorities, backport from 0.3.0.4-rc)
8149 - Directory authorities now reject relays running versions
8150 0.2.9.1-alpha through 0.2.9.4-alpha, because those relays
8151 suffer from bug 20499 and don't keep their consensus cache
8152 up-to-date. Resolves ticket 20509.
8154 o Minor features (geoip):
8155 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
8158 o Minor bugfixes (control port, backport from 0.3.0.6):
8159 - The GETINFO extra-info/digest/<digest> command was broken because
8160 of a wrong base16 decode return value check, introduced when
8161 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
8163 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
8164 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
8165 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
8167 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.0.7):
8168 - The getpid() system call is now permitted under the Linux seccomp2
8169 sandbox, to avoid crashing with versions of OpenSSL (and other
8170 libraries) that attempt to learn the process's PID by using the
8171 syscall rather than the VDSO code. Fixes bug 21943; bugfix
8174 o Minor bugfixes (memory leak, directory authority, backport
8175 from 0.3.1.2-alpha):
8176 - When directory authorities reject a router descriptor due to
8177 keypinning, free the router descriptor rather than leaking the
8178 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
8180 Changes in version 0.2.8.14 - 2017-06-08
8181 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
8182 remotely crash a hidden service with an assertion failure. Anyone
8183 running a hidden service should upgrade to this version, or to some
8184 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
8185 are not affected by TROVE-2017-004.)
8187 o Major bugfixes (hidden service, relay, security):
8188 - Fix a remotely triggerable assertion failure caused by receiving a
8189 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
8190 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
8193 o Minor features (geoip):
8194 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
8197 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
8198 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
8199 December 2016 (of which ~126 were still functional) with a list of
8200 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
8201 2017. Resolves ticket 21564.
8203 o Minor bugfixes (correctness):
8204 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
8205 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
8207 Changes in version 0.2.7.8 - 2017-06-08
8208 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
8209 remotely crash a hidden service with an assertion failure. Anyone
8210 running a hidden service should upgrade to this version, or to some
8211 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
8212 are not affected by TROVE-2017-004.)
8214 o Major bugfixes (hidden service, relay, security):
8215 - Fix a remotely triggerable assertion failure caused by receiving a
8216 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
8217 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
8220 o Minor features (geoip):
8221 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
8224 o Minor bugfixes (correctness):
8225 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
8226 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
8229 Changes in version 0.2.6.12 - 2017-06-08
8230 Tor 0.2.6.12 backports a fix for a bug that would allow an attacker to
8231 remotely crash a hidden service with an assertion failure. Anyone
8232 running a hidden service should upgrade to this version, or to some
8233 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
8234 are not affected by TROVE-2017-004.)
8236 o Major bugfixes (hidden service, relay, security):
8237 - Fix a remotely triggerable assertion failure caused by receiving a
8238 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
8239 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
8242 o Minor features (geoip):
8243 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
8246 o Minor bugfixes (correctness):
8247 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
8248 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
8250 Changes in version 0.2.5.14 - 2017-06-08
8251 Tor 0.2.5.14 backports a fix for a bug that would allow an attacker to
8252 remotely crash a hidden service with an assertion failure. Anyone
8253 running a hidden service should upgrade to this version, or to some
8254 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
8255 are not affected by TROVE-2017-004.)
8257 o Major bugfixes (hidden service, relay, security):
8258 - Fix a remotely triggerable assertion failure caused by receiving a
8259 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
8260 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
8263 o Minor features (geoip):
8264 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
8267 o Minor bugfixes (correctness):
8268 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
8269 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
8271 Changes in version 0.2.4.29 - 2017-06-08
8272 Tor 0.2.4.29 backports a fix for a bug that would allow an attacker to
8273 remotely crash a hidden service with an assertion failure. Anyone
8274 running a hidden service should upgrade to this version, or to some
8275 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
8276 are not affected by TROVE-2017-004.)
8278 o Major bugfixes (hidden service, relay, security):
8279 - Fix a remotely triggerable assertion failure caused by receiving a
8280 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
8281 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
8284 o Minor features (geoip):
8285 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
8288 o Minor bugfixes (correctness):
8289 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
8290 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
8293 Changes in version 0.3.1.2-alpha - 2017-05-26
8294 Tor 0.3.1.2-alpha is the second release in the 0.3.1.x series. It
8295 fixes a few bugs found while testing 0.3.1.1-alpha, including a
8296 memory corruption bug that affected relay stability.
8298 o Major bugfixes (crash, relay):
8299 - Fix a memory-corruption bug in relays that set MyFamily.
8300 Previously, they would double-free MyFamily elements when making
8301 the next descriptor or when changing their configuration. Fixes
8302 bug 22368; bugfix on 0.3.1.1-alpha.
8304 o Minor bugfixes (logging):
8305 - Log a better message when a directory authority replies to an
8306 upload with an unexpected status code. Fixes bug 11121; bugfix
8309 o Minor bugfixes (memory leak, directory authority):
8310 - When directory authorities reject a router descriptor due to
8311 keypinning, free the router descriptor rather than leaking the
8312 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
8315 Changes in version 0.3.1.1-alpha - 2017-05-22
8316 Tor 0.3.1.1-alpha is the first release in the 0.3.1.x series. It
8317 reduces the bandwidth usage for Tor's directory protocol, adds some
8318 basic padding to resist netflow-based traffic analysis and to serve as
8319 the basis of other padding in the future, and adds rust support to the
8322 It also contains numerous other small features and improvements to
8323 security, correctness, and performance.
8325 Below are the changes since 0.3.0.7.
8327 o Major features (directory protocol):
8328 - Tor relays and authorities can now serve clients an abbreviated
8329 version of the consensus document, containing only the changes
8330 since an older consensus document that the client holds. Clients
8331 now request these documents when available. When both client and
8332 server use this new protocol, they will use far less bandwidth (up
8333 to 94% less) to keep the client's consensus up-to-date. Implements
8334 proposal 140; closes ticket 13339. Based on work by Daniel Martí.
8335 - Tor can now compress directory traffic with lzma or with zstd
8336 compression algorithms, which can deliver better bandwidth
8337 performance. Because lzma is computationally expensive, it's only
8338 used for documents that can be compressed once and served many
8339 times. Support for these algorithms requires that tor is built
8340 with the libzstd and/or liblzma libraries available. Implements
8341 proposal 278; closes ticket 21662.
8342 - Relays now perform the more expensive compression operations, and
8343 consensus diff generation, in worker threads. This separation
8344 avoids delaying the main thread when a new consensus arrives.
8346 o Major features (experimental):
8347 - Tor can now build modules written in Rust. To turn this on, pass
8348 the "--enable-rust" flag to the configure script. It's not time to
8349 get excited yet: currently, there is no actual Rust functionality
8350 beyond some simple glue code, and a notice at startup to tell you
8351 that Rust is running. Still, we hope that programmers and
8352 packagers will try building Tor with Rust support, so that we can
8353 find issues and solve portability problems. Closes ticket 22106.
8355 o Major features (traffic analysis resistance):
8356 - Connections between clients and relays now send a padding cell in
8357 each direction every 1.5 to 9.5 seconds (tunable via consensus
8358 parameters). This padding will not resist specialized
8359 eavesdroppers, but it should be enough to make many ISPs' routine
8360 network flow logging less useful in traffic analysis against
8363 Padding is negotiated using Tor's link protocol, so both relays
8364 and clients must upgrade for this to take effect. Clients may
8365 still send padding despite the relay's version by setting
8366 ConnectionPadding 1 in torrc, and may disable padding by setting
8367 ConnectionPadding 0 in torrc. Padding may be minimized for mobile
8368 users with the torrc option ReducedConnectionPadding. Implements
8369 Proposal 251 and Section 2 of Proposal 254; closes ticket 16861.
8370 - Relays will publish 24 hour totals of padding and non-padding cell
8371 counts to their extra-info descriptors, unless PaddingStatistics 0
8372 is set in torrc. These 24 hour totals are also rounded to
8375 o Major bugfixes (connection usage):
8376 - We use NETINFO cells to try to determine if both relays involved
8377 in a connection will agree on the canonical status of that
8378 connection. We prefer the connections where this is the case for
8379 extend cells, and try to close connections where relays disagree
8380 on their canonical status early. Also, we now prefer the oldest
8381 valid connection for extend cells. These two changes should reduce
8382 the number of long-term connections that are kept open between
8383 relays. Fixes bug 17604; bugfix on 0.2.5.5-alpha.
8384 - Relays now log hourly statistics (look for
8385 "channel_check_for_duplicates" lines) on the total number of
8386 connections to other relays. If the number of connections per
8387 relay is unexpectedly large, this log message is at notice level.
8388 Otherwise it is at info.
8390 o Major bugfixes (entry guards):
8391 - Don't block bootstrapping when a primary bridge is offline and we
8392 can't get its descriptor. Fixes bug 22325; fixes one case of bug
8393 21969; bugfix on 0.3.0.3-alpha.
8395 o Major bugfixes (linux TPROXY support):
8396 - Fix a typo that had prevented TPROXY-based transparent proxying
8397 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
8398 Patch from "d4fq0fQAgoJ".
8400 o Minor features (security, windows):
8401 - Enable a couple of pieces of Windows hardening: one
8402 (HeapEnableTerminationOnCorruption) that has been on-by-default
8403 since Windows 8, and unavailable before Windows 7; and one
8404 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
8405 affect us, but shouldn't do any harm. Closes ticket 21953.
8407 o Minor features (config options):
8408 - Allow "%include" directives in torrc configuration files. These
8409 directives import the settings from other files, or from all the
8410 files in a directory. Closes ticket 1922. Code by Daniel Pinto.
8411 - Make SAVECONF return an error when overwriting a torrc that has
8412 includes. Using SAVECONF with the FORCE option will allow it to
8413 overwrite torrc even if includes are used. Related to ticket 1922.
8414 - Add "GETINFO config-can-saveconf" to tell controllers if SAVECONF
8415 will work without the FORCE option. Related to ticket 1922.
8417 o Minor features (controller):
8418 - Warn the first time that a controller requests data in the long-
8419 deprecated 'GETINFO network-status' format. Closes ticket 21703.
8421 o Minor features (defaults):
8422 - The default value for UseCreateFast is now 0: clients which
8423 haven't yet received a consensus document will now use a proper
8424 ntor handshake to talk to their directory servers whenever they
8425 can. Closes ticket 21407.
8426 - Onion key rotation and expiry intervals are now defined as a
8427 network consensus parameter, per proposal 274. The default
8428 lifetime of an onion key is increased from 7 to 28 days. Old onion
8429 keys will expire after 7 days by default. This change will make
8430 consensus diffs much smaller, and save significant bandwidth.
8431 Closes ticket 21641.
8433 o Minor features (fallback directory list):
8434 - Update the fallback directory mirror whitelist and blacklist based
8435 on operator emails. Closes task 21121.
8436 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
8437 December 2016 (of which ~126 were still functional) with a list of
8438 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
8439 2017. Resolves ticket 21564.
8441 o Minor features (hidden services, logging):
8442 - Log a message when a hidden service descriptor has fewer
8443 introduction points than specified in
8444 HiddenServiceNumIntroductionPoints. Closes tickets 21598.
8445 - Log a message when a hidden service reaches its introduction point
8446 circuit limit, and when that limit is reset. Follow up to ticket
8447 21594; closes ticket 21622.
8448 - Warn user if multiple entries in EntryNodes and at least one
8449 HiddenService are used together. Pinning EntryNodes along with a
8450 hidden service can be possibly harmful; for instance see ticket
8451 14917 or 21155. Closes ticket 21155.
8453 o Minor features (linux seccomp2 sandbox):
8454 - We now have a document storage backend compatible with the Linux
8455 seccomp2 sandbox. This backend is used for consensus documents and
8456 diffs between them; in the long term, we'd like to use it for
8457 unparseable directory material too. Closes ticket 21645
8458 - Increase the maximum allowed size passed to mprotect(PROT_WRITE)
8459 from 1MB to 16MB. This was necessary with the glibc allocator in
8460 order to allow worker threads to allocate more memory -- which in
8461 turn is necessary because of our new use of worker threads for
8462 compression. Closes ticket 22096.
8464 o Minor features (logging):
8465 - Log files are no longer created world-readable by default.
8466 (Previously, most distributors would store the logs in a non-
8467 world-readable location to prevent inappropriate access. This
8468 change is an extra precaution.) Closes ticket 21729; patch
8471 o Minor features (performance):
8472 - Our Keccak (SHA-3) implementation now accesses memory more
8473 efficiently, especially on little-endian systems. Closes
8475 - Add an O(1) implementation of channel_find_by_global_id(), to
8476 speed some controller functions.
8478 o Minor features (relay, configuration):
8479 - The MyFamily option may now be repeated as many times as desired,
8480 for relays that want to configure large families. Closes ticket
8481 4998; patch by Daniel Pinto.
8483 o Minor features (safety):
8484 - Add an explicit check to extrainfo_parse_entry_from_string() for
8485 NULL inputs. We don't believe this can actually happen, but it may
8486 help silence a warning from the Clang analyzer. Closes
8489 o Minor features (testing):
8490 - Add a "--disable-memory-sentinels" feature to help with fuzzing.
8491 When Tor is compiled with this option, we disable a number of
8492 redundant memory-safety failsafes that are intended to stop bugs
8493 from becoming security issues. This makes it easier to hunt for
8494 bugs that would be security issues without the failsafes turned
8495 on. Closes ticket 21439.
8496 - Add a general event-tracing instrumentation support to Tor. This
8497 subsystem will enable developers and researchers to add fine-
8498 grained instrumentation to their Tor instances, for use when
8499 examining Tor network performance issues. There are no trace
8500 events yet, and event-tracing is off by default unless enabled at
8501 compile time. Implements ticket 13802.
8502 - Improve our version parsing tests: add tests for typical version
8503 components, add tests for invalid versions, including numeric
8504 range and non-numeric prefixes. Unit tests 21278, 21450, and
8505 21507. Partially implements 21470.
8507 o Minor bugfixes (bandwidth accounting):
8508 - Roll over monthly accounting at the configured hour and minute,
8509 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
8510 Found by Andrey Karpov with PVS-Studio.
8512 o Minor bugfixes (code correctness):
8513 - Accurately identify client connections by their lack of peer
8514 authentication. This means that we bail out earlier if asked to
8515 extend to a client. Follow-up to 21407. Fixes bug 21406; bugfix
8518 o Minor bugfixes (configuration):
8519 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
8520 bug 22252; bugfix on 0.2.9.3-alpha.
8522 o Minor bugfixes (connection lifespan):
8523 - Allow more control over how long TLS connections are kept open:
8524 unify CircuitIdleTimeout and PredictedPortsRelevanceTime into a
8525 single option called CircuitsAvailableTimeout. Also, allow the
8526 consensus to control the default values for both this preference
8527 and the lifespan of relay-to-relay connections. Fixes bug 17592;
8528 bugfix on 0.2.5.5-alpha.
8529 - Increase the initial circuit build timeout testing frequency, to
8530 help ensure that ReducedConnectionPadding clients finish learning
8531 a timeout before their orconn would expire. The initial testing
8532 rate was set back in the days of TAP and before the Tor Browser
8533 updater, when we had to be much more careful about new clients
8534 making lots of circuits. With this change, a circuit build timeout
8535 is learned in about 15-20 minutes, instead of 100-120 minutes.
8537 o Minor bugfixes (controller):
8538 - GETINFO onions/current and onions/detached no longer respond with
8539 551 on empty lists. Fixes bug 21329; bugfix on 0.2.7.1-alpha.
8540 - Trigger HS descriptor events on the control port when the client
8541 fails to pick a hidden service directory for a hidden service.
8542 This can happen if all the hidden service directories are in
8543 ExcludeNodes, or they have all been queried within the last 15
8544 minutes. Fixes bug 22042; bugfix on 0.2.5.2-alpha.
8546 o Minor bugfixes (directory authority):
8547 - When rejecting a router descriptor for running an obsolete version
8548 of Tor without ntor support, warn about the obsolete tor version,
8549 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
8550 - Prevent the shared randomness subsystem from asserting when
8551 initialized by a bridge authority with an incomplete configuration
8552 file. Fixes bug 21586; bugfix on 0.2.9.8.
8554 o Minor bugfixes (exit-side DNS):
8555 - Fix an untriggerable assertion that checked the output of a
8556 libevent DNS error, so that the assertion actually behaves as
8557 expected. Fixes bug 22244; bugfix on 0.2.0.20-rc. Found by Andrey
8558 Karpov using PVS-Studio.
8560 o Minor bugfixes (fallback directories):
8561 - Make the usage example in updateFallbackDirs.py actually work, and
8562 explain what it does. Fixes bug 22270; bugfix on 0.3.0.3-alpha.
8563 - Decrease the guard flag average required to be a fallback. This
8564 allows us to keep relays that have their guard flag removed when
8565 they restart. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
8566 - Decrease the minimum number of fallbacks to 100. Fixes bug 20913;
8567 bugfix on 0.2.8.1-alpha.
8568 - Make sure fallback directory mirrors have the same address, port,
8569 and relay identity key for at least 30 days before they are
8570 selected. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
8572 o Minor bugfixes (hidden services):
8573 - Stop printing a cryptic warning when a hidden service gets a
8574 request to connect to a virtual port that it hasn't configured.
8575 Fixes bug 16706; bugfix on 0.2.6.3-alpha.
8576 - Simplify hidden service descriptor creation by using an existing
8577 flag to check if an introduction point is established. Fixes bug
8578 21599; bugfix on 0.2.7.2-alpha.
8580 o Minor bugfixes (memory leak):
8581 - Fix a small memory leak at exit from the backtrace handler code.
8582 Fixes bug 21788; bugfix on 0.2.5.2-alpha. Patch from Daniel Pinto.
8584 o Minor bugfixes (protocol, logging):
8585 - Downgrade a log statement about unexpected relay cells from "bug"
8586 to "protocol warning", because there is at least one use case
8587 where it can be triggered by a buggy tor implementation. Fixes bug
8588 21293; bugfix on 0.1.1.14-alpha.
8590 o Minor bugfixes (testing):
8591 - Use unbuffered I/O for utility functions around the
8592 process_handle_t type. This fixes unit test failures reported on
8593 OpenBSD and FreeBSD. Fixes bug 21654; bugfix on 0.2.3.1-alpha.
8594 - Make display of captured unit test log messages consistent. Fixes
8595 bug 21510; bugfix on 0.2.9.3-alpha.
8596 - Make test-network.sh always call chutney's test-network.sh.
8597 Previously, this only worked on systems which had bash installed,
8598 due to some bash-specific code in the script. Fixes bug 19699;
8599 bugfix on 0.3.0.4-rc. Follow-up to ticket 21581.
8601 o Minor bugfixes (voting consistency):
8602 - Reject version numbers with non-numeric prefixes (such as +, -, or
8603 whitespace). Disallowing whitespace prevents differential version
8604 parsing between POSIX-based and Windows platforms. Fixes bug 21507
8605 and part of 21508; bugfix on 0.0.8pre1.
8607 o Minor bugfixes (windows, relay):
8608 - Resolve "Failure from drain_fd: No error" warnings on Windows
8609 relays. Fixes bug 21540; bugfix on 0.2.6.3-alpha.
8611 o Code simplification and refactoring:
8612 - Break up the 630-line function connection_dir_client_reached_eof()
8613 into a dozen smaller functions. This change should help
8614 maintainability and readability of the client directory code.
8615 - Isolate our use of the openssl headers so that they are only
8616 included from our crypto wrapper modules, and from tests that
8617 examine those modules' internals. Closes ticket 21841.
8618 - Simplify our API to launch directory requests, making it more
8619 extensible and less error-prone. Now it's easier to add extra
8620 headers to directory requests. Closes ticket 21646.
8621 - Our base64 decoding functions no longer overestimate the output
8622 space that they need when parsing unpadded inputs. Closes
8624 - Remove unused "ROUTER_ADDED_NOTIFY_GENERATOR" internal value.
8625 Resolves ticket 22213.
8626 - The logic that directory caches use to spool request to clients,
8627 serving them one part at a time so as not to allocate too much
8628 memory, has been refactored for consistency. Previously there was
8629 a separate spooling implementation per type of spoolable data. Now
8630 there is one common spooling implementation, with extensible data
8631 types. Closes ticket 21651.
8632 - Tor's compression module now supports multiple backends. Part of
8633 the implementation for proposal 278; closes ticket 21663.
8636 - Clarify the behavior of the KeepAliveIsolateSOCKSAuth sub-option.
8637 Closes ticket 21873.
8638 - Correct documentation about the default DataDirectory value.
8639 Closes ticket 21151.
8640 - Document the default behavior of NumEntryGuards and
8641 NumDirectoryGuards correctly. Fixes bug 21715; bugfix
8643 - Document key=value pluggable transport arguments for Bridge lines
8644 in torrc. Fixes bug 20341; bugfix on 0.2.5.1-alpha.
8645 - Note that bandwidth-limiting options don't affect TCP headers or
8646 DNS. Closes ticket 17170.
8648 o Removed features (configuration options, all in ticket 22060):
8649 - These configuration options are now marked Obsolete, and no longer
8650 have any effect: AllowInvalidNodes, AllowSingleHopCircuits,
8651 AllowSingleHopExits, ExcludeSingleHopRelays, FastFirstHopPK,
8652 TLSECGroup, WarnUnsafeSocks. They were first marked as deprecated
8653 in 0.2.9.2-alpha and have now been removed. The previous default
8654 behavior is now always chosen; the previous (less secure) non-
8655 default behavior is now unavailable.
8656 - CloseHSClientCircuitsImmediatelyOnTimeout and
8657 CloseHSServiceRendCircuitsImmediatelyOnTimeout were deprecated in
8658 0.2.9.2-alpha and now have been removed. HS circuits never close
8659 on circuit build timeout; they have a longer timeout period.
8660 - {Control,DNS,Dir,Socks,Trans,NATD,OR}ListenAddress were deprecated
8661 in 0.2.9.2-alpha and now have been removed. Use the ORPort option
8662 (and others) to configure listen-only and advertise-only addresses.
8664 o Removed features (tools):
8665 - We've removed the tor-checkkey tool from src/tools. Long ago, we
8666 used it to help people detect RSA keys that were generated by
8667 versions of Debian affected by CVE-2008-0166. But those keys have
8668 been out of circulation for ages, and this tool is no longer
8669 required. Closes ticket 21842.
8672 Changes in version 0.3.0.7 - 2017-05-15
8673 Tor 0.3.0.7 fixes a medium-severity security bug in earlier versions
8674 of Tor 0.3.0.x, where an attacker could cause a Tor relay process
8675 to exit. Relays running earlier versions of Tor 0.3.0.x should upgrade;
8676 clients are not affected.
8678 o Major bugfixes (hidden service directory, security):
8679 - Fix an assertion failure in the hidden service directory code, which
8680 could be used by an attacker to remotely cause a Tor relay process to
8681 exit. Relays running earlier versions of Tor 0.3.0.x should upgrade.
8682 should upgrade. This security issue is tracked as TROVE-2017-002.
8683 Fixes bug 22246; bugfix on 0.3.0.1-alpha.
8686 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
8689 o Minor features (future-proofing):
8690 - Tor no longer refuses to download microdescriptors or descriptors
8691 if they are listed as "published in the future". This change will
8692 eventually allow us to stop listing meaningful "published" dates
8693 in microdescriptor consensuses, and thereby allow us to reduce the
8694 resources required to download consensus diffs by over 50%.
8695 Implements part of ticket 21642; implements part of proposal 275.
8697 o Minor bugfixes (Linux seccomp2 sandbox):
8698 - The getpid() system call is now permitted under the Linux seccomp2
8699 sandbox, to avoid crashing with versions of OpenSSL (and other
8700 libraries) that attempt to learn the process's PID by using the
8701 syscall rather than the VDSO code. Fixes bug 21943; bugfix
8705 Changes in version 0.3.0.6 - 2017-04-26
8706 Tor 0.3.0.6 is the first stable release of the Tor 0.3.0 series.
8708 With the 0.3.0 series, clients and relays now use Ed25519 keys to
8709 authenticate their link connections to relays, rather than the old
8710 RSA1024 keys that they used before. (Circuit crypto has been
8711 Curve25519-authenticated since 0.2.4.8-alpha.) We have also replaced
8712 the guard selection and replacement algorithm to behave more robustly
8713 in the presence of unreliable networks, and to resist guard-
8716 This series also includes numerous other small features and bugfixes,
8717 along with more groundwork for the upcoming hidden-services revamp.
8719 Per our stable release policy, we plan to support the Tor 0.3.0
8720 release series for at least the next nine months, or for three months
8721 after the first stable release of the 0.3.1 series: whichever is
8722 longer. If you need a release with long-term support, we recommend
8723 that you stay with the 0.2.9 series.
8725 Below are the changes since 0.3.0.5-rc. For a list of all changes
8726 since 0.2.9, see the ReleaseNotes file.
8728 o Minor features (geoip):
8729 - Update geoip and geoip6 to the April 4 2017 Maxmind GeoLite2
8732 o Minor bugfixes (control port):
8733 - The GETINFO extra-info/digest/<digest> command was broken because
8734 of a wrong base16 decode return value check, introduced when
8735 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
8737 o Minor bugfixes (crash prevention):
8738 - Fix a (currently untriggerable, but potentially dangerous) crash
8739 bug when base32-encoding inputs whose sizes are not a multiple of
8740 5. Fixes bug 21894; bugfix on 0.2.9.1-alpha.
8743 Changes in version 0.3.0.5-rc - 2017-04-05
8744 Tor 0.3.0.5-rc fixes a few remaining bugs, large and small, in the
8745 0.3.0 release series.
8747 This is the second release candidate in the Tor 0.3.0 series, and has
8748 much fewer changes than the first. If we find no new bugs or
8749 regressions here, the first stable 0.3.0 release will be nearly
8752 o Major bugfixes (crash, directory connections):
8753 - Fix a rare crash when sending a begin cell on a circuit whose
8754 linked directory connection had already been closed. Fixes bug
8755 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
8757 o Major bugfixes (guard selection):
8758 - Fix a guard selection bug where Tor would refuse to bootstrap in
8759 some cases if the user swapped a bridge for another bridge in
8760 their configuration file. Fixes bug 21771; bugfix on 0.3.0.1-alpha.
8761 Reported by "torvlnt33r".
8763 o Minor features (geoip):
8764 - Update geoip and geoip6 to the March 7 2017 Maxmind GeoLite2
8767 o Minor bugfix (compilation):
8768 - Fix a warning when compiling hs_service.c. Previously, it had no
8769 exported symbols when compiled for libor.a, resulting in a
8770 compilation warning from clang. Fixes bug 21825; bugfix
8773 o Minor bugfixes (hidden services):
8774 - Make hidden services check for failed intro point connections,
8775 even when they have exceeded their intro point creation limit.
8776 Fixes bug 21596; bugfix on 0.2.7.2-alpha. Reported by Alec Muffett.
8777 - Make hidden services with 8 to 10 introduction points check for
8778 failed circuits immediately after startup. Previously, they would
8779 wait for 5 minutes before performing their first checks. Fixes bug
8780 21594; bugfix on 0.2.3.9-alpha. Reported by Alec Muffett.
8782 o Minor bugfixes (memory leaks):
8783 - Fix a memory leak when using GETCONF on a port option. Fixes bug
8784 21682; bugfix on 0.3.0.3-alpha.
8786 o Minor bugfixes (relay):
8787 - Avoid a double-marked-circuit warning that could happen when we
8788 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
8791 o Minor bugfixes (tests):
8792 - Run the entry_guard_parse_from_state_full() test with the time set
8793 to a specific date. (The guard state that this test was parsing
8794 contained guards that had expired since the test was first
8795 written.) Fixes bug 21799; bugfix on 0.3.0.1-alpha.
8798 - Update the description of the directory server options in the
8799 manual page, to clarify that a relay no longer needs to set
8800 DirPort in order to be a directory cache. Closes ticket 21720.
8804 Changes in version 0.2.8.13 - 2017-03-03
8805 Tor 0.2.8.13 backports a security fix from later Tor
8806 releases. Anybody running Tor 0.2.8.12 or earlier should upgrade to this
8807 this release, if for some reason they cannot upgrade to a later
8808 release series, and if they build Tor with the --enable-expensive-hardening
8811 Note that support for Tor 0.2.8.x is ending next year: we will not issue
8812 any fixes for the Tor 0.2.8.x series after 1 Jan 2018. If you need
8813 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
8815 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
8816 - Fix an integer underflow bug when comparing malformed Tor
8817 versions. This bug could crash Tor when built with
8818 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
8819 0.2.9.8, which were built with -ftrapv by default. In other cases
8820 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
8821 on 0.0.8pre1. Found by OSS-Fuzz.
8823 o Minor features (geoip):
8824 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
8828 Changes in version 0.2.7.7 - 2017-03-03
8829 Tor 0.2.7.7 backports a number of security fixes from later Tor
8830 releases. Anybody running Tor 0.2.7.6 or earlier should upgrade to
8831 this release, if for some reason they cannot upgrade to a later
8834 Note that support for Tor 0.2.7.x is ending this year: we will not issue
8835 any fixes for the Tor 0.2.7.x series after 1 August 2017. If you need
8836 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
8838 o Directory authority changes (backport from 0.2.8.5-rc):
8839 - Urras is no longer a directory authority. Closes ticket 19271.
8841 o Directory authority changes (backport from 0.2.9.2-alpha):
8842 - The "Tonga" bridge authority has been retired; the new bridge
8843 authority is "Bifroest". Closes tickets 19728 and 19690.
8845 o Directory authority key updates (backport from 0.2.8.1-alpha):
8846 - Update the V3 identity key for the dannenberg directory authority:
8847 it was changed on 18 November 2015. Closes task 17906. Patch
8850 o Major bugfixes (parsing, security, backport from 0.2.9.8):
8851 - Fix a bug in parsing that could cause clients to read a single
8852 byte past the end of an allocated region. This bug could be used
8853 to cause hardened clients (built with --enable-expensive-hardening)
8854 to crash if they tried to visit a hostile hidden service. Non-
8855 hardened clients are only affected depending on the details of
8856 their platform's memory allocator. Fixes bug 21018; bugfix on
8857 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
8858 2016-12-002 and as CVE-2016-1254.
8860 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
8861 - Stop a crash that could occur when a client running with DNSPort
8862 received a query with multiple address types, and the first
8863 address type was not supported. Found and fixed by Scott Dial.
8864 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
8865 - Prevent a class of security bugs caused by treating the contents
8866 of a buffer chunk as if they were a NUL-terminated string. At
8867 least one such bug seems to be present in all currently used
8868 versions of Tor, and would allow an attacker to remotely crash
8869 most Tor instances, especially those compiled with extra compiler
8870 hardening. With this defense in place, such bugs can't crash Tor,
8871 though we should still fix them as they occur. Closes ticket
8872 20384 (TROVE-2016-10-001).
8874 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
8875 - Avoid a difficult-to-trigger heap corruption attack when extending
8876 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
8877 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
8878 Reported by Guido Vranken.
8880 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
8881 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
8882 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
8884 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
8885 - If OpenSSL fails to generate an RSA key, do not retain a dangling
8886 pointer to the previous (uninitialized) key value. The impact here
8887 should be limited to a difficult-to-trigger crash, if OpenSSL is
8888 running an engine that makes key generation failures possible, or
8889 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
8890 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
8893 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
8894 - Fix an integer underflow bug when comparing malformed Tor
8895 versions. This bug could crash Tor when built with
8896 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
8897 0.2.9.8, which were built with -ftrapv by default. In other cases
8898 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
8899 on 0.0.8pre1. Found by OSS-Fuzz.
8901 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
8902 - Make memwipe() do nothing when passed a NULL pointer or buffer of
8903 zero size. Check size argument to memwipe() for underflow. Fixes
8904 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
8907 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
8908 - Make Tor survive errors involving connections without a
8909 corresponding event object. Previously we'd fail with an
8910 assertion; now we produce a log message. Related to bug 16248.
8912 o Minor features (geoip):
8913 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
8917 Changes in version 0.2.6.11 - 2017-03-03
8918 Tor 0.2.6.11 backports a number of security fixes from later Tor
8919 releases. Anybody running Tor 0.2.6.10 or earlier should upgrade to
8920 this release, if for some reason they cannot upgrade to a later
8923 Note that support for Tor 0.2.6.x is ending this year: we will not issue
8924 any fixes for the Tor 0.2.6.x series after 1 August 2017. If you need
8925 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
8927 o Directory authority changes (backport from 0.2.8.5-rc):
8928 - Urras is no longer a directory authority. Closes ticket 19271.
8930 o Directory authority changes (backport from 0.2.9.2-alpha):
8931 - The "Tonga" bridge authority has been retired; the new bridge
8932 authority is "Bifroest". Closes tickets 19728 and 19690.
8934 o Directory authority key updates (backport from 0.2.8.1-alpha):
8935 - Update the V3 identity key for the dannenberg directory authority:
8936 it was changed on 18 November 2015. Closes task 17906. Patch
8939 o Major features (security fixes, backport from 0.2.9.4-alpha):
8940 - Prevent a class of security bugs caused by treating the contents
8941 of a buffer chunk as if they were a NUL-terminated string. At
8942 least one such bug seems to be present in all currently used
8943 versions of Tor, and would allow an attacker to remotely crash
8944 most Tor instances, especially those compiled with extra compiler
8945 hardening. With this defense in place, such bugs can't crash Tor,
8946 though we should still fix them as they occur. Closes ticket
8947 20384 (TROVE-2016-10-001).
8949 o Major bugfixes (parsing, security, backport from 0.2.9.8):
8950 - Fix a bug in parsing that could cause clients to read a single
8951 byte past the end of an allocated region. This bug could be used
8952 to cause hardened clients (built with --enable-expensive-hardening)
8953 to crash if they tried to visit a hostile hidden service. Non-
8954 hardened clients are only affected depending on the details of
8955 their platform's memory allocator. Fixes bug 21018; bugfix on
8956 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
8957 2016-12-002 and as CVE-2016-1254.
8959 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
8960 - Stop a crash that could occur when a client running with DNSPort
8961 received a query with multiple address types, and the first
8962 address type was not supported. Found and fixed by Scott Dial.
8963 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
8965 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
8966 - Fix an error that could cause us to read 4 bytes before the
8967 beginning of an openssl string. This bug could be used to cause
8968 Tor to crash on systems with unusual malloc implementations, or
8969 systems with unusual hardening installed. Fixes bug 17404; bugfix
8972 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
8973 - Avoid a difficult-to-trigger heap corruption attack when extending
8974 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
8975 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
8976 Reported by Guido Vranken.
8978 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
8979 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
8980 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
8982 o Major bugfixes (guard selection, backport from 0.2.7.6):
8983 - Actually look at the Guard flag when selecting a new directory
8984 guard. When we implemented the directory guard design, we
8985 accidentally started treating all relays as if they have the Guard
8986 flag during guard selection, leading to weaker anonymity and worse
8987 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
8990 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
8991 - If OpenSSL fails to generate an RSA key, do not retain a dangling
8992 pointer to the previous (uninitialized) key value. The impact here
8993 should be limited to a difficult-to-trigger crash, if OpenSSL is
8994 running an engine that makes key generation failures possible, or
8995 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
8996 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
8999 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
9000 - Fix an integer underflow bug when comparing malformed Tor
9001 versions. This bug could crash Tor when built with
9002 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
9003 0.2.9.8, which were built with -ftrapv by default. In other cases
9004 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
9005 on 0.0.8pre1. Found by OSS-Fuzz.
9007 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
9008 - Make memwipe() do nothing when passed a NULL pointer or buffer of
9009 zero size. Check size argument to memwipe() for underflow. Fixes
9010 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
9013 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
9014 - Make Tor survive errors involving connections without a
9015 corresponding event object. Previously we'd fail with an
9016 assertion; now we produce a log message. Related to bug 16248.
9018 o Minor features (geoip):
9019 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
9022 o Minor bugfixes (compilation, backport from 0.2.7.6):
9023 - Fix a compilation warning with Clang 3.6: Do not check the
9024 presence of an address which can never be NULL. Fixes bug 17781.
9027 Changes in version 0.2.5.13 - 2017-03-03
9028 Tor 0.2.5.13 backports a number of security fixes from later Tor
9029 releases. Anybody running Tor 0.2.5.13 or earlier should upgrade to
9030 this release, if for some reason they cannot upgrade to a later
9033 Note that support for Tor 0.2.5.x is ending next year: we will not issue
9034 any fixes for the Tor 0.2.5.x series after 1 May 2018. If you need
9035 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
9037 o Directory authority changes (backport from 0.2.8.5-rc):
9038 - Urras is no longer a directory authority. Closes ticket 19271.
9040 o Directory authority changes (backport from 0.2.9.2-alpha):
9041 - The "Tonga" bridge authority has been retired; the new bridge
9042 authority is "Bifroest". Closes tickets 19728 and 19690.
9044 o Directory authority key updates (backport from 0.2.8.1-alpha):
9045 - Update the V3 identity key for the dannenberg directory authority:
9046 it was changed on 18 November 2015. Closes task 17906. Patch
9049 o Major features (security fixes, backport from 0.2.9.4-alpha):
9050 - Prevent a class of security bugs caused by treating the contents
9051 of a buffer chunk as if they were a NUL-terminated string. At
9052 least one such bug seems to be present in all currently used
9053 versions of Tor, and would allow an attacker to remotely crash
9054 most Tor instances, especially those compiled with extra compiler
9055 hardening. With this defense in place, such bugs can't crash Tor,
9056 though we should still fix them as they occur. Closes ticket
9057 20384 (TROVE-2016-10-001).
9059 o Major bugfixes (parsing, security, backport from 0.2.9.8):
9060 - Fix a bug in parsing that could cause clients to read a single
9061 byte past the end of an allocated region. This bug could be used
9062 to cause hardened clients (built with --enable-expensive-hardening)
9063 to crash if they tried to visit a hostile hidden service. Non-
9064 hardened clients are only affected depending on the details of
9065 their platform's memory allocator. Fixes bug 21018; bugfix on
9066 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
9067 2016-12-002 and as CVE-2016-1254.
9069 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
9070 - Stop a crash that could occur when a client running with DNSPort
9071 received a query with multiple address types, and the first
9072 address type was not supported. Found and fixed by Scott Dial.
9073 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
9075 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
9076 - Fix an error that could cause us to read 4 bytes before the
9077 beginning of an openssl string. This bug could be used to cause
9078 Tor to crash on systems with unusual malloc implementations, or
9079 systems with unusual hardening installed. Fixes bug 17404; bugfix
9082 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
9083 - Avoid a difficult-to-trigger heap corruption attack when extending
9084 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
9085 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
9086 Reported by Guido Vranken.
9088 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
9089 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
9090 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
9092 o Major bugfixes (guard selection, backport from 0.2.7.6):
9093 - Actually look at the Guard flag when selecting a new directory
9094 guard. When we implemented the directory guard design, we
9095 accidentally started treating all relays as if they have the Guard
9096 flag during guard selection, leading to weaker anonymity and worse
9097 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
9100 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
9101 - If OpenSSL fails to generate an RSA key, do not retain a dangling
9102 pointer to the previous (uninitialized) key value. The impact here
9103 should be limited to a difficult-to-trigger crash, if OpenSSL is
9104 running an engine that makes key generation failures possible, or
9105 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
9106 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
9109 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
9110 - Fix an integer underflow bug when comparing malformed Tor
9111 versions. This bug could crash Tor when built with
9112 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
9113 0.2.9.8, which were built with -ftrapv by default. In other cases
9114 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
9115 on 0.0.8pre1. Found by OSS-Fuzz.
9117 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
9118 - Make memwipe() do nothing when passed a NULL pointer or buffer of
9119 zero size. Check size argument to memwipe() for underflow. Fixes
9120 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
9123 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
9124 - Make Tor survive errors involving connections without a
9125 corresponding event object. Previously we'd fail with an
9126 assertion; now we produce a log message. Related to bug 16248.
9128 o Minor features (geoip):
9129 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
9132 o Minor bugfixes (compilation, backport from 0.2.7.6):
9133 - Fix a compilation warning with Clang 3.6: Do not check the
9134 presence of an address which can never be NULL. Fixes bug 17781.
9136 o Minor bugfixes (crypto error-handling, backport from 0.2.7.2-alpha):
9137 - Check for failures from crypto_early_init, and refuse to continue.
9138 A previous typo meant that we could keep going with an
9139 uninitialized crypto library, and would have OpenSSL initialize
9140 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
9141 when implementing ticket 4900. Patch by "teor".
9143 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
9144 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
9145 a client authorized hidden service. Fixes bug 15823; bugfix
9149 Changes in version 0.2.4.28 - 2017-03-03
9150 Tor 0.2.4.28 backports a number of security fixes from later Tor
9151 releases. Anybody running Tor 0.2.4.27 or earlier should upgrade to
9152 this release, if for some reason they cannot upgrade to a later
9155 Note that support for Tor 0.2.4.x is ending soon: we will not issue
9156 any fixes for the Tor 0.2.4.x series after 1 August 2017. If you need
9157 a Tor release series with long-term support, we recommend Tor 0.2.9.x.
9159 o Directory authority changes (backport from 0.2.8.5-rc):
9160 - Urras is no longer a directory authority. Closes ticket 19271.
9162 o Directory authority changes (backport from 0.2.9.2-alpha):
9163 - The "Tonga" bridge authority has been retired; the new bridge
9164 authority is "Bifroest". Closes tickets 19728 and 19690.
9166 o Directory authority key updates (backport from 0.2.8.1-alpha):
9167 - Update the V3 identity key for the dannenberg directory authority:
9168 it was changed on 18 November 2015. Closes task 17906. Patch
9171 o Major features (security fixes, backport from 0.2.9.4-alpha):
9172 - Prevent a class of security bugs caused by treating the contents
9173 of a buffer chunk as if they were a NUL-terminated string. At
9174 least one such bug seems to be present in all currently used
9175 versions of Tor, and would allow an attacker to remotely crash
9176 most Tor instances, especially those compiled with extra compiler
9177 hardening. With this defense in place, such bugs can't crash Tor,
9178 though we should still fix them as they occur. Closes ticket
9179 20384 (TROVE-2016-10-001).
9181 o Major bugfixes (parsing, security, backport from 0.2.9.8):
9182 - Fix a bug in parsing that could cause clients to read a single
9183 byte past the end of an allocated region. This bug could be used
9184 to cause hardened clients (built with --enable-expensive-hardening)
9185 to crash if they tried to visit a hostile hidden service. Non-
9186 hardened clients are only affected depending on the details of
9187 their platform's memory allocator. Fixes bug 21018; bugfix on
9188 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
9189 2016-12-002 and as CVE-2016-1254.
9191 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
9192 - Fix an error that could cause us to read 4 bytes before the
9193 beginning of an openssl string. This bug could be used to cause
9194 Tor to crash on systems with unusual malloc implementations, or
9195 systems with unusual hardening installed. Fixes bug 17404; bugfix
9198 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
9199 - Avoid a difficult-to-trigger heap corruption attack when extending
9200 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
9201 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
9202 Reported by Guido Vranken.
9204 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
9205 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
9206 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
9208 o Major bugfixes (guard selection, backport from 0.2.7.6):
9209 - Actually look at the Guard flag when selecting a new directory
9210 guard. When we implemented the directory guard design, we
9211 accidentally started treating all relays as if they have the Guard
9212 flag during guard selection, leading to weaker anonymity and worse
9213 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
9216 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
9217 - If OpenSSL fails to generate an RSA key, do not retain a dangling
9218 pointer to the previous (uninitialized) key value. The impact here
9219 should be limited to a difficult-to-trigger crash, if OpenSSL is
9220 running an engine that makes key generation failures possible, or
9221 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
9222 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
9225 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
9226 - Fix an integer underflow bug when comparing malformed Tor
9227 versions. This bug could crash Tor when built with
9228 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
9229 0.2.9.8, which were built with -ftrapv by default. In other cases
9230 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
9231 on 0.0.8pre1. Found by OSS-Fuzz.
9233 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
9234 - Make memwipe() do nothing when passed a NULL pointer or buffer of
9235 zero size. Check size argument to memwipe() for underflow. Fixes
9236 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
9239 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
9240 - Make Tor survive errors involving connections without a
9241 corresponding event object. Previously we'd fail with an
9242 assertion; now we produce a log message. Related to bug 16248.
9244 o Minor features (DoS-resistance, backport from 0.2.7.1-alpha):
9245 - Make it harder for attackers to overload hidden services with
9246 introductions, by blocking multiple introduction requests on the
9247 same circuit. Resolves ticket 15515.
9249 o Minor features (geoip):
9250 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
9253 o Minor bugfixes (compilation, backport from 0.2.7.6):
9254 - Fix a compilation warning with Clang 3.6: Do not check the
9255 presence of an address which can never be NULL. Fixes bug 17781.
9257 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
9258 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
9259 a client authorized hidden service. Fixes bug 15823; bugfix
9263 Changes in version 0.3.0.4-rc - 2017-03-01
9264 Tor 0.3.0.4-rc fixes some remaining bugs, large and small, in the
9265 0.3.0 release series, and introduces a few reliability features to
9266 keep them from coming back.
9268 This is the first release candidate in the Tor 0.3.0 series. If we
9269 find no new bugs or regressions here, the first stable 0.3.0 release
9270 will be nearly identical to it.
9272 o Major bugfixes (bridges):
9273 - When the same bridge is configured multiple times with the same
9274 identity, but at different address:port combinations, treat those
9275 bridge instances as separate guards. This fix restores the ability
9276 of clients to configure the same bridge with multiple pluggable
9277 transports. Fixes bug 21027; bugfix on 0.3.0.1-alpha.
9279 o Major bugfixes (hidden service directory v3):
9280 - Stop crashing on a failed v3 hidden service descriptor lookup
9281 failure. Fixes bug 21471; bugfixes on 0.3.0.1-alpha.
9283 o Major bugfixes (parsing):
9284 - When parsing a malformed content-length field from an HTTP
9285 message, do not read off the end of the buffer. This bug was a
9286 potential remote denial-of-service attack against Tor clients and
9287 relays. A workaround was released in October 2016, to prevent this
9288 bug from crashing Tor. This is a fix for the underlying issue,
9289 which should no longer matter (if you applied the earlier patch).
9290 Fixes bug 20894; bugfix on 0.2.0.16-alpha. Bug found by fuzzing
9291 using AFL (http://lcamtuf.coredump.cx/afl/).
9292 - Fix an integer underflow bug when comparing malformed Tor
9293 versions. This bug could crash Tor when built with
9294 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
9295 0.2.9.8, which were built with -ftrapv by default. In other cases
9296 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
9297 on 0.0.8pre1. Found by OSS-Fuzz.
9299 o Minor feature (protocol versioning):
9300 - Add new protocol version for proposal 224. HSIntro now advertises
9301 version "3-4" and HSDir version "1-2". Fixes ticket 20656.
9303 o Minor features (directory authorities):
9304 - Directory authorities now reject descriptors that claim to be
9305 malformed versions of Tor. Helps prevent exploitation of
9307 - Reject version numbers with components that exceed INT32_MAX.
9308 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
9309 Fixes bug 21450; bugfix on 0.0.8pre1.
9310 - Directory authorities now reject relays running versions
9311 0.2.9.1-alpha through 0.2.9.4-alpha, because those relays
9312 suffer from bug 20499 and don't keep their consensus cache
9313 up-to-date. Resolves ticket 20509.
9315 o Minor features (geoip):
9316 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
9319 o Minor features (reliability, crash):
9320 - Try better to detect problems in buffers where they might grow (or
9321 think they have grown) over 2 GB in size. Diagnostic for
9324 o Minor features (testing):
9325 - During 'make test-network-all', if tor logs any warnings, ask
9326 chutney to output them. Requires a recent version of chutney with
9327 the 21572 patch. Implements 21570.
9329 o Minor bugfixes (certificate expiration time):
9330 - Avoid using link certificates that don't become valid till some
9331 time in the future. Fixes bug 21420; bugfix on 0.2.4.11-alpha
9333 o Minor bugfixes (code correctness):
9334 - Repair a couple of (unreachable or harmless) cases of the risky
9335 comparison-by-subtraction pattern that caused bug 21278.
9336 - Remove a redundant check for the UseEntryGuards option from the
9337 options_transition_affects_guards() function. Fixes bug 21492;
9338 bugfix on 0.3.0.1-alpha.
9340 o Minor bugfixes (directory mirrors):
9341 - Allow relays to use directory mirrors without a DirPort: these
9342 relays need to be contacted over their ORPorts using a begindir
9343 connection. Fixes one case of bug 20711; bugfix on 0.2.8.2-alpha.
9344 - Clarify the message logged when a remote relay is unexpectedly
9345 missing an ORPort or DirPort: users were confusing this with a
9346 local port. Fixes another case of bug 20711; bugfix
9349 o Minor bugfixes (guards):
9350 - Don't warn about a missing guard state on timeout-measurement
9351 circuits: they aren't supposed to be using guards. Fixes an
9352 instance of bug 21007; bugfix on 0.3.0.1-alpha.
9353 - Silence a BUG() warning when attempting to use a guard whose
9354 descriptor we don't know, and make this scenario less likely to
9355 happen. Fixes bug 21415; bugfix on 0.3.0.1-alpha.
9357 o Minor bugfixes (hidden service):
9358 - Pass correct buffer length when encoding legacy ESTABLISH_INTRO
9359 cells. Previously, we were using sizeof() on a pointer, instead of
9360 the real destination buffer. Fortunately, that value was only used
9361 to double-check that there was enough room--which was already
9362 enforced elsewhere. Fixes bug 21553; bugfix on 0.3.0.1-alpha.
9364 o Minor bugfixes (testing):
9365 - Fix Raspbian build issues related to missing socket errno in
9366 test_util.c. Fixes bug 21116; bugfix on 0.2.8.2. Patch
9368 - Rename "make fuzz" to "make test-fuzz-corpora", since it doesn't
9369 actually fuzz anything. Fixes bug 21447; bugfix on 0.3.0.3-alpha.
9370 - Use bash in src/test/test-network.sh. This ensures we reliably
9371 call chutney's newer tools/test-network.sh when available. Fixes
9372 bug 21562; bugfix on 0.2.9.1-alpha.
9375 - Small fixes to the fuzzing documentation. Closes ticket 21472.
9378 Changes in version 0.2.9.10 - 2017-03-01
9379 Tor 0.2.9.10 backports a security fix from later Tor release. It also
9380 includes fixes for some major issues affecting directory authorities,
9381 LibreSSL compatibility, and IPv6 correctness.
9383 The Tor 0.2.9.x release series is now marked as a long-term-support
9384 series. We intend to backport security fixes to 0.2.9.x until at
9385 least January of 2020.
9387 o Major bugfixes (directory authority, 0.3.0.3-alpha):
9388 - During voting, when marking a relay as a probable sybil, do not
9389 clear its BadExit flag: sybils can still be bad in other ways
9390 too. (We still clear the other flags.) Fixes bug 21108; bugfix
9393 o Major bugfixes (IPv6 Exits, backport from 0.3.0.3-alpha):
9394 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
9395 any IPv6 addresses. Instead, only reject a port over IPv6 if the
9396 exit policy rejects that port on more than an IPv6 /16 of
9397 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
9398 which rejected a relay's own IPv6 address by default. Fixes bug
9399 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
9401 o Major bugfixes (parsing, also in 0.3.0.4-rc):
9402 - Fix an integer underflow bug when comparing malformed Tor
9403 versions. This bug could crash Tor when built with
9404 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
9405 0.2.9.8, which were built with -ftrapv by default. In other cases
9406 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
9407 on 0.0.8pre1. Found by OSS-Fuzz.
9409 o Minor features (directory authorities, also in 0.3.0.4-rc):
9410 - Directory authorities now reject descriptors that claim to be
9411 malformed versions of Tor. Helps prevent exploitation of
9413 - Reject version numbers with components that exceed INT32_MAX.
9414 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
9415 Fixes bug 21450; bugfix on 0.0.8pre1.
9417 o Minor features (geoip):
9418 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
9421 o Minor features (portability, compilation, backport from 0.3.0.3-alpha):
9422 - Autoconf now checks to determine if OpenSSL structures are opaque,
9423 instead of explicitly checking for OpenSSL version numbers. Part
9425 - Support building with recent LibreSSL code that uses opaque
9426 structures. Closes ticket 21359.
9428 o Minor bugfixes (code correctness, also in 0.3.0.4-rc):
9429 - Repair a couple of (unreachable or harmless) cases of the risky
9430 comparison-by-subtraction pattern that caused bug 21278.
9432 o Minor bugfixes (tor-resolve, backport from 0.3.0.3-alpha):
9433 - The tor-resolve command line tool now rejects hostnames over 255
9434 characters in length. Previously, it would silently truncate them,
9435 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
9436 Patch by "junglefowl".
9439 Changes in version 0.3.0.3-alpha - 2017-02-03
9440 Tor 0.3.0.3-alpha fixes a few significant bugs introduced over the
9441 0.3.0.x development series, including some that could cause
9442 authorities to behave badly. There is also a fix for a longstanding
9443 bug that could prevent IPv6 exits from working. Tor 0.3.0.3-alpha also
9444 includes some smaller features and bugfixes.
9446 The Tor 0.3.0.x release series is now in patch-freeze: no additional
9447 features will be considered for inclusion in 0.3.0.x. We suspect that
9448 some bugs will probably remain, however, and we encourage people to
9451 o Major bugfixes (directory authority):
9452 - During voting, when marking a relay as a probable sybil, do not
9453 clear its BadExit flag: sybils can still be bad in other ways
9454 too. (We still clear the other flags.) Fixes bug 21108; bugfix
9456 - When deciding whether we have just found a router to be reachable,
9457 do not penalize it for not having performed an Ed25519 link
9458 handshake if it does not claim to support an Ed25519 handshake.
9459 Previously, we would treat such relays as non-running. Fixes bug
9460 21107; bugfix on 0.3.0.1-alpha.
9462 o Major bugfixes (entry guards):
9463 - Stop trying to build circuits through entry guards for which we
9464 have no descriptor. Also, stop crashing in the case that we *do*
9465 accidentally try to build a circuit in such a state. Fixes bug
9466 21242; bugfix on 0.3.0.1-alpha.
9468 o Major bugfixes (IPv6 Exits):
9469 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
9470 any IPv6 addresses. Instead, only reject a port over IPv6 if the
9471 exit policy rejects that port on more than an IPv6 /16 of
9472 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
9473 which rejected a relay's own IPv6 address by default. Fixes bug
9474 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
9476 o Minor feature (client):
9477 - Enable IPv6 traffic on the SocksPort by default. To disable this,
9478 a user will have to specify "NoIPv6Traffic". Closes ticket 21269.
9480 o Minor feature (fallback scripts):
9481 - Add a check_existing mode to updateFallbackDirs.py, which checks
9482 if fallbacks in the hard-coded list are working. Closes ticket
9483 20174. Patch by haxxpop.
9485 o Minor features (ciphersuite selection):
9486 - Clients now advertise a list of ciphersuites closer to the ones
9487 preferred by Firefox. Closes part of ticket 15426.
9488 - Allow relays to accept a wider range of ciphersuites, including
9489 chacha20-poly1305 and AES-CCM. Closes the other part of 15426.
9491 o Minor features (controller, configuration):
9492 - Each of the *Port options, such as SocksPort, ORPort, ControlPort,
9493 and so on, now comes with a __*Port variant that will not be saved
9494 to the torrc file by the controller's SAVECONF command. This
9495 change allows TorBrowser to set up a single-use domain socket for
9496 each time it launches Tor. Closes ticket 20956.
9497 - The GETCONF command can now query options that may only be
9498 meaningful in context-sensitive lists. This allows the controller
9499 to query the mixed SocksPort/__SocksPort style options introduced
9500 in feature 20956. Implements ticket 21300.
9502 o Minor features (portability, compilation):
9503 - Autoconf now checks to determine if OpenSSL structures are opaque,
9504 instead of explicitly checking for OpenSSL version numbers. Part
9506 - Support building with recent LibreSSL code that uses opaque
9507 structures. Closes ticket 21359.
9509 o Minor features (relay):
9510 - We now allow separation of exit and relay traffic to different
9511 source IP addresses, using the OutboundBindAddressExit and
9512 OutboundBindAddressOR options respectively. Closes ticket 17975.
9513 Written by Michael Sonntag.
9515 o Minor bugfix (logging):
9516 - Don't recommend the use of Tor2web in non-anonymous mode.
9517 Recommending Tor2web is a bad idea because the client loses all
9518 anonymity. Tor2web should only be used in specific cases by users
9519 who *know* and understand the issues. Fixes bug 21294; bugfix
9522 o Minor bugfixes (client):
9523 - Always recover from failures in extend_info_from_node(), in an
9524 attempt to prevent any recurrence of bug 21242. Fixes bug 21372;
9525 bugfix on 0.2.3.1-alpha.
9527 o Minor bugfixes (client, entry guards):
9528 - Fix a bug warning (with backtrace) when we fail a channel that
9529 circuits to fallback directories on it. Fixes bug 21128; bugfix
9531 - Fix a spurious bug warning (with backtrace) when removing an
9532 expired entry guard. Fixes bug 21129; bugfix on 0.3.0.1-alpha.
9533 - Fix a bug of the new guard algorithm where tor could stall for up
9534 to 10 minutes before retrying a guard after a long period of no
9535 network. Fixes bug 21052; bugfix on 0.3.0.1-alpha.
9536 - Do not try to build circuits until we have descriptors for our
9537 primary entry guards. Related to fix for bug 21242.
9539 o Minor bugfixes (configure, autoconf):
9540 - Rename the configure option --enable-expensive-hardening to
9541 --enable-fragile-hardening. Expensive hardening makes the tor
9542 daemon abort when some kinds of issues are detected. Thus, it
9543 makes tor more at risk of remote crashes but safer against RCE or
9544 heartbleed bug category. We now try to explain this issue in a
9545 message from the configure script. Fixes bug 21290; bugfix
9548 o Minor bugfixes (controller):
9549 - Restore the (deprecated) DROPGUARDS controller command. Fixes bug
9550 20824; bugfix on 0.3.0.1-alpha.
9552 o Minor bugfixes (hidden service):
9553 - Clean up the code for expiring intro points with no associated
9554 circuits. It was causing, rarely, a service with some expiring
9555 introduction points to not open enough additional introduction
9556 points. Fixes part of bug 21302; bugfix on 0.2.7.2-alpha.
9557 - Stop setting the torrc option HiddenServiceStatistics to "0" just
9558 because we're not a bridge or relay. Instead, we preserve whatever
9559 value the user set (or didn't set). Fixes bug 21150; bugfix
9561 - Resolve two possible underflows which could lead to creating and
9562 closing a lot of introduction point circuits in a non-stop loop.
9563 Fixes bug 21302; bugfix on 0.2.7.2-alpha.
9565 o Minor bugfixes (portability):
9566 - Use "OpenBSD" compiler macro instead of "OPENBSD" or "__OpenBSD__".
9567 It is supported by OpenBSD itself, and also by most OpenBSD
9568 variants (such as Bitrig). Fixes bug 20980; bugfix
9570 - When mapping a file of length greater than SIZE_MAX, do not
9571 silently truncate its contents. This issue could occur on 32 bit
9572 systems with large file support and files which are larger than 4
9573 GB. Fixes bug 21134; bugfix on 0.3.0.1-alpha.
9575 o Minor bugfixes (tor-resolve):
9576 - The tor-resolve command line tool now rejects hostnames over 255
9577 characters in length. Previously, it would silently truncate them,
9578 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
9579 Patch by "junglefowl".
9581 o Minor bugfixes (Windows services):
9582 - Be sure to initialize the monotonic time subsystem before using
9583 it, even when running as an NT service. Fixes bug 21356; bugfix
9587 Changes in version 0.3.0.2-alpha - 2017-01-23
9588 Tor 0.3.0.2-alpha fixes a denial-of-service bug where an attacker could
9589 cause relays and clients to crash, even if they were not built with
9590 the --enable-expensive-hardening option. This bug affects all 0.2.9.x
9591 versions, and also affects 0.3.0.1-alpha: all relays running an affected
9592 version should upgrade.
9594 Tor 0.3.0.2-alpha also improves how exit relays and clients handle DNS
9595 time-to-live values, makes directory authorities enforce the 1-to-1
9596 mapping of relay RSA identity keys to ED25519 identity keys, fixes a
9597 client-side onion service reachability bug, does better at selecting
9598 the set of fallback directories, and more.
9600 o Major bugfixes (security, also in 0.2.9.9):
9601 - Downgrade the "-ftrapv" option from "always on" to "only on when
9602 --enable-expensive-hardening is provided." This hardening option, like
9603 others, can turn survivable bugs into crashes--and having it on by
9604 default made a (relatively harmless) integer overflow bug into a
9605 denial-of-service bug. Fixes bug 21278 (TROVE-2017-001); bugfix on
9608 o Major features (security):
9609 - Change the algorithm used to decide DNS TTLs on client and server
9610 side, to better resist DNS-based correlation attacks like the
9611 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
9612 Feamster. Now relays only return one of two possible DNS TTL
9613 values, and clients are willing to believe DNS TTL values up to 3
9614 hours long. Closes ticket 19769.
9616 o Major features (directory authority, security):
9617 - The default for AuthDirPinKeys is now 1: directory authorities
9618 will reject relays where the RSA identity key matches a previously
9619 seen value, but the Ed25519 key has changed. Closes ticket 18319.
9621 o Major bugfixes (client, guard, crash):
9622 - In circuit_get_global_origin_list(), return the actual list of
9623 origin circuits. The previous version of this code returned the
9624 list of all the circuits, and could have caused strange bugs,
9625 including possible crashes. Fixes bug 21118; bugfix
9628 o Major bugfixes (client, onion service, also in 0.2.9.9):
9629 - Fix a client-side onion service reachability bug, where multiple
9630 socks requests to an onion service (or a single slow request)
9631 could cause us to mistakenly mark some of the service's
9632 introduction points as failed, and we cache that failure so
9633 eventually we run out and can't reach the service. Also resolves a
9634 mysterious "Remote server sent bogus reason code 65021" log
9635 warning. The bug was introduced in ticket 17218, where we tried to
9636 remember the circuit end reason as a uint16_t, which mangled
9637 negative values. Partially fixes bug 21056 and fixes bug 20307;
9638 bugfix on 0.2.8.1-alpha.
9640 o Major bugfixes (DNS):
9641 - Fix a bug that prevented exit nodes from caching DNS records for
9642 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
9644 o Minor features (controller):
9645 - Add "GETINFO sr/current" and "GETINFO sr/previous" keys, to expose
9646 shared-random values to the controller. Closes ticket 19925.
9648 o Minor features (entry guards):
9649 - Add UseEntryGuards to TEST_OPTIONS_DEFAULT_VALUES in order to not
9650 break regression tests.
9651 - Require UseEntryGuards when UseBridges is set, in order to make
9652 sure bridges aren't bypassed. Resolves ticket 20502.
9654 o Minor features (fallback directories):
9655 - Select 200 fallback directories for each release. Closes
9657 - Allow 3 fallback relays per operator, which is safe now that we
9658 are choosing 200 fallback relays. Closes ticket 20912.
9659 - Exclude relays affected by bug 20499 from the fallback list.
9660 Exclude relays from the fallback list if they are running versions
9661 known to be affected by bug 20499, or if in our tests they deliver
9662 a stale consensus (i.e. one that expired more than 24 hours ago).
9663 Closes ticket 20539.
9664 - Reduce the minimum fallback bandwidth to 1 MByte/s. Part of
9666 - Require fallback directories to have the same address and port for
9667 7 days (now that we have enough relays with this stability).
9668 Relays whose OnionOO stability timer is reset on restart by bug
9669 18050 should upgrade to Tor 0.2.8.7 or later, which has a fix for
9670 this issue. Closes ticket 20880; maintains short-term fix
9672 - Require fallbacks to have flags for 90% of the time (weighted
9673 decaying average), rather than 95%. This allows at least 73% of
9674 clients to bootstrap in the first 5 seconds without contacting an
9675 authority. Part of ticket 18828.
9676 - Annotate updateFallbackDirs.py with the bandwidth and consensus
9677 weight for each candidate fallback. Closes ticket 20878.
9678 - Make it easier to change the output sort order of fallbacks.
9679 Closes ticket 20822.
9680 - Display the relay fingerprint when downloading consensuses from
9681 fallbacks. Closes ticket 20908.
9683 o Minor features (geoip, also in 0.2.9.9):
9684 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
9687 o Minor features (next-gen onion service directories):
9688 - Remove the "EnableOnionServicesV3" consensus parameter that we
9689 introduced in 0.3.0.1-alpha: relays are now always willing to act
9690 as v3 onion service directories. Resolves ticket 19899.
9692 o Minor features (linting):
9693 - Enhance the changes file linter to warn on Tor versions that are
9694 prefixed with "tor-". Closes ticket 21096.
9696 o Minor features (logging):
9697 - In several places, describe unset ed25519 keys as "<unset>",
9698 rather than the scary "AAAAAAAA...AAA". Closes ticket 21037.
9700 o Minor bugfix (control protocol):
9701 - The reply to a "GETINFO config/names" request via the control
9702 protocol now spells the type "Dependent" correctly. This is a
9703 breaking change in the control protocol. (The field seems to be
9704 ignored by the most common known controllers.) Fixes bug 18146;
9705 bugfix on 0.1.1.4-alpha.
9707 o Minor bugfixes (bug resilience):
9708 - Fix an unreachable size_t overflow in base64_decode(). Fixes bug
9709 19222; bugfix on 0.2.0.9-alpha. Found by Guido Vranken; fixed by
9710 Hans Jerry Illikainen.
9712 o Minor bugfixes (build):
9713 - Replace obsolete Autoconf macros with their modern equivalent and
9714 prevent similar issues in the future. Fixes bug 20990; bugfix
9717 o Minor bugfixes (client, guards):
9718 - Fix bug where Tor would think that there are circuits waiting for
9719 better guards even though those circuits have been freed. Fixes
9720 bug 21142; bugfix on 0.3.0.1-alpha.
9722 o Minor bugfixes (config):
9723 - Don't assert on startup when trying to get the options list and
9724 LearnCircuitBuildTimeout is set to 0: we are currently parsing the
9725 options so of course they aren't ready yet. Fixes bug 21062;
9726 bugfix on 0.2.9.3-alpha.
9728 o Minor bugfixes (controller):
9729 - Make the GETINFO interface for inquiring about entry guards
9730 support the new guards backend. Fixes bug 20823; bugfix
9733 o Minor bugfixes (dead code):
9734 - Remove a redundant check for PidFile changes at runtime in
9735 options_transition_allowed(): this check is already performed
9736 regardless of whether the sandbox is active. Fixes bug 21123;
9737 bugfix on 0.2.5.4-alpha.
9739 o Minor bugfixes (documentation):
9740 - Update the tor manual page to document every option that can not
9741 be changed while tor is running. Fixes bug 21122.
9743 o Minor bugfixes (fallback directories):
9744 - Stop failing when a relay has no uptime data in
9745 updateFallbackDirs.py. Fixes bug 20945; bugfix on 0.2.8.1-alpha.
9746 - Avoid checking fallback candidates' DirPorts if they are down in
9747 OnionOO. When a relay operator has multiple relays, this
9748 prioritizes relays that are up over relays that are down. Fixes
9749 bug 20926; bugfix on 0.2.8.3-alpha.
9750 - Stop failing when OUTPUT_COMMENTS is True in updateFallbackDirs.py.
9751 Fixes bug 20877; bugfix on 0.2.8.3-alpha.
9753 o Minor bugfixes (guards, bootstrapping):
9754 - When connecting to a directory guard during bootstrap, do not mark
9755 the guard as successful until we receive a good-looking directory
9756 response from it. Fixes bug 20974; bugfix on 0.3.0.1-alpha.
9758 o Minor bugfixes (onion services):
9759 - Fix the config reload pruning of old vs new services so it
9760 actually works when both ephemeral and non-ephemeral services are
9761 configured. Fixes bug 21054; bugfix on 0.3.0.1-alpha.
9762 - Allow the number of introduction points to be as low as 0, rather
9763 than as low as 3. Fixes bug 21033; bugfix on 0.2.7.2-alpha.
9765 o Minor bugfixes (IPv6):
9766 - Make IPv6-using clients try harder to find an IPv6 directory
9767 server. Fixes bug 20999; bugfix on 0.2.8.2-alpha.
9768 - When IPv6 addresses have not been downloaded yet (microdesc
9769 consensus documents don't list relay IPv6 addresses), use hard-
9770 coded addresses for authorities, fallbacks, and configured
9771 bridges. Now IPv6-only clients can use microdescriptors. Fixes bug
9772 20996; bugfix on b167e82 from 19608 in 0.2.8.5-alpha.
9774 o Minor bugfixes (memory leaks):
9775 - Fix a memory leak when configuring hidden services. Fixes bug
9776 20987; bugfix on 0.3.0.1-alpha.
9778 o Minor bugfixes (portability, also in 0.2.9.9):
9779 - Avoid crashing when Tor is built using headers that contain
9780 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
9781 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
9783 - Fix Libevent detection on platforms without Libevent 1 headers
9784 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
9786 o Minor bugfixes (relay):
9787 - Honor DataDirectoryGroupReadable when tor is a relay. Previously,
9788 initializing the keys would reset the DataDirectory to 0700
9789 instead of 0750 even if DataDirectoryGroupReadable was set to 1.
9790 Fixes bug 19953; bugfix on 0.0.2pre16. Patch by "redfish".
9792 o Minor bugfixes (testing):
9793 - Remove undefined behavior from the backtrace generator by removing
9794 its signal handler. Fixes bug 21026; bugfix on 0.2.5.2-alpha.
9796 o Minor bugfixes (unit tests):
9797 - Allow the unit tests to pass even when DNS lookups of bogus
9798 addresses do not fail as expected. Fixes bug 20862 and 20863;
9799 bugfix on unit tests introduced in 0.2.8.1-alpha
9800 through 0.2.9.4-alpha.
9802 o Code simplification and refactoring:
9803 - Refactor code to manipulate global_origin_circuit_list into
9804 separate functions. Closes ticket 20921.
9806 o Documentation (formatting):
9807 - Clean up formatting of tor.1 man page and HTML doc, where <pre>
9808 blocks were incorrectly appearing. Closes ticket 20885.
9810 o Documentation (man page):
9811 - Clarify many options in tor.1 and add some min/max values for
9812 HiddenService options. Closes ticket 21058.
9815 Changes in version 0.2.9.9 - 2017-01-23
9816 Tor 0.2.9.9 fixes a denial-of-service bug where an attacker could
9817 cause relays and clients to crash, even if they were not built with
9818 the --enable-expensive-hardening option. This bug affects all 0.2.9.x
9819 versions, and also affects 0.3.0.1-alpha: all relays running an affected
9820 version should upgrade.
9822 This release also resolves a client-side onion service reachability
9823 bug, and resolves a pair of small portability issues.
9825 o Major bugfixes (security):
9826 - Downgrade the "-ftrapv" option from "always on" to "only on when
9827 --enable-expensive-hardening is provided." This hardening option,
9828 like others, can turn survivable bugs into crashes -- and having
9829 it on by default made a (relatively harmless) integer overflow bug
9830 into a denial-of-service bug. Fixes bug 21278 (TROVE-2017-001);
9831 bugfix on 0.2.9.1-alpha.
9833 o Major bugfixes (client, onion service):
9834 - Fix a client-side onion service reachability bug, where multiple
9835 socks requests to an onion service (or a single slow request)
9836 could cause us to mistakenly mark some of the service's
9837 introduction points as failed, and we cache that failure so
9838 eventually we run out and can't reach the service. Also resolves a
9839 mysterious "Remote server sent bogus reason code 65021" log
9840 warning. The bug was introduced in ticket 17218, where we tried to
9841 remember the circuit end reason as a uint16_t, which mangled
9842 negative values. Partially fixes bug 21056 and fixes bug 20307;
9843 bugfix on 0.2.8.1-alpha.
9845 o Minor features (geoip):
9846 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
9849 o Minor bugfixes (portability):
9850 - Avoid crashing when Tor is built using headers that contain
9851 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
9852 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
9854 - Fix Libevent detection on platforms without Libevent 1 headers
9855 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
9858 Changes in version 0.3.0.1-alpha - 2016-12-19
9859 Tor 0.3.0.1-alpha is the first alpha release in the 0.3.0 development
9860 series. It strengthens Tor's link and circuit handshakes by
9861 identifying relays by their Ed25519 keys, improves the algorithm that
9862 clients use to choose and maintain their list of guards, and includes
9863 additional backend support for the next-generation hidden service
9864 design. It also contains numerous other small features and
9865 improvements to security, correctness, and performance.
9867 Below are the changes since 0.2.9.8.
9869 o Major features (guard selection algorithm):
9870 - Tor's guard selection algorithm has been redesigned from the
9871 ground up, to better support unreliable networks and restrictive
9872 sets of entry nodes, and to better resist guard-capture attacks by
9873 hostile local networks. Implements proposal 271; closes
9876 o Major features (next-generation hidden services):
9877 - Relays can now handle v3 ESTABLISH_INTRO cells as specified by
9878 prop224 aka "Next Generation Hidden Services". Service and clients
9879 don't use this functionality yet. Closes ticket 19043. Based on
9880 initial code by Alec Heifetz.
9881 - Relays now support the HSDir version 3 protocol, so that they can
9882 can store and serve v3 descriptors. This is part of the next-
9883 generation onion service work detailed in proposal 224. Closes
9886 o Major features (protocol, ed25519 identity keys):
9887 - Relays now use Ed25519 to prove their Ed25519 identities and to
9888 one another, and to clients. This algorithm is faster and more
9889 secure than the RSA-based handshake we've been doing until now.
9890 Implements the second big part of proposal 220; Closes
9892 - Clients now support including Ed25519 identity keys in the EXTEND2
9893 cells they generate. By default, this is controlled by a consensus
9894 parameter, currently disabled. You can turn this feature on for
9895 testing by setting ExtendByEd25519ID in your configuration. This
9896 might make your traffic appear different than the traffic
9897 generated by other users, however. Implements part of ticket
9898 15056; part of proposal 220.
9899 - Relays now understand requests to extend to other relays by their
9900 Ed25519 identity keys. When an Ed25519 identity key is included in
9901 an EXTEND2 cell, the relay will only extend the circuit if the
9902 other relay can prove ownership of that identity. Implements part
9903 of ticket 15056; part of proposal 220.
9905 o Major bugfixes (scheduler):
9906 - Actually compare circuit policies in ewma_cmp_cmux(). This bug
9907 caused the channel scheduler to behave more or less randomly,
9908 rather than preferring channels with higher-priority circuits.
9909 Fixes bug 20459; bugfix on 0.2.6.2-alpha.
9911 o Minor features (controller):
9912 - When HSFETCH arguments cannot be parsed, say "Invalid argument"
9913 rather than "unrecognized." Closes ticket 20389; patch from
9916 o Minor features (diagnostic, directory client):
9917 - Warn when we find an unexpected inconsistency in directory
9918 download status objects. Prevents some negative consequences of
9921 o Minor features (directory authority):
9922 - Add a new authority-only AuthDirTestEd25519LinkKeys option (on by
9923 default) to control whether authorities should try to probe relays
9924 by their Ed25519 link keys. This option will go away in a few
9925 releases--unless we encounter major trouble in our ed25519 link
9926 protocol rollout, in which case it will serve as a safety option.
9928 o Minor features (directory cache):
9929 - Relays and bridges will now refuse to serve the consensus they
9930 have if they know it is too old for a client to use. Closes
9933 o Minor features (ed25519 link handshake):
9934 - Advertise support for the ed25519 link handshake using the
9935 subprotocol-versions mechanism, so that clients can tell which
9936 relays can identity themselves by Ed25519 ID. Closes ticket 20552.
9938 o Minor features (fingerprinting resistance, authentication):
9939 - Extend the length of RSA keys used for TLS link authentication to
9940 2048 bits. (These weren't used for forward secrecy; for forward
9941 secrecy, we used P256.) Closes ticket 13752.
9943 o Minor features (infrastructure):
9944 - Implement smartlist_add_strdup() function. Replaces the use of
9945 smartlist_add(sl, tor_strdup(str)). Closes ticket 20048.
9947 o Minor bugfixes (client):
9948 - When clients that use bridges start up with a cached consensus on
9949 disk, they were ignoring it and downloading a new one. Now they
9950 use the cached one. Fixes bug 20269; bugfix on 0.2.3.12-alpha.
9952 o Minor bugfixes (configuration):
9953 - Accept non-space whitespace characters after the severity level in
9954 the `Log` option. Fixes bug 19965; bugfix on 0.2.1.1-alpha.
9955 - Support "TByte" and "TBytes" units in options given in bytes.
9956 "TB", "terabyte(s)", "TBit(s)" and "terabit(s)" were already
9957 supported. Fixes bug 20622; bugfix on 0.2.0.14-alpha.
9959 o Minor bugfixes (consensus weight):
9960 - Add new consensus method that initializes bw weights to 1 instead
9961 of 0. This prevents a zero weight from making it all the way to
9962 the end (happens in small testing networks) and causing an error.
9963 Fixes bug 14881; bugfix on 0.2.2.17-alpha.
9965 o Minor bugfixes (descriptors):
9966 - Correctly recognise downloaded full descriptors as valid, even
9967 when using microdescriptors as circuits. This affects clients with
9968 FetchUselessDescriptors set, and may affect directory authorities.
9969 Fixes bug 20839; bugfix on 0.2.3.2-alpha.
9971 o Minor bugfixes (directory system):
9972 - Download all consensus flavors, descriptors, and authority
9973 certificates when FetchUselessDescriptors is set, regardless of
9974 whether tor is a directory cache or not. Fixes bug 20667; bugfix
9975 on all recent tor versions.
9976 - Bridges and relays now use microdescriptors (like clients do)
9977 rather than old-style router descriptors. Now bridges will blend
9978 in with clients in terms of the circuits they build. Fixes bug
9979 6769; bugfix on 0.2.3.2-alpha.
9981 o Minor bugfixes (ed25519 certificates):
9982 - Correctly interpret ed25519 certificates that would expire some
9983 time after 19 Jan 2038. Fixes bug 20027; bugfix on 0.2.7.2-alpha.
9985 o Minor bugfixes (hidden services):
9986 - Stop ignoring misconfigured hidden services. Instead, refuse to
9987 start tor until the misconfigurations have been corrected. Fixes
9988 bug 20559; bugfix on multiple commits in 0.2.7.1-alpha
9991 o Minor bugfixes (memory leak at exit):
9992 - Fix a small harmless memory leak at exit of the previously unused
9993 RSA->Ed identity cross-certificate. Fixes bug 17779; bugfix
9996 o Minor bugfixes (util):
9997 - When finishing writing a file to disk, if we were about to replace
9998 the file with the temporary file created before and we fail to
9999 replace it, remove the temporary file so it doesn't stay on disk.
10000 Fixes bug 20646; bugfix on 0.2.0.7-alpha. Patch by fk.
10002 o Minor bugfixes (Windows):
10003 - Check for getpagesize before using it to mmap files. This fixes
10004 compilation in some MinGW environments. Fixes bug 20530; bugfix on
10005 0.1.2.1-alpha. Reported by "ice".
10007 o Code simplification and refactoring:
10008 - Abolish all global guard context in entrynodes.c; replace with new
10009 guard_selection_t structure as preparation for proposal 271.
10010 Closes ticket 19858.
10011 - Introduce rend_service_is_ephemeral() that tells if given onion
10012 service is ephemeral. Replace unclear NULL-checkings for service
10013 directory with this function. Closes ticket 20526.
10014 - Extract magic numbers in circuituse.c into defined variables.
10015 - Refactor circuit_is_available_for_use to remove unnecessary check.
10016 - Refactor circuit_predict_and_launch_new for readability and
10017 testability. Closes ticket 18873.
10018 - Refactor large if statement in purpose_needs_anonymity to use
10019 switch statement instead. Closes part of ticket 20077.
10020 - Refactor the hashing API to return negative values for errors, as
10021 is done as throughout the codebase. Closes ticket 20717.
10022 - Remove data structures that were used to index or_connection
10023 objects by their RSA identity digests. These structures are fully
10024 redundant with the similar structures used in the
10025 channel abstraction.
10026 - Remove duplicate code in the channel_write_*cell() functions.
10027 Closes ticket 13827; patch from Pingl.
10028 - Remove redundant behavior of is_sensitive_dir_purpose, refactor to
10029 use only purpose_needs_anonymity. Closes part of ticket 20077.
10030 - The code to generate and parse EXTEND and EXTEND2 cells has been
10031 replaced with code automatically generated by the
10035 - Include the "TBits" unit in Tor's man page. Fixes part of bug
10036 20622; bugfix on 0.2.5.1-alpha.
10037 - Change '1' to 'weight_scale' in consensus bw weights calculation
10038 comments, as that is reality. Closes ticket 20273. Patch
10040 - Correct the value for AuthDirGuardBWGuarantee in the manpage, from
10041 250 KBytes to 2 MBytes. Fixes bug 20435; bugfix
10043 - Stop the man page from incorrectly stating that HiddenServiceDir
10044 must already exist. Fixes 20486.
10045 - Clarify that when ClientRejectInternalAddresses is enabled (which
10046 is the default), multicast DNS hostnames for machines on the local
10047 network (of the form *.local) are also rejected. Closes
10050 o Removed features:
10051 - The AuthDirMaxServersPerAuthAddr option no longer exists: The same
10052 limit for relays running on a single IP applies to authority IP
10053 addresses as well as to non-authority IP addresses. Closes
10055 - The UseDirectoryGuards torrc option no longer exists: all users
10056 that use entry guards will also use directory guards. Related to
10057 proposal 271; implements part of ticket 20831.
10060 - New unit tests for tor_htonll(). Closes ticket 19563. Patch
10061 from "overcaffeinated".
10062 - Perform the coding style checks when running the tests and fail
10063 when coding style violations are found. Closes ticket 5500.
10064 - Add tests for networkstatus_compute_bw_weights_v10.
10065 - Add unit tests circuit_predict_and_launch_new.
10066 - Extract dummy_origin_circuit_new so it can be used by other
10070 Changes in version 0.2.8.12 - 2016-12-19
10071 Tor 0.2.8.12 backports a fix for a medium-severity issue (bug 21018
10072 below) where Tor clients could crash when attempting to visit a
10073 hostile hidden service. Clients are recommended to upgrade as packages
10074 become available for their systems.
10076 It also includes an updated list of fallback directories, backported
10079 Now that the Tor 0.2.9 series is stable, only major bugfixes will be
10080 backported to 0.2.8 in the future.
10082 o Major bugfixes (parsing, security, backported from 0.2.9.8):
10083 - Fix a bug in parsing that could cause clients to read a single
10084 byte past the end of an allocated region. This bug could be used
10085 to cause hardened clients (built with --enable-expensive-hardening)
10086 to crash if they tried to visit a hostile hidden service. Non-
10087 hardened clients are only affected depending on the details of
10088 their platform's memory allocator. Fixes bug 21018; bugfix on
10089 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
10090 2016-12-002 and as CVE-2016-1254.
10092 o Minor features (fallback directory list, backported from 0.2.9.8):
10093 - Replace the 81 remaining fallbacks of the 100 originally
10094 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
10095 fallbacks (123 new, 54 existing, 27 removed) generated in December
10096 2016. Resolves ticket 20170.
10098 o Minor features (geoip, backported from 0.2.9.7-rc):
10099 - Update geoip and geoip6 to the December 7 2016 Maxmind GeoLite2
10103 Changes in version 0.2.9.8 - 2016-12-19
10104 Tor 0.2.9.8 is the first stable release of the Tor 0.2.9 series.
10106 The Tor 0.2.9 series makes mandatory a number of security features
10107 that were formerly optional. It includes support for a new shared-
10108 randomness protocol that will form the basis for next generation
10109 hidden services, includes a single-hop hidden service mode for
10110 optimizing .onion services that don't actually want to be hidden,
10111 tries harder not to overload the directory authorities with excessive
10112 downloads, and supports a better protocol versioning scheme for
10113 improved compatibility with other implementations of the Tor protocol.
10115 And of course, there are numerous other bugfixes and improvements.
10117 This release also includes a fix for a medium-severity issue (bug
10118 21018 below) where Tor clients could crash when attempting to visit a
10119 hostile hidden service. Clients are recommended to upgrade as packages
10120 become available for their systems.
10122 Below are the changes since 0.2.9.7-rc. For a list of all changes
10123 since 0.2.8, see the ReleaseNotes file.
10125 o Major bugfixes (parsing, security):
10126 - Fix a bug in parsing that could cause clients to read a single
10127 byte past the end of an allocated region. This bug could be used
10128 to cause hardened clients (built with --enable-expensive-hardening)
10129 to crash if they tried to visit a hostile hidden service. Non-
10130 hardened clients are only affected depending on the details of
10131 their platform's memory allocator. Fixes bug 21018; bugfix on
10132 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
10133 2016-12-002 and as CVE-2016-1254.
10135 o Minor features (fallback directory list):
10136 - Replace the 81 remaining fallbacks of the 100 originally
10137 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
10138 fallbacks (123 new, 54 existing, 27 removed) generated in December
10139 2016. Resolves ticket 20170.
10142 Changes in version 0.2.9.7-rc - 2016-12-12
10143 Tor 0.2.9.7-rc fixes a few small bugs remaining in Tor 0.2.9.6-rc,
10144 including a few that had prevented tests from passing on
10147 o Minor features (geoip):
10148 - Update geoip and geoip6 to the December 7 2016 Maxmind GeoLite2
10151 o Minor bugfix (build):
10152 - The current Git revision when building from a local repository is
10153 now detected correctly when using git worktrees. Fixes bug 20492;
10154 bugfix on 0.2.3.9-alpha.
10156 o Minor bugfixes (directory authority):
10157 - When computing old Tor protocol line version in protover, we were
10158 looking at 0.2.7.5 twice instead of a specific case for
10159 0.2.9.1-alpha. Fixes bug 20810; bugfix on 0.2.9.4-alpha.
10161 o Minor bugfixes (download scheduling):
10162 - Resolve a "bug" warning when considering a download schedule whose
10163 delay had approached INT_MAX. Fixes 20875; bugfix on 0.2.9.5-alpha.
10165 o Minor bugfixes (logging):
10166 - Downgrade a harmless log message about the
10167 pending_entry_connections list from "warn" to "info". Mitigates
10170 o Minor bugfixes (memory leak):
10171 - Fix a small memory leak when receiving AF_UNIX connections on a
10172 SocksPort. Fixes bug 20716; bugfix on 0.2.6.3-alpha.
10173 - When moving a signed descriptor object from a source to an
10174 existing destination, free the allocated memory inside that
10175 destination object. Fixes bug 20715; bugfix on 0.2.8.3-alpha.
10177 o Minor bugfixes (memory leak, use-after-free, linux seccomp2 sandbox):
10178 - Fix a memory leak and use-after-free error when removing entries
10179 from the sandbox's getaddrinfo() cache. Fixes bug 20710; bugfix on
10180 0.2.5.5-alpha. Patch from "cypherpunks".
10182 o Minor bugfixes (portability):
10183 - Use the correct spelling of MAC_OS_X_VERSION_10_12 on configure.ac
10184 Fixes bug 20935; bugfix on 0.2.9.6-rc.
10186 o Minor bugfixes (unit tests):
10187 - Stop expecting NetBSD unit tests to report success for ipfw. Part
10188 of a fix for bug 19960; bugfix on 0.2.9.5-alpha.
10189 - Fix tolerances in unit tests for monotonic time comparisons
10190 between nanoseconds and microseconds. Previously, we accepted a 10
10191 us difference only, which is not realistic on every platform's
10192 clock_gettime(). Fixes bug 19974; bugfix on 0.2.9.1-alpha.
10193 - Remove a double-free in the single onion service unit test. Stop
10194 ignoring a return value. Make future changes less error-prone.
10195 Fixes bug 20864; bugfix on 0.2.9.6-rc.
10198 Changes in version 0.2.8.11 - 2016-12-08
10199 Tor 0.2.8.11 backports fixes for additional portability issues that
10200 could prevent Tor from building correctly on OSX Sierra, or with
10201 OpenSSL 1.1. Affected users should upgrade; others can safely stay
10204 o Minor bugfixes (portability):
10205 - Avoid compilation errors when building on OSX Sierra. Sierra began
10206 to support the getentropy() and clock_gettime() APIs, but created
10207 a few problems in doing so. Tor 0.2.9 has a more thorough set of
10208 workarounds; in 0.2.8, we are just using the /dev/urandom and mach
10209 monotonic time interfaces. Fixes bug 20865. Bugfix
10212 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
10213 - Fix compilation with OpenSSL 1.1 and less commonly-used CPU
10214 architectures. Closes ticket 20588.
10217 Changes in version 0.2.8.10 - 2016-12-02
10218 Tor 0.2.8.10 backports a fix for a bug that would sometimes make clients
10219 unusable after they left standby mode. It also backports fixes for
10220 a few portability issues and a small but problematic memory leak.
10222 o Major bugfixes (client reliability, backport from 0.2.9.5-alpha):
10223 - When Tor leaves standby because of a new application request, open
10224 circuits as needed to serve that request. Previously, we would
10225 potentially wait a very long time. Fixes part of bug 19969; bugfix
10228 o Major bugfixes (client performance, backport from 0.2.9.5-alpha):
10229 - Clients now respond to new application stream requests immediately
10230 when they arrive, rather than waiting up to one second before
10231 starting to handle them. Fixes part of bug 19969; bugfix
10234 o Minor bugfixes (portability, backport from 0.2.9.6-rc):
10235 - Work around a bug in the OSX 10.12 SDK that would prevent us from
10236 successfully targeting earlier versions of OSX. Resolves
10239 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
10240 - Fix implicit conversion warnings under OpenSSL 1.1. Fixes bug
10241 20551; bugfix on 0.2.1.1-alpha.
10243 o Minor bugfixes (relay, backport from 0.2.9.5-alpha):
10244 - Work around a memory leak in OpenSSL 1.1 when encoding public
10245 keys. Fixes bug 20553; bugfix on 0.0.2pre8.
10247 o Minor features (geoip):
10248 - Update geoip and geoip6 to the November 3 2016 Maxmind GeoLite2
10251 Changes in version 0.2.9.6-rc - 2016-12-02
10252 Tor 0.2.9.6-rc fixes a few remaining bugs found in the previous alpha
10253 version. We hope that it will be ready to become stable soon, and we
10254 encourage everyone to test this release. If no showstopper bugs are
10255 found here, the next 0.2.9 release will be stable.
10257 o Major bugfixes (relay, resolver, logging):
10258 - For relays that don't know their own address, avoid attempting a
10259 local hostname resolve for each descriptor we download. This
10260 will cut down on the number of "Success: chose address 'x.x.x.x'"
10261 log lines, and also avoid confusing clock jumps if the resolver
10262 is slow. Fixes bugs 20423 and 20610; bugfix on 0.2.8.1-alpha.
10264 o Minor bugfixes (client, fascistfirewall):
10265 - Avoid spurious warnings when ReachableAddresses or FascistFirewall
10266 is set. Fixes bug 20306; bugfix on 0.2.8.2-alpha.
10268 o Minor bugfixes (hidden services):
10269 - Stop ignoring the anonymity status of saved keys for hidden
10270 services and single onion services when first starting tor.
10271 Instead, refuse to start tor if any hidden service key has been
10272 used in a different hidden service anonymity mode. Fixes bug
10273 20638; bugfix on 17178 in 0.2.9.3-alpha; reported by ahf.
10275 o Minor bugfixes (portability):
10276 - Work around a bug in the OSX 10.12 SDK that would prevent us from
10277 successfully targeting earlier versions of OSX. Resolves
10279 - Run correctly when built on Windows build environments that
10280 require _vcsprintf(). Fixes bug 20560; bugfix on 0.2.2.11-alpha.
10282 o Minor bugfixes (single onion services, Tor2web):
10283 - Stop complaining about long-term one-hop circuits deliberately
10284 created by single onion services and Tor2web. These log messages
10285 are intended to diagnose issue 8387, which relates to circuits
10286 hanging around forever for no reason. Fixes bug 20613; bugfix on
10287 0.2.9.1-alpha. Reported by "pastly".
10289 o Minor bugfixes (unit tests):
10290 - Stop spurious failures in the local interface address discovery
10291 unit tests. Fixes bug 20634; bugfix on 0.2.8.1-alpha; patch by
10295 - Correct the minimum bandwidth value in torrc.sample, and queue a
10296 corresponding change for torrc.minimal. Closes ticket 20085.
10299 Changes in version 0.2.9.5-alpha - 2016-11-08
10300 Tor 0.2.9.5-alpha fixes numerous bugs discovered in the previous alpha
10301 version. We believe one or two probably remain, and we encourage
10302 everyone to test this release.
10304 o Major bugfixes (client performance):
10305 - Clients now respond to new application stream requests immediately
10306 when they arrive, rather than waiting up to one second before
10307 starting to handle them. Fixes part of bug 19969; bugfix
10310 o Major bugfixes (client reliability):
10311 - When Tor leaves standby because of a new application request, open
10312 circuits as needed to serve that request. Previously, we would
10313 potentially wait a very long time. Fixes part of bug 19969; bugfix
10316 o Major bugfixes (download scheduling):
10317 - When using an exponential backoff schedule, do not give up on
10318 downloading just because we have failed a bunch of times. Since
10319 each delay is longer than the last, retrying indefinitely won't
10320 hurt. Fixes bug 20536; bugfix on 0.2.9.1-alpha.
10321 - If a consensus expires while we are waiting for certificates to
10322 download, stop waiting for certificates.
10323 - If we stop waiting for certificates less than a minute after we
10324 started downloading them, do not consider the certificate download
10325 failure a separate failure. Fixes bug 20533; bugfix
10327 - Remove the maximum delay on exponential-backoff scheduling. Since
10328 we now allow an infinite number of failures (see ticket 20536), we
10329 must now allow the time to grow longer on each failure. Fixes part
10330 of bug 20534; bugfix on 0.2.9.1-alpha.
10331 - Make our initial download delays closer to those from 0.2.8. Fixes
10332 another part of bug 20534; bugfix on 0.2.9.1-alpha.
10333 - When determining when to download a directory object, handle times
10334 after 2038 if the operating system supports them. (Someday this
10335 will be important!) Fixes bug 20587; bugfix on 0.2.8.1-alpha.
10336 - When using exponential backoff in test networks, use a lower
10337 exponent, so the delays do not vary as much. This helps test
10338 networks bootstrap consistently. Fixes bug 20597; bugfix on 20499.
10340 o Minor features (geoip):
10341 - Update geoip and geoip6 to the November 3 2016 Maxmind GeoLite2
10344 o Minor bugfixes (client directory scheduling):
10345 - Treat "relay too busy to answer request" as a failed request and a
10346 reason to back off on our retry frequency. This is safe now that
10347 exponential backoffs retry indefinitely, and avoids a bug where we
10348 would reset our download schedule erroneously. Fixes bug 20593;
10349 bugfix on 0.2.9.1-alpha.
10351 o Minor bugfixes (client, logging):
10352 - Remove a BUG warning in circuit_pick_extend_handshake(). Instead,
10353 assume all nodes support EXTEND2. Use ntor whenever a key is
10354 available. Fixes bug 20472; bugfix on 0.2.9.3-alpha.
10355 - On DNSPort, stop logging a BUG warning on a failed hostname
10356 lookup. Fixes bug 19869; bugfix on 0.2.9.1-alpha.
10358 o Minor bugfixes (hidden services):
10359 - When configuring hidden services, check every hidden service
10360 directory's permissions. Previously, we only checked the last
10361 hidden service. Fixes bug 20529; bugfix the work to fix 13942
10364 o Minor bugfixes (portability):
10365 - Fix compilation with OpenSSL 1.1 and less commonly-used CPU
10366 architectures. Closes ticket 20588.
10367 - Use ECDHE ciphers instead of ECDH in tortls tests. LibreSSL has
10368 removed the ECDH ciphers which caused the tests to fail on
10369 platforms which use it. Fixes bug 20460; bugfix on 0.2.8.1-alpha.
10370 - Fix implicit conversion warnings under OpenSSL 1.1. Fixes bug
10371 20551; bugfix on 0.2.1.1-alpha.
10373 o Minor bugfixes (relay bootstrap):
10374 - Ensure relays don't make multiple connections during bootstrap.
10375 Fixes bug 20591; bugfix on 0.2.8.1-alpha.
10377 o Minor bugfixes (relay):
10378 - Work around a memory leak in OpenSSL 1.1 when encoding public
10379 keys. Fixes bug 20553; bugfix on 0.0.2pre8.
10380 - Avoid a small memory leak when informing worker threads about
10381 rotated onion keys. Fixes bug 20401; bugfix on 0.2.6.3-alpha.
10382 - Do not try to parallelize workers more than 16x without the user
10383 explicitly configuring us to do so, even if we do detect more than
10384 16 CPU cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
10386 o Minor bugfixes (single onion services):
10387 - Start correctly when creating a single onion service in a
10388 directory that did not previously exist. Fixes bug 20484; bugfix
10391 o Minor bugfixes (testing):
10392 - Avoid a unit test failure on systems with over 16 detectable CPU
10393 cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
10396 - Clarify that setting HiddenServiceNonAnonymousMode requires you to
10397 also set "SOCKSPort 0". Fixes bug 20487; bugfix on 0.2.9.3-alpha.
10398 - Module-level documentation for several more modules. Closes
10399 tickets 19287 and 19290.
10402 Changes in version 0.2.8.9 - 2016-10-17
10403 Tor 0.2.8.9 backports a fix for a security hole in previous versions
10404 of Tor that would allow a remote attacker to crash a Tor client,
10405 hidden service, relay, or authority. All Tor users should upgrade to
10406 this version, or to 0.2.9.4-alpha. Patches will be released for older
10409 o Major features (security fixes, also in 0.2.9.4-alpha):
10410 - Prevent a class of security bugs caused by treating the contents
10411 of a buffer chunk as if they were a NUL-terminated string. At
10412 least one such bug seems to be present in all currently used
10413 versions of Tor, and would allow an attacker to remotely crash
10414 most Tor instances, especially those compiled with extra compiler
10415 hardening. With this defense in place, such bugs can't crash Tor,
10416 though we should still fix them as they occur. Closes ticket
10417 20384 (TROVE-2016-10-001).
10419 o Minor features (geoip):
10420 - Update geoip and geoip6 to the October 4 2016 Maxmind GeoLite2
10424 Changes in version 0.2.9.4-alpha - 2016-10-17
10425 Tor 0.2.9.4-alpha fixes a security hole in previous versions of Tor
10426 that would allow a remote attacker to crash a Tor client, hidden
10427 service, relay, or authority. All Tor users should upgrade to this
10428 version, or to 0.2.8.9. Patches will be released for older versions
10431 Tor 0.2.9.4-alpha also adds numerous small features and fix-ups to
10432 previous versions of Tor, including the implementation of a feature to
10433 future- proof the Tor ecosystem against protocol changes, some bug
10434 fixes necessary for Tor Browser to use unix domain sockets correctly,
10435 and several portability improvements. We anticipate that this will be
10436 the last alpha in the Tor 0.2.9 series, and that the next release will
10437 be a release candidate.
10439 o Major features (security fixes):
10440 - Prevent a class of security bugs caused by treating the contents
10441 of a buffer chunk as if they were a NUL-terminated string. At
10442 least one such bug seems to be present in all currently used
10443 versions of Tor, and would allow an attacker to remotely crash
10444 most Tor instances, especially those compiled with extra compiler
10445 hardening. With this defense in place, such bugs can't crash Tor,
10446 though we should still fix them as they occur. Closes ticket
10447 20384 (TROVE-2016-10-001).
10449 o Major features (subprotocol versions):
10450 - Tor directory authorities now vote on a set of recommended
10451 subprotocol versions, and on a set of required subprotocol
10452 versions. Clients and relays that lack support for a _required_
10453 subprotocol version will not start; those that lack support for a
10454 _recommended_ subprotocol version will warn the user to upgrade.
10455 Closes ticket 19958; implements part of proposal 264.
10456 - Tor now uses "subprotocol versions" to indicate compatibility.
10457 Previously, versions of Tor looked at the declared Tor version of
10458 a relay to tell whether they could use a given feature. Now, they
10459 should be able to rely on its declared subprotocol versions. This
10460 change allows compatible implementations of the Tor protocol(s) to
10461 exist without pretending to be 100% bug-compatible with particular
10462 releases of Tor itself. Closes ticket 19958; implements part of
10465 o Minor feature (fallback directories):
10466 - Remove broken fallbacks from the hard-coded fallback directory
10467 list. Closes ticket 20190; patch by teor.
10469 o Minor features (client, directory):
10470 - Since authorities now omit all routers that lack the Running and
10471 Valid flags, we assume that any relay listed in the consensus must
10472 have those flags. Closes ticket 20001; implements part of
10475 o Minor features (compilation, portability):
10476 - Compile correctly on MacOS 10.12 (aka "Sierra"). Closes
10479 o Minor features (development tools, etags):
10480 - Teach the "make tags" Makefile target how to correctly find
10481 "MOCK_IMPL" function definitions. Patch from nherring; closes
10484 o Minor features (geoip):
10485 - Update geoip and geoip6 to the October 4 2016 Maxmind GeoLite2
10488 o Minor features (unix domain sockets):
10489 - When configuring a unix domain socket for a SocksPort,
10490 ControlPort, or Hidden service, you can now wrap the address in
10491 quotes, using C-style escapes inside the quotes. This allows unix
10492 domain socket paths to contain spaces.
10494 o Minor features (virtual addresses):
10495 - Increase the maximum number of bits for the IPv6 virtual network
10496 prefix from 16 to 104. In this way, the condition for address
10497 allocation is less restrictive. Closes ticket 20151; feature
10500 o Minor bugfixes (address discovery):
10501 - Stop reordering IP addresses returned by the OS. This makes it
10502 more likely that Tor will guess the same relay IP address every
10503 time. Fixes issue 20163; bugfix on 0.2.7.1-alpha, ticket 17027.
10504 Reported by René Mayrhofer, patch by "cypherpunks".
10506 o Minor bugfixes (client, unix domain sockets):
10507 - Disable IsolateClientAddr when using AF_UNIX backed SocksPorts as
10508 the client address is meaningless. Fixes bug 20261; bugfix
10511 o Minor bugfixes (compilation, OpenBSD):
10512 - Detect Libevent2 functions correctly on systems that provide
10513 libevent2, but where libevent1 is linked with -levent. Fixes bug
10514 19904; bugfix on 0.2.2.24-alpha. Patch from Rubiate.
10516 o Minor bugfixes (configuration):
10517 - When parsing quoted configuration values from the torrc file,
10518 handle windows line endings correctly. Fixes bug 19167; bugfix on
10519 0.2.0.16-alpha. Patch from "Pingl".
10521 o Minor bugfixes (getpass):
10522 - Defensively fix a non-triggerable heap corruption at do_getpass()
10523 to protect ourselves from mistakes in the future. Fixes bug
10524 19223; bugfix on 0.2.7.3-rc. Bug found by Guido Vranken, patch
10527 o Minor bugfixes (hidden service):
10528 - Allow hidden services to run on IPv6 addresses even when the
10529 IPv6Exit option is not set. Fixes bug 18357; bugfix
10533 - Add module-level internal documentation for 36 C files that
10534 previously didn't have a high-level overview. Closes ticket #20385.
10536 o Required libraries:
10537 - When building with OpenSSL, Tor now requires version 1.0.1 or
10538 later. OpenSSL 1.0.0 and earlier are no longer supported by the
10539 OpenSSL team, and should not be used. Closes ticket 20303.
10542 Changes in version 0.2.9.3-alpha - 2016-09-23
10543 Tor 0.2.9.3-alpha adds improved support for entities that want to make
10544 high-performance services available through the Tor .onion mechanism
10545 without themselves receiving anonymity as they host those services. It
10546 also tries harder to ensure that all steps on a circuit are using the
10547 strongest crypto possible, strengthens some TLS properties, and
10548 resolves several bugs -- including a pair of crash bugs from the 0.2.8
10549 series. Anybody running an earlier version of 0.2.9.x should upgrade.
10551 o Major bugfixes (crash, also in 0.2.8.8):
10552 - Fix a complicated crash bug that could affect Tor clients
10553 configured to use bridges when replacing a networkstatus consensus
10554 in which one of their bridges was mentioned. OpenBSD users saw
10555 more crashes here, but all platforms were potentially affected.
10556 Fixes bug 20103; bugfix on 0.2.8.2-alpha.
10558 o Major bugfixes (relay, OOM handler, also in 0.2.8.8):
10559 - Fix a timing-dependent assertion failure that could occur when we
10560 tried to flush from a circuit after having freed its cells because
10561 of an out-of-memory condition. Fixes bug 20203; bugfix on
10562 0.2.8.1-alpha. Thanks to "cypherpunks" for help diagnosing
10565 o Major features (circuit building, security):
10566 - Authorities, relays and clients now require ntor keys in all
10567 descriptors, for all hops (except for rare hidden service protocol
10568 cases), for all circuits, and for all other roles. Part of
10570 - Tor authorities, relays, and clients only use ntor, except for
10571 rare cases in the hidden service protocol. Part of ticket 19163.
10573 o Major features (single-hop "hidden" services):
10574 - Add experimental HiddenServiceSingleHopMode and
10575 HiddenServiceNonAnonymousMode options. When both are set to 1,
10576 every hidden service on a Tor instance becomes a non-anonymous
10577 Single Onion Service. Single Onions make one-hop (direct)
10578 connections to their introduction and renzedvous points. One-hop
10579 circuits make Single Onion servers easily locatable, but clients
10580 remain location-anonymous. This is compatible with the existing
10581 hidden service implementation, and works on the current tor
10582 network without any changes to older relays or clients. Implements
10583 proposal 260, completes ticket 17178. Patch by teor and asn.
10585 o Major features (resource management):
10586 - Tor can now notice it is about to run out of sockets, and
10587 preemptively close connections of lower priority. (This feature is
10588 off by default for now, since the current prioritizing method is
10589 yet not mature enough. You can enable it by setting
10590 "DisableOOSCheck 0", but watch out: it might close some sockets
10591 you would rather have it keep.) Closes ticket 18640.
10593 o Major bugfixes (circuit building):
10594 - Hidden service client-to-intro-point and service-to-rendezvous-
10595 point circuits use the TAP key supplied by the protocol, to avoid
10596 epistemic attacks. Fixes bug 19163; bugfix on 0.2.4.18-rc.
10598 o Major bugfixes (compilation, OpenBSD):
10599 - Fix a Libevent-detection bug in our autoconf script that would
10600 prevent Tor from linking successfully on OpenBSD. Patch from
10601 rubiate. Fixes bug 19902; bugfix on 0.2.9.1-alpha.
10603 o Major bugfixes (hidden services):
10604 - Clients now require hidden services to include the TAP keys for
10605 their intro points in the hidden service descriptor. This prevents
10606 an inadvertent upgrade to ntor, which a malicious hidden service
10607 could use to distinguish clients by consensus version. Fixes bug
10608 20012; bugfix on 0.2.4.8-alpha. Patch by teor.
10610 o Minor features (security, TLS):
10611 - Servers no longer support clients that without AES ciphersuites.
10612 (3DES is no longer considered an acceptable cipher.) We believe
10613 that no such Tor clients currently exist, since Tor has required
10614 OpenSSL 0.9.7 or later since 2009. Closes ticket 19998.
10616 o Minor feature (fallback directories):
10617 - Remove 8 fallbacks that are no longer suitable, leaving 81 of the
10618 100 fallbacks originally introduced in Tor 0.2.8.2-alpha in March
10619 2016. Closes ticket 20190; patch by teor.
10621 o Minor features (geoip, also in 0.2.8.8):
10622 - Update geoip and geoip6 to the September 6 2016 Maxmind GeoLite2
10625 o Minor feature (port flags):
10626 - Add new flags to the *Port options to finer control over which
10627 requests are allowed. The flags are NoDNSRequest, NoOnionTraffic,
10628 and the synthetic flag OnionTrafficOnly, which is equivalent to
10629 NoDNSRequest, NoIPv4Traffic, and NoIPv6Traffic. Closes enhancement
10630 18693; patch by "teor".
10632 o Minor features (directory authority):
10633 - After voting, if the authorities decide that a relay is not
10634 "Valid", they no longer include it in the consensus at all. Closes
10635 ticket 20002; implements part of proposal 272.
10637 o Minor features (testing):
10638 - Disable memory protections on OpenBSD when performing our unit
10639 tests for memwipe(). The test deliberately invokes undefined
10640 behavior, and the OpenBSD protections interfere with this. Patch
10641 from "rubiate". Closes ticket 20066.
10643 o Minor features (testing, ipv6):
10644 - Add the single-onion and single-onion-ipv6 chutney targets to
10645 "make test-network-all". This requires a recent chutney version
10646 with the single onion network flavours (git c72a652 or later).
10647 Closes ticket 20072; patch by teor.
10648 - Add the hs-ipv6 chutney target to make test-network-all's IPv6
10649 tests. Remove bridges+hs, as it's somewhat redundant. This
10650 requires a recent chutney version that supports IPv6 clients,
10651 relays, and authorities. Closes ticket 20069; patch by teor.
10653 o Minor features (Tor2web):
10654 - Make Tor2web clients respect ReachableAddresses. This feature was
10655 inadvertently enabled in 0.2.8.6, then removed by bugfix 19973 on
10656 0.2.8.7. Implements feature 20034. Patch by teor.
10658 o Minor features (unit tests):
10659 - We've done significant work to make the unit tests run faster.
10660 - Our link-handshake unit tests now check that when invalid
10661 handshakes fail, they fail with the error messages we expected.
10662 - Our unit testing code that captures log messages no longer
10663 prevents them from being written out if the user asked for them
10664 (by passing --debug or --info or or --notice --warn to the "test"
10665 binary). This change prevents us from missing unexpected log
10666 messages simply because we were looking for others. Related to
10668 - The unit tests now log all warning messages with the "BUG" flag.
10669 Previously, they only logged errors by default. This change will
10670 help us make our testing code more correct, and make sure that we
10671 only hit this code when we mean to. In the meantime, however,
10672 there will be more warnings in the unit test logs than before.
10673 This is preparatory work for ticket 19999.
10674 - The unit tests now treat any failure of a "tor_assert_nonfatal()"
10675 assertion as a test failure.
10677 o Minor bug fixes (circuits):
10678 - Use the CircuitBuildTimeout option whenever
10679 LearnCircuitBuildTimeout is disabled. Previously, we would respect
10680 the option when a user disabled it, but not when it was disabled
10681 because some other option was set. Fixes bug 20073; bugfix on
10682 0.2.4.12-alpha. Patch by teor.
10684 o Minor bugfixes (allocation):
10685 - Change how we allocate memory for large chunks on buffers, to
10686 avoid a (currently impossible) integer overflow, and to waste less
10687 space when allocating unusually large chunks. Fixes bug 20081;
10688 bugfix on 0.2.0.16-alpha. Issue identified by Guido Vranken.
10689 - Always include orconfig.h before including any other C headers.
10690 Sometimes, it includes macros that affect the behavior of the
10691 standard headers. Fixes bug 19767; bugfix on 0.2.9.1-alpha (the
10692 first version to use AC_USE_SYSTEM_EXTENSIONS).
10693 - Fix a syntax error in the IF_BUG_ONCE__() macro in non-GCC-
10694 compatible compilers. Fixes bug 20141; bugfix on 0.2.9.1-alpha.
10695 Patch from Gisle Vanem.
10696 - Stop trying to build with Clang 4.0's -Wthread-safety warnings.
10697 They apparently require a set of annotations that we aren't
10698 currently using, and they create false positives in our pthreads
10699 wrappers. Fixes bug 20110; bugfix on 0.2.9.1-alpha.
10701 o Minor bugfixes (directory authority):
10702 - Die with a more useful error when the operator forgets to place
10703 the authority_signing_key file into the keys directory. This
10704 avoids an uninformative assert & traceback about having an invalid
10705 key. Fixes bug 20065; bugfix on 0.2.0.1-alpha.
10706 - When allowing private addresses, mark Exits that only exit to
10707 private locations as such. Fixes bug 20064; bugfix
10710 o Minor bugfixes (documentation):
10711 - Document the default PathsNeededToBuildCircuits value that's used
10712 by clients when the directory authorities don't set
10713 min_paths_for_circs_pct. Fixes bug 20117; bugfix on 02c320916e02
10714 in 0.2.4.10-alpha. Patch by teor, reported by Jesse V.
10715 - Fix manual for the User option: it takes a username, not a UID.
10716 Fixes bug 19122; bugfix on 0.0.2pre16 (the first version to have
10719 o Minor bugfixes (hidden services):
10720 - Stop logging intro point details to the client log on certain
10721 error conditions. Fixed as part of bug 20012; bugfix on
10722 0.2.4.8-alpha. Patch by teor.
10724 o Minor bugfixes (IPv6, testing):
10725 - Check for IPv6 correctly on Linux when running test networks.
10726 Fixes bug 19905; bugfix on 0.2.7.3-rc; patch by teor.
10728 o Minor bugfixes (Linux seccomp2 sandbox):
10729 - Add permission to run the sched_yield() and sigaltstack() system
10730 calls, in order to support versions of Tor compiled with asan or
10731 ubsan code that use these calls. Now "sandbox 1" and
10732 "--enable-expensive-hardening" should be compatible on more
10733 systems. Fixes bug 20063; bugfix on 0.2.5.1-alpha.
10735 o Minor bugfixes (logging):
10736 - When logging a message from the BUG() macro, be explicit about
10737 what we were asserting. Previously we were confusing what we were
10738 asserting with what the bug was. Fixes bug 20093; bugfix
10740 - When we are unable to remove the bw_accounting file, do not warn
10741 if the reason we couldn't remove it was that it didn't exist.
10742 Fixes bug 19964; bugfix on 0.2.5.4-alpha. Patch from 'pastly'.
10744 o Minor bugfixes (option parsing):
10745 - Count unix sockets when counting client listeners (SOCKS, Trans,
10746 NATD, and DNS). This has no user-visible behaviour changes: these
10747 options are set once, and never read. Required for correct
10748 behaviour in ticket 17178. Fixes bug 19677; bugfix on
10749 0.2.6.3-alpha. Patch by teor.
10751 o Minor bugfixes (options):
10752 - Check the consistency of UseEntryGuards and EntryNodes more
10753 reliably. Fixes bug 20074; bugfix on 0.2.4.12-alpha. Patch
10755 - Stop changing the configured value of UseEntryGuards on
10756 authorities and Tor2web clients. Fixes bug 20074; bugfix on
10757 commits 51fc6799 in 0.1.1.16-rc and acda1735 in 0.2.4.3-alpha.
10760 o Minor bugfixes (Tor2web):
10761 - Prevent Tor2web clients running hidden services, these services
10762 are not anonymous due to the one-hop client paths. Fixes bug
10763 19678. Patch by teor.
10765 o Minor bugfixes (unit tests):
10766 - Fix a shared-random unit test that was failing on big endian
10767 architectures due to internal representation of a integer copied
10768 to a buffer. The test is changed to take a full 32 bytes of data
10769 and use the output of a python script that make the COMMIT and
10770 REVEAL calculation according to the spec. Fixes bug 19977; bugfix
10772 - The tor_tls_server_info_callback unit test no longer crashes when
10773 debug-level logging is turned on. Fixes bug 20041; bugfix
10777 Changes in version 0.2.8.8 - 2016-09-23
10778 Tor 0.2.8.8 fixes two crash bugs present in previous versions of the
10779 0.2.8.x series. Relays running 0.2.8.x should upgrade, as should users
10780 who select public relays as their bridges.
10782 o Major bugfixes (crash):
10783 - Fix a complicated crash bug that could affect Tor clients
10784 configured to use bridges when replacing a networkstatus consensus
10785 in which one of their bridges was mentioned. OpenBSD users saw
10786 more crashes here, but all platforms were potentially affected.
10787 Fixes bug 20103; bugfix on 0.2.8.2-alpha.
10789 o Major bugfixes (relay, OOM handler):
10790 - Fix a timing-dependent assertion failure that could occur when we
10791 tried to flush from a circuit after having freed its cells because
10792 of an out-of-memory condition. Fixes bug 20203; bugfix on
10793 0.2.8.1-alpha. Thanks to "cypherpunks" for help diagnosing
10796 o Minor feature (fallback directories):
10797 - Remove 8 fallbacks that are no longer suitable, leaving 81 of the
10798 100 fallbacks originally introduced in Tor 0.2.8.2-alpha in March
10799 2016. Closes ticket 20190; patch by teor.
10801 o Minor features (geoip):
10802 - Update geoip and geoip6 to the September 6 2016 Maxmind GeoLite2
10806 Changes in version 0.2.9.2-alpha - 2016-08-24
10807 Tor 0.2.9.2-alpha continues development of the 0.2.9 series with
10808 several new features and bugfixes. It also includes an important
10809 authority update and an important bugfix from 0.2.8.7. Everyone who
10810 sets the ReachableAddresses option, and all bridges, are strongly
10811 encouraged to upgrade to 0.2.8.7, or to 0.2.9.2-alpha.
10813 o Directory authority changes (also in 0.2.8.7):
10814 - The "Tonga" bridge authority has been retired; the new bridge
10815 authority is "Bifroest". Closes tickets 19728 and 19690.
10817 o Major bugfixes (client, security, also in 0.2.8.7):
10818 - Only use the ReachableAddresses option to restrict the first hop
10819 in a path. In earlier versions of 0.2.8.x, it would apply to
10820 every hop in the path, with a possible degradation in anonymity
10821 for anyone using an uncommon ReachableAddress setting. Fixes bug
10822 19973; bugfix on 0.2.8.2-alpha.
10824 o Major features (user interface):
10825 - Tor now supports the ability to declare options deprecated, so
10826 that we can recommend that people stop using them. Previously,
10827 this was done in an ad-hoc way. Closes ticket 19820.
10829 o Major bugfixes (directory downloads):
10830 - Avoid resetting download status for consensuses hourly, since we
10831 already have another, smarter retry mechanism. Fixes bug 8625;
10832 bugfix on 0.2.0.9-alpha.
10834 o Minor features (config):
10835 - Warn users when descriptor and port addresses are inconsistent.
10836 Mitigates bug 13953; patch by teor.
10838 o Minor features (geoip):
10839 - Update geoip and geoip6 to the August 2 2016 Maxmind GeoLite2
10842 o Minor features (user interface):
10843 - There is a new --list-deprecated-options command-line option to
10844 list all of the deprecated options. Implemented as part of
10847 o Minor bugfixes (code style):
10848 - Fix an integer signedness conversion issue in the case conversion
10849 tables. Fixes bug 19168; bugfix on 0.2.1.11-alpha.
10851 o Minor bugfixes (compilation):
10852 - Build correctly on versions of libevent2 without support for
10853 evutil_secure_rng_add_bytes(). Fixes bug 19904; bugfix
10855 - Fix a compilation warning on GCC versions before 4.6. Our
10856 ENABLE_GCC_WARNING macro used the word "warning" as an argument,
10857 when it is also required as an argument to the compiler pragma.
10858 Fixes bug 19901; bugfix on 0.2.9.1-alpha.
10860 o Minor bugfixes (compilation, also in 0.2.8.7):
10861 - Remove an inappropriate "inline" in tortls.c that was causing
10862 warnings on older versions of GCC. Fixes bug 19903; bugfix
10865 o Minor bugfixes (fallback directories, also in 0.2.8.7):
10866 - Avoid logging a NULL string pointer when loading fallback
10867 directory information. Fixes bug 19947; bugfix on 0.2.4.7-alpha
10868 and 0.2.8.1-alpha. Report and patch by "rubiate".
10870 o Minor bugfixes (logging):
10871 - Log a more accurate message when we fail to dump a microdescriptor.
10872 Fixes bug 17758; bugfix on 0.2.2.8-alpha. Patch from Daniel Pinto.
10874 o Minor bugfixes (memory leak):
10875 - Fix a series of slow memory leaks related to parsing torrc files
10876 and options. Fixes bug 19466; bugfix on 0.2.1.6-alpha.
10878 o Deprecated features:
10879 - A number of DNS-cache-related sub-options for client ports are now
10880 deprecated for security reasons, and may be removed in a future
10881 version of Tor. (We believe that client-side DNS caching is a bad
10882 idea for anonymity, and you should not turn it on.) The options
10883 are: CacheDNS, CacheIPv4DNS, CacheIPv6DNS, UseDNSCache,
10884 UseIPv4Cache, and UseIPv6Cache.
10885 - A number of options are deprecated for security reasons, and may
10886 be removed in a future version of Tor. The options are:
10887 AllowDotExit, AllowInvalidNodes, AllowSingleHopCircuits,
10888 AllowSingleHopExits, ClientDNSRejectInternalAddresses,
10889 CloseHSClientCircuitsImmediatelyOnTimeout,
10890 CloseHSServiceRendCircuitsImmediatelyOnTimeout,
10891 ExcludeSingleHopRelays, FastFirstHopPK, TLSECGroup,
10892 UseNTorHandshake, and WarnUnsafeSocks.
10893 - The *ListenAddress options are now deprecated as unnecessary: the
10894 corresponding *Port options should be used instead. These options
10895 may someday be removed. The affected options are:
10896 ControlListenAddress, DNSListenAddress, DirListenAddress,
10897 NATDListenAddress, ORListenAddress, SocksListenAddress,
10898 and TransListenAddress.
10901 - Correct the IPv6 syntax in our documentation for the
10902 VirtualAddrNetworkIPv6 torrc option. Closes ticket 19743.
10905 - We no longer include the (dead, deprecated) bufferevent code in
10906 Tor. Closes ticket 19450. Based on a patch from U+039b.
10909 Changes in version 0.2.8.7 - 2016-08-24
10910 Tor 0.2.8.7 fixes an important bug related to the ReachableAddresses
10911 option in 0.2.8.6, and replaces a retiring bridge authority. Everyone
10912 who sets the ReachableAddresses option, and all bridges, are strongly
10913 encouraged to upgrade.
10915 o Directory authority changes:
10916 - The "Tonga" bridge authority has been retired; the new bridge
10917 authority is "Bifroest". Closes tickets 19728 and 19690.
10919 o Major bugfixes (client, security):
10920 - Only use the ReachableAddresses option to restrict the first hop
10921 in a path. In earlier versions of 0.2.8.x, it would apply to
10922 every hop in the path, with a possible degradation in anonymity
10923 for anyone using an uncommon ReachableAddress setting. Fixes bug
10924 19973; bugfix on 0.2.8.2-alpha.
10926 o Minor features (geoip):
10927 - Update geoip and geoip6 to the August 2 2016 Maxmind GeoLite2
10930 o Minor bugfixes (compilation):
10931 - Remove an inappropriate "inline" in tortls.c that was causing
10932 warnings on older versions of GCC. Fixes bug 19903; bugfix
10935 o Minor bugfixes (fallback directories):
10936 - Avoid logging a NULL string pointer when loading fallback
10937 directory information. Fixes bug 19947; bugfix on 0.2.4.7-alpha
10938 and 0.2.8.1-alpha. Report and patch by "rubiate".
10941 Changes in version 0.2.9.1-alpha - 2016-08-08
10942 Tor 0.2.9.1-alpha is the first alpha release in the 0.2.9 development
10943 series. It improves our support for hardened builds and compiler
10944 warnings, deploys some critical infrastructure for improvements to
10945 hidden services, includes a new timing backend that we hope to use for
10946 better support for traffic padding, makes it easier for programmers to
10947 log unexpected events, and contains other small improvements to
10948 security, correctness, and performance.
10950 Below are the changes since 0.2.8.6.
10952 o New system requirements:
10953 - Tor now requires Libevent version 2.0.10-stable or later. Older
10954 versions of Libevent have less efficient backends for several
10955 platforms, and lack the DNS code that we use for our server-side
10956 DNS support. This implements ticket 19554.
10957 - Tor now requires zlib version 1.2 or later, for security,
10958 efficiency, and (eventually) gzip support. (Back when we started,
10959 zlib 1.1 and zlib 1.0 were still found in the wild. 1.2 was
10960 released in 2003. We recommend the latest version.)
10962 o Major features (build, hardening):
10963 - Tor now builds with -ftrapv by default on compilers that support
10964 it. This option detects signed integer overflow (which C forbids),
10965 and turns it into a hard-failure. We do not apply this option to
10966 code that needs to run in constant time to avoid side-channels;
10967 instead, we use -fwrapv in that code. Closes ticket 17983.
10968 - When --enable-expensive-hardening is selected, stop applying the
10969 clang/gcc sanitizers to code that needs to run in constant time.
10970 Although we are aware of no introduced side-channels, we are not
10971 able to prove that there are none. Related to ticket 17983.
10973 o Major features (compilation):
10974 - Our big list of extra GCC warnings is now enabled by default when
10975 building with GCC (or with anything like Clang that claims to be
10976 GCC-compatible). To make all warnings into fatal compilation
10977 errors, pass --enable-fatal-warnings to configure. Closes
10979 - Use the Autoconf macro AC_USE_SYSTEM_EXTENSIONS to automatically
10980 turn on C and POSIX extensions. (Previously, we attempted to do
10981 this on an ad hoc basis.) Closes ticket 19139.
10983 o Major features (directory authorities, hidden services):
10984 - Directory authorities can now perform the shared randomness
10985 protocol specified by proposal 250. Using this protocol, directory
10986 authorities generate a global fresh random value every day. In the
10987 future, this value will be used by hidden services to select
10988 HSDirs. This release implements the directory authority feature;
10989 the hidden service side will be implemented in the future as part
10990 of proposal 224. Resolves ticket 16943; implements proposal 250.
10992 o Major features (downloading, random exponential backoff):
10993 - When we fail to download an object from a directory service, wait
10994 for an (exponentially increasing) randomized amount of time before
10995 retrying, rather than a fixed interval as we did before. This
10996 prevents a group of Tor instances from becoming too synchronized,
10997 or a single Tor instance from becoming too predictable, in its
10998 download schedule. Closes ticket 15942.
11000 o Major bugfixes (exit policies):
11001 - Avoid disclosing exit outbound bind addresses, configured port
11002 bind addresses, and local interface addresses in relay descriptors
11003 by default under ExitPolicyRejectPrivate. Instead, only reject
11004 these (otherwise unlisted) addresses if
11005 ExitPolicyRejectLocalInterfaces is set. Fixes bug 18456; bugfix on
11006 0.2.7.2-alpha. Patch by teor.
11008 o Major bugfixes (hidden service client):
11009 - Allow Tor clients with appropriate controllers to work with
11010 FetchHidServDescriptors set to 0. Previously, this option also
11011 disabled descriptor cache lookup, thus breaking hidden services
11012 entirely. Fixes bug 18704; bugfix on 0.2.0.20-rc. Patch by "twim".
11014 o Minor features (build, hardening):
11015 - Detect and work around a libclang_rt problem that would prevent
11016 clang from finding __mulodi4() on some 32-bit platforms, and thus
11017 keep -ftrapv from linking on those systems. Closes ticket 19079.
11018 - When building on a system without runtime support for the runtime
11019 hardening options, try to log a useful warning at configuration
11020 time, rather than an incomprehensible warning at link time. If
11021 expensive hardening was requested, this warning becomes an error.
11022 Closes ticket 18895.
11024 o Minor features (code safety):
11025 - In our integer-parsing functions, ensure that maxiumum value we
11026 give is no smaller than the minimum value. Closes ticket 19063;
11029 o Minor features (controller):
11030 - Implement new GETINFO queries for all downloads that use
11031 download_status_t to schedule retries. This allows controllers to
11032 examine the schedule for pending downloads. Closes ticket 19323.
11033 - Allow controllers to configure basic client authorization on
11034 hidden services when they create them with the ADD_ONION control
11035 command. Implements ticket 15588. Patch by "special".
11036 - Fire a STATUS_SERVER controller event whenever the hibernation
11037 status changes between "awake"/"soft"/"hard". Closes ticket 18685.
11039 o Minor features (directory authority):
11040 - Directory authorities now only give the Guard flag to a relay if
11041 they are also giving it the Stable flag. This change allows us to
11042 simplify path selection for clients. It should have minimal effect
11043 in practice, since >99% of Guards already have the Stable flag.
11044 Implements ticket 18624.
11045 - Directory authorities now write their v3-status-votes file out to
11046 disk earlier in the consensus process, so we have a record of the
11047 votes even if we abort the consensus process. Resolves
11050 o Minor features (hidden service):
11051 - Stop being so strict about the payload length of "rendezvous1"
11052 cells. We used to be locked in to the "TAP" handshake length, and
11053 now we can handle better handshakes like "ntor". Resolves
11056 o Minor features (infrastructure, time):
11057 - Tor now uses the operating system's monotonic timers (where
11058 available) for internal fine-grained timing. Previously we would
11059 look at the system clock, and then attempt to compensate for the
11060 clock running backwards. Closes ticket 18908.
11061 - Tor now includes an improved timer backend, so that we can
11062 efficiently support tens or hundreds of thousands of concurrent
11063 timers, as will be needed for some of our planned anti-traffic-
11064 analysis work. This code is based on William Ahern's "timeout.c"
11065 project, which implements a "tickless hierarchical timing wheel".
11066 Closes ticket 18365.
11068 o Minor features (logging):
11069 - Provide a more useful warning message when configured with an
11070 invalid Nickname. Closes ticket 18300; patch from "icanhasaccount".
11071 - When dumping unparseable router descriptors, optionally store them
11072 in separate files, named by digest, up to a configurable size
11073 limit. You can change the size limit by setting the
11074 MaxUnparseableDescSizeToLog option, and disable this feature by
11075 setting that option to 0. Closes ticket 18322.
11076 - Add a set of macros to check nonfatal assertions, for internal
11077 use. Migrating more of our checks to these should help us avoid
11078 needless crash bugs. Closes ticket 18613.
11080 o Minor features (performance):
11081 - Changer the "optimistic data" extension from "off by default" to
11082 "on by default". The default was ordinarily overridden by a
11083 consensus option, but when clients were bootstrapping for the
11084 first time, they would not have a consensus to get the option
11085 from. Changing this default When fetching a consensus for the
11086 first time, use optimistic data. This saves a round-trip during
11087 startup. Closes ticket 18815.
11089 o Minor features (relay, usability):
11090 - When the directory authorities refuse a bad relay's descriptor,
11091 encourage the relay operator to contact us. Many relay operators
11092 won't notice this line in their logs, but it's a win if even a few
11093 learn why we don't like what their relay was doing. Resolves
11096 o Minor features (testing):
11097 - Let backtrace tests work correctly under AddressSanitizer. Fixes
11098 part of bug 18934; bugfix on 0.2.5.2-alpha.
11099 - Move the test-network.sh script to chutney, and modify tor's test-
11100 network.sh to call the (newer) chutney version when available.
11101 Resolves ticket 19116. Patch by teor.
11102 - Use the lcov convention for marking lines as unreachable, so that
11103 we don't count them when we're generating test coverage data.
11104 Update our coverage tools to understand this convention. Closes
11107 o Minor bugfixes (bootstrap):
11108 - Remember the directory we fetched the consensus or previous
11109 certificates from, and use it to fetch future authority
11110 certificates. This change improves bootstrapping performance.
11111 Fixes bug 18963; bugfix on 0.2.8.1-alpha.
11113 o Minor bugfixes (build):
11114 - The test-stem and test-network makefile targets now depend only on
11115 the tor binary that they are testing. Previously, they depended on
11116 "make all". Fixes bug 18240; bugfix on 0.2.8.2-alpha. Based on a
11117 patch from "cypherpunks".
11119 o Minor bugfixes (circuits):
11120 - Make sure extend_info_from_router() is only called on servers.
11121 Fixes bug 19639; bugfix on 0.2.8.1-alpha.
11123 o Minor bugfixes (compilation):
11124 - When building with Clang, use a full set of GCC warnings.
11125 (Previously, we included only a subset, because of the way we
11126 detected them.) Fixes bug 19216; bugfix on 0.2.0.1-alpha.
11128 o Minor bugfixes (directory authority):
11129 - Authorities now sort the "package" lines in their votes, for ease
11130 of debugging. (They are already sorted in consensus documents.)
11131 Fixes bug 18840; bugfix on 0.2.6.3-alpha.
11132 - When parsing a detached signature, make sure we use the length of
11133 the digest algorithm instead of an hardcoded DIGEST256_LEN in
11134 order to avoid comparing bytes out-of-bounds with a smaller digest
11135 length such as SHA1. Fixes bug 19066; bugfix on 0.2.2.6-alpha.
11137 o Minor bugfixes (documentation):
11138 - Document the --passphrase-fd option in the tor manpage. Fixes bug
11139 19504; bugfix on 0.2.7.3-rc.
11140 - Fix the description of the --passphrase-fd option in the
11141 tor-gencert manpage. The option is used to pass the number of a
11142 file descriptor to read the passphrase from, not to read the file
11143 descriptor from. Fixes bug 19505; bugfix on 0.2.0.20-alpha.
11145 o Minor bugfixes (ephemeral hidden service):
11146 - When deleting an ephemeral hidden service, close its intro points
11147 even if they are not completely open. Fixes bug 18604; bugfix
11150 o Minor bugfixes (guard selection):
11151 - Use a single entry guard even if the NumEntryGuards consensus
11152 parameter is not provided. Fixes bug 17688; bugfix
11154 - Don't mark guards as unreachable if connection_connect() fails.
11155 That function fails for local reasons, so it shouldn't reveal
11156 anything about the status of the guard. Fixes bug 14334; bugfix
11159 o Minor bugfixes (hidden service client):
11160 - Increase the minimum number of internal circuits we preemptively
11161 build from 2 to 3, so a circuit is available when a client
11162 connects to another onion service. Fixes bug 13239; bugfix
11165 o Minor bugfixes (logging):
11166 - When logging a directory ownership mismatch, log the owning
11167 username correctly. Fixes bug 19578; bugfix on 0.2.2.29-beta.
11169 o Minor bugfixes (memory leaks):
11170 - Fix a small, uncommon memory leak that could occur when reading a
11171 truncated ed25519 key file. Fixes bug 18956; bugfix
11174 o Minor bugfixes (testing):
11175 - Allow clients to retry HSDirs much faster in test networks. Fixes
11176 bug 19702; bugfix on 0.2.7.1-alpha. Patch by teor.
11177 - Disable ASAN's detection of segmentation faults while running
11178 test_bt.sh, so that we can make sure that our own backtrace
11179 generation code works. Fixes another aspect of bug 18934; bugfix
11180 on 0.2.5.2-alpha. Patch from "cypherpunks".
11181 - Fix the test-network-all target on out-of-tree builds by using the
11182 correct path to the test driver script. Fixes bug 19421; bugfix
11185 o Minor bugfixes (time):
11186 - Improve overflow checks in tv_udiff and tv_mdiff. Fixes bug 19483;
11187 bugfix on all released tor versions.
11188 - When computing the difference between two times in milliseconds,
11189 we now round to the nearest millisecond correctly. Previously, we
11190 could sometimes round in the wrong direction. Fixes bug 19428;
11191 bugfix on 0.2.2.2-alpha.
11193 o Minor bugfixes (user interface):
11194 - Display a more accurate number of suppressed messages in the log
11195 rate-limiter. Previously, there was a potential integer overflow
11196 in the counter. Now, if the number of messages hits a maximum, the
11197 rate-limiter doesn't count any further. Fixes bug 19435; bugfix
11199 - Fix a typo in the passphrase prompt for the ed25519 identity key.
11200 Fixes bug 19503; bugfix on 0.2.7.2-alpha.
11202 o Code simplification and refactoring:
11203 - Remove redundant declarations of the MIN macro. Closes
11205 - Rename tor_dup_addr() to tor_addr_to_str_dup() to avoid confusion.
11206 Closes ticket 18462; patch from "icanhasaccount".
11207 - Split the 600-line directory_handle_command_get function into
11208 separate functions for different URL types. Closes ticket 16698.
11211 - Fix spelling of "--enable-tor2web-mode" in the manpage. Closes
11212 ticket 19153. Patch from "U+039b".
11214 o Removed features:
11215 - Remove support for "GET /tor/bytes.txt" DirPort request, and
11216 "GETINFO dir-usage" controller request, which were only available
11217 via a compile-time option in Tor anyway. Feature was added in
11218 0.2.2.1-alpha. Resolves ticket 19035.
11219 - There is no longer a compile-time option to disable support for
11220 TransPort. (If you don't want TransPort; just don't use it.) Patch
11221 from "U+039b". Closes ticket 19449.
11224 - Run more workqueue tests as part of "make check". These had
11225 previously been implemented, but you needed to know special
11226 command-line options to enable them.
11227 - We now have unit tests for our code to reject zlib "compression
11228 bombs". (Fortunately, the code works fine.)
11231 Changes in version 0.2.8.6 - 2016-08-02
11233 Tor 0.2.8.6 is the first stable version of the Tor 0.2.8 series.
11235 The Tor 0.2.8 series improves client bootstrapping performance,
11236 completes the authority-side implementation of improved identity
11237 keys for relays, and includes numerous bugfixes and performance
11238 improvements throughout the program. This release continues to
11239 improve the coverage of Tor's test suite. For a full list of
11240 changes since Tor 0.2.7, see the ReleaseNotes file.
11242 Changes since 0.2.8.5-rc:
11244 o Minor features (geoip):
11245 - Update geoip and geoip6 to the July 6 2016 Maxmind GeoLite2
11248 o Minor bugfixes (compilation):
11249 - Fix a compilation warning in the unit tests on systems where char
11250 is signed. Fixes bug 19682; bugfix on 0.2.8.1-alpha.
11252 o Minor bugfixes (fallback directories):
11253 - Remove 1 fallback that was on the hardcoded list, then opted-out,
11254 leaving 89 of the 100 fallbacks originally introduced in Tor
11255 0.2.8.2-alpha in March 2016. Closes ticket 19782; patch by teor.
11257 o Minor bugfixes (Linux seccomp2 sandbox):
11258 - Allow more syscalls when running with "Sandbox 1" enabled:
11259 sysinfo, getsockopt(SO_SNDBUF), and setsockopt(SO_SNDBUFFORCE). On
11260 some systems, these are required for Tor to start. Fixes bug
11261 18397; bugfix on 0.2.5.1-alpha. Patch from Daniel Pinto.
11262 - Allow IPPROTO_UDP datagram sockets when running with "Sandbox 1",
11263 so that get_interface_address6_via_udp_socket_hack() can work.
11264 Fixes bug 19660; bugfix on 0.2.5.1-alpha.
11267 Changes in version 0.2.8.5-rc - 2016-07-07
11268 Tor 0.2.8.5-rc is the second release candidate in the Tor 0.2.8
11269 series. If we find no new bugs or regressions here, the first stable
11270 0.2.8 release will be identical to it. It has a few small bugfixes
11271 against previous versions.
11273 o Directory authority changes:
11274 - Urras is no longer a directory authority. Closes ticket 19271.
11276 o Major bugfixes (heartbeat):
11277 - Fix a regression that would crash Tor when the periodic
11278 "heartbeat" log messages were disabled. Fixes bug 19454; bugfix on
11279 0.2.8.1-alpha. Reported by "kubaku".
11281 o Minor features (build):
11282 - Tor now again builds with the recent OpenSSL 1.1 development
11283 branch (tested against 1.1.0-pre6-dev). Closes ticket 19499.
11284 - When building manual pages, set the timezone to "UTC", so that the
11285 output is reproducible. Fixes bug 19558; bugfix on 0.2.2.9-alpha.
11286 Patch from intrigeri.
11288 o Minor bugfixes (fallback directory selection):
11289 - Avoid errors during fallback selection if there are no eligible
11290 fallbacks. Fixes bug 19480; bugfix on 0.2.8.3-alpha. Patch
11293 o Minor bugfixes (IPv6, microdescriptors):
11294 - Don't check node addresses when we only have a routerstatus. This
11295 allows IPv6-only clients to bootstrap by fetching microdescriptors
11296 from fallback directory mirrors. (The microdescriptor consensus
11297 has no IPv6 addresses in it.) Fixes bug 19608; bugfix
11300 o Minor bugfixes (logging):
11301 - Reduce pointlessly verbose log messages when directory servers
11302 can't be found. Fixes bug 18849; bugfix on 0.2.8.3-alpha and
11303 0.2.8.1-alpha. Patch by teor.
11304 - When a fallback directory changes its fingerprint from the hard-
11305 coded fingerprint, log a less severe, more explanatory log
11306 message. Fixes bug 18812; bugfix on 0.2.8.1-alpha. Patch by teor.
11308 o Minor bugfixes (Linux seccomp2 sandboxing):
11309 - Allow statistics to be written to disk when "Sandbox 1" is
11310 enabled. Fixes bugs 19556 and 19957; bugfix on 0.2.5.1-alpha and
11311 0.2.6.1-alpha respectively.
11313 o Minor bugfixes (user interface):
11314 - Remove a warning message "Service [scrubbed] not found after
11315 descriptor upload". This message appears when one uses HSPOST
11316 control command to upload a service descriptor. Since there is
11317 only a descriptor and no service, showing this message is
11318 pointless and confusing. Fixes bug 19464; bugfix on 0.2.7.2-alpha.
11320 o Fallback directory list:
11321 - Add a comment to the generated fallback directory list that
11322 explains how to comment out unsuitable fallbacks in a way that's
11323 compatible with the stem fallback parser.
11324 - Update fallback whitelist and blacklist based on relay operator
11325 emails. Blacklist unsuitable (non-working, over-volatile)
11326 fallbacks. Resolves ticket 19071. Patch by teor.
11327 - Remove 10 unsuitable fallbacks, leaving 90 of the 100 fallbacks
11328 originally introduced in Tor 0.2.8.2-alpha in March 2016. Closes
11329 ticket 19071; patch by teor.
11332 Changes in version 0.2.8.4-rc - 2016-06-15
11333 Tor 0.2.8.4-rc is the first release candidate in the Tor 0.2.8 series.
11334 If we find no new bugs or regressions here, the first stable 0.2.8
11335 release will be identical to it. It has a few small bugfixes against
11338 o Major bugfixes (user interface):
11339 - Correctly give a warning in the cases where a relay is specified
11340 by nickname, and one such relay is found, but it is not officially
11341 Named. Fixes bug 19203; bugfix on 0.2.3.1-alpha.
11343 o Minor features (build):
11344 - Tor now builds once again with the recent OpenSSL 1.1 development
11345 branch (tested against 1.1.0-pre5 and 1.1.0-pre6-dev).
11347 o Minor features (geoip):
11348 - Update geoip and geoip6 to the June 7 2016 Maxmind GeoLite2
11351 o Minor bugfixes (compilation):
11352 - Cause the unit tests to compile correctly on mingw64 versions that
11353 lack sscanf. Fixes bug 19213; bugfix on 0.2.7.1-alpha.
11355 o Minor bugfixes (downloading):
11356 - Predict more correctly whether we'll be downloading over HTTP when
11357 we determine the maximum length of a URL. This should avoid a
11358 "BUG" warning about the Squid HTTP proxy and its URL limits. Fixes
11362 Changes in version 0.2.8.3-alpha - 2016-05-26
11363 Tor 0.2.8.3-alpha resolves several bugs, most of them introduced over
11364 the course of the 0.2.8 development cycle. It improves the behavior of
11365 directory clients, fixes several crash bugs, fixes a gap in compiler
11366 hardening, and allows the full integration test suite to run on
11369 o Major bugfixes (security, client, DNS proxy):
11370 - Stop a crash that could occur when a client running with DNSPort
11371 received a query with multiple address types, and the first
11372 address type was not supported. Found and fixed by Scott Dial.
11373 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
11375 o Major bugfixes (security, compilation):
11376 - Correctly detect compiler flags on systems where _FORTIFY_SOURCE
11377 is predefined. Previously, our use of -D_FORTIFY_SOURCE would
11378 cause a compiler warning, thereby making other checks fail, and
11379 needlessly disabling compiler-hardening support. Fixes one case of
11380 bug 18841; bugfix on 0.2.3.17-beta. Patch from "trudokal".
11382 o Major bugfixes (security, directory authorities):
11383 - Fix a crash and out-of-bounds write during authority voting, when
11384 the list of relays includes duplicate ed25519 identity keys. Fixes
11385 bug 19032; bugfix on 0.2.8.2-alpha.
11387 o Major bugfixes (client, bootstrapping):
11388 - Check if bootstrap consensus downloads are still needed when the
11389 linked connection attaches. This prevents tor making unnecessary
11390 begindir-style connections, which are the only directory
11391 connections tor clients make since the fix for 18483 was merged.
11392 - Fix some edge cases where consensus download connections may not
11393 have been closed, even though they were not needed. Related to fix
11395 - Make relays retry consensus downloads the correct number of times,
11396 rather than the more aggressive client retry count. Fixes part of
11398 - Stop downloading consensuses when we have a consensus, even if we
11399 don't have all the certificates for it yet. Fixes bug 18809;
11400 bugfix on 0.2.8.1-alpha. Patches by arma and teor.
11402 o Major bugfixes (directory mirrors):
11403 - Decide whether to advertise begindir support in the the same way
11404 we decide whether to advertise our DirPort. Allowing these
11405 decisions to become out-of-sync led to surprising behavior like
11406 advertising begindir support when hibernation made us not
11407 advertise a DirPort. Resolves bug 18616; bugfix on 0.2.8.1-alpha.
11410 o Major bugfixes (IPv6 bridges, client):
11411 - Actually use IPv6 addresses when selecting directory addresses for
11412 IPv6 bridges. Fixes bug 18921; bugfix on 0.2.8.1-alpha. Patch
11415 o Major bugfixes (key management):
11416 - If OpenSSL fails to generate an RSA key, do not retain a dangling
11417 pointer to the previous (uninitialized) key value. The impact here
11418 should be limited to a difficult-to-trigger crash, if OpenSSL is
11419 running an engine that makes key generation failures possible, or
11420 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
11421 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
11424 o Major bugfixes (testing):
11425 - Fix a bug that would block 'make test-network-all' on systems where
11426 IPv6 packets were lost. Fixes bug 19008; bugfix on 0.2.7.3-rc.
11427 - Avoid "WSANOTINITIALISED" warnings in the unit tests. Fixes bug 18668;
11428 bugfix on 0.2.8.1-alpha.
11430 o Minor features (clients):
11431 - Make clients, onion services, and bridge relays always use an
11432 encrypted begindir connection for directory requests. Resolves
11433 ticket 18483. Patch by "teor".
11435 o Minor features (fallback directory mirrors):
11436 - Give each fallback the same weight for client selection; restrict
11437 fallbacks to one per operator; report fallback directory detail
11438 changes when rebuilding list; add new fallback directory mirrors
11439 to the whitelist; and many other minor simplifications and fixes.
11440 Closes tasks 17905, 18749, bug 18689, and fixes part of bug 18812 on
11441 0.2.8.1-alpha; patch by "teor".
11442 - Replace the 21 fallbacks generated in January 2016 and included in
11443 Tor 0.2.8.1-alpha, with a list of 100 fallbacks generated in March
11444 2016. Closes task 17158; patch by "teor".
11446 o Minor features (geoip):
11447 - Update geoip and geoip6 to the May 4 2016 Maxmind GeoLite2
11450 o Minor bugfixes (assert, portability):
11451 - Fix an assertion failure in memarea.c on systems where "long" is
11452 shorter than the size of a pointer. Fixes bug 18716; bugfix
11455 o Minor bugfixes (bootstrap):
11456 - Consistently use the consensus download schedule for authority
11457 certificates. Fixes bug 18816; bugfix on 0.2.4.13-alpha.
11459 o Minor bugfixes (build):
11460 - Remove a pair of redundant AM_CONDITIONAL declarations from
11461 configure.ac. Fixes one final case of bug 17744; bugfix
11463 - Resolve warnings when building on systems that are concerned with
11464 signed char. Fixes bug 18728; bugfix on 0.2.7.2-alpha
11466 - When libscrypt.h is found, but no libscrypt library can be linked,
11467 treat libscrypt as absent. Fixes bug 19161; bugfix
11470 o Minor bugfixes (client):
11471 - Turn all TestingClientBootstrap* into non-testing torrc options.
11472 This changes simply renames them by removing "Testing" in front of
11473 them and they do not require TestingTorNetwork to be enabled
11474 anymore. Fixes bug 18481; bugfix on 0.2.8.1-alpha.
11475 - Make directory node selection more reliable, mainly for IPv6-only
11476 clients and clients with few reachable addresses. Fixes bug 18929;
11477 bugfix on 0.2.8.1-alpha. Patch by "teor".
11479 o Minor bugfixes (controller, microdescriptors):
11480 - Make GETINFO dir/status-vote/current/consensus conform to the
11481 control specification by returning "551 Could not open cached
11482 consensus..." when not caching consensuses. Fixes bug 18920;
11483 bugfix on 0.2.2.6-alpha.
11485 o Minor bugfixes (crypto, portability):
11486 - The SHA3 and SHAKE routines now produce the correct output on Big
11487 Endian systems. No code calls either algorithm yet, so this is
11488 primarily a build fix. Fixes bug 18943; bugfix on 0.2.8.1-alpha.
11489 - Tor now builds again with the recent OpenSSL 1.1 development
11490 branch (tested against 1.1.0-pre4 and 1.1.0-pre5-dev). Closes
11493 o Minor bugfixes (directories):
11494 - When fetching extrainfo documents, compare their SHA256 digests
11495 and Ed25519 signing key certificates with the routerinfo that led
11496 us to fetch them, rather than with the most recent routerinfo.
11497 Otherwise we generate many spurious warnings about mismatches.
11498 Fixes bug 17150; bugfix on 0.2.7.2-alpha.
11500 o Minor bugfixes (logging):
11501 - When we can't generate a signing key because OfflineMasterKey is
11502 set, do not imply that we should have been able to load it. Fixes
11503 bug 18133; bugfix on 0.2.7.2-alpha.
11504 - Stop periodic_event_dispatch() from blasting twelve lines per
11505 second at loglevel debug. Fixes bug 18729; fix on 0.2.8.1-alpha.
11506 - When rejecting a misformed INTRODUCE2 cell, only log at
11507 PROTOCOL_WARN severity. Fixes bug 18761; bugfix on 0.2.8.2-alpha.
11509 o Minor bugfixes (pluggable transports):
11510 - Avoid reporting a spurious error when we decide that we don't need
11511 to terminate a pluggable transport because it has already exited.
11512 Fixes bug 18686; bugfix on 0.2.5.5-alpha.
11514 o Minor bugfixes (pointer arithmetic):
11515 - Fix a bug in memarea_alloc() that could have resulted in remote
11516 heap write access, if Tor had ever passed an unchecked size to
11517 memarea_alloc(). Fortunately, all the sizes we pass to
11518 memarea_alloc() are pre-checked to be less than 128 kilobytes.
11519 Fixes bug 19150; bugfix on 0.2.1.1-alpha. Bug found by
11522 o Minor bugfixes (relays):
11523 - Consider more config options when relays decide whether to
11524 regenerate their descriptor. Fixes more of bug 12538; bugfix
11526 - Resolve some edge cases where we might launch an ORPort
11527 reachability check even when DisableNetwork is set. Noticed while
11528 fixing bug 18616; bugfix on 0.2.3.9-alpha.
11530 o Minor bugfixes (statistics):
11531 - We now include consensus downloads via IPv6 in our directory-
11532 request statistics. Fixes bug 18460; bugfix on 0.2.3.14-alpha.
11534 o Minor bugfixes (testing):
11535 - Allow directories in small networks to bootstrap by skipping
11536 DirPort checks when the consensus has no exits. Fixes bug 19003;
11537 bugfix on 0.2.8.1-alpha. Patch by teor.
11538 - Fix a small memory leak that would occur when the
11539 TestingEnableCellStatsEvent option was turned on. Fixes bug 18673;
11540 bugfix on 0.2.5.2-alpha.
11542 o Minor bugfixes (time handling):
11543 - When correcting a corrupt 'struct tm' value, fill in the tm_wday
11544 field. Otherwise, our unit tests crash on Windows. Fixes bug
11545 18977; bugfix on 0.2.2.25-alpha.
11548 - Document the contents of the 'datadir/keys' subdirectory in the
11549 manual page. Closes ticket 17621.
11550 - Stop recommending use of nicknames to identify relays in our
11551 MapAddress documentation. Closes ticket 18312.
11554 Changes in version 0.2.8.2-alpha - 2016-03-28
11555 Tor 0.2.8.2-alpha is the second alpha in its series. It fixes numerous
11556 bugs in earlier versions of Tor, including some that prevented
11557 authorities using Tor 0.2.7.x from running correctly. IPv6 and
11558 directory support should also be much improved.
11560 o New system requirements:
11561 - Tor no longer supports versions of OpenSSL with a broken
11562 implementation of counter mode. (This bug was present in OpenSSL
11563 1.0.0, and was fixed in OpenSSL 1.0.0a.) Tor still detects, but no
11564 longer runs with, these versions.
11565 - Tor no longer attempts to support platforms where the "time_t"
11566 type is unsigned. (To the best of our knowledge, only OpenVMS does
11567 this, and Tor has never actually built on OpenVMS.) Closes
11569 - Tor now uses Autoconf version 2.63 or later, and Automake 1.11 or
11570 later (released in 2008 and 2009 respectively). If you are
11571 building Tor from the git repository instead of from the source
11572 distribution, and your tools are older than this, you will need to
11573 upgrade. Closes ticket 17732.
11575 o Major bugfixes (security, pointers):
11576 - Avoid a difficult-to-trigger heap corruption attack when extending
11577 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
11578 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
11579 Reported by Guido Vranken.
11581 o Major bugfixes (bridges, pluggable transports):
11582 - Modify the check for OR connections to private addresses. Allow
11583 bridges on private addresses, including pluggable transports that
11584 ignore the (potentially private) address in the bridge line. Fixes
11585 bug 18517; bugfix on 0.2.8.1-alpha. Reported by gk, patch by teor.
11587 o Major bugfixes (compilation):
11588 - Repair hardened builds under the clang compiler. Previously, our
11589 use of _FORTIFY_SOURCE would conflict with clang's address
11590 sanitizer. Fixes bug 14821; bugfix on 0.2.5.4-alpha.
11592 o Major bugfixes (crash on shutdown):
11593 - Correctly handle detaching circuits from muxes when shutting down.
11594 Fixes bug 18116; bugfix on 0.2.8.1-alpha.
11595 - Fix an assert-on-exit bug related to counting memory usage in
11596 rephist.c. Fixes bug 18651; bugfix on 0.2.8.1-alpha.
11598 o Major bugfixes (crash on startup):
11599 - Fix a segfault during startup: If a Unix domain socket was
11600 configured as listener (such as a ControlSocket or a SocksPort
11601 "unix:" socket), and tor was started as root but not configured to
11602 switch to another user, tor would segfault while trying to string
11603 compare a NULL value. Fixes bug 18261; bugfix on 0.2.8.1-alpha.
11606 o Major bugfixes (dns proxy mode, crash):
11607 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
11608 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
11610 o Major bugfixes (relays, bridge clients):
11611 - Ensure relays always allow IPv4 OR and Dir connections. Ensure
11612 bridge clients use the address configured in the bridge line.
11613 Fixes bug 18348; bugfix on 0.2.8.1-alpha. Reported by sysrqb,
11616 o Major bugfixes (voting):
11617 - Actually enable support for authorities to match routers by their
11618 Ed25519 identities. Previously, the code had been written, but
11619 some debugging code that had accidentally been left in the
11620 codebase made it stay turned off. Fixes bug 17702; bugfix
11622 - When collating votes by Ed25519 identities, authorities now
11623 include a "NoEdConsensus" flag if the ed25519 value (or lack
11624 thereof) for a server does not reflect the majority consensus.
11625 Related to bug 17668; bugfix on 0.2.7.2-alpha.
11626 - When generating a vote with keypinning disabled, never include two
11627 entries for the same ed25519 identity. This bug was causing
11628 authorities to generate votes that they could not parse when a
11629 router violated key pinning by changing its RSA identity but
11630 keeping its Ed25519 identity. Fixes bug 17668; fixes part of bug
11631 18318. Bugfix on 0.2.7.2-alpha.
11633 o Minor features (security, win32):
11634 - Set SO_EXCLUSIVEADDRUSE on Win32 to avoid a local port-stealing
11635 attack. Fixes bug 18123; bugfix on all tor versions. Patch
11638 o Minor features (bug-resistance):
11639 - Make Tor survive errors involving connections without a
11640 corresponding event object. Previously we'd fail with an
11641 assertion; now we produce a log message. Related to bug 16248.
11643 o Minor features (build):
11644 - Detect systems with FreeBSD-derived kernels (such as GNU/kFreeBSD)
11645 as having possible IPFW support. Closes ticket 18448. Patch from
11646 Steven Chamberlain.
11648 o Minor features (code hardening):
11649 - Use tor_snprintf() and tor_vsnprintf() even in external and low-
11650 level code, to harden against accidental failures to NUL-
11651 terminate. Part of ticket 17852. Patch from jsturgix. Found
11654 o Minor features (crypto):
11655 - Validate the hard-coded Diffie-Hellman parameters and ensure that
11656 p is a safe prime, and g is a suitable generator. Closes
11659 o Minor features (geoip):
11660 - Update geoip and geoip6 to the March 3 2016 Maxmind GeoLite2
11663 o Minor features (hidden service directory):
11664 - Streamline relay-side hsdir handling: when relays consider whether
11665 to accept an uploaded hidden service descriptor, they no longer
11666 check whether they are one of the relays in the network that is
11667 "supposed" to handle that descriptor. Implements ticket 18332.
11669 o Minor features (IPv6):
11670 - Add ClientPreferIPv6DirPort, which is set to 0 by default. If set
11671 to 1, tor prefers IPv6 directory addresses.
11672 - Add ClientUseIPv4, which is set to 1 by default. If set to 0, tor
11673 avoids using IPv4 for client OR and directory connections.
11674 - Try harder to obey the IP version restrictions "ClientUseIPv4 0",
11675 "ClientUseIPv6 0", "ClientPreferIPv6ORPort", and
11676 "ClientPreferIPv6DirPort". Closes ticket 17840; patch by teor.
11678 o Minor features (linux seccomp2 sandbox):
11679 - Reject attempts to change our Address with "Sandbox 1" enabled.
11680 Changing Address with Sandbox turned on would never actually work,
11681 but previously it would fail in strange and confusing ways. Found
11682 while fixing 18548.
11684 o Minor features (robustness):
11685 - Exit immediately with an error message if the code attempts to use
11686 Libevent without having initialized it. This should resolve some
11687 frequently-made mistakes in our unit tests. Closes ticket 18241.
11689 o Minor features (unix domain sockets):
11690 - Add a new per-socket option, RelaxDirModeCheck, to allow creating
11691 Unix domain sockets without checking the permissions on the parent
11692 directory. (Tor checks permissions by default because some
11693 operating systems only check permissions on the parent directory.
11694 However, some operating systems do look at permissions on the
11695 socket, and tor's default check is unneeded.) Closes ticket 18458.
11698 o Minor bugfixes (exit policies, security):
11699 - Refresh an exit relay's exit policy when interface addresses
11700 change. Previously, tor only refreshed the exit policy when the
11701 configured external address changed. Fixes bug 18208; bugfix on
11702 0.2.7.3-rc. Patch by teor.
11704 o Minor bugfixes (security, hidden services):
11705 - Prevent hidden services connecting to client-supplied rendezvous
11706 addresses that are reserved as internal or multicast. Fixes bug
11707 8976; bugfix on 0.2.3.21-rc. Patch by dgoulet and teor.
11709 o Minor bugfixes (build):
11710 - Do not link the unit tests against both the testing and non-
11711 testing versions of the static libraries. Fixes bug 18490; bugfix
11713 - Avoid spurious failures from configure files related to calling
11714 exit(0) in TOR_SEARCH_LIBRARY. Fixes bug 18626; bugfix on
11715 0.2.0.1-alpha. Patch from "cypherpunks".
11716 - Silence spurious clang-scan warnings in the ed25519_donna code by
11717 explicitly initializing some objects. Fixes bug 18384; bugfix on
11718 0.2.7.2-alpha. Patch by teor.
11720 o Minor bugfixes (client, bootstrap):
11721 - Count receipt of new microdescriptors as progress towards
11722 bootstrapping. Previously, with EntryNodes set, Tor might not
11723 successfully repopulate the guard set on bootstrapping. Fixes bug
11724 16825; bugfix on 0.2.3.1-alpha.
11726 o Minor bugfixes (code correctness):
11727 - Update to the latest version of Trunnel, which tries harder to
11728 avoid generating code that can invoke memcpy(p,NULL,0). Bug found
11729 by clang address sanitizer. Fixes bug 18373; bugfix
11732 o Minor bugfixes (configuration):
11733 - Fix a tiny memory leak when parsing a port configuration ending in
11734 ":auto". Fixes bug 18374; bugfix on 0.2.3.3-alpha.
11736 o Minor bugfixes (containers):
11737 - If we somehow attempt to construct a heap with more than
11738 1073741822 elements, avoid an integer overflow when maintaining
11739 the heap property. Fixes bug 18296; bugfix on 0.1.2.1-alpha.
11741 o Minor bugfixes (correctness):
11742 - Fix a bad memory handling bug that would occur if we had queued a
11743 cell on a channel's incoming queue. Fortunately, we can't actually
11744 queue a cell like that as our code is constructed today, but it's
11745 best to avoid this kind of error, even if there isn't any code
11746 that triggers it today. Fixes bug 18570; bugfix on 0.2.4.4-alpha.
11748 o Minor bugfixes (directory):
11749 - When generating a URL for a directory server on an IPv6 address,
11750 wrap the IPv6 address in square brackets. Fixes bug 18051; bugfix
11751 on 0.2.3.9-alpha. Patch from Malek.
11753 o Minor bugfixes (fallback directory mirrors):
11754 - When requesting extrainfo descriptors from a trusted directory
11755 server, check whether it is an authority or a fallback directory
11756 which supports extrainfo descriptors. Fixes bug 18489; bugfix on
11757 0.2.4.7-alpha. Reported by atagar, patch by teor.
11759 o Minor bugfixes (hidden service, client):
11760 - Handle the case where the user makes several fast consecutive
11761 requests to the same .onion address. Previously, the first six
11762 requests would each trigger a descriptor fetch, each picking a
11763 directory (there are 6 overall) and the seventh one would fail
11764 because no directories were left, thereby triggering a close on
11765 all current directory connections asking for the hidden service.
11766 The solution here is to not close the connections if we have
11767 pending directory fetches. Fixes bug 15937; bugfix
11770 o Minor bugfixes (hidden service, control port):
11771 - Add the onion address to the HS_DESC event for the UPLOADED action
11772 both on success or failure. It was previously hardcoded with
11773 UNKNOWN. Fixes bug 16023; bugfix on 0.2.7.2-alpha.
11775 o Minor bugfixes (hidden service, directory):
11776 - Bridges now refuse "rendezvous2" (hidden service descriptor)
11777 publish attempts. Suggested by ticket 18332.
11779 o Minor bugfixes (linux seccomp2 sandbox):
11780 - Allow the setrlimit syscall, and the prlimit and prlimit64
11781 syscalls, which some libc implementations use under the hood.
11782 Fixes bug 15221; bugfix on 0.2.5.1-alpha.
11783 - Avoid a 10-second delay when starting as a client with "Sandbox 1"
11784 enabled and no DNS resolvers configured. This should help TAILS
11785 start up faster. Fixes bug 18548; bugfix on 0.2.5.1-alpha.
11786 - Fix the sandbox's interoperability with unix domain sockets under
11787 setuid. Fixes bug 18253; bugfix on 0.2.8.1-alpha.
11789 o Minor bugfixes (logging):
11790 - When logging information about an unparsable networkstatus vote or
11791 consensus, do not say "vote" when we mean consensus. Fixes bug
11792 18368; bugfix on 0.2.0.8-alpha.
11793 - Scrub service name in "unrecognized service ID" log messages.
11794 Fixes bug 18600; bugfix on 0.2.4.11-alpha.
11795 - Downgrade logs and backtraces about IP versions to info-level.
11796 Only log backtraces once each time tor runs. Assists in diagnosing
11797 bug 18351; bugfix on 0.2.8.1-alpha. Reported by sysrqb and
11798 Christian, patch by teor.
11800 o Minor bugfixes (memory safety):
11801 - Avoid freeing an uninitialized pointer when opening a socket fails
11802 in get_interface_addresses_ioctl(). Fixes bug 18454; bugfix on
11803 0.2.3.11-alpha. Reported by toralf and "cypherpunks", patch
11805 - Correctly duplicate addresses in get_interface_address6_list().
11806 Fixes bug 18454; bugfix on 0.2.8.1-alpha. Reported by toralf,
11807 patch by "cypherpunks".
11808 - Fix a memory leak in tor-gencert. Fixes part of bug 18672; bugfix
11810 - Fix a memory leak in "tor --list-fingerprint". Fixes part of bug
11811 18672; bugfix on 0.2.5.1-alpha.
11813 o Minor bugfixes (private directory):
11814 - Prevent a race condition when creating private directories. Fixes
11815 part of bug 17852; bugfix on 0.0.2pre13. Part of ticket 17852.
11816 Patch from jsturgix. Found with Flawfinder.
11818 o Minor bugfixes (test networks, IPv6):
11819 - Allow internal IPv6 addresses in descriptors in test networks.
11820 Fixes bug 17153; bugfix on 0.2.3.16-alpha. Patch by teor, reported
11823 o Minor bugfixes (testing):
11824 - We no longer disable assertions in the unit tests when coverage is
11825 enabled. Instead, we require you to say --disable-asserts-in-tests
11826 to the configure script if you need assertions disabled in the
11827 unit tests (for example, if you want to perform branch coverage).
11828 Fixes bug 18242; bugfix on 0.2.7.1-alpha.
11830 o Minor bugfixes (time parsing):
11831 - Avoid overflow in tor_timegm when parsing dates in and after 2038
11832 on platforms with 32-bit time_t. Fixes bug 18479; bugfix on
11833 0.0.2pre14. Patch by teor.
11835 o Minor bugfixes (tor-gencert):
11836 - Correctly handle the case where an authority operator enters a
11837 passphrase but sends an EOF before sending a newline. Fixes bug
11838 17443; bugfix on 0.2.0.20-rc. Found by junglefowl.
11840 o Code simplification and refactoring:
11841 - Quote all the string interpolations in configure.ac -- even those
11842 which we are pretty sure can't contain spaces. Closes ticket
11843 17744. Patch from zerosion.
11844 - Remove specialized code for non-inplace AES_CTR. 99% of our AES is
11845 inplace, so there's no need to have a separate implementation for
11846 the non-inplace code. Closes ticket 18258. Patch from Malek.
11847 - Simplify return types for some crypto functions that can't
11848 actually fail. Patch from Hassan Alsibyani. Closes ticket 18259.
11851 - Change build messages to refer to "Fedora" instead of "Fedora
11852 Core", and "dnf" instead of "yum". Closes tickets 18459 and 18426.
11853 Patches from "icanhasaccount" and "cypherpunks".
11855 o Removed features:
11856 - We no longer maintain an internal freelist in memarea.c.
11857 Allocators should be good enough to make this code unnecessary,
11858 and it's doubtful that it ever had any performance benefit.
11861 - Fix several warnings from clang's address sanitizer produced in
11863 - Treat backtrace test failures as expected on FreeBSD until we
11864 solve bug 17808. Closes ticket 18204.
11867 Changes in version 0.2.8.1-alpha - 2016-02-04
11868 Tor 0.2.8.1-alpha is the first alpha release in its series. It
11869 includes numerous small features and bugfixes against previous Tor
11870 versions, and numerous small infrastructure improvements. The most
11871 notable features are a set of improvements to the directory subsystem.
11873 o Major features (security, Linux):
11874 - When Tor starts as root on Linux and is told to switch user ID, it
11875 can now retain the capability to bind to low ports. By default,
11876 Tor will do this only when it's switching user ID and some low
11877 ports have been configured. You can change this behavior with the
11878 new option KeepBindCapabilities. Closes ticket 8195.
11880 o Major features (directory system):
11881 - When bootstrapping multiple consensus downloads at a time, use the
11882 first one that starts downloading, and close the rest. This
11883 reduces failures when authorities or fallback directories are slow
11884 or down. Together with the code for feature 15775, this feature
11885 should reduces failures due to fallback churn. Implements ticket
11886 4483. Patch by "teor". Implements IPv4 portions of proposal 210 by
11887 "mikeperry" and "teor".
11888 - Include a trial list of 21 default fallback directories, generated
11889 in January 2016, based on an opt-in survey of suitable relays.
11890 Doing this should make clients bootstrap more quickly and reliably,
11891 and reduce the load on the directory authorities. Closes ticket
11892 15775. Patch by "teor".
11893 Candidates identified using an OnionOO script by "weasel", "teor",
11894 "gsathya", and "karsten".
11895 - Previously only relays that explicitly opened a directory port
11896 (DirPort) accepted directory requests from clients. Now all
11897 relays, with and without a DirPort, accept and serve tunneled
11898 directory requests that they receive through their ORPort. You can
11899 disable this behavior using the new DirCache option. Closes
11902 o Major key updates:
11903 - Update the V3 identity key for the dannenberg directory authority:
11904 it was changed on 18 November 2015. Closes task 17906. Patch
11907 o Minor features (security, clock):
11908 - Warn when the system clock appears to move back in time (when the
11909 state file was last written in the future). Tor doesn't know that
11910 consensuses have expired if the clock is in the past. Patch by
11911 "teor". Implements ticket 17188.
11913 o Minor features (security, exit policies):
11914 - ExitPolicyRejectPrivate now rejects more private addresses by
11915 default. Specifically, it now rejects the relay's outbound bind
11916 addresses (if configured), and the relay's configured port
11917 addresses (such as ORPort and DirPort). Fixes bug 17027; bugfix on
11918 0.2.0.11-alpha. Patch by "teor".
11920 o Minor features (security, memory erasure):
11921 - Set the unused entries in a smartlist to NULL. This helped catch
11922 a (harmless) bug, and shouldn't affect performance too much.
11923 Implements ticket 17026.
11924 - Use SecureMemoryWipe() function to securely clean memory on
11925 Windows. Previously we'd use OpenSSL's OPENSSL_cleanse() function.
11926 Implements feature 17986.
11927 - Use explicit_bzero or memset_s when present. Previously, we'd use
11928 OpenSSL's OPENSSL_cleanse() function. Closes ticket 7419; patches
11929 from <logan@hackers.mu> and <selven@hackers.mu>.
11930 - Make memwipe() do nothing when passed a NULL pointer or buffer of
11931 zero size. Check size argument to memwipe() for underflow. Fixes
11932 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
11935 o Minor features (security, RNG):
11936 - Adjust Tor's use of OpenSSL's RNG APIs so that they absolutely,
11937 positively are not allowed to fail. Previously we depended on
11938 internal details of OpenSSL's behavior. Closes ticket 17686.
11939 - Never use the system entropy output directly for anything besides
11940 seeding the PRNG. When we want to generate important keys, instead
11941 of using system entropy directly, we now hash it with the PRNG
11942 stream. This may help resist certain attacks based on broken OS
11943 entropy implementations. Closes part of ticket 17694.
11944 - Use modern system calls (like getentropy() or getrandom()) to
11945 generate strong entropy on platforms that have them. Closes
11948 o Minor features (accounting):
11949 - Added two modes to the AccountingRule option: One for limiting
11950 only the number of bytes sent ("AccountingRule out"), and one for
11951 limiting only the number of bytes received ("AccountingRule in").
11952 Closes ticket 15989; patch from "unixninja92".
11954 o Minor features (build):
11955 - Since our build process now uses "make distcheck", we no longer
11956 force "make dist" to depend on "make check". Closes ticket 17893;
11957 patch from "cypherpunks."
11958 - Tor now builds successfully with the recent OpenSSL 1.1
11959 development branch, and with the latest LibreSSL. Closes tickets
11960 17549, 17921, and 17984.
11962 o Minor features (controller):
11963 - Adds the FallbackDir entries to 'GETINFO config/defaults'. Closes
11964 tickets 16774 and 17817. Patch by George Tankersley.
11965 - New 'GETINFO hs/service/desc/id/' command to retrieve a hidden
11966 service descriptor from a service's local hidden service
11967 descriptor cache. Closes ticket 14846.
11968 - Add 'GETINFO exit-policy/reject-private/[default,relay]', so
11969 controllers can examine the the reject rules added by
11970 ExitPolicyRejectPrivate. This makes it easier for stem to display
11973 o Minor features (crypto):
11974 - Add SHA512 support to crypto.c. Closes ticket 17663; patch from
11976 - Add SHA3 and SHAKE support to crypto.c. Closes ticket 17783.
11977 - When allocating a digest state object, allocate no more space than
11978 we actually need. Previously, we would allocate as much space as
11979 the state for the largest algorithm would need. This change saves
11980 up to 672 bytes per circuit. Closes ticket 17796.
11981 - Improve performance when hashing non-multiple of 8 sized buffers,
11982 based on Andrew Moon's public domain SipHash-2-4 implementation.
11983 Fixes bug 17544; bugfix on 0.2.5.3-alpha.
11985 o Minor features (directory downloads):
11986 - Wait for busy authorities and fallback directories to become non-
11987 busy when bootstrapping. (A similar change was made in 6c443e987d
11988 for directory caches chosen from the consensus.) Closes ticket
11989 17864; patch by "teor".
11990 - Add UseDefaultFallbackDirs, which enables any hard-coded fallback
11991 directory mirrors. The default is 1; set it to 0 to disable
11992 fallbacks. Implements ticket 17576. Patch by "teor".
11994 o Minor features (geoip):
11995 - Update geoip and geoip6 to the January 5 2016 Maxmind GeoLite2
11998 o Minor features (IPv6):
11999 - Add an argument 'ipv6=address:orport' to the DirAuthority and
12000 FallbackDir torrc options, to specify an IPv6 address for an
12001 authority or fallback directory. Add hard-coded ipv6 addresses for
12002 directory authorities that have them. Closes ticket 17327; patch
12003 from Nick Mathewson and "teor".
12004 - Add address policy assume_action support for IPv6 addresses.
12005 - Limit IPv6 mask bits to 128.
12006 - Warn when comparing against an AF_UNSPEC address in a policy, it's
12007 almost always a bug. Closes ticket 17863; patch by "teor".
12008 - Allow users to configure directory authorities and fallback
12009 directory servers with IPv6 addresses and ORPorts. Resolves
12011 - routerset_parse now accepts IPv6 literal addresses. Fixes bug
12012 17060; bugfix on 0.2.1.3-alpha. Patch by "teor".
12013 - Make tor_ersatz_socketpair work on IPv6-only systems. Fixes bug
12014 17638; bugfix on 0.0.2pre8. Patch by "teor".
12016 o Minor features (logging):
12017 - When logging to syslog, allow a tag to be added to the syslog
12018 identity (the string prepended to every log message). The tag can
12019 be configured with SyslogIdentityTag and defaults to none. Setting
12020 it to "foo" will cause logs to be tagged as "Tor-foo". Closes
12023 o Minor features (portability):
12024 - Use timingsafe_memcmp() where available. Closes ticket 17944;
12025 patch from <logan@hackers.mu>.
12027 o Minor features (relay, address discovery):
12028 - Add a family argument to get_interface_addresses_raw() and
12029 subfunctions to make network interface address interogation more
12030 efficient. Now Tor can specifically ask for IPv4, IPv6 or both
12031 types of interfaces from the operating system. Resolves
12033 - When get_interface_address6_list(.,AF_UNSPEC,.) is called and
12034 fails to enumerate interface addresses using the platform-specific
12035 API, have it rely on the UDP socket fallback technique to try and
12036 find out what IP addresses (both IPv4 and IPv6) our machine has.
12037 Resolves ticket 17951.
12039 o Minor features (replay cache):
12040 - The replay cache now uses SHA256 instead of SHA1. Implements
12041 feature 8961. Patch by "teor", issue reported by "rransom".
12043 o Minor features (unix file permissions):
12044 - Defer creation of Unix sockets until after setuid. This avoids
12045 needing CAP_CHOWN and CAP_FOWNER when using systemd's
12046 CapabilityBoundingSet, or chown and fowner when using SELinux.
12047 Implements part of ticket 17562. Patch from Jamie Nguyen.
12048 - If any directory created by Tor is marked as group readable, the
12049 filesystem group is allowed to be either the default GID or the
12050 root user. Allowing root to read the DataDirectory prevents the
12051 need for CAP_READ_SEARCH when using systemd's
12052 CapabilityBoundingSet, or dac_read_search when using SELinux.
12053 Implements part of ticket 17562. Patch from Jamie Nguyen.
12054 - Introduce a new DataDirectoryGroupReadable option. If it is set to
12055 1, the DataDirectory will be made readable by the default GID.
12056 Implements part of ticket 17562. Patch from Jamie Nguyen.
12058 o Minor bugfixes (accounting):
12059 - The max bandwidth when using 'AccountRule sum' is now correctly
12060 logged. Fixes bug 18024; bugfix on 0.2.6.1-alpha. Patch
12061 from "unixninja92".
12063 o Minor bugfixes (code correctness):
12064 - When closing an entry connection, generate a warning if we should
12065 have sent an end cell for it but we haven't. Fixes bug 17876;
12066 bugfix on 0.2.3.2-alpha.
12067 - Assert that allocated memory held by the reputation code is freed
12068 according to its internal counters. Fixes bug 17753; bugfix
12070 - Assert when the TLS contexts fail to initialize. Fixes bug 17683;
12073 o Minor bugfixes (compilation):
12074 - Mark all object files that include micro-revision.i as depending
12075 on it, so as to make parallel builds more reliable. Fixes bug
12076 17826; bugfix on 0.2.5.1-alpha.
12077 - Don't try to use the pthread_condattr_setclock() function unless
12078 it actually exists. Fixes compilation on NetBSD-6.x. Fixes bug
12079 17819; bugfix on 0.2.6.3-alpha.
12080 - Fix backtrace compilation on FreeBSD. Fixes bug 17827; bugfix
12082 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
12083 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
12084 - Fix search for libevent libraries on OpenBSD (and other systems
12085 that install libevent 1 and libevent 2 in parallel). Fixes bug
12086 16651; bugfix on 0.1.0.7-rc. Patch from "rubiate".
12087 - Isolate environment variables meant for tests from the rest of the
12088 build system. Fixes bug 17818; bugfix on 0.2.7.3-rc.
12089 - Replace usage of 'INLINE' with 'inline'. Fixes bug 17804; bugfix
12091 - Remove config.log only from make distclean, not from make clean.
12092 Fixes bug 17924; bugfix on 0.2.4.1-alpha.
12094 o Minor bugfixes (crypto):
12095 - Check the return value of HMAC() and assert on failure. Fixes bug
12096 17658; bugfix on 0.2.3.6-alpha. Patch by "teor".
12098 o Minor bugfixes (fallback directories):
12099 - Mark fallbacks as "too busy" when they return a 503 response,
12100 rather than just marking authorities. Fixes bug 17572; bugfix on
12101 0.2.4.7-alpha. Patch by "teor".
12103 o Minor bugfixes (IPv6):
12104 - Update the limits in max_dl_per_request for IPv6 address length.
12105 Fixes bug 17573; bugfix on 0.2.1.5-alpha.
12107 o Minor bugfixes (linux seccomp2 sandbox):
12108 - Fix a crash when using offline master ed25519 keys with the Linux
12109 seccomp2 sandbox enabled. Fixes bug 17675; bugfix on 0.2.7.3-rc.
12111 o Minor bugfixes (logging):
12112 - In log messages that include a function name, use __FUNCTION__
12113 instead of __PRETTY_FUNCTION__. In GCC, these are synonymous, but
12114 with clang __PRETTY_FUNCTION__ has extra information we don't
12115 need. Fixes bug 16563; bugfix on 0.0.2pre8. Fix by Tom van
12117 - Remove needless quotes from a log message about unparseable
12118 addresses. Fixes bug 17843; bugfix on 0.2.3.3-alpha.
12120 o Minor bugfixes (portability):
12121 - Remove an #endif from configure.ac so that we correctly detect the
12122 presence of in6_addr.s6_addr32. Fixes bug 17923; bugfix
12125 o Minor bugfixes (relays):
12126 - Check that both the ORPort and DirPort (if present) are reachable
12127 before publishing a relay descriptor. Otherwise, relays publish a
12128 descriptor with DirPort 0 when the DirPort reachability test takes
12129 longer than the ORPort reachability test. Fixes bug 18050; bugfix
12130 on 0.1.0.1-rc. Reported by "starlight", patch by "teor".
12132 o Minor bugfixes (relays, hidden services):
12133 - Refuse connection requests to private OR addresses unless
12134 ExtendAllowPrivateAddresses is set. Previously, tor would connect,
12135 then refuse to send any cells to a private address. Fixes bugs
12136 17674 and 8976; bugfix on 0.2.3.21-rc. Patch by "teor".
12138 o Minor bugfixes (safe logging):
12139 - When logging a malformed hostname received through socks4, scrub
12140 it if SafeLogging says we should. Fixes bug 17419; bugfix
12143 o Minor bugfixes (statistics code):
12144 - Consistently check for overflow in round_*_to_next_multiple_of
12145 functions, and add unit tests with additional and maximal values.
12146 Fixes part of bug 13192; bugfix on 0.2.2.1-alpha.
12147 - Handle edge cases in the laplace functions: avoid division by
12148 zero, avoid taking the log of zero, and silence clang type
12149 conversion warnings using round and trunc. Add unit tests for edge
12150 cases with maximal values. Fixes part of bug 13192; bugfix
12153 o Minor bugfixes (testing):
12154 - The test for log_heartbeat was incorrectly failing in timezones
12155 with non-integer offsets. Instead of comparing the end of the time
12156 string against a constant, compare it to the output of
12157 format_local_iso_time when given the correct input. Fixes bug
12158 18039; bugfix on 0.2.5.4-alpha.
12159 - Make unit tests pass on IPv6-only systems, and systems without
12160 localhost addresses (like some FreeBSD jails). Fixes bug 17632;
12161 bugfix on 0.2.7.3-rc. Patch by "teor".
12162 - Fix a memory leak in the ntor test. Fixes bug 17778; bugfix
12164 - Check the full results of SHA256 and SHA512 digests in the unit
12165 tests. Bugfix on 0.2.2.4-alpha. Patch by "teor".
12167 o Code simplification and refactoring:
12168 - Move logging of redundant policy entries in
12169 policies_parse_exit_policy_internal into its own function. Closes
12170 ticket 17608; patch from "juce".
12171 - Extract the more complicated parts of circuit_mark_for_close()
12172 into a new function that we run periodically before circuits are
12173 freed. This change removes more than half of the functions
12174 currently in the "blob". Closes ticket 17218.
12175 - Clean up a little duplicated code in
12176 crypto_expand_key_material_TAP(). Closes ticket 17587; patch
12178 - Decouple the list of streams waiting to be attached to circuits
12179 from the overall connection list. This change makes it possible to
12180 attach streams quickly while simplifying Tor's callgraph and
12181 avoiding O(N) scans of the entire connection list. Closes
12183 - When a direct directory request fails immediately on launch,
12184 instead of relaunching that request from inside the code that
12185 launches it, instead mark the connection for teardown. This change
12186 simplifies Tor's callback and prevents the directory-request
12187 launching code from invoking itself recursively. Closes
12189 - Remove code for configuring OpenSSL dynamic locks; OpenSSL doesn't
12190 use them. Closes ticket 17926.
12193 - Add a description of the correct use of the '--keygen' command-
12194 line option. Closes ticket 17583; based on text by 's7r'.
12195 - Document the minimum HeartbeatPeriod value. Closes ticket 15638.
12196 - Explain actual minima for BandwidthRate. Closes ticket 16382.
12197 - Fix a minor formatting typo in the manpage. Closes ticket 17791.
12198 - Mention torspec URL in the manpage and point the reader to it
12199 whenever we mention a document that belongs in torspce. Fixes
12202 o Removed features:
12203 - Remove client-side support for connecting to Tor relays running
12204 versions of Tor before 0.2.3.6-alpha. These relays didn't support
12205 the v3 TLS handshake protocol, and are no longer allowed on the
12206 Tor network. Implements the client side of ticket 11150. Based on
12207 patches by Tom van der Woerdt.
12210 - Add unit tests to check for common RNG failure modes, such as
12211 returning all zeroes, identical values, or incrementing values
12212 (OpenSSL's rand_predictable feature). Patch by "teor".
12213 - Log more information when the backtrace tests fail. Closes ticket
12214 17892. Patch from "cypherpunks."
12215 - Always test both ed25519 backends, so that we can be sure that our
12216 batch-open replacement code works. Part of ticket 16794.
12217 - Cover dns_resolve_impl() in dns.c with unit tests. Implements a
12218 portion of ticket 16831.
12219 - More unit tests for compat_libevent.c, procmon.c, tortls.c,
12220 util_format.c, directory.c, and options_validate.c. Closes tickets
12221 17075, 17082, 17084, 17003, and 17076 respectively. Patches from
12223 - Unit tests for directory_handle_command_get. Closes ticket 17004.
12224 Patch from Reinaldo de Souza Jr.
12227 Changes in version 0.2.7.6 - 2015-12-10
12228 Tor version 0.2.7.6 fixes a major bug in entry guard selection, as
12229 well as a minor bug in hidden service reliability.
12231 o Major bugfixes (guard selection):
12232 - Actually look at the Guard flag when selecting a new directory
12233 guard. When we implemented the directory guard design, we
12234 accidentally started treating all relays as if they have the Guard
12235 flag during guard selection, leading to weaker anonymity and worse
12236 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
12239 o Minor features (geoip):
12240 - Update geoip and geoip6 to the December 1 2015 Maxmind GeoLite2
12243 o Minor bugfixes (compilation):
12244 - When checking for net/pfvar.h, include netinet/in.h if possible.
12245 This fixes transparent proxy detection on OpenBSD. Fixes bug
12246 17551; bugfix on 0.1.2.1-alpha. Patch from "rubiate".
12247 - Fix a compilation warning with Clang 3.6: Do not check the
12248 presence of an address which can never be NULL. Fixes bug 17781.
12250 o Minor bugfixes (correctness):
12251 - When displaying an IPv6 exit policy, include the mask bits
12252 correctly even when the number is greater than 31. Fixes bug
12253 16056; bugfix on 0.2.4.7-alpha. Patch from "gturner".
12254 - The wrong list was used when looking up expired intro points in a
12255 rend service object, causing what we think could be reachability
12256 issues for hidden services, and triggering a BUG log. Fixes bug
12257 16702; bugfix on 0.2.7.2-alpha.
12258 - Fix undefined behavior in the tor_cert_checksig function. Fixes
12259 bug 17722; bugfix on 0.2.7.2-alpha.
12262 Changes in version 0.2.7.5 - 2015-11-20
12263 The Tor 0.2.7 release series is dedicated to the memory of Tor user
12264 and privacy advocate Caspar Bowden (1961-2015). Caspar worked
12265 tirelessly to advocate human rights regardless of national borders,
12266 and oppose the encroachments of mass surveillance. He opposed national
12267 exceptionalism, he brought clarity to legal and policy debates, he
12268 understood and predicted the impact of mass surveillance on the world,
12269 and he laid the groundwork for resisting it. While serving on the Tor
12270 Project's board of directors, he brought us his uncompromising focus
12271 on technical excellence in the service of humankind. Caspar was an
12272 inimitable force for good and a wonderful friend. He was kind,
12273 humorous, generous, gallant, and believed we should protect one
12274 another without exception. We honor him here for his ideals, his
12275 efforts, and his accomplishments. Please honor his memory with works
12276 that would make him proud.
12278 Tor 0.2.7.5 is the first stable release in the Tor 0.2.7 series.
12280 The 0.2.7 series adds a more secure identity key type for relays,
12281 improves cryptography performance, resolves several longstanding
12282 hidden-service performance issues, improves controller support for
12283 hidden services, and includes small bugfixes and performance
12284 improvements throughout the program. This release series also includes
12285 more tests than before, and significant simplifications to which parts
12286 of Tor invoke which others.
12288 (This release contains no code changes since 0.2.7.4-rc.)
12291 Changes in version 0.2.7.4-rc - 2015-10-21
12292 Tor 0.2.7.4-rc is the second release candidate in the 0.2.7 series. It
12293 fixes some important memory leaks, and a scary-looking (but mostly
12294 harmless in practice) invalid-read bug. It also has a few small
12295 bugfixes, notably fixes for compilation and portability on different
12296 platforms. If no further significant bounds are found, the next
12297 release will the the official stable release.
12299 o Major bugfixes (security, correctness):
12300 - Fix an error that could cause us to read 4 bytes before the
12301 beginning of an openssl string. This bug could be used to cause
12302 Tor to crash on systems with unusual malloc implementations, or
12303 systems with unusual hardening installed. Fixes bug 17404; bugfix
12306 o Major bugfixes (correctness):
12307 - Fix a use-after-free bug in validate_intro_point_failure(). Fixes
12308 bug 17401; bugfix on 0.2.7.3-rc.
12310 o Major bugfixes (memory leaks):
12311 - Fix a memory leak in ed25519 batch signature checking. Fixes bug
12312 17398; bugfix on 0.2.6.1-alpha.
12313 - Fix a memory leak in rend_cache_failure_entry_free(). Fixes bug
12314 17402; bugfix on 0.2.7.3-rc.
12315 - Fix a memory leak when reading an expired signing key from disk.
12316 Fixes bug 17403; bugfix on 0.2.7.2-rc.
12318 o Minor features (geoIP):
12319 - Update geoip and geoip6 to the October 9 2015 Maxmind GeoLite2
12322 o Minor bugfixes (compilation):
12323 - Repair compilation with the most recent (unreleased, alpha)
12324 vesions of OpenSSL 1.1. Fixes part of ticket 17237.
12325 - Fix an integer overflow warning in test_crypto_slow.c. Fixes bug
12326 17251; bugfix on 0.2.7.2-alpha.
12327 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
12328 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
12330 o Minor bugfixes (portability):
12331 - Use libexecinfo on FreeBSD to enable backtrace support. Fixes
12332 part of bug 17151; bugfix on 0.2.5.2-alpha. Patch from
12335 o Minor bugfixes (sandbox):
12336 - Add the "hidserv-stats" filename to our sandbox filter for the
12337 HiddenServiceStatistics option to work properly. Fixes bug 17354;
12338 bugfix on 0.2.6.2-alpha. Patch from David Goulet.
12340 o Minor bugfixes (testing):
12341 - Add unit tests for get_interface_address* failure cases. Fixes bug
12342 17173; bugfix on 0.2.7.3-rc. Patch by fk/teor.
12343 - Fix breakage when running 'make check' with BSD make. Fixes bug
12344 17154; bugfix on 0.2.7.3-rc. Patch by Marcin Cieślak.
12345 - Make the get_ifaddrs_* unit tests more tolerant of different
12346 network configurations. (Don't assume every test box has an IPv4
12347 address, and don't assume every test box has a non-localhost
12348 address.) Fixes bug 17255; bugfix on 0.2.7.3-rc. Patch by "teor".
12349 - Skip backtrace tests when backtrace support is not compiled in.
12350 Fixes part of bug 17151; bugfix on 0.2.7.1-alpha. Patch from
12354 - Fix capitalization of SOCKS in sample torrc. Closes ticket 15609.
12355 - Note that HiddenServicePorts can take a unix domain socket. Closes
12359 Changes in version 0.2.7.3-rc - 2015-09-25
12360 Tor 0.2.7.3-rc is the first release candidate in the 0.2.7 series. It
12361 contains numerous usability fixes for Ed25519 keys, safeguards against
12362 several misconfiguration problems, significant simplifications to
12363 Tor's callgraph, and numerous bugfixes and small features.
12365 This is the most tested release of Tor to date. The unit tests cover
12366 39.40% of the code, and the integration tests (accessible with "make
12367 test-full-online", requiring stem and chutney and a network
12368 connection) raise the coverage to 64.49%.
12370 o Major features (security, hidden services):
12371 - Hidden services, if using the EntryNodes option, are required to
12372 use more than one EntryNode, in order to avoid a guard discovery
12373 attack. (This would only affect people who had configured hidden
12374 services and manually specified the EntryNodes option with a
12375 single entry-node. The impact was that it would be easy to
12376 remotely identify the guard node used by such a hidden service.
12377 See ticket for more information.) Fixes ticket 14917.
12379 o Major features (Ed25519 keys, keypinning):
12380 - The key-pinning option on directory authorities is now advisory-
12381 only by default. In a future version, or when the AuthDirPinKeys
12382 option is set, pins are enforced again. Disabling key-pinning
12383 seemed like a good idea so that we can survive the fallout of any
12384 usability problems associated with Ed25519 keys. Closes
12387 o Major features (Ed25519 performance):
12388 - Improve the speed of Ed25519 operations and Curve25519 keypair
12389 generation when built targeting 32 bit x86 platforms with SSE2
12390 available. Implements ticket 16535.
12391 - Improve the runtime speed of Ed25519 signature verification by
12392 using Ed25519-donna's batch verification support. Implements
12395 o Major features (performance testing):
12396 - The test-network.sh script now supports performance testing.
12397 Requires corresponding chutney performance testing changes. Patch
12398 by "teor". Closes ticket 14175.
12400 o Major features (relay, Ed25519):
12401 - Significant usability improvements for Ed25519 key management. Log
12402 messages are better, and the code can recover from far more
12403 failure conditions. Thanks to "s7r" for reporting and diagnosing
12405 - Add a new OfflineMasterKey option to tell Tor never to try loading
12406 or generating a secret Ed25519 identity key. You can use this in
12407 combination with tor --keygen to manage offline and/or encrypted
12408 Ed25519 keys. Implements ticket 16944.
12409 - Add a --newpass option to allow changing or removing the
12410 passphrase of an encrypted key with tor --keygen. Implements part
12412 - On receiving a HUP signal, check to see whether the Ed25519
12413 signing key has changed, and reload it if so. Closes ticket 16790.
12415 o Major bugfixes (relay, Ed25519):
12416 - Avoid crashing on 'tor --keygen'. Fixes bug 16679; bugfix on
12417 0.2.7.2-alpha. Reported by "s7r".
12418 - Improve handling of expired signing keys with offline master keys.
12419 Fixes bug 16685; bugfix on 0.2.7.2-alpha. Reported by "s7r".
12421 o Minor features (client-side privacy):
12422 - New KeepAliveIsolateSOCKSAuth option to indefinitely extend circuit
12423 lifespan when IsolateSOCKSAuth and streams with SOCKS
12424 authentication are attached to the circuit. This allows
12425 applications like TorBrowser to manage circuit lifetime on their
12426 own. Implements feature 15482.
12427 - When logging malformed hostnames from SOCKS5 requests, respect
12428 SafeLogging configuration. Fixes bug 16891; bugfix on 0.1.1.16-rc.
12430 o Minor features (compilation):
12431 - Give a warning as early as possible when trying to build with an
12432 unsupported OpenSSL version. Closes ticket 16901.
12433 - Fail during configure if we're trying to build against an OpenSSL
12434 built without ECC support. Fixes bug 17109, bugfix on 0.2.7.1-alpha
12435 which started requiring ECC.
12437 o Minor features (geoip):
12438 - Update geoip and geoip6 to the September 3 2015 Maxmind GeoLite2
12441 o Minor features (hidden services):
12442 - Relays need to have the Fast flag to get the HSDir flag. As this
12443 is being written, we'll go from 2745 HSDirs down to 2342, a ~14%
12444 drop. This change should make some attacks against the hidden
12445 service directory system harder. Fixes ticket 15963.
12446 - Turn on hidden service statistics collection by setting the torrc
12447 option HiddenServiceStatistics to "1" by default. (This keeps
12448 track only of the fraction of traffic used by hidden services, and
12449 the total number of hidden services in existence.) Closes
12451 - Client now uses an introduction point failure cache to know when
12452 to fetch or keep a descriptor in their cache. Previously, failures
12453 were recorded implicitly, but not explicitly remembered. Closes
12456 o Minor features (testing, authorities, documentation):
12457 - New TestingDirAuthVote{Exit,Guard,HSDir}IsStrict flags to
12458 explicitly manage consensus flags in testing networks. Patch by
12459 "robgjansen", modified by "teor". Implements part of ticket 14882.
12461 o Minor bugfixes (security, exit policies):
12462 - ExitPolicyRejectPrivate now also rejects the relay's published
12463 IPv6 address (if any), and any publicly routable IPv4 or IPv6
12464 addresses on any local interfaces. ticket 17027. Patch by "teor".
12465 Fixes bug 17027; bugfix on 0.2.0.11-alpha.
12467 o Minor bug fixes (torrc exit policies):
12468 - In torrc, "accept6 *" and "reject6 *" ExitPolicy lines now only
12469 produce IPv6 wildcard addresses. Previously they would produce
12470 both IPv4 and IPv6 wildcard addresses. Patch by "teor". Fixes part
12471 of bug 16069; bugfix on 0.2.4.7-alpha.
12472 - When parsing torrc ExitPolicies, we now warn for a number of cases
12473 where the user's intent is likely to differ from Tor's actual
12474 behavior. These include: using an IPv4 address with an accept6 or
12475 reject6 line; using "private" on an accept6 or reject6 line; and
12476 including any ExitPolicy lines after accept *:* or reject *:*.
12477 Related to ticket 16069.
12478 - When parsing torrc ExitPolicies, we now issue an info-level
12479 message when expanding an "accept/reject *" line to include both
12480 IPv4 and IPv6 wildcard addresses. Related to ticket 16069.
12481 - In each instance above, usage advice is provided to avoid the
12482 message. Resolves ticket 16069. Patch by "teor". Fixes part of bug
12483 16069; bugfix on 0.2.4.7-alpha.
12485 o Minor bugfixes (authority):
12486 - Don't assign "HSDir" to a router if it isn't Valid and Running.
12487 Fixes bug 16524; bugfix on 0.2.7.2-alpha.
12488 - Downgrade log messages about Ed25519 key issues if they are in old
12489 cached router descriptors. Fixes part of bug 16286; bugfix
12491 - When we find an Ed25519 key issue in a cached descriptor, stop
12492 saying the descriptor was just "uploaded". Fixes another part of
12493 bug 16286; bugfix on 0.2.7.2-alpha.
12495 o Minor bugfixes (control port):
12496 - Repair a warning and a spurious result when getting the maximum
12497 number of file descriptors from the controller. Fixes bug 16697;
12498 bugfix on 0.2.7.2-alpha.
12500 o Minor bugfixes (correctness):
12501 - When calling channel_free_list(), avoid calling smartlist_remove()
12502 while inside a FOREACH loop. This partially reverts commit
12503 17356fe7fd96af where the correct SMARTLIST_DEL_CURRENT was
12504 incorrectly removed. Fixes bug 16924; bugfix on 0.2.4.4-alpha.
12506 o Minor bugfixes (documentation):
12507 - Advise users on how to configure separate IPv4 and IPv6 exit
12508 policies in the manpage and sample torrcs. Related to ticket 16069.
12509 - Fix the usage message of tor-resolve(1) so that it no longer lists
12510 the removed -F option. Fixes bug 16913; bugfix on 0.2.2.28-beta.
12511 - Fix an error in the manual page and comments for
12512 TestingDirAuthVoteHSDir[IsStrict], which suggested that a HSDir
12513 required "ORPort connectivity". While this is true, it is in no
12514 way unique to the HSDir flag. Of all the flags, only HSDirs need a
12515 DirPort configured in order for the authorities to assign that
12516 particular flag. Patch by "teor". Fixed as part of 14882; bugfix
12519 o Minor bugfixes (Ed25519):
12520 - Fix a memory leak when reading router descriptors with expired
12521 Ed25519 certificates. Fixes bug 16539; bugfix on 0.2.7.2-alpha.
12523 o Minor bugfixes (linux seccomp2 sandbox):
12524 - Allow bridge authorities to run correctly under the seccomp2
12525 sandbox. Fixes bug 16964; bugfix on 0.2.5.1-alpha.
12526 - Allow routers with ed25519 keys to run correctly under the
12527 seccomp2 sandbox. Fixes bug 16965; bugfix on 0.2.7.2-alpha.
12529 o Minor bugfixes (open file limit):
12530 - Fix set_max_file_descriptors() to set by default the max open file
12531 limit to the current limit when setrlimit() fails. Fixes bug
12532 16274; bugfix on 0.2.0.10-alpha. Patch by dgoulet.
12534 o Minor bugfixes (portability):
12535 - Try harder to normalize the exit status of the Tor process to the
12536 standard-provided range. Fixes bug 16975; bugfix on every version
12538 - Check correctly for Windows socket errors in the workqueue
12539 backend. Fixes bug 16741; bugfix on 0.2.6.3-alpha.
12540 - Fix the behavior of crypto_rand_time_range() when told to consider
12541 times before 1970. (These times were possible when running in a
12542 simulated network environment where time()'s output starts at
12543 zero.) Fixes bug 16980; bugfix on 0.2.7.1-alpha.
12544 - Restore correct operation of TLS client-cipher detection on
12545 OpenSSL 1.1. Fixes bug 14047; bugfix on 0.2.7.2-alpha.
12547 o Minor bugfixes (relay):
12548 - Ensure that worker threads actually exit when a fatal error or
12549 shutdown is indicated. This fix doesn't currently affect the
12550 behavior of Tor, because Tor workers never indicates fatal error
12551 or shutdown except in the unit tests. Fixes bug 16868; bugfix
12553 - Unblock threads before releasing the work queue mutex to ensure
12554 predictable scheduling behavior. Fixes bug 16644; bugfix
12557 o Code simplification and refactoring:
12558 - Change the function that's called when we need to retry all
12559 downloads so that it only reschedules the downloads to happen
12560 immediately, rather than launching them all at once itself. This
12561 further simplifies Tor's callgraph.
12562 - Move some format-parsing functions out of crypto.c and
12563 crypto_curve25519.c into crypto_format.c and/or util_format.c.
12564 - Move the client-only parts of init_keys() into a separate
12565 function. Closes ticket 16763.
12566 - Simplify the microdesc_free() implementation so that it no longer
12567 appears (to code analysis tools) to potentially invoke a huge
12568 suite of other microdesc functions.
12569 - Simply the control graph further by deferring the inner body of
12570 directory_all_unreachable() into a callback. Closes ticket 16762.
12571 - Treat the loss of an owning controller as equivalent to a SIGTERM
12572 signal. This removes a tiny amount of duplicated code, and
12573 simplifies our callgraph. Closes ticket 16788.
12574 - When generating an event to send to the controller, we no longer
12575 put the event over the network immediately. Instead, we queue
12576 these events, and use a Libevent callback to deliver them. This
12577 change simplifies Tor's callgraph by reducing the number of
12578 functions from which all other Tor functions are reachable. Closes
12580 - Wrap Windows-only C files inside '#ifdef _WIN32' so that tools
12581 that try to scan or compile every file on Unix won't decide that
12583 - Remove the unused "nulterminate" argument from buf_pullup().
12586 - Recommend a 40 GB example AccountingMax in torrc.sample rather
12587 than a 4 GB max. Closes ticket 16742.
12588 - Include the TUNING document in our source tarball. It is referred
12589 to in the ChangeLog and an error message. Fixes bug 16929; bugfix
12593 - The internal pure-C tor-fw-helper tool is now removed from the Tor
12594 distribution, in favor of the pure-Go clone available from
12595 https://gitweb.torproject.org/tor-fw-helper.git/ . The libraries
12596 used by the C tor-fw-helper are not, in our opinion, very
12597 confidence- inspiring in their secure-programming techniques.
12598 Closes ticket 13338.
12599 - Remove the code that would try to aggressively flush controller
12600 connections while writing to them. This code was introduced in
12601 0.1.2.7-alpha, in order to keep output buffers from exceeding
12602 their limits. But there is no longer a maximum output buffer size,
12603 and flushing data in this way caused some undesirable recursions
12604 in our call graph. Closes ticket 16480.
12607 - Make "bridges+hs" the default test network. This tests almost all
12608 tor functionality during make test-network, while allowing tests
12609 to succeed on non-IPv6 systems. Requires chutney commit 396da92 in
12610 test-network-bridges-hs. Closes tickets 16945 (tor) and 16946
12611 (chutney). Patches by "teor".
12612 - Autodetect CHUTNEY_PATH if the chutney and Tor sources are side-
12613 by-side in the same parent directory. Closes ticket 16903. Patch
12615 - Use environment variables rather than autoconf substitutions to
12616 send variables from the build system to the test scripts. This
12617 change should be easier to maintain, and cause 'make distcheck' to
12618 work better than before. Fixes bug 17148.
12619 - Add a new set of callgraph analysis scripts that use clang to
12620 produce a list of which Tor functions are reachable from which
12621 other Tor functions. We're planning to use these to help simplify
12622 our code structure by identifying illogical dependencies.
12623 - Add new 'test-full' and 'test-full-online' targets to run all
12624 tests, including integration tests with stem and chutney.
12625 - Make the test-workqueue test work on Windows by initializing the
12626 network before we begin.
12627 - New make target (make test-network-all) to run multiple applicable
12628 chutney test cases. Patch from Teor; closes 16953.
12629 - Unit test dns_resolve(), dns_clip_ttl() and dns_get_expiry_ttl()
12630 functions in dns.c. Implements a portion of ticket 16831.
12631 - When building Tor with testing coverage enabled, run Chutney tests
12632 (if any) using the 'tor-cov' coverage binary.
12633 - When running test-network or test-stem, check for the absence of
12634 stem/chutney before doing any build operations.
12637 Changes in version 0.2.7.2-alpha - 2015-07-27
12638 This, the second alpha in the Tor 0.2.7 series, has a number of new
12639 features, including a way to manually pick the number of introduction
12640 points for hidden services, and the much stronger Ed25519 signing key
12641 algorithm for regular Tor relays (including support for encrypted
12642 offline identity keys in the new algorithm).
12644 Support for Ed25519 on relays is currently limited to signing router
12645 descriptors; later alphas in this series will extend Ed25519 key
12646 support to more parts of the Tor protocol.
12648 o Major features (Ed25519 identity keys, Proposal 220):
12649 - All relays now maintain a stronger identity key, using the Ed25519
12650 elliptic curve signature format. This master key is designed so
12651 that it can be kept offline. Relays also generate an online
12652 signing key, and a set of other Ed25519 keys and certificates.
12653 These are all automatically regenerated and rotated as needed.
12654 Implements part of ticket 12498.
12655 - Directory authorities now vote on Ed25519 identity keys along with
12656 RSA1024 keys. Implements part of ticket 12498.
12657 - Directory authorities track which Ed25519 identity keys have been
12658 used with which RSA1024 identity keys, and do not allow them to
12659 vary freely. Implements part of ticket 12498.
12660 - Microdescriptors now include Ed25519 identity keys. Implements
12661 part of ticket 12498.
12662 - Add support for offline encrypted Ed25519 master keys. To use this
12663 feature on your tor relay, run "tor --keygen" to make a new master
12664 key (or to make a new signing key if you already have a master
12665 key). Closes ticket 13642.
12667 o Major features (Hidden services):
12668 - Add the torrc option HiddenServiceNumIntroductionPoints, to
12669 specify a fixed number of introduction points. Its maximum value
12670 is 10 and default is 3. Using this option can increase a hidden
12671 service's reliability under load, at the cost of making it more
12672 visible that the hidden service is facing extra load. Closes
12674 - Remove the adaptive algorithm for choosing the number of
12675 introduction points, which used to change the number of
12676 introduction points (poorly) depending on the number of
12677 connections the HS sees. Closes ticket 4862.
12679 o Major features (onion key cross-certification):
12680 - Relay descriptors now include signatures of their own identity
12681 keys, made using the TAP and ntor onion keys. These signatures
12682 allow relays to prove ownership of their own onion keys. Because
12683 of this change, microdescriptors will no longer need to include
12684 RSA identity keys. Implements proposal 228; closes ticket 12499.
12686 o Major features (performance):
12687 - Improve the runtime speed of Ed25519 operations by using the
12688 public-domain Ed25519-donna by Andrew M. ("floodyberry").
12689 Implements ticket 16467.
12690 - Improve the runtime speed of the ntor handshake by using an
12691 optimized curve25519 basepoint scalarmult implementation from the
12692 public-domain Ed25519-donna by Andrew M. ("floodyberry"), based on
12693 ideas by Adam Langley. Implements ticket 9663.
12695 o Major bugfixes (client-side privacy, also in 0.2.6.9):
12696 - Properly separate out each SOCKSPort when applying stream
12697 isolation. The error occurred because each port's session group
12698 was being overwritten by a default value when the listener
12699 connection was initialized. Fixes bug 16247; bugfix on
12700 0.2.6.3-alpha. Patch by "jojelino".
12702 o Major bugfixes (hidden service clients, stability, also in 0.2.6.10):
12703 - Stop refusing to store updated hidden service descriptors on a
12704 client. This reverts commit 9407040c59218 (which indeed fixed bug
12705 14219, but introduced a major hidden service reachability
12706 regression detailed in bug 16381). This is a temporary fix since
12707 we can live with the minor issue in bug 14219 (it just results in
12708 some load on the network) but the regression of 16381 is too much
12709 of a setback. First-round fix for bug 16381; bugfix
12712 o Major bugfixes (hidden services):
12713 - When cannibalizing a circuit for an introduction point, always
12714 extend to the chosen exit node (creating a 4 hop circuit).
12715 Previously Tor would use the current circuit exit node, which
12716 changed the original choice of introduction point, and could cause
12717 the hidden service to skip excluded introduction points or
12718 reconnect to a skipped introduction point. Fixes bug 16260; bugfix
12721 o Major bugfixes (open file limit):
12722 - The open file limit wasn't checked before calling
12723 tor_accept_socket_nonblocking(), which would make Tor exceed the
12724 limit. Now, before opening a new socket, Tor validates the open
12725 file limit just before, and if the max has been reached, return an
12726 error. Fixes bug 16288; bugfix on 0.1.1.1-alpha.
12728 o Major bugfixes (stability, also in 0.2.6.10):
12729 - Stop crashing with an assertion failure when parsing certain kinds
12730 of malformed or truncated microdescriptors. Fixes bug 16400;
12731 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
12732 by "cypherpunks_backup".
12733 - Stop random client-side assertion failures that could occur when
12734 connecting to a busy hidden service, or connecting to a hidden
12735 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
12738 o Minor features (directory authorities, security, also in 0.2.6.9):
12739 - The HSDir flag given by authorities now requires the Stable flag.
12740 For the current network, this results in going from 2887 to 2806
12741 HSDirs. Also, it makes it harder for an attacker to launch a sybil
12742 attack by raising the effort for a relay to become Stable to
12743 require at the very least 7 days, while maintaining the 96 hours
12744 uptime requirement for HSDir. Implements ticket 8243.
12746 o Minor features (client):
12747 - Relax the validation of hostnames in SOCKS5 requests, allowing the
12748 character '_' to appear, in order to cope with domains observed in
12749 the wild that are serving non-RFC compliant records. Resolves
12751 - Relax the validation done to hostnames in SOCKS5 requests, and
12752 allow a single trailing '.' to cope with clients that pass FQDNs
12753 using that syntax to explicitly indicate that the domain name is
12754 fully-qualified. Fixes bug 16674; bugfix on 0.2.6.2-alpha.
12755 - Add GroupWritable and WorldWritable options to unix-socket based
12756 SocksPort and ControlPort options. These options apply to a single
12757 socket, and override {Control,Socks}SocketsGroupWritable. Closes
12760 o Minor features (control protocol):
12761 - Support network-liveness GETINFO key and NETWORK_LIVENESS event in
12762 the control protocol. Resolves ticket 15358.
12764 o Minor features (directory authorities):
12765 - Directory authorities no longer vote against the "Fast", "Stable",
12766 and "HSDir" flags just because they were going to vote against
12767 "Running": if the consensus turns out to be that the router was
12768 running, then the authority's vote should count. Patch from Peter
12769 Retzlaff; closes issue 8712.
12771 o Minor features (geoip, also in 0.2.6.10):
12772 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
12773 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
12775 o Minor features (hidden services):
12776 - Add the new options "HiddenServiceMaxStreams" and
12777 "HiddenServiceMaxStreamsCloseCircuit" to allow hidden services to
12778 limit the maximum number of simultaneous streams per circuit, and
12779 optionally tear down the circuit when the limit is exceeded. Part
12782 o Minor features (portability):
12783 - Use C99 variadic macros when the compiler is not GCC. This avoids
12784 failing compilations on MSVC, and fixes a log-file-based race
12785 condition in our old workarounds. Original patch from Gisle Vanem.
12787 o Minor bugfixes (compilation, also in 0.2.6.9):
12788 - Build with --enable-systemd correctly when libsystemd is
12789 installed, but systemd is not. Fixes bug 16164; bugfix on
12790 0.2.6.3-alpha. Patch from Peter Palfrader.
12792 o Minor bugfixes (controller):
12793 - Add the descriptor ID in each HS_DESC control event. It was
12794 missing, but specified in control-spec.txt. Fixes bug 15881;
12795 bugfix on 0.2.5.2-alpha.
12797 o Minor bugfixes (crypto error-handling, also in 0.2.6.10):
12798 - Check for failures from crypto_early_init, and refuse to continue.
12799 A previous typo meant that we could keep going with an
12800 uninitialized crypto library, and would have OpenSSL initialize
12801 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
12802 when implementing ticket 4900. Patch by "teor".
12804 o Minor bugfixes (hidden services):
12805 - Fix a crash when reloading configuration while at least one
12806 configured and one ephemeral hidden service exists. Fixes bug
12807 16060; bugfix on 0.2.7.1-alpha.
12808 - Avoid crashing with a double-free bug when we create an ephemeral
12809 hidden service but adding it fails for some reason. Fixes bug
12810 16228; bugfix on 0.2.7.1-alpha.
12812 o Minor bugfixes (Linux seccomp2 sandbox):
12813 - Use the sandbox in tor_open_cloexec whether or not O_CLOEXEC is
12814 defined. Patch by "teor". Fixes bug 16515; bugfix on 0.2.3.1-alpha.
12816 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.10):
12817 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
12818 these when eventfd2() support is missing. Fixes bug 16363; bugfix
12819 on 0.2.6.3-alpha. Patch from "teor".
12821 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.9):
12822 - Fix sandboxing to work when running as a relay, by allowing the
12823 renaming of secret_id_key, and allowing the eventfd2 and futex
12824 syscalls. Fixes bug 16244; bugfix on 0.2.6.1-alpha. Patch by
12826 - Allow systemd connections to work with the Linux seccomp2 sandbox
12827 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
12830 o Minor bugfixes (relay):
12831 - Fix a rarely-encountered memory leak when failing to initialize
12832 the thread pool. Fixes bug 16631; bugfix on 0.2.6.3-alpha. Patch
12833 from "cypherpunks".
12835 o Minor bugfixes (systemd):
12836 - Fix an accidental formatting error that broke the systemd
12837 configuration file. Fixes bug 16152; bugfix on 0.2.7.1-alpha.
12838 - Tor's systemd unit file no longer contains extraneous spaces.
12839 These spaces would sometimes confuse tools like deb-systemd-
12840 helper. Fixes bug 16162; bugfix on 0.2.5.5-alpha.
12842 o Minor bugfixes (tests):
12843 - Use the configured Python executable when running test-stem-full.
12844 Fixes bug 16470; bugfix on 0.2.7.1-alpha.
12846 o Minor bugfixes (tests, also in 0.2.6.9):
12847 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
12848 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
12850 o Minor bugfixes (threads, comments):
12851 - Always initialize return value in compute_desc_id in rendcommon.c
12852 Patch by "teor". Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
12853 - Check for NULL values in getinfo_helper_onions(). Patch by "teor".
12854 Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
12855 - Remove undefined directive-in-macro in test_util_writepid clang
12856 3.7 complains that using a preprocessor directive inside a macro
12857 invocation in test_util_writepid in test_util.c is undefined.
12858 Patch by "teor". Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
12860 o Code simplification and refactoring:
12861 - Define WINVER and _WIN32_WINNT centrally, in orconfig.h, in order
12862 to ensure they remain consistent and visible everywhere.
12863 - Remove some vestigial workarounds for the MSVC6 compiler. We
12864 haven't supported that in ages.
12865 - The link authentication code has been refactored for better
12866 testability and reliability. It now uses code generated with the
12867 "trunnel" binary encoding generator, to reduce the risk of bugs
12868 due to programmer error. Done as part of ticket 12498.
12871 - Include a specific and (hopefully) accurate documentation of the
12872 torrc file's meta-format in doc/torrc_format.txt. This is mainly
12873 of interest to people writing programs to parse or generate torrc
12874 files. This document is not a commitment to long-term
12875 compatibility; some aspects of the current format are a bit
12876 ridiculous. Closes ticket 2325.
12878 o Removed features:
12879 - Tor no longer supports copies of OpenSSL that are missing support
12880 for Elliptic Curve Cryptography. (We began using ECC when
12881 available in 0.2.4.8-alpha, for more safe and efficient key
12882 negotiation.) In particular, support for at least one of P256 or
12883 P224 is now required, with manual configuration needed if only
12884 P224 is available. Resolves ticket 16140.
12885 - Tor no longer supports versions of OpenSSL before 1.0. (If you are
12886 on an operating system that has not upgraded to OpenSSL 1.0 or
12887 later, and you compile Tor from source, you will need to install a
12888 more recent OpenSSL to link Tor against.) These versions of
12889 OpenSSL are still supported by the OpenSSL, but the numerous
12890 cryptographic improvements in later OpenSSL releases makes them a
12891 clear choice. Resolves ticket 16034.
12892 - Remove the HidServDirectoryV2 option. Now all relays offer to
12893 store hidden service descriptors. Related to 16543.
12894 - Remove the VoteOnHidServDirectoriesV2 option, since all
12895 authorities have long set it to 1. Closes ticket 16543.
12898 - Document use of coverity, clang static analyzer, and clang dynamic
12899 undefined behavior and address sanitizers in doc/HACKING. Include
12900 detailed usage instructions in the blacklist. Patch by "teor".
12901 Closes ticket 15817.
12902 - The link authentication protocol code now has extensive tests.
12903 - The relay descriptor signature testing code now has
12905 - The test_workqueue program now runs faster, and is enabled by
12906 default as a part of "make check".
12907 - Now that OpenSSL has its own scrypt implementation, add an unit
12908 test that checks for interoperability between libscrypt_scrypt()
12909 and OpenSSL's EVP_PBE_scrypt() so that we could not use libscrypt
12910 and rely on EVP_PBE_scrypt() whenever possible. Resolves
12914 Changes in version 0.2.6.10 - 2015-07-12
12915 Tor version 0.2.6.10 fixes some significant stability and hidden
12916 service client bugs, bulletproofs the cryptography init process, and
12917 fixes a bug when using the sandbox code with some older versions of
12918 Linux. Everyone running an older version, especially an older version
12919 of 0.2.6, should upgrade.
12921 o Major bugfixes (hidden service clients, stability):
12922 - Stop refusing to store updated hidden service descriptors on a
12923 client. This reverts commit 9407040c59218 (which indeed fixed bug
12924 14219, but introduced a major hidden service reachability
12925 regression detailed in bug 16381). This is a temporary fix since
12926 we can live with the minor issue in bug 14219 (it just results in
12927 some load on the network) but the regression of 16381 is too much
12928 of a setback. First-round fix for bug 16381; bugfix
12931 o Major bugfixes (stability):
12932 - Stop crashing with an assertion failure when parsing certain kinds
12933 of malformed or truncated microdescriptors. Fixes bug 16400;
12934 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
12935 by "cypherpunks_backup".
12936 - Stop random client-side assertion failures that could occur when
12937 connecting to a busy hidden service, or connecting to a hidden
12938 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
12941 o Minor features (geoip):
12942 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
12943 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
12945 o Minor bugfixes (crypto error-handling):
12946 - Check for failures from crypto_early_init, and refuse to continue.
12947 A previous typo meant that we could keep going with an
12948 uninitialized crypto library, and would have OpenSSL initialize
12949 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
12950 when implementing ticket 4900. Patch by "teor".
12952 o Minor bugfixes (Linux seccomp2 sandbox):
12953 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
12954 these when eventfd2() support is missing. Fixes bug 16363; bugfix
12955 on 0.2.6.3-alpha. Patch from "teor".
12958 Changes in version 0.2.6.9 - 2015-06-11
12959 Tor 0.2.6.9 fixes a regression in the circuit isolation code, increases the
12960 requirements for receiving an HSDir flag, and addresses some other small
12961 bugs in the systemd and sandbox code. Clients using circuit isolation
12962 should upgrade; all directory authorities should upgrade.
12964 o Major bugfixes (client-side privacy):
12965 - Properly separate out each SOCKSPort when applying stream
12966 isolation. The error occurred because each port's session group was
12967 being overwritten by a default value when the listener connection
12968 was initialized. Fixes bug 16247; bugfix on 0.2.6.3-alpha. Patch
12971 o Minor feature (directory authorities, security):
12972 - The HSDir flag given by authorities now requires the Stable flag.
12973 For the current network, this results in going from 2887 to 2806
12974 HSDirs. Also, it makes it harder for an attacker to launch a sybil
12975 attack by raising the effort for a relay to become Stable which
12976 takes at the very least 7 days to do so and by keeping the 96
12977 hours uptime requirement for HSDir. Implements ticket 8243.
12979 o Minor bugfixes (compilation):
12980 - Build with --enable-systemd correctly when libsystemd is
12981 installed, but systemd is not. Fixes bug 16164; bugfix on
12982 0.2.6.3-alpha. Patch from Peter Palfrader.
12984 o Minor bugfixes (Linux seccomp2 sandbox):
12985 - Fix sandboxing to work when running as a relaymby renaming of
12986 secret_id_key, and allowing the eventfd2 and futex syscalls. Fixes
12987 bug 16244; bugfix on 0.2.6.1-alpha. Patch by Peter Palfrader.
12988 - Allow systemd connections to work with the Linux seccomp2 sandbox
12989 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
12992 o Minor bugfixes (tests):
12993 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
12994 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
12997 Changes in version 0.2.6.8 - 2015-05-21
12998 Tor 0.2.6.8 fixes a bit of dodgy code in parsing INTRODUCE2 cells, and
12999 fixes an authority-side bug in assigning the HSDir flag. All directory
13000 authorities should upgrade.
13002 o Major bugfixes (hidden services, backport from 0.2.7.1-alpha):
13003 - Revert commit that made directory authorities assign the HSDir
13004 flag to relays without a DirPort; this was bad because such relays
13005 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
13008 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
13009 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
13010 a client authorized hidden service. Fixes bug 15823; bugfix
13013 o Minor features (geoip):
13014 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
13015 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
13019 Changes in version 0.2.7.1-alpha - 2015-05-12
13020 Tor 0.2.7.1-alpha is the first alpha release in its series. It
13021 includes numerous small features and bugfixes against previous Tor
13022 versions, and numerous small infrastructure improvements. The most
13023 notable features are several new ways for controllers to interact with
13024 the hidden services subsystem.
13026 o New system requirements:
13027 - Tor no longer includes workarounds to support Libevent versions
13028 before 1.3e. Libevent 2.0 or later is recommended. Closes
13031 o Major features (controller):
13032 - Add the ADD_ONION and DEL_ONION commands that allow the creation
13033 and management of hidden services via the controller. Closes
13035 - New "GETINFO onions/current" and "GETINFO onions/detached"
13036 commands to get information about hidden services created via the
13037 controller. Part of ticket 6411.
13038 - New HSFETCH command to launch a request for a hidden service
13039 descriptor. Closes ticket 14847.
13040 - New HSPOST command to upload a hidden service descriptor. Closes
13041 ticket 3523. Patch by "DonnchaC".
13043 o Major bugfixes (hidden services):
13044 - Revert commit that made directory authorities assign the HSDir
13045 flag to relays without a DirPort; this was bad because such relays
13046 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
13049 o Minor features (clock-jump tolerance):
13050 - Recover better when our clock jumps back many hours, like might
13051 happen for Tails or Whonix users who start with a very wrong
13052 hardware clock, use Tor to discover a more accurate time, and then
13053 fix their clock. Resolves part of ticket 8766.
13055 o Minor features (command-line interface):
13056 - Make --hash-password imply --hush to prevent unnecessary noise.
13057 Closes ticket 15542. Patch from "cypherpunks".
13058 - Print a warning whenever we find a relative file path being used
13059 as torrc option. Resolves issue 14018.
13061 o Minor features (controller):
13062 - Add DirAuthority lines for default directory authorities to the
13063 output of the "GETINFO config/defaults" command if not already
13064 present. Implements ticket 14840.
13065 - Controllers can now use "GETINFO hs/client/desc/id/..." to
13066 retrieve items from the client's hidden service descriptor cache.
13067 Closes ticket 14845.
13068 - Implement a new controller command "GETINFO status/fresh-relay-
13069 descs" to fetch a descriptor/extrainfo pair that was generated on
13070 demand just for the controller's use. Implements ticket 14784.
13072 o Minor features (DoS-resistance):
13073 - Make it harder for attackers to overload hidden services with
13074 introductions, by blocking multiple introduction requests on the
13075 same circuit. Resolves ticket 15515.
13077 o Minor features (geoip):
13078 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
13079 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
13082 o Minor features (HS popularity countermeasure):
13083 - To avoid leaking HS popularity, don't cycle the introduction point
13084 when we've handled a fixed number of INTRODUCE2 cells but instead
13085 cycle it when a random number of introductions is reached, thus
13086 making it more difficult for an attacker to find out the amount of
13087 clients that have used the introduction point for a specific HS.
13088 Closes ticket 15745.
13090 o Minor features (logging):
13091 - Include the Tor version in all LD_BUG log messages, since people
13092 tend to cut and paste those into the bugtracker. Implements
13095 o Minor features (pluggable transports):
13096 - When launching managed pluggable transports on Linux systems,
13097 attempt to have the kernel deliver a SIGTERM on tor exit if the
13098 pluggable transport process is still running. Resolves
13100 - When launching managed pluggable transports, setup a valid open
13101 stdin in the child process that can be used to detect if tor has
13102 terminated. The "TOR_PT_EXIT_ON_STDIN_CLOSE" environment variable
13103 can be used by implementations to detect this new behavior.
13104 Resolves ticket 15435.
13106 o Minor features (testing):
13107 - Add a test to verify that the compiler does not eliminate our
13108 memwipe() implementation. Closes ticket 15377.
13109 - Add make rule `check-changes` to verify the format of changes
13110 files. Closes ticket 15180.
13111 - Add unit tests for control_event_is_interesting(). Add a compile-
13112 time check that the number of events doesn't exceed the capacity
13113 of control_event_t.event_mask. Closes ticket 15431, checks for
13114 bugs similar to 13085. Patch by "teor".
13115 - Command-line argument tests moved to Stem. Resolves ticket 14806.
13116 - Integrate the ntor, backtrace, and zero-length keys tests into the
13117 automake test suite. Closes ticket 15344.
13118 - Remove assertions during builds to determine Tor's test coverage.
13119 We don't want to trigger these even in assertions, so including
13120 them artificially makes our branch coverage look worse than it is.
13121 This patch provides the new test-stem-full and coverage-html-full
13122 configure options. Implements ticket 15400.
13124 o Minor bugfixes (build):
13125 - Improve out-of-tree builds by making non-standard rules work and
13126 clean up additional files and directories. Fixes bug 15053; bugfix
13129 o Minor bugfixes (command-line interface):
13130 - When "--quiet" is provided along with "--validate-config", do not
13131 write anything to stdout on success. Fixes bug 14994; bugfix
13133 - When complaining about bad arguments to "--dump-config", use
13134 stderr, not stdout.
13136 o Minor bugfixes (configuration, unit tests):
13137 - Only add the default fallback directories when the DirAuthorities,
13138 AlternateDirAuthority, and FallbackDir directory config options
13139 are set to their defaults. The default fallback directory list is
13140 currently empty, this fix will only change tor's behavior when it
13141 has default fallback directories. Includes unit tests for
13142 consider_adding_dir_servers(). Fixes bug 15642; bugfix on
13143 90f6071d8dc0 in 0.2.4.7-alpha. Patch by "teor".
13145 o Minor bugfixes (correctness):
13146 - For correctness, avoid modifying a constant string in
13147 handle_control_postdescriptor. Fixes bug 15546; bugfix
13149 - Remove side-effects from tor_assert() calls. This was harmless,
13150 because we never disable assertions, but it is bad style and
13151 unnecessary. Fixes bug 15211; bugfix on 0.2.5.5, 0.2.2.36,
13154 o Minor bugfixes (hidden service):
13155 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
13156 a client authorized hidden service. Fixes bug 15823; bugfix
13158 - Remove an extraneous newline character from the end of hidden
13159 service descriptors. Fixes bug 15296; bugfix on 0.2.0.10-alpha.
13161 o Minor bugfixes (interface):
13162 - Print usage information for --dump-config when it is used without
13163 an argument. Also, fix the error message to use different wording
13164 and add newline at the end. Fixes bug 15541; bugfix
13167 o Minor bugfixes (logs):
13168 - When building Tor under Clang, do not include an extra set of
13169 parentheses in log messages that include function names. Fixes bug
13170 15269; bugfix on every released version of Tor when compiled with
13171 recent enough Clang.
13173 o Minor bugfixes (network):
13174 - When attempting to use fallback technique for network interface
13175 lookup, disregard loopback and multicast addresses since they are
13176 unsuitable for public communications.
13178 o Minor bugfixes (statistics):
13179 - Disregard the ConnDirectionStatistics torrc options when Tor is
13180 not a relay since in that mode of operation no sensible data is
13181 being collected and because Tor might run into measurement hiccups
13182 when running as a client for some time, then becoming a relay.
13183 Fixes bug 15604; bugfix on 0.2.2.35.
13185 o Minor bugfixes (test networks):
13186 - When self-testing reachability, use ExtendAllowPrivateAddresses to
13187 determine if local/private addresses imply reachability. The
13188 previous fix used TestingTorNetwork, which implies
13189 ExtendAllowPrivateAddresses, but this excluded rare configurations
13190 where ExtendAllowPrivateAddresses is set but TestingTorNetwork is
13191 not. Fixes bug 15771; bugfix on 0.2.6.1-alpha. Patch by "teor",
13192 issue discovered by CJ Ess.
13194 o Minor bugfixes (testing):
13195 - Check for matching value in server response in ntor_ref.py. Fixes
13196 bug 15591; bugfix on 0.2.4.8-alpha. Reported and fixed
13198 - Set the severity correctly when testing
13199 get_interface_addresses_ifaddrs() and
13200 get_interface_addresses_win32(), so that the tests fail gracefully
13201 instead of triggering an assertion. Fixes bug 15759; bugfix on
13202 0.2.6.3-alpha. Reported by Nicolas Derive.
13204 o Code simplification and refactoring:
13205 - Move the hacky fallback code out of get_interface_address6() into
13206 separate function and get it covered with unit-tests. Resolves
13208 - Refactor hidden service client-side cache lookup to intelligently
13209 report its various failure cases, and disentangle failure cases
13210 involving a lack of introduction points. Closes ticket 14391.
13211 - Use our own Base64 encoder instead of OpenSSL's, to allow more
13212 control over the output. Part of ticket 15652.
13215 - Improve the descriptions of statistics-related torrc options in
13216 the manpage to describe rationale and possible uses cases. Fixes
13218 - Improve the layout and formatting of ./configure --help messages.
13219 Closes ticket 15024. Patch from "cypherpunks".
13220 - Standardize on the term "server descriptor" in the manual page.
13221 Previously, we had used "router descriptor", "server descriptor",
13222 and "relay descriptor" interchangeably. Part of ticket 14987.
13225 - Remove `USE_OPENSSL_BASE64` and the corresponding fallback code
13226 and always use the internal Base64 decoder. The internal decoder
13227 has been part of tor since 0.2.0.10-alpha, and no one should
13228 be using the OpenSSL one. Part of ticket 15652.
13229 - Remove the 'tor_strclear()' function; use memwipe() instead.
13230 Closes ticket 14922.
13232 o Removed features:
13233 - Remove the (seldom-used) DynamicDHGroups feature. For anti-
13234 fingerprinting we now recommend pluggable transports; for forward-
13235 secrecy in TLS, we now use the P-256 group. Closes ticket 13736.
13236 - Remove the undocumented "--digests" command-line option. It
13237 complicated our build process, caused subtle build issues on
13238 multiple platforms, and is now redundant since we started
13239 including git version identifiers. Closes ticket 14742.
13240 - Tor no longer contains checks for ancient directory cache versions
13241 that didn't know about microdescriptors.
13242 - Tor no longer contains workarounds for stat files generated by
13243 super-old versions of Tor that didn't choose guards sensibly.
13246 Changes in version 0.2.4.27 - 2015-04-06
13247 Tor 0.2.4.27 backports two fixes from 0.2.6.7 for security issues that
13248 could be used by an attacker to crash hidden services, or crash clients
13249 visiting hidden services. Hidden services should upgrade as soon as
13250 possible; clients should upgrade whenever packages become available.
13252 This release also backports a simple improvement to make hidden
13253 services a bit less vulnerable to denial-of-service attacks.
13255 o Major bugfixes (security, hidden service):
13256 - Fix an issue that would allow a malicious client to trigger an
13257 assertion failure and halt a hidden service. Fixes bug 15600;
13258 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
13259 - Fix a bug that could cause a client to crash with an assertion
13260 failure when parsing a malformed hidden service descriptor. Fixes
13261 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
13263 o Minor features (DoS-resistance, hidden service):
13264 - Introduction points no longer allow multiple INTRODUCE1 cells to
13265 arrive on the same circuit. This should make it more expensive for
13266 attackers to overwhelm hidden services with introductions.
13267 Resolves ticket 15515.
13270 Changes in version 0.2.5.12 - 2015-04-06
13271 Tor 0.2.5.12 backports two fixes from 0.2.6.7 for security issues that
13272 could be used by an attacker to crash hidden services, or crash clients
13273 visiting hidden services. Hidden services should upgrade as soon as
13274 possible; clients should upgrade whenever packages become available.
13276 This release also backports a simple improvement to make hidden
13277 services a bit less vulnerable to denial-of-service attacks.
13279 o Major bugfixes (security, hidden service):
13280 - Fix an issue that would allow a malicious client to trigger an
13281 assertion failure and halt a hidden service. Fixes bug 15600;
13282 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
13283 - Fix a bug that could cause a client to crash with an assertion
13284 failure when parsing a malformed hidden service descriptor. Fixes
13285 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
13287 o Minor features (DoS-resistance, hidden service):
13288 - Introduction points no longer allow multiple INTRODUCE1 cells to
13289 arrive on the same circuit. This should make it more expensive for
13290 attackers to overwhelm hidden services with introductions.
13291 Resolves ticket 15515.
13294 Changes in version 0.2.6.7 - 2015-04-06
13295 Tor 0.2.6.7 fixes two security issues that could be used by an
13296 attacker to crash hidden services, or crash clients visiting hidden
13297 services. Hidden services should upgrade as soon as possible; clients
13298 should upgrade whenever packages become available.
13300 This release also contains two simple improvements to make hidden
13301 services a bit less vulnerable to denial-of-service attacks.
13303 o Major bugfixes (security, hidden service):
13304 - Fix an issue that would allow a malicious client to trigger an
13305 assertion failure and halt a hidden service. Fixes bug 15600;
13306 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
13307 - Fix a bug that could cause a client to crash with an assertion
13308 failure when parsing a malformed hidden service descriptor. Fixes
13309 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
13311 o Minor features (DoS-resistance, hidden service):
13312 - Introduction points no longer allow multiple INTRODUCE1 cells to
13313 arrive on the same circuit. This should make it more expensive for
13314 attackers to overwhelm hidden services with introductions.
13315 Resolves ticket 15515.
13316 - Decrease the amount of reattempts that a hidden service performs
13317 when its rendezvous circuits fail. This reduces the computational
13318 cost for running a hidden service under heavy load. Resolves
13322 Changes in version 0.2.6.6 - 2015-03-24
13323 Tor 0.2.6.6 is the first stable release in the 0.2.6 series.
13325 It adds numerous safety, security, correctness, and performance
13326 improvements. Client programs can be configured to use more kinds of
13327 sockets, AutomapHosts works better, the multithreading backend is
13328 improved, cell transmission is refactored, test coverage is much
13329 higher, more denial-of-service attacks are handled, guard selection is
13330 improved to handle long-term guards better, pluggable transports
13331 should work a bit better, and some annoying hidden service performance
13332 bugs should be addressed.
13334 o Minor bugfixes (portability):
13335 - Use the correct datatype in the SipHash-2-4 function to prevent
13336 compilers from assuming any sort of alignment. Fixes bug 15436;
13337 bugfix on 0.2.5.3-alpha.
13339 Changes in version 0.2.6.5-rc - 2015-03-18
13340 Tor 0.2.6.5-rc is the second and (hopefully) last release candidate in
13341 the 0.2.6. It fixes a small number of bugs found in 0.2.6.4-rc.
13343 o Major bugfixes (client):
13344 - Avoid crashing when making certain configuration option changes on
13345 clients. Fixes bug 15245; bugfix on 0.2.6.3-alpha. Reported
13348 o Major bugfixes (pluggable transports):
13349 - Initialize the extended OR Port authentication cookie before
13350 launching pluggable transports. This prevents a race condition
13351 that occurred when server-side pluggable transports would cache the
13352 authentication cookie before it has been (re)generated. Fixes bug
13353 15240; bugfix on 0.2.5.1-alpha.
13355 o Major bugfixes (portability):
13356 - Do not crash on startup when running on Solaris. Fixes a bug
13357 related to our fix for 9495; bugfix on 0.2.6.1-alpha. Reported
13360 o Minor features (heartbeat):
13361 - On relays, report how many connections we negotiated using each
13362 version of the Tor link protocols. This information will let us
13363 know if removing support for very old versions of the Tor
13364 protocols is harming the network. Closes ticket 15212.
13366 o Code simplification and refactoring:
13367 - Refactor main loop to extract the 'loop' part. This makes it
13368 easier to run Tor under Shadow. Closes ticket 15176.
13371 Changes in version 0.2.5.11 - 2015-03-17
13372 Tor 0.2.5.11 is the second stable release in the 0.2.5 series.
13374 It backports several bugfixes from the 0.2.6 branch, including a
13375 couple of medium-level security fixes for relays and exit nodes.
13376 It also updates the list of directory authorities.
13378 o Directory authority changes:
13379 - Remove turtles as a directory authority.
13380 - Add longclaw as a new (v3) directory authority. This implements
13381 ticket 13296. This keeps the directory authority count at 9.
13382 - The directory authority Faravahar has a new IP address. This
13383 closes ticket 14487.
13385 o Major bugfixes (crash, OSX, security):
13386 - Fix a remote denial-of-service opportunity caused by a bug in
13387 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
13390 o Major bugfixes (relay, stability, possible security):
13391 - Fix a bug that could lead to a relay crashing with an assertion
13392 failure if a buffer of exactly the wrong layout was passed to
13393 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
13394 0.2.0.10-alpha. Patch from 'cypherpunks'.
13395 - Do not assert if the 'data' pointer on a buffer is advanced to the
13396 very end of the buffer; log a BUG message instead. Only assert if
13397 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
13399 o Major bugfixes (exit node stability):
13400 - Fix an assertion failure that could occur under high DNS load.
13401 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
13402 diagnosed and fixed by "cypherpunks".
13404 o Major bugfixes (Linux seccomp2 sandbox):
13405 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
13406 crash during attempts to call wait4. Fixes bug 15088; bugfix on
13407 0.2.5.1-alpha. Patch from "sanic".
13409 o Minor features (controller):
13410 - New "GETINFO bw-event-cache" to get information about recent
13411 bandwidth events. Closes ticket 14128. Useful for controllers to
13412 get recent bandwidth history after the fix for ticket 13988.
13414 o Minor features (geoip):
13415 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
13416 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
13419 o Minor bugfixes (client, automapping):
13420 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
13421 no value follows the option. Fixes bug 14142; bugfix on
13422 0.2.4.7-alpha. Patch by "teor".
13423 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
13424 14195; bugfix on 0.1.0.1-rc.
13426 o Minor bugfixes (compilation):
13427 - Build without warnings with the stock OpenSSL srtp.h header, which
13428 has a duplicate declaration of SSL_get_selected_srtp_profile().
13429 Fixes bug 14220; this is OpenSSL's bug, not ours.
13431 o Minor bugfixes (directory authority):
13432 - Allow directory authorities to fetch more data from one another if
13433 they find themselves missing lots of votes. Previously, they had
13434 been bumping against the 10 MB queued data limit. Fixes bug 14261;
13435 bugfix on 0.1.2.5-alpha.
13436 - Enlarge the buffer to read bwauth generated files to avoid an
13437 issue when parsing the file in dirserv_read_measured_bandwidths().
13438 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
13440 o Minor bugfixes (statistics):
13441 - Increase period over which bandwidth observations are aggregated
13442 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
13444 o Minor bugfixes (preventative security, C safety):
13445 - When reading a hexadecimal, base-32, or base-64 encoded value from
13446 a string, always overwrite the whole output buffer. This prevents
13447 some bugs where we would look at (but fortunately, not reveal)
13448 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
13452 Changes in version 0.2.4.26 - 2015-03-17
13453 Tor 0.2.4.26 includes an updated list of directory authorities. It
13454 also backports a couple of stability and security bugfixes from 0.2.5
13457 o Directory authority changes:
13458 - Remove turtles as a directory authority.
13459 - Add longclaw as a new (v3) directory authority. This implements
13460 ticket 13296. This keeps the directory authority count at 9.
13461 - The directory authority Faravahar has a new IP address. This
13462 closes ticket 14487.
13464 o Major bugfixes (exit node stability, also in 0.2.6.3-alpha):
13465 - Fix an assertion failure that could occur under high DNS load.
13466 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
13467 diagnosed and fixed by "cypherpunks".
13469 o Major bugfixes (relay, stability, possible security, also in 0.2.6.4-rc):
13470 - Fix a bug that could lead to a relay crashing with an assertion
13471 failure if a buffer of exactly the wrong layout was passed to
13472 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
13473 0.2.0.10-alpha. Patch from 'cypherpunks'.
13474 - Do not assert if the 'data' pointer on a buffer is advanced to the
13475 very end of the buffer; log a BUG message instead. Only assert if
13476 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
13478 o Minor features (geoip):
13479 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
13480 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
13483 Changes in version 0.2.6.4-rc - 2015-03-09
13484 Tor 0.2.6.4-alpha fixes an issue in the directory code that an
13485 attacker might be able to use in order to crash certain Tor
13486 directories. It also resolves some minor issues left over from, or
13487 introduced in, Tor 0.2.6.3-alpha or earlier.
13489 o Major bugfixes (crash, OSX, security):
13490 - Fix a remote denial-of-service opportunity caused by a bug in
13491 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
13494 o Major bugfixes (relay, stability, possible security):
13495 - Fix a bug that could lead to a relay crashing with an assertion
13496 failure if a buffer of exactly the wrong layout is passed to
13497 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
13498 0.2.0.10-alpha. Patch from "cypherpunks".
13499 - Do not assert if the 'data' pointer on a buffer is advanced to the
13500 very end of the buffer; log a BUG message instead. Only assert if
13501 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
13503 o Major bugfixes (FreeBSD IPFW transparent proxy):
13504 - Fix address detection with FreeBSD transparent proxies, when
13505 "TransProxyType ipfw" is in use. Fixes bug 15064; bugfix
13508 o Major bugfixes (Linux seccomp2 sandbox):
13509 - Pass IPPROTO_TCP rather than 0 to socket(), so that the Linux
13510 seccomp2 sandbox doesn't fail. Fixes bug 14989; bugfix
13512 - Allow AF_UNIX hidden services to be used with the seccomp2
13513 sandbox. Fixes bug 15003; bugfix on 0.2.6.3-alpha.
13514 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
13515 crash during attempts to call wait4. Fixes bug 15088; bugfix on
13516 0.2.5.1-alpha. Patch from "sanic".
13518 o Minor features (controller):
13519 - Messages about problems in the bootstrap process now include
13520 information about the server we were trying to connect to when we
13521 noticed the problem. Closes ticket 15006.
13523 o Minor features (geoip):
13524 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
13525 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
13528 o Minor features (logs):
13529 - Quiet some log messages in the heartbeat and at startup. Closes
13532 o Minor bugfixes (certificate handling):
13533 - If an authority operator accidentally makes a signing certificate
13534 with a future publication time, do not discard its real signing
13535 certificates. Fixes bug 11457; bugfix on 0.2.0.3-alpha.
13536 - Remove any old authority certificates that have been superseded
13537 for at least two days. Previously, we would keep superseded
13538 certificates until they expired, if they were published close in
13539 time to the certificate that superseded them. Fixes bug 11454;
13540 bugfix on 0.2.1.8-alpha.
13542 o Minor bugfixes (compilation):
13543 - Fix a compilation warning on s390. Fixes bug 14988; bugfix
13545 - Fix a compilation warning on FreeBSD. Fixes bug 15151; bugfix
13548 o Minor bugfixes (testing):
13549 - Fix endianness issues in unit test for resolve_my_address() to
13550 have it pass on big endian systems. Fixes bug 14980; bugfix on
13552 - Avoid a side-effect in a tor_assert() in the unit tests. Fixes bug
13553 15188; bugfix on 0.1.2.3-alpha. Patch from Tom van der Woerdt.
13554 - When running the new 'make test-stem' target, use the configured
13555 python binary. Fixes bug 15037; bugfix on 0.2.6.3-alpha. Patch
13556 from "cypherpunks".
13557 - When running the zero-length-keys tests, do not use the default
13558 torrc file. Fixes bug 15033; bugfix on 0.2.6.3-alpha. Reported
13561 o Directory authority IP change:
13562 - The directory authority Faravahar has a new IP address. This
13563 closes ticket 14487.
13566 - Remove some lingering dead code that once supported mempools.
13567 Mempools were disabled by default in 0.2.5, and removed entirely
13568 in 0.2.6.3-alpha. Closes more of ticket 14848; patch
13572 Changes in version 0.2.6.3-alpha - 2015-02-19
13573 Tor 0.2.6.3-alpha is the third (and hopefully final) alpha release in
13574 the 0.2.6.x series. It introduces support for more kinds of sockets,
13575 makes it harder to accidentally run an exit, improves our
13576 multithreading backend, incorporates several fixes for the
13577 AutomapHostsOnResolve option, and fixes numerous other bugs besides.
13579 If no major regressions or security holes are found in this version,
13580 the next version will be a release candidate.
13582 o Deprecated versions:
13583 - Tor relays older than 0.2.4.18-rc are no longer allowed to
13584 advertise themselves on the network. Closes ticket 13555.
13586 o Major features (security, unix domain sockets):
13587 - Allow SocksPort to be an AF_UNIX Unix Domain Socket. Now high risk
13588 applications can reach Tor without having to create AF_INET or
13589 AF_INET6 sockets, meaning they can completely disable their
13590 ability to make non-Tor network connections. To create a socket of
13591 this type, use "SocksPort unix:/path/to/socket". Implements
13593 - Support mapping hidden service virtual ports to AF_UNIX sockets.
13594 The syntax is "HiddenServicePort 80 unix:/path/to/socket".
13595 Implements ticket 11485.
13597 o Major features (changed defaults):
13598 - Prevent relay operators from unintentionally running exits: When a
13599 relay is configured as an exit node, we now warn the user unless
13600 the "ExitRelay" option is set to 1. We warn even more loudly if
13601 the relay is configured with the default exit policy, since this
13602 can indicate accidental misconfiguration. Setting "ExitRelay 0"
13603 stops Tor from running as an exit relay. Closes ticket 10067.
13605 o Major features (directory system):
13606 - When downloading server- or microdescriptors from a directory
13607 server, we no longer launch multiple simultaneous requests to the
13608 same server. This reduces load on the directory servers,
13609 especially when directory guards are in use. Closes ticket 9969.
13610 - When downloading server- or microdescriptors over a tunneled
13611 connection, do not limit the length of our requests to what the
13612 Squid proxy is willing to handle. Part of ticket 9969.
13613 - Authorities can now vote on the correct digests and latest
13614 versions for different software packages. This allows packages
13615 that include Tor to use the Tor authority system as a way to get
13616 notified of updates and their correct digests. Implements proposal
13617 227. Closes ticket 10395.
13619 o Major features (guards):
13620 - Introduce the Guardfraction feature to improves load balancing on
13621 guard nodes. Specifically, it aims to reduce the traffic gap that
13622 guard nodes experience when they first get the Guard flag. This is
13623 a required step if we want to increase the guard lifetime to 9
13624 months or greater. Closes ticket 9321.
13626 o Major features (performance):
13627 - Make the CPU worker implementation more efficient by avoiding the
13628 kernel and lengthening pipelines. The original implementation used
13629 sockets to transfer data from the main thread to the workers, and
13630 didn't allow any thread to be assigned more than a single piece of
13631 work at once. The new implementation avoids communications
13632 overhead by making requests in shared memory, avoiding kernel IO
13633 where possible, and keeping more requests in flight at once.
13634 Implements ticket 9682.
13636 o Major features (relay):
13637 - Raise the minimum acceptable configured bandwidth rate for bridges
13638 to 50 KiB/sec and for relays to 75 KiB/sec. (The old values were
13639 20 KiB/sec.) Closes ticket 13822.
13641 o Major bugfixes (exit node stability):
13642 - Fix an assertion failure that could occur under high DNS load.
13643 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
13644 diagnosed and fixed by "cypherpunks".
13646 o Major bugfixes (mixed relay-client operation):
13647 - When running as a relay and client at the same time (not
13648 recommended), if we decide not to use a new guard because we want
13649 to retry older guards, only close the locally-originating circuits
13650 passing through that guard. Previously we would close all the
13651 circuits through that guard. Fixes bug 9819; bugfix on
13652 0.2.1.1-alpha. Reported by "skruffy".
13654 o Minor features (build):
13655 - New --disable-system-torrc compile-time option to prevent Tor from
13656 looking for the system-wide torrc or torrc-defaults files.
13657 Resolves ticket 13037.
13659 o Minor features (controller):
13660 - Include SOCKS_USERNAME and SOCKS_PASSWORD values in controller
13661 events so controllers can observe circuit isolation inputs. Closes
13663 - ControlPort now supports the unix:/path/to/socket syntax as an
13664 alternative to the ControlSocket option, for consistency with
13665 SocksPort and HiddenServicePort. Closes ticket 14451.
13666 - New "GETINFO bw-event-cache" to get information about recent
13667 bandwidth events. Closes ticket 14128. Useful for controllers to
13668 get recent bandwidth history after the fix for ticket 13988.
13670 o Minor features (Denial of service resistance):
13671 - Count the total number of bytes used storing hidden service
13672 descriptors against the value of MaxMemInQueues. If we're low on
13673 memory, and more than 20% of our memory is used holding hidden
13674 service descriptors, free them until no more than 10% of our
13675 memory holds hidden service descriptors. Free the least recently
13676 fetched descriptors first. Resolves ticket 13806.
13677 - When we have recently been under memory pressure (over 3/4 of
13678 MaxMemInQueues is allocated), then allocate smaller zlib objects
13679 for small requests. Closes ticket 11791.
13681 o Minor features (geoip):
13682 - Update geoip and geoip6 files to the January 7 2015 Maxmind
13683 GeoLite2 Country database.
13685 o Minor features (guard nodes):
13686 - Reduce the time delay before saving guard status to disk from 10
13687 minutes to 30 seconds (or from one hour to 10 minutes if
13688 AvoidDiskWrites is set). Closes ticket 12485.
13690 o Minor features (hidden service):
13691 - Make Sybil attacks against hidden services harder by changing the
13692 minimum time required to get the HSDir flag from 25 hours up to 96
13693 hours. Addresses ticket 14149.
13694 - New option "HiddenServiceAllowUnknownPorts" to allow hidden
13695 services to disable the anti-scanning feature introduced in
13696 0.2.6.2-alpha. With this option not set, a connection to an
13697 unlisted port closes the circuit. With this option set, only a
13698 RELAY_DONE cell is sent. Closes ticket 14084.
13700 o Minor features (interface):
13701 - Implement "-f -" command-line option to read torrc configuration
13702 from standard input, if you don't want to store the torrc file in
13703 the file system. Implements feature 13865.
13705 o Minor features (logging):
13706 - Add a count of unique clients to the bridge heartbeat message.
13707 Resolves ticket 6852.
13708 - Suppress "router info incompatible with extra info" message when
13709 reading extrainfo documents from cache. (This message got loud
13710 around when we closed bug 9812 in 0.2.6.2-alpha.) Closes
13712 - Elevate hidden service authorized-client message from DEBUG to
13713 INFO. Closes ticket 14015.
13715 o Minor features (stability):
13716 - Add assertions in our hash-table iteration code to check for
13717 corrupted values that could cause infinite loops. Closes
13720 o Minor features (systemd):
13721 - Various improvements and modernizations in systemd hardening
13722 support. Closes ticket 13805. Patch from Craig Andrews.
13724 o Minor features (testing networks):
13725 - Drop the minimum RendPostPeriod on a testing network to 5 seconds,
13726 and the default on a testing network to 2 minutes. Drop the
13727 MIN_REND_INITIAL_POST_DELAY on a testing network to 5 seconds, but
13728 keep the default on a testing network at 30 seconds. This reduces
13729 HS bootstrap time to around 25 seconds. Also, change the default
13730 time in test-network.sh to match. Closes ticket 13401. Patch
13732 - Create TestingDirAuthVoteHSDir to correspond to
13733 TestingDirAuthVoteExit/Guard. Ensures that authorities vote the
13734 HSDir flag for the listed relays regardless of uptime or ORPort
13735 connectivity. Respects the value of VoteOnHidServDirectoriesV2.
13736 Partial implementation for ticket 14067. Patch by "teor".
13738 o Minor features (tor2web mode):
13739 - Introduce the config option Tor2webRendezvousPoints, which allows
13740 clients in Tor2webMode to select a specific Rendezvous Point to be
13741 used in HS circuits. This might allow better performance for
13742 Tor2Web nodes. Implements ticket 12844.
13744 o Minor bugfixes (client DNS):
13745 - Report the correct cached DNS expiration times on SOCKS port or in
13746 DNS replies. Previously, we would report everything as "never
13747 expires." Fixes bug 14193; bugfix on 0.2.3.17-beta.
13748 - Avoid a small memory leak when we find a cached answer for a
13749 reverse DNS lookup in a client-side DNS cache. (Remember, client-
13750 side DNS caching is off by default, and is not recommended.) Fixes
13751 bug 14259; bugfix on 0.2.0.1-alpha.
13753 o Minor bugfixes (client, automapping):
13754 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
13755 no value follows the option. Fixes bug 14142; bugfix on
13756 0.2.4.7-alpha. Patch by "teor".
13757 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
13758 14195; bugfix on 0.1.0.1-rc.
13759 - Prevent changes to other options from removing the wildcard value
13760 "." from "AutomapHostsSuffixes". Fixes bug 12509; bugfix
13762 - Allow MapAddress and AutomapHostsOnResolve to work together when
13763 an address is mapped into another address type (like .onion) that
13764 must be automapped at resolve time. Fixes bug 7555; bugfix
13767 o Minor bugfixes (client, bridges):
13768 - When we are using bridges and we had a network connectivity
13769 problem, only retry connecting to our currently configured
13770 bridges, not all bridges we know about and remember using. Fixes
13771 bug 14216; bugfix on 0.2.2.17-alpha.
13773 o Minor bugfixes (client, IPv6):
13774 - Reject socks requests to literal IPv6 addresses when IPv6Traffic
13775 flag is not set; and not because the NoIPv4Traffic flag was set.
13776 Previously we'd looked at the NoIPv4Traffic flag for both types of
13777 literal addresses. Fixes bug 14280; bugfix on 0.2.4.7-alpha.
13779 o Minor bugfixes (compilation):
13780 - The address of an array in the middle of a structure will always
13781 be non-NULL. clang recognises this and complains. Disable the
13782 tautologous and redundant check to silence this warning. Fixes bug
13783 14001; bugfix on 0.2.1.2-alpha.
13784 - Avoid warnings when building with systemd 209 or later. Fixes bug
13785 14072; bugfix on 0.2.6.2-alpha. Patch from "h.venev".
13786 - Compile correctly with (unreleased) OpenSSL 1.1.0 headers.
13787 Addresses ticket 14188.
13788 - Build without warnings with the stock OpenSSL srtp.h header, which
13789 has a duplicate declaration of SSL_get_selected_srtp_profile().
13790 Fixes bug 14220; this is OpenSSL's bug, not ours.
13791 - Do not compile any code related to Tor2Web mode when Tor2Web mode
13792 is not enabled at compile time. Previously, this code was included
13793 in a disabled state. See discussion on ticket 12844.
13794 - Remove the --disable-threads configure option again. It was
13795 accidentally partially reintroduced in 29ac883606d6d. Fixes bug
13796 14819; bugfix on 0.2.6.2-alpha.
13798 o Minor bugfixes (controller):
13799 - Report "down" in response to the "GETINFO entry-guards" command
13800 when relays are down with an unreachable_since value. Previously,
13801 we would report "up". Fixes bug 14184; bugfix on 0.1.2.2-alpha.
13802 - Avoid crashing on a malformed EXTENDCIRCUIT command. Fixes bug
13803 14116; bugfix on 0.2.2.9-alpha.
13804 - Add a code for the END_CIRC_REASON_IP_NOW_REDUNDANT circuit close
13805 reason. Fixes bug 14207; bugfix on 0.2.6.2-alpha.
13807 o Minor bugfixes (directory authority):
13808 - Allow directory authorities to fetch more data from one another if
13809 they find themselves missing lots of votes. Previously, they had
13810 been bumping against the 10 MB queued data limit. Fixes bug 14261;
13811 bugfix on 0.1.2.5-alpha.
13812 - Do not attempt to download extrainfo documents which we will be
13813 unable to validate with a matching server descriptor. Fixes bug
13814 13762; bugfix on 0.2.0.1-alpha.
13815 - Fix a bug that was truncating AUTHDIR_NEWDESC events sent to the
13816 control port. Fixes bug 14953; bugfix on 0.2.0.1-alpha.
13817 - Enlarge the buffer to read bwauth generated files to avoid an
13818 issue when parsing the file in dirserv_read_measured_bandwidths().
13819 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
13821 o Minor bugfixes (file handling):
13822 - Stop failing when key files are zero-length. Instead, generate new
13823 keys, and overwrite the empty key files. Fixes bug 13111; bugfix
13824 on all versions of Tor. Patch by "teor".
13825 - Stop generating a fresh .old RSA onion key file when the .old file
13826 is missing. Fixes part of 13111; bugfix on 0.0.6rc1.
13827 - Avoid overwriting .old key files with empty key files.
13828 - Skip loading zero-length extrainfo store, router store, stats,
13829 state, and key files.
13830 - Avoid crashing when trying to reload a torrc specified as a
13831 relative path with RunAsDaemon turned on. Fixes bug 13397; bugfix
13834 o Minor bugfixes (hidden services):
13835 - Close the introduction circuit when we have no more usable intro
13836 points, instead of waiting for it to time out. This also ensures
13837 that no follow-up HS descriptor fetch is triggered when the
13838 circuit eventually times out. Fixes bug 14224; bugfix on 0.0.6.
13839 - When fetching a hidden service descriptor for a down service that
13840 was recently up, do not keep refetching until we try the same
13841 replica twice in a row. Fixes bug 14219; bugfix on 0.2.0.10-alpha.
13842 - Successfully launch Tor with a nonexistent hidden service
13843 directory. Our fix for bug 13942 didn't catch this case. Fixes bug
13844 14106; bugfix on 0.2.6.2-alpha.
13846 o Minor bugfixes (logging):
13847 - Avoid crashing when there are more log domains than entries in
13848 domain_list. Bugfix on 0.2.3.1-alpha.
13849 - Add a string representation for LD_SCHED. Fixes bug 14740; bugfix
13851 - Don't log messages to stdout twice when starting up. Fixes bug
13852 13993; bugfix on 0.2.6.1-alpha.
13854 o Minor bugfixes (parsing):
13855 - Stop accepting milliseconds (or other junk) at the end of
13856 descriptor publication times. Fixes bug 9286; bugfix on 0.0.2pre25.
13857 - Support two-number and three-number version numbers correctly, in
13858 case we change the Tor versioning system in the future. Fixes bug
13859 13661; bugfix on 0.0.8pre1.
13861 o Minor bugfixes (path counting):
13862 - When deciding whether the consensus lists any exit nodes, count
13863 the number listed in the consensus, not the number we have
13864 descriptors for. Fixes part of bug 14918; bugfix on 0.2.6.2-alpha.
13865 - When deciding whether we have any exit nodes, only examine
13866 ExitNodes when the ExitNodes option is actually set. Fixes part of
13867 bug 14918; bugfix on 0.2.6.2-alpha.
13868 - Get rid of redundant and possibly scary warnings that we are
13869 missing directory information while we bootstrap. Fixes part of
13870 bug 14918; bugfix on 0.2.6.2-alpha.
13872 o Minor bugfixes (portability):
13873 - Fix the ioctl()-based network interface lookup code so that it
13874 will work on systems that have variable-length struct ifreq, for
13876 - Fix scheduler compilation on targets where char is unsigned. Fixes
13877 bug 14764; bugfix on 0.2.6.2-alpha. Reported by Christian Kujau.
13879 o Minor bugfixes (sandbox):
13880 - Allow glibc fatal errors to be sent to stderr before Tor exits.
13881 Previously, glibc would try to write them to /dev/tty, and the
13882 sandbox would trap the call and make Tor exit prematurely. Fixes
13883 bug 14759; bugfix on 0.2.5.1-alpha.
13885 o Minor bugfixes (shutdown):
13886 - When shutting down, always call event_del() on lingering read or
13887 write events before freeing them. Otherwise, we risk double-frees
13888 or read-after-frees in event_base_free(). Fixes bug 12985; bugfix
13891 o Minor bugfixes (small memory leaks):
13892 - Avoid leaking memory when using IPv6 virtual address mappings.
13893 Fixes bug 14123; bugfix on 0.2.4.7-alpha. Patch by Tom van
13896 o Minor bugfixes (statistics):
13897 - Increase period over which bandwidth observations are aggregated
13898 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
13900 o Minor bugfixes (systemd support):
13901 - Fix detection and operation of systemd watchdog. Fixes part of bug
13902 14141; bugfix on 0.2.6.2-alpha. Patch from Tomasz Torcz.
13903 - Run correctly under systemd with the RunAsDaemon option set. Fixes
13904 part of bug 14141; bugfix on 0.2.5.7-rc. Patch from Tomasz Torcz.
13905 - Inform the systemd supervisor about more changes in the Tor
13906 process status. Implements part of ticket 14141. Patch from
13908 - Cause the "--disable-systemd" option to actually disable systemd
13909 support. Fixes bug 14350; bugfix on 0.2.6.2-alpha. Patch
13912 o Minor bugfixes (TLS):
13913 - Check more thoroughly throughout the TLS code for possible
13914 unlogged TLS errors. Possible diagnostic or fix for bug 13319.
13916 o Minor bugfixes (transparent proxy):
13917 - Use getsockname, not getsockopt, to retrieve the address for a
13918 TPROXY-redirected connection. Fixes bug 13796; bugfix
13921 o Code simplification and refactoring:
13922 - Move fields related to isolating and configuring client ports into
13923 a shared structure. Previously, they were duplicated across
13924 port_cfg_t, listener_connection_t, and edge_connection_t. Failure
13925 to copy them correctly had been the cause of at least one bug in
13926 the past. Closes ticket 8546.
13927 - Refactor the get_interface_addresses_raw() doom-function into
13928 multiple smaller and simpler subfunctions. Cover the resulting
13929 subfunctions with unit-tests. Fixes a significant portion of
13931 - Remove workaround in dirserv_thinks_router_is_hs_dir() that was
13932 only for version <= 0.2.2.24 which is now deprecated. Closes
13934 - Remove a test for a long-defunct broken version-one
13938 - Adding section on OpenBSD to our TUNING document. Thanks to mmcc
13939 for writing the OpenBSD-specific tips. Resolves ticket 13702.
13940 - Make the tor-resolve documentation match its help string and its
13941 options. Resolves part of ticket 14325.
13942 - Log a more useful error message from tor-resolve when failing to
13943 look up a hidden service address. Resolves part of ticket 14325.
13945 o Downgraded warnings:
13946 - Don't warn when we've attempted to contact a relay using the wrong
13947 ntor onion key. Closes ticket 9635.
13949 o Removed features:
13950 - To avoid confusion with the "ExitRelay" option, "ExitNode" is no
13951 longer silently accepted as an alias for "ExitNodes".
13952 - The --enable-mempool and --enable-buf-freelists options, which
13953 were originally created to work around bad malloc implementations,
13954 no longer exist. They were off-by-default in 0.2.5. Closes
13958 - Make the checkdir/perms test complete successfully even if the
13959 global umask is not 022. Fixes bug 14215; bugfix on 0.2.6.2-alpha.
13960 - Test that tor does not fail when key files are zero-length. Check
13961 that tor generates new keys, and overwrites the empty key files.
13962 - Test that tor generates new keys when keys are missing
13963 (existing behavior).
13964 - Test that tor does not overwrite key files that already contain
13965 data (existing behavior). Tests bug 13111. Patch by "teor".
13966 - New "make test-stem" target to run stem integration tests.
13967 Requires that the "STEM_SOURCE_DIR" environment variable be set.
13968 Closes ticket 14107.
13969 - Make the test_cmdline_args.py script work correctly on Windows.
13970 Patch from Gisle Vanem.
13971 - Move the slower unit tests into a new "./src/test/test-slow"
13972 binary that can be run independently of the other tests. Closes
13974 - Avoid undefined behavior when sampling huge values from the
13975 Laplace distribution. This made unittests fail on Raspberry Pi.
13976 Bug found by Device. Fixes bug 14090; bugfix on 0.2.6.2-alpha.
13979 Changes in version 0.2.6.2-alpha - 2014-12-31
13980 Tor 0.2.6.2-alpha is the second alpha release in the 0.2.6.x series.
13981 It introduces a major new backend for deciding when to send cells on
13982 channels, which should lead down the road to big performance
13983 increases. It contains security and statistics features for better
13984 work on hidden services, and numerous bugfixes.
13986 This release contains many new unit tests, along with major
13987 performance improvements for running testing networks using Chutney.
13988 Thanks to a series of patches contributed by "teor", testing networks
13989 should now bootstrap in seconds, rather than minutes.
13991 o Major features (relay, infrastructure):
13992 - Complete revision of the code that relays use to decide which cell
13993 to send next. Formerly, we selected the best circuit to write on
13994 each channel, but we didn't select among channels in any
13995 sophisticated way. Now, we choose the best circuits globally from
13996 among those whose channels are ready to deliver traffic.
13998 This patch implements a new inter-cmux comparison API, a global
13999 high/low watermark mechanism and a global scheduler loop for
14000 transmission prioritization across all channels as well as among
14001 circuits on one channel. This schedule is currently tuned to
14002 (tolerantly) avoid making changes in network performance, but it
14003 should form the basis for major circuit performance increases in
14004 the future. Code by Andrea; tuning by Rob Jansen; implements
14007 o Major features (hidden services):
14008 - Make HS port scanning more difficult by immediately closing the
14009 circuit when a user attempts to connect to a nonexistent port.
14010 Closes ticket 13667.
14011 - Add a HiddenServiceStatistics option that allows Tor relays to
14012 gather and publish statistics about the overall size and volume of
14013 hidden service usage. Specifically, when this option is turned on,
14014 an HSDir will publish an approximate number of hidden services
14015 that have published descriptors to it the past 24 hours. Also, if
14016 a relay has acted as a hidden service rendezvous point, it will
14017 publish the approximate amount of rendezvous cells it has relayed
14018 the past 24 hours. The statistics themselves are obfuscated so
14019 that the exact values cannot be derived. For more details see
14020 proposal 238, "Better hidden service stats from Tor relays". This
14021 feature is currently disabled by default. Implements feature 13192.
14023 o Major bugfixes (client, automap):
14024 - Repair automapping with IPv6 addresses. This automapping should
14025 have worked previously, but one piece of debugging code that we
14026 inserted to detect a regression actually caused the regression to
14027 manifest itself again. Fixes bug 13811 and bug 12831; bugfix on
14028 0.2.4.7-alpha. Diagnosed and fixed by Francisco Blas
14031 o Major bugfixes (hidden services):
14032 - When closing an introduction circuit that was opened in parallel
14033 with others, don't mark the introduction point as unreachable.
14034 Previously, the first successful connection to an introduction
14035 point would make the other introduction points get marked as
14036 having timed out. Fixes bug 13698; bugfix on 0.0.6rc2.
14038 o Directory authority changes:
14039 - Remove turtles as a directory authority.
14040 - Add longclaw as a new (v3) directory authority. This implements
14041 ticket 13296. This keeps the directory authority count at 9.
14043 o Major removed features:
14044 - Tor clients no longer support connecting to hidden services
14045 running on Tor 0.2.2.x and earlier; the Support022HiddenServices
14046 option has been removed. (There shouldn't be any hidden services
14047 running these versions on the network.) Closes ticket 7803.
14049 o Minor features (client):
14050 - Validate hostnames in SOCKS5 requests more strictly. If SafeSocks
14051 is enabled, reject requests with IP addresses as hostnames.
14052 Resolves ticket 13315.
14054 o Minor features (controller):
14055 - Add a "SIGNAL HEARTBEAT" controller command that tells Tor to
14056 write an unscheduled heartbeat message to the log. Implements
14059 o Minor features (geoip):
14060 - Update geoip and geoip6 to the November 15 2014 Maxmind GeoLite2
14063 o Minor features (hidden services):
14064 - When re-enabling the network, don't try to build introduction
14065 circuits until we have successfully built a circuit. This makes
14066 hidden services come up faster when the network is re-enabled.
14067 Patch from "akwizgran". Closes ticket 13447.
14068 - When we fail to retrieve a hidden service descriptor, send the
14069 controller an "HS_DESC FAILED" controller event. Implements
14071 - New HiddenServiceDirGroupReadable option to cause hidden service
14072 directories and hostname files to be created group-readable. Patch
14073 from "anon", David Stainton, and "meejah". Closes ticket 11291.
14075 o Minor features (systemd):
14076 - Where supported, when running with systemd, report successful
14077 startup to systemd. Part of ticket 11016. Patch by Michael Scherer.
14078 - When running with systemd, support systemd watchdog messages. Part
14079 of ticket 11016. Patch by Michael Scherer.
14081 o Minor features (transparent proxy):
14082 - Update the transparent proxy option checks to allow for both ipfw
14083 and pf on OS X. Closes ticket 14002.
14084 - Use the correct option when using IPv6 with transparent proxy
14085 support on Linux. Resolves 13808. Patch by Francisco Blas
14088 o Minor bugfixes (preventative security, C safety):
14089 - When reading a hexadecimal, base-32, or base-64 encoded value from
14090 a string, always overwrite the whole output buffer. This prevents
14091 some bugs where we would look at (but fortunately, not reveal)
14092 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
14094 - Clear all memory targeted by tor_addr_{to,from}_sockaddr(), not
14095 just the part that's used. This makes it harder for data leak bugs
14096 to occur in the event of other programming failures. Resolves
14099 o Minor bugfixes (client, microdescriptors):
14100 - Use a full 256 bits of the SHA256 digest of a microdescriptor when
14101 computing which microdescriptors to download. This keeps us from
14102 erroneous download behavior if two microdescriptor digests ever
14103 have the same first 160 bits. Fixes part of bug 13399; bugfix
14105 - Reset a router's status if its microdescriptor digest changes,
14106 even if the first 160 bits remain the same. Fixes part of bug
14107 13399; bugfix on 0.2.3.1-alpha.
14109 o Minor bugfixes (compilation):
14110 - Silence clang warnings under --enable-expensive-hardening,
14111 including implicit truncation of 64 bit values to 32 bit, const
14112 char assignment to self, tautological compare, and additional
14113 parentheses around equality tests. Fixes bug 13577; bugfix
14115 - Fix a clang warning about checking whether an address in the
14116 middle of a structure is NULL. Fixes bug 14001; bugfix
14119 o Minor bugfixes (hidden services):
14120 - Correctly send a controller event when we find that a rendezvous
14121 circuit has finished. Fixes bug 13936; bugfix on 0.1.1.5-alpha.
14122 - Pre-check directory permissions for new hidden-services to avoid
14123 at least one case of "Bug: Acting on config options left us in a
14124 broken state. Dying." Fixes bug 13942; bugfix on 0.0.6pre1.
14125 - When adding a new hidden service (for example, via SETCONF), Tor
14126 no longer congratulates the user for running a relay. Fixes bug
14127 13941; bugfix on 0.2.6.1-alpha.
14128 - When fetching hidden service descriptors, we now check not only
14129 for whether we got the hidden service we had in mind, but also
14130 whether we got the particular descriptors we wanted. This prevents
14131 a class of inefficient but annoying DoS attacks by hidden service
14132 directories. Fixes bug 13214; bugfix on 0.2.1.6-alpha. Reported
14135 o Minor bugfixes (Linux seccomp2 sandbox):
14136 - Make transparent proxy support work along with the seccomp2
14137 sandbox. Fixes part of bug 13808; bugfix on 0.2.5.1-alpha. Patch
14138 by Francisco Blas Izquierdo Riera.
14139 - Fix a memory leak in tor-resolve when running with the sandbox
14140 enabled. Fixes bug 14050; bugfix on 0.2.5.9-rc.
14142 o Minor bugfixes (logging):
14143 - Downgrade warnings about RSA signature failures to info log level.
14144 Emit a warning when an extra info document is found incompatible
14145 with a corresponding router descriptor. Fixes bug 9812; bugfix
14147 - Make connection_ap_handshake_attach_circuit() log the circuit ID
14148 correctly. Fixes bug 13701; bugfix on 0.0.6.
14150 o Minor bugfixes (misc):
14151 - Stop allowing invalid address patterns like "*/24" that contain
14152 both a wildcard address and a bit prefix length. This affects all
14153 our address-range parsing code. Fixes bug 7484; bugfix
14156 o Minor bugfixes (testing networks, fast startup):
14157 - Allow Tor to build circuits using a consensus with no exits. If
14158 the consensus has no exits (typical of a bootstrapping test
14159 network), allow Tor to build circuits once enough descriptors have
14160 been downloaded. This assists in bootstrapping a testing Tor
14161 network. Fixes bug 13718; bugfix on 0.2.4.10-alpha. Patch
14163 - When V3AuthVotingInterval is low, give a lower If-Modified-Since
14164 header to directory servers. This allows us to obtain consensuses
14165 promptly when the consensus interval is very short. This assists
14166 in bootstrapping a testing Tor network. Fixes parts of bugs 13718
14167 and 13963; bugfix on 0.2.0.3-alpha. Patch by "teor".
14168 - Stop assuming that private addresses are local when checking
14169 reachability in a TestingTorNetwork. Instead, when testing, assume
14170 all OR connections are remote. (This is necessary due to many test
14171 scenarios running all relays on localhost.) This assists in
14172 bootstrapping a testing Tor network. Fixes bug 13924; bugfix on
14173 0.1.0.1-rc. Patch by "teor".
14174 - Avoid building exit circuits from a consensus with no exits. Now
14175 thanks to our fix for 13718, we accept a no-exit network as not
14176 wholly lost, but we need to remember not to try to build exit
14177 circuits on it. Closes ticket 13814; patch by "teor".
14178 - Stop requiring exits to have non-zero bandwithcapacity in a
14179 TestingTorNetwork. Instead, when TestingMinExitFlagThreshold is 0,
14180 ignore exit bandwidthcapacity. This assists in bootstrapping a
14181 testing Tor network. Fixes parts of bugs 13718 and 13839; bugfix
14182 on 0.2.0.3-alpha. Patch by "teor".
14183 - Add "internal" to some bootstrap statuses when no exits are
14184 available. If the consensus does not contain Exits, Tor will only
14185 build internal circuits. In this case, relevant statuses will
14186 contain the word "internal" as indicated in the Tor control-
14187 spec.txt. When bootstrap completes, Tor will be ready to build
14188 internal circuits. If a future consensus contains Exits, exit
14189 circuits may become available. Fixes part of bug 13718; bugfix on
14190 0.2.4.10-alpha. Patch by "teor".
14191 - Decrease minimum consensus interval to 10 seconds when
14192 TestingTorNetwork is set, or 5 seconds for the first consensus.
14193 Fix assumptions throughout the code that assume larger intervals.
14194 Fixes bugs 13718 and 13823; bugfix on 0.2.0.3-alpha. Patch
14196 - Avoid excluding guards from path building in minimal test
14197 networks, when we're in a test network and excluding guards would
14198 exclude all relays. This typically occurs in incredibly small tor
14199 networks, and those using "TestingAuthVoteGuard *". Fixes part of
14200 bug 13718; bugfix on 0.1.1.11-alpha. Patch by "teor".
14202 o Code simplification and refactoring:
14203 - Stop using can_complete_circuits as a global variable; access it
14204 with a function instead.
14205 - Avoid using operators directly as macro arguments: this lets us
14206 apply coccinelle transformations to our codebase more directly.
14207 Closes ticket 13172.
14208 - Combine the functions used to parse ClientTransportPlugin and
14209 ServerTransportPlugin into a single function. Closes ticket 6456.
14210 - Add inline functions and convenience macros for inspecting channel
14211 state. Refactor the code to use convenience macros instead of
14212 checking channel state directly. Fixes issue 7356.
14213 - Document all members of was_router_added_t and rename
14214 ROUTER_WAS_NOT_NEW to ROUTER_IS_ALREADY_KNOWN to make it less
14215 confusable with ROUTER_WAS_TOO_OLD. Fixes issue 13644.
14216 - In connection_exit_begin_conn(), use END_CIRC_REASON_TORPROTOCOL
14217 constant instead of hardcoded value. Fixes issue 13840.
14218 - Refactor our generic strmap and digestmap types into a single
14219 implementation, so that we can add a new digest256map
14223 - Document the bridge-authority-only 'networkstatus-bridges' file.
14224 Closes ticket 13713; patch from "tom".
14225 - Fix typo in PredictedPortsRelevanceTime option description in
14226 manpage. Resolves issue 13707.
14227 - Stop suggesting that users specify relays by nickname: it isn't a
14228 good idea. Also, properly cross-reference how to specify relays in
14229 all parts of manual documenting options that take a list of
14230 relays. Closes ticket 13381.
14231 - Clarify the HiddenServiceDir option description in manpage to make
14232 it clear that relative paths are taken with respect to the current
14233 working directory. Also clarify that this behavior is not
14234 guaranteed to remain indefinitely. Fixes issue 13913.
14237 - New tests for many parts of channel, relay, and circuitmux
14238 functionality. Code by Andrea; part of 9262.
14239 - New tests for parse_transport_line(). Part of ticket 6456.
14240 - In the unit tests, use chgrp() to change the group of the unit
14241 test temporary directory to the current user, so that the sticky
14242 bit doesn't interfere with tests that check directory groups.
14244 - Add unit tests for resolve_my_addr(). Part of ticket 12376; patch
14248 Changes in version 0.2.6.1-alpha - 2014-10-30
14249 Tor 0.2.6.1-alpha is the first release in the Tor 0.2.6.x series. It
14250 includes numerous code cleanups and new tests, and fixes a large
14251 number of annoying bugs. Out-of-memory conditions are handled better
14252 than in 0.2.5, pluggable transports have improved proxy support, and
14253 clients now use optimistic data for contacting hidden services. Also,
14254 we are now more robust to changes in what we consider a parseable
14255 directory object, so that tightening restrictions does not have a risk
14256 of introducing infinite download loops.
14258 This is the first alpha release in a new series, so expect there to be
14259 bugs. Users who would rather test out a more stable branch should stay
14260 with 0.2.5.x for now.
14262 o New compiler and system requirements:
14263 - Tor 0.2.6.x requires that your compiler support more of the C99
14264 language standard than before. The 'configure' script now detects
14265 whether your compiler supports C99 mid-block declarations and
14266 designated initializers. If it does not, Tor will not compile.
14268 We may revisit this requirement if it turns out that a significant
14269 number of people need to build Tor with compilers that don't
14270 bother implementing a 15-year-old standard. Closes ticket 13233.
14271 - Tor no longer supports systems without threading support. When we
14272 began working on Tor, there were several systems that didn't have
14273 threads, or where the thread support wasn't able to run the
14274 threads of a single process on multiple CPUs. That no longer
14275 holds: every system where Tor needs to run well now has threading
14276 support. Resolves ticket 12439.
14278 o Removed platform support:
14279 - We no longer include special code to build on Windows CE; as far
14280 as we know, nobody has used Tor on Windows CE in a very long time.
14281 Closes ticket 11446.
14283 o Major features (bridges):
14284 - Expose the outgoing upstream HTTP/SOCKS proxy to pluggable
14285 transports if they are configured via the "TOR_PT_PROXY"
14286 environment variable. Implements proposal 232. Resolves
14289 o Major features (client performance, hidden services):
14290 - Allow clients to use optimistic data when connecting to a hidden
14291 service, which should remove a round-trip from hidden service
14292 initialization. See proposal 181 for details. Implements
14295 o Major features (directory system):
14296 - Upon receiving an unparseable directory object, if its digest
14297 matches what we expected, then don't try to download it again.
14298 Previously, when we got a descriptor we didn't like, we would keep
14299 trying to download it over and over. Closes ticket 11243.
14301 o Major features (sample torrc):
14302 - Add a new, infrequently-changed "torrc.minimal". This file is
14303 similar to torrc.sample, but it will change as infrequently as
14304 possible, for the benefit of users whose systems prompt them for
14305 intervention whenever a default configuration file is changed.
14306 Making this change allows us to update torrc.sample to be a more
14307 generally useful "sample torrc".
14309 o Major bugfixes (directory authorities):
14310 - Do not assign the HSDir flag to relays if they are not Valid, or
14311 currently hibernating. Fixes 12573; bugfix on 0.2.0.10-alpha.
14313 o Major bugfixes (directory bandwidth performance):
14314 - Don't flush the zlib buffer aggressively when compressing
14315 directory information for clients. This should save about 7% of
14316 the bandwidth currently used for compressed descriptors and
14317 microdescriptors. Fixes bug 11787; bugfix on 0.1.1.23.
14319 o Minor features (security, memory wiping):
14320 - Ensure we securely wipe keys from memory after
14321 crypto_digest_get_digest and init_curve25519_keypair_from_file
14322 have finished using them. Resolves ticket 13477.
14324 o Minor features (security, out-of-memory handling):
14325 - When handling an out-of-memory condition, allocate less memory for
14326 temporary data structures. Fixes issue 10115.
14327 - When handling an out-of-memory condition, consider more types of
14328 buffers, including those on directory connections, and zlib
14329 buffers. Resolves ticket 11792.
14332 - When identity keypair is generated for first time, log a
14333 congratulatory message that links to the new relay lifecycle
14334 document. Implements feature 10427.
14336 o Minor features (client):
14337 - Clients are now willing to send optimistic data (before they
14338 receive a 'connected' cell) to relays of any version. (Relays
14339 without support for optimistic data are no longer supported on the
14340 Tor network.) Resolves ticket 13153.
14342 o Minor features (directory authorities):
14343 - Don't list relays with a bandwidth estimate of 0 in the consensus.
14344 Implements a feature proposed during discussion of bug 13000.
14345 - In tor-gencert, report an error if the user provides the same
14346 argument more than once.
14347 - If a directory authority can't find a best consensus method in the
14348 votes that it holds, it now falls back to its favorite consensus
14349 method. Previously, it fell back to method 1. Neither of these is
14350 likely to get enough signatures, but "fall back to favorite"
14351 doesn't require us to maintain support an obsolete consensus
14352 method. Implements part of proposal 215.
14354 o Minor features (logging):
14355 - On Unix-like systems, you can now use named pipes as the target of
14356 the Log option, and other options that try to append to files.
14357 Closes ticket 12061. Patch from "carlo von lynX".
14358 - When opening a log file at startup, send it every log message that
14359 we generated between startup and opening it. Previously, log
14360 messages that were generated before opening the log file were only
14361 logged to stdout. Closes ticket 6938.
14362 - Add a TruncateLogFile option to overwrite logs instead of
14363 appending to them. Closes ticket 5583.
14365 o Minor features (portability, Solaris):
14366 - Threads are no longer disabled by default on Solaris; we believe
14367 that the versions of Solaris with broken threading support are all
14368 obsolete by now. Resolves ticket 9495.
14370 o Minor features (relay):
14371 - Re-check our address after we detect a changed IP address from
14372 getsockname(). This ensures that the controller command "GETINFO
14373 address" will report the correct value. Resolves ticket 11582.
14375 - A new AccountingRule option lets Relays set whether they'd like
14376 AccountingMax to be applied separately to inbound and outbound
14377 traffic, or applied to the sum of inbound and outbound traffic.
14378 Resolves ticket 961. Patch by "chobe".
14380 o Minor features (testing networks):
14381 - Add the TestingDirAuthVoteExit option, which lists nodes to assign
14382 the "Exit" flag regardless of their uptime, bandwidth, or exit
14383 policy. TestingTorNetwork must be set for this option to have any
14384 effect. Previously, authorities would take up to 35 minutes to
14385 give nodes the Exit flag in a test network. Partially implements
14388 o Minor features (validation):
14389 - Check all date/time values passed to tor_timegm and
14390 parse_rfc1123_time for validity, taking leap years into account.
14391 Improves HTTP header validation. Implemented with bug 13476.
14392 - In correct_tm(), limit the range of values returned by system
14393 localtime(_r) and gmtime(_r) to be between the years 1 and 8099.
14394 This means we don't have to deal with negative or too large dates,
14395 even if a clock is wrong. Otherwise we might fail to read a file
14396 written by us which includes such a date. Fixes bug 13476.
14398 o Minor bugfixes (bridge clients):
14399 - When configured to use a bridge without an identity digest (not
14400 recommended), avoid launching an extra channel to it when
14401 bootstrapping. Fixes bug 7733; bugfix on 0.2.4.4-alpha.
14403 o Minor bugfixes (bridges):
14404 - When DisableNetwork is set, do not launch pluggable transport
14405 plugins, and if any are running, terminate them. Fixes bug 13213;
14406 bugfix on 0.2.3.6-alpha.
14408 o Minor bugfixes (C correctness):
14409 - Fix several instances of possible integer overflow/underflow/NaN.
14410 Fixes bug 13104; bugfix on 0.2.3.1-alpha and later. Patches
14412 - In circuit_build_times_calculate_timeout() in circuitstats.c,
14413 avoid dividing by zero in the pareto calculations. This traps
14414 under clang's "undefined-trap" sanitizer. Fixes bug 13290; bugfix
14416 - Fix an integer overflow in format_time_interval(). Fixes bug
14417 13393; bugfix on 0.2.0.10-alpha.
14418 - Set the correct day of year value when the system's localtime(_r)
14419 or gmtime(_r) functions fail to set struct tm. Not externally
14420 visible. Fixes bug 13476; bugfix on 0.0.2pre14.
14421 - Avoid unlikely signed integer overflow in tor_timegm on systems
14422 with 32-bit time_t. Fixes bug 13476; bugfix on 0.0.2pre14.
14424 o Minor bugfixes (client):
14425 - Fix smartlist_choose_node_by_bandwidth() so that relays with the
14426 BadExit flag are not considered worthy candidates. Fixes bug
14427 13066; bugfix on 0.1.2.3-alpha.
14428 - Use the consensus schedule for downloading consensuses, and not
14429 the generic schedule. Fixes bug 11679; bugfix on 0.2.2.6-alpha.
14430 - Handle unsupported or malformed SOCKS5 requests properly by
14431 responding with the appropriate error message before closing the
14432 connection. Fixes bugs 12971 and 13314; bugfix on 0.0.2pre13.
14434 o Minor bugfixes (client, torrc):
14435 - Stop modifying the value of our DirReqStatistics torrc option just
14436 because we're not a bridge or relay. This bug was causing Tor
14437 Browser users to write "DirReqStatistics 0" in their torrc files
14438 as if they had chosen to change the config. Fixes bug 4244; bugfix
14440 - When GeoIPExcludeUnknown is enabled, do not incorrectly decide
14441 that our options have changed every time we SIGHUP. Fixes bug
14442 9801; bugfix on 0.2.4.10-alpha. Patch from "qwerty1".
14444 o Minor bugfixes (controller):
14445 - Return an error when the second or later arguments of the
14446 "setevents" controller command are invalid events. Previously we
14447 would return success while silently skipping invalid events. Fixes
14448 bug 13205; bugfix on 0.2.3.2-alpha. Reported by "fpxnns".
14450 o Minor bugfixes (directory system):
14451 - Always believe that v3 directory authorities serve extra-info
14452 documents, whether they advertise "caches-extra-info" or not.
14453 Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
14454 - When running as a v3 directory authority, advertise that you serve
14455 extra-info documents so that clients who want them can find them
14456 from you too. Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
14457 - Check the BRIDGE_DIRINFO flag bitwise rather than using equality.
14458 Previously, directories offering BRIDGE_DIRINFO and some other
14459 flag (i.e. microdescriptors or extrainfo) would be ignored when
14460 looking for bridges. Partially fixes bug 13163; bugfix
14463 o Minor bugfixes (networking):
14464 - Check for orconns and use connection_or_close_for_error() rather
14465 than connection_mark_for_close() directly in the getsockopt()
14466 failure case of connection_handle_write_impl(). Fixes bug 11302;
14467 bugfix on 0.2.4.4-alpha.
14469 o Minor bugfixes (relay):
14470 - When generating our family list, remove spaces from around the
14471 entries. Fixes bug 12728; bugfix on 0.2.1.7-alpha.
14472 - If our previous bandwidth estimate was 0 bytes, allow publishing a
14473 new relay descriptor immediately. Fixes bug 13000; bugfix
14476 o Minor bugfixes (testing networks):
14477 - Fix TestingDirAuthVoteGuard to properly give out Guard flags in a
14478 testing network. Fixes bug 13064; bugfix on 0.2.5.2-alpha.
14479 - Stop using the default authorities in networks which provide both
14480 AlternateDirAuthority and AlternateBridgeAuthority. Partially
14481 fixes bug 13163; bugfix on 0.2.0.13-alpha.
14483 o Minor bugfixes (testing):
14484 - Stop spawn test failures due to a race condition between the
14485 SIGCHLD handler updating the process status, and the test reading
14486 it. Fixes bug 13291; bugfix on 0.2.3.3-alpha.
14488 o Minor bugfixes (testing, Windows):
14489 - Avoid passing an extra backslash when creating a temporary
14490 directory for running the unit tests on Windows. Fixes bug 12392;
14491 bugfix on 0.2.2.25-alpha. Patch from Gisle Vanem.
14493 o Minor bugfixes (windows):
14494 - Remove code to special-case handling of NTE_BAD_KEYSET when
14495 acquiring windows CryptoAPI context. This error can't actually
14496 occur for the parameters we're providing. Fixes bug 10816; bugfix
14499 o Minor bugfixes (zlib):
14500 - Avoid truncating a zlib stream when trying to finalize it with an
14501 empty output buffer. Fixes bug 11824; bugfix on 0.1.1.23.
14504 - Allow our configure script to build correctly with autoconf 2.62
14505 again. Fixes bug 12693; bugfix on 0.2.5.2-alpha.
14506 - Improve the error message from ./configure to make it clear that
14507 when asciidoc has not been found, the user will have to either add
14508 --disable-asciidoc argument or install asciidoc. Resolves
14511 o Code simplification and refactoring:
14512 - Change the entry_is_live() function to take named bitfield
14513 elements instead of an unnamed list of booleans. Closes
14515 - Refactor and unit-test entry_is_time_to_retry() in entrynodes.c.
14516 Resolves ticket 12205.
14517 - Use calloc and reallocarray functions instead of multiply-
14518 then-malloc. This makes it less likely for us to fall victim to an
14519 integer overflow attack when allocating. Resolves ticket 12855.
14520 - Use the standard macro name SIZE_MAX, instead of our
14522 - Document usage of the NO_DIRINFO and ALL_DIRINFO flags clearly in
14523 functions which take them as arguments. Replace 0 with NO_DIRINFO
14524 in a function call for clarity. Seeks to prevent future issues
14526 - Avoid 4 null pointer errors under clang static analysis by using
14527 tor_assert() to prove that the pointers aren't null. Fixes
14529 - Rework the API of policies_parse_exit_policy() to use a bitmask to
14530 represent parsing options, instead of a confusing mess of
14531 booleans. Resolves ticket 8197.
14532 - Introduce a helper function to parse ExitPolicy in
14533 or_options_t structure.
14536 - Add a doc/TUNING document with tips for handling large numbers of
14537 TCP connections when running busy Tor relay. Update the warning
14538 message to point to this file when running out of sockets
14539 operating system is allowing to use simultaneously. Resolves
14542 o Removed features:
14543 - We no longer remind the user about configuration options that have
14544 been obsolete since 0.2.3.x or earlier. Patch by Adrien Bak.
14545 - Remove our old, non-weighted bandwidth-based node selection code.
14546 Previously, we used it as a fallback when we couldn't perform
14547 weighted bandwidth-based node selection. But that would only
14548 happen in the cases where we had no consensus, or when we had a
14549 consensus generated by buggy or ancient directory authorities. In
14550 either case, it's better to use the more modern, better maintained
14551 algorithm, with reasonable defaults for the weights. Closes
14553 - Remove the --disable-curve25519 configure option. Relays and
14554 clients now are required to support curve25519 and the
14556 - The old "StrictEntryNodes" and "StrictExitNodes" options, which
14557 used to be deprecated synonyms for "StrictNodes", are now marked
14558 obsolete. Resolves ticket 12226.
14559 - Clients don't understand the BadDirectory flag in the consensus
14560 anymore, and ignore it.
14563 - Refactor the function that chooses guard nodes so that it can more
14564 easily be tested; write some tests for it.
14565 - Fix and re-enable the fgets_eagain unit test. Fixes bug 12503;
14566 bugfix on 0.2.3.1-alpha. Patch from "cypherpunks."
14567 - Create unit tests for format_time_interval(). With bug 13393.
14568 - Add unit tests for tor_timegm signed overflow, tor_timegm and
14569 parse_rfc1123_time validity checks, correct_tm year clamping. Unit
14570 tests (visible) fixes in bug 13476.
14571 - Add a "coverage-html" make target to generate HTML-visualized
14572 coverage results when building with --enable-coverage. (Requires
14573 lcov.) Patch from Kevin Murray.
14574 - Enable the backtrace handler (where supported) when running the
14576 - Revise all unit tests that used the legacy test_* macros to
14577 instead use the recommended tt_* macros. This patch was generated
14578 with coccinelle, to avoid manual errors. Closes ticket 13119.
14580 o Distribution (systemd):
14581 - systemd unit file: only allow tor to write to /var/lib/tor and
14582 /var/log/tor. The rest of the filesystem is accessible for reading
14583 only. Patch by intrigeri; resolves ticket 12751.
14584 - systemd unit file: ensure that the process and all its children
14585 can never gain new privileges. Patch by intrigeri; resolves
14587 - systemd unit file: set up /var/run/tor as writable for the Tor
14588 service. Patch by intrigeri; resolves ticket 13196.
14590 o Removed features (directory authorities):
14591 - Remove code that prevented authorities from listing Tor relays
14592 affected by CVE-2011-2769 as guards. These relays are already
14593 rejected altogether due to the minimum version requirement of
14594 0.2.3.16-alpha. Closes ticket 13152.
14595 - The "AuthDirRejectUnlisted" option no longer has any effect, as
14596 the fingerprints file (approved-routers) has been deprecated.
14597 - Directory authorities do not support being Naming dirauths anymore.
14598 The "NamingAuthoritativeDir" config option is now obsolete.
14599 - Directory authorities do not support giving out the BadDirectory
14601 - Directory authorities no longer advertise or support consensus
14602 methods 1 through 12 inclusive. These consensus methods were
14603 obsolete and/or insecure: maintaining the ability to support them
14604 served no good purpose. Implements part of proposal 215; closes
14607 o Testing (test-network.sh):
14608 - Stop using "echo -n", as some shells' built-in echo doesn't
14609 support "-n". Instead, use "/bin/echo -n". Partially fixes
14611 - Stop an apparent test-network hang when used with make -j2. Fixes
14613 - Add a --delay option to test-network.sh, which configures the
14614 delay before the chutney network tests for data transmission.
14615 Partially implements ticket 13161.
14618 Changes in version 0.2.5.10 - 2014-10-24
14619 Tor 0.2.5.10 is the first stable release in the 0.2.5 series.
14621 It adds several new security features, including improved
14622 denial-of-service resistance for relays, new compiler hardening
14623 options, and a system-call sandbox for hardened installations on Linux
14624 (requires seccomp2). The controller protocol has several new features,
14625 resolving IPv6 addresses should work better than before, and relays
14626 should be a little more CPU-efficient. We've added support for more
14627 OpenBSD and FreeBSD transparent proxy types. We've improved the build
14628 system and testing infrastructure to allow unit testing of more parts
14629 of the Tor codebase. Finally, we've addressed several nagging pluggable
14630 transport usability issues, and included numerous other small bugfixes
14631 and features mentioned below.
14633 This release marks end-of-life for Tor 0.2.3.x; those Tor versions
14634 have accumulated many known flaws; everyone should upgrade.
14636 o Deprecated versions:
14637 - Tor 0.2.3.x has reached end-of-life; it has received no patches or
14638 attention for some while.
14641 Changes in version 0.2.5.9-rc - 2014-10-20
14642 Tor 0.2.5.9-rc is the third release candidate for the Tor 0.2.5.x
14643 series. It disables SSL3 in response to the recent "POODLE" attack
14644 (even though POODLE does not affect Tor). It also works around a crash
14645 bug caused by some operating systems' response to the "POODLE" attack
14646 (which does affect Tor). It also contains a few miscellaneous fixes.
14648 o Major security fixes:
14649 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
14650 today support TLS 1.0 or later, so we can safely turn off support
14651 for this old (and insecure) protocol. Fixes bug 13426.
14653 o Major bugfixes (openssl bug workaround):
14654 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
14655 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
14656 13471. This is a workaround for an OpenSSL bug.
14659 - Disable the sandbox name resolver cache when running tor-resolve:
14660 tor-resolve doesn't use the sandbox code, and turning it on was
14661 breaking attempts to do tor-resolve on a non-default server on
14662 Linux. Fixes bug 13295; bugfix on 0.2.5.3-alpha.
14664 o Compilation fixes:
14665 - Build and run correctly on systems like OpenBSD-current that have
14666 patched OpenSSL to remove get_cipher_by_char and/or its
14667 implementations. Fixes issue 13325.
14669 o Downgraded warnings:
14670 - Downgrade the severity of the 'unexpected sendme cell from client'
14671 from 'warn' to 'protocol warning'. Closes ticket 8093.
14674 Changes in version 0.2.4.25 - 2014-10-20
14675 Tor 0.2.4.25 disables SSL3 in response to the recent "POODLE" attack
14676 (even though POODLE does not affect Tor). It also works around a crash
14677 bug caused by some operating systems' response to the "POODLE" attack
14678 (which does affect Tor).
14680 o Major security fixes (also in 0.2.5.9-rc):
14681 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
14682 today support TLS 1.0 or later, so we can safely turn off support
14683 for this old (and insecure) protocol. Fixes bug 13426.
14685 o Major bugfixes (openssl bug workaround, also in 0.2.5.9-rc):
14686 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
14687 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
14688 13471. This is a workaround for an OpenSSL bug.
14691 Changes in version 0.2.5.8-rc - 2014-09-22
14692 Tor 0.2.5.8-rc is the second release candidate for the Tor 0.2.5.x
14693 series. It fixes a bug that affects consistency and speed when
14694 connecting to hidden services, and it updates the location of one of
14695 the directory authorities.
14698 - Clients now send the correct address for their chosen rendezvous
14699 point when trying to access a hidden service. They used to send
14700 the wrong address, which would still work some of the time because
14701 they also sent the identity digest of the rendezvous point, and if
14702 the hidden service happened to try connecting to the rendezvous
14703 point from a relay that already had a connection open to it,
14704 the relay would reuse that connection. Now connections to hidden
14705 services should be more robust and faster. Also, this bug meant
14706 that clients were leaking to the hidden service whether they were
14707 on a little-endian (common) or big-endian (rare) system, which for
14708 some users might have reduced their anonymity. Fixes bug 13151;
14709 bugfix on 0.2.1.5-alpha.
14711 o Directory authority changes:
14712 - Change IP address for gabelmoo (v3 directory authority).
14715 Changes in version 0.2.4.24 - 2014-09-22
14716 Tor 0.2.4.24 fixes a bug that affects consistency and speed when
14717 connecting to hidden services, and it updates the location of one of
14718 the directory authorities.
14721 - Clients now send the correct address for their chosen rendezvous
14722 point when trying to access a hidden service. They used to send
14723 the wrong address, which would still work some of the time because
14724 they also sent the identity digest of the rendezvous point, and if
14725 the hidden service happened to try connecting to the rendezvous
14726 point from a relay that already had a connection open to it,
14727 the relay would reuse that connection. Now connections to hidden
14728 services should be more robust and faster. Also, this bug meant
14729 that clients were leaking to the hidden service whether they were
14730 on a little-endian (common) or big-endian (rare) system, which for
14731 some users might have reduced their anonymity. Fixes bug 13151;
14732 bugfix on 0.2.1.5-alpha.
14734 o Directory authority changes:
14735 - Change IP address for gabelmoo (v3 directory authority).
14737 o Minor features (geoip):
14738 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
14742 Changes in version 0.2.5.7-rc - 2014-09-11
14743 Tor 0.2.5.7-rc fixes several regressions from earlier in the 0.2.5.x
14744 release series, and some long-standing bugs related to ORPort reachability
14745 testing and failure to send CREATE cells. It is the first release
14746 candidate for the Tor 0.2.5.x series.
14748 o Major bugfixes (client, startup):
14749 - Start making circuits as soon as DisabledNetwork is turned off.
14750 When Tor started with DisabledNetwork set, it would correctly
14751 conclude that it shouldn't build circuits, but it would mistakenly
14752 cache this conclusion, and continue believing it even when
14753 DisableNetwork is set to 0. Fixes the bug introduced by the fix
14754 for bug 11200; bugfix on 0.2.5.4-alpha.
14755 - Resume expanding abbreviations for command-line options. The fix
14756 for bug 4647 accidentally removed our hack from bug 586 that
14757 rewrote HashedControlPassword to __HashedControlSessionPassword
14758 when it appears on the commandline (which allowed the user to set
14759 her own HashedControlPassword in the torrc file while the
14760 controller generates a fresh session password for each run). Fixes
14761 bug 12948; bugfix on 0.2.5.1-alpha.
14762 - Warn about attempts to run hidden services and relays in the same
14763 process: that's probably not a good idea. Closes ticket 12908.
14765 o Major bugfixes (relay):
14766 - Avoid queuing or sending destroy cells for circuit ID zero when we
14767 fail to send a CREATE cell. Fixes bug 12848; bugfix on 0.0.8pre1.
14768 Found and fixed by "cypherpunks".
14769 - Fix ORPort reachability detection on relays running behind a
14770 proxy, by correctly updating the "local" mark on the controlling
14771 channel when changing the address of an or_connection_t after the
14772 handshake. Fixes bug 12160; bugfix on 0.2.4.4-alpha.
14774 o Minor features (bridge):
14775 - Add an ExtORPortCookieAuthFileGroupReadable option to make the
14776 cookie file for the ExtORPort g+r by default.
14778 o Minor features (geoip):
14779 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
14782 o Minor bugfixes (logging):
14783 - Reduce the log severity of the "Pluggable transport proxy does not
14784 provide any needed transports and will not be launched." message,
14785 since Tor Browser includes several ClientTransportPlugin lines in
14786 its torrc-defaults file, leading every Tor Browser user who looks
14787 at her logs to see these notices and wonder if they're dangerous.
14788 Resolves bug 13124; bugfix on 0.2.5.3-alpha.
14789 - Downgrade "Unexpected onionskin length after decryption" warning
14790 to a protocol-warn, since there's nothing relay operators can do
14791 about a client that sends them a malformed create cell. Resolves
14792 bug 12996; bugfix on 0.0.6rc1.
14793 - Log more specific warnings when we get an ESTABLISH_RENDEZVOUS
14794 cell on a cannibalized or non-OR circuit. Resolves ticket 12997.
14795 - When logging information about an EXTEND2 or EXTENDED2 cell, log
14796 their names correctly. Fixes part of bug 12700; bugfix
14798 - When logging information about a relay cell whose command we don't
14799 recognize, log its command as an integer. Fixes part of bug 12700;
14800 bugfix on 0.2.1.10-alpha.
14801 - Escape all strings from the directory connection before logging
14802 them. Fixes bug 13071; bugfix on 0.1.1.15. Patch from "teor".
14804 o Minor bugfixes (controller):
14805 - Restore the functionality of CookieAuthFileGroupReadable. Fixes
14806 bug 12864; bugfix on 0.2.5.1-alpha.
14807 - Actually send TRANSPORT_LAUNCHED and HS_DESC events to
14808 controllers. Fixes bug 13085; bugfix on 0.2.5.1-alpha. Patch
14811 o Minor bugfixes (compilation):
14812 - Fix compilation of test.h with MSVC. Patch from Gisle Vanem;
14813 bugfix on 0.2.5.5-alpha.
14814 - Make the nmake make files work again. Fixes bug 13081. Bugfix on
14815 0.2.5.1-alpha. Patch from "NewEraCracker".
14816 - In routerlist_assert_ok(), don't take the address of a
14817 routerinfo's cache_info member unless that routerinfo is non-NULL.
14818 Fixes bug 13096; bugfix on 0.1.1.9-alpha. Patch by "teor".
14819 - Fix a large number of false positive warnings from the clang
14820 analyzer static analysis tool. This should make real warnings
14821 easier for clang analyzer to find. Patch from "teor". Closes
14824 o Distribution (systemd):
14825 - Verify configuration file via ExecStartPre in the systemd unit
14826 file. Patch from intrigeri; resolves ticket 12730.
14827 - Explicitly disable RunAsDaemon in the systemd unit file. Our
14828 current systemd unit uses "Type = simple", so systemd does not
14829 expect tor to fork. If the user has "RunAsDaemon 1" in their
14830 torrc, then things won't work as expected. This is e.g. the case
14831 on Debian (and derivatives), since there we pass "--defaults-torrc
14832 /usr/share/tor/tor-service-defaults-torrc" (that contains
14833 "RunAsDaemon 1") by default. Patch by intrigeri; resolves
14837 - Adjust the URLs in the README to refer to the new locations of
14838 several documents on the website. Fixes bug 12830. Patch from
14840 - Document 'reject6' and 'accept6' ExitPolicy entries. Resolves
14844 Changes in version 0.2.5.6-alpha - 2014-07-28
14845 Tor 0.2.5.6-alpha brings us a big step closer to slowing down the
14846 risk from guard rotation, and fixes a variety of other issues to get
14847 us closer to a release candidate.
14849 o Major features (also in 0.2.4.23):
14850 - Make the number of entry guards configurable via a new
14851 NumEntryGuards consensus parameter, and the number of directory
14852 guards configurable via a new NumDirectoryGuards consensus
14853 parameter. Implements ticket 12688.
14855 o Major bugfixes (also in 0.2.4.23):
14856 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
14857 implementation that caused incorrect results on 32-bit
14858 implementations when certain malformed inputs were used along with
14859 a small class of private ntor keys. This bug does not currently
14860 appear to allow an attacker to learn private keys or impersonate a
14861 Tor server, but it could provide a means to distinguish 32-bit Tor
14862 implementations from 64-bit Tor implementations. Fixes bug 12694;
14863 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
14867 - Perform circuit cleanup operations even when circuit
14868 construction operations are disabled (because the network is
14869 disabled, or because there isn't enough directory information).
14870 Previously, when we were not building predictive circuits, we
14871 were not closing expired circuits either. Fixes bug 8387; bugfix on
14872 0.1.1.11-alpha. This bug became visible in 0.2.4.10-alpha when we
14873 became more strict about when we have "enough directory information
14874 to build circuits".
14877 - Authorities now assign the Guard flag to the fastest 25% of the
14878 network (it used to be the fastest 50%). Also raise the consensus
14879 weight that guarantees the Guard flag from 250 to 2000. For the
14880 current network, this results in about 1100 guards, down from 2500.
14881 This step paves the way for moving the number of entry guards
14882 down to 1 (proposal 236) while still providing reasonable expected
14883 performance for most users. Implements ticket 12690.
14884 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
14886 - Slightly enhance the diagnostic message for bug 12184.
14888 o Minor bugfixes (also in 0.2.4.23):
14889 - Warn and drop the circuit if we receive an inbound 'relay early'
14890 cell. Those used to be normal to receive on hidden service circuits
14891 due to bug 1038, but the buggy Tor versions are long gone from
14892 the network so we can afford to resume watching for them. Resolves
14893 the rest of bug 1038; bugfix on 0.2.1.19.
14894 - Correct a confusing error message when trying to extend a circuit
14895 via the control protocol but we don't know a descriptor or
14896 microdescriptor for one of the specified relays. Fixes bug 12718;
14897 bugfix on 0.2.3.1-alpha.
14900 - Fix compilation when building with bufferevents enabled. (This
14901 configuration is still not expected to work, however.)
14902 Fixes bugs 12438, 12474, 11578; bugfixes on 0.2.5.1-alpha and
14903 0.2.5.3-alpha. Patches from Anthony G. Basile and Sathyanarayanan
14905 - Compile correctly with builds and forks of OpenSSL (such as
14906 LibreSSL) that disable compression. Fixes bug 12602; bugfix on
14907 0.2.1.1-alpha. Patch from "dhill".
14910 Changes in version 0.2.4.23 - 2014-07-28
14911 Tor 0.2.4.23 brings us a big step closer to slowing down the risk from
14912 guard rotation, and also backports several important fixes from the
14913 Tor 0.2.5 alpha release series.
14916 - Clients now look at the "usecreatefast" consensus parameter to
14917 decide whether to use CREATE_FAST or CREATE cells for the first hop
14918 of their circuit. This approach can improve security on connections
14919 where Tor's circuit handshake is stronger than the available TLS
14920 connection security levels, but the tradeoff is more computational
14921 load on guard relays. Implements proposal 221. Resolves ticket 9386.
14922 - Make the number of entry guards configurable via a new
14923 NumEntryGuards consensus parameter, and the number of directory
14924 guards configurable via a new NumDirectoryGuards consensus
14925 parameter. Implements ticket 12688.
14928 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
14929 implementation that caused incorrect results on 32-bit
14930 implementations when certain malformed inputs were used along with
14931 a small class of private ntor keys. This bug does not currently
14932 appear to allow an attacker to learn private keys or impersonate a
14933 Tor server, but it could provide a means to distinguish 32-bit Tor
14934 implementations from 64-bit Tor implementations. Fixes bug 12694;
14935 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
14939 - Warn and drop the circuit if we receive an inbound 'relay early'
14940 cell. Those used to be normal to receive on hidden service circuits
14941 due to bug 1038, but the buggy Tor versions are long gone from
14942 the network so we can afford to resume watching for them. Resolves
14943 the rest of bug 1038; bugfix on 0.2.1.19.
14944 - Correct a confusing error message when trying to extend a circuit
14945 via the control protocol but we don't know a descriptor or
14946 microdescriptor for one of the specified relays. Fixes bug 12718;
14947 bugfix on 0.2.3.1-alpha.
14948 - Avoid an illegal read from stack when initializing the TLS
14949 module using a version of OpenSSL without all of the ciphers
14950 used by the v2 link handshake. Fixes bug 12227; bugfix on
14951 0.2.4.8-alpha. Found by "starlight".
14954 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
14958 Changes in version 0.2.5.5-alpha - 2014-06-18
14959 Tor 0.2.5.5-alpha fixes a wide variety of remaining issues in the Tor
14960 0.2.5.x release series, including a couple of DoS issues, some
14961 performance regressions, a large number of bugs affecting the Linux
14962 seccomp2 sandbox code, and various other bugfixes. It also adds
14963 diagnostic bugfixes for a few tricky issues that we're trying to
14966 o Major features (security, traffic analysis resistance):
14967 - Several major improvements to the algorithm used to decide when to
14968 close TLS connections. Previous versions of Tor closed connections
14969 at a fixed interval after the last time a non-padding cell was
14970 sent over the connection, regardless of the target of the
14971 connection. Now, we randomize the intervals by adding up to 50% of
14972 their base value, we measure the length of time since connection
14973 last had at least one circuit, and we allow connections to known
14974 ORs to remain open a little longer (15 minutes instead of 3
14975 minutes minimum). These changes should improve Tor's resistance
14976 against some kinds of traffic analysis, and lower some overhead
14977 from needlessly closed connections. Fixes ticket 6799.
14978 Incidentally fixes ticket 12023; bugfix on 0.2.5.1-alpha.
14980 o Major bugfixes (security, OOM, new since 0.2.5.4-alpha, also in 0.2.4.22):
14981 - Fix a memory leak that could occur if a microdescriptor parse
14982 fails during the tokenizing step. This bug could enable a memory
14983 exhaustion attack by directory servers. Fixes bug 11649; bugfix
14986 o Major bugfixes (security, directory authorities):
14987 - Directory authorities now include a digest of each relay's
14988 identity key as a part of its microdescriptor.
14990 This is a workaround for bug 11743 (reported by "cypherpunks"),
14991 where Tor clients do not support receiving multiple
14992 microdescriptors with the same SHA256 digest in the same
14993 consensus. When clients receive a consensus like this, they only
14994 use one of the relays. Without this fix, a hostile relay could
14995 selectively disable some client use of target relays by
14996 constructing a router descriptor with a different identity and the
14997 same microdescriptor parameters and getting the authorities to
14998 list it in a microdescriptor consensus. This fix prevents an
14999 attacker from causing a microdescriptor collision, because the
15000 router's identity is not forgeable.
15002 o Major bugfixes (relay):
15003 - Use a direct dirport connection when uploading non-anonymous
15004 descriptors to the directory authorities. Previously, relays would
15005 incorrectly use tunnel connections under a fairly wide variety of
15006 circumstances. Fixes bug 11469; bugfix on 0.2.4.3-alpha.
15007 - When a circuit accidentally has the same circuit ID for its
15008 forward and reverse direction, correctly detect the direction of
15009 cells using that circuit. Previously, this bug made roughly one
15010 circuit in a million non-functional. Fixes bug 12195; this is a
15011 bugfix on every version of Tor.
15013 o Major bugfixes (client, pluggable transports):
15014 - When managing pluggable transports, use OS notification facilities
15015 to learn if they have crashed, and don't attempt to kill any
15016 process that has already exited. Fixes bug 8746; bugfix
15019 o Minor features (diagnostic):
15020 - When logging a warning because of bug 7164, additionally check the
15021 hash table for consistency (as proposed on ticket 11737). This may
15022 help diagnose bug 7164.
15023 - When we log a heartbeat, log how many one-hop circuits we have
15024 that are at least 30 minutes old, and log status information about
15025 a few of them. This is an attempt to track down bug 8387.
15026 - When encountering an unexpected CR while writing text to a file on
15027 Windows, log the name of the file. Should help diagnosing
15029 - Give more specific warnings when a client notices that an onion
15030 handshake has failed. Fixes ticket 9635.
15031 - Add significant new logging code to attempt to diagnose bug 12184,
15032 where relays seem to run out of available circuit IDs.
15033 - Improve the diagnostic log message for bug 8387 even further to
15034 try to improve our odds of figuring out why one-hop directory
15035 circuits sometimes do not get closed.
15037 o Minor features (security, memory management):
15038 - Memory allocation tricks (mempools and buffer freelists) are now
15039 disabled by default. You can turn them back on with
15040 --enable-mempools and --enable-buf-freelists respectively. We're
15041 disabling these features because malloc performance is good enough
15042 on most platforms, and a similar feature in OpenSSL exacerbated
15043 exploitation of the Heartbleed attack. Resolves ticket 11476.
15045 o Minor features (security):
15046 - Apply the secure SipHash-2-4 function to the hash table mapping
15047 circuit IDs and channels to circuits. We missed this one when we
15048 were converting all the other hash functions to use SipHash back
15049 in 0.2.5.3-alpha. Resolves ticket 11750.
15051 o Minor features (build):
15052 - The configure script has a --disable-seccomp option to turn off
15053 support for libseccomp on systems that have it, in case it (or
15054 Tor's use of it) is broken. Resolves ticket 11628.
15056 o Minor features (other):
15057 - Update geoip and geoip6 to the June 4 2014 Maxmind GeoLite2
15060 o Minor bugfixes (security, new since 0.2.5.4-alpha, also in 0.2.4.22):
15061 - When running a hidden service, do not allow TunneledDirConns 0;
15062 this will keep the hidden service from running, and also
15063 make it publish its descriptors directly over HTTP. Fixes bug 10849;
15064 bugfix on 0.2.1.1-alpha.
15066 o Minor bugfixes (performance):
15067 - Avoid a bug where every successful connection made us recompute
15068 the flag telling us whether we have sufficient information to
15069 build circuits. Previously, we would forget our cached value
15070 whenever we successfully opened a channel (or marked a router as
15071 running or not running for any other reason), regardless of
15072 whether we had previously believed the router to be running. This
15073 forced us to run an expensive update operation far too often.
15074 Fixes bug 12170; bugfix on 0.1.2.1-alpha.
15075 - Avoid using tor_memeq() for checking relay cell integrity. This
15076 removes a possible performance bottleneck. Fixes part of bug
15077 12169; bugfix on 0.2.1.31.
15079 o Minor bugfixes (compilation):
15080 - Fix compilation of test_status.c when building with MVSC. Bugfix
15081 on 0.2.5.4-alpha. Patch from Gisle Vanem.
15082 - Resolve GCC complaints on OpenBSD about discarding constness in
15083 TO_{ORIGIN,OR}_CIRCUIT functions. Fixes part of bug 11633; bugfix
15084 on 0.1.1.23. Patch from Dana Koch.
15085 - Resolve clang complaints on OpenBSD with -Wshorten-64-to-32 due to
15086 treatment of long and time_t as comparable types. Fixes part of
15087 bug 11633. Patch from Dana Koch.
15088 - Make Tor compile correctly with --disable-buf-freelists. Fixes bug
15089 11623; bugfix on 0.2.5.3-alpha.
15090 - When deciding whether to build the 64-bit curve25519
15091 implementation, detect platforms where we can compile 128-bit
15092 arithmetic but cannot link it. Fixes bug 11729; bugfix on
15093 0.2.4.8-alpha. Patch from "conradev".
15094 - Fix compilation when DNS_CACHE_DEBUG is enabled. Fixes bug 11761;
15095 bugfix on 0.2.3.13-alpha. Found by "cypherpunks".
15096 - Fix compilation with dmalloc. Fixes bug 11605; bugfix
15099 o Minor bugfixes (Directory server):
15100 - When sending a compressed set of descriptors or microdescriptors,
15101 make sure to finalize the zlib stream. Previously, we would write
15102 all the compressed data, but if the last descriptor we wanted to
15103 send was missing or too old, we would not mark the stream as
15104 finished. This caused problems for decompression tools. Fixes bug
15105 11648; bugfix on 0.1.1.23.
15107 o Minor bugfixes (Linux seccomp sandbox):
15108 - Make the seccomp sandbox code compile under ARM Linux. Fixes bug
15109 11622; bugfix on 0.2.5.1-alpha.
15110 - Avoid crashing when re-opening listener ports with the seccomp
15111 sandbox active. Fixes bug 12115; bugfix on 0.2.5.1-alpha.
15112 - Avoid crashing with the seccomp sandbox enabled along with
15113 ConstrainedSockets. Fixes bug 12139; bugfix on 0.2.5.1-alpha.
15114 - When we receive a SIGHUP with the sandbox enabled, correctly
15115 support rotating our log files. Fixes bug 12032; bugfix
15117 - Avoid crash when running with sandboxing enabled and
15118 DirReqStatistics not disabled. Fixes bug 12035; bugfix
15120 - Fix a "BUG" warning when trying to write bridge-stats files with
15121 the Linux syscall sandbox filter enabled. Fixes bug 12041; bugfix
15123 - Prevent the sandbox from crashing on startup when run with the
15124 --enable-expensive-hardening configuration option. Fixes bug
15125 11477; bugfix on 0.2.5.4-alpha.
15126 - When running with DirPortFrontPage and sandboxing both enabled,
15127 reload the DirPortFrontPage correctly when restarting. Fixes bug
15128 12028; bugfix on 0.2.5.1-alpha.
15129 - Don't try to enable the sandbox when using the Tor binary to check
15130 its configuration, hash a passphrase, or so on. Doing so was
15131 crashing on startup for some users. Fixes bug 11609; bugfix
15133 - Avoid warnings when running with sandboxing and node statistics
15134 enabled at the same time. Fixes part of 12064; bugfix on
15135 0.2.5.1-alpha. Patch from Michael Wolf.
15136 - Avoid warnings when running with sandboxing enabled at the same
15137 time as cookie authentication, hidden services, or directory
15138 authority voting. Fixes part of 12064; bugfix on 0.2.5.1-alpha.
15139 - Do not allow options that require calls to exec to be enabled
15140 alongside the seccomp2 sandbox: they will inevitably crash. Fixes
15141 bug 12043; bugfix on 0.2.5.1-alpha.
15142 - Handle failures in getpwnam()/getpwuid() when running with the
15143 User option set and the Linux syscall sandbox enabled. Fixes bug
15144 11946; bugfix on 0.2.5.1-alpha.
15145 - Refactor the getaddrinfo workaround that the seccomp sandbox uses
15146 to avoid calling getaddrinfo() after installing the sandbox
15147 filters. Previously, it preloaded a cache with the IPv4 address
15148 for our hostname, and nothing else. Now, it loads the cache with
15149 every address that it used to initialize the Tor process. Fixes
15150 bug 11970; bugfix on 0.2.5.1-alpha.
15152 o Minor bugfixes (pluggable transports):
15153 - Enable the ExtORPortCookieAuthFile option, to allow changing the
15154 default location of the authentication token for the extended OR
15155 Port as used by sever-side pluggable transports. We had
15156 implemented this option before, but the code to make it settable
15157 had been omitted. Fixes bug 11635; bugfix on 0.2.5.1-alpha.
15158 - Avoid another 60-second delay when starting Tor in a pluggable-
15159 transport-using configuration when we already have cached
15160 descriptors for our bridges. Fixes bug 11965; bugfix
15163 o Minor bugfixes (client):
15164 - Avoid "Tried to open a socket with DisableNetwork set" warnings
15165 when starting a client with bridges configured and DisableNetwork
15166 set. (Tor launcher starts Tor with DisableNetwork set the first
15167 time it runs.) Fixes bug 10405; bugfix on 0.2.3.9-alpha.
15169 o Minor bugfixes (testing):
15170 - The Python parts of the test scripts now work on Python 3 as well
15171 as Python 2, so systems where '/usr/bin/python' is Python 3 will
15172 no longer have the tests break. Fixes bug 11608; bugfix
15174 - When looking for versions of python that we could run the tests
15175 with, check for "python2.7" and "python3.3"; previously we were
15176 only looking for "python", "python2", and "python3". Patch from
15177 Dana Koch. Fixes bug 11632; bugfix on 0.2.5.2-alpha.
15178 - Fix all valgrind warnings produced by the unit tests. There were
15179 over a thousand memory leak warnings previously, mostly produced
15180 by forgetting to free things in the unit test code. Fixes bug
15181 11618, bugfixes on many versions of Tor.
15183 o Minor bugfixes (tor-fw-helper):
15184 - Give a correct log message when tor-fw-helper fails to launch.
15185 (Previously, we would say something like "tor-fw-helper sent us a
15186 string we could not parse".) Fixes bug 9781; bugfix
15189 o Minor bugfixes (relay, threading):
15190 - Check return code on spawn_func() in cpuworker code, so that we
15191 don't think we've spawned a nonworking cpuworker and write junk to
15192 it forever. Fix related to bug 4345; bugfix on all released Tor
15193 versions. Found by "skruffy".
15194 - Use a pthread_attr to make sure that spawn_func() cannot return an
15195 error while at the same time launching a thread. Fix related to
15196 bug 4345; bugfix on all released Tor versions. Reported
15199 o Minor bugfixes (relay, oom prevention):
15200 - Correctly detect the total available system memory. We tried to do
15201 this in 0.2.5.4-alpha, but the code was set up to always return an
15202 error value, even on success. Fixes bug 11805; bugfix
15205 o Minor bugfixes (relay, other):
15206 - We now drop CREATE cells for already-existent circuit IDs and for
15207 zero-valued circuit IDs, regardless of other factors that might
15208 otherwise have called for DESTROY cells. Fixes bug 12191; bugfix
15210 - Avoid an illegal read from stack when initializing the TLS module
15211 using a version of OpenSSL without all of the ciphers used by the
15212 v2 link handshake. Fixes bug 12227; bugfix on 0.2.4.8-alpha. Found
15214 - When rejecting DATA cells for stream_id zero, still count them
15215 against the circuit's deliver window so that we don't fail to send
15216 a SENDME. Fixes bug 11246; bugfix on 0.2.4.10-alpha.
15218 o Minor bugfixes (logging):
15219 - Fix a misformatted log message about delayed directory fetches.
15220 Fixes bug 11654; bugfix on 0.2.5.3-alpha.
15221 - Squelch a spurious LD_BUG message "No origin circuit for
15222 successful SOCKS stream" in certain hidden service failure cases;
15226 - Include a tor.service file in contrib/dist for use with systemd.
15227 Some distributions will be able to use this file unmodified;
15228 others will need to tweak it, or write their own. Patch from Jamie
15229 Nguyen; resolves ticket 8368.
15232 - Clean up several option names in the manpage to match their real
15233 names, add the missing documentation for a couple of testing and
15234 directory authority options, remove the documentation for a
15235 V2-directory fetching option that no longer exists. Resolves
15237 - Correct the documentation so that it lists the correct directory
15238 for the stats files. (They are in a subdirectory called "stats",
15240 - In the manpage, move more authority-only options into the
15241 directory authority section so that operators of regular directory
15242 caches don't get confused.
15245 - The contrib directory has been sorted and tidied. Before, it was
15246 an unsorted dumping ground for useful and not-so-useful things.
15247 Now, it is divided based on functionality, and the items which
15248 seemed to be nonfunctional or useless have been removed. Resolves
15249 ticket 8966; based on patches from "rl1987".
15252 - Remove /tor/dbg-stability.txt URL that was meant to help debug WFU
15253 and MTBF calculations, but that nobody was using. Fixes ticket 11742.
15254 - The TunnelDirConns and PreferTunnelledDirConns options no longer
15255 exist; tunneled directory connections have been available since
15256 0.1.2.5-alpha, and turning them off is not a good idea. This is a
15257 brute-force fix for 10849, where "TunnelDirConns 0" would break
15261 Changes in version 0.2.4.22 - 2014-05-16
15262 Tor 0.2.4.22 backports numerous high-priority fixes from the Tor 0.2.5
15263 alpha release series. These include blocking all authority signing
15264 keys that may have been affected by the OpenSSL "heartbleed" bug,
15265 choosing a far more secure set of TLS ciphersuites by default, closing
15266 a couple of memory leaks that could be used to run a target relay out
15267 of RAM, and several others.
15269 o Major features (security, backport from 0.2.5.4-alpha):
15270 - Block authority signing keys that were used on authorities
15271 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
15272 don't have any evidence that these keys _were_ compromised; we're
15273 doing this to be prudent.) Resolves ticket 11464.
15275 o Major bugfixes (security, OOM):
15276 - Fix a memory leak that could occur if a microdescriptor parse
15277 fails during the tokenizing step. This bug could enable a memory
15278 exhaustion attack by directory servers. Fixes bug 11649; bugfix
15281 o Major bugfixes (TLS cipher selection, backport from 0.2.5.4-alpha):
15282 - The relay ciphersuite list is now generated automatically based on
15283 uniform criteria, and includes all OpenSSL ciphersuites with
15284 acceptable strength and forward secrecy. Previously, we had left
15285 some perfectly fine ciphersuites unsupported due to omission or
15286 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
15287 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
15288 - Relays now trust themselves to have a better view than clients of
15289 which TLS ciphersuites are better than others. (Thanks to bug
15290 11513, the relay list is now well-considered, whereas the client
15291 list has been chosen mainly for anti-fingerprinting purposes.)
15292 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
15293 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
15294 AES128. Resolves ticket 11528.
15295 - Clients now try to advertise the same list of ciphersuites as
15296 Firefox 28. This change enables selection of (fast) GCM
15297 ciphersuites, disables some strange old ciphers, and stops
15298 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
15299 Resolves ticket 11438.
15301 o Minor bugfixes (configuration, security):
15302 - When running a hidden service, do not allow TunneledDirConns 0:
15303 trying to set that option together with a hidden service would
15304 otherwise prevent the hidden service from running, and also make
15305 it publish its descriptors directly over HTTP. Fixes bug 10849;
15306 bugfix on 0.2.1.1-alpha.
15308 o Minor bugfixes (controller, backport from 0.2.5.4-alpha):
15309 - Avoid sending a garbage value to the controller when a circuit is
15310 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
15312 o Minor bugfixes (exit relay, backport from 0.2.5.4-alpha):
15313 - Stop leaking memory when we successfully resolve a PTR record.
15314 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
15316 o Minor bugfixes (bridge client, backport from 0.2.5.4-alpha):
15317 - Avoid 60-second delays in the bootstrapping process when Tor is
15318 launching for a second time while using bridges. Fixes bug 9229;
15319 bugfix on 0.2.0.3-alpha.
15321 o Minor bugfixes (relays and bridges, backport from 0.2.5.4-alpha):
15322 - Give the correct URL in the warning message when trying to run a
15323 relay on an ancient version of Windows. Fixes bug 9393.
15325 o Minor bugfixes (compilation):
15326 - Fix a compilation error when compiling with --disable-curve25519.
15327 Fixes bug 9700; bugfix on 0.2.4.17-rc.
15330 - Downgrade the warning severity for the the "md was still
15331 referenced 1 node(s)" warning. Tor 0.2.5.4-alpha has better code
15332 for trying to diagnose this bug, and the current warning in
15333 earlier versions of tor achieves nothing useful. Addresses warning
15336 o Minor features (log verbosity, backport from 0.2.5.4-alpha):
15337 - When we run out of usable circuit IDs on a channel, log only one
15338 warning for the whole channel, and describe how many circuits
15339 there were on the channel. Fixes part of ticket 11553.
15341 o Minor features (security, backport from 0.2.5.4-alpha):
15342 - Decrease the lower limit of MaxMemInCellQueues to 256 MBytes (but
15343 leave the default at 8GBytes), to better support Raspberry Pi
15344 users. Fixes bug 9686; bugfix on 0.2.4.14-alpha.
15346 o Documentation (backport from 0.2.5.4-alpha):
15347 - Correctly document that we search for a system torrc file before
15348 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
15352 Changes in version 0.2.5.4-alpha - 2014-04-25
15353 Tor 0.2.5.4-alpha includes several security and performance
15354 improvements for clients and relays, including blacklisting authority
15355 signing keys that were used while susceptible to the OpenSSL
15356 "heartbleed" bug, fixing two expensive functions on busy relays,
15357 improved TLS ciphersuite preference lists, support for run-time
15358 hardening on compilers that support AddressSanitizer, and more work on
15359 the Linux sandbox code.
15361 There are also several usability fixes for clients (especially clients
15362 that use bridges), two new TransPort protocols supported (one on
15363 OpenBSD, one on FreeBSD), and various other bugfixes.
15365 This release marks end-of-life for Tor 0.2.2.x; those Tor versions
15366 have accumulated many known flaws; everyone should upgrade.
15368 o Major features (security):
15369 - If you don't specify MaxMemInQueues yourself, Tor now tries to
15370 pick a good value based on your total system memory. Previously,
15371 the default was always 8 GB. You can still override the default by
15372 setting MaxMemInQueues yourself. Resolves ticket 11396.
15373 - Block authority signing keys that were used on authorities
15374 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
15375 don't have any evidence that these keys _were_ compromised; we're
15376 doing this to be prudent.) Resolves ticket 11464.
15378 o Major features (relay performance):
15379 - Speed up server-side lookups of rendezvous and introduction point
15380 circuits by using hashtables instead of linear searches. These
15381 functions previously accounted between 3 and 7% of CPU usage on
15382 some busy relays. Resolves ticket 9841.
15383 - Avoid wasting CPU when extending a circuit over a channel that is
15384 nearly out of circuit IDs. Previously, we would do a linear scan
15385 over possible circuit IDs before finding one or deciding that we
15386 had exhausted our possibilities. Now, we try at most 64 random
15387 circuit IDs before deciding that we probably won't succeed. Fixes
15388 a possible root cause of ticket 11553.
15390 o Major features (seccomp2 sandbox, Linux only):
15391 - The seccomp2 sandbox can now run a test network for multiple hours
15392 without crashing. The sandbox is still experimental, and more bugs
15393 will probably turn up. To try it, enable "Sandbox 1" on a Linux
15394 host. Resolves ticket 11351.
15395 - Strengthen sandbox code: the sandbox can now test the arguments
15396 for rename(), and blocks _sysctl() entirely. Resolves another part
15398 - When the sandbox blocks a system call, it now tries to log a stack
15399 trace before exiting. Resolves ticket 11465.
15401 o Major bugfixes (TLS cipher selection):
15402 - The relay ciphersuite list is now generated automatically based on
15403 uniform criteria, and includes all OpenSSL ciphersuites with
15404 acceptable strength and forward secrecy. Previously, we had left
15405 some perfectly fine ciphersuites unsupported due to omission or
15406 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
15407 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
15408 - Relays now trust themselves to have a better view than clients of
15409 which TLS ciphersuites are better than others. (Thanks to bug
15410 11513, the relay list is now well-considered, whereas the client
15411 list has been chosen mainly for anti-fingerprinting purposes.)
15412 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
15413 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
15414 AES128. Resolves ticket 11528.
15415 - Clients now try to advertise the same list of ciphersuites as
15416 Firefox 28. This change enables selection of (fast) GCM
15417 ciphersuites, disables some strange old ciphers, and stops
15418 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
15419 Resolves ticket 11438.
15421 o Major bugfixes (bridge client):
15422 - Avoid 60-second delays in the bootstrapping process when Tor is
15423 launching for a second time while using bridges. Fixes bug 9229;
15424 bugfix on 0.2.0.3-alpha.
15426 o Minor features (transparent proxy, *BSD):
15427 - Support FreeBSD's ipfw firewall interface for TransPort ports on
15428 FreeBSD. To enable it, set "TransProxyType ipfw". Resolves ticket
15429 10267; patch from "yurivict".
15430 - Support OpenBSD's divert-to rules with the pf firewall for
15431 transparent proxy ports. To enable it, set "TransProxyType
15432 pf-divert". This allows Tor to run a TransPort transparent proxy
15433 port on OpenBSD 4.4 or later without root privileges. See the
15434 pf.conf(5) manual page for information on configuring pf to use
15435 divert-to rules. Closes ticket 10896; patch from Dana Koch.
15437 o Minor features (security):
15438 - New --enable-expensive-hardening option to enable security
15439 hardening options that consume nontrivial amounts of CPU and
15440 memory. Right now, this includes AddressSanitizer and UbSan, which
15441 are supported in newer versions of GCC and Clang. Closes ticket
15444 o Minor features (log verbosity):
15445 - Demote the message that we give when a flushing connection times
15446 out for too long from NOTICE to INFO. It was usually meaningless.
15447 Resolves ticket 5286.
15448 - Don't log so many notice-level bootstrapping messages at startup
15449 about downloading descriptors. Previously, we'd log a notice
15450 whenever we learned about more routers. Now, we only log a notice
15451 at every 5% of progress. Fixes bug 9963.
15452 - Warn less verbosely when receiving a malformed
15453 ESTABLISH_RENDEZVOUS cell. Fixes ticket 11279.
15454 - When we run out of usable circuit IDs on a channel, log only one
15455 warning for the whole channel, and describe how many circuits
15456 there were on the channel. Fixes part of ticket 11553.
15458 o Minor features (relay):
15459 - If a circuit timed out for at least 3 minutes, check if we have a
15460 new external IP address, and publish a new descriptor with the new
15461 IP address if it changed. Resolves ticket 2454.
15463 o Minor features (controller):
15464 - Make the entire exit policy available from the control port via
15465 GETINFO exit-policy/*. Implements enhancement 7952. Patch from
15467 - Because of the fix for ticket 11396, the real limit for memory
15468 usage may no longer match the configured MaxMemInQueues value. The
15469 real limit is now exposed via GETINFO limits/max-mem-in-queues.
15471 o Minor features (bridge client):
15472 - Report a more useful failure message when we can't connect to a
15473 bridge because we don't have the right pluggable transport
15474 configured. Resolves ticket 9665. Patch from Fábio J. Bertinatto.
15476 o Minor features (diagnostic):
15477 - Add more log messages to diagnose bug 7164, which causes
15478 intermittent "microdesc_free() called but md was still referenced"
15479 warnings. We now include more information, to figure out why we
15480 might be cleaning a microdescriptor for being too old if it's
15481 still referenced by a live node_t object.
15483 o Minor bugfixes (client, DNSPort):
15484 - When using DNSPort, try to respond to AAAA requests with AAAA
15485 answers. Previously, we hadn't looked at the request type when
15486 deciding which answer type to prefer. Fixes bug 10468; bugfix on
15488 - When receiving a DNS query for an unsupported record type, reply
15489 with no answer rather than with a NOTIMPL error. This behavior
15490 isn't correct either, but it will break fewer client programs, we
15491 hope. Fixes bug 10268; bugfix on 0.2.0.1-alpha. Original patch
15494 o Minor bugfixes (exit relay):
15495 - Stop leaking memory when we successfully resolve a PTR record.
15496 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
15498 o Minor bugfixes (bridge client):
15499 - Stop accepting bridge lines containing hostnames. Doing so would
15500 cause clients to perform DNS requests on the hostnames, which was
15501 not sensible behavior. Fixes bug 10801; bugfix on 0.2.0.1-alpha.
15502 - Avoid a 60-second delay in the bootstrapping process when a Tor
15503 client with pluggable transports re-reads its configuration at
15504 just the wrong time. Re-fixes bug 11156; bugfix on 0.2.5.3-alpha.
15506 o Minor bugfixes (client, logging during bootstrap):
15507 - Warn only once if we start logging in an unsafe way. Previously,
15508 we complain as many times as we had problems. Fixes bug 9870;
15509 bugfix on 0.2.5.1-alpha.
15510 - Only report the first fatal bootstrap error on a given OR
15511 connection. This stops us from telling the controller bogus error
15512 messages like "DONE". Fixes bug 10431; bugfix on 0.2.1.1-alpha.
15513 - Be more helpful when trying to run sandboxed on Linux without
15514 libseccomp. Instead of saying "Sandbox is not implemented on this
15515 platform", we now explain that we need to be built with
15516 libseccomp. Fixes bug 11543; bugfix on 0.2.5.1-alpha.
15517 - Avoid generating spurious warnings when starting with
15518 DisableNetwork enabled. Fixes bug 11200 and bug 10405; bugfix on
15521 o Minor bugfixes (closing OR connections):
15522 - If write_to_buf() in connection_write_to_buf_impl_() ever fails,
15523 check if it's an or_connection_t and correctly call
15524 connection_or_close_for_error() rather than
15525 connection_mark_for_close() directly. Fixes bug 11304; bugfix on
15527 - When closing all connections on setting DisableNetwork to 1, use
15528 connection_or_close_normally() rather than closing OR connections
15529 out from under the channel layer. Fixes bug 11306; bugfix on
15532 o Minor bugfixes (controller):
15533 - Avoid sending a garbage value to the controller when a circuit is
15534 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
15536 o Minor bugfixes (tor-fw-helper):
15537 - Allow tor-fw-helper to build again by adding src/ext to its
15538 CPPFLAGS. Fixes bug 11296; bugfix on 0.2.5.3-alpha.
15540 o Minor bugfixes (bridges):
15541 - Avoid potential crashes or bad behavior when launching a
15542 server-side managed proxy with ORPort or ExtORPort temporarily
15543 disabled. Fixes bug 9650; bugfix on 0.2.3.16-alpha.
15545 o Minor bugfixes (platform-specific):
15546 - Fix compilation on Solaris, which does not have <endian.h>. Fixes
15547 bug 11426; bugfix on 0.2.5.3-alpha.
15548 - When dumping a malformed directory object to disk, save it in
15549 binary mode on Windows, not text mode. Fixes bug 11342; bugfix on
15551 - Don't report failures from make_socket_reuseable() on incoming
15552 sockets on OSX: this can happen when incoming connections close
15553 early. Fixes bug 10081.
15555 o Minor bugfixes (trivial memory leaks):
15556 - Fix a small memory leak when signing a directory object. Fixes bug
15557 11275; bugfix on 0.2.4.13-alpha.
15558 - Free placeholder entries in our circuit table at exit; fixes a
15559 harmless memory leak. Fixes bug 11278; bugfix on 0.2.5.1-alpha.
15560 - Don't re-initialize a second set of OpenSSL mutexes when starting
15561 up. Previously, we'd make one set of mutexes, and then immediately
15562 replace them with another. Fixes bug 11726; bugfix on
15564 - Resolve some memory leaks found by coverity in the unit tests, on
15565 exit in tor-gencert, and on a failure to compute digests for our
15566 own keys when generating a v3 networkstatus vote. These leaks
15567 should never have affected anyone in practice.
15569 o Minor bugfixes (hidden service):
15570 - Only retry attempts to connect to a chosen rendezvous point 8
15571 times, not 30. Fixes bug 4241; bugfix on 0.1.0.1-rc.
15573 o Minor bugfixes (misc code correctness):
15574 - Fix various instances of undefined behavior in channeltls.c,
15575 tor_memmem(), and eventdns.c that would cause us to construct
15576 pointers to memory outside an allocated object. (These invalid
15577 pointers were not accessed, but C does not even allow them to
15578 exist.) Fixes bug 10363; bugfixes on 0.1.1.1-alpha, 0.1.2.1-alpha,
15579 0.2.0.10-alpha, and 0.2.3.6-alpha. Reported by "bobnomnom".
15580 - Use the AddressSanitizer and Ubsan sanitizers (in clang-3.4) to
15581 fix some miscellaneous errors in our tests and codebase. Fixes bug
15582 11232. Bugfixes on versions back as far as 0.2.1.11-alpha.
15583 - Always check return values for unlink, munmap, UnmapViewOfFile;
15584 check strftime return values more often. In some cases all we can
15585 do is report a warning, but this may help prevent deeper bugs from
15586 going unnoticed. Closes ticket 8787; bugfixes on many, many tor
15588 - Fix numerous warnings from the clang "scan-build" static analyzer.
15589 Some of these are programming style issues; some of them are false
15590 positives that indicated awkward code; some are undefined behavior
15591 cases related to constructing (but not using) invalid pointers;
15592 some are assumptions about API behavior; some are (harmlessly)
15593 logging sizeof(ptr) bytes from a token when sizeof(*ptr) would be
15594 correct; and one or two are genuine bugs that weren't reachable
15595 from the rest of the program. Fixes bug 8793; bugfixes on many,
15599 - Build the torify.1 manpage again. Previously, we were only trying
15600 to build it when also building tor-fw-helper. That's why we didn't
15601 notice that we'd broken the ability to build it. Fixes bug 11321;
15602 bugfix on 0.2.5.1-alpha.
15603 - Fix the layout of the SOCKSPort flags in the manpage. Fixes bug
15604 11061; bugfix on 0.2.4.7-alpha.
15605 - Correctly document that we search for a system torrc file before
15606 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
15608 - Resolve warnings from Doxygen.
15610 o Code simplifications and refactoring:
15611 - Remove is_internal_IP() function. Resolves ticket 4645.
15612 - Remove unused function circuit_dump_by_chan from circuitlist.c.
15613 Closes issue 9107; patch from "marek".
15614 - Change our use of the ENUM_BF macro to avoid declarations that
15617 o Deprecated versions:
15618 - Tor 0.2.2.x has reached end-of-life; it has received no patches or
15619 attention for some while. Directory authorities no longer accept
15620 descriptors from relays running any version of Tor prior to Tor
15621 0.2.3.16-alpha. Resolves ticket 11149.
15624 - New macros in test.h to simplify writing mock-functions for unit
15625 tests. Part of ticket 11507. Patch from Dana Koch.
15626 - Complete tests for the status.c module. Resolves ticket 11507.
15627 Patch from Dana Koch.
15630 - Remove all code for the long unused v1 directory protocol.
15631 Resolves ticket 11070.
15634 Changes in version 0.2.5.3-alpha - 2014-03-22
15635 Tor 0.2.5.3-alpha includes all the fixes from 0.2.4.21. It contains
15636 two new anti-DoS features for Tor relays, resolves a bug that kept
15637 SOCKS5 support for IPv6 from working, fixes several annoying usability
15638 issues for bridge users, and removes more old code for unused
15641 The Tor 0.2.5.x release series is now in patch-freeze: no feature
15642 patches not already written will be considered for inclusion in 0.2.5.x.
15644 o Major features (relay security, DoS-resistance):
15645 - When deciding whether we have run out of memory and we need to
15646 close circuits, also consider memory allocated in buffers for
15647 streams attached to each circuit.
15649 This change, which extends an anti-DoS feature introduced in
15650 0.2.4.13-alpha and improved in 0.2.4.14-alpha, lets Tor exit relays
15651 better resist more memory-based DoS attacks than before. Since the
15652 MaxMemInCellQueues option now applies to all queues, it is renamed
15653 to MaxMemInQueues. This feature fixes bug 10169.
15654 - Avoid hash-flooding denial-of-service attacks by using the secure
15655 SipHash-2-4 hash function for our hashtables. Without this
15656 feature, an attacker could degrade performance of a targeted
15657 client or server by flooding their data structures with a large
15658 number of entries to be stored at the same hash table position,
15659 thereby slowing down the Tor instance. With this feature, hash
15660 table positions are derived from a randomized cryptographic key,
15661 and an attacker cannot predict which entries will collide. Closes
15663 - Decrease the lower limit of MaxMemInQueues to 256 MBytes (but leave
15664 the default at 8GBytes), to better support Raspberry Pi users. Fixes
15665 bug 9686; bugfix on 0.2.4.14-alpha.
15667 o Minor features (bridges, pluggable transports):
15668 - Bridges now write the SHA1 digest of their identity key
15669 fingerprint (that is, a hash of a hash of their public key) to
15670 notice-level logs, and to a new hashed-fingerprint file. This
15671 information will help bridge operators look up their bridge in
15672 Globe and similar tools. Resolves ticket 10884.
15673 - Improve the message that Tor displays when running as a bridge
15674 using pluggable transports without an Extended ORPort listener.
15675 Also, log the message in the log file too. Resolves ticket 11043.
15677 o Minor features (other):
15678 - Add a new option, PredictedPortsRelevanceTime, to control how long
15679 after having received a request to connect to a given port Tor
15680 will try to keep circuits ready in anticipation of future requests
15681 for that port. Patch from "unixninja92"; implements ticket 9176.
15682 - Generate a warning if any ports are listed in the SocksPolicy,
15683 DirPolicy, AuthDirReject, AuthDirInvalid, AuthDirBadDir, or
15684 AuthDirBadExit options. (These options only support address
15685 ranges.) Fixes part of ticket 11108.
15686 - Update geoip and geoip6 to the February 7 2014 Maxmind GeoLite2
15689 o Minor bugfixes (new since 0.2.5.2-alpha, also in 0.2.4.21):
15690 - Build without warnings under clang 3.4. (We have some macros that
15691 define static functions only some of which will get used later in
15692 the module. Starting with clang 3.4, these give a warning unless the
15693 unused attribute is set on them.) Resolves ticket 10904.
15694 - Fix build warnings about missing "a2x" comment when building the
15695 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
15696 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
15698 o Minor bugfixes (client):
15699 - Improve the log message when we can't connect to a hidden service
15700 because all of the hidden service directory nodes hosting its
15701 descriptor are excluded. Improves on our fix for bug 10722, which
15702 was a bugfix on 0.2.0.10-alpha.
15703 - Raise a control port warning when we fail to connect to all of
15704 our bridges. Previously, we didn't inform the controller, and
15705 the bootstrap process would stall. Fixes bug 11069; bugfix on
15707 - Exit immediately when a process-owning controller exits.
15708 Previously, tor relays would wait for a little while after their
15709 controller exited, as if they had gotten an INT signal -- but this
15710 was problematic, since there was no feedback for the user. To do a
15711 clean shutdown, controllers should send an INT signal and give Tor
15712 a chance to clean up. Fixes bug 10449; bugfix on 0.2.2.28-beta.
15713 - Stop attempting to connect to bridges before our pluggable
15714 transports are configured (harmless but resulted in some erroneous
15715 log messages). Fixes bug 11156; bugfix on 0.2.3.2-alpha.
15716 - Fix connections to IPv6 addresses over SOCKS5. Previously, we were
15717 generating incorrect SOCKS5 responses, and confusing client
15718 applications. Fixes bug 10987; bugfix on 0.2.4.7-alpha.
15720 o Minor bugfixes (relays and bridges):
15721 - Avoid crashing on a malformed resolv.conf file when running a
15722 relay using Libevent 1. Fixes bug 8788; bugfix on 0.1.1.23.
15723 - Non-exit relays no longer launch mock DNS requests to check for
15724 DNS hijacking. This has been unnecessary since 0.2.1.7-alpha, when
15725 non-exit relays stopped servicing DNS requests. Fixes bug 965;
15726 bugfix on 0.2.1.7-alpha. Patch from Matt Pagan.
15727 - Bridges now report complete directory request statistics. Related
15728 to bug 5824; bugfix on 0.2.2.1-alpha.
15729 - Bridges now never collect statistics that were designed for
15730 relays. Fixes bug 5824; bugfix on 0.2.3.8-alpha.
15731 - Stop giving annoying warning messages when we decide not to launch
15732 a pluggable transport proxy that we don't need (because there are
15733 no bridges configured to use it). Resolves ticket 5018; bugfix
15735 - Give the correct URL in the warning message when trying to run a
15736 relay on an ancient version of Windows. Fixes bug 9393.
15738 o Minor bugfixes (backtrace support):
15739 - Support automatic backtraces on more platforms by using the
15740 "-fasynchronous-unwind-tables" compiler option. This option is
15741 needed for platforms like 32-bit Intel where "-fomit-frame-pointer"
15742 is on by default and table generation is not. This doesn't yet
15743 add Windows support; only Linux, OSX, and some BSDs are affected.
15744 Reported by 'cypherpunks'; fixes bug 11047; bugfix on 0.2.5.2-alpha.
15745 - Avoid strange behavior if two threads hit failed assertions at the
15746 same time and both try to log backtraces at once. (Previously, if
15747 this had happened, both threads would have stored their intermediate
15748 results in the same buffer, and generated junk outputs.) Reported by
15749 "cypherpunks". Fixes bug 11048; bugfix on 0.2.5.2-alpha.
15750 - Fix a compiler warning in format_number_sigsafe(). Bugfix on
15751 0.2.5.2-alpha; patch from Nick Hopper.
15753 o Minor bugfixes (unit tests):
15754 - Fix a small bug in the unit tests that might have made the tests
15755 call 'chmod' with an uninitialized bitmask. Fixes bug 10928;
15756 bugfix on 0.2.5.1-alpha. Patch from Dana Koch.
15759 - Remove all remaining code related to version-0 hidden service
15760 descriptors: they have not been in use since 0.2.2.1-alpha. Fixes
15761 the rest of bug 10841.
15764 - Document in the manpage that "KBytes" may also be written as
15765 "kilobytes" or "KB", that "Kbits" may also be written as
15766 "kilobits", and so forth. Closes ticket 9222.
15767 - Document that the ClientOnly config option overrides ORPort.
15768 Our old explanation made ClientOnly sound as though it did
15769 nothing at all. Resolves bug 9059.
15770 - Explain that SocksPolicy, DirPolicy, and similar options don't
15771 take port arguments. Fixes the other part of ticket 11108.
15772 - Fix a comment about the rend_server_descriptor_t.protocols field
15773 to more accurately describe its range. Also, make that field
15774 unsigned, to more accurately reflect its usage. Fixes bug 9099;
15775 bugfix on 0.2.1.5-alpha.
15776 - Fix the manpage's description of HiddenServiceAuthorizeClient:
15777 the maximum client name length is 16, not 19. Fixes bug 11118;
15778 bugfix on 0.2.1.6-alpha.
15780 o Code simplifications and refactoring:
15781 - Get rid of router->address, since in all cases it was just the
15782 string representation of router->addr. Resolves ticket 5528.
15784 o Test infrastructure:
15785 - Update to the latest version of tinytest.
15786 - Improve the tinytest implementation of string operation tests so
15787 that comparisons with NULL strings no longer crash the tests; they
15788 now just fail, normally. Fixes bug 9004; bugfix on 0.2.2.4-alpha.
15791 Changes in version 0.2.4.21 - 2014-02-28
15792 Tor 0.2.4.21 further improves security against potential adversaries who
15793 find breaking 1024-bit crypto doable, and backports several stability
15794 and robustness patches from the 0.2.5 branch.
15796 o Major features (client security):
15797 - When we choose a path for a 3-hop circuit, make sure it contains
15798 at least one relay that supports the NTor circuit extension
15799 handshake. Otherwise, there is a chance that we're building
15800 a circuit that's worth attacking by an adversary who finds
15801 breaking 1024-bit crypto doable, and that chance changes the game
15802 theory. Implements ticket 9777.
15805 - Do not treat streams that fail with reason
15806 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
15807 since it could also indicate an ENETUNREACH connection error. Fixes
15808 part of bug 10777; bugfix on 0.2.4.8-alpha.
15810 o Code simplification and refactoring:
15811 - Remove data structures which were introduced to implement the
15812 CellStatistics option: they are now redundant with the new timestamp
15813 field in the regular packed_cell_t data structure, which we did
15814 in 0.2.4.18-rc in order to resolve bug 9093. Resolves ticket 10870.
15817 - Always clear OpenSSL bignums before freeing them -- even bignums
15818 that don't contain secrets. Resolves ticket 10793. Patch by
15820 - Build without warnings under clang 3.4. (We have some macros that
15821 define static functions only some of which will get used later in
15822 the module. Starting with clang 3.4, these give a warning unless the
15823 unused attribute is set on them.) Resolves ticket 10904.
15824 - Update geoip and geoip6 files to the February 7 2014 Maxmind
15825 GeoLite2 Country database.
15828 - Set the listen() backlog limit to the largest actually supported
15829 on the system, not to the value in a header file. Fixes bug 9716;
15830 bugfix on every released Tor.
15831 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
15832 exit node as a NOROUTE error, not an INTERNAL error, since they
15833 can apparently happen when trying to connect to the wrong sort
15834 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
15835 - Fix build warnings about missing "a2x" comment when building the
15836 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
15837 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
15838 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
15839 not entirely remove it from the connection lists. Fixes bug 9602;
15840 bugfix on 0.2.4.4-alpha.
15841 - Fix a segmentation fault in our benchmark code when running with
15842 Fedora's OpenSSL package, or any other OpenSSL that provides
15843 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
15844 - Turn "circuit handshake stats since last time" log messages into a
15845 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
15847 o Documentation fixes:
15848 - Document that all but one DirPort entry must have the NoAdvertise
15849 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
15852 Changes in version 0.2.5.2-alpha - 2014-02-13
15853 Tor 0.2.5.2-alpha includes all the fixes from 0.2.4.18-rc and 0.2.4.20,
15854 like the "poor random number generation" fix and the "building too many
15855 circuits" fix. It also further improves security against potential
15856 adversaries who find breaking 1024-bit crypto doable, and launches
15857 pluggable transports on demand (which gets us closer to integrating
15858 pluggable transport support by default -- not to be confused with Tor
15859 bundles enabling pluggable transports and bridges by default).
15861 o Major features (client security):
15862 - When we choose a path for a 3-hop circuit, make sure it contains
15863 at least one relay that supports the NTor circuit extension
15864 handshake. Otherwise, there is a chance that we're building
15865 a circuit that's worth attacking by an adversary who finds
15866 breaking 1024-bit crypto doable, and that chance changes the game
15867 theory. Implements ticket 9777.
15868 - Clients now look at the "usecreatefast" consensus parameter to
15869 decide whether to use CREATE_FAST or CREATE cells for the first hop
15870 of their circuit. This approach can improve security on connections
15871 where Tor's circuit handshake is stronger than the available TLS
15872 connection security levels, but the tradeoff is more computational
15873 load on guard relays. Implements proposal 221. Resolves ticket 9386.
15875 o Major features (bridges):
15876 - Don't launch pluggable transport proxies if we don't have any
15877 bridges configured that would use them. Now we can list many
15878 pluggable transports, and Tor will dynamically start one when it
15879 hears a bridge address that needs it. Resolves ticket 5018.
15880 - The bridge directory authority now assigns status flags (Stable,
15881 Guard, etc) to bridges based on thresholds calculated over all
15882 Running bridges. Now bridgedb can finally make use of its features
15883 to e.g. include at least one Stable bridge in its answers. Fixes
15886 o Major features (other):
15887 - Extend ORCONN controller event to include an "ID" parameter,
15888 and add four new controller event types CONN_BW, CIRC_BW,
15889 CELL_STATS, and TB_EMPTY that show connection and circuit usage.
15890 The new events are emitted in private Tor networks only, with the
15891 goal of being able to better track performance and load during
15892 full-network simulations. Implements proposal 218 and ticket 7359.
15893 - On some platforms (currently: recent OSX versions, glibc-based
15894 platforms that support the ELF format, and a few other
15895 Unix-like operating systems), Tor can now dump stack traces
15896 when a crash occurs or an assertion fails. By default, traces
15897 are dumped to stderr (if possible) and to any logs that are
15898 reporting errors. Implements ticket 9299.
15901 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
15902 not entirely remove it from the connection lists. Fixes bug 9602;
15903 bugfix on 0.2.4.4-alpha.
15904 - Do not treat streams that fail with reason
15905 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
15906 since it could also indicate an ENETUNREACH connection error. Fixes
15907 part of bug 10777; bugfix on 0.2.4.8-alpha.
15909 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
15910 - Do not allow OpenSSL engines to replace the PRNG, even when
15911 HardwareAccel is set. The only default builtin PRNG engine uses
15912 the Intel RDRAND instruction to replace the entire PRNG, and
15913 ignores all attempts to seed it with more entropy. That's
15914 cryptographically stupid: the right response to a new alleged
15915 entropy source is never to discard all previously used entropy
15916 sources. Fixes bug 10402; works around behavior introduced in
15917 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
15919 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
15920 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
15921 - Avoid launching spurious extra circuits when a stream is pending.
15922 This fixes a bug where any circuit that _wasn't_ unusable for new
15923 streams would be treated as if it were, causing extra circuits to
15924 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
15926 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
15927 - No longer stop reading or writing on cpuworker connections when
15928 our rate limiting buckets go empty. Now we should handle circuit
15929 handshake requests more promptly. Resolves bug 9731.
15930 - Stop trying to bootstrap all our directory information from
15931 only our first guard. Discovered while fixing bug 9946; bugfix
15934 o Minor features (bridges, pluggable transports):
15935 - Add threshold cutoffs to the networkstatus document created by
15936 the Bridge Authority. Fixes bug 1117.
15937 - On Windows, spawn background processes using the CREATE_NO_WINDOW
15938 flag. Now Tor Browser Bundle 3.5 with pluggable transports enabled
15939 doesn't pop up a blank console window. (In Tor Browser Bundle 2.x,
15940 Vidalia set this option for us.) Implements ticket 10297.
15942 o Minor features (security):
15943 - Always clear OpenSSL bignums before freeing them -- even bignums
15944 that don't contain secrets. Resolves ticket 10793. Patch by
15947 o Minor features (config options and command line):
15948 - Add an --allow-missing-torrc commandline option that tells Tor to
15949 run even if the configuration file specified by -f is not available.
15950 Implements ticket 10060.
15951 - Add support for the TPROXY transparent proxying facility on Linux.
15952 See documentation for the new TransProxyType option for more
15953 details. Implementation by "thomo". Closes ticket 10582.
15955 o Minor features (controller):
15956 - Add a new "HS_DESC" controller event that reports activities
15957 related to hidden service descriptors. Resolves ticket 8510.
15958 - New "DROPGUARDS" controller command to forget all current entry
15959 guards. Not recommended for ordinary use, since replacing guards
15960 too frequently makes several attacks easier. Resolves ticket 9934;
15963 o Minor features (build):
15964 - Assume that a user using ./configure --host wants to cross-compile,
15965 and give an error if we cannot find a properly named
15966 tool-chain. Add a --disable-tool-name-check option to proceed
15967 nevertheless. Addresses ticket 9869. Patch by Benedikt Gollatz.
15968 - If we run ./configure and the compiler recognizes -fstack-protector
15969 but the linker rejects it, warn the user about a potentially missing
15970 libssp package. Addresses ticket 9948. Patch from Benedikt Gollatz.
15972 o Minor features (testing):
15973 - If Python is installed, "make check" now runs extra tests beyond
15974 the unit test scripts.
15975 - When bootstrapping a test network, sometimes very few relays get
15976 the Guard flag. Now a new option "TestingDirAuthVoteGuard" can
15977 specify a set of relays which should be voted Guard regardless of
15978 their uptime or bandwidth. Addresses ticket 9206.
15980 o Minor features (log messages):
15981 - When ServerTransportPlugin is set on a bridge, Tor can write more
15982 useful statistics about bridge use in its extrainfo descriptors,
15983 but only if the Extended ORPort ("ExtORPort") is set too. Add a
15984 log message to inform the user in this case. Resolves ticket 9651.
15985 - When receiving a new controller connection, log the origin address.
15986 Resolves ticket 9698; patch from "sigpipe".
15987 - When logging OpenSSL engine status at startup, log the status of
15988 more engines. Fixes ticket 10043; patch from Joshua Datko.
15989 - Turn "circuit handshake stats since last time" log messages into a
15990 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
15992 o Minor features (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
15993 - Improve the circuit queue out-of-memory handler. Previously, when
15994 we ran low on memory, we'd close whichever circuits had the most
15995 queued cells. Now, we close those that have the *oldest* queued
15996 cells, on the theory that those are most responsible for us
15997 running low on memory. Based on analysis from a forthcoming paper
15998 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
15999 - Generate bootstrapping status update events correctly when fetching
16000 microdescriptors. Fixes bug 9927.
16001 - Update to the October 2 2013 Maxmind GeoLite Country database.
16003 o Minor bugfixes (clients):
16004 - When closing a channel that has already been open, do not close
16005 pending circuits that were waiting to connect to the same relay.
16006 Fixes bug 9880; bugfix on 0.2.5.1-alpha. Thanks to skruffy for
16009 o Minor bugfixes (relays):
16010 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
16011 exit node as a NOROUTE error, not an INTERNAL error, since they
16012 can apparently happen when trying to connect to the wrong sort
16013 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
16015 o Minor bugfixes (bridges):
16016 - Fix a bug where the first connection works to a bridge that uses a
16017 pluggable transport with client-side parameters, but we don't send
16018 the client-side parameters on subsequent connections. (We don't
16019 use any pluggable transports with client-side parameters yet,
16020 but ScrambleSuit will soon become the first one.) Fixes bug 9162;
16021 bugfix on 0.2.0.3-alpha. Based on a patch from "rl1987".
16023 o Minor bugfixes (node selection):
16024 - If ExcludeNodes is set, consider non-excluded hidden service
16025 directory servers before excluded ones. Do not consider excluded
16026 hidden service directory servers at all if StrictNodes is
16027 set. (Previously, we would sometimes decide to connect to those
16028 servers, and then realize before we initiated a connection that
16029 we had excluded them.) Fixes bug 10722; bugfix on 0.2.0.10-alpha.
16030 Reported by "mr-4".
16031 - If we set the ExitNodes option but it doesn't include any nodes
16032 that have the Exit flag, we would choose not to bootstrap. Now we
16033 bootstrap so long as ExitNodes includes nodes which can exit to
16034 some port. Fixes bug 10543; bugfix on 0.2.4.10-alpha.
16036 o Minor bugfixes (controller and command-line):
16037 - If changing a config option via "setconf" fails in a recoverable
16038 way, we used to nonetheless write our new control ports to the
16039 file described by the "ControlPortWriteToFile" option. Now we only
16040 write out that file if we successfully switch to the new config
16041 option. Fixes bug 5605; bugfix on 0.2.2.26-beta. Patch from "Ryman".
16042 - When a command-line option such as --version or --help that
16043 ordinarily implies --hush appears on the command line along with
16044 --quiet, then actually obey --quiet. Previously, we obeyed --quiet
16045 only if it appeared later on the command line. Fixes bug 9578;
16046 bugfix on 0.2.5.1-alpha.
16048 o Minor bugfixes (code correctness):
16049 - Previously we used two temporary files when writing descriptors to
16050 disk; now we only use one. Fixes bug 1376.
16051 - Remove an erroneous (but impossible and thus harmless) pointer
16052 comparison that would have allowed compilers to skip a bounds
16053 check in channeltls.c. Fixes bugs 10313 and 9980; bugfix on
16054 0.2.0.10-alpha. Noticed by Jared L Wong and David Fifield.
16055 - Fix an always-true assertion in pluggable transports code so it
16056 actually checks what it was trying to check. Fixes bug 10046;
16057 bugfix on 0.2.3.9-alpha. Found by "dcb".
16059 o Minor bugfixes (protocol correctness):
16060 - When receiving a VERSIONS cell with an odd number of bytes, close
16061 the connection immediately since the cell is malformed. Fixes bug
16062 10365; bugfix on 0.2.0.10-alpha. Spotted by "bobnomnom"; fix by
16065 o Minor bugfixes (build):
16066 - Restore the ability to compile Tor with V2_HANDSHAKE_SERVER
16067 turned off (that is, without support for v2 link handshakes). Fixes
16068 bug 4677; bugfix on 0.2.3.2-alpha. Patch from "piet".
16069 - Fix compilation warnings and startup issues when running with
16070 "Sandbox 1" and libseccomp-2.1.0. Fixes bug 10563; bugfix on
16072 - Fix compilation on Solaris 9, which didn't like us having an
16073 identifier named "sun". Fixes bug 10565; bugfix in 0.2.5.1-alpha.
16075 o Minor bugfixes (testing):
16076 - Fix a segmentation fault in our benchmark code when running with
16077 Fedora's OpenSSL package, or any other OpenSSL that provides
16078 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
16080 o Minor bugfixes (log messages):
16081 - Fix a bug where clients using bridges would report themselves
16082 as 50% bootstrapped even without a live consensus document.
16083 Fixes bug 9922; bugfix on 0.2.1.1-alpha.
16084 - Suppress a warning where, if there's only one directory authority
16085 in the network, we would complain that votes and signatures cannot
16086 be uploaded to other directory authorities. Fixes bug 10842;
16087 bugfix on 0.2.2.26-beta.
16088 - Report bootstrapping progress correctly when we're downloading
16089 microdescriptors. We had updated our "do we have enough microdescs
16090 to begin building circuits?" logic most recently in 0.2.4.10-alpha
16091 (see bug 5956), but we left the bootstrap status event logic at
16092 "how far through getting 1/4 of them are we?" Fixes bug 9958;
16093 bugfix on 0.2.2.36, which is where they diverged (see bug 5343).
16095 o Minor bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
16096 - Avoid a crash bug when starting with a corrupted microdescriptor
16097 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
16098 - If we fail to dump a previously cached microdescriptor to disk, avoid
16099 freeing duplicate data later on. Fixes bug 10423; bugfix on
16100 0.2.4.13-alpha. Spotted by "bobnomnom".
16102 o Minor bugfixes on 0.2.4.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
16103 - Correctly log long IPv6 exit policies, instead of truncating them
16104 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
16105 - Our default TLS ecdhe groups were backwards: we meant to be using
16106 P224 for relays (for performance win) and P256 for bridges (since
16107 it is more common in the wild). Instead we had it backwards. After
16108 reconsideration, we decided that the default should be P256 on all
16109 hosts, since its security is probably better, and since P224 is
16110 reportedly used quite little in the wild. Found by "skruffy" on
16111 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
16112 - Free directory authority certificate download statuses on exit
16113 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
16115 o Minor bugfixes on 0.2.3.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
16116 - If the guard we choose first doesn't answer, we would try the
16117 second guard, but once we connected to the second guard we would
16118 abandon it and retry the first one, slowing down bootstrapping.
16119 The fix is to treat all our initially chosen guards as acceptable
16120 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
16121 - Fix an assertion failure that would occur when disabling the
16122 ORPort setting on a running Tor process while accounting was
16123 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
16124 - When examining the list of network interfaces to find our address,
16125 do not consider non-running or disabled network interfaces. Fixes
16126 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
16127 - Avoid an off-by-one error when checking buffer boundaries when
16128 formatting the exit status of a pluggable transport helper.
16129 This is probably not an exploitable bug, but better safe than
16130 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
16133 o Removed code and features:
16134 - Clients now reject any directory authority certificates lacking
16135 a dir-key-crosscert element. These have been included since
16136 0.2.1.9-alpha, so there's no real reason for them to be optional
16137 any longer. Completes proposal 157. Resolves ticket 10162.
16138 - Remove all code that existed to support the v2 directory system,
16139 since there are no longer any v2 directory authorities. Resolves
16141 - Remove the HSAuthoritativeDir and AlternateHSAuthority torrc
16142 options, which were used for designating authorities as "Hidden
16143 service authorities". There has been no use of hidden service
16144 authorities since 0.2.2.1-alpha, when we stopped uploading or
16145 downloading v0 hidden service descriptors. Fixes bug 10881; also
16146 part of a fix for bug 10841.
16148 o Code simplification and refactoring:
16149 - Remove some old fallback code designed to keep Tor clients working
16150 in a network with only two working relays. Elsewhere in the code we
16151 have long since stopped supporting such networks, so there wasn't
16152 much point in keeping it around. Addresses ticket 9926.
16153 - Reject 0-length EXTEND2 cells more explicitly. Fixes bug 10536;
16154 bugfix on 0.2.4.8-alpha. Reported by "cypherpunks".
16155 - Remove data structures which were introduced to implement the
16156 CellStatistics option: they are now redundant with the addition
16157 of a timestamp to the regular packed_cell_t data structure, which
16158 we did in 0.2.4.18-rc in order to resolve ticket 9093. Implements
16161 o Documentation (man page) fixes:
16162 - Update manpage to describe some of the files you can expect to
16163 find in Tor's DataDirectory. Addresses ticket 9839.
16164 - Document that all but one DirPort entry must have the NoAdvertise
16165 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
16167 o Documentation fixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
16168 - Clarify the usage and risks of setting the ContactInfo torrc line
16169 for your relay or bridge. Resolves ticket 9854.
16170 - Add anchors to the manpage so we can link to the html version of
16171 the documentation for specific options. Resolves ticket 9866.
16172 - Replace remaining references to DirServer in man page and
16173 log entries. Resolves ticket 10124.
16176 - Make the "tor-gencert" tool used by directory authority operators
16177 create 2048-bit signing keys by default (rather than 1024-bit, since
16178 1024-bit is uncomfortably small these days). Addresses ticket 10324.
16181 Changes in version 0.2.4.20 - 2013-12-22
16182 Tor 0.2.4.20 fixes potentially poor random number generation for users
16183 who 1) use OpenSSL 1.0.0 or later, 2) set "HardwareAccel 1" in their
16184 torrc file, 3) have "Sandy Bridge" or "Ivy Bridge" Intel processors,
16185 and 4) have no state file in their DataDirectory (as would happen on
16186 first start). Users who generated relay or hidden service identity
16187 keys in such a situation should discard them and generate new ones.
16189 This release also fixes a logic error that caused Tor clients to build
16190 many more preemptive circuits than they actually need.
16193 - Do not allow OpenSSL engines to replace the PRNG, even when
16194 HardwareAccel is set. The only default builtin PRNG engine uses
16195 the Intel RDRAND instruction to replace the entire PRNG, and
16196 ignores all attempts to seed it with more entropy. That's
16197 cryptographically stupid: the right response to a new alleged
16198 entropy source is never to discard all previously used entropy
16199 sources. Fixes bug 10402; works around behavior introduced in
16200 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
16202 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
16203 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
16204 - Avoid launching spurious extra circuits when a stream is pending.
16205 This fixes a bug where any circuit that _wasn't_ unusable for new
16206 streams would be treated as if it were, causing extra circuits to
16207 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
16210 - Avoid a crash bug when starting with a corrupted microdescriptor
16211 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
16212 - If we fail to dump a previously cached microdescriptor to disk, avoid
16213 freeing duplicate data later on. Fixes bug 10423; bugfix on
16214 0.2.4.13-alpha. Spotted by "bobnomnom".
16217 Changes in version 0.2.4.19 - 2013-12-11
16218 The Tor 0.2.4 release series is dedicated to the memory of Aaron Swartz
16219 (1986-2013). Aaron worked on diverse projects including helping to guide
16220 Creative Commons, playing a key role in stopping SOPA/PIPA, bringing
16221 transparency to the U.S government's PACER documents, and contributing
16222 design and development for Tor and Tor2Web. Aaron was one of the latest
16223 martyrs in our collective fight for civil liberties and human rights,
16224 and his death is all the more painful because he was one of us.
16226 Tor 0.2.4.19, the first stable release in the 0.2.4 branch, features
16227 a new circuit handshake and link encryption that use ECC to provide
16228 better security and efficiency; makes relays better manage circuit
16229 creation requests; uses "directory guards" to reduce client enumeration
16230 risks; makes bridges collect and report statistics about the pluggable
16231 transports they support; cleans up and improves our geoip database;
16232 gets much closer to IPv6 support for clients, bridges, and relays; makes
16233 directory authorities use measured bandwidths rather than advertised
16234 ones when computing flags and thresholds; disables client-side DNS
16235 caching to reduce tracking risks; and fixes a big bug in bridge
16236 reachability testing. This release introduces two new design
16237 abstractions in the code: a new "channel" abstraction between circuits
16238 and or_connections to allow for implementing alternate relay-to-relay
16239 transports, and a new "circuitmux" abstraction storing the queue of
16240 circuits for a channel. The release also includes many stability,
16241 security, and privacy fixes.
16244 Changes in version 0.2.4.18-rc - 2013-11-16
16245 Tor 0.2.4.18-rc is the fourth release candidate for the Tor 0.2.4.x
16246 series. It takes a variety of fixes from the 0.2.5.x branch to improve
16247 stability, performance, and better handling of edge cases.
16250 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
16251 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
16252 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
16253 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
16254 them to solve bug 6033.)
16257 - No longer stop reading or writing on cpuworker connections when
16258 our rate limiting buckets go empty. Now we should handle circuit
16259 handshake requests more promptly. Resolves bug 9731.
16260 - If we are unable to save a microdescriptor to the journal, do not
16261 drop it from memory and then reattempt downloading it. Fixes bug
16262 9645; bugfix on 0.2.2.6-alpha.
16263 - Stop trying to bootstrap all our directory information from
16264 only our first guard. Discovered while fixing bug 9946; bugfix
16266 - The new channel code sometimes lost track of in-progress circuits,
16267 causing long-running clients to stop building new circuits. The
16268 fix is to always call circuit_n_chan_done(chan, 0) from
16269 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
16271 o Minor bugfixes (on 0.2.4.x):
16272 - Correctly log long IPv6 exit policies, instead of truncating them
16273 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
16274 - Our default TLS ecdhe groups were backwards: we meant to be using
16275 P224 for relays (for performance win) and P256 for bridges (since
16276 it is more common in the wild). Instead we had it backwards. After
16277 reconsideration, we decided that the default should be P256 on all
16278 hosts, since its security is probably better, and since P224 is
16279 reportedly used quite little in the wild. Found by "skruffy" on
16280 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
16281 - Free directory authority certificate download statuses on exit
16282 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
16284 o Minor bugfixes (on 0.2.3.x and earlier):
16285 - If the guard we choose first doesn't answer, we would try the
16286 second guard, but once we connected to the second guard we would
16287 abandon it and retry the first one, slowing down bootstrapping.
16288 The fix is to treat all our initially chosen guards as acceptable
16289 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
16290 - Fix an assertion failure that would occur when disabling the
16291 ORPort setting on a running Tor process while accounting was
16292 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
16293 - When examining the list of network interfaces to find our address,
16294 do not consider non-running or disabled network interfaces. Fixes
16295 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
16296 - Avoid an off-by-one error when checking buffer boundaries when
16297 formatting the exit status of a pluggable transport helper.
16298 This is probably not an exploitable bug, but better safe than
16299 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
16302 o Minor features (protecting client timestamps):
16303 - Clients no longer send timestamps in their NETINFO cells. These were
16304 not used for anything, and they provided one small way for clients
16305 to be distinguished from each other as they moved from network to
16306 network or behind NAT. Implements part of proposal 222.
16307 - Clients now round timestamps in INTRODUCE cells down to the nearest
16308 10 minutes. If a new Support022HiddenServices option is set to 0, or
16309 if it's set to "auto" and the feature is disabled in the consensus,
16310 the timestamp is sent as 0 instead. Implements part of proposal 222.
16311 - Stop sending timestamps in AUTHENTICATE cells. This is not such
16312 a big deal from a security point of view, but it achieves no actual
16313 good purpose, and isn't needed. Implements part of proposal 222.
16314 - Reduce down accuracy of timestamps in hidden service descriptors.
16315 Implements part of proposal 222.
16317 o Minor features (other):
16318 - Improve the circuit queue out-of-memory handler. Previously, when
16319 we ran low on memory, we'd close whichever circuits had the most
16320 queued cells. Now, we close those that have the *oldest* queued
16321 cells, on the theory that those are most responsible for us
16322 running low on memory. Based on analysis from a forthcoming paper
16323 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
16324 - Generate bootstrapping status update events correctly when fetching
16325 microdescriptors. Fixes bug 9927.
16326 - Update to the October 2 2013 Maxmind GeoLite Country database.
16328 o Documentation fixes:
16329 - Clarify the usage and risks of setting the ContactInfo torrc line
16330 for your relay or bridge. Resolves ticket 9854.
16331 - Add anchors to the manpage so we can link to the html version of
16332 the documentation for specific options. Resolves ticket 9866.
16333 - Replace remaining references to DirServer in man page and
16334 log entries. Resolves ticket 10124.
16337 Changes in version 0.2.5.1-alpha - 2013-10-02
16338 Tor 0.2.5.1-alpha introduces experimental support for syscall sandboxing
16339 on Linux, allows bridges that offer pluggable transports to report usage
16340 statistics, fixes many issues to make testing easier, and provides
16341 a pile of minor features and bugfixes that have been waiting for a
16342 release of the new branch.
16344 This is the first alpha release in a new series, so expect there to
16345 be bugs. Users who would rather test out a more stable branch should
16346 stay with 0.2.4.x for now.
16348 o Major features (security):
16349 - Use the seccomp2 syscall filtering facility on Linux to limit
16350 which system calls Tor can invoke. This is an experimental,
16351 Linux-only feature to provide defense-in-depth against unknown
16352 attacks. To try turning it on, set "Sandbox 1" in your torrc
16353 file. Please be ready to report bugs. We hope to add support
16354 for better sandboxing in the future, including more fine-grained
16355 filters, better division of responsibility, and support for more
16356 platforms. This work has been done by Cristian-Matei Toader for
16357 Google Summer of Code.
16358 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
16359 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
16360 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
16361 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
16362 them to solve bug 6033.)
16364 o Major features (other):
16365 - Add support for passing arguments to managed pluggable transport
16366 proxies. Implements ticket 3594.
16367 - Bridges now track GeoIP information and the number of their users
16368 even when pluggable transports are in use, and report usage
16369 statistics in their extra-info descriptors. Resolves tickets 4773
16371 - Make testing Tor networks bootstrap better: lower directory fetch
16372 retry schedules and maximum interval without directory requests,
16373 and raise maximum download tries. Implements ticket 6752.
16374 - Add make target 'test-network' to run tests on a Chutney network.
16375 Implements ticket 8530.
16376 - The ntor handshake is now on-by-default, no matter what the
16377 directory authorities recommend. Implements ticket 8561.
16380 - Instead of writing destroy cells directly to outgoing connection
16381 buffers, queue them and intersperse them with other outgoing cells.
16382 This can prevent a set of resource starvation conditions where too
16383 many pending destroy cells prevent data cells from actually getting
16384 delivered. Reported by "oftc_must_be_destroyed". Fixes bug 7912;
16385 bugfix on 0.2.0.1-alpha.
16386 - If we are unable to save a microdescriptor to the journal, do not
16387 drop it from memory and then reattempt downloading it. Fixes bug
16388 9645; bugfix on 0.2.2.6-alpha.
16389 - The new channel code sometimes lost track of in-progress circuits,
16390 causing long-running clients to stop building new circuits. The
16391 fix is to always call circuit_n_chan_done(chan, 0) from
16392 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
16395 - Tor now builds each source file in two modes: a mode that avoids
16396 exposing identifiers needlessly, and another mode that exposes
16397 more identifiers for testing. This lets the compiler do better at
16398 optimizing the production code, while enabling us to take more
16399 radical measures to let the unit tests test things.
16400 - The production builds no longer include functions used only in
16401 the unit tests; all functions exposed from a module only for
16402 unit-testing are now static in production builds.
16403 - Add an --enable-coverage configuration option to make the unit
16404 tests (and a new src/or/tor-cov target) to build with gcov test
16408 - We now have rudimentary function mocking support that our unit
16409 tests can use to test functions in isolation. Function mocking
16410 lets the tests temporarily replace a function's dependencies with
16411 stub functions, so that the tests can check the function without
16412 invoking the other functions it calls.
16413 - Add more unit tests for the <circid,channel>->circuit map, and
16414 the destroy-cell-tracking code to fix bug 7912.
16415 - Unit tests for failing cases of the TAP onion handshake.
16416 - More unit tests for address-manipulation functions.
16418 o Minor features (protecting client timestamps):
16419 - Clients no longer send timestamps in their NETINFO cells. These were
16420 not used for anything, and they provided one small way for clients
16421 to be distinguished from each other as they moved from network to
16422 network or behind NAT. Implements part of proposal 222.
16423 - Clients now round timestamps in INTRODUCE cells down to the nearest
16424 10 minutes. If a new Support022HiddenServices option is set to 0, or
16425 if it's set to "auto" and the feature is disabled in the consensus,
16426 the timestamp is sent as 0 instead. Implements part of proposal 222.
16427 - Stop sending timestamps in AUTHENTICATE cells. This is not such
16428 a big deal from a security point of view, but it achieves no actual
16429 good purpose, and isn't needed. Implements part of proposal 222.
16430 - Reduce down accuracy of timestamps in hidden service descriptors.
16431 Implements part of proposal 222.
16433 o Minor features (config options):
16434 - Config (torrc) lines now handle fingerprints which are missing
16435 their initial '$'. Resolves ticket 4341; improvement over 0.0.9pre5.
16436 - Support a --dump-config option to print some or all of the
16437 configured options. Mainly useful for debugging the command-line
16438 option parsing code. Helps resolve ticket 4647.
16439 - Raise awareness of safer logging: notify user of potentially
16440 unsafe config options, like logging more verbosely than severity
16441 "notice" or setting SafeLogging to 0. Resolves ticket 5584.
16442 - Add a new configuration option TestingV3AuthVotingStartOffset
16443 that bootstraps a network faster by changing the timing for
16444 consensus votes. Addresses ticket 8532.
16445 - Add a new torrc option "ServerTransportOptions" that allows
16446 bridge operators to pass configuration parameters to their
16447 pluggable transports. Resolves ticket 8929.
16448 - The config (torrc) file now accepts bandwidth and space limits in
16449 bits as well as bytes. (Anywhere that you can say "2 Kilobytes",
16450 you can now say "16 kilobits", and so on.) Resolves ticket 9214.
16453 o Minor features (build):
16454 - Add support for `--library-versions` flag. Implements ticket 6384.
16455 - Return the "unexpected sendme" warnings to a warn severity, but make
16456 them rate limited, to help diagnose ticket 8093.
16457 - Detect a missing asciidoc, and warn the user about it, during
16458 configure rather than at build time. Fixes issue 6506. Patch from
16461 o Minor features (other):
16462 - Use the SOCK_NONBLOCK socket type, if supported, to open nonblocking
16463 sockets in a single system call. Implements ticket 5129.
16464 - Log current accounting state (bytes sent and received + remaining
16465 time for the current accounting period) in the relay's heartbeat
16466 message. Implements ticket 5526; patch from Peter Retzlaff.
16467 - Implement the TRANSPORT_LAUNCHED control port event that
16468 notifies controllers about new launched pluggable
16469 transports. Resolves ticket 5609.
16470 - If we're using the pure-C 32-bit curve25519_donna implementation
16471 of curve25519, build it with the -fomit-frame-pointer option to
16472 make it go faster on register-starved hosts. This improves our
16473 handshake performance by about 6% on i386 hosts without nacl.
16474 Closes ticket 8109.
16475 - Update to the September 4 2013 Maxmind GeoLite Country database.
16478 - Set the listen() backlog limit to the largest actually supported
16479 on the system, not to the value in a header file. Fixes bug 9716;
16480 bugfix on every released Tor.
16481 - No longer accept malformed http headers when parsing urls from
16482 headers. Now we reply with Bad Request ("400"). Fixes bug 2767;
16483 bugfix on 0.0.6pre1.
16484 - In munge_extrainfo_into_routerinfo(), check the return value of
16485 memchr(). This would have been a serious issue if we ever passed
16486 it a non-extrainfo. Fixes bug 8791; bugfix on 0.2.0.6-alpha. Patch
16488 - On the chance that somebody manages to build Tor on a
16489 platform where time_t is unsigned, correct the way that
16490 microdesc_add_to_cache() handles negative time arguments.
16491 Fixes bug 8042; bugfix on 0.2.3.1-alpha.
16492 - Reject relative control socket paths and emit a warning. Previously,
16493 single-component control socket paths would be rejected, but Tor
16494 would not log why it could not validate the config. Fixes bug 9258;
16495 bugfix on 0.2.3.16-alpha.
16497 o Minor bugfixes (command line):
16498 - Use a single command-line parser for parsing torrc options on the
16499 command line and for finding special command-line options to avoid
16500 inconsistent behavior for torrc option arguments that have the same
16501 names as command-line options. Fixes bugs 4647 and 9578; bugfix on
16503 - No longer allow 'tor --hash-password' with no arguments. Fixes bug
16504 9573; bugfix on 0.0.9pre5.
16506 o Minor fixes (build, auxiliary programs):
16507 - Stop preprocessing the "torify" script with autoconf, since
16508 it no longer refers to LOCALSTATEDIR. Fixes bug 5505; patch
16510 - The tor-fw-helper program now follows the standard convention and
16511 exits with status code "0" on success. Fixes bug 9030; bugfix on
16512 0.2.3.1-alpha. Patch by Arlo Breault.
16513 - Corrected ./configure advice for what openssl dev package you should
16514 install on Debian. Fixes bug 9207; bugfix on 0.2.0.1-alpha.
16516 o Minor code improvements:
16517 - Remove constants and tests for PKCS1 padding; it's insecure and
16518 shouldn't be used for anything new. Fixes bug 8792; patch
16520 - Remove instances of strcpy() from the unit tests. They weren't
16521 hurting anything, since they were only in the unit tests, but it's
16522 embarrassing to have strcpy() in the code at all, and some analysis
16523 tools don't like it. Fixes bug 8790; bugfix on 0.2.3.6-alpha and
16524 0.2.3.8-alpha. Patch from Arlo Breault.
16526 o Removed features:
16527 - Remove migration code from when we renamed the "cached-routers"
16528 file to "cached-descriptors" back in 0.2.0.8-alpha. This
16529 incidentally resolves ticket 6502 by cleaning up the related code
16530 a bit. Patch from Akshay Hebbar.
16532 o Code simplification and refactoring:
16533 - Extract the common duplicated code for creating a subdirectory
16534 of the data directory and writing to a file in it. Fixes ticket
16535 4282; patch from Peter Retzlaff.
16536 - Since OpenSSL 0.9.7, the i2d_*() functions support allocating output
16537 buffer. Avoid calling twice: i2d_RSAPublicKey(), i2d_DHparams(),
16538 i2d_X509(), and i2d_PublicKey(). Resolves ticket 5170.
16539 - Add a set of accessor functions for the circuit timeout data
16540 structure. Fixes ticket 6153; patch from "piet".
16541 - Clean up exit paths from connection_listener_new(). Closes ticket
16542 8789. Patch from Arlo Breault.
16543 - Since we rely on OpenSSL 0.9.8 now, we can use EVP_PKEY_cmp()
16544 and drop our own custom pkey_eq() implementation. Fixes bug 9043.
16545 - Use a doubly-linked list to implement the global circuit list.
16546 Resolves ticket 9108. Patch from Marek Majkowski.
16547 - Remove contrib/id_to_fp.c since it wasn't used anywhere.
16550 Changes in version 0.2.4.17-rc - 2013-09-05
16551 Tor 0.2.4.17-rc is the third release candidate for the Tor 0.2.4.x
16552 series. It adds an emergency step to help us tolerate the massive
16553 influx of users: 0.2.4 clients using the new (faster and safer) "NTor"
16554 circuit-level handshakes now effectively jump the queue compared to
16555 the 0.2.3 clients using "TAP" handshakes. This release also fixes a
16556 big bug hindering bridge reachability tests.
16559 - Relays now process the new "NTor" circuit-level handshake requests
16560 with higher priority than the old "TAP" circuit-level handshake
16561 requests. We still process some TAP requests to not totally starve
16562 0.2.3 clients when NTor becomes popular. A new consensus parameter
16563 "NumNTorsPerTAP" lets us tune the balance later if we need to.
16564 Implements ticket 9574.
16567 - If the circuit build timeout logic is disabled (via the consensus,
16568 or because we are an authority), then don't build testing circuits.
16569 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
16570 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
16571 previously they did not, which prevented them from receiving
16572 successful connections from relays for self-test or bandwidth
16573 testing. Also, when a relay is extending a circuit to a bridge,
16574 it needs to send a NETINFO cell, even when the bridge hasn't sent
16575 an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
16576 - If the time to download the next old-style networkstatus is in
16577 the future, do not decline to consider whether to download the
16578 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
16582 - Avoid double-closing the listener socket in our socketpair()
16583 replacement (used on Windows) in the case where the addresses on
16584 our opened sockets don't match what we expected. Fixes bug 9400;
16585 bugfix on 0.0.2pre7. Found by Coverity.
16587 o Minor fixes (config options):
16588 - Avoid overflows when the user sets MaxCircuitDirtiness to a
16589 ridiculously high value, by imposing a (ridiculously high) 30-day
16590 maximum on MaxCircuitDirtiness.
16591 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
16592 message is logged at notice, not at info.
16593 - Warn and fail if a server is configured not to advertise any
16594 ORPorts at all. (We need *something* to put in our descriptor,
16595 or we just won't work.)
16598 - Track how many "TAP" and "NTor" circuit handshake requests we get,
16599 and how many we complete, and log it every hour to help relay
16600 operators follow trends in network load. Addresses ticket 9658.
16601 - Update to the August 7 2013 Maxmind GeoLite Country database.
16604 Changes in version 0.2.4.16-rc - 2013-08-10
16605 Tor 0.2.4.16-rc is the second release candidate for the Tor 0.2.4.x
16606 series. It fixes several crash bugs in the 0.2.4 branch.
16609 - Fix a bug in the voting algorithm that could yield incorrect results
16610 when a non-naming authority declared too many flags. Fixes bug 9200;
16611 bugfix on 0.2.0.3-alpha.
16612 - Fix an uninitialized read that could in some cases lead to a remote
16613 crash while parsing INTRODUCE2 cells. Bugfix on 0.2.4.1-alpha.
16614 Anybody running a hidden service on the experimental 0.2.4.x
16615 branch should upgrade. (This is, so far as we know, unrelated to
16617 - Avoid an assertion failure when processing DNS replies without the
16618 answer types we expected. Fixes bug 9337; bugfix on 0.2.4.7-alpha.
16619 - Avoid a crash when using --hash-password. Fixes bug 9295; bugfix on
16620 0.2.4.15-rc. Found by stem integration tests.
16623 - Fix an invalid memory read that occurred when a pluggable
16624 transport proxy failed its configuration protocol.
16625 Fixes bug 9288; bugfix on 0.2.4.1-alpha.
16626 - When evaluating whether to use a connection that we haven't
16627 decided is canonical using a recent link protocol version,
16628 decide that it's canonical only if it used address _does_
16629 match the desired address. Fixes bug 9309; bugfix on
16630 0.2.4.4-alpha. Reported by skruffy.
16631 - Make the default behavior of NumDirectoryGuards be to track
16632 NumEntryGuards. Now a user who changes only NumEntryGuards will get
16633 the behavior she expects. Fixes bug 9354; bugfix on 0.2.4.8-alpha.
16634 - Fix a spurious compilation warning with some older versions of
16635 GCC on FreeBSD. Fixes bug 9254; bugfix on 0.2.4.14-alpha.
16638 - Update to the July 3 2013 Maxmind GeoLite Country database.
16641 Changes in version 0.2.4.15-rc - 2013-07-01
16642 Tor 0.2.4.15-rc is the first release candidate for the Tor 0.2.4.x
16643 series. It fixes a few smaller bugs, but generally appears stable.
16644 Please test it and let us know whether it is!
16647 - When receiving a new configuration file via the control port's
16648 LOADCONF command, do not treat the defaults file as absent.
16649 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
16652 - Issue a warning when running with the bufferevents backend enabled.
16653 It's still not stable, and people should know that they're likely
16654 to hit unexpected problems. Closes ticket 9147.
16657 Changes in version 0.2.4.14-alpha - 2013-06-18
16658 Tor 0.2.4.14-alpha fixes a pair of client guard enumeration problems
16659 present in 0.2.4.13-alpha.
16662 - When we have too much memory queued in circuits (according to a new
16663 MaxMemInCellQueues option), close the circuits consuming the most
16664 memory. This prevents us from running out of memory as a relay if
16665 circuits fill up faster than they can be drained. Fixes bug 9063;
16666 bugfix on the 54th commit of Tor. This bug is a further fix beyond
16667 bug 6252, whose fix was merged into 0.2.3.21-rc.
16669 This change also fixes an earlier approach taken in 0.2.4.13-alpha,
16670 where we tried to solve this issue simply by imposing an upper limit
16671 on the number of queued cells for a single circuit. That approach
16672 proved to be problematic, since there are ways to provoke clients to
16673 send a number of cells in excess of any such reasonable limit. Fixes
16674 bug 9072; bugfix on 0.2.4.13-alpha.
16676 - Limit hidden service descriptors to at most ten introduction
16677 points, to slow one kind of guard enumeration. Fixes bug 9002;
16678 bugfix on 0.1.1.11-alpha.
16681 Changes in version 0.2.4.13-alpha - 2013-06-14
16682 Tor 0.2.4.13-alpha fixes a variety of potential remote crash
16683 vulnerabilities, makes socks5 username/password circuit isolation
16684 actually actually work (this time for sure!), and cleans up a bunch
16685 of other issues in preparation for a release candidate.
16687 o Major bugfixes (robustness):
16688 - Close any circuit that has too many cells queued on it. Fixes
16689 bug 9063; bugfix on the 54th commit of Tor. This bug is a further
16690 fix beyond bug 6252, whose fix was merged into 0.2.3.21-rc.
16691 - Prevent the get_freelists() function from running off the end of
16692 the list of freelists if it somehow gets an unrecognized
16693 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
16695 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
16696 when an exit connection with optimistic data succeeds immediately
16697 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
16699 - Fix a directory authority crash bug when building a consensus
16700 using an older consensus as its basis. Fixes bug 8833. Bugfix
16704 - Avoid a memory leak where we would leak a consensus body when we
16705 find that a consensus which we couldn't previously verify due to
16706 missing certificates is now verifiable. Fixes bug 8719; bugfix
16708 - We used to always request authority certificates by identity digest,
16709 meaning we'd get the newest one even when we wanted one with a
16710 different signing key. Then we would complain about being given
16711 a certificate we already had, and never get the one we really
16712 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
16713 resource to request the one we want. Fixes bug 5595; bugfix on
16715 - Follow the socks5 protocol when offering username/password
16716 authentication. The fix for bug 8117 exposed this bug, and it
16717 turns out real-world applications like Pidgin do care. Bugfix on
16718 0.2.3.2-alpha; fixes bug 8879.
16719 - Prevent failures on Windows Vista and later when rebuilding the
16720 microdescriptor cache. Diagnosed by Robert Ransom. Fixes bug 8822;
16721 bugfix on 0.2.4.12-alpha.
16724 - Fix an impossible buffer overrun in the AES unit tests. Fixes
16725 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
16726 - If for some reason we fail to write a microdescriptor while
16727 rebuilding the cache, do not let the annotations from that
16728 microdescriptor linger in the cache file, and do not let the
16729 microdescriptor stay recorded as present in its old location.
16730 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
16731 - Fix a memory leak that would occur whenever a configuration
16732 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
16733 - Paste the description for PathBias parameters from the man
16734 page into or.h, so the code documents them too. Fixes bug 7982;
16735 bugfix on 0.2.3.17-beta and 0.2.4.8-alpha.
16736 - Relays now treat a changed IPv6 ORPort as sufficient reason to
16737 publish an updated descriptor. Fixes bug 6026; bugfix on
16739 - When launching a resolve request on behalf of an AF_UNIX control
16740 socket, omit the address field of the new entry connection, used in
16741 subsequent controller events, rather than letting tor_dup_addr()
16742 set it to "<unknown address type>". Fixes bug 8639; bugfix on
16745 o Minor bugfixes (log messages):
16746 - Fix a scaling issue in the path bias accounting code that
16747 resulted in "Bug:" log messages from either
16748 pathbias_scale_close_rates() or pathbias_count_build_success().
16749 This represents a bugfix on a previous bugfix: the original fix
16750 attempted in 0.2.4.10-alpha was incomplete. Fixes bug 8235; bugfix
16752 - Give a less useless error message when the user asks for an IPv4
16753 address on an IPv6-only port, or vice versa. Fixes bug 8846; bugfix
16757 - Downgrade "unexpected SENDME" warnings to protocol-warn for 0.2.4.x,
16758 to tolerate bug 8093 for now.
16759 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
16760 in directory authority votes to describe whether they have enough
16761 measured bandwidths to ignore advertised (relay descriptor)
16762 bandwidth claims. Resolves ticket 8711.
16763 - Update to the June 5 2013 Maxmind GeoLite Country database.
16765 o Removed documentation:
16766 - Remove some of the older contents of doc/ as obsolete; move others
16767 to torspec.git. Fixes bug 8965.
16769 o Code simplification and refactoring:
16770 - Avoid using character buffers when constructing most directory
16771 objects: this approach was unwieldy and error-prone. Instead,
16772 build smartlists of strings, and concatenate them when done.
16775 Changes in version 0.2.4.12-alpha - 2013-04-18
16776 Tor 0.2.4.12-alpha moves Tor forward on several fronts: it starts the
16777 process for lengthening the guard rotation period, makes directory
16778 authority opinions in the consensus a bit less gameable, makes socks5
16779 username/password circuit isolation actually work, and fixes a wide
16780 variety of other issues.
16783 - Raise the default time that a client keeps an entry guard from
16784 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
16785 2012 paper. (We would make it even longer, but we need better client
16786 load balancing first.) Also, make the guard lifetime controllable
16787 via a new GuardLifetime torrc option and a GuardLifetime consensus
16788 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
16789 - Directory authorities now prefer using measured bandwidths to
16790 advertised ones when computing flags and thresholds. Resolves
16792 - Directory authorities that have more than a threshold number
16793 of relays with measured bandwidths now treat relays with unmeasured
16794 bandwidths as having bandwidth 0. Resolves ticket 8435.
16796 o Major bugfixes (assert / resource use):
16797 - Avoid a bug where our response to TLS renegotiation under certain
16798 network conditions could lead to a busy-loop, with 100% CPU
16799 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
16800 - Avoid an assertion when we discover that we'd like to write a cell
16801 onto a closing connection: just discard the cell. Fixes another
16802 case of bug 7350; bugfix on 0.2.4.4-alpha.
16804 o Major bugfixes (client-side privacy):
16805 - When we mark a circuit as unusable for new circuits, have it
16806 continue to be unusable for new circuits even if MaxCircuitDirtiness
16807 is increased too much at the wrong time, or the system clock jumps
16808 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
16809 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
16810 which have resolved to internal addresses") is set, apply that
16811 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
16812 - When an exit relay rejects a stream with reason "exit policy", but
16813 we only know an exit policy summary (e.g. from the microdesc
16814 consensus) for it, do not mark the relay as useless for all exiting.
16815 Instead, mark just the circuit as unsuitable for that particular
16816 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
16817 - Allow applications to get proper stream isolation with
16818 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
16819 username/password authentication also offer "no authentication". Tor
16820 had previously preferred "no authentication", so the applications
16821 never actually sent Tor their auth details. Now Tor selects
16822 username/password authentication if it's offered. You can disable
16823 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
16824 bug 8117; bugfix on 0.2.3.3-alpha.
16826 o Major bugfixes (other):
16827 - When unable to find any working directory nodes to use as a
16828 directory guard, give up rather than adding the same non-working
16829 nodes to the directory guard list over and over. Fixes bug 8231;
16830 bugfix on 0.2.4.8-alpha.
16833 - Reject as invalid most directory objects containing a NUL.
16834 Belt-and-suspender fix for bug 8037.
16835 - In our testsuite, create temporary directories with a bit more
16836 entropy in their name to make name collisions less likely. Fixes
16838 - Add CACHED keyword to ADDRMAP events in the control protocol
16839 to indicate whether a DNS result will be cached or not. Resolves
16841 - Update to the April 3 2013 Maxmind GeoLite Country database.
16843 o Minor features (build):
16844 - Detect and reject attempts to build Tor with threading support
16845 when OpenSSL has been compiled without threading support.
16847 - Clarify that when autoconf is checking for nacl, it is checking
16848 specifically for nacl with a fast curve25519 implementation.
16850 - Warn if building on a platform with an unsigned time_t: there
16851 are too many places where Tor currently assumes that time_t can
16852 hold negative values. We'd like to fix them all, but probably
16855 o Minor bugfixes (build):
16856 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
16857 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
16858 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
16859 - Add the old src/or/micro-revision.i filename to CLEANFILES.
16860 On the off chance that somebody has one, it will go away as soon
16861 as they run "make clean". Fix for bug 7143; bugfix on 0.2.4.1-alpha.
16862 - Build Tor correctly on 32-bit platforms where the compiler can build
16863 but not run code using the "uint128_t" construction. Fixes bug 8587;
16864 bugfix on 0.2.4.8-alpha.
16865 - Fix compilation warning with some versions of clang that would
16866 prefer the -Wswitch-enum compiler flag to warn about switch
16867 statements with missing enum values, even if those switch
16868 statements have a "default:" statement. Fixes bug 8598; bugfix
16871 o Minor bugfixes (protocol):
16872 - Fix the handling of a TRUNCATE cell when it arrives while the
16873 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
16874 - Fix a misframing issue when reading the version numbers in a
16875 VERSIONS cell. Previously we would recognize [00 01 00 02] as
16876 'version 1, version 2, and version 0x100', when it should have
16877 only included versions 1 and 2. Fixes bug 8059; bugfix on
16878 0.2.0.10-alpha. Reported pseudonymously.
16879 - Make the format and order of STREAM events for DNS lookups
16880 consistent among the various ways to launch DNS lookups. Fixes
16881 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy".
16882 - Correct our check for which versions of Tor support the EXTEND2
16883 cell. We had been willing to send it to Tor 0.2.4.7-alpha and
16884 later, when support was really added in version 0.2.4.8-alpha.
16885 Fixes bug 8464; bugfix on 0.2.4.8-alpha.
16887 o Minor bugfixes (other):
16888 - Correctly store microdescriptors and extrainfo descriptors with
16889 an internal NUL byte. Fixes bug 8037; bugfix on 0.2.0.1-alpha.
16890 Bug reported by "cypherpunks".
16891 - Increase the width of the field used to remember a connection's
16892 link protocol version to two bytes. Harmless for now, since the
16893 only currently recognized versions are one byte long. Reported
16894 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
16895 - If the state file's path bias counts are invalid (presumably from a
16896 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
16897 additional checks and log messages to the scaling of Path Bias
16898 counts, in case there still are remaining issues with scaling.
16899 Should help resolve bug 8235.
16900 - Eliminate several instances where we use "Nickname=ID" to refer to
16901 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
16902 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
16903 on 0.2.3.21-rc, 0.2.4.5-alpha, 0.2.4.8-alpha, and 0.2.4.10-alpha.
16905 o Minor bugfixes (syscalls):
16906 - Always check the return values of functions fcntl() and
16907 setsockopt(). We don't believe these are ever actually failing in
16908 practice, but better safe than sorry. Also, checking these return
16909 values should please analysis tools like Coverity. Patch from
16910 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
16911 - Use direct writes rather than stdio when building microdescriptor
16912 caches, in an attempt to mitigate bug 8031, or at least make it
16915 o Minor bugfixes (config):
16916 - When rejecting a configuration because we were unable to parse a
16917 quoted string, log an actual error message. Fixes bug 7950; bugfix
16919 - Behave correctly when the user disables LearnCircuitBuildTimeout
16920 but doesn't tell us what they would like the timeout to be. Fixes
16921 bug 6304; bugfix on 0.2.2.14-alpha.
16922 - When autodetecting the number of CPUs, use the number of available
16923 CPUs in preference to the number of configured CPUs. Inform the
16924 user if this reduces the number of available CPUs. Fixes bug 8002;
16925 bugfix on 0.2.3.1-alpha.
16926 - Make it an error when you set EntryNodes but disable UseGuardNodes,
16927 since it will (surprisingly to some users) ignore EntryNodes. Fixes
16928 bug 8180; bugfix on 0.2.3.11-alpha.
16929 - Allow TestingTorNetworks to override the 4096-byte minimum for
16930 the Fast threshold. Otherwise they can't bootstrap until they've
16931 observed more traffic. Fixes bug 8508; bugfix on 0.2.4.10-alpha.
16932 - Fix some logic errors when the user manually overrides the
16933 PathsNeededToBuildCircuits option in torrc. Fixes bug 8599; bugfix
16936 o Minor bugfixes (log messages to help diagnose bugs):
16937 - If we fail to free a microdescriptor because of bug 7164, log
16938 the filename and line number from which we tried to free it.
16939 - Add another diagnostic to the heartbeat message: track and log
16940 overhead that TLS is adding to the data we write. If this is
16941 high, we are sending too little data to SSL_write at a time.
16942 Diagnostic for bug 7707.
16943 - Add more detail to a log message about relaxed timeouts, to help
16945 - Warn more aggressively when flushing microdescriptors to a
16946 microdescriptor cache fails, in an attempt to mitigate bug 8031,
16947 or at least make it more diagnosable.
16948 - Improve debugging output to help track down bug 8185 ("Bug:
16949 outgoing relay cell has n_chan==NULL. Dropping.")
16950 - Log the purpose of a path-bias testing circuit correctly.
16951 Improves a log message from bug 8477; bugfix on 0.2.4.8-alpha.
16953 o Minor bugfixes (0.2.4.x log messages that were too noisy):
16954 - Don't attempt to relax the timeout of already opened 1-hop circuits.
16955 They might never timeout. This should eliminate some/all cases of
16956 the relaxed timeout log message.
16957 - Use circuit creation time for network liveness evaluation. This
16958 should eliminate warning log messages about liveness caused
16959 by changes in timeout evaluation. Fixes bug 6572; bugfix on
16961 - Reduce a path bias length check from notice to info. The message
16962 is triggered when creating controller circuits. Fixes bug 8196;
16963 bugfix on 0.2.4.8-alpha.
16964 - Fix a path state issue that triggered a notice during relay startup.
16965 Fixes bug 8320; bugfix on 0.2.4.10-alpha.
16966 - Reduce occurrences of warns about circuit purpose in
16967 connection_ap_expire_building(). Fixes bug 8477; bugfix on
16970 o Minor bugfixes (pre-0.2.4.x log messages that were too noisy):
16971 - If we encounter a write failure on a SOCKS connection before we
16972 finish our SOCKS handshake, don't warn that we closed the
16973 connection before we could send a SOCKS reply. Fixes bug 8427;
16974 bugfix on 0.1.0.1-rc.
16975 - Correctly recognize that [::1] is a loopback address. Fixes
16976 bug 8377; bugfix on 0.2.1.3-alpha.
16977 - Fix a directory authority warn caused when we have a large amount
16978 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
16979 - Don't log inappropriate heartbeat messages when hibernating: a
16980 hibernating node is _expected_ to drop out of the consensus,
16981 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
16982 bugfix on 0.2.3.1-alpha.
16983 - Don't complain about bootstrapping problems while hibernating.
16984 These complaints reflect a general code problem, but not one
16985 with any problematic effects (no connections are actually
16986 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
16988 o Documentation fixes:
16989 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
16990 names match. Fixes bug 7768.
16991 - Make the torify manpage no longer refer to tsocks; torify hasn't
16992 supported tsocks since 0.2.3.14-alpha.
16993 - Make the tor manpage no longer reference tsocks.
16994 - Fix the GeoIPExcludeUnknown documentation to refer to
16995 ExcludeExitNodes rather than the currently nonexistent
16996 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
16999 - The tor-tsocks.conf is no longer distributed or installed. We
17000 recommend that tsocks users use torsocks instead. Resolves
17004 Changes in version 0.2.4.11-alpha - 2013-03-11
17005 Tor 0.2.4.11-alpha makes relay measurement by directory authorities
17006 more robust, makes hidden service authentication work again, and
17007 resolves a DPI fingerprint for Tor's SSL transport.
17009 o Major features (directory authorities):
17010 - Directory authorities now support a new consensus method (17)
17011 where they cap the published bandwidth of servers for which
17012 insufficient bandwidth measurements exist. Fixes part of bug 2286.
17013 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
17014 serve any v2 directory information. Now we can test disabling the
17015 old deprecated v2 directory format, and see whether doing so has
17016 any effect on network load. Begins to fix bug 6783.
17017 - Directory authorities now include inside each vote a statement of
17018 the performance thresholds they used when assigning flags.
17019 Implements ticket 8151.
17021 o Major bugfixes (directory authorities):
17022 - Stop marking every relay as having been down for one hour every
17023 time we restart a directory authority. These artificial downtimes
17024 were messing with our Stable and Guard flag calculations. Fixes
17025 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
17027 o Major bugfixes (hidden services):
17028 - Allow hidden service authentication to succeed again. When we
17029 refactored the hidden service introduction code back
17030 in 0.2.4.1-alpha, we didn't update the code that checks
17031 whether authentication information is present, causing all
17032 authentication checks to return "false". Fix for bug 8207; bugfix
17033 on 0.2.4.1-alpha. Found by Coverity; this is CID 718615.
17035 o Minor features (relays, bridges):
17036 - Make bridge relays check once a minute for whether their IP
17037 address has changed, rather than only every 15 minutes. Resolves
17038 bugs 1913 and 1992.
17039 - Refactor resolve_my_address() so it returns the method by which we
17040 decided our public IP address (explicitly configured, resolved from
17041 explicit hostname, guessed from interfaces, learned by gethostname).
17042 Now we can provide more helpful log messages when a relay guesses
17043 its IP address incorrectly (e.g. due to unexpected lines in
17044 /etc/hosts). Resolves ticket 2267.
17045 - Teach bridge-using clients to avoid 0.2.2 bridges when making
17046 microdescriptor-related dir requests, and only fall back to normal
17047 descriptors if none of their bridges can handle microdescriptors
17048 (as opposed to the fix in ticket 4013, which caused them to fall
17049 back to normal descriptors if *any* of their bridges preferred
17050 them). Resolves ticket 4994.
17051 - Randomize the lifetime of our SSL link certificate, so censors can't
17052 use the static value for filtering Tor flows. Resolves ticket 8443;
17053 related to ticket 4014 which was included in 0.2.2.33.
17054 - Support a new version of the link protocol that allows 4-byte circuit
17055 IDs. Previously, circuit IDs were limited to 2 bytes, which presented
17056 a possible resource exhaustion issue. Closes ticket 7351; implements
17059 o Minor features (portability):
17060 - Tweak the curve25519-donna*.c implementations to tolerate systems
17061 that lack stdint.h. Fixes bug 3894; bugfix on 0.2.4.8-alpha.
17062 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
17063 the signs of types during autoconf. This is better than our old
17064 approach, which didn't work when cross-compiling.
17065 - Detect the sign of enum values, rather than assuming that MSC is the
17066 only compiler where enum types are all signed. Fixes bug 7727;
17067 bugfix on 0.2.4.10-alpha.
17069 o Minor features (other):
17070 - Say "KBytes" rather than "KB" in the man page (for various values
17071 of K), to further reduce confusion about whether Tor counts in
17072 units of memory or fractions of units of memory. Resolves ticket 7054.
17073 - Clear the high bit on curve25519 public keys before passing them to
17074 our backend, in case we ever wind up using a backend that doesn't do
17075 so itself. If we used such a backend, and *didn't* clear the high bit,
17076 we could wind up in a situation where users with such backends would
17077 be distinguishable from users without. Fixes bug 8121; bugfix on
17079 - Update to the March 6 2013 Maxmind GeoLite Country database.
17081 o Minor bugfixes (clients):
17082 - When we receive a RELAY_END cell with the reason DONE, or with no
17083 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
17084 status as "connection refused". Previously we reported these cases
17085 as success but then immediately closed the connection. Fixes bug
17086 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
17087 - Downgrade an assertion in connection_ap_expire_beginning to an
17088 LD_BUG message. The fix for bug 8024 should prevent this message
17089 from displaying, but just in case, a warn that we can diagnose
17090 is better than more assert crashes. Fixes bug 8065; bugfix on
17092 - Lower path use bias thresholds to .80 for notice and .60 for warn.
17093 Also make the rate limiting flags for the path use bias log messages
17094 independent from the original path bias flags. Fixes bug 8161;
17095 bugfix on 0.2.4.10-alpha.
17097 o Minor bugfixes (relays):
17098 - Stop trying to resolve our hostname so often (e.g. every time we
17099 think about doing a directory fetch). Now we reuse the cached
17100 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
17101 and 2410 (bugfix on 0.1.2.2-alpha).
17102 - Stop sending a stray "(null)" in some cases for the server status
17103 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
17105 - When choosing which stream on a formerly stalled circuit to wake
17106 first, make better use of the platform's weak RNG. Previously,
17107 we had been using the % ("modulo") operator to try to generate a
17108 1/N chance of picking each stream, but this behaves badly with
17109 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
17111 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
17112 Irix's random() only return 15 bits; Solaris's random() returns more
17113 bits but its RAND_MAX says it only returns 15, and so on. Motivated
17114 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
17116 o Minor bugfixes (directory authorities):
17117 - Directory authorities now use less space when formatting identical
17118 microdescriptor lines in directory votes. Fixes bug 8158; bugfix
17121 o Minor bugfixes (memory leaks spotted by Coverity -- bug 7816):
17122 - Avoid leaking memory if we fail to compute a consensus signature
17123 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
17124 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
17126 - Fix a memory leak during safe-cookie controller authentication.
17127 Bugfix on 0.2.3.13-alpha.
17128 - Avoid memory leak of IPv6 policy content if we fail to format it into
17129 a router descriptor. Bugfix on 0.2.4.7-alpha.
17131 o Minor bugfixes (other code correctness issues):
17132 - Avoid a crash if we fail to generate an extrainfo descriptor.
17133 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
17134 this is CID 718634.
17135 - When detecting the largest possible file descriptor (in order to
17136 close all file descriptors when launching a new program), actually
17137 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
17138 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
17140 - Fix a copy-and-paste error when adding a missing A1 to a routerset
17141 because of GeoIPExcludeUnknown. Fix for Coverity CID 980650.
17142 Bugfix on 0.2.4.10-alpha.
17143 - Fix an impossible-to-trigger integer overflow when estimating how
17144 long our onionskin queue would take. (This overflow would require us
17145 to accept 4 million onionskins before processing 100 of them.) Fixes
17146 bug 8210; bugfix on 0.2.4.10-alpha.
17148 o Code simplification and refactoring:
17149 - Add a wrapper function for the common "log a message with a
17153 Changes in version 0.2.4.10-alpha - 2013-02-04
17154 Tor 0.2.4.10-alpha adds defenses at the directory authority level from
17155 certain attacks that flood the network with relays; changes the queue
17156 for circuit create requests from a sized-based limit to a time-based
17157 limit; resumes building with MSVC on Windows; and fixes a wide variety
17160 o Major bugfixes (directory authority):
17161 - When computing directory thresholds, ignore any rejected-as-sybil
17162 nodes during the computation so that they can't influence Fast,
17163 Guard, etc. (We should have done this for proposal 109.) Fixes
17165 - When marking a node as a likely sybil, reset its uptime metrics
17166 to zero, so that it cannot time towards getting marked as Guard,
17167 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
17171 - When a TLS write is partially successful but incomplete, remember
17172 that the flushed part has been flushed, and notice that bytes were
17173 actually written. Reported and fixed pseudonymously. Fixes bug
17174 7708; bugfix on Tor 0.1.0.5-rc.
17175 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
17176 ID: these could be used to create unexpected streams and circuits
17177 which would count as "present" to some parts of Tor but "absent"
17178 to others, leading to zombie circuits and streams or to a bandwidth
17179 denial-of-service. Fixes bug 7889; bugfix on every released version
17180 of Tor. Reported by "oftc_must_be_destroyed".
17181 - Rename all macros in our local copy of queue.h to begin with "TOR_".
17182 This change seems the only good way to permanently prevent conflicts
17183 with queue.h on various operating systems. Fixes bug 8107; bugfix
17186 o Major features (relay):
17187 - Instead of limiting the number of queued onionskins (aka circuit
17188 create requests) to a fixed, hard-to-configure number, we limit
17189 the size of the queue based on how many we expect to be able to
17190 process in a given amount of time. We estimate the time it will
17191 take to process an onionskin based on average processing time
17192 of previous onionskins. Closes ticket 7291. You'll never have to
17193 configure MaxOnionsPending again.
17195 o Major features (portability):
17196 - Resume building correctly with MSVC and Makefile.nmake. This patch
17197 resolves numerous bugs and fixes reported by ultramage, including
17198 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
17199 - Make the ntor and curve25519 code build correctly with MSVC.
17200 Fix on 0.2.4.8-alpha.
17203 - When directory authorities are computing thresholds for flags,
17204 never let the threshold for the Fast flag fall below 4096
17205 bytes. Also, do not consider nodes with extremely low bandwidths
17206 when deciding thresholds for various directory flags. This change
17207 should raise our threshold for Fast relays, possibly in turn
17208 improving overall network performance; see ticket 1854. Resolves
17210 - The Tor client now ignores sub-domain components of a .onion
17211 address. This change makes HTTP "virtual" hosting
17212 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
17213 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
17214 hosted on the same hidden service. Implements proposal 204.
17215 - We compute the overhead from passing onionskins back and forth to
17216 cpuworkers, and report it when dumping statistics in response to
17217 SIGUSR1. Supports ticket 7291.
17219 o Minor features (path selection):
17220 - When deciding whether we have enough descriptors to build circuits,
17221 instead of looking at raw relay counts, look at which fraction
17222 of (bandwidth-weighted) paths we're able to build. This approach
17223 keeps clients from building circuits if their paths are likely to
17224 stand out statistically. The default fraction of paths needed is
17225 taken from the consensus directory; you can override it with the
17226 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
17227 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
17228 and we have GeoIP information, also exclude all nodes with unknown
17229 countries "??" and "A1". This behavior is controlled by the
17230 new GeoIPExcludeUnknown option: you can make such nodes always
17231 excluded with "GeoIPExcludeUnknown 1", and disable the feature
17232 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
17233 gets you the default behavior. Implements feature 7706.
17234 - Path Use Bias: Perform separate accounting for successful circuit
17235 use. Keep separate statistics on stream attempt rates versus stream
17236 success rates for each guard. Provide configurable thresholds to
17237 determine when to emit log messages or disable use of guards that
17238 fail too many stream attempts. Resolves ticket 7802.
17240 o Minor features (log messages):
17241 - When learning a fingerprint for a bridge, log its corresponding
17242 transport type. Implements ticket 7896.
17243 - Improve the log message when "Bug/attack: unexpected sendme cell
17244 from client" occurs, to help us track bug 8093.
17247 - Remove a couple of extraneous semicolons that were upsetting the
17248 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
17249 bugfix on 0.2.2.1-alpha.
17250 - Remove a source of rounding error during path bias count scaling;
17251 don't count cannibalized circuits as used for path bias until we
17252 actually try to use them; and fix a circuit_package_relay_cell()
17253 warning message about n_chan==NULL. Fixes bug 7802.
17254 - Detect nacl when its headers are in a nacl/ subdirectory. Also,
17255 actually link against nacl when we're configured to use it. Fixes
17256 bug 7972; bugfix on 0.2.4.8-alpha.
17257 - Compile correctly with the --disable-curve25519 option. Fixes
17258 bug 8153; bugfix on 0.2.4.8-alpha.
17260 o Build improvements:
17261 - Do not report status verbosely from autogen.sh unless the -v flag
17262 is specified. Fixes issue 4664. Patch from Onizuka.
17263 - Replace all calls to snprintf() outside of src/ext with
17264 tor_snprintf(). Also remove the #define to replace snprintf with
17265 _snprintf on Windows; they have different semantics, and all of
17266 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
17267 - Try to detect if we are ever building on a platform where
17268 memset(...,0,...) does not set the value of a double to 0.0. Such
17269 platforms are permitted by the C standard, though in practice
17270 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
17271 currently support them, but it's better to detect them and fail
17272 than to perform erroneously.
17274 o Removed features:
17275 - Stop exporting estimates of v2 and v3 directory traffic shares
17276 in extrainfo documents. They were unneeded and sometimes inaccurate.
17277 Also stop exporting any v2 directory request statistics. Resolves
17279 - Drop support for detecting and warning about versions of Libevent
17280 before 1.3e. Nothing reasonable ships with them any longer;
17281 warning the user about them shouldn't be needed. Resolves ticket
17284 o Code simplifications and refactoring:
17285 - Rename "isin" functions to "contains", for grammar. Resolves
17287 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
17288 with the natural logarithm function from the system libm. Resolves
17292 Changes in version 0.2.4.9-alpha - 2013-01-15
17293 Tor 0.2.4.9-alpha provides a quick fix to make the new ntor handshake
17294 work more robustly.
17297 - Fix backward compatibility logic when receiving an embedded ntor
17298 handshake tunneled in a CREATE cell. This clears up the "Bug:
17299 couldn't format CREATED cell" warning. Fixes bug 7959; bugfix
17303 Changes in version 0.2.4.8-alpha - 2013-01-14
17304 Tor 0.2.4.8-alpha introduces directory guards to reduce user enumeration
17305 risks, adds a new stronger and faster circuit handshake, and offers
17306 stronger and faster link encryption when both sides support it.
17309 - Preliminary support for directory guards (proposal 207): when
17310 possible, clients now use their entry guards for non-anonymous
17311 directory requests. This can help prevent client enumeration. Note
17312 that this behavior only works when we have a usable consensus
17313 directory, and when options about what to download are more or less
17314 standard. In the future we should re-bootstrap from our guards,
17315 rather than re-bootstrapping from the preconfigured list of
17316 directory sources that ships with Tor. Resolves ticket 6526.
17317 - Tor relays and clients now support a better CREATE/EXTEND cell
17318 format, allowing the sender to specify multiple address, identity,
17319 and handshake types. Implements Robert Ransom's proposal 200;
17320 closes ticket 7199.
17322 o Major features (new circuit handshake):
17323 - Tor now supports a new circuit extension handshake designed by Ian
17324 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
17325 circuit extension handshake, later called "TAP", was a bit slow
17326 (especially on the relay side), had a fragile security proof, and
17327 used weaker keys than we'd now prefer. The new circuit handshake
17328 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
17329 function, making it significantly more secure than the older
17330 handshake, and significantly faster. Tor can use one of two built-in
17331 pure-C curve25519-donna implementations by Adam Langley, or it
17332 can link against the "nacl" library for a tuned version if present.
17334 The built-in version is very fast for 64-bit systems when building
17335 with GCC. The built-in 32-bit version is still faster than the
17336 old TAP protocol, but using libnacl is better on most such hosts.
17338 Clients don't currently use this protocol by default, since
17339 comparatively few clients support it so far. To try it, set
17340 UseNTorHandshake to 1.
17342 Implements proposal 216; closes ticket 7202.
17344 o Major features (better link encryption):
17345 - Relays can now enable the ECDHE TLS ciphersuites when available
17346 and appropriate. These ciphersuites let us negotiate forward-secure
17347 TLS secret keys more safely and more efficiently than with our
17348 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
17349 public relays prefer the (faster) P224 group, and bridges prefer
17350 the (more common) P256 group; you can override this with the
17353 Enabling these ciphers was a little tricky, since for a long time,
17354 clients had been claiming to support them without actually doing
17355 so, in order to foil fingerprinting. But with the client-side
17356 implementation of proposal 198 in 0.2.3.17-beta, clients can now
17357 match the ciphers from recent Firefox versions *and* list the
17358 ciphers they actually mean, so relays can believe such clients
17359 when they advertise ECDHE support in their TLS ClientHello messages.
17361 This feature requires clients running 0.2.3.17-beta or later,
17362 and requires both sides to be running OpenSSL 1.0.0 or later
17363 with ECC support. OpenSSL 1.0.1, with the compile-time option
17364 "enable-ec_nistp_64_gcc_128", is highly recommended.
17366 Implements the relay side of proposal 198; closes ticket 7200.
17369 - Avoid crashing when, as a relay without IPv6-exit support, a
17370 client insists on getting an IPv6 address or nothing. Fixes bug
17371 7814; bugfix on 0.2.4.7-alpha.
17374 - Improve circuit build timeout handling for hidden services.
17375 In particular: adjust build timeouts more accurately depending
17376 upon the number of hop-RTTs that a particular circuit type
17377 undergoes. Additionally, launch intro circuits in parallel
17378 if they timeout, and take the first one to reply as valid.
17379 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
17380 separate error codes; or at least, don't break for that reason.
17381 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
17382 - Update to the January 2 2013 Maxmind GeoLite Country database.
17384 o Minor features (testing):
17385 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
17386 (P-256) Diffie-Hellman handshakes to src/or/bench.
17387 - Add benchmark functions to test onion handshake performance.
17389 o Minor features (path bias detection):
17390 - Alter the Path Bias log messages to be more descriptive in terms
17391 of reporting timeouts and other statistics.
17392 - Create three levels of Path Bias log messages, as opposed to just
17393 two. These are configurable via consensus as well as via the torrc
17394 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
17395 The default values are 0.70, 0.50, and 0.30 respectively.
17396 - Separate the log message levels from the decision to drop guards,
17397 which also is available via torrc option PathBiasDropGuards.
17398 PathBiasDropGuards still defaults to 0 (off).
17399 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
17400 in combination with PathBiasExtremeRate.
17401 - Increase the default values for PathBiasScaleThreshold and
17402 PathBiasCircThreshold from (200, 20) to (300, 150).
17403 - Add in circuit usage accounting to path bias. If we try to use a
17404 built circuit but fail for any reason, it counts as path bias.
17405 Certain classes of circuits where the adversary gets to pick your
17406 destination node are exempt from this accounting. Usage accounting
17407 can be specifically disabled via consensus parameter or torrc.
17408 - Convert all internal path bias state to double-precision floating
17409 point, to avoid roundoff error and other issues.
17410 - Only record path bias information for circuits that have completed
17411 *two* hops. Assuming end-to-end tagging is the attack vector, this
17412 makes us more resilient to ambient circuit failure without any
17413 detection capability loss.
17415 o Minor bugfixes (log messages):
17416 - Rate-limit the "No circuits are opened. Relaxed timeout for a
17417 circuit with channel state open..." message to once per hour to
17418 keep it from filling the notice logs. Mitigates bug 7799 but does
17419 not fix the underlying cause. Bugfix on 0.2.4.7-alpha.
17420 - Avoid spurious warnings when configuring multiple client ports of
17421 which only some are nonlocal. Previously, we had claimed that some
17422 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
17425 o Code simplifications and refactoring:
17426 - Get rid of a couple of harmless clang warnings, where we compared
17427 enums to ints. These warnings are newly introduced in clang 3.2.
17428 - Split the onion.c file into separate modules for the onion queue
17429 and the different handshakes it supports.
17430 - Remove the marshalling/unmarshalling code for sending requests to
17431 cpuworkers over a socket, and instead just send structs. The
17432 recipient will always be the same Tor binary as the sender, so
17433 any encoding is overkill.
17436 Changes in version 0.2.4.7-alpha - 2012-12-24
17437 Tor 0.2.4.7-alpha introduces a new approach to providing fallback
17438 directory mirrors for more robust bootstrapping; fixes more issues where
17439 clients with changing network conditions refuse to make any circuits;
17440 adds initial support for exiting to IPv6 addresses; resumes being able
17441 to update our GeoIP database, and includes the geoip6 file this time;
17442 turns off the client-side DNS cache by default due to privacy risks;
17443 and fixes a variety of other issues.
17445 o Major features (client resilience):
17446 - Add a new "FallbackDir" torrc option to use when we can't use
17447 a directory mirror from the consensus (either because we lack a
17448 consensus, or because they're all down). Currently, all authorities
17449 are fallbacks by default, and there are no other default fallbacks,
17450 but that will change. This option will allow us to give clients a
17451 longer list of servers to try to get a consensus from when first
17452 connecting to the Tor network, and thereby reduce load on the
17453 directory authorities. Implements proposal 206, "Preconfigured
17454 directory sources for bootstrapping". We also removed the old
17455 "FallbackNetworkstatus" option, since we never got it working well
17456 enough to use it. Closes bug 572.
17457 - If we have no circuits open, use a relaxed timeout (the
17458 95-percentile cutoff) until a circuit succeeds. This heuristic
17459 should allow Tor to succeed at building circuits even when the
17460 network connection drastically changes. Should help with bug 3443.
17462 o Major features (IPv6):
17463 - Relays can now exit to IPv6 addresses: make sure that you have IPv6
17464 connectivity, then set the IPv6Exit flag to 1. Also make sure your
17465 exit policy reads as you would like: the address * applies to all
17466 address families, whereas *4 is IPv4 address only, and *6 is IPv6
17467 addresses only. On the client side, you'll need to wait until the
17468 authorities have upgraded, wait for enough exits to support IPv6,
17469 apply the "IPv6Traffic" flag to a SocksPort, and use Socks5. Closes
17470 ticket 5547, implements proposal 117 as revised in proposal 208.
17472 We DO NOT recommend that clients with actual anonymity needs start
17473 using IPv6 over Tor yet, since not enough exits support it yet.
17475 o Major features (geoip database):
17476 - Maxmind began labelling Tor relays as being in country "A1",
17477 which breaks by-country node selection inside Tor. Now we use a
17478 script to replace "A1" ("Anonymous Proxy") entries in our geoip
17479 file with real country codes. This script fixes about 90% of "A1"
17480 entries automatically and uses manual country code assignments to
17481 fix the remaining 10%. See src/config/README.geoip for details.
17482 Fixes bug 6266. Also update to the December 5 2012 Maxmind GeoLite
17483 Country database, as modified above.
17485 o Major bugfixes (client-side DNS):
17486 - Turn off the client-side DNS cache by default. Updating and using
17487 the DNS cache is now configurable on a per-client-port
17488 level. SOCKSPort, DNSPort, etc lines may now contain
17489 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
17490 cache these types of DNS answers when we receive them from an
17491 exit node in response to an application request on this port, and
17492 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
17493 cached DNS answers of these types, we shouldn't use them. It's
17494 potentially risky to use cached DNS answers at the client, since
17495 doing so can indicate to one exit what answers we've gotten
17496 for DNS lookups in the past. With IPv6, this becomes especially
17497 problematic. Using cached DNS answers for requests on the same
17498 circuit would present less linkability risk, since all traffic
17499 on a circuit is already linkable, but it would also provide
17500 little performance benefit: the exit node caches DNS replies
17501 too. Implements a simplified version of Proposal 205. Implements
17504 o Major bugfixes (other):
17505 - Alter circuit build timeout measurement to start at the point
17506 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
17507 initialization). This should make our timeout measurements more
17508 uniform. Previously, we were sometimes including ORconn setup time
17509 in our circuit build time measurements. Should resolve bug 3443.
17510 - Fix an assertion that could trigger in hibernate_go_dormant() when
17511 closing an or_connection_t: call channel_mark_for_close() rather
17512 than connection_mark_for_close(). Fixes bug 7267. Bugfix on
17514 - Include the geoip6 IPv6 GeoIP database in the tarball. Fixes bug
17515 7655; bugfix on 0.2.4.6-alpha.
17518 - Add a new torrc option "ServerTransportListenAddr" to let bridge
17519 operators select the address where their pluggable transports will
17520 listen for connections. Resolves ticket 7013.
17521 - Allow an optional $ before the node identity digest in the
17522 controller command GETINFO ns/id/<identity>, for consistency with
17523 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
17524 - Log packaged cell fullness as part of the heartbeat message.
17525 Diagnosis to try to determine the extent of bug 7743.
17527 o Minor features (IPv6):
17528 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
17529 prefer to hand out virtual IPv6 addresses, since there are more of
17530 them and we can't run out. To override this behavior and make IPv4
17531 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
17532 or DNSPort you're using for resolving. Implements ticket 7571.
17533 - AutomapHostsOnResolve responses are now randomized, to avoid
17534 annoying situations where Tor is restarted and applications
17535 connect to the wrong addresses.
17536 - Never try more than 1000 times to pick a new virtual address when
17537 AutomapHostsOnResolve is set. That's good enough so long as we
17538 aren't close to handing out our entire virtual address space;
17539 if you're getting there, it's best to switch to IPv6 virtual
17543 - The ADDRMAP command can no longer generate an ill-formed error
17544 code on a failed MAPADDRESS. It now says "internal" rather than
17545 an English sentence fragment with spaces in the middle. Bugfix on
17546 Tor 0.2.0.19-alpha.
17547 - Fix log messages and comments to avoid saying "GMT" when we mean
17548 "UTC". Fixes bug 6113.
17549 - Compile on win64 using mingw64. Fixes bug 7260; patches from
17551 - Fix a crash when debugging unit tests on Windows: deallocate a
17552 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
17553 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
17556 - The DirServer option is now DirAuthority, for consistency with
17557 current naming patterns. You can still use the old DirServer form.
17559 o Code simplification and refactoring:
17560 - Move the client-side address-map/virtual-address/DNS-cache code
17561 out of connection_edge.c into a new addressmap.c module.
17562 - Remove unused code for parsing v1 directories and "running routers"
17563 documents. Fixes bug 6887.
17566 Changes in version 0.2.3.25 - 2012-11-19
17567 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
17568 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
17569 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
17570 programmer, and friend. Unstinting in his dedication to the cause of
17571 freedom, he inspired and helped many of us as we began our work on
17572 anonymity, and inspires us still. Please honor his memory by writing
17573 software to protect people's freedoms, and by helping others to do so.
17575 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
17576 significantly reduced directory overhead (via microdescriptors),
17577 enormous crypto performance improvements for fast relays on new
17578 enough hardware, a new v3 TLS handshake protocol that can better
17579 resist fingerprinting, support for protocol obfuscation plugins (aka
17580 pluggable transports), better scalability for hidden services, IPv6
17581 support for bridges, performance improvements like allowing clients
17582 to skip the first round-trip on the circuit ("optimistic data") and
17583 refilling token buckets more often, a new "stream isolation" design
17584 to isolate different applications on different circuits, and many
17585 stability, security, and privacy fixes.
17588 - Tor tries to wipe potentially sensitive data after using it, so
17589 that if some subsequent security failure exposes Tor's memory,
17590 the damage will be limited. But we had a bug where the compiler
17591 was eliminating these wipe operations when it decided that the
17592 memory was no longer visible to a (correctly running) program,
17593 hence defeating our attempt at defense in depth. We fix that
17594 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
17595 is unlikely to optimize away. Future versions of Tor may use
17596 a less ridiculously heavy approach for this. Fixes bug 7352.
17597 Reported in an article by Andrey Karpov.
17600 - Fix a harmless bug when opting against publishing a relay descriptor
17601 because DisableNetwork is set. Fixes bug 7464; bugfix on
17605 Changes in version 0.2.4.6-alpha - 2012-11-13
17606 Tor 0.2.4.6-alpha fixes an assert bug that has been plaguing relays,
17607 makes our defense-in-depth memory wiping more reliable, and begins to
17608 count IPv6 addresses in bridge statistics,
17611 - Fix an assertion failure that could occur when closing a connection
17612 with a spliced rendezvous circuit. Fix for bug 7212; bugfix on
17614 - Tor tries to wipe potentially sensitive data after using it, so
17615 that if some subsequent security failure exposes Tor's memory,
17616 the damage will be limited. But we had a bug where the compiler
17617 was eliminating these wipe operations when it decided that the
17618 memory was no longer visible to a (correctly running) program,
17619 hence defeating our attempt at defense in depth. We fix that
17620 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
17621 is unlikely to optimize away. Future versions of Tor may use
17622 a less ridiculously heavy approach for this. Fixes bug 7352.
17623 Reported in an article by Andrey Karpov.
17626 - Add GeoIP database for IPv6 addresses. The new config option
17628 - Bridge statistics now count bridge clients connecting over IPv6:
17629 bridge statistics files now list "bridge-ip-versions" and
17630 extra-info documents list "geoip6-db-digest". The control protocol
17631 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
17632 implementation by "shkoo", addressing ticket 5055.
17635 - Warn when we are binding low ports when hibernation is enabled;
17636 previously we had warned when we were _advertising_ low ports with
17637 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
17638 - Fix a harmless bug when opting against publishing a relay descriptor
17639 because DisableNetwork is set. Fixes bug 7464; bugfix on
17641 - Add warning message when a managed proxy dies during configuration.
17642 Fixes bug 7195; bugfix on 0.2.4.2-alpha.
17643 - Fix a linking error when building tor-fw-helper without miniupnp.
17644 Fixes bug 7235; bugfix on 0.2.4.2-alpha. Fix by Anthony G. Basile.
17645 - Check for closing an or_connection_t without going through correct
17646 channel functions; emit a warning and then call
17647 connection_or_close_for_error() so we don't assert as in bugs 7212
17649 - Compile correctly on compilers without C99 designated initializer
17650 support. Fixes bug 7286; bugfix on 0.2.4.4-alpha.
17651 - Avoid a possible assert that can occur when channel_send_destroy() is
17652 called on a channel in CHANNEL_STATE_CLOSING, CHANNEL_STATE_CLOSED,
17653 or CHANNEL_STATE_ERROR when the Tor process is resumed after being
17654 blocked for a long interval. Fixes bug 7350; bugfix on 0.2.4.4-alpha.
17655 - Fix a memory leak on failing cases of channel_tls_process_certs_cell.
17656 Fixes bug 7422; bugfix on 0.2.4.4-alpha.
17658 o Code simplification and refactoring:
17659 - Start using OpenBSD's implementation of queue.h, so that we don't
17660 need to hand-roll our own pointer and list structures whenever we
17661 need them. (We can't rely on a sys/queue.h, since some operating
17662 systems don't have them, and the ones that do have them don't all
17663 present the same extensions.)
17666 Changes in version 0.2.4.5-alpha - 2012-10-25
17667 Tor 0.2.4.5-alpha comes hard at the heels of 0.2.4.4-alpha, to fix
17668 two important security vulnerabilities that could lead to remotely
17669 triggerable relay crashes, fix a major bug that was preventing clients
17670 from choosing suitable exit nodes, and refactor some of our code.
17672 o Major bugfixes (security, also in 0.2.3.24-rc):
17673 - Fix a group of remotely triggerable assertion failures related to
17674 incorrect link protocol negotiation. Found, diagnosed, and fixed
17675 by "some guy from France". Fix for CVE-2012-2250; bugfix on
17677 - Fix a denial of service attack by which any directory authority
17678 could crash all the others, or by which a single v2 directory
17679 authority could crash everybody downloading v2 directory
17680 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
17682 o Major bugfixes (also in 0.2.3.24-rc):
17683 - When parsing exit policy summaries from microdescriptors, we had
17684 previously been ignoring the last character in each one, so that
17685 "accept 80,443,8080" would be treated by clients as indicating
17686 a node that allows access to ports 80, 443, and 808. That would
17687 lead to clients attempting connections that could never work,
17688 and ignoring exit nodes that would support their connections. Now
17689 clients parse these exit policy summaries correctly. Fixes bug 7192;
17690 bugfix on 0.2.3.1-alpha.
17692 o Minor bugfixes (also in 0.2.3.24-rc):
17693 - Clients now consider the ClientRejectInternalAddresses config option
17694 when using a microdescriptor consensus stanza to decide whether
17695 an exit relay would allow exiting to an internal address. Fixes
17696 bug 7190; bugfix on 0.2.3.1-alpha.
17699 - Only disable TLS session ticket support when running as a TLS
17700 server. Now clients will blend better with regular Firefox
17701 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
17703 o Code simplification and refactoring:
17704 - Start using OpenBSD's implementation of queue.h (originally by
17706 - Move the entry node code from circuitbuild.c to its own file.
17707 - Move the circuit build timeout tracking code from circuitbuild.c
17711 Changes in version 0.2.3.24-rc - 2012-10-25
17712 Tor 0.2.3.24-rc fixes two important security vulnerabilities that
17713 could lead to remotely triggerable relay crashes, and fixes
17714 a major bug that was preventing clients from choosing suitable exit
17717 o Major bugfixes (security):
17718 - Fix a group of remotely triggerable assertion failures related to
17719 incorrect link protocol negotiation. Found, diagnosed, and fixed
17720 by "some guy from France". Fix for CVE-2012-2250; bugfix on
17722 - Fix a denial of service attack by which any directory authority
17723 could crash all the others, or by which a single v2 directory
17724 authority could crash everybody downloading v2 directory
17725 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
17728 - When parsing exit policy summaries from microdescriptors, we had
17729 previously been ignoring the last character in each one, so that
17730 "accept 80,443,8080" would be treated by clients as indicating
17731 a node that allows access to ports 80, 443, and 808. That would
17732 lead to clients attempting connections that could never work,
17733 and ignoring exit nodes that would support their connections. Now
17734 clients parse these exit policy summaries correctly. Fixes bug 7192;
17735 bugfix on 0.2.3.1-alpha.
17738 - Clients now consider the ClientRejectInternalAddresses config option
17739 when using a microdescriptor consensus stanza to decide whether
17740 an exit relay would allow exiting to an internal address. Fixes
17741 bug 7190; bugfix on 0.2.3.1-alpha.
17744 Changes in version 0.2.4.4-alpha - 2012-10-20
17745 Tor 0.2.4.4-alpha adds a new v3 directory authority, fixes a privacy
17746 vulnerability introduced by a change in OpenSSL, fixes a remotely
17747 triggerable assert, and adds new channel_t and circuitmux_t abstractions
17748 that will make it easier to test new connection transport and cell
17749 scheduling algorithms.
17751 o New directory authorities (also in 0.2.3.23-rc):
17752 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
17753 authority. Closes ticket 5749.
17755 o Major bugfixes (security/privacy, also in 0.2.3.23-rc):
17756 - Disable TLS session tickets. OpenSSL's implementation was giving
17757 our TLS session keys the lifetime of our TLS context objects, when
17758 perfect forward secrecy would want us to discard anything that
17759 could decrypt a link connection as soon as the link connection
17760 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
17761 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
17762 - Discard extraneous renegotiation attempts once the V3 link
17763 protocol has been initiated. Failure to do so left us open to
17764 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
17765 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
17767 o Internal abstraction features:
17768 - Introduce new channel_t abstraction between circuits and
17769 or_connection_t to allow for implementing alternate OR-to-OR
17770 transports. A channel_t is an abstract object which can either be a
17771 cell-bearing channel, which is responsible for authenticating and
17772 handshaking with the remote OR and transmitting cells to and from
17773 it, or a listening channel, which spawns new cell-bearing channels
17774 at the request of remote ORs. Implements part of ticket 6465.
17775 - Also new is the channel_tls_t subclass of channel_t, adapting it
17776 to the existing or_connection_t code. The V2/V3 protocol handshaking
17777 code which formerly resided in command.c has been moved below the
17778 channel_t abstraction layer and may be found in channeltls.c now.
17779 Implements the rest of ticket 6465.
17780 - Introduce new circuitmux_t storing the queue of circuits for
17781 a channel; this encapsulates and abstracts the queue logic and
17782 circuit selection policy, and allows the latter to be overridden
17783 easily by switching out a policy object. The existing EWMA behavior
17784 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
17786 o Required libraries:
17787 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
17788 strongly recommended.
17791 - Warn users who run hidden services on a Tor client with
17792 UseEntryGuards disabled that their hidden services will be
17793 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
17794 attack which motivated Tor to support entry guards in the first
17795 place). Resolves ticket 6889.
17796 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
17797 dhill. Resolves ticket 6982.
17798 - Option OutboundBindAddress can be specified multiple times and
17799 accepts IPv6 addresses. Resolves ticket 6876.
17801 o Minor bugfixes (also in 0.2.3.23-rc):
17802 - Don't serve or accept v2 hidden service descriptors over a
17803 relay's DirPort. It's never correct to do so, and disabling it
17804 might make it more annoying to exploit any bugs that turn up in the
17805 descriptor-parsing code. Fixes bug 7149.
17806 - Fix two cases in src/or/transports.c where we were calling
17807 fmt_addr() twice in a parameter list. Bug found by David
17808 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
17809 - Fix memory leaks whenever we logged any message about the "path
17810 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
17811 - When relays refuse a "create" cell because their queue of pending
17812 create cells is too big (typically because their cpu can't keep up
17813 with the arrival rate), send back reason "resource limit" rather
17814 than reason "internal", so network measurement scripts can get a
17815 more accurate picture. Fixes bug 7037; bugfix on 0.1.1.11-alpha.
17818 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
17819 - Free some more still-in-use memory at exit, to make hunting for
17820 memory leaks easier. Resolves bug 7029.
17821 - When a Tor client gets a "truncated" relay cell, the first byte of
17822 its payload specifies why the circuit was truncated. We were
17823 ignoring this 'reason' byte when tearing down the circuit, resulting
17824 in the controller not being told why the circuit closed. Now we
17825 pass the reason from the truncated cell to the controller. Bugfix
17826 on 0.1.2.3-alpha; fixes bug 7039.
17827 - Downgrade "Failed to hand off onionskin" messages to "debug"
17828 severity, since they're typically redundant with the "Your computer
17829 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
17830 - Make clients running with IPv6 bridges connect over IPv6 again,
17831 even without setting new config options ClientUseIPv6 and
17832 ClientPreferIPv6ORPort. Fixes bug 6757; bugfix on 0.2.4.1-alpha.
17833 - Use square brackets around IPv6 addresses in numerous places
17834 that needed them, including log messages, HTTPS CONNECT proxy
17835 requests, TransportProxy statefile entries, and pluggable transport
17836 extra-info lines. Fixes bug 7011; patch by David Fifield.
17838 o Code refactoring and cleanup:
17839 - Source files taken from other packages now reside in src/ext;
17840 previously they were scattered around the rest of Tor.
17841 - Avoid use of reserved identifiers in our C code. The C standard
17842 doesn't like us declaring anything that starts with an
17843 underscore, so let's knock it off before we get in trouble. Fix
17844 for bug 1031; bugfix on the first Tor commit.
17847 Changes in version 0.2.3.23-rc - 2012-10-20
17848 Tor 0.2.3.23-rc adds a new v3 directory authority, fixes a privacy
17849 vulnerability introduced by a change in OpenSSL, and fixes a variety
17850 of smaller bugs in preparation for the release.
17852 o New directory authorities:
17853 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
17854 authority. Closes ticket 5749.
17856 o Major bugfixes (security/privacy):
17857 - Disable TLS session tickets. OpenSSL's implementation was giving
17858 our TLS session keys the lifetime of our TLS context objects, when
17859 perfect forward secrecy would want us to discard anything that
17860 could decrypt a link connection as soon as the link connection
17861 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
17862 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
17863 - Discard extraneous renegotiation attempts once the V3 link
17864 protocol has been initiated. Failure to do so left us open to
17865 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
17866 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
17869 - Fix a possible crash bug when checking for deactivated circuits
17870 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
17871 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
17873 o Minor bugfixes (on 0.2.3.x):
17874 - Fix two cases in src/or/transports.c where we were calling
17875 fmt_addr() twice in a parameter list. Bug found by David
17876 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
17877 - Convert an assert in the pathbias code to a log message. The assert
17878 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
17879 bugfix on 0.2.3.17-beta.
17880 - Fix memory leaks whenever we logged any message about the "path
17881 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
17883 o Minor bugfixes (on 0.2.2.x and earlier):
17884 - Don't serve or accept v2 hidden service descriptors over a relay's
17885 DirPort. It's never correct to do so, and disabling it might
17886 make it more annoying to exploit any bugs that turn up in the
17887 descriptor-parsing code. Fixes bug 7149.
17888 - When relays refuse a "create" cell because their queue of pending
17889 create cells is too big (typically because their cpu can't keep up
17890 with the arrival rate), send back reason "resource limit" rather
17891 than reason "internal", so network measurement scripts can get a
17892 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
17893 - Correct file sizes when reading binary files on Cygwin, to avoid
17894 a bug where Tor would fail to read its state file. Fixes bug 6844;
17895 bugfix on 0.1.2.7-alpha.
17896 - Avoid undefined behavior when parsing the list of supported
17897 rendezvous/introduction protocols in a hidden service descriptor.
17898 Previously, Tor would have confused (as-yet-unused) protocol version
17899 numbers greater than 32 with lower ones on many platforms. Fixes
17900 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
17902 o Documentation fixes:
17903 - Clarify that hidden services are TCP only. Fixes bug 6024.
17906 Changes in version 0.2.4.3-alpha - 2012-09-22
17907 Tor 0.2.4.3-alpha fixes another opportunity for a remotely triggerable
17908 assertion, resumes letting relays test reachability of their DirPort,
17909 and cleans up a bunch of smaller bugs.
17912 - Fix an assertion failure in tor_timegm() that could be triggered
17913 by a badly formatted directory object. Bug found by fuzzing with
17914 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
17917 - Fix a possible crash bug when checking for deactivated circuits
17918 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
17919 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
17920 - Allow routers to detect that their own DirPorts are running. When
17921 we removed support for versions_supports_begindir, we also
17922 accidentally removed the mechanism we used to self-test our
17923 DirPort. Diagnosed with help from kargig. Fixes bugs 6814 and 6815;
17924 bugfix on 0.2.4.2-alpha.
17926 o Security features:
17927 - Switch to a completely time-invariant approach for picking nodes
17928 weighted by bandwidth. Our old approach would run through the
17929 part of the loop after it had made its choice slightly slower
17930 than it ran through the part of the loop before it had made its
17931 choice. Addresses ticket 6538.
17932 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
17933 by tor2web clients allows hidden services to identify tor2web
17934 clients through their repeated selection of the same rendezvous
17935 and introduction point circuit endpoints (their guards). Resolves
17939 - Enable Tor to read configuration, state, and key information from
17940 a FIFO. Previously Tor would only read from files with a positive
17941 stat.st_size. Code from meejah; fixes bug 6044.
17944 - Correct file sizes when reading binary files on Cygwin, to avoid
17945 a bug where Tor would fail to read its state file. Fixes bug 6844;
17946 bugfix on 0.1.2.7-alpha.
17947 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
17948 bugfix on 0.2.0.3-alpha.
17949 - When complaining about a client port on a public address, log
17950 which address we're complaining about. Fixes bug 4020; bugfix on
17951 0.2.3.3-alpha. Patch by Tom Fitzhenry.
17952 - Convert an assert in the pathbias code to a log message. The assert
17953 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
17954 bugfix on 0.2.3.17-beta.
17955 - Our new buildsystem was overzealous about rebuilding manpages: it
17956 would rebuild them all whenever any one of them changed. Now our
17957 dependency checking should be correct. Fixes bug 6843; bugfix on
17959 - Don't do reachability testing over IPv6 unless AuthDirPublishIPv6
17960 is set. Fixes bug 6880. Bugfix on 0.2.4.1-alpha.
17961 - Correct log printout about which address family is preferred
17962 when connecting to a bridge with both an IPv4 and IPv6 OR port.
17963 Fixes bug 6884; bugfix on 0.2.4.1-alpha.
17965 o Minor bugfixes (code cleanliness):
17966 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
17967 with large values. This situation was untriggered, but nevertheless
17968 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
17969 - Reject consensus votes with more than 64 known-flags. We aren't even
17970 close to that limit yet, and our code doesn't handle it correctly.
17971 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
17972 - Avoid undefined behavior when parsing the list of supported
17973 rendezvous/introduction protocols in a hidden service descriptor.
17974 Previously, Tor would have confused (as-yet-unused) protocol version
17975 numbers greater than 32 with lower ones on many platforms. Fixes
17976 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
17977 - Fix handling of rendezvous client authorization types over 8.
17978 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
17979 - Fix building with older versions of GCC (2.95, for one) that don't
17980 like preprocessor directives inside macro arguments. Found by
17981 grarpamp. Fixes bug 6842; bugfix on 0.2.4.2-alpha.
17982 - Switch weighted node selection rule from using a list of doubles
17983 to using a list of int64_t. This change should make the process
17984 slightly easier to debug and maintain. Needed to finish ticket 6538.
17986 o Code simplification and refactoring:
17987 - Move the generic "config" code into a new file, and have "config.c"
17988 hold only torrc- and state-related code. Resolves ticket 6823.
17989 - Move the core of our "choose a weighted element at random" logic
17990 into its own function, and give it unit tests. Now the logic is
17991 testable, and a little less fragile too.
17992 - Removed the testing_since field of node_t, which hasn't been used
17993 for anything since 0.2.0.9-alpha.
17995 o Documentation fixes:
17996 - Clarify that hidden services are TCP only. Fixes bug 6024.
17997 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
18001 Changes in version 0.2.3.22-rc - 2012-09-11
18002 Tor 0.2.3.22-rc fixes another opportunity for a remotely triggerable
18006 - Fix an assertion failure in tor_timegm() that could be triggered
18007 by a badly formatted directory object. Bug found by fuzzing with
18008 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
18011 - Avoid segfault when starting up having run with an extremely old
18012 version of Tor and parsing its state file. Fixes bug 6801; bugfix
18016 Changes in version 0.2.2.39 - 2012-09-11
18017 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
18021 - Fix an assertion failure in tor_timegm() that could be triggered
18022 by a badly formatted directory object. Bug found by fuzzing with
18023 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
18024 - Do not crash when comparing an address with port value 0 to an
18025 address policy. This bug could have been used to cause a remote
18026 assertion failure by or against directory authorities, or to
18027 allow some applications to crash clients. Fixes bug 6690; bugfix
18031 Changes in version 0.2.4.2-alpha - 2012-09-10
18032 Tor 0.2.4.2-alpha enables port forwarding for pluggable transports,
18033 raises the default rate limiting even more, and makes the bootstrapping
18034 log messages less noisy.
18037 - Automatically forward the TCP ports of pluggable transport
18038 proxies using tor-fw-helper if PortForwarding is enabled. Implements
18042 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
18043 to 1GB/1GB. The previous defaults were intended to be "basically
18044 infinite", but it turns out they're now limiting our 100mbit+
18045 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
18046 last time we raised it).
18049 - Detect when we're running with a version of OpenSSL other than the
18050 one we compiled with. This has occasionally given people hard-to-
18052 - Log fewer lines at level "notice" about our OpenSSL and Libevent
18053 versions and capabilities when everything is going right. Resolves
18054 part of ticket 6736.
18055 - Directory authorities no long accept descriptors for any version of
18056 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
18057 These versions are insecure, unsupported, or both. Implements
18061 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
18062 to start with a triple-underscore so the controller won't touch it.
18063 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
18064 - Avoid segfault when starting up having run with an extremely old
18065 version of Tor and parsing its state file. Fixes bug 6801; bugfix
18067 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
18068 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
18069 - Don't follow the NULL pointer if microdescriptor generation fails.
18070 (This does not appear to be triggerable, but it's best to be safe.)
18071 Found by "f. tp.". Fixes bug 6797; bugfix on 0.2.4.1-alpha.
18072 - Fix mis-declared dependencies on src/common/crypto.c and
18073 src/or/tor_main.c that could break out-of-tree builds under some
18074 circumstances. Fixes bug 6778; bugfix on 0.2.4.1-alpha.
18075 - Avoid a warning when building common_sha1.i out of tree. Fixes bug
18076 6778; bugfix on 0.2.4.1-alpha.
18077 - Fix a harmless (in this case) build warning for implicitly
18078 converting a strlen() to an int. Bugfix on 0.2.4.1-alpha.
18080 o Removed features:
18081 - Now that all versions before 0.2.2.x are disallowed, we no longer
18082 need to work around their missing features. Thus we can remove a
18083 bunch of compatibility code.
18085 o Code refactoring:
18086 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
18087 TCP ports to forward. In the past it only accepted two ports:
18088 the ORPort and the DirPort.
18091 Changes in version 0.2.4.1-alpha - 2012-09-05
18092 Tor 0.2.4.1-alpha lets bridges publish their pluggable transports to
18093 bridgedb; lets relays use IPv6 addresses and directory authorities
18094 advertise them; and switches to a cleaner build interface.
18096 This is the first alpha release in a new series, so expect there to
18097 be bugs. Users who would rather test out a more stable branch should
18098 stay with 0.2.3.x for now.
18100 o Major features (bridges):
18101 - Bridges now report the pluggable transports they support to the
18102 bridge authority, so it can pass the supported transports on to
18103 bridgedb and/or eventually do reachability testing. Implements
18106 o Major features (IPv6):
18107 - Bridge authorities now accept IPv6 bridge addresses and include
18108 them in network status documents. Implements ticket 5534.
18109 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
18110 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
18111 to happen. Implements ticket 5535.
18112 - All kind of relays, not just bridges, can now advertise an IPv6
18113 OR port. Implements ticket 6362.
18114 - Directory authorities vote on IPv6 OR ports using the new consensus
18115 method 14. Implements ticket 6363.
18117 o Major features (build):
18118 - Switch to a nonrecursive Makefile structure. Now instead of each
18119 Makefile.am invoking other Makefile.am's, there is a master
18120 Makefile.am that includes the others. This change makes our build
18121 process slightly more maintainable, and improves parallelism for
18122 building with make -j. Original patch by Stewart Smith; various
18123 fixes by Jim Meyering.
18124 - Where available, we now use automake's "silent" make rules by
18125 default, so that warnings are easier to spot. You can get the old
18126 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
18128 o Minor features (code security and spec conformance):
18129 - Clear keys and key-derived material left on the stack in
18130 rendservice.c and rendclient.c. Check return value of
18131 crypto_pk_write_private_key_to_string() in rend_service_load_keys().
18132 These fixes should make us more forward-secure against cold-boot
18133 attacks and the like. Fixes bug 2385.
18134 - Reject EXTEND cells sent to nonexistent streams. According to the
18135 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
18136 we were only checking for stream IDs that were currently in use.
18137 Found while hunting for more instances of bug 6271. Bugfix on
18138 0.0.2pre8, which introduced incremental circuit construction.
18140 o Minor features (streamlining);
18141 - No longer include the "opt" prefix when generating routerinfos
18142 or v2 directories: it has been needless since Tor 0.1.2. Closes
18144 - Remove some now-needless code that tried to aggressively flush
18145 OR connections as data was added to them. Since 0.2.0.1-alpha, our
18146 cell queue logic has saved us from the failure mode that this code
18147 was supposed to prevent. Removing this code will limit the number
18148 of baroque control flow paths through Tor's network logic. Reported
18149 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
18151 o Minor features (controller):
18152 - Add a "GETINFO signal/names" control port command. Implements
18154 - Provide default values for all options via "GETINFO config/defaults".
18155 Implements ticket 4971.
18157 o Minor features (IPv6):
18158 - New config option "AuthDirHasIPv6Connectivity 1" that directory
18159 authorities should set if they have IPv6 connectivity and want to
18160 do reachability tests for IPv6 relays. Implements feature 5974.
18161 - A relay with an IPv6 OR port now sends that address in NETINFO
18162 cells (in addition to its other address). Implements ticket 6364.
18164 o Minor features (log messages):
18165 - Omit the first heartbeat log message, because it never has anything
18166 useful to say, and it clutters up the bootstrapping messages.
18167 Resolves ticket 6758.
18168 - Don't log about reloading the microdescriptor cache at startup. Our
18169 bootstrap warnings are supposed to tell the user when there's a
18170 problem, and our bootstrap notices say when there isn't. Resolves
18171 ticket 6759; bugfix on 0.2.2.6-alpha.
18172 - Don't log "I learned some more directory information" when we're
18173 reading cached directory information. Reserve it for when new
18174 directory information arrives in response to a fetch. Resolves
18176 - Prevent rounding error in path bias counts when scaling
18177 them down, and use the correct scale factor default. Also demote
18178 some path bias related log messages down a level and make others
18179 less scary sounding. Fixes bug 6647. Bugfix against 0.2.3.17-beta.
18180 - We no longer warn so much when generating manpages from their
18183 o Code simplifications and refactoring:
18184 - Enhance our internal sscanf replacement so that we can eliminate
18185 the last remaining uses of the system sscanf. (Though those uses
18186 of sscanf were safe, sscanf itself is generally error prone, so
18187 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
18189 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
18190 - Move last_reachable and testing_since from routerinfo_t to node_t.
18191 Implements ticket 5529.
18192 - Add replaycache_t structure, functions and unit tests, then refactor
18193 rend_service_introduce() to be more clear to read, improve, debug,
18194 and test. Resolves bug 6177.
18195 - Finally remove support for malloc_good_size and malloc_usable_size.
18196 We had hoped that these functions would let us eke a little more
18197 memory out of our malloc implementation. Unfortunately, the only
18198 implementations that provided these functions are also ones that
18199 are already efficient about not overallocation: they never got us
18200 more than 7 or so bytes per allocation. Removing them saves us a
18201 little code complexity and a nontrivial amount of build complexity.
18203 o New requirements:
18204 - Tor maintainers now require Automake version 1.9 or later to build
18205 Tor from the Git repository. (Automake is not required when building
18206 from a source distribution.)
18209 Changes in version 0.2.3.21-rc - 2012-09-05
18210 Tor 0.2.3.21-rc is the fourth release candidate for the Tor 0.2.3.x
18211 series. It fixes a trio of potential security bugs, fixes a bug where
18212 we were leaving some of the fast relays out of the microdescriptor
18213 consensus, resumes interpreting "ORPort 0" and "DirPort 0" correctly,
18214 and cleans up other smaller issues.
18216 o Major bugfixes (security):
18217 - Tear down the circuit if we get an unexpected SENDME cell. Clients
18218 could use this trick to make their circuits receive cells faster
18219 than our flow control would have allowed, or to gum up the network,
18220 or possibly to do targeted memory denial-of-service attacks on
18221 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
18222 from July 2002, before the release of Tor 0.0.0. We had committed
18223 this patch previously, but we had to revert it because of bug 6271.
18224 Now that 6271 is fixed, this patch appears to work.
18225 - Reject any attempt to extend to an internal address. Without
18226 this fix, a router could be used to probe addresses on an internal
18227 network to see whether they were accepting connections. Fixes bug
18228 6710; bugfix on 0.0.8pre1.
18229 - Do not crash when comparing an address with port value 0 to an
18230 address policy. This bug could have been used to cause a remote
18231 assertion failure by or against directory authorities, or to
18232 allow some applications to crash clients. Fixes bug 6690; bugfix
18236 - Remove the upper bound on microdescriptor length. We were hitting
18237 the limit for routers with complex exit policies or family
18238 declarations, causing clients to not use them. Fixes the first
18239 piece of bug 6404; fix on 0.2.2.6-alpha.
18240 - Detect "ORPort 0" as meaning, uniformly, that we're not running
18241 as a relay. Previously, some of our code would treat the presence
18242 of any ORPort line as meaning that we should act like a relay,
18243 even though our new listener code would correctly not open any
18244 ORPorts for ORPort 0. Similar bugs in other Port options are also
18245 fixed. Fixes the first half of bug 6507; bugfix on 0.2.3.3-alpha.
18248 - Avoid a pair of double-free and use-after-mark bugs that can
18249 occur with certain timings in canceled and re-received DNS
18250 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
18251 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
18252 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
18253 - Allow one-hop directory fetching circuits the full "circuit build
18254 timeout" period, rather than just half of it, before failing them
18255 and marking the relay down. This fix should help reduce cases where
18256 clients declare relays (or worse, bridges) unreachable because
18257 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
18258 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
18260 - Authorities no longer include any router in their microdescriptor
18261 consensuses for which they couldn't generate or agree on a
18262 microdescriptor. Fixes the second piece of bug 6404; fix on
18264 - Detect and reject attempts to specify both "FooPort" and
18265 "FooPort 0" in the same configuration domain. (It's still okay
18266 to have a FooPort in your configuration file, and use "FooPort 0"
18267 on the command line to disable it.) Fixes the second half of bug
18268 6507; bugfix on 0.2.3.3-alpha.
18269 - Make wildcarded addresses (that is, ones beginning with "*.") work
18270 when provided via the controller's MapAddress command. Previously,
18271 they were accepted, but we never actually noticed that they were
18272 wildcards. Fixes bug 6244; bugfix on 0.2.3.9-alpha.
18273 - Avoid crashing on a malformed state file where EntryGuardPathBias
18274 precedes EntryGuard. Fix for bug 6774; bugfix on 0.2.3.17-beta.
18275 - Add a (probably redundant) memory clear between iterations of
18276 the router status voting loop, to prevent future coding errors
18277 where data might leak between iterations of the loop. Resolves
18280 o Minor bugfixes (log messages):
18281 - Downgrade "set buildtimeout to low value" messages to "info"
18282 severity; they were never an actual problem, there was never
18283 anything reasonable to do about them, and they tended to spam logs
18284 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
18285 - Downgrade path-bias warning messages to "info". We'll try to get
18286 them working better in 0.2.4. Add internal circuit construction
18287 state to protect against the noisy warn message "Unexpectedly high
18288 circuit_successes". Also add some additional rate-limited notice
18289 messages to help determine the root cause of the warn. Fixes bug
18290 6475. Bugfix against 0.2.3.17-beta.
18291 - Move log message when unable to find a microdesc in a routerstatus
18292 entry to parse time. Previously we'd spam this warning every time
18293 we tried to figure out which microdescriptors to download. Fixes
18294 the third piece of bug 6404; fix on 0.2.3.18-rc.
18297 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
18298 change when the authority is deciding whether to accept a newly
18299 uploaded descriptor. Implements ticket 6423.
18300 - Add missing documentation for consensus and microdesc files.
18301 Resolves ticket 6732.
18304 Changes in version 0.2.2.38 - 2012-08-12
18305 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
18306 attack that could in theory leak path information.
18309 - Avoid an uninitialized memory read when reading a vote or consensus
18310 document that has an unrecognized flavor name. This read could
18311 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
18312 - Try to leak less information about what relays a client is
18313 choosing to a side-channel attacker. Previously, a Tor client would
18314 stop iterating through the list of available relays as soon as it
18315 had chosen one, thus finishing a little earlier when it picked
18316 a router earlier in the list. If an attacker can recover this
18317 timing information (nontrivial but not proven to be impossible),
18318 they could learn some coarse-grained information about which relays
18319 a client was picking (middle nodes in particular are likelier to
18320 be affected than exits). The timing attack might be mitigated by
18321 other factors (see bug 6537 for some discussion), but it's best
18322 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
18325 Changes in version 0.2.3.20-rc - 2012-08-05
18326 Tor 0.2.3.20-rc is the third release candidate for the Tor 0.2.3.x
18327 series. It fixes a pair of code security bugs and a potential anonymity
18328 issue, updates our RPM spec files, and cleans up other smaller issues.
18331 - Avoid read-from-freed-memory and double-free bugs that could occur
18332 when a DNS request fails while launching it. Fixes bug 6480;
18333 bugfix on 0.2.0.1-alpha.
18334 - Avoid an uninitialized memory read when reading a vote or consensus
18335 document that has an unrecognized flavor name. This read could
18336 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
18337 - Try to leak less information about what relays a client is
18338 choosing to a side-channel attacker. Previously, a Tor client would
18339 stop iterating through the list of available relays as soon as it
18340 had chosen one, thus finishing a little earlier when it picked
18341 a router earlier in the list. If an attacker can recover this
18342 timing information (nontrivial but not proven to be impossible),
18343 they could learn some coarse-grained information about which relays
18344 a client was picking (middle nodes in particular are likelier to
18345 be affected than exits). The timing attack might be mitigated by
18346 other factors (see bug 6537 for some discussion), but it's best
18347 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
18350 - Try to make the warning when giving an obsolete SOCKSListenAddress
18351 a little more useful.
18352 - Terminate active server managed proxies if Tor stops being a
18353 relay. Addresses parts of bug 6274; bugfix on 0.2.3.6-alpha.
18354 - Provide a better error message about possible OSX Asciidoc failure
18355 reasons. Fixes bug 6436.
18356 - Warn when Tor is configured to use accounting in a way that can
18357 link a hidden service to some other hidden service or public
18358 address. Resolves ticket 6490.
18361 - Check return value of fputs() when writing authority certificate
18362 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
18363 - Ignore ServerTransportPlugin lines when Tor is not configured as
18364 a relay. Fixes bug 6274; bugfix on 0.2.3.6-alpha.
18365 - When disabling guards for having too high a proportion of failed
18366 circuits, make sure to look at each guard. Fixes bug 6397; bugfix
18370 - Update our default RPM spec files to work with mock and rpmbuild
18371 on RHEL/Fedora. They have an updated set of dependencies and
18372 conflicts, a fix for an ancient typo when creating the "_tor"
18373 user, and better instructions. Thanks to Ondrej Mikle for the
18374 patch series. Fixes bug 6043.
18377 - Make it possible to set the TestingTorNetwork configuration
18378 option using AlternateDirAuthority and AlternateBridgeAuthority
18379 as an alternative to setting DirServer. Addresses ticket 6377.
18382 - Clarify the documentation for the Alternate*Authority options.
18384 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
18386 o Code simplification and refactoring:
18387 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
18388 10 lines. Also, don't nest them. Doing so in the past has
18389 led to hard-to-debug code. The new style is to use the
18390 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
18393 Changes in version 0.2.3.19-rc - 2012-07-06
18394 Tor 0.2.3.19-rc is the second release candidate for the Tor 0.2.3.x
18395 series. It fixes the compile on Windows, reverts to a GeoIP database
18396 that isn't as broken, and fixes a flow control bug that has been around
18397 since the beginning of Tor.
18400 - Fix a bug handling SENDME cells on nonexistent streams that could
18401 result in bizarre window values. Report and patch contributed
18402 pseudonymously. Fixes part of bug 6271. This bug was introduced
18403 before the first Tor release, in svn commit r152.
18404 - Revert to the May 1 2012 Maxmind GeoLite Country database. In the
18405 June 2012 database, Maxmind marked many Tor relays as country "A1",
18406 which will cause risky behavior for clients that set EntryNodes
18407 or ExitNodes. Addresses bug 6334; bugfix on 0.2.3.17-beta.
18408 - Instead of ENOBUFS on Windows, say WSAENOBUFS. Fixes compilation
18409 on Windows. Fixes bug 6296; bugfix on 0.2.3.18-rc.
18412 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
18413 bugfix on 0.2.1.10-alpha.
18416 Changes in version 0.2.3.18-rc - 2012-06-28
18417 Tor 0.2.3.18-rc is the first release candidate for the Tor 0.2.3.x
18418 series. It fixes a few smaller bugs, but generally appears stable.
18419 Please test it and let us know whether it is!
18422 - Allow wildcarded mapaddress targets to be specified on the
18423 controlport. Partially fixes bug 6244; bugfix on 0.2.3.9-alpha.
18424 - Make our linker option detection code more robust against linkers
18425 such as on FreeBSD 8, where a bad combination of options completes
18426 successfully but makes an unrunnable binary. Fixes bug 6173;
18427 bugfix on 0.2.3.17-beta.
18429 o Minor bugfixes (on 0.2.2.x and earlier):
18430 - Avoid a false positive in the util/threads unit test by increasing
18431 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
18432 - Replace "Sending publish request" log messages with "Launching
18433 upload", so that they no longer confusingly imply that we're
18434 sending something to a directory we might not even be connected
18435 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
18436 - Make sure to set *socket_error in all error cases in
18437 connection_connect(), so it can't produce a warning about
18438 errno being zero from errno_to_orconn_end_reason(). Bugfix on
18439 0.2.1.1-alpha; resolves ticket 6028.
18440 - Downgrade "Got a certificate, but we already have it" log messages
18441 from warning to info, except when we're a dirauth. Fixes bug 5238;
18442 bugfix on 0.2.1.7-alpha.
18443 - When checking for requested signatures on the latest consensus
18444 before serving it to a client, make sure to check the right
18445 consensus flavor. Bugfix on 0.2.2.6-alpha.
18446 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
18447 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
18449 o Minor bugfixes (on 0.2.3.x):
18450 - Make format_helper_exit_status() avoid unnecessary space padding
18451 and stop confusing log_from_pipe(). Fixes ticket 5557; bugfix
18453 - Downgrade a message about cleaning the microdescriptor cache to
18454 "info" from "notice". Fixes bug 6238; bugfix on 0.2.3.1-alpha.
18455 - Log a BUG message at severity INFO if we have a networkstatus with
18456 a missing entry for some microdescriptor. Continues on a patch
18458 - Improve the log message when a managed proxy fails to launch. Fixes
18459 bug 5099; bugfix on 0.2.3.6-alpha.
18460 - Don't do DNS lookups when parsing corrupted managed proxy protocol
18461 messages. Fixes bug 6226; bugfix on 0.2.3.6-alpha.
18462 - When formatting wildcarded address mappings for the controller,
18463 be sure to include "*." as appropriate. Partially fixes bug 6244;
18464 bugfix on 0.2.3.9-alpha.
18465 - Avoid a warning caused by using strcspn() from glibc with clang 3.0.
18466 Bugfix on 0.2.3.13-alpha.
18467 - Stop logging messages about running with circuit timeout learning
18468 enabled at severity LD_BUG. Fixes bug 6169; bugfix on 0.2.3.17-beta.
18469 - Disable a spurious warning about reading on a marked and flushing
18470 connection. We shouldn't be doing that, but apparently we
18471 sometimes do. Fixes bug 6203; bugfix on 0.2.3.17-beta.
18472 - Fix a bug that stopped AllowDotExit from working on addresses
18473 that had an entry in the DNS cache. Fixes bug 6211; bugfix on
18476 o Code simplification, refactoring, unit tests:
18477 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
18478 Libevent's notion of cached time when possible.
18479 - Remove duplicate code for invoking getrlimit() from control.c.
18480 - Add a unit test for the environment_variable_names_equal function.
18483 - Document the --defaults-torrc option, and the new (in 0.2.3)
18484 semantics for overriding, extending, and clearing lists of
18485 options. Closes bug 4748.
18488 Changes in version 0.2.3.17-beta - 2012-06-15
18489 Tor 0.2.3.17-beta enables compiler and linker hardening by default,
18490 gets our TLS handshake back on track for being able to blend in with
18491 Firefox, fixes a big bug in 0.2.3.16-alpha that broke Tor's interaction
18492 with Vidalia, and otherwise continues to get us closer to a release
18496 - Enable gcc and ld hardening by default. Resolves ticket 5210.
18497 - Update TLS cipher list to match Firefox 8 and later. Resolves
18499 - Implement the client side of proposal 198: remove support for
18500 clients falsely claiming to support standard ciphersuites that
18501 they can actually provide. As of modern OpenSSL versions, it's not
18502 necessary to fake any standard ciphersuite, and doing so prevents
18503 us from using better ciphersuites in the future, since servers
18504 can't know whether an advertised ciphersuite is really supported or
18505 not. Some hosts -- notably, ones with very old versions of OpenSSL
18506 or where OpenSSL has been built with ECC disabled -- will stand
18507 out because of this change; TBB users should not be affected.
18510 - Change the default value for DynamicDHGroups (introduced in
18511 0.2.3.9-alpha) to 0. This feature can make Tor relays less
18512 identifiable by their use of the mod_ssl DH group, but at
18513 the cost of some usability (#4721) and bridge tracing (#6087)
18514 regressions. Resolves ticket 5598.
18515 - Send a CRLF at the end of each STATUS_* control protocol event. This
18516 bug tickled a bug in Vidalia which would make it freeze. Fixes
18517 bug 6094; bugfix on 0.2.3.16-alpha.
18520 - Disable writing on marked-for-close connections when they are
18521 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
18522 bug 5263; bugfix on 0.0.2pre13, where we first added a special
18523 case for flushing marked connections.
18524 - Detect SSL handshake even when the initial attempt to write the
18525 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
18526 - Change the AllowDotExit rules so they should actually work.
18527 We now enforce AllowDotExit only immediately after receiving an
18528 address via SOCKS or DNSPort: other sources are free to provide
18529 .exit addresses after the resolution occurs. Fixes bug 3940;
18530 bugfix on 0.2.2.1-alpha.
18531 - Fix a (harmless) integer overflow in cell statistics reported by
18532 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
18533 - Make sure circuitbuild.c checks LearnCircuitBuildTimeout in all the
18534 right places and never depends on the consensus parameters or
18535 computes adaptive timeouts when it is disabled. Fixes bug 5049;
18536 bugfix on 0.2.2.14-alpha.
18537 - When building Tor on Windows with -DUNICODE (not default), ensure
18538 that error messages, filenames, and DNS server names are always
18539 NUL-terminated when we convert them to a single-byte encoding.
18540 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
18541 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
18542 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
18543 - Fix an edge case where TestingTorNetwork is set but the authorities
18544 and relays all have an uptime of zero, where the private Tor network
18545 could briefly lack support for hidden services. Fixes bug 3886;
18546 bugfix on 0.2.2.18-alpha.
18547 - Correct the manpage's descriptions for the default values of
18548 DirReqStatistics and ExtraInfoStatistics. Fixes bug 2865; bugfix
18550 - Fix the documentation for the --hush and --quiet command line
18551 options, which changed their behavior back in 0.2.3.3-alpha.
18552 - Fix compilation warning with clang 3.1. Fixes bug 6141; bugfix on
18556 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
18557 more information to it, so that we can track it down in case it
18558 returns again. Mitigates bug 5235.
18559 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
18560 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
18561 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
18562 - Warn the user when HTTPProxy, but no other proxy type, is
18563 configured. This can cause surprising behavior: it doesn't send
18564 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
18565 directory traffic only. Resolves ticket 4663.
18566 - Issue a notice if a guard completes less than 40% of your circuits.
18567 Threshold is configurable by torrc option PathBiasNoticeRate and
18568 consensus parameter pb_noticepct. There is additional, off-by-
18569 default code to disable guards which fail too many circuits.
18570 Addresses ticket 5458.
18571 - Update to the June 6 2012 Maxmind GeoLite Country database.
18573 o Code simplifications and refactoring:
18574 - Remove validate_pluggable_transports_config(): its warning
18575 message is now handled by connection_or_connect().
18578 Changes in version 0.2.2.37 - 2012-06-06
18579 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
18580 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
18584 - Work around a bug in OpenSSL that broke renegotiation with TLS
18585 1.1 and TLS 1.2. Without this workaround, all attempts to speak
18586 the v2 Tor connection protocol when both sides were using OpenSSL
18587 1.0.1 would fail. Resolves ticket 6033.
18588 - When waiting for a client to renegotiate, don't allow it to add
18589 any bytes to the input buffer. This fixes a potential DoS issue.
18590 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
18591 - Fix an edge case where if we fetch or publish a hidden service
18592 descriptor, we might build a 4-hop circuit and then use that circuit
18593 for exiting afterwards -- even if the new last hop doesn't obey our
18594 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
18597 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
18598 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
18601 - Tell GCC and Clang to check for any errors in format strings passed
18602 to the tor_v*(print|scan)f functions.
18605 Changes in version 0.2.3.16-alpha - 2012-06-05
18606 Tor 0.2.3.16-alpha introduces a workaround for a critical renegotiation
18607 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
18608 currently). It also fixes a variety of smaller bugs and other cleanups
18609 that get us closer to a release candidate.
18611 o Major bugfixes (general):
18612 - Work around a bug in OpenSSL that broke renegotiation with TLS
18613 1.1 and TLS 1.2. Without this workaround, all attempts to speak
18614 the v2 Tor connection protocol when both sides were using OpenSSL
18615 1.0.1 would fail. Resolves ticket 6033.
18616 - When waiting for a client to renegotiate, don't allow it to add
18617 any bytes to the input buffer. This fixes a potential DoS issue.
18618 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
18619 - Pass correct OR address to managed proxies (like obfsproxy),
18620 even when ORListenAddress is used. Fixes bug 4865; bugfix on
18622 - The advertised platform of a router now includes only its operating
18623 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not its
18624 service pack level (for Windows) or its CPU architecture (for Unix).
18625 We also no longer include the "git-XYZ" tag in the version. Resolves
18628 o Major bugfixes (clients):
18629 - If we are unable to find any exit that supports our predicted ports,
18630 stop calling them predicted, so that we don't loop and build
18631 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
18632 which introduced predicted ports.
18633 - Fix an edge case where if we fetch or publish a hidden service
18634 descriptor, we might build a 4-hop circuit and then use that circuit
18635 for exiting afterwards -- even if the new last hop doesn't obey our
18636 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
18637 - Check at each new consensus whether our entry guards were picked
18638 long enough ago that we should rotate them. Previously, we only
18639 did this check at startup, which could lead to us holding a guard
18640 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
18641 - When fetching a bridge descriptor from a bridge authority,
18642 always do so anonymously, whether we have been able to open
18643 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
18644 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
18645 but we'll need to wait for bug 6010 before it's actually usable.
18647 o Major bugfixes (directory authorities):
18648 - When computing weight parameters, behave more robustly in the
18649 presence of a bad bwweightscale value. Previously, the authorities
18650 would crash if they agreed on a sufficiently broken weight_scale
18651 value: now, they use a reasonable default and carry on. Partial
18652 fix for 5786; bugfix on 0.2.2.17-alpha.
18653 - Check more thoroughly to prevent a rogue authority from
18654 double-voting on any consensus directory parameter. Previously,
18655 authorities would crash in this case if the total number of
18656 votes for any parameter exceeded the number of active voters,
18657 but would let it pass otherwise. Partial fix for bug 5786; bugfix
18661 - Rate-limit log messages when asked to connect anonymously to
18662 a private address. When these hit, they tended to hit fast and
18663 often. Also, don't bother trying to connect to addresses that we
18664 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
18665 reply makes us think we have been lied to, even when the address the
18666 client tried to connect to was "localhost." Resolves ticket 2822.
18667 - Allow packagers to insert an extra string in server descriptor
18668 platform lines by setting the preprocessor variable TOR_BUILD_TAG.
18669 Resolves the rest of ticket 2988.
18670 - Raise the threshold of server descriptors needed (75%) and exit
18671 server descriptors needed (50%) before we will declare ourselves
18672 bootstrapped. This will make clients start building circuits a
18673 little later, but makes the initially constructed circuits less
18674 skewed and less in conflict with further directory fetches. Fixes
18676 - Close any connection that sends unrecognized junk before the
18677 handshake. Solves an issue noted in bug 4369.
18678 - Improve log messages about managed transports. Resolves ticket 5070.
18679 - Tag a bridge's descriptor as "never to be sent unencrypted".
18680 This shouldn't matter, since bridges don't open non-anonymous
18681 connections to the bridge authority and don't allow unencrypted
18682 directory connections from clients, but we might as well make
18683 sure. Closes bug 5139.
18684 - Expose our view of whether we have gone dormant to the controller,
18685 via a new "GETINFO dormant" value. Torbutton and other controllers
18686 can use this to avoid doing periodic requests through Tor while
18687 it's dormant (bug 4718). Fixes bug 5954.
18688 - Tell GCC and Clang to check for any errors in format strings passed
18689 to the tor_v*(print|scan)f functions.
18690 - Update to the May 1 2012 Maxmind GeoLite Country database.
18692 o Minor bugfixes (already included in 0.2.2.36):
18693 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
18694 Fixes bug 5346; bugfix on 0.0.8pre3.
18695 - Correct parsing of certain date types in parse_http_time().
18696 Without this patch, If-Modified-Since would behave
18697 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
18698 Esteban Manchado Velázques.
18699 - Make our number-parsing functions always treat too-large values
18700 as an error, even when those values exceed the width of the
18701 underlying type. Previously, if the caller provided these
18702 functions with minima or maxima set to the extreme values of the
18703 underlying integer type, these functions would return those
18704 values on overflow rather than treating overflow as an error.
18705 Fixes part of bug 5786; bugfix on 0.0.9.
18706 - If we hit the error case where routerlist_insert() replaces an
18707 existing (old) server descriptor, make sure to remove that
18708 server descriptor from the old_routers list. Fix related to bug
18709 1776. Bugfix on 0.2.2.18-alpha.
18710 - Clarify the behavior of MaxCircuitDirtiness with hidden service
18711 circuits. Fixes issue 5259.
18713 o Minor bugfixes (coding cleanup, on 0.2.2.x and earlier):
18714 - Prevent a null-pointer dereference when receiving a data cell
18715 for a nonexistent stream when the circuit in question has an
18716 empty deliver window. We don't believe this is triggerable,
18717 since we don't currently allow deliver windows to become empty,
18718 but the logic is tricky enough that it's better to make the code
18719 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
18720 - Fix a memory leak when trying to launch a DNS request when the
18721 network is disabled or the nameservers are unconfigurable. Fixes
18722 bug 5916; bugfix on Tor 0.1.2.1-alpha (for the unconfigurable
18723 nameserver case) and on 0.2.3.9-alpha (for the DisableNetwork case).
18724 - Don't hold a Windows file handle open for every file mapping;
18725 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
18727 - Avoid O(n^2) performance characteristics when parsing a large
18728 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
18729 - Format more doubles with %f, not %lf. Patch from grarpamp to make
18730 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
18732 - Make our replacement implementation of strtok_r() compatible with
18733 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
18734 bugfix on 0.2.2.1-alpha.
18735 - Fix a NULL-pointer dereference on a badly formed
18736 SETCIRCUITPURPOSE command. Found by mikeyc. Fixes bug 5796;
18737 bugfix on 0.2.2.9-alpha.
18738 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
18739 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
18740 - Defensively refactor rend_mid_rendezvous() so that protocol
18741 violations and length checks happen in the beginning. Fixes
18743 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
18744 that IPv6 stuff will compile on MSVC, and compilation issues
18745 will be easier to track down. Fixes bug 5861.
18747 o Minor bugfixes (correctness, on 0.2.2.x and earlier):
18748 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
18749 resource exhaustion, so that clients can adjust their load to
18750 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
18751 started using END_STREAM_REASON_RESOURCELIMIT.
18752 - Don't check for whether the address we're using for outbound
18753 connections has changed until after the outbound connection has
18754 completed. On Windows, getsockname() doesn't succeed until the
18755 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
18756 - If the configuration tries to set MyFamily on a bridge, refuse to
18757 do so, and warn about the security implications. Fixes bug 4657;
18758 bugfix on 0.2.0.3-alpha.
18759 - If the client fails to set a reasonable set of ciphersuites
18760 during its v2 handshake renegotiation, allow the renegotiation to
18761 continue nevertheless (i.e. send all the required certificates).
18762 Fixes bug 4591; bugfix on 0.2.0.20-rc.
18763 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
18764 option is set to 0 (which Vidalia version 0.2.16 now does when
18765 a SAVECONF attempt fails), perform other actions that SIGHUP
18766 usually causes (like reopening the logs). Fixes bug 5095; bugfix
18768 - If we fail to write a microdescriptor to the disk cache, do not
18769 continue replacing the old microdescriptor file. Fixes bug 2954;
18770 bugfix on 0.2.2.6-alpha.
18771 - Exit nodes don't need to fetch certificates for authorities that
18772 they don't recognize; only directory authorities, bridges,
18773 and caches need to do that. Fixes part of bug 2297; bugfix on
18775 - Correctly handle checking the permissions on the parent
18776 directory of a control socket in the root directory. Bug found
18777 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
18779 - When told to add a bridge with the same digest as a preexisting
18780 bridge but a different addr:port, change the addr:port as
18781 requested. Previously we would not notice the change. Fixes half
18782 of bug 5603; fix on 0.2.2.26-beta.
18783 - End AUTHCHALLENGE error messages (in the control protocol) with
18784 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36 and 0.2.3.13-alpha.
18786 o Minor bugfixes (on 0.2.3.x):
18787 - Turn an assertion (that the number of handshakes received as a
18788 server is not < 1) into a warning. Fixes bug 4873; bugfix on
18790 - Format IPv4 addresses correctly in ADDRMAP events. (Previously,
18791 we had reversed them when the answer was cached.) Fixes bug
18792 5723; bugfix on 0.2.3.1-alpha.
18793 - Work correctly on Linux systems with accept4 support advertised in
18794 their headers, but without accept4 support in the kernel. Fix
18795 by murb. Fixes bug 5762; bugfix on 0.2.3.1-alpha.
18796 - When told to add a bridge with the same addr:port as a preexisting
18797 bridge but a different transport, change the transport as
18798 requested. Previously we would not notice the change. Fixes half
18799 of bug 5603; fix on 0.2.3.2-alpha.
18800 - Avoid a "double-reply" warning when replying to a SOCKS request
18801 with a parse error. Patch from Fabian Keil. Fixes bug 4108;
18802 bugfix on 0.2.3.4-alpha.
18803 - Fix a bug where a bridge authority crashes if it has seen no
18804 directory requests when it's time to write statistics to disk.
18805 Fixes bug 5891; bugfix on 0.2.3.6-alpha. Also fixes bug 5508 in
18807 - Don't try to open non-control listeners when DisableNetwork is set.
18808 Previously, we'd open all listeners, then immediately close them.
18809 Fixes bug 5604; bugfix on 0.2.3.9-alpha.
18810 - Don't abort the managed proxy protocol if the managed proxy
18811 sends us an unrecognized line; ignore it instead. Fixes bug
18812 5910; bugfix on 0.2.3.9-alpha.
18813 - Fix a compile warning in crypto.c when compiling with clang 3.1.
18814 Fixes bug 5969, bugfix on 0.2.3.9-alpha.
18815 - Fix a compilation issue on GNU Hurd, which doesn't have PATH_MAX.
18816 Fixes bug 5355; bugfix on 0.2.3.11-alpha.
18817 - Remove bogus definition of "_WIN32" from src/win32/orconfig.h, to
18818 unbreak the MSVC build. Fixes bug 5858; bugfix on 0.2.3.12-alpha.
18819 - Resolve numerous small warnings and build issues with MSVC. Resolves
18822 o Documentation fixes:
18823 - Improve the manual's documentation for the NT Service command-line
18824 options. Addresses ticket 3964.
18825 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
18826 - Document the changes to the ORPort and DirPort options, and the
18827 fact that {OR/Dir}ListenAddress is now unnecessary (and
18828 therefore deprecated). Resolves ticket 5597.
18831 - Remove the torrc.bridge file: we don't use it for anything, and
18832 it had become badly desynchronized from torrc.sample. Resolves
18836 Changes in version 0.2.2.36 - 2012-05-24
18837 Tor 0.2.2.36 updates the addresses for two of the eight directory
18838 authorities, fixes some potential anonymity and security issues,
18839 and fixes several crash bugs.
18841 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
18842 known flaws, and nobody should be using them. You should upgrade. If
18843 you're using a Linux or BSD and its packages are obsolete, stop using
18844 those packages and upgrade anyway.
18846 o Directory authority changes:
18847 - Change IP address for maatuska (v3 directory authority).
18848 - Change IP address for ides (v3 directory authority), and rename
18852 - When building or running with any version of OpenSSL earlier
18853 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
18854 versions have a bug (CVE-2011-4576) in which their block cipher
18855 padding includes uninitialized data, potentially leaking sensitive
18856 information to any peer with whom they make a SSLv3 connection. Tor
18857 does not use SSL v3 by default, but a hostile client or server
18858 could force an SSLv3 connection in order to gain information that
18859 they shouldn't have been able to get. The best solution here is to
18860 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
18861 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
18862 to make sure that the bug can't happen.
18863 - Never use a bridge or a controller-supplied node as an exit, even
18864 if its exit policy allows it. Found by wanoskarnet. Fixes bug
18865 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
18866 and 0.2.0.3-alpha (for bridge-purpose descriptors).
18867 - Only build circuits if we have a sufficient threshold of the total
18868 descriptors that are marked in the consensus with the "Exit"
18869 flag. This mitigates an attack proposed by wanoskarnet, in which
18870 all of a client's bridges collude to restrict the exit nodes that
18871 the client knows about. Fixes bug 5343.
18872 - Provide controllers with a safer way to implement the cookie
18873 authentication mechanism. With the old method, if another locally
18874 running program could convince a controller that it was the Tor
18875 process, then that program could trick the controller into telling
18876 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
18877 authentication method uses a challenge-response approach to prevent
18878 this attack. Fixes bug 5185; implements proposal 193.
18881 - Avoid logging uninitialized data when unable to decode a hidden
18882 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
18883 - Avoid a client-side assertion failure when receiving an INTRODUCE2
18884 cell on a general purpose circuit. Fixes bug 5644; bugfix on
18886 - Fix builds when the path to sed, openssl, or sha1sum contains
18887 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
18889 - Correct our replacements for the timeradd() and timersub() functions
18890 on platforms that lack them (for example, Windows). The timersub()
18891 function is used when expiring circuits, while timeradd() is
18892 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
18893 bugfix on 0.2.2.24-alpha.
18894 - Fix the SOCKET_OK test that we use to tell when socket
18895 creation fails so that it works on Win64. Fixes part of bug 4533;
18896 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
18899 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
18900 Fixes bug 5346; bugfix on 0.0.8pre3.
18901 - Make our number-parsing functions always treat too-large values
18902 as an error, even when those values exceed the width of the
18903 underlying type. Previously, if the caller provided these
18904 functions with minima or maxima set to the extreme values of the
18905 underlying integer type, these functions would return those
18906 values on overflow rather than treating overflow as an error.
18907 Fixes part of bug 5786; bugfix on 0.0.9.
18908 - Older Linux kernels erroneously respond to strange nmap behavior
18909 by having accept() return successfully with a zero-length
18910 socket. When this happens, just close the connection. Previously,
18911 we would try harder to learn the remote address: but there was
18912 no such remote address to learn, and our method for trying to
18913 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
18914 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
18915 - Correct parsing of certain date types in parse_http_time().
18916 Without this patch, If-Modified-Since would behave
18917 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
18918 Esteban Manchado Velázques.
18919 - Change the BridgePassword feature (part of the "bridge community"
18920 design, which is not yet implemented) to use a time-independent
18921 comparison. The old behavior might have allowed an adversary
18922 to use timing to guess the BridgePassword value. Fixes bug 5543;
18923 bugfix on 0.2.0.14-alpha.
18924 - Detect and reject certain misformed escape sequences in
18925 configuration values. Previously, these values would cause us
18926 to crash if received in a torrc file or over an authenticated
18927 control port. Bug found by Esteban Manchado Velázquez, and
18928 independently by Robert Connolly from Matta Consulting who further
18929 noted that it allows a post-authentication heap overflow. Patch
18930 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
18931 bugfix on 0.2.0.16-alpha.
18932 - Fix a compile warning when using the --enable-openbsd-malloc
18933 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
18934 - During configure, detect when we're building with clang version
18935 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
18936 CFLAGS. clang doesn't support them yet.
18937 - When sending an HTTP/1.1 proxy request, include a Host header.
18938 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
18939 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
18940 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
18941 - If we hit the error case where routerlist_insert() replaces an
18942 existing (old) server descriptor, make sure to remove that
18943 server descriptor from the old_routers list. Fix related to bug
18944 1776. Bugfix on 0.2.2.18-alpha.
18946 o Minor bugfixes (documentation and log messages):
18947 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
18948 Fixes bug 4856; bugfix on Tor 0.0.6.
18949 - Update "ClientOnly" man page entry to explain that there isn't
18950 really any point to messing with it. Resolves ticket 5005.
18951 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
18952 directory authority option (introduced in Tor 0.2.2.34).
18953 - Downgrade the "We're missing a certificate" message from notice
18954 to info: people kept mistaking it for a real problem, whereas it
18955 is seldom the problem even when we are failing to bootstrap. Fixes
18956 bug 5067; bugfix on 0.2.0.10-alpha.
18957 - Correctly spell "connect" in a log message on failure to create a
18958 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
18959 - Clarify the behavior of MaxCircuitDirtiness with hidden service
18960 circuits. Fixes issue 5259.
18963 - Directory authorities now reject versions of Tor older than
18964 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
18965 inclusive. These versions accounted for only a small fraction of
18966 the Tor network, and have numerous known security issues. Resolves
18968 - Update to the May 1 2012 Maxmind GeoLite Country database.
18971 - When sending or relaying a RELAY_EARLY cell, we used to convert
18972 it to a RELAY cell if the connection was using the v1 link
18973 protocol. This was a workaround for older versions of Tor, which
18974 didn't handle RELAY_EARLY cells properly. Now that all supported
18975 versions can handle RELAY_EARLY cells, and now that we're enforcing
18976 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
18977 remove this workaround. Addresses bug 4786.
18980 Changes in version 0.2.3.15-alpha - 2012-04-30
18981 Tor 0.2.3.15-alpha fixes a variety of smaller bugs, including making
18982 the development branch build on Windows again.
18984 o Minor bugfixes (on 0.2.2.x and earlier):
18985 - Make sure that there are no unhandled pending TLS errors before
18986 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
18987 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
18988 Bugfix on 0.1.0.5-rc; fixes bug 4528.
18989 - Fix an assert that directory authorities could trigger on sighup
18990 during some configuration state transitions. We now don't treat
18991 it as a fatal error when the new descriptor we just generated in
18992 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
18993 - After we pick a directory mirror, we would refuse to use it if
18994 it's in our ExcludeExitNodes list, resulting in mysterious failures
18995 to bootstrap for people who just wanted to avoid exiting from
18996 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
18997 - When building with --enable-static-tor on OpenBSD, do not
18998 erroneously attempt to link -lrt. Fixes bug 5103.
19000 o Minor bugfixes (on 0.2.3.x):
19001 - When Tor is built with kernel headers from a recent (last few
19002 years) Linux kernel, do not fail to run on older (pre-2.6.28
19003 Linux kernels). Fixes bug 5112; bugfix on 0.2.3.1-alpha.
19004 - Fix cross-compilation issues with mingw. Bugfixes on 0.2.3.6-alpha
19005 and 0.2.3.12-alpha.
19006 - Fix compilation with miniupnpc version 1.6; patch from
19007 Anthony G. Basile. Fixes bug 5434; bugfix on 0.2.3.12-alpha.
19008 - Fix compilation with MSVC, which had defined MS_WINDOWS. Bugfix
19009 on 0.2.3.13-alpha; found and fixed by Gisle Vanem.
19010 - Fix compilation on platforms without unistd.h, or where environ
19011 is defined in stdlib.h. Fixes bug 5704; bugfix on 0.2.3.13-alpha.
19014 - Directory authorities are now a little more lenient at accepting
19015 older router descriptors, or newer router descriptors that don't
19016 make big changes. This should help ameliorate past and future
19017 issues where routers think they have uploaded valid descriptors,
19018 but the authorities don't think so. Fix for ticket 2479.
19019 - Make the code that clients use to detect an address change be
19020 IPv6-aware, so that it won't fill clients' logs with error
19021 messages when trying to get the IPv4 address of an IPv6
19022 connection. Implements ticket 5537.
19024 o Removed features:
19025 - Remove the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays option;
19026 authorities needed to use it for a while to keep the network working
19027 as people upgraded to 0.2.1.31, 0.2.2.34, or 0.2.3.6-alpha, but
19028 that was six months ago. As of now, it should no longer be needed
19032 Changes in version 0.2.3.14-alpha - 2012-04-23
19033 Tor 0.2.3.14-alpha fixes yet more bugs to get us closer to a release
19034 candidate. It also dramatically speeds up AES: fast relays should
19035 consider switching to the newer OpenSSL library.
19037 o Directory authority changes:
19038 - Change IP address for ides (v3 directory authority), and rename
19042 - Avoid logging uninitialized data when unable to decode a hidden
19043 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
19044 - Avoid a client-side assertion failure when receiving an INTRODUCE2
19045 cell on a general purpose circuit. Fixes bug 5644; bugfix on
19047 - If authorities are unable to get a v2 consensus document from other
19048 directory authorities, they no longer fall back to fetching
19049 them from regular directory caches. Fixes bug 5635; bugfix on
19050 0.2.2.26-beta, where routers stopped downloading v2 consensus
19051 documents entirely.
19052 - When we start a Tor client with a normal consensus already cached,
19053 be willing to download a microdescriptor consensus. Fixes bug 4011;
19054 fix on 0.2.3.1-alpha.
19056 o Major features (performance):
19057 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
19058 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
19059 vectorized AES implementations as appropriate. These can be much,
19060 much faster than other AES implementations.
19062 o Minor bugfixes (0.2.2.x and earlier):
19063 - Don't launch more than 10 service-side introduction-point circuits
19064 for a hidden service in five minutes. Previously, we would consider
19065 launching more introduction-point circuits if at least one second
19066 had passed without any introduction-point circuits failing. Fixes
19067 bug 4607; bugfix on 0.0.7pre1.
19068 - Change the BridgePassword feature (part of the "bridge community"
19069 design, which is not yet implemented) to use a time-independent
19070 comparison. The old behavior might have allowed an adversary
19071 to use timing to guess the BridgePassword value. Fixes bug 5543;
19072 bugfix on 0.2.0.14-alpha.
19073 - Enforce correct return behavior of tor_vsscanf() when the '%%'
19074 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
19075 - When sending an HTTP/1.1 proxy request, include a Host header.
19076 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
19077 - Don't log that we have "decided to publish new relay descriptor"
19078 unless we are actually publishing a descriptor. Fixes bug 3942;
19079 bugfix on 0.2.2.28-beta.
19081 o Minor bugfixes (0.2.3.x):
19082 - Fix a bug where a bridge authority crashes (on a failed assert)
19083 if it has seen no directory requests when it's time to write
19084 statistics to disk. Fixes bug 5508. Bugfix on 0.2.3.6-alpha.
19085 - Fix bug stomping on ORPort option NoListen and ignoring option
19086 NoAdvertise. Fixes bug 5151; bugfix on 0.2.3.9-alpha.
19087 - In the testsuite, provide a large enough buffer in the tor_sscanf
19088 unit test. Otherwise we'd overrun that buffer and crash during
19089 the unit tests. Found by weasel. Fixes bug 5449; bugfix on
19091 - Make sure we create the keys directory if it doesn't exist and we're
19092 about to store the dynamic Diffie-Hellman parameters. Fixes bug
19093 5572; bugfix on 0.2.3.13-alpha.
19094 - Fix a small memory leak when trying to decode incorrect base16
19095 authenticator during SAFECOOKIE authentication. Found by
19096 Coverity Scan. Fixes CID 507. Bugfix on 0.2.3.13-alpha.
19099 - Add more information to a log statement that might help track down
19100 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
19101 non-IP address" messages (or any Bug messages, for that matter!),
19102 please let us know about it.
19103 - Relays now understand an IPv6 address when they get one from a
19104 directory server. Resolves ticket 4875.
19105 - Resolve IPv6 addresses in bridge and entry statistics to country
19106 code "??" which means we at least count them. Resolves ticket 5053;
19107 improves on 0.2.3.9-alpha.
19108 - Update to the April 3 2012 Maxmind GeoLite Country database.
19109 - Begin a doc/state-contents.txt file to explain the contents of
19110 the Tor state file. Fixes bug 2987.
19112 o Default torrc changes:
19113 - Stop listing "socksport 9050" in torrc.sample. We open a socks
19114 port on 9050 by default anyway, so this should not change anything
19116 - Stop mentioning the deprecated *ListenAddress options in
19117 torrc.sample. Fixes bug 5438.
19118 - Document unit of bandwidth related options in sample torrc.
19121 o Removed features:
19122 - The "torify" script no longer supports the "tsocks" socksifier
19123 tool, since tsocks doesn't support DNS and UDP right for Tor.
19124 Everyone should be using torsocks instead. Fixes bugs 3530 and
19125 5180. Based on a patch by "ugh".
19127 o Code refactoring:
19128 - Change the symmetric cipher interface so that creating and
19129 initializing a stream cipher are no longer separate functions.
19130 - Remove all internal support for unpadded RSA. We never used it, and
19131 it would be a bad idea to start.
19134 Changes in version 0.2.3.13-alpha - 2012-03-26
19135 Tor 0.2.3.13-alpha fixes a variety of stability and correctness bugs
19136 in managed pluggable transports, as well as providing other cleanups
19137 that get us closer to a release candidate.
19139 o Directory authority changes:
19140 - Change IP address for maatuska (v3 directory authority).
19143 - Provide controllers with a safer way to implement the cookie
19144 authentication mechanism. With the old method, if another locally
19145 running program could convince a controller that it was the Tor
19146 process, then that program could trick the controller into telling
19147 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
19148 authentication method uses a challenge-response approach to prevent
19149 this attack. Fixes bug 5185, implements proposal 193.
19150 - Never use a bridge or a controller-supplied node as an exit, even
19151 if its exit policy allows it. Found by wanoskarnet. Fixes bug
19152 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
19153 and 0.2.0.3-alpha (for bridge-purpose descriptors).
19154 - Only build circuits if we have a sufficient threshold of the total
19155 descriptors that are marked in the consensus with the "Exit"
19156 flag. This mitigates an attack proposed by wanoskarnet, in which
19157 all of a client's bridges collude to restrict the exit nodes that
19158 the client knows about. Fixes bug 5343.
19160 o Major bugfixes (on Tor 0.2.3.x):
19161 - Avoid an assert when managed proxies like obfsproxy are configured,
19162 and we receive HUP signals or setconf attempts too rapidly. This
19163 situation happens most commonly when Vidalia tries to attach to
19164 Tor or tries to configure the Tor it's attached to. Fixes bug 5084;
19165 bugfix on 0.2.3.6-alpha.
19166 - Fix a relay-side pluggable transports bug where managed proxies were
19167 unreachable from the Internet, because Tor asked them to bind on
19168 localhost. Fixes bug 4725; bugfix on 0.2.3.9-alpha.
19169 - Stop discarding command-line arguments when TestingTorNetwork
19170 is set. Discovered by Kevin Bauer. Fixes bug 5373; bugfix on
19171 0.2.3.9-alpha, where task 4552 added support for two layers of
19173 - Resume allowing the unit tests to run in gdb. This was accidentally
19174 made impossible when the DisableDebuggerAttachment option was
19175 introduced. Fixes bug 5448; bugfix on 0.2.3.9-alpha.
19176 - Resume building with nat-pmp support. Fixes bug 4955; bugfix on
19177 0.2.3.11-alpha. Reported by Anthony G. Basile.
19179 o Minor bugfixes (on 0.2.2.x and earlier):
19180 - Ensure we don't cannibalize circuits that are longer than three hops
19181 already, so we don't end up making circuits with 5 or more
19182 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
19183 0.1.0.1-rc which introduced cannibalization.
19184 - Detect and reject certain misformed escape sequences in
19185 configuration values. Previously, these values would cause us
19186 to crash if received in a torrc file or over an authenticated
19187 control port. Bug found by Esteban Manchado Velázquez, and
19188 independently by Robert Connolly from Matta Consulting who further
19189 noted that it allows a post-authentication heap overflow. Patch
19190 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
19191 bugfix on 0.2.0.16-alpha.
19192 - Fix a compile warning when using the --enable-openbsd-malloc
19193 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
19194 - Directory caches no longer refuse to clean out descriptors because
19195 of missing v2 networkstatus documents, unless they're configured
19196 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
19197 0.2.2.26-beta. Patch by Daniel Bryg.
19198 - Update to the latest version of the tinytest unit testing framework.
19199 This includes a couple of bugfixes that can be relevant for
19200 running forked unit tests on Windows, and removes all reserved
19203 o Minor bugfixes (on 0.2.3.x):
19204 - On a failed pipe() call, don't leak file descriptors. Fixes bug
19205 4296; bugfix on 0.2.3.1-alpha.
19206 - Spec conformance: on a v3 handshake, do not send a NETINFO cell
19207 until after we have received a CERTS cell. Fixes bug 4361; bugfix
19208 on 0.2.3.6-alpha. Patch by "frosty".
19209 - When binding to an IPv6 address, set the IPV6_V6ONLY socket
19210 option, so that the IP stack doesn't decide to use it for IPv4
19211 too. Fixes bug 4760; bugfix on 0.2.3.9-alpha.
19212 - Ensure that variables set in Tor's environment cannot override
19213 environment variables that Tor passes to a managed
19214 pluggable-transport proxy. Previously, Tor would pass every
19215 variable in its environment to managed proxies along with the new
19216 ones, in such a way that on many operating systems, the inherited
19217 environment variables would override those which Tor tried to
19218 explicitly set. Bugfix on 0.2.3.12-alpha for most Unixoid systems;
19219 bugfix on 0.2.3.9-alpha for Windows.
19222 - A wide variety of new unit tests by Esteban Manchado Velázquez.
19223 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
19224 - Update to the March 6 2012 Maxmind GeoLite Country database.
19227 Changes in version 0.2.3.12-alpha - 2012-02-13
19228 Tor 0.2.3.12-alpha lets fast exit relays scale better, allows clients
19229 to use bridges that run Tor 0.2.2.x, and resolves several big bugs
19230 when Tor is configured to use a pluggable transport like obfsproxy.
19233 - Fix builds when the path to sed, openssl, or sha1sum contains
19234 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
19236 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
19237 connections. This change should allow busy exit relays to stop
19238 running out of available sockets as quickly. Fixes bug 4950;
19239 bugfix on 0.2.2.26-beta.
19240 - Allow 0.2.3.x clients to use 0.2.2.x bridges. Previously the client
19241 would ask the bridge for microdescriptors, which are only supported
19242 in 0.2.3.x, and then fail to bootstrap when it didn't get the
19243 answers it wanted. Fixes bug 4013; bugfix on 0.2.3.2-alpha.
19244 - Properly set up obfsproxy's environment when in managed mode. The
19245 Tor Browser Bundle needs LD_LIBRARY_PATH to be passed to obfsproxy,
19246 and when you run your Tor as a daemon, there's no HOME. Fixes bugs
19247 5076 and 5082; bugfix on 0.2.3.6-alpha.
19250 - Use the dead_strip option when building Tor on OS X. This reduces
19251 binary size by almost 19% when linking openssl and libevent
19252 statically, which we do for Tor Browser Bundle.
19253 - Fix broken URLs in the sample torrc file, and tell readers about
19254 the OutboundBindAddress, ExitPolicyRejectPrivate, and
19255 PublishServerDescriptor options. Addresses bug 4652.
19256 - Update to the February 7 2012 Maxmind GeoLite Country database.
19259 - Downgrade the "We're missing a certificate" message from notice
19260 to info: people kept mistaking it for a real problem, whereas it
19261 is seldom the problem even when we are failing to bootstrap. Fixes
19262 bug 5067; bugfix on 0.2.0.10-alpha.
19263 - Don't put "TOR_PT_EXTENDED_SERVER_PORT=127.0.0.1:4200" in a
19264 managed pluggable transport server proxy's environment.
19265 Previously, we would put it there, even though Tor doesn't
19266 implement an 'extended server port' yet, and even though Tor
19267 almost certainly isn't listening at that address. For now, we set
19268 it to an empty string to avoid crashing older obfsproxies. Bugfix
19270 - Log the heartbeat message every HeartbeatPeriod seconds, not every
19271 HeartbeatPeriod + 1 seconds. Fixes bug 4942; bugfix on
19272 0.2.3.1-alpha. Bug reported by Scott Bennett.
19273 - Calculate absolute paths correctly on Windows. Fixes bug 4973;
19274 bugfix on 0.2.3.11-alpha.
19275 - Update "ClientOnly" man page entry to explain that there isn't
19276 really any point to messing with it. Resolves ticket 5005.
19277 - Use the correct CVE number for CVE-2011-4576 in our comments and
19278 log messages. Found by "fermenthor". Resolves bug 5066; bugfix on
19281 o Code simplifications and refactoring:
19282 - Use the _WIN32 macro throughout our code to detect Windows.
19283 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
19287 Changes in version 0.2.3.11-alpha - 2012-01-22
19288 Tor 0.2.3.11-alpha marks feature-freeze for the 0.2.3 tree. It deploys
19289 the last step of the plan to limit maximum circuit length, includes
19290 a wide variety of hidden service performance and correctness fixes,
19291 works around an OpenSSL security flaw if your distro is too stubborn
19292 to upgrade, and fixes a bunch of smaller issues.
19295 - Now that Tor 0.2.0.x is completely deprecated, enable the final
19296 part of "Proposal 110: Avoiding infinite length circuits" by
19297 refusing all circuit-extend requests that do not use a relay_early
19298 cell. This change helps Tor resist a class of denial-of-service
19299 attacks by limiting the maximum circuit length.
19300 - Adjust the number of introduction points that a hidden service
19301 will try to maintain based on how long its introduction points
19302 remain in use and how many introductions they handle. Fixes
19304 - Try to use system facilities for enumerating local interface
19305 addresses, before falling back to our old approach (which was
19306 binding a UDP socket, and calling getsockname() on it). That
19307 approach was scaring OS X users whose draconian firewall
19308 software warned about binding to UDP sockets, regardless of
19309 whether packets were sent. Now we try to use getifaddrs(),
19310 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
19311 system supports. Resolves ticket 1827.
19313 o Major security workaround:
19314 - When building or running with any version of OpenSSL earlier
19315 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
19316 versions have a bug (CVE-2011-4576) in which their block cipher
19317 padding includes uninitialized data, potentially leaking sensitive
19318 information to any peer with whom they make a SSLv3 connection. Tor
19319 does not use SSL v3 by default, but a hostile client or server
19320 could force an SSLv3 connection in order to gain information that
19321 they shouldn't have been able to get. The best solution here is to
19322 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
19323 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
19324 to make sure that the bug can't happen.
19327 - Fix the SOCKET_OK test that we use to tell when socket
19328 creation fails so that it works on Win64. Fixes part of bug 4533;
19329 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
19330 - Correct our replacements for the timeradd() and timersub() functions
19331 on platforms that lack them (for example, Windows). The timersub()
19332 function is used when expiring circuits, while timeradd() is
19333 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
19334 bugfix on 0.2.2.24-alpha and 0.2.3.1-alpha.
19335 - Do not use OpenSSL 1.0.0's counter mode: it has a critical bug
19336 that was fixed in OpenSSL 1.0.0a. We test for the counter mode
19337 bug at runtime, not compile time, because some distributions hack
19338 their OpenSSL to mis-report its version. Fixes bug 4779; bugfix
19339 on 0.2.3.9-alpha. Found by Pascal.
19341 o Minor features (controller):
19342 - Use absolute path names when reporting the torrc filename in the
19343 control protocol, so a controller can more easily find the torrc
19344 file. Resolves bug 1101.
19345 - Extend the control protocol to report flags that control a circuit's
19346 path selection in CIRC events and in replies to 'GETINFO
19347 circuit-status'. Implements part of ticket 2411.
19348 - Extend the control protocol to report the hidden service address
19349 and current state of a hidden-service-related circuit in CIRC
19350 events and in replies to 'GETINFO circuit-status'. Implements part
19352 - When reporting the path to the cookie file to the controller,
19353 give an absolute path. Resolves ticket 4881.
19354 - Allow controllers to request an event notification whenever a
19355 circuit is cannibalized or its purpose is changed. Implements
19356 part of ticket 3457.
19357 - Include the creation time of a circuit in CIRC and CIRC2
19358 control-port events and the list produced by the 'GETINFO
19359 circuit-status' control-port command.
19361 o Minor features (directory authorities):
19362 - Directory authorities now reject versions of Tor older than
19363 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
19364 inclusive. These versions accounted for only a small fraction of
19365 the Tor network, and have numerous known security issues. Resolves
19367 - Authority operators can now vote for all relays in a given
19368 set of countries to be BadDir/BadExit/Invalid/Rejected.
19369 - Provide two consensus parameters (FastFlagMinThreshold and
19370 FastFlagMaxThreshold) to control the range of allowable bandwidths
19371 for the Fast directory flag. These allow authorities to run
19372 experiments on appropriate requirements for being a "Fast" node.
19373 The AuthDirFastGuarantee config value still applies. Implements
19375 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
19376 directory authority option (introduced in Tor 0.2.2.34).
19378 o Minor features (other):
19379 - Don't disable the DirPort when we cannot exceed our AccountingMax
19380 limit during this interval because the effective bandwidthrate is
19381 low enough. This is useful in a situation where AccountMax is only
19382 used as an additional safeguard or to provide statistics.
19383 - Prepend an informative header to generated dynamic_dh_params files.
19384 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
19385 EntryNodes will have no effect. Resolves issue 2571.
19386 - Log more useful messages when we fail to disable debugger
19388 - Log which authority we're missing votes from when we go to fetch
19389 them from the other auths.
19390 - Log (at debug level) whenever a circuit's purpose is changed.
19391 - Add missing documentation for the MaxClientCircuitsPending,
19392 UseMicrodescriptors, UserspaceIOCPBuffers, and
19393 _UseFilteringSSLBufferevents options, all introduced during
19394 the 0.2.3.x series.
19395 - Update to the January 3 2012 Maxmind GeoLite Country database.
19397 o Minor bugfixes (hidden services):
19398 - Don't close hidden service client circuits which have almost
19399 finished connecting to their destination when they reach
19400 the normal circuit-build timeout. Previously, we would close
19401 introduction circuits which are waiting for an acknowledgement
19402 from the introduction point, and rendezvous circuits which have
19403 been specified in an INTRODUCE1 cell sent to a hidden service,
19404 after the normal CBT. Now, we mark them as 'timed out', and launch
19405 another rendezvous attempt in parallel. This behavior change can
19406 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
19407 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
19408 - Don't close hidden-service-side rendezvous circuits when they
19409 reach the normal circuit-build timeout. This behavior change can
19410 be disabled using the new
19411 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
19412 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
19413 - Make sure we never mark the wrong rendezvous circuit as having
19414 had its introduction cell acknowledged by the introduction-point
19415 relay. Previously, when we received an INTRODUCE_ACK cell on a
19416 client-side hidden-service introduction circuit, we might have
19417 marked a rendezvous circuit other than the one we specified in
19418 the INTRODUCE1 cell as INTRO_ACKED, which would have produced
19419 a warning message and interfered with the hidden service
19420 connection-establishment process. Fixes bug 4759; bugfix on
19421 0.2.3.3-alpha, when we added the stream-isolation feature which
19422 might cause Tor to open multiple rendezvous circuits for the same
19424 - Don't trigger an assertion failure when we mark a new client-side
19425 hidden-service introduction circuit for close during the process
19426 of creating it. Fixes bug 4796; bugfix on 0.2.3.6-alpha. Reported
19429 o Minor bugfixes (log messages):
19430 - Correctly spell "connect" in a log message on failure to create a
19431 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta and
19433 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
19434 Fixes bug 4856; bugfix on Tor 0.0.6.
19435 - Fix the log message describing how we work around discovering
19436 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
19437 4837; bugfix on 0.2.2.9-alpha.
19438 - When logging about a disallowed .exit name, do not also call it
19439 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
19441 o Minor bugfixes (build fixes):
19442 - During configure, detect when we're building with clang version
19443 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
19444 CFLAGS. clang doesn't support them yet.
19445 - During configure, search for library containing cos function as
19446 libm lives in libcore on some platforms (BeOS/Haiku). Linking
19447 against libm was hard-coded before. Fixes the first part of bug
19448 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
19450 - Detect attempts to build Tor on (as yet hypothetical) versions
19451 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
19452 fix for bug 4533. Bugfix on 0.2.2.28-beta.
19453 - Preprocessor directives should not be put inside the arguments
19454 of a macro. This would break compilation with GCC releases prior
19455 to version 3.3. We would never recommend such an old GCC version,
19456 but it is apparently required for binary compatibility on some
19457 platforms (namely, certain builds of Haiku). Fixes the other part
19458 of bug 4727; bugfix on 0.2.3.3-alpha. Patch and analysis by Martin
19461 o Minor bugfixes (other):
19462 - Older Linux kernels erroneously respond to strange nmap behavior
19463 by having accept() return successfully with a zero-length
19464 socket. When this happens, just close the connection. Previously,
19465 we would try harder to learn the remote address: but there was
19466 no such remote address to learn, and our method for trying to
19467 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
19468 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
19469 - Fix null-pointer access that could occur if TLS allocation failed.
19470 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un". This was
19471 erroneously listed as fixed in 0.2.3.9-alpha, but the fix had
19472 accidentally been reverted.
19473 - Fix our implementation of crypto_random_hostname() so it can't
19474 overflow on ridiculously large inputs. (No Tor version has ever
19475 provided this kind of bad inputs, but let's be correct in depth.)
19476 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
19477 - Find more places in the code that should have been testing for
19478 invalid sockets using the SOCKET_OK macro. Required for a fix
19479 for bug 4533. Bugfix on 0.2.2.28-beta.
19480 - Fix an assertion failure when, while running with bufferevents, a
19481 connection finishes connecting after it is marked for close, but
19482 before it is closed. Fixes bug 4697; bugfix on 0.2.3.1-alpha.
19483 - test_util_spawn_background_ok() hardcoded the expected value
19484 for ENOENT to 2. This isn't portable as error numbers are
19485 platform specific, and particularly the hurd has ENOENT at
19486 0x40000002. Construct expected string at runtime, using the correct
19487 value for ENOENT. Fixes bug 4733; bugfix on 0.2.3.1-alpha.
19488 - Reject attempts to disable DisableDebuggerAttachment while Tor is
19489 running. Fixes bug 4650; bugfix on 0.2.3.9-alpha.
19490 - Use an appropriate-width type for sockets in tor-fw-helper on
19491 win64. Fixes bug 1983 at last. Bugfix on 0.2.3.9-alpha.
19494 - When sending or relaying a RELAY_EARLY cell, we used to convert
19495 it to a RELAY cell if the connection was using the v1 link
19496 protocol. This was a workaround for older versions of Tor, which
19497 didn't handle RELAY_EARLY cells properly. Now that all supported
19498 versions can handle RELAY_EARLY cells, and now that we're enforcing
19499 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
19500 remove this workaround. Addresses bug 4786.
19502 o Code simplifications and refactoring:
19503 - Use OpenSSL's built-in SSL_state_string_long() instead of our
19504 own homebrewed ssl_state_to_string() replacement. Patch from
19505 Emile Snyder. Fixes bug 4653.
19506 - Use macros to indicate OpenSSL versions, so we don't need to worry
19507 about accidental hexadecimal bit shifts.
19508 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
19510 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
19511 - Use the smartlist_add_asprintf() alias more consistently.
19512 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
19513 invalid value, rather than just -1.
19514 - Rename a handful of old identifiers, mostly related to crypto
19515 structures and crypto functions. By convention, our "create an
19516 object" functions are called "type_new()", our "free an object"
19517 functions are called "type_free()", and our types indicate that
19518 they are types only with a final "_t". But a handful of older
19519 types and functions broke these rules, with function names like
19520 "type_create" or "subsystem_op_type", or with type names like
19524 Changes in version 0.2.3.10-alpha - 2011-12-16
19525 Tor 0.2.3.10-alpha fixes a critical heap-overflow security issue in
19526 Tor's buffers code. Absolutely everybody should upgrade.
19528 The bug relied on an incorrect calculation when making data continuous
19529 in one of our IO buffers, if the first chunk of the buffer was
19530 misaligned by just the wrong amount. The miscalculation would allow an
19531 attacker to overflow a piece of heap-allocated memory. To mount this
19532 attack, the attacker would need to either open a SOCKS connection to
19533 Tor's SocksPort (usually restricted to localhost), or target a Tor
19534 instance configured to make its connections through a SOCKS proxy
19535 (which Tor does not do by default).
19537 Good security practice requires that all heap-overflow bugs should be
19538 presumed to be exploitable until proven otherwise, so we are treating
19539 this as a potential code execution attack. Please upgrade immediately!
19540 This bug does not affect bufferevents-based builds of Tor. Special
19541 thanks to "Vektor" for reporting this issue to us!
19543 This release also contains a few minor bugfixes for issues discovered
19547 - Fix a heap overflow bug that could occur when trying to pull
19548 data into the first chunk of a buffer, when that chunk had
19549 already had some data drained from it. Fixes CVE-2011-2778;
19550 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
19553 - If we can't attach streams to a rendezvous circuit when we
19554 finish connecting to a hidden service, clear the rendezvous
19555 circuit's stream-isolation state and try to attach streams
19556 again. Previously, we cleared rendezvous circuits' isolation
19557 state either too early (if they were freshly built) or not at all
19558 (if they had been built earlier and were cannibalized). Bugfix on
19559 0.2.3.3-alpha; fixes bug 4655.
19560 - Fix compilation of the libnatpmp helper on non-Windows. Bugfix on
19561 0.2.3.9-alpha; fixes bug 4691. Reported by Anthony G. Basile.
19562 - Fix an assertion failure when a relay with accounting enabled
19563 starts up while dormant. Fixes bug 4702; bugfix on 0.2.3.9-alpha.
19566 - Update to the December 6 2011 Maxmind GeoLite Country database.
19569 Changes in version 0.2.2.35 - 2011-12-16
19570 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
19571 buffers code. Absolutely everybody should upgrade.
19573 The bug relied on an incorrect calculation when making data continuous
19574 in one of our IO buffers, if the first chunk of the buffer was
19575 misaligned by just the wrong amount. The miscalculation would allow an
19576 attacker to overflow a piece of heap-allocated memory. To mount this
19577 attack, the attacker would need to either open a SOCKS connection to
19578 Tor's SocksPort (usually restricted to localhost), or target a Tor
19579 instance configured to make its connections through a SOCKS proxy
19580 (which Tor does not do by default).
19582 Good security practice requires that all heap-overflow bugs should be
19583 presumed to be exploitable until proven otherwise, so we are treating
19584 this as a potential code execution attack. Please upgrade immediately!
19585 This bug does not affect bufferevents-based builds of Tor. Special
19586 thanks to "Vektor" for reporting this issue to us!
19588 Tor 0.2.2.35 also fixes several bugs in previous versions, including
19589 crash bugs for unusual configurations, and a long-term bug that
19590 would prevent Tor from starting on Windows machines with draconian
19593 With this release, we remind everyone that 0.2.0.x has reached its
19594 formal end-of-life. Those Tor versions have many known flaws, and
19595 nobody should be using them. You should upgrade -- ideally to the
19596 0.2.2.x series. If you're using a Linux or BSD and its packages are
19597 obsolete, stop using those packages and upgrade anyway.
19599 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
19600 longer receive support after some time in early 2012.
19603 - Fix a heap overflow bug that could occur when trying to pull
19604 data into the first chunk of a buffer, when that chunk had
19605 already had some data drained from it. Fixes CVE-2011-2778;
19606 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
19607 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
19608 that it doesn't attempt to allocate a socketpair. This could cause
19609 some problems on Windows systems with overzealous firewalls. Fix for
19610 bug 4457; workaround for Libevent versions 2.0.1-alpha through
19612 - If we mark an OR connection for close based on a cell we process,
19613 don't process any further cells on it. We already avoid further
19614 reads on marked-for-close connections, but now we also discard the
19615 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
19616 which was the first version where we might mark a connection for
19617 close based on processing a cell on it.
19618 - Correctly sanity-check that we don't underflow on a memory
19619 allocation (and then assert) for hidden service introduction
19620 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
19621 bugfix on 0.2.1.5-alpha.
19622 - Fix a memory leak when we check whether a hidden service
19623 descriptor has any usable introduction points left. Fixes bug
19624 4424. Bugfix on 0.2.2.25-alpha.
19625 - Don't crash when we're running as a relay and don't have a GeoIP
19626 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
19627 we've had in the 0.2.3.x branch already.
19628 - When running as a client, do not print a misleading (and plain
19629 wrong) log message that we're collecting "directory request"
19630 statistics: clients don't collect statistics. Also don't create a
19631 useless (because empty) stats file in the stats/ directory. Fixes
19632 bug 4353; bugfix on 0.2.2.34.
19635 - Detect failure to initialize Libevent. This fix provides better
19636 detection for future instances of bug 4457.
19637 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
19638 function. This was eating up hideously large amounts of time on some
19639 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
19640 - Resolve an integer overflow bug in smartlist_ensure_capacity().
19641 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
19643 - Don't warn about unused log_mutex in log.c when building with
19644 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
19645 0.1.0.6-rc which introduced --disable-threads.
19646 - When configuring, starting, or stopping an NT service, stop
19647 immediately after the service configuration attempt has succeeded
19648 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
19649 - When sending a NETINFO cell, include the original address
19650 received for the other side, not its canonical address. Found
19651 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
19652 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
19653 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
19654 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
19655 occurred when a client tried to fetch a descriptor for a bridge
19656 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
19657 - Backport fixes for a pair of compilation warnings on Windows.
19658 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
19659 - If we had ever tried to call tor_addr_to_str on an address of
19660 unknown type, we would have done a strdup on an uninitialized
19661 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
19662 Reported by "troll_un".
19663 - Correctly detect and handle transient lookup failures from
19664 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
19665 Reported by "troll_un".
19666 - Fix null-pointer access that could occur if TLS allocation failed.
19667 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
19668 - Use tor_socket_t type for listener argument to accept(). Fixes bug
19669 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
19672 - Add two new config options for directory authorities:
19673 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
19674 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
19675 that is always sufficient to satisfy the bandwidth requirement for
19676 the Guard flag. Now it will be easier for researchers to simulate
19677 Tor networks with different values. Resolves ticket 4484.
19678 - When Tor ignores a hidden service specified in its configuration,
19679 include the hidden service's directory in the warning message.
19680 Previously, we would only tell the user that some hidden service
19681 was ignored. Bugfix on 0.0.6; fixes bug 4426.
19682 - Update to the December 6 2011 Maxmind GeoLite Country database.
19684 o Packaging changes:
19685 - Make it easier to automate expert package builds on Windows,
19686 by removing an absolute path from makensis.exe command.
19689 Changes in version 0.2.1.32 - 2011-12-16
19690 Tor 0.2.1.32 backports important security and privacy fixes for
19691 oldstable. This release is intended only for package maintainers and
19692 others who cannot use the 0.2.2 stable series. All others should be
19693 using Tor 0.2.2.x or newer.
19695 The Tor 0.2.1.x series will reach formal end-of-life some time in
19696 early 2012; we will stop releasing patches for it then.
19698 o Major bugfixes (also included in 0.2.2.x):
19699 - Correctly sanity-check that we don't underflow on a memory
19700 allocation (and then assert) for hidden service introduction
19701 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
19702 bugfix on 0.2.1.5-alpha.
19703 - Fix a heap overflow bug that could occur when trying to pull
19704 data into the first chunk of a buffer, when that chunk had
19705 already had some data drained from it. Fixes CVE-2011-2778;
19706 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
19709 - Update to the December 6 2011 Maxmind GeoLite Country database.
19712 Changes in version 0.2.3.9-alpha - 2011-12-08
19713 Tor 0.2.3.9-alpha introduces initial IPv6 support for bridges, adds
19714 a "DisableNetwork" security feature that bundles can use to avoid
19715 touching the network until bridges are configured, moves forward on
19716 the pluggable transport design, fixes a flaw in the hidden service
19717 design that unnecessarily prevented clients with wrong clocks from
19718 reaching hidden services, and fixes a wide variety of other issues.
19721 - Clients can now connect to private bridges over IPv6. Bridges
19722 still need at least one IPv4 address in order to connect to
19723 other relays. Note that we don't yet handle the case where the
19724 user has two bridge lines for the same bridge (one IPv4, one
19725 IPv6). Implements parts of proposal 186.
19726 - New "DisableNetwork" config option to prevent Tor from launching any
19727 connections or accepting any connections except on a control port.
19728 Bundles and controllers can set this option before letting Tor talk
19729 to the rest of the network, for example to prevent any connections
19730 to a non-bridge address. Packages like Orbot can also use this
19731 option to instruct Tor to save power when the network is off.
19732 - Clients and bridges can now be configured to use a separate
19733 "transport" proxy. This approach makes the censorship arms race
19734 easier by allowing bridges to use protocol obfuscation plugins. It
19735 implements the "managed proxy" part of proposal 180 (ticket 3472).
19736 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
19737 implementation. It makes AES_CTR about 7% faster than our old one
19738 (which was about 10% faster than the one OpenSSL used to provide).
19739 Resolves ticket 4526.
19740 - Add a "tor2web mode" for clients that want to connect to hidden
19741 services non-anonymously (and possibly more quickly). As a safety
19742 measure to try to keep users from turning this on without knowing
19743 what they are doing, tor2web mode must be explicitly enabled at
19744 compile time, and a copy of Tor compiled to run in tor2web mode
19745 cannot be used as a normal Tor client. Implements feature 2553.
19746 - Add experimental support for running on Windows with IOCP and no
19747 kernel-space socket buffers. This feature is controlled by a new
19748 "UserspaceIOCPBuffers" config option (off by default), which has
19749 no effect unless Tor has been built with support for bufferevents,
19750 is running on Windows, and has enabled IOCP. This may, in the long
19751 run, help solve or mitigate bug 98.
19752 - Use a more secure consensus parameter voting algorithm. Now at
19753 least three directory authorities or a majority of them must
19754 vote on a given parameter before it will be included in the
19755 consensus. Implements proposal 178.
19758 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
19759 They used to check that the timestamp was within 30 minutes
19760 of their system clock, so they could cap the size of their
19761 replay-detection cache, but that approach unnecessarily refused
19762 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
19763 the v3 intro-point protocol (the first one which sent a timestamp
19764 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
19765 - Only use the EVP interface when AES acceleration is enabled,
19766 to avoid a 5-7% performance regression. Resolves issue 4525;
19767 bugfix on 0.2.3.8-alpha.
19769 o Privacy/anonymity features (bridge detection):
19770 - Make bridge SSL certificates a bit more stealthy by using random
19771 serial numbers, in the same fashion as OpenSSL when generating
19772 self-signed certificates. Implements ticket 4584.
19773 - Introduce a new config option "DynamicDHGroups", enabled by
19774 default, which provides each bridge with a unique prime DH modulus
19775 to be used during SSL handshakes. This option attempts to help
19776 against censors who might use the Apache DH modulus as a static
19777 identifier for bridges. Addresses ticket 4548.
19779 o Minor features (new/different config options):
19780 - New configuration option "DisableDebuggerAttachment" (on by default)
19781 to prevent basic debugging attachment attempts by other processes.
19782 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
19783 - Allow MapAddress directives to specify matches against super-domains,
19784 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
19785 Implements issue 933.
19786 - Slightly change behavior of "list" options (that is, config
19787 options that can appear more than once) when they appear both in
19788 torrc and on the command line. Previously, the command-line options
19789 would be appended to the ones from torrc. Now, the command-line
19790 options override the torrc options entirely. This new behavior
19791 allows the user to override list options (like exit policies and
19792 ports to listen on) from the command line, rather than simply
19793 appending to the list.
19794 - You can get the old (appending) command-line behavior for "list"
19795 options by prefixing the option name with a "+".
19796 - You can remove all the values for a "list" option from the command
19797 line without adding any new ones by prefixing the option name
19799 - Add experimental support for a "defaults" torrc file to be parsed
19800 before the regular torrc. Torrc options override the defaults file's
19801 options in the same way that the command line overrides the torrc.
19802 The SAVECONF controller command saves only those options which
19803 differ between the current configuration and the defaults file. HUP
19804 reloads both files. (Note: This is an experimental feature; its
19805 behavior will probably be refined in future 0.2.3.x-alpha versions
19806 to better meet packagers' needs.) Implements task 4552.
19809 - Try to make the introductory warning message that Tor prints on
19810 startup more useful for actually finding help and information.
19811 Resolves ticket 2474.
19812 - Running "make version" now displays the version of Tor that
19813 we're about to build. Idea from katmagic; resolves issue 4400.
19814 - Expire old or over-used hidden service introduction points.
19815 Required by fix for bug 3460.
19816 - Move the replay-detection cache for the RSA-encrypted parts of
19817 INTRODUCE2 cells to the introduction point data structures.
19818 Previously, we would use one replay-detection cache per hidden
19819 service. Required by fix for bug 3460.
19820 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
19821 public key replay-detection cache from 60 minutes to 5 minutes. This
19822 replay-detection cache is now used only to detect multiple
19823 INTRODUCE2 cells specifying the same rendezvous point, so we can
19824 avoid launching multiple simultaneous attempts to connect to it.
19826 o Minor bugfixes (on Tor 0.2.2.x and earlier):
19827 - Resolve an integer overflow bug in smartlist_ensure_capacity().
19828 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
19830 - Fix a minor formatting issue in one of tor-gencert's error messages.
19832 - Prevent a false positive from the check-spaces script, by disabling
19833 the "whitespace between function name and (" check for functions
19835 - Fix a log message suggesting that people contact a non-existent
19836 email address. Fixes bug 3448.
19837 - Fix null-pointer access that could occur if TLS allocation failed.
19838 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
19839 - Report a real bootstrap problem to the controller on router
19840 identity mismatch. Previously we just said "foo", which probably
19841 made a lot of sense at the time. Fixes bug 4169; bugfix on
19843 - If we had ever tried to call tor_addr_to_str() on an address of
19844 unknown type, we would have done a strdup() on an uninitialized
19845 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
19846 Reported by "troll_un".
19847 - Correctly detect and handle transient lookup failures from
19848 tor_addr_lookup(). Fixes bug 4530; bugfix on 0.2.1.5-alpha.
19849 Reported by "troll_un".
19850 - Use tor_socket_t type for listener argument to accept(). Fixes bug
19851 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
19852 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
19853 bug 4532; found by "troll_un".
19855 o Minor bugfixes (on Tor 0.2.3.x):
19856 - Fix a compile warning in tor_inet_pton(). Bugfix on 0.2.3.8-alpha;
19858 - Don't send two ESTABLISH_RENDEZVOUS cells when opening a new
19859 circuit for use as a hidden service client's rendezvous point.
19860 Fixes bugs 4641 and 4171; bugfix on 0.2.3.3-alpha. Diagnosed
19861 with help from wanoskarnet.
19862 - Restore behavior of overriding SocksPort, ORPort, and similar
19863 options from the command line. Bugfix on 0.2.3.3-alpha.
19866 - Properly handle the case where the build-tree is not the same
19867 as the source tree when generating src/common/common_sha1.i,
19868 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
19869 bugfix on 0.2.0.1-alpha.
19871 o Code simplifications, cleanups, and refactorings:
19872 - Remove the pure attribute from all functions that used it
19873 previously. In many cases we assigned it incorrectly, because the
19874 functions might assert or call impure functions, and we don't have
19875 evidence that keeping the pure attribute is worthwhile. Implements
19876 changes suggested in ticket 4421.
19877 - Remove some dead code spotted by coverity. Fixes cid 432.
19878 Bugfix on 0.2.3.1-alpha, closes bug 4637.
19881 Changes in version 0.2.3.8-alpha - 2011-11-22
19882 Tor 0.2.3.8-alpha fixes some crash and assert bugs, including a
19883 socketpair-related bug that has been bothering Windows users. It adds
19884 support to serve microdescriptors to controllers, so Vidalia's network
19885 map can resume listing relays (once Vidalia implements its side),
19886 and adds better support for hardware AES acceleration. Finally, it
19887 starts the process of adjusting the bandwidth cutoff for getting the
19888 "Fast" flag from 20KB to (currently) 32KB -- preliminary results show
19889 that tiny relays harm performance more than they help network capacity.
19892 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
19893 that it doesn't attempt to allocate a socketpair. This could cause
19894 some problems on Windows systems with overzealous firewalls. Fix for
19895 bug 4457; workaround for Libevent versions 2.0.1-alpha through
19897 - Correctly sanity-check that we don't underflow on a memory
19898 allocation (and then assert) for hidden service introduction
19899 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
19900 bugfix on 0.2.1.5-alpha.
19901 - Remove the artificially low cutoff of 20KB to guarantee the Fast
19902 flag. In the past few years the average relay speed has picked
19903 up, and while the "top 7/8 of the network get the Fast flag" and
19904 "all relays with 20KB or more of capacity get the Fast flag" rules
19905 used to have the same result, now the top 7/8 of the network has
19906 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
19907 - Fix a rare assertion failure when checking whether a v0 hidden
19908 service descriptor has any usable introduction points left, and
19909 we don't have enough information to build a circuit to the first
19910 intro point named in the descriptor. The HS client code in
19911 0.2.3.x no longer uses v0 HS descriptors, but this assertion can
19912 trigger on (and crash) v0 HS authorities. Fixes bug 4411.
19913 Bugfix on 0.2.3.1-alpha; diagnosed by frosty_un.
19914 - Make bridge authorities not crash when they are asked for their own
19915 descriptor. Bugfix on 0.2.3.7-alpha, reported by Lucky Green.
19916 - When running as a client, do not print a misleading (and plain
19917 wrong) log message that we're collecting "directory request"
19918 statistics: clients don't collect statistics. Also don't create a
19919 useless (because empty) stats file in the stats/ directory. Fixes
19920 bug 4353; bugfix on 0.2.2.34 and 0.2.3.7-alpha.
19923 - Allow Tor controllers like Vidalia to obtain the microdescriptor
19924 for a relay by identity digest or nickname. Previously,
19925 microdescriptors were only available by their own digests, so a
19926 controller would have to ask for and parse the whole microdescriptor
19927 consensus in order to look up a single relay's microdesc. Fixes
19928 bug 3832; bugfix on 0.2.3.1-alpha.
19929 - Use OpenSSL's EVP interface for AES encryption, so that all AES
19930 operations can use hardware acceleration (if present). Resolves
19933 o Minor bugfixes (on 0.2.2.x and earlier):
19934 - Detect failure to initialize Libevent. This fix provides better
19935 detection for future instances of bug 4457.
19936 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
19937 function. This was eating up hideously large amounts of time on some
19938 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
19939 - Don't warn about unused log_mutex in log.c when building with
19940 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
19941 0.1.0.6-rc which introduced --disable-threads.
19942 - Allow manual 'authenticate' commands to the controller interface
19943 from netcat (nc) as well as telnet. We were rejecting them because
19944 they didn't come with the expected whitespace at the end of the
19945 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
19946 - Fix some (not actually triggerable) buffer size checks in usage of
19947 tor_inet_ntop. Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
19949 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
19950 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
19951 - When configuring, starting, or stopping an NT service, stop
19952 immediately after the service configuration attempt has succeeded
19953 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
19954 - When sending a NETINFO cell, include the original address
19955 received for the other side, not its canonical address. Found
19956 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
19957 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
19958 can pick them up when the tests aren't disabled. Bugfix on
19959 0.2.2.4-alpha which introduced tinytest.
19960 - Fix a memory leak when we check whether a hidden service
19961 descriptor has any usable introduction points left. Fixes bug
19962 4424. Bugfix on 0.2.2.25-alpha.
19963 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
19964 occurred when a client tried to fetch a descriptor for a bridge
19965 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
19967 o Minor bugfixes (on 0.2.3.x):
19968 - Make util unit tests build correctly with MSVC. Bugfix on
19969 0.2.3.3-alpha. Patch by Gisle Vanem.
19970 - Successfully detect AUTH_CHALLENGE cells with no recognized
19971 authentication type listed. Fixes bug 4367; bugfix on 0.2.3.6-alpha.
19972 Found by frosty_un.
19973 - If a relay receives an AUTH_CHALLENGE cell it can't answer,
19974 it should still send a NETINFO cell to allow the connection to
19975 become open. Fixes bug 4368; fix on 0.2.3.6-alpha; bug found by
19977 - Log less loudly when we get an invalid authentication certificate
19978 from a source other than a directory authority: it's not unusual
19979 to see invalid certs because of clock skew. Fixes bug 4370; bugfix
19981 - Tolerate servers with more clock skew in their authentication
19982 certificates than previously. Fixes bug 4371; bugfix on
19984 - Fix a couple of compile warnings on Windows. Fixes bug 4469; bugfix
19985 on 0.2.3.4-alpha and 0.2.3.6-alpha.
19988 - Add two new config options for directory authorities:
19989 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
19990 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
19991 that is always sufficient to satisfy the bandwidth requirement for
19992 the Guard flag. Now it will be easier for researchers to simulate
19993 Tor networks with different values. Resolves ticket 4484.
19994 - When Tor ignores a hidden service specified in its configuration,
19995 include the hidden service's directory in the warning message.
19996 Previously, we would only tell the user that some hidden service
19997 was ignored. Bugfix on 0.0.6; fixes bug 4426.
19998 - When we fail to initialize Libevent, retry with IOCP disabled so we
19999 don't need to turn on multi-threading support in Libevent, which in
20000 turn requires a working socketpair(). This is a workaround for bug
20001 4457, which affects Libevent versions from 2.0.1-alpha through
20003 - Detect when we try to build on a platform that doesn't define
20004 AF_UNSPEC to 0. We don't work there, so refuse to compile.
20005 - Update to the November 1 2011 Maxmind GeoLite Country database.
20007 o Packaging changes:
20008 - Make it easier to automate expert package builds on Windows,
20009 by removing an absolute path from makensis.exe command.
20011 o Code simplifications and refactoring:
20012 - Remove some redundant #include directives throughout the code.
20013 Patch from Andrea Gelmini.
20014 - Unconditionally use OpenSSL's AES implementation instead of our
20015 old built-in one. OpenSSL's AES has been better for a while, and
20016 relatively few servers should still be on any version of OpenSSL
20017 that doesn't have good optimized assembly AES.
20018 - Use the name "CERTS" consistently to refer to the new cell type;
20019 we were calling it CERT in some places and CERTS in others.
20022 - Numerous new unit tests for functions in util.c and address.c by
20024 - The long-disabled benchmark tests are now split into their own
20025 ./src/test/bench binary.
20026 - The benchmark tests can now use more accurate timers than
20027 gettimeofday() when such timers are available.
20030 Changes in version 0.2.3.7-alpha - 2011-10-30
20031 Tor 0.2.3.7-alpha fixes a crash bug in 0.2.3.6-alpha introduced by
20032 the new v3 handshake. It also resolves yet another bridge address
20036 - If we mark an OR connection for close based on a cell we process,
20037 don't process any further cells on it. We already avoid further
20038 reads on marked-for-close connections, but now we also discard the
20039 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
20040 which was the first version where we might mark a connection for
20041 close based on processing a cell on it.
20042 - Fix a double-free bug that would occur when we received an invalid
20043 certificate in a CERT cell in the new v3 handshake. Fixes bug 4343;
20044 bugfix on 0.2.3.6-alpha.
20045 - Bridges no longer include their address in NETINFO cells on outgoing
20046 OR connections, to allow them to blend in better with clients.
20047 Removes another avenue for enumerating bridges. Reported by
20048 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
20049 cells were introduced.
20052 - Fixed a typo in a hibernation-related log message. Fixes bug 4331;
20053 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
20056 Changes in version 0.2.3.6-alpha - 2011-10-26
20057 Tor 0.2.3.6-alpha includes the fix from 0.2.2.34 for a critical
20058 anonymity vulnerability where an attacker can deanonymize Tor
20059 users. Everybody should upgrade.
20061 This release also features support for a new v3 connection handshake
20062 protocol, and fixes to make hidden service connections more robust.
20065 - Implement a new handshake protocol (v3) for authenticating Tors to
20066 each other over TLS. It should be more resistant to fingerprinting
20067 than previous protocols, and should require less TLS hacking for
20068 future Tor implementations. Implements proposal 176.
20069 - Allow variable-length padding cells to disguise the length of
20070 Tor's TLS records. Implements part of proposal 184.
20072 o Privacy/anonymity fixes (clients):
20073 - Clients and bridges no longer send TLS certificate chains on
20074 outgoing OR connections. Previously, each client or bridge would
20075 use the same cert chain for all outgoing OR connections until
20076 its IP address changes, which allowed any relay that the client
20077 or bridge contacted to determine which entry guards it is using.
20078 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
20079 - If a relay receives a CREATE_FAST cell on a TLS connection, it
20080 no longer considers that connection as suitable for satisfying a
20081 circuit EXTEND request. Now relays can protect clients from the
20082 CVE-2011-2768 issue even if the clients haven't upgraded yet.
20083 - Directory authorities no longer assign the Guard flag to relays
20084 that haven't upgraded to the above "refuse EXTEND requests
20085 to client connections" fix. Now directory authorities can
20086 protect clients from the CVE-2011-2768 issue even if neither
20087 the clients nor the relays have upgraded yet. There's a new
20088 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
20089 to let us transition smoothly, else tomorrow there would be no
20092 o Major bugfixes (hidden services):
20093 - Improve hidden service robustness: when an attempt to connect to
20094 a hidden service ends, be willing to refetch its hidden service
20095 descriptors from each of the HSDir relays responsible for them
20096 immediately. Previously, we would not consider refetching the
20097 service's descriptors from each HSDir for 15 minutes after the last
20098 fetch, which was inconvenient if the hidden service was not running
20099 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
20100 - When one of a hidden service's introduction points appears to be
20101 unreachable, stop trying it. Previously, we would keep trying
20102 to build circuits to the introduction point until we lost the
20103 descriptor, usually because the user gave up and restarted Tor.
20104 Partly fixes bug 3825.
20105 - Don't launch a useless circuit after failing to use one of a
20106 hidden service's introduction points. Previously, we would
20107 launch a new introduction circuit, but not set the hidden service
20108 which that circuit was intended to connect to, so it would never
20109 actually be used. A different piece of code would then create a
20110 new introduction circuit correctly. Bug reported by katmagic and
20111 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
20113 o Major bugfixes (other):
20114 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
20115 that they initiated. Relays could distinguish incoming bridge
20116 connections from client connections, creating another avenue for
20117 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
20118 Found by "frosty_un".
20119 - Don't update the AccountingSoftLimitHitAt state file entry whenever
20120 tor gets started. This prevents a wrong average bandwidth
20121 estimate, which would cause relays to always start a new accounting
20122 interval at the earliest possible moment. Fixes bug 2003; bugfix
20123 on 0.2.2.7-alpha. Reported by BryonEldridge, who also helped
20124 immensely in tracking this bug down.
20125 - Fix a crash bug when changing node restrictions while a DNS lookup
20126 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
20129 o Minor bugfixes (on 0.2.2.x and earlier):
20130 - When a hidden service turns an extra service-side introduction
20131 circuit into a general-purpose circuit, free the rend_data and
20132 intro_key fields first, so we won't leak memory if the circuit
20133 is cannibalized for use as another service-side introduction
20134 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
20135 - Rephrase the log message emitted if the TestSocks check is
20136 successful. Patch from Fabian Keil; fixes bug 4094.
20137 - Bridges now skip DNS self-tests, to act a little more stealthily.
20138 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
20139 bridges. Patch by "warms0x".
20140 - Remove a confusing dollar sign from the example fingerprint in the
20141 man page, and also make the example fingerprint a valid one. Fixes
20142 bug 4309; bugfix on 0.2.1.3-alpha.
20143 - Fix internal bug-checking logic that was supposed to catch
20144 failures in digest generation so that it will fail more robustly
20145 if we ask for a nonexistent algorithm. Found by Coverity Scan.
20146 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
20147 - Report any failure in init_keys() calls launched because our
20148 IP address has changed. Spotted by Coverity Scan. Bugfix on
20149 0.1.1.4-alpha; fixes CID 484.
20151 o Minor bugfixes (on 0.2.3.x):
20152 - Fix a bug in configure.in that kept it from building a configure
20153 script with autoconf versions earlier than 2.61. Fixes bug 2430;
20154 bugfix on 0.2.3.1-alpha.
20155 - Don't warn users that they are exposing a client port to the
20156 Internet if they have specified an RFC1918 address. Previously,
20157 we would warn if the user had specified any non-loopback
20158 address. Bugfix on 0.2.3.3-alpha. Fixes bug 4018; reported by Tas.
20159 - Fix memory leaks in the failing cases of the new SocksPort and
20160 ControlPort code. Found by Coverity Scan. Bugfix on 0.2.3.3-alpha;
20161 fixes coverity CIDs 485, 486, and 487.
20164 - When a hidden service's introduction point times out, consider
20165 trying it again during the next attempt to connect to the
20166 HS. Previously, we would not try it again unless a newly fetched
20167 descriptor contained it. Required by fixes for bugs 1297 and 3825.
20168 - The next version of Windows will be called Windows 8, and it has
20169 a major version of 6, minor version of 2. Correctly identify that
20170 version instead of calling it "Very recent version". Resolves
20171 ticket 4153; reported by funkstar.
20172 - The Bridge Authority now writes statistics on how many bridge
20173 descriptors it gave out in total, and how many unique descriptors
20174 it gave out. It also lists how often the most and least commonly
20175 fetched descriptors were given out, as well as the median and
20176 25th/75th percentile. Implements tickets 4200 and 4294.
20177 - Update to the October 4 2011 Maxmind GeoLite Country database.
20179 o Code simplifications and refactoring:
20180 - Remove some old code to remember statistics about which descriptors
20181 we've served as a directory mirror. The feature wasn't used and
20182 is outdated now that microdescriptors are around.
20183 - Rename Tor functions that turn strings into addresses, so that
20184 "parse" indicates that no hostname resolution occurs, and
20185 "lookup" indicates that hostname resolution may occur. This
20186 should help prevent mistakes in the future. Fixes bug 3512.
20189 Changes in version 0.2.2.34 - 2011-10-26
20190 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
20191 can deanonymize Tor users. Everybody should upgrade.
20193 The attack relies on four components: 1) Clients reuse their TLS cert
20194 when talking to different relays, so relays can recognize a user by
20195 the identity key in her cert. 2) An attacker who knows the client's
20196 identity key can probe each guard relay to see if that identity key
20197 is connected to that guard relay right now. 3) A variety of active
20198 attacks in the literature (starting from "Low-Cost Traffic Analysis
20199 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
20200 discover the guard relays that a Tor user visiting the website is using.
20201 4) Clients typically pick three guards at random, so the set of guards
20202 for a given user could well be a unique fingerprint for her. This
20203 release fixes components #1 and #2, which is enough to block the attack;
20204 the other two remain as open research problems. Special thanks to
20205 "frosty_un" for reporting the issue to us!
20207 Clients should upgrade so they are no longer recognizable by the TLS
20208 certs they present. Relays should upgrade so they no longer allow a
20209 remote attacker to probe them to test whether unpatched clients are
20210 currently connected to them.
20212 This release also fixes several vulnerabilities that allow an attacker
20213 to enumerate bridge relays. Some bridge enumeration attacks still
20214 remain; see for example proposal 188.
20216 o Privacy/anonymity fixes (clients):
20217 - Clients and bridges no longer send TLS certificate chains on
20218 outgoing OR connections. Previously, each client or bridge would
20219 use the same cert chain for all outgoing OR connections until
20220 its IP address changes, which allowed any relay that the client
20221 or bridge contacted to determine which entry guards it is using.
20222 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
20223 - If a relay receives a CREATE_FAST cell on a TLS connection, it
20224 no longer considers that connection as suitable for satisfying a
20225 circuit EXTEND request. Now relays can protect clients from the
20226 CVE-2011-2768 issue even if the clients haven't upgraded yet.
20227 - Directory authorities no longer assign the Guard flag to relays
20228 that haven't upgraded to the above "refuse EXTEND requests
20229 to client connections" fix. Now directory authorities can
20230 protect clients from the CVE-2011-2768 issue even if neither
20231 the clients nor the relays have upgraded yet. There's a new
20232 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
20233 to let us transition smoothly, else tomorrow there would be no
20236 o Privacy/anonymity fixes (bridge enumeration):
20237 - Bridge relays now do their directory fetches inside Tor TLS
20238 connections, like all the other clients do, rather than connecting
20239 directly to the DirPort like public relays do. Removes another
20240 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
20241 - Bridges relays now build circuits for themselves in a more similar
20242 way to how clients build them. Removes another avenue for
20243 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
20244 when bridges were introduced.
20245 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
20246 that they initiated. Relays could distinguish incoming bridge
20247 connections from client connections, creating another avenue for
20248 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
20249 Found by "frosty_un".
20252 - Fix a crash bug when changing node restrictions while a DNS lookup
20253 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
20255 - Don't launch a useless circuit after failing to use one of a
20256 hidden service's introduction points. Previously, we would
20257 launch a new introduction circuit, but not set the hidden service
20258 which that circuit was intended to connect to, so it would never
20259 actually be used. A different piece of code would then create a
20260 new introduction circuit correctly. Bug reported by katmagic and
20261 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
20264 - Change an integer overflow check in the OpenBSD_Malloc code so
20265 that GCC is less likely to eliminate it as impossible. Patch
20266 from Mansour Moufid. Fixes bug 4059.
20267 - When a hidden service turns an extra service-side introduction
20268 circuit into a general-purpose circuit, free the rend_data and
20269 intro_key fields first, so we won't leak memory if the circuit
20270 is cannibalized for use as another service-side introduction
20271 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
20272 - Bridges now skip DNS self-tests, to act a little more stealthily.
20273 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
20274 bridges. Patch by "warms0x".
20275 - Fix internal bug-checking logic that was supposed to catch
20276 failures in digest generation so that it will fail more robustly
20277 if we ask for a nonexistent algorithm. Found by Coverity Scan.
20278 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
20279 - Report any failure in init_keys() calls launched because our
20280 IP address has changed. Spotted by Coverity Scan. Bugfix on
20281 0.1.1.4-alpha; fixes CID 484.
20283 o Minor bugfixes (log messages and documentation):
20284 - Remove a confusing dollar sign from the example fingerprint in the
20285 man page, and also make the example fingerprint a valid one. Fixes
20286 bug 4309; bugfix on 0.2.1.3-alpha.
20287 - The next version of Windows will be called Windows 8, and it has
20288 a major version of 6, minor version of 2. Correctly identify that
20289 version instead of calling it "Very recent version". Resolves
20290 ticket 4153; reported by funkstar.
20291 - Downgrade log messages about circuit timeout calibration from
20292 "notice" to "info": they don't require or suggest any human
20293 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
20294 bugfix on 0.2.2.14-alpha.
20297 - Turn on directory request statistics by default and include them in
20298 extra-info descriptors. Don't break if we have no GeoIP database.
20299 Backported from 0.2.3.1-alpha; implements ticket 3951.
20300 - Update to the October 4 2011 Maxmind GeoLite Country database.
20303 Changes in version 0.2.1.31 - 2011-10-26
20304 Tor 0.2.1.31 backports important security and privacy fixes for
20305 oldstable. This release is intended only for package maintainers and
20306 others who cannot use the 0.2.2 stable series. All others should be
20307 using Tor 0.2.2.x or newer.
20309 o Security fixes (also included in 0.2.2.x):
20310 - Replace all potentially sensitive memory comparison operations
20311 with versions whose runtime does not depend on the data being
20312 compared. This will help resist a class of attacks where an
20313 adversary can use variations in timing information to learn
20314 sensitive data. Fix for one case of bug 3122. (Safe memcmp
20315 implementation by Robert Ransom based partially on code by DJB.)
20316 - Fix an assert in parsing router descriptors containing IPv6
20317 addresses. This one took down the directory authorities when
20318 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
20320 o Privacy/anonymity fixes (also included in 0.2.2.x):
20321 - Clients and bridges no longer send TLS certificate chains on
20322 outgoing OR connections. Previously, each client or bridge would
20323 use the same cert chain for all outgoing OR connections until
20324 its IP address changes, which allowed any relay that the client
20325 or bridge contacted to determine which entry guards it is using.
20326 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
20327 - If a relay receives a CREATE_FAST cell on a TLS connection, it
20328 no longer considers that connection as suitable for satisfying a
20329 circuit EXTEND request. Now relays can protect clients from the
20330 CVE-2011-2768 issue even if the clients haven't upgraded yet.
20331 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
20332 that they initiated. Relays could distinguish incoming bridge
20333 connections from client connections, creating another avenue for
20334 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
20335 Found by "frosty_un".
20336 - When receiving a hidden service descriptor, check that it is for
20337 the hidden service we wanted. Previously, Tor would store any
20338 hidden service descriptors that a directory gave it, whether it
20339 wanted them or not. This wouldn't have let an attacker impersonate
20340 a hidden service, but it did let directories pre-seed a client
20341 with descriptors that it didn't want. Bugfix on 0.0.6.
20342 - Avoid linkability based on cached hidden service descriptors: forget
20343 all hidden service descriptors cached as a client when processing a
20344 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
20345 - Make the bridge directory authority refuse to answer directory
20346 requests for "all" descriptors. It used to include bridge
20347 descriptors in its answer, which was a major information leak.
20348 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
20349 - Don't attach new streams to old rendezvous circuits after SIGNAL
20350 NEWNYM. Previously, we would keep using an existing rendezvous
20351 circuit if it remained open (i.e. if it were kept open by a
20352 long-lived stream, or if a new stream were attached to it before
20353 Tor could notice that it was old and no longer in use). Bugfix on
20354 0.1.1.15-rc; fixes bug 3375.
20356 o Minor bugfixes (also included in 0.2.2.x):
20357 - When we restart our relay, we might get a successful connection
20358 from the outside before we've started our reachability tests,
20359 triggering a warning: "ORPort found reachable, but I have no
20360 routerinfo yet. Failing to inform controller of success." This
20361 bug was harmless unless Tor is running under a controller
20362 like Vidalia, in which case the controller would never get a
20363 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
20365 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
20366 enabled. Fixes bug 1526.
20367 - Remove undocumented option "-F" from tor-resolve: it hasn't done
20368 anything since 0.2.1.16-rc.
20369 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
20370 None of the cases where we did this before were wrong, but by making
20371 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
20372 - Fix a rare crash bug that could occur when a client was configured
20373 with a large number of bridges. Fixes bug 2629; bugfix on
20374 0.2.1.2-alpha. Bugfix by trac user "shitlei".
20375 - Correct the warning displayed when a rendezvous descriptor exceeds
20376 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
20378 - Fix an uncommon assertion failure when running with DNSPort under
20379 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
20380 - When warning about missing zlib development packages during compile,
20381 give the correct package names. Bugfix on 0.2.0.1-alpha.
20382 - Require that introduction point keys and onion keys have public
20383 exponent 65537. Bugfix on 0.2.0.10-alpha.
20384 - Do not crash when our configuration file becomes unreadable, for
20385 example due to a permissions change, between when we start up
20386 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
20388 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
20390 - Always NUL-terminate the sun_path field of a sockaddr_un before
20391 passing it to the kernel. (Not a security issue: kernels are
20392 smart enough to reject bad sockaddr_uns.) Found by Coverity;
20393 CID #428. Bugfix on Tor 0.2.0.3-alpha.
20394 - Don't stack-allocate the list of supplementary GIDs when we're
20395 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
20396 could take up to 256K, which is way too much stack. Found by
20397 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
20399 o Minor bugfixes (only in 0.2.1.x):
20400 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
20401 rely on them. Bugfix on 0.2.1.30.
20402 - Use git revisions instead of svn revisions when generating our
20403 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
20405 o Minor features (also included in 0.2.2.x):
20406 - Adjust the expiration time on our SSL session certificates to
20407 better match SSL certs seen in the wild. Resolves ticket 4014.
20408 - Allow nameservers with IPv6 address. Resolves bug 2574.
20409 - Update to the October 4 2011 Maxmind GeoLite Country database.
20412 Changes in version 0.2.3.5-alpha - 2011-09-28
20413 Tor 0.2.3.5-alpha fixes two bugs that make it possible to enumerate
20414 bridge relays; fixes an assertion error that many users started hitting
20415 today; and adds the ability to refill token buckets more often than
20416 once per second, allowing significant performance improvements.
20419 - Bridge relays now do their directory fetches inside Tor TLS
20420 connections, like all the other clients do, rather than connecting
20421 directly to the DirPort like public relays do. Removes another
20422 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
20423 - Bridges relays now build circuits for themselves in a more similar
20424 way to how clients build them. Removes another avenue for
20425 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
20426 when bridges were introduced.
20429 - Fix an "Assertion md->held_by_node == 1 failed" error that could
20430 occur when the same microdescriptor was referenced by two node_t
20431 objects at once. Fix for bug 4118; bugfix on Tor 0.2.3.1-alpha.
20433 o Major features (networking):
20434 - Add a new TokenBucketRefillInterval option to refill token buckets
20435 more frequently than once per second. This should improve network
20436 performance, alleviate queueing problems, and make traffic less
20437 bursty. Implements proposal 183; closes ticket 3630. Design by
20438 Florian Tschorsch and Björn Scheuermann; implementation by
20442 - Change an integer overflow check in the OpenBSD_Malloc code so
20443 that GCC is less likely to eliminate it as impossible. Patch
20444 from Mansour Moufid. Fixes bug 4059.
20446 o Minor bugfixes (usability):
20447 - Downgrade log messages about circuit timeout calibration from
20448 "notice" to "info": they don't require or suggest any human
20449 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
20450 bugfix on 0.2.2.14-alpha.
20452 o Minor features (diagnostics):
20453 - When the system call to create a listener socket fails, log the
20454 error message explaining why. This may help diagnose bug 4027.
20457 Changes in version 0.2.3.4-alpha - 2011-09-13
20458 Tor 0.2.3.4-alpha includes the fixes from 0.2.2.33, including a slight
20459 tweak to Tor's TLS handshake that makes relays and bridges that run
20460 this new version reachable from Iran again. It also fixes a few new
20461 bugs in 0.2.3.x, and teaches relays to recognize when they're not
20462 listed in the network consensus and republish.
20464 o Major bugfixes (also part of 0.2.2.33):
20465 - Avoid an assertion failure when reloading a configuration with
20466 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
20467 3923; bugfix on 0.2.2.25-alpha.
20469 o Minor features (security, also part of 0.2.2.33):
20470 - Check for replays of the public-key encrypted portion of an
20471 INTRODUCE1 cell, in addition to the current check for replays of
20472 the g^x value. This prevents a possible class of active attacks
20473 by an attacker who controls both an introduction point and a
20474 rendezvous point, and who uses the malleability of AES-CTR to
20475 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
20476 that these attacks are infeasible (requiring the attacker to send
20477 on the order of zettabytes of altered cells in a short interval),
20478 but we'd rather block them off in case there are any classes of
20479 this attack that we missed. Reported by Willem Pinckaers.
20481 o Minor features (also part of 0.2.2.33):
20482 - Adjust the expiration time on our SSL session certificates to
20483 better match SSL certs seen in the wild. Resolves ticket 4014.
20484 - Change the default required uptime for a relay to be accepted as
20485 a HSDir (hidden service directory) from 24 hours to 25 hours.
20486 Improves on 0.2.0.10-alpha; resolves ticket 2649.
20487 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
20488 authorities to abstain from voting on assignment of the HSDir
20489 consensus flag. Related to bug 2649.
20490 - Update to the September 6 2011 Maxmind GeoLite Country database.
20492 o Minor bugfixes (also part of 0.2.2.33):
20493 - Demote the 'replay detected' log message emitted when a hidden
20494 service receives the same Diffie-Hellman public key in two different
20495 INTRODUCE2 cells to info level. A normal Tor client can cause that
20496 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
20497 fixes part of bug 2442.
20498 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
20499 level. There is nothing that a hidden service's operator can do
20500 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
20502 - Clarify a log message specifying the characters permitted in
20503 HiddenServiceAuthorizeClient client names. Previously, the log
20504 message said that "[A-Za-z0-9+-_]" were permitted; that could have
20505 given the impression that every ASCII character between "+" and "_"
20506 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
20508 o Build fixes (also part of 0.2.2.33):
20509 - Clean up some code issues that prevented Tor from building on older
20510 BSDs. Fixes bug 3894; reported by "grarpamp".
20511 - Search for a platform-specific version of "ar" when cross-compiling.
20512 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
20515 - Fix a bug where the SocksPort option (for example) would get
20516 ignored and replaced by the default if a SocksListenAddress
20517 option was set. Bugfix on 0.2.3.3-alpha; fixes bug 3936. Fix by
20521 - Relays now try regenerating and uploading their descriptor more
20522 frequently if they are not listed in the consensus, or if the
20523 version of their descriptor listed in the consensus is too
20524 old. This fix should prevent situations where a server declines
20525 to re-publish itself because it has done so too recently, even
20526 though the authorities decided not to list its recent-enough
20527 descriptor. Fix for bug 3327.
20530 - Relays now include a reason for regenerating their descriptors
20531 in an HTTP header when uploading to the authorities. This will
20532 make it easier to debug descriptor-upload issues in the future.
20533 - When starting as root and then changing our UID via the User
20534 control option, and we have a ControlSocket configured, make sure
20535 that the ControlSocket is owned by the same account that Tor will
20536 run under. Implements ticket 3421; fix by Jérémy Bobbio.
20539 - Abort if tor_vasprintf fails in connection_printf_to_buf (a
20540 utility function used in the control-port code). This shouldn't
20541 ever happen unless Tor is completely out of memory, but if it did
20542 happen and Tor somehow recovered from it, Tor could have sent a log
20543 message to a control port in the middle of a reply to a controller
20544 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
20545 - Make 'FetchUselessDescriptors' cause all descriptor types and
20546 all consensus types (including microdescriptors) to get fetched.
20547 Fixes bug 3851; bugfix on 0.2.3.1-alpha.
20549 o Code refactoring:
20550 - Make a new "entry connection" struct as an internal subtype of "edge
20551 connection", to simplify the code and make exit connections smaller.
20554 Changes in version 0.2.2.33 - 2011-09-13
20555 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
20556 TLS handshake that makes relays and bridges that run this new version
20557 reachable from Iran again.
20560 - Avoid an assertion failure when reloading a configuration with
20561 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
20562 3923; bugfix on 0.2.2.25-alpha.
20564 o Minor features (security):
20565 - Check for replays of the public-key encrypted portion of an
20566 INTRODUCE1 cell, in addition to the current check for replays of
20567 the g^x value. This prevents a possible class of active attacks
20568 by an attacker who controls both an introduction point and a
20569 rendezvous point, and who uses the malleability of AES-CTR to
20570 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
20571 that these attacks are infeasible (requiring the attacker to send
20572 on the order of zettabytes of altered cells in a short interval),
20573 but we'd rather block them off in case there are any classes of
20574 this attack that we missed. Reported by Willem Pinckaers.
20577 - Adjust the expiration time on our SSL session certificates to
20578 better match SSL certs seen in the wild. Resolves ticket 4014.
20579 - Change the default required uptime for a relay to be accepted as
20580 a HSDir (hidden service directory) from 24 hours to 25 hours.
20581 Improves on 0.2.0.10-alpha; resolves ticket 2649.
20582 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
20583 authorities to abstain from voting on assignment of the HSDir
20584 consensus flag. Related to bug 2649.
20585 - Update to the September 6 2011 Maxmind GeoLite Country database.
20587 o Minor bugfixes (documentation and log messages):
20588 - Correct the man page to explain that HashedControlPassword and
20589 CookieAuthentication can both be set, in which case either method
20590 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
20591 when we decided to allow these config options to both be set. Issue
20592 raised by bug 3898.
20593 - Demote the 'replay detected' log message emitted when a hidden
20594 service receives the same Diffie-Hellman public key in two different
20595 INTRODUCE2 cells to info level. A normal Tor client can cause that
20596 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
20597 fixes part of bug 2442.
20598 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
20599 level. There is nothing that a hidden service's operator can do
20600 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
20602 - Clarify a log message specifying the characters permitted in
20603 HiddenServiceAuthorizeClient client names. Previously, the log
20604 message said that "[A-Za-z0-9+-_]" were permitted; that could have
20605 given the impression that every ASCII character between "+" and "_"
20606 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
20609 - Provide a substitute implementation of lround() for MSVC, which
20610 apparently lacks it. Patch from Gisle Vanem.
20611 - Clean up some code issues that prevented Tor from building on older
20612 BSDs. Fixes bug 3894; reported by "grarpamp".
20613 - Search for a platform-specific version of "ar" when cross-compiling.
20614 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
20617 Changes in version 0.2.3.3-alpha - 2011-09-01
20618 Tor 0.2.3.3-alpha adds a new "stream isolation" feature to improve Tor's
20619 security, and provides client-side support for the microdescriptor
20620 and optimistic data features introduced earlier in the 0.2.3.x
20621 series. It also includes numerous critical bugfixes in the (optional)
20622 bufferevent-based networking backend.
20624 o Major features (stream isolation):
20625 - You can now configure Tor so that streams from different
20626 applications are isolated on different circuits, to prevent an
20627 attacker who sees your streams as they leave an exit node from
20628 linking your sessions to one another. To do this, choose some way
20629 to distinguish the applications: have them connect to different
20630 SocksPorts, or have one of them use SOCKS4 while the other uses
20631 SOCKS5, or have them pass different authentication strings to the
20632 SOCKS proxy. Then, use the new SocksPort syntax to configure the
20633 degree of isolation you need. This implements Proposal 171.
20634 - There's a new syntax for specifying multiple client ports (such as
20635 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
20636 multiple *Port entries with full addr:port syntax on each.
20637 The old *ListenAddress format is still supported, but you can't
20638 mix it with the new *Port syntax.
20640 o Major features (other):
20641 - Enable microdescriptor fetching by default for clients. This allows
20642 clients to download a much smaller amount of directory information.
20643 To disable it (and go back to the old-style consensus and
20644 descriptors), set "UseMicrodescriptors 0" in your torrc file.
20645 - Tor's firewall-helper feature, introduced in 0.2.3.1-alpha (see the
20646 "PortForwarding" config option), now supports Windows.
20647 - When using an exit relay running 0.2.3.x, clients can now
20648 "optimistically" send data before the exit relay reports that
20649 the stream has opened. This saves a round trip when starting
20650 connections where the client speaks first (such as web browsing).
20651 This behavior is controlled by a consensus parameter (currently
20652 disabled). To turn it on or off manually, use the "OptimisticData"
20653 torrc option. Implements proposal 181; code by Ian Goldberg.
20655 o Major bugfixes (bufferevents, fixes on 0.2.3.1-alpha):
20656 - When using IOCP on Windows, we need to enable Libevent windows
20658 - The IOCP backend now works even when the user has not specified
20659 the (internal, debugging-only) _UseFilteringSSLBufferevents option.
20660 Fixes part of bug 3752.
20661 - Correctly record the bytes we've read and written when using
20662 bufferevents, so that we can include them in our bandwidth history
20663 and advertised bandwidth. Fixes bug 3803.
20664 - Apply rate-limiting only at the bottom of a chain of filtering
20665 bufferevents. This prevents us from filling up internal read
20666 buffers and violating rate-limits when filtering bufferevents
20667 are enabled. Fixes part of bug 3804.
20668 - Add high-watermarks to the output buffers for filtered
20669 bufferevents. This prevents us from filling up internal write
20670 buffers and wasting CPU cycles when filtering bufferevents are
20671 enabled. Fixes part of bug 3804.
20672 - Correctly notice when data has been written from a bufferevent
20673 without flushing it completely. Fixes bug 3805.
20674 - Fix a bug where server-side tunneled bufferevent-based directory
20675 streams would get closed prematurely. Fixes bug 3814.
20676 - Fix a use-after-free error with per-connection rate-limiting
20677 buckets. Fixes bug 3888.
20679 o Major bugfixes (also part of 0.2.2.31-rc):
20680 - If we're configured to write our ControlPorts to disk, only write
20681 them after switching UID and creating the data directory. This way,
20682 we don't fail when starting up with a nonexistent DataDirectory
20683 and a ControlPortWriteToFile setting based on that directory. Fixes
20684 bug 3747; bugfix on Tor 0.2.2.26-beta.
20687 - Added a new CONF_CHANGED event so that controllers can be notified
20688 of any configuration changes made by other controllers, or by the
20689 user. Implements ticket 1692.
20690 - Use evbuffer_copyout() in inspect_evbuffer(). This fixes a memory
20691 leak when using bufferevents, and lets Libevent worry about how to
20692 best copy data out of a buffer.
20693 - Replace files in stats/ rather than appending to them. Now that we
20694 include statistics in extra-info descriptors, it makes no sense to
20695 keep old statistics forever. Implements ticket 2930.
20697 o Minor features (build compatibility):
20698 - Limited, experimental support for building with nmake and MSVC.
20699 - Provide a substitute implementation of lround() for MSVC, which
20700 apparently lacks it. Patch from Gisle Vanem.
20702 o Minor features (also part of 0.2.2.31-rc):
20703 - Update to the August 2 2011 Maxmind GeoLite Country database.
20705 o Minor bugfixes (on 0.2.3.x-alpha):
20706 - Fix a spurious warning when parsing SOCKS requests with
20707 bufferevents enabled. Fixes bug 3615; bugfix on 0.2.3.2-alpha.
20708 - Get rid of a harmless warning that could happen on relays running
20709 with bufferevents. The warning was caused by someone doing an http
20710 request to a relay's orport. Also don't warn for a few related
20711 non-errors. Fixes bug 3700; bugfix on 0.2.3.1-alpha.
20713 o Minor bugfixes (on 2.2.x and earlier):
20714 - Correct the man page to explain that HashedControlPassword and
20715 CookieAuthentication can both be set, in which case either method
20716 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
20717 when we decided to allow these config options to both be set. Issue
20718 raised by bug 3898.
20719 - The "--quiet" and "--hush" options now apply not only to Tor's
20720 behavior before logs are configured, but also to Tor's behavior in
20721 the absence of configured logs. Fixes bug 3550; bugfix on
20724 o Minor bugfixes (also part of 0.2.2.31-rc):
20725 - Write several files in text mode, on OSes that distinguish text
20726 mode from binary mode (namely, Windows). These files are:
20727 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
20728 that collect those statistics; 'client_keys' and 'hostname' for
20729 hidden services that use authentication; and (in the tor-gencert
20730 utility) newly generated identity and signing keys. Previously,
20731 we wouldn't specify text mode or binary mode, leading to an
20732 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
20733 the DirRecordUsageByCountry option which would have triggered
20734 the assertion failure was added), although this assertion failure
20735 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
20736 - Selectively disable deprecation warnings on OS X because Lion
20737 started deprecating the shipped copy of openssl. Fixes bug 3643.
20738 - Remove an extra pair of quotation marks around the error
20739 message in control-port STATUS_GENERAL BUG events. Bugfix on
20740 0.1.2.6-alpha; fixes bug 3732.
20741 - When unable to format an address as a string, report its value
20742 as "???" rather than reusing the last formatted address. Bugfix
20745 o Code simplifications and refactoring:
20746 - Rewrite the listener-selection logic so that parsing which ports
20747 we want to listen on is now separate from binding to the ports
20751 - Building Tor with bufferevent support now requires Libevent
20752 2.0.13-stable or later. Previous versions of Libevent had bugs in
20753 SSL-related bufferevents and related issues that would make Tor
20754 work badly with bufferevents. Requiring 2.0.13-stable also allows
20755 Tor with bufferevents to take advantage of Libevent APIs
20756 introduced after 2.0.8-rc.
20759 Changes in version 0.2.2.32 - 2011-08-27
20760 The Tor 0.2.2 release series is dedicated to the memory of Andreas
20761 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
20762 a founder of the PETS community, a leader in our field, a mentor,
20763 and a friend. He left us with these words: "I had the possibility
20764 to contribute to this world that is not as it should be. I hope I
20765 could help in some areas to make the world a better place, and that
20766 I could also encourage other people to be engaged in improving the
20767 world. Please, stay engaged. This world needs you, your love, your
20768 initiative -- now I cannot be part of that anymore."
20770 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
20771 ready. More than two years in the making, this release features improved
20772 client performance and hidden service reliability, better compatibility
20773 for Android, correct behavior for bridges that listen on more than
20774 one address, more extensible and flexible directory object handling,
20775 better reporting of network statistics, improved code security, and
20776 many many other features and bugfixes.
20779 Changes in version 0.2.2.31-rc - 2011-08-17
20780 Tor 0.2.2.31-rc is the second and hopefully final release candidate
20781 for the Tor 0.2.2.x series.
20784 - Remove an extra pair of quotation marks around the error
20785 message in control-port STATUS_GENERAL BUG events. Bugfix on
20786 0.1.2.6-alpha; fixes bug 3732.
20787 - If we're configured to write our ControlPorts to disk, only write
20788 them after switching UID and creating the data directory. This way,
20789 we don't fail when starting up with a nonexistent DataDirectory
20790 and a ControlPortWriteToFile setting based on that directory. Fixes
20791 bug 3747; bugfix on Tor 0.2.2.26-beta.
20794 - Update to the August 2 2011 Maxmind GeoLite Country database.
20797 - Allow GETINFO fingerprint to return a fingerprint even when
20798 we have not yet built a router descriptor. Fixes bug 3577;
20799 bugfix on 0.2.0.1-alpha.
20800 - Write several files in text mode, on OSes that distinguish text
20801 mode from binary mode (namely, Windows). These files are:
20802 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
20803 that collect those statistics; 'client_keys' and 'hostname' for
20804 hidden services that use authentication; and (in the tor-gencert
20805 utility) newly generated identity and signing keys. Previously,
20806 we wouldn't specify text mode or binary mode, leading to an
20807 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
20808 the DirRecordUsageByCountry option which would have triggered
20809 the assertion failure was added), although this assertion failure
20810 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
20811 - Selectively disable deprecation warnings on OS X because Lion
20812 started deprecating the shipped copy of openssl. Fixes bug 3643.
20813 - When unable to format an address as a string, report its value
20814 as "???" rather than reusing the last formatted address. Bugfix
20818 Changes in version 0.2.3.2-alpha - 2011-07-18
20819 Tor 0.2.3.2-alpha introduces two new experimental features:
20820 microdescriptors and pluggable transports. It also continues cleaning
20821 up a variety of recently introduced features.
20824 - Clients can now use microdescriptors instead of regular descriptors
20825 to build circuits. Microdescriptors are authority-generated
20826 summaries of regular descriptors' contents, designed to change
20827 very rarely (see proposal 158 for details). This feature is
20828 designed to save bandwidth, especially for clients on slow internet
20829 connections. It's off by default for now, since nearly no caches
20830 support it, but it will be on-by-default for clients in a future
20831 version. You can use the UseMicrodescriptors option to turn it on.
20832 - Tor clients using bridges can now be configured to use a separate
20833 'transport' proxy for each bridge. This approach helps to resist
20834 censorship by allowing bridges to use protocol obfuscation
20835 plugins. It implements part of proposal 180. Implements ticket 2841.
20836 - While we're trying to bootstrap, record how many TLS connections
20837 fail in each state, and report which states saw the most failures
20838 in response to any bootstrap failures. This feature may speed up
20839 diagnosis of censorship events. Implements ticket 3116.
20841 o Major bugfixes (on 0.2.3.1-alpha):
20842 - When configuring a large set of nodes in EntryNodes (as with
20843 'EntryNodes {cc}' or 'EntryNodes 1.1.1.1/16'), choose only a
20844 random subset to be guards, and choose them in random
20845 order. Fixes bug 2798.
20846 - Tor could crash when remembering a consensus in a non-used consensus
20847 flavor without having a current consensus set. Fixes bug 3361.
20848 - Comparing an unknown address to a microdescriptor's shortened exit
20849 policy would always give a "rejected" result. Fixes bug 3599.
20850 - Using microdescriptors as a client no longer prevents Tor from
20851 uploading and downloading hidden service descriptors. Fixes
20855 - Allow nameservers with IPv6 address. Resolves bug 2574.
20856 - Accept attempts to include a password authenticator in the
20857 handshake, as supported by SOCKS5. This handles SOCKS clients that
20858 don't know how to omit a password when authenticating. Resolves
20860 - When configuring a large set of nodes in EntryNodes, and there are
20861 enough of them listed as Guard so that we don't need to consider
20862 the non-guard entries, prefer the ones listed with the Guard flag.
20863 - Check for and recover from inconsistency in the microdescriptor
20864 cache. This will make it harder for us to accidentally free a
20865 microdescriptor without removing it from the appropriate data
20866 structures. Fixes issue 3135; issue noted by "wanoskarnet".
20867 - Log SSL state transitions at log level DEBUG, log domain
20868 HANDSHAKE. This can be useful for debugging censorship events.
20869 Implements ticket 3264.
20870 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
20871 implements ticket 3439.
20873 o Minor bugfixes (on 0.2.3.1-alpha):
20874 - Do not free all general-purpose regular descriptors just
20875 because microdescriptor use is enabled. Fixes bug 3113.
20876 - Correctly link libevent_openssl when --enable-static-libevent
20877 is passed to configure. Fixes bug 3118.
20878 - Bridges should not complain during their heartbeat log messages that
20879 they are unlisted in the consensus: that's more or less the point
20880 of being a bridge. Fixes bug 3183.
20881 - Report a SIGNAL event to controllers when acting on a delayed
20882 SIGNAL NEWNYM command. Previously, we would report a SIGNAL
20883 event to the controller if we acted on a SIGNAL NEWNYM command
20884 immediately, and otherwise not report a SIGNAL event for the
20885 command at all. Fixes bug 3349.
20886 - Fix a crash when handling the SIGNAL controller command or
20887 reporting ERR-level status events with bufferevents enabled. Found
20888 by Robert Ransom. Fixes bug 3367.
20889 - Always ship the tor-fw-helper manpage in our release tarballs.
20890 Fixes bug 3389. Reported by Stephen Walker.
20891 - Fix a class of double-mark-for-close bugs when bufferevents
20892 are enabled. Fixes bug 3403.
20893 - Update tor-fw-helper to support libnatpmp-20110618. Fixes bug 3434.
20894 - Add SIGNAL to the list returned by the 'GETINFO events/names'
20895 control-port command. Fixes part of bug 3465.
20896 - Prevent using negative indices during unit test runs when read_all()
20897 fails. Spotted by coverity.
20898 - Fix a rare memory leak when checking the nodelist without it being
20899 present. Found by coverity.
20900 - Only try to download a microdescriptor-flavored consensus from
20901 a directory cache that provides them.
20903 o Minor bugfixes (on 0.2.2.x and earlier):
20904 - Assert that hidden-service-related operations are not performed
20905 using single-hop circuits. Previously, Tor would assert that
20906 client-side streams are not attached to single-hop circuits,
20907 but not that other sensitive operations on the client and service
20908 side are not performed using single-hop circuits. Fixes bug 3332;
20910 - Don't publish a new relay descriptor when we reload our onion key,
20911 unless the onion key has actually changed. Fixes bug 3263 and
20912 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
20913 - Allow GETINFO fingerprint to return a fingerprint even when
20914 we have not yet built a router descriptor. Fixes bug 3577;
20915 bugfix on 0.2.0.1-alpha.
20916 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
20917 on 0.2.2.4-alpha; fixes bug 3427.
20919 o Code simplification and refactoring:
20920 - Use tor_sscanf() in place of scanf() in more places through the
20921 code. This makes us a little more locale-independent, and
20922 should help shut up code-analysis tools that can't tell
20923 a safe sscanf string from a dangerous one.
20924 - Use tt_assert(), not tor_assert(), for checking for test failures.
20925 This makes the unit tests more able to go on in the event that
20927 - Split connection_about_to_close() into separate functions for each
20931 - On Windows, we now define the _WIN32_WINNT macros only if they
20932 are not already defined. This lets the person building Tor decide,
20933 if they want, to require a later version of Windows.
20936 Changes in version 0.2.2.30-rc - 2011-07-07
20937 Tor 0.2.2.30-rc is the first release candidate for the Tor 0.2.2.x
20938 series. It fixes a few smaller bugs, but generally appears stable.
20939 Please test it and let us know whether it is!
20942 - Send a SUCCEEDED stream event to the controller when a reverse
20943 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
20944 discovered by katmagic.
20945 - Always NUL-terminate the sun_path field of a sockaddr_un before
20946 passing it to the kernel. (Not a security issue: kernels are
20947 smart enough to reject bad sockaddr_uns.) Found by Coverity;
20948 CID #428. Bugfix on Tor 0.2.0.3-alpha.
20949 - Don't stack-allocate the list of supplementary GIDs when we're
20950 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
20951 could take up to 256K, which is way too much stack. Found by
20952 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
20953 - Add BUILDTIMEOUT_SET to the list returned by the 'GETINFO
20954 events/names' control-port command. Bugfix on 0.2.2.9-alpha;
20955 fixes part of bug 3465.
20956 - Fix a memory leak when receiving a descriptor for a hidden
20957 service we didn't ask for. Found by Coverity; CID #30. Bugfix
20961 - Update to the July 1 2011 Maxmind GeoLite Country database.
20964 Changes in version 0.2.2.29-beta - 2011-06-20
20965 Tor 0.2.2.29-beta reverts an accidental behavior change for users who
20966 have bridge lines in their torrc but don't want to use them; gets
20967 us closer to having the control socket feature working on Debian;
20968 and fixes a variety of smaller bugs.
20971 - Revert the UseBridges option to its behavior before 0.2.2.28-beta.
20972 When we changed the default behavior to "use bridges if any
20973 are listed in the torrc", we surprised users who had bridges
20974 in their torrc files but who didn't actually want to use them.
20975 Partial resolution for bug 3354.
20978 - Don't attach new streams to old rendezvous circuits after SIGNAL
20979 NEWNYM. Previously, we would keep using an existing rendezvous
20980 circuit if it remained open (i.e. if it were kept open by a
20981 long-lived stream, or if a new stream were attached to it before
20982 Tor could notice that it was old and no longer in use). Bugfix on
20983 0.1.1.15-rc; fixes bug 3375.
20986 - Fix a bug when using ControlSocketsGroupWritable with User. The
20987 directory's group would be checked against the current group, not
20988 the configured group. Patch by Jérémy Bobbio. Fixes bug 3393;
20989 bugfix on 0.2.2.26-beta.
20990 - Make connection_printf_to_buf()'s behavior sane. Its callers
20991 expect it to emit a CRLF iff the format string ends with CRLF;
20992 it actually emitted a CRLF iff (a) the format string ended with
20993 CRLF or (b) the resulting string was over 1023 characters long or
20994 (c) the format string did not end with CRLF *and* the resulting
20995 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
20996 fixes part of bug 3407.
20997 - Make send_control_event_impl()'s behavior sane. Its callers
20998 expect it to always emit a CRLF at the end of the string; it
20999 might have emitted extra control characters as well. Bugfix on
21000 0.1.1.9-alpha; fixes another part of bug 3407.
21001 - Make crypto_rand_int() check the value of its input correctly.
21002 Previously, it accepted values up to UINT_MAX, but could return a
21003 negative number if given a value above INT_MAX+1. Found by George
21004 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
21005 - Avoid a segfault when reading a malformed circuit build state
21006 with more than INT_MAX entries. Found by wanoskarnet. Bugfix on
21008 - When asked about a DNS record type we don't support via a
21009 client DNSPort, reply with NOTIMPL rather than an empty
21010 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
21011 - Fix a rare memory leak during stats writing. Found by coverity.
21014 - Update to the June 1 2011 Maxmind GeoLite Country database.
21016 o Code simplifications and refactoring:
21017 - Remove some dead code as indicated by coverity.
21018 - Remove a few dead assignments during router parsing. Found by
21020 - Add some forgotten return value checks during unit tests. Found
21022 - Don't use 1-bit wide signed bit fields. Found by coverity.
21025 Changes in version 0.2.2.28-beta - 2011-06-04
21026 Tor 0.2.2.28-beta makes great progress towards a new stable release: we
21027 fixed a big bug in whether relays stay in the consensus consistently,
21028 we moved closer to handling bridges and hidden services correctly,
21029 and we started the process of better handling the dreaded "my Vidalia
21030 died, and now my Tor demands a password when I try to reconnect to it"
21034 - Don't decide to make a new descriptor when receiving a HUP signal.
21035 This bug has caused a lot of 0.2.2.x relays to disappear from the
21036 consensus periodically. Fixes the most common case of triggering
21037 bug 1810; bugfix on 0.2.2.7-alpha.
21038 - Actually allow nameservers with IPv6 addresses. Fixes bug 2574.
21039 - Don't try to build descriptors if "ORPort auto" is set and we
21040 don't know our actual ORPort yet. Fix for bug 3216; bugfix on
21042 - Resolve a crash that occurred when setting BridgeRelay to 1 with
21043 accounting enabled. Fixes bug 3228; bugfix on 0.2.2.18-alpha.
21044 - Apply circuit timeouts to opened hidden-service-related circuits
21045 based on the correct start time. Previously, we would apply the
21046 circuit build timeout based on time since the circuit's creation;
21047 it was supposed to be applied based on time since the circuit
21048 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
21049 - Use the same circuit timeout for client-side introduction
21050 circuits as for other four-hop circuits, rather than the timeout
21051 for single-hop directory-fetch circuits; the shorter timeout may
21052 have been appropriate with the static circuit build timeout in
21053 0.2.1.x and earlier, but caused many hidden service access attempts
21054 to fail with the adaptive CBT introduced in 0.2.2.2-alpha. Bugfix
21055 on 0.2.2.2-alpha; fixes another part of bug 1297.
21056 - In ticket 2511 we fixed a case where you could use an unconfigured
21057 bridge if you had configured it as a bridge the last time you ran
21058 Tor. Now fix another edge case: if you had configured it as a bridge
21059 but then switched to a different bridge via the controller, you
21060 would still be willing to use the old one. Bugfix on 0.2.0.1-alpha;
21064 - Add an __OwningControllerProcess configuration option and a
21065 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
21066 that when it exits, Tor will shut down. Implements feature 3049.
21067 - If "UseBridges 1" is set and no bridges are configured, Tor will
21068 now refuse to build any circuits until some bridges are set.
21069 If "UseBridges auto" is set, Tor will use bridges if they are
21070 configured and we are not running as a server, but otherwise will
21071 make circuits as usual. The new default is "auto". Patch by anonym,
21072 so the Tails LiveCD can stop automatically revealing you as a Tor
21076 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
21077 - Remove a trailing asterisk from "exit-policy/default" in the
21078 output of the control port command "GETINFO info/names". Bugfix
21080 - Use a wide type to hold sockets when built for 64-bit Windows builds.
21082 - Warn when the user configures two HiddenServiceDir lines that point
21083 to the same directory. Bugfix on 0.0.6 (the version introducing
21084 HiddenServiceDir); fixes bug 3289.
21085 - Remove dead code from rend_cache_lookup_v2_desc_as_dir. Fixes
21086 part of bug 2748; bugfix on 0.2.0.10-alpha.
21087 - Log malformed requests for rendezvous descriptors as protocol
21088 warnings, not warnings. Also, use a more informative log message
21089 in case someone sees it at log level warning without prior
21090 info-level messages. Fixes the other part of bug 2748; bugfix
21092 - Clear the table recording the time of the last request for each
21093 hidden service descriptor from each HS directory on SIGNAL NEWNYM.
21094 Previously, we would clear our HS descriptor cache on SIGNAL
21095 NEWNYM, but if we had previously retrieved a descriptor (or tried
21096 to) from every directory responsible for it, we would refuse to
21097 fetch it again for up to 15 minutes. Bugfix on 0.2.2.25-alpha;
21099 - Fix a log message that said "bits" while displaying a value in
21100 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
21102 - When checking for 1024-bit keys, check for 1024 bits, not 128
21103 bytes. This allows Tor to correctly discard keys of length 1017
21104 through 1023. Bugfix on 0.0.9pre5.
21107 - Relays now log the reason for publishing a new relay descriptor,
21108 so we have a better chance of hunting down instances of bug 1810.
21109 Resolves ticket 3252.
21110 - Revise most log messages that refer to nodes by nickname to
21111 instead use the "$key=nickname at address" format. This should be
21112 more useful, especially since nicknames are less and less likely
21113 to be unique. Resolves ticket 3045.
21114 - Log (at info level) when purging pieces of hidden-service-client
21115 state because of SIGNAL NEWNYM.
21118 - Remove undocumented option "-F" from tor-resolve: it hasn't done
21119 anything since 0.2.1.16-rc.
21122 Changes in version 0.2.2.27-beta - 2011-05-18
21123 Tor 0.2.2.27-beta fixes a bridge-related stability bug in the previous
21124 release, and also adds a few more general bugfixes.
21127 - Fix a crash bug when changing bridges in a running Tor process.
21128 Fixes bug 3213; bugfix on 0.2.2.26-beta.
21129 - When the controller configures a new bridge, don't wait 10 to 60
21130 seconds before trying to fetch its descriptor. Bugfix on
21131 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
21134 - Require that onion keys have exponent 65537 in microdescriptors too.
21135 Fixes more of bug 3207; bugfix on 0.2.2.26-beta.
21136 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
21137 Changed the limit to 512 characters by removing base64 newlines.
21138 Fixes bug 2752. Fix by Michael Yakubovich.
21139 - When a client starts or stops using bridges, never use a circuit
21140 that was built before the configuration change. This behavior could
21141 put at risk a user who uses bridges to ensure that her traffic
21142 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
21146 Changes in version 0.2.2.26-beta - 2011-05-17
21147 Tor 0.2.2.26-beta fixes a variety of potential privacy problems. It
21148 also introduces a new "socksport auto" approach that should make it
21149 easier to run multiple Tors on the same system, and does a lot of
21150 cleanup to get us closer to a release candidate.
21152 o Security/privacy fixes:
21153 - Replace all potentially sensitive memory comparison operations
21154 with versions whose runtime does not depend on the data being
21155 compared. This will help resist a class of attacks where an
21156 adversary can use variations in timing information to learn
21157 sensitive data. Fix for one case of bug 3122. (Safe memcmp
21158 implementation by Robert Ransom based partially on code by DJB.)
21159 - When receiving a hidden service descriptor, check that it is for
21160 the hidden service we wanted. Previously, Tor would store any
21161 hidden service descriptors that a directory gave it, whether it
21162 wanted them or not. This wouldn't have let an attacker impersonate
21163 a hidden service, but it did let directories pre-seed a client
21164 with descriptors that it didn't want. Bugfix on 0.0.6.
21165 - On SIGHUP, do not clear out all TrackHostExits mappings, client
21166 DNS cache entries, and virtual address mappings: that's what
21167 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
21170 - The options SocksPort, ControlPort, and so on now all accept a
21171 value "auto" that opens a socket on an OS-selected port. A
21172 new ControlPortWriteToFile option tells Tor to write its
21173 actual control port or ports to a chosen file. If the option
21174 ControlPortFileGroupReadable is set, the file is created as
21175 group-readable. Now users can run two Tor clients on the same
21176 system without needing to manually mess with parameters. Resolves
21177 part of ticket 3076.
21178 - Set SO_REUSEADDR on all sockets, not just listeners. This should
21179 help busy exit nodes avoid running out of useable ports just
21180 because all the ports have been used in the near past. Resolves
21184 - New "GETINFO net/listeners/(type)" controller command to return
21185 a list of addresses and ports that are bound for listeners for a
21186 given connection type. This is useful when the user has configured
21187 "SocksPort auto" and the controller needs to know which port got
21188 chosen. Resolves another part of ticket 3076.
21189 - Add a new ControlSocketsGroupWritable configuration option: when
21190 it is turned on, ControlSockets are group-writeable by the default
21191 group of the current user. Patch by Jérémy Bobbio; implements
21193 - Tor now refuses to create a ControlSocket in a directory that is
21194 world-readable (or group-readable if ControlSocketsGroupWritable
21195 is 0). This is necessary because some operating systems do not
21196 enforce permissions on an AF_UNIX sockets. Permissions on the
21197 directory holding the socket, however, seems to work everywhere.
21198 - Rate-limit a warning about failures to download v2 networkstatus
21199 documents. Resolves part of bug 1352.
21200 - Backport code from 0.2.3.x that allows directory authorities to
21201 clean their microdescriptor caches. Needed to resolve bug 2230.
21202 - When an HTTPS proxy reports "403 Forbidden", we now explain
21203 what it means rather than calling it an unexpected status code.
21204 Closes bug 2503. Patch from Michael Yakubovich.
21205 - Update to the May 1 2011 Maxmind GeoLite Country database.
21208 - Authorities now clean their microdesc cache periodically and when
21209 reading from disk initially, not only when adding new descriptors.
21210 This prevents a bug where we could lose microdescriptors. Bugfix
21211 on 0.2.2.6-alpha. Fixes bug 2230.
21212 - Do not crash when our configuration file becomes unreadable, for
21213 example due to a permissions change, between when we start up
21214 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
21216 - Avoid a bug that would keep us from replacing a microdescriptor
21217 cache on Windows. (We would try to replace the file while still
21218 holding it open. That's fine on Unix, but Windows doesn't let us
21219 do that.) Bugfix on 0.2.2.6-alpha; bug found by wanoskarnet.
21220 - Add missing explanations for the authority-related torrc options
21221 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey in the
21222 man page. Resolves issue 2379.
21223 - As an authority, do not upload our own vote or signature set to
21224 ourself. It would tell us nothing new, and as of 0.2.2.24-alpha,
21225 it would get flagged as a duplicate. Resolves bug 3026.
21226 - Accept hidden service descriptors if we think we might be a hidden
21227 service directory, regardless of what our consensus says. This
21228 helps robustness, since clients and hidden services can sometimes
21229 have a more up-to-date view of the network consensus than we do,
21230 and if they think that the directory authorities list us a HSDir,
21231 we might actually be one. Related to bug 2732; bugfix on
21233 - When a controller changes TrackHostExits, remove mappings for
21234 hosts that should no longer have their exits tracked. Bugfix on
21236 - When a controller changes VirtualAddrNetwork, remove any mappings
21237 for hosts that were automapped to the old network. Bugfix on
21239 - When a controller changes one of the AutomapHosts* options, remove
21240 any mappings for hosts that should no longer be automapped. Bugfix
21242 - Do not reset the bridge descriptor download status every time we
21243 re-parse our configuration or get a configuration change. Fixes
21244 bug 3019; bugfix on 0.2.0.3-alpha.
21246 o Minor bugfixes (code cleanup):
21247 - When loading the microdesc journal, remember its current size.
21248 In 0.2.2, this helps prevent the microdesc journal from growing
21249 without limit on authorities (who are the only ones to use it in
21250 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
21251 Fix posted by "cypherpunks."
21252 - The microdesc journal is supposed to get rebuilt only if it is
21253 at least _half_ the length of the store, not _twice_ the length
21254 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
21255 - Fix a potential null-pointer dereference while computing a
21256 consensus. Bugfix on 0.2.0.3-alpha, found with the help of
21258 - Avoid a possible null-pointer dereference when rebuilding the mdesc
21259 cache without actually having any descriptors to cache. Bugfix on
21260 0.2.2.6-alpha. Issue discovered using clang's static analyzer.
21261 - If we fail to compute the identity digest of a v3 legacy keypair,
21262 warn, and don't use a buffer-full of junk instead. Bugfix on
21263 0.2.1.1-alpha; fixes bug 3106.
21264 - Resolve an untriggerable issue in smartlist_string_num_isin(),
21265 where if the function had ever in the future been used to check
21266 for the presence of a too-large number, it would have given an
21267 incorrect result. (Fortunately, we only used it for 16-bit
21268 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
21269 - Require that introduction point keys and onion handshake keys
21270 have a public exponent of 65537. Starts to fix bug 3207; bugfix
21273 o Removed features:
21274 - Caches no longer download and serve v2 networkstatus documents
21275 unless FetchV2Networkstatus flag is set: these documents haven't
21276 haven't been used by clients or relays since 0.2.0.x. Resolves
21280 Changes in version 0.2.3.1-alpha - 2011-05-05
21281 Tor 0.2.3.1-alpha adds some new experimental features, including support
21282 for an improved network IO backend, IOCP networking on Windows,
21283 microdescriptor caching, "fast-start" support for streams, and automatic
21284 home router configuration. There are also numerous internal improvements
21285 to try to make the code easier for developers to work with.
21287 This is the first alpha release in a new series, so expect there to be
21288 bugs. Users who would rather test out a more stable branch should
21289 stay with 0.2.2.x for now.
21292 - Tor can now optionally build with the "bufferevents" buffered IO
21293 backend provided by Libevent 2. To use this feature, make sure you
21294 have the latest possible version of Libevent, and pass the
21295 --enable-bufferevents flag to configure when building Tor from
21296 source. This feature will make our networking code more flexible,
21297 let us stack layers on each other, and let us use more efficient
21298 zero-copy transports where available.
21299 - As an experimental feature, Tor can use IOCP for networking on Windows.
21300 Once this code is tuned and optimized, it promises much better
21301 performance than the select-based backend we've used in the past. To
21302 try this feature, you must build Tor with Libevent 2, configure Tor
21303 with the "bufferevents" buffered IO backend, and add "DisableIOCP 0" to
21304 your torrc. There are known bugs here: only try this if you can help
21305 debug it as it breaks.
21306 - The EntryNodes option can now include country codes like {de} or IP
21307 addresses or network masks. Previously we had disallowed these options
21308 because we didn't have an efficient way to keep the list up to
21309 date. Fixes bug 1982, but see bug 2798 for an unresolved issue here.
21310 - Exit nodes now accept and queue data on not-yet-connected streams.
21311 Previously, the client wasn't allowed to send data until the stream was
21312 connected, which slowed down all connections. This change will enable
21313 clients to perform a "fast-start" on streams and send data without
21314 having to wait for a confirmation that the stream has opened. (Patch
21315 from Ian Goldberg; implements the server side of Proposal 174.)
21316 - Tor now has initial support for automatic port mapping on the many
21317 home routers that support NAT-PMP or UPnP. (Not yet supported on
21318 Windows). To build the support code, you'll need to have libnatpnp
21319 library and/or the libminiupnpc library, and you'll need to enable the
21320 feature specifically by passing "--enable-upnp" and/or
21321 "--enable-natpnp" to configure. To turn it on, use the new
21322 PortForwarding option.
21323 - Caches now download, cache, and serve multiple "flavors" of the
21324 consensus, including a flavor that describes microdescriptors.
21325 - Caches now download, cache, and serve microdescriptors -- small
21326 summaries of router descriptors that are authenticated by all of the
21327 directory authorities. Once enough caches are running this code,
21328 clients will be able to save significant amounts of directory bandwidth
21329 by downloading microdescriptors instead of router descriptors.
21332 - Make logging resolution configurable with a new LogTimeGranularity
21333 option, and change the default from 1 millisecond to 1 second.
21334 Implements enhancement 1668.
21335 - We log which torrc file we're using on startup. Implements ticket
21337 - Ordinarily, Tor does not count traffic from private addresses (like
21338 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
21339 There is now a new option, CountPrivateBandwidth, to disable this
21340 behavior. Patch from Daniel Cagara.
21341 - New --enable-static-tor configure option for building Tor as
21342 statically as possible. Idea, general hackery and thoughts from
21343 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
21345 - If you set the NumCPUs option to 0, Tor will now try to detect how
21346 many CPUs you have. This is the new default behavior.
21347 - Turn on directory request statistics by default and include them in
21348 extra-info descriptors. Don't break if we have no GeoIP database.
21349 - Relays that set "ConnDirectionStatistics 1" write statistics on the
21350 bidirectional use of connections to disk every 24 hours.
21351 - Add a GeoIP file digest to the extra-info descriptor. Implements
21353 - The NodeFamily option -- which let you declare that you want to
21354 consider nodes to be part of a family whether they list themselves
21355 that way or not -- now allows IP address ranges and country codes.
21356 - Add a new 'Heartbeat' log message type to periodically log a message
21357 describing Tor's status at level Notice. This feature is meant for
21358 operators who log at notice, and want to make sure that their Tor
21359 server is still working. Implementation by George Kadianakis.
21361 o Minor bugfixes (on 0.2.2.25-alpha):
21362 - When loading the microdesc journal, remember its current size.
21363 In 0.2.2, this helps prevent the microdesc journal from growing
21364 without limit on authorities (who are the only ones to use it in
21365 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
21366 Fix posted by "cypherpunks."
21367 - The microdesc journal is supposed to get rebuilt only if it is
21368 at least _half_ the length of the store, not _twice_ the length
21369 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
21370 - If as an authority we fail to compute the identity digest of a v3
21371 legacy keypair, warn, and don't use a buffer-full of junk instead.
21372 Bugfix on 0.2.1.1-alpha; fixes bug 3106.
21373 - Authorities now clean their microdesc cache periodically and when
21374 reading from disk initially, not only when adding new descriptors.
21375 This prevents a bug where we could lose microdescriptors. Bugfix
21378 o Minor features (controller):
21379 - Add a new SIGNAL event to the controller interface so that
21380 controllers can be notified when Tor handles a signal. Resolves
21381 issue 1955. Patch by John Brooks.
21382 - Add a new GETINFO option to get total bytes read and written. Patch
21383 from pipe, revised by atagar. Resolves ticket 2345.
21384 - Implement some GETINFO controller fields to provide information about
21385 the Tor process's pid, euid, username, and resource limits.
21388 - Our build system requires automake 1.6 or later to create the
21389 Makefile.in files. Previously, you could have used 1.4.
21390 This only affects developers and people building Tor from git;
21391 people who build Tor from the source distribution without changing
21392 the Makefile.am files should be fine.
21393 - Our autogen.sh script uses autoreconf to launch autoconf, automake, and
21394 so on. This is more robust against some of the failure modes
21395 associated with running the autotools pieces on their own.
21397 o Minor packaging issues:
21398 - On OpenSUSE, create the /var/run/tor directory on startup if it is not
21399 already created. Patch from Andreas Stieger. Fixes bug 2573.
21401 o Code simplifications and refactoring:
21402 - A major revision to our internal node-selecting and listing logic.
21403 Tor already had at least two major ways to look at the question of
21404 "which Tor servers do we know about": a list of router descriptors,
21405 and a list of entries in the current consensus. With
21406 microdescriptors, we're adding a third. Having so many systems
21407 without an abstraction layer over them was hurting the codebase.
21408 Now, we have a new "node_t" abstraction that presents a consistent
21409 interface to a client's view of a Tor node, and holds (nearly) all
21410 of the mutable state formerly in routerinfo_t and routerstatus_t.
21411 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
21412 no longer link against Libevent: they never used it, but
21413 our library structure used to force them to link it.
21415 o Removed features:
21416 - Remove some old code to work around even older versions of Tor that
21417 used forked processes to handle DNS requests. Such versions of Tor
21418 are no longer in use as servers.
21420 o Documentation fixes:
21421 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
21422 - Add missing documentation for the authority-related torrc options
21423 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey. Resolves
21427 Changes in version 0.2.2.25-alpha - 2011-04-29
21428 Tor 0.2.2.25-alpha fixes many bugs: hidden service clients are more
21429 robust, routers no longer overreport their bandwidth, Win7 should crash
21430 a little less, and NEWNYM (as used by Vidalia's "new identity" button)
21431 now prevents hidden service-related activity from being linkable. It
21432 provides more information to Vidalia so you can see if your bridge is
21433 working. Also, 0.2.2.25-alpha revamps the Entry/Exit/ExcludeNodes and
21434 StrictNodes configuration options to make them more reliable, more
21435 understandable, and more regularly applied. If you use those options,
21436 please see the revised documentation for them in the manual page.
21439 - Relays were publishing grossly inflated bandwidth values because
21440 they were writing their state files wrong--now they write the
21441 correct value. Also, resume reading bandwidth history from the
21442 state file correctly. Fixes bug 2704; bugfix on 0.2.2.23-alpha.
21443 - Improve hidden service robustness: When we find that we have
21444 extended a hidden service's introduction circuit to a relay not
21445 listed as an introduction point in the HS descriptor we currently
21446 have, retry with an introduction point from the current
21447 descriptor. Previously we would just give up. Fixes bugs 1024 and
21448 1930; bugfix on 0.2.0.10-alpha.
21449 - Clients now stop trying to use an exit node associated with a given
21450 destination by TrackHostExits if they fail to reach that exit node.
21451 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
21452 - Fix crash bug on platforms where gmtime and localtime can return
21453 NULL. Windows 7 users were running into this one. Fixes part of bug
21454 2077. Bugfix on all versions of Tor. Found by boboper.
21456 o Security and stability fixes:
21457 - Don't double-free a parsable, but invalid, microdescriptor, even if
21458 it is followed in the blob we're parsing by an unparsable
21459 microdescriptor. Fixes an issue reported in a comment on bug 2954.
21460 Bugfix on 0.2.2.6-alpha; fix by "cypherpunks".
21461 - If the Nickname configuration option isn't given, Tor would pick a
21462 nickname based on the local hostname as the nickname for a relay.
21463 Because nicknames are not very important in today's Tor and the
21464 "Unnamed" nickname has been implemented, this is now problematic
21465 behavior: It leaks information about the hostname without being
21466 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
21467 introduced the Unnamed nickname. Reported by tagnaq.
21468 - Fix an uncommon assertion failure when running with DNSPort under
21469 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
21470 - Avoid linkability based on cached hidden service descriptors: forget
21471 all hidden service descriptors cached as a client when processing a
21472 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
21475 - Export GeoIP information on bridge usage to controllers even if we
21476 have not yet been running for 24 hours. Now Vidalia bridge operators
21477 can get more accurate and immediate feedback about their
21478 contributions to the network.
21480 o Major features and bugfixes (node selection):
21481 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
21482 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and StrictNodes
21483 options. Previously, we had been ambiguous in describing what
21484 counted as an "exit" node, and what operations exactly "StrictNodes
21485 0" would permit. This created confusion when people saw nodes built
21486 through unexpected circuits, and made it hard to tell real bugs from
21487 surprises. Now the intended behavior is:
21488 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
21489 a node that delivers user traffic outside the Tor network.
21490 . "Entry", in the context of EntryNodes, means a node used as the
21491 first hop of a multihop circuit. It doesn't include direct
21492 connections to directory servers.
21493 . "ExcludeNodes" applies to all nodes.
21494 . "StrictNodes" changes the behavior of ExcludeNodes only. When
21495 StrictNodes is set, Tor should avoid all nodes listed in
21496 ExcludeNodes, even when it will make user requests fail. When
21497 StrictNodes is *not* set, then Tor should follow ExcludeNodes
21498 whenever it can, except when it must use an excluded node to
21499 perform self-tests, connect to a hidden service, provide a
21500 hidden service, fulfill a .exit request, upload directory
21501 information, or fetch directory information.
21502 Collectively, the changes to implement the behavior fix bug 1090.
21503 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
21504 a node is listed in both, it's treated as excluded.
21505 - ExcludeNodes now applies to directory nodes -- as a preference if
21506 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
21507 Don't exclude all the directory authorities and set StrictNodes to 1
21508 unless you really want your Tor to break.
21509 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
21510 - ExcludeExitNodes now overrides .exit requests.
21511 - We don't use bridges listed in ExcludeNodes.
21512 - When StrictNodes is 1:
21513 . We now apply ExcludeNodes to hidden service introduction points
21514 and to rendezvous points selected by hidden service users. This
21515 can make your hidden service less reliable: use it with caution!
21516 . If we have used ExcludeNodes on ourself, do not try relay
21517 reachability self-tests.
21518 . If we have excluded all the directory authorities, we will not
21519 even try to upload our descriptor if we're a relay.
21520 . Do not honor .exit requests to an excluded node.
21521 - Remove a misfeature that caused us to ignore the Fast/Stable flags
21522 when ExitNodes is set. Bugfix on 0.2.2.7-alpha.
21523 - When the set of permitted nodes changes, we now remove any mappings
21524 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
21526 - We never cannibalize a circuit that had excluded nodes on it, even
21527 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
21528 - Revert a change where we would be laxer about attaching streams to
21529 circuits than when building the circuits. This was meant to prevent
21530 a set of bugs where streams were never attachable, but our improved
21531 code here should make this unnecessary. Bugfix on 0.2.2.7-alpha.
21532 - Keep track of how many times we launch a new circuit to handle a
21533 given stream. Too many launches could indicate an inconsistency
21534 between our "launch a circuit to handle this stream" logic and our
21535 "attach this stream to one of the available circuits" logic.
21536 - Improve log messages related to excluded nodes.
21539 - Fix a spurious warning when moving from a short month to a long
21540 month on relays with month-based BandwidthAccounting. Bugfix on
21541 0.2.2.17-alpha; fixes bug 3020.
21542 - When a client finds that an origin circuit has run out of 16-bit
21543 stream IDs, we now mark it as unusable for new streams. Previously,
21544 we would try to close the entire circuit. Bugfix on 0.0.6.
21545 - Add a forgotten cast that caused a compile warning on OS X 10.6.
21546 Bugfix on 0.2.2.24-alpha.
21547 - Be more careful about reporting the correct error from a failed
21548 connect() system call. Under some circumstances, it was possible to
21549 look at an incorrect value for errno when sending the end reason.
21550 Bugfix on 0.1.0.1-rc.
21551 - Correctly handle an "impossible" overflow cases in connection byte
21552 counting, where we write or read more than 4GB on an edge connection
21553 in a single second. Bugfix on 0.1.2.8-beta.
21554 - Correct the warning displayed when a rendezvous descriptor exceeds
21555 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
21557 - Clients and hidden services now use HSDir-flagged relays for hidden
21558 service descriptor downloads and uploads even if the relays have no
21559 DirPort set and the client has disabled TunnelDirConns. This will
21560 eventually allow us to give the HSDir flag to relays with no
21561 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
21562 - Downgrade "no current certificates known for authority" message from
21563 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
21564 - Make the SIGNAL DUMP control-port command work on FreeBSD. Fixes bug
21565 2917. Bugfix on 0.1.1.1-alpha.
21566 - Only limit the lengths of single HS descriptors, even when multiple
21567 HS descriptors are published to an HSDir relay in a single POST
21568 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
21569 - Write the current time into the LastWritten line in our state file,
21570 rather than the time from the previous write attempt. Also, stop
21571 trying to use a time of -1 in our log statements. Fixes bug 3039;
21572 bugfix on 0.2.2.14-alpha.
21573 - Be more consistent in our treatment of file system paths. "~" should
21574 get expanded to the user's home directory in the Log config option.
21575 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
21576 feature for the -f and --DataDirectory options.
21579 - Make sure every relay writes a state file at least every 12 hours.
21580 Previously, a relay could go for weeks without writing its state
21581 file, and on a crash could lose its bandwidth history, capacity
21582 estimates, client country statistics, and so on. Addresses bug 3012.
21583 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
21584 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
21585 clients are already deprecated because of security bugs.
21586 - Don't allow v0 hidden service authorities to act as clients.
21587 Required by fix for bug 3000.
21588 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
21589 by fix for bug 3000.
21590 - Ensure that no empty [dirreq-](read|write)-history lines are added
21591 to an extrainfo document. Implements ticket 2497.
21593 o Code simplification and refactoring:
21594 - Remove workaround code to handle directory responses from servers
21595 that had bug 539 (they would send HTTP status 503 responses _and_
21596 send a body too). Since only server versions before
21597 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
21598 keep the workaround in place.
21599 - Remove the old 'fuzzy time' logic. It was supposed to be used for
21600 handling calculations where we have a known amount of clock skew and
21601 an allowed amount of unknown skew. But we only used it in three
21602 places, and we never adjusted the known/unknown skew values. This is
21603 still something we might want to do someday, but if we do, we'll
21604 want to do it differently.
21605 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
21606 None of the cases where we did this before were wrong, but by making
21607 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
21608 - Use GetTempDir to find the proper temporary directory location on
21609 Windows when generating temporary files for the unit tests. Patch by
21613 Changes in version 0.2.2.24-alpha - 2011-04-08
21614 Tor 0.2.2.24-alpha fixes a variety of bugs, including a big bug that
21615 prevented Tor clients from effectively using "multihomed" bridges,
21616 that is, bridges that listen on multiple ports or IP addresses so users
21617 can continue to use some of their addresses even if others get blocked.
21620 - Fix a bug where bridge users who configure the non-canonical
21621 address of a bridge automatically switch to its canonical
21622 address. If a bridge listens at more than one address, it should be
21623 able to advertise those addresses independently and any non-blocked
21624 addresses should continue to work. Bugfix on Tor 0.2.0.x. Fixes
21626 - If you configured Tor to use bridge A, and then quit and
21627 configured Tor to use bridge B instead, it would happily continue
21628 to use bridge A if it's still reachable. While this behavior is
21629 a feature if your goal is connectivity, in some scenarios it's a
21630 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
21631 - Directory authorities now use data collected from their own
21632 uptime observations when choosing whether to assign the HSDir flag
21633 to relays, instead of trusting the uptime value the relay reports in
21634 its descriptor. This change helps prevent an attack where a small
21635 set of nodes with frequently-changing identity keys can blackhole
21636 a hidden service. (Only authorities need upgrade; others will be
21637 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
21640 - When we restart our relay, we might get a successful connection
21641 from the outside before we've started our reachability tests,
21642 triggering a warning: "ORPort found reachable, but I have no
21643 routerinfo yet. Failing to inform controller of success." This
21644 bug was harmless unless Tor is running under a controller
21645 like Vidalia, in which case the controller would never get a
21646 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
21648 - Make directory authorities more accurate at recording when
21649 relays that have failed several reachability tests became
21650 unreachable, so we can provide more accuracy at assigning Stable,
21651 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
21652 - Fix an issue that prevented static linking of libevent on
21653 some platforms (notably Linux). Fixes bug 2698; bugfix on
21654 versions 0.2.1.23/0.2.2.8-alpha (the versions introducing
21655 the --with-static-libevent configure option).
21656 - We now ask the other side of a stream (the client or the exit)
21657 for more data on that stream when the amount of queued data on
21658 that stream dips low enough. Previously, we wouldn't ask the
21659 other side for more data until either it sent us more data (which
21660 it wasn't supposed to do if it had exhausted its window!) or we
21661 had completely flushed all our queued data. This flow control fix
21662 should improve throughput. Fixes bug 2756; bugfix on the earliest
21663 released versions of Tor (svn commit r152).
21664 - Avoid a double-mark-for-free warning when failing to attach a
21665 transparent proxy connection. (We thought we had fixed this in
21666 0.2.2.23-alpha, but it turns out our fix was checking the wrong
21667 connection.) Fixes bug 2757; bugfix on 0.1.2.1-alpha (the original
21668 bug) and 0.2.2.23-alpha (the incorrect fix).
21669 - When warning about missing zlib development packages during compile,
21670 give the correct package names. Bugfix on 0.2.0.1-alpha.
21673 - Directory authorities now log the source of a rejected POSTed v3
21674 networkstatus vote.
21675 - Make compilation with clang possible when using
21676 --enable-gcc-warnings by removing two warning options that clang
21677 hasn't implemented yet and by fixing a few warnings. Implements
21679 - When expiring circuits, use microsecond timers rather than
21680 one-second timers. This can avoid an unpleasant situation where a
21681 circuit is launched near the end of one second and expired right
21682 near the beginning of the next, and prevent fluctuations in circuit
21684 - Use computed circuit-build timeouts to decide when to launch
21685 parallel introduction circuits for hidden services. (Previously,
21686 we would retry after 15 seconds.)
21687 - Update to the April 1 2011 Maxmind GeoLite Country database.
21690 - Create the /var/run/tor directory on startup on OpenSUSE if it is
21691 not already created. Patch from Andreas Stieger. Fixes bug 2573.
21693 o Documentation changes:
21694 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
21695 - Resolve all doxygen warnings except those for missing documentation.
21697 - Add doxygen documentation for more functions, fields, and types.
21700 Changes in version 0.2.2.23-alpha - 2011-03-08
21701 Tor 0.2.2.23-alpha lets relays record their bandwidth history so when
21702 they restart they don't lose their bandwidth capacity estimate. This
21703 release also fixes a diverse set of user-facing bugs, ranging from
21704 relays overrunning their rate limiting to clients falsely warning about
21705 clock skew to bridge descriptor leaks by our bridge directory authority.
21708 - Stop sending a CLOCK_SKEW controller status event whenever
21709 we fetch directory information from a relay that has a wrong clock.
21710 Instead, only inform the controller when it's a trusted authority
21711 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
21712 the rest of bug 1074.
21713 - Fix an assert in parsing router descriptors containing IPv6
21714 addresses. This one took down the directory authorities when
21715 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
21716 - Make the bridge directory authority refuse to answer directory
21717 requests for "all" descriptors. It used to include bridge
21718 descriptors in its answer, which was a major information leak.
21719 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
21720 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
21721 Tor would ignore their RelayBandwidthBurst setting,
21722 potentially using more bandwidth than expected. Bugfix on
21723 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
21724 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
21725 hidserv" in her torrc. The 'hidserv' argument never controlled
21726 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
21729 - Relays now save observed peak bandwidth throughput rates to their
21730 state file (along with total usage, which was already saved)
21731 so that they can determine their correct estimated bandwidth on
21732 restart. Resolves bug 1863, where Tor relays would reset their
21733 estimated bandwidth to 0 after restarting.
21734 - Directory authorities now take changes in router IP address and
21735 ORPort into account when determining router stability. Previously,
21736 if a router changed its IP or ORPort, the authorities would not
21737 treat it as having any downtime for the purposes of stability
21738 calculation, whereas clients would experience downtime since the
21739 change could take a while to propagate to them. Resolves issue 1035.
21740 - Enable Address Space Layout Randomization (ASLR) and Data Execution
21741 Prevention (DEP) by default on Windows to make it harder for
21742 attackers to exploit vulnerabilities. Patch from John Brooks.
21744 o Minor bugfixes (on 0.2.1.x and earlier):
21745 - Fix a rare crash bug that could occur when a client was configured
21746 with a large number of bridges. Fixes bug 2629; bugfix on
21747 0.2.1.2-alpha. Bugfix by trac user "shitlei".
21748 - Avoid a double mark-for-free warning when failing to attach a
21749 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
21751 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
21752 found by "cypherpunks". This bug was introduced before the first
21753 Tor release, in svn commit r110.
21754 - Country codes aren't supported in EntryNodes until 0.2.3.x, so
21755 don't mention them in the manpage. Fixes bug 2450; issue
21756 spotted by keb and G-Lo.
21757 - Fix a bug in bandwidth history state parsing that could have been
21758 triggered if a future version of Tor ever changed the timing
21759 granularity at which bandwidth history is measured. Bugfix on
21760 Tor 0.1.1.11-alpha.
21761 - When a relay decides that its DNS is too broken for it to serve
21762 as an exit server, it advertised itself as a non-exit, but
21763 continued to act as an exit. This could create accidental
21764 partitioning opportunities for users. Instead, if a relay is
21765 going to advertise reject *:* as its exit policy, it should
21766 really act with exit policy "reject *:*". Fixes bug 2366.
21767 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
21768 - In the special case where you configure a public exit relay as your
21769 bridge, Tor would be willing to use that exit relay as the last
21770 hop in your circuit as well. Now we fail that circuit instead.
21771 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
21772 - Fix a bug with our locking implementation on Windows that couldn't
21773 correctly detect when a file was already locked. Fixes bug 2504,
21774 bugfix on 0.2.1.6-alpha.
21775 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
21776 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
21778 - Set target port in get_interface_address6() correctly. Bugfix
21779 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
21780 - Directory authorities are now more robust to hops back in time
21781 when calculating router stability. Previously, if a run of uptime
21782 or downtime appeared to be negative, the calculation could give
21783 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
21785 - Fix an assert that got triggered when using the TestingTorNetwork
21786 configuration option and then issuing a GETINFO config-text control
21787 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
21789 o Minor bugfixes (on 0.2.2.x):
21790 - Clients should not weight BadExit nodes as Exits in their node
21791 selection. Similarly, directory authorities should not count BadExit
21792 bandwidth as Exit bandwidth when computing bandwidth-weights.
21793 Bugfix on 0.2.2.10-alpha; fixes bug 2203.
21794 - Correctly clear our dir_read/dir_write history when there is an
21795 error parsing any bw history value from the state file. Bugfix on
21796 Tor 0.2.2.15-alpha.
21797 - Resolve a bug in verifying signatures of directory objects
21798 with digests longer than SHA1. Bugfix on 0.2.2.20-alpha.
21799 Fixes bug 2409. Found by "piebeer".
21800 - Bridge authorities no longer crash on SIGHUP when they try to
21801 publish their relay descriptor to themselves. Fixes bug 2572. Bugfix
21805 - Log less aggressively about circuit timeout changes, and improve
21806 some other circuit timeout messages. Resolves bug 2004.
21807 - Log a little more clearly about the times at which we're no longer
21808 accepting new connections. Resolves bug 2181.
21809 - Reject attempts at the client side to open connections to private
21810 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
21811 a randomly chosen exit node. Attempts to do so are always
21812 ill-defined, generally prevented by exit policies, and usually
21813 in error. This will also help to detect loops in transparent
21814 proxy configurations. You can disable this feature by setting
21815 "ClientRejectInternalAddresses 0" in your torrc.
21816 - Always treat failure to allocate an RSA key as an unrecoverable
21818 - Update to the March 1 2011 Maxmind GeoLite Country database.
21820 o Minor features (log subsystem):
21821 - Add documentation for configuring logging at different severities in
21822 different log domains. We've had this feature since 0.2.1.1-alpha,
21823 but for some reason it never made it into the manpage. Fixes
21825 - Make it simpler to specify "All log domains except for A and B".
21826 Previously you needed to say "[*,~A,~B]". Now you can just say
21828 - Add a "LogMessageDomains 1" option to include the domains of log
21829 messages along with the messages. Without this, there's no way
21830 to use log domains without reading the source or doing a lot
21833 o Packaging changes:
21834 - Stop shipping the Tor specs files and development proposal documents
21835 in the tarball. They are now in a separate git repository at
21836 git://git.torproject.org/torspec.git
21839 Changes in version 0.2.1.30 - 2011-02-23
21840 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
21841 change is a slight tweak to Tor's TLS handshake that makes relays
21842 and bridges that run this new version reachable from Iran again.
21843 We don't expect this tweak will win the arms race long-term, but it
21844 buys us time until we roll out a better solution.
21847 - Stop sending a CLOCK_SKEW controller status event whenever
21848 we fetch directory information from a relay that has a wrong clock.
21849 Instead, only inform the controller when it's a trusted authority
21850 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
21851 the rest of bug 1074.
21852 - Fix a bounds-checking error that could allow an attacker to
21853 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
21854 Found by "piebeer".
21855 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
21856 Tor would ignore their RelayBandwidthBurst setting,
21857 potentially using more bandwidth than expected. Bugfix on
21858 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
21859 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
21860 hidserv" in her torrc. The 'hidserv' argument never controlled
21861 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
21864 - Adjust our TLS Diffie-Hellman parameters to match those used by
21866 - Update to the February 1 2011 Maxmind GeoLite Country database.
21869 - Check for and reject overly long directory certificates and
21870 directory tokens before they have a chance to hit any assertions.
21871 Bugfix on 0.2.1.28. Found by "doorss".
21872 - Bring the logic that gathers routerinfos and assesses the
21873 acceptability of circuits into line. This prevents a Tor OP from
21874 getting locked in a cycle of choosing its local OR as an exit for a
21875 path (due to a .exit request) and then rejecting the circuit because
21876 its OR is not listed yet. It also prevents Tor clients from using an
21877 OR running in the same instance as an exit (due to a .exit request)
21878 if the OR does not meet the same requirements expected of an OR
21879 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
21881 o Packaging changes:
21882 - Stop shipping the Tor specs files and development proposal documents
21883 in the tarball. They are now in a separate git repository at
21884 git://git.torproject.org/torspec.git
21885 - Do not include Git version tags as though they are SVN tags when
21886 generating a tarball from inside a repository that has switched
21887 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
21890 Changes in version 0.2.2.22-alpha - 2011-01-25
21891 Tor 0.2.2.22-alpha fixes a few more less-critical security issues. The
21892 main other change is a slight tweak to Tor's TLS handshake that makes
21893 relays and bridges that run this new version reachable from Iran again.
21894 We don't expect this tweak will win the arms race long-term, but it
21895 will buy us a bit more time until we roll out a better solution.
21898 - Fix a bounds-checking error that could allow an attacker to
21899 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
21900 Found by "piebeer".
21901 - Don't assert when changing from bridge to relay or vice versa
21902 via the controller. The assert happened because we didn't properly
21903 initialize our keys in this case. Bugfix on 0.2.2.18-alpha; fixes
21904 bug 2433. Reported by bastik.
21907 - Adjust our TLS Diffie-Hellman parameters to match those used by
21909 - Provide a log message stating which geoip file we're parsing
21910 instead of just stating that we're parsing the geoip file.
21911 Implements ticket 2432.
21914 - Check for and reject overly long directory certificates and
21915 directory tokens before they have a chance to hit any assertions.
21916 Bugfix on 0.2.1.28 / 0.2.2.20-alpha. Found by "doorss".
21919 Changes in version 0.2.2.21-alpha - 2011-01-15
21920 Tor 0.2.2.21-alpha includes all the patches from Tor 0.2.1.29, which
21921 continues our recent code security audit work. The main fix resolves
21922 a remote heap overflow vulnerability that can allow remote code
21923 execution (CVE-2011-0427). Other fixes address a variety of assert
21924 and crash bugs, most of which we think are hard to exploit remotely.
21926 o Major bugfixes (security), also included in 0.2.1.29:
21927 - Fix a heap overflow bug where an adversary could cause heap
21928 corruption. This bug probably allows remote code execution
21929 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
21931 - Prevent a denial-of-service attack by disallowing any
21932 zlib-compressed data whose compression factor is implausibly
21933 high. Fixes part of bug 2324; reported by "doorss".
21934 - Zero out a few more keys in memory before freeing them. Fixes
21935 bug 2384 and part of bug 2385. These key instances found by
21936 "cypherpunks", based on Andrew Case's report about being able
21937 to find sensitive data in Tor's memory space if you have enough
21938 permissions. Bugfix on 0.0.2pre9.
21940 o Major bugfixes (crashes), also included in 0.2.1.29:
21941 - Prevent calls to Libevent from inside Libevent log handlers.
21942 This had potential to cause a nasty set of crashes, especially
21943 if running Libevent with debug logging enabled, and running
21944 Tor with a controller watching for low-severity log messages.
21945 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
21946 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
21947 underflow errors there too. Fixes the other part of bug 2324.
21948 - Fix a bug where we would assert if we ever had a
21949 cached-descriptors.new file (or another file read directly into
21950 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
21951 on 0.2.1.25. Found by doorss.
21952 - Fix some potential asserts and parsing issues with grossly
21953 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
21956 o Minor bugfixes (other), also included in 0.2.1.29:
21957 - Fix a bug with handling misformed replies to reverse DNS lookup
21958 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
21959 bug reported by doorss.
21960 - Fix compilation on mingw when a pthreads compatibility library
21961 has been installed. (We don't want to use it, so we shouldn't
21962 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
21963 - Fix a bug where we would declare that we had run out of virtual
21964 addresses when the address space was only half-exhausted. Bugfix
21966 - Correctly handle the case where AutomapHostsOnResolve is set but
21967 no virtual addresses are available. Fixes bug 2328; bugfix on
21968 0.1.2.1-alpha. Bug found by doorss.
21969 - Correctly handle wrapping around when we run out of virtual
21970 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
21972 o Minor features, also included in 0.2.1.29:
21973 - Update to the January 1 2011 Maxmind GeoLite Country database.
21974 - Introduce output size checks on all of our decryption functions.
21976 o Build changes, also included in 0.2.1.29:
21977 - Tor does not build packages correctly with Automake 1.6 and earlier;
21978 added a check to Makefile.am to make sure that we're building with
21979 Automake 1.7 or later.
21980 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
21981 because we built it with a too-old version of automake. Thus that
21982 release broke ./configure --enable-openbsd-malloc, which is popular
21983 among really fast exit relays on Linux.
21985 o Major bugfixes, new in 0.2.2.21-alpha:
21986 - Prevent crash/heap corruption when the cbtnummodes consensus
21987 parameter is set to 0 or large values. Fixes bug 2317; bugfix
21990 o Major features, new in 0.2.2.21-alpha:
21991 - Introduce minimum/maximum values that clients will believe
21992 from the consensus. Now we'll have a better chance to avoid crashes
21993 or worse when a consensus param has a weird value.
21995 o Minor features, new in 0.2.2.21-alpha:
21996 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
21997 used on bridges, and it makes bridge scanning somewhat easier.
21998 - If writing the state file to disk fails, wait up to an hour before
21999 retrying again, rather than trying again each second. Fixes bug
22000 2346; bugfix on Tor 0.1.1.3-alpha.
22001 - Make Libevent log messages get delivered to controllers later,
22002 and not from inside the Libevent log handler. This prevents unsafe
22003 reentrant Libevent calls while still letting the log messages
22005 - Detect platforms that brokenly use a signed size_t, and refuse to
22006 build there. Found and analyzed by doorss and rransom.
22007 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
22010 o Minor bugfixes, new in 0.2.2.21-alpha:
22011 - Handle SOCKS messages longer than 128 bytes long correctly, rather
22012 than waiting forever for them to finish. Fixes bug 2330; bugfix
22013 on 0.2.0.16-alpha. Found by doorss.
22014 - Add assertions to check for overflow in arguments to
22015 base32_encode() and base32_decode(); fix a signed-unsigned
22016 comparison there too. These bugs are not actually reachable in Tor,
22017 but it's good to prevent future errors too. Found by doorss.
22018 - Correctly detect failures to create DNS requests when using Libevent
22019 versions before v2. (Before Libevent 2, we used our own evdns
22020 implementation. Its return values for Libevent's evdns_resolve_*()
22021 functions are not consistent with those from Libevent.) Fixes bug
22022 2363; bugfix on 0.2.2.6-alpha. Found by "lodger".
22024 o Documentation, new in 0.2.2.21-alpha:
22025 - Document the default socks host and port (127.0.0.1:9050) for
22029 Changes in version 0.2.1.29 - 2011-01-15
22030 Tor 0.2.1.29 continues our recent code security audit work. The main
22031 fix resolves a remote heap overflow vulnerability that can allow remote
22032 code execution. Other fixes address a variety of assert and crash bugs,
22033 most of which we think are hard to exploit remotely.
22035 o Major bugfixes (security):
22036 - Fix a heap overflow bug where an adversary could cause heap
22037 corruption. This bug probably allows remote code execution
22038 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
22040 - Prevent a denial-of-service attack by disallowing any
22041 zlib-compressed data whose compression factor is implausibly
22042 high. Fixes part of bug 2324; reported by "doorss".
22043 - Zero out a few more keys in memory before freeing them. Fixes
22044 bug 2384 and part of bug 2385. These key instances found by
22045 "cypherpunks", based on Andrew Case's report about being able
22046 to find sensitive data in Tor's memory space if you have enough
22047 permissions. Bugfix on 0.0.2pre9.
22049 o Major bugfixes (crashes):
22050 - Prevent calls to Libevent from inside Libevent log handlers.
22051 This had potential to cause a nasty set of crashes, especially
22052 if running Libevent with debug logging enabled, and running
22053 Tor with a controller watching for low-severity log messages.
22054 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
22055 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
22056 underflow errors there too. Fixes the other part of bug 2324.
22057 - Fix a bug where we would assert if we ever had a
22058 cached-descriptors.new file (or another file read directly into
22059 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
22060 on 0.2.1.25. Found by doorss.
22061 - Fix some potential asserts and parsing issues with grossly
22062 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
22065 o Minor bugfixes (other):
22066 - Fix a bug with handling misformed replies to reverse DNS lookup
22067 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
22068 bug reported by doorss.
22069 - Fix compilation on mingw when a pthreads compatibility library
22070 has been installed. (We don't want to use it, so we shouldn't
22071 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
22072 - Fix a bug where we would declare that we had run out of virtual
22073 addresses when the address space was only half-exhausted. Bugfix
22075 - Correctly handle the case where AutomapHostsOnResolve is set but
22076 no virtual addresses are available. Fixes bug 2328; bugfix on
22077 0.1.2.1-alpha. Bug found by doorss.
22078 - Correctly handle wrapping around to when we run out of virtual
22079 address space. Found by cypherpunks, bugfix on 0.2.0.5-alpha.
22080 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
22081 because we built it with a too-old version of automake. Thus that
22082 release broke ./configure --enable-openbsd-malloc, which is popular
22083 among really fast exit relays on Linux.
22086 - Update to the January 1 2011 Maxmind GeoLite Country database.
22087 - Introduce output size checks on all of our decryption functions.
22090 - Tor does not build packages correctly with Automake 1.6 and earlier;
22091 added a check to Makefile.am to make sure that we're building with
22092 Automake 1.7 or later.
22095 Changes in version 0.2.2.20-alpha - 2010-12-17
22096 Tor 0.2.2.20-alpha does some code cleanup to reduce the risk of remotely
22097 exploitable bugs. We also fix a variety of other significant bugs,
22098 change the IP address for one of our directory authorities, and update
22099 the minimum version that Tor relays must run to join the network.
22102 - Fix a remotely exploitable bug that could be used to crash instances
22103 of Tor remotely by overflowing on the heap. Remote-code execution
22104 hasn't been confirmed, but can't be ruled out. Everyone should
22105 upgrade. Bugfix on the 0.1.1 series and later.
22106 - Fix a bug that could break accounting on 64-bit systems with large
22107 time_t values, making them hibernate for impossibly long intervals.
22108 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
22109 - Fix a logic error in directory_fetches_from_authorities() that
22110 would cause all _non_-exits refusing single-hop-like circuits
22111 to fetch from authorities, when we wanted to have _exits_ fetch
22112 from authorities. Fixes more of 2097. Bugfix on 0.2.2.16-alpha;
22114 - Fix a stream fairness bug that would cause newer streams on a given
22115 circuit to get preference when reading bytes from the origin or
22116 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
22117 introduced before the first Tor release, in svn revision r152.
22119 o Directory authority changes:
22120 - Change IP address and ports for gabelmoo (v3 directory authority).
22123 - Avoid crashes when AccountingMax is set on clients. Fixes bug 2235.
22124 Bugfix on 0.2.2.18-alpha. Diagnosed by boboper.
22125 - Fix an off-by-one error in calculating some controller command
22126 argument lengths. Fortunately, this mistake is harmless since
22127 the controller code does redundant NUL termination too. Found by
22128 boboper. Bugfix on 0.1.1.1-alpha.
22129 - Do not dereference NULL if a bridge fails to build its
22130 extra-info descriptor. Found by an anonymous commenter on
22131 Trac. Bugfix on 0.2.2.19-alpha.
22134 - Update to the December 1 2010 Maxmind GeoLite Country database.
22135 - Directory authorities now reject relays running any versions of
22136 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
22137 known bugs that keep RELAY_EARLY cells from working on rendezvous
22138 circuits. Followup to fix for bug 2081.
22139 - Directory authorities now reject relays running any version of Tor
22140 older than 0.2.0.26-rc. That version is the earliest that fetches
22141 current directory information correctly. Fixes bug 2156.
22142 - Report only the top 10 ports in exit-port stats in order not to
22143 exceed the maximum extra-info descriptor length of 50 KB. Implements
22147 Changes in version 0.2.1.28 - 2010-12-17
22148 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
22149 exploitable bugs. We also took this opportunity to change the IP address
22150 for one of our directory authorities, and to update the geoip database
22154 - Fix a remotely exploitable bug that could be used to crash instances
22155 of Tor remotely by overflowing on the heap. Remote-code execution
22156 hasn't been confirmed, but can't be ruled out. Everyone should
22157 upgrade. Bugfix on the 0.1.1 series and later.
22159 o Directory authority changes:
22160 - Change IP address and ports for gabelmoo (v3 directory authority).
22163 - Update to the December 1 2010 Maxmind GeoLite Country database.
22166 Changes in version 0.2.1.27 - 2010-11-23
22167 Yet another OpenSSL security patch broke its compatibility with Tor:
22168 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
22169 also took this opportunity to fix several crash bugs, integrate a new
22170 directory authority, and update the bundled GeoIP database.
22173 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
22174 No longer set the tlsext_host_name extension on server SSL objects;
22175 but continue to set it on client SSL objects. Our goal in setting
22176 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
22177 bugfix on 0.2.1.1-alpha.
22178 - Do not log messages to the controller while shrinking buffer
22179 freelists. Doing so would sometimes make the controller connection
22180 try to allocate a buffer chunk, which would mess up the internals
22181 of the freelist and cause an assertion failure. Fixes bug 1125;
22182 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
22183 - Learn our external IP address when we're a relay or bridge, even if
22184 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
22185 where we introduced bridge relays that don't need to publish to
22186 be useful. Fixes bug 2050.
22187 - Do even more to reject (and not just ignore) annotations on
22188 router descriptors received anywhere but from the cache. Previously
22189 we would ignore such annotations at first, but cache them to disk
22190 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
22191 - When you're using bridges and your network goes away and your
22192 bridges get marked as down, recover when you attempt a new socks
22193 connection (if the network is back), rather than waiting up to an
22194 hour to try fetching new descriptors for your bridges. Bugfix on
22195 0.2.0.3-alpha; fixes bug 1981.
22198 - Move to the November 2010 Maxmind GeoLite country db (rather
22199 than the June 2009 ip-to-country GeoIP db) for our statistics that
22200 count how many users relays are seeing from each country. Now we'll
22201 have more accurate data, especially for many African countries.
22203 o New directory authorities:
22204 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
22208 - Fix an assertion failure that could occur in directory caches or
22209 bridge users when using a very short voting interval on a testing
22210 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
22212 - Enforce multiplicity rules when parsing annotations. Bugfix on
22213 0.2.0.8-alpha. Found by piebeer.
22214 - Allow handshaking OR connections to take a full KeepalivePeriod
22215 seconds to handshake. Previously, we would close them after
22216 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
22217 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
22219 - When building with --enable-gcc-warnings on OpenBSD, disable
22220 warnings in system headers. This makes --enable-gcc-warnings
22221 pass on OpenBSD 4.8.
22224 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
22225 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
22226 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
22227 Servers can start sending this code when enough clients recognize
22228 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
22229 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
22230 Patch from mingw-san.
22233 - Remove the old debian/ directory from the main Tor distribution.
22234 The official Tor-for-debian git repository lives at the URL
22235 https://git.torproject.org/debian/tor.git
22236 - Stop shipping the old doc/website/ directory in the tarball. We
22237 changed the website format in late 2010, and what we shipped in
22238 0.2.1.26 really wasn't that useful anyway.
22241 Changes in version 0.2.2.19-alpha - 2010-11-22
22242 Yet another OpenSSL security patch broke its compatibility with Tor:
22243 Tor 0.2.2.19-alpha makes relays work with OpenSSL 0.9.8p and 1.0.0.b.
22246 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
22247 No longer set the tlsext_host_name extension on server SSL objects;
22248 but continue to set it on client SSL objects. Our goal in setting
22249 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
22250 bugfix on 0.2.1.1-alpha.
22253 - Try harder not to exceed the maximum length of 50 KB when writing
22254 statistics to extra-info descriptors. This bug was triggered by very
22255 fast relays reporting exit-port, entry, and dirreq statistics.
22256 Reported by Olaf Selke. Bugfix on 0.2.2.1-alpha. Fixes bug 2183.
22257 - Publish a router descriptor even if generating an extra-info
22258 descriptor fails. Previously we would not publish a router
22259 descriptor without an extra-info descriptor; this can cause fast
22260 exit relays collecting exit-port statistics to drop from the
22261 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
22264 Changes in version 0.2.2.18-alpha - 2010-11-16
22265 Tor 0.2.2.18-alpha fixes several crash bugs that have been nagging
22266 us lately, makes unpublished bridge relays able to detect their IP
22267 address, and fixes a wide variety of other bugs to get us much closer
22268 to a stable release.
22271 - Do even more to reject (and not just ignore) annotations on
22272 router descriptors received anywhere but from the cache. Previously
22273 we would ignore such annotations at first, but cache them to disk
22274 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
22275 - Do not log messages to the controller while shrinking buffer
22276 freelists. Doing so would sometimes make the controller connection
22277 try to allocate a buffer chunk, which would mess up the internals
22278 of the freelist and cause an assertion failure. Fixes bug 1125;
22279 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
22280 - Learn our external IP address when we're a relay or bridge, even if
22281 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
22282 where we introduced bridge relays that don't need to publish to
22283 be useful. Fixes bug 2050.
22284 - Maintain separate TLS contexts and certificates for incoming and
22285 outgoing connections in bridge relays. Previously we would use the
22286 same TLS contexts and certs for incoming and outgoing connections.
22287 Bugfix on 0.2.0.3-alpha; addresses bug 988.
22288 - Maintain separate identity keys for incoming and outgoing TLS
22289 contexts in bridge relays. Previously we would use the same
22290 identity keys for incoming and outgoing TLS contexts. Bugfix on
22291 0.2.0.3-alpha; addresses the other half of bug 988.
22292 - Avoid an assertion failure when we as an authority receive a
22293 duplicate upload of a router descriptor that we already have,
22294 but which we previously considered an obsolete descriptor.
22295 Fixes another case of bug 1776. Bugfix on 0.2.2.16-alpha.
22296 - Avoid a crash bug triggered by looking at a dangling pointer while
22297 setting the network status consensus. Found by Robert Ransom.
22298 Bugfix on 0.2.2.17-alpha. Fixes bug 2097.
22299 - Fix a logic error where servers that _didn't_ act as exits would
22300 try to keep their server lists more aggressively up to date than
22301 exits, when it was supposed to be the other way around. Bugfix
22304 o Minor bugfixes (on Tor 0.2.1.x and earlier):
22305 - When we're trying to guess whether we know our IP address as
22306 a relay, we would log various ways that we failed to guess
22307 our address, but never log that we ended up guessing it
22308 successfully. Now add a log line to help confused and anxious
22309 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
22310 - Bring the logic that gathers routerinfos and assesses the
22311 acceptability of circuits into line. This prevents a Tor OP from
22312 getting locked in a cycle of choosing its local OR as an exit for a
22313 path (due to a .exit request) and then rejecting the circuit because
22314 its OR is not listed yet. It also prevents Tor clients from using an
22315 OR running in the same instance as an exit (due to a .exit request)
22316 if the OR does not meet the same requirements expected of an OR
22317 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
22318 - Correctly describe errors that occur when generating a TLS object.
22319 Previously we would attribute them to a failure while generating a
22320 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
22322 - Enforce multiplicity rules when parsing annotations. Bugfix on
22323 0.2.0.8-alpha. Found by piebeer.
22324 - Fix warnings that newer versions of autoconf produced during
22325 ./autogen.sh. These warnings appear to be harmless in our case,
22326 but they were extremely verbose. Fixes bug 2020.
22328 o Minor bugfixes (on Tor 0.2.2.x):
22329 - Enable protection of small arrays whenever we build with gcc
22330 hardening features, not only when also building with warnings
22331 enabled. Fixes bug 2031; bugfix on 0.2.2.14-alpha. Reported by keb.
22334 - Make hidden services work better in private Tor networks by not
22335 requiring any uptime to join the hidden service descriptor
22336 DHT. Implements ticket 2088.
22337 - Rate-limit the "your application is giving Tor only an IP address"
22338 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
22339 - When AllowSingleHopExits is set, print a warning to explain to the
22340 relay operator why most clients are avoiding her relay.
22341 - Update to the November 1 2010 Maxmind GeoLite Country database.
22343 o Code simplifications and refactoring:
22344 - When we fixed bug 1038 we had to put in a restriction not to send
22345 RELAY_EARLY cells on rend circuits. This was necessary as long
22346 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
22347 active. Now remove this obsolete check. Resolves bug 2081.
22348 - Some options used different conventions for uppercasing of acronyms
22349 when comparing manpage and source. Fix those in favor of the
22350 manpage, as it makes sense to capitalize acronyms.
22351 - Remove the torrc.complete file. It hasn't been kept up to date
22352 and users will have better luck checking out the manpage.
22353 - Remove the obsolete "NoPublish" option; it has been flagged
22354 as obsolete and has produced a warning since 0.1.1.18-rc.
22355 - Remove everything related to building the expert bundle for OS X.
22356 It has confused many users, doesn't work right on OS X 10.6,
22357 and is hard to get rid of once installed. Resolves bug 1274.
22360 Changes in version 0.2.2.17-alpha - 2010-09-30
22361 Tor 0.2.2.17-alpha introduces a feature to make it harder for clients
22362 to use one-hop circuits (which can put the exit relays at higher risk,
22363 plus unbalance the network); fixes a big bug in bandwidth accounting
22364 for relays that want to limit their monthly bandwidth use; fixes a
22365 big pile of bugs in how clients tolerate temporary network failure;
22366 and makes our adaptive circuit build timeout feature (which improves
22367 client performance if your network is fast while not breaking things
22368 if your network is slow) better handle bad networks.
22371 - Exit relays now try harder to block exit attempts from unknown
22372 relays, to make it harder for people to use them as one-hop proxies
22373 a la tortunnel. Controlled by the refuseunknownexits consensus
22374 parameter (currently enabled), or you can override it on your
22375 relay with the RefuseUnknownExits torrc option. Resolves bug 1751.
22377 o Major bugfixes (0.2.1.x and earlier):
22378 - Fix a bug in bandwidth accounting that could make us use twice
22379 the intended bandwidth when our interval start changes due to
22380 daylight saving time. Now we tolerate skew in stored vs computed
22381 interval starts: if the start of the period changes by no more than
22382 50% of the period's duration, we remember bytes that we transferred
22383 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
22384 - Always search the Windows system directory for system DLLs, and
22385 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
22386 - When you're using bridges and your network goes away and your
22387 bridges get marked as down, recover when you attempt a new socks
22388 connection (if the network is back), rather than waiting up to an
22389 hour to try fetching new descriptors for your bridges. Bugfix on
22390 0.2.0.3-alpha; fixes bug 1981.
22392 o Major bugfixes (on 0.2.2.x):
22393 - Fix compilation on Windows. Bugfix on 0.2.2.16-alpha; related to
22395 - Fix a segfault that could happen when operating a bridge relay with
22396 no GeoIP database set. Fixes bug 1964; bugfix on 0.2.2.15-alpha.
22397 - The consensus bandwidth-weights (used by clients to choose fast
22398 relays) entered an unexpected edge case in September where
22399 Exits were much scarcer than Guards, resulting in bad weight
22400 recommendations. Now we compute them using new constraints that
22401 should succeed in all cases. Also alter directory authorities to
22402 not include the bandwidth-weights line if they fail to produce
22403 valid values. Fixes bug 1952; bugfix on 0.2.2.10-alpha.
22404 - When weighting bridges during path selection, we used to trust
22405 the bandwidths they provided in their descriptor, only capping them
22406 at 10MB/s. This turned out to be problematic for two reasons:
22407 Bridges could claim to handle a lot more traffic then they
22408 actually would, thus making more clients pick them and have a
22409 pretty effective DoS attack. The other issue is that new bridges
22410 that might not have a good estimate for their bw capacity yet
22411 would not get used at all unless no other bridges are available
22412 to a client. Fixes bug 1912; bugfix on 0.2.2.7-alpha.
22414 o Major bugfixes (on the circuit build timeout feature, 0.2.2.x):
22415 - Ignore cannibalized circuits when recording circuit build times.
22416 This should provide for a minor performance improvement for hidden
22417 service users using 0.2.2.14-alpha, and should remove two spurious
22418 notice log messages. Bugfix on 0.2.2.14-alpha; fixes bug 1740.
22419 - Simplify the logic that causes us to decide if the network is
22420 unavailable for purposes of recording circuit build times. If we
22421 receive no cells whatsoever for the entire duration of a circuit's
22422 full measured lifetime, the network is probably down. Also ignore
22423 one-hop directory fetching circuit timeouts when calculating our
22424 circuit build times. These changes should hopefully reduce the
22425 cases where we see ridiculous circuit build timeouts for people
22426 with spotty wireless connections. Fixes part of bug 1772; bugfix
22428 - Prevent the circuit build timeout from becoming larger than
22429 the maximum build time we have ever seen. Also, prevent the time
22430 period for measurement circuits from becoming larger than twice that
22431 value. Fixes the other part of bug 1772; bugfix on 0.2.2.2-alpha.
22434 - When we run out of directory information such that we can't build
22435 circuits, but then get enough that we can build circuits, log when
22436 we actually construct a circuit, so the user has a better chance of
22437 knowing what's going on. Fixes bug 1362.
22438 - Be more generous with how much bandwidth we'd use up (with
22439 accounting enabled) before entering "soft hibernation". Previously,
22440 we'd refuse new connections and circuits once we'd used up 95% of
22441 our allotment. Now, we use up 95% of our allotment, AND make sure
22442 that we have no more than 500MB (or 3 hours of expected traffic,
22443 whichever is lower) remaining before we enter soft hibernation.
22444 - If we've configured EntryNodes and our network goes away and/or all
22445 our entrynodes get marked down, optimistically retry them all when
22446 a new socks application request appears. Fixes bug 1882.
22447 - Add some more defensive programming for architectures that can't
22448 handle unaligned integer accesses. We don't know of any actual bugs
22449 right now, but that's the best time to fix them. Fixes bug 1943.
22450 - Support line continuations in the torrc config file. If a line
22451 ends with a single backslash character, the newline is ignored, and
22452 the configuration value is treated as continuing on the next line.
22455 o Minor bugfixes (on 0.2.1.x and earlier):
22456 - For bandwidth accounting, calculate our expected bandwidth rate
22457 based on the time during which we were active and not in
22458 soft-hibernation during the last interval. Previously, we were
22459 also considering the time spent in soft-hibernation. If this
22460 was a long time, we would wind up underestimating our bandwidth
22461 by a lot, and skewing our wakeup time towards the start of the
22462 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
22464 o Minor bugfixes (on 0.2.2.x):
22465 - Resume generating CIRC FAILED REASON=TIMEOUT control port messages,
22466 which were disabled by the circuit build timeout changes in
22467 0.2.2.14-alpha. Bugfix on 0.2.2.14-alpha; fixes bug 1739.
22468 - Make sure we don't warn about missing bandwidth weights when
22469 choosing bridges or other relays not in the consensus. Bugfix on
22470 0.2.2.10-alpha; fixes bug 1805.
22471 - In our logs, do not double-report signatures from unrecognized
22472 authorities both as "from unknown authority" and "not
22473 present". Fixes bug 1956, bugfix on 0.2.2.16-alpha.
22476 Changes in version 0.2.2.16-alpha - 2010-09-17
22477 Tor 0.2.2.16-alpha fixes a variety of old stream fairness bugs (most
22478 evident at exit relays), and also continues to resolve all the little
22479 bugs that have been filling up trac lately.
22481 o Major bugfixes (stream-level fairness):
22482 - When receiving a circuit-level SENDME for a blocked circuit, try
22483 to package cells fairly from all the streams that had previously
22484 been blocked on that circuit. Previously, we had started with the
22485 oldest stream, and allowed each stream to potentially exhaust
22486 the circuit's package window. This gave older streams on any
22487 given circuit priority over newer ones. Fixes bug 1937. Detected
22488 originally by Camilo Viecco. This bug was introduced before the
22489 first Tor release, in svn commit r152: it is the new winner of
22490 the longest-lived bug prize.
22491 - When the exit relay got a circuit-level sendme cell, it started
22492 reading on the exit streams, even if had 500 cells queued in the
22493 circuit queue already, so the circuit queue just grew and grew in
22494 some cases. We fix this by not re-enabling reading on receipt of a
22495 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
22496 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
22498 - Newly created streams were allowed to read cells onto circuits,
22499 even if the circuit's cell queue was blocked and waiting to drain.
22500 This created potential unfairness, as older streams would be
22501 blocked, but newer streams would gladly fill the queue completely.
22502 We add code to detect this situation and prevent any stream from
22503 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
22507 - Update to the September 1 2010 Maxmind GeoLite Country database.
22508 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
22509 not. This would lead to a cookie that is still not group readable.
22510 Closes bug 1843. Suggested by katmagic.
22511 - When logging a rate-limited warning, we now mention how many messages
22512 got suppressed since the last warning.
22513 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
22514 do individual connection-level rate limiting of clients. The torrc
22515 config options with the same names trump the consensus params, if
22516 both are present. Replaces the old "bwconnrate" and "bwconnburst"
22517 consensus params which were broken from 0.2.2.7-alpha through
22518 0.2.2.14-alpha. Closes bug 1947.
22519 - When a router changes IP address or port, authorities now launch
22520 a new reachability test for it. Implements ticket 1899.
22521 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
22522 2 no signature, 4 required" messages about consensus signatures
22523 easier to read, and make sure they get logged at the same severity
22524 as the messages explaining which keys are which. Fixes bug 1290.
22525 - Don't warn when we have a consensus that we can't verify because
22526 of missing certificates, unless those certificates are ones
22527 that we have been trying and failing to download. Fixes bug 1145.
22528 - If you configure your bridge with a known identity fingerprint,
22529 and the bridge authority is unreachable (as it is in at least
22530 one country now), fall back to directly requesting the descriptor
22531 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
22533 - When building with --enable-gcc-warnings on OpenBSD, disable
22534 warnings in system headers. This makes --enable-gcc-warnings
22535 pass on OpenBSD 4.8.
22537 o Minor bugfixes (on 0.2.1.x and earlier):
22538 - Authorities will now attempt to download consensuses if their
22539 own efforts to make a live consensus have failed. This change
22540 means authorities that restart will fetch a valid consensus, and
22541 it means authorities that didn't agree with the current consensus
22542 will still fetch and serve it if it has enough signatures. Bugfix
22543 on 0.2.0.9-alpha; fixes bug 1300.
22544 - Ensure DNS requests launched by "RESOLVE" commands from the
22545 controller respect the __LeaveStreamsUnattached setconf options. The
22546 same goes for requests launched via DNSPort or transparent
22547 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
22548 - Allow handshaking OR connections to take a full KeepalivePeriod
22549 seconds to handshake. Previously, we would close them after
22550 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
22551 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
22553 - Rate-limit "Failed to hand off onionskin" warnings.
22554 - Never relay a cell for a circuit we have already destroyed.
22555 Between marking a circuit as closeable and finally closing it,
22556 it may have been possible for a few queued cells to get relayed,
22557 even though they would have been immediately dropped by the next
22558 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
22559 - Never queue a cell for a circuit that's already been marked
22561 - Never vote for a server as "Running" if we have a descriptor for
22562 it claiming to be hibernating, and that descriptor was published
22563 more recently than our last contact with the server. Bugfix on
22564 0.2.0.3-alpha; fixes bug 911.
22565 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
22568 o Minor bugfixes (on 0.2.2.x):
22569 - Fix a regression introduced in 0.2.2.7-alpha that marked relays
22570 down if a directory fetch fails and you've configured either
22571 bridges or EntryNodes. The intent was to mark the relay as down
22572 _unless_ you're using bridges or EntryNodes, since if you are
22573 then you could quickly run out of entry points.
22574 - Fix the Windows directory-listing code. A bug introduced in
22575 0.2.2.14-alpha could make Windows directory servers forget to load
22576 some of their cached v2 networkstatus files.
22577 - Really allow clients to use relays as bridges. Fixes bug 1776;
22578 bugfix on 0.2.2.15-alpha.
22579 - Demote a warn to info that happens when the CellStatistics option
22580 was just enabled. Bugfix on 0.2.2.15-alpha; fixes bug 1921.
22581 Reported by Moritz Bartl.
22582 - On Windows, build correctly either with or without Unicode support.
22583 This is necessary so that Tor can support fringe platforms like
22584 Windows 98 (which has no Unicode), or Windows CE (which has no
22585 non-Unicode). Bugfix on 0.2.2.14-alpha; fixes bug 1797.
22588 - Add a unit test for cross-platform directory-listing code.
22591 Changes in version 0.2.2.15-alpha - 2010-08-18
22592 Tor 0.2.2.15-alpha fixes a big bug in hidden service availability,
22593 fixes a variety of other bugs that were preventing performance
22594 experiments from moving forward, fixes several bothersome memory leaks,
22595 and generally closes a lot of smaller bugs that have been filling up
22599 - Stop assigning the HSDir flag to relays that disable their
22600 DirPort (and thus will refuse to answer directory requests). This
22601 fix should dramatically improve the reachability of hidden services:
22602 hidden services and hidden service clients pick six HSDir relays
22603 to store and retrieve the hidden service descriptor, and currently
22604 about half of the HSDir relays will refuse to work. Bugfix on
22605 0.2.0.10-alpha; fixes part of bug 1693.
22606 - The PerConnBWRate and Burst config options, along with the
22607 bwconnrate and bwconnburst consensus params, initialized each conn's
22608 token bucket values only when the connection is established. Now we
22609 update them if the config options change, and update them every time
22610 we get a new consensus. Otherwise we can encounter an ugly edge
22611 case where we initialize an OR conn to client-level bandwidth,
22612 but then later the relay joins the consensus and we leave it
22613 throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
22614 - Fix a regression that caused Tor to rebind its ports if it receives
22615 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
22618 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
22619 should give us approximately 40-50% more Guard-flagged nodes,
22620 improving the anonymity the Tor network can provide and also
22621 decreasing the dropoff in throughput that relays experience when
22622 they first get the Guard flag.
22623 - Allow enabling or disabling the *Statistics config options while
22627 - Update to the August 1 2010 Maxmind GeoLite Country database.
22628 - Have the controller interface give a more useful message than
22629 "Internal Error" in response to failed GETINFO requests.
22630 - Warn when the same option is provided more than once in a torrc
22631 file, on the command line, or in a single SETCONF statement, and
22632 the option is one that only accepts a single line. Closes bug 1384.
22633 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
22634 Patch from mingw-san.
22635 - Add support for the country code "{??}" in torrc options like
22636 ExcludeNodes, to indicate all routers of unknown country. Closes
22638 - Relays report the number of bytes spent on answering directory
22639 requests in extra-info descriptors similar to {read,write}-history.
22640 Implements enhancement 1790.
22642 o Minor bugfixes (on 0.2.1.x and earlier):
22643 - Complain if PublishServerDescriptor is given multiple arguments that
22644 include 0 or 1. This configuration will be rejected in the future.
22645 Bugfix on 0.2.0.1-alpha; closes bug 1107.
22646 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
22647 Bugfix on 0.2.0.13-alpha; closes bug 928.
22648 - Change "Application request when we're believed to be offline."
22649 notice to "Application request when we haven't used client
22650 functionality lately.", to clarify that it's not an error. Bugfix
22651 on 0.0.9.3; fixes bug 1222.
22652 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
22653 would return "551 Internal error" rather than "552 Unrecognized key
22654 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
22655 - Users can't configure a regular relay to be their bridge. It didn't
22656 work because when Tor fetched the bridge descriptor, it found
22657 that it already had it, and didn't realize that the purpose of the
22658 descriptor had changed. Now we replace routers with a purpose other
22659 than bridge with bridge descriptors when fetching them. Bugfix on
22660 0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
22661 refetch the descriptor with router purpose 'general', disabling
22663 - Fix a rare bug in rend_fn unit tests: we would fail a test when
22664 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
22665 on 0.2.0.10-alpha; fixes bug 1808.
22666 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
22667 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
22668 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
22669 Servers can start sending this code when enough clients recognize
22670 it. Also update the spec to reflect this new reason. Bugfix on
22671 0.1.0.1-rc; fixes part of bug 1793.
22672 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
22673 when we switch from being a public relay to a bridge. Otherwise
22674 there will still be clients that see the relay in their consensus,
22675 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
22677 - Instead of giving an assertion failure on an internal mismatch
22678 on estimated freelist size, just log a BUG warning and try later.
22679 Mitigates but does not fix bug 1125.
22680 - Fix an assertion failure that could occur in caches or bridge users
22681 when using a very short voting interval on a testing network.
22682 Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.
22684 o Minor bugfixes (on 0.2.2.x):
22685 - Alter directory authorities to always consider Exit-flagged nodes
22686 as potential Guard nodes in their votes. The actual decision to
22687 use Exits as Guards is done in the consensus bandwidth weights.
22688 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
22689 - When the controller is reporting the purpose of circuits that
22690 didn't finish building before the circuit build timeout, it was
22691 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
22692 - Our libevent version parsing code couldn't handle versions like
22693 1.4.14b-stable and incorrectly warned the user about using an
22694 old and broken version of libevent. Treat 1.4.14b-stable like
22695 1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
22697 - Don't use substitution references like $(VAR:MOD) when
22698 $(asciidoc_files) is empty -- make(1) on NetBSD transforms
22699 '$(:x)' to 'x' rather than the empty string. This bites us in
22700 doc/ when configured with --disable-asciidoc. Bugfix on
22701 0.2.2.9-alpha; fixes bug 1773.
22702 - Remove a spurious hidden service server-side log notice about
22703 "Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
22705 - Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
22707 - Correctly report written bytes on linked connections. Found while
22708 implementing 1790. Bugfix on 0.2.2.4-alpha.
22709 - Fix three memory leaks: one in circuit_build_times_parse_state(),
22710 one in dirvote_add_signatures_to_pending_consensus(), and one every
22711 time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
22712 0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.
22714 o Code simplifications and refactoring:
22715 - Take a first step towards making or.h smaller by splitting out
22716 function definitions for all source files in src/or/. Leave
22717 structures and defines in or.h for now.
22718 - Remove a bunch of unused function declarations as well as a block of
22719 #if 0'd code from the unit tests. Closes bug 1824.
22720 - New unit tests for exit-port history statistics; refactored exit
22721 statistics code to be more easily tested.
22722 - Remove the old debian/ directory from the main Tor distribution.
22723 The official Tor-for-debian git repository lives at the URL
22724 https://git.torproject.org/debian/tor.git
22727 Changes in version 0.2.2.14-alpha - 2010-07-12
22728 Tor 0.2.2.14-alpha greatly improves client-side handling of
22729 circuit build timeouts, which are used to estimate speed and improve
22730 performance. We also move to a much better GeoIP database, port Tor to
22731 Windows CE, introduce new compile flags that improve code security,
22732 add an eighth v3 directory authority, and address a lot of more
22736 - Tor directory authorities no longer crash when started with a
22737 cached-microdesc-consensus file in their data directory. Bugfix
22738 on 0.2.2.6-alpha; fixes bug 1532.
22739 - Treat an unset $HOME like an empty $HOME rather than triggering an
22740 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
22741 - Ignore negative and large circuit build timeout values that can
22742 happen during a suspend or hibernate. These values caused various
22743 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
22744 - Alter calculation of Pareto distribution parameter 'Xm' for
22745 Circuit Build Timeout learning to use the weighted average of the
22746 top N=3 modes (because we have three entry guards). Considering
22747 multiple modes should improve the timeout calculation in some cases,
22748 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
22750 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
22751 right censored distribution model. This approach improves over the
22752 synthetic timeout generation approach that was producing insanely
22753 high timeout values. Now we calculate build timeouts using truncated
22754 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
22755 - Do not close circuits that are under construction when they reach
22756 the circuit build timeout. Instead, leave them building (but do not
22757 use them) for up until the time corresponding to the 95th percentile
22758 on the Pareto CDF or 60 seconds, whichever is greater. This is done
22759 to provide better data for the new Pareto model. This percentile
22760 can be controlled by the consensus.
22763 - Move to the June 2010 Maxmind GeoLite country db (rather than the
22764 June 2009 ip-to-country GeoIP db) for our statistics that count
22765 how many users relays are seeing from each country. Now we have
22766 more accurate data for many African countries.
22767 - Port Tor to build and run correctly on Windows CE systems, using
22768 the wcecompat library. Contributed by Valerio Lupi.
22769 - New "--enable-gcc-hardening" ./configure flag (off by default)
22770 to turn on gcc compile time hardening options. It ensures
22771 that signed ints have defined behavior (-fwrapv), enables
22772 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
22773 with canaries (-fstack-protector-all), turns on ASLR protection if
22774 supported by the kernel (-fPIE, -pie), and adds additional security
22775 related warnings. Verified to work on Mac OS X and Debian Lenny.
22776 - New "--enable-linker-hardening" ./configure flag (off by default)
22777 to turn on ELF specific hardening features (relro, now). This does
22778 not work with Mac OS X or any other non-ELF binary format.
22780 o New directory authorities:
22781 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
22785 - New config option "WarnUnsafeSocks 0" disables the warning that
22786 occurs whenever Tor receives a socks handshake using a version of
22787 the socks protocol that can only provide an IP address (rather
22788 than a hostname). Setups that do DNS locally over Tor are fine,
22789 and we shouldn't spam the logs in that case.
22790 - Convert the HACKING file to asciidoc, and add a few new sections
22791 to it, explaining how we use Git, how we make changelogs, and
22792 what should go in a patch.
22793 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
22794 event, to give information on the current rate of circuit timeouts
22795 over our stored history.
22796 - Add ability to disable circuit build time learning via consensus
22797 parameter and via a LearnCircuitBuildTimeout config option. Also
22798 automatically disable circuit build time calculation if we are
22799 either a AuthoritativeDirectory, or if we fail to write our state
22800 file. Fixes bug 1296.
22801 - More gracefully handle corrupt state files, removing asserts
22802 in favor of saving a backup and resetting state.
22803 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
22807 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
22809 - When a2x fails, mention that the user could disable manpages instead
22810 of trying to fix their asciidoc installation.
22811 - Where available, use Libevent 2.0's periodic timers so that our
22812 once-per-second cleanup code gets called even more closely to
22813 once per second than it would otherwise. Fixes bug 943.
22814 - If you run a bridge that listens on multiple IP addresses, and
22815 some user configures a bridge address that uses a different IP
22816 address than your bridge writes in its router descriptor, and the
22817 user doesn't specify an identity key, their Tor would discard the
22818 descriptor because "it isn't one of our configured bridges", and
22819 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
22820 Bugfix on 0.2.0.3-alpha.
22821 - If OpenSSL fails to make a duplicate of a private or public key, log
22822 an error message and try to exit cleanly. May help with debugging
22823 if bug 1209 ever remanifests.
22824 - Save a couple bytes in memory allocation every time we escape
22825 certain characters in a string. Patch from Florian Zumbiehl.
22826 - Make it explicit that we don't cannibalize one-hop circuits. This
22827 happens in the wild, but doesn't turn out to be a problem because
22828 we fortunately don't use those circuits. Many thanks to outofwords
22829 for the initial analysis and to swissknife who confirmed that
22830 two-hop circuits are actually created.
22831 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
22832 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
22833 - Eliminate a case where a circuit build time warning was displayed
22834 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
22837 Changes in version 0.2.1.26 - 2010-05-02
22838 Tor 0.2.1.26 addresses the recent connection and memory overload
22839 problems we've been seeing on relays, especially relays with their
22840 DirPort open. If your relay has been crashing, or you turned it off
22841 because it used too many resources, give this release a try.
22843 This release also fixes yet another instance of broken OpenSSL libraries
22844 that was causing some relays to drop out of the consensus.
22847 - Teach relays to defend themselves from connection overload. Relays
22848 now close idle circuits early if it looks like they were intended
22849 for directory fetches. Relays are also more aggressive about closing
22850 TLS connections that have no circuits on them. Such circuits are
22851 unlikely to be re-used, and tens of thousands of them were piling
22852 up at the fast relays, causing the relays to run out of sockets
22853 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
22854 their directory fetches over TLS).
22855 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
22856 that claim to be earlier than 0.9.8m, but which have in reality
22857 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
22858 behavior. Possible fix for some cases of bug 1346.
22859 - Directory mirrors were fetching relay descriptors only from v2
22860 directory authorities, rather than v3 authorities like they should.
22861 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
22862 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
22865 - Finally get rid of the deprecated and now harmful notion of "clique
22866 mode", where directory authorities maintain TLS connections to
22870 - In the util/threads test, no longer free the test_mutex before all
22871 worker threads have finished. Bugfix on 0.2.1.6-alpha.
22872 - The master thread could starve the worker threads quite badly on
22873 certain systems, causing them to run only partially in the allowed
22874 window. This resulted in test failures. Now the master thread sleeps
22875 occasionally for a few microseconds while the two worker-threads
22876 compete for the mutex. Bugfix on 0.2.0.1-alpha.
22879 Changes in version 0.2.2.13-alpha - 2010-04-24
22880 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
22881 problems we've been seeing on relays, especially relays with their
22882 DirPort open. If your relay has been crashing, or you turned it off
22883 because it used too many resources, give this release a try.
22886 - Teach relays to defend themselves from connection overload. Relays
22887 now close idle circuits early if it looks like they were intended
22888 for directory fetches. Relays are also more aggressive about closing
22889 TLS connections that have no circuits on them. Such circuits are
22890 unlikely to be re-used, and tens of thousands of them were piling
22891 up at the fast relays, causing the relays to run out of sockets
22892 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
22893 their directory fetches over TLS).
22896 - Finally get rid of the deprecated and now harmful notion of "clique
22897 mode", where directory authorities maintain TLS connections to
22899 - Directory authorities now do an immediate reachability check as soon
22900 as they hear about a new relay. This change should slightly reduce
22901 the time between setting up a relay and getting listed as running
22902 in the consensus. It should also improve the time between setting
22903 up a bridge and seeing use by bridge users.
22904 - Directory authorities no longer launch a TLS connection to every
22905 relay as they startup. Now that we have 2k+ descriptors cached,
22906 the resulting network hiccup is becoming a burden. Besides,
22907 authorities already avoid voting about Running for the first half
22908 hour of their uptime.
22911 Changes in version 0.2.2.12-alpha - 2010-04-20
22912 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
22913 handle and vote on descriptors. It was causing relays to drop out of
22917 - Many relays have been falling out of the consensus lately because
22918 not enough authorities know about their descriptor for them to get
22919 a majority of votes. When we deprecated the v2 directory protocol,
22920 we got rid of the only way that v3 authorities can hear from each
22921 other about other descriptors. Now authorities examine every v3
22922 vote for new descriptors, and fetch them from that authority. Bugfix
22924 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
22925 and a warning in or.h related to bandwidth_weight_rule_t that
22926 prevented clean compile on OS X. Fixes bug 1363; bugfix on
22928 - Fix a segfault on relays when DirReqStatistics is enabled
22929 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
22933 - Demote a confusing TLS warning that relay operators might get when
22934 someone tries to talk to their OrPort. It is neither the operator's
22935 fault nor can they do anything about it. Fixes bug 1364; bugfix
22939 Changes in version 0.2.2.11-alpha - 2010-04-15
22940 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
22941 libraries that was causing some relays to drop out of the consensus.
22944 - Directory mirrors were fetching relay descriptors only from v2
22945 directory authorities, rather than v3 authorities like they should.
22946 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
22947 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
22948 - Fix a parsing error that made every possible value of
22949 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
22950 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
22951 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
22952 about the option without breaking older ones.
22953 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
22954 that claim to be earlier than 0.9.8m, but which have in reality
22955 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
22956 behavior. Possible fix for some cases of bug 1346.
22959 - Experiment with a more aggressive approach to preventing clients
22960 from making one-hop exit streams. Exit relays who want to try it
22961 out can set "RefuseUnknownExits 1" in their torrc, and then look
22962 for "Attempt by %s to open a stream" log messages. Let us know
22964 - Add support for statically linking zlib by specifying
22965 --enable-static-zlib, to go with our support for statically linking
22966 openssl and libevent. Resolves bug 1358.
22969 - Fix a segfault that happens whenever a Tor client that is using
22970 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
22972 - When we cleaned up the contrib/tor-exit-notice.html file, we left
22973 out the first line. Fixes bug 1295.
22974 - When building the manpage from a tarball, we required asciidoc, but
22975 the asciidoc -> roff/html conversion was already done for the
22976 tarball. Make 'make' complain only when we need asciidoc (either
22977 because we're compiling directly from git, or because we altered
22978 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
22979 - When none of the directory authorities vote on any params, Tor
22980 segfaulted when trying to make the consensus from the votes. We
22981 didn't trigger the bug in practice, because authorities do include
22982 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
22985 - In the util/threads test, no longer free the test_mutex before all
22986 worker threads have finished. Bugfix on 0.2.1.6-alpha.
22987 - The master thread could starve the worker threads quite badly on
22988 certain systems, causing them to run only partially in the allowed
22989 window. This resulted in test failures. Now the master thread sleeps
22990 occasionally for a few microseconds while the two worker-threads
22991 compete for the mutex. Bugfix on 0.2.0.1-alpha.
22994 Changes in version 0.2.2.10-alpha - 2010-03-07
22995 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
22996 could prevent relays from guessing their IP address correctly. It also
22997 starts the groundwork for another client-side performance boost, since
22998 currently we're not making efficient use of relays that have both the
22999 Guard flag and the Exit flag.
23002 - Fix a regression from our patch for bug 1244 that caused relays
23003 to guess their IP address incorrectly if they didn't set Address
23004 in their torrc and/or their address fails to resolve. Bugfix on
23005 0.2.2.9-alpha; fixes bug 1269.
23007 o Major features (performance):
23008 - Directory authorities now compute consensus weightings that instruct
23009 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
23010 and no flag. Clients that use these weightings will distribute
23011 network load more evenly across these different relay types. The
23012 weightings are in the consensus so we can change them globally in
23013 the future. Extra thanks to "outofwords" for finding some nasty
23014 security bugs in the first implementation of this feature.
23016 o Minor features (performance):
23017 - Always perform router selections using weighted relay bandwidth,
23018 even if we don't need a high capacity circuit at the time. Non-fast
23019 circuits now only differ from fast ones in that they can use relays
23020 not marked with the Fast flag. This "feature" could turn out to
23021 be a horrible bug; we should investigate more before it goes into
23025 - Allow disabling building of the manpages. Skipping the manpage
23026 speeds up the build considerably.
23028 o Minor bugfixes (on 0.2.2.x):
23029 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
23030 Bugfix on 0.2.2.9-alpha.
23031 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
23032 config option. Bugfix on 0.2.2.7-alpha.
23033 - Ship the asciidoc-helper file in the tarball, so that people can
23034 build from source if they want to, and touching the .1.txt files
23035 doesn't break the build. Bugfix on 0.2.2.9-alpha.
23037 o Minor bugfixes (on 0.2.1.x or earlier):
23038 - Fix a dereference-then-NULL-check sequence when publishing
23039 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
23041 - Fix another dereference-then-NULL-check sequence. Bugfix on
23042 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
23043 - Make sure we treat potentially not NUL-terminated strings correctly.
23044 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
23046 o Code simplifications and refactoring:
23047 - Fix some urls in the exit notice file and make it XHTML1.1 strict
23048 compliant. Based on a patch from Christian Kujau.
23049 - Don't use sed in asciidoc-helper anymore.
23050 - Make the build process fail if asciidoc cannot be found and
23051 building with asciidoc isn't disabled.
23054 Changes in version 0.2.2.9-alpha - 2010-02-22
23055 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
23056 location of a directory authority, and cleans up a bunch of small bugs.
23058 o Directory authority changes:
23059 - Change IP address for dannenberg (v3 directory authority), and
23060 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
23061 service directory authority) from the list.
23064 - Make Tor work again on the latest OS X: when deciding whether to
23065 use strange flags to turn TLS renegotiation on, detect the OpenSSL
23066 version at run-time, not compile time. We need to do this because
23067 Apple doesn't update its dev-tools headers when it updates its
23068 libraries in a security patch.
23069 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
23070 that could happen on 32-bit platforms with 64-bit time_t. Also fix
23071 a memory leak when requesting a hidden service descriptor we've
23072 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
23074 - Authorities could be tricked into giving out the Exit flag to relays
23075 that didn't allow exiting to any ports. This bug could screw
23076 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
23077 1238. Bug discovered by Martin Kowalczyk.
23078 - When freeing a session key, zero it out completely. We only zeroed
23079 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
23080 patched by ekir. Fixes bug 1254.
23083 - Fix static compilation by listing the openssl libraries in the right
23084 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
23085 - Resume handling .exit hostnames in a special way: originally we
23086 stripped the .exit part and used the requested exit relay. In
23087 0.2.2.1-alpha we stopped treating them in any special way, meaning
23088 if you use a .exit address then Tor will pass it on to the exit
23089 relay. Now we reject the .exit stream outright, since that behavior
23090 might be more expected by the user. Found and diagnosed by Scott
23091 Bennett and Downie on or-talk.
23092 - Don't spam the controller with events when we have no file
23093 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
23094 for log messages was already solved from bug 748.)
23095 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
23097 - Make the DNSPort option work with libevent 2.x. Don't alter the
23098 behavior for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
23099 - Emit a GUARD DROPPED controller event for a case we missed.
23100 - Make more fields in the controller protocol case-insensitive, since
23101 control-spec.txt said they were.
23102 - Refactor resolve_my_address() to not use gethostbyname() anymore.
23103 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
23104 - Fix a spec conformance issue: the network-status-version token
23105 must be the first token in a v3 consensus or vote. Discovered by
23106 parakeep. Bugfix on 0.2.0.3-alpha.
23108 o Code simplifications and refactoring:
23109 - Generate our manpage and HTML documentation using Asciidoc. This
23110 change should make it easier to maintain the documentation, and
23111 produce nicer HTML.
23112 - Remove the --enable-iphone option. According to reports from Marco
23113 Bonetti, Tor builds fine without any special tweaking on recent
23114 iPhone SDK versions.
23115 - Removed some unnecessary files from the source distribution. The
23116 AUTHORS file has now been merged into the people page on the
23117 website. The roadmaps and design doc can now be found in the
23118 projects directory in svn.
23119 - Enabled various circuit build timeout constants to be controlled
23120 by consensus parameters. Also set better defaults for these
23121 parameters based on experimentation on broadband and simulated
23122 high latency links.
23125 - The 'EXTENDCIRCUIT' control port command can now be used with
23126 a circ id of 0 and no path. This feature will cause Tor to build
23127 a new 'fast' general purpose circuit using its own path selection
23129 - Added a BUILDTIMEOUT_SET controller event to describe changes
23130 to the circuit build timeout.
23131 - Future-proof the controller protocol a bit by ignoring keyword
23132 arguments we do not recognize.
23133 - Expand homedirs passed to tor-checkkey. This should silence a
23134 coverity complaint about passing a user-supplied string into
23135 open() without checking it.
23138 Changes in version 0.2.1.25 - 2010-03-16
23139 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
23140 prevent relays from guessing their IP address correctly. It also fixes
23141 several minor potential security bugs.
23144 - Fix a regression from our patch for bug 1244 that caused relays
23145 to guess their IP address incorrectly if they didn't set Address
23146 in their torrc and/or their address fails to resolve. Bugfix on
23147 0.2.1.23; fixes bug 1269.
23148 - When freeing a session key, zero it out completely. We only zeroed
23149 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
23150 patched by ekir. Fixes bug 1254.
23153 - Fix a dereference-then-NULL-check sequence when publishing
23154 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
23156 - Fix another dereference-then-NULL-check sequence. Bugfix on
23157 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
23158 - Make sure we treat potentially not NUL-terminated strings correctly.
23159 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
23163 Changes in version 0.2.1.24 - 2010-02-21
23164 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
23168 - Work correctly out-of-the-box with even more vendor-patched versions
23169 of OpenSSL. In particular, make it so Debian and OS X don't need
23170 customized patches to run/build.
23173 Changes in version 0.2.1.23 - 2010-02-13
23174 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
23175 again on the latest OS X, and updates the location of a directory
23178 o Major bugfixes (performance):
23179 - We were selecting our guards uniformly at random, and then weighting
23180 which of our guards we'd use uniformly at random. This imbalance
23181 meant that Tor clients were severely limited on throughput (and
23182 probably latency too) by the first hop in their circuit. Now we
23183 select guards weighted by currently advertised bandwidth. We also
23184 automatically discard guards picked using the old algorithm. Fixes
23185 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
23188 - Make Tor work again on the latest OS X: when deciding whether to
23189 use strange flags to turn TLS renegotiation on, detect the OpenSSL
23190 version at run-time, not compile time. We need to do this because
23191 Apple doesn't update its dev-tools headers when it updates its
23192 libraries in a security patch.
23193 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
23194 that could happen on 32-bit platforms with 64-bit time_t. Also fix
23195 a memory leak when requesting a hidden service descriptor we've
23196 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
23199 o Directory authority changes:
23200 - Change IP address for dannenberg (v3 directory authority), and
23201 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
23202 service directory authority) from the list.
23205 - Refactor resolve_my_address() to not use gethostbyname() anymore.
23206 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
23209 - Avoid a mad rush at the beginning of each month when each client
23210 rotates half of its guards. Instead we spread the rotation out
23211 throughout the month, but we still avoid leaving a precise timestamp
23212 in the state file about when we first picked the guard. Improves
23213 over the behavior introduced in 0.1.2.17.
23216 Changes in version 0.2.2.8-alpha - 2010-01-26
23217 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
23218 causing bridge relays to disappear. If you're running a bridge,
23222 - Fix a memory corruption bug on bridges that occurred during the
23223 inclusion of stats data in extra-info descriptors. Also fix the
23224 interface for geoip_get_bridge_stats* to prevent similar bugs in
23225 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
23226 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
23229 - Ignore OutboundBindAddress when connecting to localhost.
23230 Connections to localhost need to come _from_ localhost, or else
23231 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
23235 Changes in version 0.2.2.7-alpha - 2010-01-19
23236 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
23237 as laying the groundwork for further relay-side performance fixes. It
23238 also starts cleaning up client behavior with respect to the EntryNodes,
23239 ExitNodes, and StrictNodes config options.
23241 This release also rotates two directory authority keys, due to a
23242 security breach of some of the Torproject servers.
23244 o Directory authority changes:
23245 - Rotate keys (both v3 identity and relay identity) for moria1
23248 o Major features (performance):
23249 - We were selecting our guards uniformly at random, and then weighting
23250 which of our guards we'd use uniformly at random. This imbalance
23251 meant that Tor clients were severely limited on throughput (and
23252 probably latency too) by the first hop in their circuit. Now we
23253 select guards weighted by currently advertised bandwidth. We also
23254 automatically discard guards picked using the old algorithm. Fixes
23255 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
23256 - When choosing which cells to relay first, relays can now favor
23257 circuits that have been quiet recently, to provide lower latency
23258 for low-volume circuits. By default, relays enable or disable this
23259 feature based on a setting in the consensus. You can override
23260 this default by using the new "CircuitPriorityHalflife" config
23261 option. Design and code by Ian Goldberg, Can Tang, and Chris
23263 - Add separate per-conn write limiting to go with the per-conn read
23264 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
23265 but never per-conn write limits.
23266 - New consensus params "bwconnrate" and "bwconnburst" to let us
23267 rate-limit client connections as they enter the network. It's
23268 controlled in the consensus so we can turn it on and off for
23269 experiments. It's starting out off. Based on proposal 163.
23271 o Major features (relay selection options):
23272 - Switch to a StrictNodes config option, rather than the previous
23273 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
23274 "StrictExcludeNodes" option.
23275 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
23276 change during a config reload, mark and discard all our origin
23277 circuits. This fix should address edge cases where we change the
23278 config options and but then choose a circuit that we created before
23280 - If EntryNodes or ExitNodes are set, be more willing to use an
23281 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
23283 - Make EntryNodes config option much more aggressive even when
23284 StrictNodes is not set. Before it would prepend your requested
23285 entrynodes to your list of guard nodes, but feel free to use others
23286 after that. Now it chooses only from your EntryNodes if any of
23287 those are available, and only falls back to others if a) they're
23288 all down and b) StrictNodes is not set.
23289 - Now we refresh your entry guards from EntryNodes at each consensus
23290 fetch -- rather than just at startup and then they slowly rot as
23291 the network changes.
23294 - Stop bridge directory authorities from answering dbg-stability.txt
23295 directory queries, which would let people fetch a list of all
23296 bridge identities they track. Bugfix on 0.2.1.6-alpha.
23299 - Log a notice when we get a new control connection. Now it's easier
23300 for security-conscious users to recognize when a local application
23301 is knocking on their controller door. Suggested by bug 1196.
23302 - New config option "CircuitStreamTimeout" to override our internal
23303 timeout schedule for how many seconds until we detach a stream from
23304 a circuit and try a new circuit. If your network is particularly
23305 slow, you might want to set this to a number like 60.
23306 - New controller command "getinfo config-text". It returns the
23307 contents that Tor would write if you send it a SAVECONF command,
23308 so the controller can write the file to disk itself.
23309 - New options for SafeLogging to allow scrubbing only log messages
23310 generated while acting as a relay.
23311 - Ship the bridges spec file in the tarball too.
23312 - Avoid a mad rush at the beginning of each month when each client
23313 rotates half of its guards. Instead we spread the rotation out
23314 throughout the month, but we still avoid leaving a precise timestamp
23315 in the state file about when we first picked the guard. Improves
23316 over the behavior introduced in 0.1.2.17.
23318 o Minor bugfixes (compiling):
23319 - Fix compilation on OS X 10.3, which has a stub mlockall() but
23320 hides it. Bugfix on 0.2.2.6-alpha.
23321 - Fix compilation on Solaris by removing support for the
23322 DisableAllSwap config option. Solaris doesn't have an rlimit for
23323 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
23326 o Minor bugfixes (crashes):
23327 - Do not segfault when writing buffer stats when we haven't observed
23328 a single circuit to report about. Found by Fabian Lanze. Bugfix on
23330 - If we're in the pathological case where there's no exit bandwidth
23331 but there is non-exit bandwidth, or no guard bandwidth but there
23332 is non-guard bandwidth, don't crash during path selection. Bugfix
23334 - Fix an impossible-to-actually-trigger buffer overflow in relay
23335 descriptor generation. Bugfix on 0.1.0.15.
23337 o Minor bugfixes (privacy):
23338 - Fix an instance where a Tor directory mirror might accidentally
23339 log the IP address of a misbehaving Tor client. Bugfix on
23341 - Don't list Windows capabilities in relay descriptors. We never made
23342 use of them, and maybe it's a bad idea to publish them. Bugfix
23345 o Minor bugfixes (other):
23346 - Resolve an edge case in path weighting that could make us misweight
23347 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
23348 - Fix statistics on client numbers by country as seen by bridges that
23349 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
23350 intervals instead of variable 12-to-48-hour intervals.
23351 - After we free an internal connection structure, overwrite it
23352 with a different memory value than we use for overwriting a freed
23353 internal circuit structure. Should help with debugging. Suggested
23355 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
23358 o Removed features:
23359 - Remove the HSAuthorityRecordStats option that version 0 hidden
23360 service authorities could have used to track statistics of overall
23361 hidden service usage.
23364 Changes in version 0.2.1.22 - 2010-01-19
23365 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
23366 authorities -- it would tell you its whole history of bridge descriptors
23367 if you make the right directory request. This stable update also
23368 rotates two of the seven v3 directory authority keys and locations.
23370 o Directory authority changes:
23371 - Rotate keys (both v3 identity and relay identity) for moria1
23375 - Stop bridge directory authorities from answering dbg-stability.txt
23376 directory queries, which would let people fetch a list of all
23377 bridge identities they track. Bugfix on 0.2.1.6-alpha.
23380 Changes in version 0.2.1.21 - 2009-12-21
23381 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
23382 library. If you use Tor on Linux / Unix and you're getting SSL
23383 renegotiation errors, upgrading should help. We also recommend an
23384 upgrade if you're an exit relay.
23387 - Work around a security feature in OpenSSL 0.9.8l that prevents our
23388 handshake from working unless we explicitly tell OpenSSL that we
23389 are using SSL renegotiation safely. We are, of course, but OpenSSL
23390 0.9.8l won't work unless we say we are.
23391 - Avoid crashing if the client is trying to upload many bytes and the
23392 circuit gets torn down at the same time, or if the flip side
23393 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
23396 - Do not refuse to learn about authority certs and v2 networkstatus
23397 documents that are older than the latest consensus. This bug might
23398 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
23399 Spotted and fixed by xmux.
23400 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
23401 trigger platform-specific option misparsing case found by Coverity
23403 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
23404 trigger assert. Fixes bug 1173.
23407 Changes in version 0.2.2.6-alpha - 2009-11-19
23408 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
23409 support for the new lower-footprint "microdescriptor" directory design,
23410 future-proofing our consensus format against new hash functions or
23411 other changes, and an Android port. It also makes Tor compatible with
23412 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
23415 - Directory authorities can now create, vote on, and serve multiple
23416 parallel formats of directory data as part of their voting process.
23417 Partially implements Proposal 162: "Publish the consensus in
23419 - Directory authorities can now agree on and publish small summaries
23420 of router information that clients can use in place of regular
23421 server descriptors. This transition will eventually allow clients
23422 to use far less bandwidth for downloading information about the
23423 network. Begins the implementation of Proposal 158: "Clients
23424 download consensus + microdescriptors".
23425 - The directory voting system is now extensible to use multiple hash
23426 algorithms for signatures and resource selection. Newer formats
23427 are signed with SHA256, with a possibility for moving to a better
23428 hash algorithm in the future.
23429 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
23430 current and future memory pages via mlockall(). On supported
23431 platforms (modern Linux and probably BSD but not Windows or OS X),
23432 this should effectively disable any and all attempts to page out
23433 memory. This option requires that you start your Tor as root --
23434 if you use DisableAllSwap, please consider using the User option
23435 to properly reduce the privileges of your Tor.
23436 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
23437 to help Tor build correctly for Android phones.
23440 - Work around a security feature in OpenSSL 0.9.8l that prevents our
23441 handshake from working unless we explicitly tell OpenSSL that we
23442 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
23443 won't work unless we say we are.
23446 - Fix a crash bug when trying to initialize the evdns module in
23447 Libevent 2. Bugfix on 0.2.1.16-rc.
23448 - Stop logging at severity 'warn' when some other Tor client tries
23449 to establish a circuit with us using weak DH keys. It's a protocol
23450 violation, but that doesn't mean ordinary users need to hear about
23451 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
23452 - Do not refuse to learn about authority certs and v2 networkstatus
23453 documents that are older than the latest consensus. This bug might
23454 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
23455 Spotted and fixed by xmux.
23456 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
23457 - If all authorities restart at once right before a consensus vote,
23458 nobody will vote about "Running", and clients will get a consensus
23459 with no usable relays. Instead, authorities refuse to build a
23460 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
23461 - If your relay can't keep up with the number of incoming create
23462 cells, it would log one warning per failure into your logs. Limit
23463 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
23464 - Bridges now use "reject *:*" as their default exit policy. Bugfix
23465 on 0.2.0.3-alpha; fixes bug 1113.
23466 - Fix a memory leak on directory authorities during voting that was
23467 introduced in 0.2.2.1-alpha. Found via valgrind.
23470 Changes in version 0.2.1.20 - 2009-10-15
23471 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
23472 services at once, prepares for more performance improvements, and
23473 fixes a bunch of smaller bugs.
23475 The Windows and OS X bundles also include a more recent Vidalia,
23476 and switch from Privoxy to Polipo.
23478 The OS X installers are now drag and drop. It's best to un-install
23479 Tor/Vidalia and then install this new bundle, rather than upgrade. If
23480 you want to upgrade, you'll need to update the paths for Tor and Polipo
23481 in the Vidalia Settings window.
23484 - Send circuit or stream sendme cells when our window has decreased
23485 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
23486 by Karsten when testing the "reduce circuit window" performance
23487 patch. Bugfix on the 54th commit on Tor -- from July 2002,
23488 before the release of Tor 0.0.0. This is the new winner of the
23490 - Fix a remotely triggerable memory leak when a consensus document
23491 contains more than one signature from the same voter. Bugfix on
23493 - Avoid segfault in rare cases when finishing an introduction circuit
23494 as a client and finding out that we don't have an introduction key
23495 for it. Fixes bug 1073. Reported by Aaron Swartz.
23498 - Tor now reads the "circwindow" parameter out of the consensus,
23499 and uses that value for its circuit package window rather than the
23500 default of 1000 cells. Begins the implementation of proposal 168.
23502 o New directory authorities:
23503 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
23505 - Move moria1 and tonga to alternate IP addresses.
23508 - Fix a signed/unsigned compile warning in 0.2.1.19.
23509 - Fix possible segmentation fault on directory authorities. Bugfix on
23511 - Fix an extremely rare infinite recursion bug that could occur if
23512 we tried to log a message after shutting down the log subsystem.
23513 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
23514 - Fix an obscure bug where hidden services on 64-bit big-endian
23515 systems might mis-read the timestamp in v3 introduce cells, and
23516 refuse to connect back to the client. Discovered by "rotor".
23517 Bugfix on 0.2.1.6-alpha.
23518 - We were triggering a CLOCK_SKEW controller status event whenever
23519 we connect via the v2 connection protocol to any relay that has
23520 a wrong clock. Instead, we should only inform the controller when
23521 it's a trusted authority that claims our clock is wrong. Bugfix
23522 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
23523 - We were telling the controller about CHECKING_REACHABILITY and
23524 REACHABILITY_FAILED status events whenever we launch a testing
23525 circuit or notice that one has failed. Instead, only tell the
23526 controller when we want to inform the user of overall success or
23527 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
23529 - Don't warn when we're using a circuit that ends with a node
23530 excluded in ExcludeExitNodes, but the circuit is not used to access
23531 the outside world. This should help fix bug 1090. Bugfix on
23533 - Work around a small memory leak in some versions of OpenSSL that
23534 stopped the memory used by the hostname TLS extension from being
23538 - Add a "getinfo status/accepted-server-descriptor" controller
23539 command, which is the recommended way for controllers to learn
23540 whether our server descriptor has been successfully received by at
23541 least on directory authority. Un-recommend good-server-descriptor
23542 getinfo and status events until we have a better design for them.
23545 Changes in version 0.2.2.5-alpha - 2009-10-11
23546 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
23549 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
23551 o Directory authorities:
23552 - Temporarily (just for this release) move dizum to an alternate
23556 Changes in version 0.2.2.4-alpha - 2009-10-10
23557 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
23558 introduces a new unit test framework, shifts directry authority
23559 addresses around to reduce the impact from recent blocking events,
23560 and fixes a few smaller bugs.
23563 - Fix several more asserts in the circuit_build_times code, for
23564 example one that causes Tor to fail to start once we have
23565 accumulated 5000 build times in the state file. Bugfixes on
23566 0.2.2.2-alpha; fixes bug 1108.
23568 o New directory authorities:
23569 - Move moria1 and Tonga to alternate IP addresses.
23572 - Log SSL state transitions at debug level during handshake, and
23573 include SSL states in error messages. This may help debug future
23574 SSL handshake issues.
23575 - Add a new "Handshake" log domain for activities that happen
23576 during the TLS handshake.
23577 - Revert to the "June 3 2009" ip-to-country file. The September one
23578 seems to have removed most US IP addresses.
23579 - Directory authorities now reject Tor relays with versions less than
23580 0.1.2.14. This step cuts out four relays from the current network,
23581 none of which are very big.
23584 - Fix a couple of smaller issues with gathering statistics. Bugfixes
23586 - Fix two memory leaks in the error case of
23587 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
23588 - Don't count one-hop circuits when we're estimating how long it
23589 takes circuits to build on average. Otherwise we'll set our circuit
23590 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
23591 - Directory authorities no longer change their opinion of, or vote on,
23592 whether a router is Running, unless they have themselves been
23593 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
23596 o Code simplifications and refactoring:
23597 - Revise our unit tests to use the "tinytest" framework, so we
23598 can run tests in their own processes, have smarter setup/teardown
23599 code, and so on. The unit test code has moved to its own
23600 subdirectory, and has been split into multiple modules.
23603 Changes in version 0.2.2.3-alpha - 2009-09-23
23604 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
23607 - Fix an overzealous assert in our new circuit build timeout code.
23608 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
23611 - If the networkstatus consensus tells us that we should use a
23612 negative circuit package window, ignore it. Otherwise we'll
23613 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
23616 Changes in version 0.2.2.2-alpha - 2009-09-21
23617 Tor 0.2.2.2-alpha introduces our latest performance improvement for
23618 clients: Tor tracks the average time it takes to build a circuit, and
23619 avoids using circuits that take too long to build. For fast connections,
23620 this feature can cut your expected latency in half. For slow or flaky
23621 connections, it could ruin your Tor experience. Let us know if it does!
23624 - Tor now tracks how long it takes to build client-side circuits
23625 over time, and adapts its timeout to local network performance.
23626 Since a circuit that takes a long time to build will also provide
23627 bad performance, we get significant latency improvements by
23628 discarding the slowest 20% of circuits. Specifically, Tor creates
23629 circuits more aggressively than usual until it has enough data
23630 points for a good timeout estimate. Implements proposal 151.
23631 We are especially looking for reports (good and bad) from users with
23632 both EDGE and broadband connections that can move from broadband
23633 to EDGE and find out if the build-time data in the .tor/state gets
23634 reset without loss of Tor usability. You should also see a notice
23635 log message telling you that Tor has reset its timeout.
23636 - Directory authorities can now vote on arbitrary integer values as
23637 part of the consensus process. This is designed to help set
23638 network-wide parameters. Implements proposal 167.
23639 - Tor now reads the "circwindow" parameter out of the consensus,
23640 and uses that value for its circuit package window rather than the
23641 default of 1000 cells. Begins the implementation of proposal 168.
23644 - Fix a remotely triggerable memory leak when a consensus document
23645 contains more than one signature from the same voter. Bugfix on
23649 - Fix an extremely rare infinite recursion bug that could occur if
23650 we tried to log a message after shutting down the log subsystem.
23651 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
23652 - Fix parsing for memory or time units given without a space between
23653 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
23654 - A networkstatus vote must contain exactly one signature. Spec
23655 conformance issue. Bugfix on 0.2.0.3-alpha.
23656 - Fix an obscure bug where hidden services on 64-bit big-endian
23657 systems might mis-read the timestamp in v3 introduce cells, and
23658 refuse to connect back to the client. Discovered by "rotor".
23659 Bugfix on 0.2.1.6-alpha.
23660 - We were triggering a CLOCK_SKEW controller status event whenever
23661 we connect via the v2 connection protocol to any relay that has
23662 a wrong clock. Instead, we should only inform the controller when
23663 it's a trusted authority that claims our clock is wrong. Bugfix
23664 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
23665 - We were telling the controller about CHECKING_REACHABILITY and
23666 REACHABILITY_FAILED status events whenever we launch a testing
23667 circuit or notice that one has failed. Instead, only tell the
23668 controller when we want to inform the user of overall success or
23669 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
23671 - Don't warn when we're using a circuit that ends with a node
23672 excluded in ExcludeExitNodes, but the circuit is not used to access
23673 the outside world. This should help fix bug 1090, but more problems
23674 remain. Bugfix on 0.2.1.6-alpha.
23675 - Work around a small memory leak in some versions of OpenSSL that
23676 stopped the memory used by the hostname TLS extension from being
23678 - Make our 'torify' script more portable; if we have only one of
23679 'torsocks' or 'tsocks' installed, don't complain to the user;
23680 and explain our warning about tsocks better.
23683 - Add a "getinfo status/accepted-server-descriptor" controller
23684 command, which is the recommended way for controllers to learn
23685 whether our server descriptor has been successfully received by at
23686 least on directory authority. Un-recommend good-server-descriptor
23687 getinfo and status events until we have a better design for them.
23688 - Update to the "September 4 2009" ip-to-country file.
23691 Changes in version 0.2.2.1-alpha - 2009-08-26
23692 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
23693 Tor clients to bootstrap on networks where only port 80 is reachable,
23694 makes it more straightforward to support hardware crypto accelerators,
23695 and starts the groundwork for gathering stats safely at relays.
23698 - Start the process of disabling ".exit" address notation, since it
23699 can be used for a variety of esoteric application-level attacks
23700 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
23703 o New directory authorities:
23704 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
23708 - New AccelName and AccelDir options add support for dynamic OpenSSL
23709 hardware crypto acceleration engines.
23710 - Tor now supports tunneling all of its outgoing connections over
23711 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
23712 configuration options. Code by Christopher Davis.
23715 - Send circuit or stream sendme cells when our window has decreased
23716 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
23717 by Karsten when testing the "reduce circuit window" performance
23718 patch. Bugfix on the 54th commit on Tor -- from July 2002,
23719 before the release of Tor 0.0.0. This is the new winner of the
23722 o New options for gathering stats safely:
23723 - Directory mirrors that set "DirReqStatistics 1" write statistics
23724 about directory requests to disk every 24 hours. As compared to the
23725 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
23726 1) stats are written to disk exactly every 24 hours; 2) estimated
23727 shares of v2 and v3 requests are determined as mean values, not at
23728 the end of a measurement period; 3) unresolved requests are listed
23729 with country code '??'; 4) directories also measure download times.
23730 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
23731 number of exit streams and transferred bytes per port to disk every
23733 - Relays that set "CellStatistics 1" write statistics on how long
23734 cells spend in their circuit queues to disk every 24 hours.
23735 - Entry nodes that set "EntryStatistics 1" write statistics on the
23736 rough number and origins of connecting clients to disk every 24
23738 - Relays that write any of the above statistics to disk and set
23739 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
23740 their extra-info documents.
23743 - New --digests command-line switch to output the digests of the
23744 source files Tor was built with.
23745 - The "torify" script now uses torsocks where available.
23746 - The memarea code now uses a sentinel value at the end of each area
23747 to make sure nothing writes beyond the end of an area. This might
23748 help debug some conceivable causes of bug 930.
23749 - Time and memory units in the configuration file can now be set to
23750 fractional units. For example, "2.5 GB" is now a valid value for
23752 - Certain Tor clients (such as those behind check.torproject.org) may
23753 want to fetch the consensus in an extra early manner. To enable this
23754 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
23755 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
23756 as only certain clients who must have this information sooner should
23758 - Instead of adding the svn revision to the Tor version string, report
23759 the git commit (when we're building from a git checkout).
23762 - If any of the v3 certs we download are unparseable, we should
23763 actually notice the failure so we don't retry indefinitely. Bugfix
23764 on 0.2.0.x; reported by "rotator".
23765 - If the cached cert file is unparseable, warn but don't exit.
23766 - Fix possible segmentation fault on directory authorities. Bugfix on
23768 - When Tor fails to parse a descriptor of any kind, dump it to disk.
23769 Might help diagnosing bug 1051.
23771 o Deprecated and removed features:
23772 - The controller no longer accepts the old obsolete "addr-mappings/"
23773 or "unregistered-servers-" GETINFO values.
23774 - Hidden services no longer publish version 0 descriptors, and clients
23775 do not request or use version 0 descriptors. However, the old hidden
23776 service authorities still accept and serve version 0 descriptors
23777 when contacted by older hidden services/clients.
23778 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
23779 always on; using them is necessary for correct forward-compatible
23781 - Remove support for .noconnect style addresses. Nobody was using
23782 them, and they provided another avenue for detecting Tor users
23783 via application-level web tricks.
23785 o Packaging changes:
23786 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
23787 installer bundles. See
23788 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
23789 for details of what's new in Vidalia 0.2.3.
23790 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
23791 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
23792 configuration file, rather than the old Privoxy.
23793 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
23794 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
23795 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
23796 better compatibility with OS X 10.6, aka Snow Leopard.
23797 - OS X Vidalia Bundle: The multi-package installer is now replaced
23798 by a simple drag and drop to the /Applications folder. This change
23799 occurred with the upgrade to Vidalia 0.2.3.
23802 Changes in version 0.2.1.19 - 2009-07-28
23803 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
23804 services on Tor 0.2.1.3-alpha through 0.2.1.18.
23807 - Make accessing hidden services on 0.2.1.x work right again.
23808 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
23809 part of patch provided by "optimist".
23812 - When a relay/bridge is writing out its identity key fingerprint to
23813 the "fingerprint" file and to its logs, write it without spaces. Now
23814 it will look like the fingerprints in our bridges documentation,
23815 and confuse fewer users.
23818 - Relays no longer publish a new server descriptor if they change
23819 their MaxAdvertisedBandwidth config option but it doesn't end up
23820 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
23821 fixes bug 1026. Patch from Sebastian.
23822 - Avoid leaking memory every time we get a create cell but we have
23823 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
23824 fixes bug 1034. Reported by BarkerJr.
23827 Changes in version 0.2.1.18 - 2009-07-24
23828 Tor 0.2.1.18 lays the foundations for performance improvements,
23829 adds status events to help users diagnose bootstrap problems, adds
23830 optional authentication/authorization for hidden services, fixes a
23831 variety of potential anonymity problems, and includes a huge pile of
23832 other features and bug fixes.
23835 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
23838 Changes in version 0.2.1.17-rc - 2009-07-07
23839 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
23840 candidate for the 0.2.1.x series. It lays the groundwork for further
23841 client performance improvements, and also fixes a big bug with directory
23842 authorities that were causing them to assign Guard and Stable flags
23845 The Windows bundles also finally include the geoip database that we
23846 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
23847 should actually install Torbutton rather than giving you a cryptic
23848 failure message (oops).
23851 - Clients now use the bandwidth values in the consensus, rather than
23852 the bandwidth values in each relay descriptor. This approach opens
23853 the door to more accurate bandwidth estimates once the directory
23854 authorities start doing active measurements. Implements more of
23858 - When Tor clients restart after 1-5 days, they discard all their
23859 cached descriptors as too old, but they still use the cached
23860 consensus document. This approach is good for robustness, but
23861 bad for performance: since they don't know any bandwidths, they
23862 end up choosing at random rather than weighting their choice by
23863 speed. Fixed by the above feature of putting bandwidths in the
23864 consensus. Bugfix on 0.2.0.x.
23865 - Directory authorities were neglecting to mark relays down in their
23866 internal histories if the relays fall off the routerlist without
23867 ever being found unreachable. So there were relays in the histories
23868 that haven't been seen for eight months, and are listed as being
23869 up for eight months. This wreaked havoc on the "median wfu"
23870 and "median mtbf" calculations, in turn making Guard and Stable
23871 flags very wrong, hurting network performance. Fixes bugs 696 and
23872 969. Bugfix on 0.2.0.6-alpha.
23875 - Serve the DirPortFrontPage page even when we have been approaching
23876 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
23877 - The control port would close the connection before flushing long
23878 replies, such as the network consensus, if a QUIT command was issued
23879 before the reply had completed. Now, the control port flushes all
23880 pending replies before closing the connection. Also fixed a spurious
23881 warning when a QUIT command is issued after a malformed or rejected
23882 AUTHENTICATE command, but before the connection was closed. Patch
23883 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
23884 - When we can't find an intro key for a v2 hidden service descriptor,
23885 fall back to the v0 hidden service descriptor and log a bug message.
23886 Workaround for bug 1024.
23887 - Fix a log message that did not respect the SafeLogging option.
23891 - If we're a relay and we change our IP address, be more verbose
23892 about the reason that made us change. Should help track down
23893 further bugs for relays on dynamic IP addresses.
23896 Changes in version 0.2.0.35 - 2009-06-24
23898 - Avoid crashing in the presence of certain malformed descriptors.
23899 Found by lark, and by automated fuzzing.
23900 - Fix an edge case where a malicious exit relay could convince a
23901 controller that the client's DNS question resolves to an internal IP
23902 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
23905 - Finally fix the bug where dynamic-IP relays disappear when their
23906 IP address changes: directory mirrors were mistakenly telling
23907 them their old address if they asked via begin_dir, so they
23908 never got an accurate answer about their new address, so they
23909 just vanished after a day. For belt-and-suspenders, relays that
23910 don't set Address in their config now avoid using begin_dir for
23911 all direct connections. Should fix bugs 827, 883, and 900.
23912 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
23913 that would occur on some exit nodes when DNS failures and timeouts
23914 occurred in certain patterns. Fix for bug 957.
23917 - When starting with a cache over a few days old, do not leak
23918 memory for the obsolete router descriptors in it. Bugfix on
23919 0.2.0.33; fixes bug 672.
23920 - Hidden service clients didn't use a cached service descriptor that
23921 was older than 15 minutes, but wouldn't fetch a new one either,
23922 because there was already one in the cache. Now, fetch a v2
23923 descriptor unless the same descriptor was added to the cache within
23924 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
23927 Changes in version 0.2.1.16-rc - 2009-06-20
23928 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
23929 a bunch of minor bugs.
23932 - Fix an edge case where a malicious exit relay could convince a
23933 controller that the client's DNS question resolves to an internal IP
23934 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
23936 o Major performance improvements (on 0.2.0.x):
23937 - Disable and refactor some debugging checks that forced a linear scan
23938 over the whole server-side DNS cache. These accounted for over 50%
23939 of CPU time on a relatively busy exit node's gprof profile. Found
23941 - Disable some debugging checks that appeared in exit node profile
23945 - Update to the "June 3 2009" ip-to-country file.
23946 - Do not have tor-resolve automatically refuse all .onion addresses;
23947 if AutomapHostsOnResolve is set in your torrc, this will work fine.
23949 o Minor bugfixes (on 0.2.0.x):
23950 - Log correct error messages for DNS-related network errors on
23952 - Fix a race condition that could cause crashes or memory corruption
23953 when running as a server with a controller listening for log
23955 - Avoid crashing when we have a policy specified in a DirPolicy or
23956 SocksPolicy or ReachableAddresses option with ports set on it,
23957 and we re-load the policy. May fix bug 996.
23958 - Hidden service clients didn't use a cached service descriptor that
23959 was older than 15 minutes, but wouldn't fetch a new one either,
23960 because there was already one in the cache. Now, fetch a v2
23961 descriptor unless the same descriptor was added to the cache within
23962 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
23964 o Minor bugfixes (on 0.2.1.x):
23965 - Don't warn users about low port and hibernation mix when they
23966 provide a *ListenAddress directive to fix that. Bugfix on
23968 - When switching back and forth between bridge mode, do not start
23969 gathering GeoIP data until two hours have passed.
23970 - Do not complain that the user has requested an excluded node as
23971 an exit when the node is not really an exit. This could happen
23972 because the circuit was for testing, or an introduction point.
23976 Changes in version 0.2.1.15-rc - 2009-05-25
23977 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
23978 series. It fixes a major bug on fast exit relays, as well as a variety
23979 of more minor bugs.
23981 o Major bugfixes (on 0.2.0.x):
23982 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
23983 that would occur on some exit nodes when DNS failures and timeouts
23984 occurred in certain patterns. Fix for bug 957.
23986 o Minor bugfixes (on 0.2.0.x):
23987 - Actually return -1 in the error case for read_bandwidth_usage().
23988 Harmless bug, since we currently don't care about the return value
23989 anywhere. Bugfix on 0.2.0.9-alpha.
23990 - Provide a more useful log message if bug 977 (related to buffer
23991 freelists) ever reappears, and do not crash right away.
23992 - Fix an assertion failure on 64-bit platforms when we allocated
23993 memory right up to the end of a memarea, then realigned the memory
23994 one step beyond the end. Fixes a possible cause of bug 930.
23995 - Protect the count of open sockets with a mutex, so we can't
23996 corrupt it when two threads are closing or opening sockets at once.
23997 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
23998 - Don't allow a bridge to publish its router descriptor to a
23999 non-bridge directory authority. Fixes part of bug 932.
24000 - When we change to or from being a bridge, reset our counts of
24001 client usage by country. Fixes bug 932.
24002 - Fix a bug that made stream bandwidth get misreported to the
24004 - Stop using malloc_usable_size() to use more area than we had
24005 actually allocated: it was safe, but made valgrind really unhappy.
24006 - Fix a memory leak when v3 directory authorities load their keys
24007 and cert from disk. Bugfix on 0.2.0.1-alpha.
24009 o Minor bugfixes (on 0.2.1.x):
24010 - Fix use of freed memory when deciding to mark a non-addable
24011 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
24014 Changes in version 0.2.1.14-rc - 2009-04-12
24015 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
24016 series. It begins fixing some major performance problems, and also
24017 finally addresses the bug that was causing relays on dynamic IP
24018 addresses to fall out of the directory.
24021 - Clients replace entry guards that were chosen more than a few months
24022 ago. This change should significantly improve client performance,
24023 especially once more people upgrade, since relays that have been
24024 a guard for a long time are currently overloaded.
24026 o Major bugfixes (on 0.2.0):
24027 - Finally fix the bug where dynamic-IP relays disappear when their
24028 IP address changes: directory mirrors were mistakenly telling
24029 them their old address if they asked via begin_dir, so they
24030 never got an accurate answer about their new address, so they
24031 just vanished after a day. For belt-and-suspenders, relays that
24032 don't set Address in their config now avoid using begin_dir for
24033 all direct connections. Should fix bugs 827, 883, and 900.
24034 - Relays were falling out of the networkstatus consensus for
24035 part of a day if they changed their local config but the
24036 authorities discarded their new descriptor as "not sufficiently
24037 different". Now directory authorities accept a descriptor as changed
24038 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
24039 patch by Sebastian.
24040 - Avoid crashing in the presence of certain malformed descriptors.
24041 Found by lark, and by automated fuzzing.
24044 - When generating circuit events with verbose nicknames for
24045 controllers, try harder to look up nicknames for routers on a
24046 circuit. (Previously, we would look in the router descriptors we had
24047 for nicknames, but not in the consensus.) Partial fix for bug 941.
24048 - If the bridge config line doesn't specify a port, assume 443.
24049 This makes bridge lines a bit smaller and easier for users to
24051 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
24052 bytes (aka 20KB/s), to match our documentation. Also update
24053 directory authorities so they always assign the Fast flag to relays
24054 with 20KB/s of capacity. Now people running relays won't suddenly
24055 find themselves not seeing any use, if the network gets faster
24057 - Update to the "April 3 2009" ip-to-country file.
24060 - Avoid trying to print raw memory to the logs when we decide to
24061 give up on downloading a given relay descriptor. Bugfix on
24063 - In tor-resolve, when the Tor client to use is specified by
24064 <hostname>:<port>, actually use the specified port rather than
24065 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
24066 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
24067 - When starting with a cache over a few days old, do not leak
24068 memory for the obsolete router descriptors in it. Bugfix on
24070 - Avoid double-free on list of successfully uploaded hidden
24071 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
24072 - Change memarea_strndup() implementation to work even when
24073 duplicating a string at the end of a page. This bug was
24074 harmless for now, but could have meant crashes later. Fix by
24075 lark. Bugfix on 0.2.1.1-alpha.
24076 - Limit uploaded directory documents to be 16M rather than 500K.
24077 The directory authorities were refusing v3 consensus votes from
24078 other authorities, since the votes are now 504K. Fixes bug 959;
24079 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
24080 - Directory authorities should never send a 503 "busy" response to
24081 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
24085 Changes in version 0.2.1.13-alpha - 2009-03-09
24086 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
24087 cleanups. We're finally getting close to a release candidate.
24090 - Correctly update the list of which countries we exclude as
24091 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
24092 lark. Bugfix on 0.2.1.6-alpha.
24094 o Minor bugfixes (on 0.2.0.x and earlier):
24095 - Automatically detect MacOSX versions earlier than 10.4.0, and
24096 disable kqueue from inside Tor when running with these versions.
24097 We previously did this from the startup script, but that was no
24098 help to people who didn't use the startup script. Resolves bug 863.
24099 - When we had picked an exit node for a connection, but marked it as
24100 "optional", and it turned out we had no onion key for the exit,
24101 stop wanting that exit and try again. This situation may not
24102 be possible now, but will probably become feasible with proposal
24103 158. Spotted by rovv. Fixes another case of bug 752.
24104 - Clients no longer cache certificates for authorities they do not
24105 recognize. Bugfix on 0.2.0.9-alpha.
24106 - When we can't transmit a DNS request due to a network error, retry
24107 it after a while, and eventually transmit a failing response to
24108 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
24109 - If the controller claimed responsibility for a stream, but that
24110 stream never finished making its connection, it would live
24111 forever in circuit_wait state. Now we close it after SocksTimeout
24112 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
24113 - Drop begin cells to a hidden service if they come from the middle
24114 of a circuit. Patch from lark.
24115 - When we erroneously receive two EXTEND cells for the same circuit
24116 ID on the same connection, drop the second. Patch from lark.
24117 - Fix a crash that occurs on exit nodes when a nameserver request
24118 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
24119 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
24121 - Do not assume that a stack-allocated character array will be
24122 64-bit aligned on platforms that demand that uint64_t access is
24123 aligned. Possible fix for bug 604.
24124 - Parse dates and IPv4 addresses in a locale- and libc-independent
24125 manner, to avoid platform-dependent behavior on malformed input.
24126 - Build correctly when configured to build outside the main source
24127 path. Patch from Michael Gold.
24128 - We were already rejecting relay begin cells with destination port
24129 of 0. Now also reject extend cells with destination port or address
24130 of 0. Suggested by lark.
24132 o Minor bugfixes (on 0.2.1.x):
24133 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
24134 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
24135 - If we're an exit node, scrub the IP address to which we are exiting
24136 in the logs. Bugfix on 0.2.1.8-alpha.
24139 - On Linux, use the prctl call to re-enable core dumps when the user
24141 - New controller event NEWCONSENSUS that lists the networkstatus
24142 lines for every recommended relay. Now controllers like Torflow
24143 can keep up-to-date on which relays they should be using.
24144 - Update to the "February 26 2009" ip-to-country file.
24147 Changes in version 0.2.0.34 - 2009-02-08
24148 Tor 0.2.0.34 features several more security-related fixes. You should
24149 upgrade, especially if you run an exit relay (remote crash) or a
24150 directory authority (remote infinite loop), or you're on an older
24151 (pre-XP) or not-recently-patched Windows (remote exploit).
24153 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
24154 have many known flaws, and nobody should be using them. You should
24155 upgrade. If you're using a Linux or BSD and its packages are obsolete,
24156 stop using those packages and upgrade anyway.
24159 - Fix an infinite-loop bug on handling corrupt votes under certain
24160 circumstances. Bugfix on 0.2.0.8-alpha.
24161 - Fix a temporary DoS vulnerability that could be performed by
24162 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
24163 - Avoid a potential crash on exit nodes when processing malformed
24164 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
24165 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
24166 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
24169 - Fix compilation on systems where time_t is a 64-bit integer.
24170 Patch from Matthias Drochner.
24171 - Don't consider expiring already-closed client connections. Fixes
24172 bug 893. Bugfix on 0.0.2pre20.
24175 Changes in version 0.2.1.12-alpha - 2009-02-08
24176 Tor 0.2.1.12-alpha features several more security-related fixes. You
24177 should upgrade, especially if you run an exit relay (remote crash) or
24178 a directory authority (remote infinite loop), or you're on an older
24179 (pre-XP) or not-recently-patched Windows (remote exploit). It also
24180 includes a big pile of minor bugfixes and cleanups.
24183 - Fix an infinite-loop bug on handling corrupt votes under certain
24184 circumstances. Bugfix on 0.2.0.8-alpha.
24185 - Fix a temporary DoS vulnerability that could be performed by
24186 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
24187 - Avoid a potential crash on exit nodes when processing malformed
24188 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
24191 - Let controllers actually ask for the "clients_seen" event for
24192 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
24193 reported by Matt Edman.
24194 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
24196 - Fix a bug in address parsing that was preventing bridges or hidden
24197 service targets from being at IPv6 addresses.
24198 - Solve a bug that kept hardware crypto acceleration from getting
24199 enabled when accounting was turned on. Fixes bug 907. Bugfix on
24201 - Remove a bash-ism from configure.in to build properly on non-Linux
24202 platforms. Bugfix on 0.2.1.1-alpha.
24203 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
24204 headers. Bugfix on 0.2.0.10-alpha.
24205 - Don't consider expiring already-closed client connections. Fixes
24206 bug 893. Bugfix on 0.0.2pre20.
24207 - Fix another interesting corner-case of bug 891 spotted by rovv:
24208 Previously, if two hosts had different amounts of clock drift, and
24209 one of them created a new connection with just the wrong timing,
24210 the other might decide to deprecate the new connection erroneously.
24211 Bugfix on 0.1.1.13-alpha.
24212 - Resolve a very rare crash bug that could occur when the user forced
24213 a nameserver reconfiguration during the middle of a nameserver
24214 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
24215 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
24216 Bugfix on 0.2.1.7-alpha.
24217 - If we're using bridges and our network goes away, be more willing
24218 to forgive our bridges and try again when we get an application
24219 request. Bugfix on 0.2.0.x.
24222 - Support platforms where time_t is 64 bits long. (Congratulations,
24223 NetBSD!) Patch from Matthias Drochner.
24224 - Add a 'getinfo status/clients-seen' controller command, in case
24225 controllers want to hear clients_seen events but connect late.
24228 - Disable GCC's strict alias optimization by default, to avoid the
24229 likelihood of its introducing subtle bugs whenever our code violates
24230 the letter of C99's alias rules.
24233 Changes in version 0.2.0.33 - 2009-01-21
24234 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
24235 useful to users. It also finally fixes a bug where a relay or client
24236 that's been off for many days would take a long time to bootstrap.
24238 This update also fixes an important security-related bug reported by
24239 Ilja van Sprundel. You should upgrade. (We'll send out more details
24240 about the bug once people have had some time to upgrade.)
24243 - Fix a heap-corruption bug that may be remotely triggerable on
24244 some platforms. Reported by Ilja van Sprundel.
24247 - When a stream at an exit relay is in state "resolving" or
24248 "connecting" and it receives an "end" relay cell, the exit relay
24249 would silently ignore the end cell and not close the stream. If
24250 the client never closes the circuit, then the exit relay never
24251 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
24252 reported by "wood".
24253 - When sending CREATED cells back for a given circuit, use a 64-bit
24254 connection ID to find the right connection, rather than an addr:port
24255 combination. Now that we can have multiple OR connections between
24256 the same ORs, it is no longer possible to use addr:port to uniquely
24257 identify a connection.
24258 - Bridge relays that had DirPort set to 0 would stop fetching
24259 descriptors shortly after startup, and then briefly resume
24260 after a new bandwidth test and/or after publishing a new bridge
24261 descriptor. Bridge users that try to bootstrap from them would
24262 get a recent networkstatus but would get descriptors from up to
24263 18 hours earlier, meaning most of the descriptors were obsolete
24264 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
24265 - Prevent bridge relays from serving their 'extrainfo' document
24266 to anybody who asks, now that extrainfo docs include potentially
24267 sensitive aggregated client geoip summaries. Bugfix on
24269 - If the cached networkstatus consensus is more than five days old,
24270 discard it rather than trying to use it. In theory it could be
24271 useful because it lists alternate directory mirrors, but in practice
24272 it just means we spend many minutes trying directory mirrors that
24273 are long gone from the network. Also discard router descriptors as
24274 we load them if they are more than five days old, since the onion
24275 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
24278 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
24279 could make gcc generate non-functional binary search code. Bugfix
24281 - Build correctly on platforms without socklen_t.
24282 - Compile without warnings on solaris.
24283 - Avoid potential crash on internal error during signature collection.
24284 Fixes bug 864. Patch from rovv.
24285 - Correct handling of possible malformed authority signing key
24286 certificates with internal signature types. Fixes bug 880.
24287 Bugfix on 0.2.0.3-alpha.
24288 - Fix a hard-to-trigger resource leak when logging credential status.
24290 - When we can't initialize DNS because the network is down, do not
24291 automatically stop Tor from starting. Instead, we retry failed
24292 dns_init() every 10 minutes, and change the exit policy to reject
24293 *:* until one succeeds. Fixes bug 691.
24294 - Use 64 bits instead of 32 bits for connection identifiers used with
24295 the controller protocol, to greatly reduce risk of identifier reuse.
24296 - When we're choosing an exit node for a circuit, and we have
24297 no pending streams, choose a good general exit rather than one that
24298 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
24299 - Fix another case of assuming, when a specific exit is requested,
24300 that we know more than the user about what hosts it allows.
24301 Fixes one case of bug 752. Patch from rovv.
24302 - Clip the MaxCircuitDirtiness config option to a minimum of 10
24303 seconds. Warn the user if lower values are given in the
24304 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
24305 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
24306 user if lower values are given in the configuration. Bugfix on
24307 0.1.1.17-rc. Patch by Sebastian.
24308 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
24309 the cache because we already had a v0 descriptor with the same ID.
24310 Bugfix on 0.2.0.18-alpha.
24311 - Fix a race condition when freeing keys shared between main thread
24312 and CPU workers that could result in a memory leak. Bugfix on
24313 0.1.0.1-rc. Fixes bug 889.
24314 - Send a valid END cell back when a client tries to connect to a
24315 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
24316 840. Patch from rovv.
24317 - Check which hops rendezvous stream cells are associated with to
24318 prevent possible guess-the-streamid injection attacks from
24319 intermediate hops. Fixes another case of bug 446. Based on patch
24321 - If a broken client asks a non-exit router to connect somewhere,
24322 do not even do the DNS lookup before rejecting the connection.
24323 Fixes another case of bug 619. Patch from rovv.
24324 - When a relay gets a create cell it can't decrypt (e.g. because it's
24325 using the wrong onion key), we were dropping it and letting the
24326 client time out. Now actually answer with a destroy cell. Fixes
24327 bug 904. Bugfix on 0.0.2pre8.
24329 o Minor bugfixes (hidden services):
24330 - Do not throw away existing introduction points on SIGHUP. Bugfix on
24331 0.0.6pre1. Patch by Karsten. Fixes bug 874.
24334 - Report the case where all signatures in a detached set are rejected
24335 differently than the case where there is an error handling the
24337 - When we realize that another process has modified our cached
24338 descriptors, print out a more useful error message rather than
24339 triggering an assertion. Fixes bug 885. Patch from Karsten.
24340 - Implement the 0x20 hack to better resist DNS poisoning: set the
24341 case on outgoing DNS requests randomly, and reject responses that do
24342 not match the case correctly. This logic can be disabled with the
24343 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
24344 of servers that do not reliably preserve case in replies. See
24345 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
24347 - Check DNS replies for more matching fields to better resist DNS
24349 - Never use OpenSSL compression: it wastes RAM and CPU trying to
24350 compress cells, which are basically all encrypted, compressed, or
24354 Changes in version 0.2.1.11-alpha - 2009-01-20
24355 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
24356 week it will take a long time to bootstrap again" bug. It also fixes
24357 an important security-related bug reported by Ilja van Sprundel. You
24358 should upgrade. (We'll send out more details about the bug once people
24359 have had some time to upgrade.)
24362 - Fix a heap-corruption bug that may be remotely triggerable on
24363 some platforms. Reported by Ilja van Sprundel.
24366 - Discard router descriptors as we load them if they are more than
24367 five days old. Otherwise if Tor is off for a long time and then
24368 starts with cached descriptors, it will try to use the onion
24369 keys in those obsolete descriptors when building circuits. Bugfix
24370 on 0.2.0.x. Fixes bug 887.
24373 - Try to make sure that the version of Libevent we're running with
24374 is binary-compatible with the one we built with. May address bug
24376 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
24377 for bug 905. Bugfix on 0.2.1.7-alpha.
24378 - Add a new --enable-local-appdata configuration switch to change
24379 the default location of the datadir on win32 from APPDATA to
24380 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
24381 entirely. Patch from coderman.
24384 - Make outbound DNS packets respect the OutboundBindAddress setting.
24385 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
24386 - When our circuit fails at the first hop (e.g. we get a destroy
24387 cell back), avoid using that OR connection anymore, and also
24388 tell all the one-hop directory requests waiting for it that they
24389 should fail. Bugfix on 0.2.1.3-alpha.
24390 - In the torify(1) manpage, mention that tsocks will leak your
24394 Changes in version 0.2.1.10-alpha - 2009-01-06
24395 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
24396 would make the bridge relay not so useful if it had DirPort set to 0,
24397 and one that could let an attacker learn a little bit of information
24398 about the bridge's users), and a bug that would cause your Tor relay
24399 to ignore a circuit create request it can't decrypt (rather than reply
24400 with an error). It also fixes a wide variety of other bugs.
24403 - If the cached networkstatus consensus is more than five days old,
24404 discard it rather than trying to use it. In theory it could
24405 be useful because it lists alternate directory mirrors, but in
24406 practice it just means we spend many minutes trying directory
24407 mirrors that are long gone from the network. Helps bug 887 a bit;
24409 - Bridge relays that had DirPort set to 0 would stop fetching
24410 descriptors shortly after startup, and then briefly resume
24411 after a new bandwidth test and/or after publishing a new bridge
24412 descriptor. Bridge users that try to bootstrap from them would
24413 get a recent networkstatus but would get descriptors from up to
24414 18 hours earlier, meaning most of the descriptors were obsolete
24415 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
24416 - Prevent bridge relays from serving their 'extrainfo' document
24417 to anybody who asks, now that extrainfo docs include potentially
24418 sensitive aggregated client geoip summaries. Bugfix on
24422 - New controller event "clients_seen" to report a geoip-based summary
24423 of which countries we've seen clients from recently. Now controllers
24424 like Vidalia can show bridge operators that they're actually making
24426 - Build correctly against versions of OpenSSL 0.9.8 or later built
24427 without support for deprecated functions.
24428 - Update to the "December 19 2008" ip-to-country file.
24430 o Minor bugfixes (on 0.2.0.x):
24431 - Authorities now vote for the Stable flag for any router whose
24432 weighted MTBF is at least 5 days, regardless of the mean MTBF.
24433 - Do not remove routers as too old if we do not have any consensus
24434 document. Bugfix on 0.2.0.7-alpha.
24435 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
24436 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
24437 - When an exit relay resolves a stream address to a local IP address,
24438 do not just keep retrying that same exit relay over and
24439 over. Instead, just close the stream. Addresses bug 872. Bugfix
24440 on 0.2.0.32. Patch from rovv.
24441 - If a hidden service sends us an END cell, do not consider
24442 retrying the connection; just close it. Patch from rovv.
24443 - When we made bridge authorities stop serving bridge descriptors over
24444 unencrypted links, we also broke DirPort reachability testing for
24445 bridges. So bridges with a non-zero DirPort were printing spurious
24446 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
24447 - When a relay gets a create cell it can't decrypt (e.g. because it's
24448 using the wrong onion key), we were dropping it and letting the
24449 client time out. Now actually answer with a destroy cell. Fixes
24450 bug 904. Bugfix on 0.0.2pre8.
24451 - Squeeze 2-5% out of client performance (according to oprofile) by
24452 improving the implementation of some policy-manipulation functions.
24454 o Minor bugfixes (on 0.2.1.x):
24455 - Make get_interface_address() function work properly again; stop
24456 guessing the wrong parts of our address as our address.
24457 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
24458 send on that circuit. Otherwise we might violate the proposal-110
24459 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
24461 - When we're sending non-EXTEND cells to the first hop in a circuit,
24462 for example to use an encrypted directory connection, we don't need
24463 to use RELAY_EARLY cells: the first hop knows what kind of cell
24464 it is, and nobody else can even see the cell type. Conserving
24465 RELAY_EARLY cells makes it easier to cannibalize circuits like
24467 - Stop logging nameserver addresses in reverse order.
24468 - If we are retrying a directory download slowly over and over, do
24469 not automatically give up after the 254th failure. Bugfix on
24471 - Resume reporting accurate "stream end" reasons to the local control
24472 port. They were lost in the changes for Proposal 148. Bugfix on
24475 o Deprecated and removed features:
24476 - The old "tor --version --version" command, which would print out
24477 the subversion "Id" of most of the source files, is now removed. It
24478 turned out to be less useful than we'd expected, and harder to
24481 o Code simplifications and refactoring:
24482 - Change our header file guard macros to be less likely to conflict
24483 with system headers. Adam Langley noticed that we were conflicting
24484 with log.h on Android.
24485 - Tool-assisted documentation cleanup. Nearly every function or
24486 static variable in Tor should have its own documentation now.
24489 Changes in version 0.2.1.9-alpha - 2008-12-25
24490 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
24492 o New directory authorities:
24493 - gabelmoo (the authority run by Karsten Loesing) now has a new
24497 - Never use a connection with a mismatched address to extend a
24498 circuit, unless that connection is canonical. A canonical
24499 connection is one whose address is authenticated by the router's
24500 identity key, either in a NETINFO cell or in a router descriptor.
24501 - Avoid a possible memory corruption bug when receiving hidden service
24502 descriptors. Bugfix on 0.2.1.6-alpha.
24505 - Fix a logic error that would automatically reject all but the first
24506 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
24507 part of bug 813/868. Bug spotted by coderman.
24508 - When a stream at an exit relay is in state "resolving" or
24509 "connecting" and it receives an "end" relay cell, the exit relay
24510 would silently ignore the end cell and not close the stream. If
24511 the client never closes the circuit, then the exit relay never
24512 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
24513 reported by "wood".
24514 - When we can't initialize DNS because the network is down, do not
24515 automatically stop Tor from starting. Instead, retry failed
24516 dns_init() every 10 minutes, and change the exit policy to reject
24517 *:* until one succeeds. Fixes bug 691.
24520 - Give a better error message when an overzealous init script says
24521 "sudo -u username tor --user username". Makes Bug 882 easier for
24523 - When a directory authority gives us a new guess for our IP address,
24524 log which authority we used. Hopefully this will help us debug
24525 the recent complaints about bad IP address guesses.
24526 - Detect svn revision properly when we're using git-svn.
24527 - Try not to open more than one descriptor-downloading connection
24528 to an authority at once. This should reduce load on directory
24529 authorities. Fixes bug 366.
24530 - Add cross-certification to newly generated certificates, so that
24531 a signing key is enough information to look up a certificate.
24532 Partial implementation of proposal 157.
24533 - Start serving certificates by <identity digest, signing key digest>
24534 pairs. Partial implementation of proposal 157.
24535 - Clients now never report any stream end reason except 'MISC'.
24536 Implements proposal 148.
24537 - On platforms with a maximum syslog string length, truncate syslog
24538 messages to that length ourselves, rather than relying on the
24539 system to do it for us.
24540 - Optimize out calls to time(NULL) that occur for every IO operation,
24541 or for every cell. On systems where time() is a slow syscall,
24542 this fix will be slightly helpful.
24543 - Exit servers can now answer resolve requests for ip6.arpa addresses.
24544 - When we download a descriptor that we then immediately (as
24545 a directory authority) reject, do not retry downloading it right
24546 away. Should save some bandwidth on authorities. Fix for bug
24547 888. Patch by Sebastian Hahn.
24548 - When a download gets us zero good descriptors, do not notify
24549 Tor that new directory information has arrived.
24550 - Avoid some nasty corner cases in the logic for marking connections
24551 as too old or obsolete or noncanonical for circuits. Partial
24554 o Minor features (controller):
24555 - New CONSENSUS_ARRIVED event to note when a new consensus has
24556 been fetched and validated.
24557 - When we realize that another process has modified our cached
24558 descriptors file, print out a more useful error message rather
24559 than triggering an assertion. Fixes bug 885. Patch from Karsten.
24560 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
24561 controllers to prevent SIGHUP from reloading the
24562 configuration. Fixes bug 856.
24565 - Resume using the correct "REASON=" stream when telling the
24566 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
24567 - When a canonical connection appears later in our internal list
24568 than a noncanonical one for a given OR ID, always use the
24569 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
24571 - Clip the MaxCircuitDirtiness config option to a minimum of 10
24572 seconds. Warn the user if lower values are given in the
24573 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
24574 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
24575 user if lower values are given in the configuration. Bugfix on
24576 0.1.1.17-rc. Patch by Sebastian.
24577 - Fix a race condition when freeing keys shared between main thread
24578 and CPU workers that could result in a memory leak. Bugfix on
24579 0.1.0.1-rc. Fixes bug 889.
24581 o Minor bugfixes (hidden services):
24582 - Do not throw away existing introduction points on SIGHUP (bugfix on
24583 0.0.6pre1); also, do not stall hidden services because we're
24584 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
24585 by John Brooks. Patch by Karsten. Fixes bug 874.
24586 - Fix a memory leak when we decline to add a v2 rendezvous
24587 descriptor to the cache because we already had a v0 descriptor
24588 with the same ID. Bugfix on 0.2.0.18-alpha.
24590 o Deprecated and removed features:
24591 - RedirectExits has been removed. It was deprecated since
24593 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
24594 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
24595 - Cell pools are now always enabled; --disable-cell-pools is ignored.
24597 o Code simplifications and refactoring:
24598 - Rename the confusing or_is_obsolete field to the more appropriate
24599 is_bad_for_new_circs, and move it to or_connection_t where it
24601 - Move edge-only flags from connection_t to edge_connection_t: not
24602 only is this better coding, but on machines of plausible alignment,
24603 it should save 4-8 bytes per connection_t. "Every little bit helps."
24604 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
24605 for consistency; keep old option working for backward compatibility.
24606 - Simplify the code for finding connections to use for a circuit.
24609 Changes in version 0.2.1.8-alpha - 2008-12-08
24610 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
24611 builds better on unusual platforms like Solaris and old OS X, and
24612 fixes a variety of other issues.
24615 - New DirPortFrontPage option that takes an html file and publishes
24616 it as "/" on the DirPort. Now relay operators can provide a
24617 disclaimer without needing to set up a separate webserver. There's
24618 a sample disclaimer in contrib/tor-exit-notice.html.
24621 - When the client is choosing entry guards, now it selects at most
24622 one guard from a given relay family. Otherwise we could end up with
24623 all of our entry points into the network run by the same operator.
24624 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
24627 - Fix a DOS opportunity during the voting signature collection process
24628 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
24629 - Fix a possible segfault when establishing an exit connection. Bugfix
24633 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
24635 - Made Tor a little less aggressive about deleting expired
24636 certificates. Partial fix for bug 854.
24637 - Stop doing unaligned memory access that generated bus errors on
24638 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
24639 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
24640 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
24641 - Make USR2 log-level switch take effect immediately. Bugfix on
24643 - If one win32 nameserver fails to get added, continue adding the
24644 rest, and don't automatically fail.
24645 - Use fcntl() for locking when flock() is not available. Should fix
24646 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
24647 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
24648 could make gcc generate non-functional binary search code. Bugfix
24650 - Build correctly on platforms without socklen_t.
24651 - Avoid potential crash on internal error during signature collection.
24652 Fixes bug 864. Patch from rovv.
24653 - Do not use C's stdio library for writing to log files. This will
24654 improve logging performance by a minute amount, and will stop
24655 leaking fds when our disk is full. Fixes bug 861.
24656 - Stop erroneous use of O_APPEND in cases where we did not in fact
24657 want to re-seek to the end of a file before every last write().
24658 - Correct handling of possible malformed authority signing key
24659 certificates with internal signature types. Fixes bug 880. Bugfix
24661 - Fix a hard-to-trigger resource leak when logging credential status.
24665 - Directory mirrors no longer fetch the v1 directory or
24666 running-routers files. They are obsolete, and nobody asks for them
24667 anymore. This is the first step to making v1 authorities obsolete.
24669 o Minor features (controller):
24670 - Return circuit purposes in response to GETINFO circuit-status. Fixes
24674 Changes in version 0.2.0.32 - 2008-11-20
24675 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
24676 packages (and maybe other packages) noticed by Theo de Raadt, fixes
24677 a smaller security flaw that might allow an attacker to access local
24678 services, further improves hidden service performance, and fixes a
24679 variety of other issues.
24682 - The "User" and "Group" config options did not clear the
24683 supplementary group entries for the Tor process. The "User" option
24684 is now more robust, and we now set the groups to the specified
24685 user's primary group. The "Group" option is now ignored. For more
24686 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
24687 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
24688 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
24689 - The "ClientDNSRejectInternalAddresses" config option wasn't being
24690 consistently obeyed: if an exit relay refuses a stream because its
24691 exit policy doesn't allow it, we would remember what IP address
24692 the relay said the destination address resolves to, even if it's
24693 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
24696 - Fix a DOS opportunity during the voting signature collection process
24697 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
24699 o Major bugfixes (hidden services):
24700 - When fetching v0 and v2 rendezvous service descriptors in parallel,
24701 we were failing the whole hidden service request when the v0
24702 descriptor fetch fails, even if the v2 fetch is still pending and
24703 might succeed. Similarly, if the last v2 fetch fails, we were
24704 failing the whole hidden service request even if a v0 fetch is
24705 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
24706 - When extending a circuit to a hidden service directory to upload a
24707 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
24708 requests failed, because the router descriptor has not been
24709 downloaded yet. In these cases, do not attempt to upload the
24710 rendezvous descriptor, but wait until the router descriptor is
24711 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
24712 descriptor from a hidden service directory for which the router
24713 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
24717 - Fix several infrequent memory leaks spotted by Coverity.
24718 - When testing for libevent functions, set the LDFLAGS variable
24719 correctly. Found by Riastradh.
24720 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
24721 bootstrapping with tunneled directory connections. Bugfix on
24722 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
24723 - When asked to connect to A.B.exit:80, if we don't know the IP for A
24724 and we know that server B rejects most-but-not all connections to
24725 port 80, we would previously reject the connection. Now, we assume
24726 the user knows what they were asking for. Fixes bug 752. Bugfix
24727 on 0.0.9rc5. Diagnosed by BarkerJr.
24728 - If we overrun our per-second write limits a little, count this as
24729 having used up our write allocation for the second, and choke
24730 outgoing directory writes. Previously, we had only counted this when
24731 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
24732 Bugfix on 0.2.0.x (??).
24733 - Remove the old v2 directory authority 'lefkada' from the default
24734 list. It has been gone for many months.
24735 - Stop doing unaligned memory access that generated bus errors on
24736 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
24737 - Make USR2 log-level switch take effect immediately. Bugfix on
24740 o Minor bugfixes (controller):
24741 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
24742 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
24745 Changes in version 0.2.1.7-alpha - 2008-11-08
24746 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
24747 packages (and maybe other packages) noticed by Theo de Raadt, fixes
24748 a smaller security flaw that might allow an attacker to access local
24749 services, adds better defense against DNS poisoning attacks on exit
24750 relays, further improves hidden service performance, and fixes a
24751 variety of other issues.
24754 - The "ClientDNSRejectInternalAddresses" config option wasn't being
24755 consistently obeyed: if an exit relay refuses a stream because its
24756 exit policy doesn't allow it, we would remember what IP address
24757 the relay said the destination address resolves to, even if it's
24758 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
24759 - The "User" and "Group" config options did not clear the
24760 supplementary group entries for the Tor process. The "User" option
24761 is now more robust, and we now set the groups to the specified
24762 user's primary group. The "Group" option is now ignored. For more
24763 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
24764 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
24765 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
24766 - Do not use or believe expired v3 authority certificates. Patch
24767 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
24770 - Now NodeFamily and MyFamily config options allow spaces in
24771 identity fingerprints, so it's easier to paste them in.
24772 Suggested by Lucky Green.
24773 - Implement the 0x20 hack to better resist DNS poisoning: set the
24774 case on outgoing DNS requests randomly, and reject responses that do
24775 not match the case correctly. This logic can be disabled with the
24776 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
24777 of servers that do not reliably preserve case in replies. See
24778 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
24780 - Preserve case in replies to DNSPort requests in order to support
24781 the 0x20 hack for resisting DNS poisoning attacks.
24783 o Hidden service performance improvements:
24784 - When the client launches an introduction circuit, retry with a
24785 new circuit after 30 seconds rather than 60 seconds.
24786 - Launch a second client-side introduction circuit in parallel
24787 after a delay of 15 seconds (based on work by Christian Wilms).
24788 - Hidden services start out building five intro circuits rather
24789 than three, and when the first three finish they publish a service
24790 descriptor using those. Now we publish our service descriptor much
24791 faster after restart.
24794 - Minor fix in the warning messages when you're having problems
24795 bootstrapping; also, be more forgiving of bootstrap problems when
24796 we're still making incremental progress on a given bootstrap phase.
24797 - When we're choosing an exit node for a circuit, and we have
24798 no pending streams, choose a good general exit rather than one that
24799 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
24800 - Send a valid END cell back when a client tries to connect to a
24801 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
24802 840. Patch from rovv.
24803 - If a broken client asks a non-exit router to connect somewhere,
24804 do not even do the DNS lookup before rejecting the connection.
24805 Fixes another case of bug 619. Patch from rovv.
24806 - Fix another case of assuming, when a specific exit is requested,
24807 that we know more than the user about what hosts it allows.
24808 Fixes another case of bug 752. Patch from rovv.
24809 - Check which hops rendezvous stream cells are associated with to
24810 prevent possible guess-the-streamid injection attacks from
24811 intermediate hops. Fixes another case of bug 446. Based on patch
24813 - Avoid using a negative right-shift when comparing 32-bit
24814 addresses. Possible fix for bug 845 and bug 811.
24815 - Make the assert_circuit_ok() function work correctly on circuits that
24816 have already been marked for close.
24817 - Fix read-off-the-end-of-string error in unit tests when decoding
24818 introduction points.
24819 - Fix uninitialized size field for memory area allocation: may improve
24820 memory performance during directory parsing.
24821 - Treat duplicate certificate fetches as failures, so that we do
24822 not try to re-fetch an expired certificate over and over and over.
24823 - Do not say we're fetching a certificate when we'll in fact skip it
24824 because of a pending download.
24827 Changes in version 0.2.1.6-alpha - 2008-09-30
24828 Tor 0.2.1.6-alpha further improves performance and robustness of
24829 hidden services, starts work on supporting per-country relay selection,
24830 and fixes a variety of smaller issues.
24833 - Implement proposal 121: make it possible to build hidden services
24834 that only certain clients are allowed to connect to. This is
24835 enforced at several points, so that unauthorized clients are unable
24836 to send INTRODUCE cells to the service, or even (depending on the
24837 type of authentication) to learn introduction points. This feature
24838 raises the bar for certain kinds of active attacks against hidden
24839 services. Code by Karsten Loesing.
24840 - Relays now store and serve v2 hidden service descriptors by default,
24841 i.e., the new default value for HidServDirectoryV2 is 1. This is
24842 the last step in proposal 114, which aims to make hidden service
24843 lookups more reliable.
24844 - Start work to allow node restrictions to include country codes. The
24845 syntax to exclude nodes in a country with country code XX is
24846 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
24847 refinement to decide what config options should take priority if
24848 you ask to both use a particular node and exclude it.
24849 - Allow ExitNodes list to include IP ranges and country codes, just
24850 like the Exclude*Nodes lists. Patch from Robert Hogan.
24853 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
24854 Tor to fail to start if you had it configured to use a bridge
24855 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
24856 - When extending a circuit to a hidden service directory to upload a
24857 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
24858 requests failed, because the router descriptor had not been
24859 downloaded yet. In these cases, we now wait until the router
24860 descriptor is downloaded, and then retry. Likewise, clients
24861 now skip over a hidden service directory if they don't yet have
24862 its router descriptor, rather than futilely requesting it and
24863 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
24865 - When fetching v0 and v2 rendezvous service descriptors in parallel,
24866 we were failing the whole hidden service request when the v0
24867 descriptor fetch fails, even if the v2 fetch is still pending and
24868 might succeed. Similarly, if the last v2 fetch fails, we were
24869 failing the whole hidden service request even if a v0 fetch is
24870 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
24871 - DNS replies need to have names matching their requests, but
24872 these names should be in the questions section, not necessarily
24873 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
24876 - Update to the "September 1 2008" ip-to-country file.
24877 - Allow ports 465 and 587 in the default exit policy again. We had
24878 rejected them in 0.1.0.15, because back in 2005 they were commonly
24879 misconfigured and ended up as spam targets. We hear they are better
24880 locked down these days.
24881 - Use a lockfile to make sure that two Tor processes are not
24882 simultaneously running with the same datadir.
24883 - Serve the latest v3 networkstatus consensus via the control
24884 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
24885 - Better logging about stability/reliability calculations on directory
24887 - Drop the requirement to have an open dir port for storing and
24888 serving v2 hidden service descriptors.
24889 - Directory authorities now serve a /tor/dbg-stability.txt URL to
24890 help debug WFU and MTBF calculations.
24891 - Implement most of Proposal 152: allow specialized servers to permit
24892 single-hop circuits, and clients to use those servers to build
24893 single-hop circuits when using a specialized controller. Patch
24894 from Josh Albrecht. Resolves feature request 768.
24895 - Add a -p option to tor-resolve for specifying the SOCKS port: some
24896 people find host:port too confusing.
24897 - Make TrackHostExit mappings expire a while after their last use, not
24898 after their creation. Patch from Robert Hogan.
24899 - Provide circuit purposes along with circuit events to the controller.
24902 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
24904 - Fixed some memory leaks -- some quite frequent, some almost
24905 impossible to trigger -- based on results from Coverity.
24906 - When testing for libevent functions, set the LDFLAGS variable
24907 correctly. Found by Riastradh.
24908 - Fix an assertion bug in parsing policy-related options; possible fix
24910 - Catch and report a few more bootstrapping failure cases when Tor
24911 fails to establish a TCP connection. Cleanup on 0.2.1.x.
24912 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
24913 bootstrapping with tunneled directory connections. Bugfix on
24914 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
24915 - When asked to connect to A.B.exit:80, if we don't know the IP for A
24916 and we know that server B rejects most-but-not all connections to
24917 port 80, we would previously reject the connection. Now, we assume
24918 the user knows what they were asking for. Fixes bug 752. Bugfix
24919 on 0.0.9rc5. Diagnosed by BarkerJr.
24920 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
24921 service directories if they have no advertised dir port. Bugfix
24923 - If we overrun our per-second write limits a little, count this as
24924 having used up our write allocation for the second, and choke
24925 outgoing directory writes. Previously, we had only counted this when
24926 we had met our limits precisely. Fixes bug 824. Patch by rovv.
24927 Bugfix on 0.2.0.x (??).
24928 - Avoid a "0 divided by 0" calculation when calculating router uptime
24929 at directory authorities. Bugfix on 0.2.0.8-alpha.
24930 - Make DNS resolved controller events into "CLOSED", not
24931 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
24933 - Fix a bug where an unreachable relay would establish enough
24934 reachability testing circuits to do a bandwidth test -- if
24935 we already have a connection to the middle hop of the testing
24936 circuit, then it could establish the last hop by using the existing
24937 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
24938 circuits no longer use entry guards in 0.2.1.3-alpha.
24939 - If we have correct permissions on $datadir, we complain to stdout
24940 and fail to start. But dangerous permissions on
24941 $datadir/cached-status/ would cause us to open a log and complain
24942 there. Now complain to stdout and fail to start in both cases. Fixes
24943 bug 820, reported by seeess.
24944 - Remove the old v2 directory authority 'lefkada' from the default
24945 list. It has been gone for many months.
24947 o Code simplifications and refactoring:
24948 - Revise the connection_new functions so that a more typesafe variant
24949 exists. This will work better with Coverity, and let us find any
24950 actual mistakes we're making here.
24951 - Refactor unit testing logic so that dmalloc can be used sensibly
24952 with unit tests to check for memory leaks.
24953 - Move all hidden-service related fields from connection and circuit
24954 structure to substructures: this way they won't eat so much memory.
24957 Changes in version 0.2.0.31 - 2008-09-03
24958 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
24959 a big bug we're seeing where in rare cases traffic from one Tor stream
24960 gets mixed into another stream, and fixes a variety of smaller issues.
24963 - Make sure that two circuits can never exist on the same connection
24964 with the same circuit ID, even if one is marked for close. This
24965 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
24966 - Relays now reject risky extend cells: if the extend cell includes
24967 a digest of all zeroes, or asks to extend back to the relay that
24968 sent the extend cell, tear down the circuit. Ideas suggested
24970 - If not enough of our entry guards are available so we add a new
24971 one, we might use the new one even if it overlapped with the
24972 current circuit's exit relay (or its family). Anonymity bugfix
24973 pointed out by rovv.
24976 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
24977 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
24978 - Correctly detect the presence of the linux/netfilter_ipv4.h header
24979 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
24980 - Pick size of default geoip filename string correctly on windows.
24981 Fixes bug 806. Bugfix on 0.2.0.30.
24982 - Make the autoconf script accept the obsolete --with-ssl-dir
24983 option as an alias for the actually-working --with-openssl-dir
24984 option. Fix the help documentation to recommend --with-openssl-dir.
24985 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
24986 - When using the TransPort option on OpenBSD, and using the User
24987 option to change UID and drop privileges, make sure to open
24988 /dev/pf before dropping privileges. Fixes bug 782. Patch from
24989 Christopher Davis. Bugfix on 0.1.2.1-alpha.
24990 - Try to attach connections immediately upon receiving a RENDEZVOUS2
24991 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
24992 on the client side when connecting to a hidden service. Bugfix
24993 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
24994 - When closing an application-side connection because its circuit is
24995 getting torn down, generate the stream event correctly. Bugfix on
24996 0.1.2.x. Anonymous patch.
24999 Changes in version 0.2.1.5-alpha - 2008-08-31
25000 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
25001 in a lot of the infrastructure for adding authorization to hidden
25002 services, lays the groundwork for having clients read their load
25003 balancing information out of the networkstatus consensus rather than
25004 the individual router descriptors, addresses two potential anonymity
25005 issues, and fixes a variety of smaller issues.
25008 - Convert many internal address representations to optionally hold
25010 - Generate and accept IPv6 addresses in many protocol elements.
25011 - Make resolver code handle nameservers located at ipv6 addresses.
25012 - Begin implementation of proposal 121 ("Client authorization for
25013 hidden services"): configure hidden services with client
25014 authorization, publish descriptors for them, and configure
25015 authorization data for hidden services at clients. The next
25016 step is to actually access hidden services that perform client
25018 - More progress toward proposal 141: Network status consensus
25019 documents and votes now contain bandwidth information for each
25020 router and a summary of that router's exit policy. Eventually this
25021 will be used by clients so that they do not have to download every
25022 known descriptor before building circuits.
25024 o Major bugfixes (on 0.2.0.x and before):
25025 - When sending CREATED cells back for a given circuit, use a 64-bit
25026 connection ID to find the right connection, rather than an addr:port
25027 combination. Now that we can have multiple OR connections between
25028 the same ORs, it is no longer possible to use addr:port to uniquely
25029 identify a connection.
25030 - Relays now reject risky extend cells: if the extend cell includes
25031 a digest of all zeroes, or asks to extend back to the relay that
25032 sent the extend cell, tear down the circuit. Ideas suggested
25034 - If not enough of our entry guards are available so we add a new
25035 one, we might use the new one even if it overlapped with the
25036 current circuit's exit relay (or its family). Anonymity bugfix
25037 pointed out by rovv.
25040 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
25041 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
25042 - When using the TransPort option on OpenBSD, and using the User
25043 option to change UID and drop privileges, make sure to open /dev/pf
25044 before dropping privileges. Fixes bug 782. Patch from Christopher
25045 Davis. Bugfix on 0.1.2.1-alpha.
25046 - Correctly detect the presence of the linux/netfilter_ipv4.h header
25047 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
25048 - Add a missing safe_str() call for a debug log message.
25049 - Use 64 bits instead of 32 bits for connection identifiers used with
25050 the controller protocol, to greatly reduce risk of identifier reuse.
25051 - Make the autoconf script accept the obsolete --with-ssl-dir
25052 option as an alias for the actually-working --with-openssl-dir
25053 option. Fix the help documentation to recommend --with-openssl-dir.
25054 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
25057 - Rate-limit too-many-sockets messages: when they happen, they happen
25058 a lot. Resolves bug 748.
25059 - Resist DNS poisoning a little better by making sure that names in
25060 answer sections match.
25061 - Print the SOCKS5 error message string as well as the error code
25062 when a tor-resolve request fails. Patch from Jacob.
25065 Changes in version 0.2.1.4-alpha - 2008-08-04
25066 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
25069 - The address part of exit policies was not correctly written
25070 to router descriptors. This generated router descriptors that failed
25071 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
25073 - Tor triggered a false assert when extending a circuit to a relay
25074 but we already have a connection open to that relay. Noticed by
25075 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
25078 - Fix a hidden service logging bug: in some edge cases, the router
25079 descriptor of a previously picked introduction point becomes
25080 obsolete and we need to give up on it rather than continually
25081 complaining that it has become obsolete. Observed by xiando. Bugfix
25084 o Removed features:
25085 - Take out the TestVia config option, since it was a workaround for
25086 a bug that was fixed in Tor 0.1.1.21.
25089 Changes in version 0.2.1.3-alpha - 2008-08-03
25090 Tor 0.2.1.3-alpha implements most of the pieces to prevent
25091 infinite-length circuit attacks (see proposal 110); fixes a bug that
25092 might cause exit relays to corrupt streams they send back; allows
25093 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
25094 ExcludeExitNodes config options; and fixes a big pile of bugs.
25096 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
25097 - Send a bootstrap problem "warn" event on the first problem if the
25098 reason is NO_ROUTE (that is, our network is down).
25101 - Implement most of proposal 110: The first K cells to be sent
25102 along a circuit are marked as special "early" cells; only K "early"
25103 cells will be allowed. Once this code is universal, we can block
25104 certain kinds of DOS attack by requiring that EXTEND commands must
25105 be sent using an "early" cell.
25108 - Try to attach connections immediately upon receiving a RENDEZVOUS2
25109 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
25110 on the client side when connecting to a hidden service. Bugfix
25111 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
25112 - Ensure that two circuits can never exist on the same connection
25113 with the same circuit ID, even if one is marked for close. This
25114 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
25117 - When relays do their initial bandwidth measurement, don't limit
25118 to just our entry guards for the test circuits. Otherwise we tend
25119 to have multiple test circuits going through a single entry guard,
25120 which makes our bandwidth test less accurate. Fixes part of bug 654;
25121 patch contributed by Josh Albrecht.
25122 - Add an ExcludeExitNodes option so users can list a set of nodes
25123 that should be be excluded from the exit node position, but
25124 allowed elsewhere. Implements proposal 151.
25125 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
25126 ExcludeNodes and ExcludeExitNodes lists.
25127 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
25128 be more efficient. Formerly it was quadratic in the number of
25129 servers; now it should be linear. Fixes bug 509.
25130 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
25131 and n_conn_id_digest fields into a separate structure that's
25132 only needed when the circuit has not yet attached to an n_conn.
25135 - Change the contrib/tor.logrotate script so it makes the new
25136 logs as "_tor:_tor" rather than the default, which is generally
25137 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
25138 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
25139 warnings (occasionally), but it can also cause the compiler to
25140 eliminate error-checking code. Suggested by Peter Gutmann.
25141 - When a hidden service is giving up on an introduction point candidate
25142 that was not included in the last published rendezvous descriptor,
25143 don't reschedule publication of the next descriptor. Fixes bug 763.
25145 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
25146 HiddenServiceExcludeNodes as obsolete: they never worked properly,
25147 and nobody claims to be using them. Fixes bug 754. Bugfix on
25148 0.1.0.1-rc. Patch from Christian Wilms.
25149 - Fix a small alignment and memory-wasting bug on buffer chunks.
25152 o Minor bugfixes (controller):
25153 - When closing an application-side connection because its circuit
25154 is getting torn down, generate the stream event correctly.
25155 Bugfix on 0.1.2.x. Anonymous patch.
25157 o Removed features:
25158 - Remove all backward-compatibility code to support relays running
25159 versions of Tor so old that they no longer work at all on the
25163 Changes in version 0.2.0.30 - 2008-07-15
25165 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
25166 warnings (occasionally), but it can also cause the compiler to
25167 eliminate error-checking code. Suggested by Peter Gutmann.
25170 Changes in version 0.2.0.29-rc - 2008-07-08
25171 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
25172 hidden-service performance bugs, and fixes a bunch of smaller bugs.
25175 - If you have more than one bridge but don't know their keys,
25176 you would only launch a request for the descriptor of the first one
25177 on your list. (Tor considered launching requests for the others, but
25178 found that it already had a connection on the way for $0000...0000
25179 so it didn't open another.) Bugfix on 0.2.0.x.
25180 - If you have more than one bridge but don't know their keys, and the
25181 connection to one of the bridges failed, you would cancel all
25182 pending bridge connections. (After all, they all have the same
25183 digest.) Bugfix on 0.2.0.x.
25184 - When a hidden service was trying to establish an introduction point,
25185 and Tor had built circuits preemptively for such purposes, we
25186 were ignoring all the preemptive circuits and launching a new one
25187 instead. Bugfix on 0.2.0.14-alpha.
25188 - When a hidden service was trying to establish an introduction point,
25189 and Tor *did* manage to reuse one of the preemptively built
25190 circuits, it didn't correctly remember which one it used,
25191 so it asked for another one soon after, until there were no
25192 more preemptive circuits, at which point it launched one from
25193 scratch. Bugfix on 0.0.9.x.
25194 - Make directory servers include the X-Your-Address-Is: http header in
25195 their responses even for begin_dir conns. Now clients who only
25196 ever use begin_dir connections still have a way to learn their IP
25197 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
25200 - Fix a macro/CPP interaction that was confusing some compilers:
25201 some GCCs don't like #if/#endif pairs inside macro arguments.
25203 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
25204 Fixes bug 704; fix from Steven Murdoch.
25205 - When opening /dev/null in finish_daemonize(), do not pass the
25206 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
25207 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
25208 - Correctly detect transparent proxy support on Linux hosts that
25209 require in.h to be included before netfilter_ipv4.h. Patch
25211 - Disallow session resumption attempts during the renegotiation
25212 stage of the v2 handshake protocol. Clients should never be trying
25213 session resumption at this point, but apparently some did, in
25214 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
25215 found by Geoff Goodell.
25218 Changes in version 0.2.1.2-alpha - 2008-06-20
25219 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
25220 make it easier to set up your own private Tor network; fixes several
25221 big bugs with using more than one bridge relay; fixes a big bug with
25222 offering hidden services quickly after Tor starts; and uses a better
25223 API for reporting potential bootstrapping problems to the controller.
25226 - New TestingTorNetwork config option to allow adjustment of
25227 previously constant values that, while reasonable, could slow
25228 bootstrapping. Implements proposal 135. Patch from Karsten.
25231 - If you have more than one bridge but don't know their digests,
25232 you would only learn a request for the descriptor of the first one
25233 on your list. (Tor considered launching requests for the others, but
25234 found that it already had a connection on the way for $0000...0000
25235 so it didn't open another.) Bugfix on 0.2.0.x.
25236 - If you have more than one bridge but don't know their digests,
25237 and the connection to one of the bridges failed, you would cancel
25238 all pending bridge connections. (After all, they all have the
25239 same digest.) Bugfix on 0.2.0.x.
25240 - When establishing a hidden service, introduction points that
25241 originate from cannibalized circuits are completely ignored and not
25242 included in rendezvous service descriptors. This might be another
25243 reason for delay in making a hidden service available. Bugfix
25244 from long ago (0.0.9.x?)
25247 - Allow OpenSSL to use dynamic locks if it wants.
25248 - When building a consensus, do not include routers that are down.
25249 This will cut down 30% to 40% on consensus size. Implements
25251 - In directory authorities' approved-routers files, allow
25252 fingerprints with or without space.
25253 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
25254 controller can query our current bootstrap state in case it attaches
25255 partway through and wants to catch up.
25256 - Send an initial "Starting" bootstrap status event, so we have a
25257 state to start out in.
25260 - Asking for a conditional consensus at .../consensus/<fingerprints>
25261 would crash a dirserver if it did not already have a
25262 consensus. Bugfix on 0.2.1.1-alpha.
25263 - Clean up some macro/CPP interactions: some GCC versions don't like
25264 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
25267 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
25268 - Directory authorities shouldn't complain about bootstrapping
25269 problems just because they do a lot of reachability testing and
25270 some of the connection attempts fail.
25271 - Start sending "count" and "recommendation" key/value pairs in
25272 bootstrap problem status events, so the controller can hear about
25273 problems even before Tor decides they're worth reporting for sure.
25274 - If you're using bridges, generate "bootstrap problem" warnings
25275 as soon as you run out of working bridges, rather than waiting
25276 for ten failures -- which will never happen if you have less than
25278 - If we close our OR connection because there's been a circuit
25279 pending on it for too long, we were telling our bootstrap status
25280 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
25283 Changes in version 0.2.1.1-alpha - 2008-06-13
25284 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
25285 were making the Tor process bloat especially on Linux; makes our TLS
25286 handshake blend in better; sends "bootstrap phase" status events to
25287 the controller, so it can keep the user informed of progress (and
25288 problems) fetching directory information and establishing circuits;
25289 and adds a variety of smaller features.
25292 - More work on making our TLS handshake blend in: modify the list
25293 of ciphers advertised by OpenSSL in client mode to even more
25294 closely resemble a common web browser. We cheat a little so that
25295 we can advertise ciphers that the locally installed OpenSSL doesn't
25297 - Start sending "bootstrap phase" status events to the controller,
25298 so it can keep the user informed of progress fetching directory
25299 information and establishing circuits. Also inform the controller
25300 if we think we're stuck at a particular bootstrap phase. Implements
25302 - Resume using OpenSSL's RAND_poll() for better (and more portable)
25303 cross-platform entropy collection again. We used to use it, then
25304 stopped using it because of a bug that could crash systems that
25305 called RAND_poll when they had a lot of fds open. It looks like the
25306 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
25307 at startup, and to call RAND_poll() when we reseed later only if
25308 we have a non-buggy OpenSSL version.
25311 - When we choose to abandon a new entry guard because we think our
25312 older ones might be better, close any circuits pending on that
25313 new entry guard connection. This fix should make us recover much
25314 faster when our network is down and then comes back. Bugfix on
25315 0.1.2.8-beta; found by lodger.
25317 o Memory fixes and improvements:
25318 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
25319 to avoid unused RAM in buffer chunks and memory pools.
25320 - Speed up parsing and cut down on memory fragmentation by using
25321 stack-style allocations for parsing directory objects. Previously,
25322 this accounted for over 40% of allocations from within Tor's code
25323 on a typical directory cache.
25324 - Use a Bloom filter rather than a digest-based set to track which
25325 descriptors we need to keep around when we're cleaning out old
25326 router descriptors. This speeds up the computation significantly,
25327 and may reduce fragmentation.
25328 - Reduce the default smartlist size from 32 to 16; it turns out that
25329 most smartlists hold around 8-12 elements tops.
25330 - Make dumpstats() log the fullness and size of openssl-internal
25332 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
25333 patch to their OpenSSL, turn it on to save memory on servers. This
25334 patch will (with any luck) get included in a mainline distribution
25336 - Never use OpenSSL compression: it wastes RAM and CPU trying to
25337 compress cells, which are basically all encrypted, compressed,
25341 - Stop reloading the router list from disk for no reason when we
25342 run out of reachable directory mirrors. Once upon a time reloading
25343 it would set the 'is_running' flag back to 1 for them. It hasn't
25344 done that for a long time.
25345 - In very rare situations new hidden service descriptors were
25346 published earlier than 30 seconds after the last change to the
25347 service. (We currently think that a hidden service descriptor
25348 that's been stable for 30 seconds is worth publishing.)
25351 - Allow separate log levels to be configured for different logging
25352 domains. For example, this allows one to log all notices, warnings,
25353 or errors, plus all memory management messages of level debug or
25354 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
25355 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
25356 and stop using a warning that had become unfixably verbose under
25358 - New --hush command-line option similar to --quiet. While --quiet
25359 disables all logging to the console on startup, --hush limits the
25360 output to messages of warning and error severity.
25361 - Servers support a new URL scheme for consensus downloads that
25362 allows the client to specify which authorities are trusted.
25363 The server then only sends the consensus if the client will trust
25364 it. Otherwise a 404 error is sent back. Clients use this
25365 new scheme when the server supports it (meaning it's running
25366 0.2.1.1-alpha or later). Implements proposal 134.
25367 - New configure/torrc options (--enable-geoip-stats,
25368 DirRecordUsageByCountry) to record how many IPs we've served
25369 directory info to in each country code, how many status documents
25370 total we've sent to each country code, and what share of the total
25371 directory requests we should expect to see.
25372 - Use the TLS1 hostname extension to more closely resemble browser
25374 - Lots of new unit tests.
25375 - Add a macro to implement the common pattern of iterating through
25376 two parallel lists in lockstep.
25379 Changes in version 0.2.0.28-rc - 2008-06-13
25380 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
25381 performance bug, and fixes a bunch of smaller bugs.
25384 - Fix a bug where, when we were choosing the 'end stream reason' to
25385 put in our relay end cell that we send to the exit relay, Tor
25386 clients on Windows were sometimes sending the wrong 'reason'. The
25387 anonymity problem is that exit relays may be able to guess whether
25388 the client is running Windows, thus helping partition the anonymity
25389 set. Down the road we should stop sending reasons to exit relays,
25390 or otherwise prevent future versions of this bug.
25393 - While setting up a hidden service, some valid introduction circuits
25394 were overlooked and abandoned. This might be the reason for
25395 the long delay in making a hidden service available. Bugfix on
25399 - Update to the "June 9 2008" ip-to-country file.
25400 - Run 'make test' as part of 'make dist', so we stop releasing so
25401 many development snapshots that fail their unit tests.
25404 - When we're checking if we have enough dir info for each relay
25405 to begin establishing circuits, make sure that we actually have
25406 the descriptor listed in the consensus, not just any descriptor.
25408 - Bridge relays no longer print "xx=0" in their extrainfo document
25409 for every single country code in the geoip db. Bugfix on
25411 - Only warn when we fail to load the geoip file if we were planning to
25412 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
25413 - If we change our MaxAdvertisedBandwidth and then reload torrc,
25414 Tor won't realize it should publish a new relay descriptor. Fixes
25415 bug 688, reported by mfr. Bugfix on 0.1.2.x.
25416 - When we haven't had any application requests lately, don't bother
25417 logging that we have expired a bunch of descriptors. Bugfix
25419 - Make relay cells written on a connection count as non-padding when
25420 tracking how long a connection has been in use. Bugfix on
25421 0.2.0.1-alpha. Spotted by lodger.
25422 - Fix unit tests in 0.2.0.27-rc.
25423 - Fix compile on Windows.
25426 Changes in version 0.2.0.27-rc - 2008-06-03
25427 Tor 0.2.0.27-rc adds a few features we left out of the earlier
25428 release candidates. In particular, we now include an IP-to-country
25429 GeoIP database, so controllers can easily look up what country a
25430 given relay is in, and so bridge relays can give us some sanitized
25431 summaries about which countries are making use of bridges. (See proposal
25432 126-geoip-fetching.txt for details.)
25435 - Include an IP-to-country GeoIP file in the tarball, so bridge
25436 relays can report sanitized summaries of the usage they're seeing.
25439 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
25440 Robert Hogan. Fixes the first part of bug 681.
25441 - Make bridge authorities never serve extrainfo docs.
25442 - Add support to detect Libevent versions in the 1.4.x series
25444 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
25445 - Include a new contrib/tor-exit-notice.html file that exit relay
25446 operators can put on their website to help reduce abuse queries.
25449 - When tunneling an encrypted directory connection, and its first
25450 circuit fails, do not leave it unattached and ask the controller
25451 to deal. Fixes the second part of bug 681.
25452 - Make bridge authorities correctly expire old extrainfo documents
25456 Changes in version 0.2.0.26-rc - 2008-05-13
25457 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
25458 in Debian's OpenSSL packages. All users running any 0.2.0.x version
25459 should upgrade, whether they're running Debian or not.
25461 o Major security fixes:
25462 - Use new V3 directory authority keys on the tor26, gabelmoo, and
25463 moria1 V3 directory authorities. The old keys were generated with
25464 a vulnerable version of Debian's OpenSSL package, and must be
25465 considered compromised. Other authorities' keys were not generated
25466 with an affected version of OpenSSL.
25469 - List authority signatures as "unrecognized" based on DirServer
25470 lines, not on cert cache. Bugfix on 0.2.0.x.
25473 - Add a new V3AuthUseLegacyKey option to make it easier for
25474 authorities to change their identity keys if they have to.
25477 Changes in version 0.2.0.25-rc - 2008-04-23
25478 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
25481 - Remember to initialize threading before initializing logging.
25482 Otherwise, many BSD-family implementations will crash hard on
25483 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
25486 - Authorities correctly free policies on bad servers on
25487 exit. Fixes bug 672. Bugfix on 0.2.0.x.
25490 Changes in version 0.2.0.24-rc - 2008-04-22
25491 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
25492 v3 directory authority, makes relays with dynamic IP addresses and no
25493 DirPort notice more quickly when their IP address changes, fixes a few
25494 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
25496 o New directory authorities:
25497 - Take lefkada out of the list of v3 directory authorities, since
25498 it has been down for months.
25499 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
25503 - Detect address changes more quickly on non-directory mirror
25504 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
25506 o Minor features (security):
25507 - Reject requests for reverse-dns lookup of names that are in
25508 a private address space. Patch from lodger.
25509 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
25512 o Minor bugfixes (crashes):
25513 - Avoid a rare assert that can trigger when Tor doesn't have much
25514 directory information yet and it tries to fetch a v2 hidden
25515 service descriptor. Fixes bug 651, reported by nwf.
25516 - Initialize log mutex before initializing dmalloc. Otherwise,
25517 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
25518 - Use recursive pthread mutexes in order to avoid deadlock when
25519 logging debug-level messages to a controller. Bug spotted by nwf,
25520 bugfix on 0.2.0.16-alpha.
25522 o Minor bugfixes (resource management):
25523 - Keep address policies from leaking memory: start their refcount
25524 at 1, not 2. Bugfix on 0.2.0.16-alpha.
25525 - Free authority certificates on exit, so they don't look like memory
25526 leaks. Bugfix on 0.2.0.19-alpha.
25527 - Free static hashtables for policy maps and for TLS connections on
25528 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
25529 - Avoid allocating extra space when computing consensuses on 64-bit
25530 platforms. Bug spotted by aakova.
25532 o Minor bugfixes (misc):
25533 - Do not read the configuration file when we've only been told to
25534 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
25535 based on patch from Sebastian Hahn.
25536 - Exit relays that are used as a client can now reach themselves
25537 using the .exit notation, rather than just launching an infinite
25538 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
25539 - When attempting to open a logfile fails, tell us why.
25540 - Fix a dumb bug that was preventing us from knowing that we should
25541 preemptively build circuits to handle expected directory requests.
25542 Fixes bug 660. Bugfix on 0.1.2.x.
25543 - Warn less verbosely about clock skew from netinfo cells from
25544 untrusted sources. Fixes bug 663.
25545 - Make controller stream events for DNS requests more consistent,
25546 by adding "new stream" events for DNS requests, and removing
25547 spurious "stream closed" events" for cached reverse resolves.
25548 Patch from mwenge. Fixes bug 646.
25549 - Correctly notify one-hop connections when a circuit build has
25550 failed. Possible fix for bug 669. Found by lodger.
25553 Changes in version 0.2.0.23-rc - 2008-03-24
25554 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
25555 makes bootstrapping faster if the first directory mirror you contact
25556 is down. The bundles also include the new Vidalia 0.1.2 release.
25559 - When a tunneled directory request is made to a directory server
25560 that's down, notice after 30 seconds rather than 120 seconds. Also,
25561 fail any begindir streams that are pending on it, so they can
25562 retry elsewhere. This was causing multi-minute delays on bootstrap.
25565 Changes in version 0.2.0.22-rc - 2008-03-18
25566 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
25567 enables encrypted directory connections by default for non-relays, fixes
25568 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
25569 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
25572 - Enable encrypted directory connections by default for non-relays,
25573 so censor tools that block Tor directory connections based on their
25574 plaintext patterns will no longer work. This means Tor works in
25575 certain censored countries by default again.
25578 - Make sure servers always request certificates from clients during
25579 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
25580 - Do not enter a CPU-eating loop when a connection is closed in
25581 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
25582 diagnosed by lodger; bugfix on 0.2.0.20-rc.
25583 - Fix assertion failure that could occur when a blocked circuit
25584 became unblocked, and it had pending client DNS requests. Bugfix
25585 on 0.2.0.1-alpha. Fixes bug 632.
25587 o Minor bugfixes (on 0.1.2.x):
25588 - Generate "STATUS_SERVER" events rather than misspelled
25589 "STATUS_SEVER" events. Caught by mwenge.
25590 - When counting the number of bytes written on a TLS connection,
25591 look at the BIO actually used for writing to the network, not
25592 at the BIO used (sometimes) to buffer data for the network.
25593 Looking at different BIOs could result in write counts on the
25594 order of ULONG_MAX. Fixes bug 614.
25595 - On Windows, correctly detect errors when listing the contents of
25596 a directory. Fix from lodger.
25598 o Minor bugfixes (on 0.2.0.x):
25599 - Downgrade "sslv3 alert handshake failure" message to INFO.
25600 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
25601 left BandwidthRate and BandwidthBurst at the default, we would be
25602 silently limited by those defaults. Now raise them to match the
25603 RelayBandwidth* values.
25604 - Fix the SVK version detection logic to work correctly on a branch.
25605 - Make --enable-openbsd-malloc work correctly on Linux with alpha
25606 CPUs. Fixes bug 625.
25607 - Logging functions now check that the passed severity is sane.
25608 - Use proper log levels in the testsuite call of
25609 get_interface_address6().
25610 - When using a nonstandard malloc, do not use the platform values for
25611 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
25612 - Make the openbsd malloc code use 8k pages on alpha CPUs and
25614 - Detect mismatched page sizes when using --enable-openbsd-malloc.
25615 - Avoid double-marked-for-close warning when certain kinds of invalid
25616 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
25617 for bug 617. Bugfix on 0.2.0.1-alpha.
25618 - Make sure that the "NULL-means-reject *:*" convention is followed by
25619 all the policy manipulation functions, avoiding some possible crash
25620 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
25621 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
25622 actually works, and doesn't warn about every single reverse lookup.
25623 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
25626 - Only log guard node status when guard node status has changed.
25627 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
25628 make "INFO" 75% less verbose.
25631 Changes in version 0.2.0.21-rc - 2008-03-02
25632 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
25633 makes Tor work well with Vidalia again, fixes a rare assert bug,
25634 and fixes a pair of more minor bugs. The bundles also include Vidalia
25635 0.1.0 and Torbutton 1.1.16.
25638 - The control port should declare that it requires password auth
25639 when HashedControlSessionPassword is set too. Patch from Matt Edman;
25640 bugfix on 0.2.0.20-rc. Fixes bug 615.
25641 - Downgrade assert in connection_buckets_decrement() to a log message.
25642 This may help us solve bug 614, and in any case will make its
25643 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
25644 - We were sometimes miscounting the number of bytes read from the
25645 network, causing our rate limiting to not be followed exactly.
25646 Bugfix on 0.2.0.16-alpha. Reported by lodger.
25649 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
25650 OpenSSL versions should have been working fine. Diagnosis and patch
25651 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
25652 Bugfix on 0.2.0.20-rc.
25655 Changes in version 0.2.0.20-rc - 2008-02-24
25656 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
25657 makes more progress towards normalizing Tor's TLS handshake, makes
25658 hidden services work better again, helps relays bootstrap if they don't
25659 know their IP address, adds optional support for linking in openbsd's
25660 allocator or tcmalloc, allows really fast relays to scale past 15000
25661 sockets, and fixes a bunch of minor bugs reported by Veracode.
25664 - Enable the revised TLS handshake based on the one designed by
25665 Steven Murdoch in proposal 124, as revised in proposal 130. It
25666 includes version negotiation for OR connections as described in
25667 proposal 105. The new handshake is meant to be harder for censors
25668 to fingerprint, and it adds the ability to detect certain kinds of
25669 man-in-the-middle traffic analysis attacks. The version negotiation
25670 feature will allow us to improve Tor's link protocol more safely
25672 - Choose which bridge to use proportional to its advertised bandwidth,
25673 rather than uniformly at random. This should speed up Tor for
25674 bridge users. Also do this for people who set StrictEntryNodes.
25675 - When a TrackHostExits-chosen exit fails too many times in a row,
25676 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
25679 - Resolved problems with (re-)fetching hidden service descriptors.
25680 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
25681 and 0.2.0.19-alpha.
25682 - If we only ever used Tor for hidden service lookups or posts, we
25683 would stop building circuits and start refusing connections after
25684 24 hours, since we falsely believed that Tor was dormant. Reported
25685 by nwf; bugfix on 0.1.2.x.
25686 - Servers that don't know their own IP address should go to the
25687 authorities for their first directory fetch, even if their DirPort
25688 is off or if they don't know they're reachable yet. This will help
25689 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
25690 - When counting the number of open sockets, count not only the number
25691 of sockets we have received from the socket() call, but also
25692 the number we've gotten from accept() and socketpair(). This bug
25693 made us fail to count all sockets that we were using for incoming
25694 connections. Bugfix on 0.2.0.x.
25695 - Fix code used to find strings within buffers, when those strings
25696 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
25697 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
25698 - Add a new __HashedControlSessionPassword option for controllers
25699 to use for one-off session password hashes that shouldn't get
25700 saved to disk by SAVECONF --- Vidalia users were accumulating a
25701 pile of HashedControlPassword lines in their torrc files, one for
25702 each time they had restarted Tor and then clicked Save. Make Tor
25703 automatically convert "HashedControlPassword" to this new option but
25704 only when it's given on the command line. Partial fix for bug 586.
25706 o Minor features (performance):
25707 - Tune parameters for cell pool allocation to minimize amount of
25709 - Add OpenBSD malloc code from phk as an optional malloc
25710 replacement on Linux: some glibc libraries do very poorly
25711 with Tor's memory allocation patterns. Pass
25712 --enable-openbsd-malloc to get the replacement malloc code.
25713 - Add a --with-tcmalloc option to the configure script to link
25714 against tcmalloc (if present). Does not yet search for
25715 non-system include paths.
25716 - Stop imposing an arbitrary maximum on the number of file descriptors
25717 used for busy servers. Bug reported by Olaf Selke; patch from
25720 o Minor features (other):
25721 - When SafeLogging is disabled, log addresses along with all TLS
25723 - When building with --enable-gcc-warnings, check for whether Apple's
25724 warning "-Wshorten-64-to-32" is available.
25725 - Add a --passphrase-fd argument to the tor-gencert command for
25728 o Minor bugfixes (memory leaks and code problems):
25729 - We were leaking a file descriptor if Tor started with a zero-length
25730 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
25731 - Detect size overflow in zlib code. Reported by Justin Ferguson and
25733 - We were comparing the raw BridgePassword entry with a base64'ed
25734 version of it, when handling a "/tor/networkstatus-bridges"
25735 directory request. Now compare correctly. Noticed by Veracode.
25736 - Recover from bad tracked-since value in MTBF-history file.
25737 Should fix bug 537.
25738 - Alter the code that tries to recover from unhandled write
25739 errors, to not try to flush onto a socket that's given us
25740 unhandled errors. Bugfix on 0.1.2.x.
25741 - Make Unix controlsockets work correctly on OpenBSD. Patch from
25742 tup. Bugfix on 0.2.0.3-alpha.
25744 o Minor bugfixes (other):
25745 - If we have an extra-info document for our server, always make
25746 it available on the control port, even if we haven't gotten
25747 a copy of it from an authority yet. Patch from mwenge.
25748 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
25749 - Directory mirrors no longer include a guess at the client's IP
25750 address if the connection appears to be coming from the same /24
25751 network; it was producing too many wrong guesses.
25752 - Make the new hidden service code respect the SafeLogging setting.
25753 Bugfix on 0.2.0.x. Patch from Karsten.
25754 - When starting as an authority, do not overwrite all certificates
25755 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
25756 - If we're trying to flush the last bytes on a connection (for
25757 example, when answering a directory request), reset the
25758 time-to-give-up timeout every time we manage to write something
25759 on the socket. Bugfix on 0.1.2.x.
25760 - Change the behavior of "getinfo status/good-server-descriptor"
25761 so it doesn't return failure when any authority disappears.
25762 - Even though the man page said that "TrackHostExits ." should
25763 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
25764 - Report TLS "zero return" case as a "clean close" and "IO error"
25765 as a "close". Stop calling closes "unexpected closes": existing
25766 Tors don't use SSL_close(), so having a connection close without
25767 the TLS shutdown handshake is hardly unexpected.
25768 - Send NAMESERVER_STATUS messages for a single failed nameserver
25771 o Code simplifications and refactoring:
25772 - Remove the tor_strpartition function: its logic was confused,
25773 and it was only used for one thing that could be implemented far
25777 Changes in version 0.2.0.19-alpha - 2008-02-09
25778 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
25779 handshake, makes path selection for relays more secure and IP address
25780 guessing more robust, and generally fixes a lot of bugs in preparation
25781 for calling the 0.2.0 branch stable.
25784 - Do not include recognizeable strings in the commonname part of
25785 Tor's x509 certificates.
25788 - If we're a relay, avoid picking ourselves as an introduction point,
25789 a rendezvous point, or as the final hop for internal circuits. Bug
25790 reported by taranis and lodger. Bugfix on 0.1.2.x.
25791 - Patch from "Andrew S. Lists" to catch when we contact a directory
25792 mirror at IP address X and he says we look like we're coming from
25793 IP address X. Bugfix on 0.1.2.x.
25795 o Minor features (security):
25796 - Be more paranoid about overwriting sensitive memory on free(),
25797 as a defensive programming tactic to ensure forward secrecy.
25799 o Minor features (directory authority):
25800 - Actually validate the options passed to AuthDirReject,
25801 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
25802 - Reject router descriptors with out-of-range bandwidthcapacity or
25803 bandwidthburst values.
25805 o Minor features (controller):
25806 - Reject controller commands over 1MB in length. This keeps rogue
25807 processes from running us out of memory.
25809 o Minor features (misc):
25810 - Give more descriptive well-formedness errors for out-of-range
25811 hidden service descriptor/protocol versions.
25812 - Make memory debugging information describe more about history
25813 of cell allocation, so we can help reduce our memory use.
25815 o Deprecated features (controller):
25816 - The status/version/num-versioning and status/version/num-concurring
25817 GETINFO options are no longer useful in the v3 directory protocol:
25818 treat them as deprecated, and warn when they're used.
25821 - When our consensus networkstatus has been expired for a while, stop
25822 being willing to build circuits using it. Fixes bug 401. Bugfix
25824 - Directory caches now fetch certificates from all authorities
25825 listed in a networkstatus consensus, even when they do not
25826 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
25827 - When connecting to a bridge without specifying its key, insert
25828 the connection into the identity-to-connection map as soon as
25829 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
25830 - Detect versions of OS X where malloc_good_size() is present in the
25831 library but never actually declared. Resolves bug 587. Bugfix
25833 - Stop incorrectly truncating zlib responses to directory authority
25834 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
25835 - Stop recommending that every server operator send mail to tor-ops.
25836 Resolves bug 597. Bugfix on 0.1.2.x.
25837 - Don't trigger an assert if we start a directory authority with a
25838 private IP address (like 127.0.0.1).
25839 - Avoid possible failures when generating a directory with routers
25840 with over-long versions strings, or too many flags set. Bugfix
25842 - If an attempt to launch a DNS resolve request over the control
25843 port fails because we have overrun the limit on the number of
25844 connections, tell the controller that the request has failed.
25845 - Avoid using too little bandwidth when our clock skips a few
25846 seconds. Bugfix on 0.1.2.x.
25847 - Fix shell error when warning about missing packages in configure
25848 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
25849 - Do not become confused when receiving a spurious VERSIONS-like
25850 cell from a confused v1 client. Bugfix on 0.2.0.x.
25851 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
25852 introduction points for a hidden service have failed. Patch from
25853 Karsten Loesing. Bugfix on 0.2.0.x.
25855 o Code simplifications and refactoring:
25856 - Remove some needless generality from cpuworker code, for improved
25858 - Stop overloading the circuit_t.onionskin field for both "onionskin
25859 from a CREATE cell that we are waiting for a cpuworker to be
25860 assigned" and "onionskin from an EXTEND cell that we are going to
25861 send to an OR as soon as we are connected". Might help with bug 600.
25862 - Add an in-place version of aes_crypt() so that we can avoid doing a
25863 needless memcpy() call on each cell payload.
25866 Changes in version 0.2.0.18-alpha - 2008-01-25
25867 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
25868 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
25869 that can warn or reject connections to ports generally associated with
25870 vulnerable-plaintext protocols.
25872 o New directory authorities:
25873 - Set up dannenberg (run by CCC) as the sixth v3 directory
25877 - Fix a major memory leak when attempting to use the v2 TLS
25878 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
25879 - We accidentally enabled the under-development v2 TLS handshake
25880 code, which was causing log entries like "TLS error while
25881 renegotiating handshake". Disable it again. Resolves bug 590.
25882 - We were computing the wrong Content-Length: header for directory
25883 responses that need to be compressed on the fly, causing clients
25884 asking for those items to always fail. Bugfix on 0.2.0.x; partially
25888 - Avoid going directly to the directory authorities even if you're a
25889 relay, if you haven't found yourself reachable yet or if you've
25890 decided not to advertise your dirport yet. Addresses bug 556.
25891 - If we've gone 12 hours since our last bandwidth check, and we
25892 estimate we have less than 50KB bandwidth capacity but we could
25893 handle more, do another bandwidth test.
25894 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
25895 Tor can warn and/or refuse connections to ports commonly used with
25896 vulnerable-plaintext protocols. Currently we warn on ports 23,
25897 109, 110, and 143, but we don't reject any.
25900 - When we setconf ClientOnly to 1, close any current OR and Dir
25901 listeners. Reported by mwenge.
25902 - When we get a consensus that's been signed by more people than
25903 we expect, don't log about it; it's not a big deal. Reported
25907 - Don't answer "/tor/networkstatus-bridges" directory requests if
25908 the request isn't encrypted.
25909 - Make "ClientOnly 1" config option disable directory ports too.
25910 - Patches from Karsten Loesing to make v2 hidden services more
25911 robust: work even when there aren't enough HSDir relays available;
25912 retry when a v2 rend desc fetch fails; but don't retry if we
25913 already have a usable v0 rend desc.
25916 Changes in version 0.2.0.17-alpha - 2008-01-17
25917 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
25920 - Make the tor-gencert man page get included correctly in the tarball.
25923 Changes in version 0.2.0.16-alpha - 2008-01-17
25924 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
25925 Loesing, and generally cleans up a lot of features and minor bugs.
25927 o New directory authorities:
25928 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
25931 o Major performance improvements:
25932 - Switch our old ring buffer implementation for one more like that
25933 used by free Unix kernels. The wasted space in a buffer with 1mb
25934 of data will now be more like 8k than 1mb. The new implementation
25935 also avoids realloc();realloc(); patterns that can contribute to
25936 memory fragmentation.
25939 - Configuration files now accept C-style strings as values. This
25940 helps encode characters not allowed in the current configuration
25941 file format, such as newline or #. Addresses bug 557.
25942 - Although we fixed bug 539 (where servers would send HTTP status 503
25943 responses _and_ send a body too), there are still servers out
25944 there that haven't upgraded. Therefore, make clients parse such
25945 bodies when they receive them.
25946 - When we're not serving v2 directory information, there is no reason
25947 to actually keep any around. Remove the obsolete files and directory
25948 on startup if they are very old and we aren't going to serve them.
25950 o Minor performance improvements:
25951 - Reference-count and share copies of address policy entries; only 5%
25952 of them were actually distinct.
25953 - Never walk through the list of logs if we know that no log is
25954 interested in a given message.
25957 - When an authority has not signed a consensus, do not try to
25958 download a nonexistent "certificate with key 00000000". Bugfix
25959 on 0.2.0.x. Fixes bug 569.
25960 - Fix a rare assert error when we're closing one of our threads:
25961 use a mutex to protect the list of logs, so we never write to the
25962 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
25963 bug 575, which is kind of the revenge of bug 222.
25964 - Patch from Karsten Loesing to complain less at both the client
25965 and the relay when a relay used to have the HSDir flag but doesn't
25966 anymore, and we try to upload a hidden service descriptor.
25967 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
25969 - Do not try to download missing certificates until we have tried
25970 to check our fallback consensus. Fixes bug 583.
25971 - Make bridges round reported GeoIP stats info up to the nearest
25972 estimate, not down. Now we can distinguish between "0 people from
25973 this country" and "1 person from this country".
25974 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
25975 - Avoid possible segfault if key generation fails in
25976 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
25977 - Avoid segfault in the case where a badly behaved v2 versioning
25978 directory sends a signed networkstatus with missing client-versions.
25980 - Avoid segfaults on certain complex invocations of
25981 router_get_by_hexdigest(). Bugfix on 0.1.2.
25982 - Correct bad index on array access in parse_http_time(). Bugfix
25984 - Fix possible bug in vote generation when server versions are present
25985 but client versions are not.
25986 - Fix rare bug on REDIRECTSTREAM control command when called with no
25987 port set: it could erroneously report an error when none had
25989 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
25990 compressing large objects and find ourselves with more than 4k
25991 left over. Bugfix on 0.2.0.
25992 - Fix a small memory leak when setting up a hidden service.
25993 - Fix a few memory leaks that could in theory happen under bizarre
25995 - Fix an assert if we post a general-purpose descriptor via the
25996 control port but that descriptor isn't mentioned in our current
25997 network consensus. Bug reported by Jon McLachlan; bugfix on
26000 o Minor features (controller):
26001 - Get NS events working again. Patch from tup.
26002 - The GETCONF command now escapes and quotes configuration values
26003 that don't otherwise fit into the torrc file.
26004 - The SETCONF command now handles quoted values correctly.
26006 o Minor features (directory authorities):
26007 - New configuration options to override default maximum number of
26008 servers allowed on a single IP address. This is important for
26009 running a test network on a single host.
26010 - Actually implement the -s option to tor-gencert.
26011 - Add a manual page for tor-gencert.
26013 o Minor features (bridges):
26014 - Bridge authorities no longer serve bridge descriptors over
26015 unencrypted connections.
26017 o Minor features (other):
26018 - Add hidden services and DNSPorts to the list of things that make
26019 Tor accept that it has running ports. Change starting Tor with no
26020 ports from a fatal error to a warning; we might change it back if
26021 this turns out to confuse anybody. Fixes bug 579.
26024 Changes in version 0.1.2.19 - 2008-01-17
26025 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
26026 exit policy a little bit more conservative so it's safer to run an
26027 exit relay on a home system, and fixes a variety of smaller issues.
26030 - Exit policies now reject connections that are addressed to a
26031 relay's public (external) IP address too, unless
26032 ExitPolicyRejectPrivate is turned off. We do this because too
26033 many relays are running nearby to services that trust them based
26034 on network address.
26037 - When the clock jumps forward a lot, do not allow the bandwidth
26038 buckets to become negative. Fixes bug 544.
26039 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
26040 on every successful resolve. Reported by Mike Perry.
26041 - Purge old entries from the "rephist" database and the hidden
26042 service descriptor database even when DirPort is zero.
26043 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
26044 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
26045 crashing or mis-answering these requests.
26046 - When we decide to send a 503 response to a request for servers, do
26047 not then also send the server descriptors: this defeats the whole
26048 purpose. Fixes bug 539.
26051 - Changing the ExitPolicyRejectPrivate setting should cause us to
26052 rebuild our server descriptor.
26053 - Fix handling of hex nicknames when answering controller requests for
26054 networkstatus by name, or when deciding whether to warn about
26055 unknown routers in a config option. (Patch from mwenge.)
26056 - Fix a couple of hard-to-trigger autoconf problems that could result
26057 in really weird results on platforms whose sys/types.h files define
26058 nonstandard integer types.
26059 - Don't try to create the datadir when running --verify-config or
26060 --hash-password. Resolves bug 540.
26061 - If we were having problems getting a particular descriptor from the
26062 directory caches, and then we learned about a new descriptor for
26063 that router, we weren't resetting our failure count. Reported
26065 - Although we fixed bug 539 (where servers would send HTTP status 503
26066 responses _and_ send a body too), there are still servers out there
26067 that haven't upgraded. Therefore, make clients parse such bodies
26068 when they receive them.
26069 - Run correctly on systems where rlim_t is larger than unsigned long.
26070 This includes some 64-bit systems.
26071 - Run correctly on platforms (like some versions of OS X 10.5) where
26072 the real limit for number of open files is OPEN_FILES, not rlim_max
26073 from getrlimit(RLIMIT_NOFILES).
26074 - Avoid a spurious free on base64 failure.
26075 - Avoid segfaults on certain complex invocations of
26076 router_get_by_hexdigest().
26077 - Fix rare bug on REDIRECTSTREAM control command when called with no
26078 port set: it could erroneously report an error when none had
26082 Changes in version 0.2.0.15-alpha - 2007-12-25
26083 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
26084 features added in 0.2.0.13-alpha.
26087 - Fix several remotely triggerable asserts based on DirPort requests
26088 for a v2 or v3 networkstatus object before we were prepared. This
26089 was particularly bad for 0.2.0.13 and later bridge relays, who
26090 would never have a v2 networkstatus and would thus always crash
26091 when used. Bugfixes on 0.2.0.x.
26092 - Estimate the v3 networkstatus size more accurately, rather than
26093 estimating it at zero bytes and giving it artificially high priority
26094 compared to other directory requests. Bugfix on 0.2.0.x.
26097 - Fix configure.in logic for cross-compilation.
26098 - When we load a bridge descriptor from the cache, and it was
26099 previously unreachable, mark it as retriable so we won't just
26100 ignore it. Also, try fetching a new copy immediately. Bugfixes
26102 - The bridge GeoIP stats were counting other relays, for example
26103 self-reachability and authority-reachability tests.
26106 - Support compilation to target iPhone; patch from cjacker huang.
26107 To build for iPhone, pass the --enable-iphone option to configure.
26110 Changes in version 0.2.0.14-alpha - 2007-12-23
26112 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
26113 without a datadirectory from a previous Tor install. Reported
26115 - Fix a crash when we fetch a descriptor that turns out to be
26116 unexpected (it used to be in our networkstatus when we started
26117 fetching it, but it isn't in our current networkstatus), and we
26118 aren't using bridges. Bugfix on 0.2.0.x.
26119 - Fix a crash when accessing hidden services: it would work the first
26120 time you use a given introduction point for your service, but
26121 on subsequent requests we'd be using garbage memory. Fixed by
26122 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
26123 - Fix a crash when we load a bridge descriptor from disk but we don't
26124 currently have a Bridge line for it in our torrc. Bugfix on
26128 - If bridge authorities set BridgePassword, they will serve a
26129 snapshot of known bridge routerstatuses from their DirPort to
26130 anybody who knows that password. Unset by default.
26133 - Make the unit tests build again.
26134 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
26135 - Make PublishServerDescriptor default to 1, so the default doesn't
26136 have to change as we invent new directory protocol versions.
26137 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
26138 be included unless sys/time.h is already included. Fixes
26139 bug 553. Bugfix on 0.2.0.x.
26140 - If we receive a general-purpose descriptor and then receive an
26141 identical bridge-purpose descriptor soon after, don't discard
26142 the next one as a duplicate.
26145 - If BridgeRelay is set to 1, then the default for
26146 PublishServerDescriptor is now "bridge" rather than "v2,v3".
26147 - If the user sets RelayBandwidthRate but doesn't set
26148 RelayBandwidthBurst, then make them equal rather than erroring out.
26151 Changes in version 0.2.0.13-alpha - 2007-12-21
26152 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
26153 Goodell, fixes many more bugs, and adds a lot of infrastructure for
26156 o New directory authorities:
26157 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
26161 - Only update guard status (usable / not usable) once we have
26162 enough directory information. This was causing us to always pick
26163 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
26164 causing us to discard all our guards on startup if we hadn't been
26165 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
26166 - Purge old entries from the "rephist" database and the hidden
26167 service descriptor databases even when DirPort is zero. Bugfix
26169 - We were ignoring our RelayBandwidthRate for the first 30 seconds
26170 after opening a circuit -- even a relayed circuit. Bugfix on
26172 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
26173 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
26174 crashing or mis-answering these types of requests.
26175 - Relays were publishing their server descriptor to v1 and v2
26176 directory authorities, but they didn't try publishing to v3-only
26177 authorities. Fix this; and also stop publishing to v1 authorities.
26179 - When we were reading router descriptors from cache, we were ignoring
26180 the annotations -- so for example we were reading in bridge-purpose
26181 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
26182 - When we decided to send a 503 response to a request for servers, we
26183 were then also sending the server descriptors: this defeats the
26184 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
26187 - Bridge relays now behave like clients with respect to time
26188 intervals for downloading new consensus documents -- otherwise they
26189 stand out. Bridge users now wait until the end of the interval,
26190 so their bridge relay will be sure to have a new consensus document.
26191 - Three new config options (AlternateDirAuthority,
26192 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
26193 user selectively replace the default directory authorities by type,
26194 rather than the all-or-nothing replacement that DirServer offers.
26195 - Tor can now be configured to read a GeoIP file from disk in one
26196 of two formats. This can be used by controllers to map IP addresses
26197 to countries. Eventually, it may support exit-by-country.
26198 - When possible, bridge relays remember which countries users
26199 are coming from, and report aggregate information in their
26200 extra-info documents, so that the bridge authorities can learn
26201 where Tor is blocked.
26202 - Bridge directory authorities now do reachability testing on the
26203 bridges they know. They provide router status summaries to the
26204 controller via "getinfo ns/purpose/bridge", and also dump summaries
26205 to a file periodically.
26206 - Stop fetching directory info so aggressively if your DirPort is
26207 on but your ORPort is off; stop fetching v2 dir info entirely.
26208 You can override these choices with the new FetchDirInfoEarly
26212 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
26213 consensus documents when there are too many relays at a single
26214 IP address. Now clear it in v2 network status documents too, and
26215 also clear it in routerinfo_t when the relay is no longer listed
26216 in the relevant networkstatus document.
26217 - Don't crash if we get an unexpected value for the
26218 PublishServerDescriptor config option. Reported by Matt Edman;
26219 bugfix on 0.2.0.9-alpha.
26220 - Our new v2 hidden service descriptor format allows descriptors
26221 that have no introduction points. But Tor crashed when we tried
26222 to build a descriptor with no intro points (and it would have
26223 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
26224 by Karsten Loesing.
26225 - Fix building with dmalloc 5.5.2 with glibc.
26226 - Reject uploaded descriptors and extrainfo documents if they're
26227 huge. Otherwise we'll cache them all over the network and it'll
26228 clog everything up. Reported by Aljosha Judmayer.
26229 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
26230 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
26231 - When the DANGEROUS_VERSION controller status event told us we're
26232 running an obsolete version, it used the string "OLD" to describe
26233 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
26234 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
26235 - If we can't expand our list of entry guards (e.g. because we're
26236 using bridges or we have StrictEntryNodes set), don't mark relays
26237 down when they fail a directory request. Otherwise we're too quick
26238 to mark all our entry points down. Bugfix on 0.1.2.x.
26239 - Fix handling of hex nicknames when answering controller requests for
26240 networkstatus by name, or when deciding whether to warn about unknown
26241 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
26242 - Fix a couple of hard-to-trigger autoconf problems that could result
26243 in really weird results on platforms whose sys/types.h files define
26244 nonstandard integer types. Bugfix on 0.1.2.x.
26245 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
26246 - Don't crash on name lookup when we have no current consensus. Fixes
26247 bug 538; bugfix on 0.2.0.x.
26248 - Only Tors that want to mirror the v2 directory info should
26249 create the "cached-status" directory in their datadir. (All Tors
26250 used to create it.) Bugfix on 0.2.0.9-alpha.
26251 - Directory authorities should only automatically download Extra Info
26252 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
26255 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
26256 consumers. (We already do this on HUP.)
26257 - Authorities and caches fetch the v2 networkstatus documents
26258 less often, now that v3 is encouraged.
26259 - Add a new config option BridgeRelay that specifies you want to
26260 be a bridge relay. Right now the only difference is that it makes
26261 you answer begin_dir requests, and it makes you cache dir info,
26262 even if your DirPort isn't on.
26263 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
26264 ask about source, timestamp of arrival, purpose, etc. We need
26265 something like this to help Vidalia not do GeoIP lookups on bridge
26267 - Allow multiple HashedControlPassword config lines, to support
26268 multiple controller passwords.
26269 - Authorities now decide whether they're authoritative for a given
26270 router based on the router's purpose.
26271 - New config options AuthDirBadDir and AuthDirListBadDirs for
26272 authorities to mark certain relays as "bad directories" in the
26273 networkstatus documents. Also supports the "!baddir" directive in
26274 the approved-routers file.
26277 Changes in version 0.2.0.12-alpha - 2007-11-16
26278 This twelfth development snapshot fixes some more build problems as
26279 well as a few minor bugs.
26282 - Make it build on OpenBSD again. Patch from tup.
26283 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
26284 package-building for Red Hat, OS X, etc.
26286 o Minor bugfixes (on 0.1.2.x):
26287 - Changing the ExitPolicyRejectPrivate setting should cause us to
26288 rebuild our server descriptor.
26290 o Minor bugfixes (on 0.2.0.x):
26291 - When we're lacking a consensus, don't try to perform rendezvous
26292 operations. Reported by Karsten Loesing.
26293 - Fix a small memory leak whenever we decide against using a
26294 newly picked entry guard. Reported by Mike Perry.
26295 - When authorities detected more than two relays running on the same
26296 IP address, they were clearing all the status flags but forgetting
26297 to clear the "hsdir" flag. So clients were being told that a
26298 given relay was the right choice for a v2 hsdir lookup, yet they
26299 never had its descriptor because it was marked as 'not running'
26301 - If we're trying to fetch a bridge descriptor and there's no way
26302 the bridge authority could help us (for example, we don't know
26303 a digest, or there is no bridge authority), don't be so eager to
26304 fall back to asking the bridge authority.
26305 - If we're using bridges or have strictentrynodes set, and our
26306 chosen exit is in the same family as all our bridges/entry guards,
26307 then be flexible about families.
26310 - When we negotiate a v2 link-layer connection (not yet implemented),
26311 accept RELAY_EARLY cells and turn them into RELAY cells if we've
26312 negotiated a v1 connection for their next step. Initial code for
26316 Changes in version 0.2.0.11-alpha - 2007-11-12
26317 This eleventh development snapshot fixes some build problems with
26318 the previous snapshot. It also includes a more secure-by-default exit
26319 policy for relays, fixes an enormous memory leak for exit relays, and
26320 fixes another bug where servers were falling out of the directory list.
26323 - Exit policies now reject connections that are addressed to a
26324 relay's public (external) IP address too, unless
26325 ExitPolicyRejectPrivate is turned off. We do this because too
26326 many relays are running nearby to services that trust them based
26327 on network address. Bugfix on 0.1.2.x.
26330 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
26331 on every successful resolve. Reported by Mike Perry; bugfix
26333 - On authorities, never downgrade to old router descriptors simply
26334 because they're listed in the consensus. This created a catch-22
26335 where we wouldn't list a new descriptor because there was an
26336 old one in the consensus, and we couldn't get the new one in the
26337 consensus because we wouldn't list it. Possible fix for bug 548.
26338 Also, this might cause bug 543 to appear on authorities; if so,
26339 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
26341 o Packaging fixes on 0.2.0.10-alpha:
26342 - We were including instructions about what to do with the
26343 src/config/fallback-consensus file, but we weren't actually
26344 including it in the tarball. Disable all of that for now.
26347 - Allow people to say PreferTunnelledDirConns rather than
26348 PreferTunneledDirConns, for those alternate-spellers out there.
26351 - Don't reevaluate all the information from our consensus document
26352 just because we've downloaded a v2 networkstatus that we intend
26353 to cache. Fixes bug 545; bugfix on 0.2.0.x.
26356 Changes in version 0.2.0.10-alpha - 2007-11-10
26357 This tenth development snapshot adds a third v3 directory authority
26358 run by Mike Perry, adds most of Karsten Loesing's new hidden service
26359 descriptor format, fixes a bad crash bug and new bridge bugs introduced
26360 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
26361 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
26362 addresses many more minor issues.
26364 o New directory authorities:
26365 - Set up ides (run by Mike Perry) as the third v3 directory authority.
26368 - Allow tunnelled directory connections to ask for an encrypted
26369 "begin_dir" connection or an anonymized "uses a full Tor circuit"
26370 connection independently. Now we can make anonymized begin_dir
26371 connections for (e.g.) more secure hidden service posting and
26373 - More progress on proposal 114: code from Karsten Loesing to
26374 implement new hidden service descriptor format.
26375 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
26376 accommodate the growing number of servers that use the default
26377 and are reaching it.
26378 - Directory authorities use a new formula for selecting which nodes
26379 to advertise as Guards: they must be in the top 7/8 in terms of
26380 how long we have known about them, and above the median of those
26381 nodes in terms of weighted fractional uptime.
26382 - Make "not enough dir info yet" warnings describe *why* Tor feels
26383 it doesn't have enough directory info yet.
26386 - Stop servers from crashing if they set a Family option (or
26387 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
26389 - Make bridge users work again -- the move to v3 directories in
26390 0.2.0.9-alpha had introduced a number of bugs that made bridges
26391 no longer work for clients.
26392 - When the clock jumps forward a lot, do not allow the bandwidth
26393 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
26395 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
26396 - When the consensus lists a router descriptor that we previously were
26397 mirroring, but that we considered non-canonical, reload the
26398 descriptor as canonical. This fixes bug 543 where Tor servers
26399 would start complaining after a few days that they don't have
26400 enough directory information to build a circuit.
26401 - Consider replacing the current consensus when certificates arrive
26402 that make the pending consensus valid. Previously, we were only
26403 considering replacement when the new certs _didn't_ help.
26404 - Fix an assert error on startup if we didn't already have the
26405 consensus and certs cached in our datadirectory: we were caching
26406 the consensus in consensus_waiting_for_certs but then free'ing it
26408 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
26409 Request) if we need more v3 certs but we've already got pending
26410 requests for all of them.
26411 - Correctly back off from failing certificate downloads. Fixes
26413 - Authorities don't vote on the Running flag if they have been running
26414 for less than 30 minutes themselves. Fixes bug 547, where a newly
26415 started authority would vote that everyone was down.
26417 o New requirements:
26418 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
26419 it, it had no AES, and it hasn't seen any security patches since
26423 - Clients now hold circuitless TLS connections open for 1.5 times
26424 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
26425 rebuild a new circuit over them within that timeframe. Previously,
26426 they held them open only for KeepalivePeriod (5 minutes).
26427 - Use "If-Modified-Since" to avoid retrieving consensus
26428 networkstatuses that we already have.
26429 - When we have no consensus, check FallbackNetworkstatusFile (defaults
26430 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
26431 we start knowing some directory caches.
26432 - When we receive a consensus from the future, warn about skew.
26433 - Improve skew reporting: try to give the user a better log message
26434 about how skewed they are, and how much this matters.
26435 - When we have a certificate for an authority, believe that
26436 certificate's claims about the authority's IP address.
26437 - New --quiet command-line option to suppress the default console log.
26438 Good in combination with --hash-password.
26439 - Authorities send back an X-Descriptor-Not-New header in response to
26440 an accepted-but-discarded descriptor upload. Partially implements
26442 - Make the log message for "tls error. breaking." more useful.
26443 - Better log messages about certificate downloads, to attempt to
26444 track down the second incarnation of bug 546.
26446 o Minor features (bridges):
26447 - If bridge users set UpdateBridgesFromAuthority, but the digest
26448 they ask for is a 404 from the bridge authority, they now fall
26449 back to trying the bridge directly.
26450 - Bridges now use begin_dir to publish their server descriptor to
26451 the bridge authority, even when they haven't set TunnelDirConns.
26453 o Minor features (controller):
26454 - When reporting clock skew, and we know that the clock is _at least
26455 as skewed_ as some value, but we don't know the actual value,
26456 report the value as a "minimum skew."
26459 - Update linux-tor-prio.sh script to allow QoS based on the uid of
26460 the Tor process. Patch from Marco Bonetti with tweaks from Mike
26464 - Refuse to start if both ORPort and UseBridges are set. Bugfix
26465 on 0.2.0.x, suggested by Matt Edman.
26466 - Don't stop fetching descriptors when FetchUselessDescriptors is
26467 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
26468 reported by tup and ioerror.
26469 - Better log message on vote from unknown authority.
26470 - Don't log "Launching 0 request for 0 router" message.
26472 o Minor bugfixes (memory leaks):
26473 - Stop leaking memory every time we parse a v3 certificate. Bugfix
26475 - Stop leaking memory every time we load a v3 certificate. Bugfix
26476 on 0.2.0.1-alpha. Fixes bug 536.
26477 - Stop leaking a cached networkstatus on exit. Bugfix on
26479 - Stop leaking voter information every time we free a consensus.
26480 Bugfix on 0.2.0.3-alpha.
26481 - Stop leaking signed data every time we check a voter signature.
26482 Bugfix on 0.2.0.3-alpha.
26483 - Stop leaking a signature every time we fail to parse a consensus or
26484 a vote. Bugfix on 0.2.0.3-alpha.
26485 - Stop leaking v2_download_status_map on shutdown. Bugfix on
26487 - Stop leaking conn->nickname every time we make a connection to a
26488 Tor relay without knowing its expected identity digest (e.g. when
26489 using bridges). Bugfix on 0.2.0.3-alpha.
26491 - Minor bugfixes (portability):
26492 - Run correctly on platforms where rlim_t is larger than unsigned
26493 long, and/or where the real limit for number of open files is
26494 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
26495 particular, these may be needed for OS X 10.5.
26498 Changes in version 0.1.2.18 - 2007-10-28
26499 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
26500 hidden service introduction that were causing huge delays, and a big
26501 bug that was causing some servers to disappear from the network status
26502 lists for a few hours each day.
26504 o Major bugfixes (crashes):
26505 - If a connection is shut down abruptly because of something that
26506 happened inside connection_flushed_some(), do not call
26507 connection_finished_flushing(). Should fix bug 451:
26508 "connection_stop_writing: Assertion conn->write_event failed"
26509 Bugfix on 0.1.2.7-alpha.
26510 - Fix possible segfaults in functions called from
26511 rend_process_relay_cell().
26513 o Major bugfixes (hidden services):
26514 - Hidden services were choosing introduction points uniquely by
26515 hexdigest, but when constructing the hidden service descriptor
26516 they merely wrote the (potentially ambiguous) nickname.
26517 - Clients now use the v2 intro format for hidden service
26518 connections: they specify their chosen rendezvous point by identity
26519 digest rather than by (potentially ambiguous) nickname. These
26520 changes could speed up hidden service connections dramatically.
26522 o Major bugfixes (other):
26523 - Stop publishing a new server descriptor just because we get a
26524 HUP signal. This led (in a roundabout way) to some servers getting
26525 dropped from the networkstatus lists for a few hours each day.
26526 - When looking for a circuit to cannibalize, consider family as well
26527 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
26528 circuit cannibalization).
26529 - When a router wasn't listed in a new networkstatus, we were leaving
26530 the flags for that router alone -- meaning it remained Named,
26531 Running, etc -- even though absence from the networkstatus means
26532 that it shouldn't be considered to exist at all anymore. Now we
26533 clear all the flags for routers that fall out of the networkstatus
26534 consensus. Fixes bug 529.
26537 - Don't try to access (or alter) the state file when running
26538 --list-fingerprint or --verify-config or --hash-password. Resolves
26540 - When generating information telling us how to extend to a given
26541 router, do not try to include the nickname if it is
26542 absent. Resolves bug 467.
26543 - Fix a user-triggerable segfault in expand_filename(). (There isn't
26544 a way to trigger this remotely.)
26545 - When sending a status event to the controller telling it that an
26546 OR address is reachable, set the port correctly. (Previously we
26547 were reporting the dir port.)
26548 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
26549 command. Bugfix on 0.1.2.17.
26550 - When loading bandwidth history, do not believe any information in
26551 the future. Fixes bug 434.
26552 - When loading entry guard information, do not believe any information
26554 - When we have our clock set far in the future and generate an
26555 onion key, then re-set our clock to be correct, we should not stop
26556 the onion key from getting rotated.
26557 - On some platforms, accept() can return a broken address. Detect
26558 this more quietly, and deal accordingly. Fixes bug 483.
26559 - It's not actually an error to find a non-pending entry in the DNS
26560 cache when canceling a pending resolve. Don't log unless stuff
26561 is fishy. Resolves bug 463.
26562 - Don't reset trusted dir server list when we set a configuration
26563 option. Patch from Robert Hogan.
26564 - Don't try to create the datadir when running --verify-config or
26565 --hash-password. Resolves bug 540.
26568 Changes in version 0.2.0.9-alpha - 2007-10-24
26569 This ninth development snapshot switches clients to the new v3 directory
26570 system; allows servers to be listed in the network status even when they
26571 have the same nickname as a registered server; and fixes many other
26572 bugs including a big one that was causing some servers to disappear
26573 from the network status lists for a few hours each day.
26575 o Major features (directory system):
26576 - Clients now download v3 consensus networkstatus documents instead
26577 of v2 networkstatus documents. Clients and caches now base their
26578 opinions about routers on these consensus documents. Clients only
26579 download router descriptors listed in the consensus.
26580 - Authorities now list servers who have the same nickname as
26581 a different named server, but list them with a new flag,
26582 "Unnamed". Now we can list servers that happen to pick the same
26583 nickname as a server that registered two years ago and then
26584 disappeared. Partially implements proposal 122.
26585 - If the consensus lists a router as "Unnamed", the name is assigned
26586 to a different router: do not identify the router by that name.
26587 Partially implements proposal 122.
26588 - Authorities can now come to a consensus on which method to use to
26589 compute the consensus. This gives us forward compatibility.
26592 - Stop publishing a new server descriptor just because we HUP or
26593 when we find our DirPort to be reachable but won't actually publish
26594 it. New descriptors without any real changes are dropped by the
26595 authorities, and can screw up our "publish every 18 hours" schedule.
26597 - When a router wasn't listed in a new networkstatus, we were leaving
26598 the flags for that router alone -- meaning it remained Named,
26599 Running, etc -- even though absence from the networkstatus means
26600 that it shouldn't be considered to exist at all anymore. Now we
26601 clear all the flags for routers that fall out of the networkstatus
26602 consensus. Fixes bug 529; bugfix on 0.1.2.x.
26603 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
26604 extrainfo documents and then discard them immediately for not
26605 matching the latest router. Bugfix on 0.2.0.1-alpha.
26607 o Minor features (v3 directory protocol):
26608 - Allow tor-gencert to generate a new certificate without replacing
26610 - Allow certificates to include an address.
26611 - When we change our directory-cache settings, reschedule all voting
26612 and download operations.
26613 - Reattempt certificate downloads immediately on failure, as long as
26614 we haven't failed a threshold number of times yet.
26615 - Delay retrying consensus downloads while we're downloading
26616 certificates to verify the one we just got. Also, count getting a
26617 consensus that we already have (or one that isn't valid) as a failure,
26618 and count failing to get the certificates after 20 minutes as a
26620 - Build circuits and download descriptors even if our consensus is a
26621 little expired. (This feature will go away once authorities are
26624 o Minor features (router descriptor cache):
26625 - If we find a cached-routers file that's been sitting around for more
26626 than 28 days unmodified, then most likely it's a leftover from
26627 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
26629 - When we (as a cache) download a descriptor because it was listed
26630 in a consensus, remember when the consensus was supposed to expire,
26631 and don't expire the descriptor until then.
26633 o Minor features (performance):
26634 - Call routerlist_remove_old_routers() much less often. This should
26635 speed startup, especially on directory caches.
26636 - Don't try to launch new descriptor downloads quite so often when we
26637 already have enough directory information to build circuits.
26638 - Base64 decoding was actually showing up on our profile when parsing
26639 the initial descriptor file; switch to an in-process all-at-once
26640 implementation that's about 3.5x times faster than calling out to
26643 o Minor features (compilation):
26644 - Detect non-ASCII platforms (if any still exist) and refuse to
26645 build there: some of our code assumes that 'A' is 65 and so on.
26647 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
26648 - Make the "next period" votes into "current period" votes immediately
26649 after publishing the consensus; avoid a heisenbug that made them
26650 stick around indefinitely.
26651 - When we discard a vote as a duplicate, do not report this as
26653 - Treat missing v3 keys or certificates as an error when running as a
26654 v3 directory authority.
26655 - When we're configured to be a v3 authority, but we're only listed
26656 as a non-v3 authority in our DirServer line for ourself, correct
26658 - If an authority doesn't have a qualified hostname, just put
26659 its address in the vote. This fixes the problem where we referred to
26660 "moria on moria:9031."
26661 - Distinguish between detached signatures for the wrong period, and
26662 detached signatures for a divergent vote.
26663 - Fix a small memory leak when computing a consensus.
26664 - When there's no consensus, we were forming a vote every 30
26665 minutes, but writing the "valid-after" line in our vote based
26666 on our configured V3AuthVotingInterval: so unless the intervals
26667 matched up, we immediately rejected our own vote because it didn't
26668 start at the voting interval that caused us to construct a vote.
26670 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
26671 - Delete unverified-consensus when the real consensus is set.
26672 - Consider retrying a consensus networkstatus fetch immediately
26673 after one fails: don't wait 60 seconds to notice.
26674 - When fetching a consensus as a cache, wait until a newer consensus
26675 should exist before trying to replace the current one.
26676 - Use a more forgiving schedule for retrying failed consensus
26677 downloads than for other types.
26679 o Minor bugfixes (other directory issues):
26680 - Correct the implementation of "download votes by digest." Bugfix on
26682 - Authorities no longer send back "400 you're unreachable please fix
26683 it" errors to Tor servers that aren't online all the time. We're
26684 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
26686 o Minor bugfixes (controller):
26687 - Don't reset trusted dir server list when we set a configuration
26688 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
26689 - Respond to INT and TERM SIGNAL commands before we execute the
26690 signal, in case the signal shuts us down. We had a patch in
26691 0.1.2.1-alpha that tried to do this by queueing the response on
26692 the connection's buffer before shutting down, but that really
26693 isn't the same thing at all. Bug located by Matt Edman.
26695 o Minor bugfixes (misc):
26696 - Correctly check for bad options to the "PublishServerDescriptor"
26697 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
26698 - Stop leaking memory on failing case of base32_decode, and make
26699 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
26700 - Don't try to download extrainfo documents when we're trying to
26701 fetch enough directory info to build a circuit: having enough
26702 info should get priority. Bugfix on 0.2.0.x.
26703 - Don't complain that "your server has not managed to confirm that its
26704 ports are reachable" if we haven't been able to build any circuits
26705 yet. Bug found by spending four hours without a v3 consensus. Bugfix
26707 - Detect the reason for failing to mmap a descriptor file we just
26708 wrote, and give a more useful log message. Fixes bug 533. Bugfix
26711 o Code simplifications and refactoring:
26712 - Remove support for the old bw_accounting file: we've been storing
26713 bandwidth accounting information in the state file since
26714 0.1.2.5-alpha. This may result in bandwidth accounting errors
26715 if you try to upgrade from 0.1.1.x or earlier, or if you try to
26716 downgrade to 0.1.1.x or earlier.
26717 - New convenience code to locate a file within the DataDirectory.
26718 - Move non-authority functionality out of dirvote.c.
26719 - Refactor the arguments for router_pick_{directory_|trusteddir}server
26720 so that they all take the same named flags.
26723 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
26724 Unix users an easy way to script their Tor process (e.g. by
26725 adjusting bandwidth based on the time of the day).
26728 Changes in version 0.2.0.8-alpha - 2007-10-12
26729 This eighth development snapshot fixes a crash bug that's been bothering
26730 us since February 2007, lets bridge authorities store a list of bridge
26731 descriptors they've seen, gets v3 directory voting closer to working,
26732 starts caching v3 directory consensus documents on directory mirrors,
26733 and fixes a variety of smaller issues including some minor memory leaks.
26735 o Major features (router descriptor cache):
26736 - Store routers in a file called cached-descriptors instead of in
26737 cached-routers. Initialize cached-descriptors from cached-routers
26738 if the old format is around. The new format allows us to store
26739 annotations along with descriptors.
26740 - Use annotations to record the time we received each descriptor, its
26741 source, and its purpose.
26742 - Disable the SETROUTERPURPOSE controller command: it is now
26744 - Controllers should now specify cache=no or cache=yes when using
26745 the +POSTDESCRIPTOR command.
26746 - Bridge authorities now write bridge descriptors to disk, meaning
26747 we can export them to other programs and begin distributing them
26750 o Major features (directory authorities):
26751 - When a v3 authority is missing votes or signatures, it now tries
26753 - Directory authorities track weighted fractional uptime as well as
26754 weighted mean-time-between failures. WFU is suitable for deciding
26755 whether a node is "usually up", while MTBF is suitable for deciding
26756 whether a node is "likely to stay up." We need both, because
26757 "usually up" is a good requirement for guards, while "likely to
26758 stay up" is a good requirement for long-lived connections.
26760 o Major features (v3 directory system):
26761 - Caches now download v3 network status documents as needed,
26762 and download the descriptors listed in them.
26763 - All hosts now attempt to download and keep fresh v3 authority
26764 certificates, and re-attempt after failures.
26765 - More internal-consistency checks for vote parsing.
26767 o Major bugfixes (crashes):
26768 - If a connection is shut down abruptly because of something that
26769 happened inside connection_flushed_some(), do not call
26770 connection_finished_flushing(). Should fix bug 451. Bugfix on
26773 o Major bugfixes (performance):
26774 - Fix really bad O(n^2) performance when parsing a long list of
26775 routers: Instead of searching the entire list for an "extra-info "
26776 string which usually wasn't there, once for every routerinfo
26777 we read, just scan lines forward until we find one we like.
26779 - When we add data to a write buffer in response to the data on that
26780 write buffer getting low because of a flush, do not consider the
26781 newly added data as a candidate for immediate flushing, but rather
26782 make it wait until the next round of writing. Otherwise, we flush
26783 and refill recursively, and a single greedy TLS connection can
26784 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
26786 o Minor features (v3 authority system):
26787 - Add more ways for tools to download the votes that lead to the
26789 - Send a 503 when low on bandwidth and a vote, consensus, or
26790 certificate is requested.
26791 - If-modified-since is now implemented properly for all kinds of
26792 certificate requests.
26794 o Minor bugfixes (network statuses):
26795 - Tweak the implementation of proposal 109 slightly: allow at most
26796 two Tor servers on the same IP address, except if it's the location
26797 of a directory authority, in which case allow five. Bugfix on
26800 o Minor bugfixes (controller):
26801 - When sending a status event to the controller telling it that an
26802 OR address is reachable, set the port correctly. (Previously we
26803 were reporting the dir port.) Bugfix on 0.1.2.x.
26805 o Minor bugfixes (v3 directory system):
26806 - Fix logic to look up a cert by its signing key digest. Bugfix on
26808 - Only change the reply to a vote to "OK" if it's not already
26809 set. This gets rid of annoying "400 OK" log messages, which may
26810 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
26811 - When we get a valid consensus, recompute the voting schedule.
26812 - Base the valid-after time of a vote on the consensus voting
26813 schedule, not on our preferred schedule.
26814 - Make the return values and messages from signature uploads and
26815 downloads more sensible.
26816 - Fix a memory leak when serving votes and consensus documents, and
26817 another when serving certificates.
26819 o Minor bugfixes (performance):
26820 - Use a slightly simpler string hashing algorithm (copying Python's
26821 instead of Java's) and optimize our digest hashing algorithm to take
26822 advantage of 64-bit platforms and to remove some possibly-costly
26824 - Fix a minor memory leak whenever we parse guards from our state
26825 file. Bugfix on 0.2.0.7-alpha.
26826 - Fix a minor memory leak whenever we write out a file. Bugfix on
26828 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
26829 command. Bugfix on 0.2.0.5-alpha.
26831 o Minor bugfixes (portability):
26832 - On some platforms, accept() can return a broken address. Detect
26833 this more quietly, and deal accordingly. Fixes bug 483.
26834 - Stop calling tor_strlower() on uninitialized memory in some cases.
26835 Bugfix in 0.2.0.7-alpha.
26837 o Minor bugfixes (usability):
26838 - Treat some 403 responses from directory servers as INFO rather than
26839 WARN-severity events.
26840 - It's not actually an error to find a non-pending entry in the DNS
26841 cache when canceling a pending resolve. Don't log unless stuff is
26842 fishy. Resolves bug 463.
26844 o Minor bugfixes (anonymity):
26845 - Never report that we've used more bandwidth than we're willing to
26846 relay: it leaks how much non-relay traffic we're using. Resolves
26848 - When looking for a circuit to cannibalize, consider family as well
26849 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
26850 circuit cannibalization).
26852 o Code simplifications and refactoring:
26853 - Make a bunch of functions static. Remove some dead code.
26854 - Pull out about a third of the really big routerlist.c; put it in a
26855 new module, networkstatus.c.
26856 - Merge the extra fields in local_routerstatus_t back into
26857 routerstatus_t: we used to need one routerstatus_t for each
26858 authority's opinion, plus a local_routerstatus_t for the locally
26859 computed consensus opinion. To save space, we put the locally
26860 modified fields into local_routerstatus_t, and only the common
26861 stuff into routerstatus_t. But once v3 directories are in use,
26862 clients and caches will no longer need to hold authority opinions;
26863 thus, the rationale for keeping the types separate is now gone.
26864 - Make the code used to reschedule and reattempt downloads more
26866 - Turn all 'Are we a directory server/mirror?' logic into a call to
26868 - Remove the code to generate the oldest (v1) directory format.
26869 The code has been disabled since 0.2.0.5-alpha.
26872 Changes in version 0.2.0.7-alpha - 2007-09-21
26873 This seventh development snapshot makes bridges work again, makes bridge
26874 authorities work for the first time, fixes two huge performance flaws
26875 in hidden services, and fixes a variety of minor issues.
26877 o New directory authorities:
26878 - Set up moria1 and tor26 as the first v3 directory authorities. See
26879 doc/spec/dir-spec.txt for details on the new directory design.
26881 o Major bugfixes (crashes):
26882 - Fix possible segfaults in functions called from
26883 rend_process_relay_cell(). Bugfix on 0.1.2.x.
26885 o Major bugfixes (bridges):
26886 - Fix a bug that made servers send a "404 Not found" in response to
26887 attempts to fetch their server descriptor. This caused Tor servers
26888 to take many minutes to establish reachability for their DirPort,
26889 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
26890 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
26891 users configure that and specify a bridge with an identity
26892 fingerprint, now they will lookup the bridge descriptor at the
26893 default bridge authority via a one-hop tunnel, but once circuits
26894 are established they will switch to a three-hop tunnel for later
26895 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
26897 o Major bugfixes (hidden services):
26898 - Hidden services were choosing introduction points uniquely by
26899 hexdigest, but when constructing the hidden service descriptor
26900 they merely wrote the (potentially ambiguous) nickname.
26901 - Clients now use the v2 intro format for hidden service
26902 connections: they specify their chosen rendezvous point by identity
26903 digest rather than by (potentially ambiguous) nickname. Both
26904 are bugfixes on 0.1.2.x, and they could speed up hidden service
26905 connections dramatically. Thanks to Karsten Loesing.
26907 o Minor features (security):
26908 - As a client, do not believe any server that tells us that an
26909 address maps to an internal address space.
26910 - Make it possible to enable HashedControlPassword and
26911 CookieAuthentication at the same time.
26913 o Minor features (guard nodes):
26914 - Tag every guard node in our state file with the version that
26915 we believe added it, or with our own version if we add it. This way,
26916 if a user temporarily runs an old version of Tor and then switches
26917 back to a new one, she doesn't automatically lose her guards.
26919 o Minor features (speed):
26920 - When implementing AES counter mode, update only the portions of the
26921 counter buffer that need to change, and don't keep separate
26922 network-order and host-order counters when they are the same (i.e.,
26923 on big-endian hosts.)
26925 o Minor features (controller):
26926 - Accept LF instead of CRLF on controller, since some software has a
26927 hard time generating real Internet newlines.
26928 - Add GETINFO values for the server status events
26929 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
26932 o Removed features:
26933 - Routers no longer include bandwidth-history lines in their
26934 descriptors; this information is already available in extra-info
26935 documents, and including it in router descriptors took up 60%
26936 (!) of compressed router descriptor downloads. Completes
26937 implementation of proposal 104.
26938 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
26939 and TorControl.py, as they use the old v0 controller protocol,
26940 and are obsoleted by TorFlow anyway.
26941 - Drop support for v1 rendezvous descriptors, since we never used
26942 them anyway, and the code has probably rotted by now. Based on
26943 patch from Karsten Loesing.
26944 - On OSX, stop warning the user that kqueue support in libevent is
26945 "experimental", since it seems to have worked fine for ages.
26948 - When generating information telling us how to extend to a given
26949 router, do not try to include the nickname if it is absent. Fixes
26950 bug 467. Bugfix on 0.2.0.3-alpha.
26951 - Fix a user-triggerable (but not remotely-triggerable) segfault
26952 in expand_filename(). Bugfix on 0.1.2.x.
26953 - Fix a memory leak when freeing incomplete requests from DNSPort.
26954 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
26955 - Don't try to access (or alter) the state file when running
26956 --list-fingerprint or --verify-config or --hash-password. (Resolves
26957 bug 499.) Bugfix on 0.1.2.x.
26958 - Servers used to decline to publish their DirPort if their
26959 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
26960 were below a threshold. Now they only look at BandwidthRate and
26961 RelayBandwidthRate. Bugfix on 0.1.2.x.
26962 - Remove an optimization in the AES counter-mode code that assumed
26963 that the counter never exceeded 2^68. When the counter can be set
26964 arbitrarily as an IV (as it is by Karsten's new hidden services
26965 code), this assumption no longer holds. Bugfix on 0.1.2.x.
26966 - Resume listing "AUTHORITY" flag for authorities in network status.
26967 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
26969 o Code simplifications and refactoring:
26970 - Revamp file-writing logic so we don't need to have the entire
26971 contents of a file in memory at once before we write to disk. Tor,
26973 - Turn "descriptor store" into a full-fledged type.
26974 - Move all NT services code into a separate source file.
26975 - Unify all code that computes medians, percentile elements, etc.
26976 - Get rid of a needless malloc when parsing address policies.
26979 Changes in version 0.1.2.17 - 2007-08-30
26980 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
26981 X bundles. Vidalia 0.0.14 makes authentication required for the
26982 ControlPort in the default configuration, which addresses important
26983 security risks. Everybody who uses Vidalia (or another controller)
26986 In addition, this Tor update fixes major load balancing problems with
26987 path selection, which should speed things up a lot once many people
26990 o Major bugfixes (security):
26991 - We removed support for the old (v0) control protocol. It has been
26992 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
26993 become more of a headache than it's worth.
26995 o Major bugfixes (load balancing):
26996 - When choosing nodes for non-guard positions, weight guards
26997 proportionally less, since they already have enough load. Patch
26999 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
27000 will allow fast Tor servers to get more attention.
27001 - When we're upgrading from an old Tor version, forget our current
27002 guards and pick new ones according to the new weightings. These
27003 three load balancing patches could raise effective network capacity
27004 by a factor of four. Thanks to Mike Perry for measurements.
27006 o Major bugfixes (stream expiration):
27007 - Expire not-yet-successful application streams in all cases if
27008 they've been around longer than SocksTimeout. Right now there are
27009 some cases where the stream will live forever, demanding a new
27010 circuit every 15 seconds. Fixes bug 454; reported by lodger.
27012 o Minor features (controller):
27013 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
27014 is valid before any authentication has been received. It tells
27015 a controller what kind of authentication is expected, and what
27016 protocol is spoken. Implements proposal 119.
27018 o Minor bugfixes (performance):
27019 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
27020 greatly speeding up loading cached-routers from disk on startup.
27021 - Disable sentinel-based debugging for buffer code: we squashed all
27022 the bugs that this was supposed to detect a long time ago, and now
27023 its only effect is to change our buffer sizes from nice powers of
27024 two (which platform mallocs tend to like) to values slightly over
27025 powers of two (which make some platform mallocs sad).
27027 o Minor bugfixes (misc):
27028 - If exit bandwidth ever exceeds one third of total bandwidth, then
27029 use the correct formula to weight exit nodes when choosing paths.
27030 Based on patch from Mike Perry.
27031 - Choose perfectly fairly among routers when choosing by bandwidth and
27032 weighting by fraction of bandwidth provided by exits. Previously, we
27033 would choose with only approximate fairness, and correct ourselves
27034 if we ran off the end of the list.
27035 - If we require CookieAuthentication but we fail to write the
27036 cookie file, we would warn but not exit, and end up in a state
27037 where no controller could authenticate. Now we exit.
27038 - If we require CookieAuthentication, stop generating a new cookie
27039 every time we change any piece of our config.
27040 - Refuse to start with certain directory authority keys, and
27041 encourage people using them to stop.
27042 - Terminate multi-line control events properly. Original patch
27044 - Fix a minor memory leak when we fail to find enough suitable
27045 servers to choose a circuit.
27046 - Stop leaking part of the descriptor when we run into a particularly
27047 unparseable piece of it.
27050 Changes in version 0.2.0.6-alpha - 2007-08-26
27051 This sixth development snapshot features a new Vidalia version in the
27052 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
27053 the ControlPort in the default configuration, which addresses important
27056 In addition, this snapshot fixes major load balancing problems
27057 with path selection, which should speed things up a lot once many
27058 people have upgraded. The directory authorities also use a new
27059 mean-time-between-failure approach to tracking which servers are stable,
27060 rather than just looking at the most recent uptime.
27062 o New directory authorities:
27063 - Set up Tonga as the default bridge directory authority.
27066 - Directory authorities now track servers by weighted
27067 mean-times-between-failures. When we have 4 or more days of data,
27068 use measured MTBF rather than declared uptime to decide whether
27069 to call a router Stable. Implements proposal 108.
27071 o Major bugfixes (load balancing):
27072 - When choosing nodes for non-guard positions, weight guards
27073 proportionally less, since they already have enough load. Patch
27075 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
27076 will allow fast Tor servers to get more attention.
27077 - When we're upgrading from an old Tor version, forget our current
27078 guards and pick new ones according to the new weightings. These
27079 three load balancing patches could raise effective network capacity
27080 by a factor of four. Thanks to Mike Perry for measurements.
27082 o Major bugfixes (descriptor parsing):
27083 - Handle unexpected whitespace better in malformed descriptors. Bug
27084 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
27087 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
27088 GETINFO for Torstat to use until it can switch to using extrainfos.
27089 - Optionally (if built with -DEXPORTMALLINFO) export the output
27090 of mallinfo via http, as tor/mallinfo.txt. Only accessible
27094 - Do not intermix bridge routers with controller-added
27095 routers. (Bugfix on 0.2.0.x)
27096 - Do not fail with an assert when accept() returns an unexpected
27097 address family. Addresses but does not wholly fix bug 483. (Bugfix
27099 - Let directory authorities startup even when they can't generate
27100 a descriptor immediately, e.g. because they don't know their
27102 - Stop putting the authentication cookie in a file called "0"
27103 in your working directory if you don't specify anything for the
27104 new CookieAuthFile option. Reported by Matt Edman.
27105 - Make it possible to read the PROTOCOLINFO response in a way that
27106 conforms to our control-spec. Reported by Matt Edman.
27107 - Fix a minor memory leak when we fail to find enough suitable
27108 servers to choose a circuit. Bugfix on 0.1.2.x.
27109 - Stop leaking part of the descriptor when we run into a particularly
27110 unparseable piece of it. Bugfix on 0.1.2.x.
27111 - Unmap the extrainfo cache file on exit.
27114 Changes in version 0.2.0.5-alpha - 2007-08-19
27115 This fifth development snapshot fixes compilation on Windows again;
27116 fixes an obnoxious client-side bug that slowed things down and put
27117 extra load on the network; gets us closer to using the v3 directory
27118 voting scheme; makes it easier for Tor controllers to use cookie-based
27119 authentication; and fixes a variety of other bugs.
27121 o Removed features:
27122 - Version 1 directories are no longer generated in full. Instead,
27123 authorities generate and serve "stub" v1 directories that list
27124 no servers. This will stop Tor versions 0.1.0.x and earlier from
27125 working, but (for security reasons) nobody should be running those
27128 o Major bugfixes (compilation, 0.2.0.x):
27129 - Try to fix Win32 compilation again: improve checking for IPv6 types.
27130 - Try to fix MSVC compilation: build correctly on platforms that do
27131 not define s6_addr16 or s6_addr32.
27132 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
27135 o Major bugfixes (stream expiration):
27136 - Expire not-yet-successful application streams in all cases if
27137 they've been around longer than SocksTimeout. Right now there are
27138 some cases where the stream will live forever, demanding a new
27139 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
27140 reported by lodger.
27142 o Minor features (directory servers):
27143 - When somebody requests a list of statuses or servers, and we have
27144 none of those, return a 404 rather than an empty 200.
27146 o Minor features (directory voting):
27147 - Store v3 consensus status consensuses on disk, and reload them
27150 o Minor features (security):
27151 - Warn about unsafe ControlPort configurations.
27152 - Refuse to start with certain directory authority keys, and
27153 encourage people using them to stop.
27155 o Minor features (controller):
27156 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
27157 is valid before any authentication has been received. It tells
27158 a controller what kind of authentication is expected, and what
27159 protocol is spoken. Implements proposal 119.
27160 - New config option CookieAuthFile to choose a new location for the
27161 cookie authentication file, and config option
27162 CookieAuthFileGroupReadable to make it group-readable.
27164 o Minor features (unit testing):
27165 - Add command-line arguments to unit-test executable so that we can
27166 invoke any chosen test from the command line rather than having
27167 to run the whole test suite at once; and so that we can turn on
27168 logging for the unit tests.
27170 o Minor bugfixes (on 0.1.2.x):
27171 - If we require CookieAuthentication but we fail to write the
27172 cookie file, we would warn but not exit, and end up in a state
27173 where no controller could authenticate. Now we exit.
27174 - If we require CookieAuthentication, stop generating a new cookie
27175 every time we change any piece of our config.
27176 - When loading bandwidth history, do not believe any information in
27177 the future. Fixes bug 434.
27178 - When loading entry guard information, do not believe any information
27180 - When we have our clock set far in the future and generate an
27181 onion key, then re-set our clock to be correct, we should not stop
27182 the onion key from getting rotated.
27183 - Clean up torrc sample config file.
27184 - Do not automatically run configure from autogen.sh. This
27185 non-standard behavior tended to annoy people who have built other
27188 o Minor bugfixes (on 0.2.0.x):
27189 - Fix a bug with AutomapHostsOnResolve that would always cause
27190 the second request to fail. Bug reported by Kate. Bugfix on
27192 - Fix a bug in ADDRMAP controller replies that would sometimes
27193 try to print a NULL. Patch from tup.
27194 - Read v3 directory authority keys from the right location.
27195 - Numerous bugfixes to directory voting code.
27198 Changes in version 0.1.2.16 - 2007-08-01
27199 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
27200 remote attacker in certain situations to rewrite the user's torrc
27201 configuration file. This can completely compromise anonymity of users
27202 in most configurations, including those running the Vidalia bundles,
27203 TorK, etc. Or worse.
27205 o Major security fixes:
27206 - Close immediately after missing authentication on control port;
27207 do not allow multiple authentication attempts.
27210 Changes in version 0.2.0.4-alpha - 2007-08-01
27211 This fourth development snapshot fixes a critical security vulnerability
27212 for most users, specifically those running Vidalia, TorK, etc. Everybody
27213 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
27215 o Major security fixes:
27216 - Close immediately after missing authentication on control port;
27217 do not allow multiple authentication attempts.
27219 o Major bugfixes (compilation):
27220 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
27223 o Minor features (performance):
27224 - Be even more aggressive about releasing RAM from small
27225 empty buffers. Thanks to our free-list code, this shouldn't be too
27226 performance-intensive.
27227 - Disable sentinel-based debugging for buffer code: we squashed all
27228 the bugs that this was supposed to detect a long time ago, and
27229 now its only effect is to change our buffer sizes from nice
27230 powers of two (which platform mallocs tend to like) to values
27231 slightly over powers of two (which make some platform mallocs sad).
27232 - Log malloc statistics from mallinfo() on platforms where it
27236 Changes in version 0.2.0.3-alpha - 2007-07-29
27237 This third development snapshot introduces new experimental
27238 blocking-resistance features and a preliminary version of the v3
27239 directory voting design, and includes many other smaller features
27243 - The first pieces of our "bridge" design for blocking-resistance
27244 are implemented. People can run bridge directory authorities;
27245 people can run bridges; and people can configure their Tor clients
27246 with a set of bridges to use as the first hop into the Tor network.
27247 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
27249 - Create listener connections before we setuid to the configured
27250 User and Group. Now non-Windows users can choose port values
27251 under 1024, start Tor as root, and have Tor bind those ports
27252 before it changes to another UID. (Windows users could already
27254 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
27255 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
27256 on "vserver" accounts. (Patch from coderman.)
27257 - Be even more aggressive about separating local traffic from relayed
27258 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
27260 o Major features (experimental):
27261 - First cut of code for "v3 dir voting": directory authorities will
27262 vote on a common network status document rather than each publishing
27263 their own opinion. This code needs more testing and more corner-case
27264 handling before it's ready for use.
27267 - Directory authorities now call routers Fast if their bandwidth is
27268 at least 100KB/s, and consider their bandwidth adequate to be a
27269 Guard if it is at least 250KB/s, no matter the medians. This fix
27270 complements proposal 107. [Bugfix on 0.1.2.x]
27271 - Directory authorities now never mark more than 3 servers per IP as
27272 Valid and Running. (Implements proposal 109, by Kevin Bauer and
27274 - Minor change to organizationName and commonName generation
27275 procedures in TLS certificates during Tor handshakes, to invalidate
27276 some earlier censorware approaches. This is not a long-term
27277 solution, but applying it will give us a bit of time to look into
27278 the epidemiology of countermeasures as they spread.
27280 o Major bugfixes (directory):
27281 - Rewrite directory tokenization code to never run off the end of
27282 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
27284 o Minor features (controller):
27285 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
27286 match requests to applications. (Patch from Robert Hogan.)
27287 - Report address and port correctly on connections to DNSPort. (Patch
27288 from Robert Hogan.)
27289 - Add a RESOLVE command to launch hostname lookups. (Original patch
27290 from Robert Hogan.)
27291 - Add GETINFO status/enough-dir-info to let controllers tell whether
27292 Tor has downloaded sufficient directory information. (Patch
27294 - You can now use the ControlSocket option to tell Tor to listen for
27295 controller connections on Unix domain sockets on systems that
27296 support them. (Patch from Peter Palfrader.)
27297 - STREAM NEW events are generated for DNSPort requests and for
27298 tunneled directory connections. (Patch from Robert Hogan.)
27299 - New "GETINFO address-mappings/*" command to get address mappings
27300 with expiry information. "addr-mappings/*" is now deprecated.
27303 o Minor features (misc):
27304 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
27306 - The tor-gencert tool for v3 directory authorities now creates all
27307 files as readable to the file creator only, and write-protects
27308 the authority identity key.
27309 - When dumping memory usage, list bytes used in buffer memory
27311 - When running with dmalloc, dump more stats on hup and on exit.
27312 - Directory authorities now fail quickly and (relatively) harmlessly
27313 if they generate a network status document that is somehow
27316 o Traffic load balancing improvements:
27317 - If exit bandwidth ever exceeds one third of total bandwidth, then
27318 use the correct formula to weight exit nodes when choosing paths.
27319 (Based on patch from Mike Perry.)
27320 - Choose perfectly fairly among routers when choosing by bandwidth and
27321 weighting by fraction of bandwidth provided by exits. Previously, we
27322 would choose with only approximate fairness, and correct ourselves
27323 if we ran off the end of the list. [Bugfix on 0.1.2.x]
27325 o Performance improvements:
27326 - Be more aggressive with freeing buffer RAM or putting it on the
27328 - Use Critical Sections rather than Mutexes for synchronizing threads
27329 on win32; Mutexes are heavier-weight, and designed for synchronizing
27332 o Deprecated and removed features:
27333 - RedirectExits is now deprecated.
27334 - Stop allowing address masks that do not correspond to bit prefixes.
27335 We have warned about these for a really long time; now it's time
27336 to reject them. (Patch from croup.)
27338 o Minor bugfixes (directory):
27339 - Fix another crash bug related to extra-info caching. (Bug found by
27340 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
27341 - Directories no longer return a "304 not modified" when they don't
27342 have the networkstatus the client asked for. Also fix a memory
27343 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
27344 - We had accidentally labelled 0.1.2.x directory servers as not
27345 suitable for begin_dir requests, and had labelled no directory
27346 servers as suitable for uploading extra-info documents. [Bugfix
27349 o Minor bugfixes (dns):
27350 - Fix a crash when DNSPort is set more than once. (Patch from Robert
27351 Hogan.) [Bugfix on 0.2.0.2-alpha]
27352 - Add DNSPort connections to the global connection list, so that we
27353 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
27355 - Fix a dangling reference that could lead to a crash when DNSPort is
27356 changed or closed (Patch from Robert Hogan.) [Bugfix on
27359 o Minor bugfixes (controller):
27360 - Provide DNS expiry times in GMT, not in local time. For backward
27361 compatibility, ADDRMAP events only provide GMT expiry in an extended
27362 field. "GETINFO address-mappings" always does the right thing.
27363 - Use CRLF line endings properly in NS events.
27364 - Terminate multi-line control events properly. (Original patch
27365 from tup.) [Bugfix on 0.1.2.x-alpha]
27366 - Do not include spaces in SOURCE_ADDR fields in STREAM
27367 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
27370 Changes in version 0.1.2.15 - 2007-07-17
27371 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
27372 problems, fixes compilation on BSD, and fixes a variety of other
27373 bugs. Everybody should upgrade.
27375 o Major bugfixes (compilation):
27376 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
27378 o Major bugfixes (crashes):
27379 - Try even harder not to dereference the first character after
27380 an mmap(). Reported by lodger.
27381 - Fix a crash bug in directory authorities when we re-number the
27382 routerlist while inserting a new router.
27383 - When the cached-routers file is an even multiple of the page size,
27384 don't run off the end and crash. (Fixes bug 455; based on idea
27386 - Fix eventdns.c behavior on Solaris: It is critical to include
27387 orconfig.h _before_ sys/types.h, so that we can get the expected
27388 definition of _FILE_OFFSET_BITS.
27390 o Major bugfixes (security):
27391 - Fix a possible buffer overrun when using BSD natd support. Bug
27393 - When sending destroy cells from a circuit's origin, don't include
27394 the reason for tearing down the circuit. The spec says we didn't,
27395 and now we actually don't. Reported by lodger.
27396 - Keep streamids from different exits on a circuit separate. This
27397 bug may have allowed other routers on a given circuit to inject
27398 cells into streams. Reported by lodger; fixes bug 446.
27399 - If there's a never-before-connected-to guard node in our list,
27400 never choose any guards past it. This way we don't expand our
27401 guard list unless we need to.
27403 o Minor bugfixes (guard nodes):
27404 - Weight guard selection by bandwidth, so that low-bandwidth nodes
27405 don't get overused as guards.
27407 o Minor bugfixes (directory):
27408 - Correctly count the number of authorities that recommend each
27409 version. Previously, we were under-counting by 1.
27410 - Fix a potential crash bug when we load many server descriptors at
27411 once and some of them make others of them obsolete. Fixes bug 458.
27413 o Minor bugfixes (hidden services):
27414 - Stop tearing down the whole circuit when the user asks for a
27415 connection to a port that the hidden service didn't configure.
27418 o Minor bugfixes (misc):
27419 - On Windows, we were preventing other processes from reading
27420 cached-routers while Tor was running. Reported by janbar.
27421 - Fix a possible (but very unlikely) bug in picking routers by
27422 bandwidth. Add a log message to confirm that it is in fact
27423 unlikely. Patch from lodger.
27424 - Backport a couple of memory leak fixes.
27425 - Backport miscellaneous cosmetic bugfixes.
27428 Changes in version 0.2.0.2-alpha - 2007-06-02
27429 o Major bugfixes on 0.2.0.1-alpha:
27430 - Fix an assertion failure related to servers without extra-info digests.
27431 Resolves bugs 441 and 442.
27433 o Minor features (directory):
27434 - Support "If-Modified-Since" when answering HTTP requests for
27435 directories, running-routers documents, and network-status documents.
27436 (There's no need to support it for router descriptors, since those
27437 are downloaded by descriptor digest.)
27439 o Minor build issues:
27440 - Clear up some MIPSPro compiler warnings.
27441 - When building from a tarball on a machine that happens to have SVK
27442 installed, report the micro-revision as whatever version existed
27443 in the tarball, not as "x".
27446 Changes in version 0.2.0.1-alpha - 2007-06-01
27447 This early development snapshot provides new features for people running
27448 Tor as both a client and a server (check out the new RelayBandwidth
27449 config options); lets Tor run as a DNS proxy; and generally moves us
27450 forward on a lot of fronts.
27452 o Major features, server usability:
27453 - New config options RelayBandwidthRate and RelayBandwidthBurst:
27454 a separate set of token buckets for relayed traffic. Right now
27455 relayed traffic is defined as answers to directory requests, and
27456 OR connections that don't have any local circuits on them.
27458 o Major features, client usability:
27459 - A client-side DNS proxy feature to replace the need for
27460 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
27461 for DNS requests on port 9999, use the Tor network to resolve them
27462 anonymously, and send the reply back like a regular DNS server.
27463 The code still only implements a subset of DNS.
27464 - Make PreferTunneledDirConns and TunnelDirConns work even when
27465 we have no cached directory info. This means Tor clients can now
27466 do all of their connections protected by TLS.
27468 o Major features, performance and efficiency:
27469 - Directory authorities accept and serve "extra info" documents for
27470 routers. These documents contain fields from router descriptors
27471 that aren't usually needed, and that use a lot of excess
27472 bandwidth. Once these fields are removed from router descriptors,
27473 the bandwidth savings should be about 60%. [Partially implements
27475 - Servers upload extra-info documents to any authority that accepts
27476 them. Authorities (and caches that have been configured to download
27477 extra-info documents) download them as needed. [Partially implements
27479 - Change the way that Tor buffers data that it is waiting to write.
27480 Instead of queueing data cells in an enormous ring buffer for each
27481 client->OR or OR->OR connection, we now queue cells on a separate
27482 queue for each circuit. This lets us use less slack memory, and
27483 will eventually let us be smarter about prioritizing different kinds
27485 - Use memory pools to allocate cells with better speed and memory
27486 efficiency, especially on platforms where malloc() is inefficient.
27487 - Stop reading on edge connections when their corresponding circuit
27488 buffers are full; start again as the circuits empty out.
27490 o Major features, other:
27491 - Add an HSAuthorityRecordStats option that hidden service authorities
27492 can use to track statistics of overall hidden service usage without
27493 logging information that would be very useful to an attacker.
27494 - Start work implementing multi-level keys for directory authorities:
27495 Add a standalone tool to generate key certificates. (Proposal 103.)
27498 - Directory authorities now call routers Stable if they have an
27499 uptime of at least 30 days, even if that's not the median uptime
27500 in the network. Implements proposal 107, suggested by Kevin Bauer
27503 o Minor fixes (resource management):
27504 - Count the number of open sockets separately from the number
27505 of active connection_t objects. This will let us avoid underusing
27506 our allocated connection limit.
27507 - We no longer use socket pairs to link an edge connection to an
27508 anonymous directory connection or a DirPort test connection.
27509 Instead, we track the link internally and transfer the data
27510 in-process. This saves two sockets per "linked" connection (at the
27511 client and at the server), and avoids the nasty Windows socketpair()
27513 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
27514 for every single inactive connection_t. Free items from the
27515 4k/16k-buffer free lists when they haven't been used for a while.
27517 o Minor features (build):
27518 - Make autoconf search for libevent, openssl, and zlib consistently.
27519 - Update deprecated macros in configure.in.
27520 - When warning about missing headers, tell the user to let us
27521 know if the compile succeeds anyway, so we can downgrade the
27523 - Include the current subversion revision as part of the version
27524 string: either fetch it directly if we're in an SVN checkout, do
27525 some magic to guess it if we're in an SVK checkout, or use
27526 the last-detected version if we're building from a .tar.gz.
27527 Use this version consistently in log messages.
27529 o Minor features (logging):
27530 - Always prepend "Bug: " to any log message about a bug.
27531 - Put a platform string (e.g. "Linux i686") in the startup log
27532 message, so when people paste just their logs, we know if it's
27533 OpenBSD or Windows or what.
27534 - When logging memory usage, break down memory used in buffers by
27537 o Minor features (directory system):
27538 - New config option V2AuthoritativeDirectory that all directory
27539 authorities should set. This will let future authorities choose
27540 not to serve V2 directory information.
27541 - Directory authorities allow multiple router descriptors and/or extra
27542 info documents to be uploaded in a single go. This will make
27543 implementing proposal 104 simpler.
27545 o Minor features (controller):
27546 - Add a new config option __DisablePredictedCircuits designed for
27547 use by the controller, when we don't want Tor to build any circuits
27549 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
27550 so we can exit from the middle of the circuit.
27551 - Implement "getinfo status/circuit-established".
27552 - Implement "getinfo status/version/..." so a controller can tell
27553 whether the current version is recommended, and whether any versions
27554 are good, and how many authorities agree. (Patch from shibz.)
27556 o Minor features (hidden services):
27557 - Allow multiple HiddenServicePort directives with the same virtual
27558 port; when they occur, the user is sent round-robin to one
27559 of the target ports chosen at random. Partially fixes bug 393 by
27560 adding limited ad-hoc round-robining.
27562 o Minor features (other):
27564 - Add a new AutomapHostsOnResolve option: when it is enabled, any
27565 resolve request for hosts matching a given pattern causes Tor to
27566 generate an internal virtual address mapping for that host. This
27567 allows DNSPort to work sensibly with hidden service users. By
27568 default, .exit and .onion addresses are remapped; the list of
27569 patterns can be reconfigured with AutomapHostsSuffixes.
27570 - Add an "-F" option to tor-resolve to force a resolve for a .onion
27571 address. Thanks to the AutomapHostsOnResolve option, this is no
27572 longer a completely silly thing to do.
27573 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
27574 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
27575 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
27576 minus 1 byte: the actual maximum declared bandwidth.
27578 o Removed features:
27579 - Removed support for the old binary "version 0" controller protocol.
27580 This has been deprecated since 0.1.1, and warnings have been issued
27581 since 0.1.2. When we encounter a v0 control message, we now send
27582 back an error and close the connection.
27583 - Remove the old "dns worker" server DNS code: it hasn't been default
27584 since 0.1.2.2-alpha, and all the servers seem to be using the new
27587 o Minor bugfixes (portability):
27588 - Even though Windows is equally happy with / and \ as path separators,
27589 try to use \ consistently on Windows and / consistently on Unix: it
27590 makes the log messages nicer.
27591 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
27592 - Read resolv.conf files correctly on platforms where read() returns
27593 partial results on small file reads.
27595 o Minor bugfixes (directory):
27596 - Correctly enforce that elements of directory objects do not appear
27597 more often than they are allowed to appear.
27598 - When we are reporting the DirServer line we just parsed, we were
27599 logging the second stanza of the key fingerprint, not the first.
27601 o Minor bugfixes (logging):
27602 - When we hit an EOF on a log (probably because we're shutting down),
27603 don't try to remove the log from the list: just mark it as
27604 unusable. (Bulletproofs against bug 222.)
27606 o Minor bugfixes (other):
27607 - In the exitlist script, only consider the most recently published
27608 server descriptor for each server. Also, when the user requests
27609 a list of servers that _reject_ connections to a given address,
27610 explicitly exclude the IPs that also have servers that accept
27611 connections to that address. (Resolves bug 405.)
27612 - Stop allowing hibernating servers to be "stable" or "fast".
27613 - On Windows, we were preventing other processes from reading
27614 cached-routers while Tor was running. (Reported by janbar)
27615 - Make the NodeFamilies config option work. (Reported by
27616 lodger -- it has never actually worked, even though we added it
27618 - Check return values from pthread_mutex functions.
27619 - Don't save non-general-purpose router descriptors to the disk cache,
27620 because we have no way of remembering what their purpose was when
27622 - Add even more asserts to hunt down bug 417.
27623 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
27624 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
27625 Add a log message to confirm that it is in fact unlikely.
27627 o Minor bugfixes (controller):
27628 - Make 'getinfo fingerprint' return a 551 error if we're not a
27629 server, so we match what the control spec claims we do. Reported
27631 - Fix a typo in an error message when extendcircuit fails that
27632 caused us to not follow the \r\n-based delimiter protocol. Reported
27635 o Code simplifications and refactoring:
27636 - Stop passing around circuit_t and crypt_path_t pointers that are
27637 implicit in other procedure arguments.
27638 - Drop the old code to choke directory connections when the
27639 corresponding OR connections got full: thanks to the cell queue
27640 feature, OR conns don't get full any more.
27641 - Make dns_resolve() handle attaching connections to circuits
27642 properly, so the caller doesn't have to.
27643 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
27644 - Keep the connection array as a dynamic smartlist_t, rather than as
27645 a fixed-sized array. This is important, as the number of connections
27646 is becoming increasingly decoupled from the number of sockets.
27649 Changes in version 0.1.2.14 - 2007-05-25
27650 Tor 0.1.2.14 changes the addresses of two directory authorities (this
27651 change especially affects those who serve or use hidden services),
27652 and fixes several other crash- and security-related bugs.
27654 o Directory authority changes:
27655 - Two directory authorities (moria1 and moria2) just moved to new
27656 IP addresses. This change will particularly affect those who serve
27657 or use hidden services.
27659 o Major bugfixes (crashes):
27660 - If a directory server runs out of space in the connection table
27661 as it's processing a begin_dir request, it will free the exit stream
27662 but leave it attached to the circuit, leading to unpredictable
27663 behavior. (Reported by seeess, fixes bug 425.)
27664 - Fix a bug in dirserv_remove_invalid() that would cause authorities
27665 to corrupt memory under some really unlikely scenarios.
27666 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
27667 - Avoid segfaults when reading from mmaped descriptor file. (Reported
27670 o Major bugfixes (security):
27671 - When choosing an entry guard for a circuit, avoid using guards
27672 that are in the same family as the chosen exit -- not just guards
27673 that are exactly the chosen exit. (Reported by lodger.)
27675 o Major bugfixes (resource management):
27676 - If a directory authority is down, skip it when deciding where to get
27677 networkstatus objects or descriptors. Otherwise we keep asking
27678 every 10 seconds forever. Fixes bug 384.
27679 - Count it as a failure if we fetch a valid network-status but we
27680 don't want to keep it. Otherwise we'll keep fetching it and keep
27681 not wanting to keep it. Fixes part of bug 422.
27682 - If all of our dirservers have given us bad or no networkstatuses
27683 lately, then stop hammering them once per minute even when we
27684 think they're failed. Fixes another part of bug 422.
27687 - Actually set the purpose correctly for descriptors inserted with
27688 purpose=controller.
27689 - When we have k non-v2 authorities in our DirServer config,
27690 we ignored the last k authorities in the list when updating our
27692 - Correctly back-off from requesting router descriptors that we are
27693 having a hard time downloading.
27694 - Read resolv.conf files correctly on platforms where read() returns
27695 partial results on small file reads.
27696 - Don't rebuild the entire router store every time we get 32K of
27697 routers: rebuild it when the journal gets very large, or when
27698 the gaps in the store get very large.
27701 - When routers publish SVN revisions in their router descriptors,
27702 authorities now include those versions correctly in networkstatus
27704 - Warn when using a version of libevent before 1.3b to run a server on
27705 OSX or BSD: these versions interact badly with userspace threads.
27708 Changes in version 0.1.2.13 - 2007-04-24
27709 This release features some major anonymity fixes, such as safer path
27710 selection; better client performance; faster bootstrapping, better
27711 address detection, and better DNS support for servers; write limiting as
27712 well as read limiting to make servers easier to run; and a huge pile of
27713 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
27715 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
27716 of the Freenode IRC network, remembering his patience and vision for
27717 free speech on the Internet.
27720 - Fix a memory leak when we ask for "all" networkstatuses and we
27721 get one we don't recognize.
27722 - Add more asserts to hunt down bug 417.
27723 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
27726 Changes in version 0.1.2.12-rc - 2007-03-16
27728 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
27729 directory information requested inside Tor connections (i.e. via
27730 begin_dir cells). It only triggered when the same connection was
27731 serving other data at the same time. Reported by seeess.
27734 - When creating a circuit via the controller, send a 'launched'
27735 event when we're done, so we follow the spec better.
27738 Changes in version 0.1.2.11-rc - 2007-03-15
27739 o Minor bugfixes (controller), reported by daejees:
27740 - Correct the control spec to match how the code actually responds
27741 to 'getinfo addr-mappings/*'.
27742 - The control spec described a GUARDS event, but the code
27743 implemented a GUARD event. Standardize on GUARD, but let people
27744 ask for GUARDS too.
27747 Changes in version 0.1.2.10-rc - 2007-03-07
27748 o Major bugfixes (Windows):
27749 - Do not load the NT services library functions (which may not exist)
27750 just to detect if we're a service trying to shut down. Now we run
27751 on Win98 and friends again.
27753 o Minor bugfixes (other):
27754 - Clarify a couple of log messages.
27755 - Fix a misleading socks5 error number.
27758 Changes in version 0.1.2.9-rc - 2007-03-02
27759 o Major bugfixes (Windows):
27760 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
27761 of the usual GCC "%llu". This prevents a bug when saving 64-bit
27762 int configuration values: the high-order 32 bits would get
27763 truncated. In particular, we were being bitten by the default
27764 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
27765 and maybe also bug 397.)
27767 o Minor bugfixes (performance):
27768 - Use OpenSSL's AES implementation on platforms where it's faster.
27769 This could save us as much as 10% CPU usage.
27771 o Minor bugfixes (server):
27772 - Do not rotate onion key immediately after setting it for the first
27775 o Minor bugfixes (directory authorities):
27776 - Stop calling servers that have been hibernating for a long time
27777 "stable". Also, stop letting hibernating or obsolete servers affect
27778 uptime and bandwidth cutoffs.
27779 - Stop listing hibernating servers in the v1 directory.
27781 o Minor bugfixes (hidden services):
27782 - Upload hidden service descriptors slightly less often, to reduce
27783 load on authorities.
27785 o Minor bugfixes (other):
27786 - Fix an assert that could trigger if a controller quickly set then
27787 cleared EntryNodes. Bug found by Udo van den Heuvel.
27788 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
27790 - Fix a potential race condition in the rpm installer. Found by
27792 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
27793 of 2 as indicating that the server is completely bad; it sometimes
27794 means that the server is just bad for the request in question. (may fix
27795 the last of bug 326.)
27796 - Disable encrypted directory connections when we don't have a server
27797 descriptor for the destination. We'll get this working again in
27801 Changes in version 0.1.2.8-beta - 2007-02-26
27802 o Major bugfixes (crashes):
27803 - Stop crashing when the controller asks us to resetconf more than
27804 one config option at once. (Vidalia 0.0.11 does this.)
27805 - Fix a crash that happened on Win98 when we're given command-line
27806 arguments: don't try to load NT service functions from advapi32.dll
27807 except when we need them. (Bug introduced in 0.1.2.7-alpha;
27809 - Fix a longstanding obscure crash bug that could occur when
27810 we run out of DNS worker processes. (Resolves bug 390.)
27812 o Major bugfixes (hidden services):
27813 - Correctly detect whether hidden service descriptor downloads are
27814 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
27816 o Major bugfixes (accounting):
27817 - When we start during an accounting interval before it's time to wake
27818 up, remember to wake up at the correct time. (May fix bug 342.)
27820 o Minor bugfixes (controller):
27821 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
27822 clear the corresponding on_circuit variable, and remember later
27823 that we don't need to send a redundant CLOSED event. Resolves part
27825 - Report events where a resolve succeeded or where we got a socks
27826 protocol error correctly, rather than calling both of them
27828 - Change reported stream target addresses to IP consistently when
27829 we finally get the IP from an exit node.
27830 - Send log messages to the controller even if they happen to be very
27833 o Minor bugfixes (other):
27834 - Display correct results when reporting which versions are
27835 recommended, and how recommended they are. (Resolves bug 383.)
27836 - Improve our estimates for directory bandwidth to be less random:
27837 guess that an unrecognized directory will have the average bandwidth
27838 from all known directories, not that it will have the average
27839 bandwidth from those directories earlier than it on the list.
27840 - If we start a server with ClientOnly 1, then set ClientOnly to 0
27841 and hup, stop triggering an assert based on an empty onion_key.
27842 - On platforms with no working mmap() equivalent, don't warn the
27843 user when cached-routers doesn't exist.
27844 - Warn the user when mmap() [or its equivalent] fails for some reason
27845 other than file-not-found.
27846 - Don't warn the user when cached-routers.new doesn't exist: that's
27847 perfectly fine when starting up for the first time.
27848 - When EntryNodes are configured, rebuild the guard list to contain,
27849 in order: the EntryNodes that were guards before; the rest of the
27850 EntryNodes; the nodes that were guards before.
27851 - Mask out all signals in sub-threads; only the libevent signal
27852 handler should be processing them. This should prevent some crashes
27853 on some machines using pthreads. (Patch from coderman.)
27854 - Fix switched arguments on memset in the implementation of
27855 tor_munmap() for systems with no mmap() call.
27856 - When Tor receives a router descriptor that it asked for, but
27857 no longer wants (because it has received fresh networkstatuses
27858 in the meantime), do not warn the user. Cache the descriptor if
27859 we're a cache; drop it if we aren't.
27860 - Make earlier entry guards _really_ get retried when the network
27862 - On a malformed DNS reply, always give an error to the corresponding
27864 - Build with recent libevents on platforms that do not define the
27865 nonstandard types "u_int8_t" and friends.
27867 o Minor features (controller):
27868 - Warn the user when an application uses the obsolete binary v0
27869 control protocol. We're planning to remove support for it during
27870 the next development series, so it's good to give people some
27872 - Add STREAM_BW events to report per-entry-stream bandwidth
27873 use. (Patch from Robert Hogan.)
27874 - Rate-limit SIGNEWNYM signals in response to controllers that
27875 impolitely generate them for every single stream. (Patch from
27876 mwenge; closes bug 394.)
27877 - Make REMAP stream events have a SOURCE (cache or exit), and
27878 make them generated in every case where we get a successful
27879 connected or resolved cell.
27881 o Minor bugfixes (performance):
27882 - Call router_have_min_dir_info half as often. (This is showing up in
27883 some profiles, but not others.)
27884 - When using GCC, make log_debug never get called at all, and its
27885 arguments never get evaluated, when no debug logs are configured.
27886 (This is showing up in some profiles, but not others.)
27889 - Remove some never-implemented options. Mark PathlenCoinWeight as
27891 - Implement proposal 106: Stop requiring clients to have well-formed
27892 certificates; stop checking nicknames in certificates. (Clients
27893 have certificates so that they can look like Tor servers, but in
27894 the future we might want to allow them to look like regular TLS
27895 clients instead. Nicknames in certificates serve no purpose other
27896 than making our protocol easier to recognize on the wire.)
27897 - Revise messages on handshake failure again to be even more clear about
27898 which are incoming connections and which are outgoing.
27899 - Discard any v1 directory info that's over 1 month old (for
27900 directories) or over 1 week old (for running-routers lists).
27901 - Do not warn when individual nodes in the configuration's EntryNodes,
27902 ExitNodes, etc are down: warn only when all possible nodes
27903 are down. (Fixes bug 348.)
27904 - Always remove expired routers and networkstatus docs before checking
27905 whether we have enough information to build circuits. (Fixes
27907 - Put a lower-bound on MaxAdvertisedBandwidth.
27910 Changes in version 0.1.2.7-alpha - 2007-02-06
27911 o Major bugfixes (rate limiting):
27912 - Servers decline directory requests much more aggressively when
27913 they're low on bandwidth. Otherwise they end up queueing more and
27914 more directory responses, which can't be good for latency.
27915 - But never refuse directory requests from local addresses.
27916 - Fix a memory leak when sending a 503 response for a networkstatus
27918 - Be willing to read or write on local connections (e.g. controller
27919 connections) even when the global rate limiting buckets are empty.
27920 - If our system clock jumps back in time, don't publish a negative
27921 uptime in the descriptor. Also, don't let the global rate limiting
27922 buckets go absurdly negative.
27923 - Flush local controller connection buffers periodically as we're
27924 writing to them, so we avoid queueing 4+ megabytes of data before
27927 o Major bugfixes (NT services):
27928 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
27929 command-line flag so that admins can override the default by saying
27930 "tor --service install --user "SomeUser"". This will not affect
27931 existing installed services. Also, warn the user that the service
27932 will look for its configuration file in the service user's
27933 %appdata% directory. (We can't do the 'hardwire the user's appdata
27934 directory' trick any more, since we may not have read access to that
27937 o Major bugfixes (other):
27938 - Previously, we would cache up to 16 old networkstatus documents
27939 indefinitely, if they came from nontrusted authorities. Now we
27940 discard them if they are more than 10 days old.
27941 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
27943 - Detect and reject malformed DNS responses containing circular
27945 - If exits are rare enough that we're not marking exits as guards,
27946 ignore exit bandwidth when we're deciding the required bandwidth
27948 - When we're handling a directory connection tunneled over Tor,
27949 don't fill up internal memory buffers with all the data we want
27950 to tunnel; instead, only add it if the OR connection that will
27951 eventually receive it has some room for it. (This can lead to
27952 slowdowns in tunneled dir connections; a better solution will have
27953 to wait for 0.2.0.)
27955 o Minor bugfixes (dns):
27956 - Add some defensive programming to eventdns.c in an attempt to catch
27957 possible memory-stomping bugs.
27958 - Detect and reject DNS replies containing IPv4 or IPv6 records with
27959 an incorrect number of bytes. (Previously, we would ignore the
27961 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
27962 in the correct order, and doesn't crash.
27963 - Free memory held in recently-completed DNS lookup attempts on exit.
27964 This was not a memory leak, but may have been hiding memory leaks.
27965 - Handle TTL values correctly on reverse DNS lookups.
27966 - Treat failure to parse resolv.conf as an error.
27968 o Minor bugfixes (other):
27969 - Fix crash with "tor --list-fingerprint" (reported by seeess).
27970 - When computing clock skew from directory HTTP headers, consider what
27971 time it was when we finished asking for the directory, not what
27973 - Expire socks connections if they spend too long waiting for the
27974 handshake to finish. Previously we would let them sit around for
27975 days, if the connecting application didn't close them either.
27976 - And if the socks handshake hasn't started, don't send a
27977 "DNS resolve socks failed" handshake reply; just close it.
27978 - Stop using C functions that OpenBSD's linker doesn't like.
27979 - Don't launch requests for descriptors unless we have networkstatuses
27980 from at least half of the authorities. This delays the first
27981 download slightly under pathological circumstances, but can prevent
27982 us from downloading a bunch of descriptors we don't need.
27983 - Do not log IPs with TLS failures for incoming TLS
27984 connections. (Fixes bug 382.)
27985 - If the user asks to use invalid exit nodes, be willing to use
27987 - Stop using the reserved ac_cv namespace in our configure script.
27988 - Call stat() slightly less often; use fstat() when possible.
27989 - Refactor the way we handle pending circuits when an OR connection
27990 completes or fails, in an attempt to fix a rare crash bug.
27991 - Only rewrite a conn's address based on X-Forwarded-For: headers
27992 if it's a parseable public IP address; and stop adding extra quotes
27993 to the resulting address.
27996 - Weight directory requests by advertised bandwidth. Now we can
27997 let servers enable write limiting but still allow most clients to
27998 succeed at their directory requests. (We still ignore weights when
27999 choosing a directory authority; I hope this is a feature.)
28002 - Create a new file ReleaseNotes which was the old ChangeLog. The
28003 new ChangeLog file now includes the summaries for all development
28005 - Check for addresses with invalid characters at the exit as well
28006 as at the client, and warn less verbosely when they fail. You can
28007 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
28008 - Adapt a patch from goodell to let the contrib/exitlist script
28009 take arguments rather than require direct editing.
28010 - Inform the server operator when we decide not to advertise a
28011 DirPort due to AccountingMax enabled or a low BandwidthRate. It
28012 was confusing Zax, so now we're hopefully more helpful.
28013 - Bring us one step closer to being able to establish an encrypted
28014 directory tunnel without knowing a descriptor first. Still not
28015 ready yet. As part of the change, now assume we can use a
28016 create_fast cell if we don't know anything about a router.
28017 - Allow exit nodes to use nameservers running on ports other than 53.
28018 - Servers now cache reverse DNS replies.
28019 - Add an --ignore-missing-torrc command-line option so that we can
28020 get the "use sensible defaults if the configuration file doesn't
28021 exist" behavior even when specifying a torrc location on the command
28024 o Minor features (controller):
28025 - Track reasons for OR connection failure; make these reasons
28026 available via the controller interface. (Patch from Mike Perry.)
28027 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
28028 can learn when clients are sending malformed hostnames to Tor.
28029 - Clean up documentation for controller status events.
28030 - Add a REMAP status to stream events to note that a stream's
28031 address has changed because of a cached address or a MapAddress
28035 Changes in version 0.1.2.6-alpha - 2007-01-09
28037 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
28038 connection handles more than 4 gigs in either direction, we crash.
28039 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
28040 advertised exit node, somebody might try to exit from us when
28041 we're bootstrapping and before we've built our descriptor yet.
28042 Refuse the connection rather than crashing.
28045 - Warn if we (as a server) find that we've resolved an address that we
28046 weren't planning to resolve.
28047 - Warn that using select() on any libevent version before 1.1 will be
28048 unnecessarily slow (even for select()).
28049 - Flush ERR-level controller status events just like we currently
28050 flush ERR-level log events, so that a Tor shutdown doesn't prevent
28051 the controller from learning about current events.
28053 o Minor features (more controller status events):
28054 - Implement EXTERNAL_ADDRESS server status event so controllers can
28055 learn when our address changes.
28056 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
28057 can learn when directories reject our descriptor.
28058 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
28059 can learn when a client application is speaking a non-socks protocol
28061 - Implement DANGEROUS_SOCKS client status event so controllers
28062 can learn when a client application is leaking DNS addresses.
28063 - Implement BUG general status event so controllers can learn when
28064 Tor is unhappy about its internal invariants.
28065 - Implement CLOCK_SKEW general status event so controllers can learn
28066 when Tor thinks the system clock is set incorrectly.
28067 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
28068 server status events so controllers can learn when their descriptors
28069 are accepted by a directory.
28070 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
28071 server status events so controllers can learn about Tor's progress in
28072 deciding whether it's reachable from the outside.
28073 - Implement BAD_LIBEVENT general status event so controllers can learn
28074 when we have a version/method combination in libevent that needs to
28076 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
28077 and DNS_USELESS server status events so controllers can learn
28078 about changes to DNS server status.
28080 o Minor features (directory):
28081 - Authorities no longer recommend exits as guards if this would shift
28082 too much load to the exit nodes.
28085 Changes in version 0.1.2.5-alpha - 2007-01-06
28087 - Enable write limiting as well as read limiting. Now we sacrifice
28088 capacity if we're pushing out lots of directory traffic, rather
28089 than overrunning the user's intended bandwidth limits.
28090 - Include TLS overhead when counting bandwidth usage; previously, we
28091 would count only the bytes sent over TLS, but not the bytes used
28093 - Support running the Tor service with a torrc not in the same
28094 directory as tor.exe and default to using the torrc located in
28095 the %appdata%\Tor\ of the user who installed the service. Patch
28097 - Servers now check for the case when common DNS requests are going to
28098 wildcarded addresses (i.e. all getting the same answer), and change
28099 their exit policy to reject *:* if it's happening.
28100 - Implement BEGIN_DIR cells, so we can connect to the directory
28101 server via TLS to do encrypted directory requests rather than
28102 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
28103 config options if you like.
28105 o Minor features (config and docs):
28106 - Start using the state file to store bandwidth accounting data:
28107 the bw_accounting file is now obsolete. We'll keep generating it
28108 for a while for people who are still using 0.1.2.4-alpha.
28109 - Try to batch changes to the state file so that we do as few
28110 disk writes as possible while still storing important things in
28112 - The state file and the bw_accounting file get saved less often when
28113 the AvoidDiskWrites config option is set.
28114 - Make PIDFile work on Windows (untested).
28115 - Add internal descriptions for a bunch of configuration options:
28116 accessible via controller interface and in comments in saved
28118 - Reject *:563 (NNTPS) in the default exit policy. We already reject
28119 NNTP by default, so this seems like a sensible addition.
28120 - Clients now reject hostnames with invalid characters. This should
28121 avoid some inadvertent info leaks. Add an option
28122 AllowNonRFC953Hostnames to disable this behavior, in case somebody
28123 is running a private network with hosts called @, !, and #.
28124 - Add a maintainer script to tell us which options are missing
28125 documentation: "make check-docs".
28126 - Add a new address-spec.txt document to describe our special-case
28127 addresses: .exit, .onion, and .noconnnect.
28129 o Minor features (DNS):
28130 - Ongoing work on eventdns infrastructure: now it has dns server
28131 and ipv6 support. One day Tor will make use of it.
28132 - Add client-side caching for reverse DNS lookups.
28133 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
28134 - When we change nameservers or IP addresses, reset and re-launch
28135 our tests for DNS hijacking.
28137 o Minor features (directory):
28138 - Authorities now specify server versions in networkstatus. This adds
28139 about 2% to the size of compressed networkstatus docs, and allows
28140 clients to tell which servers support BEGIN_DIR and which don't.
28141 The implementation is forward-compatible with a proposed future
28142 protocol version scheme not tied to Tor versions.
28143 - DirServer configuration lines now have an orport= option so
28144 clients can open encrypted tunnels to the authorities without
28145 having downloaded their descriptors yet. Enabled for moria1,
28146 moria2, tor26, and lefkada now in the default configuration.
28147 - Directory servers are more willing to send a 503 "busy" if they
28148 are near their write limit, especially for v1 directory requests.
28149 Now they can use their limited bandwidth for actual Tor traffic.
28150 - Clients track responses with status 503 from dirservers. After a
28151 dirserver has given us a 503, we try not to use it until an hour has
28152 gone by, or until we have no dirservers that haven't given us a 503.
28153 - When we get a 503 from a directory, and we're not a server, we don't
28154 count the failure against the total number of failures allowed
28155 for the thing we're trying to download.
28156 - Report X-Your-Address-Is correctly from tunneled directory
28157 connections; don't report X-Your-Address-Is when it's an internal
28158 address; and never believe reported remote addresses when they're
28160 - Protect against an unlikely DoS attack on directory servers.
28161 - Add a BadDirectory flag to network status docs so that authorities
28162 can (eventually) tell clients about caches they believe to be
28165 o Minor features (controller):
28166 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
28167 - Reimplement GETINFO so that info/names stays in sync with the
28169 - Implement "GETINFO fingerprint".
28170 - Implement "SETEVENTS GUARD" so controllers can get updates on
28171 entry guard status as it changes.
28173 o Minor features (clean up obsolete pieces):
28174 - Remove some options that have been deprecated since at least
28175 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
28176 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
28177 to set log options.
28178 - We no longer look for identity and onion keys in "identity.key" and
28179 "onion.key" -- these were replaced by secret_id_key and
28180 secret_onion_key in 0.0.8pre1.
28181 - We no longer require unrecognized directory entries to be
28184 o Major bugfixes (security):
28185 - Stop sending the HttpProxyAuthenticator string to directory
28186 servers when directory connections are tunnelled through Tor.
28187 - Clients no longer store bandwidth history in the state file.
28188 - Do not log introduction points for hidden services if SafeLogging
28190 - When generating bandwidth history, round down to the nearest
28191 1k. When storing accounting data, round up to the nearest 1k.
28192 - When we're running as a server, remember when we last rotated onion
28193 keys, so that we will rotate keys once they're a week old even if
28194 we never stay up for a week ourselves.
28196 o Major bugfixes (other):
28197 - Fix a longstanding bug in eventdns that prevented the count of
28198 timed-out resolves from ever being reset. This bug caused us to
28199 give up on a nameserver the third time it timed out, and try it
28200 10 seconds later... and to give up on it every time it timed out
28202 - Take out the '5 second' timeout from the connection retry
28203 schedule. Now the first connect attempt will wait a full 10
28204 seconds before switching to a new circuit. Perhaps this will help
28205 a lot. Based on observations from Mike Perry.
28206 - Fix a bug on the Windows implementation of tor_mmap_file() that
28207 would prevent the cached-routers file from ever loading. Reported
28211 - Fix an assert failure when a directory authority sets
28212 AuthDirRejectUnlisted and then receives a descriptor from an
28213 unlisted router. Reported by seeess.
28214 - Avoid a double-free when parsing malformed DirServer lines.
28215 - Fix a bug when a BSD-style PF socket is first used. Patch from
28217 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
28218 to resolve an address at a given exit node even when they ask for
28220 - Servers no longer ever list themselves in their "family" line,
28221 even if configured to do so. This makes it easier to configure
28222 family lists conveniently.
28223 - When running as a server, don't fall back to 127.0.0.1 when no
28224 nameservers are configured in /etc/resolv.conf; instead, make the
28225 user fix resolv.conf or specify nameservers explicitly. (Resolves
28227 - Stop accepting certain malformed ports in configured exit policies.
28228 - Don't re-write the fingerprint file every restart, unless it has
28230 - Stop warning when a single nameserver fails: only warn when _all_ of
28231 our nameservers have failed. Also, when we only have one nameserver,
28232 raise the threshold for deciding that the nameserver is dead.
28233 - Directory authorities now only decide that routers are reachable
28234 if their identity keys are as expected.
28235 - When the user uses bad syntax in the Log config line, stop
28236 suggesting other bad syntax as a replacement.
28237 - Correctly detect ipv6 DNS capability on OpenBSD.
28239 o Minor bugfixes (controller):
28240 - Report the circuit number correctly in STREAM CLOSED events. Bug
28241 reported by Mike Perry.
28242 - Do not report bizarre values for results of accounting GETINFOs
28243 when the last second's write or read exceeds the allotted bandwidth.
28244 - Report "unrecognized key" rather than an empty string when the
28245 controller tries to fetch a networkstatus that doesn't exist.
28248 Changes in version 0.1.1.26 - 2006-12-14
28249 o Security bugfixes:
28250 - Stop sending the HttpProxyAuthenticator string to directory
28251 servers when directory connections are tunnelled through Tor.
28252 - Clients no longer store bandwidth history in the state file.
28253 - Do not log introduction points for hidden services if SafeLogging
28257 - Fix an assert failure when a directory authority sets
28258 AuthDirRejectUnlisted and then receives a descriptor from an
28259 unlisted router (reported by seeess).
28262 Changes in version 0.1.2.4-alpha - 2006-12-03
28264 - Add support for using natd; this allows FreeBSDs earlier than
28265 5.1.2 to have ipfw send connections through Tor without using
28266 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
28269 - Make all connections to addresses of the form ".noconnect"
28270 immediately get closed. This lets application/controller combos
28271 successfully test whether they're talking to the same Tor by
28272 watching for STREAM events.
28273 - Make cross.sh cross-compilation script work even when autogen.sh
28274 hasn't been run. (Patch from Michael Mohr.)
28275 - Statistics dumped by -USR2 now include a breakdown of public key
28276 operations, for profiling.
28279 - Fix a major leak when directory authorities parse their
28280 approved-routers list, a minor memory leak when we fail to pick
28281 an exit node, and a few rare leaks on errors.
28282 - Handle TransPort connections even when the server sends data before
28283 the client sends data. Previously, the connection would just hang
28284 until the client sent data. (Patch from tup based on patch from
28286 - Avoid assert failure when our cached-routers file is empty on
28290 - Don't log spurious warnings when we see a circuit close reason we
28291 don't recognize; it's probably just from a newer version of Tor.
28292 - Have directory authorities allow larger amounts of drift in uptime
28293 without replacing the server descriptor: previously, a server that
28294 restarted every 30 minutes could have 48 "interesting" descriptors
28296 - Start linking to the Tor specification and Tor reference manual
28297 correctly in the Windows installer.
28298 - Add Vidalia to the OS X uninstaller script, so when we uninstall
28299 Tor/Privoxy we also uninstall Vidalia.
28300 - Resume building on Irix64, and fix a lot of warnings from its
28301 MIPSpro C compiler.
28302 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
28303 when we're running as a client.
28306 Changes in version 0.1.1.25 - 2006-11-04
28308 - When a client asks us to resolve (rather than connect to)
28309 an address, and we have a cached answer, give them the cached
28310 answer. Previously, we would give them no answer at all.
28311 - We were building exactly the wrong circuits when we predict
28312 hidden service requirements, meaning Tor would have to build all
28313 its circuits on demand.
28314 - If none of our live entry guards have a high uptime, but we
28315 require a guard with a high uptime, try adding a new guard before
28316 we give up on the requirement. This patch should make long-lived
28317 connections more stable on average.
28318 - When testing reachability of our DirPort, don't launch new
28319 tests when there's already one in progress -- unreachable
28320 servers were stacking up dozens of testing streams.
28322 o Security bugfixes:
28323 - When the user sends a NEWNYM signal, clear the client-side DNS
28324 cache too. Otherwise we continue to act on previous information.
28327 - Avoid a memory corruption bug when creating a hash table for
28329 - Avoid possibility of controller-triggered crash when misusing
28330 certain commands from a v0 controller on platforms that do not
28331 handle printf("%s",NULL) gracefully.
28332 - Avoid infinite loop on unexpected controller input.
28333 - Don't log spurious warnings when we see a circuit close reason we
28334 don't recognize; it's probably just from a newer version of Tor.
28335 - Add Vidalia to the OS X uninstaller script, so when we uninstall
28336 Tor/Privoxy we also uninstall Vidalia.
28339 Changes in version 0.1.2.3-alpha - 2006-10-29
28341 - Prepare for servers to publish descriptors less often: never
28342 discard a descriptor simply for being too old until either it is
28343 recommended by no authorities, or until we get a better one for
28344 the same router. Make caches consider retaining old recommended
28345 routers for even longer.
28346 - If most authorities set a BadExit flag for a server, clients
28347 don't think of it as a general-purpose exit. Clients only consider
28348 authorities that advertise themselves as listing bad exits.
28349 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
28350 headers for content, so that we can work better in the presence of
28351 caching HTTP proxies.
28352 - Allow authorities to list nodes as bad exits by fingerprint or by
28355 o Minor features, controller:
28356 - Add a REASON field to CIRC events; for backward compatibility, this
28357 field is sent only to controllers that have enabled the extended
28358 event format. Also, add additional reason codes to explain why
28359 a given circuit has been destroyed or truncated. (Patches from
28361 - Add a REMOTE_REASON field to extended CIRC events to tell the
28362 controller about why a remote OR told us to close a circuit.
28363 - Stream events also now have REASON and REMOTE_REASON fields,
28364 working much like those for circuit events.
28365 - There's now a GETINFO ns/... field so that controllers can ask Tor
28366 about the current status of a router.
28367 - A new event type "NS" to inform a controller when our opinion of
28368 a router's status has changed.
28369 - Add a GETINFO events/names and GETINFO features/names so controllers
28370 can tell which events and features are supported.
28371 - A new CLEARDNSCACHE signal to allow controllers to clear the
28372 client-side DNS cache without expiring circuits.
28374 o Security bugfixes:
28375 - When the user sends a NEWNYM signal, clear the client-side DNS
28376 cache too. Otherwise we continue to act on previous information.
28379 - Avoid sending junk to controllers or segfaulting when a controller
28380 uses EVENT_NEW_DESC with verbose nicknames.
28381 - Stop triggering asserts if the controller tries to extend hidden
28382 service circuits (reported by mwenge).
28383 - Avoid infinite loop on unexpected controller input.
28384 - When the controller does a "GETINFO network-status", tell it
28385 about even those routers whose descriptors are very old, and use
28386 long nicknames where appropriate.
28387 - Change NT service functions to be loaded on demand. This lets us
28388 build with MinGW without breaking Tor for Windows 98 users.
28389 - Do DirPort reachability tests less often, since a single test
28390 chews through many circuits before giving up.
28391 - In the hidden service example in torrc.sample, stop recommending
28392 esoteric and discouraged hidden service options.
28393 - When stopping an NT service, wait up to 10 sec for it to actually
28394 stop. Patch from Matt Edman; resolves bug 295.
28395 - Fix handling of verbose nicknames with ORCONN controller events:
28396 make them show up exactly when requested, rather than exactly when
28398 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
28399 printing a duplicate "$" in the keys we send (reported by mwenge).
28400 - Correctly set maximum connection limit on Cygwin. (This time
28402 - Try to detect Windows correctly when cross-compiling.
28403 - Detect the size of the routers file correctly even if it is
28404 corrupted (on systems without mmap) or not page-aligned (on systems
28405 with mmap). This bug was harmless.
28406 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
28407 to open a stream fails; now we do in more cases. This should
28408 make clients able to find a good exit faster in some cases, since
28409 unhandleable requests will now get an error rather than timing out.
28410 - Resolve two memory leaks when rebuilding the on-disk router cache
28411 (reported by fookoowa).
28412 - Clean up minor code warnings suggested by the MIPSpro C compiler,
28413 and reported by some Centos users.
28414 - Controller signals now work on non-Unix platforms that don't define
28415 SIGUSR1 and SIGUSR2 the way we expect.
28416 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
28417 values before failing, and always enables eventdns.
28418 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
28419 Try to fix this in configure.in by checking for most functions
28420 before we check for libevent.
28423 Changes in version 0.1.2.2-alpha - 2006-10-07
28425 - Make our async eventdns library on-by-default for Tor servers,
28426 and plan to deprecate the separate dnsworker threads.
28427 - Add server-side support for "reverse" DNS lookups (using PTR
28428 records so clients can determine the canonical hostname for a given
28429 IPv4 address). Only supported by servers using eventdns; servers
28430 now announce in their descriptors whether they support eventdns.
28431 - Specify and implement client-side SOCKS5 interface for reverse DNS
28432 lookups (see doc/socks-extensions.txt).
28433 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
28434 connect to directory servers through Tor. Previously, clients needed
28435 to find Tor exits to make private connections to directory servers.
28436 - Avoid choosing Exit nodes for entry or middle hops when the
28437 total bandwidth available from non-Exit nodes is much higher than
28438 the total bandwidth available from Exit nodes.
28439 - Workaround for name servers (like Earthlink's) that hijack failing
28440 DNS requests and replace the no-such-server answer with a "helpful"
28441 redirect to an advertising-driven search portal. Also work around
28442 DNS hijackers who "helpfully" decline to hijack known-invalid
28443 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
28444 lets you turn it off.
28445 - Send out a burst of long-range padding cells once we've established
28446 that we're reachable. Spread them over 4 circuits, so hopefully
28447 a few will be fast. This exercises our bandwidth and bootstraps
28448 us into the directory more quickly.
28450 o New/improved config options:
28451 - Add new config option "ResolvConf" to let the server operator
28452 choose an alternate resolve.conf file when using eventdns.
28453 - Add an "EnforceDistinctSubnets" option to control our "exclude
28454 servers on the same /16" behavior. It's still on by default; this
28455 is mostly for people who want to operate private test networks with
28456 all the machines on the same subnet.
28457 - If one of our entry guards is on the ExcludeNodes list, or the
28458 directory authorities don't think it's a good guard, treat it as
28459 if it were unlisted: stop using it as a guard, and throw it off
28460 the guards list if it stays that way for a long time.
28461 - Allow directory authorities to be marked separately as authorities
28462 for the v1 directory protocol, the v2 directory protocol, and
28463 as hidden service directories, to make it easier to retire old
28464 authorities. V1 authorities should set "HSAuthoritativeDir 1"
28465 to continue being hidden service authorities too.
28466 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
28468 o Minor features, controller:
28469 - Fix CIRC controller events so that controllers can learn the
28470 identity digests of non-Named servers used in circuit paths.
28471 - Let controllers ask for more useful identifiers for servers. Instead
28472 of learning identity digests for un-Named servers and nicknames
28473 for Named servers, the new identifiers include digest, nickname,
28474 and indication of Named status. Off by default; see control-spec.txt
28475 for more information.
28476 - Add a "getinfo address" controller command so it can display Tor's
28477 best guess to the user.
28478 - New controller event to alert the controller when our server
28479 descriptor has changed.
28480 - Give more meaningful errors on controller authentication failure.
28482 o Minor features, other:
28483 - When asked to resolve a hostname, don't use non-exit servers unless
28484 requested to do so. This allows servers with broken DNS to be
28485 useful to the network.
28486 - Divide eventdns log messages into warn and info messages.
28487 - Reserve the nickname "Unnamed" for routers that can't pick
28488 a hostname: any router can call itself Unnamed; directory
28489 authorities will never allocate Unnamed to any particular router;
28490 clients won't believe that any router is the canonical Unnamed.
28491 - Only include function names in log messages for info/debug messages.
28492 For notice/warn/err, the content of the message should be clear on
28493 its own, and printing the function name only confuses users.
28494 - Avoid some false positives during reachability testing: don't try
28495 to test via a server that's on the same /24 as us.
28496 - If we fail to build a circuit to an intended enclave, and it's
28497 not mandatory that we use that enclave, stop wanting it.
28498 - When eventdns is enabled, allow multithreaded builds on NetBSD and
28499 OpenBSD. (We had previously disabled threads on these platforms
28500 because they didn't have working thread-safe resolver functions.)
28502 o Major bugfixes, anonymity/security:
28503 - If a client asked for a server by name, and there's a named server
28504 in our network-status but we don't have its descriptor yet, we
28505 could return an unnamed server instead.
28506 - Fix NetBSD bug that could allow someone to force uninitialized RAM
28507 to be sent to a server's DNS resolver. This only affects NetBSD
28508 and other platforms that do not bounds-check tolower().
28509 - Reject (most) attempts to use Tor circuits with length one. (If
28510 many people start using Tor as a one-hop proxy, exit nodes become
28511 a more attractive target for compromise.)
28512 - Just because your DirPort is open doesn't mean people should be
28513 able to remotely teach you about hidden service descriptors. Now
28514 only accept rendezvous posts if you've got HSAuthoritativeDir set.
28516 o Major bugfixes, other:
28517 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
28518 - When a client asks the server to resolve (not connect to)
28519 an address, and it has a cached answer, give them the cached answer.
28520 Previously, the server would give them no answer at all.
28521 - Allow really slow clients to not hang up five minutes into their
28522 directory downloads (suggested by Adam J. Richter).
28523 - We were building exactly the wrong circuits when we anticipated
28524 hidden service requirements, meaning Tor would have to build all
28525 its circuits on demand.
28526 - Avoid crashing when we mmap a router cache file of size 0.
28527 - When testing reachability of our DirPort, don't launch new
28528 tests when there's already one in progress -- unreachable
28529 servers were stacking up dozens of testing streams.
28531 o Minor bugfixes, correctness:
28532 - If we're a directory mirror and we ask for "all" network status
28533 documents, we would discard status documents from authorities
28534 we don't recognize.
28535 - Avoid a memory corruption bug when creating a hash table for
28537 - Avoid controller-triggered crash when misusing certain commands
28538 from a v0 controller on platforms that do not handle
28539 printf("%s",NULL) gracefully.
28540 - Don't crash when a controller sends a third argument to an
28541 "extendcircuit" request.
28542 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
28543 response; fix error code when "getinfo dir/status/" fails.
28544 - Avoid crash when telling controller stream-status and a stream
28546 - Patch from Adam Langley to fix assert() in eventdns.c.
28547 - Fix a debug log message in eventdns to say "X resolved to Y"
28548 instead of "X resolved to X".
28549 - Make eventdns give strings for DNS errors, not just error numbers.
28550 - Track unreachable entry guards correctly: don't conflate
28551 'unreachable by us right now' with 'listed as down by the directory
28552 authorities'. With the old code, if a guard was unreachable by
28553 us but listed as running, it would clog our guard list forever.
28554 - Behave correctly in case we ever have a network with more than
28555 2GB/s total advertised capacity.
28556 - Make TrackExitHosts case-insensitive, and fix the behavior of
28557 ".suffix" TrackExitHosts items to avoid matching in the middle of
28559 - Finally fix the openssl warnings from newer gccs that believe that
28560 ignoring a return value is okay, but casting a return value and
28561 then ignoring it is a sign of madness.
28562 - Prevent the contrib/exitlist script from printing the same
28563 result more than once.
28564 - Patch from Steve Hildrey: Generate network status correctly on
28565 non-versioning dirservers.
28566 - Don't listen to the X-Your-Address-Is hint if you did the lookup
28567 via Tor; otherwise you'll think you're the exit node's IP address.
28569 o Minor bugfixes, performance:
28570 - Two small performance improvements on parsing descriptors.
28571 - Major performance improvement on inserting descriptors: change
28572 algorithm from O(n^2) to O(n).
28573 - Make the common memory allocation path faster on machines where
28574 malloc(0) returns a pointer.
28575 - Start remembering X-Your-Address-Is directory hints even if you're
28576 a client, so you can become a server more smoothly.
28577 - Avoid duplicate entries on MyFamily line in server descriptor.
28579 o Packaging, features:
28580 - Remove architecture from OS X builds. The official builds are
28581 now universal binaries.
28582 - The Debian package now uses --verify-config when (re)starting,
28583 to distinguish configuration errors from other errors.
28584 - Update RPMs to require libevent 1.1b.
28586 o Packaging, bugfixes:
28587 - Patches so Tor builds with MinGW on Windows.
28588 - Patches so Tor might run on Cygwin again.
28589 - Resume building on non-gcc compilers and ancient gcc. Resume
28590 building with the -O0 compile flag. Resume building cleanly on
28592 - Run correctly on OS X platforms with case-sensitive filesystems.
28593 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
28594 - Add autoconf checks so Tor can build on Solaris x86 again.
28597 - Documented (and renamed) ServerDNSSearchDomains and
28598 ServerDNSResolvConfFile options.
28599 - Be clearer that the *ListenAddress directives can be repeated
28603 Changes in version 0.1.1.24 - 2006-09-29
28605 - Allow really slow clients to not hang up five minutes into their
28606 directory downloads (suggested by Adam J. Richter).
28607 - Fix major performance regression from 0.1.0.x: instead of checking
28608 whether we have enough directory information every time we want to
28609 do something, only check when the directory information has changed.
28610 This should improve client CPU usage by 25-50%.
28611 - Don't crash if, after a server has been running for a while,
28612 it can't resolve its hostname.
28615 - Allow Tor to start when RunAsDaemon is set but no logs are set.
28616 - Don't crash when the controller receives a third argument to an
28617 "extendcircuit" request.
28618 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
28619 response; fix error code when "getinfo dir/status/" fails.
28620 - Fix configure.in to not produce broken configure files with
28621 more recent versions of autoconf. Thanks to Clint for his auto*
28623 - Fix security bug on NetBSD that could allow someone to force
28624 uninitialized RAM to be sent to a server's DNS resolver. This
28625 only affects NetBSD and other platforms that do not bounds-check
28627 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
28628 methods: these are known to be buggy.
28629 - If we're a directory mirror and we ask for "all" network status
28630 documents, we would discard status documents from authorities
28631 we don't recognize.
28634 Changes in version 0.1.2.1-alpha - 2006-08-27
28636 - Add "eventdns" async dns library from Adam Langley, tweaked to
28637 build on OSX and Windows. Only enabled if you pass the
28638 --enable-eventdns argument to configure.
28639 - Allow servers with no hostname or IP address to learn their
28640 IP address by asking the directory authorities. This code only
28641 kicks in when you would normally have exited with a "no address"
28642 error. Nothing's authenticated, so use with care.
28643 - Rather than waiting a fixed amount of time between retrying
28644 application connections, we wait only 5 seconds for the first,
28645 10 seconds for the second, and 15 seconds for each retry after
28646 that. Hopefully this will improve the expected user experience.
28647 - Patch from Tup to add support for transparent AP connections:
28648 this basically bundles the functionality of trans-proxy-tor
28649 into the Tor mainline. Now hosts with compliant pf/netfilter
28650 implementations can redirect TCP connections straight to Tor
28651 without diverting through SOCKS. Needs docs.
28652 - Busy directory servers save lots of memory by spooling server
28653 descriptors, v1 directories, and v2 networkstatus docs to buffers
28654 as needed rather than en masse. Also mmap the cached-routers
28655 files, so we don't need to keep the whole thing in memory too.
28656 - Automatically avoid picking more than one node from the same
28657 /16 network when constructing a circuit.
28658 - Revise and clean up the torrc.sample that we ship with; add
28659 a section for BandwidthRate and BandwidthBurst.
28662 - Split circuit_t into origin_circuit_t and or_circuit_t, and
28663 split connection_t into edge, or, dir, control, and base structs.
28664 These will save quite a bit of memory on busy servers, and they'll
28665 also help us track down bugs in the code and bugs in the spec.
28666 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
28667 or later. Log when we are doing this, so we can diagnose it when
28668 it fails. (Also, recommend libevent 1.1b for kqueue and
28669 win32 methods; deprecate libevent 1.0b harder; make libevent
28670 recommendation system saner.)
28671 - Start being able to build universal binaries on OS X (thanks
28673 - Export the default exit policy via the control port, so controllers
28674 don't need to guess what it is / will be later.
28675 - Add a man page entry for ProtocolWarnings.
28676 - Add TestVia config option to the man page.
28677 - Remove even more protocol-related warnings from Tor server logs,
28678 such as bad TLS handshakes and malformed begin cells.
28679 - Stop fetching descriptors if you're not a dir mirror and you
28680 haven't tried to establish any circuits lately. [This currently
28681 causes some dangerous behavior, because when you start up again
28682 you'll use your ancient server descriptors.]
28683 - New DirPort behavior: if you have your dirport set, you download
28684 descriptors aggressively like a directory mirror, whether or not
28685 your ORPort is set.
28686 - Get rid of the router_retry_connections notion. Now routers
28687 no longer try to rebuild long-term connections to directory
28688 authorities, and directory authorities no longer try to rebuild
28689 long-term connections to all servers. We still don't hang up
28690 connections in these two cases though -- we need to look at it
28691 more carefully to avoid flapping, and we likely need to wait til
28692 0.1.1.x is obsolete.
28693 - Drop compatibility with obsolete Tors that permit create cells
28694 to have the wrong circ_id_type.
28695 - Re-enable per-connection rate limiting. Get rid of the "OP
28696 bandwidth" concept. Lay groundwork for "bandwidth classes" --
28697 separate global buckets that apply depending on what sort of conn
28699 - Start publishing one minute or so after we find our ORPort
28700 to be reachable. This will help reduce the number of descriptors
28701 we have for ourselves floating around, since it's quite likely
28702 other things (e.g. DirPort) will change during that minute too.
28703 - Fork the v1 directory protocol into its own spec document,
28704 and mark dir-spec.txt as the currently correct (v2) spec.
28707 - When we find our DirPort to be reachable, publish a new descriptor
28708 so we'll tell the world (reported by pnx).
28709 - Publish a new descriptor after we hup/reload. This is important
28710 if our config has changed such that we'll want to start advertising
28711 our DirPort now, etc.
28712 - Allow Tor to start when RunAsDaemon is set but no logs are set.
28713 - When we have a state file we cannot parse, tell the user and
28714 move it aside. Now we avoid situations where the user starts
28715 Tor in 1904, Tor writes a state file with that timestamp in it,
28716 the user fixes her clock, and Tor refuses to start.
28717 - Fix configure.in to not produce broken configure files with
28718 more recent versions of autoconf. Thanks to Clint for his auto*
28720 - "tor --verify-config" now exits with -1(255) or 0 depending on
28721 whether the config options are bad or good.
28722 - Resolve bug 321 when using dnsworkers: append a period to every
28723 address we resolve at the exit node, so that we do not accidentally
28724 pick up local addresses, and so that failing searches are retried
28725 in the resolver search domains. (This is already solved for
28726 eventdns.) (This breaks Blossom servers for now.)
28727 - If we are using an exit enclave and we can't connect, e.g. because
28728 its webserver is misconfigured to not listen on localhost, then
28729 back off and try connecting from somewhere else before we fail.
28732 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
28733 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
28734 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
28735 when the IP address is mapped through MapAddress to a hostname.
28736 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
28737 useless IPv6 DNS resolves.
28738 - Patch suggested by Karsten Loesing: respond to SIGNAL command
28739 before we execute the signal, in case the signal shuts us down.
28740 - Clean up AllowInvalidNodes man page entry.
28741 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
28742 - Add more asserts to track down an assert error on a windows Tor
28743 server with connection_add being called with socket == -1.
28744 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
28745 - Fix misleading log messages: an entry guard that is "unlisted",
28746 as well as not known to be "down" (because we've never heard
28747 of it), is not therefore "up".
28748 - Remove code to special-case "-cvs" ending, since it has not
28749 actually mattered since 0.0.9.
28750 - Make our socks5 handling more robust to broken socks clients:
28751 throw out everything waiting on the buffer in between socks
28752 handshake phases, since they can't possibly (so the theory
28753 goes) have predicted what we plan to respond to them.
28756 Changes in version 0.1.1.23 - 2006-07-30
28758 - Fast Tor servers, especially exit nodes, were triggering asserts
28759 due to a bug in handling the list of pending DNS resolves. Some
28760 bugs still remain here; we're hunting them.
28761 - Entry guards could crash clients by sending unexpected input.
28762 - More fixes on reachability testing: if you find yourself reachable,
28763 then don't ever make any client requests (so you stop predicting
28764 circuits), then hup or have your clock jump, then later your IP
28765 changes, you won't think circuits are working, so you won't try to
28766 test reachability, so you won't publish.
28769 - Avoid a crash if the controller does a resetconf firewallports
28770 and then a setconf fascistfirewall=1.
28771 - Avoid an integer underflow when the dir authority decides whether
28772 a router is stable: we might wrongly label it stable, and compute
28773 a slightly wrong median stability, when a descriptor is published
28775 - Fix a place where we might trigger an assert if we can't build our
28776 own server descriptor yet.
28779 Changes in version 0.1.1.22 - 2006-07-05
28781 - Fix a big bug that was causing servers to not find themselves
28782 reachable if they changed IP addresses. Since only 0.1.1.22+
28783 servers can do reachability testing correctly, now we automatically
28784 make sure to test via one of these.
28785 - Fix to allow clients and mirrors to learn directory info from
28786 descriptor downloads that get cut off partway through.
28787 - Directory authorities had a bug in deciding if a newly published
28788 descriptor was novel enough to make everybody want a copy -- a few
28789 servers seem to be publishing new descriptors many times a minute.
28791 - Fix a rare bug that was causing some servers to complain about
28792 "closing wedged cpuworkers" and skip some circuit create requests.
28793 - Make the Exit flag in directory status documents actually work.
28796 Changes in version 0.1.1.21 - 2006-06-10
28797 o Crash and assert fixes from 0.1.1.20:
28798 - Fix a rare crash on Tor servers that have enabled hibernation.
28799 - Fix a seg fault on startup for Tor networks that use only one
28800 directory authority.
28801 - Fix an assert from a race condition that occurs on Tor servers
28802 while exiting, where various threads are trying to log that they're
28803 exiting, and delete the logs, at the same time.
28804 - Make our unit tests pass again on certain obscure platforms.
28807 - Add support for building SUSE RPM packages.
28808 - Speed up initial bootstrapping for clients: if we are making our
28809 first ever connection to any entry guard, then don't mark it down
28811 - When only one Tor server in the network is labelled as a guard,
28812 and we've already picked him, we would cycle endlessly picking him
28813 again, being unhappy about it, etc. Now we specifically exclude
28814 current guards when picking a new guard.
28815 - Servers send create cells more reliably after the TLS connection
28816 is established: we were sometimes forgetting to send half of them
28817 when we had more than one pending.
28818 - If we get a create cell that asks us to extend somewhere, but the
28819 Tor server there doesn't match the expected digest, we now send
28820 a destroy cell back, rather than silently doing nothing.
28821 - Make options->RedirectExit work again.
28822 - Make cookie authentication for the controller work again.
28823 - Stop being picky about unusual characters in the arguments to
28824 mapaddress. It's none of our business.
28825 - Add a new config option "TestVia" that lets you specify preferred
28826 middle hops to use for test circuits. Perhaps this will let me
28827 debug the reachability problems better.
28829 o Log / documentation fixes:
28830 - If we're a server and some peer has a broken TLS certificate, don't
28831 log about it unless ProtocolWarnings is set, i.e., we want to hear
28832 about protocol violations by others.
28833 - Fix spelling of VirtualAddrNetwork in man page.
28834 - Add a better explanation at the top of the autogenerated torrc file
28835 about what happened to our old torrc.
28838 Changes in version 0.1.1.20 - 2006-05-23
28840 - Downgrade a log severity where servers complain that they're
28842 - Avoid a compile warning on FreeBSD.
28843 - Remove string size limit on NEWDESC messages; solve bug 291.
28844 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
28845 more thoroughly when we're running on windows.
28848 Changes in version 0.1.1.19-rc - 2006-05-03
28850 - Regenerate our local descriptor if it's dirty and we try to use
28851 it locally (e.g. if it changes during reachability detection).
28852 - If we setconf our ORPort to 0, we continued to listen on the
28853 old ORPort and receive connections.
28854 - Avoid a second warning about machine/limits.h on Debian
28856 - Be willing to add our own routerinfo into the routerlist.
28857 Now authorities will include themselves in their directories
28858 and network-statuses.
28859 - Stop trying to upload rendezvous descriptors to every
28860 directory authority: only try the v1 authorities.
28861 - Servers no longer complain when they think they're not
28862 registered with the directory authorities. There were too many
28864 - Backport dist-rpm changes so rpms can be built without errors.
28867 - Implement an option, VirtualAddrMask, to set which addresses
28868 get handed out in response to mapaddress requests. This works
28869 around a bug in tsocks where 127.0.0.0/8 is never socksified.
28872 Changes in version 0.1.1.18-rc - 2006-04-10
28874 - Work harder to download live network-statuses from all the
28875 directory authorities we know about. Improve the threshold
28876 decision logic so we're more robust to edge cases.
28877 - When fetching rendezvous descriptors, we were willing to ask
28878 v2 authorities too, which would always return 404.
28881 - Stop listing down or invalid nodes in the v1 directory. This will
28882 reduce its bulk by about 1/3, and reduce load on directory
28884 - When deciding whether a router is Fast or Guard-worthy, consider
28885 his advertised BandwidthRate and not just the BandwidthCapacity.
28886 - No longer ship INSTALL and README files -- they are useless now.
28887 - Force rpmbuild to behave and honor target_cpu.
28888 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
28889 - Start to include translated versions of the tor-doc-*.html
28890 files, along with the screenshots. Still needs more work.
28891 - Start sending back 512 and 451 errors if mapaddress fails,
28892 rather than not sending anything back at all.
28893 - When we fail to bind or listen on an incoming or outgoing
28894 socket, we should close it before failing. otherwise we just
28895 leak it. (thanks to weasel for finding.)
28896 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
28897 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
28898 - Make NoPublish (even though deprecated) work again.
28899 - Fix a minor security flaw where a versioning auth dirserver
28900 could list a recommended version many times in a row to make
28901 clients more convinced that it's recommended.
28902 - Fix crash bug if there are two unregistered servers running
28903 with the same nickname, one of them is down, and you ask for
28904 them by nickname in your EntryNodes or ExitNodes. Also, try
28905 to pick the one that's running rather than an arbitrary one.
28906 - Fix an infinite loop we could hit if we go offline for too long.
28907 - Complain when we hit WSAENOBUFS on recv() or write() too.
28908 Perhaps this will help us hunt the bug.
28909 - If you're not a versioning dirserver, don't put the string
28910 "client-versions \nserver-versions \n" in your network-status.
28911 - Lower the minimum required number of file descriptors to 1000,
28912 so we can have some overhead for Valgrind on Linux, where the
28913 default ulimit -n is 1024.
28916 - Add tor.dizum.com as the fifth authoritative directory server.
28917 - Add a new config option FetchUselessDescriptors, off by default,
28918 for when you plan to run "exitlist" on your client and you want
28919 to know about even the non-running descriptors.
28922 Changes in version 0.1.1.17-rc - 2006-03-28
28924 - Clients and servers since 0.1.1.10-alpha have been expiring
28925 connections whenever they are idle for 5 minutes and they *do*
28926 have circuits on them. Oops. With this new version, clients will
28927 discard their previous entry guard choices and avoid choosing
28928 entry guards running these flawed versions.
28929 - Fix memory leak when uncompressing concatenated zlib streams. This
28930 was causing substantial leaks over time on Tor servers.
28931 - The v1 directory was including servers as much as 48 hours old,
28932 because that's how the new routerlist->routers works. Now only
28933 include them if they're 20 hours old or less.
28936 - Resume building on irix64, netbsd 2.0, etc.
28937 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
28939 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
28940 and it is confusing some users.
28941 - Mirrors stop caching the v1 directory so often.
28942 - Make the max number of old descriptors that a cache will hold
28943 rise with the number of directory authorities, so we can scale.
28944 - Change our win32 uname() hack to be more forgiving about what
28945 win32 versions it thinks it's found.
28948 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
28950 - When the controller's *setconf commands fail, collect an error
28951 message in a string and hand it back to the controller.
28952 - Make the v2 dir's "Fast" flag based on relative capacity, just
28953 like "Stable" is based on median uptime. Name everything in the
28954 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
28955 - Log server fingerprint on startup, so new server operators don't
28956 have to go hunting around their filesystem for it.
28957 - Return a robots.txt on our dirport to discourage google indexing.
28958 - Let the controller ask for GETINFO dir/status/foo so it can ask
28959 directly rather than connecting to the dir port. Only works when
28960 dirport is set for now.
28962 o New config options rather than constants in the code:
28963 - SocksTimeout: How long do we let a socks connection wait
28964 unattached before we fail it?
28965 - CircuitBuildTimeout: Cull non-open circuits that were born
28966 at least this many seconds ago.
28967 - CircuitIdleTimeout: Cull open clean circuits that were born
28968 at least this many seconds ago.
28971 Changes in version 0.1.1.16-rc - 2006-03-18
28972 o Bugfixes on 0.1.1.15-rc:
28973 - Fix assert when the controller asks to attachstream a connect-wait
28974 or resolve-wait stream.
28975 - Now do address rewriting when the controller asks us to attach
28976 to a particular circuit too. This will let Blossom specify
28977 "moria2.exit" without having to learn what moria2's IP address is.
28978 - Make the "tor --verify-config" command-line work again, so people
28979 can automatically check if their torrc will parse.
28980 - Authoritative dirservers no longer require an open connection from
28981 a server to consider him "reachable". We need this change because
28982 when we add new auth dirservers, old servers won't know not to
28984 - Let Tor build on Sun CC again.
28985 - Fix an off-by-one buffer size in dirserv.c that magically never
28986 hit our three authorities but broke sjmurdoch's own tor network.
28987 - If we as a directory mirror don't know of any v1 directory
28988 authorities, then don't try to cache any v1 directories.
28989 - Stop warning about unknown servers in our family when they are
28990 given as hex digests.
28991 - Stop complaining as quickly to the server operator that he
28992 hasn't registered his nickname/key binding.
28993 - Various cleanups so we can add new V2 Auth Dirservers.
28994 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
28995 reflect the updated flags in our v2 dir protocol.
28996 - Resume allowing non-printable characters for exit streams (both
28997 for connecting and for resolving). Now we tolerate applications
28998 that don't follow the RFCs. But continue to block malformed names
29001 o Bugfixes on 0.1.0.x:
29002 - Fix assert bug in close_logs(): when we close and delete logs,
29003 remove them all from the global "logfiles" list.
29004 - Fix minor integer overflow in calculating when we expect to use up
29005 our bandwidth allocation before hibernating.
29006 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
29007 there are multiple SSLs installed with different versions.
29008 - When we try to be a server and Address is not explicitly set and
29009 our hostname resolves to a private IP address, try to use an
29010 interface address if it has a public address. Now Windows machines
29011 that think of themselves as localhost can work by default.
29014 - Let the controller ask for GETINFO dir/server/foo so it can ask
29015 directly rather than connecting to the dir port.
29016 - Let the controller tell us about certain router descriptors
29017 that it doesn't want Tor to use in circuits. Implement
29018 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
29019 - New config option SafeSocks to reject all application connections
29020 using unsafe socks protocols. Defaults to off.
29023 Changes in version 0.1.1.15-rc - 2006-03-11
29024 o Bugfixes and cleanups:
29025 - When we're printing strings from the network, don't try to print
29026 non-printable characters. This protects us against shell escape
29027 sequence exploits, and also against attacks to fool humans into
29028 misreading their logs.
29029 - Fix a bug where Tor would fail to establish any connections if you
29030 left it off for 24 hours and then started it: we were happy with
29031 the obsolete network statuses, but they all referred to router
29032 descriptors that were too old to fetch, so we ended up with no
29033 valid router descriptors.
29034 - Fix a seg fault in the controller's "getinfo orconn-status"
29035 command while listing status on incoming handshaking connections.
29036 Introduce a status name "NEW" for these connections.
29037 - If we get a linelist or linelist_s config option from the torrc
29038 (e.g. ExitPolicy) and it has no value, warn and skip rather than
29039 silently resetting it to its default.
29040 - Don't abandon entry guards until they've been down or gone for
29042 - Cleaner and quieter log messages.
29045 - New controller signal NEWNYM that makes new application requests
29046 use clean circuits.
29047 - Add a new circuit purpose 'controller' to let the controller ask
29048 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
29049 controller command to let you specify the purpose if you're
29050 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
29051 command to let you change a circuit's purpose after it's been
29053 - Accept "private:*" in routerdesc exit policies; not generated yet
29054 because older Tors do not understand it.
29055 - Add BSD-style contributed startup script "rc.subr" from Peter
29059 Changes in version 0.1.1.14-alpha - 2006-02-20
29060 o Bugfixes on 0.1.1.x:
29061 - Don't die if we ask for a stdout or stderr log (even implicitly)
29062 and we're set to RunAsDaemon -- just warn.
29063 - We still had a few bugs in the OR connection rotation code that
29064 caused directory servers to slowly aggregate connections to other
29065 fast Tor servers. This time for sure!
29066 - Make log entries on Win32 include the name of the function again.
29067 - We were treating a pair of exit policies if they were equal even
29068 if one said accept and the other said reject -- causing us to
29069 not always publish a new descriptor since we thought nothing
29071 - Retry pending server downloads as well as pending networkstatus
29072 downloads when we unexpectedly get a socks request.
29073 - We were ignoring the IS_FAST flag in the directory status,
29074 meaning we were willing to pick trivial-bandwidth nodes for "fast"
29076 - If the controller's SAVECONF command fails (e.g. due to file
29077 permissions), let the controller know that it failed.
29080 - If we're trying to be a Tor server and running Windows 95/98/ME
29081 as a server, explain that we'll likely crash.
29082 - When we're a server, a client asks for an old-style directory,
29083 and our write bucket is empty, don't give it to him. This way
29084 small servers can continue to serve the directory *sometimes*,
29085 without getting overloaded.
29086 - Compress exit policies even more -- look for duplicate lines
29088 - Clients now honor the "guard" flag in the router status when
29089 picking entry guards, rather than looking at is_fast or is_stable.
29090 - Retain unrecognized lines in $DATADIR/state file, so that we can
29091 be forward-compatible.
29092 - Generate 18.0.0.0/8 address policy format in descs when we can;
29093 warn when the mask is not reducible to a bit-prefix.
29094 - Let the user set ControlListenAddress in the torrc. This can be
29095 dangerous, but there are some cases (like a secured LAN) where it
29097 - Split ReachableAddresses into ReachableDirAddresses and
29098 ReachableORAddresses, so we can restrict Dir conns to port 80
29099 and OR conns to port 443.
29100 - Now we can target arch and OS in rpm builds (contributed by
29101 Phobos). Also make the resulting dist-rpm filename match the
29103 - New config options to help controllers: FetchServerDescriptors
29104 and FetchHidServDescriptors for whether to fetch server
29105 info and hidserv info or let the controller do it, and
29106 PublishServerDescriptor and PublishHidServDescriptors.
29107 - Also let the controller set the __AllDirActionsPrivate config
29108 option if you want all directory fetches/publishes to happen via
29109 Tor (it assumes your controller bootstraps your circuits).
29112 Changes in version 0.1.0.17 - 2006-02-17
29113 o Crash bugfixes on 0.1.0.x:
29114 - When servers with a non-zero DirPort came out of hibernation,
29115 sometimes they would trigger an assert.
29117 o Other important bugfixes:
29118 - On platforms that don't have getrlimit (like Windows), we were
29119 artificially constraining ourselves to a max of 1024
29120 connections. Now just assume that we can handle as many as 15000
29121 connections. Hopefully this won't cause other problems.
29123 o Backported features:
29124 - When we're a server, a client asks for an old-style directory,
29125 and our write bucket is empty, don't give it to him. This way
29126 small servers can continue to serve the directory *sometimes*,
29127 without getting overloaded.
29128 - Whenever you get a 503 in response to a directory fetch, try
29129 once more. This will become important once servers start sending
29130 503's whenever they feel busy.
29131 - Fetch a new directory every 120 minutes, not every 40 minutes.
29132 Now that we have hundreds of thousands of users running the old
29133 directory algorithm, it's starting to hurt a lot.
29134 - Bump up the period for forcing a hidden service descriptor upload
29135 from 20 minutes to 1 hour.
29138 Changes in version 0.1.1.13-alpha - 2006-02-09
29139 o Crashes in 0.1.1.x:
29140 - When you tried to setconf ORPort via the controller, Tor would
29141 crash. So people using TorCP to become a server were sad.
29142 - Solve (I hope) the stack-smashing bug that we were seeing on fast
29143 servers. The problem appears to be something do with OpenSSL's
29144 random number generation, or how we call it, or something. Let me
29145 know if the crashes continue.
29146 - Turn crypto hardware acceleration off by default, until we find
29147 somebody smart who can test it for us. (It appears to produce
29148 seg faults in at least some cases.)
29149 - Fix a rare assert error when we've tried all intro points for
29150 a hidden service and we try fetching the service descriptor again:
29151 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
29154 - Fix a major load balance bug: we were round-robining in 16 KB
29155 chunks, and servers with bandwidthrate of 20 KB, while downloading
29156 a 600 KB directory, would starve their other connections. Now we
29157 try to be a bit more fair.
29158 - Dir authorities and mirrors were never expiring the newest
29159 descriptor for each server, causing memory and directory bloat.
29160 - Fix memory-bloating and connection-bloating bug on servers: We
29161 were never closing any connection that had ever had a circuit on
29162 it, because we were checking conn->n_circuits == 0, yet we had a
29163 bug that let it go negative.
29164 - Make Tor work using squid as your http proxy again -- squid
29165 returns an error if you ask for a URL that's too long, and it uses
29166 a really generic error message. Plus, many people are behind a
29167 transparent squid so they don't even realize it.
29168 - On platforms that don't have getrlimit (like Windows), we were
29169 artificially constraining ourselves to a max of 1024
29170 connections. Now just assume that we can handle as many as 15000
29171 connections. Hopefully this won't cause other problems.
29172 - Add a new config option ExitPolicyRejectPrivate which defaults to
29173 1. This means all exit policies will begin with rejecting private
29174 addresses, unless the server operator explicitly turns it off.
29177 - Clients no longer download descriptors for non-running
29179 - Before we add new directory authorities, we should make it
29180 clear that only v1 authorities should receive/publish hidden
29181 service descriptors.
29184 - As soon as we've fetched some more directory info, immediately
29185 try to download more server descriptors. This way we don't have
29186 a 10 second pause during initial bootstrapping.
29187 - Remove even more loud log messages that the server operator can't
29189 - When we're running an obsolete or un-recommended version, make
29190 the log message more clear about what the problem is and what
29191 versions *are* still recommended.
29192 - Provide a more useful warn message when our onion queue gets full:
29193 the CPU is too slow or the exit policy is too liberal.
29194 - Don't warn when we receive a 503 from a dirserver/cache -- this
29195 will pave the way for them being able to refuse if they're busy.
29196 - When we fail to bind a listener, try to provide a more useful
29197 log message: e.g., "Is Tor already running?"
29198 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
29199 Goldberg can prove things about our handshake protocol more
29201 - MaxConn has been obsolete for a while now. Document the ConnLimit
29202 config option, which is a *minimum* number of file descriptors
29203 that must be available else Tor refuses to start.
29204 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
29205 if you log to syslog and want something other than LOG_DAEMON.
29206 - Make dirservers generate a separate "guard" flag to mean,
29207 "would make a good entry guard". Make clients parse it and vote
29208 on it. Not used by clients yet.
29209 - Implement --with-libevent-dir option to ./configure. Also, improve
29210 search techniques to find libevent, and use those for openssl too.
29211 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
29212 - Only start testing reachability once we've established a
29213 circuit. This will make startup on dirservers less noisy.
29214 - Don't try to upload hidden service descriptors until we have
29215 established a circuit.
29216 - Fix the controller's "attachstream 0" command to treat conn like
29217 it just connected, doing address remapping, handling .exit and
29218 .onion idioms, and so on. Now we're more uniform in making sure
29219 that the controller hears about new and closing connections.
29222 Changes in version 0.1.1.12-alpha - 2006-01-11
29223 o Bugfixes on 0.1.1.x:
29224 - The fix to close duplicate server connections was closing all
29225 Tor client connections if they didn't establish a circuit
29226 quickly enough. Oops.
29227 - Fix minor memory issue (double-free) that happened on exit.
29229 o Bugfixes on 0.1.0.x:
29230 - Tor didn't warn when it failed to open a log file.
29233 Changes in version 0.1.1.11-alpha - 2006-01-10
29234 o Crashes in 0.1.1.x:
29235 - Include all the assert/crash fixes from 0.1.0.16.
29236 - If you start Tor and then quit very quickly, there were some
29237 races that tried to free things that weren't allocated yet.
29238 - Fix a rare memory stomp if you're running hidden services.
29239 - Fix segfault when specifying DirServer in config without nickname.
29240 - Fix a seg fault when you finish connecting to a server but at
29241 that moment you dump his server descriptor.
29242 - Extendcircuit and Attachstream controller commands would
29243 assert/crash if you don't give them enough arguments.
29244 - Fix an assert error when we're out of space in the connection_list
29245 and we try to post a hidden service descriptor (reported by weasel).
29246 - If you specify a relative torrc path and you set RunAsDaemon in
29247 your torrc, then it chdir()'s to the new directory. If you HUP,
29248 it tries to load the new torrc location, fails, and exits.
29249 The fix: no longer allow a relative path to torrc using -f.
29252 - Implement "entry guards": automatically choose a handful of entry
29253 nodes and stick with them for all circuits. Only pick new guards
29254 when the ones you have are unsuitable, and if the old guards
29255 become suitable again, switch back. This will increase security
29256 dramatically against certain end-point attacks. The EntryNodes
29257 config option now provides some hints about which entry guards you
29258 want to use most; and StrictEntryNodes means to only use those.
29259 - New directory logic: download by descriptor digest, not by
29260 fingerprint. Caches try to download all listed digests from
29261 authorities; clients try to download "best" digests from caches.
29262 This avoids partitioning and isolating attacks better.
29263 - Make the "stable" router flag in network-status be the median of
29264 the uptimes of running valid servers, and make clients pay
29265 attention to the network-status flags. Thus the cutoff adapts
29266 to the stability of the network as a whole, making IRC, IM, etc
29267 connections more reliable.
29270 - Tor servers with dynamic IP addresses were needing to wait 18
29271 hours before they could start doing reachability testing using
29272 the new IP address and ports. This is because they were using
29273 the internal descriptor to learn what to test, yet they were only
29274 rebuilding the descriptor once they decided they were reachable.
29275 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
29276 to download certain server descriptors, throw them away, and then
29277 fetch them again after 30 minutes. Now mirrors throw away these
29278 server descriptors so clients can't get them.
29279 - We were leaving duplicate connections to other ORs open for a week,
29280 rather than closing them once we detect a duplicate. This only
29281 really affected authdirservers, but it affected them a lot.
29282 - Spread the authdirservers' reachability testing over the entire
29283 testing interval, so we don't try to do 500 TLS's at once every
29287 - If the network is down, and we try to connect to a conn because
29288 we have a circuit in mind, and we timeout (30 seconds) because the
29289 network never answers, we were expiring the circuit, but we weren't
29290 obsoleting the connection or telling the entry_guards functions.
29291 - Some Tor servers process billions of cells per day. These statistics
29292 need to be uint64_t's.
29293 - Check for integer overflows in more places, when adding elements
29294 to smartlists. This could possibly prevent a buffer overflow
29295 on malicious huge inputs. I don't see any, but I haven't looked
29297 - ReachableAddresses kept growing new "reject *:*" lines on every
29299 - When you "setconf log" via the controller, it should remove all
29300 logs. We were automatically adding back in a "log notice stdout".
29301 - Newly bootstrapped Tor networks couldn't establish hidden service
29302 circuits until they had nodes with high uptime. Be more tolerant.
29303 - We were marking servers down when they could not answer every piece
29304 of the directory request we sent them. This was far too harsh.
29305 - Fix the torify (tsocks) config file to not use Tor for localhost
29307 - Directory authorities now go to the proper authority when asking for
29308 a networkstatus, even when they want a compressed one.
29309 - Fix a harmless bug that was causing Tor servers to log
29310 "Got an end because of misc error, but we're not an AP. Closing."
29311 - Authorities were treating their own descriptor changes as cosmetic,
29312 meaning the descriptor available in the network-status and the
29313 descriptor that clients downloaded were different.
29314 - The OS X installer was adding a symlink for tor_resolve but
29315 the binary was called tor-resolve (reported by Thomas Hardly).
29316 - Workaround a problem with some http proxies where they refuse GET
29317 requests that specify "Content-Length: 0" (reported by Adrian).
29318 - Fix wrong log message when you add a "HiddenServiceNodes" config
29319 line without any HiddenServiceDir line (reported by Chris Thomas).
29322 - Write the TorVersion into the state file so we have a prayer of
29323 keeping forward and backward compatibility.
29324 - Revive the FascistFirewall config option rather than eliminating it:
29325 now it's a synonym for ReachableAddresses *:80,*:443.
29326 - Clients choose directory servers from the network status lists,
29327 not from their internal list of router descriptors. Now they can
29328 go to caches directly rather than needing to go to authorities
29330 - Directory authorities ignore router descriptors that have only
29331 cosmetic differences: do this for 0.1.0.x servers now too.
29332 - Add a new flag to network-status indicating whether the server
29333 can answer v2 directory requests too.
29334 - Authdirs now stop whining so loudly about bad descriptors that
29335 they fetch from other dirservers. So when there's a log complaint,
29336 it's for sure from a freshly uploaded descriptor.
29337 - Reduce memory requirements in our structs by changing the order
29339 - There used to be two ways to specify your listening ports in a
29340 server descriptor: on the "router" line and with a separate "ports"
29341 line. Remove support for the "ports" line.
29342 - New config option "AuthDirRejectUnlisted" for auth dirservers as
29343 a panic button: if we get flooded with unusable servers we can
29344 revert to only listing servers in the approved-routers file.
29345 - Auth dir servers can now mark a fingerprint as "!reject" or
29346 "!invalid" in the approved-routers file (as its nickname), to
29347 refuse descriptors outright or include them but marked as invalid.
29348 - Servers store bandwidth history across restarts/crashes.
29349 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
29350 get a better idea of why their circuits failed. Not used yet.
29351 - Directory mirrors now cache up to 16 unrecognized network-status
29352 docs. Now we can add new authdirservers and they'll be cached too.
29353 - When picking a random directory, prefer non-authorities if any
29355 - New controller option "getinfo desc/all-recent" to fetch the
29356 latest server descriptor for every router that Tor knows about.
29359 Changes in version 0.1.0.16 - 2006-01-02
29360 o Crash bugfixes on 0.1.0.x:
29361 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
29362 corrupting the heap, losing FDs, or crashing when we need to resize
29363 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
29364 - It turns out sparc64 platforms crash on unaligned memory access
29365 too -- so detect and avoid this.
29366 - Handle truncated compressed data correctly (by detecting it and
29368 - Fix possible-but-unlikely free(NULL) in control.c.
29369 - When we were closing connections, there was a rare case that
29370 stomped on memory, triggering seg faults and asserts.
29371 - Avoid potential infinite recursion when building a descriptor. (We
29372 don't know that it ever happened, but better to fix it anyway.)
29373 - We were neglecting to unlink marked circuits from soon-to-close OR
29374 connections, which caused some rare scribbling on freed memory.
29375 - Fix a memory stomping race bug when closing the joining point of two
29376 rendezvous circuits.
29377 - Fix an assert in time parsing found by Steven Murdoch.
29379 o Other bugfixes on 0.1.0.x:
29380 - When we're doing reachability testing, provide more useful log
29381 messages so the operator knows what to expect.
29382 - Do not check whether DirPort is reachable when we are suppressing
29383 advertising it because of hibernation.
29384 - When building with -static or on Solaris, we sometimes needed -ldl.
29385 - When we're deciding whether a stream has enough circuits around
29386 that can handle it, count the freshly dirty ones and not the ones
29387 that are so dirty they won't be able to handle it.
29388 - When we're expiring old circuits, we had a logic error that caused
29389 us to close new rendezvous circuits rather than old ones.
29390 - Give a more helpful log message when you try to change ORPort via
29391 the controller: you should upgrade Tor if you want that to work.
29392 - We were failing to parse Tor versions that start with "Tor ".
29393 - Tolerate faulty streams better: when a stream fails for reason
29394 exitpolicy, stop assuming that the router is lying about his exit
29395 policy. When a stream fails for reason misc, allow it to retry just
29396 as if it was resolvefailed. When a stream has failed three times,
29397 reset its failure count so we can try again and get all three tries.
29400 Changes in version 0.1.1.10-alpha - 2005-12-11
29401 o Correctness bugfixes on 0.1.0.x:
29402 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
29403 corrupting the heap, losing FDs, or crashing when we need to resize
29404 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
29405 - Stop doing the complex voodoo overkill checking for insecure
29406 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
29407 - When we were closing connections, there was a rare case that
29408 stomped on memory, triggering seg faults and asserts.
29409 - We were neglecting to unlink marked circuits from soon-to-close OR
29410 connections, which caused some rare scribbling on freed memory.
29411 - When we're deciding whether a stream has enough circuits around
29412 that can handle it, count the freshly dirty ones and not the ones
29413 that are so dirty they won't be able to handle it.
29414 - Recover better from TCP connections to Tor servers that are
29415 broken but don't tell you (it happens!); and rotate TLS
29416 connections once a week.
29417 - When we're expiring old circuits, we had a logic error that caused
29418 us to close new rendezvous circuits rather than old ones.
29419 - Fix a scary-looking but apparently harmless bug where circuits
29420 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
29421 servers, and never switch to state CIRCUIT_STATE_OPEN.
29422 - When building with -static or on Solaris, we sometimes needed to
29424 - Give a useful message when people run Tor as the wrong user,
29425 rather than telling them to start chowning random directories.
29426 - We were failing to inform the controller about new .onion streams.
29428 o Security bugfixes on 0.1.0.x:
29429 - Refuse server descriptors if the fingerprint line doesn't match
29430 the included identity key. Tor doesn't care, but other apps (and
29431 humans) might actually be trusting the fingerprint line.
29432 - We used to kill the circuit when we receive a relay command we
29433 don't recognize. Now we just drop it.
29434 - Start obeying our firewall options more rigorously:
29435 . If we can't get to a dirserver directly, try going via Tor.
29436 . Don't ever try to connect (as a client) to a place our
29437 firewall options forbid.
29438 . If we specify a proxy and also firewall options, obey the
29439 firewall options even when we're using the proxy: some proxies
29440 can only proxy to certain destinations.
29441 - Fix a bug found by Lasse Overlier: when we were making internal
29442 circuits (intended to be cannibalized later for rendezvous and
29443 introduction circuits), we were picking them so that they had
29444 useful exit nodes. There was no need for this, and it actually
29445 aids some statistical attacks.
29446 - Start treating internal circuits and exit circuits separately.
29447 It's important to keep them separate because internal circuits
29448 have their last hops picked like middle hops, rather than like
29449 exit hops. So exiting on them will break the user's expectations.
29451 o Bugfixes on 0.1.1.x:
29452 - Take out the mis-feature where we tried to detect IP address
29453 flapping for people with DynDNS, and chose not to upload a new
29454 server descriptor sometimes.
29455 - Try to be compatible with OpenSSL 0.9.6 again.
29456 - Log fix: when the controller is logging about .onion addresses,
29457 sometimes it didn't include the ".onion" part of the address.
29458 - Don't try to modify options->DirServers internally -- if the
29459 user didn't specify any, just add the default ones directly to
29460 the trusted dirserver list. This fixes a bug where people running
29461 controllers would use SETCONF on some totally unrelated config
29462 option, and Tor would start yelling at them about changing their
29464 - Let the controller's redirectstream command specify a port, in
29465 case the controller wants to change that too.
29466 - When we requested a pile of server descriptors, we sometimes
29467 accidentally launched a duplicate request for the first one.
29468 - Bugfix for trackhostexits: write down the fingerprint of the
29469 chosen exit, not its nickname, because the chosen exit might not
29471 - When parsing foo.exit, if foo is unknown, and we are leaving
29472 circuits unattached, set the chosen_exit field and leave the
29473 address empty. This matters because controllers got confused
29475 - Directory authorities no longer try to download server
29476 descriptors that they know they will reject.
29478 o Features and updates:
29479 - Replace balanced trees with hash tables: this should make stuff
29480 significantly faster.
29481 - Resume using the AES counter-mode implementation that we ship,
29482 rather than OpenSSL's. Ours is significantly faster.
29483 - Many other CPU and memory improvements.
29484 - Add a new config option FastFirstHopPK (on by default) so clients
29485 do a trivial crypto handshake for their first hop, since TLS has
29486 already taken care of confidentiality and authentication.
29487 - Add a new config option TestSocks so people can see if their
29488 applications are using socks4, socks4a, socks5-with-ip, or
29489 socks5-with-hostname. This way they don't have to keep mucking
29490 with tcpdump and wondering if something got cached somewhere.
29491 - Warn when listening on a public address for socks. I suspect a
29492 lot of people are setting themselves up as open socks proxies,
29493 and they have no idea that jerks on the Internet are using them,
29494 since they simply proxy the traffic into the Tor network.
29495 - Add "private:*" as an alias in configuration for policies. Now
29496 you can simplify your exit policy rather than needing to list
29497 every single internal or nonroutable network space.
29498 - Add a new controller event type that allows controllers to get
29499 all server descriptors that were uploaded to a router in its role
29500 as authoritative dirserver.
29501 - Start shipping socks-extensions.txt, tor-doc-unix.html,
29502 tor-doc-server.html, and stylesheet.css in the tarball.
29503 - Stop shipping tor-doc.html in the tarball.
29506 Changes in version 0.1.1.9-alpha - 2005-11-15
29507 o Usability improvements:
29508 - Start calling it FooListenAddress rather than FooBindAddress,
29509 since few of our users know what it means to bind an address
29511 - Reduce clutter in server logs. We're going to try to make
29512 them actually usable now. New config option ProtocolWarnings that
29513 lets you hear about how _other Tors_ are breaking the protocol. Off
29515 - Divide log messages into logging domains. Once we put some sort
29516 of interface on this, it will let people looking at more verbose
29517 log levels specify the topics they want to hear more about.
29518 - Make directory servers return better http 404 error messages
29519 instead of a generic "Servers unavailable".
29520 - Check for even more Windows version flags when writing the platform
29521 string in server descriptors, and note any we don't recognize.
29522 - Clean up more of the OpenSSL memory when exiting, so we can detect
29523 memory leaks better.
29524 - Make directory authorities be non-versioning, non-naming by
29525 default. Now we can add new directory servers without requiring
29526 their operators to pay close attention.
29527 - When logging via syslog, include the pid whenever we provide
29528 a log entry. Suggested by Todd Fries.
29530 o Performance improvements:
29531 - Directory servers now silently throw away new descriptors that
29532 haven't changed much if the timestamps are similar. We do this to
29533 tolerate older Tor servers that upload a new descriptor every 15
29534 minutes. (It seemed like a good idea at the time.)
29535 - Inline bottleneck smartlist functions; use fast versions by default.
29536 - Add a "Map from digest to void*" abstraction digestmap_t so we
29537 can do less hex encoding/decoding. Use it in router_get_by_digest()
29538 to resolve a performance bottleneck.
29539 - Allow tor_gzip_uncompress to extract as much as possible from
29540 truncated compressed data. Try to extract as many
29541 descriptors as possible from truncated http responses (when
29542 DIR_PURPOSE_FETCH_ROUTERDESC).
29543 - Make circ->onionskin a pointer, not a static array. moria2 was using
29544 125000 circuit_t's after it had been up for a few weeks, which
29545 translates to 20+ megs of wasted space.
29546 - The private half of our EDH handshake keys are now chosen out
29547 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
29549 o Security improvements:
29550 - Start making directory caches retain old routerinfos, so soon
29551 clients can start asking by digest of descriptor rather than by
29552 fingerprint of server.
29553 - Add half our entropy from RAND_poll in OpenSSL. This knows how
29554 to use egd (if present), openbsd weirdness (if present), vms/os2
29555 weirdness (if we ever port there), and more in the future.
29557 o Bugfixes on 0.1.0.x:
29558 - Do round-robin writes of at most 16 kB per write. This might be
29559 more fair on loaded Tor servers, and it might resolve our Windows
29560 crash bug. It might also slow things down.
29561 - Our TLS handshakes were generating a single public/private
29562 keypair for the TLS context, rather than making a new one for
29563 each new connections. Oops. (But we were still rotating them
29564 periodically, so it's not so bad.)
29565 - When we were cannibalizing a circuit with a particular exit
29566 node in mind, we weren't checking to see if that exit node was
29567 already present earlier in the circuit. Oops.
29568 - When a Tor server's IP changes (e.g. from a dyndns address),
29569 upload a new descriptor so clients will learn too.
29570 - Really busy servers were keeping enough circuits open on stable
29571 connections that they were wrapping around the circuit_id
29572 space. (It's only two bytes.) This exposed a bug where we would
29573 feel free to reuse a circuit_id even if it still exists but has
29574 been marked for close. Try to fix this bug. Some bug remains.
29575 - If we would close a stream early (e.g. it asks for a .exit that
29576 we know would refuse it) but the LeaveStreamsUnattached config
29577 option is set by the controller, then don't close it.
29579 o Bugfixes on 0.1.1.8-alpha:
29580 - Fix a big pile of memory leaks, some of them serious.
29581 - Do not try to download a routerdesc if we would immediately reject
29583 - Resume inserting a newline between all router descriptors when
29584 generating (old style) signed directories, since our spec says
29586 - When providing content-type application/octet-stream for
29587 server descriptors using .z, we were leaving out the
29588 content-encoding header. Oops. (Everything tolerated this just
29589 fine, but that doesn't mean we need to be part of the problem.)
29590 - Fix a potential seg fault in getconf and getinfo using version 1
29591 of the controller protocol.
29592 - Avoid crash: do not check whether DirPort is reachable when we
29593 are suppressing it because of hibernation.
29594 - Make --hash-password not crash on exit.
29597 Changes in version 0.1.1.8-alpha - 2005-10-07
29598 o New features (major):
29599 - Clients don't download or use the directory anymore. Now they
29600 download and use network-statuses from the trusted dirservers,
29601 and fetch individual server descriptors as needed from mirrors.
29602 See dir-spec.txt for all the gory details.
29603 - Be more conservative about whether to advertise our DirPort.
29604 The main change is to not advertise if we're running at capacity
29605 and either a) we could hibernate or b) our capacity is low and
29606 we're using a default DirPort.
29607 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
29609 o New features (minor):
29610 - Try to be smart about when to retry network-status and
29611 server-descriptor fetches. Still needs some tuning.
29612 - Stop parsing, storing, or using running-routers output (but
29613 mirrors still cache and serve it).
29614 - Consider a threshold of versioning dirservers (dirservers who have
29615 an opinion about which Tor versions are still recommended) before
29616 deciding whether to warn the user that he's obsolete.
29617 - Dirservers can now reject/invalidate by key and IP, with the
29618 config options "AuthDirInvalid" and "AuthDirReject". This is
29619 useful since currently we automatically list servers as running
29620 and usable even if we know they're jerks.
29621 - Provide dire warnings to any users who set DirServer; move it out
29622 of torrc.sample and into torrc.complete.
29623 - Add MyFamily to torrc.sample in the server section.
29624 - Add nicknames to the DirServer line, so we can refer to them
29625 without requiring all our users to memorize their IP addresses.
29626 - When we get an EOF or a timeout on a directory connection, note
29627 how many bytes of serverdesc we are dropping. This will help
29628 us determine whether it is smart to parse incomplete serverdesc
29630 - Add a new function to "change pseudonyms" -- that is, to stop
29631 using any currently-dirty circuits for new streams, so we don't
29632 link new actions to old actions. Currently it's only called on
29633 HUP (or SIGNAL RELOAD).
29634 - On sighup, if UseHelperNodes changed to 1, use new circuits.
29635 - Start using RAND_bytes rather than RAND_pseudo_bytes from
29636 OpenSSL. Also, reseed our entropy every hour, not just at
29637 startup. And entropy in 512-bit chunks, not 160-bit chunks.
29639 o Fixes on 0.1.1.7-alpha:
29640 - Nobody ever implemented EVENT_ADDRMAP for control protocol
29641 version 0, so don't let version 0 controllers ask for it.
29642 - If you requested something with too many newlines via the
29643 v1 controller protocol, you could crash tor.
29644 - Fix a number of memory leaks, including some pretty serious ones.
29645 - Re-enable DirPort testing again, so Tor servers will be willing
29646 to advertise their DirPort if it's reachable.
29647 - On TLS handshake, only check the other router's nickname against
29648 its expected nickname if is_named is set.
29650 o Fixes forward-ported from 0.1.0.15:
29651 - Don't crash when we don't have any spare file descriptors and we
29652 try to spawn a dns or cpu worker.
29653 - Make the numbers in read-history and write-history into uint64s,
29654 so they don't overflow and publish negatives in the descriptor.
29656 o Fixes on 0.1.0.x:
29657 - For the OS X package's modified privoxy config file, comment
29658 out the "logfile" line so we don't log everything passed
29660 - We were whining about using socks4 or socks5-with-local-lookup
29661 even when it's an IP in the "virtual" range we designed exactly
29663 - We were leaking some memory every time the client changes IPs.
29664 - Never call free() on tor_malloc()d memory. This will help us
29665 use dmalloc to detect memory leaks.
29666 - Check for named servers when looking them up by nickname;
29667 warn when we'recalling a non-named server by its nickname;
29668 don't warn twice about the same name.
29669 - Try to list MyFamily elements by key, not by nickname, and warn
29670 if we've not heard of the server.
29671 - Make windows platform detection (uname equivalent) smarter.
29672 - It turns out sparc64 doesn't like unaligned access either.
29675 Changes in version 0.1.0.15 - 2005-09-23
29676 o Bugfixes on 0.1.0.x:
29677 - Reject ports 465 and 587 (spam targets) in default exit policy.
29678 - Don't crash when we don't have any spare file descriptors and we
29679 try to spawn a dns or cpu worker.
29680 - Get rid of IgnoreVersion undocumented config option, and make us
29681 only warn, never exit, when we're running an obsolete version.
29682 - Don't try to print a null string when your server finds itself to
29683 be unreachable and the Address config option is empty.
29684 - Make the numbers in read-history and write-history into uint64s,
29685 so they don't overflow and publish negatives in the descriptor.
29686 - Fix a minor memory leak in smartlist_string_remove().
29687 - We were only allowing ourselves to upload a server descriptor at
29688 most every 20 minutes, even if it changed earlier than that.
29689 - Clean up log entries that pointed to old URLs.
29692 Changes in version 0.1.1.7-alpha - 2005-09-14
29693 o Fixes on 0.1.1.6-alpha:
29694 - Exit servers were crashing when people asked them to make a
29695 connection to an address not in their exit policy.
29696 - Looking up a non-existent stream for a v1 control connection would
29698 - Fix a seg fault if we ask a dirserver for a descriptor by
29699 fingerprint but he doesn't know about him.
29700 - SETCONF was appending items to linelists, not clearing them.
29701 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
29702 out and refuse the setconf if it would fail.
29703 - Downgrade the dirserver log messages when whining about
29707 - Add Peter Palfrader's check-tor script to tor/contrib/
29708 It lets you easily check whether a given server (referenced by
29709 nickname) is reachable by you.
29710 - Numerous changes to move towards client-side v2 directories. Not
29713 o Fixes on 0.1.0.x:
29714 - If the user gave tor an odd number of command-line arguments,
29715 we were silently ignoring the last one. Now we complain and fail.
29716 [This wins the oldest-bug prize -- this bug has been present since
29717 November 2002, as released in Tor 0.0.0.]
29718 - Do not use unaligned memory access on alpha, mips, or mipsel.
29719 It *works*, but is very slow, so we treat them as if it doesn't.
29720 - Retry directory requests if we fail to get an answer we like
29721 from a given dirserver (we were retrying before, but only if
29722 we fail to connect).
29723 - When writing the RecommendedVersions line, sort them first.
29724 - When the client asked for a rendezvous port that the hidden
29725 service didn't want to provide, we were sending an IP address
29726 back along with the end cell. Fortunately, it was zero. But stop
29728 - Correct "your server is reachable" log entries to indicate that
29729 it was self-testing that told us so.
29732 Changes in version 0.1.1.6-alpha - 2005-09-09
29733 o Fixes on 0.1.1.5-alpha:
29734 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
29735 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
29736 - Fix bug with tor_memmem finding a match at the end of the string.
29737 - Make unit tests run without segfaulting.
29738 - Resolve some solaris x86 compile warnings.
29739 - Handle duplicate lines in approved-routers files without warning.
29740 - Fix bug where as soon as a server refused any requests due to his
29741 exit policy (e.g. when we ask for localhost and he tells us that's
29742 127.0.0.1 and he won't do it), we decided he wasn't obeying his
29743 exit policy using him for any exits.
29744 - Only do openssl hardware accelerator stuff if openssl version is
29747 o New controller features/fixes:
29748 - Add a "RESETCONF" command so you can set config options like
29749 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
29750 a config option in the torrc with no value, then it clears it
29751 entirely (rather than setting it to its default).
29752 - Add a "GETINFO config-file" to tell us where torrc is.
29753 - Avoid sending blank lines when GETINFO replies should be empty.
29754 - Add a QUIT command for the controller (for using it manually).
29755 - Fix a bug in SAVECONF that was adding default dirservers and
29756 other redundant entries to the torrc file.
29758 o Start on the new directory design:
29759 - Generate, publish, cache, serve new network-status format.
29760 - Publish individual descriptors (by fingerprint, by "all", and by
29762 - Publish client and server recommended versions separately.
29763 - Allow tor_gzip_uncompress() to handle multiple concatenated
29764 compressed strings. Serve compressed groups of router
29765 descriptors. The compression logic here could be more
29767 - Distinguish v1 authorities (all currently trusted directories)
29768 from v2 authorities (all trusted directories).
29769 - Change DirServers config line to note which dirs are v1 authorities.
29770 - Add configuration option "V1AuthoritativeDirectory 1" which
29771 moria1, moria2, and tor26 should set.
29772 - Remove option when getting directory cache to see whether they
29773 support running-routers; they all do now. Replace it with one
29774 to see whether caches support v2 stuff.
29777 - Dirservers now do their own external reachability testing of each
29778 Tor server, and only list them as running if they've been found to
29779 be reachable. We also send back warnings to the server's logs if
29780 it uploads a descriptor that we already believe is unreachable.
29781 - Implement exit enclaves: if we know an IP address for the
29782 destination, and there's a running Tor server at that address
29783 which allows exit to the destination, then extend the circuit to
29784 that exit first. This provides end-to-end encryption and end-to-end
29785 authentication. Also, if the user wants a .exit address or enclave,
29786 use 4 hops rather than 3, and cannibalize a general circ for it
29788 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
29789 controller. Also, rotate dns and cpu workers if the controller
29790 changes options that will affect them; and initialize the dns
29791 worker cache tree whether or not we start out as a server.
29792 - Only upload a new server descriptor when options change, 18
29793 hours have passed, uptime is reset, or bandwidth changes a lot.
29794 - Check [X-]Forwarded-For headers in HTTP requests when generating
29795 log messages. This lets people run dirservers (and caches) behind
29796 Apache but still know which IP addresses are causing warnings.
29798 o Config option changes:
29799 - Replace (Fascist)Firewall* config options with a new
29800 ReachableAddresses option that understands address policies.
29801 For example, "ReachableAddresses *:80,*:443"
29802 - Get rid of IgnoreVersion undocumented config option, and make us
29803 only warn, never exit, when we're running an obsolete version.
29804 - Make MonthlyAccountingStart config option truly obsolete now.
29806 o Fixes on 0.1.0.x:
29807 - Reject ports 465 and 587 in the default exit policy, since
29808 people have started using them for spam too.
29809 - It turns out we couldn't bootstrap a network since we added
29810 reachability detection in 0.1.0.1-rc. Good thing the Tor network
29811 has never gone down. Add an AssumeReachable config option to let
29812 servers and dirservers bootstrap. When we're trying to build a
29813 high-uptime or high-bandwidth circuit but there aren't enough
29814 suitable servers, try being less picky rather than simply failing.
29815 - Our logic to decide if the OR we connected to was the right guy
29816 was brittle and maybe open to a mitm for unverified routers.
29817 - We weren't cannibalizing circuits correctly for
29818 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
29819 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
29820 build those from scratch. This should make hidden services faster.
29821 - Predict required circuits better, with an eye toward making hidden
29822 services faster on the service end.
29823 - Retry streams if the exit node sends back a 'misc' failure. This
29824 should result in fewer random failures. Also, after failing
29825 from resolve failed or misc, reset the num failures, so we give
29826 it a fair shake next time we try.
29827 - Clean up the rendezvous warn log msgs, and downgrade some to info.
29828 - Reduce severity on logs about dns worker spawning and culling.
29829 - When we're shutting down and we do something like try to post a
29830 server descriptor or rendezvous descriptor, don't complain that
29831 we seem to be unreachable. Of course we are, we're shutting down.
29832 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
29833 We don't use them yet, but maybe one day our DNS resolver will be
29834 able to discover them.
29835 - Make ContactInfo mandatory for authoritative directory servers.
29836 - Require server descriptors to list IPv4 addresses -- hostnames
29837 are no longer allowed. This also fixes some potential security
29838 problems with people providing hostnames as their address and then
29839 preferentially resolving them to partition users.
29840 - Change log line for unreachability to explicitly suggest /etc/hosts
29841 as the culprit. Also make it clearer what IP address and ports we're
29842 testing for reachability.
29843 - Put quotes around user-supplied strings when logging so users are
29844 more likely to realize if they add bad characters (like quotes)
29846 - Let auth dir servers start without specifying an Address config
29848 - Make unit tests (and other invocations that aren't the real Tor)
29849 run without launching listeners, creating subdirectories, and so on.
29852 Changes in version 0.1.1.5-alpha - 2005-08-08
29853 o Bugfixes included in 0.1.0.14.
29855 o Bugfixes on 0.1.0.x:
29856 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
29857 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
29858 it would silently using ignore the 6668.
29861 Changes in version 0.1.0.14 - 2005-08-08
29862 o Bugfixes on 0.1.0.x:
29863 - Fix the other half of the bug with crypto handshakes
29865 - Fix an assert trigger if you send a 'signal term' via the
29866 controller when it's listening for 'event info' messages.
29869 Changes in version 0.1.1.4-alpha - 2005-08-04
29870 o Bugfixes included in 0.1.0.13.
29873 - Improve tor_gettimeofday() granularity on windows.
29874 - Make clients regenerate their keys when their IP address changes.
29875 - Implement some more GETINFO goodness: expose helper nodes, config
29876 options, getinfo keys.
29879 Changes in version 0.1.0.13 - 2005-08-04
29880 o Bugfixes on 0.1.0.x:
29881 - Fix a critical bug in the security of our crypto handshakes.
29882 - Fix a size_t underflow in smartlist_join_strings2() that made
29883 it do bad things when you hand it an empty smartlist.
29884 - Fix Windows installer to ship Tor license (thanks to Aphex for
29885 pointing out this oversight) and put a link to the doc directory
29887 - Explicitly set no-unaligned-access for sparc: it turns out the
29888 new gcc's let you compile broken code, but that doesn't make it
29892 Changes in version 0.1.1.3-alpha - 2005-07-23
29893 o Bugfixes on 0.1.1.2-alpha:
29894 - Fix a bug in handling the controller's "post descriptor"
29896 - Fix several bugs in handling the controller's "extend circuit"
29898 - Fix a bug in handling the controller's "stream status" event.
29899 - Fix an assert failure if we have a controller listening for
29900 circuit events and we go offline.
29901 - Re-allow hidden service descriptors to publish 0 intro points.
29902 - Fix a crash when generating your hidden service descriptor if
29903 you don't have enough intro points already.
29905 o New features on 0.1.1.2-alpha:
29906 - New controller function "getinfo accounting", to ask how
29907 many bytes we've used in this time period.
29908 - Experimental support for helper nodes: a lot of the risk from
29909 a small static adversary comes because users pick new random
29910 nodes every time they rebuild a circuit. Now users will try to
29911 stick to the same small set of entry nodes if they can. Not
29912 enabled by default yet.
29914 o Bugfixes on 0.1.0.12:
29915 - If you're an auth dir server, always publish your dirport,
29916 even if you haven't yet found yourself to be reachable.
29917 - Fix a size_t underflow in smartlist_join_strings2() that made
29918 it do bad things when you hand it an empty smartlist.
29921 Changes in version 0.1.0.12 - 2005-07-18
29922 o New directory servers:
29923 - tor26 has changed IP address.
29925 o Bugfixes on 0.1.0.x:
29926 - Fix a possible double-free in tor_gzip_uncompress().
29927 - When --disable-threads is set, do not search for or link against
29928 pthreads libraries.
29929 - Don't trigger an assert if an authoritative directory server
29930 claims its dirport is 0.
29931 - Fix bug with removing Tor as an NT service: some people were
29932 getting "The service did not return an error." Thanks to Matt
29936 Changes in version 0.1.1.2-alpha - 2005-07-15
29937 o New directory servers:
29938 - tor26 has changed IP address.
29940 o Bugfixes on 0.1.0.x, crashes/leaks:
29941 - Port the servers-not-obeying-their-exit-policies fix from
29943 - Fix an fd leak in start_daemon().
29944 - On Windows, you can't always reopen a port right after you've
29945 closed it. So change retry_listeners() to only close and re-open
29946 ports that have changed.
29947 - Fix a possible double-free in tor_gzip_uncompress().
29949 o Bugfixes on 0.1.0.x, usability:
29950 - When tor_socketpair() fails in Windows, give a reasonable
29951 Windows-style errno back.
29952 - Let people type "tor --install" as well as "tor -install" when
29954 want to make it an NT service.
29955 - NT service patch from Matt Edman to improve error messages.
29956 - When the controller asks for a config option with an abbreviated
29957 name, give the full name in our response.
29958 - Correct the man page entry on TrackHostExitsExpire.
29959 - Looks like we were never delivering deflated (i.e. compressed)
29960 running-routers lists, even when asked. Oops.
29961 - When --disable-threads is set, do not search for or link against
29962 pthreads libraries.
29964 o Bugfixes on 0.1.1.x:
29965 - Fix a seg fault with autodetecting which controller version is
29969 - New hidden service descriptor format: put a version in it, and
29970 let people specify introduction/rendezvous points that aren't
29971 in "the directory" (which is subjective anyway).
29972 - Allow the DEBUG controller event to work again. Mark certain log
29973 entries as "don't tell this to controllers", so we avoid cycles.
29976 Changes in version 0.1.0.11 - 2005-06-30
29977 o Bugfixes on 0.1.0.x:
29978 - Fix major security bug: servers were disregarding their
29979 exit policies if clients behaved unexpectedly.
29980 - Make OS X init script check for missing argument, so we don't
29981 confuse users who invoke it incorrectly.
29982 - Fix a seg fault in "tor --hash-password foo".
29983 - The MAPADDRESS control command was broken.
29986 Changes in version 0.1.1.1-alpha - 2005-06-29
29988 - Make OS X init script check for missing argument, so we don't
29989 confuse users who invoke it incorrectly.
29990 - Fix a seg fault in "tor --hash-password foo".
29991 - Fix a possible way to DoS dirservers.
29992 - When we complain that your exit policy implicitly allows local or
29993 private address spaces, name them explicitly so operators can
29995 - Make the log message less scary when all the dirservers are
29996 temporarily unreachable.
29997 - We were printing the number of idle dns workers incorrectly when
30001 - Revised controller protocol (version 1) that uses ascii rather
30002 than binary. Add supporting libraries in python and java so you
30003 can use the controller from your applications without caring how
30004 our protocol works.
30005 - Spiffy new support for crypto hardware accelerators. Can somebody
30009 Changes in version 0.0.9.10 - 2005-06-16
30010 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
30011 - Refuse relay cells that claim to have a length larger than the
30012 maximum allowed. This prevents a potential attack that could read
30013 arbitrary memory (e.g. keys) from an exit server's process
30017 Changes in version 0.1.0.10 - 2005-06-14
30018 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
30019 libevent before 1.1a.
30022 Changes in version 0.1.0.9-rc - 2005-06-09
30024 - Reset buf->highwater every time buf_shrink() is called, not just on
30025 a successful shrink. This was causing significant memory bloat.
30026 - Fix buffer overflow when checking hashed passwords.
30027 - Security fix: if seeding the RNG on Win32 fails, quit.
30028 - Allow seeding the RNG on Win32 even when you're not running as
30030 - Disable threading on Solaris too. Something is wonky with it,
30031 cpuworkers, and reentrant libs.
30032 - Reenable the part of the code that tries to flush as soon as an
30033 OR outbuf has a full TLS record available. Perhaps this will make
30034 OR outbufs not grow as huge except in rare cases, thus saving lots
30035 of CPU time plus memory.
30036 - Reject malformed .onion addresses rather then passing them on as
30037 normal web requests.
30038 - Adapt patch from Adam Langley: fix possible memory leak in
30039 tor_lookup_hostname().
30040 - Initialize libevent later in the startup process, so the logs are
30041 already established by the time we start logging libevent warns.
30042 - Use correct errno on win32 if libevent fails.
30043 - Check and warn about known-bad/slow libevent versions.
30044 - Pay more attention to the ClientOnly config option.
30045 - Have torctl.in/tor.sh.in check for location of su binary (needed
30047 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
30048 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
30049 HttpProxyAuthenticator
30050 - Stop warning about sigpipes in the logs. We're going to
30051 pretend that getting these occasionally is normal and fine.
30052 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
30054 installer screens; and don't put stuff into StartupItems unless
30055 the user asks you to.
30056 - Require servers that use the default dirservers to have public IP
30057 addresses. We have too many servers that are configured with private
30058 IPs and their admins never notice the log entries complaining that
30059 their descriptors are being rejected.
30060 - Add OSX uninstall instructions. An actual uninstall script will
30064 Changes in version 0.1.0.8-rc - 2005-05-23
30066 - It turns out that kqueue on OS X 10.3.9 was causing kernel
30067 panics. Disable kqueue on all OS X Tors.
30068 - Fix RPM: remove duplicate line accidentally added to the rpm
30070 - Disable threads on openbsd too, since its gethostaddr is not
30072 - Tolerate libevent 0.8 since it still works, even though it's
30074 - Enable building on Red Hat 9.0 again.
30075 - Allow the middle hop of the testing circuit to be running any
30076 version, now that most of them have the bugfix to let them connect
30077 to unknown servers. This will allow reachability testing to work
30078 even when 0.0.9.7-0.0.9.9 become obsolete.
30079 - Handle relay cells with rh.length too large. This prevents
30080 a potential attack that could read arbitrary memory (maybe even
30081 keys) from the exit server's process.
30082 - We screwed up the dirport reachability testing when we don't yet
30083 have a cached version of the directory. Hopefully now fixed.
30084 - Clean up router_load_single_router() (used by the controller),
30085 so it doesn't seg fault on error.
30086 - Fix a minor memory leak when somebody establishes an introduction
30087 point at your Tor server.
30088 - If a socks connection ends because read fails, don't warn that
30089 you're not sending a socks reply back.
30092 - Add HttpProxyAuthenticator config option too, that works like
30093 the HttpsProxyAuthenticator config option.
30094 - Encode hashed controller passwords in hex instead of base64,
30095 to make it easier to write controllers.
30098 Changes in version 0.1.0.7-rc - 2005-05-17
30100 - Fix a bug in the OS X package installer that prevented it from
30101 installing on Tiger.
30102 - Fix a script bug in the OS X package installer that made it
30103 complain during installation.
30104 - Find libevent even if it's hiding in /usr/local/ and your
30105 CFLAGS and LDFLAGS don't tell you to look there.
30106 - Be able to link with libevent as a shared library (the default
30107 after 1.0d), even if it's hiding in /usr/local/lib and even
30108 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
30109 assuming you're running gcc. Otherwise fail and give a useful
30111 - Fix a bug in the RPM packager: set home directory for _tor to
30112 something more reasonable when first installing.
30113 - Free a minor amount of memory that is still reachable on exit.
30116 Changes in version 0.1.0.6-rc - 2005-05-14
30118 - Implement --disable-threads configure option. Disable threads on
30119 netbsd by default, because it appears to have no reentrant resolver
30121 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
30122 release (1.1) detects and disables kqueue if it's broken.
30123 - Append default exit policy before checking for implicit internal
30124 addresses. Now we don't log a bunch of complaints on startup
30125 when using the default exit policy.
30126 - Some people were putting "Address " in their torrc, and they had
30127 a buggy resolver that resolved " " to 0.0.0.0. Oops.
30128 - If DataDir is ~/.tor, and that expands to /.tor, then default to
30129 LOCALSTATEDIR/tor instead.
30130 - Fix fragmented-message bug in TorControl.py.
30131 - Resolve a minor bug which would prevent unreachable dirports
30132 from getting suppressed in the published descriptor.
30133 - When the controller gave us a new descriptor, we weren't resolving
30134 it immediately, so Tor would think its address was 0.0.0.0 until
30135 we fetched a new directory.
30136 - Fix an uppercase/lowercase case error in suppressing a bogus
30137 libevent warning on some Linuxes.
30140 - Begin scrubbing sensitive strings from logs by default. Turn off
30141 the config option SafeLogging if you need to do debugging.
30142 - Switch to a new buffer management algorithm, which tries to avoid
30143 reallocing and copying quite as much. In first tests it looks like
30144 it uses *more* memory on average, but less cpu.
30145 - First cut at support for "create-fast" cells. Clients can use
30146 these when extending to their first hop, since the TLS already
30147 provides forward secrecy and authentication. Not enabled on
30149 - When dirservers refuse a router descriptor, we now log its
30150 contactinfo, platform, and the poster's IP address.
30151 - Call tor_free_all instead of connections_free_all after forking, to
30152 save memory on systems that need to fork.
30153 - Whine at you if you're a server and you don't set your contactinfo.
30154 - Implement --verify-config command-line option to check if your torrc
30155 is valid without actually launching Tor.
30156 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
30157 rather than just rejecting it.
30160 Changes in version 0.1.0.5-rc - 2005-04-27
30162 - Stop trying to print a null pointer if an OR conn fails because
30163 we didn't like its cert.
30165 - Switch our internal buffers implementation to use a ring buffer,
30166 to hopefully improve performance for fast servers a lot.
30167 - Add HttpsProxyAuthenticator support (basic auth only), based
30168 on patch from Adam Langley.
30169 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
30170 the fast servers that have been joining lately.
30171 - Give hidden service accesses extra time on the first attempt,
30172 since 60 seconds is often only barely enough. This might improve
30174 - Improve performance for dirservers: stop re-parsing the whole
30175 directory every time you regenerate it.
30176 - Add more debugging info to help us find the weird dns freebsd
30177 pthreads bug; cleaner debug messages to help track future issues.
30180 Changes in version 0.0.9.9 - 2005-04-23
30181 o Bugfixes on 0.0.9.x:
30182 - If unofficial Tor clients connect and send weird TLS certs, our
30183 Tor server triggers an assert. This release contains a minimal
30184 backport from the broader fix that we put into 0.1.0.4-rc.
30187 Changes in version 0.1.0.4-rc - 2005-04-23
30189 - If unofficial Tor clients connect and send weird TLS certs, our
30190 Tor server triggers an assert. Stop asserting, and start handling
30191 TLS errors better in other situations too.
30192 - When the controller asks us to tell it about all the debug-level
30193 logs, it turns out we were generating debug-level logs while
30194 telling it about them, which turns into a bad loop. Now keep
30195 track of whether you're sending a debug log to the controller,
30196 and don't log when you are.
30197 - Fix the "postdescriptor" feature of the controller interface: on
30198 non-complete success, only say "done" once.
30200 - Clients are now willing to load balance over up to 2mB, not 1mB,
30201 of advertised bandwidth capacity.
30202 - Add a NoPublish config option, so you can be a server (e.g. for
30203 testing running Tor servers in other Tor networks) without
30204 publishing your descriptor to the primary dirservers.
30207 Changes in version 0.1.0.3-rc - 2005-04-08
30208 o Improvements on 0.1.0.2-rc:
30209 - Client now retries when streams end early for 'hibernating' or
30210 'resource limit' reasons, rather than failing them.
30211 - More automated handling for dirserver operators:
30212 - Automatically approve nodes running 0.1.0.2-rc or later,
30213 now that the the reachability detection stuff is working.
30214 - Now we allow two unverified servers with the same nickname
30215 but different keys. But if a nickname is verified, only that
30216 nickname+key are allowed.
30217 - If you're an authdirserver connecting to an address:port,
30218 and it's not the OR you were expecting, forget about that
30219 descriptor. If he *was* the one you were expecting, then forget
30220 about all other descriptors for that address:port.
30221 - Allow servers to publish descriptors from 12 hours in the future.
30222 Corollary: only whine about clock skew from the dirserver if
30223 he's a trusted dirserver (since now even verified servers could
30224 have quite wrong clocks).
30225 - Adjust maximum skew and age for rendezvous descriptors: let skew
30226 be 48 hours rather than 90 minutes.
30227 - Efficiency improvements:
30228 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
30229 it much faster to look up a circuit for each relay cell.
30230 - Remove most calls to assert_all_pending_dns_resolves_ok(),
30231 since they're eating our cpu on exit nodes.
30232 - Stop wasting time doing a case insensitive comparison for every
30233 dns name every time we do any lookup. Canonicalize the names to
30234 lowercase and be done with it.
30235 - Start sending 'truncated' cells back rather than destroy cells,
30236 if the circuit closes in front of you. This means we won't have
30237 to abandon partially built circuits.
30238 - Only warn once per nickname from add_nickname_list_to_smartlist
30239 per failure, so an entrynode or exitnode choice that's down won't
30241 - Put a note in the torrc about abuse potential with the default
30243 - Revise control spec and implementation to allow all log messages to
30244 be sent to controller with their severities intact (suggested by
30245 Matt Edman). Update TorControl to handle new log event types.
30246 - Provide better explanation messages when controller's POSTDESCRIPTOR
30248 - Stop putting nodename in the Platform string in server descriptors.
30249 It doesn't actually help, and it is confusing/upsetting some people.
30251 o Bugfixes on 0.1.0.2-rc:
30252 - We were printing the host mask wrong in exit policies in server
30253 descriptors. This isn't a critical bug though, since we were still
30254 obeying the exit policy internally.
30255 - Fix Tor when compiled with libevent but without pthreads: move
30256 connection_unregister() from _connection_free() to
30258 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
30259 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
30260 when we look through the connection array, we'll find any of the
30261 cpu/dnsworkers. This is no good.
30263 o Bugfixes on 0.0.9.8:
30264 - Fix possible bug on threading platforms (e.g. win32) which was
30265 leaking a file descriptor whenever a cpuworker or dnsworker died.
30266 - When using preferred entry or exit nodes, ignore whether the
30267 circuit wants uptime or capacity. They asked for the nodes, they
30269 - chdir() to your datadirectory at the *end* of the daemonize process,
30270 not the beginning. This was a problem because the first time you
30271 run tor, if your datadir isn't there, and you have runasdaemon set
30272 to 1, it will try to chdir to it before it tries to create it. Oops.
30273 - Handle changed router status correctly when dirserver reloads
30274 fingerprint file. We used to be dropping all unverified descriptors
30275 right then. The bug was hidden because we would immediately
30276 fetch a directory from another dirserver, which would include the
30277 descriptors we just dropped.
30278 - When we're connecting to an OR and he's got a different nickname/key
30279 than we were expecting, only complain loudly if we're an OP or a
30280 dirserver. Complaining loudly to the OR admins just confuses them.
30281 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
30282 artificially capped at 500kB.
30285 Changes in version 0.0.9.8 - 2005-04-07
30286 o Bugfixes on 0.0.9.x:
30287 - We have a bug that I haven't found yet. Sometimes, very rarely,
30288 cpuworkers get stuck in the 'busy' state, even though the cpuworker
30289 thinks of itself as idle. This meant that no new circuits ever got
30290 established. Here's a workaround to kill any cpuworker that's been
30291 busy for more than 100 seconds.
30294 Changes in version 0.1.0.2-rc - 2005-04-01
30295 o Bugfixes on 0.1.0.1-rc:
30296 - Fixes on reachability detection:
30297 - Don't check for reachability while hibernating.
30298 - If ORPort is reachable but DirPort isn't, still publish the
30299 descriptor, but zero out DirPort until it's found reachable.
30300 - When building testing circs for ORPort testing, use only
30301 high-bandwidth nodes, so fewer circuits fail.
30302 - Complain about unreachable ORPort separately from unreachable
30303 DirPort, so the user knows what's going on.
30304 - Make sure we only conclude ORPort reachability if we didn't
30305 initiate the conn. Otherwise we could falsely conclude that
30306 we're reachable just because we connected to the guy earlier
30307 and he used that same pipe to extend to us.
30308 - Authdirservers shouldn't do ORPort reachability detection,
30309 since they're in clique mode, so it will be rare to find a
30310 server not already connected to them.
30311 - When building testing circuits, always pick middle hops running
30312 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
30313 bug. (This is a kludge; it will go away when 0.0.9.x becomes
30315 - When we decide we're reachable, actually publish our descriptor
30317 - Fix bug in redirectstream in the controller.
30318 - Fix the state descriptor strings so logs don't claim edge streams
30319 are in a different state than they actually are.
30320 - Use recent libevent features when possible (this only really affects
30321 win32 and osx right now, because the new libevent with these
30322 features hasn't been released yet). Add code to suppress spurious
30324 - Prevent possible segfault in connection_close_unattached_ap().
30325 - Fix newlines on torrc in win32.
30326 - Improve error msgs when tor-resolve fails.
30328 o Improvements on 0.0.9.x:
30329 - New experimental script tor/contrib/ExerciseServer.py (needs more
30330 work) that uses the controller interface to build circuits and
30331 fetch pages over them. This will help us bootstrap servers that
30332 have lots of capacity but haven't noticed it yet.
30333 - New experimental script tor/contrib/PathDemo.py (needs more work)
30334 that uses the controller interface to let you choose whole paths
30336 "<hostname>.<path,separated by dots>.<length of path>.path"
30337 - When we've connected to an OR and handshaked but didn't like
30338 the result, we were closing the conn without sending destroy
30339 cells back for pending circuits. Now send those destroys.
30342 Changes in version 0.0.9.7 - 2005-04-01
30343 o Bugfixes on 0.0.9.x:
30344 - Fix another race crash bug (thanks to Glenn Fink for reporting).
30345 - Compare identity to identity, not to nickname, when extending to
30346 a router not already in the directory. This was preventing us from
30347 extending to unknown routers. Oops.
30348 - Make sure to create OS X Tor user in <500 range, so we aren't
30349 creating actual system users.
30350 - Note where connection-that-hasn't-sent-end was marked, and fix
30351 a few really loud instances of this harmless bug (it's fixed more
30355 Changes in version 0.1.0.1-rc - 2005-03-28
30357 - Add reachability testing. Your Tor server will automatically try
30358 to see if its ORPort and DirPort are reachable from the outside,
30359 and it won't upload its descriptor until it decides they are.
30360 - Handle unavailable hidden services better. Handle slow or busy
30361 hidden services better.
30362 - Add support for CONNECTing through https proxies, with "HttpsProxy"
30364 - New exit policy: accept most low-numbered ports, rather than
30365 rejecting most low-numbered ports.
30366 - More Tor controller support (still experimental). See
30367 http://tor.eff.org/doc/control-spec.txt for all the new features,
30368 including signals to emulate unix signals from any platform;
30369 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
30370 closestream; closecircuit; etc.
30371 - Make nt services work and start on startup on win32 (based on
30372 patch by Matt Edman).
30373 - Add a new AddressMap config directive to rewrite incoming socks
30374 addresses. This lets you, for example, declare an implicit
30375 required exit node for certain sites.
30376 - Add a new TrackHostExits config directive to trigger addressmaps
30377 for certain incoming socks addresses -- for sites that break when
30378 your exit keeps changing (based on patch by Mike Perry).
30379 - Redo the client-side dns cache so it's just an addressmap too.
30380 - Notice when our IP changes, and reset stats/uptime/reachability.
30381 - When an application is using socks5, give him the whole variety of
30382 potential socks5 responses (connect refused, host unreachable, etc),
30383 rather than just "success" or "failure".
30384 - A more sane version numbering system. See
30385 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
30386 - New contributed script "exitlist": a simple python script to
30387 parse directories and find Tor nodes that exit to listed
30389 - New contributed script "privoxy-tor-toggle" to toggle whether
30390 Privoxy uses Tor. Seems to be configured for Debian by default.
30391 - Report HTTP reasons to client when getting a response from directory
30392 servers -- so you can actually know what went wrong.
30393 - New config option MaxAdvertisedBandwidth which lets you advertise
30394 a low bandwidthrate (to not attract as many circuits) while still
30395 allowing a higher bandwidthrate in reality.
30397 o Robustness/stability fixes:
30398 - Make Tor use Niels Provos's libevent instead of its current
30399 poll-but-sometimes-select mess. This will let us use faster async
30400 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
30402 - pthread support now too. This was forced because when we forked,
30403 we ended up wasting a lot of duplicate ram over time. Also switch
30404 to foo_r versions of some library calls to allow reentry and
30406 - Better handling for heterogeneous / unreliable nodes:
30407 - Annotate circuits w/ whether they aim to contain high uptime nodes
30408 and/or high capacity nodes. When building circuits, choose
30410 - This means that every single node in an intro rend circuit,
30411 not just the last one, will have a minimum uptime.
30412 - New config option LongLivedPorts to indicate application streams
30413 that will want high uptime circuits.
30414 - Servers reset uptime when a dir fetch entirely fails. This
30415 hopefully reflects stability of the server's network connectivity.
30416 - If somebody starts his tor server in Jan 2004 and then fixes his
30417 clock, don't make his published uptime be a year.
30418 - Reset published uptime when you wake up from hibernation.
30419 - Introduce a notion of 'internal' circs, which are chosen without
30420 regard to the exit policy of the last hop. Intro and rendezvous
30421 circs must be internal circs, to avoid leaking information. Resolve
30422 and connect streams can use internal circs if they want.
30423 - New circuit pooling algorithm: make sure to have enough circs around
30424 to satisfy any predicted ports, and also make sure to have 2 internal
30425 circs around if we've required internal circs lately (and with high
30426 uptime if we've seen that lately too).
30427 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
30428 which describes how often we retry making new circuits if current
30429 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
30430 how long we're willing to make use of an already-dirty circuit.
30431 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
30432 circ as necessary, if there are any completed ones lying around
30433 when we try to launch one.
30434 - Make hidden services try to establish a rendezvous for 30 seconds,
30435 rather than for n (where n=3) attempts to build a circuit.
30436 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
30437 "ShutdownWaitLength".
30438 - Try to be more zealous about calling connection_edge_end when
30439 things go bad with edge conns in connection.c.
30440 - Revise tor-spec to add more/better stream end reasons.
30441 - Revise all calls to connection_edge_end to avoid sending "misc",
30442 and to take errno into account where possible.
30445 - Fix a race condition that can trigger an assert, when we have a
30446 pending create cell and an OR connection fails right then.
30447 - Fix several double-mark-for-close bugs, e.g. where we were finding
30448 a conn for a cell even if that conn is already marked for close.
30449 - Make sequence of log messages when starting on win32 with no config
30450 file more reasonable.
30451 - When choosing an exit node for a new non-internal circ, don't take
30452 into account whether it'll be useful for any pending x.onion
30453 addresses -- it won't.
30454 - Turn addr_policy_compare from a tristate to a quadstate; this should
30455 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
30456 for google.com" problem.
30457 - Make "platform" string in descriptor more accurate for Win32 servers,
30458 so it's not just "unknown platform".
30459 - Fix an edge case in parsing config options (thanks weasel).
30460 If they say "--" on the commandline, it's not an option.
30461 - Reject odd-looking addresses at the client (e.g. addresses that
30462 contain a colon), rather than having the server drop them because
30464 - tor-resolve requests were ignoring .exit if there was a working circuit
30465 they could use instead.
30466 - REUSEADDR on normal platforms means you can rebind to the port
30467 right after somebody else has let it go. But REUSEADDR on win32
30468 means to let you bind to the port _even when somebody else
30469 already has it bound_! So, don't do that on Win32.
30470 - Change version parsing logic: a version is "obsolete" if it is not
30471 recommended and (1) there is a newer recommended version in the
30472 same series, or (2) there are no recommended versions in the same
30473 series, but there are some recommended versions in a newer series.
30474 A version is "new" if it is newer than any recommended version in
30476 - Stop most cases of hanging up on a socks connection without sending
30480 - Require BandwidthRate to be at least 20kB/s for servers.
30481 - When a dirserver causes you to give a warn, mention which dirserver
30483 - New config option DirAllowPrivateAddresses for authdirservers.
30484 Now by default they refuse router descriptors that have non-IP or
30485 private-IP addresses.
30486 - Stop publishing socksport in the directory, since it's not
30487 actually meant to be public. For compatibility, publish a 0 there
30489 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
30490 smart" value, that is low for servers and high for clients.
30491 - If our clock jumps forward by 100 seconds or more, assume something
30492 has gone wrong with our network and abandon all not-yet-used circs.
30493 - Warn when exit policy implicitly allows local addresses.
30494 - If we get an incredibly skewed timestamp from a dirserver mirror
30495 that isn't a verified OR, don't warn -- it's probably him that's
30497 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
30498 cookies to disk and doesn't log each web request to disk. (Thanks
30499 to Brett Carrington for pointing this out.)
30500 - When a client asks us for a dir mirror and we don't have one,
30501 launch an attempt to get a fresh one.
30502 - If we're hibernating and we get a SIGINT, exit immediately.
30503 - Add --with-dmalloc ./configure option, to track memory leaks.
30504 - And try to free all memory on closing, so we can detect what
30506 - Cache local dns resolves correctly even when they're .exit
30508 - Give a better warning when some other server advertises an
30509 ORPort that is actually an apache running ssl.
30510 - Add "opt hibernating 1" to server descriptor to make it clearer
30511 whether the server is hibernating.
30514 Changes in version 0.0.9.6 - 2005-03-24
30515 o Bugfixes on 0.0.9.x (crashes and asserts):
30516 - Add new end stream reasons to maintenance branch. Fix bug where
30517 reason (8) could trigger an assert. Prevent bug from recurring.
30518 - Apparently win32 stat wants paths to not end with a slash.
30519 - Fix assert triggers in assert_cpath_layer_ok(), where we were
30520 blowing away the circuit that conn->cpath_layer points to, then
30521 checking to see if the circ is well-formed. Backport check to make
30522 sure we dont use the cpath on a closed connection.
30523 - Prevent circuit_resume_edge_reading_helper() from trying to package
30524 inbufs for marked-for-close streams.
30525 - Don't crash on hup if your options->address has become unresolvable.
30526 - Some systems (like OS X) sometimes accept() a connection and tell
30527 you the remote host is 0.0.0.0:0. If this happens, due to some
30528 other mis-features, we get confused; so refuse the conn for now.
30530 o Bugfixes on 0.0.9.x (other):
30531 - Fix harmless but scary "Unrecognized content encoding" warn message.
30532 - Add new stream error reason: TORPROTOCOL reason means "you are not
30533 speaking a version of Tor I understand; say bye-bye to your stream."
30534 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
30535 into the future, now that we are more tolerant of skew. This
30536 resolves a bug where a Tor server would refuse to cache a directory
30537 because all the directories it gets are too far in the future;
30538 yet the Tor server never logs any complaints about clock skew.
30539 - Mac packaging magic: make man pages useable, and do not overwrite
30540 existing torrc files.
30541 - Make OS X log happily to /var/log/tor/tor.log
30544 Changes in version 0.0.9.5 - 2005-02-22
30545 o Bugfixes on 0.0.9.x:
30546 - Fix an assert race at exit nodes when resolve requests fail.
30547 - Stop picking unverified dir mirrors--it only leads to misery.
30548 - Patch from Matt Edman to make NT services work better. Service
30549 support is still not compiled into the executable by default.
30550 - Patch from Dmitri Bely so the Tor service runs better under
30551 the win32 SYSTEM account.
30552 - Make tor-resolve actually work (?) on Win32.
30553 - Fix a sign bug when getrlimit claims to have 4+ billion
30554 file descriptors available.
30555 - Stop refusing to start when bandwidthburst == bandwidthrate.
30556 - When create cells have been on the onion queue more than five
30557 seconds, just send back a destroy and take them off the list.
30560 Changes in version 0.0.9.4 - 2005-02-03
30561 o Bugfixes on 0.0.9:
30562 - Fix an assert bug that took down most of our servers: when
30563 a server claims to have 1 GB of bandwidthburst, don't
30565 - Don't crash as badly if we have spawned the max allowed number
30566 of dnsworkers, or we're out of file descriptors.
30567 - Block more file-sharing ports in the default exit policy.
30568 - MaxConn is now automatically set to the hard limit of max
30569 file descriptors we're allowed (ulimit -n), minus a few for
30571 - Give a clearer message when servers need to raise their
30572 ulimit -n when they start running out of file descriptors.
30573 - SGI Compatibility patches from Jan Schaumann.
30574 - Tolerate a corrupt cached directory better.
30575 - When a dirserver hasn't approved your server, list which one.
30576 - Go into soft hibernation after 95% of the bandwidth is used,
30577 not 99%. This is especially important for daily hibernators who
30578 have a small accounting max. Hopefully it will result in fewer
30579 cut connections when the hard hibernation starts.
30580 - Load-balance better when using servers that claim more than
30581 800kB/s of capacity.
30582 - Make NT services work (experimental, only used if compiled in).
30585 Changes in version 0.0.9.3 - 2005-01-21
30586 o Bugfixes on 0.0.9:
30587 - Backport the cpu use fixes from main branch, so busy servers won't
30588 need as much processor time.
30589 - Work better when we go offline and then come back, or when we
30590 run Tor at boot before the network is up. We do this by
30591 optimistically trying to fetch a new directory whenever an
30592 application request comes in and we think we're offline -- the
30593 human is hopefully a good measure of when the network is back.
30594 - Backport some minimal hidserv bugfixes: keep rend circuits open as
30595 long as you keep using them; actually publish hidserv descriptors
30596 shortly after they change, rather than waiting 20-40 minutes.
30597 - Enable Mac startup script by default.
30598 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
30599 - When you update AllowUnverifiedNodes or FirewallPorts via the
30600 controller's setconf feature, we were always appending, never
30602 - When you update HiddenServiceDir via setconf, it was screwing up
30603 the order of reading the lines, making it fail.
30604 - Do not rewrite a cached directory back to the cache; otherwise we
30605 will think it is recent and not fetch a newer one on startup.
30606 - Workaround for webservers that lie about Content-Encoding: Tor
30607 now tries to autodetect compressed directories and compression
30608 itself. This lets us Proxypass dir fetches through apache.
30611 Changes in version 0.0.9.2 - 2005-01-04
30612 o Bugfixes on 0.0.9 (crashes and asserts):
30613 - Fix an assert on startup when the disk is full and you're logging
30615 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
30616 style address, then we'd crash.
30617 - Fix an assert trigger when the running-routers string we get from
30618 a dirserver is broken.
30619 - Make worker threads start and run on win32. Now win32 servers
30621 - Bandaid (not actually fix, but now it doesn't crash) an assert
30622 where the dns worker dies mysteriously and the main Tor process
30623 doesn't remember anything about the address it was resolving.
30625 o Bugfixes on 0.0.9 (Win32):
30626 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
30627 name out of the warning/assert messages.
30628 - Fix a superficial "unhandled error on read" bug on win32.
30629 - The win32 installer no longer requires a click-through for our
30630 license, since our Free Software license grants rights but does not
30632 - Win32: When connecting to a dirserver fails, try another one
30633 immediately. (This was already working for non-win32 Tors.)
30634 - Stop trying to parse $HOME on win32 when hunting for default
30636 - Make tor-resolve.c work on win32 by calling network_init().
30638 o Bugfixes on 0.0.9 (other):
30639 - Make 0.0.9.x build on Solaris again.
30640 - Due to a fencepost error, we were blowing away the \n when reporting
30641 confvalue items in the controller. So asking for multiple config
30642 values at once couldn't work.
30643 - When listing circuits that are pending on an opening OR connection,
30644 if we're an OR we were listing circuits that *end* at us as
30645 being pending on every listener, dns/cpu worker, etc. Stop that.
30646 - Dirservers were failing to create 'running-routers' or 'directory'
30647 strings if we had more than some threshold of routers. Fix them so
30648 they can handle any number of routers.
30649 - Fix a superficial "Duplicate mark for close" bug.
30650 - Stop checking for clock skew for OR connections, even for servers.
30651 - Fix a fencepost error that was chopping off the last letter of any
30652 nickname that is the maximum allowed nickname length.
30653 - Update URLs in log messages so they point to the new website.
30654 - Fix a potential problem in mangling server private keys while
30655 writing to disk (not triggered yet, as far as we know).
30656 - Include the licenses for other free software we include in Tor,
30657 now that we're shipping binary distributions more regularly.
30660 Changes in version 0.0.9.1 - 2004-12-15
30661 o Bugfixes on 0.0.9:
30662 - Make hibernation actually work.
30663 - Make HashedControlPassword config option work.
30664 - When we're reporting event circuit status to a controller,
30665 don't use the stream status code.
30668 Changes in version 0.0.9 - 2004-12-12
30670 - Clean up manpage and torrc.sample file.
30671 - Clean up severities and text of log warnings.
30673 - Make servers trigger an assert when they enter hibernation.
30676 Changes in version 0.0.9rc7 - 2004-12-08
30677 o Bugfixes on 0.0.9rc:
30678 - Fix a stack-trashing crash when an exit node begins hibernating.
30679 - Avoid looking at unallocated memory while considering which
30680 ports we need to build circuits to cover.
30681 - Stop a sigpipe: when an 'end' cell races with eof from the app,
30682 we shouldn't hold-open-until-flush if the eof arrived first.
30683 - Fix a bug with init_cookie_authentication() in the controller.
30684 - When recommending new-format log lines, if the upper bound is
30685 LOG_ERR, leave it implicit.
30687 o Bugfixes on 0.0.8.1:
30688 - Fix a whole slew of memory leaks.
30689 - Fix isspace() and friends so they still make Solaris happy
30690 but also so they don't trigger asserts on win32.
30691 - Fix parse_iso_time on platforms without strptime (eg win32).
30692 - win32: tolerate extra "readable" events better.
30693 - win32: when being multithreaded, leave parent fdarray open.
30694 - Make unit tests work on win32.
30697 Changes in version 0.0.9rc6 - 2004-12-06
30698 o Bugfixes on 0.0.9pre:
30699 - Clean up some more integer underflow opportunities (not exploitable
30701 - While hibernating, hup should not regrow our listeners.
30702 - Send an end to the streams we close when we hibernate, rather
30703 than just chopping them off.
30704 - React to eof immediately on non-open edge connections.
30706 o Bugfixes on 0.0.8.1:
30707 - Calculate timeout for waiting for a connected cell from the time
30708 we sent the begin cell, not from the time the stream started. If
30709 it took a long time to establish the circuit, we would time out
30710 right after sending the begin cell.
30711 - Fix router_compare_addr_to_addr_policy: it was not treating a port
30712 of * as always matching, so we were picking reject *:* nodes as
30713 exit nodes too. Oops.
30716 - New circuit building strategy: keep a list of ports that we've
30717 used in the past 6 hours, and always try to have 2 circuits open
30718 or on the way that will handle each such port. Seed us with port
30719 80 so web users won't complain that Tor is "slow to start up".
30720 - Make kill -USR1 dump more useful stats about circuits.
30721 - When warning about retrying or giving up, print the address, so
30722 the user knows which one it's talking about.
30723 - If you haven't used a clean circuit in an hour, throw it away,
30724 just to be on the safe side. (This means after 6 hours a totally
30725 unused Tor client will have no circuits open.)
30728 Changes in version 0.0.9rc5 - 2004-12-01
30729 o Bugfixes on 0.0.8.1:
30730 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
30731 - Let resolve conns retry/expire also, rather than sticking around
30733 - If we are using select, make sure we stay within FD_SETSIZE.
30735 o Bugfixes on 0.0.9pre:
30736 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
30737 but doesn't seem to be currently; thanks to Ilja van Sprundel for
30739 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
30740 instead. Impose minima and maxima for all *Period options; impose
30741 even tighter maxima for fetching if we are a caching dirserver.
30742 Clip rather than rejecting.
30743 - Fetch cached running-routers from servers that serve it (that is,
30744 authdirservers and servers running 0.0.9rc5-cvs or later.)
30747 - Accept *:706 (silc) in default exit policy.
30748 - Implement new versioning format for post 0.1.
30749 - Support "foo.nickname.exit" addresses, to let Alice request the
30750 address "foo" as viewed by exit node "nickname". Based on a patch
30752 - Make tor --version --version dump the cvs Id of every file.
30755 Changes in version 0.0.9rc4 - 2004-11-28
30756 o Bugfixes on 0.0.8.1:
30757 - Make windows sockets actually non-blocking (oops), and handle
30758 win32 socket errors better.
30760 o Bugfixes on 0.0.9rc1:
30761 - Actually catch the -USR2 signal.
30764 Changes in version 0.0.9rc3 - 2004-11-25
30765 o Bugfixes on 0.0.8.1:
30766 - Flush the log file descriptor after we print "Tor opening log file",
30767 so we don't see those messages days later.
30769 o Bugfixes on 0.0.9rc1:
30770 - Make tor-resolve work again.
30771 - Avoid infinite loop in tor-resolve if tor hangs up on it.
30772 - Fix an assert trigger for clients/servers handling resolves.
30775 Changes in version 0.0.9rc2 - 2004-11-24
30776 o Bugfixes on 0.0.9rc1:
30777 - I broke socks5 support while fixing the eof bug.
30778 - Allow unitless bandwidths and intervals; they default to bytes
30780 - New servers don't start out hibernating; they are active until
30781 they run out of bytes, so they have a better estimate of how
30782 long it takes, and so their operators can know they're working.
30785 Changes in version 0.0.9rc1 - 2004-11-23
30786 o Bugfixes on 0.0.8.1:
30787 - Finally fix a bug that's been plaguing us for a year:
30788 With high load, circuit package window was reaching 0. Whenever
30789 we got a circuit-level sendme, we were reading a lot on each
30790 socket, but only writing out a bit. So we would eventually reach
30791 eof. This would be noticed and acted on even when there were still
30792 bytes sitting in the inbuf.
30793 - When poll() is interrupted, we shouldn't believe the revents values.
30795 o Bugfixes on 0.0.9pre6:
30796 - Fix hibernate bug that caused pre6 to be broken.
30797 - Don't keep rephist info for routers that haven't had activity for
30798 24 hours. (This matters now that clients have keys, since we track
30800 - Never call close_temp_logs while validating log options.
30801 - Fix backslash-escaping on tor.sh.in and torctl.in.
30804 - Implement weekly/monthly/daily accounting: now you specify your
30805 hibernation properties by
30806 AccountingMax N bytes|KB|MB|GB|TB
30807 AccountingStart day|week|month [day] HH:MM
30808 Defaults to "month 1 0:00".
30809 - Let bandwidth and interval config options be specified as 5 bytes,
30810 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
30811 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
30812 get back to normal.)
30813 - If your requested entry or exit node has advertised bandwidth 0,
30815 - Be more greedy about filling up relay cells -- we try reading again
30816 once we've processed the stuff we read, in case enough has arrived
30817 to fill the last cell completely.
30818 - Apply NT service patch from Osamu Fujino. Still needs more work.
30821 Changes in version 0.0.9pre6 - 2004-11-15
30822 o Bugfixes on 0.0.8.1:
30823 - Fix assert failure on malformed socks4a requests.
30824 - Use identity comparison, not nickname comparison, to choose which
30825 half of circuit-ID-space each side gets to use. This is needed
30826 because sometimes we think of a router as a nickname, and sometimes
30827 as a hex ID, and we can't predict what the other side will do.
30828 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
30829 write() call will fail and we handle it there.
30830 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
30831 and smartlist_len, which are two major profiling offenders.
30833 o Bugfixes on 0.0.9pre5:
30834 - Fix a bug in read_all that was corrupting config files on windows.
30835 - When we're raising the max number of open file descriptors to
30836 'unlimited', don't log that we just raised it to '-1'.
30837 - Include event code with events, as required by control-spec.txt.
30838 - Don't give a fingerprint when clients do --list-fingerprint:
30839 it's misleading, because it will never be the same again.
30840 - Stop using strlcpy in tor_strndup, since it was slowing us
30842 - Remove warn on startup about missing cached-directory file.
30843 - Make kill -USR1 work again.
30844 - Hibernate if we start tor during the "wait for wakeup-time" phase
30845 of an accounting interval. Log our hibernation plans better.
30846 - Authoritative dirservers now also cache their directory, so they
30847 have it on start-up.
30850 - Fetch running-routers; cache running-routers; compress
30851 running-routers; serve compressed running-routers.z
30852 - Add NSI installer script contributed by J Doe.
30853 - Commit VC6 and VC7 workspace/project files.
30854 - Commit a tor.spec for making RPM files, with help from jbash.
30855 - Add contrib/torctl.in contributed by Glenn Fink.
30856 - Implement the control-spec's SAVECONF command, to write your
30857 configuration to torrc.
30858 - Get cookie authentication for the controller closer to working.
30859 - Include control-spec.txt in the tarball.
30860 - When set_conf changes our server descriptor, upload a new copy.
30861 But don't upload it too often if there are frequent changes.
30862 - Document authentication config in man page, and document signals
30864 - Clean up confusing parts of man page and torrc.sample.
30865 - Make expand_filename handle ~ and ~username.
30866 - Use autoconf to enable largefile support where necessary. Use
30867 ftello where available, since ftell can fail at 2GB.
30868 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
30869 log more informatively.
30870 - Give a slightly more useful output for "tor -h".
30871 - Refuse application socks connections to port 0.
30872 - Check clock skew for verified servers, but allow unverified
30873 servers and clients to have any clock skew.
30874 - Break DirFetchPostPeriod into:
30875 - DirFetchPeriod for fetching full directory,
30876 - StatusFetchPeriod for fetching running-routers,
30877 - DirPostPeriod for posting server descriptor,
30878 - RendPostPeriod for posting hidden service descriptors.
30879 - Make sure the hidden service descriptors are at a random offset
30880 from each other, to hinder linkability.
30883 Changes in version 0.0.9pre5 - 2004-11-09
30884 o Bugfixes on 0.0.9pre4:
30885 - Fix a seg fault in unit tests (doesn't affect main program).
30886 - Fix an assert bug where a hidden service provider would fail if
30887 the first hop of his rendezvous circuit was down.
30888 - Hidden service operators now correctly handle version 1 style
30889 INTRODUCE1 cells (nobody generates them still, so not a critical
30891 - If do_hup fails, actually notice.
30892 - Handle more errnos from accept() without closing the listener.
30893 Some OpenBSD machines were closing their listeners because
30894 they ran out of file descriptors.
30895 - Send resolve cells to exit routers that are running a new
30896 enough version of the resolve code to work right.
30897 - Better handling of winsock includes on non-MSV win32 compilers.
30898 - Some people had wrapped their tor client/server in a script
30899 that would restart it whenever it died. This did not play well
30900 with our "shut down if your version is obsolete" code. Now people
30901 don't fetch a new directory if their local cached version is
30903 - Make our autogen.sh work on ksh as well as bash.
30906 - Hibernation: New config option "AccountingMaxKB" lets you
30907 set how many KBytes per month you want to allow your server to
30908 consume. Rather than spreading those bytes out evenly over the
30909 month, we instead hibernate for some of the month and pop up
30910 at a deterministic time, work until the bytes are consumed, then
30911 hibernate again. Config option "MonthlyAccountingStart" lets you
30912 specify which day of the month your billing cycle starts on.
30913 - Control interface: a separate program can now talk to your
30914 client/server over a socket, and get/set config options, receive
30915 notifications of circuits and streams starting/finishing/dying,
30916 bandwidth used, etc. The next step is to get some GUIs working.
30917 Let us know if you want to help out. See doc/control-spec.txt .
30918 - Ship a contrib/tor-control.py as an example script to interact
30919 with the control port.
30920 - "tor --hash-password zzyxz" will output a salted password for
30921 use in authenticating to the control interface.
30922 - New log format in config:
30923 "Log minsev[-maxsev] stdout|stderr|syslog" or
30924 "Log minsev[-maxsev] file /var/foo"
30927 - DirPolicy config option, to let people reject incoming addresses
30928 from their dirserver.
30929 - "tor --list-fingerprint" will list your identity key fingerprint
30931 - Add "pass" target for RedirectExit, to make it easier to break
30932 out of a sequence of RedirectExit rules.
30933 - Clients now generate a TLS cert too, in preparation for having
30934 them act more like real nodes.
30935 - Ship src/win32/ in the tarball, so people can use it to build.
30936 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
30938 - New "router-status" line in directory, to better bind each verified
30939 nickname to its identity key.
30940 - Deprecate unofficial config option abbreviations, and abbreviations
30941 not on the command line.
30942 - Add a pure-C tor-resolve implementation.
30943 - Use getrlimit and friends to ensure we can reach MaxConn (currently
30944 1024) file descriptors.
30946 o Code security improvements, inspired by Ilja:
30947 - Replace sprintf with snprintf. (I think they were all safe, but
30949 - Replace strcpy/strncpy with strlcpy in more places.
30950 - Avoid strcat; use snprintf or strlcat instead.
30951 - snprintf wrapper with consistent (though not C99) overflow behavior.
30954 Changes in version 0.0.9pre4 - 2004-10-17
30955 o Bugfixes on 0.0.9pre3:
30956 - If the server doesn't specify an exit policy, use the real default
30957 exit policy, not reject *:*.
30958 - Ignore fascistfirewall when uploading/downloading hidden service
30959 descriptors, since we go through Tor for those; and when using
30960 an HttpProxy, since we assume it can reach them all.
30961 - When looking for an authoritative dirserver, use only the ones
30962 configured at boot. Don't bother looking in the directory.
30963 - The rest of the fix for get_default_conf_file() on older win32.
30964 - Make 'Routerfile' config option obsolete.
30967 - New 'MyFamily nick1,...' config option for a server to
30968 specify other servers that shouldn't be used in the same circuit
30969 with it. Only believed if nick1 also specifies us.
30970 - New 'NodeFamily nick1,nick2,...' config option for a client to
30971 specify nodes that it doesn't want to use in the same circuit.
30972 - New 'Redirectexit pattern address:port' config option for a
30973 server to redirect exit connections, e.g. to a local squid.
30976 Changes in version 0.0.9pre3 - 2004-10-13
30977 o Bugfixes on 0.0.8.1:
30978 - Better torrc example lines for dirbindaddress and orbindaddress.
30979 - Improved bounds checking on parsed ints (e.g. config options and
30980 the ones we find in directories.)
30981 - Better handling of size_t vs int, so we're more robust on 64
30983 - Fix the rest of the bug where a newly started OR would appear
30984 as unverified even after we've added his fingerprint and hupped
30986 - Fix a bug from 0.0.7: when read() failed on a stream, we would
30987 close it without sending back an end. So 'connection refused'
30988 would simply be ignored and the user would get no response.
30990 o Bugfixes on 0.0.9pre2:
30991 - Serving the cached-on-disk directory to people is bad. We now
30992 provide no directory until we've fetched a fresh one.
30993 - Workaround for bug on windows where cached-directories get crlf
30995 - Make get_default_conf_file() work on older windows too.
30996 - If we write a *:* exit policy line in the descriptor, don't write
30997 any more exit policy lines.
31000 - Use only 0.0.9pre1 and later servers for resolve cells.
31001 - Make the dirservers file obsolete.
31002 - Include a dir-signing-key token in directories to tell the
31003 parsing entity which key is being used to sign.
31004 - Remove the built-in bulky default dirservers string.
31005 - New config option "Dirserver %s:%d [fingerprint]", which can be
31006 repeated as many times as needed. If no dirservers specified,
31007 default to moria1,moria2,tor26.
31008 - Make moria2 advertise a dirport of 80, so people behind firewalls
31009 will be able to get a directory.
31010 - Http proxy support
31011 - Dirservers translate requests for http://%s:%d/x to /x
31012 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
31013 be routed through this host.
31014 - Clients ask for /tor/x rather than /x for new enough dirservers.
31015 This way we can one day coexist peacefully with apache.
31016 - Clients specify a "Host: %s%d" http header, to be compatible
31017 with more proxies, and so running squid on an exit node can work.
31020 Changes in version 0.0.8.1 - 2004-10-13
31022 - Fix a seg fault that can be triggered remotely for Tor
31023 clients/servers with an open dirport.
31024 - Fix a rare assert trigger, where routerinfos for entries in
31025 our cpath would expire while we're building the path.
31026 - Fix a bug in OutboundBindAddress so it (hopefully) works.
31027 - Fix a rare seg fault for people running hidden services on
31028 intermittent connections.
31029 - Fix a bug in parsing opt keywords with objects.
31030 - Fix a stale pointer assert bug when a stream detaches and
31032 - Fix a string format vulnerability (probably not exploitable)
31033 in reporting stats locally.
31034 - Fix an assert trigger: sometimes launching circuits can fail
31035 immediately, e.g. because too many circuits have failed recently.
31036 - Fix a compile warning on 64 bit platforms.
31039 Changes in version 0.0.9pre2 - 2004-10-03
31041 - Make fetching a cached directory work for 64-bit platforms too.
31042 - Make zlib.h a required header, not an optional header.
31045 Changes in version 0.0.9pre1 - 2004-10-01
31047 - Stop using separate defaults for no-config-file and
31048 empty-config-file. Now you have to explicitly turn off SocksPort,
31049 if you don't want it open.
31050 - Fix a bug in OutboundBindAddress so it (hopefully) works.
31051 - Improve man page to mention more of the 0.0.8 features.
31052 - Fix a rare seg fault for people running hidden services on
31053 intermittent connections.
31054 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
31056 - Fix more dns related bugs: send back resolve_failed and end cells
31057 more reliably when the resolve fails, rather than closing the
31058 circuit and then trying to send the cell. Also attach dummy resolve
31059 connections to a circuit *before* calling dns_resolve(), to fix
31060 a bug where cached answers would never be sent in RESOLVED cells.
31061 - When we run out of disk space, or other log writing error, don't
31062 crash. Just stop logging to that log and continue.
31063 - We were starting to daemonize before we opened our logs, so if
31064 there were any problems opening logs, we would complain to stderr,
31065 which wouldn't work, and then mysteriously exit.
31066 - Fix a rare bug where sometimes a verified OR would connect to us
31067 before he'd uploaded his descriptor, which would cause us to
31068 assign conn->nickname as though he's unverified. Now we look through
31069 the fingerprint list to see if he's there.
31070 - Fix a rare assert trigger, where routerinfos for entries in
31071 our cpath would expire while we're building the path.
31074 - Clients can ask dirservers for /dir.z to get a compressed version
31075 of the directory. Only works for servers running 0.0.9, of course.
31076 - Make clients cache directories and use them to seed their router
31077 lists at startup. This means clients have a datadir again.
31078 - Configuration infrastructure support for warning on obsolete
31080 - Respond to content-encoding headers by trying to uncompress as
31082 - Reply with a deflated directory when a client asks for "dir.z".
31083 We could use allow-encodings instead, but allow-encodings isn't
31084 specified in HTTP 1.0.
31085 - Raise the max dns workers from 50 to 100.
31086 - Discourage people from setting their dirfetchpostperiod more often
31087 than once per minute.
31088 - Protect dirservers from overzealous descriptor uploading -- wait
31089 10 seconds after directory gets dirty, before regenerating.
31092 Changes in version 0.0.8 - 2004-08-25
31093 o Port it to SunOS 5.9 / Athena
31096 Changes in version 0.0.8rc2 - 2004-08-20
31097 o Make it compile on cygwin again.
31098 o When picking unverified routers, skip those with low uptime and/or
31099 low bandwidth, depending on what properties you care about.
31102 Changes in version 0.0.8rc1 - 2004-08-18
31103 o Changes from 0.0.7.3:
31105 - Fix assert triggers: if the other side returns an address 0.0.0.0,
31106 don't put it into the client dns cache.
31107 - If a begin failed due to exit policy, but we believe the IP address
31108 should have been allowed, switch that router to exitpolicy reject *:*
31109 until we get our next directory.
31111 - Clients choose nodes proportional to advertised bandwidth.
31112 - Avoid using nodes with low uptime as introduction points.
31113 - Handle servers with dynamic IP addresses: don't replace
31114 options->Address with the resolved one at startup, and
31115 detect our address right before we make a routerinfo each time.
31116 - 'FascistFirewall' option to pick dirservers and ORs on specific
31117 ports; plus 'FirewallPorts' config option to tell FascistFirewall
31118 which ports are open. (Defaults to 80,443)
31119 - Be more aggressive about trying to make circuits when the network
31120 has changed (e.g. when you unsuspend your laptop).
31121 - Check for time skew on http headers; report date in response to
31123 - If the entrynode config line has only one node, don't pick it as
31125 - Add strict{entry|exit}nodes config options. If set to 1, then
31126 we refuse to build circuits that don't include the specified entry
31128 - OutboundBindAddress config option, to bind to a specific
31129 IP address for outgoing connect()s.
31130 - End truncated log entries (e.g. directories) with "[truncated]".
31132 o Patches to 0.0.8preX:
31134 - Patches to compile and run on win32 again (maybe)?
31135 - Fix crash when looking for ~/.torrc with no $HOME set.
31136 - Fix a race bug in the unit tests.
31137 - Handle verified/unverified name collisions better when new
31138 routerinfo's arrive in a directory.
31139 - Sometimes routers were getting entered into the stats before
31140 we'd assigned their identity_digest. Oops.
31141 - Only pick and establish intro points after we've gotten a
31144 - AllowUnverifiedNodes config option to let circuits choose no-name
31145 routers in entry,middle,exit,introduction,rendezvous positions.
31146 Allow middle and rendezvous positions by default.
31147 - Add a man page for tor-resolve.
31150 Changes in version 0.0.7.3 - 2004-08-12
31151 o Stop dnsworkers from triggering an assert failure when you
31152 ask them to resolve the host "".
31155 Changes in version 0.0.8pre3 - 2004-08-09
31156 o Changes from 0.0.7.2:
31157 - Allow multiple ORs with same nickname in routerlist -- now when
31158 people give us one identity key for a nickname, then later
31159 another, we don't constantly complain until the first expires.
31160 - Remember used bandwidth (both in and out), and publish 15-minute
31161 snapshots for the past day into our descriptor.
31162 - You can now fetch $DIRURL/running-routers to get just the
31163 running-routers line, not the whole descriptor list. (But
31164 clients don't use this yet.)
31165 - When people mistakenly use Tor as an http proxy, point them
31166 at the tor-doc.html rather than the INSTALL.
31167 - Remove our mostly unused -- and broken -- hex_encode()
31168 function. Use base16_encode() instead. (Thanks to Timo Lindfors
31169 for pointing out this bug.)
31170 - Rotate onion keys every 12 hours, not every 2 hours, so we have
31171 fewer problems with people using the wrong key.
31172 - Change the default exit policy to reject the default edonkey,
31173 kazaa, gnutella ports.
31174 - Add replace_file() to util.[ch] to handle win32's rename().
31176 o Changes from 0.0.8preX:
31177 - Fix two bugs in saving onion keys to disk when rotating, so
31178 hopefully we'll get fewer people using old onion keys.
31179 - Fix an assert error that was making SocksPolicy not work.
31180 - Be willing to expire routers that have an open dirport -- it's
31181 just the authoritative dirservers we want to not forget.
31182 - Reject tor-resolve requests for .onion addresses early, so we
31183 don't build a whole rendezvous circuit and then fail.
31184 - When you're warning a server that he's unverified, don't cry
31185 wolf unpredictably.
31186 - Fix a race condition: don't try to extend onto a connection
31187 that's still handshaking.
31188 - For servers in clique mode, require the conn to be open before
31189 you'll choose it for your path.
31190 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
31191 end relay cell, etc.
31192 - Measure bandwidth capacity over the last 24 hours, not just 12
31193 - Bugfix: authoritative dirservers were making and signing a new
31194 directory for each client, rather than reusing the cached one.
31197 Changes in version 0.0.8pre2 - 2004-08-04
31198 o Changes from 0.0.7.2:
31200 - Check directory signature _before_ you decide whether you're
31201 you're running an obsolete version and should exit.
31202 - Check directory signature _before_ you parse the running-routers
31203 list to decide who's running or verified.
31204 - Bugfixes and features:
31205 - Check return value of fclose while writing to disk, so we don't
31206 end up with broken files when servers run out of disk space.
31207 - Log a warning if the user uses an unsafe socks variant, so people
31208 are more likely to learn about privoxy or socat.
31209 - Dirservers now include RFC1123-style dates in the HTTP headers,
31210 which one day we will use to better detect clock skew.
31212 o Changes from 0.0.8pre1:
31213 - Make it compile without warnings again on win32.
31214 - Log a warning if you're running an unverified server, to let you
31215 know you might want to get it verified.
31216 - Only pick a default nickname if you plan to be a server.
31219 Changes in version 0.0.8pre1 - 2004-07-23
31221 - Made our unit tests compile again on OpenBSD 3.5, and tor
31222 itself compile again on OpenBSD on a sparc64.
31223 - We were neglecting milliseconds when logging on win32, so
31224 everything appeared to happen at the beginning of each second.
31226 o Protocol changes:
31227 - 'Extend' relay cell payloads now include the digest of the
31228 intended next hop's identity key. Now we can verify that we're
31229 extending to the right router, and also extend to routers we
31230 hadn't heard of before.
31233 - Tor nodes can now act as relays (with an advertised ORPort)
31234 without being manually verified by the dirserver operators.
31235 - Uploaded descriptors of unverified routers are now accepted
31236 by the dirservers, and included in the directory.
31237 - Verified routers are listed by nickname in the running-routers
31238 list; unverified routers are listed as "$<fingerprint>".
31239 - We now use hash-of-identity-key in most places rather than
31240 nickname or addr:port, for improved security/flexibility.
31241 - To avoid Sybil attacks, paths still use only verified servers.
31242 But now we have a chance to play around with hybrid approaches.
31243 - Nodes track bandwidth usage to estimate capacity (not used yet).
31244 - ClientOnly option for nodes that never want to become servers.
31245 - Directory caching.
31246 - "AuthoritativeDir 1" option for the official dirservers.
31247 - Now other nodes (clients and servers) will cache the latest
31248 directory they've pulled down.
31249 - They can enable their DirPort to serve it to others.
31250 - Clients will pull down a directory from any node with an open
31251 DirPort, and check the signature/timestamp correctly.
31252 - Authoritative dirservers now fetch directories from other
31253 authdirservers, to stay better synced.
31254 - Running-routers list tells who's down also, along with noting
31255 if they're verified (listed by nickname) or unverified (listed
31257 - Allow dirservers to serve running-router list separately.
31258 This isn't used yet.
31259 - ORs connect-on-demand to other ORs
31260 - If you get an extend cell to an OR you're not connected to,
31261 connect, handshake, and forward the create cell.
31262 - The authoritative dirservers stay connected to everybody,
31263 and everybody stays connected to 0.0.7 servers, but otherwise
31264 clients/servers expire unused connections after 5 minutes.
31265 - When servers get a sigint, they delay 30 seconds (refusing new
31266 connections) then exit. A second sigint causes immediate exit.
31267 - File and name management:
31268 - Look for .torrc if no CONFDIR "torrc" is found.
31269 - If no datadir is defined, then choose, make, and secure ~/.tor
31271 - If torrc not found, exitpolicy reject *:*.
31272 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
31273 - If no nickname is defined, derive default from hostname.
31274 - Rename secret key files, e.g. identity.key -> secret_id_key,
31275 to discourage people from mailing their identity key to tor-ops.
31276 - Refuse to build a circuit before the directory has arrived --
31277 it won't work anyway, since you won't know the right onion keys
31279 - Try other dirservers immediately if the one you try is down. This
31280 should tolerate down dirservers better now.
31281 - Parse tor version numbers so we can do an is-newer-than check
31282 rather than an is-in-the-list check.
31283 - New socks command 'resolve', to let us shim gethostbyname()
31285 - A 'tor_resolve' script to access the socks resolve functionality.
31286 - A new socks-extensions.txt doc file to describe our
31287 interpretation and extensions to the socks protocols.
31288 - Add a ContactInfo option, which gets published in descriptor.
31289 - Publish OR uptime in descriptor (and thus in directory) too.
31290 - Write tor version at the top of each log file
31291 - New docs in the tarball:
31293 - Document that you should proxy your SSL traffic too.
31296 Changes in version 0.0.7.2 - 2004-07-07
31297 o A better fix for the 0.0.0.0 problem, that will hopefully
31298 eliminate the remaining related assertion failures.
31301 Changes in version 0.0.7.1 - 2004-07-04
31302 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
31303 since internally we use 0.0.0.0 to signify "not yet resolved".
31306 Changes in version 0.0.7 - 2004-06-07
31307 o Updated the man page to reflect the new features.
31310 Changes in version 0.0.7rc2 - 2004-06-06
31311 o Changes from 0.0.7rc1:
31312 - Make it build on Win32 again.
31313 o Changes from 0.0.6.2:
31314 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
31318 Changes in version 0.0.7rc1 - 2004-06-02
31320 - On sighup, we were adding another log without removing the first
31321 one. So log messages would get duplicated n times for n sighups.
31322 - Several cases of using a connection after we'd freed it. The
31323 problem was that connections that are pending resolve are in both
31324 the pending_resolve tree, and also the circuit's resolving_streams
31325 list. When you want to remove one, you must remove it from both.
31326 - Fix a double-mark-for-close where an end cell arrived for a
31327 resolving stream, and then the resolve failed.
31328 - Check directory signatures based on name of signer, not on whom
31329 we got the directory from. This will let us cache directories more
31332 - Crank up some of our constants to handle more users.
31335 Changes in version 0.0.7pre1 - 2004-06-02
31336 o Fixes for crashes and other obnoxious bugs:
31337 - Fix an epipe bug: sometimes when directory connections failed
31338 to connect, we would give them a chance to flush before closing
31340 - When we detached from a circuit because of resolvefailed, we
31341 would immediately try the same circuit twice more, and then
31342 give up on the resolve thinking we'd tried three different
31344 - Limit the number of intro circuits we'll attempt to build for a
31345 hidden service per 15-minute period.
31346 - Check recommended-software string *early*, before actually parsing
31347 the directory. Thus we can detect an obsolete version and exit,
31348 even if the new directory format doesn't parse.
31349 o Fixes for security bugs:
31350 - Remember which nodes are dirservers when you startup, and if a
31351 random OR enables his dirport, don't automatically assume he's
31352 a trusted dirserver.
31354 - Directory connections were asking the wrong poll socket to
31355 start writing, and not asking themselves to start writing.
31356 - When we detached from a circuit because we sent a begin but
31357 didn't get a connected, we would use it again the first time;
31358 but after that we would correctly switch to a different one.
31359 - Stop warning when the first onion decrypt attempt fails; they
31360 will sometimes legitimately fail now that we rotate keys.
31361 - Override unaligned-access-ok check when $host_cpu is ia64 or
31362 arm. Apparently they allow it but the kernel whines.
31363 - Dirservers try to reconnect periodically too, in case connections
31365 - Fix some memory leaks in directory servers.
31366 - Allow backslash in Win32 filenames.
31367 - Made Tor build complain-free on FreeBSD, hopefully without
31368 breaking other BSD builds. We'll see.
31370 - Doxygen markup on all functions and global variables.
31371 - Make directory functions update routerlist, not replace it. So
31372 now directory disagreements are not so critical a problem.
31373 - Remove the upper limit on number of descriptors in a dirserver's
31374 directory (not that we were anywhere close).
31375 - Allow multiple logfiles at different severity ranges.
31376 - Allow *BindAddress to specify ":port" rather than setting *Port
31377 separately. Allow multiple instances of each BindAddress config
31378 option, so you can bind to multiple interfaces if you want.
31379 - Allow multiple exit policy lines, which are processed in order.
31380 Now we don't need that huge line with all the commas in it.
31381 - Enable accept/reject policies on SOCKS connections, so you can bind
31382 to 0.0.0.0 but still control who can use your OP.
31385 Changes in version 0.0.6.2 - 2004-05-16
31386 o Our integrity-checking digest was checking only the most recent cell,
31387 not the previous cells like we'd thought.
31388 Thanks to Stefan Mark for finding the flaw!
31391 Changes in version 0.0.6.1 - 2004-05-06
31392 o Fix two bugs in our AES counter-mode implementation (this affected
31393 onion-level stream encryption, but not TLS-level). It turns
31394 out we were doing something much more akin to a 16-character
31395 polyalphabetic cipher. Oops.
31396 Thanks to Stefan Mark for finding the flaw!
31397 o Retire moria3 as a directory server, and add tor26 as a directory
31401 Changes in version 0.0.6 - 2004-05-02
31402 [version bump only]
31405 Changes in version 0.0.6rc4 - 2004-05-01
31406 o Update the built-in dirservers list to use the new directory format
31407 o Fix a rare seg fault: if a node offering a hidden service attempts
31408 to build a circuit to Alice's rendezvous point and fails before it
31409 reaches the last hop, it retries with a different circuit, but
31411 o Handle windows socket errors correctly.
31414 Changes in version 0.0.6rc3 - 2004-04-28
31415 o Don't expire non-general excess circuits (if we had enough
31416 circuits open, we were expiring rendezvous circuits -- even
31417 when they had a stream attached. oops.)
31418 o Fetch randomness from /dev/urandom better (not via fopen/fread)
31419 o Better debugging for tls errors
31420 o Some versions of openssl have an SSL_pending function that erroneously
31421 returns bytes when there is a non-application record pending.
31422 o Set Content-Type on the directory and hidserv descriptor.
31423 o Remove IVs from cipher code, since AES-ctr has none.
31424 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
31425 o We were using an array of length zero in a few places.
31426 o win32's gethostbyname can't resolve an IP to an IP.
31427 o win32's close can't close a socket.
31430 Changes in version 0.0.6rc2 - 2004-04-26
31431 o Fix a bug where we were closing tls connections intermittently.
31432 It turns out openssl keeps its errors around -- so if an error
31433 happens, and you don't ask about it, and then another openssl
31434 operation happens and succeeds, and you ask if there was an error,
31435 it tells you about the first error. Fun fun.
31436 o Fix a bug that's been lurking since 27 may 03 (!)
31437 When passing back a destroy cell, we would use the wrong circ id.
31438 'Mostly harmless', but still worth fixing.
31439 o Since we don't support truncateds much, don't bother sending them;
31440 just close the circ.
31441 o check for <machine/limits.h> so we build on NetBSD again (I hope).
31442 o don't crash if a conn that sent a begin has suddenly lost its circuit
31443 (this was quite rare).
31446 Changes in version 0.0.6rc1 - 2004-04-25
31447 o We now rotate link (tls context) keys and onion keys.
31448 o CREATE cells now include oaep padding, so you can tell
31449 if you decrypted them correctly.
31450 o Add bandwidthburst to server descriptor.
31451 o Directories now say which dirserver signed them.
31452 o Use a tor_assert macro that logs failed assertions too.
31455 Changes in version 0.0.6pre5 - 2004-04-18
31456 o changes from 0.0.6pre4:
31457 - make tor build on broken freebsd 5.2 installs
31458 - fix a failed assert when you try an intro point, get a nack, and try
31459 a second one and it works.
31460 - when alice uses a port that the hidden service doesn't accept,
31461 it now sends back an end cell (denied by exit policy). otherwise
31462 alice would just have to wait to time out.
31463 - fix another rare bug: when we had tried all the intro
31464 points for a hidden service, we fetched the descriptor
31465 again, but we left our introcirc thinking it had already
31466 sent an intro, so it kept waiting for a response...
31467 - bugfix: when you sleep your hidden-service laptop, as soon
31468 as it wakes up it tries to upload a service descriptor, but
31469 socketpair fails for some reason (localhost not up yet?).
31470 now we simply give up on that upload, and we'll try again later.
31471 i'd still like to find the bug though.
31472 - if an intro circ waiting for an ack dies before getting one, then
31474 - we were reusing stale service descriptors and refetching usable
31478 Changes in version 0.0.6pre4 - 2004-04-14
31479 o changes from 0.0.6pre3:
31480 - when bob fails to connect to the rendezvous point, and his
31481 circ didn't fail because of the rendezvous point itself, then
31482 he retries a couple of times
31483 - we expire introduction and rendezvous circs more thoroughly
31484 (sometimes they were hanging around forever)
31485 - we expire unattached rendezvous streams that have been around
31486 too long (they were sticking around forever).
31487 - fix a measly fencepost error that was crashing everybody with
31491 Changes in version 0.0.6pre3 - 2004-04-14
31492 o changes from 0.0.6pre2:
31493 - make hup work again
31494 - fix some memory leaks for dirservers
31495 - allow more skew in rendezvous descriptor timestamps, to help
31496 handle people like blanu who don't know what time it is
31497 - normal circs are 3 hops, but some rend/intro circs are 4, if
31498 the initiator doesn't get to choose the last hop
31499 - send acks for introductions, so alice can know whether to try
31501 - bob publishes intro points more correctly
31502 o changes from 0.0.5:
31503 - fix an assert trigger that's been plaguing us since the days
31504 of 0.0.2prexx (thanks weasel!)
31505 - retry stream correctly when we fail to connect because of
31506 exit-policy-reject (should try another) or can't-resolve-address
31507 (also should try another, because dns on random internet servers
31509 - when we hup a dirserver and we've *removed* a server from the
31510 approved-routers list, now we remove that server from the
31511 in-memory directories too
31514 Changes in version 0.0.6pre2 - 2004-04-08
31515 o We fixed our base32 implementation. Now it works on all architectures.
31518 Changes in version 0.0.6pre1 - 2004-04-08
31520 - Hidden services and rendezvous points are implemented. Go to
31521 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
31522 hidden services. (This only works via a socks4a proxy such as
31523 Privoxy, and currently it's quite slow.)
31526 Changes in version 0.0.5 - 2004-03-30
31527 [version bump only]
31530 Changes in version 0.0.5rc3 - 2004-03-29
31531 o Install torrc as torrc.sample -- we no longer clobber your
31533 o Re-enable recommendedversion checking (we broke it in rc2, oops)
31534 o Add in a 'notice' log level for things the operator should hear
31535 but that aren't warnings
31538 Changes in version 0.0.5rc2 - 2004-03-29
31539 o Hold socks connection open until reply is flushed (if possible)
31540 o Make exit nodes resolve IPs to IPs immediately, rather than asking
31541 the dns farm to do it.
31542 o Fix c99 aliasing warnings in rephist.c
31543 o Don't include server descriptors that are older than 24 hours in the
31545 o Give socks 'reject' replies their whole 15s to attempt to flush,
31546 rather than seeing the 60s timeout and assuming the flush had failed.
31547 o Clean automake droppings from the cvs repository
31550 Changes in version 0.0.5rc1 - 2004-03-28
31551 o Fix mangled-state bug in directory fetching (was causing sigpipes).
31552 o Only build circuits after we've fetched the directory: clients were
31553 using only the directory servers before they'd fetched a directory.
31554 This also means longer startup time; so it goes.
31555 o Fix an assert trigger where an OP would fail to handshake, and we'd
31556 expect it to have a nickname.
31557 o Work around a tsocks bug: do a socks reject when AP connection dies
31558 early, else tsocks goes into an infinite loop.
31561 Changes in version 0.0.4 - 2004-03-26
31562 o When connecting to a dirserver or OR and the network is down,
31566 Changes in version 0.0.3 - 2004-03-26
31567 o Warn and fail if server chose a nickname with illegal characters
31568 o Port to Solaris and Sparc:
31569 - include missing header fcntl.h
31570 - have autoconf find -lsocket -lnsl automatically
31571 - deal with hardware word alignment
31572 - make uname() work (solaris has a different return convention)
31573 - switch from using signal() to sigaction()
31574 o Preliminary work on reputation system:
31575 - Keep statistics on success/fail of connect attempts; they're published
31576 by kill -USR1 currently.
31577 - Add a RunTesting option to try to learn link state by creating test
31578 circuits, even when SocksPort is off.
31579 - Remove unused open circuits when there are too many.
31582 Changes in version 0.0.2 - 2004-03-19
31583 - Include strlcpy and strlcat for safer string ops
31584 - define INADDR_NONE so we compile (but still not run) on solaris
31587 Changes in version 0.0.2pre27 - 2004-03-14
31589 - Allow internal tor networks (we were rejecting internal IPs,
31590 now we allow them if they're set explicitly).
31591 - And fix a few endian issues.
31594 Changes in version 0.0.2pre26 - 2004-03-14
31596 - If a stream times out after 15s without a connected cell, don't
31597 try that circuit again: try a new one.
31598 - Retry streams at most 4 times. Then give up.
31599 - When a dirserver gets a descriptor from an unknown router, it
31600 logs its fingerprint (so the dirserver operator can choose to
31601 accept it even without mail from the server operator).
31602 - Inform unapproved servers when we reject their descriptors.
31603 - Make tor build on Windows again. It works as a client, who knows
31605 - Clearer instructions in the torrc for how to set up a server.
31606 - Be more efficient about reading fd's when our global token bucket
31607 (used for rate limiting) becomes empty.
31609 - Stop asserting that computers always go forward in time. It's
31611 - When we sent a cell (e.g. destroy) and then marked an OR connection
31612 expired, we might close it before finishing a flush if the other
31613 side isn't reading right then.
31614 - Don't allow dirservers to start if they haven't defined
31615 RecommendedVersions
31616 - We were caching transient dns failures. Oops.
31617 - Prevent servers from publishing an internal IP as their address.
31618 - Address a strcat vulnerability in circuit.c
31621 Changes in version 0.0.2pre25 - 2004-03-04
31623 - Put the OR's IP in its router descriptor, not its fqdn. That way
31624 we'll stop being stalled by gethostbyname for nodes with flaky dns,
31627 - If the user typed in an address that didn't resolve, the server
31631 Changes in version 0.0.2pre24 - 2004-03-03
31633 - Fix an assertion failure in dns.c, where we were trying to dequeue
31634 a pending dns resolve even if it wasn't pending
31635 - Fix a spurious socks5 warning about still trying to write after the
31636 connection is finished.
31637 - Hold certain marked_for_close connections open until they're finished
31638 flushing, rather than losing bytes by closing them too early.
31639 - Correctly report the reason for ending a stream
31640 - Remove some duplicate calls to connection_mark_for_close
31641 - Put switch_id and start_daemon earlier in the boot sequence, so it
31642 will actually try to chdir() to options.DataDirectory
31643 - Make 'make test' exit(1) if a test fails; fix some unit tests
31644 - Make tor fail when you use a config option it doesn't know about,
31645 rather than warn and continue.
31646 - Make --version work
31647 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
31650 Changes in version 0.0.2pre23 - 2004-02-29
31652 - Print a statement when the first circ is finished, so the user
31653 knows it's working.
31654 - If a relay cell is unrecognized at the end of the circuit,
31655 send back a destroy. (So attacks to mutate cells are more
31657 - New config option 'excludenodes' to avoid certain nodes for circuits.
31658 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
31659 so you can collect coredumps there.
31661 - Fix a bug in tls flushing where sometimes data got wedged and
31662 didn't flush until more data got sent. Hopefully this bug was
31663 a big factor in the random delays we were seeing.
31664 - Make 'connected' cells include the resolved IP, so the client
31665 dns cache actually gets populated.
31666 - Disallow changing from ORPort=0 to ORPort>0 on hup.
31667 - When we time-out on a stream and detach from the circuit, send an
31668 end cell down it first.
31669 - Only warn about an unknown router (in exitnodes, entrynodes,
31670 excludenodes) after we've fetched a directory.
31673 Changes in version 0.0.2pre22 - 2004-02-26
31675 - Servers publish less revealing uname information in descriptors.
31676 - More memory tracking and assertions, to crash more usefully when
31678 - If the default torrc isn't there, just use some default defaults.
31679 Plus provide an internal dirservers file if they don't have one.
31680 - When the user tries to use Tor as an http proxy, give them an http
31681 501 failure explaining that we're a socks proxy.
31682 - Dump a new router.desc on hup, to help confused people who change
31683 their exit policies and then wonder why router.desc doesn't reflect
31685 - Clean up the generic tor.sh init script that we ship with.
31687 - If the exit stream is pending on the resolve, and a destroy arrives,
31688 then the stream wasn't getting removed from the pending list. I
31689 think this was the one causing recent server crashes.
31690 - Use a more robust poll on OSX 10.3, since their poll is flaky.
31691 - When it couldn't resolve any dirservers, it was useless from then on.
31692 Now it reloads the RouterFile (or default dirservers) if it has no
31694 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
31695 many users don't even *have* a /usr/local/sbin/.
31698 Changes in version 0.0.2pre21 - 2004-02-18
31700 - There's a ChangeLog file that actually reflects the changelog.
31701 - There's a 'torify' wrapper script, with an accompanying
31702 tor-tsocks.conf, that simplifies the process of using tsocks for
31703 tor. It even has a man page.
31704 - The tor binary gets installed to sbin rather than bin now.
31705 - Retry streams where the connected cell hasn't arrived in 15 seconds
31706 - Clean up exit policy handling -- get the default out of the torrc,
31707 so we can update it without forcing each server operator to fix
31709 - Allow imaps and pop3s in default exit policy
31711 - Prevent picking middleman nodes as the last node in the circuit
31714 Changes in version 0.0.2pre20 - 2004-01-30
31716 - We now have a deb package, and it's in debian unstable. Go to
31717 it, apt-getters. :)
31718 - I've split the TotalBandwidth option into BandwidthRate (how many
31719 bytes per second you want to allow, long-term) and
31720 BandwidthBurst (how many bytes you will allow at once before the cap
31721 kicks in). This better token bucket approach lets you, say, set
31722 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
31723 performance while not exceeding your monthly bandwidth quota.
31724 - Push out a tls record's worth of data once you've got it, rather
31725 than waiting until you've read everything waiting to be read. This
31726 may improve performance by pipelining better. We'll see.
31727 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
31728 from failed circuits (if they haven't been connected yet) and attach
31730 - Expire old streams that haven't managed to connect. Some day we'll
31731 have them reattach to new circuits instead.
31734 - Fix several memory leaks that were causing servers to become bloated
31736 - Fix a few very rare assert triggers. A few more remain.
31737 - Setuid to User _before_ complaining about running as root.
31740 Changes in version 0.0.2pre19 - 2004-01-07
31742 - Fix deadlock condition in dns farm. We were telling a child to die by
31743 closing the parent's file descriptor to him. But newer children were
31744 inheriting the open file descriptor from the parent, and since they
31745 weren't closing it, the socket never closed, so the child never read
31746 eof, so he never knew to exit. Similarly, dns workers were holding
31747 open other sockets, leading to all sorts of chaos.
31748 - New cleaner daemon() code for forking and backgrounding.
31749 - If you log to a file, it now prints an entry at the top of the
31750 logfile so you know it's working.
31751 - The onionskin challenge length was 30 bytes longer than necessary.
31752 - Started to patch up the spec so it's not quite so out of date.
31755 Changes in version 0.0.2pre18 - 2004-01-02
31757 - Fix endian issues with the 'integrity' field in the relay header.
31758 - Fix a potential bug where connections in state
31759 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
31762 Changes in version 0.0.2pre17 - 2003-12-30
31764 - Made --debuglogfile (or any second log file, actually) work.
31765 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
31766 adversary could force us into an infinite loop.
31769 - Each onionskin handshake now includes a hash of the computed key,
31770 to prove the server's identity and help perfect forward secrecy.
31771 - Changed cell size from 256 to 512 bytes (working toward compatibility
31773 - Changed cell length to 2 bytes, and moved it to the relay header.
31774 - Implemented end-to-end integrity checking for the payloads of
31776 - Separated streamid from 'recognized' (otherwise circuits will get
31777 messed up when we try to have streams exit from the middle). We
31778 use the integrity-checking to confirm that a cell is addressed to
31780 - Randomize the initial circid and streamid values, so an adversary who
31781 breaks into a node can't learn how many circuits or streams have
31785 Changes in version 0.0.2pre16 - 2003-12-14
31787 - Fixed a bug that made HUP trigger an assert
31788 - Fixed a bug where a circuit that immediately failed wasn't being
31789 counted as a failed circuit in counting retries.
31792 - Now we close the circuit when we get a truncated cell: otherwise we're
31793 open to an anonymity attack where a bad node in the path truncates
31794 the circuit and then we open streams at him.
31795 - Add port ranges to exit policies
31796 - Add a conservative default exit policy
31797 - Warn if you're running tor as root
31798 - on HUP, retry OR connections and close/rebind listeners
31799 - options.EntryNodes: try these nodes first when picking the first node
31800 - options.ExitNodes: if your best choices happen to include any of
31801 your preferred exit nodes, you choose among just those preferred
31803 - options.ExcludedNodes: nodes that are never picked in path building
31806 Changes in version 0.0.2pre15 - 2003-12-03
31807 o Robustness and bugfixes:
31808 - Sometimes clients would cache incorrect DNS resolves, which would
31809 really screw things up.
31810 - An OP that goes offline would slowly leak all its sockets and stop
31812 - A wide variety of bugfixes in exit node selection, exit policy
31813 handling, and processing pending streams when a new circuit is
31815 - Pick nodes for a path only from those the directory says are up
31816 - Choose randomly from all running dirservers, not always the first one
31817 - Increase allowed http header size for directory fetch.
31818 - Stop writing to stderr (if we're daemonized it will be closed).
31819 - Enable -g always, so cores will be more useful to me.
31820 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
31823 - Wrote a man page. It lists commonly used options.
31826 - Change default loglevel to warn.
31827 - Make PidFile default to null rather than littering in your CWD.
31828 - OnionRouter config option is now obsolete. Instead it just checks
31830 - Moved to a single unified torrc file for both clients and servers.
31833 Changes in version 0.0.2pre14 - 2003-11-29
31834 o Robustness and bugfixes:
31835 - Force the admin to make the DataDirectory himself
31836 - to get ownership/permissions right
31837 - so clients no longer make a DataDirectory and then never use it
31838 - fix bug where a client who was offline for 45 minutes would never
31839 pull down a directory again
31840 - fix (or at least hide really well) the dns assert bug that was
31841 causing server crashes
31842 - warnings and improved robustness wrt clockskew for certs
31843 - use the native daemon(3) to daemonize, when available
31844 - exit if bind() fails
31845 - exit if neither socksport nor orport is defined
31846 - include our own tor_timegm (Win32 doesn't have its own)
31847 - bugfix for win32 with lots of connections
31848 - fix minor bias in PRNG
31849 - make dirserver more robust to corrupt cached directory
31852 - Wrote the design document (woo)
31854 o Circuit building and exit policies:
31855 - Circuits no longer try to use nodes that the directory has told them
31857 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
31858 bitcounts (18.0.0.0/8).
31859 - Make AP connections standby for a circuit if no suitable circuit
31860 exists, rather than failing
31861 - Circuits choose exit node based on addr/port, exit policies, and
31862 which AP connections are standing by
31863 - Bump min pathlen from 2 to 3
31864 - Relay end cells have a payload to describe why the stream ended.
31865 - If the stream failed because of exit policy, try again with a new
31867 - Clients have a dns cache to remember resolved addresses.
31868 - Notice more quickly when we have no working circuits
31871 - APPort is now called SocksPort
31872 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
31874 - RecommendedVersions is now a config variable rather than
31875 hardcoded (for dirservers)
31876 - Reloads config on HUP
31877 - Usage info on -h or --help
31878 - If you set User and Group config vars, it'll setu/gid to them.
31881 Changes in version 0.0.2pre13 - 2003-10-19
31882 o General stability:
31883 - SSL_write no longer fails when it returns WANTWRITE and the number
31884 of bytes in the buf has changed by the next SSL_write call.
31885 - Fix segfault fetching directory when network is down
31886 - Fix a variety of minor memory leaks
31887 - Dirservers reload the fingerprints file on HUP, so I don't have
31888 to take down the network when I approve a new router
31889 - Default server config file has explicit Address line to specify fqdn
31892 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
31893 - Make listener connections not ever alloc bufs
31895 o Autoconf improvements:
31896 - don't clobber an external CFLAGS in ./configure
31897 - Make install now works
31898 - create var/lib/tor on make install
31899 - autocreate a tor.sh initscript to help distribs
31900 - autocreate the torrc and sample-server-torrc with correct paths
31902 o Log files and Daemonizing now work:
31903 - If --DebugLogFile is specified, log to it at -l debug
31904 - If --LogFile is specified, use it instead of commandline
31905 - If --RunAsDaemon is set, tor forks and backgrounds on startup