1 This document summarizes new features and bugfixes in each stable release
2 of Tor. If you want to see more detailed descriptions of the changes in
3 each development snapshot, see the ChangeLog file.
5 Changes in version 0.3.2.9 - 2018-01-09
6 Tor 0.3.2.9 is the first stable release in the 0.3.2 series.
8 The 0.3.2 series includes our long-anticipated new onion service
9 design, with numerous security features. (For more information, see
10 our blog post at https://blog.torproject.org/fall-harvest.) We also
11 have a new circuit scheduler algorithm for improved performance on
12 relays everywhere (see https://blog.torproject.org/kist-and-tell),
13 along with many smaller features and bugfixes.
15 Per our stable release policy, we plan to support each stable release
16 series for at least the next nine months, or for three months after
17 the first stable release of the next series: whichever is longer. If
18 you need a release with long-term support, we recommend that you stay
19 with the 0.2.9 series.
21 Below is a list of the changes since 0.3.1.7. For a list of all
22 changes since 0.3.2.8-rc, see the ChangeLog file.
24 o Directory authority changes:
25 - Add "Bastet" as a ninth directory authority to the default list.
27 - The directory authority "Longclaw" has changed its IP address.
29 - Remove longclaw's IPv6 address, as it will soon change. Authority
30 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
31 3/8 directory authorities with IPv6 addresses, but there are also
32 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
33 - Add an IPv6 address for the "bastet" directory authority. Closes
36 o Major features (next-generation onion services):
37 - Tor now supports the next-generation onion services protocol for
38 clients and services! As part of this release, the core of
39 proposal 224 has been implemented and is available for
40 experimentation and testing by our users. This newer version of
41 onion services ("v3") features many improvements over the legacy
44 a) Better crypto (replaced SHA1/DH/RSA1024
45 with SHA3/ed25519/curve25519)
47 b) Improved directory protocol, leaking much less information to
50 c) Improved directory protocol, with smaller surface for
53 d) Better onion address security against impersonation.
55 e) More extensible introduction/rendezvous protocol.
57 f) A cleaner and more modular codebase.
59 You can identify a next-generation onion address by its length:
60 they are 56 characters long, as in
61 "4acth47i6kxnvkewtm6q7ib2s3ufpo5sqbsnzjpbi7utijcltosqemad.onion".
63 In the future, we will release more options and features for v3
64 onion services, but we first need a testing period, so that the
65 current codebase matures and becomes more robust. Planned features
66 include: offline keys, advanced client authorization, improved
67 guard algorithms, and statistics. For full details, see
70 Legacy ("v2") onion services will still work for the foreseeable
71 future, and will remain the default until this new codebase gets
72 tested and hardened. Service operators who want to experiment with
73 the new system can use the 'HiddenServiceVersion 3' torrc
74 directive along with the regular onion service configuration
75 options. For more information, see our blog post at
76 "https://blog.torproject.org/fall-harvest". Enjoy!
78 o Major feature (scheduler, channel):
79 - Tor now uses new schedulers to decide which circuits should
80 deliver cells first, in order to improve congestion at relays. The
81 first type is called "KIST" ("Kernel Informed Socket Transport"),
82 and is only available on Linux-like systems: it uses feedback from
83 the kernel to prevent the kernel's TCP buffers from growing too
84 full. The second new scheduler type is called "KISTLite": it
85 behaves the same as KIST, but runs on systems without kernel
86 support for inspecting TCP implementation details. The old
87 scheduler is still available, under the name "Vanilla". To change
88 the default scheduler preference order, use the new "Schedulers"
89 option. (The default preference order is "KIST,KISTLite,Vanilla".)
91 Matt Traudt implemented KIST, based on research by Rob Jansen,
92 John Geddes, Christ Wacek, Micah Sherr, and Paul Syverson. For
93 more information, see the design paper at
94 http://www.robgjansen.com/publications/kist-sec2014.pdf and the
95 followup implementation paper at https://arxiv.org/abs/1709.01044.
96 Closes ticket 12541. For more information, see our blog post at
97 "https://blog.torproject.org/kist-and-tell".
99 o Major bugfixes (security, general):
100 - Fix a denial of service bug where an attacker could use a
101 malformed directory object to cause a Tor instance to pause while
102 OpenSSL would try to read a passphrase from the terminal. (Tor
103 instances run without a terminal, which is the case for most Tor
104 packages, are not impacted.) Fixes bug 24246; bugfix on every
105 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
106 Found by OSS-Fuzz as testcase 6360145429790720.
108 o Major bugfixes (security, directory authority):
109 - Fix a denial of service issue where an attacker could crash a
110 directory authority using a malformed router descriptor. Fixes bug
111 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
114 o Major bugfixes (security, onion service v2):
115 - Fix a use-after-free error that could crash v2 Tor onion services
116 when they failed to open circuits while expiring introduction
117 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
118 also tracked as TROVE-2017-013 and CVE-2017-8823.
119 - When checking for replays in the INTRODUCE1 cell data for a
120 (legacy) onion service, correctly detect replays in the RSA-
121 encrypted part of the cell. We were previously checking for
122 replays on the entire cell, but those can be circumvented due to
123 the malleability of Tor's legacy hybrid encryption. This fix helps
124 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
125 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
128 o Major bugfixes (security, relay):
129 - When running as a relay, make sure that we never build a path
130 through ourselves, even in the case where we have somehow lost the
131 version of our descriptor appearing in the consensus. Fixes part
132 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
133 as TROVE-2017-012 and CVE-2017-8822.
134 - When running as a relay, make sure that we never choose ourselves
135 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
136 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
138 o Major bugfixes (bootstrapping):
139 - Fetch descriptors aggressively whenever we lack enough to build
140 circuits, regardless of how many descriptors we are missing.
141 Previously, we would delay launching the fetch when we had fewer
142 than 15 missing descriptors, even if some of those descriptors
143 were blocking circuits from building. Fixes bug 23985; bugfix on
144 0.1.1.11-alpha. The effects of this bug became worse in
145 0.3.0.3-alpha, when we began treating missing descriptors from our
146 primary guards as a reason to delay circuits.
147 - Don't try fetching microdescriptors from relays that have failed
148 to deliver them in the past. Fixes bug 23817; bugfix
151 o Major bugfixes (circuit prediction):
152 - Fix circuit prediction logic so that a client doesn't treat a port
153 as being "handled" by a circuit if that circuit already has
154 isolation settings on it. This change should make Tor clients more
155 responsive by improving their chances of having a pre-created
156 circuit ready for use when a request arrives. Fixes bug 18859;
157 bugfix on 0.2.3.3-alpha.
159 o Major bugfixes (exit relays, DNS):
160 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
161 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
162 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
163 identifying and finding a workaround to this bug and to Moritz,
164 Arthur Edelstein, and Roger for helping to track it down and
167 o Major bugfixes (relay, crash, assertion failure):
168 - Fix a timing-based assertion failure that could occur when the
169 circuit out-of-memory handler freed a connection's output buffer.
170 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
172 o Major bugfixes (usability, control port):
173 - Report trusted clock skew indications as bootstrap errors, so
174 controllers can more easily alert users when their clocks are
175 wrong. Fixes bug 23506; bugfix on 0.1.2.6-alpha.
177 o Minor features (bridge):
178 - Bridge relays can now set the BridgeDistribution config option to
179 add a "bridge-distribution-request" line to their bridge
180 descriptor, which tells BridgeDB how they'd like their bridge
181 address to be given out. (Note that as of Oct 2017, BridgeDB does
182 not yet implement this feature.) As a side benefit, this feature
183 provides a way to distinguish bridge descriptors from non-bridge
184 descriptors. Implements tickets 18329.
185 - When handling the USERADDR command on an ExtOrPort, warn when the
186 transports provides a USERADDR with no port. In a future version,
187 USERADDR commands of this format may be rejected. Detects problems
188 related to ticket 23080.
190 o Minor features (bug detection):
191 - Log a warning message with a stack trace for any attempt to call
192 get_options() during option validation. This pattern has caused
193 subtle bugs in the past. Closes ticket 22281.
195 o Minor features (build, compilation):
196 - The "check-changes" feature is now part of the "make check" tests;
197 we'll use it to try to prevent misformed changes files from
198 accumulating. Closes ticket 23564.
199 - Tor builds should now fail if there are any mismatches between the
200 C type representing a configuration variable and the C type the
201 data-driven parser uses to store a value there. Previously, we
202 needed to check these by hand, which sometimes led to mistakes.
205 o Minor features (client):
206 - You can now use Tor as a tunneled HTTP proxy: use the new
207 HTTPTunnelPort option to open a port that accepts HTTP CONNECT
208 requests. Closes ticket 22407.
209 - Add an extra check to make sure that we always use the newer guard
210 selection code for picking our guards. Closes ticket 22779.
211 - When downloading (micro)descriptors, don't split the list into
212 multiple requests unless we want at least 32 descriptors.
213 Previously, we split at 4, not 32, which led to significant
214 overhead in HTTP request size and degradation in compression
215 performance. Closes ticket 23220.
216 - Improve log messages when missing descriptors for primary guards.
217 Resolves ticket 23670.
219 o Minor features (command line):
220 - Add a new commandline option, --key-expiration, which prints when
221 the current signing key is going to expire. Implements ticket
222 17639; patch by Isis Lovecruft.
224 o Minor features (control port):
225 - If an application tries to use the control port as an HTTP proxy,
226 respond with a meaningful "This is the Tor control port" message,
227 and log the event. Closes ticket 1667. Patch from Ravi
229 - Provide better error message for GETINFO desc/(id|name) when not
230 fetching router descriptors. Closes ticket 5847. Patch by
232 - Add GETINFO "{desc,md}/download-enabled", to inform the controller
233 whether Tor will try to download router descriptors and
234 microdescriptors respectively. Closes ticket 22684.
235 - Added new GETINFO targets "ip-to-country/{ipv4,ipv6}-available",
236 so controllers can tell whether the geoip databases are loaded.
238 - Adds a timestamp field to the CIRC_BW and STREAM_BW bandwidth
239 events. Closes ticket 19254. Patch by "DonnchaC".
241 o Minor features (development support):
242 - Developers can now generate a call-graph for Tor using the
243 "calltool" python program, which post-processes object dumps. It
244 should work okay on many Linux and OSX platforms, and might work
245 elsewhere too. To run it, install calltool from
246 https://gitweb.torproject.org/user/nickm/calltool.git and run
247 "make callgraph". Closes ticket 19307.
249 o Minor features (directory authority):
250 - Make the "Exit" flag assignment only depend on whether the exit
251 policy allows connections to ports 80 and 443. Previously relays
252 would get the Exit flag if they allowed connections to one of
253 these ports and also port 6667. Resolves ticket 23637.
255 o Minor features (ed25519):
256 - Add validation function to checks for torsion components in
257 ed25519 public keys, used by prop224 client-side code. Closes
258 ticket 22006. Math help by Ian Goldberg.
260 o Minor features (exit relay, DNS):
261 - Improve the clarity and safety of the log message from evdns when
262 receiving an apparently spoofed DNS reply. Closes ticket 3056.
264 o Minor features (fallback directory mirrors):
265 - The fallback directory list has been re-generated based on the
266 current status of the network. Tor uses fallback directories to
267 bootstrap when it doesn't yet have up-to-date directory
268 information. Closes ticket 24801.
269 - Make the default DirAuthorityFallbackRate 0.1, so that clients
270 prefer to bootstrap from fallback directory mirrors. This is a
271 follow-up to 24679, which removed weights from the default
272 fallbacks. Implements ticket 24681.
274 o Minor features (geoip):
275 - Update geoip and geoip6 to the January 5 2018 Maxmind GeoLite2
278 o Minor features (integration, hardening):
279 - Add a new NoExec option to prevent Tor from running other
280 programs. When this option is set to 1, Tor will never try to run
281 another program, regardless of the settings of
282 PortForwardingHelper, ClientTransportPlugin, or
283 ServerTransportPlugin. Once NoExec is set, it cannot be disabled
284 without restarting Tor. Closes ticket 22976.
286 o Minor features (linux seccomp2 sandbox):
287 - Update the sandbox rules so that they should now work correctly
288 with Glibc 2.26. Closes ticket 24315.
290 o Minor features (logging):
291 - Provide better warnings when the getrandom() syscall fails. Closes
293 - Downgrade a pair of log messages that could occur when an exit's
294 resolver gave us an unusual (but not forbidden) response. Closes
296 - Improve the message we log when re-enabling circuit build timeouts
297 after having received a consensus. Closes ticket 20963.
298 - Log more circuit information whenever we are about to try to
299 package a relay cell on a circuit with a nonexistent n_chan.
300 Attempt to diagnose ticket 8185.
301 - Improve info-level log identification of particular circuits, to
302 help with debugging. Closes ticket 23645.
303 - Improve the warning message for specifying a relay by nickname.
304 The previous message implied that nickname registration was still
305 part of the Tor network design, which it isn't. Closes
307 - If the sandbox filter fails to load, suggest to the user that
308 their kernel might not support seccomp2. Closes ticket 23090.
310 o Minor features (onion service, circuit, logging):
311 - Improve logging of many callsite in the circuit subsystem to print
312 the circuit identifier(s).
313 - Log when we cleanup an intro point from a service so we know when
314 and for what reason it happened. Closes ticket 23604.
316 o Minor features (portability):
317 - Tor now compiles correctly on arm64 with libseccomp-dev installed.
318 (It doesn't yet work with the sandbox enabled.) Closes
320 - Check at configure time whether uint8_t is the same type as
321 unsigned char. Lots of existing code already makes this
322 assumption, and there could be strict aliasing issues if the
323 assumption is violated. Closes ticket 22410.
325 o Minor features (relay):
326 - When choosing which circuits can be expired as unused, consider
327 circuits from clients even if those clients used regular CREATE
328 cells to make them; and do not consider circuits from relays even
329 if they were made with CREATE_FAST. Part of ticket 22805.
330 - Reject attempts to use relative file paths when RunAsDaemon is
331 set. Previously, Tor would accept these, but the directory-
332 changing step of RunAsDaemon would give strange and/or confusing
333 results. Closes ticket 22731.
335 o Minor features (relay statistics):
336 - Change relay bandwidth reporting stats interval from 4 hours to 24
337 hours in order to reduce the efficiency of guard discovery
338 attacks. Fixes ticket 23856.
340 o Minor features (reverted deprecations):
341 - The ClientDNSRejectInternalAddresses flag can once again be set in
342 non-testing Tor networks, so long as they do not use the default
343 directory authorities. This change also removes the deprecation of
344 this flag from 0.2.9.2-alpha. Closes ticket 21031.
346 o Minor features (robustness):
347 - Change several fatal assertions when flushing buffers into non-
348 fatal assertions, to prevent any recurrence of 23690.
350 o Minor features (startup, safety):
351 - When configured to write a PID file, Tor now exits if it is unable
352 to do so. Previously, it would warn and continue. Closes
355 o Minor features (static analysis):
356 - The BUG() macro has been changed slightly so that Coverity no
357 longer complains about dead code if the bug is impossible. Closes
360 o Minor features (testing):
361 - Our fuzzing tests now test the encrypted portions of v3 onion
362 service descriptors. Implements more of 21509.
363 - Add a unit test to make sure that our own generated platform
364 string will be accepted by directory authorities. Closes
366 - The default chutney network tests now include tests for the v3
367 onion service design. Make sure you have the latest version of
368 chutney if you want to run these. Closes ticket 22437.
369 - Add a unit test to verify that we can parse a hardcoded v2 onion
370 service descriptor. Closes ticket 15554.
372 o Minor bugfixes (address selection):
373 - When the fascist_firewall_choose_address_ functions don't find a
374 reachable address, set the returned address to the null address
375 and port. This is a precautionary measure, because some callers do
376 not check the return value. Fixes bug 24736; bugfix
379 o Minor bugfixes (bootstrapping):
380 - When warning about state file clock skew, report the correct
381 direction for the detected skew. Fixes bug 23606; bugfix
384 o Minor bugfixes (bridge clients, bootstrap):
385 - Retry directory downloads when we get our first bridge descriptor
386 during bootstrap or while reconnecting to the network. Keep
387 retrying every time we get a bridge descriptor, until we have a
388 reachable bridge. Fixes part of bug 24367; bugfix on 0.2.0.3-alpha.
389 - Stop delaying bridge descriptor fetches when we have cached bridge
390 descriptors. Instead, only delay bridge descriptor fetches when we
391 have at least one reachable bridge. Fixes part of bug 24367;
392 bugfix on 0.2.0.3-alpha.
393 - Stop delaying directory fetches when we have cached bridge
394 descriptors. Instead, only delay bridge descriptor fetches when
395 all our bridges are definitely unreachable. Fixes part of bug
396 24367; bugfix on 0.2.0.3-alpha.
398 o Minor bugfixes (bridge):
399 - Overwrite the bridge address earlier in the process of retrieving
400 its descriptor, to make sure we reach it on the configured
401 address. Fixes bug 20532; bugfix on 0.2.0.10-alpha.
403 o Minor bugfixes (build, compilation):
404 - Fix a compilation warning when building with zstd support on
405 32-bit platforms. Fixes bug 23568; bugfix on 0.3.1.1-alpha. Found
406 and fixed by Andreas Stieger.
407 - When searching for OpenSSL, don't accept any OpenSSL library that
408 lacks TLSv1_1_method(): Tor doesn't build with those versions.
409 Additionally, look in /usr/local/opt/openssl, if it's present.
410 These changes together repair the default build on OSX systems
411 with Homebrew installed. Fixes bug 23602; bugfix on 0.2.7.2-alpha.
412 - Fix a signed/unsigned comparison warning introduced by our fix to
413 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
414 - Fix a memory leak warning in one of the libevent-related
415 configuration tests that could occur when manually specifying
416 -fsanitize=address. Fixes bug 24279; bugfix on 0.3.0.2-alpha.
417 Found and patched by Alex Xu.
418 - Fix unused-variable warnings in donna's Curve25519 SSE2 code.
419 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
421 o Minor bugfixes (certificate handling):
422 - Fix a time handling bug in Tor certificates set to expire after
423 the year 2106. Fixes bug 23055; bugfix on 0.3.0.1-alpha. Found by
424 Coverity as CID 1415728.
426 o Minor bugfixes (client):
427 - By default, do not enable storage of client-side DNS values. These
428 values were unused by default previously, but they should not have
429 been cached at all. Fixes bug 24050; bugfix on 0.2.6.3-alpha.
431 o Minor bugfixes (client, usability):
432 - Refrain from needlessly rejecting SOCKS5-with-hostnames and
433 SOCKS4a requests that contain IP address strings, even when
434 SafeSocks in enabled, as this prevents user from connecting to
435 known IP addresses without relying on DNS for resolving. SafeSocks
436 still rejects SOCKS connections that connect to IP addresses when
437 those addresses are _not_ encoded as hostnames. Fixes bug 22461;
438 bugfix on Tor 0.2.6.2-alpha.
440 o Minor bugfixes (code correctness):
441 - Call htons() in extend_cell_format() for encoding a 16-bit value.
442 Previously we used ntohs(), which happens to behave the same on
443 all the platforms we support, but which isn't really correct.
444 Fixes bug 23106; bugfix on 0.2.4.8-alpha.
445 - For defense-in-depth, make the controller's write_escaped_data()
446 function robust to extremely long inputs. Fixes bug 19281; bugfix
447 on 0.1.1.1-alpha. Reported by Guido Vranken.
448 - Fix several places in our codebase where a C compiler would be
449 likely to eliminate a check, based on assuming that undefined
450 behavior had not happened elsewhere in the code. These cases are
451 usually a sign of redundant checking or dubious arithmetic. Found
452 by Georg Koppen using the "STACK" tool from Wang, Zeldovich,
453 Kaashoek, and Solar-Lezama. Fixes bug 24423; bugfix on various
456 o Minor bugfixes (compression):
457 - Handle a pathological case when decompressing Zstandard data when
458 the output buffer size is zero. Fixes bug 23551; bugfix
461 o Minor bugfixes (consensus expiry):
462 - Check for adequate directory information correctly. Previously, Tor
463 would reconsider whether it had sufficient directory information
464 every 2 minutes. Fixes bug 23091; bugfix on 0.2.0.19-alpha.
466 o Minor bugfixes (control port, linux seccomp2 sandbox):
467 - Avoid a crash when attempting to use the seccomp2 sandbox together
468 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
471 o Minor bugfixes (control port, onion services):
472 - Report "FAILED" instead of "UPLOAD_FAILED" "FAILED" for the
473 HS_DESC event when a service is not able to upload a descriptor.
474 Fixes bug 24230; bugfix on 0.2.7.1-alpha.
476 o Minor bugfixes (directory cache):
477 - Recover better from empty or corrupt files in the consensus cache
478 directory. Fixes bug 24099; bugfix on 0.3.1.1-alpha.
479 - When a consensus diff calculation is only partially successful,
480 only record the successful parts as having succeeded. Partial
481 success can happen if (for example) one compression method fails
482 but the others succeed. Previously we misrecorded all the
483 calculations as having succeeded, which would later cause a
484 nonfatal assertion failure. Fixes bug 24086; bugfix
487 o Minor bugfixes (directory client):
488 - On failure to download directory information, delay retry attempts
489 by a random amount based on the "decorrelated jitter" algorithm.
490 Our previous delay algorithm tended to produce extra-long delays
491 too easily. Fixes bug 23816; bugfix on 0.2.9.1-alpha.
493 o Minor bugfixes (directory protocol):
494 - Directory servers now include a "Date:" http header for response
495 codes other than 200. Clients starting with a skewed clock and a
496 recent consensus were getting "304 Not modified" responses from
497 directory authorities, so without the Date header, the client
498 would never hear about a wrong clock. Fixes bug 23499; bugfix
500 - Make clients wait for 6 seconds before trying to download a
501 consensus from an authority. Fixes bug 17750; bugfix
504 o Minor bugfixes (documentation):
505 - Document better how to read gcov, and what our gcov postprocessing
506 scripts do. Fixes bug 23739; bugfix on 0.2.9.1-alpha.
507 - Fix manpage to not refer to the obsolete (and misspelled)
508 UseEntryGuardsAsDirectoryGuards parameter in the description of
509 NumDirectoryGuards. Fixes bug 23611; bugfix on 0.2.4.8-alpha.
511 o Minor bugfixes (DoS-resistance):
512 - If future code asks if there are any running bridges, without
513 checking if bridges are enabled, log a BUG warning rather than
514 crashing. Fixes bug 23524; bugfix on 0.3.0.1-alpha.
516 o Minor bugfixes (entry guards):
517 - Tor now updates its guard state when it reads a consensus
518 regardless of whether it's missing descriptors. That makes tor use
519 its primary guards to fetch descriptors in some edge cases where
520 it would previously have used fallback directories. Fixes bug
521 23862; bugfix on 0.3.0.1-alpha.
523 o Minor bugfixes (format strictness):
524 - Restrict several data formats to decimal. Previously, the
525 BuildTimeHistogram entries in the state file, the "bw=" entries in
526 the bandwidth authority file, and the process IDs passed to the
527 __OwningControllerProcess option could all be specified in hex or
528 octal as well as in decimal. This was not an intentional feature.
529 Fixes bug 22802; bugfixes on 0.2.2.1-alpha, 0.2.2.2-alpha,
532 o Minor bugfixes (heartbeat):
533 - If we fail to write a heartbeat message, schedule a retry for the
534 minimum heartbeat interval number of seconds in the future. Fixes
535 bug 19476; bugfix on 0.2.3.1-alpha.
537 o Minor bugfixes (logging):
538 - Suppress a log notice when relay descriptors arrive. We already
539 have a bootstrap progress for this so no need to log notice
540 everytime tor receives relay descriptors. Microdescriptors behave
541 the same. Fixes bug 23861; bugfix on 0.2.8.2-alpha.
542 - Remove duplicate log messages regarding opening non-local
543 SocksPorts upon parsing config and opening listeners at startup.
544 Fixes bug 4019; bugfix on 0.2.3.3-alpha.
545 - Use a more comprehensible log message when telling the user
546 they've excluded every running exit node. Fixes bug 7890; bugfix
548 - When logging the number of descriptors we intend to download per
549 directory request, do not log a number higher than then the number
550 of descriptors we're fetching in total. Fixes bug 19648; bugfix
552 - When warning about a directory owned by the wrong user, log the
553 actual name of the user owning the directory. Previously, we'd log
554 the name of the process owner twice. Fixes bug 23487; bugfix
556 - Fix some messages on unexpected errors from the seccomp2 library.
557 Fixes bug 22750; bugfix on 0.2.5.1-alpha. Patch from "cypherpunks".
558 - The tor specification says hop counts are 1-based, so fix two log
559 messages that mistakenly logged 0-based hop counts. Fixes bug
560 18982; bugfix on 0.2.6.2-alpha and 0.2.4.5-alpha. Patch by teor.
561 Credit to Xiaofan Li for reporting this issue.
563 o Minor bugfixes (logging, relay shutdown, annoyance):
564 - When a circuit is marked for close, do not attempt to package any
565 cells for channels on that circuit. Previously, we would detect
566 this condition lower in the call stack, when we noticed that the
567 circuit had no attached channel, and log an annoying message.
568 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
570 o Minor bugfixes (memory safety, defensive programming):
571 - Clear the target address when node_get_prim_orport() returns
572 early. Fixes bug 23874; bugfix on 0.2.8.2-alpha.
574 o Minor bugfixes (memory usage):
575 - When queuing DESTROY cells on a channel, only queue the circuit-id
576 and reason fields: not the entire 514-byte cell. This fix should
577 help mitigate any bugs or attacks that fill up these queues, and
578 free more RAM for other uses. Fixes bug 24666; bugfix
581 o Minor bugfixes (network layer):
582 - When closing a connection via close_connection_immediately(), we
583 mark it as "not blocked on bandwidth", to prevent later calls from
584 trying to unblock it, and give it permission to read. This fixes a
585 backtrace warning that can happen on relays under various
586 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
588 o Minor bugfixes (onion services):
589 - The introduction circuit was being timed out too quickly while
590 waiting for the rendezvous circuit to complete. Keep the intro
591 circuit around longer instead of timing out and reopening new ones
592 constantly. Fixes bug 23681; bugfix on 0.2.4.8-alpha.
593 - Rename the consensus parameter "hsdir-interval" to "hsdir_interval"
594 so it matches dir-spec.txt. Fixes bug 24262; bugfix
596 - When handling multiple SOCKS request for the same .onion address,
597 only fetch the service descriptor once.
598 - Avoid a possible double close of a circuit by the intro point on
599 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
600 bugfix on 0.3.0.1-alpha.
601 - When reloading configured onion services, copy all information
602 from the old service object. Previously, some data was omitted,
603 causing delays in descriptor upload, and other bugs. Fixes bug
604 23790; bugfix on 0.2.1.9-alpha.
606 o Minor bugfixes (path selection):
607 - When selecting relays by bandwidth, avoid a rounding error that
608 could sometimes cause load to be imbalanced incorrectly.
609 Previously, we would always round upwards; now, we round towards
610 the nearest integer. This had the biggest effect when a relay's
611 weight adjustments should have given it weight 0, but it got
612 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
613 - When calculating the fraction of nodes that have descriptors, and
614 all nodes in the network have zero bandwidths, count the number of
615 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
616 - Actually log the total bandwidth in compute_weighted_bandwidths().
617 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
619 o Minor bugfixes (portability):
620 - Stop using the PATH_MAX variable, which is not defined on GNU
621 Hurd. Fixes bug 23098; bugfix on 0.3.1.1-alpha.
622 - Fix a bug in the bit-counting parts of our timing-wheel code on
623 MSVC. (Note that MSVC is still not a supported build platform, due
624 to cryptographic timing channel risks.) Fixes bug 24633; bugfix
627 o Minor bugfixes (relay):
628 - When uploading our descriptor for the first time after startup,
629 report the reason for uploading as "Tor just started" rather than
630 leaving it blank. Fixes bug 22885; bugfix on 0.2.3.4-alpha.
631 - Avoid unnecessary calls to directory_fetches_from_authorities() on
632 relays, to prevent spurious address resolutions and descriptor
633 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
634 bugfix on in 0.2.8.1-alpha.
635 - Avoid a crash when transitioning from client mode to bridge mode.
636 Previously, we would launch the worker threads whenever our
637 "public server" mode changed, but not when our "server" mode
638 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
640 o Minor bugfixes (testing):
641 - Fix a spurious fuzzing-only use of an uninitialized value. Found
642 by Brian Carpenter. Fixes bug 24082; bugfix on 0.3.0.3-alpha.
643 - Test that IPv6-only clients can use microdescriptors when running
644 "make test-network-all". Requires chutney master 61c28b9 or later.
646 - Prevent scripts/test/coverage from attempting to move gcov output
647 to the root directory. Fixes bug 23741; bugfix on 0.2.5.1-alpha.
648 - Capture and detect several "Result does not fit" warnings in unit
649 tests on platforms with 32-bit time_t. Fixes bug 21800; bugfix
651 - Fix additional channelpadding unit test failures by using mocked
652 time instead of actual time for all tests. Fixes bug 23608; bugfix
654 - Fix a bug in our fuzzing mock replacement for crypto_pk_checksig(),
655 to correctly handle cases where a caller gives it an RSA key of
656 under 160 bits. (This is not actually a bug in Tor itself, but
657 rather in our fuzzing code.) Fixes bug 24247; bugfix on
658 0.3.0.3-alpha. Found by OSS-Fuzz as issue 4177.
659 - Fix a broken unit test for the OutboundAddress option: the parsing
660 function was never returning an error on failure. Fixes bug 23366;
661 bugfix on 0.3.0.3-alpha.
662 - Fix a signed-integer overflow in the unit tests for
663 dir/download_status_random_backoff, which was untriggered until we
664 fixed bug 17750. Fixes bug 22924; bugfix on 0.2.9.1-alpha.
666 o Minor bugfixes (usability, control port):
667 - Stop making an unnecessary routerlist check in NETINFO clock skew
668 detection; this was preventing clients from reporting NETINFO clock
669 skew to controllers. Fixes bug 23532; bugfix on 0.2.4.4-alpha.
671 o Code simplification and refactoring:
672 - Remove various ways of testing circuits and connections for
673 "clientness"; instead, favor channel_is_client(). Part of
675 - Extract the code for handling newly-open channels into a separate
676 function from the general code to handle channel state
677 transitions. This change simplifies our callgraph, reducing the
678 size of the largest strongly connected component by roughly a
679 factor of two. Closes ticket 22608.
680 - Remove dead code for largely unused statistics on the number of
681 times we've attempted various public key operations. Fixes bug
682 19871; bugfix on 0.1.2.4-alpha. Fix by Isis Lovecruft.
683 - Remove several now-obsolete functions for asking about old
684 variants directory authority status. Closes ticket 22311; patch
686 - Remove some of the code that once supported "Named" and "Unnamed"
687 routers. Authorities no longer vote for these flags. Closes
689 - Rename the obsolete malleable hybrid_encrypt functions used in TAP
690 and old hidden services, to indicate that they aren't suitable for
691 new protocols or formats. Closes ticket 23026.
692 - Replace our STRUCT_OFFSET() macro with offsetof(). Closes ticket
693 22521. Patch from Neel Chauhan.
694 - Split the enormous circuit_send_next_onion_skin() function into
695 multiple subfunctions. Closes ticket 22804.
696 - Split the portions of the buffer.c module that handle particular
697 protocols into separate modules. Part of ticket 23149.
698 - Use our test macros more consistently, to produce more useful
699 error messages when our unit tests fail. Add coccinelle patches to
700 allow us to re-check for test macro uses. Closes ticket 22497.
702 o Deprecated features:
703 - The ReachableDirAddresses and ClientPreferIPv6DirPort options are
704 now deprecated; they do not apply to relays, and they have had no
705 effect on clients since 0.2.8.x. Closes ticket 19704.
706 - Deprecate HTTPProxy/HTTPProxyAuthenticator config options. They
707 only applies to direct unencrypted HTTP connections to your
708 directory server, which your Tor probably isn't using. Closes
712 - Add notes in man page regarding OS support for the various
713 scheduler types. Attempt to use less jargon in the scheduler
714 section. Closes ticket 24254.
715 - Clarify that the Address option is entirely about setting an
716 advertised IPv4 address. Closes ticket 18891.
717 - Clarify the manpage's use of the term "address" to clarify what
718 kind of address is intended. Closes ticket 21405.
719 - Document that onion service subdomains are allowed, and ignored.
721 - Clarify in the manual that "Sandbox 1" is only supported on Linux
722 kernels. Closes ticket 22677.
723 - Document all values of PublishServerDescriptor in the manpage.
725 - Improve the documentation for the directory port part of the
726 DirAuthority line. Closes ticket 20152.
727 - Restore documentation for the authorities' "approved-routers"
728 file. Closes ticket 21148.
731 - The AllowDotExit option has been removed as unsafe. It has been
732 deprecated since 0.2.9.2-alpha. Closes ticket 23426.
733 - The ClientDNSRejectInternalAddresses flag can no longer be set on
734 non-testing networks. It has been deprecated since 0.2.9.2-alpha.
736 - The controller API no longer includes an AUTHDIR_NEWDESCS event:
737 nobody was using it any longer. Closes ticket 22377.
740 Changes in version 0.3.1.9 - 2017-12-01:
741 Tor 0.3.1.9 backports important security and stability fixes from the
742 0.3.2 development series. All Tor users should upgrade to this
743 release, or to another of the releases coming out today.
745 o Major bugfixes (security, backport from 0.3.2.6-alpha):
746 - Fix a denial of service bug where an attacker could use a
747 malformed directory object to cause a Tor instance to pause while
748 OpenSSL would try to read a passphrase from the terminal. (Tor
749 instances run without a terminal, which is the case for most Tor
750 packages, are not impacted.) Fixes bug 24246; bugfix on every
751 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
752 Found by OSS-Fuzz as testcase 6360145429790720.
753 - Fix a denial of service issue where an attacker could crash a
754 directory authority using a malformed router descriptor. Fixes bug
755 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
757 - When checking for replays in the INTRODUCE1 cell data for a
758 (legacy) onion service, correctly detect replays in the RSA-
759 encrypted part of the cell. We were previously checking for
760 replays on the entire cell, but those can be circumvented due to
761 the malleability of Tor's legacy hybrid encryption. This fix helps
762 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
763 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
766 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
767 - Fix a use-after-free error that could crash v2 Tor onion services
768 when they failed to open circuits while expiring introduction
769 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
770 also tracked as TROVE-2017-013 and CVE-2017-8823.
772 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
773 - When running as a relay, make sure that we never build a path
774 through ourselves, even in the case where we have somehow lost the
775 version of our descriptor appearing in the consensus. Fixes part
776 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
777 as TROVE-2017-012 and CVE-2017-8822.
778 - When running as a relay, make sure that we never choose ourselves
779 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
780 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
782 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
783 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
784 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
785 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
786 identifying and finding a workaround to this bug and to Moritz,
787 Arthur Edelstein, and Roger for helping to track it down and
790 o Minor features (bridge):
791 - Bridges now include notice in their descriptors that they are
792 bridges, and notice of their distribution status, based on their
793 publication settings. Implements ticket 18329. For more fine-
794 grained control of how a bridge is distributed, upgrade to 0.3.2.x
797 o Minor features (directory authority, backport from 0.3.2.6-alpha):
798 - Add an IPv6 address for the "bastet" directory authority. Closes
801 o Minor features (geoip):
802 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
805 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
806 - Avoid unnecessary calls to directory_fetches_from_authorities() on
807 relays, to prevent spurious address resolutions and descriptor
808 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
809 bugfix on in 0.2.8.1-alpha.
811 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
812 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
813 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
815 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
816 - When a circuit is marked for close, do not attempt to package any
817 cells for channels on that circuit. Previously, we would detect
818 this condition lower in the call stack, when we noticed that the
819 circuit had no attached channel, and log an annoying message.
820 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
822 o Minor bugfixes (onion service, backport from 0.3.2.5-alpha):
823 - Rename the consensus parameter "hsdir-interval" to "hsdir_interval"
824 so it matches dir-spec.txt. Fixes bug 24262; bugfix
827 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
828 - Avoid a crash when transitioning from client mode to bridge mode.
829 Previously, we would launch the worker threads whenever our
830 "public server" mode changed, but not when our "server" mode
831 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
834 Changes in version 0.3.0.13 - 2017-12-01
835 Tor 0.3.0.13 backports important security and stability bugfixes from
836 later Tor releases. All Tor users should upgrade to this release, or
837 to another of the releases coming out today.
839 Note: the Tor 0.3.0 series will no longer be supported after 26 Jan
840 2018. If you need a release with long-term support, please stick with
841 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
843 o Major bugfixes (security, backport from 0.3.2.6-alpha):
844 - Fix a denial of service bug where an attacker could use a
845 malformed directory object to cause a Tor instance to pause while
846 OpenSSL would try to read a passphrase from the terminal. (Tor
847 instances run without a terminal, which is the case for most Tor
848 packages, are not impacted.) Fixes bug 24246; bugfix on every
849 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
850 Found by OSS-Fuzz as testcase 6360145429790720.
851 - Fix a denial of service issue where an attacker could crash a
852 directory authority using a malformed router descriptor. Fixes bug
853 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
855 - When checking for replays in the INTRODUCE1 cell data for a
856 (legacy) onion service, correctly detect replays in the RSA-
857 encrypted part of the cell. We were previously checking for
858 replays on the entire cell, but those can be circumvented due to
859 the malleability of Tor's legacy hybrid encryption. This fix helps
860 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
861 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
864 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
865 - Fix a use-after-free error that could crash v2 Tor onion services
866 when they failed to open circuits while expiring introduction
867 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
868 also tracked as TROVE-2017-013 and CVE-2017-8823.
870 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
871 - When running as a relay, make sure that we never build a path
872 through ourselves, even in the case where we have somehow lost the
873 version of our descriptor appearing in the consensus. Fixes part
874 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
875 as TROVE-2017-012 and CVE-2017-8822.
876 - When running as a relay, make sure that we never choose ourselves
877 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
878 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
880 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
881 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
882 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
883 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
884 identifying and finding a workaround to this bug and to Moritz,
885 Arthur Edelstein, and Roger for helping to track it down and
888 o Minor features (security, windows, backport from 0.3.1.1-alpha):
889 - Enable a couple of pieces of Windows hardening: one
890 (HeapEnableTerminationOnCorruption) that has been on-by-default
891 since Windows 8, and unavailable before Windows 7; and one
892 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
893 affect us, but shouldn't do any harm. Closes ticket 21953.
895 o Minor features (bridge, backport from 0.3.1.9):
896 - Bridges now include notice in their descriptors that they are
897 bridges, and notice of their distribution status, based on their
898 publication settings. Implements ticket 18329. For more fine-
899 grained control of how a bridge is distributed, upgrade to 0.3.2.x
902 o Minor features (directory authority, backport from 0.3.2.6-alpha):
903 - Add an IPv6 address for the "bastet" directory authority. Closes
906 o Minor features (geoip):
907 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
910 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
911 - Avoid unnecessary calls to directory_fetches_from_authorities() on
912 relays, to prevent spurious address resolutions and descriptor
913 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
914 bugfix on in 0.2.8.1-alpha.
916 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
917 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
918 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
920 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
921 - When a circuit is marked for close, do not attempt to package any
922 cells for channels on that circuit. Previously, we would detect
923 this condition lower in the call stack, when we noticed that the
924 circuit had no attached channel, and log an annoying message.
925 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
927 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
928 - Avoid a crash when transitioning from client mode to bridge mode.
929 Previously, we would launch the worker threads whenever our
930 "public server" mode changed, but not when our "server" mode
931 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
933 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
934 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
935 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
938 Changes in version 0.2.9.14 - 2017-12-01
939 Tor 0.3.0.13 backports important security and stability bugfixes from
940 later Tor releases. All Tor users should upgrade to this release, or
941 to another of the releases coming out today.
943 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
944 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
945 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
946 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
947 identifying and finding a workaround to this bug and to Moritz,
948 Arthur Edelstein, and Roger for helping to track it down and
951 o Major bugfixes (security, backport from 0.3.2.6-alpha):
952 - Fix a denial of service bug where an attacker could use a
953 malformed directory object to cause a Tor instance to pause while
954 OpenSSL would try to read a passphrase from the terminal. (Tor
955 instances run without a terminal, which is the case for most Tor
956 packages, are not impacted.) Fixes bug 24246; bugfix on every
957 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
958 Found by OSS-Fuzz as testcase 6360145429790720.
959 - Fix a denial of service issue where an attacker could crash a
960 directory authority using a malformed router descriptor. Fixes bug
961 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
963 - When checking for replays in the INTRODUCE1 cell data for a
964 (legacy) onion service, correctly detect replays in the RSA-
965 encrypted part of the cell. We were previously checking for
966 replays on the entire cell, but those can be circumvented due to
967 the malleability of Tor's legacy hybrid encryption. This fix helps
968 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
969 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
972 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
973 - Fix a use-after-free error that could crash v2 Tor onion services
974 when they failed to open circuits while expiring introduction
975 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
976 also tracked as TROVE-2017-013 and CVE-2017-8823.
978 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
979 - When running as a relay, make sure that we never build a path
980 through ourselves, even in the case where we have somehow lost the
981 version of our descriptor appearing in the consensus. Fixes part
982 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
983 as TROVE-2017-012 and CVE-2017-8822.
985 o Minor features (bridge, backport from 0.3.1.9):
986 - Bridges now include notice in their descriptors that they are
987 bridges, and notice of their distribution status, based on their
988 publication settings. Implements ticket 18329. For more fine-
989 grained control of how a bridge is distributed, upgrade to 0.3.2.x
992 o Minor features (directory authority, backport from 0.3.2.6-alpha):
993 - Add an IPv6 address for the "bastet" directory authority. Closes
996 o Minor features (geoip):
997 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
1000 o Minor features (security, windows, backport from 0.3.1.1-alpha):
1001 - Enable a couple of pieces of Windows hardening: one
1002 (HeapEnableTerminationOnCorruption) that has been on-by-default
1003 since Windows 8, and unavailable before Windows 7; and one
1004 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
1005 affect us, but shouldn't do any harm. Closes ticket 21953.
1007 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
1008 - Avoid unnecessary calls to directory_fetches_from_authorities() on
1009 relays, to prevent spurious address resolutions and descriptor
1010 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
1011 bugfix on in 0.2.8.1-alpha.
1013 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
1014 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
1015 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
1017 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
1018 - When a circuit is marked for close, do not attempt to package any
1019 cells for channels on that circuit. Previously, we would detect
1020 this condition lower in the call stack, when we noticed that the
1021 circuit had no attached channel, and log an annoying message.
1022 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
1024 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
1025 - Avoid a crash when transitioning from client mode to bridge mode.
1026 Previously, we would launch the worker threads whenever our
1027 "public server" mode changed, but not when our "server" mode
1028 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
1030 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
1031 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
1032 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
1035 Changes in version 0.2.8.17 - 2017-12-01
1036 Tor 0.2.8.17 backports important security and stability bugfixes from
1037 later Tor releases. All Tor users should upgrade to this release, or
1038 to another of the releases coming out today.
1040 Note: the Tor 0.2.8 series will no longer be supported after 1 Jan
1041 2018. If you need a release with long-term support, please upgrade with
1042 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
1044 o Major bugfixes (security, backport from 0.3.2.6-alpha):
1045 - Fix a denial of service bug where an attacker could use a
1046 malformed directory object to cause a Tor instance to pause while
1047 OpenSSL would try to read a passphrase from the terminal. (Tor
1048 instances run without a terminal, which is the case for most Tor
1049 packages, are not impacted.) Fixes bug 24246; bugfix on every
1050 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
1051 Found by OSS-Fuzz as testcase 6360145429790720.
1052 - When checking for replays in the INTRODUCE1 cell data for a
1053 (legacy) onion service, correctly detect replays in the RSA-
1054 encrypted part of the cell. We were previously checking for
1055 replays on the entire cell, but those can be circumvented due to
1056 the malleability of Tor's legacy hybrid encryption. This fix helps
1057 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
1058 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
1061 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
1062 - Fix a use-after-free error that could crash v2 Tor onion services
1063 when they failed to open circuits while expiring introduction
1064 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
1065 also tracked as TROVE-2017-013 and CVE-2017-8823.
1067 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
1068 - When running as a relay, make sure that we never build a path through
1069 ourselves, even in the case where we have somehow lost the version of
1070 our descriptor appearing in the consensus. Fixes part of bug 21534;
1071 bugfix on 0.2.0.1-alpha. This issue is also tracked as TROVE-2017-012
1074 o Minor features (bridge, backport from 0.3.1.9):
1075 - Bridges now include notice in their descriptors that they are
1076 bridges, and notice of their distribution status, based on their
1077 publication settings. Implements ticket 18329. For more fine-
1078 grained control of how a bridge is distributed, upgrade to 0.3.2.x
1081 o Minor features (directory authority, backport from 0.3.2.6-alpha):
1082 - Add an IPv6 address for the "bastet" directory authority. Closes
1085 o Minor features (geoip):
1086 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
1089 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
1090 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
1091 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
1094 Changes in version 0.2.5.16 - 2017-12-01
1095 Tor 0.2.5.13 backports important security and stability bugfixes from
1096 later Tor releases. All Tor users should upgrade to this release, or
1097 to another of the releases coming out today.
1099 Note: the Tor 0.2.5 series will no longer be supported after 1 May
1100 2018. If you need a release with long-term support, please upgrade to
1101 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
1103 o Major bugfixes (security, backport from 0.3.2.6-alpha):
1104 - Fix a denial of service bug where an attacker could use a
1105 malformed directory object to cause a Tor instance to pause while
1106 OpenSSL would try to read a passphrase from the terminal. (Tor
1107 instances run without a terminal, which is the case for most Tor
1108 packages, are not impacted.) Fixes bug 24246; bugfix on every
1109 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
1110 Found by OSS-Fuzz as testcase 6360145429790720.
1111 - When checking for replays in the INTRODUCE1 cell data for a
1112 (legacy) onion service, correctly detect replays in the RSA-
1113 encrypted part of the cell. We were previously checking for
1114 replays on the entire cell, but those can be circumvented due to
1115 the malleability of Tor's legacy hybrid encryption. This fix helps
1116 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
1117 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
1120 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
1121 - When running as a relay, make sure that we never build a path
1122 through ourselves, even in the case where we have somehow lost the
1123 version of our descriptor appearing in the consensus. Fixes part
1124 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
1125 as TROVE-2017-012 and CVE-2017-8822.
1127 o Minor features (bridge, backport from 0.3.1.9):
1128 - Bridges now include notice in their descriptors that they are
1129 bridges, and notice of their distribution status, based on their
1130 publication settings. Implements ticket 18329. For more fine-
1131 grained control of how a bridge is distributed, upgrade to 0.3.2.x
1134 o Minor features (geoip):
1135 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
1139 Changes in version 0.2.5.15 - 2017-10-25
1140 Tor 0.2.5.15 backports a collection of bugfixes from later Tor release
1141 series. It also adds a new directory authority, Bastet.
1143 Note: the Tor 0.2.5 series will no longer be supported after 1 May
1144 2018. If you need a release with long-term support, please upgrade to
1145 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
1147 o Directory authority changes:
1148 - Add "Bastet" as a ninth directory authority to the default list.
1149 Closes ticket 23910.
1150 - The directory authority "Longclaw" has changed its IP address.
1151 Closes ticket 23592.
1153 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
1154 - Avoid an assertion failure bug affecting our implementation of
1155 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
1156 handling of "0xx" differs from what we had expected. Fixes bug
1157 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
1159 o Minor features (geoip):
1160 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
1163 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
1164 - Fix a memset() off the end of an array when packing cells. This
1165 bug should be harmless in practice, since the corrupted bytes are
1166 still in the same structure, and are always padding bytes,
1167 ignored, or immediately overwritten, depending on compiler
1168 behavior. Nevertheless, because the memset()'s purpose is to make
1169 sure that any other cell-handling bugs can't expose bytes to the
1170 network, we need to fix it. Fixes bug 22737; bugfix on
1171 0.2.4.11-alpha. Fixes CID 1401591.
1173 o Build features (backport from 0.3.1.5-alpha):
1174 - Tor's repository now includes a Travis Continuous Integration (CI)
1175 configuration file (.travis.yml). This is meant to help new
1176 developers and contributors who fork Tor to a Github repository be
1177 better able to test their changes, and understand what we expect
1178 to pass. To use this new build feature, you must fork Tor to your
1179 Github account, then go into the "Integrations" menu in the
1180 repository settings for your fork and enable Travis, then push
1181 your changes. Closes ticket 22636.
1184 Changes in version 0.2.8.16 - 2017-10-25
1185 Tor 0.2.8.16 backports a collection of bugfixes from later Tor release
1186 series, including a bugfix for a crash issue that had affected relays
1187 under memory pressure. It also adds a new directory authority, Bastet.
1189 Note: the Tor 0.2.8 series will no longer be supported after 1 Jan
1190 2018. If you need a release with long-term support, please stick with
1191 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
1193 o Directory authority changes:
1194 - Add "Bastet" as a ninth directory authority to the default list.
1195 Closes ticket 23910.
1196 - The directory authority "Longclaw" has changed its IP address.
1197 Closes ticket 23592.
1199 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
1200 - Fix a timing-based assertion failure that could occur when the
1201 circuit out-of-memory handler freed a connection's output buffer.
1202 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
1204 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
1205 - Remove longclaw's IPv6 address, as it will soon change. Authority
1206 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
1207 3/8 directory authorities with IPv6 addresses, but there are also
1208 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
1210 o Minor features (geoip):
1211 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
1215 Changes in version 0.2.9.13 - 2017-10-25
1216 Tor 0.2.9.13 backports a collection of bugfixes from later Tor release
1217 series, including a bugfix for a crash issue that had affected relays
1218 under memory pressure. It also adds a new directory authority, Bastet.
1220 o Directory authority changes:
1221 - Add "Bastet" as a ninth directory authority to the default list.
1222 Closes ticket 23910.
1223 - The directory authority "Longclaw" has changed its IP address.
1224 Closes ticket 23592.
1226 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
1227 - Fix a timing-based assertion failure that could occur when the
1228 circuit out-of-memory handler freed a connection's output buffer.
1229 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
1231 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
1232 - Remove longclaw's IPv6 address, as it will soon change. Authority
1233 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
1234 3/8 directory authorities with IPv6 addresses, but there are also
1235 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
1237 o Minor features (geoip):
1238 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
1241 o Minor bugfixes (directory authority, backport from 0.3.1.5-alpha):
1242 - When a directory authority rejects a descriptor or extrainfo with
1243 a given digest, mark that digest as undownloadable, so that we do
1244 not attempt to download it again over and over. We previously
1245 tried to avoid downloading such descriptors by other means, but we
1246 didn't notice if we accidentally downloaded one anyway. This
1247 behavior became problematic in 0.2.7.2-alpha, when authorities
1248 began pinning Ed25519 keys. Fixes bug 22349; bugfix
1251 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
1252 - Clear the address when node_get_prim_orport() returns early.
1253 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
1255 o Minor bugfixes (Windows service, backport from 0.3.1.6-rc):
1256 - When running as a Windows service, set the ID of the main thread
1257 correctly. Failure to do so made us fail to send log messages to
1258 the controller in 0.2.1.16-rc, slowed down controller event
1259 delivery in 0.2.7.3-rc and later, and crash with an assertion
1260 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
1261 Patch and diagnosis from "Vort".
1264 Changes in version 0.3.0.12 - 2017-10-25
1265 Tor 0.3.0.12 backports a collection of bugfixes from later Tor release
1266 series, including a bugfix for a crash issue that had affected relays
1267 under memory pressure. It also adds a new directory authority, Bastet.
1269 Note: the Tor 0.3.0 series will no longer be supported after 26 Jan
1270 2018. If you need a release with long-term support, please stick with
1271 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
1273 o Directory authority changes:
1274 - Add "Bastet" as a ninth directory authority to the default list.
1275 Closes ticket 23910.
1276 - The directory authority "Longclaw" has changed its IP address.
1277 Closes ticket 23592.
1279 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
1280 - Fix a timing-based assertion failure that could occur when the
1281 circuit out-of-memory handler freed a connection's output buffer.
1282 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
1284 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
1285 - Remove longclaw's IPv6 address, as it will soon change. Authority
1286 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
1287 3/8 directory authorities with IPv6 addresses, but there are also
1288 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
1290 o Minor features (geoip):
1291 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
1294 o Minor bugfixes (directory authority, backport from 0.3.1.5-alpha):
1295 - When a directory authority rejects a descriptor or extrainfo with
1296 a given digest, mark that digest as undownloadable, so that we do
1297 not attempt to download it again over and over. We previously
1298 tried to avoid downloading such descriptors by other means, but we
1299 didn't notice if we accidentally downloaded one anyway. This
1300 behavior became problematic in 0.2.7.2-alpha, when authorities
1301 began pinning Ed25519 keys. Fixes bug 22349; bugfix
1304 o Minor bugfixes (hidden service, relay, backport from 0.3.2.2-alpha):
1305 - Avoid a possible double close of a circuit by the intro point on
1306 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
1307 bugfix on 0.3.0.1-alpha.
1309 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
1310 - Clear the address when node_get_prim_orport() returns early.
1311 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
1313 o Minor bugfixes (Windows service, backport from 0.3.1.6-rc):
1314 - When running as a Windows service, set the ID of the main thread
1315 correctly. Failure to do so made us fail to send log messages to
1316 the controller in 0.2.1.16-rc, slowed down controller event
1317 delivery in 0.2.7.3-rc and later, and crash with an assertion
1318 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
1319 Patch and diagnosis from "Vort".
1322 Changes in version 0.3.1.8 - 2017-10-25
1323 Tor 0.3.1.8 is the second stable release in the 0.3.1 series.
1324 It includes several bugfixes, including a bugfix for a crash issue
1325 that had affected relays under memory pressure. It also adds
1326 a new directory authority, Bastet.
1328 o Directory authority changes:
1329 - Add "Bastet" as a ninth directory authority to the default list.
1330 Closes ticket 23910.
1331 - The directory authority "Longclaw" has changed its IP address.
1332 Closes ticket 23592.
1334 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
1335 - Fix a timing-based assertion failure that could occur when the
1336 circuit out-of-memory handler freed a connection's output buffer.
1337 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
1339 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
1340 - Remove longclaw's IPv6 address, as it will soon change. Authority
1341 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
1342 3/8 directory authorities with IPv6 addresses, but there are also
1343 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
1345 o Minor features (geoip):
1346 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
1349 o Minor bugfixes (compilation, backport from 0.3.2.2-alpha):
1350 - Fix a compilation warning when building with zstd support on
1351 32-bit platforms. Fixes bug 23568; bugfix on 0.3.1.1-alpha. Found
1352 and fixed by Andreas Stieger.
1354 o Minor bugfixes (compression, backport from 0.3.2.2-alpha):
1355 - Handle a pathological case when decompressing Zstandard data when
1356 the output buffer size is zero. Fixes bug 23551; bugfix
1359 o Minor bugfixes (directory authority, backport from 0.3.2.1-alpha):
1360 - Remove the length limit on HTTP status lines that authorities can
1361 send in their replies. Fixes bug 23499; bugfix on 0.3.1.6-rc.
1363 o Minor bugfixes (hidden service, relay, backport from 0.3.2.2-alpha):
1364 - Avoid a possible double close of a circuit by the intro point on
1365 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
1366 bugfix on 0.3.0.1-alpha.
1368 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
1369 - Clear the address when node_get_prim_orport() returns early.
1370 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
1372 o Minor bugfixes (unit tests, backport from 0.3.2.2-alpha):
1373 - Fix additional channelpadding unit test failures by using mocked
1374 time instead of actual time for all tests. Fixes bug 23608; bugfix
1378 Changes in version 0.2.8.15 - 2017-09-18
1379 Tor 0.2.8.15 backports a collection of bugfixes from later
1382 Most significantly, it includes a fix for TROVE-2017-008, a
1383 security bug that affects hidden services running with the
1384 SafeLogging option disabled. For more information, see
1385 https://trac.torproject.org/projects/tor/ticket/23490
1387 Note that Tor 0.2.8.x will no longer be supported after 1 Jan
1388 2018. We suggest that you upgrade to the latest stable release if
1389 possible. If you can't, we recommend that you upgrade at least to
1390 0.2.9, which will be supported until 2020.
1392 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
1393 - Avoid an assertion failure bug affecting our implementation of
1394 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
1395 handling of "0xx" differs from what we had expected. Fixes bug
1396 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
1399 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
1402 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
1403 - Backport a fix for an "unused variable" warning that appeared
1404 in some versions of mingw. Fixes bug 22838; bugfix on
1407 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
1408 - Fix a memset() off the end of an array when packing cells. This
1409 bug should be harmless in practice, since the corrupted bytes are
1410 still in the same structure, and are always padding bytes,
1411 ignored, or immediately overwritten, depending on compiler
1412 behavior. Nevertheless, because the memset()'s purpose is to make
1413 sure that any other cell-handling bugs can't expose bytes to the
1414 network, we need to fix it. Fixes bug 22737; bugfix on
1415 0.2.4.11-alpha. Fixes CID 1401591.
1417 o Build features (backport from 0.3.1.5-alpha):
1418 - Tor's repository now includes a Travis Continuous Integration (CI)
1419 configuration file (.travis.yml). This is meant to help new
1420 developers and contributors who fork Tor to a Github repository be
1421 better able to test their changes, and understand what we expect
1422 to pass. To use this new build feature, you must fork Tor to your
1423 Github account, then go into the "Integrations" menu in the
1424 repository settings for your fork and enable Travis, then push
1425 your changes. Closes ticket 22636.
1428 Changes in version 0.2.9.12 - 2017-09-18
1429 Tor 0.2.9.12 backports a collection of bugfixes from later
1432 Most significantly, it includes a fix for TROVE-2017-008, a
1433 security bug that affects hidden services running with the
1434 SafeLogging option disabled. For more information, see
1435 https://trac.torproject.org/projects/tor/ticket/23490
1437 o Major features (security, backport from 0.3.0.2-alpha):
1438 - Change the algorithm used to decide DNS TTLs on client and server
1439 side, to better resist DNS-based correlation attacks like the
1440 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
1441 Feamster. Now relays only return one of two possible DNS TTL
1442 values, and clients are willing to believe DNS TTL values up to 3
1443 hours long. Closes ticket 19769.
1445 o Major bugfixes (crash, directory connections, backport from 0.3.0.5-rc):
1446 - Fix a rare crash when sending a begin cell on a circuit whose
1447 linked directory connection had already been closed. Fixes bug
1448 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
1450 o Major bugfixes (DNS, backport from 0.3.0.2-alpha):
1451 - Fix a bug that prevented exit nodes from caching DNS records for
1452 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
1454 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
1455 - Fix a typo that had prevented TPROXY-based transparent proxying
1456 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
1457 Patch from "d4fq0fQAgoJ".
1459 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
1460 - Avoid an assertion failure bug affecting our implementation of
1461 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
1462 handling of "0xx" differs from what we had expected. Fixes bug
1463 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
1465 o Minor features (code style, backport from 0.3.1.3-alpha):
1466 - Add "Falls through" comments to our codebase, in order to silence
1467 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
1468 Stieger. Closes ticket 22446.
1470 o Minor features (geoip):
1471 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
1474 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.1-alpha):
1475 - Roll over monthly accounting at the configured hour and minute,
1476 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
1477 Found by Andrey Karpov with PVS-Studio.
1479 o Minor bugfixes (compilation, backport from 0.3.1.5-alpha):
1480 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
1481 bugfix on 0.2.8.1-alpha.
1482 - Fix warnings when building with libscrypt and openssl scrypt support
1483 on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
1484 - When building with certain versions the mingw C header files, avoid
1485 float-conversion warnings when calling the C functions isfinite(),
1486 isnan(), and signbit(). Fixes bug 22801; bugfix on 0.2.8.1-alpha.
1488 o Minor bugfixes (compilation, backport from 0.3.1.7):
1489 - Avoid compiler warnings in the unit tests for running tor_sscanf()
1490 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
1492 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
1493 - Backport a fix for an "unused variable" warning that appeared
1494 in some versions of mingw. Fixes bug 22838; bugfix on
1497 o Minor bugfixes (controller, backport from 0.3.1.7):
1498 - Do not crash when receiving a HSPOST command with an empty body.
1499 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
1500 - Do not crash when receiving a POSTDESCRIPTOR command with an
1501 empty body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
1503 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
1504 - Avoid Coverity build warnings related to our BUG() macro. By
1505 default, Coverity treats BUG() as the Linux kernel does: an
1506 instant abort(). We need to override that so our BUG() macro
1507 doesn't prevent Coverity from analyzing functions that use it.
1508 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
1510 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
1511 - Fix a memset() off the end of an array when packing cells. This
1512 bug should be harmless in practice, since the corrupted bytes are
1513 still in the same structure, and are always padding bytes,
1514 ignored, or immediately overwritten, depending on compiler
1515 behavior. Nevertheless, because the memset()'s purpose is to make
1516 sure that any other cell-handling bugs can't expose bytes to the
1517 network, we need to fix it. Fixes bug 22737; bugfix on
1518 0.2.4.11-alpha. Fixes CID 1401591.
1520 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
1521 - When setting the maximum number of connections allowed by the OS,
1522 always allow some extra file descriptors for other files. Fixes
1523 bug 22797; bugfix on 0.2.0.10-alpha.
1525 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
1526 - Avoid a sandbox failure when trying to re-bind to a socket and
1527 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
1529 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
1530 - Permit the fchmod system call, to avoid crashing on startup when
1531 starting with the seccomp2 sandbox and an unexpected set of
1532 permissions on the data directory or its contents. Fixes bug
1533 22516; bugfix on 0.2.5.4-alpha.
1535 o Minor bugfixes (relay, backport from 0.3.0.5-rc):
1536 - Avoid a double-marked-circuit warning that could happen when we
1537 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
1540 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
1541 - Reject version numbers with non-numeric prefixes (such as +, -, or
1542 whitespace). Disallowing whitespace prevents differential version
1543 parsing between POSIX-based and Windows platforms. Fixes bug 21507
1544 and part of 21508; bugfix on 0.0.8pre1.
1546 o Build features (backport from 0.3.1.5-alpha):
1547 - Tor's repository now includes a Travis Continuous Integration (CI)
1548 configuration file (.travis.yml). This is meant to help new
1549 developers and contributors who fork Tor to a Github repository be
1550 better able to test their changes, and understand what we expect
1551 to pass. To use this new build feature, you must fork Tor to your
1552 Github account, then go into the "Integrations" menu in the
1553 repository settings for your fork and enable Travis, then push
1554 your changes. Closes ticket 22636.
1557 Changes in version 0.3.0.11 - 2017-09-18
1558 Tor 0.3.0.11 backports a collection of bugfixes from Tor the 0.3.1
1561 Most significantly, it includes a fix for TROVE-2017-008, a
1562 security bug that affects hidden services running with the
1563 SafeLogging option disabled. For more information, see
1564 https://trac.torproject.org/projects/tor/ticket/23490
1566 o Minor features (code style, backport from 0.3.1.7):
1567 - Add "Falls through" comments to our codebase, in order to silence
1568 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
1569 Stieger. Closes ticket 22446.
1572 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
1575 o Minor bugfixes (compilation, backport from 0.3.1.7):
1576 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
1577 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
1579 o Minor bugfixes (controller, backport from 0.3.1.7):
1580 - Do not crash when receiving a HSPOST command with an empty body.
1581 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
1582 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
1583 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
1585 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
1586 - When setting the maximum number of connections allowed by the OS,
1587 always allow some extra file descriptors for other files. Fixes
1588 bug 22797; bugfix on 0.2.0.10-alpha.
1590 o Minor bugfixes (logging, relay, backport from 0.3.1.6-rc):
1591 - Remove a forgotten debugging message when an introduction point
1592 successfully establishes a hidden service prop224 circuit with
1594 - Change three other log_warn() for an introduction point to
1595 protocol warnings, because they can be failure from the network
1596 and are not relevant to the operator. Fixes bug 23078; bugfix on
1597 0.3.0.1-alpha and 0.3.0.2-alpha.
1600 Changes in version 0.3.1.7 - 2017-09-18
1601 Tor 0.3.1.7 is the first stable release in the 0.3.1 series.
1603 With the 0.3.1 series, Tor now serves and downloads directory
1604 information in more compact formats, to save on bandwidth overhead. It
1605 also contains a new padding system to resist netflow-based traffic
1606 analysis, and experimental support for building parts of Tor in Rust
1607 (though no parts of Tor are in Rust yet). There are also numerous
1608 small features, bugfixes on earlier release series, and groundwork for
1609 the hidden services revamp of 0.3.2.
1611 This release also includes a fix for TROVE-2017-008, a security bug
1612 that affects hidden services running with the SafeLogging option
1613 disabled. For more information, see
1614 https://trac.torproject.org/projects/tor/ticket/23490
1616 Per our stable release policy, we plan to support each stable release
1617 series for at least the next nine months, or for three months after
1618 the first stable release of the next series: whichever is longer. If
1619 you need a release with long-term support, we recommend that you stay
1620 with the 0.2.9 series.
1622 Below is a list of the changes since 0.3.0. For a list of all
1623 changes since 0.3.1.6-rc, see the ChangeLog file.
1626 - To build with zstd and lzma support, Tor now requires the
1627 pkg-config tool at build time.
1629 o Major bugfixes (security, hidden services, loggging):
1630 - Fix a bug where we could log uninitialized stack when a certain
1631 hidden service error occurred while SafeLogging was disabled.
1632 Fixes bug #23490; bugfix on 0.2.7.2-alpha.
1633 This is also tracked as TROVE-2017-008 and CVE-2017-0380.
1635 o Major features (build system, continuous integration):
1636 - Tor's repository now includes a Travis Continuous Integration (CI)
1637 configuration file (.travis.yml). This is meant to help new
1638 developers and contributors who fork Tor to a Github repository be
1639 better able to test their changes, and understand what we expect
1640 to pass. To use this new build feature, you must fork Tor to your
1641 Github account, then go into the "Integrations" menu in the
1642 repository settings for your fork and enable Travis, then push
1643 your changes. Closes ticket 22636.
1645 o Major features (directory protocol):
1646 - Tor relays and authorities can now serve clients an abbreviated
1647 version of the consensus document, containing only the changes
1648 since an older consensus document that the client holds. Clients
1649 now request these documents when available. When both client and
1650 server use this new protocol, they will use far less bandwidth (up
1651 to 94% less) to keep the client's consensus up-to-date. Implements
1652 proposal 140; closes ticket 13339. Based on work by Daniel MartÃ.
1653 - Tor can now compress directory traffic with lzma or with zstd
1654 compression algorithms, which can deliver better bandwidth
1655 performance. Because lzma is computationally expensive, it's only
1656 used for documents that can be compressed once and served many
1657 times. Support for these algorithms requires that tor is built
1658 with the libzstd and/or liblzma libraries available. Implements
1659 proposal 278; closes ticket 21662.
1660 - Relays now perform the more expensive compression operations, and
1661 consensus diff generation, in worker threads. This separation
1662 avoids delaying the main thread when a new consensus arrives.
1664 o Major features (experimental):
1665 - Tor can now build modules written in Rust. To turn this on, pass
1666 the "--enable-rust" flag to the configure script. It's not time to
1667 get excited yet: currently, there is no actual Rust functionality
1668 beyond some simple glue code, and a notice at startup to tell you
1669 that Rust is running. Still, we hope that programmers and
1670 packagers will try building Tor with Rust support, so that we can
1671 find issues and solve portability problems. Closes ticket 22106.
1673 o Major features (traffic analysis resistance):
1674 - Connections between clients and relays now send a padding cell in
1675 each direction every 1.5 to 9.5 seconds (tunable via consensus
1676 parameters). This padding will not resist specialized
1677 eavesdroppers, but it should be enough to make many ISPs' routine
1678 network flow logging less useful in traffic analysis against
1681 Padding is negotiated using Tor's link protocol, so both relays
1682 and clients must upgrade for this to take effect. Clients may
1683 still send padding despite the relay's version by setting
1684 ConnectionPadding 1 in torrc, and may disable padding by setting
1685 ConnectionPadding 0 in torrc. Padding may be minimized for mobile
1686 users with the torrc option ReducedConnectionPadding. Implements
1687 Proposal 251 and Section 2 of Proposal 254; closes ticket 16861.
1688 - Relays will publish 24 hour totals of padding and non-padding cell
1689 counts to their extra-info descriptors, unless PaddingStatistics 0
1690 is set in torrc. These 24 hour totals are also rounded to
1693 o Major bugfixes (hidden service, relay, security):
1694 - Fix a remotely triggerable assertion failure when a hidden service
1695 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
1696 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
1697 - Fix a remotely triggerable assertion failure caused by receiving a
1698 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
1699 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
1702 o Major bugfixes (path selection, security):
1703 - When choosing which guard to use for a circuit, avoid the exit's
1704 family along with the exit itself. Previously, the new guard
1705 selection logic avoided the exit, but did not consider its family.
1706 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
1707 006 and CVE-2017-0377.
1709 o Major bugfixes (connection usage):
1710 - We use NETINFO cells to try to determine if both relays involved
1711 in a connection will agree on the canonical status of that
1712 connection. We prefer the connections where this is the case for
1713 extend cells, and try to close connections where relays disagree
1714 on their canonical status early. Also, we now prefer the oldest
1715 valid connection for extend cells. These two changes should reduce
1716 the number of long-term connections that are kept open between
1717 relays. Fixes bug 17604; bugfix on 0.2.5.5-alpha.
1718 - Relays now log hourly statistics (look for
1719 "channel_check_for_duplicates" lines) on the total number of
1720 connections to other relays. If the number of connections per
1721 relay is unexpectedly large, this log message is at notice level.
1722 Otherwise it is at info.
1724 o Major bugfixes (entry guards):
1725 - When starting with an old consensus, do not add new entry guards
1726 unless the consensus is "reasonably live" (under 1 day old). Fixes
1727 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
1728 - Don't block bootstrapping when a primary bridge is offline and we
1729 can't get its descriptor. Fixes bug 22325; fixes one case of bug
1730 21969; bugfix on 0.3.0.3-alpha.
1732 o Major bugfixes (linux TPROXY support):
1733 - Fix a typo that had prevented TPROXY-based transparent proxying
1734 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
1735 Patch from "d4fq0fQAgoJ".
1737 o Major bugfixes (openbsd, denial-of-service):
1738 - Avoid an assertion failure bug affecting our implementation of
1739 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
1740 handling of "0xx" differs from what we had expected. Fixes bug
1741 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
1743 o Major bugfixes (relay, link handshake):
1744 - When performing the v3 link handshake on a TLS connection, report
1745 that we have the x509 certificate that we actually used on that
1746 connection, even if we have changed certificates since that
1747 connection was first opened. Previously, we would claim to have
1748 used our most recent x509 link certificate, which would sometimes
1749 make the link handshake fail. Fixes one case of bug 22460; bugfix
1752 o Major bugfixes (relays, key management):
1753 - Regenerate link and authentication certificates whenever the key
1754 that signs them changes; also, regenerate link certificates
1755 whenever the signed key changes. Previously, these processes were
1756 only weakly coupled, and we relays could (for minutes to hours)
1757 wind up with an inconsistent set of keys and certificates, which
1758 other relays would not accept. Fixes two cases of bug 22460;
1759 bugfix on 0.3.0.1-alpha.
1760 - When sending an Ed25519 signing->link certificate in a CERTS cell,
1761 send the certificate that matches the x509 certificate that we
1762 used on the TLS connection. Previously, there was a race condition
1763 if the TLS context rotated after we began the TLS handshake but
1764 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
1767 o Minor features (security, windows):
1768 - Enable a couple of pieces of Windows hardening: one
1769 (HeapEnableTerminationOnCorruption) that has been on-by-default
1770 since Windows 8, and unavailable before Windows 7; and one
1771 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
1772 affect us, but shouldn't do any harm. Closes ticket 21953.
1774 o Minor features (bridge authority):
1775 - Add "fingerprint" lines to the networkstatus-bridges file produced
1776 by bridge authorities. Closes ticket 22207.
1778 o Minor features (code style):
1779 - Add "Falls through" comments to our codebase, in order to silence
1780 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
1781 Stieger. Closes ticket 22446.
1783 o Minor features (config options):
1784 - Allow "%include" directives in torrc configuration files. These
1785 directives import the settings from other files, or from all the
1786 files in a directory. Closes ticket 1922. Code by Daniel Pinto.
1787 - Make SAVECONF return an error when overwriting a torrc that has
1788 includes. Using SAVECONF with the FORCE option will allow it to
1789 overwrite torrc even if includes are used. Related to ticket 1922.
1790 - Add "GETINFO config-can-saveconf" to tell controllers if SAVECONF
1791 will work without the FORCE option. Related to ticket 1922.
1793 o Minor features (controller):
1794 - Warn the first time that a controller requests data in the long-
1795 deprecated 'GETINFO network-status' format. Closes ticket 21703.
1797 o Minor features (defaults):
1798 - The default value for UseCreateFast is now 0: clients which
1799 haven't yet received a consensus document will now use a proper
1800 ntor handshake to talk to their directory servers whenever they
1801 can. Closes ticket 21407.
1802 - Onion key rotation and expiry intervals are now defined as a
1803 network consensus parameter, per proposal 274. The default
1804 lifetime of an onion key is increased from 7 to 28 days. Old onion
1805 keys will expire after 7 days by default. This change will make
1806 consensus diffs much smaller, and save significant bandwidth.
1807 Closes ticket 21641.
1809 o Minor features (defensive programming):
1810 - Create a pair of consensus parameters, nf_pad_tor2web and
1811 nf_pad_single_onion, to disable netflow padding in the consensus
1812 for non-anonymous connections in case the overhead is high. Closes
1815 o Minor features (diagnostic):
1816 - Add a stack trace to the bug warnings that can be logged when
1817 trying to send an outgoing relay cell with n_chan == 0. Diagnostic
1818 attempt for bug 23105.
1819 - Add logging messages to try to diagnose a rare bug that seems to
1820 generate RSA->Ed25519 cross-certificates dated in the 1970s. We
1821 think this is happening because of incorrect system clocks, but
1822 we'd like to know for certain. Diagnostic for bug 22466.
1823 - Avoid an assertion failure, and log a better error message, when
1824 unable to remove a file from the consensus cache on Windows.
1825 Attempts to mitigate and diagnose bug 22752.
1827 o Minor features (directory authority):
1828 - Improve the message that authorities report to relays that present
1829 RSA/Ed25519 keypairs that conflict with previously pinned keys.
1830 Closes ticket 22348.
1832 o Minor features (directory cache, consensus diff):
1833 - Add a new MaxConsensusAgeForDiffs option to allow directory cache
1834 operators with low-resource environments to adjust the number of
1835 consensuses they'll store and generate diffs from. Most cache
1836 operators should leave it unchanged. Helps to work around
1839 o Minor features (fallback directory list):
1840 - Update the fallback directory mirror whitelist and blacklist based
1841 on operator emails. Closes task 21121.
1842 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
1843 December 2016 (of which ~126 were still functional) with a list of
1844 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
1845 2017. Resolves ticket 21564.
1847 o Minor features (geoip):
1848 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
1851 o Minor features (hidden services, logging):
1852 - Log a message when a hidden service descriptor has fewer
1853 introduction points than specified in
1854 HiddenServiceNumIntroductionPoints. Closes tickets 21598.
1855 - Log a message when a hidden service reaches its introduction point
1856 circuit limit, and when that limit is reset. Follow up to ticket
1857 21594; closes ticket 21622.
1858 - Warn user if multiple entries in EntryNodes and at least one
1859 HiddenService are used together. Pinning EntryNodes along with a
1860 hidden service can be possibly harmful; for instance see ticket
1861 14917 or 21155. Closes ticket 21155.
1863 o Minor features (linux seccomp2 sandbox):
1864 - We now have a document storage backend compatible with the Linux
1865 seccomp2 sandbox. This backend is used for consensus documents and
1866 diffs between them; in the long term, we'd like to use it for
1867 unparseable directory material too. Closes ticket 21645
1868 - Increase the maximum allowed size passed to mprotect(PROT_WRITE)
1869 from 1MB to 16MB. This was necessary with the glibc allocator in
1870 order to allow worker threads to allocate more memory -- which in
1871 turn is necessary because of our new use of worker threads for
1872 compression. Closes ticket 22096.
1874 o Minor features (logging):
1875 - Log files are no longer created world-readable by default.
1876 (Previously, most distributors would store the logs in a non-
1877 world-readable location to prevent inappropriate access. This
1878 change is an extra precaution.) Closes ticket 21729; patch
1881 o Minor features (performance):
1882 - Our Keccak (SHA-3) implementation now accesses memory more
1883 efficiently, especially on little-endian systems. Closes
1885 - Add an O(1) implementation of channel_find_by_global_id(), to
1886 speed some controller functions.
1888 o Minor features (relay, configuration):
1889 - The MyFamily option may now be repeated as many times as desired,
1890 for relays that want to configure large families. Closes ticket
1891 4998; patch by Daniel Pinto.
1893 o Minor features (relay, performance):
1894 - Always start relays with at least two worker threads, to prevent
1895 priority inversion on slow tasks. Part of the fix for bug 22883.
1896 - Allow background work to be queued with different priorities, so
1897 that a big pile of slow low-priority jobs will not starve out
1898 higher priority jobs. This lays the groundwork for a fix for
1901 o Minor features (safety):
1902 - Add an explicit check to extrainfo_parse_entry_from_string() for
1903 NULL inputs. We don't believe this can actually happen, but it may
1904 help silence a warning from the Clang analyzer. Closes
1907 o Minor features (testing):
1908 - Add more tests for compression backend initialization. Closes
1910 - Add a "--disable-memory-sentinels" feature to help with fuzzing.
1911 When Tor is compiled with this option, we disable a number of
1912 redundant memory-safety failsafes that are intended to stop bugs
1913 from becoming security issues. This makes it easier to hunt for
1914 bugs that would be security issues without the failsafes turned
1915 on. Closes ticket 21439.
1916 - Add a general event-tracing instrumentation support to Tor. This
1917 subsystem will enable developers and researchers to add fine-
1918 grained instrumentation to their Tor instances, for use when
1919 examining Tor network performance issues. There are no trace
1920 events yet, and event-tracing is off by default unless enabled at
1921 compile time. Implements ticket 13802.
1922 - Improve our version parsing tests: add tests for typical version
1923 components, add tests for invalid versions, including numeric
1924 range and non-numeric prefixes. Unit tests 21278, 21450, and
1925 21507. Partially implements 21470.
1927 o Minor bugfixes (bandwidth accounting):
1928 - Roll over monthly accounting at the configured hour and minute,
1929 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
1930 Found by Andrey Karpov with PVS-Studio.
1932 o Minor bugfixes (code correctness):
1933 - Accurately identify client connections by their lack of peer
1934 authentication. This means that we bail out earlier if asked to
1935 extend to a client. Follow-up to 21407. Fixes bug 21406; bugfix
1938 o Minor bugfixes (compilation warnings):
1939 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug
1940 22915; bugfix on 0.2.8.1-alpha.
1941 - Fix warnings when building with libscrypt and openssl scrypt
1942 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
1943 - When building with certain versions of the mingw C header files,
1944 avoid float-conversion warnings when calling the C functions
1945 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
1948 o Minor bugfixes (compilation):
1949 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
1950 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
1952 o Minor bugfixes (compression):
1953 - When spooling compressed data to an output buffer, don't try to
1954 spool more data when there is no more data to spool and we are not
1955 trying to flush the input. Previously, we would sometimes launch
1956 compression requests with nothing to do, which interferes with our
1957 22672 checks. Fixes bug 22719; bugfix on 0.2.0.16-alpha.
1959 o Minor bugfixes (configuration):
1960 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
1961 bug 22252; bugfix on 0.2.9.3-alpha.
1963 o Minor bugfixes (connection lifespan):
1964 - Allow more control over how long TLS connections are kept open:
1965 unify CircuitIdleTimeout and PredictedPortsRelevanceTime into a
1966 single option called CircuitsAvailableTimeout. Also, allow the
1967 consensus to control the default values for both this preference
1968 and the lifespan of relay-to-relay connections. Fixes bug 17592;
1969 bugfix on 0.2.5.5-alpha.
1970 - Increase the initial circuit build timeout testing frequency, to
1971 help ensure that ReducedConnectionPadding clients finish learning
1972 a timeout before their orconn would expire. The initial testing
1973 rate was set back in the days of TAP and before the Tor Browser
1974 updater, when we had to be much more careful about new clients
1975 making lots of circuits. With this change, a circuit build timeout
1976 is learned in about 15-20 minutes, instead of 100-120 minutes.
1978 o Minor bugfixes (controller):
1979 - Do not crash when receiving a HSPOST command with an empty body.
1980 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
1981 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
1982 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
1983 - GETINFO onions/current and onions/detached no longer respond with
1984 551 on empty lists. Fixes bug 21329; bugfix on 0.2.7.1-alpha.
1985 - Trigger HS descriptor events on the control port when the client
1986 fails to pick a hidden service directory for a hidden service.
1987 This can happen if all the hidden service directories are in
1988 ExcludeNodes, or they have all been queried within the last 15
1989 minutes. Fixes bug 22042; bugfix on 0.2.5.2-alpha.
1991 o Minor bugfixes (correctness):
1992 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
1993 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
1995 o Minor bugfixes (coverity build support):
1996 - Avoid Coverity build warnings related to our BUG() macro. By
1997 default, Coverity treats BUG() as the Linux kernel does: an
1998 instant abort(). We need to override that so our BUG() macro
1999 doesn't prevent Coverity from analyzing functions that use it.
2000 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
2002 o Minor bugfixes (defensive programming):
2003 - Detect and break out of infinite loops in our compression code. We
2004 don't think that any such loops exist now, but it's best to be
2005 safe. Closes ticket 22672.
2006 - Fix a memset() off the end of an array when packing cells. This
2007 bug should be harmless in practice, since the corrupted bytes are
2008 still in the same structure, and are always padding bytes,
2009 ignored, or immediately overwritten, depending on compiler
2010 behavior. Nevertheless, because the memset()'s purpose is to make
2011 sure that any other cell-handling bugs can't expose bytes to the
2012 network, we need to fix it. Fixes bug 22737; bugfix on
2013 0.2.4.11-alpha. Fixes CID 1401591.
2015 o Minor bugfixes (directory authority):
2016 - When a directory authority rejects a descriptor or extrainfo with
2017 a given digest, mark that digest as undownloadable, so that we do
2018 not attempt to download it again over and over. We previously
2019 tried to avoid downloading such descriptors by other means, but we
2020 didn't notice if we accidentally downloaded one anyway. This
2021 behavior became problematic in 0.2.7.2-alpha, when authorities
2022 began pinning Ed25519 keys. Fixes bug 22349; bugfix
2024 - When rejecting a router descriptor for running an obsolete version
2025 of Tor without ntor support, warn about the obsolete tor version,
2026 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
2027 - Prevent the shared randomness subsystem from asserting when
2028 initialized by a bridge authority with an incomplete configuration
2029 file. Fixes bug 21586; bugfix on 0.2.9.8.
2031 o Minor bugfixes (error reporting, windows):
2032 - When formatting Windows error messages, use the English format to
2033 avoid codepage issues. Fixes bug 22520; bugfix on 0.1.2.8-alpha.
2036 o Minor bugfixes (exit-side DNS):
2037 - Fix an untriggerable assertion that checked the output of a
2038 libevent DNS error, so that the assertion actually behaves as
2039 expected. Fixes bug 22244; bugfix on 0.2.0.20-rc. Found by Andrey
2040 Karpov using PVS-Studio.
2042 o Minor bugfixes (fallback directories):
2043 - Make the usage example in updateFallbackDirs.py actually work, and
2044 explain what it does. Fixes bug 22270; bugfix on 0.3.0.3-alpha.
2045 - Decrease the guard flag average required to be a fallback. This
2046 allows us to keep relays that have their guard flag removed when
2047 they restart. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
2048 - Decrease the minimum number of fallbacks to 100. Fixes bug 20913;
2049 bugfix on 0.2.8.1-alpha.
2050 - Make sure fallback directory mirrors have the same address, port,
2051 and relay identity key for at least 30 days before they are
2052 selected. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
2054 o Minor bugfixes (file limits, osx):
2055 - When setting the maximum number of connections allowed by the OS,
2056 always allow some extra file descriptors for other files. Fixes
2057 bug 22797; bugfix on 0.2.0.10-alpha.
2059 o Minor bugfixes (hidden services):
2060 - Increase the number of circuits that a service is allowed to
2061 open over a specific period of time. The value was lower than it
2062 should be (8 vs 12) in the normal case of 3 introduction points.
2063 Fixes bug 22159; bugfix on 0.3.0.5-rc.
2064 - Fix a BUG warning during HSv3 descriptor decoding that could be
2065 cause by a specially crafted descriptor. Fixes bug 23233; bugfix
2066 on 0.3.0.1-alpha. Bug found by "haxxpop".
2067 - Stop printing a cryptic warning when a hidden service gets a
2068 request to connect to a virtual port that it hasn't configured.
2069 Fixes bug 16706; bugfix on 0.2.6.3-alpha.
2070 - Simplify hidden service descriptor creation by using an existing
2071 flag to check if an introduction point is established. Fixes bug
2072 21599; bugfix on 0.2.7.2-alpha.
2074 o Minor bugfixes (link handshake):
2075 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
2076 months, and regenerate it when it is within one month of expiring.
2077 Previously, we had generated this certificate at startup with a
2078 ten-year lifetime, but that could lead to weird behavior when Tor
2079 was started with a grossly inaccurate clock. Mitigates bug 22466;
2080 mitigation on 0.3.0.1-alpha.
2082 o Minor bugfixes (linux seccomp2 sandbox):
2083 - Avoid a sandbox failure when trying to re-bind to a socket and
2084 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
2085 - Permit the fchmod system call, to avoid crashing on startup when
2086 starting with the seccomp2 sandbox and an unexpected set of
2087 permissions on the data directory or its contents. Fixes bug
2088 22516; bugfix on 0.2.5.4-alpha.
2090 o Minor bugfixes (logging):
2091 - When decompressing, do not warn if we fail to decompress using a
2092 compression method that we merely guessed. Fixes part of bug
2093 22670; bugfix on 0.1.1.14-alpha.
2094 - When decompressing, treat mismatch between content-encoding and
2095 actual compression type as a protocol warning. Fixes part of bug
2096 22670; bugfix on 0.1.1.9-alpha.
2097 - Downgrade "assigned_to_cpuworker failed" message to info-level
2098 severity. In every case that can reach it, either a better warning
2099 has already been logged, or no warning is warranted. Fixes bug
2100 22356; bugfix on 0.2.6.3-alpha.
2101 - Log a better message when a directory authority replies to an
2102 upload with an unexpected status code. Fixes bug 11121; bugfix
2104 - Downgrade a log statement about unexpected relay cells from "bug"
2105 to "protocol warning", because there is at least one use case
2106 where it can be triggered by a buggy tor implementation. Fixes bug
2107 21293; bugfix on 0.1.1.14-alpha.
2109 o Minor bugfixes (logging, relay):
2110 - Remove a forgotten debugging message when an introduction point
2111 successfully establishes a hidden service prop224 circuit with
2113 - Change three other log_warn() for an introduction point to
2114 protocol warnings, because they can be failure from the network
2115 and are not relevant to the operator. Fixes bug 23078; bugfix on
2116 0.3.0.1-alpha and 0.3.0.2-alpha.
2118 o Minor bugfixes (relay):
2119 - Inform the geoip and rephist modules about all requests, even on
2120 relays that are only fetching microdescriptors. Fixes a bug
2121 related to 21585; bugfix on 0.3.0.1-alpha.
2123 o Minor bugfixes (memory leaks):
2124 - Fix a small memory leak at exit from the backtrace handler code.
2125 Fixes bug 21788; bugfix on 0.2.5.2-alpha. Patch from Daniel Pinto.
2126 - When directory authorities reject a router descriptor due to
2127 keypinning, free the router descriptor rather than leaking the
2128 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
2129 - Fix a small memory leak when validating a configuration that uses
2130 two or more AF_UNIX sockets for the same port type. Fixes bug
2131 23053; bugfix on 0.2.6.3-alpha. This is CID 1415725.
2133 o Minor bugfixes (process behavior):
2134 - When exiting because of an error, always exit with a nonzero exit
2135 status. Previously, we would fail to report an error in our exit
2136 status in cases related to __OwningControllerProcess failure,
2137 lockfile contention, and Ed25519 key initialization. Fixes bug
2138 22720; bugfix on versions 0.2.1.6-alpha, 0.2.2.28-beta, and
2139 0.2.7.2-alpha respectively. Reported by "f55jwk4f"; patch
2142 o Minor bugfixes (robustness, error handling):
2143 - Improve our handling of the cases where OpenSSL encounters a
2144 memory error while encoding keys and certificates. We haven't
2145 observed these errors in the wild, but if they do happen, we now
2146 detect and respond better. Fixes bug 19418; bugfix on all versions
2147 of Tor. Reported by Guido Vranken.
2149 o Minor bugfixes (testing):
2150 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
2151 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
2152 - Use unbuffered I/O for utility functions around the
2153 process_handle_t type. This fixes unit test failures reported on
2154 OpenBSD and FreeBSD. Fixes bug 21654; bugfix on 0.2.3.1-alpha.
2155 - Make display of captured unit test log messages consistent. Fixes
2156 bug 21510; bugfix on 0.2.9.3-alpha.
2157 - Make test-network.sh always call chutney's test-network.sh.
2158 Previously, this only worked on systems which had bash installed,
2159 due to some bash-specific code in the script. Fixes bug 19699;
2160 bugfix on 0.3.0.4-rc. Follow-up to ticket 21581.
2161 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
2162 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
2163 - The unit tests now pass on systems where localhost is misconfigured
2164 to some IPv4 address other than 127.0.0.1. Fixes bug 6298; bugfix
2167 o Minor bugfixes (voting consistency):
2168 - Reject version numbers with non-numeric prefixes (such as +, -, or
2169 whitespace). Disallowing whitespace prevents differential version
2170 parsing between POSIX-based and Windows platforms. Fixes bug 21507
2171 and part of 21508; bugfix on 0.0.8pre1.
2173 o Minor bugfixes (Windows service):
2174 - When running as a Windows service, set the ID of the main thread
2175 correctly. Failure to do so made us fail to send log messages to
2176 the controller in 0.2.1.16-rc, slowed down controller event
2177 delivery in 0.2.7.3-rc and later, and crash with an assertion
2178 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
2179 Patch and diagnosis from "Vort".
2181 o Minor bugfixes (windows, relay):
2182 - Resolve "Failure from drain_fd: No error" warnings on Windows
2183 relays. Fixes bug 21540; bugfix on 0.2.6.3-alpha.
2185 o Code simplification and refactoring:
2186 - Break up the 630-line function connection_dir_client_reached_eof()
2187 into a dozen smaller functions. This change should help
2188 maintainability and readability of the client directory code.
2189 - Isolate our use of the openssl headers so that they are only
2190 included from our crypto wrapper modules, and from tests that
2191 examine those modules' internals. Closes ticket 21841.
2192 - Simplify our API to launch directory requests, making it more
2193 extensible and less error-prone. Now it's easier to add extra
2194 headers to directory requests. Closes ticket 21646.
2195 - Our base64 decoding functions no longer overestimate the output
2196 space that they need when parsing unpadded inputs. Closes
2198 - Remove unused "ROUTER_ADDED_NOTIFY_GENERATOR" internal value.
2199 Resolves ticket 22213.
2200 - The logic that directory caches use to spool request to clients,
2201 serving them one part at a time so as not to allocate too much
2202 memory, has been refactored for consistency. Previously there was
2203 a separate spooling implementation per type of spoolable data. Now
2204 there is one common spooling implementation, with extensible data
2205 types. Closes ticket 21651.
2206 - Tor's compression module now supports multiple backends. Part of
2207 the implementation for proposal 278; closes ticket 21663.
2210 - Add a manpage description for the key-pinning-journal file. Closes
2212 - Correctly note that bandwidth accounting values are stored in the
2213 state file, and the bw_accounting file is now obsolete. Closes
2215 - Document more of the files in the Tor data directory, including
2216 cached-extrainfo, secret_onion_key{,_ntor}.old, hidserv-stats,
2217 approved-routers, sr-random, and diff-cache. Found while fixing
2219 - Clarify the manpage for the (deprecated) torify script. Closes
2221 - Clarify the behavior of the KeepAliveIsolateSOCKSAuth sub-option.
2222 Closes ticket 21873.
2223 - Correct documentation about the default DataDirectory value.
2224 Closes ticket 21151.
2225 - Document the default behavior of NumEntryGuards and
2226 NumDirectoryGuards correctly. Fixes bug 21715; bugfix
2228 - Document key=value pluggable transport arguments for Bridge lines
2229 in torrc. Fixes bug 20341; bugfix on 0.2.5.1-alpha.
2230 - Note that bandwidth-limiting options don't affect TCP headers or
2231 DNS. Closes ticket 17170.
2233 o Removed features (configuration options, all in ticket 22060):
2234 - These configuration options are now marked Obsolete, and no longer
2235 have any effect: AllowInvalidNodes, AllowSingleHopCircuits,
2236 AllowSingleHopExits, ExcludeSingleHopRelays, FastFirstHopPK,
2237 TLSECGroup, WarnUnsafeSocks. They were first marked as deprecated
2238 in 0.2.9.2-alpha and have now been removed. The previous default
2239 behavior is now always chosen; the previous (less secure) non-
2240 default behavior is now unavailable.
2241 - CloseHSClientCircuitsImmediatelyOnTimeout and
2242 CloseHSServiceRendCircuitsImmediatelyOnTimeout were deprecated in
2243 0.2.9.2-alpha and now have been removed. HS circuits never close
2244 on circuit build timeout; they have a longer timeout period.
2245 - {Control,DNS,Dir,Socks,Trans,NATD,OR}ListenAddress were deprecated
2246 in 0.2.9.2-alpha and now have been removed. Use the ORPort option
2247 (and others) to configure listen-only and advertise-only addresses.
2249 o Removed features (tools):
2250 - We've removed the tor-checkkey tool from src/tools. Long ago, we
2251 used it to help people detect RSA keys that were generated by
2252 versions of Debian affected by CVE-2008-0166. But those keys have
2253 been out of circulation for ages, and this tool is no longer
2254 required. Closes ticket 21842.
2257 Changes in version 0.3.0.10 - 2017-08-02
2258 Tor 0.3.0.10 backports a collection of small-to-medium bugfixes
2259 from the current Tor alpha series. OpenBSD users and TPROXY users
2260 should upgrade; others are probably okay sticking with 0.3.0.9.
2262 o Major features (build system, continuous integration, backport from 0.3.1.5-alpha):
2263 - Tor's repository now includes a Travis Continuous Integration (CI)
2264 configuration file (.travis.yml). This is meant to help new
2265 developers and contributors who fork Tor to a Github repository be
2266 better able to test their changes, and understand what we expect
2267 to pass. To use this new build feature, you must fork Tor to your
2268 Github account, then go into the "Integrations" menu in the
2269 repository settings for your fork and enable Travis, then push
2270 your changes. Closes ticket 22636.
2272 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
2273 - Fix a typo that had prevented TPROXY-based transparent proxying
2274 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
2275 Patch from "d4fq0fQAgoJ".
2277 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
2278 - Avoid an assertion failure bug affecting our implementation of
2279 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
2280 handling of "0xbar" differs from what we had expected. Fixes bug
2281 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
2283 o Minor features (backport from 0.3.1.5-alpha):
2284 - Update geoip and geoip6 to the July 4 2017 Maxmind GeoLite2
2287 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.2-alpha):
2288 - Roll over monthly accounting at the configured hour and minute,
2289 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
2290 Found by Andrey Karpov with PVS-Studio.
2292 o Minor bugfixes (compilation warnings, backport from 0.3.1.5-alpha):
2293 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
2294 bugfix on 0.2.8.1-alpha.
2295 - Fix warnings when building with libscrypt and openssl scrypt
2296 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
2297 - When building with certain versions of the mingw C header files,
2298 avoid float-conversion warnings when calling the C functions
2299 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
2302 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
2303 - Backport a fix for an "unused variable" warning that appeared
2304 in some versions of mingw. Fixes bug 22838; bugfix on
2307 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
2308 - Avoid Coverity build warnings related to our BUG() macro. By
2309 default, Coverity treats BUG() as the Linux kernel does: an
2310 instant abort(). We need to override that so our BUG() macro
2311 doesn't prevent Coverity from analyzing functions that use it.
2312 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
2314 o Minor bugfixes (directory authority, backport from 0.3.1.1-alpha):
2315 - When rejecting a router descriptor for running an obsolete version
2316 of Tor without ntor support, warn about the obsolete tor version,
2317 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
2319 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
2320 - Avoid a sandbox failure when trying to re-bind to a socket and
2321 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
2323 o Minor bugfixes (unit tests, backport from 0.3.1.5-alpha)
2324 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
2325 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
2328 Changes in version 0.3.0.9 - 2017-06-29
2329 Tor 0.3.0.9 fixes a path selection bug that would allow a client
2330 to use a guard that was in the same network family as a chosen exit
2331 relay. This is a security regression; all clients running earlier
2332 versions of 0.3.0.x or 0.3.1.x should upgrade to 0.3.0.9 or
2335 This release also backports several other bugfixes from the 0.3.1.x
2338 o Major bugfixes (path selection, security, backport from 0.3.1.4-alpha):
2339 - When choosing which guard to use for a circuit, avoid the exit's
2340 family along with the exit itself. Previously, the new guard
2341 selection logic avoided the exit, but did not consider its family.
2342 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
2343 006 and CVE-2017-0377.
2345 o Major bugfixes (entry guards, backport from 0.3.1.1-alpha):
2346 - Don't block bootstrapping when a primary bridge is offline and we
2347 can't get its descriptor. Fixes bug 22325; fixes one case of bug
2348 21969; bugfix on 0.3.0.3-alpha.
2350 o Major bugfixes (entry guards, backport from 0.3.1.4-alpha):
2351 - When starting with an old consensus, do not add new entry guards
2352 unless the consensus is "reasonably live" (under 1 day old). Fixes
2353 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
2355 o Minor features (geoip):
2356 - Update geoip and geoip6 to the June 8 2017 Maxmind GeoLite2
2359 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
2360 - Reject version numbers with non-numeric prefixes (such as +, -, or
2361 whitespace). Disallowing whitespace prevents differential version
2362 parsing between POSIX-based and Windows platforms. Fixes bug 21507
2363 and part of 21508; bugfix on 0.0.8pre1.
2365 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
2366 - Permit the fchmod system call, to avoid crashing on startup when
2367 starting with the seccomp2 sandbox and an unexpected set of
2368 permissions on the data directory or its contents. Fixes bug
2369 22516; bugfix on 0.2.5.4-alpha.
2371 o Minor bugfixes (defensive programming, backport from 0.3.1.4-alpha):
2372 - Fix a memset() off the end of an array when packing cells. This
2373 bug should be harmless in practice, since the corrupted bytes are
2374 still in the same structure, and are always padding bytes,
2375 ignored, or immediately overwritten, depending on compiler
2376 behavior. Nevertheless, because the memset()'s purpose is to make
2377 sure that any other cell-handling bugs can't expose bytes to the
2378 network, we need to fix it. Fixes bug 22737; bugfix on
2379 0.2.4.11-alpha. Fixes CID 1401591.
2382 Changes in version 0.3.0.8 - 2017-06-08
2383 Tor 0.3.0.8 fixes a pair of bugs that would allow an attacker to
2384 remotely crash a hidden service with an assertion failure. Anyone
2385 running a hidden service should upgrade to this version, or to some
2386 other version with fixes for TROVE-2017-004 and TROVE-2017-005.
2388 Tor 0.3.0.8 also includes fixes for several key management bugs
2389 that sometimes made relays unreliable, as well as several other
2390 bugfixes described below.
2392 o Major bugfixes (hidden service, relay, security, backport
2393 from 0.3.1.3-alpha):
2394 - Fix a remotely triggerable assertion failure when a hidden service
2395 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
2396 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
2397 - Fix a remotely triggerable assertion failure caused by receiving a
2398 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
2399 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
2402 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
2403 - When performing the v3 link handshake on a TLS connection, report
2404 that we have the x509 certificate that we actually used on that
2405 connection, even if we have changed certificates since that
2406 connection was first opened. Previously, we would claim to have
2407 used our most recent x509 link certificate, which would sometimes
2408 make the link handshake fail. Fixes one case of bug 22460; bugfix
2411 o Major bugfixes (relays, key management, backport from 0.3.1.3-alpha):
2412 - Regenerate link and authentication certificates whenever the key
2413 that signs them changes; also, regenerate link certificates
2414 whenever the signed key changes. Previously, these processes were
2415 only weakly coupled, and we relays could (for minutes to hours)
2416 wind up with an inconsistent set of keys and certificates, which
2417 other relays would not accept. Fixes two cases of bug 22460;
2418 bugfix on 0.3.0.1-alpha.
2419 - When sending an Ed25519 signing->link certificate in a CERTS cell,
2420 send the certificate that matches the x509 certificate that we
2421 used on the TLS connection. Previously, there was a race condition
2422 if the TLS context rotated after we began the TLS handshake but
2423 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
2426 o Major bugfixes (hidden service v3, backport from 0.3.1.1-alpha):
2427 - Stop rejecting v3 hidden service descriptors because their size
2428 did not match an old padding rule. Fixes bug 22447; bugfix on
2431 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
2432 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
2433 December 2016 (of which ~126 were still functional) with a list of
2434 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
2435 2017. Resolves ticket 21564.
2437 o Minor bugfixes (configuration, backport from 0.3.1.1-alpha):
2438 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
2439 bug 22252; bugfix on 0.2.9.3-alpha.
2441 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
2442 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
2443 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
2445 o Minor bugfixes (link handshake, backport from 0.3.1.3-alpha):
2446 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
2447 months, and regenerate it when it is within one month of expiring.
2448 Previously, we had generated this certificate at startup with a
2449 ten-year lifetime, but that could lead to weird behavior when Tor
2450 was started with a grossly inaccurate clock. Mitigates bug 22466;
2451 mitigation on 0.3.0.1-alpha.
2453 o Minor bugfixes (memory leak, directory authority, backport from
2455 - When directory authorities reject a router descriptor due to
2456 keypinning, free the router descriptor rather than leaking the
2457 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
2460 Changes in version 0.2.9.11 - 2017-06-08
2461 Tor 0.2.9.11 backports a fix for a bug that would allow an attacker to
2462 remotely crash a hidden service with an assertion failure. Anyone
2463 running a hidden service should upgrade to this version, or to some
2464 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
2465 are not affected by TROVE-2017-004.)
2467 Tor 0.2.9.11 also backports fixes for several key management bugs
2468 that sometimes made relays unreliable, as well as several other
2469 bugfixes described below.
2471 o Major bugfixes (hidden service, relay, security, backport
2472 from 0.3.1.3-alpha):
2473 - Fix a remotely triggerable assertion failure caused by receiving a
2474 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
2475 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
2478 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
2479 - When performing the v3 link handshake on a TLS connection, report
2480 that we have the x509 certificate that we actually used on that
2481 connection, even if we have changed certificates since that
2482 connection was first opened. Previously, we would claim to have
2483 used our most recent x509 link certificate, which would sometimes
2484 make the link handshake fail. Fixes one case of bug 22460; bugfix
2487 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
2488 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
2489 December 2016 (of which ~126 were still functional) with a list of
2490 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
2491 2017. Resolves ticket 21564.
2493 o Minor features (future-proofing, backport from 0.3.0.7):
2494 - Tor no longer refuses to download microdescriptors or descriptors if
2495 they are listed as "published in the future". This change will
2496 eventually allow us to stop listing meaningful "published" dates
2497 in microdescriptor consensuses, and thereby allow us to reduce the
2498 resources required to download consensus diffs by over 50%.
2499 Implements part of ticket 21642; implements part of proposal 275.
2501 o Minor features (directory authorities, backport from 0.3.0.4-rc)
2502 - Directory authorities now reject relays running versions
2503 0.2.9.1-alpha through 0.2.9.4-alpha, because those relays
2504 suffer from bug 20499 and don't keep their consensus cache
2505 up-to-date. Resolves ticket 20509.
2507 o Minor features (geoip):
2508 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
2511 o Minor bugfixes (control port, backport from 0.3.0.6):
2512 - The GETINFO extra-info/digest/<digest> command was broken because
2513 of a wrong base16 decode return value check, introduced when
2514 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
2516 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
2517 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
2518 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
2520 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.0.7):
2521 - The getpid() system call is now permitted under the Linux seccomp2
2522 sandbox, to avoid crashing with versions of OpenSSL (and other
2523 libraries) that attempt to learn the process's PID by using the
2524 syscall rather than the VDSO code. Fixes bug 21943; bugfix
2527 o Minor bugfixes (memory leak, directory authority, backport
2528 from 0.3.1.2-alpha):
2529 - When directory authorities reject a router descriptor due to
2530 keypinning, free the router descriptor rather than leaking the
2531 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
2533 Changes in version 0.2.8.14 - 2017-06-08
2534 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
2535 remotely crash a hidden service with an assertion failure. Anyone
2536 running a hidden service should upgrade to this version, or to some
2537 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
2538 are not affected by TROVE-2017-004.)
2540 o Major bugfixes (hidden service, relay, security):
2541 - Fix a remotely triggerable assertion failure caused by receiving a
2542 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
2543 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
2546 o Minor features (geoip):
2547 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
2550 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
2551 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
2552 December 2016 (of which ~126 were still functional) with a list of
2553 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
2554 2017. Resolves ticket 21564.
2556 o Minor bugfixes (correctness):
2557 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
2558 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
2560 Changes in version 0.2.7.8 - 2017-06-08
2561 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
2562 remotely crash a hidden service with an assertion failure. Anyone
2563 running a hidden service should upgrade to this version, or to some
2564 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
2565 are not affected by TROVE-2017-004.)
2567 o Major bugfixes (hidden service, relay, security):
2568 - Fix a remotely triggerable assertion failure caused by receiving a
2569 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
2570 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
2573 o Minor features (geoip):
2574 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
2577 o Minor bugfixes (correctness):
2578 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
2579 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
2582 Changes in version 0.2.6.12 - 2017-06-08
2583 Tor 0.2.6.12 backports a fix for a bug that would allow an attacker to
2584 remotely crash a hidden service with an assertion failure. Anyone
2585 running a hidden service should upgrade to this version, or to some
2586 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
2587 are not affected by TROVE-2017-004.)
2589 o Major bugfixes (hidden service, relay, security):
2590 - Fix a remotely triggerable assertion failure caused by receiving a
2591 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
2592 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
2595 o Minor features (geoip):
2596 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
2599 o Minor bugfixes (correctness):
2600 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
2601 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
2603 Changes in version 0.2.5.14 - 2017-06-08
2604 Tor 0.2.5.14 backports a fix for a bug that would allow an attacker to
2605 remotely crash a hidden service with an assertion failure. Anyone
2606 running a hidden service should upgrade to this version, or to some
2607 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
2608 are not affected by TROVE-2017-004.)
2610 o Major bugfixes (hidden service, relay, security):
2611 - Fix a remotely triggerable assertion failure caused by receiving a
2612 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
2613 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
2616 o Minor features (geoip):
2617 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
2620 o Minor bugfixes (correctness):
2621 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
2622 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
2624 Changes in version 0.2.4.29 - 2017-06-08
2625 Tor 0.2.4.29 backports a fix for a bug that would allow an attacker to
2626 remotely crash a hidden service with an assertion failure. Anyone
2627 running a hidden service should upgrade to this version, or to some
2628 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
2629 are not affected by TROVE-2017-004.)
2631 o Major bugfixes (hidden service, relay, security):
2632 - Fix a remotely triggerable assertion failure caused by receiving a
2633 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
2634 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
2637 o Minor features (geoip):
2638 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
2641 o Minor bugfixes (correctness):
2642 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
2643 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
2646 Changes in version 0.3.0.7 - 2017-05-15
2647 Tor 0.3.0.7 fixes a medium-severity security bug in earlier versions
2648 of Tor 0.3.0.x, where an attacker could cause a Tor relay process
2649 to exit. Relays running earlier versions of Tor 0.3.0.x should upgrade;
2650 clients are not affected.
2652 o Major bugfixes (hidden service directory, security):
2653 - Fix an assertion failure in the hidden service directory code, which
2654 could be used by an attacker to remotely cause a Tor relay process to
2655 exit. Relays running earlier versions of Tor 0.3.0.x should upgrade.
2656 should upgrade. This security issue is tracked as TROVE-2017-002.
2657 Fixes bug 22246; bugfix on 0.3.0.1-alpha.
2660 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
2663 o Minor features (future-proofing):
2664 - Tor no longer refuses to download microdescriptors or descriptors
2665 if they are listed as "published in the future". This change will
2666 eventually allow us to stop listing meaningful "published" dates
2667 in microdescriptor consensuses, and thereby allow us to reduce the
2668 resources required to download consensus diffs by over 50%.
2669 Implements part of ticket 21642; implements part of proposal 275.
2671 o Minor bugfixes (Linux seccomp2 sandbox):
2672 - The getpid() system call is now permitted under the Linux seccomp2
2673 sandbox, to avoid crashing with versions of OpenSSL (and other
2674 libraries) that attempt to learn the process's PID by using the
2675 syscall rather than the VDSO code. Fixes bug 21943; bugfix
2679 Changes in version 0.3.0.6 - 2017-04-26
2680 Tor 0.3.0.6 is the first stable release of the Tor 0.3.0 series.
2682 With the 0.3.0 series, clients and relays now use Ed25519 keys to
2683 authenticate their link connections to relays, rather than the old
2684 RSA1024 keys that they used before. (Circuit crypto has been
2685 Curve25519-authenticated since 0.2.4.8-alpha.) We have also replaced
2686 the guard selection and replacement algorithm to behave more robustly
2687 in the presence of unreliable networks, and to resist guard-
2690 This series also includes numerous other small features and bugfixes,
2691 along with more groundwork for the upcoming hidden-services revamp.
2693 Per our stable release policy, we plan to support the Tor 0.3.0
2694 release series for at least the next nine months, or for three months
2695 after the first stable release of the 0.3.1 series: whichever is
2696 longer. If you need a release with long-term support, we recommend
2697 that you stay with the 0.2.9 series.
2699 Below are the changes since 0.2.9.10. For a list of only the changes
2700 since 0.3.0.5-rc, see the ChangeLog file.
2702 o Major features (directory authority, security):
2703 - The default for AuthDirPinKeys is now 1: directory authorities
2704 will reject relays where the RSA identity key matches a previously
2705 seen value, but the Ed25519 key has changed. Closes ticket 18319.
2707 o Major features (guard selection algorithm):
2708 - Tor's guard selection algorithm has been redesigned from the
2709 ground up, to better support unreliable networks and restrictive
2710 sets of entry nodes, and to better resist guard-capture attacks by
2711 hostile local networks. Implements proposal 271; closes
2714 o Major features (next-generation hidden services):
2715 - Relays can now handle v3 ESTABLISH_INTRO cells as specified by
2716 prop224 aka "Next Generation Hidden Services". Service and clients
2717 don't use this functionality yet. Closes ticket 19043. Based on
2718 initial code by Alec Heifetz.
2719 - Relays now support the HSDir version 3 protocol, so that they can
2720 can store and serve v3 descriptors. This is part of the next-
2721 generation onion service work detailed in proposal 224. Closes
2724 o Major features (protocol, ed25519 identity keys):
2725 - Clients now support including Ed25519 identity keys in the EXTEND2
2726 cells they generate. By default, this is controlled by a consensus
2727 parameter, currently disabled. You can turn this feature on for
2728 testing by setting ExtendByEd25519ID in your configuration. This
2729 might make your traffic appear different than the traffic
2730 generated by other users, however. Implements part of ticket
2731 15056; part of proposal 220.
2732 - Relays now understand requests to extend to other relays by their
2733 Ed25519 identity keys. When an Ed25519 identity key is included in
2734 an EXTEND2 cell, the relay will only extend the circuit if the
2735 other relay can prove ownership of that identity. Implements part
2736 of ticket 15056; part of proposal 220.
2737 - Relays now use Ed25519 to prove their Ed25519 identities and to
2738 one another, and to clients. This algorithm is faster and more
2739 secure than the RSA-based handshake we've been doing until now.
2740 Implements the second big part of proposal 220; Closes
2743 o Major features (security):
2744 - Change the algorithm used to decide DNS TTLs on client and server
2745 side, to better resist DNS-based correlation attacks like the
2746 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
2747 Feamster. Now relays only return one of two possible DNS TTL
2748 values, and clients are willing to believe DNS TTL values up to 3
2749 hours long. Closes ticket 19769.
2751 o Major bugfixes (client, onion service, also in 0.2.9.9):
2752 - Fix a client-side onion service reachability bug, where multiple
2753 socks requests to an onion service (or a single slow request)
2754 could cause us to mistakenly mark some of the service's
2755 introduction points as failed, and we cache that failure so
2756 eventually we run out and can't reach the service. Also resolves a
2757 mysterious "Remote server sent bogus reason code 65021" log
2758 warning. The bug was introduced in ticket 17218, where we tried to
2759 remember the circuit end reason as a uint16_t, which mangled
2760 negative values. Partially fixes bug 21056 and fixes bug 20307;
2761 bugfix on 0.2.8.1-alpha.
2763 o Major bugfixes (crash, directory connections):
2764 - Fix a rare crash when sending a begin cell on a circuit whose
2765 linked directory connection had already been closed. Fixes bug
2766 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
2768 o Major bugfixes (directory authority):
2769 - During voting, when marking a relay as a probable sybil, do not
2770 clear its BadExit flag: sybils can still be bad in other ways
2771 too. (We still clear the other flags.) Fixes bug 21108; bugfix
2774 o Major bugfixes (DNS):
2775 - Fix a bug that prevented exit nodes from caching DNS records for
2776 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
2778 o Major bugfixes (IPv6 Exits):
2779 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
2780 any IPv6 addresses. Instead, only reject a port over IPv6 if the
2781 exit policy rejects that port on more than an IPv6 /16 of
2782 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
2783 which rejected a relay's own IPv6 address by default. Fixes bug
2784 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
2786 o Major bugfixes (parsing):
2787 - Fix an integer underflow bug when comparing malformed Tor
2788 versions. This bug could crash Tor when built with
2789 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
2790 0.2.9.8, which were built with -ftrapv by default. In other cases
2791 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
2792 on 0.0.8pre1. Found by OSS-Fuzz.
2793 - When parsing a malformed content-length field from an HTTP
2794 message, do not read off the end of the buffer. This bug was a
2795 potential remote denial-of-service attack against Tor clients and
2796 relays. A workaround was released in October 2016, to prevent this
2797 bug from crashing Tor. This is a fix for the underlying issue,
2798 which should no longer matter (if you applied the earlier patch).
2799 Fixes bug 20894; bugfix on 0.2.0.16-alpha. Bug found by fuzzing
2800 using AFL (http://lcamtuf.coredump.cx/afl/).
2802 o Major bugfixes (scheduler):
2803 - Actually compare circuit policies in ewma_cmp_cmux(). This bug
2804 caused the channel scheduler to behave more or less randomly,
2805 rather than preferring channels with higher-priority circuits.
2806 Fixes bug 20459; bugfix on 0.2.6.2-alpha.
2808 o Major bugfixes (security, also in 0.2.9.9):
2809 - Downgrade the "-ftrapv" option from "always on" to "only on when
2810 --enable-expensive-hardening is provided." This hardening option,
2811 like others, can turn survivable bugs into crashes--and having it
2812 on by default made a (relatively harmless) integer overflow bug
2813 into a denial-of-service bug. Fixes bug 21278 (TROVE-2017-001);
2814 bugfix on 0.2.9.1-alpha.
2816 o Minor feature (client):
2817 - Enable IPv6 traffic on the SocksPort by default. To disable this,
2818 a user will have to specify "NoIPv6Traffic". Closes ticket 21269.
2820 o Minor feature (fallback scripts):
2821 - Add a check_existing mode to updateFallbackDirs.py, which checks
2822 if fallbacks in the hard-coded list are working. Closes ticket
2823 20174. Patch by haxxpop.
2825 o Minor feature (protocol versioning):
2826 - Add new protocol version for proposal 224. HSIntro now advertises
2827 version "3-4" and HSDir version "1-2". Fixes ticket 20656.
2829 o Minor features (ciphersuite selection):
2830 - Allow relays to accept a wider range of ciphersuites, including
2831 chacha20-poly1305 and AES-CCM. Closes the other part of 15426.
2832 - Clients now advertise a list of ciphersuites closer to the ones
2833 preferred by Firefox. Closes part of ticket 15426.
2835 o Minor features (controller):
2836 - Add "GETINFO sr/current" and "GETINFO sr/previous" keys, to expose
2837 shared-random values to the controller. Closes ticket 19925.
2838 - When HSFETCH arguments cannot be parsed, say "Invalid argument"
2839 rather than "unrecognized." Closes ticket 20389; patch from
2842 o Minor features (controller, configuration):
2843 - Each of the *Port options, such as SocksPort, ORPort, ControlPort,
2844 and so on, now comes with a __*Port variant that will not be saved
2845 to the torrc file by the controller's SAVECONF command. This
2846 change allows TorBrowser to set up a single-use domain socket for
2847 each time it launches Tor. Closes ticket 20956.
2848 - The GETCONF command can now query options that may only be
2849 meaningful in context-sensitive lists. This allows the controller
2850 to query the mixed SocksPort/__SocksPort style options introduced
2851 in feature 20956. Implements ticket 21300.
2853 o Minor features (diagnostic, directory client):
2854 - Warn when we find an unexpected inconsistency in directory
2855 download status objects. Prevents some negative consequences of
2858 o Minor features (directory authorities):
2859 - Directory authorities now reject descriptors that claim to be
2860 malformed versions of Tor. Helps prevent exploitation of
2862 - Reject version numbers with components that exceed INT32_MAX.
2863 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
2864 Fixes bug 21450; bugfix on 0.0.8pre1.
2866 o Minor features (directory authority):
2867 - Add a new authority-only AuthDirTestEd25519LinkKeys option (on by
2868 default) to control whether authorities should try to probe relays
2869 by their Ed25519 link keys. This option will go away in a few
2870 releases--unless we encounter major trouble in our ed25519 link
2871 protocol rollout, in which case it will serve as a safety option.
2873 o Minor features (directory cache):
2874 - Relays and bridges will now refuse to serve the consensus they
2875 have if they know it is too old for a client to use. Closes
2878 o Minor features (ed25519 link handshake):
2879 - Advertise support for the ed25519 link handshake using the
2880 subprotocol-versions mechanism, so that clients can tell which
2881 relays can identity themselves by Ed25519 ID. Closes ticket 20552.
2883 o Minor features (entry guards):
2884 - Add UseEntryGuards to TEST_OPTIONS_DEFAULT_VALUES in order to not
2885 break regression tests.
2886 - Require UseEntryGuards when UseBridges is set, in order to make
2887 sure bridges aren't bypassed. Resolves ticket 20502.
2889 o Minor features (fallback directories):
2890 - Allow 3 fallback relays per operator, which is safe now that we
2891 are choosing 200 fallback relays. Closes ticket 20912.
2892 - Annotate updateFallbackDirs.py with the bandwidth and consensus
2893 weight for each candidate fallback. Closes ticket 20878.
2894 - Display the relay fingerprint when downloading consensuses from
2895 fallbacks. Closes ticket 20908.
2896 - Exclude relays affected by bug 20499 from the fallback list.
2897 Exclude relays from the fallback list if they are running versions
2898 known to be affected by bug 20499, or if in our tests they deliver
2899 a stale consensus (i.e. one that expired more than 24 hours ago).
2900 Closes ticket 20539.
2901 - Make it easier to change the output sort order of fallbacks.
2902 Closes ticket 20822.
2903 - Reduce the minimum fallback bandwidth to 1 MByte/s. Part of
2905 - Require fallback directories to have the same address and port for
2906 7 days (now that we have enough relays with this stability).
2907 Relays whose OnionOO stability timer is reset on restart by bug
2908 18050 should upgrade to Tor 0.2.8.7 or later, which has a fix for
2909 this issue. Closes ticket 20880; maintains short-term fix
2911 - Require fallbacks to have flags for 90% of the time (weighted
2912 decaying average), rather than 95%. This allows at least 73% of
2913 clients to bootstrap in the first 5 seconds without contacting an
2914 authority. Part of ticket 18828.
2915 - Select 200 fallback directories for each release. Closes
2918 o Minor features (fingerprinting resistance, authentication):
2919 - Extend the length of RSA keys used for TLS link authentication to
2920 2048 bits. (These weren't used for forward secrecy; for forward
2921 secrecy, we used P256.) Closes ticket 13752.
2923 o Minor features (geoip):
2924 - Update geoip and geoip6 to the April 4 2017 Maxmind GeoLite2
2927 o Minor features (geoip, also in 0.2.9.9):
2928 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
2931 o Minor features (infrastructure):
2932 - Implement smartlist_add_strdup() function. Replaces the use of
2933 smartlist_add(sl, tor_strdup(str)). Closes ticket 20048.
2935 o Minor features (linting):
2936 - Enhance the changes file linter to warn on Tor versions that are
2937 prefixed with "tor-". Closes ticket 21096.
2939 o Minor features (logging):
2940 - In several places, describe unset ed25519 keys as "<unset>",
2941 rather than the scary "AAAAAAAA...AAA". Closes ticket 21037.
2943 o Minor features (portability, compilation):
2944 - Autoconf now checks to determine if OpenSSL structures are opaque,
2945 instead of explicitly checking for OpenSSL version numbers. Part
2947 - Support building with recent LibreSSL code that uses opaque
2948 structures. Closes ticket 21359.
2950 o Minor features (relay):
2951 - We now allow separation of exit and relay traffic to different
2952 source IP addresses, using the OutboundBindAddressExit and
2953 OutboundBindAddressOR options respectively. Closes ticket 17975.
2954 Written by Michael Sonntag.
2956 o Minor features (reliability, crash):
2957 - Try better to detect problems in buffers where they might grow (or
2958 think they have grown) over 2 GB in size. Diagnostic for
2961 o Minor features (testing):
2962 - During 'make test-network-all', if tor logs any warnings, ask
2963 chutney to output them. Requires a recent version of chutney with
2964 the 21572 patch. Implements 21570.
2966 o Minor bugfix (control protocol):
2967 - The reply to a "GETINFO config/names" request via the control
2968 protocol now spells the type "Dependent" correctly. This is a
2969 breaking change in the control protocol. (The field seems to be
2970 ignored by the most common known controllers.) Fixes bug 18146;
2971 bugfix on 0.1.1.4-alpha.
2972 - The GETINFO extra-info/digest/<digest> command was broken because
2973 of a wrong base16 decode return value check, introduced when
2974 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
2976 o Minor bugfix (logging):
2977 - Don't recommend the use of Tor2web in non-anonymous mode.
2978 Recommending Tor2web is a bad idea because the client loses all
2979 anonymity. Tor2web should only be used in specific cases by users
2980 who *know* and understand the issues. Fixes bug 21294; bugfix
2983 o Minor bugfixes (bug resilience):
2984 - Fix an unreachable size_t overflow in base64_decode(). Fixes bug
2985 19222; bugfix on 0.2.0.9-alpha. Found by Guido Vranken; fixed by
2986 Hans Jerry Illikainen.
2988 o Minor bugfixes (build):
2989 - Replace obsolete Autoconf macros with their modern equivalent and
2990 prevent similar issues in the future. Fixes bug 20990; bugfix
2993 o Minor bugfixes (certificate expiration time):
2994 - Avoid using link certificates that don't become valid till some
2995 time in the future. Fixes bug 21420; bugfix on 0.2.4.11-alpha
2997 o Minor bugfixes (client):
2998 - Always recover from failures in extend_info_from_node(), in an
2999 attempt to prevent any recurrence of bug 21242. Fixes bug 21372;
3000 bugfix on 0.2.3.1-alpha.
3001 - When clients that use bridges start up with a cached consensus on
3002 disk, they were ignoring it and downloading a new one. Now they
3003 use the cached one. Fixes bug 20269; bugfix on 0.2.3.12-alpha.
3005 o Minor bugfixes (code correctness):
3006 - Repair a couple of (unreachable or harmless) cases of the risky
3007 comparison-by-subtraction pattern that caused bug 21278.
3009 o Minor bugfixes (config):
3010 - Don't assert on startup when trying to get the options list and
3011 LearnCircuitBuildTimeout is set to 0: we are currently parsing the
3012 options so of course they aren't ready yet. Fixes bug 21062;
3013 bugfix on 0.2.9.3-alpha.
3015 o Minor bugfixes (configuration):
3016 - Accept non-space whitespace characters after the severity level in
3017 the `Log` option. Fixes bug 19965; bugfix on 0.2.1.1-alpha.
3018 - Support "TByte" and "TBytes" units in options given in bytes.
3019 "TB", "terabyte(s)", "TBit(s)" and "terabit(s)" were already
3020 supported. Fixes bug 20622; bugfix on 0.2.0.14-alpha.
3022 o Minor bugfixes (configure, autoconf):
3023 - Rename the configure option --enable-expensive-hardening to
3024 --enable-fragile-hardening. Expensive hardening makes the tor
3025 daemon abort when some kinds of issues are detected. Thus, it
3026 makes tor more at risk of remote crashes but safer against RCE or
3027 heartbleed bug category. We now try to explain this issue in a
3028 message from the configure script. Fixes bug 21290; bugfix
3031 o Minor bugfixes (consensus weight):
3032 - Add new consensus method that initializes bw weights to 1 instead
3033 of 0. This prevents a zero weight from making it all the way to
3034 the end (happens in small testing networks) and causing an error.
3035 Fixes bug 14881; bugfix on 0.2.2.17-alpha.
3037 o Minor bugfixes (crash prevention):
3038 - Fix an (currently untriggerable, but potentially dangerous) crash
3039 bug when base32-encoding inputs whose sizes are not a multiple of
3040 5. Fixes bug 21894; bugfix on 0.2.9.1-alpha.
3042 o Minor bugfixes (dead code):
3043 - Remove a redundant check for PidFile changes at runtime in
3044 options_transition_allowed(): this check is already performed
3045 regardless of whether the sandbox is active. Fixes bug 21123;
3046 bugfix on 0.2.5.4-alpha.
3048 o Minor bugfixes (descriptors):
3049 - Correctly recognise downloaded full descriptors as valid, even
3050 when using microdescriptors as circuits. This affects clients with
3051 FetchUselessDescriptors set, and may affect directory authorities.
3052 Fixes bug 20839; bugfix on 0.2.3.2-alpha.
3054 o Minor bugfixes (directory mirrors):
3055 - Allow relays to use directory mirrors without a DirPort: these
3056 relays need to be contacted over their ORPorts using a begindir
3057 connection. Fixes one case of bug 20711; bugfix on 0.2.8.2-alpha.
3058 - Clarify the message logged when a remote relay is unexpectedly
3059 missing an ORPort or DirPort: users were confusing this with a
3060 local port. Fixes another case of bug 20711; bugfix
3063 o Minor bugfixes (directory system):
3064 - Bridges and relays now use microdescriptors (like clients do)
3065 rather than old-style router descriptors. Now bridges will blend
3066 in with clients in terms of the circuits they build. Fixes bug
3067 6769; bugfix on 0.2.3.2-alpha.
3068 - Download all consensus flavors, descriptors, and authority
3069 certificates when FetchUselessDescriptors is set, regardless of
3070 whether tor is a directory cache or not. Fixes bug 20667; bugfix
3071 on all recent tor versions.
3073 o Minor bugfixes (documentation):
3074 - Update the tor manual page to document every option that can not
3075 be changed while tor is running. Fixes bug 21122.
3077 o Minor bugfixes (ed25519 certificates):
3078 - Correctly interpret ed25519 certificates that would expire some
3079 time after 19 Jan 2038. Fixes bug 20027; bugfix on 0.2.7.2-alpha.
3081 o Minor bugfixes (fallback directories):
3082 - Avoid checking fallback candidates' DirPorts if they are down in
3083 OnionOO. When a relay operator has multiple relays, this
3084 prioritizes relays that are up over relays that are down. Fixes
3085 bug 20926; bugfix on 0.2.8.3-alpha.
3086 - Stop failing when OUTPUT_COMMENTS is True in updateFallbackDirs.py.
3087 Fixes bug 20877; bugfix on 0.2.8.3-alpha.
3088 - Stop failing when a relay has no uptime data in
3089 updateFallbackDirs.py. Fixes bug 20945; bugfix on 0.2.8.1-alpha.
3091 o Minor bugfixes (hidden service):
3092 - Clean up the code for expiring intro points with no associated
3093 circuits. It was causing, rarely, a service with some expiring
3094 introduction points to not open enough additional introduction
3095 points. Fixes part of bug 21302; bugfix on 0.2.7.2-alpha.
3096 - Resolve two possible underflows which could lead to creating and
3097 closing a lot of introduction point circuits in a non-stop loop.
3098 Fixes bug 21302; bugfix on 0.2.7.2-alpha.
3099 - Stop setting the torrc option HiddenServiceStatistics to "0" just
3100 because we're not a bridge or relay. Instead, we preserve whatever
3101 value the user set (or didn't set). Fixes bug 21150; bugfix
3104 o Minor bugfixes (hidden services):
3105 - Make hidden services check for failed intro point connections,
3106 even when they have exceeded their intro point creation limit.
3107 Fixes bug 21596; bugfix on 0.2.7.2-alpha. Reported by Alec Muffett.
3108 - Make hidden services with 8 to 10 introduction points check for
3109 failed circuits immediately after startup. Previously, they would
3110 wait for 5 minutes before performing their first checks. Fixes bug
3111 21594; bugfix on 0.2.3.9-alpha. Reported by Alec Muffett.
3112 - Stop ignoring misconfigured hidden services. Instead, refuse to
3113 start tor until the misconfigurations have been corrected. Fixes
3114 bug 20559; bugfix on multiple commits in 0.2.7.1-alpha
3117 o Minor bugfixes (IPv6):
3118 - Make IPv6-using clients try harder to find an IPv6 directory
3119 server. Fixes bug 20999; bugfix on 0.2.8.2-alpha.
3120 - When IPv6 addresses have not been downloaded yet (microdesc
3121 consensus documents don't list relay IPv6 addresses), use hard-
3122 coded addresses for authorities, fallbacks, and configured
3123 bridges. Now IPv6-only clients can use microdescriptors. Fixes bug
3124 20996; bugfix on b167e82 from 19608 in 0.2.8.5-alpha.
3126 o Minor bugfixes (memory leak at exit):
3127 - Fix a small harmless memory leak at exit of the previously unused
3128 RSA->Ed identity cross-certificate. Fixes bug 17779; bugfix
3131 o Minor bugfixes (onion services):
3132 - Allow the number of introduction points to be as low as 0, rather
3133 than as low as 3. Fixes bug 21033; bugfix on 0.2.7.2-alpha.
3135 o Minor bugfixes (portability):
3136 - Use "OpenBSD" compiler macro instead of "OPENBSD" or "__OpenBSD__".
3137 It is supported by OpenBSD itself, and also by most OpenBSD
3138 variants (such as Bitrig). Fixes bug 20980; bugfix
3141 o Minor bugfixes (portability, also in 0.2.9.9):
3142 - Avoid crashing when Tor is built using headers that contain
3143 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
3144 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
3146 - Fix Libevent detection on platforms without Libevent 1 headers
3147 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
3149 o Minor bugfixes (relay):
3150 - Avoid a double-marked-circuit warning that could happen when we
3151 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
3153 - Honor DataDirectoryGroupReadable when tor is a relay. Previously,
3154 initializing the keys would reset the DataDirectory to 0700
3155 instead of 0750 even if DataDirectoryGroupReadable was set to 1.
3156 Fixes bug 19953; bugfix on 0.0.2pre16. Patch by "redfish".
3158 o Minor bugfixes (testing):
3159 - Fix Raspbian build issues related to missing socket errno in
3160 test_util.c. Fixes bug 21116; bugfix on 0.2.8.2. Patch by "hein".
3161 - Remove undefined behavior from the backtrace generator by removing
3162 its signal handler. Fixes bug 21026; bugfix on 0.2.5.2-alpha.
3163 - Use bash in src/test/test-network.sh. This ensures we reliably
3164 call chutney's newer tools/test-network.sh when available. Fixes
3165 bug 21562; bugfix on 0.2.9.1-alpha.
3167 o Minor bugfixes (tor-resolve):
3168 - The tor-resolve command line tool now rejects hostnames over 255
3169 characters in length. Previously, it would silently truncate them,
3170 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
3171 Patch by "junglefowl".
3173 o Minor bugfixes (unit tests):
3174 - Allow the unit tests to pass even when DNS lookups of bogus
3175 addresses do not fail as expected. Fixes bug 20862 and 20863;
3176 bugfix on unit tests introduced in 0.2.8.1-alpha
3177 through 0.2.9.4-alpha.
3179 o Minor bugfixes (util):
3180 - When finishing writing a file to disk, if we were about to replace
3181 the file with the temporary file created before and we fail to
3182 replace it, remove the temporary file so it doesn't stay on disk.
3183 Fixes bug 20646; bugfix on 0.2.0.7-alpha. Patch by fk.
3185 o Minor bugfixes (Windows services):
3186 - Be sure to initialize the monotonic time subsystem before using
3187 it, even when running as an NT service. Fixes bug 21356; bugfix
3190 o Minor bugfixes (Windows):
3191 - Check for getpagesize before using it to mmap files. This fixes
3192 compilation in some MinGW environments. Fixes bug 20530; bugfix on
3193 0.1.2.1-alpha. Reported by "ice".
3195 o Code simplification and refactoring:
3196 - Abolish all global guard context in entrynodes.c; replace with new
3197 guard_selection_t structure as preparation for proposal 271.
3198 Closes ticket 19858.
3199 - Extract magic numbers in circuituse.c into defined variables.
3200 - Introduce rend_service_is_ephemeral() that tells if given onion
3201 service is ephemeral. Replace unclear NULL-checkings for service
3202 directory with this function. Closes ticket 20526.
3203 - Refactor circuit_is_available_for_use to remove unnecessary check.
3204 - Refactor circuit_predict_and_launch_new for readability and
3205 testability. Closes ticket 18873.
3206 - Refactor code to manipulate global_origin_circuit_list into
3207 separate functions. Closes ticket 20921.
3208 - Refactor large if statement in purpose_needs_anonymity to use
3209 switch statement instead. Closes part of ticket 20077.
3210 - Refactor the hashing API to return negative values for errors, as
3211 is done as throughout the codebase. Closes ticket 20717.
3212 - Remove data structures that were used to index or_connection
3213 objects by their RSA identity digests. These structures are fully
3214 redundant with the similar structures used in the
3215 channel abstraction.
3216 - Remove duplicate code in the channel_write_*cell() functions.
3217 Closes ticket 13827; patch from Pingl.
3218 - Remove redundant behavior of is_sensitive_dir_purpose, refactor to
3219 use only purpose_needs_anonymity. Closes part of ticket 20077.
3220 - The code to generate and parse EXTEND and EXTEND2 cells has been
3221 replaced with code automatically generated by the
3224 o Documentation (formatting):
3225 - Clean up formatting of tor.1 man page and HTML doc, where <pre>
3226 blocks were incorrectly appearing. Closes ticket 20885.
3228 o Documentation (man page):
3229 - Clarify many options in tor.1 and add some min/max values for
3230 HiddenService options. Closes ticket 21058.
3233 - Change '1' to 'weight_scale' in consensus bw weights calculation
3234 comments, as that is reality. Closes ticket 20273. Patch
3236 - Clarify that when ClientRejectInternalAddresses is enabled (which
3237 is the default), multicast DNS hostnames for machines on the local
3238 network (of the form *.local) are also rejected. Closes
3240 - Correct the value for AuthDirGuardBWGuarantee in the manpage, from
3241 250 KBytes to 2 MBytes. Fixes bug 20435; bugfix on 0.2.5.6-alpha.
3242 - Include the "TBits" unit in Tor's man page. Fixes part of bug
3243 20622; bugfix on 0.2.5.1-alpha.
3244 - Small fixes to the fuzzing documentation. Closes ticket 21472.
3245 - Stop the man page from incorrectly stating that HiddenServiceDir
3246 must already exist. Fixes 20486.
3247 - Update the description of the directory server options in the
3248 manual page, to clarify that a relay no longer needs to set
3249 DirPort in order to be a directory cache. Closes ticket 21720.
3252 - The AuthDirMaxServersPerAuthAddr option no longer exists: The same
3253 limit for relays running on a single IP applies to authority IP
3254 addresses as well as to non-authority IP addresses. Closes
3256 - The UseDirectoryGuards torrc option no longer exists: all users
3257 that use entry guards will also use directory guards. Related to
3258 proposal 271; implements part of ticket 20831.
3261 - Add tests for networkstatus_compute_bw_weights_v10.
3262 - Add unit tests circuit_predict_and_launch_new.
3263 - Extract dummy_origin_circuit_new so it can be used by other
3265 - New unit tests for tor_htonll(). Closes ticket 19563. Patch
3266 from "overcaffeinated".
3267 - Perform the coding style checks when running the tests and fail
3268 when coding style violations are found. Closes ticket 5500.
3271 Changes in version 0.2.8.13 - 2017-03-03
3272 Tor 0.2.8.13 backports a security fix from later Tor
3273 releases. Anybody running Tor 0.2.8.12 or earlier should upgrade to this
3274 this release, if for some reason they cannot upgrade to a later
3275 release series, and if they build Tor with the --enable-expensive-hardening
3278 Note that support for Tor 0.2.8.x is ending next year: we will not issue
3279 any fixes for the Tor 0.2.8.x series after 1 Jan 2018. If you need
3280 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
3282 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
3283 - Fix an integer underflow bug when comparing malformed Tor
3284 versions. This bug could crash Tor when built with
3285 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
3286 0.2.9.8, which were built with -ftrapv by default. In other cases
3287 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
3288 on 0.0.8pre1. Found by OSS-Fuzz.
3290 o Minor features (geoip):
3291 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
3295 Changes in version 0.2.7.7 - 2017-03-03
3296 Tor 0.2.7.7 backports a number of security fixes from later Tor
3297 releases. Anybody running Tor 0.2.7.6 or earlier should upgrade to
3298 this release, if for some reason they cannot upgrade to a later
3301 Note that support for Tor 0.2.7.x is ending this year: we will not issue
3302 any fixes for the Tor 0.2.7.x series after 1 August 2017. If you need
3303 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
3305 o Directory authority changes (backport from 0.2.8.5-rc):
3306 - Urras is no longer a directory authority. Closes ticket 19271.
3308 o Directory authority changes (backport from 0.2.9.2-alpha):
3309 - The "Tonga" bridge authority has been retired; the new bridge
3310 authority is "Bifroest". Closes tickets 19728 and 19690.
3312 o Directory authority key updates (backport from 0.2.8.1-alpha):
3313 - Update the V3 identity key for the dannenberg directory authority:
3314 it was changed on 18 November 2015. Closes task 17906. Patch
3317 o Major bugfixes (parsing, security, backport from 0.2.9.8):
3318 - Fix a bug in parsing that could cause clients to read a single
3319 byte past the end of an allocated region. This bug could be used
3320 to cause hardened clients (built with --enable-expensive-hardening)
3321 to crash if they tried to visit a hostile hidden service. Non-
3322 hardened clients are only affected depending on the details of
3323 their platform's memory allocator. Fixes bug 21018; bugfix on
3324 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
3325 2016-12-002 and as CVE-2016-1254.
3327 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
3328 - Stop a crash that could occur when a client running with DNSPort
3329 received a query with multiple address types, and the first
3330 address type was not supported. Found and fixed by Scott Dial.
3331 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
3332 - Prevent a class of security bugs caused by treating the contents
3333 of a buffer chunk as if they were a NUL-terminated string. At
3334 least one such bug seems to be present in all currently used
3335 versions of Tor, and would allow an attacker to remotely crash
3336 most Tor instances, especially those compiled with extra compiler
3337 hardening. With this defense in place, such bugs can't crash Tor,
3338 though we should still fix them as they occur. Closes ticket
3339 20384 (TROVE-2016-10-001).
3341 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
3342 - Avoid a difficult-to-trigger heap corruption attack when extending
3343 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
3344 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
3345 Reported by Guido Vranken.
3347 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
3348 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
3349 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
3351 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
3352 - If OpenSSL fails to generate an RSA key, do not retain a dangling
3353 pointer to the previous (uninitialized) key value. The impact here
3354 should be limited to a difficult-to-trigger crash, if OpenSSL is
3355 running an engine that makes key generation failures possible, or
3356 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
3357 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
3360 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
3361 - Fix an integer underflow bug when comparing malformed Tor
3362 versions. This bug could crash Tor when built with
3363 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
3364 0.2.9.8, which were built with -ftrapv by default. In other cases
3365 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
3366 on 0.0.8pre1. Found by OSS-Fuzz.
3368 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
3369 - Make memwipe() do nothing when passed a NULL pointer or buffer of
3370 zero size. Check size argument to memwipe() for underflow. Fixes
3371 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
3374 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
3375 - Make Tor survive errors involving connections without a
3376 corresponding event object. Previously we'd fail with an
3377 assertion; now we produce a log message. Related to bug 16248.
3379 o Minor features (geoip):
3380 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
3384 Changes in version 0.2.6.11 - 2017-03-03
3385 Tor 0.2.6.11 backports a number of security fixes from later Tor
3386 releases. Anybody running Tor 0.2.6.10 or earlier should upgrade to
3387 this release, if for some reason they cannot upgrade to a later
3390 Note that support for Tor 0.2.6.x is ending this year: we will not issue
3391 any fixes for the Tor 0.2.6.x series after 1 August 2017. If you need
3392 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
3394 o Directory authority changes (backport from 0.2.8.5-rc):
3395 - Urras is no longer a directory authority. Closes ticket 19271.
3397 o Directory authority changes (backport from 0.2.9.2-alpha):
3398 - The "Tonga" bridge authority has been retired; the new bridge
3399 authority is "Bifroest". Closes tickets 19728 and 19690.
3401 o Directory authority key updates (backport from 0.2.8.1-alpha):
3402 - Update the V3 identity key for the dannenberg directory authority:
3403 it was changed on 18 November 2015. Closes task 17906. Patch
3406 o Major features (security fixes, backport from 0.2.9.4-alpha):
3407 - Prevent a class of security bugs caused by treating the contents
3408 of a buffer chunk as if they were a NUL-terminated string. At
3409 least one such bug seems to be present in all currently used
3410 versions of Tor, and would allow an attacker to remotely crash
3411 most Tor instances, especially those compiled with extra compiler
3412 hardening. With this defense in place, such bugs can't crash Tor,
3413 though we should still fix them as they occur. Closes ticket
3414 20384 (TROVE-2016-10-001).
3416 o Major bugfixes (parsing, security, backport from 0.2.9.8):
3417 - Fix a bug in parsing that could cause clients to read a single
3418 byte past the end of an allocated region. This bug could be used
3419 to cause hardened clients (built with --enable-expensive-hardening)
3420 to crash if they tried to visit a hostile hidden service. Non-
3421 hardened clients are only affected depending on the details of
3422 their platform's memory allocator. Fixes bug 21018; bugfix on
3423 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
3424 2016-12-002 and as CVE-2016-1254.
3426 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
3427 - Stop a crash that could occur when a client running with DNSPort
3428 received a query with multiple address types, and the first
3429 address type was not supported. Found and fixed by Scott Dial.
3430 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
3432 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
3433 - Fix an error that could cause us to read 4 bytes before the
3434 beginning of an openssl string. This bug could be used to cause
3435 Tor to crash on systems with unusual malloc implementations, or
3436 systems with unusual hardening installed. Fixes bug 17404; bugfix
3439 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
3440 - Avoid a difficult-to-trigger heap corruption attack when extending
3441 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
3442 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
3443 Reported by Guido Vranken.
3445 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
3446 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
3447 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
3449 o Major bugfixes (guard selection, backport from 0.2.7.6):
3450 - Actually look at the Guard flag when selecting a new directory
3451 guard. When we implemented the directory guard design, we
3452 accidentally started treating all relays as if they have the Guard
3453 flag during guard selection, leading to weaker anonymity and worse
3454 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
3457 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
3458 - If OpenSSL fails to generate an RSA key, do not retain a dangling
3459 pointer to the previous (uninitialized) key value. The impact here
3460 should be limited to a difficult-to-trigger crash, if OpenSSL is
3461 running an engine that makes key generation failures possible, or
3462 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
3463 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
3466 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
3467 - Fix an integer underflow bug when comparing malformed Tor
3468 versions. This bug could crash Tor when built with
3469 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
3470 0.2.9.8, which were built with -ftrapv by default. In other cases
3471 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
3472 on 0.0.8pre1. Found by OSS-Fuzz.
3474 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
3475 - Make memwipe() do nothing when passed a NULL pointer or buffer of
3476 zero size. Check size argument to memwipe() for underflow. Fixes
3477 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
3480 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
3481 - Make Tor survive errors involving connections without a
3482 corresponding event object. Previously we'd fail with an
3483 assertion; now we produce a log message. Related to bug 16248.
3485 o Minor features (geoip):
3486 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
3489 o Minor bugfixes (compilation, backport from 0.2.7.6):
3490 - Fix a compilation warning with Clang 3.6: Do not check the
3491 presence of an address which can never be NULL. Fixes bug 17781.
3494 Changes in version 0.2.5.13 - 2017-03-03
3495 Tor 0.2.5.13 backports a number of security fixes from later Tor
3496 releases. Anybody running Tor 0.2.5.13 or earlier should upgrade to
3497 this release, if for some reason they cannot upgrade to a later
3500 Note that support for Tor 0.2.5.x is ending next year: we will not issue
3501 any fixes for the Tor 0.2.5.x series after 1 May 2018. If you need
3502 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
3504 o Directory authority changes (backport from 0.2.8.5-rc):
3505 - Urras is no longer a directory authority. Closes ticket 19271.
3507 o Directory authority changes (backport from 0.2.9.2-alpha):
3508 - The "Tonga" bridge authority has been retired; the new bridge
3509 authority is "Bifroest". Closes tickets 19728 and 19690.
3511 o Directory authority key updates (backport from 0.2.8.1-alpha):
3512 - Update the V3 identity key for the dannenberg directory authority:
3513 it was changed on 18 November 2015. Closes task 17906. Patch
3516 o Major features (security fixes, backport from 0.2.9.4-alpha):
3517 - Prevent a class of security bugs caused by treating the contents
3518 of a buffer chunk as if they were a NUL-terminated string. At
3519 least one such bug seems to be present in all currently used
3520 versions of Tor, and would allow an attacker to remotely crash
3521 most Tor instances, especially those compiled with extra compiler
3522 hardening. With this defense in place, such bugs can't crash Tor,
3523 though we should still fix them as they occur. Closes ticket
3524 20384 (TROVE-2016-10-001).
3526 o Major bugfixes (parsing, security, backport from 0.2.9.8):
3527 - Fix a bug in parsing that could cause clients to read a single
3528 byte past the end of an allocated region. This bug could be used
3529 to cause hardened clients (built with --enable-expensive-hardening)
3530 to crash if they tried to visit a hostile hidden service. Non-
3531 hardened clients are only affected depending on the details of
3532 their platform's memory allocator. Fixes bug 21018; bugfix on
3533 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
3534 2016-12-002 and as CVE-2016-1254.
3536 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
3537 - Stop a crash that could occur when a client running with DNSPort
3538 received a query with multiple address types, and the first
3539 address type was not supported. Found and fixed by Scott Dial.
3540 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
3542 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
3543 - Fix an error that could cause us to read 4 bytes before the
3544 beginning of an openssl string. This bug could be used to cause
3545 Tor to crash on systems with unusual malloc implementations, or
3546 systems with unusual hardening installed. Fixes bug 17404; bugfix
3549 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
3550 - Avoid a difficult-to-trigger heap corruption attack when extending
3551 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
3552 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
3553 Reported by Guido Vranken.
3555 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
3556 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
3557 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
3559 o Major bugfixes (guard selection, backport from 0.2.7.6):
3560 - Actually look at the Guard flag when selecting a new directory
3561 guard. When we implemented the directory guard design, we
3562 accidentally started treating all relays as if they have the Guard
3563 flag during guard selection, leading to weaker anonymity and worse
3564 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
3567 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
3568 - If OpenSSL fails to generate an RSA key, do not retain a dangling
3569 pointer to the previous (uninitialized) key value. The impact here
3570 should be limited to a difficult-to-trigger crash, if OpenSSL is
3571 running an engine that makes key generation failures possible, or
3572 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
3573 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
3576 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
3577 - Fix an integer underflow bug when comparing malformed Tor
3578 versions. This bug could crash Tor when built with
3579 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
3580 0.2.9.8, which were built with -ftrapv by default. In other cases
3581 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
3582 on 0.0.8pre1. Found by OSS-Fuzz.
3584 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
3585 - Make memwipe() do nothing when passed a NULL pointer or buffer of
3586 zero size. Check size argument to memwipe() for underflow. Fixes
3587 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
3590 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
3591 - Make Tor survive errors involving connections without a
3592 corresponding event object. Previously we'd fail with an
3593 assertion; now we produce a log message. Related to bug 16248.
3595 o Minor features (geoip):
3596 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
3599 o Minor bugfixes (compilation, backport from 0.2.7.6):
3600 - Fix a compilation warning with Clang 3.6: Do not check the
3601 presence of an address which can never be NULL. Fixes bug 17781.
3603 o Minor bugfixes (crypto error-handling, backport from 0.2.7.2-alpha):
3604 - Check for failures from crypto_early_init, and refuse to continue.
3605 A previous typo meant that we could keep going with an
3606 uninitialized crypto library, and would have OpenSSL initialize
3607 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
3608 when implementing ticket 4900. Patch by "teor".
3610 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
3611 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
3612 a client authorized hidden service. Fixes bug 15823; bugfix
3616 Changes in version 0.2.4.28 - 2017-03-03
3617 Tor 0.2.4.28 backports a number of security fixes from later Tor
3618 releases. Anybody running Tor 0.2.4.27 or earlier should upgrade to
3619 this release, if for some reason they cannot upgrade to a later
3622 Note that support for Tor 0.2.4.x is ending soon: we will not issue
3623 any fixes for the Tor 0.2.4.x series after 1 August 2017. If you need
3624 a Tor release series with long-term support, we recommend Tor 0.2.9.x.
3626 o Directory authority changes (backport from 0.2.8.5-rc):
3627 - Urras is no longer a directory authority. Closes ticket 19271.
3629 o Directory authority changes (backport from 0.2.9.2-alpha):
3630 - The "Tonga" bridge authority has been retired; the new bridge
3631 authority is "Bifroest". Closes tickets 19728 and 19690.
3633 o Directory authority key updates (backport from 0.2.8.1-alpha):
3634 - Update the V3 identity key for the dannenberg directory authority:
3635 it was changed on 18 November 2015. Closes task 17906. Patch
3638 o Major features (security fixes, backport from 0.2.9.4-alpha):
3639 - Prevent a class of security bugs caused by treating the contents
3640 of a buffer chunk as if they were a NUL-terminated string. At
3641 least one such bug seems to be present in all currently used
3642 versions of Tor, and would allow an attacker to remotely crash
3643 most Tor instances, especially those compiled with extra compiler
3644 hardening. With this defense in place, such bugs can't crash Tor,
3645 though we should still fix them as they occur. Closes ticket
3646 20384 (TROVE-2016-10-001).
3648 o Major bugfixes (parsing, security, backport from 0.2.9.8):
3649 - Fix a bug in parsing that could cause clients to read a single
3650 byte past the end of an allocated region. This bug could be used
3651 to cause hardened clients (built with --enable-expensive-hardening)
3652 to crash if they tried to visit a hostile hidden service. Non-
3653 hardened clients are only affected depending on the details of
3654 their platform's memory allocator. Fixes bug 21018; bugfix on
3655 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
3656 2016-12-002 and as CVE-2016-1254.
3658 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
3659 - Fix an error that could cause us to read 4 bytes before the
3660 beginning of an openssl string. This bug could be used to cause
3661 Tor to crash on systems with unusual malloc implementations, or
3662 systems with unusual hardening installed. Fixes bug 17404; bugfix
3665 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
3666 - Avoid a difficult-to-trigger heap corruption attack when extending
3667 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
3668 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
3669 Reported by Guido Vranken.
3671 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
3672 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
3673 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
3675 o Major bugfixes (guard selection, backport from 0.2.7.6):
3676 - Actually look at the Guard flag when selecting a new directory
3677 guard. When we implemented the directory guard design, we
3678 accidentally started treating all relays as if they have the Guard
3679 flag during guard selection, leading to weaker anonymity and worse
3680 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
3683 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
3684 - If OpenSSL fails to generate an RSA key, do not retain a dangling
3685 pointer to the previous (uninitialized) key value. The impact here
3686 should be limited to a difficult-to-trigger crash, if OpenSSL is
3687 running an engine that makes key generation failures possible, or
3688 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
3689 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
3692 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
3693 - Fix an integer underflow bug when comparing malformed Tor
3694 versions. This bug could crash Tor when built with
3695 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
3696 0.2.9.8, which were built with -ftrapv by default. In other cases
3697 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
3698 on 0.0.8pre1. Found by OSS-Fuzz.
3700 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
3701 - Make memwipe() do nothing when passed a NULL pointer or buffer of
3702 zero size. Check size argument to memwipe() for underflow. Fixes
3703 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
3706 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
3707 - Make Tor survive errors involving connections without a
3708 corresponding event object. Previously we'd fail with an
3709 assertion; now we produce a log message. Related to bug 16248.
3711 o Minor features (DoS-resistance, backport from 0.2.7.1-alpha):
3712 - Make it harder for attackers to overload hidden services with
3713 introductions, by blocking multiple introduction requests on the
3714 same circuit. Resolves ticket 15515.
3716 o Minor features (geoip):
3717 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
3720 o Minor bugfixes (compilation, backport from 0.2.7.6):
3721 - Fix a compilation warning with Clang 3.6: Do not check the
3722 presence of an address which can never be NULL. Fixes bug 17781.
3724 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
3725 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
3726 a client authorized hidden service. Fixes bug 15823; bugfix
3730 Changes in version 0.2.9.10 - 2017-03-01
3731 Tor 0.2.9.10 backports a security fix from later Tor release. It also
3732 includes fixes for some major issues affecting directory authorities,
3733 LibreSSL compatibility, and IPv6 correctness.
3735 The Tor 0.2.9.x release series is now marked as a long-term-support
3736 series. We intend to backport security fixes to 0.2.9.x until at
3737 least January of 2020.
3739 o Major bugfixes (directory authority, 0.3.0.3-alpha):
3740 - During voting, when marking a relay as a probable sybil, do not
3741 clear its BadExit flag: sybils can still be bad in other ways
3742 too. (We still clear the other flags.) Fixes bug 21108; bugfix
3745 o Major bugfixes (IPv6 Exits, backport from 0.3.0.3-alpha):
3746 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
3747 any IPv6 addresses. Instead, only reject a port over IPv6 if the
3748 exit policy rejects that port on more than an IPv6 /16 of
3749 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
3750 which rejected a relay's own IPv6 address by default. Fixes bug
3751 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
3753 o Major bugfixes (parsing, also in 0.3.0.4-rc):
3754 - Fix an integer underflow bug when comparing malformed Tor
3755 versions. This bug could crash Tor when built with
3756 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
3757 0.2.9.8, which were built with -ftrapv by default. In other cases
3758 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
3759 on 0.0.8pre1. Found by OSS-Fuzz.
3761 o Minor features (directory authorities, also in 0.3.0.4-rc):
3762 - Directory authorities now reject descriptors that claim to be
3763 malformed versions of Tor. Helps prevent exploitation of
3765 - Reject version numbers with components that exceed INT32_MAX.
3766 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
3767 Fixes bug 21450; bugfix on 0.0.8pre1.
3769 o Minor features (geoip):
3770 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
3773 o Minor features (portability, compilation, backport from 0.3.0.3-alpha):
3774 - Autoconf now checks to determine if OpenSSL structures are opaque,
3775 instead of explicitly checking for OpenSSL version numbers. Part
3777 - Support building with recent LibreSSL code that uses opaque
3778 structures. Closes ticket 21359.
3780 o Minor bugfixes (code correctness, also in 0.3.0.4-rc):
3781 - Repair a couple of (unreachable or harmless) cases of the risky
3782 comparison-by-subtraction pattern that caused bug 21278.
3784 o Minor bugfixes (tor-resolve, backport from 0.3.0.3-alpha):
3785 - The tor-resolve command line tool now rejects hostnames over 255
3786 characters in length. Previously, it would silently truncate them,
3787 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
3788 Patch by "junglefowl".
3791 Changes in version 0.2.9.9 - 2017-01-23
3792 Tor 0.2.9.9 fixes a denial-of-service bug where an attacker could
3793 cause relays and clients to crash, even if they were not built with
3794 the --enable-expensive-hardening option. This bug affects all 0.2.9.x
3795 versions, and also affects 0.3.0.1-alpha: all relays running an affected
3796 version should upgrade.
3798 This release also resolves a client-side onion service reachability
3799 bug, and resolves a pair of small portability issues.
3801 o Major bugfixes (security):
3802 - Downgrade the "-ftrapv" option from "always on" to "only on when
3803 --enable-expensive-hardening is provided." This hardening option,
3804 like others, can turn survivable bugs into crashes -- and having
3805 it on by default made a (relatively harmless) integer overflow bug
3806 into a denial-of-service bug. Fixes bug 21278 (TROVE-2017-001);
3807 bugfix on 0.2.9.1-alpha.
3809 o Major bugfixes (client, onion service):
3810 - Fix a client-side onion service reachability bug, where multiple
3811 socks requests to an onion service (or a single slow request)
3812 could cause us to mistakenly mark some of the service's
3813 introduction points as failed, and we cache that failure so
3814 eventually we run out and can't reach the service. Also resolves a
3815 mysterious "Remote server sent bogus reason code 65021" log
3816 warning. The bug was introduced in ticket 17218, where we tried to
3817 remember the circuit end reason as a uint16_t, which mangled
3818 negative values. Partially fixes bug 21056 and fixes bug 20307;
3819 bugfix on 0.2.8.1-alpha.
3821 o Minor features (geoip):
3822 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
3825 o Minor bugfixes (portability):
3826 - Avoid crashing when Tor is built using headers that contain
3827 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
3828 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
3830 - Fix Libevent detection on platforms without Libevent 1 headers
3831 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
3834 Changes in version 0.2.8.12 - 2016-12-19
3835 Tor 0.2.8.12 backports a fix for a medium-severity issue (bug 21018
3836 below) where Tor clients could crash when attempting to visit a
3837 hostile hidden service. Clients are recommended to upgrade as packages
3838 become available for their systems.
3840 It also includes an updated list of fallback directories, backported
3843 Now that the Tor 0.2.9 series is stable, only major bugfixes will be
3844 backported to 0.2.8 in the future.
3846 o Major bugfixes (parsing, security, backported from 0.2.9.8):
3847 - Fix a bug in parsing that could cause clients to read a single
3848 byte past the end of an allocated region. This bug could be used
3849 to cause hardened clients (built with --enable-expensive-hardening)
3850 to crash if they tried to visit a hostile hidden service. Non-
3851 hardened clients are only affected depending on the details of
3852 their platform's memory allocator. Fixes bug 21018; bugfix on
3853 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
3854 2016-12-002 and as CVE-2016-1254.
3856 o Minor features (fallback directory list, backported from 0.2.9.8):
3857 - Replace the 81 remaining fallbacks of the 100 originally
3858 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
3859 fallbacks (123 new, 54 existing, 27 removed) generated in December
3860 2016. Resolves ticket 20170.
3862 o Minor features (geoip, backported from 0.2.9.7-rc):
3863 - Update geoip and geoip6 to the December 7 2016 Maxmind GeoLite2
3867 Changes in version 0.2.9.8 - 2016-12-19
3868 Tor 0.2.9.8 is the first stable release of the Tor 0.2.9 series.
3870 The Tor 0.2.9 series makes mandatory a number of security features
3871 that were formerly optional. It includes support for a new shared-
3872 randomness protocol that will form the basis for next generation
3873 hidden services, includes a single-hop hidden service mode for
3874 optimizing .onion services that don't actually want to be hidden,
3875 tries harder not to overload the directory authorities with excessive
3876 downloads, and supports a better protocol versioning scheme for
3877 improved compatibility with other implementations of the Tor protocol.
3879 And of course, there are numerous other bugfixes and improvements.
3881 This release also includes a fix for a medium-severity issue (bug
3882 21018 below) where Tor clients could crash when attempting to visit a
3883 hostile hidden service. Clients are recommended to upgrade as packages
3884 become available for their systems.
3886 Below are listed the changes since Tor 0.2.8.11. For a list of
3887 changes since 0.2.9.7-rc, see the ChangeLog file.
3889 o New system requirements:
3890 - When building with OpenSSL, Tor now requires version 1.0.1 or
3891 later. OpenSSL 1.0.0 and earlier are no longer supported by the
3892 OpenSSL team, and should not be used. Closes ticket 20303.
3893 - Tor now requires Libevent version 2.0.10-stable or later. Older
3894 versions of Libevent have less efficient backends for several
3895 platforms, and lack the DNS code that we use for our server-side
3896 DNS support. This implements ticket 19554.
3897 - Tor now requires zlib version 1.2 or later, for security,
3898 efficiency, and (eventually) gzip support. (Back when we started,
3899 zlib 1.1 and zlib 1.0 were still found in the wild. 1.2 was
3900 released in 2003. We recommend the latest version.)
3902 o Deprecated features:
3903 - A number of DNS-cache-related sub-options for client ports are now
3904 deprecated for security reasons, and may be removed in a future
3905 version of Tor. (We believe that client-side DNS caching is a bad
3906 idea for anonymity, and you should not turn it on.) The options
3907 are: CacheDNS, CacheIPv4DNS, CacheIPv6DNS, UseDNSCache,
3908 UseIPv4Cache, and UseIPv6Cache.
3909 - A number of options are deprecated for security reasons, and may
3910 be removed in a future version of Tor. The options are:
3911 AllowDotExit, AllowInvalidNodes, AllowSingleHopCircuits,
3912 AllowSingleHopExits, ClientDNSRejectInternalAddresses,
3913 CloseHSClientCircuitsImmediatelyOnTimeout,
3914 CloseHSServiceRendCircuitsImmediatelyOnTimeout,
3915 ExcludeSingleHopRelays, FastFirstHopPK, TLSECGroup,
3916 UseNTorHandshake, and WarnUnsafeSocks.
3917 - The *ListenAddress options are now deprecated as unnecessary: the
3918 corresponding *Port options should be used instead. These options
3919 may someday be removed. The affected options are:
3920 ControlListenAddress, DNSListenAddress, DirListenAddress,
3921 NATDListenAddress, ORListenAddress, SocksListenAddress,
3922 and TransListenAddress.
3924 o Major bugfixes (parsing, security, new since 0.2.9.7-rc):
3925 - Fix a bug in parsing that could cause clients to read a single
3926 byte past the end of an allocated region. This bug could be used
3927 to cause hardened clients (built with --enable-expensive-hardening)
3928 to crash if they tried to visit a hostile hidden service. Non-
3929 hardened clients are only affected depending on the details of
3930 their platform's memory allocator. Fixes bug 21018; bugfix on
3931 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
3932 2016-12-002 and as CVE-2016-1254.
3934 o Major features (build, hardening):
3935 - Tor now builds with -ftrapv by default on compilers that support
3936 it. This option detects signed integer overflow (which C forbids),
3937 and turns it into a hard-failure. We do not apply this option to
3938 code that needs to run in constant time to avoid side-channels;
3939 instead, we use -fwrapv in that code. Closes ticket 17983.
3940 - When --enable-expensive-hardening is selected, stop applying the
3941 clang/gcc sanitizers to code that needs to run in constant time.
3942 Although we are aware of no introduced side-channels, we are not
3943 able to prove that there are none. Related to ticket 17983.
3945 o Major features (circuit building, security):
3946 - Authorities, relays, and clients now require ntor keys in all
3947 descriptors, for all hops (except for rare hidden service protocol
3948 cases), for all circuits, and for all other roles. Part of
3950 - Authorities, relays, and clients only use ntor, except for
3951 rare cases in the hidden service protocol. Part of ticket 19163.
3953 o Major features (compilation):
3954 - Our big list of extra GCC warnings is now enabled by default when
3955 building with GCC (or with anything like Clang that claims to be
3956 GCC-compatible). To make all warnings into fatal compilation
3957 errors, pass --enable-fatal-warnings to configure. Closes
3959 - Use the Autoconf macro AC_USE_SYSTEM_EXTENSIONS to automatically
3960 turn on C and POSIX extensions. (Previously, we attempted to do
3961 this on an ad hoc basis.) Closes ticket 19139.
3963 o Major features (directory authorities, hidden services):
3964 - Directory authorities can now perform the shared randomness
3965 protocol specified by proposal 250. Using this protocol, directory
3966 authorities generate a global fresh random value every day. In the
3967 future, this value will be used by hidden services to select
3968 HSDirs. This release implements the directory authority feature;
3969 the hidden service side will be implemented in the future as part
3970 of proposal 224. Resolves ticket 16943; implements proposal 250.
3972 o Major features (downloading, random exponential backoff):
3973 - When we fail to download an object from a directory service, wait
3974 for an (exponentially increasing) randomized amount of time before
3975 retrying, rather than a fixed interval as we did before. This
3976 prevents a group of Tor instances from becoming too synchronized,
3977 or a single Tor instance from becoming too predictable, in its
3978 download schedule. Closes ticket 15942.
3980 o Major features (resource management):
3981 - Tor can now notice it is about to run out of sockets, and
3982 preemptively close connections of lower priority. (This feature is
3983 off by default for now, since the current prioritizing method is
3984 yet not mature enough. You can enable it by setting
3985 "DisableOOSCheck 0", but watch out: it might close some sockets
3986 you would rather have it keep.) Closes ticket 18640.
3988 o Major features (single-hop "hidden" services):
3989 - Add experimental HiddenServiceSingleHopMode and
3990 HiddenServiceNonAnonymousMode options. When both are set to 1,
3991 every hidden service on that Tor instance becomes a non-anonymous
3992 Single Onion Service. Single Onions make one-hop (direct)
3993 connections to their introduction and rendezvous points. One-hop
3994 circuits make Single Onion servers easily locatable, but clients
3995 remain location-anonymous. This is compatible with the existing
3996 hidden service implementation, and works on the current Tor
3997 network without any changes to older relays or clients. Implements
3998 proposal 260, completes ticket 17178. Patch by teor and asn.
4000 o Major features (subprotocol versions):
4001 - Tor directory authorities now vote on a set of recommended
4002 "subprotocol versions", and on a set of required subprotocol
4003 versions. Clients and relays that lack support for a _required_
4004 subprotocol version will not start; those that lack support for a
4005 _recommended_ subprotocol version will warn the user to upgrade.
4006 This change allows compatible implementations of the Tor protocol(s)
4007 to exist without pretending to be 100% bug-compatible with
4008 particular releases of Tor itself. Closes ticket 19958; implements
4009 part of proposal 264.
4011 o Major bugfixes (circuit building):
4012 - Hidden service client-to-intro-point and service-to-rendezvous-
4013 point circuits use the TAP key supplied by the protocol, to avoid
4014 epistemic attacks. Fixes bug 19163; bugfix on 0.2.4.18-rc.
4016 o Major bugfixes (download scheduling):
4017 - Avoid resetting download status for consensuses hourly, since we
4018 already have another, smarter retry mechanism. Fixes bug 8625;
4019 bugfix on 0.2.0.9-alpha.
4020 - If a consensus expires while we are waiting for certificates to
4021 download, stop waiting for certificates.
4022 - If we stop waiting for certificates less than a minute after we
4023 started downloading them, do not consider the certificate download
4024 failure a separate failure. Fixes bug 20533; bugfix
4026 - When using exponential backoff in test networks, use a lower
4027 exponent, so the delays do not vary as much. This helps test
4028 networks bootstrap consistently. Fixes bug 20597; bugfix on 20499.
4030 o Major bugfixes (exit policies):
4031 - Avoid disclosing exit outbound bind addresses, configured port
4032 bind addresses, and local interface addresses in relay descriptors
4033 by default under ExitPolicyRejectPrivate. Instead, only reject
4034 these (otherwise unlisted) addresses if
4035 ExitPolicyRejectLocalInterfaces is set. Fixes bug 18456; bugfix on
4036 0.2.7.2-alpha. Patch by teor.
4038 o Major bugfixes (hidden services):
4039 - Allow Tor clients with appropriate controllers to work with
4040 FetchHidServDescriptors set to 0. Previously, this option also
4041 disabled descriptor cache lookup, thus breaking hidden services
4042 entirely. Fixes bug 18704; bugfix on 0.2.0.20-rc. Patch by "twim".
4043 - Clients now require hidden services to include the TAP keys for
4044 their intro points in the hidden service descriptor. This prevents
4045 an inadvertent upgrade to ntor, which a malicious hidden service
4046 could use to distinguish clients by consensus version. Fixes bug
4047 20012; bugfix on 0.2.4.8-alpha. Patch by teor.
4049 o Major bugfixes (relay, resolver, logging):
4050 - For relays that don't know their own address, avoid attempting a
4051 local hostname resolve for each descriptor we download. This
4052 will cut down on the number of "Success: chose address 'x.x.x.x'"
4053 log lines, and also avoid confusing clock jumps if the resolver
4054 is slow. Fixes bugs 20423 and 20610; bugfix on 0.2.8.1-alpha.
4056 o Minor features (port flags):
4057 - Add new flags to the *Port options to give finer control over which
4058 requests are allowed. The flags are NoDNSRequest, NoOnionTraffic,
4059 and the synthetic flag OnionTrafficOnly, which is equivalent to
4060 NoDNSRequest, NoIPv4Traffic, and NoIPv6Traffic. Closes enhancement
4061 18693; patch by "teor".
4063 o Minor features (build, hardening):
4064 - Detect and work around a libclang_rt problem that would prevent
4065 clang from finding __mulodi4() on some 32-bit platforms, and thus
4066 keep -ftrapv from linking on those systems. Closes ticket 19079.
4067 - When building on a system without runtime support for the runtime
4068 hardening options, try to log a useful warning at configuration
4069 time, rather than an incomprehensible warning at link time. If
4070 expensive hardening was requested, this warning becomes an error.
4071 Closes ticket 18895.
4073 o Minor features (client, directory):
4074 - Since authorities now omit all routers that lack the Running and
4075 Valid flags, we assume that any relay listed in the consensus must
4076 have those flags. Closes ticket 20001; implements part of
4079 o Minor features (code safety):
4080 - In our integer-parsing functions, ensure that the maximum value we
4081 allow is no smaller than the minimum value. Closes ticket 19063;
4082 patch from "U+039b".
4084 o Minor features (compilation, portability):
4085 - Compile correctly on MacOS 10.12 (aka "Sierra"). Closes
4088 o Minor features (config):
4089 - Warn users when descriptor and port addresses are inconsistent.
4090 Mitigates bug 13953; patch by teor.
4092 o Minor features (controller):
4093 - Allow controllers to configure basic client authorization on
4094 hidden services when they create them with the ADD_ONION controller
4095 command. Implements ticket 15588. Patch by "special".
4096 - Fire a STATUS_SERVER controller event whenever the hibernation
4097 status changes between "awake"/"soft"/"hard". Closes ticket 18685.
4098 - Implement new GETINFO queries for all downloads that use
4099 download_status_t to schedule retries. This allows controllers to
4100 examine the schedule for pending downloads. Closes ticket 19323.
4102 o Minor features (development tools, etags):
4103 - Teach the "make tags" Makefile target how to correctly find
4104 "MOCK_IMPL" function definitions. Patch from nherring; closes
4107 o Minor features (directory authority):
4108 - After voting, if the authorities decide that a relay is not
4109 "Valid", they no longer include it in the consensus at all. Closes
4110 ticket 20002; implements part of proposal 272.
4111 - Directory authorities now only give the Guard flag to a relay if
4112 they are also giving it the Stable flag. This change allows us to
4113 simplify path selection for clients. It should have minimal effect
4114 in practice, since >99% of Guards already have the Stable flag.
4115 Implements ticket 18624.
4116 - Directory authorities now write their v3-status-votes file out to
4117 disk earlier in the consensus process, so we have a record of the
4118 votes even if we abort the consensus process. Resolves
4121 o Minor features (fallback directory list, new since 0.2.9.7-rc):
4122 - Replace the 81 remaining fallbacks of the 100 originally
4123 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
4124 fallbacks (123 new, 54 existing, 27 removed) generated in December
4125 2016. Resolves ticket 20170.
4127 o Minor features (hidden service):
4128 - Stop being so strict about the payload length of "rendezvous1"
4129 cells. We used to be locked in to the "TAP" handshake length, and
4130 now we can handle better handshakes like "ntor". Resolves
4133 o Minor features (infrastructure, time):
4134 - Tor now includes an improved timer backend, so that we can
4135 efficiently support tens or hundreds of thousands of concurrent
4136 timers, as will be needed for some of our planned anti-traffic-
4137 analysis work. This code is based on William Ahern's "timeout.c"
4138 project, which implements a "tickless hierarchical timing wheel".
4139 Closes ticket 18365.
4140 - Tor now uses the operating system's monotonic timers (where
4141 available) for internal fine-grained timing. Previously we would
4142 look at the system clock, and then attempt to compensate for the
4143 clock running backwards. Closes ticket 18908.
4145 o Minor features (logging):
4146 - Add a set of macros to check nonfatal assertions, for internal
4147 use. Migrating more of our checks to these should help us avoid
4148 needless crash bugs. Closes ticket 18613.
4149 - Provide a more useful warning message when configured with an
4150 invalid Nickname. Closes ticket 18300; patch from "icanhasaccount".
4151 - When dumping unparseable router descriptors, optionally store them
4152 in separate files, named by digest, up to a configurable size
4153 limit. You can change the size limit by setting the
4154 MaxUnparseableDescSizeToLog option, and disable this feature by
4155 setting that option to 0. Closes ticket 18322.
4157 o Minor features (performance):
4158 - Change the "optimistic data" extension from "off by default" to
4159 "on by default". The default was ordinarily overridden by a
4160 consensus option, but when clients were bootstrapping for the
4161 first time, they would not have a consensus to get the option
4162 from. Changing this default saves a round-trip during startup.
4163 Closes ticket 18815.
4165 o Minor features (relay, usability):
4166 - When the directory authorities refuse a bad relay's descriptor,
4167 encourage the relay operator to contact us. Many relay operators
4168 won't notice this line in their logs, but it's a win if even a few
4169 learn why we don't like what their relay was doing. Resolves
4172 o Minor features (security, TLS):
4173 - Servers no longer support clients that lack AES ciphersuites.
4174 (3DES is no longer considered an acceptable cipher.) We believe
4175 that no such Tor clients currently exist, since Tor has required
4176 OpenSSL 0.9.7 or later since 2009. Closes ticket 19998.
4178 o Minor features (testing):
4179 - Disable memory protections on OpenBSD when performing our unit
4180 tests for memwipe(). The test deliberately invokes undefined
4181 behavior, and the OpenBSD protections interfere with this. Patch
4182 from "rubiate". Closes ticket 20066.
4183 - Move the test-network.sh script to chutney, and modify tor's test-
4184 network.sh to call the (newer) chutney version when available.
4185 Resolves ticket 19116. Patch by teor.
4186 - Use the lcov convention for marking lines as unreachable, so that
4187 we don't count them when we're generating test coverage data.
4188 Update our coverage tools to understand this convention. Closes
4190 - Our link-handshake unit tests now check that when invalid
4191 handshakes fail, they fail with the error messages we expected.
4192 - Our unit testing code that captures log messages no longer
4193 prevents them from being written out if the user asked for them
4194 (by passing --debug or --info or --notice or --warn to the "test"
4195 binary). This change prevents us from missing unexpected log
4196 messages simply because we were looking for others. Related to
4198 - The unit tests now log all warning messages with the "BUG" flag.
4199 Previously, they only logged errors by default. This change will
4200 help us make our testing code more correct, and make sure that we
4201 only hit this code when we mean to. In the meantime, however,
4202 there will be more warnings in the unit test logs than before.
4203 This is preparatory work for ticket 19999.
4204 - The unit tests now treat any failure of a "tor_assert_nonfatal()"
4205 assertion as a test failure.
4206 - We've done significant work to make the unit tests run faster.
4208 o Minor features (testing, ipv6):
4209 - Add the hs-ipv6 chutney target to make test-network-all's IPv6
4210 tests. Remove bridges+hs, as it's somewhat redundant. This
4211 requires a recent chutney version that supports IPv6 clients,
4212 relays, and authorities. Closes ticket 20069; patch by teor.
4213 - Add the single-onion and single-onion-ipv6 chutney targets to
4214 "make test-network-all". This requires a recent chutney version
4215 with the single onion network flavors (git c72a652 or later).
4216 Closes ticket 20072; patch by teor.
4218 o Minor features (Tor2web):
4219 - Make Tor2web clients respect ReachableAddresses. This feature was
4220 inadvertently enabled in 0.2.8.6, then removed by bugfix 19973 on
4221 0.2.8.7. Implements feature 20034. Patch by teor.
4223 o Minor features (unix domain sockets):
4224 - When configuring a unix domain socket for a SocksPort,
4225 ControlPort, or Hidden service, you can now wrap the address in
4226 quotes, using C-style escapes inside the quotes. This allows unix
4227 domain socket paths to contain spaces. Resolves ticket 18753.
4229 o Minor features (user interface):
4230 - Tor now supports the ability to declare options deprecated, so
4231 that we can recommend that people stop using them. Previously, this
4232 was done in an ad-hoc way. There is a new --list-deprecated-options
4233 command-line option to list all of the deprecated options. Closes
4236 o Minor features (virtual addresses):
4237 - Increase the maximum number of bits for the IPv6 virtual network
4238 prefix from 16 to 104. In this way, the condition for address
4239 allocation is less restrictive. Closes ticket 20151; feature
4242 o Minor bug fixes (circuits):
4243 - Use the CircuitBuildTimeout option whenever
4244 LearnCircuitBuildTimeout is disabled. Previously, we would respect
4245 the option when a user disabled it, but not when it was disabled
4246 because some other option was set. Fixes bug 20073; bugfix on
4247 0.2.4.12-alpha. Patch by teor.
4249 o Minor bugfixes (build):
4250 - The current Git revision when building from a local repository is
4251 now detected correctly when using git worktrees. Fixes bug 20492;
4252 bugfix on 0.2.3.9-alpha.
4254 o Minor bugfixes (relay address discovery):
4255 - Stop reordering IP addresses returned by the OS. This makes it
4256 more likely that Tor will guess the same relay IP address every
4257 time. Fixes issue 20163; bugfix on 0.2.7.1-alpha, ticket 17027.
4258 Reported by René Mayrhofer, patch by "cypherpunks".
4260 o Minor bugfixes (memory allocation):
4261 - Change how we allocate memory for large chunks on buffers, to
4262 avoid a (currently impossible) integer overflow, and to waste less
4263 space when allocating unusually large chunks. Fixes bug 20081;
4264 bugfix on 0.2.0.16-alpha. Issue identified by Guido Vranken.
4266 o Minor bugfixes (bootstrap):
4267 - Remember the directory server we fetched the consensus or previous
4268 certificates from, and use it to fetch future authority
4269 certificates. This change improves bootstrapping performance.
4270 Fixes bug 18963; bugfix on 0.2.8.1-alpha.
4272 o Minor bugfixes (circuits):
4273 - Make sure extend_info_from_router() is only called on servers.
4274 Fixes bug 19639; bugfix on 0.2.8.1-alpha.
4276 o Minor bugfixes (client, fascistfirewall):
4277 - Avoid spurious warnings when ReachableAddresses or FascistFirewall
4278 is set. Fixes bug 20306; bugfix on 0.2.8.2-alpha.
4280 o Minor bugfixes (client, unix domain sockets):
4281 - Disable IsolateClientAddr when using AF_UNIX backed SocksPorts as
4282 the client address is meaningless. Fixes bug 20261; bugfix
4285 o Minor bugfixes (code style):
4286 - Fix an integer signedness conversion issue in the case conversion
4287 tables. Fixes bug 19168; bugfix on 0.2.1.11-alpha.
4289 o Minor bugfixes (compilation):
4290 - Build correctly on versions of libevent2 without support for
4291 evutil_secure_rng_add_bytes(). Fixes bug 19904; bugfix
4293 - When building with Clang, use a full set of GCC warnings.
4294 (Previously, we included only a subset, because of the way we
4295 detected them.) Fixes bug 19216; bugfix on 0.2.0.1-alpha.
4296 - Detect Libevent2 functions correctly on systems that provide
4297 libevent2, but where libevent1 is linked with -levent. Fixes bug
4298 19904; bugfix on 0.2.2.24-alpha. Patch from Rubiate.
4299 - Run correctly when built on Windows build environments that
4300 require _vcsprintf(). Fixes bug 20560; bugfix on 0.2.2.11-alpha.
4302 o Minor bugfixes (configuration):
4303 - When parsing quoted configuration values from the torrc file,
4304 handle Windows line endings correctly. Fixes bug 19167; bugfix on
4305 0.2.0.16-alpha. Patch from "Pingl".
4307 o Minor bugfixes (directory authority):
4308 - Authorities now sort the "package" lines in their votes, for ease
4309 of debugging. (They are already sorted in consensus documents.)
4310 Fixes bug 18840; bugfix on 0.2.6.3-alpha.
4311 - Die with a more useful error when the operator forgets to place
4312 the authority_signing_key file into the keys directory. This
4313 avoids an uninformative assert & traceback about having an invalid
4314 key. Fixes bug 20065; bugfix on 0.2.0.1-alpha.
4315 - When allowing private addresses, mark Exits that only exit to
4316 private locations as such. Fixes bug 20064; bugfix
4318 - When parsing a detached signature, make sure we use the length of
4319 the digest algorithm instead of a hardcoded DIGEST256_LEN in
4320 order to avoid comparing bytes out-of-bounds with a smaller digest
4321 length such as SHA1. Fixes bug 19066; bugfix on 0.2.2.6-alpha.
4323 o Minor bugfixes (getpass):
4324 - Defensively fix a non-triggerable heap corruption at do_getpass()
4325 to protect ourselves from mistakes in the future. Fixes bug
4326 19223; bugfix on 0.2.7.3-rc. Bug found by Guido Vranken, patch
4329 o Minor bugfixes (guard selection):
4330 - Don't mark guards as unreachable if connection_connect() fails.
4331 That function fails for local reasons, so it shouldn't reveal
4332 anything about the status of the guard. Fixes bug 14334; bugfix
4334 - Use a single entry guard even if the NumEntryGuards consensus
4335 parameter is not provided. Fixes bug 17688; bugfix
4338 o Minor bugfixes (hidden services):
4339 - Increase the minimum number of internal circuits we preemptively
4340 build from 2 to 3, so a circuit is available when a client
4341 connects to another onion service. Fixes bug 13239; bugfix
4343 - Allow hidden services to run on IPv6 addresses even when the
4344 IPv6Exit option is not set. Fixes bug 18357; bugfix
4346 - Stop logging intro point details to the client log on certain
4347 error conditions. Fixed as part of bug 20012; bugfix on
4348 0.2.4.8-alpha. Patch by teor.
4349 - When deleting an ephemeral hidden service, close its intro points
4350 even if they are not completely open. Fixes bug 18604; bugfix
4352 - When configuring hidden services, check every hidden service
4353 directory's permissions. Previously, we only checked the last
4354 hidden service. Fixes bug 20529; bugfix on 0.2.6.2-alpha.
4356 o Minor bugfixes (IPv6, testing):
4357 - Check for IPv6 correctly on Linux when running test networks.
4358 Fixes bug 19905; bugfix on 0.2.7.3-rc; patch by teor.
4360 o Minor bugfixes (Linux seccomp2 sandbox):
4361 - Add permission to run the sched_yield() and sigaltstack() system
4362 calls, in order to support versions of Tor compiled with asan or
4363 ubsan code that use these calls. Now "sandbox 1" and
4364 "--enable-expensive-hardening" should be compatible on more
4365 systems. Fixes bug 20063; bugfix on 0.2.5.1-alpha.
4367 o Minor bugfixes (logging):
4368 - Downgrade a harmless log message about the
4369 pending_entry_connections list from "warn" to "info". Mitigates
4371 - Log a more accurate message when we fail to dump a microdescriptor.
4372 Fixes bug 17758; bugfix on 0.2.2.8-alpha. Patch from Daniel Pinto.
4373 - When logging a directory ownership mismatch, log the owning
4374 username correctly. Fixes bug 19578; bugfix on 0.2.2.29-beta.
4375 - When we are unable to remove the bw_accounting file, do not warn
4376 if the reason we couldn't remove it was that it didn't exist.
4377 Fixes bug 19964; bugfix on 0.2.5.4-alpha. Patch from pastly.
4379 o Minor bugfixes (memory leak):
4380 - Fix a series of slow memory leaks related to parsing torrc files
4381 and options. Fixes bug 19466; bugfix on 0.2.1.6-alpha.
4382 - Avoid a small memory leak when informing worker threads about
4383 rotated onion keys. Fixes bug 20401; bugfix on 0.2.6.3-alpha.
4384 - Fix a small memory leak when receiving AF_UNIX connections on a
4385 SocksPort. Fixes bug 20716; bugfix on 0.2.6.3-alpha.
4386 - When moving a signed descriptor object from a source to an
4387 existing destination, free the allocated memory inside that
4388 destination object. Fixes bug 20715; bugfix on 0.2.8.3-alpha.
4389 - Fix a memory leak and use-after-free error when removing entries
4390 from the sandbox's getaddrinfo() cache. Fixes bug 20710; bugfix on
4391 0.2.5.5-alpha. Patch from "cypherpunks".
4392 - Fix a small, uncommon memory leak that could occur when reading a
4393 truncated ed25519 key file. Fixes bug 18956; bugfix
4396 o Minor bugfixes (option parsing):
4397 - Count unix sockets when counting client listeners (SOCKS, Trans,
4398 NATD, and DNS). This has no user-visible behavior changes: these
4399 options are set once, and never read. Required for correct
4400 behavior in ticket 17178. Fixes bug 19677; bugfix on
4401 0.2.6.3-alpha. Patch by teor.
4403 o Minor bugfixes (options):
4404 - Check the consistency of UseEntryGuards and EntryNodes more
4405 reliably. Fixes bug 20074; bugfix on 0.2.4.12-alpha. Patch
4407 - Stop changing the configured value of UseEntryGuards on
4408 authorities and Tor2web clients. Fixes bug 20074; bugfix on
4409 commits 51fc6799 in 0.1.1.16-rc and acda1735 in 0.2.4.3-alpha.
4412 o Minor bugfixes (relay):
4413 - Ensure relays don't make multiple connections during bootstrap.
4414 Fixes bug 20591; bugfix on 0.2.8.1-alpha.
4415 - Do not try to parallelize workers more than 16x without the user
4416 explicitly configuring us to do so, even if we do detect more than
4417 16 CPU cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
4419 o Minor bugfixes (testing):
4420 - The test-stem and test-network makefile targets now depend only on
4421 the tor binary that they are testing. Previously, they depended on
4422 "make all". Fixes bug 18240; bugfix on 0.2.8.2-alpha. Based on a
4423 patch from "cypherpunks".
4424 - Allow clients to retry HSDirs much faster in test networks. Fixes
4425 bug 19702; bugfix on 0.2.7.1-alpha. Patch by teor.
4426 - Avoid a unit test failure on systems with over 16 detectable CPU
4427 cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
4428 - Let backtrace tests work correctly under AddressSanitizer:
4429 disable ASAN's detection of segmentation faults while running
4430 test_bt.sh, so that we can make sure that our own backtrace
4431 generation code works. Fixes bug 18934; bugfix
4432 on 0.2.5.2-alpha. Patch from "cypherpunks".
4433 - Fix the test-network-all target on out-of-tree builds by using the
4434 correct path to the test driver script. Fixes bug 19421; bugfix
4436 - Stop spurious failures in the local interface address discovery
4437 unit tests. Fixes bug 20634; bugfix on 0.2.8.1-alpha; patch by
4439 - Use ECDHE ciphers instead of ECDH in tortls tests. LibreSSL has
4440 removed the ECDH ciphers which caused the tests to fail on
4441 platforms which use it. Fixes bug 20460; bugfix on 0.2.8.1-alpha.
4442 - The tor_tls_server_info_callback unit test no longer crashes when
4443 debug-level logging is turned on. Fixes bug 20041; bugfix
4446 o Minor bugfixes (time):
4447 - Improve overflow checks in tv_udiff and tv_mdiff. Fixes bug 19483;
4448 bugfix on all released tor versions.
4449 - When computing the difference between two times in milliseconds,
4450 we now round to the nearest millisecond correctly. Previously, we
4451 could sometimes round in the wrong direction. Fixes bug 19428;
4452 bugfix on 0.2.2.2-alpha.
4454 o Minor bugfixes (Tor2web):
4455 - Prevent Tor2web clients from running hidden services: these services
4456 are not anonymous due to the one-hop client paths. Fixes bug
4457 19678. Patch by teor.
4459 o Minor bugfixes (user interface):
4460 - Display a more accurate number of suppressed messages in the log
4461 rate-limiter. Previously, there was a potential integer overflow
4462 in the counter. Now, if the number of messages hits a maximum, the
4463 rate-limiter doesn't count any further. Fixes bug 19435; bugfix
4465 - Fix a typo in the passphrase prompt for the ed25519 identity key.
4466 Fixes bug 19503; bugfix on 0.2.7.2-alpha.
4468 o Code simplification and refactoring:
4469 - Remove redundant declarations of the MIN macro. Closes
4471 - Rename tor_dup_addr() to tor_addr_to_str_dup() to avoid confusion.
4472 Closes ticket 18462; patch from "icanhasaccount".
4473 - Split the 600-line directory_handle_command_get function into
4474 separate functions for different URL types. Closes ticket 16698.
4477 - Add module-level internal documentation for 36 C files that
4478 previously didn't have a high-level overview. Closes ticket 20385.
4479 - Correct the IPv6 syntax in our documentation for the
4480 VirtualAddrNetworkIPv6 torrc option. Closes ticket 19743.
4481 - Correct the minimum bandwidth value in torrc.sample, and queue a
4482 corresponding change for torrc.minimal. Closes ticket 20085.
4483 - Fix spelling of "--enable-tor2web-mode" in the manpage. Closes
4484 ticket 19153. Patch from "U+039b".
4485 - Module-level documentation for several more modules. Closes
4486 tickets 19287 and 19290.
4487 - Document the --passphrase-fd option in the tor manpage. Fixes bug
4488 19504; bugfix on 0.2.7.3-rc.
4489 - Document the default PathsNeededToBuildCircuits value that's used
4490 by clients when the directory authorities don't set
4491 min_paths_for_circs_pct. Fixes bug 20117; bugfix on 0.2.4.10-alpha.
4492 Patch by teor, reported by Jesse V.
4493 - Fix manual for the User option: it takes a username, not a UID.
4494 Fixes bug 19122; bugfix on 0.0.2pre16 (the first version to have
4496 - Fix the description of the --passphrase-fd option in the
4497 tor-gencert manpage. The option is used to pass the number of a
4498 file descriptor to read the passphrase from, not to read the file
4499 descriptor from. Fixes bug 19505; bugfix on 0.2.0.20-alpha.
4502 - We no longer include the (dead, deprecated) bufferevent code in
4503 Tor. Closes ticket 19450. Based on a patch from "U+039b".
4506 - Remove support for "GET /tor/bytes.txt" DirPort request, and
4507 "GETINFO dir-usage" controller request, which were only available
4508 via a compile-time option in Tor anyway. Feature was added in
4509 0.2.2.1-alpha. Resolves ticket 19035.
4510 - There is no longer a compile-time option to disable support for
4511 TransPort. (If you don't want TransPort, just don't use it.) Patch
4512 from "U+039b". Closes ticket 19449.
4515 - Run more workqueue tests as part of "make check". These had
4516 previously been implemented, but you needed to know special
4517 command-line options to enable them.
4518 - We now have unit tests for our code to reject zlib "compression
4519 bombs". (Fortunately, the code works fine.)
4522 Changes in version 0.2.8.11 - 2016-12-08
4523 Tor 0.2.8.11 backports fixes for additional portability issues that
4524 could prevent Tor from building correctly on OSX Sierra, or with
4525 OpenSSL 1.1. Affected users should upgrade; others can safely stay
4528 o Minor bugfixes (portability):
4529 - Avoid compilation errors when building on OSX Sierra. Sierra began
4530 to support the getentropy() and clock_gettime() APIs, but created
4531 a few problems in doing so. Tor 0.2.9 has a more thorough set of
4532 workarounds; in 0.2.8, we are just using the /dev/urandom and mach
4533 monotonic time interfaces. Fixes bug 20865. Bugfix
4536 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
4537 - Fix compilation with OpenSSL 1.1 and less commonly-used CPU
4538 architectures. Closes ticket 20588.
4541 Changes in version 0.2.8.10 - 2016-12-02
4542 Tor 0.2.8.10 backports a fix for a bug that would sometimes make clients
4543 unusable after they left standby mode. It also backports fixes for
4544 a few portability issues and a small but problematic memory leak.
4546 o Major bugfixes (client reliability, backport from 0.2.9.5-alpha):
4547 - When Tor leaves standby because of a new application request, open
4548 circuits as needed to serve that request. Previously, we would
4549 potentially wait a very long time. Fixes part of bug 19969; bugfix
4552 o Major bugfixes (client performance, backport from 0.2.9.5-alpha):
4553 - Clients now respond to new application stream requests immediately
4554 when they arrive, rather than waiting up to one second before
4555 starting to handle them. Fixes part of bug 19969; bugfix
4558 o Minor bugfixes (portability, backport from 0.2.9.6-rc):
4559 - Work around a bug in the OSX 10.12 SDK that would prevent us from
4560 successfully targeting earlier versions of OSX. Resolves
4563 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
4564 - Fix implicit conversion warnings under OpenSSL 1.1. Fixes bug
4565 20551; bugfix on 0.2.1.1-alpha.
4567 o Minor bugfixes (relay, backport from 0.2.9.5-alpha):
4568 - Work around a memory leak in OpenSSL 1.1 when encoding public
4569 keys. Fixes bug 20553; bugfix on 0.0.2pre8.
4571 o Minor features (geoip):
4572 - Update geoip and geoip6 to the November 3 2016 Maxmind GeoLite2
4576 Changes in version 0.2.8.9 - 2016-10-17
4577 Tor 0.2.8.9 backports a fix for a security hole in previous versions
4578 of Tor that would allow a remote attacker to crash a Tor client,
4579 hidden service, relay, or authority. All Tor users should upgrade to
4580 this version, or to 0.2.9.4-alpha. Patches will be released for older
4583 o Major features (security fixes, also in 0.2.9.4-alpha):
4584 - Prevent a class of security bugs caused by treating the contents
4585 of a buffer chunk as if they were a NUL-terminated string. At
4586 least one such bug seems to be present in all currently used
4587 versions of Tor, and would allow an attacker to remotely crash
4588 most Tor instances, especially those compiled with extra compiler
4589 hardening. With this defense in place, such bugs can't crash Tor,
4590 though we should still fix them as they occur. Closes ticket
4591 20384 (TROVE-2016-10-001).
4593 o Minor features (geoip):
4594 - Update geoip and geoip6 to the October 4 2016 Maxmind GeoLite2
4598 Changes in version 0.2.8.8 - 2016-09-23
4599 Tor 0.2.8.8 fixes two crash bugs present in previous versions of the
4600 0.2.8.x series. Relays running 0.2.8.x should upgrade, as should users
4601 who select public relays as their bridges.
4603 o Major bugfixes (crash):
4604 - Fix a complicated crash bug that could affect Tor clients
4605 configured to use bridges when replacing a networkstatus consensus
4606 in which one of their bridges was mentioned. OpenBSD users saw
4607 more crashes here, but all platforms were potentially affected.
4608 Fixes bug 20103; bugfix on 0.2.8.2-alpha.
4610 o Major bugfixes (relay, OOM handler):
4611 - Fix a timing-dependent assertion failure that could occur when we
4612 tried to flush from a circuit after having freed its cells because
4613 of an out-of-memory condition. Fixes bug 20203; bugfix on
4614 0.2.8.1-alpha. Thanks to "cypherpunks" for help diagnosing
4617 o Minor feature (fallback directories):
4618 - Remove broken fallbacks from the hard-coded fallback directory
4619 list. Closes ticket 20190; patch by teor.
4621 o Minor features (geoip):
4622 - Update geoip and geoip6 to the September 6 2016 Maxmind GeoLite2
4626 Changes in version 0.2.8.7 - 2016-08-24
4627 Tor 0.2.8.7 fixes an important bug related to the ReachableAddresses
4628 option in 0.2.8.6, and replaces a retiring bridge authority. Everyone
4629 who sets the ReachableAddresses option, and all bridges, are strongly
4630 encouraged to upgrade.
4632 o Directory authority changes:
4633 - The "Tonga" bridge authority has been retired; the new bridge
4634 authority is "Bifroest". Closes tickets 19728 and 19690.
4636 o Major bugfixes (client, security):
4637 - Only use the ReachableAddresses option to restrict the first hop
4638 in a path. In earlier versions of 0.2.8.x, it would apply to
4639 every hop in the path, with a possible degradation in anonymity
4640 for anyone using an uncommon ReachableAddress setting. Fixes bug
4641 19973; bugfix on 0.2.8.2-alpha.
4643 o Minor features (geoip):
4644 - Update geoip and geoip6 to the August 2 2016 Maxmind GeoLite2
4647 o Minor bugfixes (compilation):
4648 - Remove an inappropriate "inline" in tortls.c that was causing
4649 warnings on older versions of GCC. Fixes bug 19903; bugfix
4652 o Minor bugfixes (fallback directories):
4653 - Avoid logging a NULL string pointer when loading fallback
4654 directory information. Fixes bug 19947; bugfix on 0.2.4.7-alpha
4655 and 0.2.8.1-alpha. Report and patch by "rubiate".
4658 Changes in version 0.2.8.6 - 2016-08-02
4660 Tor 0.2.8.6 is the first stable version of the Tor 0.2.8 series.
4662 The Tor 0.2.8 series improves client bootstrapping performance,
4663 completes the authority-side implementation of improved identity
4664 keys for relays, and includes numerous bugfixes and performance
4665 improvements throughout the program. This release continues to
4666 improve the coverage of Tor's test suite. For a full list of
4667 changes since Tor 0.2.7, see the ReleaseNotes file.
4669 Below is a list of the changes since Tor 0.2.7.
4671 o New system requirements:
4672 - Tor no longer attempts to support platforms where the "time_t"
4673 type is unsigned. (To the best of our knowledge, only OpenVMS does
4674 this, and Tor has never actually built on OpenVMS.) Closes
4676 - Tor no longer supports versions of OpenSSL with a broken
4677 implementation of counter mode. (This bug was present in OpenSSL
4678 1.0.0, and was fixed in OpenSSL 1.0.0a.) Tor still detects, but no
4679 longer runs with, these versions.
4680 - Tor now uses Autoconf version 2.63 or later, and Automake 1.11 or
4681 later (released in 2008 and 2009 respectively). If you are
4682 building Tor from the git repository instead of from the source
4683 distribution, and your tools are older than this, you will need to
4684 upgrade. Closes ticket 17732.
4686 o Directory authority changes:
4687 - Update the V3 identity key for the dannenberg directory authority:
4688 it was changed on 18 November 2015. Closes task 17906. Patch
4690 - Urras is no longer a directory authority. Closes ticket 19271.
4692 o Major features (directory system):
4693 - Include a trial list of default fallback directories, based on an
4694 opt-in survey of suitable relays. Doing this should make clients
4695 bootstrap more quickly and reliably, and reduce the load on the
4696 directory authorities. Closes ticket 15775. Patch by teor.
4697 Candidates identified using an OnionOO script by weasel, teor,
4698 gsathya, and karsten.
4699 - Previously only relays that explicitly opened a directory port
4700 (DirPort) accepted directory requests from clients. Now all
4701 relays, with and without a DirPort, accept and serve tunneled
4702 directory requests that they receive through their ORPort. You can
4703 disable this behavior using the new DirCache option. Closes
4705 - When bootstrapping multiple consensus downloads at a time, use the
4706 first one that starts downloading, and close the rest. This
4707 reduces failures when authorities or fallback directories are slow
4708 or down. Together with the code for feature 15775, this feature
4709 should reduces failures due to fallback churn. Implements ticket
4710 4483. Patch by teor. Implements IPv4 portions of proposal 210 by
4713 o Major features (security, Linux):
4714 - When Tor starts as root on Linux and is told to switch user ID, it
4715 can now retain the capability to bind to low ports. By default,
4716 Tor will do this only when it's switching user ID and some low
4717 ports have been configured. You can change this behavior with the
4718 new option KeepBindCapabilities. Closes ticket 8195.
4720 o Major bugfixes (client, bootstrapping):
4721 - Check if bootstrap consensus downloads are still needed when the
4722 linked connection attaches. This prevents tor making unnecessary
4723 begindir-style connections, which are the only directory
4724 connections tor clients make since the fix for 18483 was merged.
4725 - Fix some edge cases where consensus download connections may not
4726 have been closed, even though they were not needed. Related to fix
4728 - Make relays retry consensus downloads the correct number of times,
4729 rather than the more aggressive client retry count. Fixes part of
4732 o Major bugfixes (dns proxy mode, crash):
4733 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
4734 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
4736 o Major bugfixes (ed25519, voting):
4737 - Actually enable support for authorities to match routers by their
4738 Ed25519 identities. Previously, the code had been written, but
4739 some debugging code that had accidentally been left in the
4740 codebase made it stay turned off. Fixes bug 17702; bugfix
4742 - When collating votes by Ed25519 identities, authorities now
4743 include a "NoEdConsensus" flag if the ed25519 value (or lack
4744 thereof) for a server does not reflect the majority consensus.
4745 Related to bug 17668; bugfix on 0.2.7.2-alpha.
4746 - When generating a vote with keypinning disabled, never include two
4747 entries for the same ed25519 identity. This bug was causing
4748 authorities to generate votes that they could not parse when a
4749 router violated key pinning by changing its RSA identity but
4750 keeping its Ed25519 identity. Fixes bug 17668; fixes part of bug
4751 18318. Bugfix on 0.2.7.2-alpha.
4753 o Major bugfixes (key management):
4754 - If OpenSSL fails to generate an RSA key, do not retain a dangling
4755 pointer to the previous (uninitialized) key value. The impact here
4756 should be limited to a difficult-to-trigger crash, if OpenSSL is
4757 running an engine that makes key generation failures possible, or
4758 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
4759 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
4762 o Major bugfixes (security, client, DNS proxy):
4763 - Stop a crash that could occur when a client running with DNSPort
4764 received a query with multiple address types, and the first
4765 address type was not supported. Found and fixed by Scott Dial.
4766 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
4768 o Major bugfixes (security, compilation):
4769 - Correctly detect compiler flags on systems where _FORTIFY_SOURCE
4770 is predefined. Previously, our use of -D_FORTIFY_SOURCE would
4771 cause a compiler warning, thereby making other checks fail, and
4772 needlessly disabling compiler-hardening support. Fixes one case of
4773 bug 18841; bugfix on 0.2.3.17-beta. Patch from "trudokal".
4774 - Repair hardened builds under the clang compiler. Previously, our
4775 use of _FORTIFY_SOURCE would conflict with clang's address
4776 sanitizer. Fixes bug 14821; bugfix on 0.2.5.4-alpha.
4778 o Major bugfixes (security, pointers):
4779 - Avoid a difficult-to-trigger heap corruption attack when extending
4780 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
4781 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
4782 Reported by Guido Vranken.
4784 o Major bugfixes (testing):
4785 - Fix a bug that would block 'make test-network-all' on systems where
4786 IPv6 packets were lost. Fixes bug 19008; bugfix on 0.2.7.3-rc.
4788 o Major bugfixes (user interface):
4789 - Correctly give a warning in the cases where a relay is specified
4790 by nickname, and one such relay is found, but it is not officially
4791 Named. Fixes bug 19203; bugfix on 0.2.3.1-alpha.
4793 o Minor features (accounting):
4794 - Added two modes to the AccountingRule option: One for limiting
4795 only the number of bytes sent ("AccountingRule out"), and one for
4796 limiting only the number of bytes received ("AccountingRule in").
4797 Closes ticket 15989; patch from "unixninja92".
4799 o Minor features (bug-resistance):
4800 - Make Tor survive errors involving connections without a
4801 corresponding event object. Previously we'd fail with an
4802 assertion; now we produce a log message. Related to bug 16248.
4803 - Use tor_snprintf() and tor_vsnprintf() even in external and low-
4804 level code, to harden against accidental failures to NUL-
4805 terminate. Part of ticket 17852. Patch from jsturgix. Found
4808 o Minor features (build):
4809 - Detect systems with FreeBSD-derived kernels (such as GNU/kFreeBSD)
4810 as having possible IPFW support. Closes ticket 18448. Patch from
4812 - Since our build process now uses "make distcheck", we no longer
4813 force "make dist" to depend on "make check". Closes ticket 17893;
4814 patch from "cypherpunks".
4815 - Tor now builds once again with the recent OpenSSL 1.1 development
4816 branch (tested against 1.1.0-pre5 and 1.1.0-pre6-dev). We have been
4817 tracking OpenSSL 1.1 development as it has progressed, and fixing
4818 numerous compatibility issues as they arose. See tickets
4819 17549, 17921, 17984, 19499, and 18286.
4820 - When building manual pages, set the timezone to "UTC", so that the
4821 output is reproducible. Fixes bug 19558; bugfix on 0.2.2.9-alpha.
4822 Patch from intrigeri.
4824 o Minor features (clients):
4825 - Make clients, onion services, and bridge relays always use an
4826 encrypted begindir connection for directory requests. Resolves
4827 ticket 18483. Patch by teor.
4829 o Minor features (controller):
4830 - Add 'GETINFO exit-policy/reject-private/[default,relay]', so
4831 controllers can examine the the reject rules added by
4832 ExitPolicyRejectPrivate. This makes it easier for stem to display
4834 - Adds the FallbackDir entries to 'GETINFO config/defaults'. Closes
4835 tickets 16774 and 17817. Patch by George Tankersley.
4836 - New 'GETINFO hs/service/desc/id/' command to retrieve a hidden
4837 service descriptor from a service's local hidden service
4838 descriptor cache. Closes ticket 14846.
4840 o Minor features (crypto):
4841 - Add SHA3 and SHAKE support to crypto.c. Closes ticket 17783.
4842 - Add SHA512 support to crypto.c. Closes ticket 17663; patch from
4844 - Improve performance when hashing non-multiple of 8 sized buffers,
4845 based on Andrew Moon's public domain SipHash-2-4 implementation.
4846 Fixes bug 17544; bugfix on 0.2.5.3-alpha.
4847 - Validate the hard-coded Diffie-Hellman parameters and ensure that
4848 p is a safe prime, and g is a suitable generator. Closes
4850 - When allocating a digest state object, allocate no more space than
4851 we actually need. Previously, we would allocate as much space as
4852 the state for the largest algorithm would need. This change saves
4853 up to 672 bytes per circuit. Closes ticket 17796.
4855 o Minor features (directory downloads):
4856 - Add UseDefaultFallbackDirs, which enables any hard-coded fallback
4857 directory mirrors. The default is 1; set it to 0 to disable
4858 fallbacks. Implements ticket 17576. Patch by teor.
4859 - Wait for busy authorities and fallback directories to become non-
4860 busy when bootstrapping. (A similar change was made in 6c443e987d
4861 for directory caches chosen from the consensus.) Closes ticket
4862 17864; patch by teor.
4864 o Minor features (geoip):
4865 - Update geoip and geoip6 to the July 6 2016 Maxmind GeoLite2
4868 o Minor features (hidden service directory):
4869 - Streamline relay-side hsdir handling: when relays consider whether
4870 to accept an uploaded hidden service descriptor, they no longer
4871 check whether they are one of the relays in the network that is
4872 "supposed" to handle that descriptor. Implements ticket 18332.
4874 o Minor features (IPv6):
4875 - Add ClientPreferIPv6DirPort, which is set to 0 by default. If set
4876 to 1, tor prefers IPv6 directory addresses.
4877 - Add ClientUseIPv4, which is set to 1 by default. If set to 0, tor
4878 avoids using IPv4 for client OR and directory connections.
4879 - Add address policy assume_action support for IPv6 addresses.
4880 - Add an argument 'ipv6=address:orport' to the DirAuthority and
4881 FallbackDir torrc options, to specify an IPv6 address for an
4882 authority or fallback directory. Add hard-coded ipv6 addresses for
4883 directory authorities that have them. Closes ticket 17327; patch
4884 from Nick Mathewson and teor.
4885 - Allow users to configure directory authorities and fallback
4886 directory servers with IPv6 addresses and ORPorts. Resolves
4888 - Limit IPv6 mask bits to 128.
4889 - Make tor_ersatz_socketpair work on IPv6-only systems. Fixes bug
4890 17638; bugfix on 0.0.2pre8. Patch by teor.
4891 - Try harder to obey the IP version restrictions "ClientUseIPv4 0",
4892 "ClientUseIPv6 0", "ClientPreferIPv6ORPort", and
4893 "ClientPreferIPv6DirPort". Closes ticket 17840; patch by teor.
4894 - Warn when comparing against an AF_UNSPEC address in a policy, it's
4895 almost always a bug. Closes ticket 17863; patch by teor.
4896 - routerset_parse now accepts IPv6 literal addresses. Fixes bug
4897 17060; bugfix on 0.2.1.3-alpha. Patch by teor.
4899 o Minor features (Linux seccomp2 sandbox):
4900 - Reject attempts to change our Address with "Sandbox 1" enabled.
4901 Changing Address with Sandbox turned on would never actually work,
4902 but previously it would fail in strange and confusing ways. Found
4905 o Minor features (logging):
4906 - When logging to syslog, allow a tag to be added to the syslog
4907 identity (the string prepended to every log message). The tag can
4908 be configured with SyslogIdentityTag and defaults to none. Setting
4909 it to "foo" will cause logs to be tagged as "Tor-foo". Closes
4912 o Minor features (portability):
4913 - Use timingsafe_memcmp() where available. Closes ticket 17944;
4914 patch from <logan@hackers.mu>.
4916 o Minor features (relay, address discovery):
4917 - Add a family argument to get_interface_addresses_raw() and
4918 subfunctions to make network interface address interogation more
4919 efficient. Now Tor can specifically ask for IPv4, IPv6 or both
4920 types of interfaces from the operating system. Resolves
4922 - When get_interface_address6_list(.,AF_UNSPEC,.) is called and
4923 fails to enumerate interface addresses using the platform-specific
4924 API, have it rely on the UDP socket fallback technique to try and
4925 find out what IP addresses (both IPv4 and IPv6) our machine has.
4926 Resolves ticket 17951.
4928 o Minor features (replay cache):
4929 - The replay cache now uses SHA256 instead of SHA1. Implements
4930 feature 8961. Patch by teor, issue reported by rransom.
4932 o Minor features (robustness):
4933 - Exit immediately with an error message if the code attempts to use
4934 Libevent without having initialized it. This should resolve some
4935 frequently-made mistakes in our unit tests. Closes ticket 18241.
4937 o Minor features (security, clock):
4938 - Warn when the system clock appears to move back in time (when the
4939 state file was last written in the future). Tor doesn't know that
4940 consensuses have expired if the clock is in the past. Patch by
4941 teor. Implements ticket 17188.
4943 o Minor features (security, exit policies):
4944 - ExitPolicyRejectPrivate now rejects more private addresses by
4945 default. Specifically, it now rejects the relay's outbound bind
4946 addresses (if configured), and the relay's configured port
4947 addresses (such as ORPort and DirPort). Fixes bug 17027; bugfix on
4948 0.2.0.11-alpha. Patch by teor.
4950 o Minor features (security, memory erasure):
4951 - Make memwipe() do nothing when passed a NULL pointer or buffer of
4952 zero size. Check size argument to memwipe() for underflow. Fixes
4953 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
4955 - Set the unused entries in a smartlist to NULL. This helped catch
4956 a (harmless) bug, and shouldn't affect performance too much.
4957 Implements ticket 17026.
4958 - Use SecureMemoryWipe() function to securely clean memory on
4959 Windows. Previously we'd use OpenSSL's OPENSSL_cleanse() function.
4960 Implements feature 17986.
4961 - Use explicit_bzero or memset_s when present. Previously, we'd use
4962 OpenSSL's OPENSSL_cleanse() function. Closes ticket 7419; patches
4963 from <logan@hackers.mu> and <selven@hackers.mu>.
4965 o Minor features (security, RNG):
4966 - Adjust Tor's use of OpenSSL's RNG APIs so that they absolutely,
4967 positively are not allowed to fail. Previously we depended on
4968 internal details of OpenSSL's behavior. Closes ticket 17686.
4969 - Never use the system entropy output directly for anything besides
4970 seeding the PRNG. When we want to generate important keys, instead
4971 of using system entropy directly, we now hash it with the PRNG
4972 stream. This may help resist certain attacks based on broken OS
4973 entropy implementations. Closes part of ticket 17694.
4974 - Use modern system calls (like getentropy() or getrandom()) to
4975 generate strong entropy on platforms that have them. Closes
4978 o Minor features (security, win32):
4979 - Set SO_EXCLUSIVEADDRUSE on Win32 to avoid a local port-stealing
4980 attack. Fixes bug 18123; bugfix on all tor versions. Patch
4983 o Minor features (unix domain sockets):
4984 - Add a new per-socket option, RelaxDirModeCheck, to allow creating
4985 Unix domain sockets without checking the permissions on the parent
4986 directory. (Tor checks permissions by default because some
4987 operating systems only check permissions on the parent directory.
4988 However, some operating systems do look at permissions on the
4989 socket, and tor's default check is unneeded.) Closes ticket 18458.
4992 o Minor features (unix file permissions):
4993 - Defer creation of Unix sockets until after setuid. This avoids
4994 needing CAP_CHOWN and CAP_FOWNER when using systemd's
4995 CapabilityBoundingSet, or chown and fowner when using SELinux.
4996 Implements part of ticket 17562. Patch from Jamie Nguyen.
4997 - If any directory created by Tor is marked as group readable, the
4998 filesystem group is allowed to be either the default GID or the
4999 root user. Allowing root to read the DataDirectory prevents the
5000 need for CAP_READ_SEARCH when using systemd's
5001 CapabilityBoundingSet, or dac_read_search when using SELinux.
5002 Implements part of ticket 17562. Patch from Jamie Nguyen.
5003 - Introduce a new DataDirectoryGroupReadable option. If it is set to
5004 1, the DataDirectory will be made readable by the default GID.
5005 Implements part of ticket 17562. Patch from Jamie Nguyen.
5007 o Minor bugfixes (accounting):
5008 - The max bandwidth when using 'AccountRule sum' is now correctly
5009 logged. Fixes bug 18024; bugfix on 0.2.6.1-alpha. Patch
5012 o Minor bugfixes (assert, portability):
5013 - Fix an assertion failure in memarea.c on systems where "long" is
5014 shorter than the size of a pointer. Fixes bug 18716; bugfix
5017 o Minor bugfixes (bootstrap):
5018 - Consistently use the consensus download schedule for authority
5019 certificates. Fixes bug 18816; bugfix on 0.2.4.13-alpha.
5021 o Minor bugfixes (build):
5022 - Avoid spurious failures from configure files related to calling
5023 exit(0) in TOR_SEARCH_LIBRARY. Fixes bug 18626; bugfix on
5024 0.2.0.1-alpha. Patch from "cypherpunks".
5025 - Do not link the unit tests against both the testing and non-
5026 testing versions of the static libraries. Fixes bug 18490; bugfix
5028 - Resolve warnings when building on systems that are concerned with
5029 signed char. Fixes bug 18728; bugfix on 0.2.7.2-alpha
5031 - Silence spurious clang-scan warnings in the ed25519_donna code by
5032 explicitly initializing some objects. Fixes bug 18384; bugfix on
5033 0.2.7.2-alpha. Patch by teor.
5034 - When libscrypt.h is found, but no libscrypt library can be linked,
5035 treat libscrypt as absent. Fixes bug 19161; bugfix
5037 - Cause the unit tests to compile correctly on mingw64 versions that
5038 lack sscanf. Fixes bug 19213; bugfix on 0.2.7.1-alpha.
5039 - Don't try to use the pthread_condattr_setclock() function unless
5040 it actually exists. Fixes compilation on NetBSD-6.x. Fixes bug
5041 17819; bugfix on 0.2.6.3-alpha.
5042 - Fix backtrace compilation on FreeBSD. Fixes bug 17827; bugfix
5044 - Fix search for libevent libraries on OpenBSD (and other systems
5045 that install libevent 1 and libevent 2 in parallel). Fixes bug
5046 16651; bugfix on 0.1.0.7-rc. Patch from "rubiate".
5047 - Isolate environment variables meant for tests from the rest of the
5048 build system. Fixes bug 17818; bugfix on 0.2.7.3-rc.
5049 - Mark all object files that include micro-revision.i as depending
5050 on it, so as to make parallel builds more reliable. Fixes bug
5051 17826; bugfix on 0.2.5.1-alpha.
5052 - Remove config.log only from make distclean, not from make clean.
5053 Fixes bug 17924; bugfix on 0.2.4.1-alpha.
5054 - Replace usage of 'INLINE' with 'inline'. Fixes bug 17804; bugfix
5056 - Remove an #endif from configure.ac so that we correctly detect the
5057 presence of in6_addr.s6_addr32. Fixes bug 17923; bugfix
5060 o Minor bugfixes (client, bootstrap):
5061 - Count receipt of new microdescriptors as progress towards
5062 bootstrapping. Previously, with EntryNodes set, Tor might not
5063 successfully repopulate the guard set on bootstrapping. Fixes bug
5064 16825; bugfix on 0.2.3.1-alpha.
5066 o Minor bugfixes (code correctness):
5067 - Fix a bad memory handling bug that would occur if we had queued a
5068 cell on a channel's incoming queue. Fortunately, we can't actually
5069 queue a cell like that as our code is constructed today, but it's
5070 best to avoid this kind of error, even if there isn't any code
5071 that triggers it today. Fixes bug 18570; bugfix on 0.2.4.4-alpha.
5072 - Assert that allocated memory held by the reputation code is freed
5073 according to its internal counters. Fixes bug 17753; bugfix
5075 - Assert when the TLS contexts fail to initialize. Fixes bug 17683;
5077 - Update to the latest version of Trunnel, which tries harder to
5078 avoid generating code that can invoke memcpy(p,NULL,0). Bug found
5079 by clang address sanitizer. Fixes bug 18373; bugfix
5081 - When closing an entry connection, generate a warning if we should
5082 have sent an end cell for it but we haven't. Fixes bug 17876;
5083 bugfix on 0.2.3.2-alpha.
5085 o Minor bugfixes (configuration):
5086 - Fix a tiny memory leak when parsing a port configuration ending in
5087 ":auto". Fixes bug 18374; bugfix on 0.2.3.3-alpha.
5089 o Minor bugfixes (containers):
5090 - If we somehow attempt to construct a heap with more than
5091 1073741822 elements, avoid an integer overflow when maintaining
5092 the heap property. Fixes bug 18296; bugfix on 0.1.2.1-alpha.
5094 o Minor bugfixes (controller, microdescriptors):
5095 - Make GETINFO dir/status-vote/current/consensus conform to the
5096 control specification by returning "551 Could not open cached
5097 consensus..." when not caching consensuses. Fixes bug 18920;
5098 bugfix on 0.2.2.6-alpha.
5100 o Minor bugfixes (crypto):
5101 - Check the return value of HMAC() and assert on failure. Fixes bug
5102 17658; bugfix on 0.2.3.6-alpha. Patch by teor.
5104 o Minor bugfixes (directories):
5105 - When fetching extrainfo documents, compare their SHA256 digests
5106 and Ed25519 signing key certificates with the routerinfo that led
5107 us to fetch them, rather than with the most recent routerinfo.
5108 Otherwise we generate many spurious warnings about mismatches.
5109 Fixes bug 17150; bugfix on 0.2.7.2-alpha.
5110 - When generating a URL for a directory server on an IPv6 address,
5111 wrap the IPv6 address in square brackets. Fixes bug 18051; bugfix
5112 on 0.2.3.9-alpha. Patch from Malek.
5114 o Minor bugfixes (downloading):
5115 - Predict more correctly whether we'll be downloading over HTTP when
5116 we determine the maximum length of a URL. This should avoid a
5117 "BUG" warning about the Squid HTTP proxy and its URL limits. Fixes
5120 o Minor bugfixes (exit policies, security):
5121 - Refresh an exit relay's exit policy when interface addresses
5122 change. Previously, tor only refreshed the exit policy when the
5123 configured external address changed. Fixes bug 18208; bugfix on
5124 0.2.7.3-rc. Patch by teor.
5126 o Minor bugfixes (fallback directories):
5127 - Mark fallbacks as "too busy" when they return a 503 response,
5128 rather than just marking authorities. Fixes bug 17572; bugfix on
5129 0.2.4.7-alpha. Patch by teor.
5130 - When requesting extrainfo descriptors from a trusted directory
5131 server, check whether it is an authority or a fallback directory
5132 which supports extrainfo descriptors. Fixes bug 18489; bugfix on
5133 0.2.4.7-alpha. Reported by atagar, patch by teor.
5135 o Minor bugfixes (hidden service, client):
5136 - Handle the case where the user makes several fast consecutive
5137 requests to the same .onion address. Previously, the first six
5138 requests would each trigger a descriptor fetch, each picking a
5139 directory (there are 6 overall) and the seventh one would fail
5140 because no directories were left, thereby triggering a close on
5141 all current directory connections asking for the hidden service.
5142 The solution here is to not close the connections if we have
5143 pending directory fetches. Fixes bug 15937; bugfix
5146 o Minor bugfixes (hidden service, control port):
5147 - Add the onion address to the HS_DESC event for the UPLOADED action
5148 both on success or failure. It was previously hardcoded with
5149 UNKNOWN. Fixes bug 16023; bugfix on 0.2.7.2-alpha.
5151 o Minor bugfixes (hidden service, directory):
5152 - Bridges now refuse "rendezvous2" (hidden service descriptor)
5153 publish attempts. Suggested by ticket 18332.
5155 o Minor bugfixes (IPv6):
5156 - Update the limits in max_dl_per_request for IPv6 address length.
5157 Fixes bug 17573; bugfix on 0.2.1.5-alpha.
5159 o Minor bugfixes (Linux seccomp2 sandbox):
5160 - Allow more syscalls when running with "Sandbox 1" enabled:
5161 sysinfo, getsockopt(SO_SNDBUF), and setsockopt(SO_SNDBUFFORCE). On
5162 some systems, these are required for Tor to start. Fixes bug
5163 18397; bugfix on 0.2.5.1-alpha. Patch from Daniel Pinto.
5164 - Allow IPPROTO_UDP datagram sockets when running with "Sandbox 1",
5165 so that get_interface_address6_via_udp_socket_hack() can work.
5166 Fixes bug 19660; bugfix on 0.2.5.1-alpha.
5167 - Allow the setrlimit syscall, and the prlimit and prlimit64
5168 syscalls, which some libc implementations use under the hood.
5169 Fixes bug 15221; bugfix on 0.2.5.1-alpha.
5170 - Avoid a 10-second delay when starting as a client with "Sandbox 1"
5171 enabled and no DNS resolvers configured. This should help TAILS
5172 start up faster. Fixes bug 18548; bugfix on 0.2.5.1-alpha.
5173 - Fix a crash when using offline master ed25519 keys with the Linux
5174 seccomp2 sandbox enabled. Fixes bug 17675; bugfix on 0.2.7.3-rc.
5175 - Allow statistics to be written to disk when "Sandbox 1" is
5176 enabled. Fixes bugs 19556 and 19957; bugfix on 0.2.5.1-alpha and
5177 0.2.6.1-alpha respectively.
5179 o Minor bugfixes (logging):
5180 - In log messages that include a function name, use __FUNCTION__
5181 instead of __PRETTY_FUNCTION__. In GCC, these are synonymous, but
5182 with clang __PRETTY_FUNCTION__ has extra information we don't
5183 need. Fixes bug 16563; bugfix on 0.0.2pre8. Fix by Tom van
5185 - Remove needless quotes from a log message about unparseable
5186 addresses. Fixes bug 17843; bugfix on 0.2.3.3-alpha.
5187 - Scrub service name in "unrecognized service ID" log messages.
5188 Fixes bug 18600; bugfix on 0.2.4.11-alpha.
5189 - When logging information about an unparsable networkstatus vote or
5190 consensus, do not say "vote" when we mean consensus. Fixes bug
5191 18368; bugfix on 0.2.0.8-alpha.
5192 - When we can't generate a signing key because OfflineMasterKey is
5193 set, do not imply that we should have been able to load it. Fixes
5194 bug 18133; bugfix on 0.2.7.2-alpha.
5195 - When logging a malformed hostname received through socks4, scrub
5196 it if SafeLogging says we should. Fixes bug 17419; bugfix
5199 o Minor bugfixes (memory safety):
5200 - Avoid freeing an uninitialized pointer when opening a socket fails
5201 in get_interface_addresses_ioctl(). Fixes bug 18454; bugfix on
5202 0.2.3.11-alpha. Reported by toralf and "cypherpunks", patch
5204 - Fix a memory leak in "tor --list-fingerprint". Fixes part of bug
5205 18672; bugfix on 0.2.5.1-alpha.
5206 - Fix a memory leak in tor-gencert. Fixes part of bug 18672; bugfix
5209 o Minor bugfixes (pluggable transports):
5210 - Avoid reporting a spurious error when we decide that we don't need
5211 to terminate a pluggable transport because it has already exited.
5212 Fixes bug 18686; bugfix on 0.2.5.5-alpha.
5214 o Minor bugfixes (pointer arithmetic):
5215 - Fix a bug in memarea_alloc() that could have resulted in remote
5216 heap write access, if Tor had ever passed an unchecked size to
5217 memarea_alloc(). Fortunately, all the sizes we pass to
5218 memarea_alloc() are pre-checked to be less than 128 kilobytes.
5219 Fixes bug 19150; bugfix on 0.2.1.1-alpha. Bug found by
5222 o Minor bugfixes (private directory):
5223 - Prevent a race condition when creating private directories. Fixes
5224 part of bug 17852; bugfix on 0.0.2pre13. Part of ticket 17852.
5225 Patch from jsturgix. Found with Flawfinder.
5227 o Minor bugfixes (relays):
5228 - Check that both the ORPort and DirPort (if present) are reachable
5229 before publishing a relay descriptor. Otherwise, relays publish a
5230 descriptor with DirPort 0 when the DirPort reachability test takes
5231 longer than the ORPort reachability test. Fixes bug 18050; bugfix
5232 on 0.1.0.1-rc. Reported by "starlight", patch by teor.
5233 - Resolve some edge cases where we might launch an ORPort
5234 reachability check even when DisableNetwork is set. Noticed while
5235 fixing bug 18616; bugfix on 0.2.3.9-alpha.
5237 o Minor bugfixes (relays, hidden services):
5238 - Refuse connection requests to private OR addresses unless
5239 ExtendAllowPrivateAddresses is set. Previously, tor would connect,
5240 then refuse to send any cells to a private address. Fixes bugs
5241 17674 and 8976; bugfix on 0.2.3.21-rc. Patch by teor.
5243 o Minor bugfixes (security, hidden services):
5244 - Prevent hidden services connecting to client-supplied rendezvous
5245 addresses that are reserved as internal or multicast. Fixes bug
5246 8976; bugfix on 0.2.3.21-rc. Patch by dgoulet and teor.
5248 o Minor bugfixes (statistics):
5249 - Consistently check for overflow in round_*_to_next_multiple_of
5250 functions, and add unit tests with additional and maximal values.
5251 Fixes part of bug 13192; bugfix on 0.2.2.1-alpha.
5252 - Handle edge cases in the laplace functions: avoid division by
5253 zero, avoid taking the log of zero, and silence clang type
5254 conversion warnings using round and trunc. Add unit tests for edge
5255 cases with maximal values. Fixes part of bug 13192; bugfix
5257 - We now include consensus downloads via IPv6 in our directory-
5258 request statistics. Fixes bug 18460; bugfix on 0.2.3.14-alpha.
5260 o Minor bugfixes (test networks, IPv6):
5261 - Allow internal IPv6 addresses in descriptors in test networks.
5262 Fixes bug 17153; bugfix on 0.2.3.16-alpha. Patch by teor, reported
5265 o Minor bugfixes (testing):
5266 - Check the full results of SHA256 and SHA512 digests in the unit
5267 tests. Bugfix on 0.2.2.4-alpha. Patch by teor.
5268 - Fix a memory leak in the ntor test. Fixes bug 17778; bugfix
5270 - Fix a small memory leak that would occur when the
5271 TestingEnableCellStatsEvent option was turned on. Fixes bug 18673;
5272 bugfix on 0.2.5.2-alpha.
5273 - Make unit tests pass on IPv6-only systems, and systems without
5274 localhost addresses (like some FreeBSD jails). Fixes bug 17632;
5275 bugfix on 0.2.7.3-rc. Patch by teor.
5276 - The test for log_heartbeat was incorrectly failing in timezones
5277 with non-integer offsets. Instead of comparing the end of the time
5278 string against a constant, compare it to the output of
5279 format_local_iso_time when given the correct input. Fixes bug
5280 18039; bugfix on 0.2.5.4-alpha.
5281 - We no longer disable assertions in the unit tests when coverage is
5282 enabled. Instead, we require you to say --disable-asserts-in-tests
5283 to the configure script if you need assertions disabled in the
5284 unit tests (for example, if you want to perform branch coverage).
5285 Fixes bug 18242; bugfix on 0.2.7.1-alpha.
5287 o Minor bugfixes (time handling):
5288 - When correcting a corrupt 'struct tm' value, fill in the tm_wday
5289 field. Otherwise, our unit tests crash on Windows. Fixes bug
5290 18977; bugfix on 0.2.2.25-alpha.
5291 - Avoid overflow in tor_timegm when parsing dates in and after 2038
5292 on platforms with 32-bit time_t. Fixes bug 18479; bugfix on
5293 0.0.2pre14. Patch by teor.
5295 o Minor bugfixes (tor-gencert):
5296 - Correctly handle the case where an authority operator enters a
5297 passphrase but sends an EOF before sending a newline. Fixes bug
5298 17443; bugfix on 0.2.0.20-rc. Found by junglefowl.
5300 o Code simplification and refactoring:
5301 - Clean up a little duplicated code in
5302 crypto_expand_key_material_TAP(). Closes ticket 17587; patch
5304 - Decouple the list of streams waiting to be attached to circuits
5305 from the overall connection list. This change makes it possible to
5306 attach streams quickly while simplifying Tor's callgraph and
5307 avoiding O(N) scans of the entire connection list. Closes
5309 - Extract the more complicated parts of circuit_mark_for_close()
5310 into a new function that we run periodically before circuits are
5311 freed. This change removes more than half of the functions
5312 currently in the "blob". Closes ticket 17218.
5313 - Move logging of redundant policy entries in
5314 policies_parse_exit_policy_internal into its own function. Closes
5315 ticket 17608; patch from "juce".
5316 - Quote all the string interpolations in configure.ac -- even those
5317 which we are pretty sure can't contain spaces. Closes ticket
5318 17744. Patch from zerosion.
5319 - Remove code for configuring OpenSSL dynamic locks; OpenSSL doesn't
5320 use them. Closes ticket 17926.
5321 - Remove specialized code for non-inplace AES_CTR. 99% of our AES is
5322 inplace, so there's no need to have a separate implementation for
5323 the non-inplace code. Closes ticket 18258. Patch from Malek.
5324 - Simplify return types for some crypto functions that can't
5325 actually fail. Patch from Hassan Alsibyani. Closes ticket 18259.
5326 - When a direct directory request fails immediately on launch,
5327 instead of relaunching that request from inside the code that
5328 launches it, instead mark the connection for teardown. This change
5329 simplifies Tor's callback and prevents the directory-request
5330 launching code from invoking itself recursively. Closes
5334 - Add a description of the correct use of the '--keygen' command-
5335 line option. Closes ticket 17583; based on text by 's7r'.
5336 - Change build messages to refer to "Fedora" instead of "Fedora
5337 Core", and "dnf" instead of "yum". Closes tickets 18459 and 18426.
5338 Patches from "icanhasaccount" and "cypherpunks".
5339 - Document the contents of the 'datadir/keys' subdirectory in the
5340 manual page. Closes ticket 17621.
5341 - Document the minimum HeartbeatPeriod value. Closes ticket 15638.
5342 - Explain actual minima for BandwidthRate. Closes ticket 16382.
5343 - Fix a minor formatting typo in the manpage. Closes ticket 17791.
5344 - Mention torspec URL in the manpage and point the reader to it
5345 whenever we mention a document that belongs in torspce. Fixes
5347 - Stop recommending use of nicknames to identify relays in our
5348 MapAddress documentation. Closes ticket 18312.
5351 - Remove client-side support for connecting to Tor relays running
5352 versions of Tor before 0.2.3.6-alpha. These relays didn't support
5353 the v3 TLS handshake protocol, and are no longer allowed on the
5354 Tor network. Implements the client side of ticket 11150. Based on
5355 patches by Tom van der Woerdt.
5356 - We no longer maintain an internal freelist in memarea.c.
5357 Allocators should be good enough to make this code unnecessary,
5358 and it's doubtful that it ever had any performance benefit.
5361 - Add unit tests to check for common RNG failure modes, such as
5362 returning all zeroes, identical values, or incrementing values
5363 (OpenSSL's rand_predictable feature). Patch by teor.
5364 - Always test both ed25519 backends, so that we can be sure that our
5365 batch-open replacement code works. Part of ticket 16794.
5366 - Cover dns_resolve_impl() in dns.c with unit tests. Implements a
5367 portion of ticket 16831.
5368 - Fix several warnings from clang's address sanitizer produced in
5370 - Log more information when the backtrace tests fail. Closes ticket
5371 17892. Patch from "cypherpunks."
5372 - More unit tests for compat_libevent.c, procmon.c, tortls.c,
5373 util_format.c, directory.c, and options_validate.c. Closes tickets
5374 17075, 17082, 17084, 17003, and 17076 respectively. Patches from
5376 - Treat backtrace test failures as expected on FreeBSD until we
5377 solve bug 17808. Closes ticket 18204.
5378 - Unit tests for directory_handle_command_get. Closes ticket 17004.
5379 Patch from Reinaldo de Souza Jr.
5382 Changes in version 0.2.7.6 - 2015-12-10
5383 Tor version 0.2.7.6 fixes a major bug in entry guard selection, as
5384 well as a minor bug in hidden service reliability.
5386 o Major bugfixes (guard selection):
5387 - Actually look at the Guard flag when selecting a new directory
5388 guard. When we implemented the directory guard design, we
5389 accidentally started treating all relays as if they have the Guard
5390 flag during guard selection, leading to weaker anonymity and worse
5391 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
5394 o Minor features (geoip):
5395 - Update geoip and geoip6 to the December 1 2015 Maxmind GeoLite2
5398 o Minor bugfixes (compilation):
5399 - When checking for net/pfvar.h, include netinet/in.h if possible.
5400 This fixes transparent proxy detection on OpenBSD. Fixes bug
5401 17551; bugfix on 0.1.2.1-alpha. Patch from "rubiate".
5402 - Fix a compilation warning with Clang 3.6: Do not check the
5403 presence of an address which can never be NULL. Fixes bug 17781.
5405 o Minor bugfixes (correctness):
5406 - When displaying an IPv6 exit policy, include the mask bits
5407 correctly even when the number is greater than 31. Fixes bug
5408 16056; bugfix on 0.2.4.7-alpha. Patch from "gturner".
5409 - The wrong list was used when looking up expired intro points in a
5410 rend service object, causing what we think could be reachability
5411 issues for hidden services, and triggering a BUG log. Fixes bug
5412 16702; bugfix on 0.2.7.2-alpha.
5413 - Fix undefined behavior in the tor_cert_checksig function. Fixes
5414 bug 17722; bugfix on 0.2.7.2-alpha.
5417 Changes in version 0.2.7.5 - 2015-11-20
5418 The Tor 0.2.7 release series is dedicated to the memory of Tor user
5419 and privacy advocate Caspar Bowden (1961-2015). Caspar worked
5420 tirelessly to advocate human rights regardless of national borders,
5421 and oppose the encroachments of mass surveillance. He opposed national
5422 exceptionalism, he brought clarity to legal and policy debates, he
5423 understood and predicted the impact of mass surveillance on the world,
5424 and he laid the groundwork for resisting it. While serving on the Tor
5425 Project's board of directors, he brought us his uncompromising focus
5426 on technical excellence in the service of humankind. Caspar was an
5427 inimitable force for good and a wonderful friend. He was kind,
5428 humorous, generous, gallant, and believed we should protect one
5429 another without exception. We honor him here for his ideals, his
5430 efforts, and his accomplishments. Please honor his memory with works
5431 that would make him proud.
5433 Tor 0.2.7.5 is the first stable release in the Tor 0.2.7 series.
5435 The 0.2.7 series adds a more secure identity key type for relays,
5436 improves cryptography performance, resolves several longstanding
5437 hidden-service performance issues, improves controller support for
5438 hidden services, and includes small bugfixes and performance
5439 improvements throughout the program. This release series also includes
5440 more tests than before, and significant simplifications to which parts
5441 of Tor invoke which others. For a full list of changes, see below.
5443 o New system requirements:
5444 - Tor no longer includes workarounds to support Libevent versions
5445 before 1.3e. Libevent 2.0 or later is recommended. Closes
5447 - Tor no longer supports copies of OpenSSL that are missing support
5448 for Elliptic Curve Cryptography. (We began using ECC when
5449 available in 0.2.4.8-alpha, for more safe and efficient key
5450 negotiation.) In particular, support for at least one of P256 or
5451 P224 is now required, with manual configuration needed if only
5452 P224 is available. Resolves ticket 16140.
5453 - Tor no longer supports versions of OpenSSL before 1.0. (If you are
5454 on an operating system that has not upgraded to OpenSSL 1.0 or
5455 later, and you compile Tor from source, you will need to install a
5456 more recent OpenSSL to link Tor against.) These versions of
5457 OpenSSL are still supported by the OpenSSL, but the numerous
5458 cryptographic improvements in later OpenSSL releases makes them a
5459 clear choice. Resolves ticket 16034.
5461 o Major features (controller):
5462 - Add the ADD_ONION and DEL_ONION commands that allow the creation
5463 and management of hidden services via the controller. Closes
5465 - New "GETINFO onions/current" and "GETINFO onions/detached"
5466 commands to get information about hidden services created via the
5467 controller. Part of ticket 6411.
5468 - New HSFETCH command to launch a request for a hidden service
5469 descriptor. Closes ticket 14847.
5470 - New HSPOST command to upload a hidden service descriptor. Closes
5471 ticket 3523. Patch by "DonnchaC".
5473 o Major features (Ed25519 identity keys, Proposal 220):
5474 - Add support for offline encrypted Ed25519 master keys. To use this
5475 feature on your tor relay, run "tor --keygen" to make a new master
5476 key (or to make a new signing key if you already have a master
5477 key). Closes ticket 13642.
5478 - All relays now maintain a stronger identity key, using the Ed25519
5479 elliptic curve signature format. This master key is designed so
5480 that it can be kept offline. Relays also generate an online
5481 signing key, and a set of other Ed25519 keys and certificates.
5482 These are all automatically regenerated and rotated as needed.
5483 Implements part of ticket 12498.
5484 - Directory authorities now vote on Ed25519 identity keys along with
5485 RSA1024 keys. Implements part of ticket 12498.
5486 - Directory authorities track which Ed25519 identity keys have been
5487 used with which RSA1024 identity keys, and do not allow them to
5488 vary freely. Implements part of ticket 12498.
5489 - Microdescriptors now include Ed25519 identity keys. Implements
5490 part of ticket 12498.
5491 - Add a --newpass option to allow changing or removing the
5492 passphrase of an encrypted key with tor --keygen. Implements part
5494 - Add a new OfflineMasterKey option to tell Tor never to try loading
5495 or generating a secret Ed25519 identity key. You can use this in
5496 combination with tor --keygen to manage offline and/or encrypted
5497 Ed25519 keys. Implements ticket 16944.
5498 - On receiving a HUP signal, check to see whether the Ed25519
5499 signing key has changed, and reload it if so. Closes ticket 16790.
5500 - Significant usability improvements for Ed25519 key management. Log
5501 messages are better, and the code can recover from far more
5502 failure conditions. Thanks to "s7r" for reporting and diagnosing
5505 o Major features (ECC performance):
5506 - Improve the runtime speed of Ed25519 signature verification by
5507 using Ed25519-donna's batch verification support. Implements
5509 - Improve the speed of Ed25519 operations and Curve25519 keypair
5510 generation when built targeting 32 bit x86 platforms with SSE2
5511 available. Implements ticket 16535.
5512 - Improve the runtime speed of Ed25519 operations by using the
5513 public-domain Ed25519-donna by Andrew M. ("floodyberry").
5514 Implements ticket 16467.
5515 - Improve the runtime speed of the ntor handshake by using an
5516 optimized curve25519 basepoint scalarmult implementation from the
5517 public-domain Ed25519-donna by Andrew M. ("floodyberry"), based on
5518 ideas by Adam Langley. Implements ticket 9663.
5520 o Major features (Hidden services):
5521 - Hidden services, if using the EntryNodes option, are required to
5522 use more than one EntryNode, in order to avoid a guard discovery
5523 attack. (This would only affect people who had configured hidden
5524 services and manually specified the EntryNodes option with a
5525 single entry-node. The impact was that it would be easy to
5526 remotely identify the guard node used by such a hidden service.
5527 See ticket for more information.) Fixes ticket 14917.
5528 - Add the torrc option HiddenServiceNumIntroductionPoints, to
5529 specify a fixed number of introduction points. Its maximum value
5530 is 10 and default is 3. Using this option can increase a hidden
5531 service's reliability under load, at the cost of making it more
5532 visible that the hidden service is facing extra load. Closes
5534 - Remove the adaptive algorithm for choosing the number of
5535 introduction points, which used to change the number of
5536 introduction points (poorly) depending on the number of
5537 connections the HS sees. Closes ticket 4862.
5539 o Major features (onion key cross-certification):
5540 - Relay descriptors now include signatures of their own identity
5541 keys, made using the TAP and ntor onion keys. These signatures
5542 allow relays to prove ownership of their own onion keys. Because
5543 of this change, microdescriptors will no longer need to include
5544 RSA identity keys. Implements proposal 228; closes ticket 12499.
5546 o Major bugfixes (client-side privacy, also in 0.2.6.9):
5547 - Properly separate out each SOCKSPort when applying stream
5548 isolation. The error occurred because each port's session group
5549 was being overwritten by a default value when the listener
5550 connection was initialized. Fixes bug 16247; bugfix on
5551 0.2.6.3-alpha. Patch by "jojelino".
5553 o Major bugfixes (hidden service clients, stability, also in 0.2.6.10):
5554 - Stop refusing to store updated hidden service descriptors on a
5555 client. This reverts commit 9407040c59218 (which indeed fixed bug
5556 14219, but introduced a major hidden service reachability
5557 regression detailed in bug 16381). This is a temporary fix since
5558 we can live with the minor issue in bug 14219 (it just results in
5559 some load on the network) but the regression of 16381 is too much
5560 of a setback. First-round fix for bug 16381; bugfix
5563 o Major bugfixes (hidden services):
5564 - Revert commit that made directory authorities assign the HSDir
5565 flag to relays without a DirPort; this was bad because such relays
5566 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
5568 - When cannibalizing a circuit for an introduction point, always
5569 extend to the chosen exit node (creating a 4 hop circuit).
5570 Previously Tor would use the current circuit exit node, which
5571 changed the original choice of introduction point, and could cause
5572 the hidden service to skip excluded introduction points or
5573 reconnect to a skipped introduction point. Fixes bug 16260; bugfix
5576 o Major bugfixes (memory leaks):
5577 - Fix a memory leak in ed25519 batch signature checking. Fixes bug
5578 17398; bugfix on 0.2.6.1-alpha.
5580 o Major bugfixes (open file limit):
5581 - The open file limit wasn't checked before calling
5582 tor_accept_socket_nonblocking(), which would make Tor exceed the
5583 limit. Now, before opening a new socket, Tor validates the open
5584 file limit just before, and if the max has been reached, return an
5585 error. Fixes bug 16288; bugfix on 0.1.1.1-alpha.
5587 o Major bugfixes (security, correctness):
5588 - Fix an error that could cause us to read 4 bytes before the
5589 beginning of an openssl string. This bug could be used to cause
5590 Tor to crash on systems with unusual malloc implementations, or
5591 systems with unusual hardening installed. Fixes bug 17404; bugfix
5594 o Major bugfixes (stability, also in 0.2.6.10):
5595 - Stop crashing with an assertion failure when parsing certain kinds
5596 of malformed or truncated microdescriptors. Fixes bug 16400;
5597 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
5598 by "cypherpunks_backup".
5599 - Stop random client-side assertion failures that could occur when
5600 connecting to a busy hidden service, or connecting to a hidden
5601 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
5604 o Minor features (client, SOCKS):
5605 - Add GroupWritable and WorldWritable options to unix-socket based
5606 SocksPort and ControlPort options. These options apply to a single
5607 socket, and override {Control,Socks}SocketsGroupWritable. Closes
5609 - Relax the validation done to hostnames in SOCKS5 requests, and
5610 allow a single trailing '.' to cope with clients that pass FQDNs
5611 using that syntax to explicitly indicate that the domain name is
5612 fully-qualified. Fixes bug 16674; bugfix on 0.2.6.2-alpha.
5613 - Relax the validation of hostnames in SOCKS5 requests, allowing the
5614 character '_' to appear, in order to cope with domains observed in
5615 the wild that are serving non-RFC compliant records. Resolves
5618 o Minor features (client-side privacy):
5619 - New KeepAliveIsolateSOCKSAuth option to indefinitely extend circuit
5620 lifespan when IsolateSOCKSAuth and streams with SOCKS
5621 authentication are attached to the circuit. This allows
5622 applications like TorBrowser to manage circuit lifetime on their
5623 own. Implements feature 15482.
5624 - When logging malformed hostnames from SOCKS5 requests, respect
5625 SafeLogging configuration. Fixes bug 16891; bugfix on 0.1.1.16-rc.
5627 o Minor features (clock-jump tolerance):
5628 - Recover better when our clock jumps back many hours, like might
5629 happen for Tails or Whonix users who start with a very wrong
5630 hardware clock, use Tor to discover a more accurate time, and then
5631 fix their clock. Resolves part of ticket 8766.
5633 o Minor features (command-line interface):
5634 - Make --hash-password imply --hush to prevent unnecessary noise.
5635 Closes ticket 15542. Patch from "cypherpunks".
5636 - Print a warning whenever we find a relative file path being used
5637 as torrc option. Resolves issue 14018.
5639 o Minor features (compilation):
5640 - Give a warning as early as possible when trying to build with an
5641 unsupported OpenSSL version. Closes ticket 16901.
5642 - Use C99 variadic macros when the compiler is not GCC. This avoids
5643 failing compilations on MSVC, and fixes a log-file-based race
5644 condition in our old workarounds. Original patch from Gisle Vanem.
5646 o Minor features (control protocol):
5647 - Support network-liveness GETINFO key and NETWORK_LIVENESS event in
5648 the control protocol. Resolves ticket 15358.
5650 o Minor features (controller):
5651 - Add DirAuthority lines for default directory authorities to the
5652 output of the "GETINFO config/defaults" command if not already
5653 present. Implements ticket 14840.
5654 - Controllers can now use "GETINFO hs/client/desc/id/..." to
5655 retrieve items from the client's hidden service descriptor cache.
5656 Closes ticket 14845.
5657 - Implement a new controller command "GETINFO status/fresh-relay-
5658 descs" to fetch a descriptor/extrainfo pair that was generated on
5659 demand just for the controller's use. Implements ticket 14784.
5661 o Minor features (directory authorities):
5662 - Directory authorities no longer vote against the "Fast", "Stable",
5663 and "HSDir" flags just because they were going to vote against
5664 "Running": if the consensus turns out to be that the router was
5665 running, then the authority's vote should count. Patch from Peter
5666 Retzlaff; closes issue 8712.
5668 o Minor features (directory authorities, security, also in 0.2.6.9):
5669 - The HSDir flag given by authorities now requires the Stable flag.
5670 For the current network, this results in going from 2887 to 2806
5671 HSDirs. Also, it makes it harder for an attacker to launch a sybil
5672 attack by raising the effort for a relay to become Stable to
5673 require at the very least 7 days, while maintaining the 96 hours
5674 uptime requirement for HSDir. Implements ticket 8243.
5676 o Minor features (DoS-resistance):
5677 - Make it harder for attackers to overload hidden services with
5678 introductions, by blocking multiple introduction requests on the
5679 same circuit. Resolves ticket 15515.
5681 o Minor features (geoip):
5682 - Update geoip and geoip6 to the October 9 2015 Maxmind GeoLite2
5685 o Minor features (hidden services):
5686 - Add the new options "HiddenServiceMaxStreams" and
5687 "HiddenServiceMaxStreamsCloseCircuit" to allow hidden services to
5688 limit the maximum number of simultaneous streams per circuit, and
5689 optionally tear down the circuit when the limit is exceeded. Part
5691 - Client now uses an introduction point failure cache to know when
5692 to fetch or keep a descriptor in their cache. Previously, failures
5693 were recorded implicitly, but not explicitly remembered. Closes
5695 - Relays need to have the Fast flag to get the HSDir flag. As this
5696 is being written, we'll go from 2745 HSDirs down to 2342, a ~14%
5697 drop. This change should make some attacks against the hidden
5698 service directory system harder. Fixes ticket 15963.
5699 - Turn on hidden service statistics collection by setting the torrc
5700 option HiddenServiceStatistics to "1" by default. (This keeps
5701 track only of the fraction of traffic used by hidden services, and
5702 the total number of hidden services in existence.) Closes
5704 - To avoid leaking HS popularity, don't cycle the introduction point
5705 when we've handled a fixed number of INTRODUCE2 cells but instead
5706 cycle it when a random number of introductions is reached, thus
5707 making it more difficult for an attacker to find out the amount of
5708 clients that have used the introduction point for a specific HS.
5709 Closes ticket 15745.
5711 o Minor features (logging):
5712 - Include the Tor version in all LD_BUG log messages, since people
5713 tend to cut and paste those into the bugtracker. Implements
5716 o Minor features (pluggable transports):
5717 - When launching managed pluggable transports on Linux systems,
5718 attempt to have the kernel deliver a SIGTERM on tor exit if the
5719 pluggable transport process is still running. Resolves
5721 - When launching managed pluggable transports, setup a valid open
5722 stdin in the child process that can be used to detect if tor has
5723 terminated. The "TOR_PT_EXIT_ON_STDIN_CLOSE" environment variable
5724 can be used by implementations to detect this new behavior.
5725 Resolves ticket 15435.
5727 o Minor bugfixes (torrc exit policies):
5728 - In each instance above, usage advice is provided to avoid the
5729 message. Resolves ticket 16069. Patch by "teor". Fixes part of bug
5730 16069; bugfix on 0.2.4.7-alpha.
5731 - In torrc, "accept6 *" and "reject6 *" ExitPolicy lines now only
5732 produce IPv6 wildcard addresses. Previously they would produce
5733 both IPv4 and IPv6 wildcard addresses. Patch by "teor". Fixes part
5734 of bug 16069; bugfix on 0.2.4.7-alpha.
5735 - When parsing torrc ExitPolicies, we now issue an info-level
5736 message when expanding an "accept/reject *" line to include both
5737 IPv4 and IPv6 wildcard addresses. Related to ticket 16069.
5738 - When parsing torrc ExitPolicies, we now warn for a number of cases
5739 where the user's intent is likely to differ from Tor's actual
5740 behavior. These include: using an IPv4 address with an accept6 or
5741 reject6 line; using "private" on an accept6 or reject6 line; and
5742 including any ExitPolicy lines after accept *:* or reject *:*.
5743 Related to ticket 16069.
5745 o Minor bugfixes (command-line interface):
5746 - When "--quiet" is provided along with "--validate-config", do not
5747 write anything to stdout on success. Fixes bug 14994; bugfix
5749 - When complaining about bad arguments to "--dump-config", use
5751 - Print usage information for --dump-config when it is used without
5752 an argument. Also, fix the error message to use different wording
5753 and add newline at the end. Fixes bug 15541; bugfix
5756 o Minor bugfixes (compilation):
5757 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
5758 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
5759 - Repair compilation with the most recent (unreleased, alpha)
5760 vesions of OpenSSL 1.1. Fixes part of ticket 17237.
5762 o Minor bugfixes (compilation, also in 0.2.6.9):
5763 - Build with --enable-systemd correctly when libsystemd is
5764 installed, but systemd is not. Fixes bug 16164; bugfix on
5765 0.2.6.3-alpha. Patch from Peter Palfrader.
5767 o Minor bugfixes (configuration, unit tests):
5768 - Only add the default fallback directories when the DirAuthorities,
5769 AlternateDirAuthority, and FallbackDir directory config options
5770 are set to their defaults. The default fallback directory list is
5771 currently empty, this fix will only change tor's behavior when it
5772 has default fallback directories. Includes unit tests for
5773 consider_adding_dir_servers(). Fixes bug 15642; bugfix on
5774 90f6071d8dc0 in 0.2.4.7-alpha. Patch by "teor".
5776 o Minor bugfixes (controller):
5777 - Add the descriptor ID in each HS_DESC control event. It was
5778 missing, but specified in control-spec.txt. Fixes bug 15881;
5779 bugfix on 0.2.5.2-alpha.
5781 o Minor bugfixes (correctness):
5782 - For correctness, avoid modifying a constant string in
5783 handle_control_postdescriptor. Fixes bug 15546; bugfix
5785 - Remove side-effects from tor_assert() calls. This was harmless,
5786 because we never disable assertions, but it is bad style and
5787 unnecessary. Fixes bug 15211; bugfix on 0.2.5.5, 0.2.2.36,
5789 - When calling channel_free_list(), avoid calling smartlist_remove()
5790 while inside a FOREACH loop. This partially reverts commit
5791 17356fe7fd96af where the correct SMARTLIST_DEL_CURRENT was
5792 incorrectly removed. Fixes bug 16924; bugfix on 0.2.4.4-alpha.
5794 o Minor bugfixes (crypto error-handling, also in 0.2.6.10):
5795 - Check for failures from crypto_early_init, and refuse to continue.
5796 A previous typo meant that we could keep going with an
5797 uninitialized crypto library, and would have OpenSSL initialize
5798 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
5799 when implementing ticket 4900. Patch by "teor".
5801 o Minor bugfixes (hidden service):
5802 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
5803 a client authorized hidden service. Fixes bug 15823; bugfix
5805 - Remove an extraneous newline character from the end of hidden
5806 service descriptors. Fixes bug 15296; bugfix on 0.2.0.10-alpha.
5808 o Minor bugfixes (Linux seccomp2 sandbox):
5809 - Use the sandbox in tor_open_cloexec whether or not O_CLOEXEC is
5810 defined. Patch by "teor". Fixes bug 16515; bugfix on 0.2.3.1-alpha.
5811 - Allow bridge authorities to run correctly under the seccomp2
5812 sandbox. Fixes bug 16964; bugfix on 0.2.5.1-alpha.
5813 - Add the "hidserv-stats" filename to our sandbox filter for the
5814 HiddenServiceStatistics option to work properly. Fixes bug 17354;
5815 bugfix on 0.2.6.2-alpha. Patch from David Goulet.
5817 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.10):
5818 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
5819 these when eventfd2() support is missing. Fixes bug 16363; bugfix
5820 on 0.2.6.3-alpha. Patch from "teor".
5822 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.9):
5823 - Allow systemd connections to work with the Linux seccomp2 sandbox
5824 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
5826 - Fix sandboxing to work when running as a relay, by allowing the
5827 renaming of secret_id_key, and allowing the eventfd2 and futex
5828 syscalls. Fixes bug 16244; bugfix on 0.2.6.1-alpha. Patch by
5831 o Minor bugfixes (logging):
5832 - When building Tor under Clang, do not include an extra set of
5833 parentheses in log messages that include function names. Fixes bug
5834 15269; bugfix on every released version of Tor when compiled with
5835 recent enough Clang.
5837 o Minor bugfixes (network):
5838 - When attempting to use fallback technique for network interface
5839 lookup, disregard loopback and multicast addresses since they are
5840 unsuitable for public communications.
5842 o Minor bugfixes (open file limit):
5843 - Fix set_max_file_descriptors() to set by default the max open file
5844 limit to the current limit when setrlimit() fails. Fixes bug
5845 16274; bugfix on tor- 0.2.0.10-alpha. Patch by dgoulet.
5847 o Minor bugfixes (portability):
5848 - Check correctly for Windows socket errors in the workqueue
5849 backend. Fixes bug 16741; bugfix on 0.2.6.3-alpha.
5850 - Try harder to normalize the exit status of the Tor process to the
5851 standard-provided range. Fixes bug 16975; bugfix on every version
5853 - Use libexecinfo on FreeBSD to enable backtrace support. Fixes part
5854 of bug 17151; bugfix on 0.2.5.2-alpha. Patch from Marcin Cieślak.
5856 o Minor bugfixes (relay):
5857 - Ensure that worker threads actually exit when a fatal error or
5858 shutdown is indicated. This fix doesn't currently affect the
5859 behavior of Tor, because Tor workers never indicates fatal error
5860 or shutdown except in the unit tests. Fixes bug 16868; bugfix
5862 - Fix a rarely-encountered memory leak when failing to initialize
5863 the thread pool. Fixes bug 16631; bugfix on 0.2.6.3-alpha. Patch
5865 - Unblock threads before releasing the work queue mutex to ensure
5866 predictable scheduling behavior. Fixes bug 16644; bugfix
5869 o Minor bugfixes (security, exit policies):
5870 - ExitPolicyRejectPrivate now also rejects the relay's published
5871 IPv6 address (if any), and any publicly routable IPv4 or IPv6
5872 addresses on any local interfaces. ticket 17027. Patch by "teor".
5873 Fixes bug 17027; bugfix on 0.2.0.11-alpha.
5875 o Minor bugfixes (statistics):
5876 - Disregard the ConnDirectionStatistics torrc options when Tor is
5877 not a relay since in that mode of operation no sensible data is
5878 being collected and because Tor might run into measurement hiccups
5879 when running as a client for some time, then becoming a relay.
5880 Fixes bug 15604; bugfix on 0.2.2.35.
5882 o Minor bugfixes (systemd):
5883 - Tor's systemd unit file no longer contains extraneous spaces.
5884 These spaces would sometimes confuse tools like deb-systemd-
5885 helper. Fixes bug 16162; bugfix on 0.2.5.5-alpha.
5887 o Minor bugfixes (test networks):
5888 - When self-testing reachability, use ExtendAllowPrivateAddresses to
5889 determine if local/private addresses imply reachability. The
5890 previous fix used TestingTorNetwork, which implies
5891 ExtendAllowPrivateAddresses, but this excluded rare configurations
5892 where ExtendAllowPrivateAddresses is set but TestingTorNetwork is
5893 not. Fixes bug 15771; bugfix on 0.2.6.1-alpha. Patch by "teor",
5894 issue discovered by CJ Ess.
5896 o Minor bugfixes (tests, also in 0.2.6.9):
5897 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
5898 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
5900 o Code simplification and refactoring:
5901 - Change the function that's called when we need to retry all
5902 downloads so that it only reschedules the downloads to happen
5903 immediately, rather than launching them all at once itself. This
5904 further simplifies Tor's callgraph.
5905 - Define WINVER and _WIN32_WINNT centrally, in orconfig.h, in order
5906 to ensure they remain consistent and visible everywhere.
5907 - Move some format-parsing functions out of crypto.c and
5908 crypto_curve25519.c into crypto_format.c and/or util_format.c.
5909 - Move the client-only parts of init_keys() into a separate
5910 function. Closes ticket 16763.
5911 - Move the hacky fallback code out of get_interface_address6() into
5912 separate function and get it covered with unit-tests. Resolves
5914 - Refactor hidden service client-side cache lookup to intelligently
5915 report its various failure cases, and disentangle failure cases
5916 involving a lack of introduction points. Closes ticket 14391.
5917 - Remove some vestigial workarounds for the MSVC6 compiler. We
5918 haven't supported that in ages.
5919 - Remove the unused "nulterminate" argument from buf_pullup().
5920 - Simplify the microdesc_free() implementation so that it no longer
5921 appears (to code analysis tools) to potentially invoke a huge
5922 suite of other microdesc functions.
5923 - Simply the control graph further by deferring the inner body of
5924 directory_all_unreachable() into a callback. Closes ticket 16762.
5925 - The link authentication code has been refactored for better
5926 testability and reliability. It now uses code generated with the
5927 "trunnel" binary encoding generator, to reduce the risk of bugs
5928 due to programmer error. Done as part of ticket 12498.
5929 - Treat the loss of an owning controller as equivalent to a SIGTERM
5930 signal. This removes a tiny amount of duplicated code, and
5931 simplifies our callgraph. Closes ticket 16788.
5932 - Use our own Base64 encoder instead of OpenSSL's, to allow more
5933 control over the output. Part of ticket 15652.
5934 - When generating an event to send to the controller, we no longer
5935 put the event over the network immediately. Instead, we queue
5936 these events, and use a Libevent callback to deliver them. This
5937 change simplifies Tor's callgraph by reducing the number of
5938 functions from which all other Tor functions are reachable. Closes
5940 - Wrap Windows-only C files inside '#ifdef _WIN32' so that tools
5941 that try to scan or compile every file on Unix won't decide that
5945 - Fix capitalization of SOCKS in sample torrc. Closes ticket 15609.
5946 - Improve the descriptions of statistics-related torrc options in
5947 the manpage to describe rationale and possible uses cases. Fixes
5949 - Improve the layout and formatting of ./configure --help messages.
5950 Closes ticket 15024. Patch from "cypherpunks".
5951 - Include a specific and (hopefully) accurate documentation of the
5952 torrc file's meta-format in doc/torrc_format.txt. This is mainly
5953 of interest to people writing programs to parse or generate torrc
5954 files. This document is not a commitment to long-term
5955 compatibility; some aspects of the current format are a bit
5956 ridiculous. Closes ticket 2325.
5957 - Include the TUNING document in our source tarball. It is referred
5958 to in the ChangeLog and an error message. Fixes bug 16929; bugfix
5960 - Note that HiddenServicePorts can take a unix domain socket. Closes
5962 - Recommend a 40 GB example AccountingMax in torrc.sample rather
5963 than a 4 GB max. Closes ticket 16742.
5964 - Standardize on the term "server descriptor" in the manual page.
5965 Previously, we had used "router descriptor", "server descriptor",
5966 and "relay descriptor" interchangeably. Part of ticket 14987.
5967 - Advise users on how to configure separate IPv4 and IPv6 exit
5968 policies in the manpage and sample torrcs. Related to ticket 16069.
5969 - Fix an error in the manual page and comments for
5970 TestingDirAuthVoteHSDir[IsStrict], which suggested that a HSDir
5971 required "ORPort connectivity". While this is true, it is in no
5972 way unique to the HSDir flag. Of all the flags, only HSDirs need a
5973 DirPort configured in order for the authorities to assign that
5974 particular flag. Patch by "teor". Fixed as part of 14882; bugfix
5976 - Fix the usage message of tor-resolve(1) so that it no longer lists
5977 the removed -F option. Fixes bug 16913; bugfix on 0.2.2.28-beta.
5980 - Remove `USE_OPENSSL_BASE64` and the corresponding fallback code
5981 and always use the internal Base64 decoder. The internal decoder
5982 has been part of tor since 0.2.0.10-alpha, and no one should
5983 be using the OpenSSL one. Part of ticket 15652.
5984 - Remove the 'tor_strclear()' function; use memwipe() instead.
5985 Closes ticket 14922.
5986 - Remove the code that would try to aggressively flush controller
5987 connections while writing to them. This code was introduced in
5988 0.1.2.7-alpha, in order to keep output buffers from exceeding
5989 their limits. But there is no longer a maximum output buffer size,
5990 and flushing data in this way caused some undesirable recursions
5991 in our call graph. Closes ticket 16480.
5992 - The internal pure-C tor-fw-helper tool is now removed from the Tor
5993 distribution, in favor of the pure-Go clone available from
5994 https://gitweb.torproject.org/tor-fw-helper.git/ . The libraries
5995 used by the C tor-fw-helper are not, in our opinion, very
5996 confidence- inspiring in their secure-programming techniques.
5997 Closes ticket 13338.
6000 - Remove the (seldom-used) DynamicDHGroups feature. For anti-
6001 fingerprinting we now recommend pluggable transports; for forward-
6002 secrecy in TLS, we now use the P-256 group. Closes ticket 13736.
6003 - Remove the HidServDirectoryV2 option. Now all relays offer to
6004 store hidden service descriptors. Related to 16543.
6005 - Remove the VoteOnHidServDirectoriesV2 option, since all
6006 authorities have long set it to 1. Closes ticket 16543.
6007 - Remove the undocumented "--digests" command-line option. It
6008 complicated our build process, caused subtle build issues on
6009 multiple platforms, and is now redundant since we started
6010 including git version identifiers. Closes ticket 14742.
6011 - Tor no longer contains checks for ancient directory cache versions
6012 that didn't know about microdescriptors.
6013 - Tor no longer contains workarounds for stat files generated by
6014 super-old versions of Tor that didn't choose guards sensibly.
6017 - The test-network.sh script now supports performance testing.
6018 Requires corresponding chutney performance testing changes. Patch
6019 by "teor". Closes ticket 14175.
6020 - Add a new set of callgraph analysis scripts that use clang to
6021 produce a list of which Tor functions are reachable from which
6022 other Tor functions. We're planning to use these to help simplify
6023 our code structure by identifying illogical dependencies.
6024 - Add new 'test-full' and 'test-full-online' targets to run all
6025 tests, including integration tests with stem and chutney.
6026 - Autodetect CHUTNEY_PATH if the chutney and Tor sources are side-
6027 by-side in the same parent directory. Closes ticket 16903. Patch
6029 - Document use of coverity, clang static analyzer, and clang dynamic
6030 undefined behavior and address sanitizers in doc/HACKING. Include
6031 detailed usage instructions in the blacklist. Patch by "teor".
6032 Closes ticket 15817.
6033 - Make "bridges+hs" the default test network. This tests almost all
6034 tor functionality during make test-network, while allowing tests
6035 to succeed on non-IPv6 systems. Requires chutney commit 396da92 in
6036 test-network-bridges-hs. Closes tickets 16945 (tor) and 16946
6037 (chutney). Patches by "teor".
6038 - Make the test-workqueue test work on Windows by initializing the
6039 network before we begin.
6040 - New make target (make test-network-all) to run multiple applicable
6041 chutney test cases. Patch from Teor; closes 16953.
6042 - Now that OpenSSL has its own scrypt implementation, add an unit
6043 test that checks for interoperability between libscrypt_scrypt()
6044 and OpenSSL's EVP_PBE_scrypt() so that we could not use libscrypt
6045 and rely on EVP_PBE_scrypt() whenever possible. Resolves
6047 - The link authentication protocol code now has extensive tests.
6048 - The relay descriptor signature testing code now has
6050 - The test_workqueue program now runs faster, and is enabled by
6051 default as a part of "make check".
6052 - Unit test dns_resolve(), dns_clip_ttl() and dns_get_expiry_ttl()
6053 functions in dns.c. Implements a portion of ticket 16831.
6054 - Use environment variables rather than autoconf substitutions to
6055 send variables from the build system to the test scripts. This
6056 change should be easier to maintain, and cause 'make distcheck' to
6057 work better than before. Fixes bug 17148.
6058 - When building Tor with testing coverage enabled, run Chutney tests
6059 (if any) using the 'tor-cov' coverage binary.
6060 - When running test-network or test-stem, check for the absence of
6061 stem/chutney before doing any build operations.
6062 - Add a test to verify that the compiler does not eliminate our
6063 memwipe() implementation. Closes ticket 15377.
6064 - Add make rule `check-changes` to verify the format of changes
6065 files. Closes ticket 15180.
6066 - Add unit tests for control_event_is_interesting(). Add a compile-
6067 time check that the number of events doesn't exceed the capacity
6068 of control_event_t.event_mask. Closes ticket 15431, checks for
6069 bugs similar to 13085. Patch by "teor".
6070 - Command-line argument tests moved to Stem. Resolves ticket 14806.
6071 - Integrate the ntor, backtrace, and zero-length keys tests into the
6072 automake test suite. Closes ticket 15344.
6073 - Remove assertions during builds to determine Tor's test coverage.
6074 We don't want to trigger these even in assertions, so including
6075 them artificially makes our branch coverage look worse than it is.
6076 This patch provides the new test-stem-full and coverage-html-full
6077 configure options. Implements ticket 15400.
6078 - New TestingDirAuthVote{Exit,Guard,HSDir}IsStrict flags to
6079 explicitly manage consensus flags in testing networks. Patch by
6080 "robgjansen", modified by "teor". Implements part of ticket 14882.
6081 - Check for matching value in server response in ntor_ref.py. Fixes
6082 bug 15591; bugfix on 0.2.4.8-alpha. Reported and fixed
6084 - Set the severity correctly when testing
6085 get_interface_addresses_ifaddrs() and
6086 get_interface_addresses_win32(), so that the tests fail gracefully
6087 instead of triggering an assertion. Fixes bug 15759; bugfix on
6088 0.2.6.3-alpha. Reported by Nicolas Derive.
6090 Changes in version 0.2.6.10 - 2015-07-12
6091 Tor version 0.2.6.10 fixes some significant stability and hidden
6092 service client bugs, bulletproofs the cryptography init process, and
6093 fixes a bug when using the sandbox code with some older versions of
6094 Linux. Everyone running an older version, especially an older version
6095 of 0.2.6, should upgrade.
6097 o Major bugfixes (hidden service clients, stability):
6098 - Stop refusing to store updated hidden service descriptors on a
6099 client. This reverts commit 9407040c59218 (which indeed fixed bug
6100 14219, but introduced a major hidden service reachability
6101 regression detailed in bug 16381). This is a temporary fix since
6102 we can live with the minor issue in bug 14219 (it just results in
6103 some load on the network) but the regression of 16381 is too much
6104 of a setback. First-round fix for bug 16381; bugfix
6107 o Major bugfixes (stability):
6108 - Stop crashing with an assertion failure when parsing certain kinds
6109 of malformed or truncated microdescriptors. Fixes bug 16400;
6110 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
6111 by "cypherpunks_backup".
6112 - Stop random client-side assertion failures that could occur when
6113 connecting to a busy hidden service, or connecting to a hidden
6114 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
6117 o Minor features (geoip):
6118 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
6119 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
6121 o Minor bugfixes (crypto error-handling):
6122 - Check for failures from crypto_early_init, and refuse to continue.
6123 A previous typo meant that we could keep going with an
6124 uninitialized crypto library, and would have OpenSSL initialize
6125 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
6126 when implementing ticket 4900. Patch by "teor".
6128 o Minor bugfixes (Linux seccomp2 sandbox):
6129 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
6130 these when eventfd2() support is missing. Fixes bug 16363; bugfix
6131 on 0.2.6.3-alpha. Patch from "teor".
6134 Changes in version 0.2.6.9 - 2015-06-11
6135 Tor 0.2.6.9 fixes a regression in the circuit isolation code, increases the
6136 requirements for receiving an HSDir flag, and addresses some other small
6137 bugs in the systemd and sandbox code. Clients using circuit isolation
6138 should upgrade; all directory authorities should upgrade.
6140 o Major bugfixes (client-side privacy):
6141 - Properly separate out each SOCKSPort when applying stream
6142 isolation. The error occurred because each port's session group was
6143 being overwritten by a default value when the listener connection
6144 was initialized. Fixes bug 16247; bugfix on 0.2.6.3-alpha. Patch
6147 o Minor feature (directory authorities, security):
6148 - The HSDir flag given by authorities now requires the Stable flag.
6149 For the current network, this results in going from 2887 to 2806
6150 HSDirs. Also, it makes it harder for an attacker to launch a sybil
6151 attack by raising the effort for a relay to become Stable which
6152 takes at the very least 7 days to do so and by keeping the 96
6153 hours uptime requirement for HSDir. Implements ticket 8243.
6155 o Minor bugfixes (compilation):
6156 - Build with --enable-systemd correctly when libsystemd is
6157 installed, but systemd is not. Fixes bug 16164; bugfix on
6158 0.2.6.3-alpha. Patch from Peter Palfrader.
6160 o Minor bugfixes (Linux seccomp2 sandbox):
6161 - Fix sandboxing to work when running as a relaymby renaming of
6162 secret_id_key, and allowing the eventfd2 and futex syscalls. Fixes
6163 bug 16244; bugfix on 0.2.6.1-alpha. Patch by Peter Palfrader.
6164 - Allow systemd connections to work with the Linux seccomp2 sandbox
6165 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
6168 o Minor bugfixes (tests):
6169 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
6170 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
6173 Changes in version 0.2.6.8 - 2015-05-21
6174 Tor 0.2.6.8 fixes a bit of dodgy code in parsing INTRODUCE2 cells, and
6175 fixes an authority-side bug in assigning the HSDir flag. All directory
6176 authorities should upgrade.
6178 o Major bugfixes (hidden services, backport from 0.2.7.1-alpha):
6179 - Revert commit that made directory authorities assign the HSDir
6180 flag to relays without a DirPort; this was bad because such relays
6181 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
6184 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
6185 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
6186 a client authorized hidden service. Fixes bug 15823; bugfix
6189 o Minor features (geoip):
6190 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
6191 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
6195 Changes in version 0.2.6.7 - 2015-04-06
6196 Tor 0.2.6.7 fixes two security issues that could be used by an
6197 attacker to crash hidden services, or crash clients visiting hidden
6198 services. Hidden services should upgrade as soon as possible; clients
6199 should upgrade whenever packages become available.
6201 This release also contains two simple improvements to make hidden
6202 services a bit less vulnerable to denial-of-service attacks.
6204 o Major bugfixes (security, hidden service):
6205 - Fix an issue that would allow a malicious client to trigger an
6206 assertion failure and halt a hidden service. Fixes bug 15600;
6207 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
6208 - Fix a bug that could cause a client to crash with an assertion
6209 failure when parsing a malformed hidden service descriptor. Fixes
6210 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
6212 o Minor features (DoS-resistance, hidden service):
6213 - Introduction points no longer allow multiple INTRODUCE1 cells to
6214 arrive on the same circuit. This should make it more expensive for
6215 attackers to overwhelm hidden services with introductions.
6216 Resolves ticket 15515.
6217 - Decrease the amount of reattempts that a hidden service performs
6218 when its rendezvous circuits fail. This reduces the computational
6219 cost for running a hidden service under heavy load. Resolves
6223 Changes in version 0.2.5.12 - 2015-04-06
6224 Tor 0.2.5.12 backports two fixes from 0.2.6.7 for security issues that
6225 could be used by an attacker to crash hidden services, or crash clients
6226 visiting hidden services. Hidden services should upgrade as soon as
6227 possible; clients should upgrade whenever packages become available.
6229 This release also backports a simple improvement to make hidden
6230 services a bit less vulnerable to denial-of-service attacks.
6232 o Major bugfixes (security, hidden service):
6233 - Fix an issue that would allow a malicious client to trigger an
6234 assertion failure and halt a hidden service. Fixes bug 15600;
6235 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
6236 - Fix a bug that could cause a client to crash with an assertion
6237 failure when parsing a malformed hidden service descriptor. Fixes
6238 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
6240 o Minor features (DoS-resistance, hidden service):
6241 - Introduction points no longer allow multiple INTRODUCE1 cells to
6242 arrive on the same circuit. This should make it more expensive for
6243 attackers to overwhelm hidden services with introductions.
6244 Resolves ticket 15515.
6247 Changes in version 0.2.4.27 - 2015-04-06
6248 Tor 0.2.4.27 backports two fixes from 0.2.6.7 for security issues that
6249 could be used by an attacker to crash hidden services, or crash clients
6250 visiting hidden services. Hidden services should upgrade as soon as
6251 possible; clients should upgrade whenever packages become available.
6253 This release also backports a simple improvement to make hidden
6254 services a bit less vulnerable to denial-of-service attacks.
6256 o Major bugfixes (security, hidden service):
6257 - Fix an issue that would allow a malicious client to trigger an
6258 assertion failure and halt a hidden service. Fixes bug 15600;
6259 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
6260 - Fix a bug that could cause a client to crash with an assertion
6261 failure when parsing a malformed hidden service descriptor. Fixes
6262 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
6264 o Minor features (DoS-resistance, hidden service):
6265 - Introduction points no longer allow multiple INTRODUCE1 cells to
6266 arrive on the same circuit. This should make it more expensive for
6267 attackers to overwhelm hidden services with introductions.
6268 Resolves ticket 15515.
6271 Changes in version 0.2.6.6 - 2015-03-24
6272 Tor 0.2.6.6 is the first stable release in the 0.2.6 series.
6274 It adds numerous safety, security, correctness, and performance
6275 improvements. Client programs can be configured to use more kinds of
6276 sockets, AutomapHosts works better, the multithreading backend is
6277 improved, cell transmission is refactored, test coverage is much
6278 higher, more denial-of-service attacks are handled, guard selection is
6279 improved to handle long-term guards better, pluggable transports
6280 should work a bit better, and some annoying hidden service performance
6281 bugs should be addressed.
6283 o New compiler and system requirements:
6284 - Tor 0.2.6.x requires that your compiler support more of the C99
6285 language standard than before. The 'configure' script now detects
6286 whether your compiler supports C99 mid-block declarations and
6287 designated initializers. If it does not, Tor will not compile.
6289 We may revisit this requirement if it turns out that a significant
6290 number of people need to build Tor with compilers that don't
6291 bother implementing a 15-year-old standard. Closes ticket 13233.
6292 - Tor no longer supports systems without threading support. When we
6293 began working on Tor, there were several systems that didn't have
6294 threads, or where the thread support wasn't able to run the
6295 threads of a single process on multiple CPUs. That no longer
6296 holds: every system where Tor needs to run well now has threading
6297 support. Resolves ticket 12439.
6299 o Deprecated versions and removed support:
6300 - Tor relays older than 0.2.4.18-rc are no longer allowed to
6301 advertise themselves on the network. Closes ticket 13555.
6302 - Tor clients no longer support connecting to hidden services
6303 running on Tor 0.2.2.x and earlier; the Support022HiddenServices
6304 option has been removed. (There shouldn't be any hidden services
6305 running these versions on the network.) Closes ticket 7803.
6307 o Directory authority changes:
6308 - The directory authority Faravahar has a new IP address. This
6309 closes ticket 14487.
6310 - Remove turtles as a directory authority.
6311 - Add longclaw as a new (v3) directory authority. This implements
6312 ticket 13296. This keeps the directory authority count at 9.
6314 o Major features (bridges):
6315 - Expose the outgoing upstream HTTP/SOCKS proxy to pluggable
6316 transports if they are configured via the "TOR_PT_PROXY"
6317 environment variable. Implements proposal 232. Resolves
6320 o Major features (changed defaults):
6321 - Prevent relay operators from unintentionally running exits: When a
6322 relay is configured as an exit node, we now warn the user unless
6323 the "ExitRelay" option is set to 1. We warn even more loudly if
6324 the relay is configured with the default exit policy, since this
6325 can indicate accidental misconfiguration. Setting "ExitRelay 0"
6326 stops Tor from running as an exit relay. Closes ticket 10067.
6328 o Major features (client performance, hidden services):
6329 - Allow clients to use optimistic data when connecting to a hidden
6330 service, which should remove a round-trip from hidden service
6331 initialization. See proposal 181 for details. Implements
6334 o Major features (directory system):
6335 - Upon receiving an unparseable directory object, if its digest
6336 matches what we expected, then don't try to download it again.
6337 Previously, when we got a descriptor we didn't like, we would keep
6338 trying to download it over and over. Closes ticket 11243.
6339 - When downloading server- or microdescriptors from a directory
6340 server, we no longer launch multiple simultaneous requests to the
6341 same server. This reduces load on the directory servers,
6342 especially when directory guards are in use. Closes ticket 9969.
6343 - When downloading server- or microdescriptors over a tunneled
6344 connection, do not limit the length of our requests to what the
6345 Squid proxy is willing to handle. Part of ticket 9969.
6346 - Authorities can now vote on the correct digests and latest
6347 versions for different software packages. This allows packages
6348 that include Tor to use the Tor authority system as a way to get
6349 notified of updates and their correct digests. Implements proposal
6350 227. Closes ticket 10395.
6352 o Major features (guards):
6353 - Introduce the Guardfraction feature to improves load balancing on
6354 guard nodes. Specifically, it aims to reduce the traffic gap that
6355 guard nodes experience when they first get the Guard flag. This is
6356 a required step if we want to increase the guard lifetime to 9
6357 months or greater. Closes ticket 9321.
6359 o Major features (hidden services):
6360 - Make HS port scanning more difficult by immediately closing the
6361 circuit when a user attempts to connect to a nonexistent port.
6362 Closes ticket 13667.
6363 - Add a HiddenServiceStatistics option that allows Tor relays to
6364 gather and publish statistics about the overall size and volume of
6365 hidden service usage. Specifically, when this option is turned on,
6366 an HSDir will publish an approximate number of hidden services
6367 that have published descriptors to it the past 24 hours. Also, if
6368 a relay has acted as a hidden service rendezvous point, it will
6369 publish the approximate amount of rendezvous cells it has relayed
6370 the past 24 hours. The statistics themselves are obfuscated so
6371 that the exact values cannot be derived. For more details see
6372 proposal 238, "Better hidden service stats from Tor relays". This
6373 feature is currently disabled by default. Implements feature 13192.
6375 o Major features (performance):
6376 - Make the CPU worker implementation more efficient by avoiding the
6377 kernel and lengthening pipelines. The original implementation used
6378 sockets to transfer data from the main thread to the workers, and
6379 didn't allow any thread to be assigned more than a single piece of
6380 work at once. The new implementation avoids communications
6381 overhead by making requests in shared memory, avoiding kernel IO
6382 where possible, and keeping more requests in flight at once.
6383 Implements ticket 9682.
6385 o Major features (relay):
6386 - Raise the minimum acceptable configured bandwidth rate for bridges
6387 to 50 KiB/sec and for relays to 75 KiB/sec. (The old values were
6388 20 KiB/sec.) Closes ticket 13822.
6389 - Complete revision of the code that relays use to decide which cell
6390 to send next. Formerly, we selected the best circuit to write on
6391 each channel, but we didn't select among channels in any
6392 sophisticated way. Now, we choose the best circuits globally from
6393 among those whose channels are ready to deliver traffic.
6395 This patch implements a new inter-cmux comparison API, a global
6396 high/low watermark mechanism and a global scheduler loop for
6397 transmission prioritization across all channels as well as among
6398 circuits on one channel. This schedule is currently tuned to
6399 (tolerantly) avoid making changes in network performance, but it
6400 should form the basis for major circuit performance increases in
6401 the future. Code by Andrea; tuning by Rob Jansen; implements
6404 o Major features (sample torrc):
6405 - Add a new, infrequently-changed "torrc.minimal". This file is
6406 similar to torrc.sample, but it will change as infrequently as
6407 possible, for the benefit of users whose systems prompt them for
6408 intervention whenever a default configuration file is changed.
6409 Making this change allows us to update torrc.sample to be a more
6410 generally useful "sample torrc".
6412 o Major features (security, unix domain sockets):
6413 - Allow SocksPort to be an AF_UNIX Unix Domain Socket. Now high risk
6414 applications can reach Tor without having to create AF_INET or
6415 AF_INET6 sockets, meaning they can completely disable their
6416 ability to make non-Tor network connections. To create a socket of
6417 this type, use "SocksPort unix:/path/to/socket". Implements
6419 - Support mapping hidden service virtual ports to AF_UNIX sockets.
6420 The syntax is "HiddenServicePort 80 unix:/path/to/socket".
6421 Implements ticket 11485.
6423 o Major bugfixes (client, automap):
6424 - Repair automapping with IPv6 addresses. This automapping should
6425 have worked previously, but one piece of debugging code that we
6426 inserted to detect a regression actually caused the regression to
6427 manifest itself again. Fixes bug 13811 and bug 12831; bugfix on
6428 0.2.4.7-alpha. Diagnosed and fixed by Francisco Blas
6431 o Major bugfixes (crash, OSX, security):
6432 - Fix a remote denial-of-service opportunity caused by a bug in
6433 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
6436 o Major bugfixes (directory authorities):
6437 - Do not assign the HSDir flag to relays if they are not Valid, or
6438 currently hibernating. Fixes 12573; bugfix on 0.2.0.10-alpha.
6440 o Major bugfixes (directory bandwidth performance):
6441 - Don't flush the zlib buffer aggressively when compressing
6442 directory information for clients. This should save about 7% of
6443 the bandwidth currently used for compressed descriptors and
6444 microdescriptors. Fixes bug 11787; bugfix on 0.1.1.23.
6446 o Major bugfixes (exit node stability):
6447 - Fix an assertion failure that could occur under high DNS load.
6448 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
6449 diagnosed and fixed by "cypherpunks".
6451 o Major bugfixes (FreeBSD IPFW transparent proxy):
6452 - Fix address detection with FreeBSD transparent proxies, when
6453 "TransProxyType ipfw" is in use. Fixes bug 15064; bugfix
6456 o Major bugfixes (hidden services):
6457 - When closing an introduction circuit that was opened in parallel
6458 with others, don't mark the introduction point as unreachable.
6459 Previously, the first successful connection to an introduction
6460 point would make the other introduction points get marked as
6461 having timed out. Fixes bug 13698; bugfix on 0.0.6rc2.
6463 o Major bugfixes (Linux seccomp2 sandbox):
6464 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
6465 crash during attempts to call wait4. Fixes bug 15088; bugfix on
6466 0.2.5.1-alpha. Patch from "sanic".
6468 o Major bugfixes (mixed relay-client operation):
6469 - When running as a relay and client at the same time (not
6470 recommended), if we decide not to use a new guard because we want
6471 to retry older guards, only close the locally-originating circuits
6472 passing through that guard. Previously we would close all the
6473 circuits through that guard. Fixes bug 9819; bugfix on
6474 0.2.1.1-alpha. Reported by "skruffy".
6476 o Major bugfixes (pluggable transports):
6477 - Initialize the extended OR Port authentication cookie before
6478 launching pluggable transports. This prevents a race condition
6479 that occurred when server-side pluggable transports would cache the
6480 authentication cookie before it has been (re)generated. Fixes bug
6481 15240; bugfix on 0.2.5.1-alpha.
6483 o Major bugfixes (relay, stability, possible security):
6484 - Fix a bug that could lead to a relay crashing with an assertion
6485 failure if a buffer of exactly the wrong layout is passed to
6486 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
6487 0.2.0.10-alpha. Patch from "cypherpunks".
6488 - Do not assert if the 'data' pointer on a buffer is advanced to the
6489 very end of the buffer; log a BUG message instead. Only assert if
6490 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
6492 o Minor features (build):
6493 - New --disable-system-torrc compile-time option to prevent Tor from
6494 looking for the system-wide torrc or torrc-defaults files.
6495 Resolves ticket 13037.
6497 o Minor features (client):
6498 - Clients are now willing to send optimistic data (before they
6499 receive a 'connected' cell) to relays of any version. (Relays
6500 without support for optimistic data are no longer supported on the
6501 Tor network.) Resolves ticket 13153.
6503 o Minor features (client):
6504 - Validate hostnames in SOCKS5 requests more strictly. If SafeSocks
6505 is enabled, reject requests with IP addresses as hostnames.
6506 Resolves ticket 13315.
6508 o Minor features (controller):
6509 - Add a "SIGNAL HEARTBEAT" controller command that tells Tor to
6510 write an unscheduled heartbeat message to the log. Implements
6512 - Include SOCKS_USERNAME and SOCKS_PASSWORD values in controller
6513 events so controllers can observe circuit isolation inputs. Closes
6515 - ControlPort now supports the unix:/path/to/socket syntax as an
6516 alternative to the ControlSocket option, for consistency with
6517 SocksPort and HiddenServicePort. Closes ticket 14451.
6518 - New "GETINFO bw-event-cache" to get information about recent
6519 bandwidth events. Closes ticket 14128. Useful for controllers to
6520 get recent bandwidth history after the fix for ticket 13988.
6521 - Messages about problems in the bootstrap process now include
6522 information about the server we were trying to connect to when we
6523 noticed the problem. Closes ticket 15006.
6525 o Minor features (Denial of service resistance):
6526 - Count the total number of bytes used storing hidden service
6527 descriptors against the value of MaxMemInQueues. If we're low on
6528 memory, and more than 20% of our memory is used holding hidden
6529 service descriptors, free them until no more than 10% of our
6530 memory holds hidden service descriptors. Free the least recently
6531 fetched descriptors first. Resolves ticket 13806.
6532 - When we have recently been under memory pressure (over 3/4 of
6533 MaxMemInQueues is allocated), then allocate smaller zlib objects
6534 for small requests. Closes ticket 11791.
6536 o Minor features (directory authorities):
6537 - Don't list relays with a bandwidth estimate of 0 in the consensus.
6538 Implements a feature proposed during discussion of bug 13000.
6539 - In tor-gencert, report an error if the user provides the same
6540 argument more than once.
6541 - If a directory authority can't find a best consensus method in the
6542 votes that it holds, it now falls back to its favorite consensus
6543 method. Previously, it fell back to method 1. Neither of these is
6544 likely to get enough signatures, but "fall back to favorite"
6545 doesn't require us to maintain support an obsolete consensus
6546 method. Implements part of proposal 215.
6548 o Minor features (geoip):
6549 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
6550 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
6553 o Minor features (guard nodes):
6554 - Reduce the time delay before saving guard status to disk from 10
6555 minutes to 30 seconds (or from one hour to 10 minutes if
6556 AvoidDiskWrites is set). Closes ticket 12485.
6558 o Minor features (heartbeat):
6559 - On relays, report how many connections we negotiated using each
6560 version of the Tor link protocols. This information will let us
6561 know if removing support for very old versions of the Tor
6562 protocols is harming the network. Closes ticket 15212.
6564 o Minor features (hidden service):
6565 - Make Sybil attacks against hidden services harder by changing the
6566 minimum time required to get the HSDir flag from 25 hours up to 96
6567 hours. Addresses ticket 14149.
6568 - New option "HiddenServiceAllowUnknownPorts" to allow hidden
6569 services to disable the anti-scanning feature introduced in
6570 0.2.6.2-alpha. With this option not set, a connection to an
6571 unlisted port closes the circuit. With this option set, only a
6572 RELAY_DONE cell is sent. Closes ticket 14084.
6573 - When re-enabling the network, don't try to build introduction
6574 circuits until we have successfully built a circuit. This makes
6575 hidden services come up faster when the network is re-enabled.
6576 Patch from "akwizgran". Closes ticket 13447.
6577 - When we fail to retrieve a hidden service descriptor, send the
6578 controller an "HS_DESC FAILED" controller event. Implements
6580 - New HiddenServiceDirGroupReadable option to cause hidden service
6581 directories and hostname files to be created group-readable. Patch
6582 from "anon", David Stainton, and "meejah". Closes ticket 11291.
6584 o Minor features (interface):
6585 - Implement "-f -" command-line option to read torrc configuration
6586 from standard input, if you don't want to store the torrc file in
6587 the file system. Implements feature 13865.
6589 o Minor features (logging):
6590 - Add a count of unique clients to the bridge heartbeat message.
6591 Resolves ticket 6852.
6592 - Suppress "router info incompatible with extra info" message when
6593 reading extrainfo documents from cache. (This message got loud
6594 around when we closed bug 9812 in 0.2.6.2-alpha.) Closes
6596 - Elevate hidden service authorized-client message from DEBUG to
6597 INFO. Closes ticket 14015.
6598 - On Unix-like systems, you can now use named pipes as the target of
6599 the Log option, and other options that try to append to files.
6600 Closes ticket 12061. Patch from "carlo von lynX".
6601 - When opening a log file at startup, send it every log message that
6602 we generated between startup and opening it. Previously, log
6603 messages that were generated before opening the log file were only
6604 logged to stdout. Closes ticket 6938.
6605 - Add a TruncateLogFile option to overwrite logs instead of
6606 appending to them. Closes ticket 5583.
6607 - Quiet some log messages in the heartbeat and at startup. Closes
6610 o Minor features (portability, Solaris):
6611 - Threads are no longer disabled by default on Solaris; we believe
6612 that the versions of Solaris with broken threading support are all
6613 obsolete by now. Resolves ticket 9495.
6615 o Minor features (relay):
6616 - Re-check our address after we detect a changed IP address from
6617 getsockname(). This ensures that the controller command "GETINFO
6618 address" will report the correct value. Resolves ticket 11582.
6620 - A new AccountingRule option lets Relays set whether they'd like
6621 AccountingMax to be applied separately to inbound and outbound
6622 traffic, or applied to the sum of inbound and outbound traffic.
6623 Resolves ticket 961. Patch by "chobe".
6624 - When identity keypair is generated for first time, log a
6625 congratulatory message that links to the new relay lifecycle
6626 document. Implements feature 10427.
6628 o Minor features (security, memory wiping):
6629 - Ensure we securely wipe keys from memory after
6630 crypto_digest_get_digest and init_curve25519_keypair_from_file
6631 have finished using them. Resolves ticket 13477.
6633 o Minor features (security, out-of-memory handling):
6634 - When handling an out-of-memory condition, allocate less memory for
6635 temporary data structures. Fixes issue 10115.
6636 - When handling an out-of-memory condition, consider more types of
6637 buffers, including those on directory connections, and zlib
6638 buffers. Resolves ticket 11792.
6640 o Minor features (stability):
6641 - Add assertions in our hash-table iteration code to check for
6642 corrupted values that could cause infinite loops. Closes
6645 o Minor features (systemd):
6646 - Various improvements and modernizations in systemd hardening
6647 support. Closes ticket 13805. Patch from Craig Andrews.
6648 - Where supported, when running with systemd, report successful
6649 startup to systemd. Part of ticket 11016. Patch by Michael Scherer.
6650 - When running with systemd, support systemd watchdog messages. Part
6651 of ticket 11016. Patch by Michael Scherer.
6653 o Minor features (testing networks):
6654 - Add the TestingDirAuthVoteExit option, which lists nodes to assign
6655 the "Exit" flag regardless of their uptime, bandwidth, or exit
6656 policy. TestingTorNetwork must be set for this option to have any
6657 effect. Previously, authorities would take up to 35 minutes to
6658 give nodes the Exit flag in a test network. Partially implements
6660 - Drop the minimum RendPostPeriod on a testing network to 5 seconds,
6661 and the default on a testing network to 2 minutes. Drop the
6662 MIN_REND_INITIAL_POST_DELAY on a testing network to 5 seconds, but
6663 keep the default on a testing network at 30 seconds. This reduces
6664 HS bootstrap time to around 25 seconds. Also, change the default
6665 time in test-network.sh to match. Closes ticket 13401. Patch
6667 - Create TestingDirAuthVoteHSDir to correspond to
6668 TestingDirAuthVoteExit/Guard. Ensures that authorities vote the
6669 HSDir flag for the listed relays regardless of uptime or ORPort
6670 connectivity. Respects the value of VoteOnHidServDirectoriesV2.
6671 Partial implementation for ticket 14067. Patch by "teor".
6673 o Minor features (tor2web mode):
6674 - Introduce the config option Tor2webRendezvousPoints, which allows
6675 clients in Tor2webMode to select a specific Rendezvous Point to be
6676 used in HS circuits. This might allow better performance for
6677 Tor2Web nodes. Implements ticket 12844.
6679 o Minor features (transparent proxy):
6680 - Update the transparent proxy option checks to allow for both ipfw
6681 and pf on OS X. Closes ticket 14002.
6682 - Use the correct option when using IPv6 with transparent proxy
6683 support on Linux. Resolves 13808. Patch by Francisco Blas
6686 o Minor features (validation):
6687 - Check all date/time values passed to tor_timegm and
6688 parse_rfc1123_time for validity, taking leap years into account.
6689 Improves HTTP header validation. Implemented with bug 13476.
6690 - In correct_tm(), limit the range of values returned by system
6691 localtime(_r) and gmtime(_r) to be between the years 1 and 8099.
6692 This means we don't have to deal with negative or too large dates,
6693 even if a clock is wrong. Otherwise we might fail to read a file
6694 written by us which includes such a date. Fixes bug 13476.
6695 - Stop allowing invalid address patterns like "*/24" that contain
6696 both a wildcard address and a bit prefix length. This affects all
6697 our address-range parsing code. Fixes bug 7484; bugfix
6700 o Minor bugfixes (bridge clients):
6701 - When configured to use a bridge without an identity digest (not
6702 recommended), avoid launching an extra channel to it when
6703 bootstrapping. Fixes bug 7733; bugfix on 0.2.4.4-alpha.
6705 o Minor bugfixes (bridges):
6706 - When DisableNetwork is set, do not launch pluggable transport
6707 plugins, and if any are running, terminate them. Fixes bug 13213;
6708 bugfix on 0.2.3.6-alpha.
6710 o Minor bugfixes (C correctness):
6711 - Fix several instances of possible integer overflow/underflow/NaN.
6712 Fixes bug 13104; bugfix on 0.2.3.1-alpha and later. Patches
6714 - In circuit_build_times_calculate_timeout() in circuitstats.c,
6715 avoid dividing by zero in the pareto calculations. This traps
6716 under clang's "undefined-trap" sanitizer. Fixes bug 13290; bugfix
6718 - Fix an integer overflow in format_time_interval(). Fixes bug
6719 13393; bugfix on 0.2.0.10-alpha.
6720 - Set the correct day of year value when the system's localtime(_r)
6721 or gmtime(_r) functions fail to set struct tm. Not externally
6722 visible. Fixes bug 13476; bugfix on 0.0.2pre14.
6723 - Avoid unlikely signed integer overflow in tor_timegm on systems
6724 with 32-bit time_t. Fixes bug 13476; bugfix on 0.0.2pre14.
6726 o Minor bugfixes (certificate handling):
6727 - If an authority operator accidentally makes a signing certificate
6728 with a future publication time, do not discard its real signing
6729 certificates. Fixes bug 11457; bugfix on 0.2.0.3-alpha.
6730 - Remove any old authority certificates that have been superseded
6731 for at least two days. Previously, we would keep superseded
6732 certificates until they expired, if they were published close in
6733 time to the certificate that superseded them. Fixes bug 11454;
6734 bugfix on 0.2.1.8-alpha.
6736 o Minor bugfixes (client):
6737 - Fix smartlist_choose_node_by_bandwidth() so that relays with the
6738 BadExit flag are not considered worthy candidates. Fixes bug
6739 13066; bugfix on 0.1.2.3-alpha.
6740 - Use the consensus schedule for downloading consensuses, and not
6741 the generic schedule. Fixes bug 11679; bugfix on 0.2.2.6-alpha.
6742 - Handle unsupported or malformed SOCKS5 requests properly by
6743 responding with the appropriate error message before closing the
6744 connection. Fixes bugs 12971 and 13314; bugfix on 0.0.2pre13.
6746 o Minor bugfixes (client, automapping):
6747 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
6748 no value follows the option. Fixes bug 14142; bugfix on
6749 0.2.4.7-alpha. Patch by "teor".
6750 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
6751 14195; bugfix on 0.1.0.1-rc.
6752 - Prevent changes to other options from removing the wildcard value
6753 "." from "AutomapHostsSuffixes". Fixes bug 12509; bugfix
6755 - Allow MapAddress and AutomapHostsOnResolve to work together when
6756 an address is mapped into another address type (like .onion) that
6757 must be automapped at resolve time. Fixes bug 7555; bugfix
6760 o Minor bugfixes (client, bridges):
6761 - When we are using bridges and we had a network connectivity
6762 problem, only retry connecting to our currently configured
6763 bridges, not all bridges we know about and remember using. Fixes
6764 bug 14216; bugfix on 0.2.2.17-alpha.
6766 o Minor bugfixes (client, DNS):
6767 - Report the correct cached DNS expiration times on SOCKS port or in
6768 DNS replies. Previously, we would report everything as "never
6769 expires." Fixes bug 14193; bugfix on 0.2.3.17-beta.
6770 - Avoid a small memory leak when we find a cached answer for a
6771 reverse DNS lookup in a client-side DNS cache. (Remember, client-
6772 side DNS caching is off by default, and is not recommended.) Fixes
6773 bug 14259; bugfix on 0.2.0.1-alpha.
6775 o Minor bugfixes (client, IPv6):
6776 - Reject socks requests to literal IPv6 addresses when IPv6Traffic
6777 flag is not set; and not because the NoIPv4Traffic flag was set.
6778 Previously we'd looked at the NoIPv4Traffic flag for both types of
6779 literal addresses. Fixes bug 14280; bugfix on 0.2.4.7-alpha.
6781 o Minor bugfixes (client, microdescriptors):
6782 - Use a full 256 bits of the SHA256 digest of a microdescriptor when
6783 computing which microdescriptors to download. This keeps us from
6784 erroneous download behavior if two microdescriptor digests ever
6785 have the same first 160 bits. Fixes part of bug 13399; bugfix
6787 - Reset a router's status if its microdescriptor digest changes,
6788 even if the first 160 bits remain the same. Fixes part of bug
6789 13399; bugfix on 0.2.3.1-alpha.
6791 o Minor bugfixes (client, torrc):
6792 - Stop modifying the value of our DirReqStatistics torrc option just
6793 because we're not a bridge or relay. This bug was causing Tor
6794 Browser users to write "DirReqStatistics 0" in their torrc files
6795 as if they had chosen to change the config. Fixes bug 4244; bugfix
6797 - When GeoIPExcludeUnknown is enabled, do not incorrectly decide
6798 that our options have changed every time we SIGHUP. Fixes bug
6799 9801; bugfix on 0.2.4.10-alpha. Patch from "qwerty1".
6801 o Minor bugfixes (compilation):
6802 - Fix a compilation warning on s390. Fixes bug 14988; bugfix
6804 - Silence clang warnings under --enable-expensive-hardening,
6805 including implicit truncation of 64 bit values to 32 bit, const
6806 char assignment to self, tautological compare, and additional
6807 parentheses around equality tests. Fixes bug 13577; bugfix
6809 - Fix a clang warning about checking whether an address in the
6810 middle of a structure is NULL. Fixes bug 14001; bugfix
6812 - The address of an array in the middle of a structure will always
6813 be non-NULL. clang recognises this and complains. Disable the
6814 tautologous and redundant check to silence this warning. Fixes bug
6815 14001; bugfix on 0.2.1.2-alpha.
6816 - Compile correctly with (unreleased) OpenSSL 1.1.0 headers.
6817 Addresses ticket 14188.
6818 - Build without warnings with the stock OpenSSL srtp.h header, which
6819 has a duplicate declaration of SSL_get_selected_srtp_profile().
6820 Fixes bug 14220; this is OpenSSL's bug, not ours.
6821 - Do not compile any code related to Tor2Web mode when Tor2Web mode
6822 is not enabled at compile time. Previously, this code was included
6823 in a disabled state. See discussion on ticket 12844.
6824 - Allow our configure script to build correctly with autoconf 2.62
6825 again. Fixes bug 12693; bugfix on 0.2.5.2-alpha.
6826 - Improve the error message from ./configure to make it clear that
6827 when asciidoc has not been found, the user will have to either add
6828 --disable-asciidoc argument or install asciidoc. Resolves
6831 o Minor bugfixes (controller):
6832 - Report "down" in response to the "GETINFO entry-guards" command
6833 when relays are down with an unreachable_since value. Previously,
6834 we would report "up". Fixes bug 14184; bugfix on 0.1.2.2-alpha.
6835 - Avoid crashing on a malformed EXTENDCIRCUIT command. Fixes bug
6836 14116; bugfix on 0.2.2.9-alpha.
6838 o Minor bugfixes (controller):
6839 - Return an error when the second or later arguments of the
6840 "setevents" controller command are invalid events. Previously we
6841 would return success while silently skipping invalid events. Fixes
6842 bug 13205; bugfix on 0.2.3.2-alpha. Reported by "fpxnns".
6844 o Minor bugfixes (directory authority):
6845 - Allow directory authorities to fetch more data from one another if
6846 they find themselves missing lots of votes. Previously, they had
6847 been bumping against the 10 MB queued data limit. Fixes bug 14261;
6848 bugfix on 0.1.2.5-alpha.
6849 - Do not attempt to download extrainfo documents which we will be
6850 unable to validate with a matching server descriptor. Fixes bug
6851 13762; bugfix on 0.2.0.1-alpha.
6852 - Fix a bug that was truncating AUTHDIR_NEWDESC events sent to the
6853 control port. Fixes bug 14953; bugfix on 0.2.0.1-alpha.
6854 - Enlarge the buffer to read bwauth generated files to avoid an
6855 issue when parsing the file in dirserv_read_measured_bandwidths().
6856 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
6857 - When running as a v3 directory authority, advertise that you serve
6858 extra-info documents so that clients who want them can find them
6859 from you too. Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
6861 o Minor bugfixes (directory system):
6862 - Always believe that v3 directory authorities serve extra-info
6863 documents, whether they advertise "caches-extra-info" or not.
6864 Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
6865 - Check the BRIDGE_DIRINFO flag bitwise rather than using equality.
6866 Previously, directories offering BRIDGE_DIRINFO and some other
6867 flag (i.e. microdescriptors or extrainfo) would be ignored when
6868 looking for bridges. Partially fixes bug 13163; bugfix
6871 o Minor bugfixes (file handling):
6872 - Stop failing when key files are zero-length. Instead, generate new
6873 keys, and overwrite the empty key files. Fixes bug 13111; bugfix
6874 on all versions of Tor. Patch by "teor".
6875 - Stop generating a fresh .old RSA onion key file when the .old file
6876 is missing. Fixes part of 13111; bugfix on 0.0.6rc1.
6877 - Avoid overwriting .old key files with empty key files.
6878 - Skip loading zero-length extrainfo store, router store, stats,
6879 state, and key files.
6880 - Avoid crashing when trying to reload a torrc specified as a
6881 relative path with RunAsDaemon turned on. Fixes bug 13397; bugfix
6884 o Minor bugfixes (hidden services):
6885 - Close the introduction circuit when we have no more usable intro
6886 points, instead of waiting for it to time out. This also ensures
6887 that no follow-up HS descriptor fetch is triggered when the
6888 circuit eventually times out. Fixes bug 14224; bugfix on 0.0.6.
6889 - When fetching a hidden service descriptor for a down service that
6890 was recently up, do not keep refetching until we try the same
6891 replica twice in a row. Fixes bug 14219; bugfix on 0.2.0.10-alpha.
6892 - Correctly send a controller event when we find that a rendezvous
6893 circuit has finished. Fixes bug 13936; bugfix on 0.1.1.5-alpha.
6894 - Pre-check directory permissions for new hidden-services to avoid
6895 at least one case of "Bug: Acting on config options left us in a
6896 broken state. Dying." Fixes bug 13942; bugfix on 0.0.6pre1.
6897 - When fetching hidden service descriptors, we now check not only
6898 for whether we got the hidden service we had in mind, but also
6899 whether we got the particular descriptors we wanted. This prevents
6900 a class of inefficient but annoying DoS attacks by hidden service
6901 directories. Fixes bug 13214; bugfix on 0.2.1.6-alpha. Reported
6904 o Minor bugfixes (Linux seccomp2 sandbox):
6905 - Make transparent proxy support work along with the seccomp2
6906 sandbox. Fixes part of bug 13808; bugfix on 0.2.5.1-alpha. Patch
6907 by Francisco Blas Izquierdo Riera.
6908 - Fix a memory leak in tor-resolve when running with the sandbox
6909 enabled. Fixes bug 14050; bugfix on 0.2.5.9-rc.
6910 - Allow glibc fatal errors to be sent to stderr before Tor exits.
6911 Previously, glibc would try to write them to /dev/tty, and the
6912 sandbox would trap the call and make Tor exit prematurely. Fixes
6913 bug 14759; bugfix on 0.2.5.1-alpha.
6915 o Minor bugfixes (logging):
6916 - Avoid crashing when there are more log domains than entries in
6917 domain_list. Bugfix on 0.2.3.1-alpha.
6918 - Downgrade warnings about RSA signature failures to info log level.
6919 Emit a warning when an extra info document is found incompatible
6920 with a corresponding router descriptor. Fixes bug 9812; bugfix
6922 - Make connection_ap_handshake_attach_circuit() log the circuit ID
6923 correctly. Fixes bug 13701; bugfix on 0.0.6.
6925 o Minor bugfixes (networking):
6926 - Check for orconns and use connection_or_close_for_error() rather
6927 than connection_mark_for_close() directly in the getsockopt()
6928 failure case of connection_handle_write_impl(). Fixes bug 11302;
6929 bugfix on 0.2.4.4-alpha.
6931 o Minor bugfixes (parsing):
6932 - Stop accepting milliseconds (or other junk) at the end of
6933 descriptor publication times. Fixes bug 9286; bugfix on 0.0.2pre25.
6934 - Support two-number and three-number version numbers correctly, in
6935 case we change the Tor versioning system in the future. Fixes bug
6936 13661; bugfix on 0.0.8pre1.
6938 o Minor bugfixes (portability):
6939 - Fix the ioctl()-based network interface lookup code so that it
6940 will work on systems that have variable-length struct ifreq, for
6942 - Use the correct datatype in the SipHash-2-4 function to prevent
6943 compilers from assuming any sort of alignment. Fixes bug 15436;
6944 bugfix on 0.2.5.3-alpha.
6946 o Minor bugfixes (preventative security, C safety):
6947 - When reading a hexadecimal, base-32, or base-64 encoded value from
6948 a string, always overwrite the whole output buffer. This prevents
6949 some bugs where we would look at (but fortunately, not reveal)
6950 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
6952 - Clear all memory targeted by tor_addr_{to,from}_sockaddr(), not
6953 just the part that's used. This makes it harder for data leak bugs
6954 to occur in the event of other programming failures. Resolves
6957 o Minor bugfixes (relay):
6958 - When generating our family list, remove spaces from around the
6959 entries. Fixes bug 12728; bugfix on 0.2.1.7-alpha.
6960 - If our previous bandwidth estimate was 0 bytes, allow publishing a
6961 new relay descriptor immediately. Fixes bug 13000; bugfix
6964 o Minor bugfixes (shutdown):
6965 - When shutting down, always call event_del() on lingering read or
6966 write events before freeing them. Otherwise, we risk double-frees
6967 or read-after-frees in event_base_free(). Fixes bug 12985; bugfix
6970 o Minor bugfixes (small memory leaks):
6971 - Avoid leaking memory when using IPv6 virtual address mappings.
6972 Fixes bug 14123; bugfix on 0.2.4.7-alpha. Patch by Tom van
6975 o Minor bugfixes (statistics):
6976 - Increase period over which bandwidth observations are aggregated
6977 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
6979 o Minor bugfixes (systemd support):
6980 - Run correctly under systemd with the RunAsDaemon option set. Fixes
6981 part of bug 14141; bugfix on 0.2.5.7-rc. Patch from Tomasz Torcz.
6982 - Inform the systemd supervisor about more changes in the Tor
6983 process status. Implements part of ticket 14141. Patch from
6986 o Minor bugfixes (testing networks):
6987 - Fix TestingDirAuthVoteGuard to properly give out Guard flags in a
6988 testing network. Fixes bug 13064; bugfix on 0.2.5.2-alpha.
6989 - Stop using the default authorities in networks which provide both
6990 AlternateDirAuthority and AlternateBridgeAuthority. Partially
6991 fixes bug 13163; bugfix on 0.2.0.13-alpha.
6993 o Minor bugfixes (testing networks, fast startup):
6994 - Allow Tor to build circuits using a consensus with no exits. If
6995 the consensus has no exits (typical of a bootstrapping test
6996 network), allow Tor to build circuits once enough descriptors have
6997 been downloaded. This assists in bootstrapping a testing Tor
6998 network. Fixes bug 13718; bugfix on 0.2.4.10-alpha. Patch
7000 - When V3AuthVotingInterval is low, give a lower If-Modified-Since
7001 header to directory servers. This allows us to obtain consensuses
7002 promptly when the consensus interval is very short. This assists
7003 in bootstrapping a testing Tor network. Fixes parts of bugs 13718
7004 and 13963; bugfix on 0.2.0.3-alpha. Patch by "teor".
7005 - Stop assuming that private addresses are local when checking
7006 reachability in a TestingTorNetwork. Instead, when testing, assume
7007 all OR connections are remote. (This is necessary due to many test
7008 scenarios running all relays on localhost.) This assists in
7009 bootstrapping a testing Tor network. Fixes bug 13924; bugfix on
7010 0.1.0.1-rc. Patch by "teor".
7011 - Avoid building exit circuits from a consensus with no exits. Now
7012 thanks to our fix for 13718, we accept a no-exit network as not
7013 wholly lost, but we need to remember not to try to build exit
7014 circuits on it. Closes ticket 13814; patch by "teor".
7015 - Stop requiring exits to have non-zero bandwithcapacity in a
7016 TestingTorNetwork. Instead, when TestingMinExitFlagThreshold is 0,
7017 ignore exit bandwidthcapacity. This assists in bootstrapping a
7018 testing Tor network. Fixes parts of bugs 13718 and 13839; bugfix
7019 on 0.2.0.3-alpha. Patch by "teor".
7020 - Add "internal" to some bootstrap statuses when no exits are
7021 available. If the consensus does not contain Exits, Tor will only
7022 build internal circuits. In this case, relevant statuses will
7023 contain the word "internal" as indicated in the Tor control-
7024 spec.txt. When bootstrap completes, Tor will be ready to build
7025 internal circuits. If a future consensus contains Exits, exit
7026 circuits may become available. Fixes part of bug 13718; bugfix on
7027 0.2.4.10-alpha. Patch by "teor".
7028 - Decrease minimum consensus interval to 10 seconds when
7029 TestingTorNetwork is set, or 5 seconds for the first consensus.
7030 Fix assumptions throughout the code that assume larger intervals.
7031 Fixes bugs 13718 and 13823; bugfix on 0.2.0.3-alpha. Patch
7033 - Avoid excluding guards from path building in minimal test
7034 networks, when we're in a test network and excluding guards would
7035 exclude all relays. This typically occurs in incredibly small tor
7036 networks, and those using "TestingAuthVoteGuard *". Fixes part of
7037 bug 13718; bugfix on 0.1.1.11-alpha. Patch by "teor".
7039 o Minor bugfixes (testing):
7040 - Avoid a side-effect in a tor_assert() in the unit tests. Fixes bug
7041 15188; bugfix on 0.1.2.3-alpha. Patch from Tom van der Woerdt.
7042 - Stop spawn test failures due to a race condition between the
7043 SIGCHLD handler updating the process status, and the test reading
7044 it. Fixes bug 13291; bugfix on 0.2.3.3-alpha.
7045 - Avoid passing an extra backslash when creating a temporary
7046 directory for running the unit tests on Windows. Fixes bug 12392;
7047 bugfix on 0.2.2.25-alpha. Patch from Gisle Vanem.
7049 o Minor bugfixes (TLS):
7050 - Check more thoroughly throughout the TLS code for possible
7051 unlogged TLS errors. Possible diagnostic or fix for bug 13319.
7053 o Minor bugfixes (transparent proxy):
7054 - Use getsockname, not getsockopt, to retrieve the address for a
7055 TPROXY-redirected connection. Fixes bug 13796; bugfix
7058 o Minor bugfixes (windows):
7059 - Remove code to special-case handling of NTE_BAD_KEYSET when
7060 acquiring windows CryptoAPI context. This error can't actually
7061 occur for the parameters we're providing. Fixes bug 10816; bugfix
7064 o Minor bugfixes (zlib):
7065 - Avoid truncating a zlib stream when trying to finalize it with an
7066 empty output buffer. Fixes bug 11824; bugfix on 0.1.1.23.
7068 o Code simplification and refactoring:
7069 - Change the entry_is_live() function to take named bitfield
7070 elements instead of an unnamed list of booleans. Closes
7072 - Refactor and unit-test entry_is_time_to_retry() in entrynodes.c.
7073 Resolves ticket 12205.
7074 - Use calloc and reallocarray functions instead of multiply-
7075 then-malloc. This makes it less likely for us to fall victim to an
7076 integer overflow attack when allocating. Resolves ticket 12855.
7077 - Use the standard macro name SIZE_MAX, instead of our
7079 - Document usage of the NO_DIRINFO and ALL_DIRINFO flags clearly in
7080 functions which take them as arguments. Replace 0 with NO_DIRINFO
7081 in a function call for clarity. Seeks to prevent future issues
7083 - Avoid 4 null pointer errors under clang static analysis by using
7084 tor_assert() to prove that the pointers aren't null. Fixes
7086 - Rework the API of policies_parse_exit_policy() to use a bitmask to
7087 represent parsing options, instead of a confusing mess of
7088 booleans. Resolves ticket 8197.
7089 - Introduce a helper function to parse ExitPolicy in
7090 or_options_t structure.
7091 - Move fields related to isolating and configuring client ports into
7092 a shared structure. Previously, they were duplicated across
7093 port_cfg_t, listener_connection_t, and edge_connection_t. Failure
7094 to copy them correctly had been the cause of at least one bug in
7095 the past. Closes ticket 8546.
7096 - Refactor the get_interface_addresses_raw() doom-function into
7097 multiple smaller and simpler subfunctions. Cover the resulting
7098 subfunctions with unit-tests. Fixes a significant portion of
7100 - Remove workaround in dirserv_thinks_router_is_hs_dir() that was
7101 only for version <= 0.2.2.24 which is now deprecated. Closes
7103 - Remove a test for a long-defunct broken version-one
7105 - Refactor main loop to extract the 'loop' part. This makes it
7106 easier to run Tor under Shadow. Closes ticket 15176.
7107 - Stop using can_complete_circuits as a global variable; access it
7108 with a function instead.
7109 - Avoid using operators directly as macro arguments: this lets us
7110 apply coccinelle transformations to our codebase more directly.
7111 Closes ticket 13172.
7112 - Combine the functions used to parse ClientTransportPlugin and
7113 ServerTransportPlugin into a single function. Closes ticket 6456.
7114 - Add inline functions and convenience macros for inspecting channel
7115 state. Refactor the code to use convenience macros instead of
7116 checking channel state directly. Fixes issue 7356.
7117 - Document all members of was_router_added_t and rename
7118 ROUTER_WAS_NOT_NEW to ROUTER_IS_ALREADY_KNOWN to make it less
7119 confusable with ROUTER_WAS_TOO_OLD. Fixes issue 13644.
7120 - In connection_exit_begin_conn(), use END_CIRC_REASON_TORPROTOCOL
7121 constant instead of hardcoded value. Fixes issue 13840.
7122 - Refactor our generic strmap and digestmap types into a single
7123 implementation, so that we can add a new digest256map
7127 - Add a doc/TUNING document with tips for handling large numbers of
7128 TCP connections when running busy Tor relay. Update the warning
7129 message to point to this file when running out of sockets
7130 operating system is allowing to use simultaneously. Resolves
7132 - Adding section on OpenBSD to our TUNING document. Thanks to mmcc
7133 for writing the OpenBSD-specific tips. Resolves ticket 13702.
7134 - Make the tor-resolve documentation match its help string and its
7135 options. Resolves part of ticket 14325.
7136 - Log a more useful error message from tor-resolve when failing to
7137 look up a hidden service address. Resolves part of ticket 14325.
7138 - Document the bridge-authority-only 'networkstatus-bridges' file.
7139 Closes ticket 13713; patch from "tom".
7140 - Fix typo in PredictedPortsRelevanceTime option description in
7141 manpage. Resolves issue 13707.
7142 - Stop suggesting that users specify relays by nickname: it isn't a
7143 good idea. Also, properly cross-reference how to specify relays in
7144 all parts of manual documenting options that take a list of
7145 relays. Closes ticket 13381.
7146 - Clarify the HiddenServiceDir option description in manpage to make
7147 it clear that relative paths are taken with respect to the current
7148 working directory. Also clarify that this behavior is not
7149 guaranteed to remain indefinitely. Fixes issue 13913.
7151 o Distribution (systemd):
7152 - systemd unit file: only allow tor to write to /var/lib/tor and
7153 /var/log/tor. The rest of the filesystem is accessible for reading
7154 only. Patch by intrigeri; resolves ticket 12751.
7155 - systemd unit file: ensure that the process and all its children
7156 can never gain new privileges. Patch by intrigeri; resolves
7158 - systemd unit file: set up /var/run/tor as writable for the Tor
7159 service. Patch by intrigeri; resolves ticket 13196.
7161 o Downgraded warnings:
7162 - Don't warn when we've attempted to contact a relay using the wrong
7163 ntor onion key. Closes ticket 9635.
7166 - Remove some lingering dead code that once supported mempools.
7167 Mempools were disabled by default in 0.2.5, and removed entirely
7168 in 0.2.6.3-alpha. Closes more of ticket 14848; patch
7171 o Removed features (directory authorities):
7172 - Remove code that prevented authorities from listing Tor relays
7173 affected by CVE-2011-2769 as guards. These relays are already
7174 rejected altogether due to the minimum version requirement of
7175 0.2.3.16-alpha. Closes ticket 13152.
7176 - The "AuthDirRejectUnlisted" option no longer has any effect, as
7177 the fingerprints file (approved-routers) has been deprecated.
7178 - Directory authorities do not support being Naming dirauths anymore.
7179 The "NamingAuthoritativeDir" config option is now obsolete.
7180 - Directory authorities do not support giving out the BadDirectory
7182 - Directory authorities no longer advertise or support consensus
7183 methods 1 through 12 inclusive. These consensus methods were
7184 obsolete and/or insecure: maintaining the ability to support them
7185 served no good purpose. Implements part of proposal 215; closes
7189 - To avoid confusion with the "ExitRelay" option, "ExitNode" is no
7190 longer silently accepted as an alias for "ExitNodes".
7191 - The --enable-mempool and --enable-buf-freelists options, which
7192 were originally created to work around bad malloc implementations,
7193 no longer exist. They were off-by-default in 0.2.5. Closes
7195 - We no longer remind the user about configuration options that have
7196 been obsolete since 0.2.3.x or earlier. Patch by Adrien Bak.
7197 - Remove our old, non-weighted bandwidth-based node selection code.
7198 Previously, we used it as a fallback when we couldn't perform
7199 weighted bandwidth-based node selection. But that would only
7200 happen in the cases where we had no consensus, or when we had a
7201 consensus generated by buggy or ancient directory authorities. In
7202 either case, it's better to use the more modern, better maintained
7203 algorithm, with reasonable defaults for the weights. Closes
7205 - Remove the --disable-curve25519 configure option. Relays and
7206 clients now are required to support curve25519 and the
7208 - The old "StrictEntryNodes" and "StrictExitNodes" options, which
7209 used to be deprecated synonyms for "StrictNodes", are now marked
7210 obsolete. Resolves ticket 12226.
7211 - Clients don't understand the BadDirectory flag in the consensus
7212 anymore, and ignore it.
7214 o Removed platform support:
7215 - We no longer include special code to build on Windows CE; as far
7216 as we know, nobody has used Tor on Windows CE in a very long time.
7217 Closes ticket 11446.
7219 o Testing (test-network.sh):
7220 - Stop using "echo -n", as some shells' built-in echo doesn't
7221 support "-n". Instead, use "/bin/echo -n". Partially fixes
7223 - Stop an apparent test-network hang when used with make -j2. Fixes
7225 - Add a --delay option to test-network.sh, which configures the
7226 delay before the chutney network tests for data transmission.
7227 Partially implements ticket 13161.
7230 - Test that tor does not fail when key files are zero-length. Check
7231 that tor generates new keys, and overwrites the empty key files.
7232 - Test that tor generates new keys when keys are missing
7233 (existing behavior).
7234 - Test that tor does not overwrite key files that already contain
7235 data (existing behavior). Tests bug 13111. Patch by "teor".
7236 - New "make test-stem" target to run stem integration tests.
7237 Requires that the "STEM_SOURCE_DIR" environment variable be set.
7238 Closes ticket 14107.
7239 - Make the test_cmdline_args.py script work correctly on Windows.
7240 Patch from Gisle Vanem.
7241 - Move the slower unit tests into a new "./src/test/test-slow"
7242 binary that can be run independently of the other tests. Closes
7244 - New tests for many parts of channel, relay, and circuitmux
7245 functionality. Code by Andrea; part of 9262.
7246 - New tests for parse_transport_line(). Part of ticket 6456.
7247 - In the unit tests, use chgrp() to change the group of the unit
7248 test temporary directory to the current user, so that the sticky
7249 bit doesn't interfere with tests that check directory groups.
7251 - Add unit tests for resolve_my_addr(). Part of ticket 12376; patch
7253 - Refactor the function that chooses guard nodes so that it can more
7254 easily be tested; write some tests for it.
7255 - Fix and re-enable the fgets_eagain unit test. Fixes bug 12503;
7256 bugfix on 0.2.3.1-alpha. Patch from "cypherpunks."
7257 - Create unit tests for format_time_interval(). With bug 13393.
7258 - Add unit tests for tor_timegm signed overflow, tor_timegm and
7259 parse_rfc1123_time validity checks, correct_tm year clamping. Unit
7260 tests (visible) fixes in bug 13476.
7261 - Add a "coverage-html" make target to generate HTML-visualized
7262 coverage results when building with --enable-coverage. (Requires
7263 lcov.) Patch from Kevin Murray.
7264 - Enable the backtrace handler (where supported) when running the
7266 - Revise all unit tests that used the legacy test_* macros to
7267 instead use the recommended tt_* macros. This patch was generated
7268 with coccinelle, to avoid manual errors. Closes ticket 13119.
7270 Changes in version 0.2.5.11 - 2015-03-17
7271 Tor 0.2.5.11 is the second stable release in the 0.2.5 series.
7273 It backports several bugfixes from the 0.2.6 branch, including a
7274 couple of medium-level security fixes for relays and exit nodes.
7275 It also updates the list of directory authorities.
7277 o Directory authority changes:
7278 - Remove turtles as a directory authority.
7279 - Add longclaw as a new (v3) directory authority. This implements
7280 ticket 13296. This keeps the directory authority count at 9.
7281 - The directory authority Faravahar has a new IP address. This
7282 closes ticket 14487.
7284 o Major bugfixes (crash, OSX, security):
7285 - Fix a remote denial-of-service opportunity caused by a bug in
7286 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
7289 o Major bugfixes (relay, stability, possible security):
7290 - Fix a bug that could lead to a relay crashing with an assertion
7291 failure if a buffer of exactly the wrong layout was passed to
7292 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
7293 0.2.0.10-alpha. Patch from 'cypherpunks'.
7294 - Do not assert if the 'data' pointer on a buffer is advanced to the
7295 very end of the buffer; log a BUG message instead. Only assert if
7296 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
7298 o Major bugfixes (exit node stability):
7299 - Fix an assertion failure that could occur under high DNS load.
7300 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
7301 diagnosed and fixed by "cypherpunks".
7303 o Major bugfixes (Linux seccomp2 sandbox):
7304 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
7305 crash during attempts to call wait4. Fixes bug 15088; bugfix on
7306 0.2.5.1-alpha. Patch from "sanic".
7308 o Minor features (controller):
7309 - New "GETINFO bw-event-cache" to get information about recent
7310 bandwidth events. Closes ticket 14128. Useful for controllers to
7311 get recent bandwidth history after the fix for ticket 13988.
7313 o Minor features (geoip):
7314 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
7315 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
7318 o Minor bugfixes (client, automapping):
7319 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
7320 no value follows the option. Fixes bug 14142; bugfix on
7321 0.2.4.7-alpha. Patch by "teor".
7322 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
7323 14195; bugfix on 0.1.0.1-rc.
7325 o Minor bugfixes (compilation):
7326 - Build without warnings with the stock OpenSSL srtp.h header, which
7327 has a duplicate declaration of SSL_get_selected_srtp_profile().
7328 Fixes bug 14220; this is OpenSSL's bug, not ours.
7330 o Minor bugfixes (directory authority):
7331 - Allow directory authorities to fetch more data from one another if
7332 they find themselves missing lots of votes. Previously, they had
7333 been bumping against the 10 MB queued data limit. Fixes bug 14261;
7334 bugfix on 0.1.2.5-alpha.
7335 - Enlarge the buffer to read bwauth generated files to avoid an
7336 issue when parsing the file in dirserv_read_measured_bandwidths().
7337 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
7339 o Minor bugfixes (statistics):
7340 - Increase period over which bandwidth observations are aggregated
7341 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
7343 o Minor bugfixes (preventative security, C safety):
7344 - When reading a hexadecimal, base-32, or base-64 encoded value from
7345 a string, always overwrite the whole output buffer. This prevents
7346 some bugs where we would look at (but fortunately, not reveal)
7347 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
7351 Changes in version 0.2.4.26 - 2015-03-17
7352 Tor 0.2.4.26 includes an updated list of directory authorities. It
7353 also backports a couple of stability and security bugfixes from 0.2.5
7356 o Directory authority changes:
7357 - Remove turtles as a directory authority.
7358 - Add longclaw as a new (v3) directory authority. This implements
7359 ticket 13296. This keeps the directory authority count at 9.
7360 - The directory authority Faravahar has a new IP address. This
7361 closes ticket 14487.
7363 o Major bugfixes (exit node stability, also in 0.2.6.3-alpha):
7364 - Fix an assertion failure that could occur under high DNS load.
7365 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
7366 diagnosed and fixed by "cypherpunks".
7368 o Major bugfixes (relay, stability, possible security, also in 0.2.6.4-rc):
7369 - Fix a bug that could lead to a relay crashing with an assertion
7370 failure if a buffer of exactly the wrong layout was passed to
7371 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
7372 0.2.0.10-alpha. Patch from 'cypherpunks'.
7373 - Do not assert if the 'data' pointer on a buffer is advanced to the
7374 very end of the buffer; log a BUG message instead. Only assert if
7375 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
7377 o Minor features (geoip):
7378 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
7379 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
7382 Changes in version 0.2.5.10 - 2014-10-24
7383 Tor 0.2.5.10 is the first stable release in the 0.2.5 series.
7385 It adds several new security features, including improved
7386 denial-of-service resistance for relays, new compiler hardening
7387 options, and a system-call sandbox for hardened installations on Linux
7388 (requires seccomp2). The controller protocol has several new features,
7389 resolving IPv6 addresses should work better than before, and relays
7390 should be a little more CPU-efficient. We've added support for more
7391 OpenBSD and FreeBSD transparent proxy types. We've improved the build
7392 system and testing infrastructure to allow unit testing of more parts
7393 of the Tor codebase. Finally, we've addressed several nagging pluggable
7394 transport usability issues, and included numerous other small bugfixes
7395 and features mentioned below.
7397 This release marks end-of-life for Tor 0.2.3.x; those Tor versions
7398 have accumulated many known flaws; everyone should upgrade.
7400 o Major features (security):
7401 - The ntor handshake is now on-by-default, no matter what the
7402 directory authorities recommend. Implements ticket 8561.
7403 - Make the "tor-gencert" tool used by directory authority operators
7404 create 2048-bit signing keys by default (rather than 1024-bit, since
7405 1024-bit is uncomfortably small these days). Addresses ticket 10324.
7406 - Warn about attempts to run hidden services and relays in the same
7407 process: that's probably not a good idea. Closes ticket 12908.
7408 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
7409 today support TLS 1.0 or later, so we can safely turn off support
7410 for this old (and insecure) protocol. Fixes bug 13426.
7412 o Major features (relay security, DoS-resistance):
7413 - When deciding whether we have run out of memory and we need to
7414 close circuits, also consider memory allocated in buffers for
7415 streams attached to each circuit.
7417 This change, which extends an anti-DoS feature introduced in
7418 0.2.4.13-alpha and improved in 0.2.4.14-alpha, lets Tor exit relays
7419 better resist more memory-based DoS attacks than before. Since the
7420 MaxMemInCellQueues option now applies to all queues, it is renamed
7421 to MaxMemInQueues. This feature fixes bug 10169.
7422 - Avoid hash-flooding denial-of-service attacks by using the secure
7423 SipHash-2-4 hash function for our hashtables. Without this
7424 feature, an attacker could degrade performance of a targeted
7425 client or server by flooding their data structures with a large
7426 number of entries to be stored at the same hash table position,
7427 thereby slowing down the Tor instance. With this feature, hash
7428 table positions are derived from a randomized cryptographic key,
7429 and an attacker cannot predict which entries will collide. Closes
7431 - If you don't specify MaxMemInQueues yourself, Tor now tries to
7432 pick a good value based on your total system memory. Previously,
7433 the default was always 8 GB. You can still override the default by
7434 setting MaxMemInQueues yourself. Resolves ticket 11396.
7436 o Major features (bridges and pluggable transports):
7437 - Add support for passing arguments to managed pluggable transport
7438 proxies. Implements ticket 3594.
7439 - Bridges now track GeoIP information and the number of their users
7440 even when pluggable transports are in use, and report usage
7441 statistics in their extra-info descriptors. Resolves tickets 4773
7443 - Don't launch pluggable transport proxies if we don't have any
7444 bridges configured that would use them. Now we can list many
7445 pluggable transports, and Tor will dynamically start one when it
7446 hears a bridge address that needs it. Resolves ticket 5018.
7447 - The bridge directory authority now assigns status flags (Stable,
7448 Guard, etc) to bridges based on thresholds calculated over all
7449 Running bridges. Now bridgedb can finally make use of its features
7450 to e.g. include at least one Stable bridge in its answers. Fixes
7453 o Major features (controller):
7454 - Extend ORCONN controller event to include an "ID" parameter,
7455 and add four new controller event types CONN_BW, CIRC_BW,
7456 CELL_STATS, and TB_EMPTY that show connection and circuit usage.
7457 The new events are emitted in private Tor networks only, with the
7458 goal of being able to better track performance and load during
7459 full-network simulations. Implements proposal 218 and ticket 7359.
7461 o Major features (relay performance):
7462 - Speed up server-side lookups of rendezvous and introduction point
7463 circuits by using hashtables instead of linear searches. These
7464 functions previously accounted between 3 and 7% of CPU usage on
7465 some busy relays. Resolves ticket 9841.
7466 - Avoid wasting CPU when extending a circuit over a channel that is
7467 nearly out of circuit IDs. Previously, we would do a linear scan
7468 over possible circuit IDs before finding one or deciding that we
7469 had exhausted our possibilities. Now, we try at most 64 random
7470 circuit IDs before deciding that we probably won't succeed. Fixes
7471 a possible root cause of ticket 11553.
7473 o Major features (seccomp2 sandbox, Linux only):
7474 - Use the seccomp2 syscall filtering facility on Linux to limit
7475 which system calls Tor can invoke. This is an experimental,
7476 Linux-only feature to provide defense-in-depth against unknown
7477 attacks. To try turning it on, set "Sandbox 1" in your torrc
7478 file. Please be ready to report bugs. We hope to add support
7479 for better sandboxing in the future, including more fine-grained
7480 filters, better division of responsibility, and support for more
7481 platforms. This work has been done by Cristian-Matei Toader for
7482 Google Summer of Code. Resolves tickets 11351 and 11465.
7484 o Major features (testing networks):
7485 - Make testing Tor networks bootstrap better: lower directory fetch
7486 retry schedules and maximum interval without directory requests,
7487 and raise maximum download tries. Implements ticket 6752.
7488 - Add make target 'test-network' to run tests on a Chutney network.
7489 Implements ticket 8530.
7491 o Major features (other):
7492 - On some platforms (currently: recent OSX versions, glibc-based
7493 platforms that support the ELF format, and a few other
7494 Unix-like operating systems), Tor can now dump stack traces
7495 when a crash occurs or an assertion fails. By default, traces
7496 are dumped to stderr (if possible) and to any logs that are
7497 reporting errors. Implements ticket 9299.
7499 o Deprecated versions:
7500 - Tor 0.2.3.x has reached end-of-life; it has received no patches or
7501 attention for some while.
7503 o Major bugfixes (security, directory authorities):
7504 - Directory authorities now include a digest of each relay's
7505 identity key as a part of its microdescriptor.
7507 This is a workaround for bug 11743 (reported by "cypherpunks"),
7508 where Tor clients do not support receiving multiple
7509 microdescriptors with the same SHA256 digest in the same
7510 consensus. When clients receive a consensus like this, they only
7511 use one of the relays. Without this fix, a hostile relay could
7512 selectively disable some client use of target relays by
7513 constructing a router descriptor with a different identity and the
7514 same microdescriptor parameters and getting the authorities to
7515 list it in a microdescriptor consensus. This fix prevents an
7516 attacker from causing a microdescriptor collision, because the
7517 router's identity is not forgeable.
7519 o Major bugfixes (openssl bug workaround):
7520 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
7521 1.0.1j, built with the 'no-ssl3' configuration option. Fixes
7522 bug 13471. This is a workaround for an OpenSSL bug.
7524 o Major bugfixes (client):
7525 - Perform circuit cleanup operations even when circuit
7526 construction operations are disabled (because the network is
7527 disabled, or because there isn't enough directory information).
7528 Previously, when we were not building predictive circuits, we
7529 were not closing expired circuits either. Fixes bug 8387; bugfix on
7530 0.1.1.11-alpha. This bug became visible in 0.2.4.10-alpha when we
7531 became more strict about when we have "enough directory information
7534 o Major bugfixes (client, pluggable transports):
7535 - When managing pluggable transports, use OS notification facilities
7536 to learn if they have crashed, and don't attempt to kill any
7537 process that has already exited. Fixes bug 8746; bugfix
7540 o Major bugfixes (relay denial of service):
7541 - Instead of writing destroy cells directly to outgoing connection
7542 buffers, queue them and intersperse them with other outgoing cells.
7543 This can prevent a set of resource starvation conditions where too
7544 many pending destroy cells prevent data cells from actually getting
7545 delivered. Reported by "oftc_must_be_destroyed". Fixes bug 7912;
7546 bugfix on 0.2.0.1-alpha.
7548 o Major bugfixes (relay):
7549 - Avoid queuing or sending destroy cells for circuit ID zero when we
7550 fail to send a CREATE cell. Fixes bug 12848; bugfix on 0.0.8pre1.
7551 Found and fixed by "cypherpunks".
7552 - Fix ORPort reachability detection on relays running behind a
7553 proxy, by correctly updating the "local" mark on the controlling
7554 channel when changing the address of an or_connection_t after the
7555 handshake. Fixes bug 12160; bugfix on 0.2.4.4-alpha.
7556 - Use a direct dirport connection when uploading non-anonymous
7557 descriptors to the directory authorities. Previously, relays would
7558 incorrectly use tunnel connections under a fairly wide variety of
7559 circumstances. Fixes bug 11469; bugfix on 0.2.4.3-alpha.
7560 - When a circuit accidentally has the same circuit ID for its
7561 forward and reverse direction, correctly detect the direction of
7562 cells using that circuit. Previously, this bug made roughly one
7563 circuit in a million non-functional. Fixes bug 12195; this is a
7564 bugfix on every version of Tor.
7566 o Minor features (security):
7567 - New --enable-expensive-hardening option to enable security
7568 hardening options that consume nontrivial amounts of CPU and
7569 memory. Right now, this includes AddressSanitizer and UbSan, which
7570 are supported in newer versions of GCC and Clang. Closes ticket
7572 - Authorities now assign the Guard flag to the fastest 25% of the
7573 network (it used to be the fastest 50%). Also raise the consensus
7574 weight that guarantees the Guard flag from 250 to 2000. For the
7575 current network, this results in about 1100 guards, down from 2500.
7576 This step paves the way for moving the number of entry guards
7577 down to 1 (proposal 236) while still providing reasonable expected
7578 performance for most users. Implements ticket 12690.
7580 o Minor features (security, memory management):
7581 - Memory allocation tricks (mempools and buffer freelists) are now
7582 disabled by default. You can turn them back on with
7583 --enable-mempools and --enable-buf-freelists respectively. We're
7584 disabling these features because malloc performance is good enough
7585 on most platforms, and a similar feature in OpenSSL exacerbated
7586 exploitation of the Heartbleed attack. Resolves ticket 11476.
7588 o Minor features (bridge client):
7589 - Report a more useful failure message when we can't connect to a
7590 bridge because we don't have the right pluggable transport
7591 configured. Resolves ticket 9665. Patch from Fábio J. Bertinatto.
7593 o Minor features (bridge):
7594 - Add an ExtORPortCookieAuthFileGroupReadable option to make the
7595 cookie file for the ExtORPort g+r by default.
7597 o Minor features (bridges, pluggable transports):
7598 - Bridges now write the SHA1 digest of their identity key
7599 fingerprint (that is, a hash of a hash of their public key) to
7600 notice-level logs, and to a new hashed-fingerprint file. This
7601 information will help bridge operators look up their bridge in
7602 Globe and similar tools. Resolves ticket 10884.
7603 - Improve the message that Tor displays when running as a bridge
7604 using pluggable transports without an Extended ORPort listener.
7605 Also, log the message in the log file too. Resolves ticket 11043.
7606 - Add threshold cutoffs to the networkstatus document created by
7607 the Bridge Authority. Fixes bug 1117.
7608 - On Windows, spawn background processes using the CREATE_NO_WINDOW
7609 flag. Now Tor Browser Bundle 3.5 with pluggable transports enabled
7610 doesn't pop up a blank console window. (In Tor Browser Bundle 2.x,
7611 Vidalia set this option for us.) Implements ticket 10297.
7613 o Minor features (build):
7614 - The configure script has a --disable-seccomp option to turn off
7615 support for libseccomp on systems that have it, in case it (or
7616 Tor's use of it) is broken. Resolves ticket 11628.
7617 - Assume that a user using ./configure --host wants to cross-compile,
7618 and give an error if we cannot find a properly named
7619 tool-chain. Add a --disable-tool-name-check option to proceed
7620 nevertheless. Addresses ticket 9869. Patch by Benedikt Gollatz.
7621 - If we run ./configure and the compiler recognizes -fstack-protector
7622 but the linker rejects it, warn the user about a potentially missing
7623 libssp package. Addresses ticket 9948. Patch from Benedikt Gollatz.
7624 - Add support for `--library-versions` flag. Implements ticket 6384.
7625 - Return the "unexpected sendme" warnings to a warn severity, but make
7626 them rate limited, to help diagnose ticket 8093.
7627 - Detect a missing asciidoc, and warn the user about it, during
7628 configure rather than at build time. Fixes issue 6506. Patch from
7631 o Minor features (client):
7632 - Add a new option, PredictedPortsRelevanceTime, to control how long
7633 after having received a request to connect to a given port Tor
7634 will try to keep circuits ready in anticipation of future requests
7635 for that port. Patch from "unixninja92"; implements ticket 9176.
7637 o Minor features (config options and command line):
7638 - Add an --allow-missing-torrc commandline option that tells Tor to
7639 run even if the configuration file specified by -f is not available.
7640 Implements ticket 10060.
7641 - Add support for the TPROXY transparent proxying facility on Linux.
7642 See documentation for the new TransProxyType option for more
7643 details. Implementation by "thomo". Closes ticket 10582.
7645 o Minor features (config options):
7646 - Config (torrc) lines now handle fingerprints which are missing
7647 their initial '$'. Resolves ticket 4341; improvement over 0.0.9pre5.
7648 - Support a --dump-config option to print some or all of the
7649 configured options. Mainly useful for debugging the command-line
7650 option parsing code. Helps resolve ticket 4647.
7651 - Raise awareness of safer logging: notify user of potentially
7652 unsafe config options, like logging more verbosely than severity
7653 "notice" or setting SafeLogging to 0. Resolves ticket 5584.
7654 - Add a new configuration option TestingV3AuthVotingStartOffset
7655 that bootstraps a network faster by changing the timing for
7656 consensus votes. Addresses ticket 8532.
7657 - Add a new torrc option "ServerTransportOptions" that allows
7658 bridge operators to pass configuration parameters to their
7659 pluggable transports. Resolves ticket 8929.
7660 - The config (torrc) file now accepts bandwidth and space limits in
7661 bits as well as bytes. (Anywhere that you can say "2 Kilobytes",
7662 you can now say "16 kilobits", and so on.) Resolves ticket 9214.
7665 o Minor features (controller):
7666 - Make the entire exit policy available from the control port via
7667 GETINFO exit-policy/*. Implements enhancement 7952. Patch from
7669 - Because of the fix for ticket 11396, the real limit for memory
7670 usage may no longer match the configured MaxMemInQueues value. The
7671 real limit is now exposed via GETINFO limits/max-mem-in-queues.
7672 - Add a new "HS_DESC" controller event that reports activities
7673 related to hidden service descriptors. Resolves ticket 8510.
7674 - New "DROPGUARDS" controller command to forget all current entry
7675 guards. Not recommended for ordinary use, since replacing guards
7676 too frequently makes several attacks easier. Resolves ticket 9934;
7678 - Implement the TRANSPORT_LAUNCHED control port event that
7679 notifies controllers about new launched pluggable
7680 transports. Resolves ticket 5609.
7682 o Minor features (diagnostic):
7683 - When logging a warning because of bug 7164, additionally check the
7684 hash table for consistency (as proposed on ticket 11737). This may
7685 help diagnose bug 7164.
7686 - When we log a heartbeat, log how many one-hop circuits we have
7687 that are at least 30 minutes old, and log status information about
7688 a few of them. This is an attempt to track down bug 8387.
7689 - When encountering an unexpected CR while writing text to a file on
7690 Windows, log the name of the file. Should help diagnosing
7692 - Give more specific warnings when a client notices that an onion
7693 handshake has failed. Fixes ticket 9635.
7694 - Add significant new logging code to attempt to diagnose bug 12184,
7695 where relays seem to run out of available circuit IDs.
7696 - Improve the diagnostic log message for bug 8387 even further to
7697 try to improve our odds of figuring out why one-hop directory
7698 circuits sometimes do not get closed.
7699 - Add more log messages to diagnose bug 7164, which causes
7700 intermittent "microdesc_free() called but md was still referenced"
7701 warnings. We now include more information, to figure out why we
7702 might be cleaning a microdescriptor for being too old if it's
7703 still referenced by a live node_t object.
7704 - Log current accounting state (bytes sent and received + remaining
7705 time for the current accounting period) in the relay's heartbeat
7706 message. Implements ticket 5526; patch from Peter Retzlaff.
7708 o Minor features (geoip):
7709 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
7712 o Minor features (interface):
7713 - Generate a warning if any ports are listed in the SocksPolicy,
7714 DirPolicy, AuthDirReject, AuthDirInvalid, AuthDirBadDir, or
7715 AuthDirBadExit options. (These options only support address
7716 ranges.) Fixes part of ticket 11108.
7718 o Minor features (kernel API usage):
7719 - Use the SOCK_NONBLOCK socket type, if supported, to open nonblocking
7720 sockets in a single system call. Implements ticket 5129.
7722 o Minor features (log messages):
7723 - When ServerTransportPlugin is set on a bridge, Tor can write more
7724 useful statistics about bridge use in its extrainfo descriptors,
7725 but only if the Extended ORPort ("ExtORPort") is set too. Add a
7726 log message to inform the user in this case. Resolves ticket 9651.
7727 - When receiving a new controller connection, log the origin address.
7728 Resolves ticket 9698; patch from "sigpipe".
7729 - When logging OpenSSL engine status at startup, log the status of
7730 more engines. Fixes ticket 10043; patch from Joshua Datko.
7732 o Minor features (log verbosity):
7733 - Demote the message that we give when a flushing connection times
7734 out for too long from NOTICE to INFO. It was usually meaningless.
7735 Resolves ticket 5286.
7736 - Don't log so many notice-level bootstrapping messages at startup
7737 about downloading descriptors. Previously, we'd log a notice
7738 whenever we learned about more routers. Now, we only log a notice
7739 at every 5% of progress. Fixes bug 9963.
7740 - Warn less verbosely when receiving a malformed
7741 ESTABLISH_RENDEZVOUS cell. Fixes ticket 11279.
7743 o Minor features (performance):
7744 - If we're using the pure-C 32-bit curve25519_donna implementation
7745 of curve25519, build it with the -fomit-frame-pointer option to
7746 make it go faster on register-starved hosts. This improves our
7747 handshake performance by about 6% on i386 hosts without nacl.
7750 o Minor features (relay):
7751 - If a circuit timed out for at least 3 minutes, check if we have a
7752 new external IP address, and publish a new descriptor with the new
7753 IP address if it changed. Resolves ticket 2454.
7755 o Minor features (testing):
7756 - If Python is installed, "make check" now runs extra tests beyond
7757 the unit test scripts.
7758 - When bootstrapping a test network, sometimes very few relays get
7759 the Guard flag. Now a new option "TestingDirAuthVoteGuard" can
7760 specify a set of relays which should be voted Guard regardless of
7761 their uptime or bandwidth. Addresses ticket 9206.
7763 o Minor features (transparent proxy, *BSD):
7764 - Support FreeBSD's ipfw firewall interface for TransPort ports on
7765 FreeBSD. To enable it, set "TransProxyType ipfw". Resolves ticket
7766 10267; patch from "yurivict".
7767 - Support OpenBSD's divert-to rules with the pf firewall for
7768 transparent proxy ports. To enable it, set "TransProxyType
7769 pf-divert". This allows Tor to run a TransPort transparent proxy
7770 port on OpenBSD 4.4 or later without root privileges. See the
7771 pf.conf(5) manual page for information on configuring pf to use
7772 divert-to rules. Closes ticket 10896; patch from Dana Koch.
7774 o Minor bugfixes (bridge client):
7775 - Stop accepting bridge lines containing hostnames. Doing so would
7776 cause clients to perform DNS requests on the hostnames, which was
7777 not sensible behavior. Fixes bug 10801; bugfix on 0.2.0.1-alpha.
7779 o Minor bugfixes (bridges):
7780 - Avoid potential crashes or bad behavior when launching a
7781 server-side managed proxy with ORPort or ExtORPort temporarily
7782 disabled. Fixes bug 9650; bugfix on 0.2.3.16-alpha.
7783 - Fix a bug where the first connection works to a bridge that uses a
7784 pluggable transport with client-side parameters, but we don't send
7785 the client-side parameters on subsequent connections. (We don't
7786 use any pluggable transports with client-side parameters yet,
7787 but ScrambleSuit will soon become the first one.) Fixes bug 9162;
7788 bugfix on 0.2.0.3-alpha. Based on a patch from "rl1987".
7790 o Minor bugfixes (build, auxiliary programs):
7791 - Stop preprocessing the "torify" script with autoconf, since
7792 it no longer refers to LOCALSTATEDIR. Fixes bug 5505; patch
7794 - The tor-fw-helper program now follows the standard convention and
7795 exits with status code "0" on success. Fixes bug 9030; bugfix on
7796 0.2.3.1-alpha. Patch by Arlo Breault.
7797 - Corrected ./configure advice for what openssl dev package you should
7798 install on Debian. Fixes bug 9207; bugfix on 0.2.0.1-alpha.
7800 o Minor bugfixes (client):
7801 - Avoid "Tried to open a socket with DisableNetwork set" warnings
7802 when starting a client with bridges configured and DisableNetwork
7803 set. (Tor launcher starts Tor with DisableNetwork set the first
7804 time it runs.) Fixes bug 10405; bugfix on 0.2.3.9-alpha.
7805 - Improve the log message when we can't connect to a hidden service
7806 because all of the hidden service directory nodes hosting its
7807 descriptor are excluded. Improves on our fix for bug 10722, which
7808 was a bugfix on 0.2.0.10-alpha.
7809 - Raise a control port warning when we fail to connect to all of
7810 our bridges. Previously, we didn't inform the controller, and
7811 the bootstrap process would stall. Fixes bug 11069; bugfix on
7813 - Exit immediately when a process-owning controller exits.
7814 Previously, tor relays would wait for a little while after their
7815 controller exited, as if they had gotten an INT signal -- but this
7816 was problematic, since there was no feedback for the user. To do a
7817 clean shutdown, controllers should send an INT signal and give Tor
7818 a chance to clean up. Fixes bug 10449; bugfix on 0.2.2.28-beta.
7819 - Stop attempting to connect to bridges before our pluggable
7820 transports are configured (harmless but resulted in some erroneous
7821 log messages). Fixes bug 11156; bugfix on 0.2.3.2-alpha.
7822 - Fix connections to IPv6 addresses over SOCKS5. Previously, we were
7823 generating incorrect SOCKS5 responses, and confusing client
7824 applications. Fixes bug 10987; bugfix on 0.2.4.7-alpha.
7826 o Minor bugfixes (client, DNSPort):
7827 - When using DNSPort, try to respond to AAAA requests with AAAA
7828 answers. Previously, we hadn't looked at the request type when
7829 deciding which answer type to prefer. Fixes bug 10468; bugfix on
7831 - When receiving a DNS query for an unsupported record type, reply
7832 with no answer rather than with a NOTIMPL error. This behavior
7833 isn't correct either, but it will break fewer client programs, we
7834 hope. Fixes bug 10268; bugfix on 0.2.0.1-alpha. Original patch
7837 o Minor bugfixes (client, logging during bootstrap):
7838 - Only report the first fatal bootstrap error on a given OR
7839 connection. This stops us from telling the controller bogus error
7840 messages like "DONE". Fixes bug 10431; bugfix on 0.2.1.1-alpha.
7841 - Avoid generating spurious warnings when starting with
7842 DisableNetwork enabled. Fixes bug 11200 and bug 10405; bugfix on
7845 o Minor bugfixes (closing OR connections):
7846 - If write_to_buf() in connection_write_to_buf_impl_() ever fails,
7847 check if it's an or_connection_t and correctly call
7848 connection_or_close_for_error() rather than
7849 connection_mark_for_close() directly. Fixes bug 11304; bugfix on
7851 - When closing all connections on setting DisableNetwork to 1, use
7852 connection_or_close_normally() rather than closing OR connections
7853 out from under the channel layer. Fixes bug 11306; bugfix on
7856 o Minor bugfixes (code correctness):
7857 - Previously we used two temporary files when writing descriptors to
7858 disk; now we only use one. Fixes bug 1376.
7859 - Remove an erroneous (but impossible and thus harmless) pointer
7860 comparison that would have allowed compilers to skip a bounds
7861 check in channeltls.c. Fixes bugs 10313 and 9980; bugfix on
7862 0.2.0.10-alpha. Noticed by Jared L Wong and David Fifield.
7863 - Fix an always-true assertion in pluggable transports code so it
7864 actually checks what it was trying to check. Fixes bug 10046;
7865 bugfix on 0.2.3.9-alpha. Found by "dcb".
7867 o Minor bugfixes (command line):
7868 - Use a single command-line parser for parsing torrc options on the
7869 command line and for finding special command-line options to avoid
7870 inconsistent behavior for torrc option arguments that have the same
7871 names as command-line options. Fixes bugs 4647 and 9578; bugfix on
7873 - No longer allow 'tor --hash-password' with no arguments. Fixes bug
7874 9573; bugfix on 0.0.9pre5.
7876 o Minor bugfixes (compilation):
7877 - Compile correctly with builds and forks of OpenSSL (such as
7878 LibreSSL) that disable compression. Fixes bug 12602; bugfix on
7879 0.2.1.1-alpha. Patch from "dhill".
7880 - Restore the ability to compile Tor with V2_HANDSHAKE_SERVER
7881 turned off (that is, without support for v2 link handshakes). Fixes
7882 bug 4677; bugfix on 0.2.3.2-alpha. Patch from "piet".
7883 - In routerlist_assert_ok(), don't take the address of a
7884 routerinfo's cache_info member unless that routerinfo is non-NULL.
7885 Fixes bug 13096; bugfix on 0.1.1.9-alpha. Patch by "teor".
7886 - Fix a large number of false positive warnings from the clang
7887 analyzer static analysis tool. This should make real warnings
7888 easier for clang analyzer to find. Patch from "teor". Closes
7890 - Resolve GCC complaints on OpenBSD about discarding constness in
7891 TO_{ORIGIN,OR}_CIRCUIT functions. Fixes part of bug 11633; bugfix
7892 on 0.1.1.23. Patch from Dana Koch.
7893 - Resolve clang complaints on OpenBSD with -Wshorten-64-to-32 due to
7894 treatment of long and time_t as comparable types. Fixes part of
7895 bug 11633. Patch from Dana Koch.
7896 - When deciding whether to build the 64-bit curve25519
7897 implementation, detect platforms where we can compile 128-bit
7898 arithmetic but cannot link it. Fixes bug 11729; bugfix on
7899 0.2.4.8-alpha. Patch from "conradev".
7900 - Fix compilation when DNS_CACHE_DEBUG is enabled. Fixes bug 11761;
7901 bugfix on 0.2.3.13-alpha. Found by "cypherpunks".
7902 - Fix compilation with dmalloc. Fixes bug 11605; bugfix
7904 - Build and run correctly on systems like OpenBSD-current that have
7905 patched OpenSSL to remove get_cipher_by_char and/or its
7906 implementations. Fixes issue 13325.
7908 o Minor bugfixes (controller and command-line):
7909 - If changing a config option via "setconf" fails in a recoverable
7910 way, we used to nonetheless write our new control ports to the
7911 file described by the "ControlPortWriteToFile" option. Now we only
7912 write out that file if we successfully switch to the new config
7913 option. Fixes bug 5605; bugfix on 0.2.2.26-beta. Patch from "Ryman".
7915 o Minor bugfixes (directory server):
7916 - No longer accept malformed http headers when parsing urls from
7917 headers. Now we reply with Bad Request ("400"). Fixes bug 2767;
7918 bugfix on 0.0.6pre1.
7919 - When sending a compressed set of descriptors or microdescriptors,
7920 make sure to finalize the zlib stream. Previously, we would write
7921 all the compressed data, but if the last descriptor we wanted to
7922 send was missing or too old, we would not mark the stream as
7923 finished. This caused problems for decompression tools. Fixes bug
7924 11648; bugfix on 0.1.1.23.
7926 o Minor bugfixes (hidden service):
7927 - Only retry attempts to connect to a chosen rendezvous point 8
7928 times, not 30. Fixes bug 4241; bugfix on 0.1.0.1-rc.
7930 o Minor bugfixes (interface):
7931 - Reject relative control socket paths and emit a warning. Previously,
7932 single-component control socket paths would be rejected, but Tor
7933 would not log why it could not validate the config. Fixes bug 9258;
7934 bugfix on 0.2.3.16-alpha.
7936 o Minor bugfixes (log messages):
7937 - Fix a bug where clients using bridges would report themselves
7938 as 50% bootstrapped even without a live consensus document.
7939 Fixes bug 9922; bugfix on 0.2.1.1-alpha.
7940 - Suppress a warning where, if there's only one directory authority
7941 in the network, we would complain that votes and signatures cannot
7942 be uploaded to other directory authorities. Fixes bug 10842;
7943 bugfix on 0.2.2.26-beta.
7944 - Report bootstrapping progress correctly when we're downloading
7945 microdescriptors. We had updated our "do we have enough microdescs
7946 to begin building circuits?" logic most recently in 0.2.4.10-alpha
7947 (see bug 5956), but we left the bootstrap status event logic at
7948 "how far through getting 1/4 of them are we?" Fixes bug 9958;
7949 bugfix on 0.2.2.36, which is where they diverged (see bug 5343).
7951 o Minor bugfixes (logging):
7952 - Downgrade "Unexpected onionskin length after decryption" warning
7953 to a protocol-warn, since there's nothing relay operators can do
7954 about a client that sends them a malformed create cell. Resolves
7955 bug 12996; bugfix on 0.0.6rc1.
7956 - Log more specific warnings when we get an ESTABLISH_RENDEZVOUS
7957 cell on a cannibalized or non-OR circuit. Resolves ticket 12997.
7958 - When logging information about an EXTEND2 or EXTENDED2 cell, log
7959 their names correctly. Fixes part of bug 12700; bugfix
7961 - When logging information about a relay cell whose command we don't
7962 recognize, log its command as an integer. Fixes part of bug 12700;
7963 bugfix on 0.2.1.10-alpha.
7964 - Escape all strings from the directory connection before logging
7965 them. Fixes bug 13071; bugfix on 0.1.1.15. Patch from "teor".
7966 - Squelch a spurious LD_BUG message "No origin circuit for
7967 successful SOCKS stream" in certain hidden service failure cases;
7969 - Downgrade the severity of the 'unexpected sendme cell from client'
7970 from 'warn' to 'protocol warning'. Closes ticket 8093.
7972 o Minor bugfixes (misc code correctness):
7973 - In munge_extrainfo_into_routerinfo(), check the return value of
7974 memchr(). This would have been a serious issue if we ever passed
7975 it a non-extrainfo. Fixes bug 8791; bugfix on 0.2.0.6-alpha. Patch
7977 - On the chance that somebody manages to build Tor on a
7978 platform where time_t is unsigned, correct the way that
7979 microdesc_add_to_cache() handles negative time arguments.
7980 Fixes bug 8042; bugfix on 0.2.3.1-alpha.
7981 - Fix various instances of undefined behavior in channeltls.c,
7982 tor_memmem(), and eventdns.c that would cause us to construct
7983 pointers to memory outside an allocated object. (These invalid
7984 pointers were not accessed, but C does not even allow them to
7985 exist.) Fixes bug 10363; bugfixes on 0.1.1.1-alpha, 0.1.2.1-alpha,
7986 0.2.0.10-alpha, and 0.2.3.6-alpha. Reported by "bobnomnom".
7987 - Use the AddressSanitizer and Ubsan sanitizers (in clang-3.4) to
7988 fix some miscellaneous errors in our tests and codebase. Fixes bug
7989 11232. Bugfixes on versions back as far as 0.2.1.11-alpha.
7990 - Always check return values for unlink, munmap, UnmapViewOfFile;
7991 check strftime return values more often. In some cases all we can
7992 do is report a warning, but this may help prevent deeper bugs from
7993 going unnoticed. Closes ticket 8787; bugfixes on many, many tor
7995 - Fix numerous warnings from the clang "scan-build" static analyzer.
7996 Some of these are programming style issues; some of them are false
7997 positives that indicated awkward code; some are undefined behavior
7998 cases related to constructing (but not using) invalid pointers;
7999 some are assumptions about API behavior; some are (harmlessly)
8000 logging sizeof(ptr) bytes from a token when sizeof(*ptr) would be
8001 correct; and one or two are genuine bugs that weren't reachable
8002 from the rest of the program. Fixes bug 8793; bugfixes on many,
8005 o Minor bugfixes (node selection):
8006 - If ExcludeNodes is set, consider non-excluded hidden service
8007 directory servers before excluded ones. Do not consider excluded
8008 hidden service directory servers at all if StrictNodes is
8009 set. (Previously, we would sometimes decide to connect to those
8010 servers, and then realize before we initiated a connection that
8011 we had excluded them.) Fixes bug 10722; bugfix on 0.2.0.10-alpha.
8013 - If we set the ExitNodes option but it doesn't include any nodes
8014 that have the Exit flag, we would choose not to bootstrap. Now we
8015 bootstrap so long as ExitNodes includes nodes which can exit to
8016 some port. Fixes bug 10543; bugfix on 0.2.4.10-alpha.
8018 o Minor bugfixes (performance):
8019 - Avoid a bug where every successful connection made us recompute
8020 the flag telling us whether we have sufficient information to
8021 build circuits. Previously, we would forget our cached value
8022 whenever we successfully opened a channel (or marked a router as
8023 running or not running for any other reason), regardless of
8024 whether we had previously believed the router to be running. This
8025 forced us to run an expensive update operation far too often.
8026 Fixes bug 12170; bugfix on 0.1.2.1-alpha.
8027 - Avoid using tor_memeq() for checking relay cell integrity. This
8028 removes a possible performance bottleneck. Fixes part of bug
8029 12169; bugfix on 0.2.1.31.
8031 o Minor bugfixes (platform-specific):
8032 - When dumping a malformed directory object to disk, save it in
8033 binary mode on Windows, not text mode. Fixes bug 11342; bugfix on
8035 - Don't report failures from make_socket_reuseable() on incoming
8036 sockets on OSX: this can happen when incoming connections close
8037 early. Fixes bug 10081.
8039 o Minor bugfixes (pluggable transports):
8040 - Avoid another 60-second delay when starting Tor in a pluggable-
8041 transport-using configuration when we already have cached
8042 descriptors for our bridges. Fixes bug 11965; bugfix
8045 o Minor bugfixes (protocol correctness):
8046 - When receiving a VERSIONS cell with an odd number of bytes, close
8047 the connection immediately since the cell is malformed. Fixes bug
8048 10365; bugfix on 0.2.0.10-alpha. Spotted by "bobnomnom"; fix by
8051 o Minor bugfixes (relay, other):
8052 - We now drop CREATE cells for already-existent circuit IDs and for
8053 zero-valued circuit IDs, regardless of other factors that might
8054 otherwise have called for DESTROY cells. Fixes bug 12191; bugfix
8056 - When rejecting DATA cells for stream_id zero, still count them
8057 against the circuit's deliver window so that we don't fail to send
8058 a SENDME. Fixes bug 11246; bugfix on 0.2.4.10-alpha.
8060 o Minor bugfixes (relay, threading):
8061 - Check return code on spawn_func() in cpuworker code, so that we
8062 don't think we've spawned a nonworking cpuworker and write junk to
8063 it forever. Fix related to bug 4345; bugfix on all released Tor
8064 versions. Found by "skruffy".
8065 - Use a pthread_attr to make sure that spawn_func() cannot return an
8066 error while at the same time launching a thread. Fix related to
8067 bug 4345; bugfix on all released Tor versions. Reported
8070 o Minor bugfixes (relays and bridges):
8071 - Avoid crashing on a malformed resolv.conf file when running a
8072 relay using Libevent 1. Fixes bug 8788; bugfix on 0.1.1.23.
8073 - Non-exit relays no longer launch mock DNS requests to check for
8074 DNS hijacking. This has been unnecessary since 0.2.1.7-alpha, when
8075 non-exit relays stopped servicing DNS requests. Fixes bug 965;
8076 bugfix on 0.2.1.7-alpha. Patch from Matt Pagan.
8077 - Bridges now report complete directory request statistics. Related
8078 to bug 5824; bugfix on 0.2.2.1-alpha.
8079 - Bridges now never collect statistics that were designed for
8080 relays. Fixes bug 5824; bugfix on 0.2.3.8-alpha.
8082 o Minor bugfixes (testing):
8083 - Fix all valgrind warnings produced by the unit tests. There were
8084 over a thousand memory leak warnings previously, mostly produced
8085 by forgetting to free things in the unit test code. Fixes bug
8086 11618, bugfixes on many versions of Tor.
8088 o Minor bugfixes (tor-fw-helper):
8089 - Give a correct log message when tor-fw-helper fails to launch.
8090 (Previously, we would say something like "tor-fw-helper sent us a
8091 string we could not parse".) Fixes bug 9781; bugfix
8094 o Minor bugfixes (trivial memory leaks):
8095 - Fix a small memory leak when signing a directory object. Fixes bug
8096 11275; bugfix on 0.2.4.13-alpha.
8097 - Resolve some memory leaks found by coverity in the unit tests, on
8098 exit in tor-gencert, and on a failure to compute digests for our
8099 own keys when generating a v3 networkstatus vote. These leaks
8100 should never have affected anyone in practice.
8102 o Code simplification and refactoring:
8103 - Remove some old fallback code designed to keep Tor clients working
8104 in a network with only two working relays. Elsewhere in the code we
8105 have long since stopped supporting such networks, so there wasn't
8106 much point in keeping it around. Addresses ticket 9926.
8107 - Reject 0-length EXTEND2 cells more explicitly. Fixes bug 10536;
8108 bugfix on 0.2.4.8-alpha. Reported by "cypherpunks".
8109 - Extract the common duplicated code for creating a subdirectory
8110 of the data directory and writing to a file in it. Fixes ticket
8111 4282; patch from Peter Retzlaff.
8112 - Since OpenSSL 0.9.7, the i2d_*() functions support allocating output
8113 buffer. Avoid calling twice: i2d_RSAPublicKey(), i2d_DHparams(),
8114 i2d_X509(), and i2d_PublicKey(). Resolves ticket 5170.
8115 - Add a set of accessor functions for the circuit timeout data
8116 structure. Fixes ticket 6153; patch from "piet".
8117 - Clean up exit paths from connection_listener_new(). Closes ticket
8118 8789. Patch from Arlo Breault.
8119 - Since we rely on OpenSSL 0.9.8 now, we can use EVP_PKEY_cmp()
8120 and drop our own custom pkey_eq() implementation. Fixes bug 9043.
8121 - Use a doubly-linked list to implement the global circuit list.
8122 Resolves ticket 9108. Patch from Marek Majkowski.
8123 - Remove contrib/id_to_fp.c since it wasn't used anywhere.
8124 - Remove constants and tests for PKCS1 padding; it's insecure and
8125 shouldn't be used for anything new. Fixes bug 8792; patch
8127 - Remove instances of strcpy() from the unit tests. They weren't
8128 hurting anything, since they were only in the unit tests, but it's
8129 embarrassing to have strcpy() in the code at all, and some analysis
8130 tools don't like it. Fixes bug 8790; bugfix on 0.2.3.6-alpha and
8131 0.2.3.8-alpha. Patch from Arlo Breault.
8132 - Remove is_internal_IP() function. Resolves ticket 4645.
8133 - Remove unused function circuit_dump_by_chan from circuitlist.c.
8134 Closes issue 9107; patch from "marek".
8135 - Change our use of the ENUM_BF macro to avoid declarations that
8137 - Get rid of router->address, since in all cases it was just the
8138 string representation of router->addr. Resolves ticket 5528.
8141 - Adjust the URLs in the README to refer to the new locations of
8142 several documents on the website. Fixes bug 12830. Patch from
8144 - Document 'reject6' and 'accept6' ExitPolicy entries. Resolves
8146 - Update manpage to describe some of the files you can expect to
8147 find in Tor's DataDirectory. Addresses ticket 9839.
8148 - Clean up several option names in the manpage to match their real
8149 names, add the missing documentation for a couple of testing and
8150 directory authority options, remove the documentation for a
8151 V2-directory fetching option that no longer exists. Resolves
8153 - Correct the documentation so that it lists the correct directory
8154 for the stats files. (They are in a subdirectory called "stats",
8156 - In the manpage, move more authority-only options into the
8157 directory authority section so that operators of regular directory
8158 caches don't get confused.
8159 - Fix the layout of the SOCKSPort flags in the manpage. Fixes bug
8160 11061; bugfix on 0.2.4.7-alpha.
8161 - Resolve warnings from Doxygen.
8162 - Document in the manpage that "KBytes" may also be written as
8163 "kilobytes" or "KB", that "Kbits" may also be written as
8164 "kilobits", and so forth. Closes ticket 9222.
8165 - Document that the ClientOnly config option overrides ORPort.
8166 Our old explanation made ClientOnly sound as though it did
8167 nothing at all. Resolves bug 9059.
8168 - Explain that SocksPolicy, DirPolicy, and similar options don't
8169 take port arguments. Fixes the other part of ticket 11108.
8170 - Fix a comment about the rend_server_descriptor_t.protocols field
8171 to more accurately describe its range. Also, make that field
8172 unsigned, to more accurately reflect its usage. Fixes bug 9099;
8173 bugfix on 0.2.1.5-alpha.
8174 - Fix the manpage's description of HiddenServiceAuthorizeClient:
8175 the maximum client name length is 16, not 19. Fixes bug 11118;
8176 bugfix on 0.2.1.6-alpha.
8179 - The contrib directory has been sorted and tidied. Before, it was
8180 an unsorted dumping ground for useful and not-so-useful things.
8181 Now, it is divided based on functionality, and the items which
8182 seemed to be nonfunctional or useless have been removed. Resolves
8183 ticket 8966; based on patches from "rl1987".
8185 o Removed code and features:
8186 - Clients now reject any directory authority certificates lacking
8187 a dir-key-crosscert element. These have been included since
8188 0.2.1.9-alpha, so there's no real reason for them to be optional
8189 any longer. Completes proposal 157. Resolves ticket 10162.
8190 - Remove all code that existed to support the v2 directory system,
8191 since there are no longer any v2 directory authorities. Resolves
8193 - Remove the HSAuthoritativeDir and AlternateHSAuthority torrc
8194 options, which were used for designating authorities as "Hidden
8195 service authorities". There has been no use of hidden service
8196 authorities since 0.2.2.1-alpha, when we stopped uploading or
8197 downloading v0 hidden service descriptors. Fixes bug 10881; also
8198 part of a fix for bug 10841.
8199 - Remove /tor/dbg-stability.txt URL that was meant to help debug WFU
8200 and MTBF calculations, but that nobody was using. Fixes bug 11742.
8201 - The TunnelDirConns and PreferTunnelledDirConns options no longer
8202 exist; tunneled directory connections have been available since
8203 0.1.2.5-alpha, and turning them off is not a good idea. This is a
8204 brute-force fix for 10849, where "TunnelDirConns 0" would break
8206 - Remove all code for the long unused v1 directory protocol.
8207 Resolves ticket 11070.
8208 - Remove all remaining code related to version-0 hidden service
8209 descriptors: they have not been in use since 0.2.2.1-alpha. Fixes
8210 the rest of bug 10841.
8211 - Remove migration code from when we renamed the "cached-routers"
8212 file to "cached-descriptors" back in 0.2.0.8-alpha. This
8213 incidentally resolves ticket 6502 by cleaning up the related code
8214 a bit. Patch from Akshay Hebbar.
8216 o Test infrastructure:
8217 - Tor now builds each source file in two modes: a mode that avoids
8218 exposing identifiers needlessly, and another mode that exposes
8219 more identifiers for testing. This lets the compiler do better at
8220 optimizing the production code, while enabling us to take more
8221 radical measures to let the unit tests test things.
8222 - The production builds no longer include functions used only in
8223 the unit tests; all functions exposed from a module only for
8224 unit-testing are now static in production builds.
8225 - Add an --enable-coverage configuration option to make the unit
8226 tests (and a new src/or/tor-cov target) to build with gcov test
8228 - Update to the latest version of tinytest.
8229 - Improve the tinytest implementation of string operation tests so
8230 that comparisons with NULL strings no longer crash the tests; they
8231 now just fail, normally. Fixes bug 9004; bugfix on 0.2.2.4-alpha.
8232 - New macros in test.h to simplify writing mock-functions for unit
8233 tests. Part of ticket 11507. Patch from Dana Koch.
8234 - We now have rudimentary function mocking support that our unit
8235 tests can use to test functions in isolation. Function mocking
8236 lets the tests temporarily replace a function's dependencies with
8237 stub functions, so that the tests can check the function without
8238 invoking the other functions it calls.
8241 - Complete tests for the status.c module. Resolves ticket 11507.
8242 Patch from Dana Koch.
8243 - Add more unit tests for the <circid,channel>->circuit map, and
8244 the destroy-cell-tracking code to fix bug 7912.
8245 - Unit tests for failing cases of the TAP onion handshake.
8246 - More unit tests for address-manipulation functions.
8248 o Distribution (systemd):
8249 - Include a tor.service file in contrib/dist for use with systemd.
8250 Some distributions will be able to use this file unmodified;
8251 others will need to tweak it, or write their own. Patch from Jamie
8252 Nguyen; resolves ticket 8368.
8253 - Verify configuration file via ExecStartPre in the systemd unit
8254 file. Patch from intrigeri; resolves ticket 12730.
8255 - Explicitly disable RunAsDaemon in the systemd unit file. Our
8256 current systemd unit uses "Type = simple", so systemd does not
8257 expect tor to fork. If the user has "RunAsDaemon 1" in their
8258 torrc, then things won't work as expected. This is e.g. the case
8259 on Debian (and derivatives), since there we pass "--defaults-torrc
8260 /usr/share/tor/tor-service-defaults-torrc" (that contains
8261 "RunAsDaemon 1") by default. Patch by intrigeri; resolves
8265 Changes in version 0.2.4.25 - 2014-10-20
8266 Tor 0.2.4.25 disables SSL3 in response to the recent "POODLE" attack
8267 (even though POODLE does not affect Tor). It also works around a crash
8268 bug caused by some operating systems' response to the "POODLE" attack
8269 (which does affect Tor).
8271 o Major security fixes (also in 0.2.5.9-rc):
8272 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
8273 today support TLS 1.0 or later, so we can safely turn off support
8274 for this old (and insecure) protocol. Fixes bug 13426.
8276 o Major bugfixes (openssl bug workaround, also in 0.2.5.9-rc):
8277 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
8278 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
8279 13471. This is a workaround for an OpenSSL bug.
8282 Changes in version 0.2.4.24 - 2014-09-22
8283 Tor 0.2.4.24 fixes a bug that affects consistency and speed when
8284 connecting to hidden services, and it updates the location of one of
8285 the directory authorities.
8288 - Clients now send the correct address for their chosen rendezvous
8289 point when trying to access a hidden service. They used to send
8290 the wrong address, which would still work some of the time because
8291 they also sent the identity digest of the rendezvous point, and if
8292 the hidden service happened to try connecting to the rendezvous
8293 point from a relay that already had a connection open to it,
8294 the relay would reuse that connection. Now connections to hidden
8295 services should be more robust and faster. Also, this bug meant
8296 that clients were leaking to the hidden service whether they were
8297 on a little-endian (common) or big-endian (rare) system, which for
8298 some users might have reduced their anonymity. Fixes bug 13151;
8299 bugfix on 0.2.1.5-alpha.
8301 o Directory authority changes:
8302 - Change IP address for gabelmoo (v3 directory authority).
8304 o Minor features (geoip):
8305 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
8309 Changes in version 0.2.4.23 - 2014-07-28
8310 Tor 0.2.4.23 brings us a big step closer to slowing down the risk from
8311 guard rotation, and also backports several important fixes from the
8312 Tor 0.2.5 alpha release series.
8315 - Clients now look at the "usecreatefast" consensus parameter to
8316 decide whether to use CREATE_FAST or CREATE cells for the first hop
8317 of their circuit. This approach can improve security on connections
8318 where Tor's circuit handshake is stronger than the available TLS
8319 connection security levels, but the tradeoff is more computational
8320 load on guard relays. Implements proposal 221. Resolves ticket 9386.
8321 - Make the number of entry guards configurable via a new
8322 NumEntryGuards consensus parameter, and the number of directory
8323 guards configurable via a new NumDirectoryGuards consensus
8324 parameter. Implements ticket 12688.
8327 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
8328 implementation that caused incorrect results on 32-bit
8329 implementations when certain malformed inputs were used along with
8330 a small class of private ntor keys. This bug does not currently
8331 appear to allow an attacker to learn private keys or impersonate a
8332 Tor server, but it could provide a means to distinguish 32-bit Tor
8333 implementations from 64-bit Tor implementations. Fixes bug 12694;
8334 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
8338 - Warn and drop the circuit if we receive an inbound 'relay early'
8339 cell. Those used to be normal to receive on hidden service circuits
8340 due to bug 1038, but the buggy Tor versions are long gone from
8341 the network so we can afford to resume watching for them. Resolves
8342 the rest of bug 1038; bugfix on 0.2.1.19.
8343 - Correct a confusing error message when trying to extend a circuit
8344 via the control protocol but we don't know a descriptor or
8345 microdescriptor for one of the specified relays. Fixes bug 12718;
8346 bugfix on 0.2.3.1-alpha.
8347 - Avoid an illegal read from stack when initializing the TLS
8348 module using a version of OpenSSL without all of the ciphers
8349 used by the v2 link handshake. Fixes bug 12227; bugfix on
8350 0.2.4.8-alpha. Found by "starlight".
8353 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
8357 Changes in version 0.2.4.22 - 2014-05-16
8358 Tor 0.2.4.22 backports numerous high-priority fixes from the Tor 0.2.5
8359 alpha release series. These include blocking all authority signing
8360 keys that may have been affected by the OpenSSL "heartbleed" bug,
8361 choosing a far more secure set of TLS ciphersuites by default, closing
8362 a couple of memory leaks that could be used to run a target relay out
8363 of RAM, and several others.
8365 o Major features (security, backport from 0.2.5.4-alpha):
8366 - Block authority signing keys that were used on authorities
8367 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
8368 don't have any evidence that these keys _were_ compromised; we're
8369 doing this to be prudent.) Resolves ticket 11464.
8371 o Major bugfixes (security, OOM):
8372 - Fix a memory leak that could occur if a microdescriptor parse
8373 fails during the tokenizing step. This bug could enable a memory
8374 exhaustion attack by directory servers. Fixes bug 11649; bugfix
8377 o Major bugfixes (TLS cipher selection, backport from 0.2.5.4-alpha):
8378 - The relay ciphersuite list is now generated automatically based on
8379 uniform criteria, and includes all OpenSSL ciphersuites with
8380 acceptable strength and forward secrecy. Previously, we had left
8381 some perfectly fine ciphersuites unsupported due to omission or
8382 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
8383 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
8384 - Relays now trust themselves to have a better view than clients of
8385 which TLS ciphersuites are better than others. (Thanks to bug
8386 11513, the relay list is now well-considered, whereas the client
8387 list has been chosen mainly for anti-fingerprinting purposes.)
8388 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
8389 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
8390 AES128. Resolves ticket 11528.
8391 - Clients now try to advertise the same list of ciphersuites as
8392 Firefox 28. This change enables selection of (fast) GCM
8393 ciphersuites, disables some strange old ciphers, and stops
8394 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
8395 Resolves ticket 11438.
8397 o Minor bugfixes (configuration, security):
8398 - When running a hidden service, do not allow TunneledDirConns 0:
8399 trying to set that option together with a hidden service would
8400 otherwise prevent the hidden service from running, and also make
8401 it publish its descriptors directly over HTTP. Fixes bug 10849;
8402 bugfix on 0.2.1.1-alpha.
8404 o Minor bugfixes (controller, backport from 0.2.5.4-alpha):
8405 - Avoid sending a garbage value to the controller when a circuit is
8406 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
8408 o Minor bugfixes (exit relay, backport from 0.2.5.4-alpha):
8409 - Stop leaking memory when we successfully resolve a PTR record.
8410 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
8412 o Minor bugfixes (bridge client, backport from 0.2.5.4-alpha):
8413 - Avoid 60-second delays in the bootstrapping process when Tor is
8414 launching for a second time while using bridges. Fixes bug 9229;
8415 bugfix on 0.2.0.3-alpha.
8417 o Minor bugfixes (relays and bridges, backport from 0.2.5.4-alpha):
8418 - Give the correct URL in the warning message when trying to run a
8419 relay on an ancient version of Windows. Fixes bug 9393.
8421 o Minor bugfixes (compilation):
8422 - Fix a compilation error when compiling with --disable-curve25519.
8423 Fixes bug 9700; bugfix on 0.2.4.17-rc.
8426 - Downgrade the warning severity for the the "md was still
8427 referenced 1 node(s)" warning. Tor 0.2.5.4-alpha has better code
8428 for trying to diagnose this bug, and the current warning in
8429 earlier versions of tor achieves nothing useful. Addresses warning
8432 o Minor features (log verbosity, backport from 0.2.5.4-alpha):
8433 - When we run out of usable circuit IDs on a channel, log only one
8434 warning for the whole channel, and describe how many circuits
8435 there were on the channel. Fixes part of ticket 11553.
8437 o Minor features (security, backport from 0.2.5.4-alpha):
8438 - Decrease the lower limit of MaxMemInCellQueues to 256 MBytes (but
8439 leave the default at 8GBytes), to better support Raspberry Pi
8440 users. Fixes bug 9686; bugfix on 0.2.4.14-alpha.
8442 o Documentation (backport from 0.2.5.4-alpha):
8443 - Correctly document that we search for a system torrc file before
8444 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
8448 Changes in version 0.2.4.21 - 2014-02-28
8449 Tor 0.2.4.21 further improves security against potential adversaries who
8450 find breaking 1024-bit crypto doable, and backports several stability
8451 and robustness patches from the 0.2.5 branch.
8453 o Major features (client security):
8454 - When we choose a path for a 3-hop circuit, make sure it contains
8455 at least one relay that supports the NTor circuit extension
8456 handshake. Otherwise, there is a chance that we're building
8457 a circuit that's worth attacking by an adversary who finds
8458 breaking 1024-bit crypto doable, and that chance changes the game
8459 theory. Implements ticket 9777.
8462 - Do not treat streams that fail with reason
8463 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
8464 since it could also indicate an ENETUNREACH connection error. Fixes
8465 part of bug 10777; bugfix on 0.2.4.8-alpha.
8467 o Code simplification and refactoring:
8468 - Remove data structures which were introduced to implement the
8469 CellStatistics option: they are now redundant with the new timestamp
8470 field in the regular packed_cell_t data structure, which we did
8471 in 0.2.4.18-rc in order to resolve bug 9093. Resolves ticket 10870.
8474 - Always clear OpenSSL bignums before freeing them -- even bignums
8475 that don't contain secrets. Resolves ticket 10793. Patch by
8477 - Build without warnings under clang 3.4. (We have some macros that
8478 define static functions only some of which will get used later in
8479 the module. Starting with clang 3.4, these give a warning unless the
8480 unused attribute is set on them.) Resolves ticket 10904.
8481 - Update geoip and geoip6 files to the February 7 2014 Maxmind
8482 GeoLite2 Country database.
8485 - Set the listen() backlog limit to the largest actually supported
8486 on the system, not to the value in a header file. Fixes bug 9716;
8487 bugfix on every released Tor.
8488 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
8489 exit node as a NOROUTE error, not an INTERNAL error, since they
8490 can apparently happen when trying to connect to the wrong sort
8491 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
8492 - Fix build warnings about missing "a2x" comment when building the
8493 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
8494 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
8495 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
8496 not entirely remove it from the connection lists. Fixes bug 9602;
8497 bugfix on 0.2.4.4-alpha.
8498 - Fix a segmentation fault in our benchmark code when running with
8499 Fedora's OpenSSL package, or any other OpenSSL that provides
8500 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
8501 - Turn "circuit handshake stats since last time" log messages into a
8502 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
8504 o Documentation fixes:
8505 - Document that all but one DirPort entry must have the NoAdvertise
8506 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
8509 Changes in version 0.2.4.20 - 2013-12-22
8510 Tor 0.2.4.20 fixes potentially poor random number generation for users
8511 who 1) use OpenSSL 1.0.0 or later, 2) set "HardwareAccel 1" in their
8512 torrc file, 3) have "Sandy Bridge" or "Ivy Bridge" Intel processors,
8513 and 4) have no state file in their DataDirectory (as would happen on
8514 first start). Users who generated relay or hidden service identity
8515 keys in such a situation should discard them and generate new ones.
8517 This release also fixes a logic error that caused Tor clients to build
8518 many more preemptive circuits than they actually need.
8521 - Do not allow OpenSSL engines to replace the PRNG, even when
8522 HardwareAccel is set. The only default builtin PRNG engine uses
8523 the Intel RDRAND instruction to replace the entire PRNG, and
8524 ignores all attempts to seed it with more entropy. That's
8525 cryptographically stupid: the right response to a new alleged
8526 entropy source is never to discard all previously used entropy
8527 sources. Fixes bug 10402; works around behavior introduced in
8528 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
8530 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
8531 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
8532 - Avoid launching spurious extra circuits when a stream is pending.
8533 This fixes a bug where any circuit that _wasn't_ unusable for new
8534 streams would be treated as if it were, causing extra circuits to
8535 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
8538 - Avoid a crash bug when starting with a corrupted microdescriptor
8539 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
8540 - If we fail to dump a previously cached microdescriptor to disk, avoid
8541 freeing duplicate data later on. Fixes bug 10423; bugfix on
8542 0.2.4.13-alpha. Spotted by "bobnomnom".
8545 Changes in version 0.2.4.19 - 2013-12-11
8546 The Tor 0.2.4 release series is dedicated to the memory of Aaron Swartz
8547 (1986-2013). Aaron worked on diverse projects including helping to guide
8548 Creative Commons, playing a key role in stopping SOPA/PIPA, bringing
8549 transparency to the U.S government's PACER documents, and contributing
8550 design and development for Tor and Tor2Web. Aaron was one of the latest
8551 martyrs in our collective fight for civil liberties and human rights,
8552 and his death is all the more painful because he was one of us.
8554 Tor 0.2.4.19, the first stable release in the 0.2.4 branch, features
8555 a new circuit handshake and link encryption that use ECC to provide
8556 better security and efficiency; makes relays better manage circuit
8557 creation requests; uses "directory guards" to reduce client enumeration
8558 risks; makes bridges collect and report statistics about the pluggable
8559 transports they support; cleans up and improves our geoip database;
8560 gets much closer to IPv6 support for clients, bridges, and relays; makes
8561 directory authorities use measured bandwidths rather than advertised
8562 ones when computing flags and thresholds; disables client-side DNS
8563 caching to reduce tracking risks; and fixes a big bug in bridge
8564 reachability testing. This release introduces two new design
8565 abstractions in the code: a new "channel" abstraction between circuits
8566 and or_connections to allow for implementing alternate relay-to-relay
8567 transports, and a new "circuitmux" abstraction storing the queue of
8568 circuits for a channel. The release also includes many stability,
8569 security, and privacy fixes.
8571 o Major features (new circuit handshake):
8572 - Tor now supports a new circuit extension handshake designed by Ian
8573 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
8574 circuit extension handshake, later called "TAP", was a bit slow
8575 (especially on the relay side), had a fragile security proof, and
8576 used weaker keys than we'd now prefer. The new circuit handshake
8577 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
8578 function, making it significantly more secure than the older
8579 handshake, and significantly faster. Tor can use one of two built-in
8580 pure-C curve25519-donna implementations by Adam Langley, or it
8581 can link against the "nacl" library for a tuned version if present.
8583 The built-in version is very fast for 64-bit systems when building
8584 with GCC. The built-in 32-bit version is still faster than the
8585 old TAP protocol, but using libnacl is better on most such hosts.
8587 Implements proposal 216; closes ticket 7202.
8589 o Major features (better link encryption):
8590 - Relays can now enable the ECDHE TLS ciphersuites when available
8591 and appropriate. These ciphersuites let us negotiate forward-secure
8592 TLS secret keys more safely and more efficiently than with our
8593 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
8594 public relays prefer the (faster) P224 group, and bridges prefer
8595 the (more common) P256 group; you can override this with the
8598 This feature requires clients running 0.2.3.17-beta or later,
8599 and requires both sides to be running OpenSSL 1.0.0 or later
8600 with ECC support. OpenSSL 1.0.1, with the compile-time option
8601 "enable-ec_nistp_64_gcc_128", is highly recommended.
8603 Implements the relay side of proposal 198; closes ticket 7200.
8605 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
8606 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
8607 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
8608 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
8609 them to solve bug 6033.)
8611 o Major features (relay performance):
8612 - Instead of limiting the number of queued onionskins (aka circuit
8613 create requests) to a fixed, hard-to-configure number, we limit
8614 the size of the queue based on how many we expect to be able to
8615 process in a given amount of time. We estimate the time it will
8616 take to process an onionskin based on average processing time
8617 of previous onionskins. Closes ticket 7291. You'll never have to
8618 configure MaxOnionsPending again.
8619 - Relays process the new "NTor" circuit-level handshake requests
8620 with higher priority than the old "TAP" circuit-level handshake
8621 requests. We still process some TAP requests to not totally starve
8622 0.2.3 clients when NTor becomes popular. A new consensus parameter
8623 "NumNTorsPerTAP" lets us tune the balance later if we need to.
8624 Implements ticket 9574.
8626 o Major features (client bootstrapping resilience):
8627 - Add a new "FallbackDir" torrc option to use when we can't use
8628 a directory mirror from the consensus (either because we lack a
8629 consensus, or because they're all down). Currently, all authorities
8630 are fallbacks by default, and there are no other default fallbacks,
8631 but that will change. This option will allow us to give clients a
8632 longer list of servers to try to get a consensus from when first
8633 connecting to the Tor network, and thereby reduce load on the
8634 directory authorities. Implements proposal 206, "Preconfigured
8635 directory sources for bootstrapping". We also removed the old
8636 "FallbackNetworkstatus" option, since we never got it working well
8637 enough to use it. Closes bug 572.
8638 - If we have no circuits open, use a relaxed timeout (the
8639 95th-percentile cutoff) until a circuit succeeds. This heuristic
8640 should allow Tor to succeed at building circuits even when the
8641 network connection drastically changes. Should help with bug 3443.
8643 o Major features (use of guards):
8644 - Support directory guards (proposal 207): when possible, clients now
8645 use their entry guards for non-anonymous directory requests. This
8646 can help prevent client enumeration. Note that this behavior only
8647 works when we have a usable consensus directory, and when options
8648 about what to download are more or less standard. In the future we
8649 should re-bootstrap from our guards, rather than re-bootstrapping
8650 from the preconfigured list of directory sources that ships with
8651 Tor. Resolves ticket 6526.
8652 - Raise the default time that a client keeps an entry guard from
8653 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
8654 2012 paper. (We would make it even longer, but we need better client
8655 load balancing first.) Also, make the guard lifetime controllable
8656 via a new GuardLifetime torrc option and a GuardLifetime consensus
8657 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
8659 o Major features (bridges with pluggable transports):
8660 - Bridges now report the pluggable transports they support to the
8661 bridge authority, so it can pass the supported transports on to
8662 bridgedb and/or eventually do reachability testing. Implements
8664 - Automatically forward the TCP ports of pluggable transport
8665 proxies using tor-fw-helper if PortForwarding is enabled. Implements
8668 o Major features (geoip database):
8669 - Maxmind began labelling Tor relays as being in country "A1",
8670 which breaks by-country node selection inside Tor. Now we use a
8671 script to replace "A1" ("Anonymous Proxy") entries in our geoip
8672 file with real country codes. This script fixes about 90% of "A1"
8673 entries automatically and uses manual country code assignments to
8674 fix the remaining 10%. See src/config/README.geoip for details.
8676 - Add GeoIP database for IPv6 addresses. The new config option
8678 - Update to the October 2 2013 Maxmind GeoLite Country database.
8680 o Major features (IPv6):
8681 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
8682 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
8683 to happen. Implements ticket 5535.
8684 - All kind of relays, not just bridges, can now advertise an IPv6
8685 OR port. Implements ticket 6362.
8686 - Relays can now exit to IPv6 addresses: make sure that you have IPv6
8687 connectivity, then set the IPv6Exit flag to 1. Also make sure your
8688 exit policy reads as you would like: the address * applies to all
8689 address families, whereas *4 is IPv4 address only, and *6 is IPv6
8690 addresses only. On the client side, you'll need to wait for enough
8691 exits to support IPv6, apply the "IPv6Traffic" flag to a SocksPort,
8692 and use Socks5. Closes ticket 5547, implements proposal 117 as
8693 revised in proposal 208.
8694 - Bridge authorities now accept IPv6 bridge addresses and include
8695 them in network status documents. Implements ticket 5534.
8696 - Directory authorities vote on IPv6 OR ports. Implements ticket 6363.
8698 o Major features (directory authorities):
8699 - Directory authorities now prefer using measured bandwidths to
8700 advertised ones when computing flags and thresholds. Resolves
8702 - Directory authorities that vote measured bandwidths about more
8703 than a threshold number of relays now treat relays with
8704 unmeasured bandwidths as having bandwidth 0 when computing their
8705 flags. Resolves ticket 8435.
8706 - Directory authorities now support a new consensus method (17)
8707 where they cap the published bandwidth of relays for which
8708 insufficient bandwidth measurements exist. Fixes part of bug 2286.
8709 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
8710 serve any v2 directory information. Now we can test disabling the
8711 old deprecated v2 directory format, and see whether doing so has
8712 any effect on network load. Begins to fix bug 6783.
8714 o Major features (build and portability):
8715 - Switch to a nonrecursive Makefile structure. Now instead of each
8716 Makefile.am invoking other Makefile.am's, there is a master
8717 Makefile.am that includes the others. This change makes our build
8718 process slightly more maintainable, and improves parallelism for
8719 building with make -j. Original patch by Stewart Smith; various
8720 fixes by Jim Meyering.
8721 - Where available, we now use automake's "silent" make rules by
8722 default, so that warnings are easier to spot. You can get the old
8723 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
8724 - Resume building correctly with MSVC and Makefile.nmake. This patch
8725 resolves numerous bugs and fixes reported by ultramage, including
8726 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
8728 o Security features:
8729 - Switch to a completely time-invariant approach for picking nodes
8730 weighted by bandwidth. Our old approach would run through the
8731 part of the loop after it had made its choice slightly slower
8732 than it ran through the part of the loop before it had made its
8733 choice. Addresses ticket 6538.
8734 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
8735 by tor2web clients allows hidden services to identify tor2web
8736 clients through their repeated selection of the same rendezvous
8737 and introduction point circuit endpoints (their guards). Resolves
8740 o Major bugfixes (relay denial of service):
8741 - When we have too much memory queued in circuits (according to a new
8742 MaxMemInCellQueues option), close the circuits that have the oldest
8743 queued cells, on the theory that those are most responsible for
8744 us running low on memory. This prevents us from running out of
8745 memory as a relay if circuits fill up faster than they can be
8746 drained. Fixes bugs 9063 and 9093; bugfix on the 54th commit of
8747 Tor. This bug is a further fix beyond bug 6252, whose fix was
8748 merged into 0.2.3.21-rc.
8749 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
8750 ID: these could be used to create unexpected streams and circuits
8751 which would count as "present" to some parts of Tor but "absent"
8752 to others, leading to zombie circuits and streams or to a bandwidth
8753 denial-of-service. Fixes bug 7889; bugfix on every released version
8754 of Tor. Reported by "oftc_must_be_destroyed".
8755 - Avoid a bug where our response to TLS renegotiation under certain
8756 network conditions could lead to a busy-loop, with 100% CPU
8757 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
8759 o Major bugfixes (asserts, crashes, leaks):
8760 - Prevent the get_freelists() function from running off the end of
8761 the list of freelists if it somehow gets an unrecognized
8762 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
8764 - Avoid a memory leak where we would leak a consensus body when we
8765 find that a consensus which we couldn't previously verify due to
8766 missing certificates is now verifiable. Fixes bug 8719; bugfix
8768 - If we are unable to save a microdescriptor to the journal, do not
8769 drop it from memory and then reattempt downloading it. Fixes bug
8770 9645; bugfix on 0.2.2.6-alpha.
8771 - Fix an assertion failure that would occur when disabling the
8772 ORPort setting on a running Tor process while accounting was
8773 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
8774 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
8775 when an exit connection with optimistic data succeeds immediately
8776 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
8778 - Fix a memory leak that would occur whenever a configuration
8779 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
8781 o Major bugfixes (relay rate limiting):
8782 - When a TLS write is partially successful but incomplete, remember
8783 that the flushed part has been flushed, and notice that bytes were
8784 actually written. Reported and fixed pseudonymously. Fixes bug 7708;
8785 bugfix on Tor 0.1.0.5-rc.
8786 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
8787 to 1GB/1GB. The previous defaults were intended to be "basically
8788 infinite", but it turns out they're now limiting our 100mbit+
8789 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
8790 last time we raised it).
8791 - No longer stop reading or writing on cpuworker connections when
8792 our rate limiting buckets go empty. Now we should handle circuit
8793 handshake requests more promptly. Resolves bug 9731.
8795 o Major bugfixes (client-side privacy):
8796 - When we mark a circuit as unusable for new circuits, have it
8797 continue to be unusable for new circuits even if MaxCircuitDirtiness
8798 is increased too much at the wrong time, or the system clock jumps
8799 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
8800 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
8801 which have resolved to internal addresses") is set, apply that
8802 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
8803 - When an exit relay rejects a stream with reason "exit policy", but
8804 we only know an exit policy summary (e.g. from the microdesc
8805 consensus) for it, do not mark the relay as useless for all exiting.
8806 Instead, mark just the circuit as unsuitable for that particular
8807 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
8809 o Major bugfixes (stream isolation):
8810 - Allow applications to get proper stream isolation with
8811 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
8812 username/password authentication also offer "no authentication". Tor
8813 had previously preferred "no authentication", so the applications
8814 never actually sent Tor their auth details. Now Tor selects
8815 username/password authentication if it's offered. You can disable
8816 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
8817 bug 8117; bugfix on 0.2.3.3-alpha.
8818 - Follow the socks5 protocol when offering username/password
8819 authentication. The fix for bug 8117 exposed this bug, and it
8820 turns out real-world applications like Pidgin do care. Bugfix on
8821 0.2.3.2-alpha; fixes bug 8879.
8823 o Major bugfixes (client circuit building):
8824 - Alter circuit build timeout measurement to start at the point
8825 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
8826 initialization). This should make our timeout measurements more
8827 uniform. Previously, we were sometimes including ORconn setup time
8828 in our circuit build time measurements. Should resolve bug 3443.
8829 - If the circuit build timeout logic is disabled (via the consensus,
8830 or because we are an authority), then don't build testing circuits.
8831 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
8833 o Major bugfixes (client-side DNS):
8834 - Turn off the client-side DNS cache by default. Updating and using
8835 the DNS cache is now configurable on a per-client-port
8836 level. SOCKSPort, DNSPort, etc lines may now contain
8837 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
8838 cache these types of DNS answers when we receive them from an
8839 exit node in response to an application request on this port, and
8840 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
8841 cached DNS answers of these types, we shouldn't use them. It's
8842 potentially risky to use cached DNS answers at the client, since
8843 doing so can indicate to one exit what answers we've gotten
8844 for DNS lookups in the past. With IPv6, this becomes especially
8845 problematic. Using cached DNS answers for requests on the same
8846 circuit would present less linkability risk, since all traffic
8847 on a circuit is already linkable, but it would also provide
8848 little performance benefit: the exit node caches DNS replies
8849 too. Implements a simplified version of Proposal 205. Implements
8852 o Major bugfixes (hidden service privacy):
8853 - Limit hidden service descriptors to at most ten introduction
8854 points, to slow one kind of guard enumeration. Fixes bug 9002;
8855 bugfix on 0.1.1.11-alpha.
8857 o Major bugfixes (directory fetching):
8858 - If the time to download the next old-style networkstatus is in
8859 the future, do not decline to consider whether to download the
8860 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
8862 - We used to always request authority certificates by identity digest,
8863 meaning we'd get the newest one even when we wanted one with a
8864 different signing key. Then we would complain about being given
8865 a certificate we already had, and never get the one we really
8866 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
8867 resource to request the one we want. Fixes bug 5595; bugfix on
8870 o Major bugfixes (bridge reachability):
8871 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
8872 previously they did not, which prevented them from receiving
8873 successful connections from relays for self-test or bandwidth
8874 testing. Also, when a relay is extending a circuit to a bridge,
8875 it needs to send a NETINFO cell, even when the bridge hasn't sent
8876 an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
8878 o Major bugfixes (control interface):
8879 - When receiving a new configuration file via the control port's
8880 LOADCONF command, do not treat the defaults file as absent.
8881 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
8883 o Major bugfixes (directory authorities):
8884 - Stop marking every relay as having been down for one hour every
8885 time we restart a directory authority. These artificial downtimes
8886 were messing with our Stable and Guard flag calculations. Fixes
8887 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
8888 - When computing directory thresholds, ignore any rejected-as-sybil
8889 nodes during the computation so that they can't influence Fast,
8890 Guard, etc. (We should have done this for proposal 109.) Fixes
8892 - When marking a node as a likely sybil, reset its uptime metrics
8893 to zero, so that it cannot time towards getting marked as Guard,
8894 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
8896 - Fix a bug in the voting algorithm that could yield incorrect results
8897 when a non-naming authority declared too many flags. Fixes bug 9200;
8898 bugfix on 0.2.0.3-alpha.
8900 o Internal abstraction features:
8901 - Introduce new channel_t abstraction between circuits and
8902 or_connection_t to allow for implementing alternate OR-to-OR
8903 transports. A channel_t is an abstract object which can either be a
8904 cell-bearing channel, which is responsible for authenticating and
8905 handshaking with the remote OR and transmitting cells to and from
8906 it, or a listening channel, which spawns new cell-bearing channels
8907 at the request of remote ORs. Implements part of ticket 6465.
8908 - Make a channel_tls_t subclass of channel_t, adapting it to the
8909 existing or_connection_t code. The V2/V3 protocol handshaking
8910 code which formerly resided in command.c has been moved below the
8911 channel_t abstraction layer and may be found in channeltls.c now.
8912 Implements the rest of ticket 6465.
8913 - Introduce new circuitmux_t storing the queue of circuits for
8914 a channel; this encapsulates and abstracts the queue logic and
8915 circuit selection policy, and allows the latter to be overridden
8916 easily by switching out a policy object. The existing EWMA behavior
8917 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
8919 o New build requirements:
8920 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
8921 strongly recommended.
8922 - Tor maintainers now require Automake version 1.9 or later to build
8923 Tor from the Git repository. (Automake is not required when building
8924 from a source distribution.)
8926 o Minor features (protocol):
8927 - No longer include the "opt" prefix when generating routerinfos
8928 or v2 directories: it has been needless since Tor 0.1.2. Closes
8930 - Reject EXTEND cells sent to nonexistent streams. According to the
8931 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
8932 we were only checking for stream IDs that were currently in use.
8933 Found while hunting for more instances of bug 6271. Bugfix on
8934 0.0.2pre8, which introduced incremental circuit construction.
8935 - Tor relays and clients now support a better CREATE/EXTEND cell
8936 format, allowing the sender to specify multiple address, identity,
8937 and handshake types. Implements Robert Ransom's proposal 200;
8939 - Reject as invalid most directory objects containing a NUL.
8940 Belt-and-suspender fix for bug 8037.
8942 o Minor features (security):
8943 - Clear keys and key-derived material left on the stack in
8944 rendservice.c and rendclient.c. Check return value of
8945 crypto_pk_write_private_key_to_string() in rend_service_load_keys().
8946 These fixes should make us more forward-secure against cold-boot
8947 attacks and the like. Fixes bug 2385.
8948 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
8949 Irix's random() only return 15 bits; Solaris's random() returns more
8950 bits but its RAND_MAX says it only returns 15, and so on. Motivated
8951 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
8953 o Minor features (control protocol):
8954 - Add a "GETINFO signal/names" control port command. Implements
8956 - Provide default values for all options via "GETINFO config/defaults".
8957 Implements ticket 4971.
8958 - Allow an optional $ before the node identity digest in the
8959 controller command GETINFO ns/id/<identity>, for consistency with
8960 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
8961 - Add CACHED keyword to ADDRMAP events in the control protocol
8962 to indicate whether a DNS result will be cached or not. Resolves
8964 - Generate bootstrapping status update events correctly when fetching
8965 microdescriptors. Fixes bug 9927.
8967 o Minor features (path selection):
8968 - When deciding whether we have enough descriptors to build circuits,
8969 instead of looking at raw relay counts, look at which fraction
8970 of (bandwidth-weighted) paths we're able to build. This approach
8971 keeps clients from building circuits if their paths are likely to
8972 stand out statistically. The default fraction of paths needed is
8973 taken from the consensus directory; you can override it with the
8974 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
8975 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
8976 and we have GeoIP information, also exclude all nodes with unknown
8977 countries "??" and "A1". This behavior is controlled by the
8978 new GeoIPExcludeUnknown option: you can make such nodes always
8979 excluded with "GeoIPExcludeUnknown 1", and disable the feature
8980 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
8981 gets you the default behavior. Implements feature 7706.
8983 o Minor features (hidden services):
8984 - Improve circuit build timeout handling for hidden services.
8985 In particular: adjust build timeouts more accurately depending
8986 upon the number of hop-RTTs that a particular circuit type
8987 undergoes. Additionally, launch intro circuits in parallel
8988 if they timeout, and take the first one to reply as valid.
8989 - The Tor client now ignores sub-domain components of a .onion
8990 address. This change makes HTTP "virtual" hosting
8991 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
8992 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
8993 hosted on the same hidden service. Implements proposal 204.
8994 - Enable Tor to read configuration, state, and key information from
8995 a FIFO. Previously Tor would only read from files with a positive
8996 stat.st_size. Code from meejah; fixes bug 6044.
8998 o Minor features (clients):
8999 - Teach bridge-using clients to avoid 0.2.2.x bridges when making
9000 microdescriptor-related dir requests, and only fall back to normal
9001 descriptors if none of their bridges can handle microdescriptors
9002 (as opposed to the fix in ticket 4013, which caused them to fall
9003 back to normal descriptors if *any* of their bridges preferred
9004 them). Resolves ticket 4994.
9005 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
9006 TCP ports to forward. In the past it only accepted two ports:
9007 the ORPort and the DirPort.
9009 o Minor features (protecting client timestamps):
9010 - Clients no longer send timestamps in their NETINFO cells. These were
9011 not used for anything, and they provided one small way for clients
9012 to be distinguished from each other as they moved from network to
9013 network or behind NAT. Implements part of proposal 222.
9014 - Clients now round timestamps in INTRODUCE cells down to the nearest
9015 10 minutes. If a new Support022HiddenServices option is set to 0, or
9016 if it's set to "auto" and the feature is disabled in the consensus,
9017 the timestamp is sent as 0 instead. Implements part of proposal 222.
9018 - Stop sending timestamps in AUTHENTICATE cells. This is not such
9019 a big deal from a security point of view, but it achieves no actual
9020 good purpose, and isn't needed. Implements part of proposal 222.
9021 - Reduce down accuracy of timestamps in hidden service descriptors.
9022 Implements part of proposal 222.
9024 o Minor features (bridges):
9025 - Make bridge relays check once a minute for whether their IP
9026 address has changed, rather than only every 15 minutes. Resolves
9028 - Bridge statistics now count bridge clients connecting over IPv6:
9029 bridge statistics files now list "bridge-ip-versions" and
9030 extra-info documents list "geoip6-db-digest". The control protocol
9031 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
9032 implementation by "shkoo", addressing ticket 5055.
9033 - Add a new torrc option "ServerTransportListenAddr" to let bridge
9034 operators select the address where their pluggable transports will
9035 listen for connections. Resolves ticket 7013.
9036 - Randomize the lifetime of our SSL link certificate, so censors can't
9037 use the static value for filtering Tor flows. Resolves ticket 8443;
9038 related to ticket 4014 which was included in 0.2.2.33.
9040 o Minor features (relays):
9041 - Option OutboundBindAddress can be specified multiple times and
9042 accepts IPv6 addresses. Resolves ticket 6876.
9044 o Minor features (IPv6, client side):
9045 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
9046 prefer to hand out virtual IPv6 addresses, since there are more of
9047 them and we can't run out. To override this behavior and make IPv4
9048 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
9049 or DNSPort you're using for resolving. Implements ticket 7571.
9050 - AutomapHostsOnResolve responses are now randomized, to avoid
9051 annoying situations where Tor is restarted and applications
9052 connect to the wrong addresses.
9053 - Never try more than 1000 times to pick a new virtual address when
9054 AutomapHostsOnResolve is set. That's good enough so long as we
9055 aren't close to handing out our entire virtual address space;
9056 if you're getting there, it's best to switch to IPv6 virtual
9059 o Minor features (IPv6, relay/authority side):
9060 - New config option "AuthDirHasIPv6Connectivity 1" that directory
9061 authorities should set if they have IPv6 connectivity and want to
9062 do reachability tests for IPv6 relays. Implements feature 5974.
9063 - A relay with an IPv6 OR port now sends that address in NETINFO
9064 cells (in addition to its other address). Implements ticket 6364.
9066 o Minor features (directory authorities):
9067 - Directory authorities no long accept descriptors for any version of
9068 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
9069 These versions are insecure, unsupported, or both. Implements
9071 - When directory authorities are computing thresholds for flags,
9072 never let the threshold for the Fast flag fall below 4096
9073 bytes. Also, do not consider nodes with extremely low bandwidths
9074 when deciding thresholds for various directory flags. This change
9075 should raise our threshold for Fast relays, possibly in turn
9076 improving overall network performance; see ticket 1854. Resolves
9078 - Directory authorities now include inside each vote a statement of
9079 the performance thresholds they used when assigning flags.
9080 Implements ticket 8151.
9081 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
9082 in directory authority votes to describe whether they have enough
9083 measured bandwidths to ignore advertised (relay descriptor)
9084 bandwidth claims. Resolves ticket 8711.
9086 o Minor features (path bias detection):
9087 - Path Use Bias: Perform separate accounting for successful circuit
9088 use. Keep separate statistics on stream attempt rates versus stream
9089 success rates for each guard. Provide configurable thresholds to
9090 determine when to emit log messages or disable use of guards that
9091 fail too many stream attempts. Resolves ticket 7802.
9092 - Create three levels of Path Bias log messages, as opposed to just
9093 two. These are configurable via consensus as well as via the torrc
9094 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
9095 The default values are 0.70, 0.50, and 0.30 respectively.
9096 - Separate the log message levels from the decision to drop guards,
9097 which also is available via torrc option PathBiasDropGuards.
9098 PathBiasDropGuards still defaults to 0 (off).
9099 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
9100 in combination with PathBiasExtremeRate.
9101 - Increase the default values for PathBiasScaleThreshold and
9102 PathBiasCircThreshold from (200, 20) to (300, 150).
9103 - Add in circuit usage accounting to path bias. If we try to use a
9104 built circuit but fail for any reason, it counts as path bias.
9105 Certain classes of circuits where the adversary gets to pick your
9106 destination node are exempt from this accounting. Usage accounting
9107 can be specifically disabled via consensus parameter or torrc.
9108 - Convert all internal path bias state to double-precision floating
9109 point, to avoid roundoff error and other issues.
9110 - Only record path bias information for circuits that have completed
9111 *two* hops. Assuming end-to-end tagging is the attack vector, this
9112 makes us more resilient to ambient circuit failure without any
9113 detection capability loss.
9115 o Minor features (build):
9116 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
9117 dhill. Resolves ticket 6982.
9118 - Compile on win64 using mingw64. Fixes bug 7260; patches from
9120 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
9121 separate error codes; or at least, don't break for that reason.
9122 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
9124 o Build improvements (autotools):
9125 - Warn if building on a platform with an unsigned time_t: there
9126 are too many places where Tor currently assumes that time_t can
9127 hold negative values. We'd like to fix them all, but probably
9129 - Do not report status verbosely from autogen.sh unless the -v flag
9130 is specified. Fixes issue 4664. Patch from Onizuka.
9131 - Detect and reject attempts to build Tor with threading support
9132 when OpenSSL has been compiled without threading support.
9134 - Try to detect if we are ever building on a platform where
9135 memset(...,0,...) does not set the value of a double to 0.0. Such
9136 platforms are permitted by the C standard, though in practice
9137 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
9138 currently support them, but it's better to detect them and fail
9139 than to perform erroneously.
9140 - We no longer warn so much when generating manpages from their
9142 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
9143 the signs of types during autoconf. This is better than our old
9144 approach, which didn't work when cross-compiling.
9146 o Minor features (log messages, warnings):
9147 - Detect when we're running with a version of OpenSSL other than the
9148 one we compiled with. This conflict has occasionally given people
9149 hard-to-track-down errors.
9150 - Warn users who run hidden services on a Tor client with
9151 UseEntryGuards disabled that their hidden services will be
9152 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
9153 attack which motivated Tor to support entry guards in the first
9154 place). Resolves ticket 6889.
9155 - Warn when we are binding low ports when hibernation is enabled;
9156 previously we had warned when we were _advertising_ low ports with
9157 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
9158 - Issue a warning when running with the bufferevents backend enabled.
9159 It's still not stable, and people should know that they're likely
9160 to hit unexpected problems. Closes ticket 9147.
9162 o Minor features (log messages, notices):
9163 - Refactor resolve_my_address() so it returns the method by which we
9164 decided our public IP address (explicitly configured, resolved from
9165 explicit hostname, guessed from interfaces, learned by gethostname).
9166 Now we can provide more helpful log messages when a relay guesses
9167 its IP address incorrectly (e.g. due to unexpected lines in
9168 /etc/hosts). Resolves ticket 2267.
9169 - Track how many "TAP" and "NTor" circuit handshake requests we get,
9170 and how many we complete, and log it every hour to help relay
9171 operators follow trends in network load. Addresses ticket 9658.
9173 o Minor features (log messages, diagnostics):
9174 - If we fail to free a microdescriptor because of bug 7164, log
9175 the filename and line number from which we tried to free it.
9176 - We compute the overhead from passing onionskins back and forth to
9177 cpuworkers, and report it when dumping statistics in response to
9178 SIGUSR1. Supports ticket 7291.
9179 - Add another diagnostic to the heartbeat message: track and log
9180 overhead that TLS is adding to the data we write. If this is
9181 high, we are sending too little data to SSL_write at a time.
9182 Diagnostic for bug 7707.
9183 - Log packaged cell fullness as part of the heartbeat message.
9184 Diagnosis to try to determine the extent of bug 7743.
9185 - Add more detail to a log message about relaxed timeouts, to help
9187 - When learning a fingerprint for a bridge, log its corresponding
9188 transport type. Implements ticket 7896.
9189 - Warn more aggressively when flushing microdescriptors to a
9190 microdescriptor cache fails, in an attempt to mitigate bug 8031,
9191 or at least make it more diagnosable.
9192 - Improve the log message when "Bug/attack: unexpected sendme cell
9193 from client" occurs, to help us track bug 8093.
9194 - Improve debugging output to help track down bug 8185 ("Bug:
9195 outgoing relay cell has n_chan==NULL. Dropping.")
9197 o Minor features (log messages, quieter bootstrapping):
9198 - Log fewer lines at level "notice" about our OpenSSL and Libevent
9199 versions and capabilities when everything is going right. Resolves
9200 part of ticket 6736.
9201 - Omit the first heartbeat log message, because it never has anything
9202 useful to say, and it clutters up the bootstrapping messages.
9203 Resolves ticket 6758.
9204 - Don't log about reloading the microdescriptor cache at startup. Our
9205 bootstrap warnings are supposed to tell the user when there's a
9206 problem, and our bootstrap notices say when there isn't. Resolves
9207 ticket 6759; bugfix on 0.2.2.6-alpha.
9208 - Don't log "I learned some more directory information" when we're
9209 reading cached directory information. Reserve it for when new
9210 directory information arrives in response to a fetch. Resolves
9212 - Don't complain about bootstrapping problems while hibernating.
9213 These complaints reflect a general code problem, but not one
9214 with any problematic effects (no connections are actually
9215 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
9217 o Minor features (testing):
9218 - In our testsuite, create temporary directories with a bit more
9219 entropy in their name to make name collisions less likely. Fixes
9221 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
9222 (P-256) Diffie-Hellman handshakes to src/or/bench.
9223 - Add benchmark functions to test onion handshake performance.
9226 - The DirServer option is now DirAuthority, for consistency with
9227 current naming patterns. You can still use the old DirServer form.
9229 o Minor bugfixes (protocol):
9230 - Fix the handling of a TRUNCATE cell when it arrives while the
9231 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
9232 - When a Tor client gets a "truncated" relay cell, the first byte of
9233 its payload specifies why the circuit was truncated. We were
9234 ignoring this 'reason' byte when tearing down the circuit, resulting
9235 in the controller not being told why the circuit closed. Now we
9236 pass the reason from the truncated cell to the controller. Bugfix
9237 on 0.1.2.3-alpha; fixes bug 7039.
9238 - Fix a misframing issue when reading the version numbers in a
9239 VERSIONS cell. Previously we would recognize [00 01 00 02] as
9240 'version 1, version 2, and version 0x100', when it should have
9241 only included versions 1 and 2. Fixes bug 8059; bugfix on
9242 0.2.0.10-alpha. Reported pseudonymously.
9243 - Make the format and order of STREAM events for DNS lookups
9244 consistent among the various ways to launch DNS lookups. Fixes
9245 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy".
9247 o Minor bugfixes (syscalls and disk interaction):
9248 - Always check the return values of functions fcntl() and
9249 setsockopt(). We don't believe these are ever actually failing in
9250 practice, but better safe than sorry. Also, checking these return
9251 values should please analysis tools like Coverity. Patch from
9252 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
9253 - Avoid double-closing the listener socket in our socketpair()
9254 replacement (used on Windows) in the case where the addresses on
9255 our opened sockets don't match what we expected. Fixes bug 9400;
9256 bugfix on 0.0.2pre7. Found by Coverity.
9257 - Correctly store microdescriptors and extrainfo descriptors that
9258 include an internal NUL byte. Fixes bug 8037; bugfix on
9259 0.2.0.1-alpha. Bug reported by "cypherpunks".
9260 - If for some reason we fail to write a microdescriptor while
9261 rebuilding the cache, do not let the annotations from that
9262 microdescriptor linger in the cache file, and do not let the
9263 microdescriptor stay recorded as present in its old location.
9264 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
9265 - Use direct writes rather than stdio when building microdescriptor
9266 caches, in an attempt to mitigate bug 8031, or at least make it
9269 o Minor fixes (config options):
9270 - Warn and fail if a server is configured not to advertise any
9271 ORPorts at all. (We need *something* to put in our descriptor,
9272 or we just won't work.)
9273 - Behave correctly when the user disables LearnCircuitBuildTimeout
9274 but doesn't tell us what they would like the timeout to be. Fixes
9275 bug 6304; bugfix on 0.2.2.14-alpha.
9276 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
9277 to start with a triple-underscore so the controller won't touch it.
9278 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
9279 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
9280 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
9281 - When autodetecting the number of CPUs, use the number of available
9282 CPUs in preference to the number of configured CPUs. Inform the
9283 user if this reduces the number of available CPUs. Fixes bug 8002;
9284 bugfix on 0.2.3.1-alpha.
9285 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
9286 - Make it an error when you set EntryNodes but disable UseGuardNodes,
9287 since it will (surprisingly to some users) ignore EntryNodes. Fixes
9288 bug 8180; bugfix on 0.2.3.11-alpha.
9289 - Avoid overflows when the user sets MaxCircuitDirtiness to a
9290 ridiculously high value, by imposing a (ridiculously high) 30-day
9291 maximum on MaxCircuitDirtiness.
9293 o Minor bugfixes (control protocol):
9294 - Stop sending a stray "(null)" in some cases for the server status
9295 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
9297 - The ADDRMAP command can no longer generate an ill-formed error
9298 code on a failed MAPADDRESS. It now says "internal" rather than
9299 an English sentence fragment with spaces in the middle. Bugfix on
9302 o Minor bugfixes (clients / edges):
9303 - When we receive a RELAY_END cell with the reason DONE, or with no
9304 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
9305 status as "connection refused". Previously we reported these cases
9306 as success but then immediately closed the connection. Fixes bug
9307 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
9308 - If the guard we choose first doesn't answer, we would try the
9309 second guard, but once we connected to the second guard we would
9310 abandon it and retry the first one, slowing down bootstrapping.
9311 The fix is to treat all our initially chosen guards as acceptable
9312 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
9313 - When choosing which stream on a formerly stalled circuit to wake
9314 first, make better use of the platform's weak RNG. Previously,
9315 we had been using the % ("modulo") operator to try to generate a
9316 1/N chance of picking each stream, but this behaves badly with
9317 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
9320 o Minor bugfixes (path bias detection):
9321 - If the state file's path bias counts are invalid (presumably from a
9322 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
9323 additional checks and log messages to the scaling of Path Bias
9324 counts, in case there still are remaining issues with scaling.
9325 Should help resolve bug 8235.
9326 - Prevent rounding error in path bias counts when scaling
9327 them down, and use the correct scale factor default. Also demote
9328 some path bias related log messages down a level and make others
9329 less scary sounding. Fixes bug 6647. Bugfix on 0.2.3.17-beta.
9330 - Remove a source of rounding error during path bias count scaling;
9331 don't count cannibalized circuits as used for path bias until we
9332 actually try to use them; and fix a circuit_package_relay_cell()
9333 warning message about n_chan==NULL. Fixes bug 7802.
9334 - Paste the description for PathBias parameters from the man
9335 page into or.h, so the code documents them too. Fixes bug 7982;
9336 bugfix on 0.2.3.17-beta.
9338 o Minor bugfixes (relays):
9339 - Stop trying to resolve our hostname so often (e.g. every time we
9340 think about doing a directory fetch). Now we reuse the cached
9341 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
9342 and 2410 (bugfix on 0.1.2.2-alpha).
9343 - When examining the list of network interfaces to find our address,
9344 do not consider non-running or disabled network interfaces. Fixes
9345 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
9347 o Minor bugfixes (blocking resistance):
9348 - Only disable TLS session ticket support when running as a TLS
9349 server. Now clients will blend better with regular Firefox
9350 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
9352 o Minor bugfixes (IPv6):
9353 - Use square brackets around IPv6 addresses in numerous places
9354 that needed them, including log messages, HTTPS CONNECT proxy
9355 requests, TransportProxy statefile entries, and pluggable transport
9356 extra-info lines. Fixes bug 7011; patch by David Fifield.
9358 o Minor bugfixes (directory authorities):
9359 - Reject consensus votes with more than 64 known-flags. We aren't even
9360 close to that limit yet, and our code doesn't handle it correctly.
9361 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
9362 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
9363 bugfix on 0.2.0.3-alpha.
9365 o Minor bugfixes (memory leaks):
9366 - Avoid leaking memory if we fail to compute a consensus signature
9367 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
9368 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
9369 on 0.2.1.1-alpha; fixes bug 7816.
9370 - Fix a memory leak during safe-cookie controller authentication.
9371 Bugfix on 0.2.3.13-alpha; fixes bug 7816.
9372 - Free some more still-in-use memory at exit, to make hunting for
9373 memory leaks easier. Resolves bug 7029.
9375 o Minor bugfixes (code correctness):
9376 - Increase the width of the field used to remember a connection's
9377 link protocol version to two bytes. Harmless for now, since the
9378 only currently recognized versions are one byte long. Reported
9379 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
9380 - Fix a crash when debugging unit tests on Windows: deallocate a
9381 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
9382 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
9383 - When detecting the largest possible file descriptor (in order to
9384 close all file descriptors when launching a new program), actually
9385 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
9386 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
9388 - Avoid a crash if we fail to generate an extrainfo descriptor.
9389 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
9391 - Avoid an off-by-one error when checking buffer boundaries when
9392 formatting the exit status of a pluggable transport helper.
9393 This is probably not an exploitable bug, but better safe than
9394 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
9396 - Get rid of a couple of harmless clang warnings, where we compared
9397 enums to ints. These warnings are newly introduced in clang 3.2.
9399 o Minor bugfixes (code cleanliness):
9400 - Avoid use of reserved identifiers in our C code. The C standard
9401 doesn't like us declaring anything that starts with an
9402 underscore, so let's knock it off before we get in trouble. Fix
9403 for bug 1031; bugfix on the first Tor commit.
9404 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
9405 with large values. This situation was untriggered, but nevertheless
9406 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
9407 - Fix an impossible buffer overrun in the AES unit tests. Fixes
9408 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
9409 - Fix handling of rendezvous client authorization types over 8.
9410 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
9411 - Remove a couple of extraneous semicolons that were upsetting the
9412 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
9413 bugfix on 0.2.2.1-alpha.
9414 - When complaining about a client port on a public address, log
9415 which address we're complaining about. Fixes bug 4020; bugfix on
9416 0.2.3.3-alpha. Patch by Tom Fitzhenry.
9418 o Minor bugfixes (log messages, warnings):
9419 - If we encounter a write failure on a SOCKS connection before we
9420 finish our SOCKS handshake, don't warn that we closed the
9421 connection before we could send a SOCKS reply. Fixes bug 8427;
9422 bugfix on 0.1.0.1-rc.
9423 - Fix a directory authority warn caused when we have a large amount
9424 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
9425 - Downgrade "Failed to hand off onionskin" messages to "debug"
9426 severity, since they're typically redundant with the "Your computer
9427 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
9428 - Avoid spurious warnings when configuring multiple client ports of
9429 which only some are nonlocal. Previously, we had claimed that some
9430 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
9433 o Minor bugfixes (log messages, other):
9434 - Fix log messages and comments to avoid saying "GMT" when we mean
9435 "UTC". Fixes bug 6113.
9436 - When rejecting a configuration because we were unable to parse a
9437 quoted string, log an actual error message. Fixes bug 7950; bugfix
9439 - Correctly recognize that [::1] is a loopback address. Fixes
9440 bug 8377; bugfix on 0.2.1.3-alpha.
9441 - Don't log inappropriate heartbeat messages when hibernating: a
9442 hibernating node is _expected_ to drop out of the consensus,
9443 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
9444 bugfix on 0.2.3.1-alpha.
9445 - Eliminate several instances where we use "Nickname=ID" to refer to
9446 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
9447 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
9450 o Minor bugfixes (build):
9451 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
9452 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
9453 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
9455 o Documentation fixes:
9456 - Make the torify manpage no longer refer to tsocks; torify hasn't
9457 supported tsocks since 0.2.3.14-alpha.
9458 - Make the tor manpage no longer reference tsocks.
9459 - Fix the GeoIPExcludeUnknown documentation to refer to
9460 ExcludeExitNodes rather than the currently nonexistent
9461 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
9462 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
9464 - Say "KBytes" rather than "KB" in the man page (for various values
9465 of K), to further reduce confusion about whether Tor counts in
9466 units of memory or fractions of units of memory. Resolves ticket 7054.
9467 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
9468 names match. Fixes bug 7768.
9469 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
9470 message is logged at notice, not at info.
9471 - Clarify the usage and risks of setting the ContactInfo torrc line
9472 for your relay or bridge. Resolves ticket 9854.
9473 - Add anchors to the manpage so we can link to the html version of
9474 the documentation for specific options. Resolves ticket 9866.
9475 - Replace remaining references to DirServer in man page and
9476 log entries. Resolves ticket 10124.
9479 - Stop exporting estimates of v2 and v3 directory traffic shares
9480 in extrainfo documents. They were unneeded and sometimes inaccurate.
9481 Also stop exporting any v2 directory request statistics. Resolves
9483 - Drop support for detecting and warning about versions of Libevent
9484 before 1.3e. Nothing reasonable ships with them any longer; warning
9485 the user about them shouldn't be needed. Resolves ticket 6826.
9486 - Now that all versions before 0.2.2.x are disallowed, we no longer
9487 need to work around their missing features. Remove a bunch of
9491 - The tor-tsocks.conf is no longer distributed or installed. We
9492 recommend that tsocks users use torsocks instead. Resolves
9494 - Remove some of the older contents of doc/ as obsolete; move others
9495 to torspec.git. Fixes bug 8965.
9497 o Code simplification:
9498 - Avoid using character buffers when constructing most directory
9499 objects: this approach was unwieldy and error-prone. Instead,
9500 build smartlists of strings, and concatenate them when done.
9501 - Rename "isin" functions to "contains", for grammar. Resolves
9503 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
9504 with the natural logarithm function from the system libm. Resolves
9506 - Start using OpenBSD's implementation of queue.h, so that we don't
9507 need to hand-roll our own pointer and list structures whenever we
9508 need them. (We can't rely on a sys/queue.h, since some operating
9509 systems don't have them, and the ones that do have them don't all
9510 present the same extensions.)
9511 - Start using OpenBSD's implementation of queue.h (originally by
9513 - Enhance our internal sscanf replacement so that we can eliminate
9514 the last remaining uses of the system sscanf. (Though those uses
9515 of sscanf were safe, sscanf itself is generally error prone, so
9516 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
9518 - Replace all calls to snprintf() outside of src/ext with
9519 tor_snprintf(). Also remove the #define to replace snprintf with
9520 _snprintf on Windows; they have different semantics, and all of
9521 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
9524 - Add a wrapper function for the common "log a message with a
9526 - Split the onion.c file into separate modules for the onion queue
9527 and the different handshakes it supports.
9528 - Move the client-side address-map/virtual-address/DNS-cache code
9529 out of connection_edge.c into a new addressmap.c module.
9530 - Move the entry node code from circuitbuild.c to its own file.
9531 - Move the circuit build timeout tracking code from circuitbuild.c
9533 - Source files taken from other packages now reside in src/ext;
9534 previously they were scattered around the rest of Tor.
9535 - Move the generic "config" code into a new file, and have "config.c"
9536 hold only torrc- and state-related code. Resolves ticket 6823.
9537 - Move the core of our "choose a weighted element at random" logic
9538 into its own function, and give it unit tests. Now the logic is
9539 testable, and a little less fragile too.
9540 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
9541 - Move last_reachable and testing_since from routerinfo_t to node_t.
9542 Implements ticket 5529.
9543 - Add replaycache_t structure, functions and unit tests, then refactor
9544 rend_service_introduce() to be more clear to read, improve, debug,
9545 and test. Resolves bug 6177.
9548 - Remove some now-needless code that tried to aggressively flush
9549 OR connections as data was added to them. Since 0.2.0.1-alpha, our
9550 cell queue logic has saved us from the failure mode that this code
9551 was supposed to prevent. Removing this code will limit the number
9552 of baroque control flow paths through Tor's network logic. Reported
9553 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
9554 - Remove unused code for parsing v1 directories and "running routers"
9555 documents. Fixes bug 6887.
9556 - Remove the marshalling/unmarshalling code for sending requests to
9557 cpuworkers over a socket, and instead just send structs. The
9558 recipient will always be the same Tor binary as the sender, so
9559 any encoding is overkill.
9560 - Remove the testing_since field of node_t, which hasn't been used
9561 for anything since 0.2.0.9-alpha.
9562 - Finally remove support for malloc_good_size and malloc_usable_size.
9563 We had hoped that these functions would let us eke a little more
9564 memory out of our malloc implementation. Unfortunately, the only
9565 implementations that provided these functions are also ones that
9566 are already efficient about not overallocation: they never got us
9567 more than 7 or so bytes per allocation. Removing them saves us a
9568 little code complexity and a nontrivial amount of build complexity.
9571 Changes in version 0.2.3.25 - 2012-11-19
9572 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
9573 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
9574 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
9575 programmer, and friend. Unstinting in his dedication to the cause of
9576 freedom, he inspired and helped many of us as we began our work on
9577 anonymity, and inspires us still. Please honor his memory by writing
9578 software to protect people's freedoms, and by helping others to do so.
9580 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
9581 significantly reduced directory overhead (via microdescriptors),
9582 enormous crypto performance improvements for fast relays on new
9583 enough hardware, a new v3 TLS handshake protocol that can better
9584 resist fingerprinting, support for protocol obfuscation plugins (aka
9585 pluggable transports), better scalability for hidden services, IPv6
9586 support for bridges, performance improvements like allowing clients
9587 to skip the first round-trip on the circuit ("optimistic data") and
9588 refilling token buckets more often, a new "stream isolation" design
9589 to isolate different applications on different circuits, and many
9590 stability, security, and privacy fixes.
9592 Major features (v3 directory protocol):
9593 - Clients now use microdescriptors instead of regular descriptors
9594 to build circuits. Microdescriptors are authority-generated
9595 summaries of regular descriptors' contents, designed to change very
9596 rarely (see proposal 158 for details). This feature is designed
9597 to save bandwidth, especially for clients on slow internet
9598 connections. Use "UseMicrodescriptors 0" to disable it.
9599 - Caches now download, cache, and serve microdescriptors, as well
9600 as multiple "flavors" of the consensus, including a flavor that
9601 describes microdescriptors.
9603 o Major features (build hardening):
9604 - Enable gcc and ld hardening by default. Resolves ticket 5210.
9606 o Major features (relay scaling):
9607 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
9608 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
9609 vectorized AES implementations as appropriate. These can be much,
9610 much faster than other AES implementations.
9611 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
9612 implementation. It makes AES_CTR about 7% faster than our old one
9613 (which was about 10% faster than the one OpenSSL used to provide).
9614 Resolves ticket 4526.
9615 - Use OpenSSL's EVP interface for AES encryption, so that all AES
9616 operations can use hardware acceleration (if present). Resolves
9618 - Unconditionally use OpenSSL's AES implementation instead of our
9619 old built-in one. OpenSSL's AES has been better for a while, and
9620 relatively few servers should still be on any version of OpenSSL
9621 that doesn't have good optimized assembly AES.
9623 o Major features (blocking resistance):
9624 - Update TLS cipher list to match Firefox 8 and later. Resolves
9626 - Remove support for clients falsely claiming to support standard
9627 ciphersuites that they can actually provide. As of modern OpenSSL
9628 versions, it's not necessary to fake any standard ciphersuite,
9629 and doing so prevents us from using better ciphersuites in the
9630 future, since servers can't know whether an advertised ciphersuite
9631 is really supported or not. Some hosts -- notably, ones with very
9632 old versions of OpenSSL or where OpenSSL has been built with ECC
9633 disabled -- will stand out because of this change; TBB users should
9634 not be affected. Implements the client side of proposal 198.
9635 - Implement a new handshake protocol (v3) for authenticating Tors to
9636 each other over TLS. It should be more resistant to fingerprinting
9637 than previous protocols, and should require less TLS hacking for
9638 future Tor implementations. Implements proposal 176.
9639 - Allow variable-length padding cells, to disguise the length of
9640 Tor's TLS records. Implements part of proposal 184.
9641 - While we're trying to bootstrap, record how many TLS connections
9642 fail in each state, and report which states saw the most failures
9643 in response to any bootstrap failures. This feature may speed up
9644 diagnosis of censorship events. Implements ticket 3116.
9646 o Major features (pluggable transports):
9647 - Clients and bridges can now be configured to use a separate
9648 "transport" proxy. This approach makes the censorship arms race
9649 easier by allowing bridges to use protocol obfuscation plugins.
9650 Implements proposal 180 (tickets 2841 and 3472).
9652 o Major features (DoS resistance):
9653 - Now that Tor 0.2.0.x is completely deprecated, enable the final
9654 part of "Proposal 110: Avoiding infinite length circuits" by
9655 refusing all circuit-extend requests that do not use a relay_early
9656 cell. This change helps Tor resist a class of denial-of-service
9657 attacks by limiting the maximum circuit length.
9658 - Tear down the circuit if we get an unexpected SENDME cell. Clients
9659 could use this trick to make their circuits receive cells faster
9660 than our flow control would have allowed, or to gum up the network,
9661 or possibly to do targeted memory denial-of-service attacks on
9662 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
9663 from July 2002, before the release of Tor 0.0.0.
9665 o Major features (hidden services):
9666 - Adjust the number of introduction points that a hidden service
9667 will try to maintain based on how long its introduction points
9668 remain in use and how many introductions they handle. Fixes
9670 - Add a "tor2web mode" for clients that want to connect to hidden
9671 services non-anonymously (and possibly more quickly). As a safety
9672 measure to try to keep users from turning this on without knowing
9673 what they are doing, tor2web mode must be explicitly enabled at
9674 compile time, and a copy of Tor compiled to run in tor2web mode
9675 cannot be used as a normal Tor client. Implements feature 2553.
9677 o Major features (IPv6):
9678 - Clients can now connect to private bridges over IPv6. Bridges
9679 still need at least one IPv4 address in order to connect to
9680 other relays. Note that we don't yet handle the case where the
9681 user has two bridge lines for the same bridge (one IPv4, one
9682 IPv6). Implements parts of proposal 186.
9684 o Major features (directory authorities):
9685 - Use a more secure consensus parameter voting algorithm. Now at
9686 least three directory authorities or a majority of them must
9687 vote on a given parameter before it will be included in the
9688 consensus. Implements proposal 178.
9689 - Remove the artificially low cutoff of 20KB to guarantee the Fast
9690 flag. In the past few years the average relay speed has picked
9691 up, and while the "top 7/8 of the network get the Fast flag" and
9692 "all relays with 20KB or more of capacity get the Fast flag" rules
9693 used to have the same result, now the top 7/8 of the network has
9694 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
9696 o Major features (performance):
9697 - Exit nodes now accept and queue data on not-yet-connected streams.
9698 Previously, the client wasn't allowed to send data until the
9699 stream was connected, which slowed down all connections. This
9700 change will enable clients to perform a "fast-start" on streams
9701 and send data without having to wait for a confirmation that the
9702 stream has opened. Patch from Ian Goldberg; implements the server
9703 side of Proposal 174.
9704 - When using an exit relay running 0.2.3.x, clients can now
9705 "optimistically" send data before the exit relay reports that
9706 the stream has opened. This saves a round trip when starting
9707 connections where the client speaks first (such as web browsing).
9708 This behavior is controlled by a consensus parameter (currently
9709 disabled). To turn it on or off manually, use the "OptimisticData"
9710 torrc option. Implements proposal 181; code by Ian Goldberg.
9711 - Add a new TokenBucketRefillInterval option to refill token buckets
9712 more frequently than once per second. This should improve network
9713 performance, alleviate queueing problems, and make traffic less
9714 bursty. Implements proposal 183; closes ticket 3630. Design by
9715 Florian Tschorsch and Björn Scheuermann; implementation by
9717 - Raise the threshold of server descriptors needed (75%) and exit
9718 server descriptors needed (50%) before we will declare ourselves
9719 bootstrapped. This will make clients start building circuits a
9720 little later, but makes the initially constructed circuits less
9721 skewed and less in conflict with further directory fetches. Fixes
9724 o Major features (relays):
9725 - Relays now try regenerating and uploading their descriptor more
9726 frequently if they are not listed in the consensus, or if the
9727 version of their descriptor listed in the consensus is too
9728 old. This fix should prevent situations where a server declines
9729 to re-publish itself because it has done so too recently, even
9730 though the authorities decided not to list its recent-enough
9731 descriptor. Fix for bug 3327.
9733 o Major features (stream isolation):
9734 - You can now configure Tor so that streams from different
9735 applications are isolated on different circuits, to prevent an
9736 attacker who sees your streams as they leave an exit node from
9737 linking your sessions to one another. To do this, choose some way
9738 to distinguish the applications: have them connect to different
9739 SocksPorts, or have one of them use SOCKS4 while the other uses
9740 SOCKS5, or have them pass different authentication strings to the
9741 SOCKS proxy. Then, use the new SocksPort syntax to configure the
9742 degree of isolation you need. This implements Proposal 171.
9743 - There's a new syntax for specifying multiple client ports (such as
9744 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
9745 multiple *Port entries with full addr:port syntax on each.
9746 The old *ListenAddress format is still supported, but you can't
9747 mix it with the new *Port syntax.
9749 o Major features (bufferevents):
9750 - Tor can now optionally build with the "bufferevents" buffered IO
9751 backend provided by Libevent 2. To use this feature, make sure you
9752 have the latest possible version of Libevent, and pass the
9753 --enable-bufferevents flag to configure when building Tor from
9754 source. This feature will make our networking code more flexible,
9755 let us stack layers on each other, and let us use more efficient
9756 zero-copy transports where available.
9757 - Add experimental support for running on Windows with IOCP and no
9758 kernel-space socket buffers. This feature is controlled by a new
9759 "UserspaceIOCPBuffers" config option (off by default), which has
9760 no effect unless Tor has been built with bufferevents enabled,
9761 you're running on Windows, and you've set "DisableIOCP 0". In the
9762 long run, this may help solve or mitigate bug 98.
9764 o Major features (path selection):
9765 - The EntryNodes option can now include country codes like {de} or IP
9766 addresses or network masks. Previously we had disallowed these
9767 options because we didn't have an efficient way to keep the list up
9768 to date. Addresses ticket 1982, but see bug 2798 for an unresolved
9771 o Major features (port forwarding):
9772 - Add support for automatic port mapping on the many home routers
9773 that support NAT-PMP or UPnP. To build the support code, you'll
9774 need to have the libnatpnp library and/or the libminiupnpc library,
9775 and you'll need to enable the feature specifically by passing
9776 "--enable-upnp" and/or "--enable-natpnp" to ./configure. To turn
9777 it on, use the new PortForwarding option.
9779 o Major features (logging):
9780 - Add a new 'Heartbeat' log message type to periodically log a message
9781 describing Tor's status at level Notice. This feature is meant for
9782 operators who log at notice, and want to make sure that their Tor
9783 server is still working. Implementation by George Kadianakis.
9784 - Make logging resolution configurable with a new LogTimeGranularity
9785 option, and change the default from 1 millisecond to 1 second.
9786 Implements enhancement 1668.
9788 o Major features (other):
9789 - New "DisableNetwork" config option to prevent Tor from launching any
9790 connections or accepting any connections except on a control port.
9791 Bundles and controllers can set this option before letting Tor talk
9792 to the rest of the network, for example to prevent any connections
9793 to a non-bridge address. Packages like Orbot can also use this
9794 option to instruct Tor to save power when the network is off.
9795 - Try to use system facilities for enumerating local interface
9796 addresses, before falling back to our old approach (which was
9797 binding a UDP socket, and calling getsockname() on it). That
9798 approach was scaring OS X users whose draconian firewall
9799 software warned about binding to UDP sockets regardless of
9800 whether packets were sent. Now we try to use getifaddrs(),
9801 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
9802 system supports. Resolves ticket 1827.
9803 - Add experimental support for a "defaults" torrc file to be parsed
9804 before the regular torrc. Torrc options override the defaults file's
9805 options in the same way that the command line overrides the torrc.
9806 The SAVECONF controller command saves only those options which
9807 differ between the current configuration and the defaults file. HUP
9808 reloads both files. Implements task 4552.
9810 o New directory authorities:
9811 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
9812 authority. Closes ticket 5749.
9814 o Security/privacy fixes:
9815 - Avoid read-from-freed-memory and double-free bugs that could occur
9816 when a DNS request fails while launching it. Fixes bug 6480;
9817 bugfix on 0.2.0.1-alpha.
9818 - Reject any attempt to extend to an internal address. Without
9819 this fix, a router could be used to probe addresses on an internal
9820 network to see whether they were accepting connections. Fixes bug
9821 6710; bugfix on 0.0.8pre1.
9822 - Close any connection that sends unrecognized junk before the TLS
9823 handshake. Solves an issue noted in bug 4369.
9824 - The advertised platform of a relay now includes only its operating
9825 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not
9826 its service pack level (for Windows) or its CPU architecture
9827 (for Unix). Also drop the "git-XYZ" tag in the version. Packagers
9828 can insert an extra string in the platform line by setting the
9829 preprocessor variable TOR_BUILD_TAG. Resolves bug 2988.
9830 - Disable TLS session tickets. OpenSSL's implementation was giving
9831 our TLS session keys the lifetime of our TLS context objects, when
9832 perfect forward secrecy would want us to discard anything that
9833 could decrypt a link connection as soon as the link connection
9834 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
9835 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
9836 - Tor tries to wipe potentially sensitive data after using it, so
9837 that if some subsequent security failure exposes Tor's memory,
9838 the damage will be limited. But we had a bug where the compiler
9839 was eliminating these wipe operations when it decided that the
9840 memory was no longer visible to a (correctly running) program,
9841 hence defeating our attempt at defense in depth. We fix that
9842 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
9843 is unlikely to optimize away. Future versions of Tor may use
9844 a less ridiculously heavy approach for this. Fixes bug 7352.
9845 Reported in an article by Andrey Karpov.
9847 o Major bugfixes (crashes and asserts):
9848 - Avoid a pair of double-free and use-after-mark bugs that can
9849 occur with certain timings in canceled and re-received DNS
9850 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
9851 - Fix a denial of service attack by which any directory authority
9852 could crash all the others, or by which a single v2 directory
9853 authority could crash everybody downloading v2 directory
9854 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
9855 - Fix an assert that directory authorities could trigger on sighup
9856 during some configuration state transitions. We now don't treat
9857 it as a fatal error when the new descriptor we just generated in
9858 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
9859 - Avoid segfault when starting up having run with an extremely old
9860 version of Tor and parsing its state file. Fixes bug 6801; bugfix
9863 o Major bugfixes (clients):
9864 - If we are unable to find any exit that supports our predicted ports,
9865 stop calling them predicted, so that we don't loop and build
9866 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
9867 which introduced predicted ports.
9868 - Check at each new consensus whether our entry guards were picked
9869 long enough ago that we should rotate them. Previously, we only
9870 did this check at startup, which could lead to us holding a guard
9871 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
9872 - When fetching a bridge descriptor from a bridge authority,
9873 always do so anonymously, whether we have been able to open
9874 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
9875 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
9876 but we'll need to wait for bug 6010 before it's actually usable.
9878 o Major bugfixes (directory voting):
9879 - Check more thoroughly to prevent a rogue authority from
9880 double-voting on any consensus directory parameter. Previously,
9881 authorities would crash in this case if the total number of
9882 votes for any parameter exceeded the number of active voters,
9883 but would let it pass otherwise. Partially fixes bug 5786; bugfix
9885 - When computing weight parameters, behave more robustly in the
9886 presence of a bad bwweightscale value. Previously, the authorities
9887 would crash if they agreed on a sufficiently broken weight_scale
9888 value; now, they use a reasonable default and carry on. Fixes the
9889 rest of bug 5786; bugfix on 0.2.2.17-alpha.
9890 - If authorities are unable to get a v2 consensus document from other
9891 directory authorities, they no longer fall back to fetching
9892 them from regular directory caches. Fixes bug 5635; bugfix on
9893 0.2.2.26-beta, where routers stopped downloading v2 consensus
9896 o Major bugfixes (relays):
9897 - Fix a bug handling SENDME cells on nonexistent streams that could
9898 result in bizarre window values. Report and patch contributed
9899 pseudonymously. Fixes part of bug 6271. This bug was introduced
9900 before the first Tor release, in svn commit r152.
9901 - Don't update the AccountingSoftLimitHitAt state file entry whenever
9902 tor gets started. This prevents a wrong average bandwidth
9903 estimate, which would cause relays to always start a new accounting
9904 interval at the earliest possible moment. Fixes bug 2003; bugfix
9905 on 0.2.2.7-alpha. Reported by Bryon Eldridge, who also helped
9906 immensely in tracking this bug down.
9907 - Fix a possible crash bug when checking for deactivated circuits
9908 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
9909 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
9910 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
9911 connections. This change should allow busy exit relays to stop
9912 running out of available sockets as quickly. Fixes bug 4950;
9913 bugfix on 0.2.2.26-beta.
9915 o Major bugfixes (blocking resistance):
9916 - Bridges no longer include their address in NETINFO cells on outgoing
9917 OR connections, to allow them to blend in better with clients.
9918 Removes another avenue for enumerating bridges. Reported by
9919 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
9920 cells were introduced.
9921 - Warn the user when HTTPProxy, but no other proxy type, is
9922 configured. This can cause surprising behavior: it doesn't send
9923 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
9924 directory traffic only. Resolves ticket 4663.
9926 o Major bugfixes (hidden services):
9927 - Improve hidden service robustness: when an attempt to connect to
9928 a hidden service ends, be willing to refetch its hidden service
9929 descriptors from each of the HSDir relays responsible for them
9930 immediately. Previously, we would not consider refetching the
9931 service's descriptors from each HSDir for 15 minutes after the last
9932 fetch, which was inconvenient if the hidden service was not running
9933 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
9934 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
9935 They used to check that the timestamp was within 30 minutes
9936 of their system clock, so they could cap the size of their
9937 replay-detection cache, but that approach unnecessarily refused
9938 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
9939 the v3 intro-point protocol (the first one which sent a timestamp
9940 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
9941 - When one of a hidden service's introduction points appears to be
9942 unreachable, stop trying it. Previously, we would keep trying
9943 to build circuits to the introduction point until we lost the
9944 descriptor, usually because the user gave up and restarted Tor.
9945 Fixes part of bug 3825.
9947 o Changes to default torrc file:
9948 - Stop listing "socksport 9050" in torrc.sample. We open a socks
9949 port on 9050 by default anyway, so this should not change anything
9951 - Stop mentioning the deprecated *ListenAddress options in
9952 torrc.sample. Fixes bug 5438.
9953 - Document unit of bandwidth-related options in sample torrc.
9955 - Fix broken URLs in the sample torrc file, and tell readers about
9956 the OutboundBindAddress, ExitPolicyRejectPrivate, and
9957 PublishServerDescriptor options. Addresses bug 4652.
9959 o Minor features (directory authorities):
9960 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
9961 change when the authority is deciding whether to accept a newly
9962 uploaded descriptor. Implements ticket 6423.
9963 - Directory authorities are now a little more lenient at accepting
9964 older router descriptors, or newer router descriptors that don't
9965 make big changes. This should help ameliorate past and future
9966 issues where routers think they have uploaded valid descriptors,
9967 but the authorities don't think so. Fix for ticket 2479.
9968 - Authority operators can now vote for all relays in a given
9969 set of countries to be BadDir/BadExit/Invalid/Rejected.
9970 - Provide two consensus parameters (FastFlagMinThreshold and
9971 FastFlagMaxThreshold) to control the range of allowable bandwidths
9972 for the Fast directory flag. These allow authorities to run
9973 experiments on appropriate requirements for being a "Fast" node.
9974 The AuthDirFastGuarantee config value still applies. Implements
9977 o Minor features (bridges / bridge authorities):
9978 - Make bridge SSL certificates a bit more stealthy by using random
9979 serial numbers, in the same fashion as OpenSSL when generating
9980 self-signed certificates. Implements ticket 4584.
9981 - Tag a bridge's descriptor as "never to be sent unencrypted".
9982 This shouldn't matter, since bridges don't open non-anonymous
9983 connections to the bridge authority and don't allow unencrypted
9984 directory connections from clients, but we might as well make
9985 sure. Closes bug 5139.
9986 - The Bridge Authority now writes statistics on how many bridge
9987 descriptors it gave out in total, and how many unique descriptors
9988 it gave out. It also lists how often the most and least commonly
9989 fetched descriptors were given out, as well as the median and
9990 25th/75th percentile. Implements tickets 4200 and 4294.
9992 o Minor features (IPv6):
9993 - Make the code that clients use to detect an address change be
9994 IPv6-aware, so that it won't fill clients' logs with error
9995 messages when trying to get the IPv4 address of an IPv6
9996 connection. Implements ticket 5537.
9997 - Relays now understand an IPv6 address when they get one from a
9998 directory server. Resolves ticket 4875.
10000 o Minor features (hidden services):
10001 - Expire old or over-used hidden service introduction points.
10002 Required by fix for bug 3460.
10003 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
10004 public key replay-detection cache from 60 minutes to 5 minutes. This
10005 replay-detection cache is now used only to detect multiple
10006 INTRODUCE2 cells specifying the same rendezvous point, so we can
10007 avoid launching multiple simultaneous attempts to connect to it.
10008 - When a hidden service's introduction point times out, consider
10009 trying it again during the next attempt to connect to the
10010 HS. Previously, we would not try it again unless a newly fetched
10011 descriptor contained it. Required by fixes for bugs 1297 and 3825.
10013 o Minor features (relays):
10014 - Relays now include a reason for regenerating their descriptors
10015 in an HTTP header when uploading to the authorities. This will
10016 make it easier to debug descriptor-upload issues in the future.
10017 - Turn on directory request statistics by default and include them in
10018 extra-info descriptors. Don't break if we have no GeoIP database.
10019 - Replace files in stats/ rather than appending to them. Now that we
10020 include statistics in extra-info descriptors, it makes no sense to
10021 keep old statistics forever. Implements ticket 2930.
10022 - Relays that set "ConnDirectionStatistics 1" write statistics on the
10023 bidirectional use of connections to disk every 24 hours.
10024 - Add a GeoIP file digest to the extra-info descriptor. Implements
10027 o Minor features (new config options):
10028 - New config option "DynamicDHGroups" (disabled by default) provides
10029 each bridge with a unique prime DH modulus to be used during
10030 SSL handshakes. This option attempts to help against censors
10031 who might use the Apache DH modulus as a static identifier for
10032 bridges. Addresses ticket 4548.
10033 - New config option "DisableDebuggerAttachment" (on by default)
10034 to prevent basic debugging attachment attempts by other processes.
10035 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
10036 - Ordinarily, Tor does not count traffic from private addresses (like
10037 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
10038 There is now a new option, CountPrivateBandwidth, to disable this
10039 behavior. Patch from Daniel Cagara.
10041 o Minor features (different behavior for old config options):
10042 - Allow MapAddress directives to specify matches against super-domains,
10043 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
10044 Implements issue 933.
10045 - Don't disable the DirPort when we cannot exceed our AccountingMax
10046 limit during this interval because the effective bandwidthrate is
10047 low enough. This is useful in a situation where AccountMax is only
10048 used as an additional safeguard or to provide statistics.
10049 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
10050 implements ticket 3439.
10051 - When configuring a large set of nodes in EntryNodes, and there are
10052 enough of them listed as Guard so that we don't need to consider
10053 the non-guard entries, prefer the ones listed with the Guard flag.
10054 - If you set the NumCPUs option to 0, Tor will now try to detect how
10055 many CPUs you have. This is the new default behavior.
10056 - The NodeFamily option -- which let you declare that you want to
10057 consider nodes to be part of a family whether they list themselves
10058 that way or not -- now allows IP address ranges and country codes.
10060 o Minor features (new command-line config behavior):
10061 - Slightly change behavior of "list" options (that is, config
10062 options that can appear more than once) when they appear both in
10063 torrc and on the command line. Previously, the command-line options
10064 would be appended to the ones from torrc. Now, the command-line
10065 options override the torrc options entirely. This new behavior
10066 allows the user to override list options (like exit policies and
10067 ports to listen on) from the command line, rather than simply
10068 appending to the list.
10069 - You can get the old (appending) command-line behavior for "list"
10070 options by prefixing the option name with a "+".
10071 - You can remove all the values for a "list" option from the command
10072 line without adding any new ones by prefixing the option name
10075 o Minor features (controller, new events):
10076 - Extend the control protocol to report flags that control a circuit's
10077 path selection in CIRC events and in replies to 'GETINFO
10078 circuit-status'. Implements part of ticket 2411.
10079 - Extend the control protocol to report the hidden service address
10080 and current state of a hidden-service-related circuit in CIRC
10081 events and in replies to 'GETINFO circuit-status'. Implements part
10083 - Include the creation time of a circuit in CIRC and CIRC2
10084 control-port events and the list produced by the 'GETINFO
10085 circuit-status' control-port command.
10086 - Add a new CONF_CHANGED event so that controllers can be notified
10087 of any configuration changes made by other controllers, or by the
10088 user. Implements ticket 1692.
10089 - Add a new SIGNAL event to the controller interface so that
10090 controllers can be notified when Tor handles a signal. Resolves
10091 issue 1955. Patch by John Brooks.
10093 o Minor features (controller, new getinfo options):
10094 - Expose our view of whether we have gone dormant to the controller,
10095 via a new "GETINFO dormant" value. Torbutton and other controllers
10096 can use this to avoid doing periodic requests through Tor while
10097 it's dormant (bug 4718). Resolves ticket 5954.
10098 - Add a new GETINFO option to get total bytes read and written. Patch
10099 from pipe, revised by atagar. Resolves ticket 2345.
10100 - Implement new GETINFO controller fields to provide information about
10101 the Tor process's pid, euid, username, and resource limits.
10103 o Minor features (controller, other):
10104 - Allow controllers to request an event notification whenever a
10105 circuit is cannibalized or its purpose is changed. Implements
10106 part of ticket 3457.
10107 - Use absolute path names when reporting the torrc filename in the
10108 control protocol, so a controller can more easily find the torrc
10109 file. Resolves bug 1101.
10110 - When reporting the path to the cookie file to the controller,
10111 give an absolute path. Resolves ticket 4881.
10113 o Minor features (log messages):
10114 - Add more information to a log statement that might help track down
10115 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
10116 non-IP address" messages (or any Bug messages, for that matter!),
10117 please let us know about it.
10118 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
10119 EntryNodes will have no effect. Resolves issue 2571.
10120 - Try to make the introductory warning message that Tor prints on
10121 startup more useful for actually finding help and information.
10122 Resolves ticket 2474.
10123 - When the system call to create a listener socket fails, log the
10124 error message explaining why. This may help diagnose bug 4027.
10126 o Minor features (other):
10127 - When we fail to initialize Libevent, retry with IOCP disabled so we
10128 don't need to turn on multi-threading support in Libevent, which in
10129 turn requires a working socketpair(). This is a workaround for bug
10130 4457, which affects Libevent versions from 2.0.1-alpha through
10132 - When starting as root and then changing our UID via the User
10133 control option, and we have a ControlSocket configured, make sure
10134 that the ControlSocket is owned by the same account that Tor will
10135 run under. Implements ticket 3421; fix by Jérémy Bobbio.
10136 - Accept attempts to include a password authenticator in the
10137 handshake, as supported by SOCKS5. This handles SOCKS clients that
10138 don't know how to omit a password when authenticating. Resolves
10140 - Check for and recover from inconsistency in the microdescriptor
10141 cache. This will make it harder for us to accidentally free a
10142 microdescriptor without removing it from the appropriate data
10143 structures. Fixes issue 3135; issue noted by "wanoskarnet".
10144 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
10146 o Minor bugfixes (code security):
10147 - Prevent a null-pointer dereference when receiving a data cell
10148 for a nonexistent stream when the circuit in question has an
10149 empty deliver window. We don't believe this is triggerable,
10150 since we don't currently allow deliver windows to become empty,
10151 but the logic is tricky enough that it's better to make the code
10152 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
10153 - Fix a (harmless) integer overflow in cell statistics reported by
10154 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
10155 - Fix our implementation of crypto_random_hostname() so it can't
10156 overflow on ridiculously large inputs. (No Tor version has ever
10157 provided this kind of bad inputs, but let's be correct in depth.)
10158 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
10159 - Add a (probably redundant) memory clear between iterations of
10160 the router status voting loop, to prevent future coding errors
10161 where data might leak between iterations of the loop. Resolves
10164 o Minor bugfixes (wrapper functions):
10165 - Abort if tor_vasprintf() fails in connection_printf_to_buf() (a
10166 utility function used in the control-port code). This shouldn't
10167 ever happen unless Tor is completely out of memory, but if it did
10168 happen and Tor somehow recovered from it, Tor could have sent a log
10169 message to a control port in the middle of a reply to a controller
10170 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
10171 - Fix some (not actually triggerable) buffer size checks in usage of
10172 tor_inet_ntop(). Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
10174 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
10175 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
10176 - Enforce correct return behavior of tor_vsscanf() when the '%%'
10177 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
10178 - Make our replacement implementation of strtok_r() compatible with
10179 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
10180 bugfix on 0.2.2.1-alpha.
10181 - Find more places in the code that should have been testing for
10182 invalid sockets using the SOCKET_OK macro. Required for a fix
10183 for bug 4533. Bugfix on 0.2.2.28-beta.
10185 o Minor bugfixes (code correctness):
10186 - Check return value of fputs() when writing authority certificate
10187 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
10188 - When building Tor on Windows with -DUNICODE (not default), ensure
10189 that error messages, filenames, and DNS server names are always
10190 NUL-terminated when we convert them to a single-byte encoding.
10191 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
10192 - Fix a memory leak when trying to launch a DNS request when the
10193 nameservers are unconfigurable. Fixes bug 5916; bugfix on Tor
10195 - Correct file sizes when reading binary files on Cygwin, to avoid
10196 a bug where Tor would fail to read its state file. Fixes bug 6844;
10197 bugfix on 0.1.2.7-alpha.
10198 - Make sure to set *socket_error in all error cases in
10199 connection_connect(), so it can't produce a warning about
10200 errno being zero from errno_to_orconn_end_reason(). Bugfix on
10201 0.2.1.1-alpha; resolves ticket 6028.
10202 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
10203 bug 4532; found by "troll_un".
10205 o Minor bugfixes (clients):
10206 - Allow one-hop directory-fetching circuits the full "circuit build
10207 timeout" period, rather than just half of it, before failing them
10208 and marking the relay down. This fix should help reduce cases where
10209 clients declare relays (or worse, bridges) unreachable because
10210 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
10211 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
10213 - Ensure we don't cannibalize circuits that are longer than three hops
10214 already, so we don't end up making circuits with 5 or more
10215 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
10216 0.1.0.1-rc which introduced cannibalization.
10218 o Minor bugfixes (relays):
10219 - Don't publish a new relay descriptor when we reload our onion key,
10220 unless the onion key has actually changed. Fixes bug 3263 and
10221 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
10222 - When relays refuse a "create" cell because their queue of pending
10223 create cells is too big (typically because their cpu can't keep up
10224 with the arrival rate), send back reason "resource limit" rather
10225 than reason "internal", so network measurement scripts can get a
10226 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
10227 - Exit nodes don't need to fetch certificates for authorities that
10228 they don't recognize; only directory authorities, bridges,
10229 and caches need to do that. Fixes part of bug 2297; bugfix on
10232 o Minor bugfixes (directory authority / mirrors):
10233 - Avoid O(n^2) performance characteristics when parsing a large
10234 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
10235 - Authorities no longer include any router in their microdescriptor
10236 consensuses for which they couldn't generate or agree on a
10237 microdescriptor. Fixes the second piece of bug 6404; fix on
10239 - When checking for requested signatures on the latest consensus
10240 before serving it to a client, make sure to check the right
10241 consensus flavor. Bugfix on 0.2.2.6-alpha.
10242 - Fix an edge case where TestingTorNetwork is set but the authorities
10243 and relays all have an uptime of zero, so the private Tor network
10244 could briefly lack support for hidden services. Fixes bug 3886;
10245 bugfix on 0.2.2.18-alpha.
10246 - Directory caches no longer refuse to clean out descriptors because
10247 of missing v2 networkstatus documents, unless they're configured
10248 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
10249 0.2.2.26-beta. Patch by Daniel Bryg.
10250 - Don't serve or accept v2 hidden service descriptors over a relay's
10251 DirPort. It's never correct to do so, and disabling it might
10252 make it more annoying to exploit any bugs that turn up in the
10253 descriptor-parsing code. Fixes bug 7149.
10255 o Minor bugfixes (hidden services, client-side):
10256 - Assert that hidden-service-related operations are not performed
10257 using single-hop circuits. Previously, Tor would assert that
10258 client-side streams are not attached to single-hop circuits,
10259 but not that other sensitive operations on the client and service
10260 side are not performed using single-hop circuits. Fixes bug 3332;
10262 - Avoid undefined behavior when parsing the list of supported
10263 rendezvous/introduction protocols in a hidden service descriptor.
10264 Previously, Tor would have confused (as-yet-unused) protocol version
10265 numbers greater than 32 with lower ones on many platforms. Fixes
10266 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
10267 - Don't close hidden service client circuits which have almost
10268 finished connecting to their destination when they reach
10269 the normal circuit-build timeout. Previously, we would close
10270 introduction circuits which are waiting for an acknowledgement
10271 from the introduction point, and rendezvous circuits which have
10272 been specified in an INTRODUCE1 cell sent to a hidden service,
10273 after the normal CBT. Now, we mark them as 'timed out', and launch
10274 another rendezvous attempt in parallel. This behavior change can
10275 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
10276 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
10278 o Minor bugfixes (hidden services, service-side):
10279 - Don't close hidden-service-side rendezvous circuits when they
10280 reach the normal circuit-build timeout. This behavior change can
10281 be disabled using the new
10282 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
10283 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
10284 - Don't launch more than 10 service-side introduction-point circuits
10285 for a hidden service in five minutes. Previously, we would consider
10286 launching more introduction-point circuits if at least one second
10287 had passed without any introduction-point circuits failing. Fixes
10288 bug 4607; bugfix on 0.0.7pre1.
10290 o Minor bugfixes (config option behavior):
10291 - If the user tries to set MyFamily on a bridge, refuse to
10292 do so, and warn about the security implications. Fixes bug 4657;
10293 bugfix on 0.2.0.3-alpha.
10294 - The "--quiet" and "--hush" options now apply not only to Tor's
10295 behavior before logs are configured, but also to Tor's behavior in
10296 the absence of configured logs. Fixes bug 3550; bugfix on
10298 - Change the AllowDotExit rules so they should actually work.
10299 We now enforce AllowDotExit only immediately after receiving an
10300 address via SOCKS or DNSPort: other sources are free to provide
10301 .exit addresses after the resolution occurs. Fixes bug 3940;
10302 bugfix on 0.2.2.1-alpha.
10303 - Make "LearnCircuitBuildTimeout 0" work more reliably. Specifically,
10304 don't depend on the consensus parameters or compute adaptive
10305 timeouts when it is disabled. Fixes bug 5049; bugfix on
10307 - After we pick a directory mirror, we would refuse to use it if
10308 it's in our ExcludeExitNodes list, resulting in mysterious failures
10309 to bootstrap for people who just wanted to avoid exiting from
10310 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
10311 - When told to add a bridge with the same digest as a preexisting
10312 bridge but a different addr:port, change the addr:port as
10313 requested. Previously we would not notice the change. Fixes half
10314 of bug 5603; fix on 0.2.2.26-beta.
10316 o Minor bugfixes (controller):
10317 - Allow manual 'authenticate' commands to the controller interface
10318 from netcat (nc) as well as telnet. We were rejecting them because
10319 they didn't come with the expected whitespace at the end of the
10320 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
10321 - Report a real bootstrap problem to the controller on router
10322 identity mismatch. Previously we just said "foo", which probably
10323 made a lot of sense at the time. Fixes bug 4169; bugfix on
10325 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
10326 option is set to 0 (which Vidalia version 0.2.16 now does when
10327 a SAVECONF attempt fails), perform other actions that SIGHUP
10328 usually causes (like reopening the logs). Fixes bug 5095; bugfix
10330 - Correctly handle checking the permissions on the parent
10331 directory of a control socket in the root directory. Bug found
10332 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
10334 - End AUTHCHALLENGE error messages (in the control protocol) with
10335 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36.
10337 o Minor bugfixes (network reading/writing):
10338 - Disable writing on marked-for-close connections when they are
10339 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
10340 bug 5263; bugfix on 0.0.2pre13, where we first added a special
10341 case for flushing marked connections.
10342 - Make sure that there are no unhandled pending TLS errors before
10343 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
10344 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
10345 Bugfix on 0.1.0.5-rc; fixes bug 4528.
10346 - Detect SSL handshake even when the initial attempt to write the
10347 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
10348 - If the client fails to set a reasonable set of ciphersuites
10349 during its v2 handshake renegotiation, allow the renegotiation to
10350 continue nevertheless (i.e. send all the required certificates).
10351 Fixes bug 4591; bugfix on 0.2.0.20-rc.
10353 o Minor bugfixes (other):
10354 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
10355 resource exhaustion, so that clients can adjust their load to
10356 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
10357 started using END_STREAM_REASON_RESOURCELIMIT.
10358 - Don't check for whether the address we're using for outbound
10359 connections has changed until after the outbound connection has
10360 completed. On Windows, getsockname() doesn't succeed until the
10361 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
10362 - Don't hold a Windows file handle open for every file mapping;
10363 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
10365 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
10366 bugfix on 0.2.1.10-alpha.
10367 - If we fail to write a microdescriptor to the disk cache, do not
10368 continue replacing the old microdescriptor file. Fixes bug 2954;
10369 bugfix on 0.2.2.6-alpha.
10371 o Minor bugfixes (log messages, path selection):
10372 - Downgrade "set buildtimeout to low value" messages to "info"
10373 severity; they were never an actual problem, there was never
10374 anything reasonable to do about them, and they tended to spam logs
10375 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
10376 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
10377 more information to it, so that we can track it down in case it
10378 returns again. Mitigates bug 5235.
10379 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
10380 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
10381 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
10382 - Issue a log message if a guard completes less than 40% of your
10383 circuits. Threshold is configurable by torrc option
10384 PathBiasNoticeRate and consensus parameter pb_noticepct. There is
10385 additional, off-by-default code to disable guards which fail too
10386 many circuits. Addresses ticket 5458.
10388 o Minor bugfixes (log messages, client):
10389 - Downgrade "Got a certificate, but we already have it" log messages
10390 from warning to info, except when we're a dirauth. Fixes bug 5238;
10391 bugfix on 0.2.1.7-alpha.
10392 - Fix the log message describing how we work around discovering
10393 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
10394 4837; bugfix on 0.2.2.9-alpha.
10395 - When logging about a disallowed .exit name, do not also call it
10396 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
10397 - Fix a log message suggesting that people contact a non-existent
10398 email address. Fixes bug 3448.
10399 - Rephrase the log message emitted if the TestSocks check is
10400 successful. Patch from Fabian Keil; fixes bug 4094.
10401 - Log (at debug level) whenever a circuit's purpose is changed.
10402 - Log SSL state transitions at log level DEBUG, log domain
10403 HANDSHAKE. This can be useful for debugging censorship events.
10404 Implements ticket 3264.
10405 - We now log which torrc file we're using on startup. Implements
10407 - Rate-limit log messages when asked to connect anonymously to
10408 a private address. When these hit, they tended to hit fast and
10409 often. Also, don't bother trying to connect to addresses that we
10410 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
10411 reply makes us think we have been lied to, even when the address the
10412 client tried to connect to was "localhost." Resolves ticket 2822.
10414 o Minor bugfixes (log messages, non-client):
10415 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
10416 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
10417 - Don't log that we have "decided to publish new relay descriptor"
10418 unless we are actually publishing a descriptor. Fixes bug 3942;
10419 bugfix on 0.2.2.28-beta.
10420 - Log which authority we're missing votes from when we go to fetch
10421 them from the other auths.
10422 - Replace "Sending publish request" log messages with "Launching
10423 upload", so that they no longer confusingly imply that we're
10424 sending something to a directory we might not even be connected
10425 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
10426 - Warn when Tor is configured to use accounting in a way that can
10427 link a hidden service to some other hidden service or public
10428 address. Resolves ticket 6490.
10429 - Fix a minor formatting issue in one of tor-gencert's error messages.
10433 - Update to the latest version of the tinytest unit testing framework.
10434 This includes a couple of bugfixes that can be relevant for
10435 running forked unit tests on Windows, and removes all reserved
10437 - Avoid a false positive in the util/threads unit test by increasing
10438 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
10439 - Make it possible to set the TestingTorNetwork configuration
10440 option using AlternateDirAuthority and AlternateBridgeAuthority
10441 as an alternative to setting DirServer. Addresses ticket 6377.
10442 - Add a unit test for the environment_variable_names_equal() function.
10443 - A wide variety of new unit tests by Esteban Manchado Velázquez.
10444 - Numerous new unit tests for functions in util.c and address.c by
10446 - The long-disabled benchmark tests are now split into their own
10447 ./src/test/bench binary.
10448 - The benchmark tests can now use more accurate timers than
10449 gettimeofday() when such timers are available.
10450 - Use tt_assert(), not tor_assert(), for checking for test failures.
10451 This makes the unit tests more able to go on in the event that
10454 o Build improvements:
10455 - Use the dead_strip option when building Tor on OS X. This reduces
10456 binary size by almost 19% when linking openssl and libevent
10457 statically, which we do for Tor Browser Bundle.
10458 - Provide a better error message about possible OSX Asciidoc failure
10459 reasons. Fixes bug 6436.
10460 - Detect attempts to build Tor on (as yet hypothetical) versions
10461 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
10462 fix for bug 4533. Bugfix on 0.2.2.28-beta.
10463 - On Windows, we now define the _WIN32_WINNT macros only if they
10464 are not already defined. This lets the person building Tor decide,
10465 if they want, to require a later version of Windows.
10466 - Our autogen.sh script now uses autoreconf to launch autoconf,
10467 automake, and so on. This is more robust against some of the failure
10468 modes associated with running the autotools pieces on their own.
10469 - Running "make version" now displays the version of Tor that
10470 we're about to build. Idea from katmagic; resolves issue 4400.
10471 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
10472 on 0.2.2.4-alpha; fixes bug 3427.
10473 - New --enable-static-tor configure option for building Tor as
10474 statically as possible. Idea, general hackery and thoughts from
10475 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
10477 - Limited, experimental support for building with nmake and MSVC.
10479 o Build requirements:
10480 - Building Tor with bufferevent support now requires Libevent
10481 2.0.13-stable or later. Previous versions of Libevent had bugs in
10482 SSL-related bufferevents and related issues that would make Tor
10483 work badly with bufferevents. Requiring 2.0.13-stable also allows
10484 Tor with bufferevents to take advantage of Libevent APIs
10485 introduced after 2.0.8-rc.
10486 - Our build system requires automake 1.6 or later to create the
10487 Makefile.in files. Previously, you could have used 1.4.
10488 This only affects developers and people building Tor from git;
10489 people who build Tor from the source distribution without changing
10490 the Makefile.am files should be fine.
10491 - Detect when we try to build on a platform that doesn't define
10492 AF_UNSPEC to 0. We don't work there, so refuse to compile.
10494 o Build fixes (compile/link):
10495 - Format more doubles with %f, not %lf. Patch from grarpamp to make
10496 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
10498 - When building with --enable-static-tor on OpenBSD, do not
10499 erroneously attempt to link -lrt. Fixes bug 5103.
10500 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
10501 that IPv6 stuff will compile on MSVC, and compilation issues
10502 will be easier to track down. Fixes bug 5861.
10503 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
10504 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
10505 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
10506 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
10508 o Build fixes (other):
10509 - Use the _WIN32 macro throughout our code to detect Windows.
10510 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
10512 - Properly handle the case where the build-tree is not the same
10513 as the source tree when generating src/common/common_sha1.i,
10514 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
10515 bugfix on 0.2.0.1-alpha.
10516 - During configure, search for library containing cos function as
10517 libm lives in libcore on some platforms (BeOS/Haiku). Linking
10518 against libm was hard-coded before. Fixes the first part of bug
10519 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
10521 - Prevent a false positive from the check-spaces script, by disabling
10522 the "whitespace between function name and (" check for functions
10525 o Packaging (RPM) changes:
10526 - Update our default RPM spec files to work with mock and rpmbuild
10527 on RHEL/Fedora. They have an updated set of dependencies and
10528 conflicts, a fix for an ancient typo when creating the "_tor"
10529 user, and better instructions. Thanks to Ondrej Mikle for the
10530 patch series. Fixes bug 6043.
10531 - On OpenSUSE, create the /var/run/tor directory on startup if it
10532 is not already created. Patch from Andreas Stieger. Fixes bug 2573.
10534 o Code refactoring (safety):
10535 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
10536 10 lines. Also, don't nest them. Doing so in the past has
10537 led to hard-to-debug code. The new style is to use the
10538 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
10539 - Use macros to indicate OpenSSL versions, so we don't need to worry
10540 about accidental hexadecimal bit shifts.
10541 - Use tor_sscanf() in place of scanf() in more places through the
10542 code. This makes us a little more locale-independent, and
10543 should help shut up code-analysis tools that can't tell
10544 a safe sscanf string from a dangerous one.
10545 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
10546 - Use the smartlist_add_asprintf() alias more consistently.
10548 o Code refactoring (consolidate):
10549 - A major revision to our internal node-selecting and listing logic.
10550 Tor already had at least two major ways to look at the question of
10551 "which Tor servers do we know about": a list of router descriptors,
10552 and a list of entries in the current consensus. With
10553 microdescriptors, we're adding a third. Having so many systems
10554 without an abstraction layer over them was hurting the codebase.
10555 Now, we have a new "node_t" abstraction that presents a consistent
10556 interface to a client's view of a Tor node, and holds (nearly) all
10557 of the mutable state formerly in routerinfo_t and routerstatus_t.
10558 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
10559 Libevent's notion of cached time when possible.
10560 - Remove duplicate code for invoking getrlimit() from control.c.
10561 - Use OpenSSL's built-in SSL_state_string_long() instead of our
10562 own homebrewed ssl_state_to_string() replacement. Patch from
10563 Emile Snyder. Fixes bug 4653.
10564 - Change the symmetric cipher interface so that creating and
10565 initializing a stream cipher are no longer separate functions.
10567 o Code refactoring (separate):
10568 - Make a new "entry connection" struct as an internal subtype of "edge
10569 connection", to simplify the code and make exit connections smaller.
10570 - Split connection_about_to_close() into separate functions for each
10572 - Rewrite the listener-selection logic so that parsing which ports
10573 we want to listen on is now separate from binding to the ports
10576 o Code refactoring (name changes):
10577 - Rename a handful of old identifiers, mostly related to crypto
10578 structures and crypto functions. By convention, our "create an
10579 object" functions are called "type_new()", our "free an object"
10580 functions are called "type_free()", and our types indicate that
10581 they are types only with a final "_t". But a handful of older
10582 types and functions broke these rules, with function names like
10583 "type_create" or "subsystem_op_type", or with type names like
10585 - Rename Tor functions that turn strings into addresses, so that
10586 "parse" indicates that no hostname resolution occurs, and
10587 "lookup" indicates that hostname resolution may occur. This
10588 should help prevent mistakes in the future. Fixes bug 3512.
10589 - Use the name "CERTS" consistently to refer to the new cell type;
10590 we were calling it CERT in some places and CERTS in others.
10591 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
10592 invalid value, rather than just -1.
10593 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
10594 can pick them up when the tests aren't disabled. Bugfix on
10595 0.2.2.4-alpha which introduced tinytest.
10597 o Code refactoring (other):
10598 - Defensively refactor rend_mid_rendezvous() so that protocol
10599 violations and length checks happen in the beginning. Fixes
10601 - Remove the pure attribute from all functions that used it
10602 previously. In many cases we assigned it incorrectly, because the
10603 functions might assert or call impure functions, and we don't have
10604 evidence that keeping the pure attribute is worthwhile. Implements
10605 changes suggested in ticket 4421.
10606 - Move the replay-detection cache for the RSA-encrypted parts of
10607 INTRODUCE2 cells to the introduction point data structures.
10608 Previously, we would use one replay-detection cache per hidden
10609 service. Required by fix for bug 3460.
10610 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
10611 no longer link against Libevent: they never used it, but
10612 our library structure used to force them to link it.
10614 o Removed features and files:
10615 - Remove all internal support for unpadded RSA. We never used it, and
10616 it would be a bad idea to start.
10617 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
10619 - Remove some redundant #include directives throughout the code.
10620 Patch from Andrea Gelmini.
10621 - Remove some old code to remember statistics about which descriptors
10622 we've served as a directory mirror. The feature wasn't used and
10623 is outdated now that microdescriptors are around.
10624 - Remove some old code to work around even older versions of Tor that
10625 used forked processes to handle DNS requests. Such versions of Tor
10626 are no longer in use as relays.
10627 - The "torify" script no longer supports the "tsocks" socksifier
10628 tool, since tsocks doesn't support DNS and UDP right for Tor.
10629 Everyone should be using torsocks instead. Fixes bugs 3530 and
10630 5180. Based on a patch by "ugh".
10631 - Remove the torrc.bridge file: we don't use it for anything, and
10632 it had become badly desynchronized from torrc.sample. Resolves
10636 - Begin a doc/state-contents.txt file to explain the contents of
10637 the Tor state file. Fixes bug 2987.
10638 - Clarify the documentation for the Alternate*Authority options.
10640 - Document the --defaults-torrc option, and the new semantics for
10641 overriding, extending, and clearing lists of options. Closes
10643 - Add missing man page documentation for consensus and microdesc
10644 files. Resolves ticket 6732.
10645 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
10647 o Documentation fixes:
10648 - Improve the manual's documentation for the NT Service command-line
10649 options. Addresses ticket 3964.
10650 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
10651 - Document the changes to the ORPort and DirPort options, and the
10652 fact that {OR/Dir}ListenAddress is now unnecessary (and
10653 therefore deprecated). Resolves ticket 5597.
10654 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
10655 - Clarify that hidden services are TCP only. Fixes bug 6024.
10658 Changes in version 0.2.2.39 - 2012-09-11
10659 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
10663 - Fix an assertion failure in tor_timegm() that could be triggered
10664 by a badly formatted directory object. Bug found by fuzzing with
10665 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
10666 - Do not crash when comparing an address with port value 0 to an
10667 address policy. This bug could have been used to cause a remote
10668 assertion failure by or against directory authorities, or to
10669 allow some applications to crash clients. Fixes bug 6690; bugfix
10673 Changes in version 0.2.2.38 - 2012-08-12
10674 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
10675 attack that could in theory leak path information.
10678 - Avoid an uninitialized memory read when reading a vote or consensus
10679 document that has an unrecognized flavor name. This read could
10680 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
10681 - Try to leak less information about what relays a client is
10682 choosing to a side-channel attacker. Previously, a Tor client would
10683 stop iterating through the list of available relays as soon as it
10684 had chosen one, thus finishing a little earlier when it picked
10685 a router earlier in the list. If an attacker can recover this
10686 timing information (nontrivial but not proven to be impossible),
10687 they could learn some coarse-grained information about which relays
10688 a client was picking (middle nodes in particular are likelier to
10689 be affected than exits). The timing attack might be mitigated by
10690 other factors (see bug 6537 for some discussion), but it's best
10691 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
10694 Changes in version 0.2.2.37 - 2012-06-06
10695 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
10696 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
10700 - Work around a bug in OpenSSL that broke renegotiation with TLS
10701 1.1 and TLS 1.2. Without this workaround, all attempts to speak
10702 the v2 Tor connection protocol when both sides were using OpenSSL
10703 1.0.1 would fail. Resolves ticket 6033.
10704 - When waiting for a client to renegotiate, don't allow it to add
10705 any bytes to the input buffer. This fixes a potential DoS issue.
10706 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
10707 - Fix an edge case where if we fetch or publish a hidden service
10708 descriptor, we might build a 4-hop circuit and then use that circuit
10709 for exiting afterwards -- even if the new last hop doesn't obey our
10710 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
10713 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
10714 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
10717 - Tell GCC and Clang to check for any errors in format strings passed
10718 to the tor_v*(print|scan)f functions.
10721 Changes in version 0.2.2.36 - 2012-05-24
10722 Tor 0.2.2.36 updates the addresses for two of the eight directory
10723 authorities, fixes some potential anonymity and security issues,
10724 and fixes several crash bugs.
10726 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
10727 known flaws, and nobody should be using them. You should upgrade. If
10728 you're using a Linux or BSD and its packages are obsolete, stop using
10729 those packages and upgrade anyway.
10731 o Directory authority changes:
10732 - Change IP address for maatuska (v3 directory authority).
10733 - Change IP address for ides (v3 directory authority), and rename
10737 - When building or running with any version of OpenSSL earlier
10738 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
10739 versions have a bug (CVE-2011-4576) in which their block cipher
10740 padding includes uninitialized data, potentially leaking sensitive
10741 information to any peer with whom they make a SSLv3 connection. Tor
10742 does not use SSL v3 by default, but a hostile client or server
10743 could force an SSLv3 connection in order to gain information that
10744 they shouldn't have been able to get. The best solution here is to
10745 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
10746 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
10747 to make sure that the bug can't happen.
10748 - Never use a bridge or a controller-supplied node as an exit, even
10749 if its exit policy allows it. Found by wanoskarnet. Fixes bug
10750 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
10751 and 0.2.0.3-alpha (for bridge-purpose descriptors).
10752 - Only build circuits if we have a sufficient threshold of the total
10753 descriptors that are marked in the consensus with the "Exit"
10754 flag. This mitigates an attack proposed by wanoskarnet, in which
10755 all of a client's bridges collude to restrict the exit nodes that
10756 the client knows about. Fixes bug 5343.
10757 - Provide controllers with a safer way to implement the cookie
10758 authentication mechanism. With the old method, if another locally
10759 running program could convince a controller that it was the Tor
10760 process, then that program could trick the controller into telling
10761 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
10762 authentication method uses a challenge-response approach to prevent
10763 this attack. Fixes bug 5185; implements proposal 193.
10766 - Avoid logging uninitialized data when unable to decode a hidden
10767 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
10768 - Avoid a client-side assertion failure when receiving an INTRODUCE2
10769 cell on a general purpose circuit. Fixes bug 5644; bugfix on
10771 - Fix builds when the path to sed, openssl, or sha1sum contains
10772 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
10774 - Correct our replacements for the timeradd() and timersub() functions
10775 on platforms that lack them (for example, Windows). The timersub()
10776 function is used when expiring circuits, while timeradd() is
10777 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
10778 bugfix on 0.2.2.24-alpha.
10779 - Fix the SOCKET_OK test that we use to tell when socket
10780 creation fails so that it works on Win64. Fixes part of bug 4533;
10781 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
10784 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
10785 Fixes bug 5346; bugfix on 0.0.8pre3.
10786 - Make our number-parsing functions always treat too-large values
10787 as an error, even when those values exceed the width of the
10788 underlying type. Previously, if the caller provided these
10789 functions with minima or maxima set to the extreme values of the
10790 underlying integer type, these functions would return those
10791 values on overflow rather than treating overflow as an error.
10792 Fixes part of bug 5786; bugfix on 0.0.9.
10793 - Older Linux kernels erroneously respond to strange nmap behavior
10794 by having accept() return successfully with a zero-length
10795 socket. When this happens, just close the connection. Previously,
10796 we would try harder to learn the remote address: but there was
10797 no such remote address to learn, and our method for trying to
10798 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
10799 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
10800 - Correct parsing of certain date types in parse_http_time().
10801 Without this patch, If-Modified-Since would behave
10802 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
10803 Esteban Manchado Velázques.
10804 - Change the BridgePassword feature (part of the "bridge community"
10805 design, which is not yet implemented) to use a time-independent
10806 comparison. The old behavior might have allowed an adversary
10807 to use timing to guess the BridgePassword value. Fixes bug 5543;
10808 bugfix on 0.2.0.14-alpha.
10809 - Detect and reject certain misformed escape sequences in
10810 configuration values. Previously, these values would cause us
10811 to crash if received in a torrc file or over an authenticated
10812 control port. Bug found by Esteban Manchado Velázquez, and
10813 independently by Robert Connolly from Matta Consulting who further
10814 noted that it allows a post-authentication heap overflow. Patch
10815 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
10816 bugfix on 0.2.0.16-alpha.
10817 - Fix a compile warning when using the --enable-openbsd-malloc
10818 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
10819 - During configure, detect when we're building with clang version
10820 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
10821 CFLAGS. clang doesn't support them yet.
10822 - When sending an HTTP/1.1 proxy request, include a Host header.
10823 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
10824 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
10825 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
10826 - If we hit the error case where routerlist_insert() replaces an
10827 existing (old) server descriptor, make sure to remove that
10828 server descriptor from the old_routers list. Fix related to bug
10829 1776. Bugfix on 0.2.2.18-alpha.
10831 o Minor bugfixes (documentation and log messages):
10832 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
10833 Fixes bug 4856; bugfix on Tor 0.0.6.
10834 - Update "ClientOnly" man page entry to explain that there isn't
10835 really any point to messing with it. Resolves ticket 5005.
10836 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
10837 directory authority option (introduced in Tor 0.2.2.34).
10838 - Downgrade the "We're missing a certificate" message from notice
10839 to info: people kept mistaking it for a real problem, whereas it
10840 is seldom the problem even when we are failing to bootstrap. Fixes
10841 bug 5067; bugfix on 0.2.0.10-alpha.
10842 - Correctly spell "connect" in a log message on failure to create a
10843 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
10844 - Clarify the behavior of MaxCircuitDirtiness with hidden service
10845 circuits. Fixes issue 5259.
10848 - Directory authorities now reject versions of Tor older than
10849 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
10850 inclusive. These versions accounted for only a small fraction of
10851 the Tor network, and have numerous known security issues. Resolves
10853 - Update to the May 1 2012 Maxmind GeoLite Country database.
10856 - When sending or relaying a RELAY_EARLY cell, we used to convert
10857 it to a RELAY cell if the connection was using the v1 link
10858 protocol. This was a workaround for older versions of Tor, which
10859 didn't handle RELAY_EARLY cells properly. Now that all supported
10860 versions can handle RELAY_EARLY cells, and now that we're enforcing
10861 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
10862 remove this workaround. Addresses bug 4786.
10865 Changes in version 0.2.2.35 - 2011-12-16
10866 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
10867 buffers code. Absolutely everybody should upgrade.
10869 The bug relied on an incorrect calculation when making data continuous
10870 in one of our IO buffers, if the first chunk of the buffer was
10871 misaligned by just the wrong amount. The miscalculation would allow an
10872 attacker to overflow a piece of heap-allocated memory. To mount this
10873 attack, the attacker would need to either open a SOCKS connection to
10874 Tor's SocksPort (usually restricted to localhost), or target a Tor
10875 instance configured to make its connections through a SOCKS proxy
10876 (which Tor does not do by default).
10878 Good security practice requires that all heap-overflow bugs should be
10879 presumed to be exploitable until proven otherwise, so we are treating
10880 this as a potential code execution attack. Please upgrade immediately!
10881 This bug does not affect bufferevents-based builds of Tor. Special
10882 thanks to "Vektor" for reporting this issue to us!
10884 Tor 0.2.2.35 also fixes several bugs in previous versions, including
10885 crash bugs for unusual configurations, and a long-term bug that
10886 would prevent Tor from starting on Windows machines with draconian
10889 With this release, we remind everyone that 0.2.0.x has reached its
10890 formal end-of-life. Those Tor versions have many known flaws, and
10891 nobody should be using them. You should upgrade -- ideally to the
10892 0.2.2.x series. If you're using a Linux or BSD and its packages are
10893 obsolete, stop using those packages and upgrade anyway.
10895 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
10896 longer receive support after some time in early 2012.
10899 - Fix a heap overflow bug that could occur when trying to pull
10900 data into the first chunk of a buffer, when that chunk had
10901 already had some data drained from it. Fixes CVE-2011-2778;
10902 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
10903 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
10904 that it doesn't attempt to allocate a socketpair. This could cause
10905 some problems on Windows systems with overzealous firewalls. Fix for
10906 bug 4457; workaround for Libevent versions 2.0.1-alpha through
10908 - If we mark an OR connection for close based on a cell we process,
10909 don't process any further cells on it. We already avoid further
10910 reads on marked-for-close connections, but now we also discard the
10911 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
10912 which was the first version where we might mark a connection for
10913 close based on processing a cell on it.
10914 - Correctly sanity-check that we don't underflow on a memory
10915 allocation (and then assert) for hidden service introduction
10916 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
10917 bugfix on 0.2.1.5-alpha.
10918 - Fix a memory leak when we check whether a hidden service
10919 descriptor has any usable introduction points left. Fixes bug
10920 4424. Bugfix on 0.2.2.25-alpha.
10921 - Don't crash when we're running as a relay and don't have a GeoIP
10922 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
10923 we've had in the 0.2.3.x branch already.
10924 - When running as a client, do not print a misleading (and plain
10925 wrong) log message that we're collecting "directory request"
10926 statistics: clients don't collect statistics. Also don't create a
10927 useless (because empty) stats file in the stats/ directory. Fixes
10928 bug 4353; bugfix on 0.2.2.34.
10931 - Detect failure to initialize Libevent. This fix provides better
10932 detection for future instances of bug 4457.
10933 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
10934 function. This was eating up hideously large amounts of time on some
10935 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
10936 - Resolve an integer overflow bug in smartlist_ensure_capacity().
10937 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
10939 - Don't warn about unused log_mutex in log.c when building with
10940 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
10941 0.1.0.6-rc which introduced --disable-threads.
10942 - When configuring, starting, or stopping an NT service, stop
10943 immediately after the service configuration attempt has succeeded
10944 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
10945 - When sending a NETINFO cell, include the original address
10946 received for the other side, not its canonical address. Found
10947 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
10948 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
10949 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
10950 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
10951 occurred when a client tried to fetch a descriptor for a bridge
10952 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
10953 - Backport fixes for a pair of compilation warnings on Windows.
10954 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
10955 - If we had ever tried to call tor_addr_to_str on an address of
10956 unknown type, we would have done a strdup on an uninitialized
10957 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
10958 Reported by "troll_un".
10959 - Correctly detect and handle transient lookup failures from
10960 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
10961 Reported by "troll_un".
10962 - Fix null-pointer access that could occur if TLS allocation failed.
10963 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
10964 - Use tor_socket_t type for listener argument to accept(). Fixes bug
10965 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
10968 - Add two new config options for directory authorities:
10969 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
10970 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
10971 that is always sufficient to satisfy the bandwidth requirement for
10972 the Guard flag. Now it will be easier for researchers to simulate
10973 Tor networks with different values. Resolves ticket 4484.
10974 - When Tor ignores a hidden service specified in its configuration,
10975 include the hidden service's directory in the warning message.
10976 Previously, we would only tell the user that some hidden service
10977 was ignored. Bugfix on 0.0.6; fixes bug 4426.
10978 - Update to the December 6 2011 Maxmind GeoLite Country database.
10980 o Packaging changes:
10981 - Make it easier to automate expert package builds on Windows,
10982 by removing an absolute path from makensis.exe command.
10985 Changes in version 0.2.1.32 - 2011-12-16
10986 Tor 0.2.1.32 backports important security and privacy fixes for
10987 oldstable. This release is intended only for package maintainers and
10988 others who cannot use the 0.2.2 stable series. All others should be
10989 using Tor 0.2.2.x or newer.
10991 The Tor 0.2.1.x series will reach formal end-of-life some time in
10992 early 2012; we will stop releasing patches for it then.
10994 o Major bugfixes (also included in 0.2.2.x):
10995 - Correctly sanity-check that we don't underflow on a memory
10996 allocation (and then assert) for hidden service introduction
10997 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
10998 bugfix on 0.2.1.5-alpha.
10999 - Fix a heap overflow bug that could occur when trying to pull
11000 data into the first chunk of a buffer, when that chunk had
11001 already had some data drained from it. Fixes CVE-2011-2778;
11002 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
11005 - Update to the December 6 2011 Maxmind GeoLite Country database.
11008 Changes in version 0.2.2.34 - 2011-10-26
11009 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
11010 can deanonymize Tor users. Everybody should upgrade.
11012 The attack relies on four components: 1) Clients reuse their TLS cert
11013 when talking to different relays, so relays can recognize a user by
11014 the identity key in her cert. 2) An attacker who knows the client's
11015 identity key can probe each guard relay to see if that identity key
11016 is connected to that guard relay right now. 3) A variety of active
11017 attacks in the literature (starting from "Low-Cost Traffic Analysis
11018 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
11019 discover the guard relays that a Tor user visiting the website is using.
11020 4) Clients typically pick three guards at random, so the set of guards
11021 for a given user could well be a unique fingerprint for her. This
11022 release fixes components #1 and #2, which is enough to block the attack;
11023 the other two remain as open research problems. Special thanks to
11024 "frosty_un" for reporting the issue to us!
11026 Clients should upgrade so they are no longer recognizable by the TLS
11027 certs they present. Relays should upgrade so they no longer allow a
11028 remote attacker to probe them to test whether unpatched clients are
11029 currently connected to them.
11031 This release also fixes several vulnerabilities that allow an attacker
11032 to enumerate bridge relays. Some bridge enumeration attacks still
11033 remain; see for example proposal 188.
11035 o Privacy/anonymity fixes (clients):
11036 - Clients and bridges no longer send TLS certificate chains on
11037 outgoing OR connections. Previously, each client or bridge would
11038 use the same cert chain for all outgoing OR connections until
11039 its IP address changes, which allowed any relay that the client
11040 or bridge contacted to determine which entry guards it is using.
11041 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
11042 - If a relay receives a CREATE_FAST cell on a TLS connection, it
11043 no longer considers that connection as suitable for satisfying a
11044 circuit EXTEND request. Now relays can protect clients from the
11045 CVE-2011-2768 issue even if the clients haven't upgraded yet.
11046 - Directory authorities no longer assign the Guard flag to relays
11047 that haven't upgraded to the above "refuse EXTEND requests
11048 to client connections" fix. Now directory authorities can
11049 protect clients from the CVE-2011-2768 issue even if neither
11050 the clients nor the relays have upgraded yet. There's a new
11051 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
11052 to let us transition smoothly, else tomorrow there would be no
11055 o Privacy/anonymity fixes (bridge enumeration):
11056 - Bridge relays now do their directory fetches inside Tor TLS
11057 connections, like all the other clients do, rather than connecting
11058 directly to the DirPort like public relays do. Removes another
11059 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
11060 - Bridges relays now build circuits for themselves in a more similar
11061 way to how clients build them. Removes another avenue for
11062 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
11063 when bridges were introduced.
11064 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
11065 that they initiated. Relays could distinguish incoming bridge
11066 connections from client connections, creating another avenue for
11067 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
11068 Found by "frosty_un".
11071 - Fix a crash bug when changing node restrictions while a DNS lookup
11072 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
11074 - Don't launch a useless circuit after failing to use one of a
11075 hidden service's introduction points. Previously, we would
11076 launch a new introduction circuit, but not set the hidden service
11077 which that circuit was intended to connect to, so it would never
11078 actually be used. A different piece of code would then create a
11079 new introduction circuit correctly. Bug reported by katmagic and
11080 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
11083 - Change an integer overflow check in the OpenBSD_Malloc code so
11084 that GCC is less likely to eliminate it as impossible. Patch
11085 from Mansour Moufid. Fixes bug 4059.
11086 - When a hidden service turns an extra service-side introduction
11087 circuit into a general-purpose circuit, free the rend_data and
11088 intro_key fields first, so we won't leak memory if the circuit
11089 is cannibalized for use as another service-side introduction
11090 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
11091 - Bridges now skip DNS self-tests, to act a little more stealthily.
11092 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
11093 bridges. Patch by "warms0x".
11094 - Fix internal bug-checking logic that was supposed to catch
11095 failures in digest generation so that it will fail more robustly
11096 if we ask for a nonexistent algorithm. Found by Coverity Scan.
11097 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
11098 - Report any failure in init_keys() calls launched because our
11099 IP address has changed. Spotted by Coverity Scan. Bugfix on
11100 0.1.1.4-alpha; fixes CID 484.
11102 o Minor bugfixes (log messages and documentation):
11103 - Remove a confusing dollar sign from the example fingerprint in the
11104 man page, and also make the example fingerprint a valid one. Fixes
11105 bug 4309; bugfix on 0.2.1.3-alpha.
11106 - The next version of Windows will be called Windows 8, and it has
11107 a major version of 6, minor version of 2. Correctly identify that
11108 version instead of calling it "Very recent version". Resolves
11109 ticket 4153; reported by funkstar.
11110 - Downgrade log messages about circuit timeout calibration from
11111 "notice" to "info": they don't require or suggest any human
11112 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
11113 bugfix on 0.2.2.14-alpha.
11116 - Turn on directory request statistics by default and include them in
11117 extra-info descriptors. Don't break if we have no GeoIP database.
11118 Backported from 0.2.3.1-alpha; implements ticket 3951.
11119 - Update to the October 4 2011 Maxmind GeoLite Country database.
11122 Changes in version 0.2.1.31 - 2011-10-26
11123 Tor 0.2.1.31 backports important security and privacy fixes for
11124 oldstable. This release is intended only for package maintainers and
11125 others who cannot use the 0.2.2 stable series. All others should be
11126 using Tor 0.2.2.x or newer.
11128 o Security fixes (also included in 0.2.2.x):
11129 - Replace all potentially sensitive memory comparison operations
11130 with versions whose runtime does not depend on the data being
11131 compared. This will help resist a class of attacks where an
11132 adversary can use variations in timing information to learn
11133 sensitive data. Fix for one case of bug 3122. (Safe memcmp
11134 implementation by Robert Ransom based partially on code by DJB.)
11135 - Fix an assert in parsing router descriptors containing IPv6
11136 addresses. This one took down the directory authorities when
11137 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
11139 o Privacy/anonymity fixes (also included in 0.2.2.x):
11140 - Clients and bridges no longer send TLS certificate chains on
11141 outgoing OR connections. Previously, each client or bridge would
11142 use the same cert chain for all outgoing OR connections until
11143 its IP address changes, which allowed any relay that the client
11144 or bridge contacted to determine which entry guards it is using.
11145 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
11146 - If a relay receives a CREATE_FAST cell on a TLS connection, it
11147 no longer considers that connection as suitable for satisfying a
11148 circuit EXTEND request. Now relays can protect clients from the
11149 CVE-2011-2768 issue even if the clients haven't upgraded yet.
11150 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
11151 that they initiated. Relays could distinguish incoming bridge
11152 connections from client connections, creating another avenue for
11153 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
11154 Found by "frosty_un".
11155 - When receiving a hidden service descriptor, check that it is for
11156 the hidden service we wanted. Previously, Tor would store any
11157 hidden service descriptors that a directory gave it, whether it
11158 wanted them or not. This wouldn't have let an attacker impersonate
11159 a hidden service, but it did let directories pre-seed a client
11160 with descriptors that it didn't want. Bugfix on 0.0.6.
11161 - Avoid linkability based on cached hidden service descriptors: forget
11162 all hidden service descriptors cached as a client when processing a
11163 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
11164 - Make the bridge directory authority refuse to answer directory
11165 requests for "all" descriptors. It used to include bridge
11166 descriptors in its answer, which was a major information leak.
11167 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
11168 - Don't attach new streams to old rendezvous circuits after SIGNAL
11169 NEWNYM. Previously, we would keep using an existing rendezvous
11170 circuit if it remained open (i.e. if it were kept open by a
11171 long-lived stream, or if a new stream were attached to it before
11172 Tor could notice that it was old and no longer in use). Bugfix on
11173 0.1.1.15-rc; fixes bug 3375.
11175 o Minor bugfixes (also included in 0.2.2.x):
11176 - When we restart our relay, we might get a successful connection
11177 from the outside before we've started our reachability tests,
11178 triggering a warning: "ORPort found reachable, but I have no
11179 routerinfo yet. Failing to inform controller of success." This
11180 bug was harmless unless Tor is running under a controller
11181 like Vidalia, in which case the controller would never get a
11182 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
11184 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
11185 enabled. Fixes bug 1526.
11186 - Remove undocumented option "-F" from tor-resolve: it hasn't done
11187 anything since 0.2.1.16-rc.
11188 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
11189 None of the cases where we did this before were wrong, but by making
11190 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
11191 - Fix a rare crash bug that could occur when a client was configured
11192 with a large number of bridges. Fixes bug 2629; bugfix on
11193 0.2.1.2-alpha. Bugfix by trac user "shitlei".
11194 - Correct the warning displayed when a rendezvous descriptor exceeds
11195 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
11197 - Fix an uncommon assertion failure when running with DNSPort under
11198 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
11199 - When warning about missing zlib development packages during compile,
11200 give the correct package names. Bugfix on 0.2.0.1-alpha.
11201 - Require that introduction point keys and onion keys have public
11202 exponent 65537. Bugfix on 0.2.0.10-alpha.
11203 - Do not crash when our configuration file becomes unreadable, for
11204 example due to a permissions change, between when we start up
11205 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
11207 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
11209 - Always NUL-terminate the sun_path field of a sockaddr_un before
11210 passing it to the kernel. (Not a security issue: kernels are
11211 smart enough to reject bad sockaddr_uns.) Found by Coverity;
11212 CID #428. Bugfix on Tor 0.2.0.3-alpha.
11213 - Don't stack-allocate the list of supplementary GIDs when we're
11214 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
11215 could take up to 256K, which is way too much stack. Found by
11216 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
11218 o Minor bugfixes (only in 0.2.1.x):
11219 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
11220 rely on them. Bugfix on 0.2.1.30.
11221 - Use git revisions instead of svn revisions when generating our
11222 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
11224 o Minor features (also included in 0.2.2.x):
11225 - Adjust the expiration time on our SSL session certificates to
11226 better match SSL certs seen in the wild. Resolves ticket 4014.
11227 - Allow nameservers with IPv6 address. Resolves bug 2574.
11228 - Update to the October 4 2011 Maxmind GeoLite Country database.
11231 Changes in version 0.2.2.33 - 2011-09-13
11232 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
11233 TLS handshake that makes relays and bridges that run this new version
11234 reachable from Iran again.
11237 - Avoid an assertion failure when reloading a configuration with
11238 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
11239 3923; bugfix on 0.2.2.25-alpha.
11241 o Minor features (security):
11242 - Check for replays of the public-key encrypted portion of an
11243 INTRODUCE1 cell, in addition to the current check for replays of
11244 the g^x value. This prevents a possible class of active attacks
11245 by an attacker who controls both an introduction point and a
11246 rendezvous point, and who uses the malleability of AES-CTR to
11247 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
11248 that these attacks are infeasible (requiring the attacker to send
11249 on the order of zettabytes of altered cells in a short interval),
11250 but we'd rather block them off in case there are any classes of
11251 this attack that we missed. Reported by Willem Pinckaers.
11254 - Adjust the expiration time on our SSL session certificates to
11255 better match SSL certs seen in the wild. Resolves ticket 4014.
11256 - Change the default required uptime for a relay to be accepted as
11257 a HSDir (hidden service directory) from 24 hours to 25 hours.
11258 Improves on 0.2.0.10-alpha; resolves ticket 2649.
11259 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
11260 authorities to abstain from voting on assignment of the HSDir
11261 consensus flag. Related to bug 2649.
11262 - Update to the September 6 2011 Maxmind GeoLite Country database.
11264 o Minor bugfixes (documentation and log messages):
11265 - Correct the man page to explain that HashedControlPassword and
11266 CookieAuthentication can both be set, in which case either method
11267 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
11268 when we decided to allow these config options to both be set. Issue
11269 raised by bug 3898.
11270 - Demote the 'replay detected' log message emitted when a hidden
11271 service receives the same Diffie-Hellman public key in two different
11272 INTRODUCE2 cells to info level. A normal Tor client can cause that
11273 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
11274 fixes part of bug 2442.
11275 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
11276 level. There is nothing that a hidden service's operator can do
11277 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
11279 - Clarify a log message specifying the characters permitted in
11280 HiddenServiceAuthorizeClient client names. Previously, the log
11281 message said that "[A-Za-z0-9+-_]" were permitted; that could have
11282 given the impression that every ASCII character between "+" and "_"
11283 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
11286 - Provide a substitute implementation of lround() for MSVC, which
11287 apparently lacks it. Patch from Gisle Vanem.
11288 - Clean up some code issues that prevented Tor from building on older
11289 BSDs. Fixes bug 3894; reported by "grarpamp".
11290 - Search for a platform-specific version of "ar" when cross-compiling.
11291 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
11294 Changes in version 0.2.2.32 - 2011-08-27
11295 The Tor 0.2.2 release series is dedicated to the memory of Andreas
11296 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
11297 a founder of the PETS community, a leader in our field, a mentor,
11298 and a friend. He left us with these words: "I had the possibility
11299 to contribute to this world that is not as it should be. I hope I
11300 could help in some areas to make the world a better place, and that
11301 I could also encourage other people to be engaged in improving the
11302 world. Please, stay engaged. This world needs you, your love, your
11303 initiative -- now I cannot be part of that anymore."
11305 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
11306 ready. More than two years in the making, this release features improved
11307 client performance and hidden service reliability, better compatibility
11308 for Android, correct behavior for bridges that listen on more than
11309 one address, more extensible and flexible directory object handling,
11310 better reporting of network statistics, improved code security, and
11311 many many other features and bugfixes.
11313 o Major features (client performance):
11314 - When choosing which cells to relay first, relays now favor circuits
11315 that have been quiet recently, to provide lower latency for
11316 low-volume circuits. By default, relays enable or disable this
11317 feature based on a setting in the consensus. They can override
11318 this default by using the new "CircuitPriorityHalflife" config
11319 option. Design and code by Ian Goldberg, Can Tang, and Chris
11321 - Directory authorities now compute consensus weightings that instruct
11322 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
11323 and no flag. Clients use these weightings to distribute network load
11324 more evenly across these different relay types. The weightings are
11325 in the consensus so we can change them globally in the future. Extra
11326 thanks to "outofwords" for finding some nasty security bugs in
11327 the first implementation of this feature.
11329 o Major features (client performance, circuit build timeout):
11330 - Tor now tracks how long it takes to build client-side circuits
11331 over time, and adapts its timeout to local network performance.
11332 Since a circuit that takes a long time to build will also provide
11333 bad performance, we get significant latency improvements by
11334 discarding the slowest 20% of circuits. Specifically, Tor creates
11335 circuits more aggressively than usual until it has enough data
11336 points for a good timeout estimate. Implements proposal 151.
11337 - Circuit build timeout constants can be controlled by consensus
11338 parameters. We set good defaults for these parameters based on
11339 experimentation on broadband and simulated high-latency links.
11340 - Circuit build time learning can be disabled via consensus parameter
11341 or by the client via a LearnCircuitBuildTimeout config option. We
11342 also automatically disable circuit build time calculation if either
11343 AuthoritativeDirectory is set, or if we fail to write our state
11344 file. Implements ticket 1296.
11346 o Major features (relays use their capacity better):
11347 - Set SO_REUSEADDR socket option on all sockets, not just
11348 listeners. This should help busy exit nodes avoid running out of
11349 useable ports just because all the ports have been used in the
11350 near past. Resolves issue 2850.
11351 - Relays now save observed peak bandwidth throughput rates to their
11352 state file (along with total usage, which was already saved),
11353 so that they can determine their correct estimated bandwidth on
11354 restart. Resolves bug 1863, where Tor relays would reset their
11355 estimated bandwidth to 0 after restarting.
11356 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
11357 should give us approximately 40-50% more Guard-flagged nodes,
11358 improving the anonymity the Tor network can provide and also
11359 decreasing the dropoff in throughput that relays experience when
11360 they first get the Guard flag.
11361 - Directory authorities now take changes in router IP address and
11362 ORPort into account when determining router stability. Previously,
11363 if a router changed its IP or ORPort, the authorities would not
11364 treat it as having any downtime for the purposes of stability
11365 calculation, whereas clients would experience downtime since the
11366 change would take a while to propagate to them. Resolves issue 1035.
11367 - New AccelName and AccelDir options add support for dynamic OpenSSL
11368 hardware crypto acceleration engines.
11370 o Major features (relays control their load better):
11371 - Exit relays now try harder to block exit attempts from unknown
11372 relays, to make it harder for people to use them as one-hop proxies
11373 a la tortunnel. Controlled by the refuseunknownexits consensus
11374 parameter (currently enabled), or you can override it on your
11375 relay with the RefuseUnknownExits torrc option. Resolves bug 1751;
11376 based on a variant of proposal 163.
11377 - Add separate per-conn write limiting to go with the per-conn read
11378 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
11379 but never per-conn write limits.
11380 - New consensus params "bwconnrate" and "bwconnburst" to let us
11381 rate-limit client connections as they enter the network. It's
11382 controlled in the consensus so we can turn it on and off for
11383 experiments. It's starting out off. Based on proposal 163.
11385 o Major features (controllers):
11386 - Export GeoIP information on bridge usage to controllers even if we
11387 have not yet been running for 24 hours. Now Vidalia bridge operators
11388 can get more accurate and immediate feedback about their
11389 contributions to the network.
11390 - Add an __OwningControllerProcess configuration option and a
11391 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
11392 that when it exits, Tor will shut down. Implements feature 3049.
11394 o Major features (directory authorities):
11395 - Directory authorities now create, vote on, and serve multiple
11396 parallel formats of directory data as part of their voting process.
11397 Partially implements Proposal 162: "Publish the consensus in
11399 - Directory authorities now agree on and publish small summaries
11400 of router information that clients can use in place of regular
11401 server descriptors. This transition will allow Tor 0.2.3 clients
11402 to use far less bandwidth for downloading information about the
11403 network. Begins the implementation of Proposal 158: "Clients
11404 download consensus + microdescriptors".
11405 - The directory voting system is now extensible to use multiple hash
11406 algorithms for signatures and resource selection. Newer formats
11407 are signed with SHA256, with a possibility for moving to a better
11408 hash algorithm in the future.
11409 - Directory authorities can now vote on arbitrary integer values as
11410 part of the consensus process. This is designed to help set
11411 network-wide parameters. Implements proposal 167.
11413 o Major features and bugfixes (node selection):
11414 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
11415 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and Strict*Nodes
11416 options. Previously, we had been ambiguous in describing what
11417 counted as an "exit" node, and what operations exactly "StrictNodes
11418 0" would permit. This created confusion when people saw nodes built
11419 through unexpected circuits, and made it hard to tell real bugs from
11420 surprises. Now the intended behavior is:
11421 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
11422 a node that delivers user traffic outside the Tor network.
11423 . "Entry", in the context of EntryNodes, means a node used as the
11424 first hop of a multihop circuit. It doesn't include direct
11425 connections to directory servers.
11426 . "ExcludeNodes" applies to all nodes.
11427 . "StrictNodes" changes the behavior of ExcludeNodes only. When
11428 StrictNodes is set, Tor should avoid all nodes listed in
11429 ExcludeNodes, even when it will make user requests fail. When
11430 StrictNodes is *not* set, then Tor should follow ExcludeNodes
11431 whenever it can, except when it must use an excluded node to
11432 perform self-tests, connect to a hidden service, provide a
11433 hidden service, fulfill a .exit request, upload directory
11434 information, or fetch directory information.
11435 Collectively, the changes to implement the behavior fix bug 1090.
11436 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
11437 change during a config reload, mark and discard all our origin
11438 circuits. This fix should address edge cases where we change the
11439 config options and but then choose a circuit that we created before
11441 - Make EntryNodes config option much more aggressive even when
11442 StrictNodes is not set. Before it would prepend your requested
11443 entrynodes to your list of guard nodes, but feel free to use others
11444 after that. Now it chooses only from your EntryNodes if any of
11445 those are available, and only falls back to others if a) they're
11446 all down and b) StrictNodes is not set.
11447 - Now we refresh your entry guards from EntryNodes at each consensus
11448 fetch -- rather than just at startup and then they slowly rot as
11449 the network changes.
11450 - Add support for the country code "{??}" in torrc options like
11451 ExcludeNodes, to indicate all routers of unknown country. Closes
11453 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
11454 a node is listed in both, it's treated as excluded.
11455 - ExcludeNodes now applies to directory nodes -- as a preference if
11456 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
11457 Don't exclude all the directory authorities and set StrictNodes to 1
11458 unless you really want your Tor to break.
11459 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
11460 - ExcludeExitNodes now overrides .exit requests.
11461 - We don't use bridges listed in ExcludeNodes.
11462 - When StrictNodes is 1:
11463 . We now apply ExcludeNodes to hidden service introduction points
11464 and to rendezvous points selected by hidden service users. This
11465 can make your hidden service less reliable: use it with caution!
11466 . If we have used ExcludeNodes on ourself, do not try relay
11467 reachability self-tests.
11468 . If we have excluded all the directory authorities, we will not
11469 even try to upload our descriptor if we're a relay.
11470 . Do not honor .exit requests to an excluded node.
11471 - When the set of permitted nodes changes, we now remove any mappings
11472 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
11474 - We never cannibalize a circuit that had excluded nodes on it, even
11475 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
11476 - Improve log messages related to excluded nodes.
11478 o Major features (misc):
11479 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
11480 to help Tor build correctly for Android phones.
11481 - The options SocksPort, ControlPort, and so on now all accept a
11482 value "auto" that opens a socket on an OS-selected port. A
11483 new ControlPortWriteToFile option tells Tor to write its
11484 actual control port or ports to a chosen file. If the option
11485 ControlPortFileGroupReadable is set, the file is created as
11486 group-readable. Now users can run two Tor clients on the same
11487 system without needing to manually mess with parameters. Resolves
11488 part of ticket 3076.
11489 - Tor now supports tunneling all of its outgoing connections over
11490 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
11491 configuration options. Code by Christopher Davis.
11493 o Code security improvements:
11494 - Replace all potentially sensitive memory comparison operations
11495 with versions whose runtime does not depend on the data being
11496 compared. This will help resist a class of attacks where an
11497 adversary can use variations in timing information to learn
11498 sensitive data. Fix for one case of bug 3122. (Safe memcmp
11499 implementation by Robert Ransom based partially on code by DJB.)
11500 - Enable Address Space Layout Randomization (ASLR) and Data Execution
11501 Prevention (DEP) by default on Windows to make it harder for
11502 attackers to exploit vulnerabilities. Patch from John Brooks.
11503 - New "--enable-gcc-hardening" ./configure flag (off by default)
11504 to turn on gcc compile time hardening options. It ensures
11505 that signed ints have defined behavior (-fwrapv), enables
11506 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
11507 with canaries (-fstack-protector-all), turns on ASLR protection if
11508 supported by the kernel (-fPIE, -pie), and adds additional security
11509 related warnings. Verified to work on Mac OS X and Debian Lenny.
11510 - New "--enable-linker-hardening" ./configure flag (off by default)
11511 to turn on ELF specific hardening features (relro, now). This does
11512 not work with Mac OS X or any other non-ELF binary format.
11513 - Always search the Windows system directory for system DLLs, and
11514 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
11515 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
11516 current and future memory pages via mlockall(). On supported
11517 platforms (modern Linux and probably BSD but not Windows or OS X),
11518 this should effectively disable any and all attempts to page out
11519 memory. This option requires that you start your Tor as root --
11520 if you use DisableAllSwap, please consider using the User option
11521 to properly reduce the privileges of your Tor.
11523 o Major bugfixes (crashes):
11524 - Fix crash bug on platforms where gmtime and localtime can return
11525 NULL. Windows 7 users were running into this one. Fixes part of bug
11526 2077. Bugfix on all versions of Tor. Found by boboper.
11527 - Introduce minimum/maximum values that clients will believe
11528 from the consensus. Now we'll have a better chance to avoid crashes
11529 or worse when a consensus param has a weird value.
11530 - Fix a rare crash bug that could occur when a client was configured
11531 with a large number of bridges. Fixes bug 2629; bugfix on
11532 0.2.1.2-alpha. Bugfix by trac user "shitlei".
11533 - Do not crash when our configuration file becomes unreadable, for
11534 example due to a permissions change, between when we start up
11535 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
11537 - If we're in the pathological case where there's no exit bandwidth
11538 but there is non-exit bandwidth, or no guard bandwidth but there
11539 is non-guard bandwidth, don't crash during path selection. Bugfix
11541 - Fix a crash bug when trying to initialize the evdns module in
11542 Libevent 2. Bugfix on 0.2.1.16-rc.
11544 o Major bugfixes (stability):
11545 - Fix an assert in parsing router descriptors containing IPv6
11546 addresses. This one took down the directory authorities when
11547 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
11548 - Fix an uncommon assertion failure when running with DNSPort under
11549 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
11550 - Treat an unset $HOME like an empty $HOME rather than triggering an
11551 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
11552 - More gracefully handle corrupt state files, removing asserts
11553 in favor of saving a backup and resetting state.
11554 - Instead of giving an assertion failure on an internal mismatch
11555 on estimated freelist size, just log a BUG warning and try later.
11556 Mitigates but does not fix bug 1125.
11557 - Fix an assert that got triggered when using the TestingTorNetwork
11558 configuration option and then issuing a GETINFO config-text control
11559 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
11560 - If the cached cert file is unparseable, warn but don't exit.
11562 o Privacy fixes (relays/bridges):
11563 - Don't list Windows capabilities in relay descriptors. We never made
11564 use of them, and maybe it's a bad idea to publish them. Bugfix
11566 - If the Nickname configuration option isn't given, Tor would pick a
11567 nickname based on the local hostname as the nickname for a relay.
11568 Because nicknames are not very important in today's Tor and the
11569 "Unnamed" nickname has been implemented, this is now problematic
11570 behavior: It leaks information about the hostname without being
11571 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
11572 introduced the Unnamed nickname. Reported by tagnaq.
11573 - Maintain separate TLS contexts and certificates for incoming and
11574 outgoing connections in bridge relays. Previously we would use the
11575 same TLS contexts and certs for incoming and outgoing connections.
11576 Bugfix on 0.2.0.3-alpha; addresses bug 988.
11577 - Maintain separate identity keys for incoming and outgoing TLS
11578 contexts in bridge relays. Previously we would use the same
11579 identity keys for incoming and outgoing TLS contexts. Bugfix on
11580 0.2.0.3-alpha; addresses the other half of bug 988.
11581 - Make the bridge directory authority refuse to answer directory
11582 requests for "all descriptors". It used to include bridge
11583 descriptors in its answer, which was a major information leak.
11584 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
11586 o Privacy fixes (clients):
11587 - When receiving a hidden service descriptor, check that it is for
11588 the hidden service we wanted. Previously, Tor would store any
11589 hidden service descriptors that a directory gave it, whether it
11590 wanted them or not. This wouldn't have let an attacker impersonate
11591 a hidden service, but it did let directories pre-seed a client
11592 with descriptors that it didn't want. Bugfix on 0.0.6.
11593 - Start the process of disabling ".exit" address notation, since it
11594 can be used for a variety of esoteric application-level attacks
11595 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
11597 - Reject attempts at the client side to open connections to private
11598 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
11599 a randomly chosen exit node. Attempts to do so are always
11600 ill-defined, generally prevented by exit policies, and usually
11601 in error. This will also help to detect loops in transparent
11602 proxy configurations. You can disable this feature by setting
11603 "ClientRejectInternalAddresses 0" in your torrc.
11604 - Log a notice when we get a new control connection. Now it's easier
11605 for security-conscious users to recognize when a local application
11606 is knocking on their controller door. Suggested by bug 1196.
11608 o Privacy fixes (newnym):
11609 - Avoid linkability based on cached hidden service descriptors: forget
11610 all hidden service descriptors cached as a client when processing a
11611 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
11612 - On SIGHUP, do not clear out all TrackHostExits mappings, client
11613 DNS cache entries, and virtual address mappings: that's what
11614 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
11615 - Don't attach new streams to old rendezvous circuits after SIGNAL
11616 NEWNYM. Previously, we would keep using an existing rendezvous
11617 circuit if it remained open (i.e. if it were kept open by a
11618 long-lived stream, or if a new stream were attached to it before
11619 Tor could notice that it was old and no longer in use). Bugfix on
11620 0.1.1.15-rc; fixes bug 3375.
11622 o Major bugfixes (relay bandwidth accounting):
11623 - Fix a bug that could break accounting on 64-bit systems with large
11624 time_t values, making them hibernate for impossibly long intervals.
11625 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
11626 - Fix a bug in bandwidth accounting that could make us use twice
11627 the intended bandwidth when our interval start changes due to
11628 daylight saving time. Now we tolerate skew in stored vs computed
11629 interval starts: if the start of the period changes by no more than
11630 50% of the period's duration, we remember bytes that we transferred
11631 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
11633 o Major bugfixes (bridges):
11634 - Bridges now use "reject *:*" as their default exit policy. Bugfix
11635 on 0.2.0.3-alpha. Fixes bug 1113.
11636 - If you configure your bridge with a known identity fingerprint,
11637 and the bridge authority is unreachable (as it is in at least
11638 one country now), fall back to directly requesting the descriptor
11639 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
11641 - Fix a bug where bridge users who configure the non-canonical
11642 address of a bridge automatically switch to its canonical
11643 address. If a bridge listens at more than one address, it
11644 should be able to advertise those addresses independently and
11645 any non-blocked addresses should continue to work. Bugfix on Tor
11646 0.2.0.3-alpha. Fixes bug 2510.
11647 - If you configure Tor to use bridge A, and then quit and
11648 configure Tor to use bridge B instead (or if you change Tor
11649 to use bridge B via the controller), it would happily continue
11650 to use bridge A if it's still reachable. While this behavior is
11651 a feature if your goal is connectivity, in some scenarios it's a
11652 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
11653 - When the controller configures a new bridge, don't wait 10 to 60
11654 seconds before trying to fetch its descriptor. Bugfix on
11655 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
11657 o Major bugfixes (directory authorities):
11658 - Many relays have been falling out of the consensus lately because
11659 not enough authorities know about their descriptor for them to get
11660 a majority of votes. When we deprecated the v2 directory protocol,
11661 we got rid of the only way that v3 authorities can hear from each
11662 other about other descriptors. Now authorities examine every v3
11663 vote for new descriptors, and fetch them from that authority. Bugfix
11665 - Authorities could be tricked into giving out the Exit flag to relays
11666 that didn't allow exiting to any ports. This bug could screw
11667 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
11668 1238. Bug discovered by Martin Kowalczyk.
11669 - If all authorities restart at once right before a consensus vote,
11670 nobody will vote about "Running", and clients will get a consensus
11671 with no usable relays. Instead, authorities refuse to build a
11672 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
11674 o Major bugfixes (stream-level fairness):
11675 - When receiving a circuit-level SENDME for a blocked circuit, try
11676 to package cells fairly from all the streams that had previously
11677 been blocked on that circuit. Previously, we had started with the
11678 oldest stream, and allowed each stream to potentially exhaust
11679 the circuit's package window. This gave older streams on any
11680 given circuit priority over newer ones. Fixes bug 1937. Detected
11681 originally by Camilo Viecco. This bug was introduced before the
11682 first Tor release, in svn commit r152: it is the new winner of
11683 the longest-lived bug prize.
11684 - Fix a stream fairness bug that would cause newer streams on a given
11685 circuit to get preference when reading bytes from the origin or
11686 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
11687 introduced before the first Tor release, in svn revision r152.
11688 - When the exit relay got a circuit-level sendme cell, it started
11689 reading on the exit streams, even if had 500 cells queued in the
11690 circuit queue already, so the circuit queue just grew and grew in
11691 some cases. We fix this by not re-enabling reading on receipt of a
11692 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
11693 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
11695 - Newly created streams were allowed to read cells onto circuits,
11696 even if the circuit's cell queue was blocked and waiting to drain.
11697 This created potential unfairness, as older streams would be
11698 blocked, but newer streams would gladly fill the queue completely.
11699 We add code to detect this situation and prevent any stream from
11700 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
11703 o Major bugfixes (hidden services):
11704 - Apply circuit timeouts to opened hidden-service-related circuits
11705 based on the correct start time. Previously, we would apply the
11706 circuit build timeout based on time since the circuit's creation;
11707 it was supposed to be applied based on time since the circuit
11708 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
11709 - Improve hidden service robustness: When we find that we have
11710 extended a hidden service's introduction circuit to a relay not
11711 listed as an introduction point in the HS descriptor we currently
11712 have, retry with an introduction point from the current
11713 descriptor. Previously we would just give up. Fixes bugs 1024 and
11714 1930; bugfix on 0.2.0.10-alpha.
11715 - Directory authorities now use data collected from their own
11716 uptime observations when choosing whether to assign the HSDir flag
11717 to relays, instead of trusting the uptime value the relay reports in
11718 its descriptor. This change helps prevent an attack where a small
11719 set of nodes with frequently-changing identity keys can blackhole
11720 a hidden service. (Only authorities need upgrade; others will be
11721 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
11722 - Stop assigning the HSDir flag to relays that disable their
11723 DirPort (and thus will refuse to answer directory requests). This
11724 fix should dramatically improve the reachability of hidden services:
11725 hidden services and hidden service clients pick six HSDir relays
11726 to store and retrieve the hidden service descriptor, and currently
11727 about half of the HSDir relays will refuse to work. Bugfix on
11728 0.2.0.10-alpha; fixes part of bug 1693.
11730 o Major bugfixes (misc):
11731 - Clients now stop trying to use an exit node associated with a given
11732 destination by TrackHostExits if they fail to reach that exit node.
11733 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
11734 - Fix a regression that caused Tor to rebind its ports if it receives
11735 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
11736 - Remove an extra pair of quotation marks around the error
11737 message in control-port STATUS_GENERAL BUG events. Bugfix on
11738 0.1.2.6-alpha; fixes bug 3732.
11740 o Minor features (relays):
11741 - Ensure that no empty [dirreq-](read|write)-history lines are added
11742 to an extrainfo document. Implements ticket 2497.
11743 - When bandwidth accounting is enabled, be more generous with how
11744 much bandwidth we'll use up before entering "soft hibernation".
11745 Previously, we'd refuse new connections and circuits once we'd
11746 used up 95% of our allotment. Now, we use up 95% of our allotment,
11747 AND make sure that we have no more than 500MB (or 3 hours of
11748 expected traffic, whichever is lower) remaining before we enter
11750 - Relays now log the reason for publishing a new relay descriptor,
11751 so we have a better chance of hunting down instances of bug 1810.
11752 Resolves ticket 3252.
11753 - Log a little more clearly about the times at which we're no longer
11754 accepting new connections (e.g. due to hibernating). Resolves
11756 - When AllowSingleHopExits is set, print a warning to explain to the
11757 relay operator why most clients are avoiding her relay.
11758 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
11759 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
11760 clients are already deprecated because of security bugs.
11762 o Minor features (network statistics):
11763 - Directory mirrors that set "DirReqStatistics 1" write statistics
11764 about directory requests to disk every 24 hours. As compared to the
11765 "--enable-geoip-stats" ./configure flag in 0.2.1.x, there are a few
11766 improvements: 1) stats are written to disk exactly every 24 hours;
11767 2) estimated shares of v2 and v3 requests are determined as mean
11768 values, not at the end of a measurement period; 3) unresolved
11769 requests are listed with country code '??'; 4) directories also
11770 measure download times.
11771 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
11772 number of exit streams and transferred bytes per port to disk every
11774 - Relays that set "CellStatistics 1" write statistics on how long
11775 cells spend in their circuit queues to disk every 24 hours.
11776 - Entry nodes that set "EntryStatistics 1" write statistics on the
11777 rough number and origins of connecting clients to disk every 24
11779 - Relays that write any of the above statistics to disk and set
11780 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
11781 their extra-info documents. Implements proposal 166.
11783 o Minor features (GeoIP and statistics):
11784 - Provide a log message stating which geoip file we're parsing
11785 instead of just stating that we're parsing the geoip file.
11786 Implements ticket 2432.
11787 - Make sure every relay writes a state file at least every 12 hours.
11788 Previously, a relay could go for weeks without writing its state
11789 file, and on a crash could lose its bandwidth history, capacity
11790 estimates, client country statistics, and so on. Addresses bug 3012.
11791 - Relays report the number of bytes spent on answering directory
11792 requests in extra-info descriptors similar to {read,write}-history.
11793 Implements enhancement 1790.
11794 - Report only the top 10 ports in exit-port stats in order not to
11795 exceed the maximum extra-info descriptor length of 50 KB. Implements
11797 - If writing the state file to disk fails, wait up to an hour before
11798 retrying again, rather than trying again each second. Fixes bug
11799 2346; bugfix on Tor 0.1.1.3-alpha.
11800 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
11801 when we switch from being a public relay to a bridge. Otherwise
11802 there will still be clients that see the relay in their consensus,
11803 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes
11805 - Update to the August 2 2011 Maxmind GeoLite Country database.
11807 o Minor features (clients):
11808 - When expiring circuits, use microsecond timers rather than
11809 one-second timers. This can avoid an unpleasant situation where a
11810 circuit is launched near the end of one second and expired right
11811 near the beginning of the next, and prevent fluctuations in circuit
11813 - If we've configured EntryNodes and our network goes away and/or all
11814 our entrynodes get marked down, optimistically retry them all when
11815 a new socks application request appears. Fixes bug 1882.
11816 - Always perform router selections using weighted relay bandwidth,
11817 even if we don't need a high capacity circuit at the time. Non-fast
11818 circuits now only differ from fast ones in that they can use relays
11819 not marked with the Fast flag. This "feature" could turn out to
11820 be a horrible bug; we should investigate more before it goes into
11822 - When we run out of directory information such that we can't build
11823 circuits, but then get enough that we can build circuits, log when
11824 we actually construct a circuit, so the user has a better chance of
11825 knowing what's going on. Fixes bug 1362.
11826 - Log SSL state transitions at debug level during handshake, and
11827 include SSL states in error messages. This may help debug future
11828 SSL handshake issues.
11830 o Minor features (directory authorities):
11831 - When a router changes IP address or port, authorities now launch
11832 a new reachability test for it. Implements ticket 1899.
11833 - Directory authorities now reject relays running any versions of
11834 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
11835 known bugs that keep RELAY_EARLY cells from working on rendezvous
11836 circuits. Followup to fix for bug 2081.
11837 - Directory authorities now reject relays running any version of Tor
11838 older than 0.2.0.26-rc. That version is the earliest that fetches
11839 current directory information correctly. Fixes bug 2156.
11840 - Directory authorities now do an immediate reachability check as soon
11841 as they hear about a new relay. This change should slightly reduce
11842 the time between setting up a relay and getting listed as running
11843 in the consensus. It should also improve the time between setting
11844 up a bridge and seeing use by bridge users.
11845 - Directory authorities no longer launch a TLS connection to every
11846 relay as they startup. Now that we have 2k+ descriptors cached,
11847 the resulting network hiccup is becoming a burden. Besides,
11848 authorities already avoid voting about Running for the first half
11849 hour of their uptime.
11850 - Directory authorities now log the source of a rejected POSTed v3
11851 networkstatus vote, so we can track failures better.
11852 - Backport code from 0.2.3.x that allows directory authorities to
11853 clean their microdescriptor caches. Needed to resolve bug 2230.
11855 o Minor features (hidden services):
11856 - Use computed circuit-build timeouts to decide when to launch
11857 parallel introduction circuits for hidden services. (Previously,
11858 we would retry after 15 seconds.)
11859 - Don't allow v0 hidden service authorities to act as clients.
11860 Required by fix for bug 3000.
11861 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
11862 by fix for bug 3000.
11863 - Make hidden services work better in private Tor networks by not
11864 requiring any uptime to join the hidden service descriptor
11865 DHT. Implements ticket 2088.
11866 - Log (at info level) when purging pieces of hidden-service-client
11867 state because of SIGNAL NEWNYM.
11869 o Minor features (controller interface):
11870 - New "GETINFO net/listeners/(type)" controller command to return
11871 a list of addresses and ports that are bound for listeners for a
11872 given connection type. This is useful when the user has configured
11873 "SocksPort auto" and the controller needs to know which port got
11874 chosen. Resolves another part of ticket 3076.
11875 - Have the controller interface give a more useful message than
11876 "Internal Error" in response to failed GETINFO requests.
11877 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
11878 event, to give information on the current rate of circuit timeouts
11879 over our stored history.
11880 - The 'EXTENDCIRCUIT' control port command can now be used with
11881 a circ id of 0 and no path. This feature will cause Tor to build
11882 a new 'fast' general purpose circuit using its own path selection
11884 - Added a BUILDTIMEOUT_SET controller event to describe changes
11885 to the circuit build timeout.
11886 - New controller command "getinfo config-text". It returns the
11887 contents that Tor would write if you send it a SAVECONF command,
11888 so the controller can write the file to disk itself.
11890 o Minor features (controller protocol):
11891 - Add a new ControlSocketsGroupWritable configuration option: when
11892 it is turned on, ControlSockets are group-writeable by the default
11893 group of the current user. Patch by Jérémy Bobbio; implements
11895 - Tor now refuses to create a ControlSocket in a directory that is
11896 world-readable (or group-readable if ControlSocketsGroupWritable
11897 is 0). This is necessary because some operating systems do not
11898 enforce permissions on an AF_UNIX sockets. Permissions on the
11899 directory holding the socket, however, seems to work everywhere.
11900 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
11901 not. This would lead to a cookie that is still not group readable.
11902 Closes bug 1843. Suggested by katmagic.
11903 - Future-proof the controller protocol a bit by ignoring keyword
11904 arguments we do not recognize.
11906 o Minor features (more useful logging):
11907 - Revise most log messages that refer to nodes by nickname to
11908 instead use the "$key=nickname at address" format. This should be
11909 more useful, especially since nicknames are less and less likely
11910 to be unique. Resolves ticket 3045.
11911 - When an HTTPS proxy reports "403 Forbidden", we now explain
11912 what it means rather than calling it an unexpected status code.
11913 Closes bug 2503. Patch from Michael Yakubovich.
11914 - Rate-limit a warning about failures to download v2 networkstatus
11915 documents. Resolves part of bug 1352.
11916 - Rate-limit the "your application is giving Tor only an IP address"
11917 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
11918 - Rate-limit "Failed to hand off onionskin" warnings.
11919 - When logging a rate-limited warning, we now mention how many messages
11920 got suppressed since the last warning.
11921 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
11922 2 no signature, 4 required" messages about consensus signatures
11923 easier to read, and make sure they get logged at the same severity
11924 as the messages explaining which keys are which. Fixes bug 1290.
11925 - Don't warn when we have a consensus that we can't verify because
11926 of missing certificates, unless those certificates are ones
11927 that we have been trying and failing to download. Fixes bug 1145.
11929 o Minor features (log domains):
11930 - Add documentation for configuring logging at different severities in
11931 different log domains. We've had this feature since 0.2.1.1-alpha,
11932 but for some reason it never made it into the manpage. Fixes
11934 - Make it simpler to specify "All log domains except for A and B".
11935 Previously you needed to say "[*,~A,~B]". Now you can just say
11937 - Add a "LogMessageDomains 1" option to include the domains of log
11938 messages along with the messages. Without this, there's no way
11939 to use log domains without reading the source or doing a lot
11941 - Add a new "Handshake" log domain for activities that happen
11942 during the TLS handshake.
11944 o Minor features (build process):
11945 - Make compilation with clang possible when using
11946 "--enable-gcc-warnings" by removing two warning options that clang
11947 hasn't implemented yet and by fixing a few warnings. Resolves
11949 - Detect platforms that brokenly use a signed size_t, and refuse to
11950 build there. Found and analyzed by doorss and rransom.
11951 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
11953 - Add support for statically linking zlib by specifying
11954 "--enable-static-zlib", to go with our support for statically
11955 linking openssl and libevent. Resolves bug 1358.
11956 - Instead of adding the svn revision to the Tor version string, report
11957 the git commit (when we're building from a git checkout).
11958 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
11960 - New --digests command-line switch to output the digests of the
11961 source files Tor was built with.
11962 - Generate our manpage and HTML documentation using Asciidoc. This
11963 change should make it easier to maintain the documentation, and
11964 produce nicer HTML. The build process fails if asciidoc cannot
11965 be found and building with asciidoc isn't disabled (via the
11966 "--disable-asciidoc" argument to ./configure. Skipping the manpage
11967 speeds up the build considerably.
11969 o Minor features (options / torrc):
11970 - Warn when the same option is provided more than once in a torrc
11971 file, on the command line, or in a single SETCONF statement, and
11972 the option is one that only accepts a single line. Closes bug 1384.
11973 - Warn when the user configures two HiddenServiceDir lines that point
11974 to the same directory. Bugfix on 0.0.6 (the version introducing
11975 HiddenServiceDir); fixes bug 3289.
11976 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
11977 do individual connection-level rate limiting of clients. The torrc
11978 config options with the same names trump the consensus params, if
11979 both are present. Replaces the old "bwconnrate" and "bwconnburst"
11980 consensus params which were broken from 0.2.2.7-alpha through
11981 0.2.2.14-alpha. Closes bug 1947.
11982 - New config option "WarnUnsafeSocks 0" disables the warning that
11983 occurs whenever Tor receives a socks handshake using a version of
11984 the socks protocol that can only provide an IP address (rather
11985 than a hostname). Setups that do DNS locally over Tor are fine,
11986 and we shouldn't spam the logs in that case.
11987 - New config option "CircuitStreamTimeout" to override our internal
11988 timeout schedule for how many seconds until we detach a stream from
11989 a circuit and try a new circuit. If your network is particularly
11990 slow, you might want to set this to a number like 60.
11991 - New options for SafeLogging to allow scrubbing only log messages
11992 generated while acting as a relay. Specify "SafeLogging relay" if
11993 you want to ensure that only messages known to originate from
11994 client use of the Tor process will be logged unsafely.
11995 - Time and memory units in the configuration file can now be set to
11996 fractional units. For example, "2.5 GB" is now a valid value for
11998 - Support line continuations in the torrc config file. If a line
11999 ends with a single backslash character, the newline is ignored, and
12000 the configuration value is treated as continuing on the next line.
12003 o Minor features (unit tests):
12004 - Revise our unit tests to use the "tinytest" framework, so we
12005 can run tests in their own processes, have smarter setup/teardown
12006 code, and so on. The unit test code has moved to its own
12007 subdirectory, and has been split into multiple modules.
12008 - Add a unit test for cross-platform directory-listing code.
12009 - Add some forgotten return value checks during unit tests. Found
12011 - Use GetTempDir to find the proper temporary directory location on
12012 Windows when generating temporary files for the unit tests. Patch
12015 o Minor features (misc):
12016 - The "torify" script now uses torsocks where available.
12017 - Make Libevent log messages get delivered to controllers later,
12018 and not from inside the Libevent log handler. This prevents unsafe
12019 reentrant Libevent calls while still letting the log messages
12021 - Certain Tor clients (such as those behind check.torproject.org) may
12022 want to fetch the consensus in an extra early manner. To enable this
12023 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
12024 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
12025 as only certain clients who must have this information sooner should
12027 - Expand homedirs passed to tor-checkkey. This should silence a
12028 coverity complaint about passing a user-supplied string into
12029 open() without checking it.
12030 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
12031 used on bridges, and it makes bridge scanning somewhat easier.
12032 - Create the /var/run/tor directory on startup on OpenSUSE if it is
12033 not already created. Patch from Andreas Stieger. Fixes bug 2573.
12035 o Minor bugfixes (relays):
12036 - When a relay decides that its DNS is too broken for it to serve
12037 as an exit server, it advertised itself as a non-exit, but
12038 continued to act as an exit. This could create accidental
12039 partitioning opportunities for users. Instead, if a relay is
12040 going to advertise reject *:* as its exit policy, it should
12041 really act with exit policy "reject *:*". Fixes bug 2366.
12042 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
12043 - Publish a router descriptor even if generating an extra-info
12044 descriptor fails. Previously we would not publish a router
12045 descriptor without an extra-info descriptor; this can cause fast
12046 exit relays collecting exit-port statistics to drop from the
12047 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
12048 - When we're trying to guess whether we know our IP address as
12049 a relay, we would log various ways that we failed to guess
12050 our address, but never log that we ended up guessing it
12051 successfully. Now add a log line to help confused and anxious
12052 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
12053 - For bandwidth accounting, calculate our expected bandwidth rate
12054 based on the time during which we were active and not in
12055 soft-hibernation during the last interval. Previously, we were
12056 also considering the time spent in soft-hibernation. If this
12057 was a long time, we would wind up underestimating our bandwidth
12058 by a lot, and skewing our wakeup time towards the start of the
12059 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
12060 - Demote a confusing TLS warning that relay operators might get when
12061 someone tries to talk to their ORPort. It is not the operator's
12062 fault, nor can they do anything about it. Fixes bug 1364; bugfix
12064 - Change "Application request when we're believed to be offline."
12065 notice to "Application request when we haven't used client
12066 functionality lately.", to clarify that it's not an error. Bugfix
12067 on 0.0.9.3; fixes bug 1222.
12069 o Minor bugfixes (bridges):
12070 - When a client starts or stops using bridges, never use a circuit
12071 that was built before the configuration change. This behavior could
12072 put at risk a user who uses bridges to ensure that her traffic
12073 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
12075 - Do not reset the bridge descriptor download status every time we
12076 re-parse our configuration or get a configuration change. Fixes
12077 bug 3019; bugfix on 0.2.0.3-alpha.
12078 - Users couldn't configure a regular relay to be their bridge. It
12079 didn't work because when Tor fetched the bridge descriptor, it found
12080 that it already had it, and didn't realize that the purpose of the
12081 descriptor had changed. Now we replace routers with a purpose other
12082 than bridge with bridge descriptors when fetching them. Bugfix on
12083 0.1.1.9-alpha. Fixes bug 1776.
12084 - In the special case where you configure a public exit relay as your
12085 bridge, Tor would be willing to use that exit relay as the last
12086 hop in your circuit as well. Now we fail that circuit instead.
12087 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
12089 o Minor bugfixes (clients):
12090 - We now ask the other side of a stream (the client or the exit)
12091 for more data on that stream when the amount of queued data on
12092 that stream dips low enough. Previously, we wouldn't ask the
12093 other side for more data until either it sent us more data (which
12094 it wasn't supposed to do if it had exhausted its window!) or we
12095 had completely flushed all our queued data. This flow control fix
12096 should improve throughput. Fixes bug 2756; bugfix on the earliest
12097 released versions of Tor (svn commit r152).
12098 - When a client finds that an origin circuit has run out of 16-bit
12099 stream IDs, we now mark it as unusable for new streams. Previously,
12100 we would try to close the entire circuit. Bugfix on 0.0.6.
12101 - Make it explicit that we don't cannibalize one-hop circuits. This
12102 happens in the wild, but doesn't turn out to be a problem because
12103 we fortunately don't use those circuits. Many thanks to outofwords
12104 for the initial analysis and to swissknife who confirmed that
12105 two-hop circuits are actually created.
12106 - Resolve an edge case in path weighting that could make us misweight
12107 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
12108 - Make the DNSPort option work with libevent 2.x. Don't alter the
12109 behavior for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
12111 o Minor bugfixes (directory authorities):
12112 - Make directory authorities more accurate at recording when
12113 relays that have failed several reachability tests became
12114 unreachable, so we can provide more accuracy at assigning Stable,
12115 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
12116 - Directory authorities are now more robust to hops back in time
12117 when calculating router stability. Previously, if a run of uptime
12118 or downtime appeared to be negative, the calculation could give
12119 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
12121 - Directory authorities will now attempt to download consensuses
12122 if their own efforts to make a live consensus have failed. This
12123 change means authorities that restart will fetch a valid
12124 consensus, and it means authorities that didn't agree with the
12125 current consensus will still fetch and serve it if it has enough
12126 signatures. Bugfix on 0.2.0.9-alpha; fixes bug 1300.
12127 - Never vote for a server as "Running" if we have a descriptor for
12128 it claiming to be hibernating, and that descriptor was published
12129 more recently than our last contact with the server. Bugfix on
12130 0.2.0.3-alpha; fixes bug 911.
12131 - Directory authorities no longer change their opinion of, or vote on,
12132 whether a router is Running, unless they have themselves been
12133 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
12136 o Minor bugfixes (hidden services):
12137 - Log malformed requests for rendezvous descriptors as protocol
12138 warnings, not warnings. Also, use a more informative log message
12139 in case someone sees it at log level warning without prior
12140 info-level messages. Fixes bug 2748; bugfix on 0.2.0.10-alpha.
12141 - Accept hidden service descriptors if we think we might be a hidden
12142 service directory, regardless of what our consensus says. This
12143 helps robustness, since clients and hidden services can sometimes
12144 have a more up-to-date view of the network consensus than we do,
12145 and if they think that the directory authorities list us a HSDir,
12146 we might actually be one. Related to bug 2732; bugfix on
12148 - Correct the warning displayed when a rendezvous descriptor exceeds
12149 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
12151 - Clients and hidden services now use HSDir-flagged relays for hidden
12152 service descriptor downloads and uploads even if the relays have no
12153 DirPort set and the client has disabled TunnelDirConns. This will
12154 eventually allow us to give the HSDir flag to relays with no
12155 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
12156 - Only limit the lengths of single HS descriptors, even when multiple
12157 HS descriptors are published to an HSDir relay in a single POST
12158 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
12160 o Minor bugfixes (controllers):
12161 - Allow GETINFO fingerprint to return a fingerprint even when
12162 we have not yet built a router descriptor. Fixes bug 3577;
12163 bugfix on 0.2.0.1-alpha.
12164 - Send a SUCCEEDED stream event to the controller when a reverse
12165 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
12166 discovered by katmagic.
12167 - Remove a trailing asterisk from "exit-policy/default" in the
12168 output of the control port command "GETINFO info/names". Bugfix
12170 - Make the SIGNAL DUMP controller command work on FreeBSD. Fixes bug
12171 2917. Bugfix on 0.1.1.1-alpha.
12172 - When we restart our relay, we might get a successful connection
12173 from the outside before we've started our reachability tests,
12174 triggering a warning: "ORPort found reachable, but I have no
12175 routerinfo yet. Failing to inform controller of success." This
12176 bug was harmless unless Tor is running under a controller
12177 like Vidalia, in which case the controller would never get a
12178 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
12180 - When a controller changes TrackHostExits, remove mappings for
12181 hosts that should no longer have their exits tracked. Bugfix on
12183 - When a controller changes VirtualAddrNetwork, remove any mappings
12184 for hosts that were automapped to the old network. Bugfix on
12186 - When a controller changes one of the AutomapHosts* options, remove
12187 any mappings for hosts that should no longer be automapped. Bugfix
12189 - Fix an off-by-one error in calculating some controller command
12190 argument lengths. Fortunately, this mistake is harmless since
12191 the controller code does redundant NUL termination too. Found by
12192 boboper. Bugfix on 0.1.1.1-alpha.
12193 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
12194 would return "551 Internal error" rather than "552 Unrecognized key
12195 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
12196 - Don't spam the controller with events when we have no file
12197 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
12198 for log messages was already solved from bug 748.)
12199 - Emit a GUARD DROPPED controller event for a case we missed.
12200 - Ensure DNS requests launched by "RESOLVE" commands from the
12201 controller respect the __LeaveStreamsUnattached setconf options. The
12202 same goes for requests launched via DNSPort or transparent
12203 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
12205 o Minor bugfixes (config options):
12206 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
12207 Change the limit to 512 characters by removing base64 newlines.
12208 Fixes bug 2752. Fix by Michael Yakubovich.
12209 - Complain if PublishServerDescriptor is given multiple arguments that
12210 include 0 or 1. This configuration will be rejected in the future.
12211 Bugfix on 0.2.0.1-alpha; closes bug 1107.
12212 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
12213 Bugfix on 0.2.0.13-alpha; closes bug 928.
12215 o Minor bugfixes (log subsystem fixes):
12216 - When unable to format an address as a string, report its value
12217 as "???" rather than reusing the last formatted address. Bugfix
12219 - Be more consistent in our treatment of file system paths. "~" should
12220 get expanded to the user's home directory in the Log config option.
12221 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
12222 feature for the -f and --DataDirectory options.
12224 o Minor bugfixes (memory management):
12225 - Don't stack-allocate the list of supplementary GIDs when we're
12226 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
12227 could take up to 256K, which is way too much stack. Found by
12228 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
12229 - Save a couple bytes in memory allocation every time we escape
12230 certain characters in a string. Patch from Florian Zumbiehl.
12232 o Minor bugfixes (protocol correctness):
12233 - When checking for 1024-bit keys, check for 1024 bits, not 128
12234 bytes. This allows Tor to correctly discard keys of length 1017
12235 through 1023. Bugfix on 0.0.9pre5.
12236 - Require that introduction point keys and onion handshake keys
12237 have a public exponent of 65537. Starts to fix bug 3207; bugfix
12239 - Handle SOCKS messages longer than 128 bytes long correctly, rather
12240 than waiting forever for them to finish. Fixes bug 2330; bugfix
12241 on 0.2.0.16-alpha. Found by doorss.
12242 - Never relay a cell for a circuit we have already destroyed.
12243 Between marking a circuit as closeable and finally closing it,
12244 it may have been possible for a few queued cells to get relayed,
12245 even though they would have been immediately dropped by the next
12246 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
12247 - Never queue a cell for a circuit that's already been marked
12249 - Fix a spec conformance issue: the network-status-version token
12250 must be the first token in a v3 consensus or vote. Discovered by
12251 "parakeep". Bugfix on 0.2.0.3-alpha.
12252 - A networkstatus vote must contain exactly one signature. Spec
12253 conformance issue. Bugfix on 0.2.0.3-alpha.
12254 - When asked about a DNS record type we don't support via a
12255 client DNSPort, reply with NOTIMPL rather than an empty
12256 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
12257 - Make more fields in the controller protocol case-insensitive, since
12258 control-spec.txt said they were.
12260 o Minor bugfixes (log messages):
12261 - Fix a log message that said "bits" while displaying a value in
12262 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
12264 - Downgrade "no current certificates known for authority" message from
12265 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
12266 - Correctly describe errors that occur when generating a TLS object.
12267 Previously we would attribute them to a failure while generating a
12268 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
12270 - Fix an instance where a Tor directory mirror might accidentally
12271 log the IP address of a misbehaving Tor client. Bugfix on
12273 - Stop logging at severity 'warn' when some other Tor client tries
12274 to establish a circuit with us using weak DH keys. It's a protocol
12275 violation, but that doesn't mean ordinary users need to hear about
12276 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
12277 - If your relay can't keep up with the number of incoming create
12278 cells, it would log one warning per failure into your logs. Limit
12279 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
12281 o Minor bugfixes (build fixes):
12282 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
12283 - When warning about missing zlib development packages during compile,
12284 give the correct package names. Bugfix on 0.2.0.1-alpha.
12285 - Fix warnings that newer versions of autoconf produce during
12286 ./autogen.sh. These warnings appear to be harmless in our case,
12287 but they were extremely verbose. Fixes bug 2020.
12288 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
12291 o Minor bugfixes (portability):
12292 - Write several files in text mode, on OSes that distinguish text
12293 mode from binary mode (namely, Windows). These files are:
12294 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
12295 that collect those statistics; 'client_keys' and 'hostname' for
12296 hidden services that use authentication; and (in the tor-gencert
12297 utility) newly generated identity and signing keys. Previously,
12298 we wouldn't specify text mode or binary mode, leading to an
12299 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
12300 the DirRecordUsageByCountry option which would have triggered
12301 the assertion failure was added), although this assertion failure
12302 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
12303 - Selectively disable deprecation warnings on OS X because Lion
12304 started deprecating the shipped copy of openssl. Fixes bug 3643.
12305 - Use a wide type to hold sockets when built for 64-bit Windows.
12307 - Fix an issue that prevented static linking of libevent on
12308 some platforms (notably Linux). Fixes bug 2698; bugfix on 0.2.1.23,
12309 where we introduced the "--with-static-libevent" configure option.
12310 - Fix a bug with our locking implementation on Windows that couldn't
12311 correctly detect when a file was already locked. Fixes bug 2504,
12312 bugfix on 0.2.1.6-alpha.
12313 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
12315 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
12316 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
12319 o Minor bugfixes (code correctness):
12320 - Always NUL-terminate the sun_path field of a sockaddr_un before
12321 passing it to the kernel. (Not a security issue: kernels are
12322 smart enough to reject bad sockaddr_uns.) Found by Coverity;
12323 CID #428. Bugfix on Tor 0.2.0.3-alpha.
12324 - Make connection_printf_to_buf()'s behavior sane. Its callers
12325 expect it to emit a CRLF iff the format string ends with CRLF;
12326 it actually emitted a CRLF iff (a) the format string ended with
12327 CRLF or (b) the resulting string was over 1023 characters long or
12328 (c) the format string did not end with CRLF *and* the resulting
12329 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
12330 fixes part of bug 3407.
12331 - Make send_control_event_impl()'s behavior sane. Its callers
12332 expect it to always emit a CRLF at the end of the string; it
12333 might have emitted extra control characters as well. Bugfix on
12334 0.1.1.9-alpha; fixes another part of bug 3407.
12335 - Make crypto_rand_int() check the value of its input correctly.
12336 Previously, it accepted values up to UINT_MAX, but could return a
12337 negative number if given a value above INT_MAX+1. Found by George
12338 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
12339 - Fix a potential null-pointer dereference while computing a
12340 consensus. Bugfix on 0.2.0.3-alpha, found with the help of
12342 - If we fail to compute the identity digest of a v3 legacy keypair,
12343 warn, and don't use a buffer-full of junk instead. Bugfix on
12344 0.2.1.1-alpha; fixes bug 3106.
12345 - Resolve an untriggerable issue in smartlist_string_num_isin(),
12346 where if the function had ever in the future been used to check
12347 for the presence of a too-large number, it would have given an
12348 incorrect result. (Fortunately, we only used it for 16-bit
12349 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
12350 - Be more careful about reporting the correct error from a failed
12351 connect() system call. Under some circumstances, it was possible to
12352 look at an incorrect value for errno when sending the end reason.
12353 Bugfix on 0.1.0.1-rc.
12354 - Correctly handle an "impossible" overflow cases in connection byte
12355 counting, where we write or read more than 4GB on an edge connection
12356 in a single second. Bugfix on 0.1.2.8-beta.
12357 - Avoid a double mark-for-free warning when failing to attach a
12358 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
12360 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
12361 found by "cypherpunks". This bug was introduced before the first
12362 Tor release, in svn commit r110.
12363 - Fix a bug in bandwidth history state parsing that could have been
12364 triggered if a future version of Tor ever changed the timing
12365 granularity at which bandwidth history is measured. Bugfix on
12366 Tor 0.1.1.11-alpha.
12367 - Add assertions to check for overflow in arguments to
12368 base32_encode() and base32_decode(); fix a signed-unsigned
12369 comparison there too. These bugs are not actually reachable in Tor,
12370 but it's good to prevent future errors too. Found by doorss.
12371 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
12373 - Set target port in get_interface_address6() correctly. Bugfix
12374 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
12375 - Fix an impossible-to-actually-trigger buffer overflow in relay
12376 descriptor generation. Bugfix on 0.1.0.15.
12377 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
12379 o Minor bugfixes (code improvements):
12380 - After we free an internal connection structure, overwrite it
12381 with a different memory value than we use for overwriting a freed
12382 internal circuit structure. Should help with debugging. Suggested
12384 - If OpenSSL fails to make a duplicate of a private or public key, log
12385 an error message and try to exit cleanly. May help with debugging
12386 if bug 1209 ever remanifests.
12387 - Some options used different conventions for uppercasing of acronyms
12388 when comparing manpage and source. Fix those in favor of the
12389 manpage, as it makes sense to capitalize acronyms.
12390 - Take a first step towards making or.h smaller by splitting out
12391 function definitions for all source files in src/or/. Leave
12392 structures and defines in or.h for now.
12393 - Remove a few dead assignments during router parsing. Found by
12395 - Don't use 1-bit wide signed bit fields. Found by coverity.
12396 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
12397 None of the cases where we did this before were wrong, but by making
12398 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
12399 - The memarea code now uses a sentinel value at the end of each area
12400 to make sure nothing writes beyond the end of an area. This might
12401 help debug some conceivable causes of bug 930.
12402 - Always treat failure to allocate an RSA key as an unrecoverable
12404 - Add some more defensive programming for architectures that can't
12405 handle unaligned integer accesses. We don't know of any actual bugs
12406 right now, but that's the best time to fix them. Fixes bug 1943.
12408 o Minor bugfixes (misc):
12409 - Fix a rare bug in rend_fn unit tests: we would fail a test when
12410 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
12411 on 0.2.0.10-alpha; fixes bug 1808.
12412 - Where available, use Libevent 2.0's periodic timers so that our
12413 once-per-second cleanup code gets called even more closely to
12414 once per second than it would otherwise. Fixes bug 943.
12415 - Ignore OutboundBindAddress when connecting to localhost.
12416 Connections to localhost need to come _from_ localhost, or else
12417 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
12419 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
12421 - If any of the v3 certs we download are unparseable, we should
12422 actually notice the failure so we don't retry indefinitely. Bugfix
12423 on 0.2.0.x; reported by "rotator".
12424 - When Tor fails to parse a descriptor of any kind, dump it to disk.
12425 Might help diagnosing bug 1051.
12426 - Make our 'torify' script more portable; if we have only one of
12427 'torsocks' or 'tsocks' installed, don't complain to the user;
12428 and explain our warning about tsocks better.
12429 - Fix some urls in the exit notice file and make it XHTML1.1 strict
12430 compliant. Based on a patch from Christian Kujau.
12432 o Documentation changes:
12433 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
12434 - Resolve all doxygen warnings except those for missing documentation.
12436 - Add doxygen documentation for more functions, fields, and types.
12437 - Convert the HACKING file to asciidoc, and add a few new sections
12438 to it, explaining how we use Git, how we make changelogs, and
12439 what should go in a patch.
12440 - Document the default socks host and port (127.0.0.1:9050) for
12442 - Removed some unnecessary files from the source distribution. The
12443 AUTHORS file has now been merged into the people page on the
12444 website. The roadmaps and design doc can now be found in the
12445 projects directory in svn.
12447 o Deprecated and removed features (config):
12448 - Remove the torrc.complete file. It hasn't been kept up to date
12449 and users will have better luck checking out the manpage.
12450 - Remove the HSAuthorityRecordStats option that version 0 hidden
12451 service authorities could use to track statistics of overall v0
12452 hidden service usage.
12453 - Remove the obsolete "NoPublish" option; it has been flagged
12454 as obsolete and has produced a warning since 0.1.1.18-rc.
12455 - Caches no longer download and serve v2 networkstatus documents
12456 unless FetchV2Networkstatus flag is set: these documents haven't
12457 haven't been used by clients or relays since 0.2.0.x. Resolves
12460 o Deprecated and removed features (controller):
12461 - The controller no longer accepts the old obsolete "addr-mappings/"
12462 or "unregistered-servers-" GETINFO values.
12463 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
12464 always on; using them is necessary for correct forward-compatible
12467 o Deprecated and removed features (misc):
12468 - Hidden services no longer publish version 0 descriptors, and clients
12469 do not request or use version 0 descriptors. However, the old hidden
12470 service authorities still accept and serve version 0 descriptors
12471 when contacted by older hidden services/clients.
12472 - Remove undocumented option "-F" from tor-resolve: it hasn't done
12473 anything since 0.2.1.16-rc.
12474 - Remove everything related to building the expert bundle for OS X.
12475 It has confused many users, doesn't work right on OS X 10.6,
12476 and is hard to get rid of once installed. Resolves bug 1274.
12477 - Remove support for .noconnect style addresses. Nobody was using
12478 them, and they provided another avenue for detecting Tor users
12479 via application-level web tricks.
12480 - When we fixed bug 1038 we had to put in a restriction not to send
12481 RELAY_EARLY cells on rend circuits. This was necessary as long
12482 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
12483 active. Now remove this obsolete check. Resolves bug 2081.
12484 - Remove workaround code to handle directory responses from servers
12485 that had bug 539 (they would send HTTP status 503 responses _and_
12486 send a body too). Since only server versions before
12487 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
12488 keep the workaround in place.
12489 - Remove the old 'fuzzy time' logic. It was supposed to be used for
12490 handling calculations where we have a known amount of clock skew and
12491 an allowed amount of unknown skew. But we only used it in three
12492 places, and we never adjusted the known/unknown skew values. This is
12493 still something we might want to do someday, but if we do, we'll
12494 want to do it differently.
12495 - Remove the "--enable-iphone" option to ./configure. According to
12496 reports from Marco Bonetti, Tor builds fine without any special
12497 tweaking on recent iPhone SDK versions.
12500 Changes in version 0.2.1.30 - 2011-02-23
12501 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
12502 change is a slight tweak to Tor's TLS handshake that makes relays
12503 and bridges that run this new version reachable from Iran again.
12504 We don't expect this tweak will win the arms race long-term, but it
12505 buys us time until we roll out a better solution.
12508 - Stop sending a CLOCK_SKEW controller status event whenever
12509 we fetch directory information from a relay that has a wrong clock.
12510 Instead, only inform the controller when it's a trusted authority
12511 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
12512 the rest of bug 1074.
12513 - Fix a bounds-checking error that could allow an attacker to
12514 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
12515 Found by "piebeer".
12516 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
12517 Tor would ignore their RelayBandwidthBurst setting,
12518 potentially using more bandwidth than expected. Bugfix on
12519 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
12520 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
12521 hidserv" in her torrc. The 'hidserv' argument never controlled
12522 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
12525 - Adjust our TLS Diffie-Hellman parameters to match those used by
12527 - Update to the February 1 2011 Maxmind GeoLite Country database.
12530 - Check for and reject overly long directory certificates and
12531 directory tokens before they have a chance to hit any assertions.
12532 Bugfix on 0.2.1.28. Found by "doorss".
12533 - Bring the logic that gathers routerinfos and assesses the
12534 acceptability of circuits into line. This prevents a Tor OP from
12535 getting locked in a cycle of choosing its local OR as an exit for a
12536 path (due to a .exit request) and then rejecting the circuit because
12537 its OR is not listed yet. It also prevents Tor clients from using an
12538 OR running in the same instance as an exit (due to a .exit request)
12539 if the OR does not meet the same requirements expected of an OR
12540 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
12542 o Packaging changes:
12543 - Stop shipping the Tor specs files and development proposal documents
12544 in the tarball. They are now in a separate git repository at
12545 git://git.torproject.org/torspec.git
12546 - Do not include Git version tags as though they are SVN tags when
12547 generating a tarball from inside a repository that has switched
12548 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
12551 Changes in version 0.2.1.29 - 2011-01-15
12552 Tor 0.2.1.29 continues our recent code security audit work. The main
12553 fix resolves a remote heap overflow vulnerability that can allow remote
12554 code execution. Other fixes address a variety of assert and crash bugs,
12555 most of which we think are hard to exploit remotely.
12557 o Major bugfixes (security):
12558 - Fix a heap overflow bug where an adversary could cause heap
12559 corruption. This bug probably allows remote code execution
12560 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
12562 - Prevent a denial-of-service attack by disallowing any
12563 zlib-compressed data whose compression factor is implausibly
12564 high. Fixes part of bug 2324; reported by "doorss".
12565 - Zero out a few more keys in memory before freeing them. Fixes
12566 bug 2384 and part of bug 2385. These key instances found by
12567 "cypherpunks", based on Andrew Case's report about being able
12568 to find sensitive data in Tor's memory space if you have enough
12569 permissions. Bugfix on 0.0.2pre9.
12571 o Major bugfixes (crashes):
12572 - Prevent calls to Libevent from inside Libevent log handlers.
12573 This had potential to cause a nasty set of crashes, especially
12574 if running Libevent with debug logging enabled, and running
12575 Tor with a controller watching for low-severity log messages.
12576 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
12577 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
12578 underflow errors there too. Fixes the other part of bug 2324.
12579 - Fix a bug where we would assert if we ever had a
12580 cached-descriptors.new file (or another file read directly into
12581 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
12582 on 0.2.1.25. Found by doorss.
12583 - Fix some potential asserts and parsing issues with grossly
12584 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
12587 o Minor bugfixes (other):
12588 - Fix a bug with handling misformed replies to reverse DNS lookup
12589 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
12590 bug reported by doorss.
12591 - Fix compilation on mingw when a pthreads compatibility library
12592 has been installed. (We don't want to use it, so we shouldn't
12593 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
12594 - Fix a bug where we would declare that we had run out of virtual
12595 addresses when the address space was only half-exhausted. Bugfix
12597 - Correctly handle the case where AutomapHostsOnResolve is set but
12598 no virtual addresses are available. Fixes bug 2328; bugfix on
12599 0.1.2.1-alpha. Bug found by doorss.
12600 - Correctly handle wrapping around when we run out of virtual
12601 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
12604 - Update to the January 1 2011 Maxmind GeoLite Country database.
12605 - Introduce output size checks on all of our decryption functions.
12608 - Tor does not build packages correctly with Automake 1.6 and earlier;
12609 added a check to Makefile.am to make sure that we're building with
12610 Automake 1.7 or later.
12611 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
12612 because we built it with a too-old version of automake. Thus that
12613 release broke ./configure --enable-openbsd-malloc, which is popular
12614 among really fast exit relays on Linux.
12617 Changes in version 0.2.1.28 - 2010-12-17
12618 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
12619 exploitable bugs. We also took this opportunity to change the IP address
12620 for one of our directory authorities, and to update the geoip database
12624 - Fix a remotely exploitable bug that could be used to crash instances
12625 of Tor remotely by overflowing on the heap. Remote-code execution
12626 hasn't been confirmed, but can't be ruled out. Everyone should
12627 upgrade. Bugfix on the 0.1.1 series and later.
12629 o Directory authority changes:
12630 - Change IP address and ports for gabelmoo (v3 directory authority).
12633 - Update to the December 1 2010 Maxmind GeoLite Country database.
12636 Changes in version 0.2.1.27 - 2010-11-23
12637 Yet another OpenSSL security patch broke its compatibility with Tor:
12638 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
12639 also took this opportunity to fix several crash bugs, integrate a new
12640 directory authority, and update the bundled GeoIP database.
12643 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
12644 No longer set the tlsext_host_name extension on server SSL objects;
12645 but continue to set it on client SSL objects. Our goal in setting
12646 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
12647 bugfix on 0.2.1.1-alpha.
12648 - Do not log messages to the controller while shrinking buffer
12649 freelists. Doing so would sometimes make the controller connection
12650 try to allocate a buffer chunk, which would mess up the internals
12651 of the freelist and cause an assertion failure. Fixes bug 1125;
12652 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
12653 - Learn our external IP address when we're a relay or bridge, even if
12654 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
12655 where we introduced bridge relays that don't need to publish to
12656 be useful. Fixes bug 2050.
12657 - Do even more to reject (and not just ignore) annotations on
12658 router descriptors received anywhere but from the cache. Previously
12659 we would ignore such annotations at first, but cache them to disk
12660 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
12661 - When you're using bridges and your network goes away and your
12662 bridges get marked as down, recover when you attempt a new socks
12663 connection (if the network is back), rather than waiting up to an
12664 hour to try fetching new descriptors for your bridges. Bugfix on
12665 0.2.0.3-alpha; fixes bug 1981.
12668 - Move to the November 2010 Maxmind GeoLite country db (rather
12669 than the June 2009 ip-to-country GeoIP db) for our statistics that
12670 count how many users relays are seeing from each country. Now we'll
12671 have more accurate data, especially for many African countries.
12673 o New directory authorities:
12674 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
12678 - Fix an assertion failure that could occur in directory caches or
12679 bridge users when using a very short voting interval on a testing
12680 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
12682 - Enforce multiplicity rules when parsing annotations. Bugfix on
12683 0.2.0.8-alpha. Found by piebeer.
12684 - Allow handshaking OR connections to take a full KeepalivePeriod
12685 seconds to handshake. Previously, we would close them after
12686 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
12687 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
12689 - When building with --enable-gcc-warnings on OpenBSD, disable
12690 warnings in system headers. This makes --enable-gcc-warnings
12691 pass on OpenBSD 4.8.
12694 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
12695 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
12696 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
12697 Servers can start sending this code when enough clients recognize
12698 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
12699 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
12700 Patch from mingw-san.
12703 - Remove the old debian/ directory from the main Tor distribution.
12704 The official Tor-for-debian git repository lives at the URL
12705 https://git.torproject.org/debian/tor.git
12706 - Stop shipping the old doc/website/ directory in the tarball. We
12707 changed the website format in late 2010, and what we shipped in
12708 0.2.1.26 really wasn't that useful anyway.
12711 Changes in version 0.2.1.26 - 2010-05-02
12712 Tor 0.2.1.26 addresses the recent connection and memory overload
12713 problems we've been seeing on relays, especially relays with their
12714 DirPort open. If your relay has been crashing, or you turned it off
12715 because it used too many resources, give this release a try.
12717 This release also fixes yet another instance of broken OpenSSL libraries
12718 that was causing some relays to drop out of the consensus.
12721 - Teach relays to defend themselves from connection overload. Relays
12722 now close idle circuits early if it looks like they were intended
12723 for directory fetches. Relays are also more aggressive about closing
12724 TLS connections that have no circuits on them. Such circuits are
12725 unlikely to be re-used, and tens of thousands of them were piling
12726 up at the fast relays, causing the relays to run out of sockets
12727 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
12728 their directory fetches over TLS).
12729 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
12730 that claim to be earlier than 0.9.8m, but which have in reality
12731 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
12732 behavior. Possible fix for some cases of bug 1346.
12733 - Directory mirrors were fetching relay descriptors only from v2
12734 directory authorities, rather than v3 authorities like they should.
12735 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
12736 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
12739 - Finally get rid of the deprecated and now harmful notion of "clique
12740 mode", where directory authorities maintain TLS connections to
12744 - In the util/threads test, no longer free the test_mutex before all
12745 worker threads have finished. Bugfix on 0.2.1.6-alpha.
12746 - The master thread could starve the worker threads quite badly on
12747 certain systems, causing them to run only partially in the allowed
12748 window. This resulted in test failures. Now the master thread sleeps
12749 occasionally for a few microseconds while the two worker-threads
12750 compete for the mutex. Bugfix on 0.2.0.1-alpha.
12753 Changes in version 0.2.1.25 - 2010-03-16
12754 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
12755 prevent relays from guessing their IP address correctly. It also fixes
12756 several minor potential security bugs.
12759 - Fix a regression from our patch for bug 1244 that caused relays
12760 to guess their IP address incorrectly if they didn't set Address
12761 in their torrc and/or their address fails to resolve. Bugfix on
12762 0.2.1.23; fixes bug 1269.
12763 - When freeing a session key, zero it out completely. We only zeroed
12764 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
12765 patched by ekir. Fixes bug 1254.
12768 - Fix a dereference-then-NULL-check sequence when publishing
12769 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
12771 - Fix another dereference-then-NULL-check sequence. Bugfix on
12772 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
12773 - Make sure we treat potentially not NUL-terminated strings correctly.
12774 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
12777 Changes in version 0.2.1.24 - 2010-02-21
12778 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
12782 - Work correctly out-of-the-box with even more vendor-patched versions
12783 of OpenSSL. In particular, make it so Debian and OS X don't need
12784 customized patches to run/build.
12787 Changes in version 0.2.1.23 - 2010-02-13
12788 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
12789 again on the latest OS X, and updates the location of a directory
12792 o Major bugfixes (performance):
12793 - We were selecting our guards uniformly at random, and then weighting
12794 which of our guards we'd use uniformly at random. This imbalance
12795 meant that Tor clients were severely limited on throughput (and
12796 probably latency too) by the first hop in their circuit. Now we
12797 select guards weighted by currently advertised bandwidth. We also
12798 automatically discard guards picked using the old algorithm. Fixes
12799 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
12802 - Make Tor work again on the latest OS X: when deciding whether to
12803 use strange flags to turn TLS renegotiation on, detect the OpenSSL
12804 version at run-time, not compile time. We need to do this because
12805 Apple doesn't update its dev-tools headers when it updates its
12806 libraries in a security patch.
12807 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
12808 that could happen on 32-bit platforms with 64-bit time_t. Also fix
12809 a memory leak when requesting a hidden service descriptor we've
12810 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
12814 - Refactor resolve_my_address() to not use gethostbyname() anymore.
12815 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
12818 - Avoid a mad rush at the beginning of each month when each client
12819 rotates half of its guards. Instead we spread the rotation out
12820 throughout the month, but we still avoid leaving a precise timestamp
12821 in the state file about when we first picked the guard. Improves
12822 over the behavior introduced in 0.1.2.17.
12825 Changes in version 0.2.1.22 - 2010-01-19
12826 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
12827 authorities -- it would tell you its whole history of bridge descriptors
12828 if you make the right directory request. This stable update also
12829 rotates two of the seven v3 directory authority keys and locations.
12831 o Directory authority changes:
12832 - Rotate keys (both v3 identity and relay identity) for moria1
12836 - Stop bridge directory authorities from answering dbg-stability.txt
12837 directory queries, which would let people fetch a list of all
12838 bridge identities they track. Bugfix on 0.2.1.6-alpha.
12841 Changes in version 0.2.1.21 - 2009-12-21
12842 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
12843 library. If you use Tor on Linux / Unix and you're getting SSL
12844 renegotiation errors, upgrading should help. We also recommend an
12845 upgrade if you're an exit relay.
12848 - Work around a security feature in OpenSSL 0.9.8l that prevents our
12849 handshake from working unless we explicitly tell OpenSSL that we
12850 are using SSL renegotiation safely. We are, of course, but OpenSSL
12851 0.9.8l won't work unless we say we are.
12852 - Avoid crashing if the client is trying to upload many bytes and the
12853 circuit gets torn down at the same time, or if the flip side
12854 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
12857 - Do not refuse to learn about authority certs and v2 networkstatus
12858 documents that are older than the latest consensus. This bug might
12859 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
12860 Spotted and fixed by xmux.
12861 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
12862 trigger platform-specific option misparsing case found by Coverity
12864 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
12865 trigger assert. Fixes bug 1173.
12868 Changes in version 0.2.1.20 - 2009-10-15
12869 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
12870 services at once, prepares for more performance improvements, and
12871 fixes a bunch of smaller bugs.
12873 The Windows and OS X bundles also include a more recent Vidalia,
12874 and switch from Privoxy to Polipo.
12876 The OS X installers are now drag and drop. It's best to un-install
12877 Tor/Vidalia and then install this new bundle, rather than upgrade. If
12878 you want to upgrade, you'll need to update the paths for Tor and Polipo
12879 in the Vidalia Settings window.
12882 - Send circuit or stream sendme cells when our window has decreased
12883 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
12884 by Karsten when testing the "reduce circuit window" performance
12885 patch. Bugfix on the 54th commit on Tor -- from July 2002,
12886 before the release of Tor 0.0.0. This is the new winner of the
12888 - Fix a remotely triggerable memory leak when a consensus document
12889 contains more than one signature from the same voter. Bugfix on
12891 - Avoid segfault in rare cases when finishing an introduction circuit
12892 as a client and finding out that we don't have an introduction key
12893 for it. Fixes bug 1073. Reported by Aaron Swartz.
12896 - Tor now reads the "circwindow" parameter out of the consensus,
12897 and uses that value for its circuit package window rather than the
12898 default of 1000 cells. Begins the implementation of proposal 168.
12900 o New directory authorities:
12901 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
12903 - Move moria1 and tonga to alternate IP addresses.
12906 - Fix a signed/unsigned compile warning in 0.2.1.19.
12907 - Fix possible segmentation fault on directory authorities. Bugfix on
12909 - Fix an extremely rare infinite recursion bug that could occur if
12910 we tried to log a message after shutting down the log subsystem.
12911 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
12912 - Fix an obscure bug where hidden services on 64-bit big-endian
12913 systems might mis-read the timestamp in v3 introduce cells, and
12914 refuse to connect back to the client. Discovered by "rotor".
12915 Bugfix on 0.2.1.6-alpha.
12916 - We were triggering a CLOCK_SKEW controller status event whenever
12917 we connect via the v2 connection protocol to any relay that has
12918 a wrong clock. Instead, we should only inform the controller when
12919 it's a trusted authority that claims our clock is wrong. Bugfix
12920 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
12921 - We were telling the controller about CHECKING_REACHABILITY and
12922 REACHABILITY_FAILED status events whenever we launch a testing
12923 circuit or notice that one has failed. Instead, only tell the
12924 controller when we want to inform the user of overall success or
12925 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
12927 - Don't warn when we're using a circuit that ends with a node
12928 excluded in ExcludeExitNodes, but the circuit is not used to access
12929 the outside world. This should help fix bug 1090. Bugfix on
12931 - Work around a small memory leak in some versions of OpenSSL that
12932 stopped the memory used by the hostname TLS extension from being
12936 - Add a "getinfo status/accepted-server-descriptor" controller
12937 command, which is the recommended way for controllers to learn
12938 whether our server descriptor has been successfully received by at
12939 least on directory authority. Un-recommend good-server-descriptor
12940 getinfo and status events until we have a better design for them.
12943 Changes in version 0.2.1.19 - 2009-07-28
12944 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
12948 - Make accessing hidden services on 0.2.1.x work right again.
12949 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
12950 part of patch provided by "optimist".
12953 - When a relay/bridge is writing out its identity key fingerprint to
12954 the "fingerprint" file and to its logs, write it without spaces. Now
12955 it will look like the fingerprints in our bridges documentation,
12956 and confuse fewer users.
12959 - Relays no longer publish a new server descriptor if they change
12960 their MaxAdvertisedBandwidth config option but it doesn't end up
12961 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
12962 fixes bug 1026. Patch from Sebastian.
12963 - Avoid leaking memory every time we get a create cell but we have
12964 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
12965 fixes bug 1034. Reported by BarkerJr.
12968 Changes in version 0.2.1.18 - 2009-07-24
12969 Tor 0.2.1.18 lays the foundations for performance improvements,
12970 adds status events to help users diagnose bootstrap problems, adds
12971 optional authentication/authorization for hidden services, fixes a
12972 variety of potential anonymity problems, and includes a huge pile of
12973 other features and bug fixes.
12975 o Major features (clients):
12976 - Start sending "bootstrap phase" status events to the controller,
12977 so it can keep the user informed of progress fetching directory
12978 information and establishing circuits. Also inform the controller
12979 if we think we're stuck at a particular bootstrap phase. Implements
12981 - Clients replace entry guards that were chosen more than a few months
12982 ago. This change should significantly improve client performance,
12983 especially once more people upgrade, since relays that have been
12984 a guard for a long time are currently overloaded.
12985 - Network status consensus documents and votes now contain bandwidth
12986 information for each relay. Clients use the bandwidth values
12987 in the consensus, rather than the bandwidth values in each
12988 relay descriptor. This approach opens the door to more accurate
12989 bandwidth estimates once the directory authorities start doing
12990 active measurements. Implements part of proposal 141.
12992 o Major features (relays):
12993 - Disable and refactor some debugging checks that forced a linear scan
12994 over the whole server-side DNS cache. These accounted for over 50%
12995 of CPU time on a relatively busy exit node's gprof profile. Also,
12996 disable some debugging checks that appeared in exit node profile
12997 data. Found by Jacob.
12998 - New DirPortFrontPage option that takes an html file and publishes
12999 it as "/" on the DirPort. Now relay operators can provide a
13000 disclaimer without needing to set up a separate webserver. There's
13001 a sample disclaimer in contrib/tor-exit-notice.html.
13003 o Major features (hidden services):
13004 - Make it possible to build hidden services that only certain clients
13005 are allowed to connect to. This is enforced at several points,
13006 so that unauthorized clients are unable to send INTRODUCE cells
13007 to the service, or even (depending on the type of authentication)
13008 to learn introduction points. This feature raises the bar for
13009 certain kinds of active attacks against hidden services. Design
13010 and code by Karsten Loesing. Implements proposal 121.
13011 - Relays now store and serve v2 hidden service descriptors by default,
13012 i.e., the new default value for HidServDirectoryV2 is 1. This is
13013 the last step in proposal 114, which aims to make hidden service
13014 lookups more reliable.
13016 o Major features (path selection):
13017 - ExitNodes and Exclude*Nodes config options now allow you to restrict
13018 by country code ("{US}") or IP address or address pattern
13019 ("255.128.0.0/16"). Patch from Robert Hogan. It still needs some
13020 refinement to decide what config options should take priority if
13021 you ask to both use a particular node and exclude it.
13023 o Major features (misc):
13024 - When building a consensus, do not include routers that are down.
13025 This cuts down 30% to 40% on consensus size. Implements proposal
13027 - New TestingTorNetwork config option to allow adjustment of
13028 previously constant values that could slow bootstrapping. Implements
13029 proposal 135. Patch from Karsten.
13030 - Convert many internal address representations to optionally hold
13031 IPv6 addresses. Generate and accept IPv6 addresses in many protocol
13032 elements. Make resolver code handle nameservers located at IPv6
13034 - More work on making our TLS handshake blend in: modify the list
13035 of ciphers advertised by OpenSSL in client mode to even more
13036 closely resemble a common web browser. We cheat a little so that
13037 we can advertise ciphers that the locally installed OpenSSL doesn't
13039 - Use the TLS1 hostname extension to more closely resemble browser
13042 o Security fixes (anonymity/entropy):
13043 - Never use a connection with a mismatched address to extend a
13044 circuit, unless that connection is canonical. A canonical
13045 connection is one whose address is authenticated by the router's
13046 identity key, either in a NETINFO cell or in a router descriptor.
13047 - Implement most of proposal 110: The first K cells to be sent
13048 along a circuit are marked as special "early" cells; only K "early"
13049 cells will be allowed. Once this code is universal, we can block
13050 certain kinds of denial-of-service attack by requiring that EXTEND
13051 commands must be sent using an "early" cell.
13052 - Resume using OpenSSL's RAND_poll() for better (and more portable)
13053 cross-platform entropy collection again. We used to use it, then
13054 stopped using it because of a bug that could crash systems that
13055 called RAND_poll when they had a lot of fds open. It looks like the
13056 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
13057 at startup, and to call RAND_poll() when we reseed later only if
13058 we have a non-buggy OpenSSL version.
13059 - When the client is choosing entry guards, now it selects at most
13060 one guard from a given relay family. Otherwise we could end up with
13061 all of our entry points into the network run by the same operator.
13062 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
13063 - Do not use or believe expired v3 authority certificates. Patch
13064 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
13065 - Drop begin cells to a hidden service if they come from the middle
13066 of a circuit. Patch from lark.
13067 - When we erroneously receive two EXTEND cells for the same circuit
13068 ID on the same connection, drop the second. Patch from lark.
13069 - Authorities now vote for the Stable flag for any router whose
13070 weighted MTBF is at least 5 days, regardless of the mean MTBF.
13071 - Clients now never report any stream end reason except 'MISC'.
13072 Implements proposal 148.
13074 o Major bugfixes (crashes):
13075 - Parse dates and IPv4 addresses in a locale- and libc-independent
13076 manner, to avoid platform-dependent behavior on malformed input.
13077 - Fix a crash that occurs on exit nodes when a nameserver request
13078 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
13079 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
13081 - Do not assume that a stack-allocated character array will be
13082 64-bit aligned on platforms that demand that uint64_t access is
13083 aligned. Possible fix for bug 604.
13084 - Resolve a very rare crash bug that could occur when the user forced
13085 a nameserver reconfiguration during the middle of a nameserver
13086 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
13087 - Avoid a "0 divided by 0" calculation when calculating router uptime
13088 at directory authorities. Bugfix on 0.2.0.8-alpha.
13089 - Fix an assertion bug in parsing policy-related options; possible fix
13091 - Rate-limit too-many-sockets messages: when they happen, they happen
13092 a lot and end up filling up the disk. Resolves bug 748.
13093 - Fix a race condition that could cause crashes or memory corruption
13094 when running as a server with a controller listening for log
13096 - Avoid crashing when we have a policy specified in a DirPolicy or
13097 SocksPolicy or ReachableAddresses option with ports set on it,
13098 and we re-load the policy. May fix bug 996.
13099 - Fix an assertion failure on 64-bit platforms when we allocated
13100 memory right up to the end of a memarea, then realigned the memory
13101 one step beyond the end. Fixes a possible cause of bug 930.
13102 - Protect the count of open sockets with a mutex, so we can't
13103 corrupt it when two threads are closing or opening sockets at once.
13104 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
13106 o Major bugfixes (clients):
13107 - Discard router descriptors as we load them if they are more than
13108 five days old. Otherwise if Tor is off for a long time and then
13109 starts with cached descriptors, it will try to use the onion keys
13110 in those obsolete descriptors when building circuits. Fixes bug 887.
13111 - When we choose to abandon a new entry guard because we think our
13112 older ones might be better, close any circuits pending on that
13113 new entry guard connection. This fix should make us recover much
13114 faster when our network is down and then comes back. Bugfix on
13115 0.1.2.8-beta; found by lodger.
13116 - When Tor clients restart after 1-5 days, they discard all their
13117 cached descriptors as too old, but they still use the cached
13118 consensus document. This approach is good for robustness, but
13119 bad for performance: since they don't know any bandwidths, they
13120 end up choosing at random rather than weighting their choice by
13121 speed. Fixed by the above feature of putting bandwidths in the
13124 o Major bugfixes (relays):
13125 - Relays were falling out of the networkstatus consensus for
13126 part of a day if they changed their local config but the
13127 authorities discarded their new descriptor as "not sufficiently
13128 different". Now directory authorities accept a descriptor as changed
13129 if BandwidthRate or BandwidthBurst changed. Partial fix for bug 962;
13130 patch by Sebastian.
13131 - Ensure that two circuits can never exist on the same connection
13132 with the same circuit ID, even if one is marked for close. This
13133 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
13134 - Directory authorities were neglecting to mark relays down in their
13135 internal histories if the relays fall off the routerlist without
13136 ever being found unreachable. So there were relays in the histories
13137 that haven't been seen for eight months, and are listed as being
13138 up for eight months. This wreaked havoc on the "median wfu" and
13139 "median mtbf" calculations, in turn making Guard and Stable flags
13140 wrong, hurting network performance. Fixes bugs 696 and 969. Bugfix
13143 o Major bugfixes (hidden services):
13144 - When establishing a hidden service, introduction points that
13145 originate from cannibalized circuits were completely ignored
13146 and not included in rendezvous service descriptors. This might
13147 have been another reason for delay in making a hidden service
13148 available. Bugfix from long ago (0.0.9.x?)
13150 o Major bugfixes (memory and resource management):
13151 - Fixed some memory leaks -- some quite frequent, some almost
13152 impossible to trigger -- based on results from Coverity.
13153 - Speed up parsing and cut down on memory fragmentation by using
13154 stack-style allocations for parsing directory objects. Previously,
13155 this accounted for over 40% of allocations from within Tor's code
13156 on a typical directory cache.
13157 - Use a Bloom filter rather than a digest-based set to track which
13158 descriptors we need to keep around when we're cleaning out old
13159 router descriptors. This speeds up the computation significantly,
13160 and may reduce fragmentation.
13162 o New/changed config options:
13163 - Now NodeFamily and MyFamily config options allow spaces in
13164 identity fingerprints, so it's easier to paste them in.
13165 Suggested by Lucky Green.
13166 - Allow ports 465 and 587 in the default exit policy again. We had
13167 rejected them in 0.1.0.15, because back in 2005 they were commonly
13168 misconfigured and ended up as spam targets. We hear they are better
13169 locked down these days.
13170 - Make TrackHostExit mappings expire a while after their last use, not
13171 after their creation. Patch from Robert Hogan.
13172 - Add an ExcludeExitNodes option so users can list a set of nodes
13173 that should be be excluded from the exit node position, but
13174 allowed elsewhere. Implements proposal 151.
13175 - New --hush command-line option similar to --quiet. While --quiet
13176 disables all logging to the console on startup, --hush limits the
13177 output to messages of warning and error severity.
13178 - New configure/torrc options (--enable-geoip-stats,
13179 DirRecordUsageByCountry) to record how many IPs we've served
13180 directory info to in each country code, how many status documents
13181 total we've sent to each country code, and what share of the total
13182 directory requests we should expect to see.
13183 - Make outbound DNS packets respect the OutboundBindAddress setting.
13184 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
13185 - Allow separate log levels to be configured for different logging
13186 domains. For example, this allows one to log all notices, warnings,
13187 or errors, plus all memory management messages of level debug or
13188 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
13189 - Update to the "June 3 2009" ip-to-country file.
13191 o Minor features (relays):
13192 - Raise the minimum rate limiting to be a relay from 20000 bytes
13193 to 20480 bytes (aka 20KB/s), to match our documentation. Also
13194 update directory authorities so they always assign the Fast flag
13195 to relays with 20KB/s of capacity. Now people running relays won't
13196 suddenly find themselves not seeing any use, if the network gets
13198 - If we're a relay and we change our IP address, be more verbose
13199 about the reason that made us change. Should help track down
13200 further bugs for relays on dynamic IP addresses.
13201 - Exit servers can now answer resolve requests for ip6.arpa addresses.
13202 - Implement most of Proposal 152: allow specialized servers to permit
13203 single-hop circuits, and clients to use those servers to build
13204 single-hop circuits when using a specialized controller. Patch
13205 from Josh Albrecht. Resolves feature request 768.
13206 - When relays do their initial bandwidth measurement, don't limit
13207 to just our entry guards for the test circuits. Otherwise we tend
13208 to have multiple test circuits going through a single entry guard,
13209 which makes our bandwidth test less accurate. Fixes part of bug 654;
13210 patch contributed by Josh Albrecht.
13212 o Minor features (directory authorities):
13213 - Try not to open more than one descriptor-downloading connection
13214 to an authority at once. This should reduce load on directory
13215 authorities. Fixes bug 366.
13216 - Add cross-certification to newly generated certificates, so that
13217 a signing key is enough information to look up a certificate. Start
13218 serving certificates by <identity digest, signing key digest>
13219 pairs. Implements proposal 157.
13220 - When a directory authority downloads a descriptor that it then
13221 immediately rejects, do not retry downloading it right away. Should
13222 save some bandwidth on authorities. Fix for bug 888. Patch by
13224 - Directory authorities now serve a /tor/dbg-stability.txt URL to
13225 help debug WFU and MTBF calculations.
13226 - In directory authorities' approved-routers files, allow
13227 fingerprints with or without space.
13229 o Minor features (directory mirrors):
13230 - When a download gets us zero good descriptors, do not notify
13231 Tor that new directory information has arrived.
13232 - Servers support a new URL scheme for consensus downloads that
13233 allows the client to specify which authorities are trusted.
13234 The server then only sends the consensus if the client will trust
13235 it. Otherwise a 404 error is sent back. Clients use this
13236 new scheme when the server supports it (meaning it's running
13237 0.2.1.1-alpha or later). Implements proposal 134.
13239 o Minor features (bridges):
13240 - If the bridge config line doesn't specify a port, assume 443.
13241 This makes bridge lines a bit smaller and easier for users to
13243 - If we're using bridges and our network goes away, be more willing
13244 to forgive our bridges and try again when we get an application
13247 o Minor features (hidden services):
13248 - When the client launches an introduction circuit, retry with a
13249 new circuit after 30 seconds rather than 60 seconds.
13250 - Launch a second client-side introduction circuit in parallel
13251 after a delay of 15 seconds (based on work by Christian Wilms).
13252 - Hidden services start out building five intro circuits rather
13253 than three, and when the first three finish they publish a service
13254 descriptor using those. Now we publish our service descriptor much
13255 faster after restart.
13256 - Drop the requirement to have an open dir port for storing and
13257 serving v2 hidden service descriptors.
13259 o Minor features (build and packaging):
13260 - On Linux, use the prctl call to re-enable core dumps when the User
13262 - Try to make sure that the version of Libevent we're running with
13263 is binary-compatible with the one we built with. May address bug
13265 - Add a new --enable-local-appdata configuration switch to change
13266 the default location of the datadir on win32 from APPDATA to
13267 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
13268 entirely. Patch from coderman.
13269 - Build correctly against versions of OpenSSL 0.9.8 or later that
13270 are built without support for deprecated functions.
13271 - On platforms with a maximum syslog string length, truncate syslog
13272 messages to that length ourselves, rather than relying on the
13273 system to do it for us.
13274 - Automatically detect MacOSX versions earlier than 10.4.0, and
13275 disable kqueue from inside Tor when running with these versions.
13276 We previously did this from the startup script, but that was no
13277 help to people who didn't use the startup script. Resolves bug 863.
13278 - Build correctly when configured to build outside the main source
13279 path. Patch from Michael Gold.
13280 - Disable GCC's strict alias optimization by default, to avoid the
13281 likelihood of its introducing subtle bugs whenever our code violates
13282 the letter of C99's alias rules.
13283 - Change the contrib/tor.logrotate script so it makes the new
13284 logs as "_tor:_tor" rather than the default, which is generally
13285 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
13286 - Change our header file guard macros to be less likely to conflict
13287 with system headers. Adam Langley noticed that we were conflicting
13288 with log.h on Android.
13289 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
13290 and stop using a warning that had become unfixably verbose under
13292 - Use a lockfile to make sure that two Tor processes are not
13293 simultaneously running with the same datadir.
13294 - Allow OpenSSL to use dynamic locks if it wants.
13295 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
13297 o Minor features (controllers):
13298 - When generating circuit events with verbose nicknames for
13299 controllers, try harder to look up nicknames for routers on a
13300 circuit. (Previously, we would look in the router descriptors we had
13301 for nicknames, but not in the consensus.) Partial fix for bug 941.
13302 - New controller event NEWCONSENSUS that lists the networkstatus
13303 lines for every recommended relay. Now controllers like Torflow
13304 can keep up-to-date on which relays they should be using.
13305 - New controller event "clients_seen" to report a geoip-based summary
13306 of which countries we've seen clients from recently. Now controllers
13307 like Vidalia can show bridge operators that they're actually making
13309 - Add a 'getinfo status/clients-seen' controller command, in case
13310 controllers want to hear clients_seen events but connect late.
13311 - New CONSENSUS_ARRIVED event to note when a new consensus has
13312 been fetched and validated.
13313 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
13314 controllers to prevent SIGHUP from reloading the configuration.
13316 - Return circuit purposes in response to GETINFO circuit-status.
13318 - Serve the latest v3 networkstatus consensus via the control
13319 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
13320 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
13321 controller can query our current bootstrap state in case it attaches
13322 partway through and wants to catch up.
13323 - Provide circuit purposes along with circuit events to the controller.
13325 o Minor features (tools):
13326 - Do not have tor-resolve automatically refuse all .onion addresses;
13327 if AutomapHostsOnResolve is set in your torrc, this will work fine.
13328 - Add a -p option to tor-resolve for specifying the SOCKS port: some
13329 people find host:port too confusing.
13330 - Print the SOCKS5 error message string as well as the error code
13331 when a tor-resolve request fails. Patch from Jacob.
13333 o Minor bugfixes (memory and resource management):
13334 - Clients no longer cache certificates for authorities they do not
13335 recognize. Bugfix on 0.2.0.9-alpha.
13336 - Do not use C's stdio library for writing to log files. This will
13337 improve logging performance by a minute amount, and will stop
13338 leaking fds when our disk is full. Fixes bug 861.
13339 - Stop erroneous use of O_APPEND in cases where we did not in fact
13340 want to re-seek to the end of a file before every last write().
13341 - Fix a small alignment and memory-wasting bug on buffer chunks.
13343 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
13344 to avoid unused RAM in buffer chunks and memory pools.
13345 - Reduce the default smartlist size from 32 to 16; it turns out that
13346 most smartlists hold around 8-12 elements tops.
13347 - Make dumpstats() log the fullness and size of openssl-internal
13349 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
13350 patch to their OpenSSL, turn it on to save memory on servers. This
13351 patch will (with any luck) get included in a mainline distribution
13353 - Fix a memory leak when v3 directory authorities load their keys
13354 and cert from disk. Bugfix on 0.2.0.1-alpha.
13355 - Stop using malloc_usable_size() to use more area than we had
13356 actually allocated: it was safe, but made valgrind really unhappy.
13357 - Make the assert_circuit_ok() function work correctly on circuits that
13358 have already been marked for close.
13359 - Fix uninitialized size field for memory area allocation: may improve
13360 memory performance during directory parsing.
13362 o Minor bugfixes (clients):
13363 - Stop reloading the router list from disk for no reason when we
13364 run out of reachable directory mirrors. Once upon a time reloading
13365 it would set the 'is_running' flag back to 1 for them. It hasn't
13366 done that for a long time.
13367 - When we had picked an exit node for a connection, but marked it as
13368 "optional", and it turned out we had no onion key for the exit,
13369 stop wanting that exit and try again. This situation may not
13370 be possible now, but will probably become feasible with proposal
13371 158. Spotted by rovv. Fixes another case of bug 752.
13372 - Fix a bug in address parsing that was preventing bridges or hidden
13373 service targets from being at IPv6 addresses.
13374 - Do not remove routers as too old if we do not have any consensus
13375 document. Bugfix on 0.2.0.7-alpha.
13376 - When an exit relay resolves a stream address to a local IP address,
13377 do not just keep retrying that same exit relay over and
13378 over. Instead, just close the stream. Addresses bug 872. Bugfix
13379 on 0.2.0.32. Patch from rovv.
13380 - Made Tor a little less aggressive about deleting expired
13381 certificates. Partial fix for bug 854.
13382 - Treat duplicate certificate fetches as failures, so that we do
13383 not try to re-fetch an expired certificate over and over and over.
13384 - Do not say we're fetching a certificate when we'll in fact skip it
13385 because of a pending download.
13386 - If we have correct permissions on $datadir, we complain to stdout
13387 and fail to start. But dangerous permissions on
13388 $datadir/cached-status/ would cause us to open a log and complain
13389 there. Now complain to stdout and fail to start in both cases. Fixes
13390 bug 820, reported by seeess.
13392 o Minor bugfixes (bridges):
13393 - When we made bridge authorities stop serving bridge descriptors over
13394 unencrypted links, we also broke DirPort reachability testing for
13395 bridges. So bridges with a non-zero DirPort were printing spurious
13396 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
13397 - Don't allow a bridge to publish its router descriptor to a
13398 non-bridge directory authority. Fixes part of bug 932.
13399 - When we change to or from being a bridge, reset our counts of
13400 client usage by country. Fixes bug 932.
13402 o Minor bugfixes (relays):
13403 - Log correct error messages for DNS-related network errors on
13405 - Actually return -1 in the error case for read_bandwidth_usage().
13406 Harmless bug, since we currently don't care about the return value
13407 anywhere. Bugfix on 0.2.0.9-alpha.
13408 - Provide a more useful log message if bug 977 (related to buffer
13409 freelists) ever reappears, and do not crash right away.
13410 - We were already rejecting relay begin cells with destination port
13411 of 0. Now also reject extend cells with destination port or address
13412 of 0. Suggested by lark.
13413 - When we can't transmit a DNS request due to a network error, retry
13414 it after a while, and eventually transmit a failing response to
13415 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
13416 - Solve a bug that kept hardware crypto acceleration from getting
13417 enabled when accounting was turned on. Fixes bug 907. Bugfix on
13419 - When a canonical connection appears later in our internal list
13420 than a noncanonical one for a given OR ID, always use the
13421 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
13423 - Avoid some nasty corner cases in the logic for marking connections
13424 as too old or obsolete or noncanonical for circuits. Partial
13426 - Fix another interesting corner-case of bug 891 spotted by rovv:
13427 Previously, if two hosts had different amounts of clock drift, and
13428 one of them created a new connection with just the wrong timing,
13429 the other might decide to deprecate the new connection erroneously.
13430 Bugfix on 0.1.1.13-alpha.
13431 - If one win32 nameserver fails to get added, continue adding the
13432 rest, and don't automatically fail.
13433 - Fix a bug where an unreachable relay would establish enough
13434 reachability testing circuits to do a bandwidth test -- if
13435 we already have a connection to the middle hop of the testing
13436 circuit, then it could establish the last hop by using the existing
13437 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
13438 circuits no longer use entry guards in 0.2.1.3-alpha.
13440 o Minor bugfixes (directory authorities):
13441 - Limit uploaded directory documents to be 16M rather than 500K.
13442 The directory authorities were refusing v3 consensus votes from
13443 other authorities, since the votes are now 504K. Fixes bug 959;
13444 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
13445 - Directory authorities should never send a 503 "busy" response to
13446 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
13448 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
13449 headers. Bugfix on 0.2.0.10-alpha.
13451 o Minor bugfixes (hidden services):
13452 - When we can't find an intro key for a v2 hidden service descriptor,
13453 fall back to the v0 hidden service descriptor and log a bug message.
13454 Workaround for bug 1024.
13455 - In very rare situations new hidden service descriptors were
13456 published earlier than 30 seconds after the last change to the
13457 service. (We currently think that a hidden service descriptor
13458 that's been stable for 30 seconds is worth publishing.)
13459 - If a hidden service sends us an END cell, do not consider
13460 retrying the connection; just close it. Patch from rovv.
13461 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
13462 service directories if they have no advertised dir port. Bugfix
13465 o Minor bugfixes (tools):
13466 - In the torify(1) manpage, mention that tsocks will leak your
13469 o Minor bugfixes (controllers):
13470 - If the controller claimed responsibility for a stream, but that
13471 stream never finished making its connection, it would live
13472 forever in circuit_wait state. Now we close it after SocksTimeout
13473 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
13474 - Make DNS resolved controller events into "CLOSED", not
13475 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
13477 - The control port would close the connection before flushing long
13478 replies, such as the network consensus, if a QUIT command was issued
13479 before the reply had completed. Now, the control port flushes all
13480 pending replies before closing the connection. Also fix a spurious
13481 warning when a QUIT command is issued after a malformed or rejected
13482 AUTHENTICATE command, but before the connection was closed. Patch
13483 by Marcus Griep. Fixes bugs 1015 and 1016.
13484 - Fix a bug that made stream bandwidth get misreported to the
13487 o Deprecated and removed features:
13488 - The old "tor --version --version" command, which would print out
13489 the subversion "Id" of most of the source files, is now removed. It
13490 turned out to be less useful than we'd expected, and harder to
13492 - RedirectExits has been removed. It was deprecated since
13494 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
13495 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
13496 - Cell pools are now always enabled; --disable-cell-pools is ignored.
13497 - Directory mirrors no longer fetch the v1 directory or
13498 running-routers files. They are obsolete, and nobody asks for them
13499 anymore. This is the first step to making v1 authorities obsolete.
13500 - Take out the TestVia config option, since it was a workaround for
13501 a bug that was fixed in Tor 0.1.1.21.
13502 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
13503 HiddenServiceExcludeNodes as obsolete: they never worked properly,
13504 and nobody seems to be using them. Fixes bug 754. Bugfix on
13505 0.1.0.1-rc. Patch from Christian Wilms.
13506 - Remove all backward-compatibility code for relays running
13507 versions of Tor so old that they no longer work at all on the
13510 o Code simplifications and refactoring:
13511 - Tool-assisted documentation cleanup. Nearly every function or
13512 static variable in Tor should have its own documentation now.
13513 - Rename the confusing or_is_obsolete field to the more appropriate
13514 is_bad_for_new_circs, and move it to or_connection_t where it
13516 - Move edge-only flags from connection_t to edge_connection_t: not
13517 only is this better coding, but on machines of plausible alignment,
13518 it should save 4-8 bytes per connection_t. "Every little bit helps."
13519 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
13520 for consistency; keep old option working for backward compatibility.
13521 - Simplify the code for finding connections to use for a circuit.
13522 - Revise the connection_new functions so that a more typesafe variant
13523 exists. This will work better with Coverity, and let us find any
13524 actual mistakes we're making here.
13525 - Refactor unit testing logic so that dmalloc can be used sensibly
13526 with unit tests to check for memory leaks.
13527 - Move all hidden-service related fields from connection and circuit
13528 structure to substructures: this way they won't eat so much memory.
13529 - Squeeze 2-5% out of client performance (according to oprofile) by
13530 improving the implementation of some policy-manipulation functions.
13531 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
13532 be more efficient. Formerly it was quadratic in the number of
13533 servers; now it should be linear. Fixes bug 509.
13534 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
13535 and n_conn_id_digest fields into a separate structure that's
13536 only needed when the circuit has not yet attached to an n_conn.
13537 - Optimize out calls to time(NULL) that occur for every IO operation,
13538 or for every cell. On systems like Windows where time() is a
13539 slow syscall, this fix will be slightly helpful.
13542 Changes in version 0.2.0.35 - 2009-06-24
13544 - Avoid crashing in the presence of certain malformed descriptors.
13545 Found by lark, and by automated fuzzing.
13546 - Fix an edge case where a malicious exit relay could convince a
13547 controller that the client's DNS question resolves to an internal IP
13548 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
13551 - Finally fix the bug where dynamic-IP relays disappear when their
13552 IP address changes: directory mirrors were mistakenly telling
13553 them their old address if they asked via begin_dir, so they
13554 never got an accurate answer about their new address, so they
13555 just vanished after a day. For belt-and-suspenders, relays that
13556 don't set Address in their config now avoid using begin_dir for
13557 all direct connections. Should fix bugs 827, 883, and 900.
13558 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
13559 that would occur on some exit nodes when DNS failures and timeouts
13560 occurred in certain patterns. Fix for bug 957.
13563 - When starting with a cache over a few days old, do not leak
13564 memory for the obsolete router descriptors in it. Bugfix on
13565 0.2.0.33; fixes bug 672.
13566 - Hidden service clients didn't use a cached service descriptor that
13567 was older than 15 minutes, but wouldn't fetch a new one either,
13568 because there was already one in the cache. Now, fetch a v2
13569 descriptor unless the same descriptor was added to the cache within
13570 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
13573 Changes in version 0.2.0.34 - 2009-02-08
13574 Tor 0.2.0.34 features several more security-related fixes. You should
13575 upgrade, especially if you run an exit relay (remote crash) or a
13576 directory authority (remote infinite loop), or you're on an older
13577 (pre-XP) or not-recently-patched Windows (remote exploit).
13579 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
13580 have many known flaws, and nobody should be using them. You should
13581 upgrade. If you're using a Linux or BSD and its packages are obsolete,
13582 stop using those packages and upgrade anyway.
13585 - Fix an infinite-loop bug on handling corrupt votes under certain
13586 circumstances. Bugfix on 0.2.0.8-alpha.
13587 - Fix a temporary DoS vulnerability that could be performed by
13588 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
13589 - Avoid a potential crash on exit nodes when processing malformed
13590 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
13591 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
13592 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
13595 - Fix compilation on systems where time_t is a 64-bit integer.
13596 Patch from Matthias Drochner.
13597 - Don't consider expiring already-closed client connections. Fixes
13598 bug 893. Bugfix on 0.0.2pre20.
13601 Changes in version 0.2.0.33 - 2009-01-21
13602 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
13603 useful to users. It also finally fixes a bug where a relay or client
13604 that's been off for many days would take a long time to bootstrap.
13606 This update also fixes an important security-related bug reported by
13607 Ilja van Sprundel. You should upgrade. (We'll send out more details
13608 about the bug once people have had some time to upgrade.)
13611 - Fix a heap-corruption bug that may be remotely triggerable on
13612 some platforms. Reported by Ilja van Sprundel.
13615 - When a stream at an exit relay is in state "resolving" or
13616 "connecting" and it receives an "end" relay cell, the exit relay
13617 would silently ignore the end cell and not close the stream. If
13618 the client never closes the circuit, then the exit relay never
13619 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
13620 reported by "wood".
13621 - When sending CREATED cells back for a given circuit, use a 64-bit
13622 connection ID to find the right connection, rather than an addr:port
13623 combination. Now that we can have multiple OR connections between
13624 the same ORs, it is no longer possible to use addr:port to uniquely
13625 identify a connection.
13626 - Bridge relays that had DirPort set to 0 would stop fetching
13627 descriptors shortly after startup, and then briefly resume
13628 after a new bandwidth test and/or after publishing a new bridge
13629 descriptor. Bridge users that try to bootstrap from them would
13630 get a recent networkstatus but would get descriptors from up to
13631 18 hours earlier, meaning most of the descriptors were obsolete
13632 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
13633 - Prevent bridge relays from serving their 'extrainfo' document
13634 to anybody who asks, now that extrainfo docs include potentially
13635 sensitive aggregated client geoip summaries. Bugfix on
13637 - If the cached networkstatus consensus is more than five days old,
13638 discard it rather than trying to use it. In theory it could be
13639 useful because it lists alternate directory mirrors, but in practice
13640 it just means we spend many minutes trying directory mirrors that
13641 are long gone from the network. Also discard router descriptors as
13642 we load them if they are more than five days old, since the onion
13643 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
13646 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
13647 could make gcc generate non-functional binary search code. Bugfix
13649 - Build correctly on platforms without socklen_t.
13650 - Compile without warnings on solaris.
13651 - Avoid potential crash on internal error during signature collection.
13652 Fixes bug 864. Patch from rovv.
13653 - Correct handling of possible malformed authority signing key
13654 certificates with internal signature types. Fixes bug 880.
13655 Bugfix on 0.2.0.3-alpha.
13656 - Fix a hard-to-trigger resource leak when logging credential status.
13658 - When we can't initialize DNS because the network is down, do not
13659 automatically stop Tor from starting. Instead, we retry failed
13660 dns_init() every 10 minutes, and change the exit policy to reject
13661 *:* until one succeeds. Fixes bug 691.
13662 - Use 64 bits instead of 32 bits for connection identifiers used with
13663 the controller protocol, to greatly reduce risk of identifier reuse.
13664 - When we're choosing an exit node for a circuit, and we have
13665 no pending streams, choose a good general exit rather than one that
13666 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
13667 - Fix another case of assuming, when a specific exit is requested,
13668 that we know more than the user about what hosts it allows.
13669 Fixes one case of bug 752. Patch from rovv.
13670 - Clip the MaxCircuitDirtiness config option to a minimum of 10
13671 seconds. Warn the user if lower values are given in the
13672 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
13673 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
13674 user if lower values are given in the configuration. Bugfix on
13675 0.1.1.17-rc. Patch by Sebastian.
13676 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
13677 the cache because we already had a v0 descriptor with the same ID.
13678 Bugfix on 0.2.0.18-alpha.
13679 - Fix a race condition when freeing keys shared between main thread
13680 and CPU workers that could result in a memory leak. Bugfix on
13681 0.1.0.1-rc. Fixes bug 889.
13682 - Send a valid END cell back when a client tries to connect to a
13683 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
13684 840. Patch from rovv.
13685 - Check which hops rendezvous stream cells are associated with to
13686 prevent possible guess-the-streamid injection attacks from
13687 intermediate hops. Fixes another case of bug 446. Based on patch
13689 - If a broken client asks a non-exit router to connect somewhere,
13690 do not even do the DNS lookup before rejecting the connection.
13691 Fixes another case of bug 619. Patch from rovv.
13692 - When a relay gets a create cell it can't decrypt (e.g. because it's
13693 using the wrong onion key), we were dropping it and letting the
13694 client time out. Now actually answer with a destroy cell. Fixes
13695 bug 904. Bugfix on 0.0.2pre8.
13697 o Minor bugfixes (hidden services):
13698 - Do not throw away existing introduction points on SIGHUP. Bugfix on
13699 0.0.6pre1. Patch by Karsten. Fixes bug 874.
13702 - Report the case where all signatures in a detached set are rejected
13703 differently than the case where there is an error handling the
13705 - When we realize that another process has modified our cached
13706 descriptors, print out a more useful error message rather than
13707 triggering an assertion. Fixes bug 885. Patch from Karsten.
13708 - Implement the 0x20 hack to better resist DNS poisoning: set the
13709 case on outgoing DNS requests randomly, and reject responses that do
13710 not match the case correctly. This logic can be disabled with the
13711 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
13712 of servers that do not reliably preserve case in replies. See
13713 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
13715 - Check DNS replies for more matching fields to better resist DNS
13717 - Never use OpenSSL compression: it wastes RAM and CPU trying to
13718 compress cells, which are basically all encrypted, compressed, or
13722 Changes in version 0.2.0.32 - 2008-11-20
13723 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
13724 packages (and maybe other packages) noticed by Theo de Raadt, fixes
13725 a smaller security flaw that might allow an attacker to access local
13726 services, further improves hidden service performance, and fixes a
13727 variety of other issues.
13730 - The "User" and "Group" config options did not clear the
13731 supplementary group entries for the Tor process. The "User" option
13732 is now more robust, and we now set the groups to the specified
13733 user's primary group. The "Group" option is now ignored. For more
13734 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
13735 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
13736 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
13737 - The "ClientDNSRejectInternalAddresses" config option wasn't being
13738 consistently obeyed: if an exit relay refuses a stream because its
13739 exit policy doesn't allow it, we would remember what IP address
13740 the relay said the destination address resolves to, even if it's
13741 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
13744 - Fix a DOS opportunity during the voting signature collection process
13745 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
13747 o Major bugfixes (hidden services):
13748 - When fetching v0 and v2 rendezvous service descriptors in parallel,
13749 we were failing the whole hidden service request when the v0
13750 descriptor fetch fails, even if the v2 fetch is still pending and
13751 might succeed. Similarly, if the last v2 fetch fails, we were
13752 failing the whole hidden service request even if a v0 fetch is
13753 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
13754 - When extending a circuit to a hidden service directory to upload a
13755 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
13756 requests failed, because the router descriptor has not been
13757 downloaded yet. In these cases, do not attempt to upload the
13758 rendezvous descriptor, but wait until the router descriptor is
13759 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
13760 descriptor from a hidden service directory for which the router
13761 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
13765 - Fix several infrequent memory leaks spotted by Coverity.
13766 - When testing for libevent functions, set the LDFLAGS variable
13767 correctly. Found by Riastradh.
13768 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
13769 bootstrapping with tunneled directory connections. Bugfix on
13770 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
13771 - When asked to connect to A.B.exit:80, if we don't know the IP for A
13772 and we know that server B rejects most-but-not all connections to
13773 port 80, we would previously reject the connection. Now, we assume
13774 the user knows what they were asking for. Fixes bug 752. Bugfix
13775 on 0.0.9rc5. Diagnosed by BarkerJr.
13776 - If we overrun our per-second write limits a little, count this as
13777 having used up our write allocation for the second, and choke
13778 outgoing directory writes. Previously, we had only counted this when
13779 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
13780 Bugfix on 0.2.0.x (??).
13781 - Remove the old v2 directory authority 'lefkada' from the default
13782 list. It has been gone for many months.
13783 - Stop doing unaligned memory access that generated bus errors on
13784 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
13785 - Make USR2 log-level switch take effect immediately. Bugfix on
13788 o Minor bugfixes (controller):
13789 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
13790 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
13793 Changes in version 0.2.0.31 - 2008-09-03
13794 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
13795 a big bug we're seeing where in rare cases traffic from one Tor stream
13796 gets mixed into another stream, and fixes a variety of smaller issues.
13799 - Make sure that two circuits can never exist on the same connection
13800 with the same circuit ID, even if one is marked for close. This
13801 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
13802 - Relays now reject risky extend cells: if the extend cell includes
13803 a digest of all zeroes, or asks to extend back to the relay that
13804 sent the extend cell, tear down the circuit. Ideas suggested
13806 - If not enough of our entry guards are available so we add a new
13807 one, we might use the new one even if it overlapped with the
13808 current circuit's exit relay (or its family). Anonymity bugfix
13809 pointed out by rovv.
13812 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
13813 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
13814 - Correctly detect the presence of the linux/netfilter_ipv4.h header
13815 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
13816 - Pick size of default geoip filename string correctly on windows.
13817 Fixes bug 806. Bugfix on 0.2.0.30.
13818 - Make the autoconf script accept the obsolete --with-ssl-dir
13819 option as an alias for the actually-working --with-openssl-dir
13820 option. Fix the help documentation to recommend --with-openssl-dir.
13821 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
13822 - When using the TransPort option on OpenBSD, and using the User
13823 option to change UID and drop privileges, make sure to open
13824 /dev/pf before dropping privileges. Fixes bug 782. Patch from
13825 Christopher Davis. Bugfix on 0.1.2.1-alpha.
13826 - Try to attach connections immediately upon receiving a RENDEZVOUS2
13827 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
13828 on the client side when connecting to a hidden service. Bugfix
13829 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
13830 - When closing an application-side connection because its circuit is
13831 getting torn down, generate the stream event correctly. Bugfix on
13832 0.1.2.x. Anonymous patch.
13835 Changes in version 0.2.0.30 - 2008-07-15
13836 This new stable release switches to a more efficient directory
13837 distribution design, adds features to make connections to the Tor
13838 network harder to block, allows Tor to act as a DNS proxy, adds separate
13839 rate limiting for relayed traffic to make it easier for clients to
13840 become relays, fixes a variety of potential anonymity problems, and
13841 includes the usual huge pile of other features and bug fixes.
13843 o New v3 directory design:
13844 - Tor now uses a new way to learn about and distribute information
13845 about the network: the directory authorities vote on a common
13846 network status document rather than each publishing their own
13847 opinion. Now clients and caches download only one networkstatus
13848 document to bootstrap, rather than downloading one for each
13849 authority. Clients only download router descriptors listed in
13850 the consensus. Implements proposal 101; see doc/spec/dir-spec.txt
13852 - Set up moria1, tor26, and dizum as v3 directory authorities
13853 in addition to being v2 authorities. Also add three new ones:
13854 ides (run by Mike Perry), gabelmoo (run by Karsten Loesing), and
13855 dannenberg (run by CCC).
13856 - Switch to multi-level keys for directory authorities: now their
13857 long-term identity key can be kept offline, and they periodically
13858 generate a new signing key. Clients fetch the "key certificates"
13859 to keep up to date on the right keys. Add a standalone tool
13860 "tor-gencert" to generate key certificates. Implements proposal 103.
13861 - Add a new V3AuthUseLegacyKey config option to make it easier for
13862 v3 authorities to change their identity keys if another bug like
13863 Debian's OpenSSL RNG flaw appears.
13864 - Authorities and caches fetch the v2 networkstatus documents
13865 less often, now that v3 is recommended.
13867 o Make Tor connections stand out less on the wire:
13868 - Use an improved TLS handshake designed by Steven Murdoch in proposal
13869 124, as revised in proposal 130. The new handshake is meant to
13870 be harder for censors to fingerprint, and it adds the ability
13871 to detect certain kinds of man-in-the-middle traffic analysis
13872 attacks. The new handshake format includes version negotiation for
13873 OR connections as described in proposal 105, which will allow us
13874 to improve Tor's link protocol more safely in the future.
13875 - Enable encrypted directory connections by default for non-relays,
13876 so censor tools that block Tor directory connections based on their
13877 plaintext patterns will no longer work. This means Tor works in
13878 certain censored countries by default again.
13879 - Stop including recognizeable strings in the commonname part of
13880 Tor's x509 certificates.
13882 o Implement bridge relays:
13883 - Bridge relays (or "bridges" for short) are Tor relays that aren't
13884 listed in the main Tor directory. Since there is no complete public
13885 list of them, even an ISP that is filtering connections to all the
13886 known Tor relays probably won't be able to block all the bridges.
13887 See doc/design-paper/blocking.pdf and proposal 125 for details.
13888 - New config option BridgeRelay that specifies you want to be a
13889 bridge relay rather than a normal relay. When BridgeRelay is set
13890 to 1, then a) you cache dir info even if your DirPort ins't on,
13891 and b) the default for PublishServerDescriptor is now "bridge"
13892 rather than "v2,v3".
13893 - New config option "UseBridges 1" for clients that want to use bridge
13894 relays instead of ordinary entry guards. Clients then specify
13895 bridge relays by adding "Bridge" lines to their config file. Users
13896 can learn about a bridge relay either manually through word of
13897 mouth, or by one of our rate-limited mechanisms for giving out
13898 bridge addresses without letting an attacker easily enumerate them
13899 all. See https://www.torproject.org/bridges for details.
13900 - Bridge relays behave like clients with respect to time intervals
13901 for downloading new v3 consensus documents -- otherwise they
13902 stand out. Bridge users now wait until the end of the interval,
13903 so their bridge relay will be sure to have a new consensus document.
13905 o Implement bridge directory authorities:
13906 - Bridge authorities are like normal directory authorities, except
13907 they don't serve a list of known bridges. Therefore users that know
13908 a bridge's fingerprint can fetch a relay descriptor for that bridge,
13909 including fetching updates e.g. if the bridge changes IP address,
13910 yet an attacker can't just fetch a list of all the bridges.
13911 - Set up Tonga as the default bridge directory authority.
13912 - Bridge authorities refuse to serve bridge descriptors or other
13913 bridge information over unencrypted connections (that is, when
13914 responding to direct DirPort requests rather than begin_dir cells.)
13915 - Bridge directory authorities do reachability testing on the
13916 bridges they know. They provide router status summaries to the
13917 controller via "getinfo ns/purpose/bridge", and also dump summaries
13918 to a file periodically, so we can keep internal stats about which
13919 bridges are functioning.
13920 - If bridge users set the UpdateBridgesFromAuthority config option,
13921 but the digest they ask for is a 404 on the bridge authority,
13922 they fall back to contacting the bridge directly.
13923 - Bridges always use begin_dir to publish their server descriptor to
13924 the bridge authority using an anonymous encrypted tunnel.
13925 - Early work on a "bridge community" design: if bridge authorities set
13926 the BridgePassword config option, they will serve a snapshot of
13927 known bridge routerstatuses from their DirPort to anybody who
13928 knows that password. Unset by default.
13929 - Tor now includes an IP-to-country GeoIP file, so bridge relays can
13930 report sanitized aggregated summaries in their extra-info documents
13931 privately to the bridge authority, listing which countries are
13932 able to reach them. We hope this mechanism will let us learn when
13933 certain countries start trying to block bridges.
13934 - Bridge authorities write bridge descriptors to disk, so they can
13935 reload them after a reboot. They can also export the descriptors
13936 to other programs, so we can distribute them to blocked users via
13937 the BridgeDB interface, e.g. via https://bridges.torproject.org/
13938 and bridges@torproject.org.
13940 o Tor can be a DNS proxy:
13941 - The new client-side DNS proxy feature replaces the need for
13942 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
13943 for DNS requests on port 9999, use the Tor network to resolve them
13944 anonymously, and send the reply back like a regular DNS server.
13945 The code still only implements a subset of DNS.
13946 - Add a new AutomapHostsOnResolve option: when it is enabled, any
13947 resolve request for hosts matching a given pattern causes Tor to
13948 generate an internal virtual address mapping for that host. This
13949 allows DNSPort to work sensibly with hidden service users. By
13950 default, .exit and .onion addresses are remapped; the list of
13951 patterns can be reconfigured with AutomapHostsSuffixes.
13952 - Add an "-F" option to tor-resolve to force a resolve for a .onion
13953 address. Thanks to the AutomapHostsOnResolve option, this is no
13954 longer a completely silly thing to do.
13956 o Major features (relay usability):
13957 - New config options RelayBandwidthRate and RelayBandwidthBurst:
13958 a separate set of token buckets for relayed traffic. Right now
13959 relayed traffic is defined as answers to directory requests, and
13960 OR connections that don't have any local circuits on them. See
13961 proposal 111 for details.
13962 - Create listener connections before we setuid to the configured
13963 User and Group. Now non-Windows users can choose port values
13964 under 1024, start Tor as root, and have Tor bind those ports
13965 before it changes to another UID. (Windows users could already
13967 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
13968 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
13969 on "vserver" accounts. Patch from coderman.
13971 o Major features (directory authorities):
13972 - Directory authorities track weighted fractional uptime and weighted
13973 mean-time-between failures for relays. WFU is suitable for deciding
13974 whether a node is "usually up", while MTBF is suitable for deciding
13975 whether a node is "likely to stay up." We need both, because
13976 "usually up" is a good requirement for guards, while "likely to
13977 stay up" is a good requirement for long-lived connections.
13978 - Directory authorities use a new formula for selecting which relays
13979 to advertise as Guards: they must be in the top 7/8 in terms of
13980 how long we have known about them, and above the median of those
13981 nodes in terms of weighted fractional uptime.
13982 - Directory authorities use a new formula for selecting which relays
13983 to advertise as Stable: when we have 4 or more days of data, use
13984 median measured MTBF rather than median declared uptime. Implements
13986 - Directory authorities accept and serve "extra info" documents for
13987 routers. Routers now publish their bandwidth-history lines in the
13988 extra-info docs rather than the main descriptor. This step saves
13989 60% (!) on compressed router descriptor downloads. Servers upload
13990 extra-info docs to any authority that accepts them; directory
13991 authorities now allow multiple router descriptors and/or extra
13992 info documents to be uploaded in a single go. Authorities, and
13993 caches that have been configured to download extra-info documents,
13994 download them as needed. Implements proposal 104.
13995 - Authorities now list relays who have the same nickname as
13996 a different named relay, but list them with a new flag:
13997 "Unnamed". Now we can make use of relays that happen to pick the
13998 same nickname as a server that registered two years ago and then
13999 disappeared. Implements proposal 122.
14000 - Store routers in a file called cached-descriptors instead of in
14001 cached-routers. Initialize cached-descriptors from cached-routers
14002 if the old format is around. The new format allows us to store
14003 annotations along with descriptors, to record the time we received
14004 each descriptor, its source, and its purpose: currently one of
14005 general, controller, or bridge.
14007 o Major features (other):
14008 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
14009 Tor can warn and/or refuse connections to ports commonly used with
14010 vulnerable-plaintext protocols. Currently we warn on ports 23,
14011 109, 110, and 143, but we don't reject any. Based on proposal 129
14012 by Kevin Bauer and Damon McCoy.
14013 - Integrate Karsten Loesing's Google Summer of Code project to publish
14014 hidden service descriptors on a set of redundant relays that are a
14015 function of the hidden service address. Now we don't have to rely
14016 on three central hidden service authorities for publishing and
14017 fetching every hidden service descriptor. Implements proposal 114.
14018 - Allow tunnelled directory connections to ask for an encrypted
14019 "begin_dir" connection or an anonymized "uses a full Tor circuit"
14020 connection independently. Now we can make anonymized begin_dir
14021 connections for (e.g.) more secure hidden service posting and
14024 o Major bugfixes (crashes and assert failures):
14025 - Stop imposing an arbitrary maximum on the number of file descriptors
14026 used for busy servers. Bug reported by Olaf Selke; patch from
14028 - Avoid possible failures when generating a directory with routers
14029 with over-long versions strings, or too many flags set.
14030 - Fix a rare assert error when we're closing one of our threads:
14031 use a mutex to protect the list of logs, so we never write to the
14032 list as it's being freed. Fixes the very rare bug 575, which is
14033 kind of the revenge of bug 222.
14034 - Avoid segfault in the case where a badly behaved v2 versioning
14035 directory sends a signed networkstatus with missing client-versions.
14036 - When we hit an EOF on a log (probably because we're shutting down),
14037 don't try to remove the log from the list: just mark it as
14038 unusable. (Bulletproofs against bug 222.)
14040 o Major bugfixes (code security fixes):
14041 - Detect size overflow in zlib code. Reported by Justin Ferguson and
14043 - Rewrite directory tokenization code to never run off the end of
14044 a string. Fixes bug 455. Patch from croup.
14045 - Be more paranoid about overwriting sensitive memory on free(),
14046 as a defensive programming tactic to ensure forward secrecy.
14048 o Major bugfixes (anonymity fixes):
14049 - Reject requests for reverse-dns lookup of names that are in
14050 a private address space. Patch from lodger.
14051 - Never report that we've used more bandwidth than we're willing to
14052 relay: it leaks how much non-relay traffic we're using. Resolves
14054 - As a client, do not believe any server that tells us that an
14055 address maps to an internal address space.
14056 - Warn about unsafe ControlPort configurations.
14057 - Directory authorities now call routers Fast if their bandwidth is
14058 at least 100KB/s, and consider their bandwidth adequate to be a
14059 Guard if it is at least 250KB/s, no matter the medians. This fix
14060 complements proposal 107.
14061 - Directory authorities now never mark more than 2 servers per IP as
14062 Valid and Running (or 5 on addresses shared by authorities).
14063 Implements proposal 109, by Kevin Bauer and Damon McCoy.
14064 - If we're a relay, avoid picking ourselves as an introduction point,
14065 a rendezvous point, or as the final hop for internal circuits. Bug
14066 reported by taranis and lodger.
14067 - Exit relays that are used as a client can now reach themselves
14068 using the .exit notation, rather than just launching an infinite
14069 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
14070 - Fix a bug where, when we were choosing the 'end stream reason' to
14071 put in our relay end cell that we send to the exit relay, Tor
14072 clients on Windows were sometimes sending the wrong 'reason'. The
14073 anonymity problem is that exit relays may be able to guess whether
14074 the client is running Windows, thus helping partition the anonymity
14075 set. Down the road we should stop sending reasons to exit relays,
14076 or otherwise prevent future versions of this bug.
14077 - Only update guard status (usable / not usable) once we have
14078 enough directory information. This was causing us to discard all our
14079 guards on startup if we hadn't been running for a few weeks. Fixes
14081 - When our directory information has been expired for a while, stop
14082 being willing to build circuits using it. Fixes bug 401.
14084 o Major bugfixes (peace of mind for relay operators)
14085 - Non-exit relays no longer answer "resolve" relay cells, so they
14086 can't be induced to do arbitrary DNS requests. (Tor clients already
14087 avoid using non-exit relays for resolve cells, but now servers
14088 enforce this too.) Fixes bug 619. Patch from lodger.
14089 - When we setconf ClientOnly to 1, close any current OR and Dir
14090 listeners. Reported by mwenge.
14092 o Major bugfixes (other):
14093 - If we only ever used Tor for hidden service lookups or posts, we
14094 would stop building circuits and start refusing connections after
14095 24 hours, since we falsely believed that Tor was dormant. Reported
14097 - Add a new __HashedControlSessionPassword option for controllers
14098 to use for one-off session password hashes that shouldn't get
14099 saved to disk by SAVECONF --- Vidalia users were accumulating a
14100 pile of HashedControlPassword lines in their torrc files, one for
14101 each time they had restarted Tor and then clicked Save. Make Tor
14102 automatically convert "HashedControlPassword" to this new option but
14103 only when it's given on the command line. Partial fix for bug 586.
14104 - Patch from "Andrew S. Lists" to catch when we contact a directory
14105 mirror at IP address X and he says we look like we're coming from
14106 IP address X. Otherwise this would screw up our address detection.
14107 - Reject uploaded descriptors and extrainfo documents if they're
14108 huge. Otherwise we'll cache them all over the network and it'll
14109 clog everything up. Suggested by Aljosha Judmayer.
14110 - When a hidden service was trying to establish an introduction point,
14111 and Tor *did* manage to reuse one of the preemptively built
14112 circuits, it didn't correctly remember which one it used,
14113 so it asked for another one soon after, until there were no
14114 more preemptive circuits, at which point it launched one from
14115 scratch. Bugfix on 0.0.9.x.
14117 o Rate limiting and load balancing improvements:
14118 - When we add data to a write buffer in response to the data on that
14119 write buffer getting low because of a flush, do not consider the
14120 newly added data as a candidate for immediate flushing, but rather
14121 make it wait until the next round of writing. Otherwise, we flush
14122 and refill recursively, and a single greedy TLS connection can
14123 eat all of our bandwidth.
14124 - When counting the number of bytes written on a TLS connection,
14125 look at the BIO actually used for writing to the network, not
14126 at the BIO used (sometimes) to buffer data for the network.
14127 Looking at different BIOs could result in write counts on the
14128 order of ULONG_MAX. Fixes bug 614.
14129 - If we change our MaxAdvertisedBandwidth and then reload torrc,
14130 Tor won't realize it should publish a new relay descriptor. Fixes
14131 bug 688, reported by mfr.
14132 - Avoid using too little bandwidth when our clock skips a few seconds.
14133 - Choose which bridge to use proportional to its advertised bandwidth,
14134 rather than uniformly at random. This should speed up Tor for
14135 bridge users. Also do this for people who set StrictEntryNodes.
14137 o Bootstrapping faster and building circuits more intelligently:
14138 - Fix bug 660 that was preventing us from knowing that we should
14139 preemptively build circuits to handle expected directory requests.
14140 - When we're checking if we have enough dir info for each relay
14141 to begin establishing circuits, make sure that we actually have
14142 the descriptor listed in the consensus, not just any descriptor.
14143 - Correctly notify one-hop connections when a circuit build has
14144 failed. Possible fix for bug 669. Found by lodger.
14145 - Clients now hold circuitless TLS connections open for 1.5 times
14146 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
14147 rebuild a new circuit over them within that timeframe. Previously,
14148 they held them open only for KeepalivePeriod (5 minutes).
14150 o Performance improvements (memory):
14151 - Add OpenBSD malloc code from "phk" as an optional malloc
14152 replacement on Linux: some glibc libraries do very poorly with
14153 Tor's memory allocation patterns. Pass --enable-openbsd-malloc to
14154 ./configure to get the replacement malloc code.
14155 - Switch our old ring buffer implementation for one more like that
14156 used by free Unix kernels. The wasted space in a buffer with 1mb
14157 of data will now be more like 8k than 1mb. The new implementation
14158 also avoids realloc();realloc(); patterns that can contribute to
14159 memory fragmentation.
14160 - Change the way that Tor buffers data that it is waiting to write.
14161 Instead of queueing data cells in an enormous ring buffer for each
14162 client->OR or OR->OR connection, we now queue cells on a separate
14163 queue for each circuit. This lets us use less slack memory, and
14164 will eventually let us be smarter about prioritizing different kinds
14166 - Reference-count and share copies of address policy entries; only 5%
14167 of them were actually distinct.
14168 - Tune parameters for cell pool allocation to minimize amount of
14170 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
14171 for every single inactive connection_t. Free items from the
14172 4k/16k-buffer free lists when they haven't been used for a while.
14173 - Make memory debugging information describe more about history
14174 of cell allocation, so we can help reduce our memory use.
14175 - Be even more aggressive about releasing RAM from small
14176 empty buffers. Thanks to our free-list code, this shouldn't be too
14177 performance-intensive.
14178 - Log malloc statistics from mallinfo() on platforms where it exists.
14179 - Use memory pools to allocate cells with better speed and memory
14180 efficiency, especially on platforms where malloc() is inefficient.
14181 - Add a --with-tcmalloc option to the configure script to link
14182 against tcmalloc (if present). Does not yet search for non-system
14185 o Performance improvements (socket management):
14186 - Count the number of open sockets separately from the number of
14187 active connection_t objects. This will let us avoid underusing
14188 our allocated connection limit.
14189 - We no longer use socket pairs to link an edge connection to an
14190 anonymous directory connection or a DirPort test connection.
14191 Instead, we track the link internally and transfer the data
14192 in-process. This saves two sockets per "linked" connection (at the
14193 client and at the server), and avoids the nasty Windows socketpair()
14195 - We were leaking a file descriptor if Tor started with a zero-length
14196 cached-descriptors file. Patch by "freddy77".
14198 o Performance improvements (CPU use):
14199 - Never walk through the list of logs if we know that no log target
14200 is interested in a given message.
14201 - Call routerlist_remove_old_routers() much less often. This should
14202 speed startup, especially on directory caches.
14203 - Base64 decoding was actually showing up on our profile when parsing
14204 the initial descriptor file; switch to an in-process all-at-once
14205 implementation that's about 3.5x times faster than calling out to
14207 - Use a slightly simpler string hashing algorithm (copying Python's
14208 instead of Java's) and optimize our digest hashing algorithm to take
14209 advantage of 64-bit platforms and to remove some possibly-costly
14211 - When implementing AES counter mode, update only the portions of the
14212 counter buffer that need to change, and don't keep separate
14213 network-order and host-order counters on big-endian hosts (where
14214 they are the same).
14215 - Add an in-place version of aes_crypt() so that we can avoid doing a
14216 needless memcpy() call on each cell payload.
14217 - Use Critical Sections rather than Mutexes for synchronizing threads
14218 on win32; Mutexes are heavier-weight, and designed for synchronizing
14221 o Performance improvements (bandwidth use):
14222 - Don't try to launch new descriptor downloads quite so often when we
14223 already have enough directory information to build circuits.
14224 - Version 1 directories are no longer generated in full. Instead,
14225 authorities generate and serve "stub" v1 directories that list
14226 no servers. This will stop Tor versions 0.1.0.x and earlier from
14227 working, but (for security reasons) nobody should be running those
14229 - Avoid going directly to the directory authorities even if you're a
14230 relay, if you haven't found yourself reachable yet or if you've
14231 decided not to advertise your dirport yet. Addresses bug 556.
14232 - If we've gone 12 hours since our last bandwidth check, and we
14233 estimate we have less than 50KB bandwidth capacity but we could
14234 handle more, do another bandwidth test.
14235 - Support "If-Modified-Since" when answering HTTP requests for
14236 directories, running-routers documents, and v2 and v3 networkstatus
14237 documents. (There's no need to support it for router descriptors,
14238 since those are downloaded by descriptor digest.)
14239 - Stop fetching directory info so aggressively if your DirPort is
14240 on but your ORPort is off; stop fetching v2 dir info entirely.
14241 You can override these choices with the new FetchDirInfoEarly
14244 o Changed config option behavior (features):
14245 - Configuration files now accept C-style strings as values. This
14246 helps encode characters not allowed in the current configuration
14247 file format, such as newline or #. Addresses bug 557.
14248 - Add hidden services and DNSPorts to the list of things that make
14249 Tor accept that it has running ports. Change starting Tor with no
14250 ports from a fatal error to a warning; we might change it back if
14251 this turns out to confuse anybody. Fixes bug 579.
14252 - Make PublishServerDescriptor default to 1, so the default doesn't
14253 have to change as we invent new directory protocol versions.
14254 - Allow people to say PreferTunnelledDirConns rather than
14255 PreferTunneledDirConns, for those alternate-spellers out there.
14256 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
14257 accommodate the growing number of servers that use the default
14258 and are reaching it.
14259 - Make it possible to enable HashedControlPassword and
14260 CookieAuthentication at the same time.
14261 - When a TrackHostExits-chosen exit fails too many times in a row,
14262 stop using it. Fixes bug 437.
14264 o Changed config option behavior (bugfixes):
14265 - Do not read the configuration file when we've only been told to
14266 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
14267 based on patch from Sebastian Hahn.
14268 - Actually validate the options passed to AuthDirReject,
14269 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
14270 - Make "ClientOnly 1" config option disable directory ports too.
14271 - Don't stop fetching descriptors when FetchUselessDescriptors is
14272 set, even if we stop asking for circuits. Bug reported by tup
14274 - Servers used to decline to publish their DirPort if their
14275 BandwidthRate or MaxAdvertisedBandwidth were below a threshold. Now
14276 they look only at BandwidthRate and RelayBandwidthRate.
14277 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
14278 minus 1 byte: the actual maximum declared bandwidth.
14279 - Make "TrackHostExits ." actually work. Bugfix on 0.1.0.x.
14280 - Make the NodeFamilies config option work. (Reported by
14281 lodger -- it has never actually worked, even though we added it
14283 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
14284 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
14286 o New config options:
14287 - New configuration options AuthDirMaxServersPerAddr and
14288 AuthDirMaxServersperAuthAddr to override default maximum number
14289 of servers allowed on a single IP address. This is important for
14290 running a test network on a single host.
14291 - Three new config options (AlternateDirAuthority,
14292 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
14293 user selectively replace the default directory authorities by type,
14294 rather than the all-or-nothing replacement that DirServer offers.
14295 - New config options AuthDirBadDir and AuthDirListBadDirs for
14296 authorities to mark certain relays as "bad directories" in the
14297 networkstatus documents. Also supports the "!baddir" directive in
14298 the approved-routers file.
14299 - New config option V2AuthoritativeDirectory that all v2 directory
14300 authorities must set. This lets v3 authorities choose not to serve
14301 v2 directory information.
14303 o Minor features (other):
14304 - When we're not serving v2 directory information, there is no reason
14305 to actually keep any around. Remove the obsolete files and directory
14306 on startup if they are very old and we aren't going to serve them.
14307 - When we negotiate a v2 link-layer connection (not yet implemented),
14308 accept RELAY_EARLY cells and turn them into RELAY cells if we've
14309 negotiated a v1 connection for their next step. Initial steps for
14311 - When we have no consensus, check FallbackNetworkstatusFile (defaults
14312 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
14313 we can start out knowing some directory caches. We don't ship with
14314 a fallback consensus by default though, because it was making
14315 bootstrapping take too long while we tried many down relays.
14316 - Authorities send back an X-Descriptor-Not-New header in response to
14317 an accepted-but-discarded descriptor upload. Partially implements
14319 - If we find a cached-routers file that's been sitting around for more
14320 than 28 days unmodified, then most likely it's a leftover from
14321 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
14323 - When we (as a cache) download a descriptor because it was listed
14324 in a consensus, remember when the consensus was supposed to expire,
14325 and don't expire the descriptor until then.
14326 - Optionally (if built with -DEXPORTMALLINFO) export the output
14327 of mallinfo via http, as tor/mallinfo.txt. Only accessible
14329 - Tag every guard node in our state file with the version that
14330 we believe added it, or with our own version if we add it. This way,
14331 if a user temporarily runs an old version of Tor and then switches
14332 back to a new one, she doesn't automatically lose her guards.
14333 - When somebody requests a list of statuses or servers, and we have
14334 none of those, return a 404 rather than an empty 200.
14335 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
14337 - Add an HSAuthorityRecordStats option that hidden service authorities
14338 can use to track statistics of overall hidden service usage without
14339 logging information that would be as useful to an attacker.
14340 - Allow multiple HiddenServicePort directives with the same virtual
14341 port; when they occur, the user is sent round-robin to one
14342 of the target ports chosen at random. Partially fixes bug 393 by
14343 adding limited ad-hoc round-robining.
14344 - Revamp file-writing logic so we don't need to have the entire
14345 contents of a file in memory at once before we write to disk. Tor,
14348 o Minor bugfixes (other):
14349 - Alter the code that tries to recover from unhandled write
14350 errors, to not try to flush onto a socket that's given us
14352 - Directory mirrors no longer include a guess at the client's IP
14353 address if the connection appears to be coming from the same /24
14354 network; it was producing too many wrong guesses.
14355 - If we're trying to flush the last bytes on a connection (for
14356 example, when answering a directory request), reset the
14357 time-to-give-up timeout every time we manage to write something
14359 - Reject router descriptors with out-of-range bandwidthcapacity or
14360 bandwidthburst values.
14361 - If we can't expand our list of entry guards (e.g. because we're
14362 using bridges or we have StrictEntryNodes set), don't mark relays
14363 down when they fail a directory request. Otherwise we're too quick
14364 to mark all our entry points down.
14365 - Authorities no longer send back "400 you're unreachable please fix
14366 it" errors to Tor servers that aren't online all the time. We're
14367 supposed to tolerate these servers now.
14368 - Let directory authorities startup even when they can't generate
14369 a descriptor immediately, e.g. because they don't know their
14371 - Correctly enforce that elements of directory objects do not appear
14372 more often than they are allowed to appear.
14373 - Stop allowing hibernating servers to be "stable" or "fast".
14374 - On Windows, we were preventing other processes from reading
14375 cached-routers while Tor was running. (Reported by janbar)
14376 - Check return values from pthread_mutex functions.
14377 - When opening /dev/null in finish_daemonize(), do not pass the
14378 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
14379 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
14381 o Controller features:
14382 - The GETCONF command now escapes and quotes configuration values
14383 that don't otherwise fit into the torrc file.
14384 - The SETCONF command now handles quoted values correctly.
14385 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
14386 ask about source, timestamp of arrival, purpose, etc. We need
14387 something like this to help Vidalia not do GeoIP lookups on bridge
14389 - Allow multiple HashedControlPassword config lines, to support
14390 multiple controller passwords.
14391 - Accept LF instead of CRLF on controller, since some software has a
14392 hard time generating real Internet newlines.
14393 - Add GETINFO values for the server status events
14394 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
14396 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
14397 GETINFO for Torstat to use until it can switch to using extrainfos.
14398 - New config option CookieAuthFile to choose a new location for the
14399 cookie authentication file, and config option
14400 CookieAuthFileGroupReadable to make it group-readable.
14401 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
14402 match requests to applications. Patch from Robert Hogan.
14403 - Add a RESOLVE command to launch hostname lookups. Original patch
14405 - Add GETINFO status/enough-dir-info to let controllers tell whether
14406 Tor has downloaded sufficient directory information. Patch from Tup.
14407 - You can now use the ControlSocket option to tell Tor to listen for
14408 controller connections on Unix domain sockets on systems that
14409 support them. Patch from Peter Palfrader.
14410 - New "GETINFO address-mappings/*" command to get address mappings
14411 with expiry information. "addr-mappings/*" is now deprecated.
14413 - Add a new config option __DisablePredictedCircuits designed for
14414 use by the controller, when we don't want Tor to build any circuits
14416 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
14417 so we can exit from the middle of the circuit.
14418 - Implement "getinfo status/circuit-established".
14419 - Implement "getinfo status/version/..." so a controller can tell
14420 whether the current version is recommended, and whether any versions
14421 are good, and how many authorities agree. Patch from "shibz".
14422 - Controllers should now specify cache=no or cache=yes when using
14423 the +POSTDESCRIPTOR command.
14424 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
14425 Robert Hogan. Fixes the first part of bug 681.
14426 - When reporting clock skew, and we know that the clock is _at least
14427 as skewed_ as some value, but we don't know the actual value,
14428 report the value as a "minimum skew."
14430 o Controller bugfixes:
14431 - Generate "STATUS_SERVER" events rather than misspelled
14432 "STATUS_SEVER" events. Caught by mwenge.
14433 - Reject controller commands over 1MB in length, so rogue
14434 processes can't run us out of memory.
14435 - Change the behavior of "getinfo status/good-server-descriptor"
14436 so it doesn't return failure when any authority disappears.
14437 - Send NAMESERVER_STATUS messages for a single failed nameserver
14439 - When the DANGEROUS_VERSION controller status event told us we're
14440 running an obsolete version, it used the string "OLD" to describe
14441 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
14442 "OBSOLETE" in both cases.
14443 - Respond to INT and TERM SIGNAL commands before we execute the
14444 signal, in case the signal shuts us down. We had a patch in
14445 0.1.2.1-alpha that tried to do this by queueing the response on
14446 the connection's buffer before shutting down, but that really
14447 isn't the same thing at all. Bug located by Matt Edman.
14448 - Provide DNS expiry times in GMT, not in local time. For backward
14449 compatibility, ADDRMAP events only provide GMT expiry in an extended
14450 field. "GETINFO address-mappings" always does the right thing.
14451 - Use CRLF line endings properly in NS events.
14452 - Make 'getinfo fingerprint' return a 551 error if we're not a
14453 server, so we match what the control spec claims we do. Reported
14455 - Fix a typo in an error message when extendcircuit fails that
14456 caused us to not follow the \r\n-based delimiter protocol. Reported
14458 - When tunneling an encrypted directory connection, and its first
14459 circuit fails, do not leave it unattached and ask the controller
14460 to deal. Fixes the second part of bug 681.
14461 - Treat some 403 responses from directory servers as INFO rather than
14462 WARN-severity events.
14464 o Portability / building / compiling:
14465 - When building with --enable-gcc-warnings, check for whether Apple's
14466 warning "-Wshorten-64-to-32" is available.
14467 - Support compilation to target iPhone; patch from cjacker huang.
14468 To build for iPhone, pass the --enable-iphone option to configure.
14469 - Port Tor to build and run correctly on Windows CE systems, using
14470 the wcecompat library. Contributed by Valerio Lupi.
14471 - Detect non-ASCII platforms (if any still exist) and refuse to
14472 build there: some of our code assumes that 'A' is 65 and so on.
14473 - Clear up some MIPSPro compiler warnings.
14474 - Make autoconf search for libevent, openssl, and zlib consistently.
14475 - Update deprecated macros in configure.in.
14476 - When warning about missing headers, tell the user to let us
14477 know if the compile succeeds anyway, so we can downgrade the
14479 - Include the current subversion revision as part of the version
14480 string: either fetch it directly if we're in an SVN checkout, do
14481 some magic to guess it if we're in an SVK checkout, or use
14482 the last-detected version if we're building from a .tar.gz.
14483 Use this version consistently in log messages.
14484 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
14485 - Read resolv.conf files correctly on platforms where read() returns
14486 partial results on small file reads.
14487 - Build without verbose warnings even on gcc 4.2 and 4.3.
14488 - On Windows, correctly detect errors when listing the contents of
14489 a directory. Fix from lodger.
14490 - Run 'make test' as part of 'make dist', so we stop releasing so
14491 many development snapshots that fail their unit tests.
14492 - Add support to detect Libevent versions in the 1.4.x series
14494 - Add command-line arguments to unit-test executable so that we can
14495 invoke any chosen test from the command line rather than having
14496 to run the whole test suite at once; and so that we can turn on
14497 logging for the unit tests.
14498 - Do not automatically run configure from autogen.sh. This
14499 non-standard behavior tended to annoy people who have built other
14501 - Fix a macro/CPP interaction that was confusing some compilers:
14502 some GCCs don't like #if/#endif pairs inside macro arguments.
14504 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
14505 Fixes bug 704; fix from Steven Murdoch.
14506 - Correctly detect transparent proxy support on Linux hosts that
14507 require in.h to be included before netfilter_ipv4.h. Patch
14510 o Logging improvements:
14511 - When we haven't had any application requests lately, don't bother
14512 logging that we have expired a bunch of descriptors.
14513 - When attempting to open a logfile fails, tell us why.
14514 - Only log guard node status when guard node status has changed.
14515 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
14516 make "INFO" 75% less verbose.
14517 - When SafeLogging is disabled, log addresses along with all TLS
14519 - Report TLS "zero return" case as a "clean close" and "IO error"
14520 as a "close". Stop calling closes "unexpected closes": existing
14521 Tors don't use SSL_close(), so having a connection close without
14522 the TLS shutdown handshake is hardly unexpected.
14523 - When we receive a consensus from the future, warn about skew.
14524 - Make "not enough dir info yet" warnings describe *why* Tor feels
14525 it doesn't have enough directory info yet.
14526 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
14527 consumers. (We already do this on HUP.)
14528 - Give more descriptive well-formedness errors for out-of-range
14529 hidden service descriptor/protocol versions.
14530 - Stop recommending that every server operator send mail to tor-ops.
14531 Resolves bug 597. Bugfix on 0.1.2.x.
14532 - Improve skew reporting: try to give the user a better log message
14533 about how skewed they are, and how much this matters.
14534 - New --quiet command-line option to suppress the default console log.
14535 Good in combination with --hash-password.
14536 - Don't complain that "your server has not managed to confirm that its
14537 ports are reachable" if we haven't been able to build any circuits
14539 - Detect the reason for failing to mmap a descriptor file we just
14540 wrote, and give a more useful log message. Fixes bug 533.
14541 - Always prepend "Bug: " to any log message about a bug.
14542 - When dumping memory usage, list bytes used in buffer memory
14544 - When running with dmalloc, dump more stats on hup and on exit.
14545 - Put a platform string (e.g. "Linux i686") in the startup log
14546 message, so when people paste just their logs, we know if it's
14547 OpenBSD or Windows or what.
14548 - When logging memory usage, break down memory used in buffers by
14550 - When we are reporting the DirServer line we just parsed, we were
14551 logging the second stanza of the key fingerprint, not the first.
14552 - Even though Windows is equally happy with / and \ as path separators,
14553 try to use \ consistently on Windows and / consistently on Unix: it
14554 makes the log messages nicer.
14555 - On OSX, stop warning the user that kqueue support in libevent is
14556 "experimental", since it seems to have worked fine for ages.
14558 o Contributed scripts and tools:
14559 - Update linux-tor-prio.sh script to allow QoS based on the uid of
14560 the Tor process. Patch from Marco Bonetti with tweaks from Mike
14562 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
14563 Unix users an easy way to script their Tor process (e.g. by
14564 adjusting bandwidth based on the time of the day).
14565 - In the exitlist script, only consider the most recently published
14566 server descriptor for each server. Also, when the user requests
14567 a list of servers that _reject_ connections to a given address,
14568 explicitly exclude the IPs that also have servers that accept
14569 connections to that address. Resolves bug 405.
14570 - Include a new contrib/tor-exit-notice.html file that exit relay
14571 operators can put on their website to help reduce abuse queries.
14573 o Newly deprecated features:
14574 - The status/version/num-versioning and status/version/num-concurring
14575 GETINFO controller options are no longer useful in the v3 directory
14576 protocol: treat them as deprecated, and warn when they're used.
14577 - The RedirectExits config option is now deprecated.
14579 o Removed features:
14580 - Drop the old code to choke directory connections when the
14581 corresponding OR connections got full: thanks to the cell queue
14582 feature, OR conns don't get full any more.
14583 - Remove the old "dns worker" server DNS code: it hasn't been default
14584 since 0.1.2.2-alpha, and all the servers are using the new
14586 - Remove the code to generate the oldest (v1) directory format.
14587 - Remove support for the old bw_accounting file: we've been storing
14588 bandwidth accounting information in the state file since
14589 0.1.2.5-alpha. This may result in bandwidth accounting errors
14590 if you try to upgrade from 0.1.1.x or earlier, or if you try to
14591 downgrade to 0.1.1.x or earlier.
14592 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
14593 it, it had no AES, and it hasn't seen any security patches since
14595 - Stop overloading the circuit_t.onionskin field for both "onionskin
14596 from a CREATE cell that we are waiting for a cpuworker to be
14597 assigned" and "onionskin from an EXTEND cell that we are going to
14598 send to an OR as soon as we are connected". Might help with bug 600.
14599 - Remove the tor_strpartition() function: its logic was confused,
14600 and it was only used for one thing that could be implemented far
14602 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
14603 and TorControl.py, as they use the old v0 controller protocol,
14604 and are obsoleted by TorFlow anyway.
14605 - Drop support for v1 rendezvous descriptors, since we never used
14606 them anyway, and the code has probably rotted by now. Based on
14607 patch from Karsten Loesing.
14608 - Stop allowing address masks that do not correspond to bit prefixes.
14609 We have warned about these for a really long time; now it's time
14610 to reject them. (Patch from croup.)
14611 - Remove an optimization in the AES counter-mode code that assumed
14612 that the counter never exceeded 2^68. When the counter can be set
14613 arbitrarily as an IV (as it is by Karsten's new hidden services
14614 code), this assumption no longer holds.
14615 - Disable the SETROUTERPURPOSE controller command: it is now
14619 Changes in version 0.1.2.19 - 2008-01-17
14620 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
14621 exit policy a little bit more conservative so it's safer to run an
14622 exit relay on a home system, and fixes a variety of smaller issues.
14625 - Exit policies now reject connections that are addressed to a
14626 relay's public (external) IP address too, unless
14627 ExitPolicyRejectPrivate is turned off. We do this because too
14628 many relays are running nearby to services that trust them based
14629 on network address.
14632 - When the clock jumps forward a lot, do not allow the bandwidth
14633 buckets to become negative. Fixes bug 544.
14634 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
14635 on every successful resolve. Reported by Mike Perry.
14636 - Purge old entries from the "rephist" database and the hidden
14637 service descriptor database even when DirPort is zero.
14638 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
14639 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
14640 crashing or mis-answering these requests.
14641 - When we decide to send a 503 response to a request for servers, do
14642 not then also send the server descriptors: this defeats the whole
14643 purpose. Fixes bug 539.
14646 - Changing the ExitPolicyRejectPrivate setting should cause us to
14647 rebuild our server descriptor.
14648 - Fix handling of hex nicknames when answering controller requests for
14649 networkstatus by name, or when deciding whether to warn about
14650 unknown routers in a config option. (Patch from mwenge.)
14651 - Fix a couple of hard-to-trigger autoconf problems that could result
14652 in really weird results on platforms whose sys/types.h files define
14653 nonstandard integer types.
14654 - Don't try to create the datadir when running --verify-config or
14655 --hash-password. Resolves bug 540.
14656 - If we were having problems getting a particular descriptor from the
14657 directory caches, and then we learned about a new descriptor for
14658 that router, we weren't resetting our failure count. Reported
14660 - Although we fixed bug 539 (where servers would send HTTP status 503
14661 responses _and_ send a body too), there are still servers out there
14662 that haven't upgraded. Therefore, make clients parse such bodies
14663 when they receive them.
14664 - Run correctly on systems where rlim_t is larger than unsigned long.
14665 This includes some 64-bit systems.
14666 - Run correctly on platforms (like some versions of OS X 10.5) where
14667 the real limit for number of open files is OPEN_FILES, not rlim_max
14668 from getrlimit(RLIMIT_NOFILES).
14669 - Avoid a spurious free on base64 failure.
14670 - Avoid segfaults on certain complex invocations of
14671 router_get_by_hexdigest().
14672 - Fix rare bug on REDIRECTSTREAM control command when called with no
14673 port set: it could erroneously report an error when none had
14677 Changes in version 0.1.2.18 - 2007-10-28
14678 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
14679 hidden service introduction that were causing huge delays, and a big
14680 bug that was causing some servers to disappear from the network status
14681 lists for a few hours each day.
14683 o Major bugfixes (crashes):
14684 - If a connection is shut down abruptly because of something that
14685 happened inside connection_flushed_some(), do not call
14686 connection_finished_flushing(). Should fix bug 451:
14687 "connection_stop_writing: Assertion conn->write_event failed"
14688 Bugfix on 0.1.2.7-alpha.
14689 - Fix possible segfaults in functions called from
14690 rend_process_relay_cell().
14692 o Major bugfixes (hidden services):
14693 - Hidden services were choosing introduction points uniquely by
14694 hexdigest, but when constructing the hidden service descriptor
14695 they merely wrote the (potentially ambiguous) nickname.
14696 - Clients now use the v2 intro format for hidden service
14697 connections: they specify their chosen rendezvous point by identity
14698 digest rather than by (potentially ambiguous) nickname. These
14699 changes could speed up hidden service connections dramatically.
14701 o Major bugfixes (other):
14702 - Stop publishing a new server descriptor just because we get a
14703 HUP signal. This led (in a roundabout way) to some servers getting
14704 dropped from the networkstatus lists for a few hours each day.
14705 - When looking for a circuit to cannibalize, consider family as well
14706 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
14707 circuit cannibalization).
14708 - When a router wasn't listed in a new networkstatus, we were leaving
14709 the flags for that router alone -- meaning it remained Named,
14710 Running, etc -- even though absence from the networkstatus means
14711 that it shouldn't be considered to exist at all anymore. Now we
14712 clear all the flags for routers that fall out of the networkstatus
14713 consensus. Fixes bug 529.
14716 - Don't try to access (or alter) the state file when running
14717 --list-fingerprint or --verify-config or --hash-password. Resolves
14719 - When generating information telling us how to extend to a given
14720 router, do not try to include the nickname if it is
14721 absent. Resolves bug 467.
14722 - Fix a user-triggerable segfault in expand_filename(). (There isn't
14723 a way to trigger this remotely.)
14724 - When sending a status event to the controller telling it that an
14725 OR address is reachable, set the port correctly. (Previously we
14726 were reporting the dir port.)
14727 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
14728 command. Bugfix on 0.1.2.17.
14729 - When loading bandwidth history, do not believe any information in
14730 the future. Fixes bug 434.
14731 - When loading entry guard information, do not believe any information
14733 - When we have our clock set far in the future and generate an
14734 onion key, then re-set our clock to be correct, we should not stop
14735 the onion key from getting rotated.
14736 - On some platforms, accept() can return a broken address. Detect
14737 this more quietly, and deal accordingly. Fixes bug 483.
14738 - It's not actually an error to find a non-pending entry in the DNS
14739 cache when canceling a pending resolve. Don't log unless stuff
14740 is fishy. Resolves bug 463.
14741 - Don't reset trusted dir server list when we set a configuration
14742 option. Patch from Robert Hogan.
14745 Changes in version 0.1.2.17 - 2007-08-30
14746 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
14747 X bundles. Vidalia 0.0.14 makes authentication required for the
14748 ControlPort in the default configuration, which addresses important
14749 security risks. Everybody who uses Vidalia (or another controller)
14752 In addition, this Tor update fixes major load balancing problems with
14753 path selection, which should speed things up a lot once many people
14756 o Major bugfixes (security):
14757 - We removed support for the old (v0) control protocol. It has been
14758 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
14759 become more of a headache than it's worth.
14761 o Major bugfixes (load balancing):
14762 - When choosing nodes for non-guard positions, weight guards
14763 proportionally less, since they already have enough load. Patch
14765 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
14766 will allow fast Tor servers to get more attention.
14767 - When we're upgrading from an old Tor version, forget our current
14768 guards and pick new ones according to the new weightings. These
14769 three load balancing patches could raise effective network capacity
14770 by a factor of four. Thanks to Mike Perry for measurements.
14772 o Major bugfixes (stream expiration):
14773 - Expire not-yet-successful application streams in all cases if
14774 they've been around longer than SocksTimeout. Right now there are
14775 some cases where the stream will live forever, demanding a new
14776 circuit every 15 seconds. Fixes bug 454; reported by lodger.
14778 o Minor features (controller):
14779 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
14780 is valid before any authentication has been received. It tells
14781 a controller what kind of authentication is expected, and what
14782 protocol is spoken. Implements proposal 119.
14784 o Minor bugfixes (performance):
14785 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
14786 greatly speeding up loading cached-routers from disk on startup.
14787 - Disable sentinel-based debugging for buffer code: we squashed all
14788 the bugs that this was supposed to detect a long time ago, and now
14789 its only effect is to change our buffer sizes from nice powers of
14790 two (which platform mallocs tend to like) to values slightly over
14791 powers of two (which make some platform mallocs sad).
14793 o Minor bugfixes (misc):
14794 - If exit bandwidth ever exceeds one third of total bandwidth, then
14795 use the correct formula to weight exit nodes when choosing paths.
14796 Based on patch from Mike Perry.
14797 - Choose perfectly fairly among routers when choosing by bandwidth and
14798 weighting by fraction of bandwidth provided by exits. Previously, we
14799 would choose with only approximate fairness, and correct ourselves
14800 if we ran off the end of the list.
14801 - If we require CookieAuthentication but we fail to write the
14802 cookie file, we would warn but not exit, and end up in a state
14803 where no controller could authenticate. Now we exit.
14804 - If we require CookieAuthentication, stop generating a new cookie
14805 every time we change any piece of our config.
14806 - Refuse to start with certain directory authority keys, and
14807 encourage people using them to stop.
14808 - Terminate multi-line control events properly. Original patch
14810 - Fix a minor memory leak when we fail to find enough suitable
14811 servers to choose a circuit.
14812 - Stop leaking part of the descriptor when we run into a particularly
14813 unparseable piece of it.
14816 Changes in version 0.1.2.16 - 2007-08-01
14817 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
14818 remote attacker in certain situations to rewrite the user's torrc
14819 configuration file. This can completely compromise anonymity of users
14820 in most configurations, including those running the Vidalia bundles,
14821 TorK, etc. Or worse.
14823 o Major security fixes:
14824 - Close immediately after missing authentication on control port;
14825 do not allow multiple authentication attempts.
14828 Changes in version 0.1.2.15 - 2007-07-17
14829 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
14830 problems, fixes compilation on BSD, and fixes a variety of other
14831 bugs. Everybody should upgrade.
14833 o Major bugfixes (compilation):
14834 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
14836 o Major bugfixes (crashes):
14837 - Try even harder not to dereference the first character after
14838 an mmap(). Reported by lodger.
14839 - Fix a crash bug in directory authorities when we re-number the
14840 routerlist while inserting a new router.
14841 - When the cached-routers file is an even multiple of the page size,
14842 don't run off the end and crash. (Fixes bug 455; based on idea
14844 - Fix eventdns.c behavior on Solaris: It is critical to include
14845 orconfig.h _before_ sys/types.h, so that we can get the expected
14846 definition of _FILE_OFFSET_BITS.
14848 o Major bugfixes (security):
14849 - Fix a possible buffer overrun when using BSD natd support. Bug
14851 - When sending destroy cells from a circuit's origin, don't include
14852 the reason for tearing down the circuit. The spec says we didn't,
14853 and now we actually don't. Reported by lodger.
14854 - Keep streamids from different exits on a circuit separate. This
14855 bug may have allowed other routers on a given circuit to inject
14856 cells into streams. Reported by lodger; fixes bug 446.
14857 - If there's a never-before-connected-to guard node in our list,
14858 never choose any guards past it. This way we don't expand our
14859 guard list unless we need to.
14861 o Minor bugfixes (guard nodes):
14862 - Weight guard selection by bandwidth, so that low-bandwidth nodes
14863 don't get overused as guards.
14865 o Minor bugfixes (directory):
14866 - Correctly count the number of authorities that recommend each
14867 version. Previously, we were under-counting by 1.
14868 - Fix a potential crash bug when we load many server descriptors at
14869 once and some of them make others of them obsolete. Fixes bug 458.
14871 o Minor bugfixes (hidden services):
14872 - Stop tearing down the whole circuit when the user asks for a
14873 connection to a port that the hidden service didn't configure.
14876 o Minor bugfixes (misc):
14877 - On Windows, we were preventing other processes from reading
14878 cached-routers while Tor was running. Reported by janbar.
14879 - Fix a possible (but very unlikely) bug in picking routers by
14880 bandwidth. Add a log message to confirm that it is in fact
14881 unlikely. Patch from lodger.
14882 - Backport a couple of memory leak fixes.
14883 - Backport miscellaneous cosmetic bugfixes.
14886 Changes in version 0.1.2.14 - 2007-05-25
14887 Tor 0.1.2.14 changes the addresses of two directory authorities (this
14888 change especially affects those who serve or use hidden services),
14889 and fixes several other crash- and security-related bugs.
14891 o Directory authority changes:
14892 - Two directory authorities (moria1 and moria2) just moved to new
14893 IP addresses. This change will particularly affect those who serve
14894 or use hidden services.
14896 o Major bugfixes (crashes):
14897 - If a directory server runs out of space in the connection table
14898 as it's processing a begin_dir request, it will free the exit stream
14899 but leave it attached to the circuit, leading to unpredictable
14900 behavior. (Reported by seeess, fixes bug 425.)
14901 - Fix a bug in dirserv_remove_invalid() that would cause authorities
14902 to corrupt memory under some really unlikely scenarios.
14903 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
14904 - Avoid segfaults when reading from mmaped descriptor file. (Reported
14907 o Major bugfixes (security):
14908 - When choosing an entry guard for a circuit, avoid using guards
14909 that are in the same family as the chosen exit -- not just guards
14910 that are exactly the chosen exit. (Reported by lodger.)
14912 o Major bugfixes (resource management):
14913 - If a directory authority is down, skip it when deciding where to get
14914 networkstatus objects or descriptors. Otherwise we keep asking
14915 every 10 seconds forever. Fixes bug 384.
14916 - Count it as a failure if we fetch a valid network-status but we
14917 don't want to keep it. Otherwise we'll keep fetching it and keep
14918 not wanting to keep it. Fixes part of bug 422.
14919 - If all of our dirservers have given us bad or no networkstatuses
14920 lately, then stop hammering them once per minute even when we
14921 think they're failed. Fixes another part of bug 422.
14924 - Actually set the purpose correctly for descriptors inserted with
14925 purpose=controller.
14926 - When we have k non-v2 authorities in our DirServer config,
14927 we ignored the last k authorities in the list when updating our
14929 - Correctly back-off from requesting router descriptors that we are
14930 having a hard time downloading.
14931 - Read resolv.conf files correctly on platforms where read() returns
14932 partial results on small file reads.
14933 - Don't rebuild the entire router store every time we get 32K of
14934 routers: rebuild it when the journal gets very large, or when
14935 the gaps in the store get very large.
14938 - When routers publish SVN revisions in their router descriptors,
14939 authorities now include those versions correctly in networkstatus
14941 - Warn when using a version of libevent before 1.3b to run a server on
14942 OSX or BSD: these versions interact badly with userspace threads.
14945 Changes in version 0.1.2.13 - 2007-04-24
14946 This release features some major anonymity fixes, such as safer path
14947 selection; better client performance; faster bootstrapping, better
14948 address detection, and better DNS support for servers; write limiting as
14949 well as read limiting to make servers easier to run; and a huge pile of
14950 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
14952 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
14953 of the Freenode IRC network, remembering his patience and vision for
14954 free speech on the Internet.
14956 o Major features, client performance:
14957 - Weight directory requests by advertised bandwidth. Now we can
14958 let servers enable write limiting but still allow most clients to
14959 succeed at their directory requests. (We still ignore weights when
14960 choosing a directory authority; I hope this is a feature.)
14961 - Stop overloading exit nodes -- avoid choosing them for entry or
14962 middle hops when the total bandwidth available from non-exit nodes
14963 is much higher than the total bandwidth available from exit nodes.
14964 - Rather than waiting a fixed amount of time between retrying
14965 application connections, we wait only 10 seconds for the first,
14966 10 seconds for the second, and 15 seconds for each retry after
14967 that. Hopefully this will improve the expected user experience.
14968 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
14969 to open a stream fails; now we do in more cases. This should
14970 make clients able to find a good exit faster in some cases, since
14971 unhandleable requests will now get an error rather than timing out.
14973 o Major features, client functionality:
14974 - Implement BEGIN_DIR cells, so we can connect to a directory
14975 server via TLS to do encrypted directory requests rather than
14976 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
14977 config options if you like. For now, this feature only works if
14978 you already have a descriptor for the destination dirserver.
14979 - Add support for transparent application connections: this basically
14980 bundles the functionality of trans-proxy-tor into the Tor
14981 mainline. Now hosts with compliant pf/netfilter implementations
14982 can redirect TCP connections straight to Tor without diverting
14983 through SOCKS. (Based on patch from tup.)
14984 - Add support for using natd; this allows FreeBSDs earlier than
14985 5.1.2 to have ipfw send connections through Tor without using
14986 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
14988 o Major features, servers:
14989 - Setting up a dyndns name for your server is now optional: servers
14990 with no hostname or IP address will learn their IP address by
14991 asking the directory authorities. This code only kicks in when you
14992 would normally have exited with a "no address" error. Nothing's
14993 authenticated, so use with care.
14994 - Directory servers now spool server descriptors, v1 directories,
14995 and v2 networkstatus objects to buffers as needed rather than en
14996 masse. They also mmap the cached-routers files. These steps save
14998 - Stop requiring clients to have well-formed certificates, and stop
14999 checking nicknames in certificates. (Clients have certificates so
15000 that they can look like Tor servers, but in the future we might want
15001 to allow them to look like regular TLS clients instead. Nicknames
15002 in certificates serve no purpose other than making our protocol
15003 easier to recognize on the wire.) Implements proposal 106.
15005 o Improvements on DNS support:
15006 - Add "eventdns" asynchronous dns library originally based on code
15007 from Adam Langley. Now we can discard the old rickety dnsworker
15008 concept, and support a wider variety of DNS functions. Allows
15009 multithreaded builds on NetBSD and OpenBSD again.
15010 - Add server-side support for "reverse" DNS lookups (using PTR
15011 records so clients can determine the canonical hostname for a given
15012 IPv4 address). Only supported by servers using eventdns; servers
15013 now announce in their descriptors if they don't support eventdns.
15014 - Workaround for name servers (like Earthlink's) that hijack failing
15015 DNS requests and replace the no-such-server answer with a "helpful"
15016 redirect to an advertising-driven search portal. Also work around
15017 DNS hijackers who "helpfully" decline to hijack known-invalid
15018 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
15019 lets you turn it off.
15020 - Servers now check for the case when common DNS requests are going to
15021 wildcarded addresses (i.e. all getting the same answer), and change
15022 their exit policy to reject *:* if it's happening.
15023 - When asked to resolve a hostname, don't use non-exit servers unless
15024 requested to do so. This allows servers with broken DNS to be
15025 useful to the network.
15026 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
15027 useless IPv6 DNS resolves.
15028 - Specify and implement client-side SOCKS5 interface for reverse DNS
15029 lookups (see doc/socks-extensions.txt). Also cache them.
15030 - When we change nameservers or IP addresses, reset and re-launch
15031 our tests for DNS hijacking.
15033 o Improvements on reachability testing:
15034 - Servers send out a burst of long-range padding cells once they've
15035 established that they're reachable. Spread them over 4 circuits,
15036 so hopefully a few will be fast. This exercises bandwidth and
15037 bootstraps them into the directory more quickly.
15038 - When we find our DirPort to be reachable, publish a new descriptor
15039 so we'll tell the world (reported by pnx).
15040 - Directory authorities now only decide that routers are reachable
15041 if their identity keys are as expected.
15042 - Do DirPort reachability tests less often, since a single test
15043 chews through many circuits before giving up.
15044 - Avoid some false positives during reachability testing: don't try
15045 to test via a server that's on the same /24 network as us.
15046 - Start publishing one minute or so after we find our ORPort
15047 to be reachable. This will help reduce the number of descriptors
15048 we have for ourselves floating around, since it's quite likely
15049 other things (e.g. DirPort) will change during that minute too.
15050 - Routers no longer try to rebuild long-term connections to directory
15051 authorities, and directory authorities no longer try to rebuild
15052 long-term connections to all servers. We still don't hang up
15053 connections in these two cases though -- we need to look at it
15054 more carefully to avoid flapping, and we likely need to wait til
15055 0.1.1.x is obsolete.
15057 o Improvements on rate limiting:
15058 - Enable write limiting as well as read limiting. Now we sacrifice
15059 capacity if we're pushing out lots of directory traffic, rather
15060 than overrunning the user's intended bandwidth limits.
15061 - Include TLS overhead when counting bandwidth usage; previously, we
15062 would count only the bytes sent over TLS, but not the bytes used
15064 - Servers decline directory requests much more aggressively when
15065 they're low on bandwidth. Otherwise they end up queueing more and
15066 more directory responses, which can't be good for latency.
15067 - But never refuse directory requests from local addresses.
15068 - Be willing to read or write on local connections (e.g. controller
15069 connections) even when the global rate limiting buckets are empty.
15070 - Flush local controller connection buffers periodically as we're
15071 writing to them, so we avoid queueing 4+ megabytes of data before
15073 - Revise and clean up the torrc.sample that we ship with; add
15074 a section for BandwidthRate and BandwidthBurst.
15076 o Major features, NT services:
15077 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
15078 command-line flag so that admins can override the default by saying
15079 "tor --service install --user "SomeUser"". This will not affect
15080 existing installed services. Also, warn the user that the service
15081 will look for its configuration file in the service user's
15082 %appdata% directory. (We can't do the "hardwire the user's appdata
15083 directory" trick any more, since we may not have read access to that
15085 - Support running the Tor service with a torrc not in the same
15086 directory as tor.exe and default to using the torrc located in
15087 the %appdata%\Tor\ of the user who installed the service. Patch
15089 - Add an --ignore-missing-torrc command-line option so that we can
15090 get the "use sensible defaults if the configuration file doesn't
15091 exist" behavior even when specifying a torrc location on the
15093 - When stopping an NT service, wait up to 10 sec for it to actually
15094 stop. (Patch from Matt Edman; resolves bug 295.)
15096 o Directory authority improvements:
15097 - Stop letting hibernating or obsolete servers affect uptime and
15099 - Stop listing hibernating servers in the v1 directory.
15100 - Authorities no longer recommend exits as guards if this would shift
15101 too much load to the exit nodes.
15102 - Authorities now specify server versions in networkstatus. This adds
15103 about 2% to the size of compressed networkstatus docs, and allows
15104 clients to tell which servers support BEGIN_DIR and which don't.
15105 The implementation is forward-compatible with a proposed future
15106 protocol version scheme not tied to Tor versions.
15107 - DirServer configuration lines now have an orport= option so
15108 clients can open encrypted tunnels to the authorities without
15109 having downloaded their descriptors yet. Enabled for moria1,
15110 moria2, tor26, and lefkada now in the default configuration.
15111 - Add a BadDirectory flag to network status docs so that authorities
15112 can (eventually) tell clients about caches they believe to be
15113 broken. Not used yet.
15114 - Allow authorities to list nodes as bad exits in their
15115 approved-routers file by fingerprint or by address. If most
15116 authorities set a BadExit flag for a server, clients don't think
15117 of it as a general-purpose exit. Clients only consider authorities
15118 that advertise themselves as listing bad exits.
15119 - Patch from Steve Hildrey: Generate network status correctly on
15120 non-versioning dirservers.
15121 - Have directory authorities allow larger amounts of drift in uptime
15122 without replacing the server descriptor: previously, a server that
15123 restarted every 30 minutes could have 48 "interesting" descriptors
15125 - Reserve the nickname "Unnamed" for routers that can't pick
15126 a hostname: any router can call itself Unnamed; directory
15127 authorities will never allocate Unnamed to any particular router;
15128 clients won't believe that any router is the canonical Unnamed.
15130 o Directory mirrors and clients:
15131 - Discard any v1 directory info that's over 1 month old (for
15132 directories) or over 1 week old (for running-routers lists).
15133 - Clients track responses with status 503 from dirservers. After a
15134 dirserver has given us a 503, we try not to use it until an hour has
15135 gone by, or until we have no dirservers that haven't given us a 503.
15136 - When we get a 503 from a directory, and we're not a server, we no
15137 longer count the failure against the total number of failures
15138 allowed for the object we're trying to download.
15139 - Prepare for servers to publish descriptors less often: never
15140 discard a descriptor simply for being too old until either it is
15141 recommended by no authorities, or until we get a better one for
15142 the same router. Make caches consider retaining old recommended
15143 routers for even longer.
15144 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
15145 headers for content, so that we can work better in the presence of
15146 caching HTTP proxies.
15147 - Stop fetching descriptors if you're not a dir mirror and you
15148 haven't tried to establish any circuits lately. (This currently
15149 causes some dangerous behavior, because when you start up again
15150 you'll use your ancient server descriptors.)
15152 o Major fixes, crashes:
15153 - Stop crashing when the controller asks us to resetconf more than
15154 one config option at once. (Vidalia 0.0.11 does this.)
15155 - Fix a longstanding obscure crash bug that could occur when we run
15156 out of DNS worker processes, if we're not using eventdns. (Resolves
15158 - Fix an assert that could trigger if a controller quickly set then
15159 cleared EntryNodes. (Bug found by Udo van den Heuvel.)
15160 - Avoid crash when telling controller about stream-status and a
15161 stream is detached.
15162 - Avoid sending junk to controllers or segfaulting when a controller
15163 uses EVENT_NEW_DESC with verbose nicknames.
15164 - Stop triggering asserts if the controller tries to extend hidden
15165 service circuits (reported by mwenge).
15166 - If we start a server with ClientOnly 1, then set ClientOnly to 0
15167 and hup, stop triggering an assert based on an empty onion_key.
15168 - Mask out all signals in sub-threads; only the libevent signal
15169 handler should be processing them. This should prevent some crashes
15170 on some machines using pthreads. (Patch from coderman.)
15171 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
15173 o Major fixes, anonymity/security:
15174 - Automatically avoid picking more than one node from the same
15175 /16 network when constructing a circuit. Add an
15176 "EnforceDistinctSubnets" option to let people disable it if they
15177 want to operate private test networks on a single subnet.
15178 - When generating bandwidth history, round down to the nearest
15179 1k. When storing accounting data, round up to the nearest 1k.
15180 - When we're running as a server, remember when we last rotated onion
15181 keys, so that we will rotate keys once they're a week old even if
15182 we never stay up for a week ourselves.
15183 - If a client asked for a server by name, and there's a named server
15184 in our network-status but we don't have its descriptor yet, we
15185 could return an unnamed server instead.
15186 - Reject (most) attempts to use Tor circuits with length one. (If
15187 many people start using Tor as a one-hop proxy, exit nodes become
15188 a more attractive target for compromise.)
15189 - Just because your DirPort is open doesn't mean people should be
15190 able to remotely teach you about hidden service descriptors. Now
15191 only accept rendezvous posts if you've got HSAuthoritativeDir set.
15192 - Fix a potential race condition in the rpm installer. Found by
15194 - Do not log IPs with TLS failures for incoming TLS
15195 connections. (Fixes bug 382.)
15197 o Major fixes, other:
15198 - If our system clock jumps back in time, don't publish a negative
15199 uptime in the descriptor.
15200 - When we start during an accounting interval before it's time to wake
15201 up, remember to wake up at the correct time. (May fix bug 342.)
15202 - Previously, we would cache up to 16 old networkstatus documents
15203 indefinitely, if they came from nontrusted authorities. Now we
15204 discard them if they are more than 10 days old.
15205 - When we have a state file we cannot parse, tell the user and
15206 move it aside. Now we avoid situations where the user starts
15207 Tor in 1904, Tor writes a state file with that timestamp in it,
15208 the user fixes her clock, and Tor refuses to start.
15209 - Publish a new descriptor after we hup/reload. This is important
15210 if our config has changed such that we'll want to start advertising
15211 our DirPort now, etc.
15212 - If we are using an exit enclave and we can't connect, e.g. because
15213 its webserver is misconfigured to not listen on localhost, then
15214 back off and try connecting from somewhere else before we fail.
15216 o New config options or behaviors:
15217 - When EntryNodes are configured, rebuild the guard list to contain,
15218 in order: the EntryNodes that were guards before; the rest of the
15219 EntryNodes; the nodes that were guards before.
15220 - Do not warn when individual nodes in the configuration's EntryNodes,
15221 ExitNodes, etc are down: warn only when all possible nodes
15222 are down. (Fixes bug 348.)
15223 - Put a lower-bound on MaxAdvertisedBandwidth.
15224 - Start using the state file to store bandwidth accounting data:
15225 the bw_accounting file is now obsolete. We'll keep generating it
15226 for a while for people who are still using 0.1.2.4-alpha.
15227 - Try to batch changes to the state file so that we do as few
15228 disk writes as possible while still storing important things in
15230 - The state file and the bw_accounting file get saved less often when
15231 the AvoidDiskWrites config option is set.
15232 - Make PIDFile work on Windows.
15233 - Add internal descriptions for a bunch of configuration options:
15234 accessible via controller interface and in comments in saved
15236 - Reject *:563 (NNTPS) in the default exit policy. We already reject
15237 NNTP by default, so this seems like a sensible addition.
15238 - Clients now reject hostnames with invalid characters. This should
15239 avoid some inadvertent info leaks. Add an option
15240 AllowNonRFC953Hostnames to disable this behavior, in case somebody
15241 is running a private network with hosts called @, !, and #.
15242 - Check for addresses with invalid characters at the exit as well,
15243 and warn less verbosely when they fail. You can override this by
15244 setting ServerDNSAllowNonRFC953Addresses to 1.
15245 - Remove some options that have been deprecated since at least
15246 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
15247 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
15248 to set log options. Mark PathlenCoinWeight as obsolete.
15249 - Stop accepting certain malformed ports in configured exit policies.
15250 - When the user uses bad syntax in the Log config line, stop
15251 suggesting other bad syntax as a replacement.
15252 - Add new config option "ResolvConf" to let the server operator
15253 choose an alternate resolve.conf file when using eventdns.
15254 - If one of our entry guards is on the ExcludeNodes list, or the
15255 directory authorities don't think it's a good guard, treat it as
15256 if it were unlisted: stop using it as a guard, and throw it off
15257 the guards list if it stays that way for a long time.
15258 - Allow directory authorities to be marked separately as authorities
15259 for the v1 directory protocol, the v2 directory protocol, and
15260 as hidden service directories, to make it easier to retire old
15261 authorities. V1 authorities should set "HSAuthoritativeDir 1"
15262 to continue being hidden service authorities too.
15263 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
15264 - Make TrackExitHosts case-insensitive, and fix the behavior of
15265 ".suffix" TrackExitHosts items to avoid matching in the middle of
15267 - New DirPort behavior: if you have your dirport set, you download
15268 descriptors aggressively like a directory mirror, whether or not
15269 your ORPort is set.
15272 - Create a new file ReleaseNotes which was the old ChangeLog. The
15273 new ChangeLog file now includes the notes for all development
15275 - Add a new address-spec.txt document to describe our special-case
15276 addresses: .exit, .onion, and .noconnnect.
15277 - Fork the v1 directory protocol into its own spec document,
15278 and mark dir-spec.txt as the currently correct (v2) spec.
15280 o Packaging, porting, and contrib
15281 - "tor --verify-config" now exits with -1(255) or 0 depending on
15282 whether the config options are bad or good.
15283 - The Debian package now uses --verify-config when (re)starting,
15284 to distinguish configuration errors from other errors.
15285 - Adapt a patch from goodell to let the contrib/exitlist script
15286 take arguments rather than require direct editing.
15287 - Prevent the contrib/exitlist script from printing the same
15288 result more than once.
15289 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
15290 - In the hidden service example in torrc.sample, stop recommending
15291 esoteric and discouraged hidden service options.
15292 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
15293 values before failing, and always enables eventdns.
15294 - Try to detect Windows correctly when cross-compiling.
15295 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
15296 Try to fix this in configure.in by checking for most functions
15297 before we check for libevent.
15298 - Update RPMs to require libevent 1.2.
15299 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
15300 or later. Log when we are doing this, so we can diagnose it when
15301 it fails. (Also, recommend libevent 1.1b for kqueue and
15302 win32 methods; deprecate libevent 1.0b harder; make libevent
15303 recommendation system saner.)
15304 - Build with recent (1.3+) libevents on platforms that do not
15305 define the nonstandard types "u_int8_t" and friends.
15306 - Remove architecture from OS X builds. The official builds are
15307 now universal binaries.
15308 - Run correctly on OS X platforms with case-sensitive filesystems.
15309 - Correctly set maximum connection limit on Cygwin. (This time
15311 - Start compiling on MinGW on Windows (patches from Mike Chiussi
15313 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
15314 - Finally fix the openssl warnings from newer gccs that believe that
15315 ignoring a return value is okay, but casting a return value and
15316 then ignoring it is a sign of madness.
15317 - On architectures where sizeof(int)>4, still clamp declarable
15318 bandwidth to INT32_MAX.
15320 o Minor features, controller:
15321 - Warn the user when an application uses the obsolete binary v0
15322 control protocol. We're planning to remove support for it during
15323 the next development series, so it's good to give people some
15325 - Add STREAM_BW events to report per-entry-stream bandwidth
15326 use. (Patch from Robert Hogan.)
15327 - Rate-limit SIGNEWNYM signals in response to controllers that
15328 impolitely generate them for every single stream. (Patch from
15329 mwenge; closes bug 394.)
15330 - Add a REMAP status to stream events to note that a stream's
15331 address has changed because of a cached address or a MapAddress
15333 - Make REMAP stream events have a SOURCE (cache or exit), and
15334 make them generated in every case where we get a successful
15335 connected or resolved cell.
15336 - Track reasons for OR connection failure; make these reasons
15337 available via the controller interface. (Patch from Mike Perry.)
15338 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
15339 can learn when clients are sending malformed hostnames to Tor.
15340 - Specify and implement some of the controller status events.
15341 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
15342 - Reimplement GETINFO so that info/names stays in sync with the
15344 - Implement "GETINFO fingerprint".
15345 - Implement "SETEVENTS GUARD" so controllers can get updates on
15346 entry guard status as it changes.
15347 - Make all connections to addresses of the form ".noconnect"
15348 immediately get closed. This lets application/controller combos
15349 successfully test whether they're talking to the same Tor by
15350 watching for STREAM events.
15351 - Add a REASON field to CIRC events; for backward compatibility, this
15352 field is sent only to controllers that have enabled the extended
15353 event format. Also, add additional reason codes to explain why
15354 a given circuit has been destroyed or truncated. (Patches from
15356 - Add a REMOTE_REASON field to extended CIRC events to tell the
15357 controller why a remote OR told us to close a circuit.
15358 - Stream events also now have REASON and REMOTE_REASON fields,
15359 working much like those for circuit events.
15360 - There's now a GETINFO ns/... field so that controllers can ask Tor
15361 about the current status of a router.
15362 - A new event type "NS" to inform a controller when our opinion of
15363 a router's status has changed.
15364 - Add a GETINFO events/names and GETINFO features/names so controllers
15365 can tell which events and features are supported.
15366 - A new CLEARDNSCACHE signal to allow controllers to clear the
15367 client-side DNS cache without expiring circuits.
15368 - Fix CIRC controller events so that controllers can learn the
15369 identity digests of non-Named servers used in circuit paths.
15370 - Let controllers ask for more useful identifiers for servers. Instead
15371 of learning identity digests for un-Named servers and nicknames
15372 for Named servers, the new identifiers include digest, nickname,
15373 and indication of Named status. Off by default; see control-spec.txt
15374 for more information.
15375 - Add a "getinfo address" controller command so it can display Tor's
15376 best guess to the user.
15377 - New controller event to alert the controller when our server
15378 descriptor has changed.
15379 - Give more meaningful errors on controller authentication failure.
15380 - Export the default exit policy via the control port, so controllers
15381 don't need to guess what it is / will be later.
15383 o Minor bugfixes, controller:
15384 - When creating a circuit via the controller, send a 'launched'
15385 event when we're done, so we follow the spec better.
15386 - Correct the control spec to match how the code actually responds
15387 to 'getinfo addr-mappings/*'. Reported by daejees.
15388 - The control spec described a GUARDS event, but the code
15389 implemented a GUARD event. Standardize on GUARD, but let people
15390 ask for GUARDS too. Reported by daejees.
15391 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
15392 clear the corresponding on_circuit variable, and remember later
15393 that we don't need to send a redundant CLOSED event. (Resolves part
15395 - Report events where a resolve succeeded or where we got a socks
15396 protocol error correctly, rather than calling both of them
15398 - Change reported stream target addresses to IP consistently when
15399 we finally get the IP from an exit node.
15400 - Send log messages to the controller even if they happen to be very
15402 - Flush ERR-level controller status events just like we currently
15403 flush ERR-level log events, so that a Tor shutdown doesn't prevent
15404 the controller from learning about current events.
15405 - Report the circuit number correctly in STREAM CLOSED events. Bug
15406 reported by Mike Perry.
15407 - Do not report bizarre values for results of accounting GETINFOs
15408 when the last second's write or read exceeds the allotted bandwidth.
15409 - Report "unrecognized key" rather than an empty string when the
15410 controller tries to fetch a networkstatus that doesn't exist.
15411 - When the controller does a "GETINFO network-status", tell it
15412 about even those routers whose descriptors are very old, and use
15413 long nicknames where appropriate.
15414 - Fix handling of verbose nicknames with ORCONN controller events:
15415 make them show up exactly when requested, rather than exactly when
15417 - Controller signals now work on non-Unix platforms that don't define
15418 SIGUSR1 and SIGUSR2 the way we expect.
15419 - Respond to SIGNAL command before we execute the signal, in case
15420 the signal shuts us down. Suggested by Karsten Loesing.
15421 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
15423 o Minor features, code performance:
15424 - Major performance improvement on inserting descriptors: change
15425 algorithm from O(n^2) to O(n).
15426 - Do not rotate onion key immediately after setting it for the first
15428 - Call router_have_min_dir_info half as often. (This is showing up in
15429 some profiles, but not others.)
15430 - When using GCC, make log_debug never get called at all, and its
15431 arguments never get evaluated, when no debug logs are configured.
15432 (This is showing up in some profiles, but not others.)
15433 - Statistics dumped by -USR2 now include a breakdown of public key
15434 operations, for profiling.
15435 - Make the common memory allocation path faster on machines where
15436 malloc(0) returns a pointer.
15437 - Split circuit_t into origin_circuit_t and or_circuit_t, and
15438 split connection_t into edge, or, dir, control, and base structs.
15439 These will save quite a bit of memory on busy servers, and they'll
15440 also help us track down bugs in the code and bugs in the spec.
15441 - Use OpenSSL's AES implementation on platforms where it's faster.
15442 This could save us as much as 10% CPU usage.
15444 o Minor features, descriptors and descriptor handling:
15445 - Avoid duplicate entries on MyFamily line in server descriptor.
15446 - When Tor receives a router descriptor that it asked for, but
15447 no longer wants (because it has received fresh networkstatuses
15448 in the meantime), do not warn the user. Cache the descriptor if
15449 we're a cache; drop it if we aren't.
15450 - Servers no longer ever list themselves in their "family" line,
15451 even if configured to do so. This makes it easier to configure
15452 family lists conveniently.
15454 o Minor fixes, confusing/misleading log messages:
15455 - Display correct results when reporting which versions are
15456 recommended, and how recommended they are. (Resolves bug 383.)
15457 - Inform the server operator when we decide not to advertise a
15458 DirPort due to AccountingMax enabled or a low BandwidthRate.
15459 - Only include function names in log messages for info/debug messages.
15460 For notice/warn/err, the content of the message should be clear on
15461 its own, and printing the function name only confuses users.
15462 - Remove even more protocol-related warnings from Tor server logs,
15463 such as bad TLS handshakes and malformed begin cells.
15464 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
15465 when the IP address is mapped through MapAddress to a hostname.
15466 - Fix misleading log messages: an entry guard that is "unlisted",
15467 as well as not known to be "down" (because we've never heard
15468 of it), is not therefore "up".
15470 o Minor fixes, old/obsolete behavior:
15471 - Start assuming we can use a create_fast cell if we don't know
15472 what version a router is running.
15473 - We no longer look for identity and onion keys in "identity.key" and
15474 "onion.key" -- these were replaced by secret_id_key and
15475 secret_onion_key in 0.0.8pre1.
15476 - We no longer require unrecognized directory entries to be
15478 - Drop compatibility with obsolete Tors that permit create cells
15479 to have the wrong circ_id_type.
15480 - Remove code to special-case "-cvs" ending, since it has not
15481 actually mattered since 0.0.9.
15482 - Don't re-write the fingerprint file every restart, unless it has
15485 o Minor fixes, misc client-side behavior:
15486 - Always remove expired routers and networkstatus docs before checking
15487 whether we have enough information to build circuits. (Fixes
15489 - When computing clock skew from directory HTTP headers, consider what
15490 time it was when we finished asking for the directory, not what
15492 - Make our socks5 handling more robust to broken socks clients:
15493 throw out everything waiting on the buffer in between socks
15494 handshake phases, since they can't possibly (so the theory
15495 goes) have predicted what we plan to respond to them.
15496 - Expire socks connections if they spend too long waiting for the
15497 handshake to finish. Previously we would let them sit around for
15498 days, if the connecting application didn't close them either.
15499 - And if the socks handshake hasn't started, don't send a
15500 "DNS resolve socks failed" handshake reply; just close it.
15501 - If the user asks to use invalid exit nodes, be willing to use
15503 - Track unreachable entry guards correctly: don't conflate
15504 'unreachable by us right now' with 'listed as down by the directory
15505 authorities'. With the old code, if a guard was unreachable by us
15506 but listed as running, it would clog our guard list forever.
15507 - Behave correctly in case we ever have a network with more than
15508 2GB/s total advertised capacity.
15509 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
15510 - Fix a memory leak when we ask for "all" networkstatuses and we
15511 get one we don't recognize.
15514 Changes in version 0.1.1.26 - 2006-12-14
15515 o Security bugfixes:
15516 - Stop sending the HttpProxyAuthenticator string to directory
15517 servers when directory connections are tunnelled through Tor.
15518 - Clients no longer store bandwidth history in the state file.
15519 - Do not log introduction points for hidden services if SafeLogging
15523 - Fix an assert failure when a directory authority sets
15524 AuthDirRejectUnlisted and then receives a descriptor from an
15525 unlisted router (reported by seeess).
15528 Changes in version 0.1.1.25 - 2006-11-04
15530 - When a client asks us to resolve (rather than connect to)
15531 an address, and we have a cached answer, give them the cached
15532 answer. Previously, we would give them no answer at all.
15533 - We were building exactly the wrong circuits when we predict
15534 hidden service requirements, meaning Tor would have to build all
15535 its circuits on demand.
15536 - If none of our live entry guards have a high uptime, but we
15537 require a guard with a high uptime, try adding a new guard before
15538 we give up on the requirement. This patch should make long-lived
15539 connections more stable on average.
15540 - When testing reachability of our DirPort, don't launch new
15541 tests when there's already one in progress -- unreachable
15542 servers were stacking up dozens of testing streams.
15544 o Security bugfixes:
15545 - When the user sends a NEWNYM signal, clear the client-side DNS
15546 cache too. Otherwise we continue to act on previous information.
15549 - Avoid a memory corruption bug when creating a hash table for
15551 - Avoid possibility of controller-triggered crash when misusing
15552 certain commands from a v0 controller on platforms that do not
15553 handle printf("%s",NULL) gracefully.
15554 - Avoid infinite loop on unexpected controller input.
15555 - Don't log spurious warnings when we see a circuit close reason we
15556 don't recognize; it's probably just from a newer version of Tor.
15557 - Add Vidalia to the OS X uninstaller script, so when we uninstall
15558 Tor/Privoxy we also uninstall Vidalia.
15561 Changes in version 0.1.1.24 - 2006-09-29
15563 - Allow really slow clients to not hang up five minutes into their
15564 directory downloads (suggested by Adam J. Richter).
15565 - Fix major performance regression from 0.1.0.x: instead of checking
15566 whether we have enough directory information every time we want to
15567 do something, only check when the directory information has changed.
15568 This should improve client CPU usage by 25-50%.
15569 - Don't crash if, after a server has been running for a while,
15570 it can't resolve its hostname.
15571 - When a client asks us to resolve (not connect to) an address,
15572 and we have a cached answer, give them the cached answer.
15573 Previously, we would give them no answer at all.
15576 - Allow Tor to start when RunAsDaemon is set but no logs are set.
15577 - Don't crash when the controller receives a third argument to an
15578 "extendcircuit" request.
15579 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
15580 response; fix error code when "getinfo dir/status/" fails.
15581 - Fix configure.in to not produce broken configure files with
15582 more recent versions of autoconf. Thanks to Clint for his auto*
15584 - Fix security bug on NetBSD that could allow someone to force
15585 uninitialized RAM to be sent to a server's DNS resolver. This
15586 only affects NetBSD and other platforms that do not bounds-check
15588 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
15589 methods: these are known to be buggy.
15590 - If we're a directory mirror and we ask for "all" network status
15591 documents, we would discard status documents from authorities
15592 we don't recognize.
15595 Changes in version 0.1.1.23 - 2006-07-30
15597 - Fast Tor servers, especially exit nodes, were triggering asserts
15598 due to a bug in handling the list of pending DNS resolves. Some
15599 bugs still remain here; we're hunting them.
15600 - Entry guards could crash clients by sending unexpected input.
15601 - More fixes on reachability testing: if you find yourself reachable,
15602 then don't ever make any client requests (so you stop predicting
15603 circuits), then hup or have your clock jump, then later your IP
15604 changes, you won't think circuits are working, so you won't try to
15605 test reachability, so you won't publish.
15608 - Avoid a crash if the controller does a resetconf firewallports
15609 and then a setconf fascistfirewall=1.
15610 - Avoid an integer underflow when the dir authority decides whether
15611 a router is stable: we might wrongly label it stable, and compute
15612 a slightly wrong median stability, when a descriptor is published
15614 - Fix a place where we might trigger an assert if we can't build our
15615 own server descriptor yet.
15618 Changes in version 0.1.1.22 - 2006-07-05
15620 - Fix a big bug that was causing servers to not find themselves
15621 reachable if they changed IP addresses. Since only 0.1.1.22+
15622 servers can do reachability testing correctly, now we automatically
15623 make sure to test via one of these.
15624 - Fix to allow clients and mirrors to learn directory info from
15625 descriptor downloads that get cut off partway through.
15626 - Directory authorities had a bug in deciding if a newly published
15627 descriptor was novel enough to make everybody want a copy -- a few
15628 servers seem to be publishing new descriptors many times a minute.
15630 - Fix a rare bug that was causing some servers to complain about
15631 "closing wedged cpuworkers" and skip some circuit create requests.
15632 - Make the Exit flag in directory status documents actually work.
15635 Changes in version 0.1.1.21 - 2006-06-10
15636 o Crash and assert fixes from 0.1.1.20:
15637 - Fix a rare crash on Tor servers that have enabled hibernation.
15638 - Fix a seg fault on startup for Tor networks that use only one
15639 directory authority.
15640 - Fix an assert from a race condition that occurs on Tor servers
15641 while exiting, where various threads are trying to log that they're
15642 exiting, and delete the logs, at the same time.
15643 - Make our unit tests pass again on certain obscure platforms.
15646 - Add support for building SUSE RPM packages.
15647 - Speed up initial bootstrapping for clients: if we are making our
15648 first ever connection to any entry guard, then don't mark it down
15650 - When only one Tor server in the network is labelled as a guard,
15651 and we've already picked him, we would cycle endlessly picking him
15652 again, being unhappy about it, etc. Now we specifically exclude
15653 current guards when picking a new guard.
15654 - Servers send create cells more reliably after the TLS connection
15655 is established: we were sometimes forgetting to send half of them
15656 when we had more than one pending.
15657 - If we get a create cell that asks us to extend somewhere, but the
15658 Tor server there doesn't match the expected digest, we now send
15659 a destroy cell back, rather than silently doing nothing.
15660 - Make options->RedirectExit work again.
15661 - Make cookie authentication for the controller work again.
15662 - Stop being picky about unusual characters in the arguments to
15663 mapaddress. It's none of our business.
15664 - Add a new config option "TestVia" that lets you specify preferred
15665 middle hops to use for test circuits. Perhaps this will let me
15666 debug the reachability problems better.
15668 o Log / documentation fixes:
15669 - If we're a server and some peer has a broken TLS certificate, don't
15670 log about it unless ProtocolWarnings is set, i.e., we want to hear
15671 about protocol violations by others.
15672 - Fix spelling of VirtualAddrNetwork in man page.
15673 - Add a better explanation at the top of the autogenerated torrc file
15674 about what happened to our old torrc.
15677 Changes in version 0.1.1.20 - 2006-05-23
15678 o Crash and assert fixes from 0.1.0.17:
15679 - Fix assert bug in close_logs() on exit: when we close and delete
15680 logs, remove them all from the global "logfiles" list.
15681 - Fix an assert error when we're out of space in the connection_list
15682 and we try to post a hidden service descriptor (reported by Peter
15684 - Fix a rare assert error when we've tried all intro points for
15685 a hidden service and we try fetching the service descriptor again:
15686 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed".
15687 - Setconf SocksListenAddress kills Tor if it fails to bind. Now back
15688 out and refuse the setconf if it would fail.
15689 - If you specify a relative torrc path and you set RunAsDaemon in
15690 your torrc, then it chdir()'s to the new directory. If you then
15691 HUP, it tries to load the new torrc location, fails, and exits.
15692 The fix: no longer allow a relative path to torrc when using -f.
15693 - Check for integer overflows in more places, when adding elements
15694 to smartlists. This could possibly prevent a buffer overflow
15695 on malicious huge inputs.
15697 o Security fixes, major:
15698 - When we're printing strings from the network, don't try to print
15699 non-printable characters. Now we're safer against shell escape
15700 sequence exploits, and also against attacks to fool users into
15701 misreading their logs.
15702 - Implement entry guards: automatically choose a handful of entry
15703 nodes and stick with them for all circuits. Only pick new guards
15704 when the ones you have are unsuitable, and if the old guards
15705 become suitable again, switch back. This will increase security
15706 dramatically against certain end-point attacks. The EntryNodes
15707 config option now provides some hints about which entry guards you
15708 want to use most; and StrictEntryNodes means to only use those.
15709 Fixes CVE-2006-0414.
15710 - Implement exit enclaves: if we know an IP address for the
15711 destination, and there's a running Tor server at that address
15712 which allows exit to the destination, then extend the circuit to
15713 that exit first. This provides end-to-end encryption and end-to-end
15714 authentication. Also, if the user wants a .exit address or enclave,
15715 use 4 hops rather than 3, and cannibalize a general circ for it
15717 - Obey our firewall options more faithfully:
15718 . If we can't get to a dirserver directly, try going via Tor.
15719 . Don't ever try to connect (as a client) to a place our
15720 firewall options forbid.
15721 . If we specify a proxy and also firewall options, obey the
15722 firewall options even when we're using the proxy: some proxies
15723 can only proxy to certain destinations.
15724 - Make clients regenerate their keys when their IP address changes.
15725 - For the OS X package's modified privoxy config file, comment
15726 out the "logfile" line so we don't log everything passed
15728 - Our TLS handshakes were generating a single public/private
15729 keypair for the TLS context, rather than making a new one for
15730 each new connection. Oops. (But we were still rotating them
15731 periodically, so it's not so bad.)
15732 - When we were cannibalizing a circuit with a particular exit
15733 node in mind, we weren't checking to see if that exit node was
15734 already present earlier in the circuit. Now we are.
15735 - Require server descriptors to list IPv4 addresses -- hostnames
15736 are no longer allowed. This also fixes potential vulnerabilities
15737 to servers providing hostnames as their address and then
15738 preferentially resolving them so they can partition users.
15739 - Our logic to decide if the OR we connected to was the right guy
15740 was brittle and maybe open to a mitm for invalid routers.
15742 o Security fixes, minor:
15743 - Adjust tor-spec.txt to parameterize cell and key lengths. Now
15744 Ian Goldberg can prove things about our handshake protocol more
15746 - Make directory authorities generate a separate "guard" flag to
15747 mean "would make a good entry guard". Clients now honor the
15748 is_guard flag rather than looking at is_fast or is_stable.
15749 - Try to list MyFamily elements by key, not by nickname, and warn
15750 if we've not heard of a server.
15751 - Start using RAND_bytes rather than RAND_pseudo_bytes from
15752 OpenSSL. Also, reseed our entropy every hour, not just at
15753 startup. And add entropy in 512-bit chunks, not 160-bit chunks.
15754 - Refuse server descriptors where the fingerprint line doesn't match
15755 the included identity key. Tor doesn't care, but other apps (and
15756 humans) might actually be trusting the fingerprint line.
15757 - We used to kill the circuit when we receive a relay command we
15758 don't recognize. Now we just drop that cell.
15759 - Fix a bug found by Lasse Overlier: when we were making internal
15760 circuits (intended to be cannibalized later for rendezvous and
15761 introduction circuits), we were picking them so that they had
15762 useful exit nodes. There was no need for this, and it actually
15763 aids some statistical attacks.
15764 - Start treating internal circuits and exit circuits separately.
15765 It's important to keep them separate because internal circuits
15766 have their last hops picked like middle hops, rather than like
15767 exit hops. So exiting on them will break the user's expectations.
15768 - Fix a possible way to DoS dirservers.
15769 - When the client asked for a rendezvous port that the hidden
15770 service didn't want to provide, we were sending an IP address
15771 back along with the end cell. Fortunately, it was zero. But stop
15774 o Packaging improvements:
15775 - Implement --with-libevent-dir option to ./configure. Improve
15776 search techniques to find libevent, and use those for openssl too.
15777 - Fix a couple of bugs in OpenSSL detection. Deal better when
15778 there are multiple SSLs installed with different versions.
15779 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
15780 - On non-gcc compilers (e.g. Solaris's cc), use "-g -O" instead of
15782 - Make unit tests (and other invocations that aren't the real Tor)
15783 run without launching listeners, creating subdirectories, and so on.
15784 - The OS X installer was adding a symlink for tor_resolve but
15785 the binary was called tor-resolve (reported by Thomas Hardly).
15786 - Now we can target arch and OS in rpm builds (contributed by
15787 Phobos). Also make the resulting dist-rpm filename match the
15789 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
15790 if you log to syslog and want something other than LOG_DAEMON.
15791 - Fix the torify (tsocks) config file to not use Tor for localhost
15793 - Start shipping socks-extensions.txt, tor-doc-unix.html,
15794 tor-doc-server.html, and stylesheet.css in the tarball.
15795 - Stop shipping tor-doc.html, INSTALL, and README in the tarball.
15796 They are useless now.
15797 - Add Peter Palfrader's contributed check-tor script. It lets you
15798 easily check whether a given server (referenced by nickname)
15799 is reachable by you.
15800 - Add BSD-style contributed startup script "rc.subr" from Peter
15803 o Directory improvements -- new directory protocol:
15804 - See tor/doc/dir-spec.txt for all the juicy details. Key points:
15805 - Authorities and caches publish individual descriptors (by
15806 digest, by fingerprint, by "all", and by "tell me yours").
15807 - Clients don't download or use the old directory anymore. Now they
15808 download network-statuses from the directory authorities, and
15809 fetch individual server descriptors as needed from mirrors.
15810 - Clients don't download descriptors of non-running servers.
15811 - Download descriptors by digest, not by fingerprint. Caches try to
15812 download all listed digests from authorities; clients try to
15813 download "best" digests from caches. This avoids partitioning
15814 and isolating attacks better.
15815 - Only upload a new server descriptor when options change, 18
15816 hours have passed, uptime is reset, or bandwidth changes a lot.
15817 - Directory authorities silently throw away new descriptors that
15818 haven't changed much if the timestamps are similar. We do this to
15819 tolerate older Tor servers that upload a new descriptor every 15
15820 minutes. (It seemed like a good idea at the time.)
15821 - Clients choose directory servers from the network status lists,
15822 not from their internal list of router descriptors. Now they can
15823 go to caches directly rather than needing to go to authorities
15824 to bootstrap the first set of descriptors.
15825 - When picking a random directory, prefer non-authorities if any
15827 - Add a new flag to network-status indicating whether the server
15828 can answer v2 directory requests too.
15829 - Directory mirrors now cache up to 16 unrecognized network-status
15830 docs, so new directory authorities will be cached too.
15831 - Stop parsing, storing, or using running-routers output (but
15832 mirrors still cache and serve it).
15833 - Clients consider a threshold of "versioning" directory authorities
15834 before deciding whether to warn the user that he's obsolete.
15835 - Authorities publish separate sorted lists of recommended versions
15836 for clients and for servers.
15837 - Change DirServers config line to note which dirs are v1 authorities.
15838 - Put nicknames on the DirServer line, so we can refer to them
15839 without requiring all our users to memorize their IP addresses.
15840 - Remove option when getting directory cache to see whether they
15841 support running-routers; they all do now. Replace it with one
15842 to see whether caches support v2 stuff.
15843 - Stop listing down or invalid nodes in the v1 directory. This
15844 reduces its bulk by about 1/3, and reduces load on mirrors.
15845 - Mirrors no longer cache the v1 directory as often.
15846 - If we as a directory mirror don't know of any v1 directory
15847 authorities, then don't try to cache any v1 directories.
15849 o Other directory improvements:
15850 - Add lefkada.eecs.harvard.edu and tor.dizum.com as fourth and
15851 fifth authoritative directory servers.
15852 - Directory authorities no longer require an open connection from
15853 a server to consider him "reachable". We need this change because
15854 when we add new directory authorities, old servers won't know not
15855 to hang up on them.
15856 - Dir authorities now do their own external reachability testing
15857 of each server, and only list as running the ones they found to
15858 be reachable. We also send back warnings to the server's logs if
15859 it uploads a descriptor that we already believe is unreachable.
15860 - Spread the directory authorities' reachability testing over the
15861 entire testing interval, so we don't try to do 500 TLS's at once
15863 - Make the "stable" router flag in network-status be the median of
15864 the uptimes of running valid servers, and make clients pay
15865 attention to the network-status flags. Thus the cutoff adapts
15866 to the stability of the network as a whole, making IRC, IM, etc
15867 connections more reliable.
15868 - Make the v2 dir's "Fast" flag based on relative capacity, just
15869 like "Stable" is based on median uptime. Name everything in the
15870 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
15871 - Retry directory requests if we fail to get an answer we like
15872 from a given dirserver (we were retrying before, but only if
15873 we fail to connect).
15874 - Return a robots.txt on our dirport to discourage google indexing.
15876 o Controller protocol improvements:
15877 - Revised controller protocol (version 1) that uses ascii rather
15878 than binary: tor/doc/control-spec.txt. Add supporting libraries
15879 in python and java and c# so you can use the controller from your
15880 applications without caring how our protocol works.
15881 - Allow the DEBUG controller event to work again. Mark certain log
15882 entries as "don't tell this to controllers", so we avoid cycles.
15883 - New controller function "getinfo accounting", to ask how
15884 many bytes we've used in this time period.
15885 - Add a "resetconf" command so you can set config options like
15886 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
15887 a config option in the torrc with no value, then it clears it
15888 entirely (rather than setting it to its default).
15889 - Add a "getinfo config-file" to tell us where torrc is. Also
15890 expose guard nodes, config options/names.
15891 - Add a "quit" command (when when using the controller manually).
15892 - Add a new signal "newnym" to "change pseudonyms" -- that is, to
15893 stop using any currently-dirty circuits for new streams, so we
15894 don't link new actions to old actions. This also occurs on HUP
15895 or "signal reload".
15896 - If we would close a stream early (e.g. it asks for a .exit that
15897 we know would refuse it) but the LeaveStreamsUnattached config
15898 option is set by the controller, then don't close it.
15899 - Add a new controller event type "authdir_newdescs" that allows
15900 controllers to get all server descriptors that were uploaded to
15901 a router in its role as directory authority.
15902 - New controller option "getinfo desc/all-recent" to fetch the
15903 latest server descriptor for every router that Tor knows about.
15904 - Fix the controller's "attachstream 0" command to treat conn like
15905 it just connected, doing address remapping, handling .exit and
15906 .onion idioms, and so on. Now we're more uniform in making sure
15907 that the controller hears about new and closing connections.
15908 - Permit transitioning from ORPort==0 to ORPort!=0, and back, from
15909 the controller. Also, rotate dns and cpu workers if the controller
15910 changes options that will affect them; and initialize the dns
15911 worker cache tree whether or not we start out as a server.
15912 - Add a new circuit purpose 'controller' to let the controller ask
15913 for a circuit that Tor won't try to use. Extend the "extendcircuit"
15914 controller command to let you specify the purpose if you're starting
15915 a new circuit. Add a new "setcircuitpurpose" controller command to
15916 let you change a circuit's purpose after it's been created.
15917 - Let the controller ask for "getinfo dir/server/foo" so it can ask
15918 directly rather than connecting to the dir port. "getinfo
15919 dir/status/foo" also works, but currently only if your DirPort
15921 - Let the controller tell us about certain router descriptors
15922 that it doesn't want Tor to use in circuits. Implement
15923 "setrouterpurpose" and modify "+postdescriptor" to do this.
15924 - If the controller's *setconf commands fail, collect an error
15925 message in a string and hand it back to the controller -- don't
15926 just tell them to go read their logs.
15928 o Scalability, resource management, and performance:
15929 - Fix a major load balance bug: we were round-robin reading in 16 KB
15930 chunks, and servers with bandwidthrate of 20 KB, while downloading
15931 a 600 KB directory, would starve their other connections. Now we
15932 try to be a bit more fair.
15933 - Be more conservative about whether to advertise our DirPort.
15934 The main change is to not advertise if we're running at capacity
15935 and either a) we could hibernate ever or b) our capacity is low
15936 and we're using a default DirPort.
15937 - We weren't cannibalizing circuits correctly for
15938 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
15939 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
15940 build those from scratch. This should make hidden services faster.
15941 - Predict required circuits better, with an eye toward making hidden
15942 services faster on the service end.
15943 - Compress exit policies even more: look for duplicate lines and
15945 - Generate 18.0.0.0/8 address policy format in descs when we can;
15946 warn when the mask is not reducible to a bit-prefix.
15947 - There used to be two ways to specify your listening ports in a
15948 server descriptor: on the "router" line and with a separate "ports"
15949 line. Remove support for the "ports" line.
15950 - Reduce memory requirements in our structs by changing the order
15951 of fields. Replace balanced trees with hash tables. Inline
15952 bottleneck smartlist functions. Add a "Map from digest to void*"
15953 abstraction so we can do less hex encoding/decoding, and use it
15954 in router_get_by_digest(). Many other CPU and memory improvements.
15955 - Allow tor_gzip_uncompress to extract as much as possible from
15956 truncated compressed data. Try to extract as many
15957 descriptors as possible from truncated http responses (when
15958 purpose is DIR_PURPOSE_FETCH_ROUTERDESC).
15959 - Make circ->onionskin a pointer, not a static array. moria2 was using
15960 125000 circuit_t's after it had been up for a few weeks, which
15961 translates to 20+ megs of wasted space.
15962 - The private half of our EDH handshake keys are now chosen out
15963 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
15964 - Stop doing the complex voodoo overkill checking for insecure
15965 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
15966 - Do round-robin writes for TLS of at most 16 kB per write. This
15967 might be more fair on loaded Tor servers.
15968 - Do not use unaligned memory access on alpha, mips, or mipsel.
15969 It *works*, but is very slow, so we treat them as if it doesn't.
15971 o Other bugfixes and improvements:
15972 - Start storing useful information to $DATADIR/state, so we can
15973 remember things across invocations of Tor. Retain unrecognized
15974 lines so we can be forward-compatible, and write a TorVersion line
15975 so we can be backward-compatible.
15976 - If ORPort is set, Address is not explicitly set, and our hostname
15977 resolves to a private IP address, try to use an interface address
15978 if it has a public address. Now Windows machines that think of
15979 themselves as localhost can guess their address.
15980 - Regenerate our local descriptor if it's dirty and we try to use
15981 it locally (e.g. if it changes during reachability detection).
15982 This was causing some Tor servers to keep publishing the same
15983 initial descriptor forever.
15984 - Tor servers with dynamic IP addresses were needing to wait 18
15985 hours before they could start doing reachability testing using
15986 the new IP address and ports. This is because they were using
15987 the internal descriptor to learn what to test, yet they were only
15988 rebuilding the descriptor once they decided they were reachable.
15989 - It turns out we couldn't bootstrap a network since we added
15990 reachability detection in 0.1.0.1-rc. Good thing the Tor network
15991 has never gone down. Add an AssumeReachable config option to let
15992 servers and authorities bootstrap. When we're trying to build a
15993 high-uptime or high-bandwidth circuit but there aren't enough
15994 suitable servers, try being less picky rather than simply failing.
15995 - Newly bootstrapped Tor networks couldn't establish hidden service
15996 circuits until they had nodes with high uptime. Be more tolerant.
15997 - Really busy servers were keeping enough circuits open on stable
15998 connections that they were wrapping around the circuit_id
15999 space. (It's only two bytes.) This exposed a bug where we would
16000 feel free to reuse a circuit_id even if it still exists but has
16001 been marked for close. Try to fix this bug. Some bug remains.
16002 - When we fail to bind or listen on an incoming or outgoing
16003 socket, we now close it before refusing, rather than just
16004 leaking it. (Thanks to Peter Palfrader for finding.)
16005 - Fix a file descriptor leak in start_daemon().
16006 - On Windows, you can't always reopen a port right after you've
16007 closed it. So change retry_listeners() to only close and re-open
16008 ports that have changed.
16009 - Workaround a problem with some http proxies that refuse GET
16010 requests that specify "Content-Length: 0". Reported by Adrian.
16011 - Recover better from TCP connections to Tor servers that are
16012 broken but don't tell you (it happens!); and rotate TLS
16013 connections once a week.
16014 - Fix a scary-looking but apparently harmless bug where circuits
16015 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
16016 servers, and never switch to state CIRCUIT_STATE_OPEN.
16017 - Check for even more Windows version flags when writing the platform
16018 string in server descriptors, and note any we don't recognize.
16019 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
16020 get a better idea of why their circuits failed. Not used yet.
16021 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
16022 We don't use them yet, but maybe one day our DNS resolver will be
16023 able to discover them.
16024 - Let people type "tor --install" as well as "tor -install" when they
16025 want to make it an NT service.
16026 - Looks like we were never delivering deflated (i.e. compressed)
16027 running-routers lists, even when asked. Oops.
16028 - We were leaking some memory every time the client changed IPs.
16029 - Clean up more of the OpenSSL memory when exiting, so we can detect
16030 memory leaks better.
16031 - Never call free() on tor_malloc()d memory. This will help us
16032 use dmalloc to detect memory leaks.
16033 - Some Tor servers process billions of cells per day. These
16034 statistics are now uint64_t's.
16035 - Check [X-]Forwarded-For headers in HTTP requests when generating
16036 log messages. This lets people run dirservers (and caches) behind
16037 Apache but still know which IP addresses are causing warnings.
16038 - Fix minor integer overflow in calculating when we expect to use up
16039 our bandwidth allocation before hibernating.
16040 - Lower the minimum required number of file descriptors to 1000,
16041 so we can have some overhead for Valgrind on Linux, where the
16042 default ulimit -n is 1024.
16043 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
16044 and its existence is confusing some users.
16046 o Config option fixes:
16047 - Add a new config option ExitPolicyRejectPrivate which defaults
16048 to on. Now all exit policies will begin with rejecting private
16049 addresses, unless the server operator explicitly turns it off.
16050 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB.
16051 - Add new ReachableORAddresses and ReachableDirAddresses options
16052 that understand address policies. FascistFirewall is now a synonym
16053 for "ReachableORAddresses *:443", "ReachableDirAddresses *:80".
16054 - Start calling it FooListenAddress rather than FooBindAddress,
16055 since few of our users know what it means to bind an address
16057 - If the user gave Tor an odd number of command-line arguments,
16058 we were silently ignoring the last one. Now we complain and fail.
16059 This wins the oldest-bug prize -- this bug has been present since
16060 November 2002, as released in Tor 0.0.0.
16061 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
16062 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
16063 it would silently ignore the 6668.
16064 - If we get a linelist or linelist_s config option from the torrc,
16065 e.g. ExitPolicy, and it has no value, warn and skip rather than
16066 silently resetting it to its default.
16067 - Setconf was appending items to linelists, not clearing them.
16068 - Add MyFamily to torrc.sample in the server section, so operators
16069 will be more likely to learn that it exists.
16070 - Make ContactInfo mandatory for authoritative directory servers.
16071 - MaxConn has been obsolete for a while now. Document the ConnLimit
16072 config option, which is a *minimum* number of file descriptors
16073 that must be available else Tor refuses to start.
16074 - Get rid of IgnoreVersion undocumented config option, and make us
16075 only warn, never exit, when we're running an obsolete version.
16076 - Make MonthlyAccountingStart config option truly obsolete now.
16077 - Correct the man page entry on TrackHostExitsExpire.
16078 - Let directory authorities start even if they don't specify an
16079 Address config option.
16080 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
16081 reflect the updated flags in our v2 dir protocol.
16083 o Config option features:
16084 - Add a new config option FastFirstHopPK (on by default) so clients
16085 do a trivial crypto handshake for their first hop, since TLS has
16086 already taken care of confidentiality and authentication.
16087 - Let the user set ControlListenAddress in the torrc. This can be
16088 dangerous, but there are some cases (like a secured LAN) where it
16090 - New config options to help controllers: FetchServerDescriptors
16091 and FetchHidServDescriptors for whether to fetch server
16092 info and hidserv info or let the controller do it, and
16093 PublishServerDescriptor and PublishHidServDescriptors.
16094 - Also let the controller set the __AllDirActionsPrivate config
16095 option if you want all directory fetches/publishes to happen via
16096 Tor (it assumes your controller bootstraps your circuits).
16097 - Add "HardwareAccel" config option: support for crypto hardware
16098 accelerators via OpenSSL. Off by default, until we find somebody
16099 smart who can test it for us. (It appears to produce seg faults
16100 in at least some cases.)
16101 - New config option "AuthDirRejectUnlisted" for directory authorities
16102 as a panic button: if we get flooded with unusable servers we can
16103 revert to only listing servers in the approved-routers file.
16104 - Directory authorities can now reject/invalidate by key and IP,
16105 with the config options "AuthDirInvalid" and "AuthDirReject", or
16106 by marking a fingerprint as "!reject" or "!invalid" (as its
16107 nickname) in the approved-routers file. This is useful since
16108 currently we automatically list servers as running and usable
16109 even if we know they're jerks.
16110 - Add a new config option TestSocks so people can see whether their
16111 applications are using socks4, socks4a, socks5-with-ip, or
16112 socks5-with-fqdn. This way they don't have to keep mucking
16113 with tcpdump and wondering if something got cached somewhere.
16114 - Add "private:*" as an alias in configuration for policies. Now
16115 you can simplify your exit policy rather than needing to list
16116 every single internal or nonroutable network space.
16117 - Accept "private:*" in routerdesc exit policies; not generated yet
16118 because older Tors do not understand it.
16119 - Add configuration option "V1AuthoritativeDirectory 1" which
16120 moria1, moria2, and tor26 have set.
16121 - Implement an option, VirtualAddrMask, to set which addresses
16122 get handed out in response to mapaddress requests. This works
16123 around a bug in tsocks where 127.0.0.0/8 is never socksified.
16124 - Add a new config option FetchUselessDescriptors, off by default,
16125 for when you plan to run "exitlist" on your client and you want
16126 to know about even the non-running descriptors.
16127 - SocksTimeout: How long do we let a socks connection wait
16128 unattached before we fail it?
16129 - CircuitBuildTimeout: Cull non-open circuits that were born
16130 at least this many seconds ago.
16131 - CircuitIdleTimeout: Cull open clean circuits that were born
16132 at least this many seconds ago.
16133 - New config option SafeSocks to reject all application connections
16134 using unsafe socks protocols. Defaults to off.
16136 o Improved and clearer log messages:
16137 - Reduce clutter in server logs. We're going to try to make
16138 them actually usable now. New config option ProtocolWarnings that
16139 lets you hear about how _other Tors_ are breaking the protocol. Off
16141 - Divide log messages into logging domains. Once we put some sort
16142 of interface on this, it will let people looking at more verbose
16143 log levels specify the topics they want to hear more about.
16144 - Log server fingerprint on startup, so new server operators don't
16145 have to go hunting around their filesystem for it.
16146 - Provide dire warnings to any users who set DirServer manually;
16147 move it out of torrc.sample and into torrc.complete.
16148 - Make the log message less scary when all the dirservers are
16149 temporarily unreachable.
16150 - When tor_socketpair() fails in Windows, give a reasonable
16151 Windows-style errno back.
16152 - Improve tor_gettimeofday() granularity on windows.
16153 - We were printing the number of idle dns workers incorrectly when
16155 - Handle duplicate lines in approved-routers files without warning.
16156 - We were whining about using socks4 or socks5-with-local-lookup
16157 even when it's an IP address in the "virtual" range we designed
16158 exactly for this case.
16159 - Check for named servers when looking them up by nickname;
16160 warn when we're calling a non-named server by its nickname;
16161 don't warn twice about the same name.
16162 - Downgrade the dirserver log messages when whining about
16164 - Correct "your server is reachable" log entries to indicate that
16165 it was self-testing that told us so.
16166 - If we're trying to be a Tor server and running Windows 95/98/ME
16167 as a server, explain that we'll likely crash.
16168 - Provide a more useful warn message when our onion queue gets full:
16169 the CPU is too slow or the exit policy is too liberal.
16170 - Don't warn when we receive a 503 from a dirserver/cache -- this
16171 will pave the way for them being able to refuse if they're busy.
16172 - When we fail to bind a listener, try to provide a more useful
16173 log message: e.g., "Is Tor already running?"
16174 - Only start testing reachability once we've established a
16175 circuit. This will make startup on dir authorities less noisy.
16176 - Don't try to upload hidden service descriptors until we have
16177 established a circuit.
16178 - Tor didn't warn when it failed to open a log file.
16179 - Warn when listening on a public address for socks. We suspect a
16180 lot of people are setting themselves up as open socks proxies,
16181 and they have no idea that jerks on the Internet are using them,
16182 since they simply proxy the traffic into the Tor network.
16183 - Give a useful message when people run Tor as the wrong user,
16184 rather than telling them to start chowning random directories.
16185 - Fix a harmless bug that was causing Tor servers to log
16186 "Got an end because of misc error, but we're not an AP. Closing."
16187 - Fix wrong log message when you add a "HiddenServiceNodes" config
16188 line without any HiddenServiceDir line (reported by Chris Thomas).
16189 - Directory authorities now stop whining so loudly about bad
16190 descriptors that they fetch from other dirservers. So when there's
16191 a log complaint, it's for sure from a freshly uploaded descriptor.
16192 - When logging via syslog, include the pid whenever we provide
16193 a log entry. Suggested by Todd Fries.
16194 - When we're shutting down and we do something like try to post a
16195 server descriptor or rendezvous descriptor, don't complain that
16196 we seem to be unreachable. Of course we are, we're shutting down.
16197 - Change log line for unreachability to explicitly suggest /etc/hosts
16198 as the culprit. Also make it clearer what IP address and ports we're
16199 testing for reachability.
16200 - Put quotes around user-supplied strings when logging so users are
16201 more likely to realize if they add bad characters (like quotes)
16203 - NT service patch from Matt Edman to improve error messages on Win32.
16206 Changes in version 0.1.0.17 - 2006-02-17
16207 o Crash bugfixes on 0.1.0.x:
16208 - When servers with a non-zero DirPort came out of hibernation,
16209 sometimes they would trigger an assert.
16211 o Other important bugfixes:
16212 - On platforms that don't have getrlimit (like Windows), we were
16213 artificially constraining ourselves to a max of 1024
16214 connections. Now just assume that we can handle as many as 15000
16215 connections. Hopefully this won't cause other problems.
16217 o Backported features:
16218 - When we're a server, a client asks for an old-style directory,
16219 and our write bucket is empty, don't give it to him. This way
16220 small servers can continue to serve the directory *sometimes*,
16221 without getting overloaded.
16222 - Whenever you get a 503 in response to a directory fetch, try
16223 once more. This will become important once servers start sending
16224 503's whenever they feel busy.
16225 - Fetch a new directory every 120 minutes, not every 40 minutes.
16226 Now that we have hundreds of thousands of users running the old
16227 directory algorithm, it's starting to hurt a lot.
16228 - Bump up the period for forcing a hidden service descriptor upload
16229 from 20 minutes to 1 hour.
16232 Changes in version 0.1.0.16 - 2006-01-02
16233 o Crash bugfixes on 0.1.0.x:
16234 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
16235 corrupting the heap, losing FDs, or crashing when we need to resize
16236 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
16237 - It turns out sparc64 platforms crash on unaligned memory access
16238 too -- so detect and avoid this.
16239 - Handle truncated compressed data correctly (by detecting it and
16241 - Fix possible-but-unlikely free(NULL) in control.c.
16242 - When we were closing connections, there was a rare case that
16243 stomped on memory, triggering seg faults and asserts.
16244 - Avoid potential infinite recursion when building a descriptor. (We
16245 don't know that it ever happened, but better to fix it anyway.)
16246 - We were neglecting to unlink marked circuits from soon-to-close OR
16247 connections, which caused some rare scribbling on freed memory.
16248 - Fix a memory stomping race bug when closing the joining point of two
16249 rendezvous circuits.
16250 - Fix an assert in time parsing found by Steven Murdoch.
16252 o Other bugfixes on 0.1.0.x:
16253 - When we're doing reachability testing, provide more useful log
16254 messages so the operator knows what to expect.
16255 - Do not check whether DirPort is reachable when we are suppressing
16256 advertising it because of hibernation.
16257 - When building with -static or on Solaris, we sometimes needed -ldl.
16258 - One of the dirservers (tor26) changed its IP address.
16259 - When we're deciding whether a stream has enough circuits around
16260 that can handle it, count the freshly dirty ones and not the ones
16261 that are so dirty they won't be able to handle it.
16262 - When we're expiring old circuits, we had a logic error that caused
16263 us to close new rendezvous circuits rather than old ones.
16264 - Give a more helpful log message when you try to change ORPort via
16265 the controller: you should upgrade Tor if you want that to work.
16266 - We were failing to parse Tor versions that start with "Tor ".
16267 - Tolerate faulty streams better: when a stream fails for reason
16268 exitpolicy, stop assuming that the router is lying about his exit
16269 policy. When a stream fails for reason misc, allow it to retry just
16270 as if it was resolvefailed. When a stream has failed three times,
16271 reset its failure count so we can try again and get all three tries.
16274 Changes in version 0.1.0.15 - 2005-09-23
16275 o Bugfixes on 0.1.0.x:
16276 - Reject ports 465 and 587 (spam targets) in default exit policy.
16277 - Don't crash when we don't have any spare file descriptors and we
16278 try to spawn a dns or cpu worker.
16279 - Get rid of IgnoreVersion undocumented config option, and make us
16280 only warn, never exit, when we're running an obsolete version.
16281 - Don't try to print a null string when your server finds itself to
16282 be unreachable and the Address config option is empty.
16283 - Make the numbers in read-history and write-history into uint64s,
16284 so they don't overflow and publish negatives in the descriptor.
16285 - Fix a minor memory leak in smartlist_string_remove().
16286 - We were only allowing ourselves to upload a server descriptor at
16287 most every 20 minutes, even if it changed earlier than that.
16288 - Clean up log entries that pointed to old URLs.
16291 Changes in version 0.1.0.14 - 2005-08-08
16292 o Bugfixes on 0.1.0.x:
16293 - Fix the other half of the bug with crypto handshakes
16295 - Fix an assert trigger if you send a 'signal term' via the
16296 controller when it's listening for 'event info' messages.
16299 Changes in version 0.1.0.13 - 2005-08-04
16300 o Bugfixes on 0.1.0.x:
16301 - Fix a critical bug in the security of our crypto handshakes.
16302 - Fix a size_t underflow in smartlist_join_strings2() that made
16303 it do bad things when you hand it an empty smartlist.
16304 - Fix Windows installer to ship Tor license (thanks to Aphex for
16305 pointing out this oversight) and put a link to the doc directory
16307 - Explicitly set no-unaligned-access for sparc: it turns out the
16308 new gcc's let you compile broken code, but that doesn't make it
16312 Changes in version 0.1.0.12 - 2005-07-18
16313 o New directory servers:
16314 - tor26 has changed IP address.
16316 o Bugfixes on 0.1.0.x:
16317 - Fix a possible double-free in tor_gzip_uncompress().
16318 - When --disable-threads is set, do not search for or link against
16319 pthreads libraries.
16320 - Don't trigger an assert if an authoritative directory server
16321 claims its dirport is 0.
16322 - Fix bug with removing Tor as an NT service: some people were
16323 getting "The service did not return an error." Thanks to Matt
16327 Changes in version 0.1.0.11 - 2005-06-30
16328 o Bugfixes on 0.1.0.x:
16329 - Fix major security bug: servers were disregarding their
16330 exit policies if clients behaved unexpectedly.
16331 - Make OS X init script check for missing argument, so we don't
16332 confuse users who invoke it incorrectly.
16333 - Fix a seg fault in "tor --hash-password foo".
16334 - The MAPADDRESS control command was broken.
16337 Changes in version 0.1.0.10 - 2005-06-14
16339 - Make NT services work and start on startup on Win32 (based on
16340 patch by Matt Edman). See the FAQ entry for details.
16341 - Make 'platform' string in descriptor more accurate for Win32
16342 servers, so it's not just "unknown platform".
16343 - REUSEADDR on normal platforms means you can rebind to the port
16344 right after somebody else has let it go. But REUSEADDR on Win32
16345 means you can bind to the port _even when somebody else already
16346 has it bound_! So, don't do that on Win32.
16347 - Clean up the log messages when starting on Win32 with no config
16349 - Allow seeding the RNG on Win32 even when you're not running as
16350 Administrator. If seeding the RNG on Win32 fails, quit.
16352 o Assert / crash bugs:
16353 - Refuse relay cells that claim to have a length larger than the
16354 maximum allowed. This prevents a potential attack that could read
16355 arbitrary memory (e.g. keys) from an exit server's process
16357 - If unofficial Tor clients connect and send weird TLS certs, our
16358 Tor server triggers an assert. Stop asserting, and start handling
16359 TLS errors better in other situations too.
16360 - Fix a race condition that can trigger an assert when we have a
16361 pending create cell and an OR connection attempt fails.
16364 - Use pthreads for worker processes rather than forking. This was
16365 forced because when we forked, we ended up wasting a lot of
16366 duplicate ram over time.
16367 - Also switch to foo_r versions of some library calls to allow
16368 reentry and threadsafeness.
16369 - Implement --disable-threads configure option. Disable threads on
16370 netbsd and openbsd by default, because they have no reentrant
16371 resolver functions (!), and on solaris since it has other
16373 - Fix possible bug on threading platforms (e.g. win32) which was
16374 leaking a file descriptor whenever a cpuworker or dnsworker died.
16375 - Fix a minor memory leak when somebody establishes an introduction
16376 point at your Tor server.
16377 - Fix possible memory leak in tor_lookup_hostname(). (Thanks to
16379 - Add ./configure --with-dmalloc option, to track memory leaks.
16380 - And try to free all memory on closing, so we can detect what
16383 o Protocol correctness:
16384 - When we've connected to an OR and handshaked but didn't like
16385 the result, we were closing the conn without sending destroy
16386 cells back for pending circuits. Now send those destroys.
16387 - Start sending 'truncated' cells back rather than destroy cells
16388 if the circuit closes in front of you. This means we won't have
16389 to abandon partially built circuits.
16390 - Handle changed router status correctly when dirserver reloads
16391 fingerprint file. We used to be dropping all unverified descriptors
16392 right then. The bug was hidden because we would immediately
16393 fetch a directory from another dirserver, which would include the
16394 descriptors we just dropped.
16395 - Revise tor-spec to add more/better stream end reasons.
16396 - Revise all calls to connection_edge_end to avoid sending 'misc',
16397 and to take errno into account where possible.
16398 - Client now retries when streams end early for 'hibernating' or
16399 'resource limit' reasons, rather than failing them.
16400 - Try to be more zealous about calling connection_edge_end when
16401 things go bad with edge conns in connection.c.
16403 o Robustness improvements:
16404 - Better handling for heterogeneous / unreliable nodes:
16405 - Annotate circuits with whether they aim to contain high uptime
16406 nodes and/or high capacity nodes. When building circuits, choose
16408 - This means that every single node in an intro rend circuit,
16409 not just the last one, will have a minimum uptime.
16410 - New config option LongLivedPorts to indicate application streams
16411 that will want high uptime circuits.
16412 - Servers reset uptime when a dir fetch entirely fails. This
16413 hopefully reflects stability of the server's network connectivity.
16414 - If somebody starts his tor server in Jan 2004 and then fixes his
16415 clock, don't make his published uptime be a year.
16416 - Reset published uptime when we wake up from hibernation.
16417 - Introduce a notion of 'internal' circs, which are chosen without
16418 regard to the exit policy of the last hop. Intro and rendezvous
16419 circs must be internal circs, to avoid leaking information. Resolve
16420 and connect streams can use internal circs if they want.
16421 - New circuit pooling algorithm: keep track of what destination ports
16422 we've used recently (start out assuming we'll want to use 80), and
16423 make sure to have enough circs around to satisfy these ports. Also
16424 make sure to have 2 internal circs around if we've required internal
16425 circs lately (and with high uptime if we've seen that lately too).
16426 - Turn addr_policy_compare from a tristate to a quadstate; this should
16427 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
16428 for google.com" problem.
16429 - When a client asks us for a dir mirror and we don't have one,
16430 launch an attempt to get a fresh one.
16431 - First cut at support for "create-fast" cells. Clients can use
16432 these when extending to their first hop, since the TLS already
16433 provides forward secrecy and authentication. Not enabled on
16436 o Reachability testing.
16437 - Your Tor server will automatically try to see if its ORPort and
16438 DirPort are reachable from the outside, and it won't upload its
16439 descriptor until it decides at least ORPort is reachable (when
16440 DirPort is not yet found reachable, publish it as zero).
16441 - When building testing circs for ORPort testing, use only
16442 high-bandwidth nodes, so fewer circuits fail.
16443 - Notice when our IP changes, and reset stats/uptime/reachability.
16444 - Authdirservers don't do ORPort reachability detection, since
16445 they're in clique mode, so it will be rare to find a server not
16446 already connected to them.
16447 - Authdirservers now automatically approve nodes running 0.1.0.2-rc
16451 - Now we allow two unverified servers with the same nickname
16452 but different keys. But if a nickname is verified, only that
16453 nickname+key are allowed.
16454 - If you're an authdirserver connecting to an address:port,
16455 and it's not the OR you were expecting, forget about that
16456 descriptor. If he *was* the one you were expecting, then forget
16457 about all other descriptors for that address:port.
16458 - Allow servers to publish descriptors from 12 hours in the future.
16459 Corollary: only whine about clock skew from the dirserver if
16460 he's a trusted dirserver (since now even verified servers could
16461 have quite wrong clocks).
16462 - Require servers that use the default dirservers to have public IP
16463 addresses. We have too many servers that are configured with private
16464 IPs and their admins never notice the log entries complaining that
16465 their descriptors are being rejected.
16467 o Efficiency improvements:
16468 - Use libevent. Now we can use faster async cores (like epoll, kpoll,
16469 and /dev/poll), and hopefully work better on Windows too.
16470 - Apple's OS X 10.4.0 ships with a broken kqueue API, and using
16471 kqueue on 10.3.9 causes kernel panics. Don't use kqueue on OS X.
16472 - Find libevent even if it's hiding in /usr/local/ and your
16473 CFLAGS and LDFLAGS don't tell you to look there.
16474 - Be able to link with libevent as a shared library (the default
16475 after 1.0d), even if it's hiding in /usr/local/lib and even
16476 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
16477 assuming you're running gcc. Otherwise fail and give a useful
16479 - Switch to a new buffer management algorithm, which tries to avoid
16480 reallocing and copying quite as much. In first tests it looks like
16481 it uses *more* memory on average, but less cpu.
16482 - Switch our internal buffers implementation to use a ring buffer,
16483 to hopefully improve performance for fast servers a lot.
16484 - Reenable the part of the code that tries to flush as soon as an
16485 OR outbuf has a full TLS record available. Perhaps this will make
16486 OR outbufs not grow as huge except in rare cases, thus saving lots
16487 of CPU time plus memory.
16488 - Improve performance for dirservers: stop re-parsing the whole
16489 directory every time you regenerate it.
16490 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
16491 it much faster to look up a circuit for each relay cell.
16492 - Remove most calls to assert_all_pending_dns_resolves_ok(),
16493 since they're eating our cpu on exit nodes.
16494 - Stop wasting time doing a case insensitive comparison for every
16495 dns name every time we do any lookup. Canonicalize the names to
16496 lowercase when you first see them.
16499 - Handle unavailable hidden services better. Handle slow or busy
16500 hidden services better.
16501 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
16502 circ as necessary, if there are any completed ones lying around
16503 when we try to launch one.
16504 - Make hidden services try to establish a rendezvous for 30 seconds
16505 after fetching the descriptor, rather than for n (where n=3)
16506 attempts to build a circuit.
16507 - Adjust maximum skew and age for rendezvous descriptors: let skew
16508 be 48 hours rather than 90 minutes.
16509 - Reject malformed .onion addresses rather then passing them on as
16510 normal web requests.
16513 - More Tor controller support. See
16514 http://tor.eff.org/doc/control-spec.txt for all the new features,
16515 including signals to emulate unix signals from any platform;
16516 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
16517 closestream; closecircuit; etc.
16518 - Encode hashed controller passwords in hex instead of base64,
16519 to make it easier to write controllers.
16520 - Revise control spec and implementation to allow all log messages to
16521 be sent to controller with their severities intact (suggested by
16522 Matt Edman). Disable debug-level logs while delivering a debug-level
16523 log to the controller, to prevent loop. Update TorControl to handle
16524 new log event types.
16526 o New config options/defaults:
16527 - Begin scrubbing sensitive strings from logs by default. Turn off
16528 the config option SafeLogging if you need to do debugging.
16529 - New exit policy: accept most low-numbered ports, rather than
16530 rejecting most low-numbered ports.
16531 - Put a note in the torrc about abuse potential with the default
16533 - Add support for CONNECTing through https proxies, with "HttpsProxy"
16535 - Add HttpProxyAuthenticator and HttpsProxyAuthenticator support
16536 based on patch from Adam Langley (basic auth only).
16537 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
16538 the fast servers that have been joining lately. (Clients are now
16539 willing to load balance over up to 2 MB of advertised bandwidth
16541 - New config option MaxAdvertisedBandwidth which lets you advertise
16542 a low bandwidthrate (to not attract as many circuits) while still
16543 allowing a higher bandwidthrate in reality.
16544 - Require BandwidthRate to be at least 20kB/s for servers.
16545 - Add a NoPublish config option, so you can be a server (e.g. for
16546 testing running Tor servers in other Tor networks) without
16547 publishing your descriptor to the primary dirservers.
16548 - Add a new AddressMap config directive to rewrite incoming socks
16549 addresses. This lets you, for example, declare an implicit
16550 required exit node for certain sites.
16551 - Add a new TrackHostExits config directive to trigger addressmaps
16552 for certain incoming socks addresses -- for sites that break when
16553 your exit keeps changing (based on patch from Mike Perry).
16554 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
16555 which describes how often we retry making new circuits if current
16556 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
16557 how long we're willing to make use of an already-dirty circuit.
16558 - Change compiled-in SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to
16559 a config option "ShutdownWaitLength" (when using kill -INT on
16561 - Fix an edge case in parsing config options: if they say "--"
16562 on the commandline, it's not a config option (thanks weasel).
16563 - New config option DirAllowPrivateAddresses for authdirservers.
16564 Now by default they refuse router descriptors that have non-IP or
16565 private-IP addresses.
16566 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
16567 smart" default value: low for servers and high for clients.
16568 - Some people were putting "Address " in their torrc, and they had
16569 a buggy resolver that resolved " " to 0.0.0.0. Oops.
16570 - If DataDir is ~/.tor, and that expands to /.tor, then default to
16571 LOCALSTATEDIR/tor instead.
16572 - Implement --verify-config command-line option to check if your torrc
16573 is valid without actually launching Tor.
16575 o Logging improvements:
16576 - When dirservers refuse a server descriptor, we now log its
16577 contactinfo, platform, and the poster's IP address.
16578 - Only warn once per nickname from add_nickname_list_to_smartlist()
16579 per failure, so an entrynode or exitnode choice that's down won't
16581 - When we're connecting to an OR and he's got a different nickname/key
16582 than we were expecting, only complain loudly if we're an OP or a
16583 dirserver. Complaining loudly to the OR admins just confuses them.
16584 - Whine at you if you're a server and you don't set your contactinfo.
16585 - Warn when exit policy implicitly allows local addresses.
16586 - Give a better warning when some other server advertises an
16587 ORPort that is actually an apache running ssl.
16588 - If we get an incredibly skewed timestamp from a dirserver mirror
16589 that isn't a verified OR, don't warn -- it's probably him that's
16591 - When a dirserver causes you to give a warn, mention which dirserver
16593 - Initialize libevent later in the startup process, so the logs are
16594 already established by the time we start logging libevent warns.
16595 - Use correct errno on win32 if libevent fails.
16596 - Check and warn about known-bad/slow libevent versions.
16597 - Stop warning about sigpipes in the logs. We're going to
16598 pretend that getting these occasionally is normal and fine.
16600 o New contrib scripts:
16601 - New experimental script tor/contrib/exitlist: a simple python
16602 script to parse directories and find Tor nodes that exit to listed
16604 - New experimental script tor/contrib/ExerciseServer.py (needs more
16605 work) that uses the controller interface to build circuits and
16606 fetch pages over them. This will help us bootstrap servers that
16607 have lots of capacity but haven't noticed it yet.
16608 - New experimental script tor/contrib/PathDemo.py (needs more work)
16609 that uses the controller interface to let you choose whole paths
16611 "<hostname>.<path,separated by dots>.<length of path>.path"
16612 - New contributed script "privoxy-tor-toggle" to toggle whether
16613 Privoxy uses Tor. Seems to be configured for Debian by default.
16614 - Have torctl.in/tor.sh.in check for location of su binary (needed
16618 - chdir() to your datadirectory at the *end* of the daemonize process,
16619 not the beginning. This was a problem because the first time you
16620 run tor, if your datadir isn't there, and you have runasdaemon set
16621 to 1, it will try to chdir to it before it tries to create it. Oops.
16622 - Fix several double-mark-for-close bugs, e.g. where we were finding
16623 a conn for a cell even if that conn is already marked for close.
16624 - Stop most cases of hanging up on a socks connection without sending
16626 - Fix a bug in the RPM package: set home directory for _tor to
16627 something more reasonable when first installing.
16628 - Stop putting nodename in the Platform string in server descriptors.
16629 It doesn't actually help, and it is confusing/upsetting some people.
16630 - When using preferred entry or exit nodes, ignore whether the
16631 circuit wants uptime or capacity. They asked for the nodes, they
16633 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
16634 artificially capped at 500kB.
16635 - Cache local dns resolves correctly even when they're .exit
16637 - If we're hibernating and we get a SIGINT, exit immediately.
16638 - tor-resolve requests were ignoring .exit if there was a working circuit
16639 they could use instead.
16640 - Pay more attention to the ClientOnly config option.
16641 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in certain
16642 installer screens; and don't put stuff into StartupItems unless
16643 the user asks you to.
16646 - Rewrite address "serifos.exit" to "externalIP.serifos.exit"
16647 rather than just rejecting it.
16648 - If our clock jumps forward by 100 seconds or more, assume something
16649 has gone wrong with our network and abandon all not-yet-used circs.
16650 - When an application is using socks5, give him the whole variety of
16651 potential socks5 responses (connect refused, host unreachable, etc),
16652 rather than just "success" or "failure".
16653 - A more sane version numbering system. See
16654 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
16655 - Change version parsing logic: a version is "obsolete" if it is not
16656 recommended and (1) there is a newer recommended version in the
16657 same series, or (2) there are no recommended versions in the same
16658 series, but there are some recommended versions in a newer series.
16659 A version is "new" if it is newer than any recommended version in
16661 - Report HTTP reasons to client when getting a response from directory
16662 servers -- so you can actually know what went wrong.
16663 - Reject odd-looking addresses at the client (e.g. addresses that
16664 contain a colon), rather than having the server drop them because
16666 - Stop publishing socksport in the directory, since it's not
16667 actually meant to be public. For compatibility, publish a 0 there
16669 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
16670 cookies to disk and doesn't log each web request to disk. (Thanks
16671 to Brett Carrington for pointing this out.)
16672 - Add OSX uninstall instructions. An actual uninstall script will
16674 - Add "opt hibernating 1" to server descriptor to make it clearer
16675 whether the server is hibernating.
16678 Changes in version 0.0.9.10 - 2005-06-16
16679 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
16680 - Refuse relay cells that claim to have a length larger than the
16681 maximum allowed. This prevents a potential attack that could read
16682 arbitrary memory (e.g. keys) from an exit server's process
16686 Changes in version 0.0.9.9 - 2005-04-23
16687 o Bugfixes on 0.0.9.x:
16688 - If unofficial Tor clients connect and send weird TLS certs, our
16689 Tor server triggers an assert. This release contains a minimal
16690 backport from the broader fix that we put into 0.1.0.4-rc.
16693 Changes in version 0.0.9.8 - 2005-04-07
16694 o Bugfixes on 0.0.9.x:
16695 - We have a bug that I haven't found yet. Sometimes, very rarely,
16696 cpuworkers get stuck in the 'busy' state, even though the cpuworker
16697 thinks of itself as idle. This meant that no new circuits ever got
16698 established. Here's a workaround to kill any cpuworker that's been
16699 busy for more than 100 seconds.
16702 Changes in version 0.0.9.7 - 2005-04-01
16703 o Bugfixes on 0.0.9.x:
16704 - Fix another race crash bug (thanks to Glenn Fink for reporting).
16705 - Compare identity to identity, not to nickname, when extending to
16706 a router not already in the directory. This was preventing us from
16707 extending to unknown routers. Oops.
16708 - Make sure to create OS X Tor user in <500 range, so we aren't
16709 creating actual system users.
16710 - Note where connection-that-hasn't-sent-end was marked, and fix
16711 a few really loud instances of this harmless bug (it's fixed more
16715 Changes in version 0.0.9.6 - 2005-03-24
16716 o Bugfixes on 0.0.9.x (crashes and asserts):
16717 - Add new end stream reasons to maintenance branch. Fix bug where
16718 reason (8) could trigger an assert. Prevent bug from recurring.
16719 - Apparently win32 stat wants paths to not end with a slash.
16720 - Fix assert triggers in assert_cpath_layer_ok(), where we were
16721 blowing away the circuit that conn->cpath_layer points to, then
16722 checking to see if the circ is well-formed. Backport check to make
16723 sure we dont use the cpath on a closed connection.
16724 - Prevent circuit_resume_edge_reading_helper() from trying to package
16725 inbufs for marked-for-close streams.
16726 - Don't crash on hup if your options->address has become unresolvable.
16727 - Some systems (like OS X) sometimes accept() a connection and tell
16728 you the remote host is 0.0.0.0:0. If this happens, due to some
16729 other mis-features, we get confused; so refuse the conn for now.
16731 o Bugfixes on 0.0.9.x (other):
16732 - Fix harmless but scary "Unrecognized content encoding" warn message.
16733 - Add new stream error reason: TORPROTOCOL reason means "you are not
16734 speaking a version of Tor I understand; say bye-bye to your stream."
16735 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
16736 into the future, now that we are more tolerant of skew. This
16737 resolves a bug where a Tor server would refuse to cache a directory
16738 because all the directories it gets are too far in the future;
16739 yet the Tor server never logs any complaints about clock skew.
16740 - Mac packaging magic: make man pages useable, and do not overwrite
16741 existing torrc files.
16742 - Make OS X log happily to /var/log/tor/tor.log
16745 Changes in version 0.0.9.5 - 2005-02-22
16746 o Bugfixes on 0.0.9.x:
16747 - Fix an assert race at exit nodes when resolve requests fail.
16748 - Stop picking unverified dir mirrors--it only leads to misery.
16749 - Patch from Matt Edman to make NT services work better. Service
16750 support is still not compiled into the executable by default.
16751 - Patch from Dmitri Bely so the Tor service runs better under
16752 the win32 SYSTEM account.
16753 - Make tor-resolve actually work (?) on Win32.
16754 - Fix a sign bug when getrlimit claims to have 4+ billion
16755 file descriptors available.
16756 - Stop refusing to start when bandwidthburst == bandwidthrate.
16757 - When create cells have been on the onion queue more than five
16758 seconds, just send back a destroy and take them off the list.
16761 Changes in version 0.0.9.4 - 2005-02-03
16762 o Bugfixes on 0.0.9:
16763 - Fix an assert bug that took down most of our servers: when
16764 a server claims to have 1 GB of bandwidthburst, don't
16766 - Don't crash as badly if we have spawned the max allowed number
16767 of dnsworkers, or we're out of file descriptors.
16768 - Block more file-sharing ports in the default exit policy.
16769 - MaxConn is now automatically set to the hard limit of max
16770 file descriptors we're allowed (ulimit -n), minus a few for
16772 - Give a clearer message when servers need to raise their
16773 ulimit -n when they start running out of file descriptors.
16774 - SGI Compatibility patches from Jan Schaumann.
16775 - Tolerate a corrupt cached directory better.
16776 - When a dirserver hasn't approved your server, list which one.
16777 - Go into soft hibernation after 95% of the bandwidth is used,
16778 not 99%. This is especially important for daily hibernators who
16779 have a small accounting max. Hopefully it will result in fewer
16780 cut connections when the hard hibernation starts.
16781 - Load-balance better when using servers that claim more than
16782 800kB/s of capacity.
16783 - Make NT services work (experimental, only used if compiled in).
16786 Changes in version 0.0.9.3 - 2005-01-21
16787 o Bugfixes on 0.0.9:
16788 - Backport the cpu use fixes from main branch, so busy servers won't
16789 need as much processor time.
16790 - Work better when we go offline and then come back, or when we
16791 run Tor at boot before the network is up. We do this by
16792 optimistically trying to fetch a new directory whenever an
16793 application request comes in and we think we're offline -- the
16794 human is hopefully a good measure of when the network is back.
16795 - Backport some minimal hidserv bugfixes: keep rend circuits open as
16796 long as you keep using them; actually publish hidserv descriptors
16797 shortly after they change, rather than waiting 20-40 minutes.
16798 - Enable Mac startup script by default.
16799 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
16800 - When you update AllowUnverifiedNodes or FirewallPorts via the
16801 controller's setconf feature, we were always appending, never
16803 - When you update HiddenServiceDir via setconf, it was screwing up
16804 the order of reading the lines, making it fail.
16805 - Do not rewrite a cached directory back to the cache; otherwise we
16806 will think it is recent and not fetch a newer one on startup.
16807 - Workaround for webservers that lie about Content-Encoding: Tor
16808 now tries to autodetect compressed directories and compression
16809 itself. This lets us Proxypass dir fetches through apache.
16812 Changes in version 0.0.9.2 - 2005-01-04
16813 o Bugfixes on 0.0.9 (crashes and asserts):
16814 - Fix an assert on startup when the disk is full and you're logging
16816 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
16817 style address, then we'd crash.
16818 - Fix an assert trigger when the running-routers string we get from
16819 a dirserver is broken.
16820 - Make worker threads start and run on win32. Now win32 servers
16822 - Bandaid (not actually fix, but now it doesn't crash) an assert
16823 where the dns worker dies mysteriously and the main Tor process
16824 doesn't remember anything about the address it was resolving.
16826 o Bugfixes on 0.0.9 (Win32):
16827 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
16828 name out of the warning/assert messages.
16829 - Fix a superficial "unhandled error on read" bug on win32.
16830 - The win32 installer no longer requires a click-through for our
16831 license, since our Free Software license grants rights but does not
16833 - Win32: When connecting to a dirserver fails, try another one
16834 immediately. (This was already working for non-win32 Tors.)
16835 - Stop trying to parse $HOME on win32 when hunting for default
16837 - Make tor-resolve.c work on win32 by calling network_init().
16839 o Bugfixes on 0.0.9 (other):
16840 - Make 0.0.9.x build on Solaris again.
16841 - Due to a fencepost error, we were blowing away the \n when reporting
16842 confvalue items in the controller. So asking for multiple config
16843 values at once couldn't work.
16844 - When listing circuits that are pending on an opening OR connection,
16845 if we're an OR we were listing circuits that *end* at us as
16846 being pending on every listener, dns/cpu worker, etc. Stop that.
16847 - Dirservers were failing to create 'running-routers' or 'directory'
16848 strings if we had more than some threshold of routers. Fix them so
16849 they can handle any number of routers.
16850 - Fix a superficial "Duplicate mark for close" bug.
16851 - Stop checking for clock skew for OR connections, even for servers.
16852 - Fix a fencepost error that was chopping off the last letter of any
16853 nickname that is the maximum allowed nickname length.
16854 - Update URLs in log messages so they point to the new website.
16855 - Fix a potential problem in mangling server private keys while
16856 writing to disk (not triggered yet, as far as we know).
16857 - Include the licenses for other free software we include in Tor,
16858 now that we're shipping binary distributions more regularly.
16861 Changes in version 0.0.9.1 - 2004-12-15
16862 o Bugfixes on 0.0.9:
16863 - Make hibernation actually work.
16864 - Make HashedControlPassword config option work.
16865 - When we're reporting event circuit status to a controller,
16866 don't use the stream status code.
16869 Changes in version 0.0.9 - 2004-12-12
16870 o Bugfixes on 0.0.8.1 (Crashes and asserts):
16871 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
16872 write() call will fail and we handle it there.
16873 - When we run out of disk space, or other log writing error, don't
16874 crash. Just stop logging to that log and continue.
16875 - Fix isspace() and friends so they still make Solaris happy
16876 but also so they don't trigger asserts on win32.
16877 - Fix assert failure on malformed socks4a requests.
16878 - Fix an assert bug where a hidden service provider would fail if
16879 the first hop of his rendezvous circuit was down.
16880 - Better handling of size_t vs int, so we're more robust on 64
16883 o Bugfixes on 0.0.8.1 (Win32):
16884 - Make windows sockets actually non-blocking (oops), and handle
16885 win32 socket errors better.
16886 - Fix parse_iso_time on platforms without strptime (eg win32).
16887 - win32: when being multithreaded, leave parent fdarray open.
16888 - Better handling of winsock includes on non-MSV win32 compilers.
16889 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
16891 - Make unit tests work on win32.
16893 o Bugfixes on 0.0.8.1 (Path selection and streams):
16894 - Calculate timeout for waiting for a connected cell from the time
16895 we sent the begin cell, not from the time the stream started. If
16896 it took a long time to establish the circuit, we would time out
16897 right after sending the begin cell.
16898 - Fix router_compare_addr_to_addr_policy: it was not treating a port
16899 of * as always matching, so we were picking reject *:* nodes as
16900 exit nodes too. Oops.
16901 - When read() failed on a stream, we would close it without sending
16902 back an end. So 'connection refused' would simply be ignored and
16903 the user would get no response.
16904 - Stop a sigpipe: when an 'end' cell races with eof from the app,
16905 we shouldn't hold-open-until-flush if the eof arrived first.
16906 - Let resolve conns retry/expire also, rather than sticking around
16908 - Fix more dns related bugs: send back resolve_failed and end cells
16909 more reliably when the resolve fails, rather than closing the
16910 circuit and then trying to send the cell. Also attach dummy resolve
16911 connections to a circuit *before* calling dns_resolve(), to fix
16912 a bug where cached answers would never be sent in RESOLVED cells.
16914 o Bugfixes on 0.0.8.1 (Circuits):
16915 - Finally fix a bug that's been plaguing us for a year:
16916 With high load, circuit package window was reaching 0. Whenever
16917 we got a circuit-level sendme, we were reading a lot on each
16918 socket, but only writing out a bit. So we would eventually reach
16919 eof. This would be noticed and acted on even when there were still
16920 bytes sitting in the inbuf.
16921 - Use identity comparison, not nickname comparison, to choose which
16922 half of circuit-ID-space each side gets to use. This is needed
16923 because sometimes we think of a router as a nickname, and sometimes
16924 as a hex ID, and we can't predict what the other side will do.
16926 o Bugfixes on 0.0.8.1 (Other):
16927 - Fix a whole slew of memory leaks.
16928 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
16929 - If we are using select, make sure we stay within FD_SETSIZE.
16930 - When poll() is interrupted, we shouldn't believe the revents values.
16931 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
16932 and smartlist_len, which are two major profiling offenders.
16933 - If do_hup fails, actually notice.
16934 - Flush the log file descriptor after we print "Tor opening log file",
16935 so we don't see those messages days later.
16936 - Hidden service operators now correctly handle version 1 style
16937 INTRODUCE1 cells (nobody generates them still, so not a critical
16939 - Handle more errnos from accept() without closing the listener.
16940 Some OpenBSD machines were closing their listeners because
16941 they ran out of file descriptors.
16942 - Some people had wrapped their tor client/server in a script
16943 that would restart it whenever it died. This did not play well
16944 with our "shut down if your version is obsolete" code. Now people
16945 don't fetch a new directory if their local cached version is
16947 - Make our autogen.sh work on ksh as well as bash.
16948 - Better torrc example lines for dirbindaddress and orbindaddress.
16949 - Improved bounds checking on parsed ints (e.g. config options and
16950 the ones we find in directories.)
16951 - Stop using separate defaults for no-config-file and
16952 empty-config-file. Now you have to explicitly turn off SocksPort,
16953 if you don't want it open.
16954 - We were starting to daemonize before we opened our logs, so if
16955 there were any problems opening logs, we would complain to stderr,
16956 which wouldn't work, and then mysteriously exit.
16957 - If a verified OR connects to us before he's uploaded his descriptor,
16958 or we verify him and hup but he still has the original TLS
16959 connection, then conn->nickname is still set like he's unverified.
16961 o Code security improvements, inspired by Ilja:
16962 - tor_snprintf wrapper over snprintf with consistent (though not C99)
16964 - Replace sprintf with tor_snprintf. (I think they were all safe, but
16966 - Replace strcpy/strncpy with strlcpy in more places.
16967 - Avoid strcat; use tor_snprintf or strlcat instead.
16969 o Features (circuits and streams):
16970 - New circuit building strategy: keep a list of ports that we've
16971 used in the past 6 hours, and always try to have 2 circuits open
16972 or on the way that will handle each such port. Seed us with port
16973 80 so web users won't complain that Tor is "slow to start up".
16974 - Make kill -USR1 dump more useful stats about circuits.
16975 - When warning about retrying or giving up, print the address, so
16976 the user knows which one it's talking about.
16977 - If you haven't used a clean circuit in an hour, throw it away,
16978 just to be on the safe side. (This means after 6 hours a totally
16979 unused Tor client will have no circuits open.)
16980 - Support "foo.nickname.exit" addresses, to let Alice request the
16981 address "foo" as viewed by exit node "nickname". Based on a patch
16982 from Geoff Goodell.
16983 - If your requested entry or exit node has advertised bandwidth 0,
16985 - Be more greedy about filling up relay cells -- we try reading again
16986 once we've processed the stuff we read, in case enough has arrived
16987 to fill the last cell completely.
16988 - Refuse application socks connections to port 0.
16989 - Use only 0.0.9pre1 and later servers for resolve cells.
16991 o Features (bandwidth):
16992 - Hibernation: New config option "AccountingMax" lets you
16993 set how many bytes per month (in each direction) you want to
16994 allow your server to consume. Rather than spreading those
16995 bytes out evenly over the month, we instead hibernate for some
16996 of the month and pop up at a deterministic time, work until
16997 the bytes are consumed, then hibernate again. Config option
16998 "MonthlyAccountingStart" lets you specify which day of the month
16999 your billing cycle starts on.
17000 - Implement weekly/monthly/daily accounting: now you specify your
17001 hibernation properties by
17002 AccountingMax N bytes|KB|MB|GB|TB
17003 AccountingStart day|week|month [day] HH:MM
17004 Defaults to "month 1 0:00".
17005 - Let bandwidth and interval config options be specified as 5 bytes,
17006 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
17008 o Features (directories):
17009 - New "router-status" line in directory, to better bind each verified
17010 nickname to its identity key.
17011 - Clients can ask dirservers for /dir.z to get a compressed version
17012 of the directory. Only works for servers running 0.0.9, of course.
17013 - Make clients cache directories and use them to seed their router
17014 lists at startup. This means clients have a datadir again.
17015 - Respond to content-encoding headers by trying to uncompress as
17017 - Clients and servers now fetch running-routers; cache
17018 running-routers; compress running-routers; serve compressed
17020 - Make moria2 advertise a dirport of 80, so people behind firewalls
17021 will be able to get a directory.
17022 - Http proxy support
17023 - Dirservers translate requests for http://%s:%d/x to /x
17024 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
17025 be routed through this host.
17026 - Clients ask for /tor/x rather than /x for new enough dirservers.
17027 This way we can one day coexist peacefully with apache.
17028 - Clients specify a "Host: %s%d" http header, to be compatible
17029 with more proxies, and so running squid on an exit node can work.
17030 - Protect dirservers from overzealous descriptor uploading -- wait
17031 10 seconds after directory gets dirty, before regenerating.
17033 o Features (packages and install):
17034 - Add NSI installer contributed by J Doe.
17035 - Apply NT service patch from Osamu Fujino. Still needs more work.
17036 - Commit VC6 and VC7 workspace/project files.
17037 - Commit a tor.spec for making RPM files, with help from jbash.
17038 - Add contrib/torctl.in contributed by Glenn Fink.
17039 - Make expand_filename handle ~ and ~username.
17040 - Use autoconf to enable largefile support where necessary. Use
17041 ftello where available, since ftell can fail at 2GB.
17042 - Ship src/win32/ in the tarball, so people can use it to build.
17043 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
17046 o Features (ui controller):
17047 - Control interface: a separate program can now talk to your
17048 client/server over a socket, and get/set config options, receive
17049 notifications of circuits and streams starting/finishing/dying,
17050 bandwidth used, etc. The next step is to get some GUIs working.
17051 Let us know if you want to help out. See doc/control-spec.txt .
17052 - Ship a contrib/tor-control.py as an example script to interact
17053 with the control port.
17054 - "tor --hash-password zzyxz" will output a salted password for
17055 use in authenticating to the control interface.
17056 - Implement the control-spec's SAVECONF command, to write your
17057 configuration to torrc.
17058 - Get cookie authentication for the controller closer to working.
17059 - When set_conf changes our server descriptor, upload a new copy.
17060 But don't upload it too often if there are frequent changes.
17062 o Features (config and command-line):
17063 - Deprecate unofficial config option abbreviations, and abbreviations
17064 not on the command line.
17065 - Configuration infrastructure support for warning on obsolete
17067 - Give a slightly more useful output for "tor -h".
17068 - Break DirFetchPostPeriod into:
17069 - DirFetchPeriod for fetching full directory,
17070 - StatusFetchPeriod for fetching running-routers,
17071 - DirPostPeriod for posting server descriptor,
17072 - RendPostPeriod for posting hidden service descriptors.
17073 - New log format in config:
17074 "Log minsev[-maxsev] stdout|stderr|syslog" or
17075 "Log minsev[-maxsev] file /var/foo"
17076 - DirPolicy config option, to let people reject incoming addresses
17077 from their dirserver.
17078 - "tor --list-fingerprint" will list your identity key fingerprint
17080 - Make tor --version --version dump the cvs Id of every file.
17081 - New 'MyFamily nick1,...' config option for a server to
17082 specify other servers that shouldn't be used in the same circuit
17083 with it. Only believed if nick1 also specifies us.
17084 - New 'NodeFamily nick1,nick2,...' config option for a client to
17085 specify nodes that it doesn't want to use in the same circuit.
17086 - New 'Redirectexit pattern address:port' config option for a
17087 server to redirect exit connections, e.g. to a local squid.
17088 - Add "pass" target for RedirectExit, to make it easier to break
17089 out of a sequence of RedirectExit rules.
17090 - Make the dirservers file obsolete.
17091 - Include a dir-signing-key token in directories to tell the
17092 parsing entity which key is being used to sign.
17093 - Remove the built-in bulky default dirservers string.
17094 - New config option "Dirserver %s:%d [fingerprint]", which can be
17095 repeated as many times as needed. If no dirservers specified,
17096 default to moria1,moria2,tor26.
17097 - Make 'Routerfile' config option obsolete.
17098 - Discourage people from setting their dirfetchpostperiod more often
17099 than once per minute.
17101 o Features (other):
17102 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
17103 get back to normal.)
17104 - Accept *:706 (silc) in default exit policy.
17105 - Implement new versioning format for post 0.1.
17106 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
17107 log more informatively.
17108 - Check clock skew for verified servers, but allow unverified
17109 servers and clients to have any clock skew.
17110 - Make sure the hidden service descriptors are at a random offset
17111 from each other, to hinder linkability.
17112 - Clients now generate a TLS cert too, in preparation for having
17113 them act more like real nodes.
17114 - Add a pure-C tor-resolve implementation.
17115 - Use getrlimit and friends to ensure we can reach MaxConn (currently
17116 1024) file descriptors.
17117 - Raise the max dns workers from 50 to 100.
17120 Changes in version 0.0.8.1 - 2004-10-13
17122 - Fix a seg fault that can be triggered remotely for Tor
17123 clients/servers with an open dirport.
17124 - Fix a rare assert trigger, where routerinfos for entries in
17125 our cpath would expire while we're building the path.
17126 - Fix a bug in OutboundBindAddress so it (hopefully) works.
17127 - Fix a rare seg fault for people running hidden services on
17128 intermittent connections.
17129 - Fix a bug in parsing opt keywords with objects.
17130 - Fix a stale pointer assert bug when a stream detaches and
17132 - Fix a string format vulnerability (probably not exploitable)
17133 in reporting stats locally.
17134 - Fix an assert trigger: sometimes launching circuits can fail
17135 immediately, e.g. because too many circuits have failed recently.
17136 - Fix a compile warning on 64 bit platforms.
17139 Changes in version 0.0.8 - 2004-08-25
17141 - Made our unit tests compile again on OpenBSD 3.5, and tor
17142 itself compile again on OpenBSD on a sparc64.
17143 - We were neglecting milliseconds when logging on win32, so
17144 everything appeared to happen at the beginning of each second.
17145 - Check directory signature _before_ you decide whether you're
17146 you're running an obsolete version and should exit.
17147 - Check directory signature _before_ you parse the running-routers
17148 list to decide who's running.
17149 - Check return value of fclose while writing to disk, so we don't
17150 end up with broken files when servers run out of disk space.
17151 - Port it to SunOS 5.9 / Athena
17152 - Fix two bugs in saving onion keys to disk when rotating, so
17153 hopefully we'll get fewer people using old onion keys.
17154 - Remove our mostly unused -- and broken -- hex_encode()
17155 function. Use base16_encode() instead. (Thanks to Timo Lindfors
17156 for pointing out this bug.)
17157 - Only pick and establish intro points after we've gotten a
17159 - Fix assert triggers: if the other side returns an address 0.0.0.0,
17160 don't put it into the client dns cache.
17161 - If a begin failed due to exit policy, but we believe the IP
17162 address should have been allowed, switch that router to exitpolicy
17163 reject *:* until we get our next directory.
17165 o Protocol changes:
17166 - 'Extend' relay cell payloads now include the digest of the
17167 intended next hop's identity key. Now we can verify that we're
17168 extending to the right router, and also extend to routers we
17169 hadn't heard of before.
17172 - Tor nodes can now act as relays (with an advertised ORPort)
17173 without being manually verified by the dirserver operators.
17174 - Uploaded descriptors of unverified routers are now accepted
17175 by the dirservers, and included in the directory.
17176 - Verified routers are listed by nickname in the running-routers
17177 list; unverified routers are listed as "$<fingerprint>".
17178 - We now use hash-of-identity-key in most places rather than
17179 nickname or addr:port, for improved security/flexibility.
17180 - AllowUnverifiedNodes config option to let circuits choose no-name
17181 routers in entry,middle,exit,introduction,rendezvous positions.
17182 Allow middle and rendezvous positions by default.
17183 - When picking unverified routers, skip those with low uptime and/or
17184 low bandwidth, depending on what properties you care about.
17185 - ClientOnly option for nodes that never want to become servers.
17186 - Directory caching.
17187 - "AuthoritativeDir 1" option for the official dirservers.
17188 - Now other nodes (clients and servers) will cache the latest
17189 directory they've pulled down.
17190 - They can enable their DirPort to serve it to others.
17191 - Clients will pull down a directory from any node with an open
17192 DirPort, and check the signature/timestamp correctly.
17193 - Authoritative dirservers now fetch directories from other
17194 authdirservers, to stay better synced.
17195 - Running-routers list tells who's down also, along with noting
17196 if they're verified (listed by nickname) or unverified (listed
17198 - Allow dirservers to serve running-router list separately.
17199 This isn't used yet.
17200 - You can now fetch $DIRURL/running-routers to get just the
17201 running-routers line, not the whole descriptor list. (But
17202 clients don't use this yet.)
17203 - Clients choose nodes proportional to advertised bandwidth.
17204 - Clients avoid using nodes with low uptime as introduction points.
17205 - Handle servers with dynamic IP addresses: don't just replace
17206 options->Address with the resolved one at startup, and
17207 detect our address right before we make a routerinfo each time.
17208 - 'FascistFirewall' option to pick dirservers and ORs on specific
17209 ports; plus 'FirewallPorts' config option to tell FascistFirewall
17210 which ports are open. (Defaults to 80,443)
17211 - Try other dirservers immediately if the one you try is down. This
17212 should tolerate down dirservers better now.
17213 - ORs connect-on-demand to other ORs
17214 - If you get an extend cell to an OR you're not connected to,
17215 connect, handshake, and forward the create cell.
17216 - The authoritative dirservers stay connected to everybody,
17217 and everybody stays connected to 0.0.7 servers, but otherwise
17218 clients/servers expire unused connections after 5 minutes.
17219 - When servers get a sigint, they delay 30 seconds (refusing new
17220 connections) then exit. A second sigint causes immediate exit.
17221 - File and name management:
17222 - Look for .torrc if no CONFDIR "torrc" is found.
17223 - If no datadir is defined, then choose, make, and secure ~/.tor
17225 - If torrc not found, exitpolicy reject *:*.
17226 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
17227 - If no nickname is defined, derive default from hostname.
17228 - Rename secret key files, e.g. identity.key -> secret_id_key,
17229 to discourage people from mailing their identity key to tor-ops.
17230 - Refuse to build a circuit before the directory has arrived --
17231 it won't work anyway, since you won't know the right onion keys
17233 - Parse tor version numbers so we can do an is-newer-than check
17234 rather than an is-in-the-list check.
17235 - New socks command 'resolve', to let us shim gethostbyname()
17237 - A 'tor_resolve' script to access the socks resolve functionality.
17238 - A new socks-extensions.txt doc file to describe our
17239 interpretation and extensions to the socks protocols.
17240 - Add a ContactInfo option, which gets published in descriptor.
17241 - Write tor version at the top of each log file
17242 - New docs in the tarball:
17244 - Document that you should proxy your SSL traffic too.
17245 - Log a warning if the user uses an unsafe socks variant, so people
17246 are more likely to learn about privoxy or socat.
17247 - Log a warning if you're running an unverified server, to let you
17248 know you might want to get it verified.
17249 - Change the default exit policy to reject the default edonkey,
17250 kazaa, gnutella ports.
17251 - Add replace_file() to util.[ch] to handle win32's rename().
17252 - Publish OR uptime in descriptor (and thus in directory) too.
17253 - Remember used bandwidth (both in and out), and publish 15-minute
17254 snapshots for the past day into our descriptor.
17255 - Be more aggressive about trying to make circuits when the network
17256 has changed (e.g. when you unsuspend your laptop).
17257 - Check for time skew on http headers; report date in response to
17259 - If the entrynode config line has only one node, don't pick it as
17261 - Add strict{entry|exit}nodes config options. If set to 1, then
17262 we refuse to build circuits that don't include the specified entry
17264 - OutboundBindAddress config option, to bind to a specific
17265 IP address for outgoing connect()s.
17266 - End truncated log entries (e.g. directories) with "[truncated]".
17269 Changes in version 0.0.7.3 - 2004-08-12
17270 o Stop dnsworkers from triggering an assert failure when you
17271 ask them to resolve the host "".
17274 Changes in version 0.0.7.2 - 2004-07-07
17275 o A better fix for the 0.0.0.0 problem, that will hopefully
17276 eliminate the remaining related assertion failures.
17279 Changes in version 0.0.7.1 - 2004-07-04
17280 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
17281 since internally we use 0.0.0.0 to signify "not yet resolved".
17284 Changes in version 0.0.7 - 2004-06-07
17285 o Fixes for crashes and other obnoxious bugs:
17286 - Fix an epipe bug: sometimes when directory connections failed
17287 to connect, we would give them a chance to flush before closing
17289 - When we detached from a circuit because of resolvefailed, we
17290 would immediately try the same circuit twice more, and then
17291 give up on the resolve thinking we'd tried three different
17293 - Limit the number of intro circuits we'll attempt to build for a
17294 hidden service per 15-minute period.
17295 - Check recommended-software string *early*, before actually parsing
17296 the directory. Thus we can detect an obsolete version and exit,
17297 even if the new directory format doesn't parse.
17298 o Fixes for security bugs:
17299 - Remember which nodes are dirservers when you startup, and if a
17300 random OR enables his dirport, don't automatically assume he's
17301 a trusted dirserver.
17303 - Directory connections were asking the wrong poll socket to
17304 start writing, and not asking themselves to start writing.
17305 - When we detached from a circuit because we sent a begin but
17306 didn't get a connected, we would use it again the first time;
17307 but after that we would correctly switch to a different one.
17308 - Stop warning when the first onion decrypt attempt fails; they
17309 will sometimes legitimately fail now that we rotate keys.
17310 - Override unaligned-access-ok check when $host_cpu is ia64 or
17311 arm. Apparently they allow it but the kernel whines.
17312 - Dirservers try to reconnect periodically too, in case connections
17314 - Fix some memory leaks in directory servers.
17315 - Allow backslash in Win32 filenames.
17316 - Made Tor build complain-free on FreeBSD, hopefully without
17317 breaking other BSD builds. We'll see.
17318 - Check directory signatures based on name of signer, not on whom
17319 we got the directory from. This will let us cache directories more
17321 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
17324 - Doxygen markup on all functions and global variables.
17325 - Make directory functions update routerlist, not replace it. So
17326 now directory disagreements are not so critical a problem.
17327 - Remove the upper limit on number of descriptors in a dirserver's
17328 directory (not that we were anywhere close).
17329 - Allow multiple logfiles at different severity ranges.
17330 - Allow *BindAddress to specify ":port" rather than setting *Port
17331 separately. Allow multiple instances of each BindAddress config
17332 option, so you can bind to multiple interfaces if you want.
17333 - Allow multiple exit policy lines, which are processed in order.
17334 Now we don't need that huge line with all the commas in it.
17335 - Enable accept/reject policies on SOCKS connections, so you can bind
17336 to 0.0.0.0 but still control who can use your OP.
17337 - Updated the man page to reflect these features.
17340 Changes in version 0.0.6.2 - 2004-05-16
17341 o Our integrity-checking digest was checking only the most recent cell,
17342 not the previous cells like we'd thought.
17343 Thanks to Stefan Mark for finding the flaw!
17346 Changes in version 0.0.6.1 - 2004-05-06
17347 o Fix two bugs in our AES counter-mode implementation (this affected
17348 onion-level stream encryption, but not TLS-level). It turns
17349 out we were doing something much more akin to a 16-character
17350 polyalphabetic cipher. Oops.
17351 Thanks to Stefan Mark for finding the flaw!
17352 o Retire moria3 as a directory server, and add tor26 as a directory
17356 Changes in version 0.0.6 - 2004-05-02
17358 - Hidden services and rendezvous points are implemented. Go to
17359 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
17360 hidden services. (This only works via a socks4a proxy such as
17361 Privoxy, and currently it's quite slow.)
17362 - We now rotate link (tls context) keys and onion keys.
17363 - CREATE cells now include oaep padding, so you can tell
17364 if you decrypted them correctly.
17365 - Retry stream correctly when we fail to connect because of
17366 exit-policy-reject (should try another) or can't-resolve-address.
17367 - When we hup a dirserver and we've *removed* a server from the
17368 approved-routers list, now we remove that server from the
17369 in-memory directories too.
17370 - Add bandwidthburst to server descriptor.
17371 - Directories now say which dirserver signed them.
17372 - Use a tor_assert macro that logs failed assertions too.
17373 - Since we don't support truncateds much, don't bother sending them;
17374 just close the circ.
17375 - Fetch randomness from /dev/urandom better (not via fopen/fread)
17376 - Better debugging for tls errors
17377 - Set Content-Type on the directory and hidserv descriptor.
17378 - Remove IVs from cipher code, since AES-ctr has none.
17380 - Fix an assert trigger for exit nodes that's been plaguing us since
17381 the days of 0.0.2prexx (thanks weasel!)
17382 - Fix a bug where we were closing tls connections intermittently.
17383 It turns out openssl keeps its errors around -- so if an error
17384 happens, and you don't ask about it, and then another openssl
17385 operation happens and succeeds, and you ask if there was an error,
17386 it tells you about the first error.
17387 - Fix a bug that's been lurking since 27 may 03 (!)
17388 When passing back a destroy cell, we would use the wrong circ id.
17389 - Don't crash if a conn that sent a begin has suddenly lost its circuit.
17390 - Some versions of openssl have an SSL_pending function that erroneously
17391 returns bytes when there is a non-application record pending.
17392 - Win32 fixes. Tor now compiles on win32 with no warnings/errors.
17393 o We were using an array of length zero in a few places.
17394 o Win32's gethostbyname can't resolve an IP to an IP.
17395 o Win32's close can't close a socket.
17396 o Handle windows socket errors correctly.
17398 - check for <sys/limits.h> so we build on FreeBSD again, and
17399 <machine/limits.h> for NetBSD.
17402 Changes in version 0.0.5 - 2004-03-30
17403 o Install torrc as torrc.sample -- we no longer clobber your
17405 o Fix mangled-state bug in directory fetching (was causing sigpipes).
17406 o Only build circuits after we've fetched the directory: clients were
17407 using only the directory servers before they'd fetched a directory.
17408 This also means longer startup time; so it goes.
17409 o Fix an assert trigger where an OP would fail to handshake, and we'd
17410 expect it to have a nickname.
17411 o Work around a tsocks bug: do a socks reject when AP connection dies
17412 early, else tsocks goes into an infinite loop.
17413 o Hold socks connection open until reply is flushed (if possible)
17414 o Make exit nodes resolve IPs to IPs immediately, rather than asking
17415 the dns farm to do it.
17416 o Fix c99 aliasing warnings in rephist.c
17417 o Don't include server descriptors that are older than 24 hours in the
17419 o Give socks 'reject' replies their whole 15s to attempt to flush,
17420 rather than seeing the 60s timeout and assuming the flush had failed.
17421 o Clean automake droppings from the cvs repository
17422 o Add in a 'notice' log level for things the operator should hear
17423 but that aren't warnings
17426 Changes in version 0.0.4 - 2004-03-26
17427 o When connecting to a dirserver or OR and the network is down,
17431 Changes in version 0.0.3 - 2004-03-26
17432 o Warn and fail if server chose a nickname with illegal characters
17433 o Port to Solaris and Sparc:
17434 - include missing header fcntl.h
17435 - have autoconf find -lsocket -lnsl automatically
17436 - deal with hardware word alignment
17437 - make uname() work (solaris has a different return convention)
17438 - switch from using signal() to sigaction()
17439 o Preliminary work on reputation system:
17440 - Keep statistics on success/fail of connect attempts; they're published
17441 by kill -USR1 currently.
17442 - Add a RunTesting option to try to learn link state by creating test
17443 circuits, even when SocksPort is off.
17444 - Remove unused open circuits when there are too many.
17447 Changes in version 0.0.2 - 2004-03-19
17448 - Include strlcpy and strlcat for safer string ops
17449 - define INADDR_NONE so we compile (but still not run) on solaris
17452 Changes in version 0.0.2pre27 - 2004-03-14
17454 - Allow internal tor networks (we were rejecting internal IPs,
17455 now we allow them if they're set explicitly).
17456 - And fix a few endian issues.
17459 Changes in version 0.0.2pre26 - 2004-03-14
17461 - If a stream times out after 15s without a connected cell, don't
17462 try that circuit again: try a new one.
17463 - Retry streams at most 4 times. Then give up.
17464 - When a dirserver gets a descriptor from an unknown router, it
17465 logs its fingerprint (so the dirserver operator can choose to
17466 accept it even without mail from the server operator).
17467 - Inform unapproved servers when we reject their descriptors.
17468 - Make tor build on Windows again. It works as a client, who knows
17470 - Clearer instructions in the torrc for how to set up a server.
17471 - Be more efficient about reading fd's when our global token bucket
17472 (used for rate limiting) becomes empty.
17474 - Stop asserting that computers always go forward in time. It's
17476 - When we sent a cell (e.g. destroy) and then marked an OR connection
17477 expired, we might close it before finishing a flush if the other
17478 side isn't reading right then.
17479 - Don't allow dirservers to start if they haven't defined
17480 RecommendedVersions
17481 - We were caching transient dns failures. Oops.
17482 - Prevent servers from publishing an internal IP as their address.
17483 - Address a strcat vulnerability in circuit.c
17486 Changes in version 0.0.2pre25 - 2004-03-04
17488 - Put the OR's IP in its router descriptor, not its fqdn. That way
17489 we'll stop being stalled by gethostbyname for nodes with flaky dns,
17492 - If the user typed in an address that didn't resolve, the server
17496 Changes in version 0.0.2pre24 - 2004-03-03
17498 - Fix an assertion failure in dns.c, where we were trying to dequeue
17499 a pending dns resolve even if it wasn't pending
17500 - Fix a spurious socks5 warning about still trying to write after the
17501 connection is finished.
17502 - Hold certain marked_for_close connections open until they're finished
17503 flushing, rather than losing bytes by closing them too early.
17504 - Correctly report the reason for ending a stream
17505 - Remove some duplicate calls to connection_mark_for_close
17506 - Put switch_id and start_daemon earlier in the boot sequence, so it
17507 will actually try to chdir() to options.DataDirectory
17508 - Make 'make test' exit(1) if a test fails; fix some unit tests
17509 - Make tor fail when you use a config option it doesn't know about,
17510 rather than warn and continue.
17511 - Make --version work
17512 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
17515 Changes in version 0.0.2pre23 - 2004-02-29
17517 - Print a statement when the first circ is finished, so the user
17518 knows it's working.
17519 - If a relay cell is unrecognized at the end of the circuit,
17520 send back a destroy. (So attacks to mutate cells are more
17522 - New config option 'excludenodes' to avoid certain nodes for circuits.
17523 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
17524 so you can collect coredumps there.
17526 - Fix a bug in tls flushing where sometimes data got wedged and
17527 didn't flush until more data got sent. Hopefully this bug was
17528 a big factor in the random delays we were seeing.
17529 - Make 'connected' cells include the resolved IP, so the client
17530 dns cache actually gets populated.
17531 - Disallow changing from ORPort=0 to ORPort>0 on hup.
17532 - When we time-out on a stream and detach from the circuit, send an
17533 end cell down it first.
17534 - Only warn about an unknown router (in exitnodes, entrynodes,
17535 excludenodes) after we've fetched a directory.
17538 Changes in version 0.0.2pre22 - 2004-02-26
17540 - Servers publish less revealing uname information in descriptors.
17541 - More memory tracking and assertions, to crash more usefully when
17543 - If the default torrc isn't there, just use some default defaults.
17544 Plus provide an internal dirservers file if they don't have one.
17545 - When the user tries to use Tor as an http proxy, give them an http
17546 501 failure explaining that we're a socks proxy.
17547 - Dump a new router.desc on hup, to help confused people who change
17548 their exit policies and then wonder why router.desc doesn't reflect
17550 - Clean up the generic tor.sh init script that we ship with.
17552 - If the exit stream is pending on the resolve, and a destroy arrives,
17553 then the stream wasn't getting removed from the pending list. I
17554 think this was the one causing recent server crashes.
17555 - Use a more robust poll on OSX 10.3, since their poll is flaky.
17556 - When it couldn't resolve any dirservers, it was useless from then on.
17557 Now it reloads the RouterFile (or default dirservers) if it has no
17559 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
17560 many users don't even *have* a /usr/local/sbin/.
17563 Changes in version 0.0.2pre21 - 2004-02-18
17565 - There's a ChangeLog file that actually reflects the changelog.
17566 - There's a 'torify' wrapper script, with an accompanying
17567 tor-tsocks.conf, that simplifies the process of using tsocks for
17568 tor. It even has a man page.
17569 - The tor binary gets installed to sbin rather than bin now.
17570 - Retry streams where the connected cell hasn't arrived in 15 seconds
17571 - Clean up exit policy handling -- get the default out of the torrc,
17572 so we can update it without forcing each server operator to fix
17574 - Allow imaps and pop3s in default exit policy
17576 - Prevent picking middleman nodes as the last node in the circuit
17579 Changes in version 0.0.2pre20 - 2004-01-30
17581 - We now have a deb package, and it's in debian unstable. Go to
17582 it, apt-getters. :)
17583 - I've split the TotalBandwidth option into BandwidthRate (how many
17584 bytes per second you want to allow, long-term) and
17585 BandwidthBurst (how many bytes you will allow at once before the cap
17586 kicks in). This better token bucket approach lets you, say, set
17587 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
17588 performance while not exceeding your monthly bandwidth quota.
17589 - Push out a tls record's worth of data once you've got it, rather
17590 than waiting until you've read everything waiting to be read. This
17591 may improve performance by pipelining better. We'll see.
17592 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
17593 from failed circuits (if they haven't been connected yet) and attach
17595 - Expire old streams that haven't managed to connect. Some day we'll
17596 have them reattach to new circuits instead.
17599 - Fix several memory leaks that were causing servers to become bloated
17601 - Fix a few very rare assert triggers. A few more remain.
17602 - Setuid to User _before_ complaining about running as root.
17605 Changes in version 0.0.2pre19 - 2004-01-07
17607 - Fix deadlock condition in dns farm. We were telling a child to die by
17608 closing the parent's file descriptor to him. But newer children were
17609 inheriting the open file descriptor from the parent, and since they
17610 weren't closing it, the socket never closed, so the child never read
17611 eof, so he never knew to exit. Similarly, dns workers were holding
17612 open other sockets, leading to all sorts of chaos.
17613 - New cleaner daemon() code for forking and backgrounding.
17614 - If you log to a file, it now prints an entry at the top of the
17615 logfile so you know it's working.
17616 - The onionskin challenge length was 30 bytes longer than necessary.
17617 - Started to patch up the spec so it's not quite so out of date.
17620 Changes in version 0.0.2pre18 - 2004-01-02
17622 - Fix endian issues with the 'integrity' field in the relay header.
17623 - Fix a potential bug where connections in state
17624 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
17627 Changes in version 0.0.2pre17 - 2003-12-30
17629 - Made --debuglogfile (or any second log file, actually) work.
17630 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
17631 adversary could force us into an infinite loop.
17634 - Each onionskin handshake now includes a hash of the computed key,
17635 to prove the server's identity and help perfect forward secrecy.
17636 - Changed cell size from 256 to 512 bytes (working toward compatibility
17638 - Changed cell length to 2 bytes, and moved it to the relay header.
17639 - Implemented end-to-end integrity checking for the payloads of
17641 - Separated streamid from 'recognized' (otherwise circuits will get
17642 messed up when we try to have streams exit from the middle). We
17643 use the integrity-checking to confirm that a cell is addressed to
17645 - Randomize the initial circid and streamid values, so an adversary who
17646 breaks into a node can't learn how many circuits or streams have
17650 Changes in version 0.0.2pre16 - 2003-12-14
17652 - Fixed a bug that made HUP trigger an assert
17653 - Fixed a bug where a circuit that immediately failed wasn't being
17654 counted as a failed circuit in counting retries.
17657 - Now we close the circuit when we get a truncated cell: otherwise we're
17658 open to an anonymity attack where a bad node in the path truncates
17659 the circuit and then we open streams at him.
17660 - Add port ranges to exit policies
17661 - Add a conservative default exit policy
17662 - Warn if you're running tor as root
17663 - on HUP, retry OR connections and close/rebind listeners
17664 - options.EntryNodes: try these nodes first when picking the first node
17665 - options.ExitNodes: if your best choices happen to include any of
17666 your preferred exit nodes, you choose among just those preferred
17668 - options.ExcludedNodes: nodes that are never picked in path building
17671 Changes in version 0.0.2pre15 - 2003-12-03
17672 o Robustness and bugfixes:
17673 - Sometimes clients would cache incorrect DNS resolves, which would
17674 really screw things up.
17675 - An OP that goes offline would slowly leak all its sockets and stop
17677 - A wide variety of bugfixes in exit node selection, exit policy
17678 handling, and processing pending streams when a new circuit is
17680 - Pick nodes for a path only from those the directory says are up
17681 - Choose randomly from all running dirservers, not always the first one
17682 - Increase allowed http header size for directory fetch.
17683 - Stop writing to stderr (if we're daemonized it will be closed).
17684 - Enable -g always, so cores will be more useful to me.
17685 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
17688 - Wrote a man page. It lists commonly used options.
17691 - Change default loglevel to warn.
17692 - Make PidFile default to null rather than littering in your CWD.
17693 - OnionRouter config option is now obsolete. Instead it just checks
17695 - Moved to a single unified torrc file for both clients and servers.
17698 Changes in version 0.0.2pre14 - 2003-11-29
17699 o Robustness and bugfixes:
17700 - Force the admin to make the DataDirectory himself
17701 - to get ownership/permissions right
17702 - so clients no longer make a DataDirectory and then never use it
17703 - fix bug where a client who was offline for 45 minutes would never
17704 pull down a directory again
17705 - fix (or at least hide really well) the dns assert bug that was
17706 causing server crashes
17707 - warnings and improved robustness wrt clockskew for certs
17708 - use the native daemon(3) to daemonize, when available
17709 - exit if bind() fails
17710 - exit if neither socksport nor orport is defined
17711 - include our own tor_timegm (Win32 doesn't have its own)
17712 - bugfix for win32 with lots of connections
17713 - fix minor bias in PRNG
17714 - make dirserver more robust to corrupt cached directory
17717 - Wrote the design document (woo)
17719 o Circuit building and exit policies:
17720 - Circuits no longer try to use nodes that the directory has told them
17722 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
17723 bitcounts (18.0.0.0/8).
17724 - Make AP connections standby for a circuit if no suitable circuit
17725 exists, rather than failing
17726 - Circuits choose exit node based on addr/port, exit policies, and
17727 which AP connections are standing by
17728 - Bump min pathlen from 2 to 3
17729 - Relay end cells have a payload to describe why the stream ended.
17730 - If the stream failed because of exit policy, try again with a new
17732 - Clients have a dns cache to remember resolved addresses.
17733 - Notice more quickly when we have no working circuits
17736 - APPort is now called SocksPort
17737 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
17739 - RecommendedVersions is now a config variable rather than
17740 hardcoded (for dirservers)
17741 - Reloads config on HUP
17742 - Usage info on -h or --help
17743 - If you set User and Group config vars, it'll setu/gid to them.
17745 Changes in version 0.0.2pre13 - 2003-10-19
17746 o General stability:
17747 - SSL_write no longer fails when it returns WANTWRITE and the number
17748 of bytes in the buf has changed by the next SSL_write call.
17749 - Fix segfault fetching directory when network is down
17750 - Fix a variety of minor memory leaks
17751 - Dirservers reload the fingerprints file on HUP, so I don't have
17752 to take down the network when I approve a new router
17753 - Default server config file has explicit Address line to specify fqdn
17756 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
17757 - Make listener connections not ever alloc bufs
17759 o Autoconf improvements:
17760 - don't clobber an external CFLAGS in ./configure
17761 - Make install now works
17762 - create var/lib/tor on make install
17763 - autocreate a tor.sh initscript to help distribs
17764 - autocreate the torrc and sample-server-torrc with correct paths
17766 o Log files and Daemonizing now work:
17767 - If --DebugLogFile is specified, log to it at -l debug
17768 - If --LogFile is specified, use it instead of commandline
17769 - If --RunAsDaemon is set, tor forks and backgrounds on startup